...
| Info |
|---|
If you are new to the project, another great resource to reference is our New Developer Document.a great place to start is Getting Started |
Methodology
In order to accelerate project delivery, OpenLMIS version 3 uses a scaled agile approach. Read more about our Methodology and Process.
...
- Processor which supports virtualization: i.e. it must be able to run Docker
- 16 GB RAM (at least 8GB allocated to Docker)
- GitHub Account
- Good 3G internet
- Clay Crosby (Unlicensed) or Craig Appl (Unlicensed) Can you please update these system requirements with any additional requirements for the reporting stack
Tech Stack
For OpenLMIS version 3, the primary technologies used are:
...
The dev community supports several communication channels. Each mode serves a different purpose:
- The developer Google GroupOpenLMIS Discourse
- Discussions, questions and decisions on application design and behavior. As messages are kept forever, this is the place to record the how and why for future reference
- Discussions and decisions by the Tech Committee (as well as the other OpenLMIS Committees)
- Technical support questions
- Announcements, news, etc.
- Slack
- For messages that are transient/short-lived. Good for real-time discussion and project messaging. No guarantee messages are persisted forever.
- #dev is reserved for tool notifications. Humans shouldn't generally post here as it will get lost among automated notifications
- #general for most OpenLMIS messages
- #toolbox for tools and techniques relevant to the OpenLMIS' tech stack
- #random for non-project FYIs, relevant articles and links, etc.
- JIRA
- Issue tracking, project management, Epics, Stories, etc.
- Discussion on specific bugs, stories, etc. should use the Comment facility on the JIRA issues, NOT private emails.
- Email
- If an email thread veers to generating discussions/decisions that should be public per a healthy open source project, move it to a community forum.
...