-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MajiFix Roadmap 2018 #2
MajiFix Roadmap 2018 #2
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@joshuamabina Thanks for the PR, can review my comments and advice. In case of anything which is not clear yet don't hesitate to ask.
roadmaps/2018.md
Outdated
@@ -1,7 +1,19 @@ | |||
# Majifix Roadmap 2018 | |||
|
|||
This page outlines work that is currently being worked on and things we plan to work on next, within this year of 2018. That said, we do value feedback from the community to help us better understand user needs and adjust priorities. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is nicely done. It clearly explain the concept of the roadmap
roadmaps/2018.md
Outdated
## Majifix API | ||
|
||
Majifix API is built on Node.JS. It is a RESTful API layer designed in support of reporting and tracking common public-service (i.e. water) problems. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For this section, It is also nicely done but we should move it up to the introduction part where we explain about majifix components. We can expand components descriptions to be paragraphs in-stead of being just a single or two lines.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@lykmapipo If you have time please create a skeleton for the roadmap for the API so that the structure can be easily replicated to other majifix products
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@BenMaruchu I appreciate the feedback.
- I think moving it to the introduction part is wise.
- I think the road-map will make much more sense, to show what is to be shipped, even if itemized (no paragraphs). @lykmapipo Maybe the skeleton should consider this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@joshuamabina & @BenMaruchu Sure. Roadmap template will make sense. Please @joshuamabina initiate and I will guide.
@BenMaruchu & @lykmapipo please share backlog and/or milestones so that we can update pending items as on the template. |
@joshuamabina Add Local Deployment section on roadmap |
@joshuamabina & @BenMaruchu Local Deployment will require us to document all steps and system specifications to be able to deploy majifix locally. Automation scripts will be also required |
The start of majifix roadmap. Please review and advise.