Roadmap

Todo:

• Add a tag for v1.5 to current next-dev head
• Merge next-dev into next
• Merge the summer code sprint contributions into next-dev

CMS

1. Integrate tinymvc or other php framework(adds some code but speeds up development)
2. Add a plugin to show student/class progress in graphs
3. New template
4. Add support for step by step, presentation style, articles( there are a couple of js solutions for this)

Wild ideas:

Rest api frontend which serves json

Container engine

1. Extend the daemon to control both vagrant and docker challenges.

2. Make the communication via a rest interface (we already serve json) (we could use a microframework like flask for this.)

3. Security -- so far most of the config is default

4. Extend ContainerEngine support for scripting languages like Python, NodeJS, Ruby on rails. See issue #181

5. Extend the ContainerEngine to support Linux platforms like Fedora, CentOS, and ArchLinux. See issue #180.

6. Adding logging support for container daemon runtime error. As of now, the daemon is working properly but if for any chance it fails to work or it crashes, there is no way we can debug this. See issue #179

Ideas

Challenge repository --> github repository to host challenges and cms functionality to download/install challenges

Challenges:

• Zap command line/api challenge which uses a script like puppet's quest to guide the user through it.
• Host the other owasp vulnerable apps
• Fix vulnerable source code so that it passes the unit tests