From Martin's notes:
Re-make Download site as a simple web page and update it with new theme.
Switch download.moodle.org from CVS to git
We discussed your thoughts for the download site some time ago, but i've completely forgotten it.
I think you want the CI server to automate a lot of the building etc, but perhaps in the meantime I could create the front page for the download site with the appropriate hooks for automation to come later?
Note that MDLSITE-2045 has been created about the improved (git-based) packaging process happening @ download.moodle.org. Note it's 100% done by download.moodle.org but it should be easier to move the "trigger" to Jenkins once everything is working ok (MDLSITE-2047 for more details).
This is only about packaging, not about releasing (aka, branching, editing version.php...). For that mdlrelease continues being our guide.
Assigning this to Barbara to come up with a better design in HTML/CSS for this page.
It should be a simple matter then to wire that to the scripts for the data.
Increasing priority as this issue needs to be completed at the same time as moodle.org. The downloads site will no longer appear to be part of moodle.org; instead it will be a site with top menu items:
Packages | Plugins | Language packs
We will also need to figure out how to separate plugins navigation from moodle.org navigation.