Focus on new design for the router system, and take decision
decide if this replace the previous system,
or if this is provided as another solution (we would then have 2 routers system).
It might be possible to implement the previous uri and uri-template router with the new design, and mark them obsolete, this would avoid breaking existing code, but if no-one ask for it, no need to spend time doing it.
Current activities
Technology forecasting about REST, Hypermedia API, Collection/JSON, HAL, ...
Building a CMS framework inspired by Drupal, and using EWF
Libraries in-progress or draft: OAuth (consumer), Google API, Github API, Template engine, Wikitext parser, CMS (including sub libraries which will be part of EWF, such as session handling, mailer, ...)
Documentation
Remaining issues
Review design in relation to concurrency, and provide example demonstrating concurrency with EWF
Review design to allow easier extension/customization of EWF, such as using its own MIME handlers.
Demo for a CMS built with EWF (inspired by Drupal)