FusionForge

Difference between revisions of "Roadmap"

From FusionForge Wiki
Jump to: navigation, search
m
(4.9 or 5.0 or whatever: GFAS migration script committed)
Line 21: Line 21:
 
* Provide install CD build (cbayle)
 
* Provide install CD build (cbayle)
 
* Developed by lolando for clients, will be merged after the jobs are finished:
 
* Developed by lolando for clients, will be merged after the jobs are finished:
** GForge AS → FusionForge migration script (not complete yet)
+
** GForge AS → FusionForge migration script (committed to trunk)
 
** ability to use email address (in addition to login name) for logging in if sys_require_unique_email is true;
 
** 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) enforce the acceptance of terms of use on account creation;

Revision as of 09:07, 15 April 2009

Roadmap and work in progress

4.8

  • New version of the phpwiki plugin
  • New tag cloud feature
  • Full listing of projects
  • More translations if they happen
  • Partial test suite

Tentative timeline for 4.8:

  • Branch created 2009-04-03
  • 4.8rc1 mid-April
  • 4.8 final sometime in May

4.9 or 5.0 or whatever

  • Finish merging in the Novaforge changes (gcuellar)
  • Factoring some code in the scm* plugins (lolando)
  • New scmbzr plugin (lolando)
  • New scmgit plugin (aljeux)
  • Finish URL relocation (lolando)
  • Provide install CD build (cbayle)
  • Developed by lolando for clients, will be merged after the jobs are finished:
    • GForge AS → FusionForge migration script (committed to trunk)
    • 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

Long-term

  • Safe SQL (no string concatenation of SQL and args) (started by lolando)
  • 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