-
Notifications
You must be signed in to change notification settings - Fork 31
Document Structure at Readthedocs #74
Copy link
Copy link
Open
Labels
DocumentationIssue / feature refers to docs not codeIssue / feature refers to docs not codeFeature requestSuggest an idea for this projectSuggest an idea for this projectHelp WantedNeed some help with this task.Need some help with this task.P0High priority issueHigh priority issue
Milestone
Metadata
Metadata
Assignees
Labels
DocumentationIssue / feature refers to docs not codeIssue / feature refers to docs not codeFeature requestSuggest an idea for this projectSuggest an idea for this projectHelp WantedNeed some help with this task.Need some help with this task.P0High priority issueHigh priority issue
Type
Fields
Give feedbackNo fields configured for issues without a type.
@Tlazypanda has a first draft full diagram of how the pieces of mojo global fit together and how to work together; we need to make a public version of that document and add it to our documentation.
https://hackmd.io/@itm2017004/ByX5A1fgP
What to do
Propose a diagram in the Moja global README.
Investigate and agree on the final diagram in the Moja global README.
Create a public version of the diagram and content.
Submit a pull request to about moja global.
Show diagram in the Moga global README
Why do it
Moja global has many projects with many contributors. We want contributors to spend time working on valuable areas of Moja global that help the project. By investing time and effort into the project, we want to reward that time and effort with accepted contributions. To accept meaningful contributions, we need to make it more clear how Moja global fits together and how to work together. This is part of internal communication.
Refer tolink to the map of current moja global GitHub repositories and the content within them.
The proposal documentation is here
These are created by https://github.com/sabitarao.
@Tlazypanda @gmajan