Norbert Hartl <norb...@hartl.name> writes: > Wow that sounds a lot of things are possible. Do you have a roadmap?
There are plenty of things we would like to do: - clean the issue tracker by doing all the simple things (it's time for users to write their ideas there) - facilitate the creation of new Pillar projects. Currently, it's a hell to start a new book or a new lecture. - simplify Pillar to avoid the current transformation to a build system. We want to remove the dependency to the Mustache template engine. We also want to remove Pillar's ability to compile LaTeX files to PDF. I want Pillar to do just 1 thing: convert a .pillar to a .tex/.html/.*. The rest will move to external projects, reusing as much as possible of what's already there (e.g., GNU/Make) and leveraging other tools (e.g., other template engines, even not implemented in Pharo). - refactor and recompose Pillar's source code to break all package cycles. Also make sure no new cycle is created in the future by adding a check in the test suite. - add a new XML-based exporter to publish the Mooc on a dedicated platform - take care of all the user's feedback during the internship -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
