To ensure uniformity across all projects, I propose the following structure :

└── Project/
    ├── About project
    ├── Where it fits in the big picture
    ├── Prerequisites for the dev setup
    ├── Guide to using the project
    ├── Potential bugs that might be encountered

Feedback page can be included at the end of every section/page based on the content

Hey, I missed today's meet. Is it possible to provide the MoM?

Minutes of meeting (MoMs) of DWG (8 June, 2022): 1. Discussed spatial inputs used in

GCBM

simulation. You can look at the notebooks for each file here . I will be creating an issue to include

study_area.json

as a notebook in the same section. 2. We are proceeding with developing the community website though on a parallel branch, I will also be making an issue for that with the figma link attached. 3. For folks who want to know about

GCBM

, can undergo the

GCBM

training, for now it has been uploaded in a google drive here, slide and hands-on exercises. 4. @few-sugar-35346 showcased the feedback funnel she has been building for the documentation channel. For people who may have better suggestions to improve the UI can reach out to her. She also shared her work on documenting the

GCBM

, you can find all the link in this particular text. 5. We are onboarding a new sponsor- Microsoft Azure and folks who who could like to work with Azure in the moja ecosystem can get in touch with @bumpy-plastic-43748. 6. @bumpy-plastic-43748 suggested to start a new project where some people can create demos for all of our repositories, the video should cover everything from setting up the project to the entire workflow. 7. I will be helping a few people with the new

GCBM

workflow, if you are someone who's interested, you can reach out to me so I can make sure if you are included in the meet. 8. Namya suggested a way to bring uniformity in project documentation by following a uniform way to the structure our documentations. 9. @full-baker-30162 talked about the project and milestones she will be working on as an Outreachy intern. 10. @steep-church-89185 suggested a way through which we can improve the current documentation for FLINT.cloud, you can find more about it here . I'm glad a lot of people decided to join us today and I hope it stays the same for the rest of the meetings!

has renamed the channel from "documentation" to "08-documentation"

@bumpy-plastic-43748 @mysterious-potato-97426 @mammoth-zebra-48407 in the readme of moja global main page, can we have these sort of charts explaining how the various projects work together. I saw it over OpenMined github landing page readme file. So, I thought, it will great to implement it here as well. I believe it will act as good way to understand the workflow of the organization as a whole. Feel free to drop your thoughts over this.

<!channel>, The Documentation working group meet will start today at 6 pm IST. We have a few agendas for today's meet: 1. I will be presenting a demo for the GCBM API. 2. Audit existing docs: we are planning to start with Understanding the FLINT section. 3. Co-ordinate the work around revamping the community website. https://meet.google.com/euc-txfg-zrq

MoM for today's DWG meet: 1. We have started to audit the existing docs, interested contributors can read about pools, operations, and modules and submit a feedback using the feedback funnel(at the end of each section) on what could be improved or maybe a brief summary of their over-all experience while going through these topics. (This does count as a valid contribution since it will help us tremendously to improve our overall docs experience.) 2. I put up a demo for the new

REST_API_GCBM

, if you wish to run it yourself, you can go through this doc having all the required commands. @lemon-traffic-55355 will be volunteering to help develop documentation for the new run. For now, its only running on Linux. 3. @few-sugar-35346 and @microscopic-monitor-39787 presented the work that they have been doing as a part of their GSoD internships. 4. The new community website is finally coming to life, thanks to @lively-advantage-93462 and @silly-addition-53033!

Reminder: We had started auditing the existing docs two weeks back. People can start with pools, operations, and modules and submit a feedback using the feedback funnel(at the end of each section) on what could be improved or maybe a brief summary of their over-all experience while going through these topics. We don't have a lot of responses yet and we won't be able to move to the next section without it. Could help us tremendously on improving the existing docs.

<!channel> We will be having the Documentation working group meet at 6 pm IST today. We have a few topics to discuss: 1. The main agenda for today will be discussing and dividing the work for the upcoming GCBM API development. 2. Update on docs audit. https://meet.google.com/euc-txfg-zrq

Cool video on documentation

hi, I'd like to work on issue #175

hi, I've opened a teeny-tiny doc issue (https://github.com/moja-global/FLINT/issues/120), I wasn't sure whom to tag. Could a maintainer pls take a look and let me know if I can go ahead with working on it?

do we need to do the DCO sign off on doc update PRs?

Hyy everyone! Anyone here participate in lfx mentorship?

Hi @careful-lizard-83404 @red-truck-36891 @bumpy-plastic-43748 I am a MERN developer by profession and am interested in contributing to the technical writing FLINT project. Hope I am not late 😅

Good day everyone please we are looking to restart the documentation working group meet, please fill out this form to indicate the most suitable day and time for the meet https://docs.google.com/forms/d/e/1FAIpQLSfdAtrUBlu_FkZbA4hKQCnpFTpmfk3mLS2mBUGD7qw-Kq5GzA/viewform

Figure 6 is cool too.

hey everybody remeber we are having a documentation working group meetup on Wednesday 31st of August 2022 7pm IST, to discuss the land sector datasets and how we can contribute to moja global, fill out this form if you'd like a reminder https://docs.google.com/forms/d/e/1FAIpQLSfdAtrUBlu_FkZbA4hKQCnpFTpmfk3mLS2mBUGD7qw-Kq5GzA/viewform

Hello can I have an invite to the meet?

the meeting will start in about 10 minutes everybody

heyy we are live come join us

hey everybody, this is the recording of the meeting https://tldv.io/app/meetings/630f639eb0399a0014192805/

Hello, here is the presentation from Land_sector dataset meet with @microscopic-monitor-39787. You can check out the repo and index to see which dataset are currently processed and in use by the flint. Also, the repo would contain more information on how to preprocess raw datasets. "Please review individual dataset licence terms and conditions. Please note, while all care has been taken to ensure data is open data available for use, individual datasets will have their own license conditions and citation requirements." Some catalogs where you can find dataset to contribute include FAO data, Global forest watch, Lucid, FAO soil hub, data world etc. As long as the dataset is of AFOLU sector, open and the license is admissible, it would be useful for Moja Global.

sorry ya'll, i missed the DWG meet this time :(( i've watched the recording tho, great presentation @few-room-82258 🙌 i'll make sure i'm there at future meetings!

I've raised an issue, now I have 2 options: 1) use a title link to each and every abbreviation and direct the user to that particular page where the abbreviation was first introduced but while using this, the user might find it difficult to navigate back to the page. 2) use a footer note and describe each and every abbreviation on that page itself but this might be useless for those who familiar with these terms and provide more information on that page. What should I do?

FLINT.Cloud's New docs theme 🤩

hey @careful-lizard-83404, I had a chat with @victorious-ability-26142 regarding putting images in the FLINT Handbook (like these). Your thoughts on this? Also, where could we extract such images from?

I guess alignment issues? Try aligning ".. list-table:: Title" with ".. toctree:: " directive. Otherwise the hidden hides the table also.

Hi

I am Kanu mike chibundu