First iteration of roadmap document and call for contributions. #1 #6

status.md

@@ -3,8 +3,78 @@ layout: page
 title: Status
 ---
 
-Follow the progress of the Content as Code partnership:
+## Current
+
+> [Contribute your ideas and discuss the approach of Content as Code #1](https://github.com/iilab/contentascode/issues/1)
+
+> [Contribute your ideas and follow the discussion about the choice of authoring environment #5](https://github.com/iilab/contentascode/issues/5)
+
+> [Help develop the proof of concept #7](https://github.com/iilab/contentascode/issues/7)
+
+## Roadmap
+
+* TOC
+{:toc}
+
+### Proof of Concept - v0.0.1
+
+In the run up to the IFF the proposed tasks to help get the partnership off the ground are:
+
+#### Design
+
+- [Iterate on the ecosystem design document #1](https://github.com/iilab/contentascode/issues/1)
+- [Document translation workflow #2](https://github.com/iilab/contentascode/issues/2)
+- [Implement translation workflow scripts #3](https://github.com/iilab/contentascode/issues/3)
+- [Document possible legacy technology constraints and requirements #4](https://github.com/iilab/contentascode/issues/4)
+- [Choose editor(s) as a basis for the authoring environment #5](https://github.com/iilab/contentascode/issues/5)
+- [Discuss Roadmap #6](https://github.com/iilab/contentascode/issues/6)
+
+
+#### Implementation
+
+- [Implement Proof of Concept #7](https://github.com/iilab/contentascode/issues/7)
+
+> Milestone [Lift off](https://github.com/iilab/contentascode/milestones/Lift%20off)
+> Version [v0.0.1](https://github.com/iilab/contentascode/issues/7) - https://github.com/iilab/contentascode/issues/7
+
+ -  Authoring
+     + [ ] Github
+     + [ ] Jekyll
+     + [ ] Prose
+ - Translation
+     + [ ] Transifex
+
+ - Collaboration
+     + [ ] Github - Fork and pull request
+
+ - Management
+     + [ ] Waffle 
+ - CMS Parity
+     + [ ] Comments - Github issues?
+     + [ ] Stats - Piwik
+
+ - Deployment
+     + [ ] Single repo and one click deploy 
+
+### Prototype - v0.1.0
+
+Prototype should allow to do demos and showcase how key functionalities will work and improve existing content workflows.
+
+> Milestone [Prototype](https://github.com/iilab/contentascode/milestones/Prototype) - https://github.com/iilab/contentascode/milestones/Prototype
+> Version [v0.1.0](https://github.com/iilab/contentascode/issues/9) - https://github.com/iilab/contentascode/issues/9
+
+### Minimum Viable Implementation - v1.0.0
+
+Minimum viable implementation which would allow partners to adopt the workflow and technology in production.
+
+> Milestone [Minimum Viable Implementation](https://github.com/iilab/contentascode/milestones/Minimum%20Viable%20Implementation%20) - https://github.com/iilab/contentascode/milestones/Minimum%20Viable%20Implementation%20
+> Version [v1.0.0](https://github.com/iilab/contentascode/issues/8) - https://github.com/iilab/contentascode/issues/8
+
+## Follow
+
+Follow the progress of the Content as Code partnership and contribute:
+
+ - By [commenting and creating github issues](https://github.com/iilab/contentascode/issues) 
+ - By [watching the github repository](https://github.com/iilab/contentascode/subscription)
+ - By joining us at the [Internet Freedom Festival](https://internetfreedomfestival.org/) content re-use session.
 
- - By [commenting and creating github issues](https://github.com/iilab/contentascode-site/issues) 
- - By [watching the github repository](https://github.com/iilab/contentascode-site/subscription)
- - By joining us at the [Internet Freedom Festival](https://internetfreedomfestival.org/) content re-use session.