Revision as of 16:33, 25 August 2009

Roadmap and work in progress

4.9 or 5.0 or whatever

Already committed to trunk

• Unmodified packages can now work with a URL prefix
• GForge AS → FusionForge migration script
• New plugins initially developed for Adullact: extratabs, projectlabels
• Another new plugin that was only maintained for Adullact in recent times: globalsearch
• New features developed by lolando for AdaCore:
  • ability to use email address (in addition to login name) for logging in if sys_require_unique_email is true;
  • (optional) enforce the acceptance of terms of use on account creation;
  • (optional) block anonymous downloads from the FRS;
  • command-line scripts to inject users, groups and file releases into the database from text files.

For fusionforge build:

• Continuous integration applied to fusionforge package build (cbayle)
• Test suite

Not committed yet

(In various states of development: from "not finished" to "not even started")

• Safe SQL, with db_query_params rather than string concatenation of SQL and args (started by lolando) (needed for operation with magic_quotes_gpc=off)
• Finish merging in the Novaforge changes (gcuellar)
• Refactoring the scm* plugins, and implementing new ones for Bazaar, Git, Mercurial and Darcs (lolando)
• Update the Mediawiki plugin to have separate wikis per project (lolando)
• Provide install CD build (cbayle)
• New plugin initially developed for Adullact: contribtracker

Long-term

• Advanced URL relocation (with a dispatcher)
• Revamp authentication/identification (SimpleSAMLphp) (cbayle)
• Use MIT Simile Web Widgets[1] (cbayle)
• Rethink authorization code (XACML, ACL, ...) (cbayle)
• Cleanly separate SQL and HTML
• Use a framework?
• Simplified configuration management (one .ini file, or store config in database) (lolando)
• Factorization of code: monitoring, upload.
• GPG integration
• Blog plugin (LifeType b2evolution WordPressMu) ?

Back to FusionForge