Intended Audience and Reading Suggestions
This document was written so that developers, project managers, marketing staff, testers, documentation writers and our community is able to understand. The rest of this document from onwards is written by following a procedure to outline key areas of the project, so that it can be understood as clearly as possible by everyone reading it.
Reading this document might be boring, but it's the best way to eliminate confusion, redundant questions and it will help all of us to be on the same page with the future and vision of the project.
It is suggested that you read this whitepaper in sequential order at least once, because that's the order it was written in. That way you'll get the best possible understanding of the whole project concept. After that you can jump around and re-read any section as you wish.
Last updated