You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think we can build an index in this repo, and split the document for three part:
Developer document
User document
Learning material for DIY lover
Therefore, we will be able to maintain a loose organization with some support from project management tools and provide possibility for developer, user, learner and allow other idea to join the discussion.
Index (Table of Content)
README.md
Introduction of the latest development
CHANGELOG news of all related repository
Collect issues on requirement level / new idea
Index of other repository and documents
Raise new idea for noise meter in Civic Tech event (30 sec pitch section)
Developer document
Information needs to know for building the production level deliverable
Project plan and point of contact for different resources
Deliverable list
Quality control HOW-TO
Maintenance task list
Project deliverable feature list
Architecture design and other UMLs (Project Spec)
User document
New issue HOW-TO
Ask for help HOW-TO and WHERE
Tutorial for setup
Tutorial for different user scenarios
Tutorial for common troubleshooting
Learning material for DIY lover [HOW-TO build your own noise meter]
@vgotcheva Can you help to check with Gabe if the proposed document structure align with the benefit of all related stakeholders (developers, contributors, users, learners, maybe beneficial owners, and other related personals)?
We need to write a document that introduces Project Noise Meter to everyone interested in learning about it or contributing to it.
The text was updated successfully, but these errors were encountered: