From FusionForge Wiki
Revision as of 11:52, 4 April 2014 by Beuc-inria (talk | contribs) (* Topics */ release process)

Jump to: navigation, search



  • Meet each others :)
  • Talk about everybody's work on forges
  • Plan the roadmap/features for the next FusionForge version, and prepare an announcement, grouping planned improvements by visibility and use Fusionforge tracker to display it (roadmap) :
    • End-user
    • Site-admins
    • Developers


  • Improve Ergonomy & accessibility
    • Involves a templating system (Symfony's Twig?), a microframework (Symfony's Silex? )
    • Should we try to share a Common plugin system, or support others? mediawiki ?, drupal ?, ...?
    • Use standard Fusionforge templating system, HTML and utils helpers to clean the code.
  • Concurrent_WebDAV_and_SSH
    • leads: Gitolite-style single user? Apache-Fuse IPC? SabreDav?
  • Responsiveness (create projects & SSH keys immediately)
    • leads: dedicated daemon? Reuse tools like RabbitMQ or Redis, or Fedmsg [1] [2] or re-code?
    • Or a job queue and a frequent cron job (every minute? five minutes?) that only runs what's needed
    • Or use the standard job-server.pl ship by Fusionforge.
  • Common installation system & merge/minimize Debian packaging branch
  • Private Git repositories browsing [3]
  • NFS limitations (16 groups/user) - what to recommend? (kernel patch, webdav, iSCSI)
  • GID potential conflicts (user gids start at 20000, is at 39000 at Inria, projects starts at 50000)
  • taking care of the open Features Requests, Patches and Bugs.
  • Use/make ldap or Idp provider plugin (openid, cas, fusiondirectory, lemonldap, simplesamlphp )?
  • Planetforge, Forge Ecosystem
  • Release process
    • Use tracker vote system to adapt our roadmap.
    • Make the release cycle *way* shorter, to help void forks (e.g. EvolvisForge stuck on 5.1)
    • 5.4 or 6.0 ?