Design & Development Process » History » Version 2
Design & Development Process¶
The design process for Orvos is based on agile development principles. We maintain a list of all known bugs in the Issues database. The development work is currently organized into 2 week sprints, but contributions are welcome at anytime.
The plan for what we build is described in the Backlog of user stories. Anyone is open to contribute user stories by creating a New Issue and making it a story. Please try to write well crafted stories.
Right now, the engineers at Clinical Future are deciding which Backlog items go into each sprint. As the community expands, we expect that we'll lengthen sprints, and expand use the IRC and email lists to get a lazy consensus on the backlog for each sprint. Of course, you don't have to work off of the Backlog. If some other aspect of the project interests or you want to write other code, go for it. The Backlog is just a suggestion.
We are starting to organize the work driving towards releases. Look a the Roadmap and Release Plan to see what we're currently thinking. Overtime we expect to shift to a regular release schedule and use a process of online design summits to decide on release themes.