Roadmap for Feb 2014
- Change product name from "RazorFlow Framework" to simply "RazorFlow". The product was originally called "RazorFlow Framework" in case we would introduce a new side-product, and
- Move the core framework code to "razorflow/razorflow"
- Move docs to "razorflow/docs"
- Move razordoc to a separate repo and write introductory notes for it.
People who wish to be closely involved with the development, provide feedback on the development will be made available in Google Groups. All plans will be sent to this contributor mailing list before
A usage survey will be made to understand the usage of RazorFlow. The results of the survey (with anonymized data) will be made available publicly.
We will consider the best route to modifying the project to suit the community requirement.
There will be a chat room established for users to discuss RazorFlow and ask questions. The developers of RazorFlow will make an effort to spend some time on weekends on that channel and answer questions.
The website doesn't reflect that it's open source sufficiently well enough.
If users wish to contribute documentation it should be easy by writing a pull request.