[Fusioninventory-devel] Organize display of projects in the forge

Fabrice Flore-Thebault themroc at centsix.org
Mon Sep 6 19:49:58 UTC 2010


I propose this reorganisation of the display of the projects in the forge :

+ FusionInventory Agent
  ++ agent-tools
  ++ fusioninventory-agent-task-backup
  ++ fusioninventory-agent-task-fai
  ++ fusioninventory-agent-task-ltsp
  ++ fusioninventory-agent-task-opsi
  ++ fusioninventory-agent-task-netdiscovery
  ++ fusioninventory-agent-task-ocsdeploy
  ++ fusioninventory-agent-task-snmpquery
+ FusionInventory for GLPI
  ++ plugin_fusinvdeploy
  ++ plugin_fusinvinventory
  ++ plugin_fusinvsnmp
+ Libfusioninventory-server-php
+ Fusioninventory Community
+ Documentation


Reasons : 

- Have a readable page on : http://forge.fusioninventory.org/projects

- There is no use getting too deep into tree construction : "FusionInventory 
Agent" and  "FusionInventory for GLPI" are the two main projects, they deserve 
a visible place in the root tree.

- The actual "Fusioninventory" project in the forge is about the community 
life of the project : events, presentations, announces, tshirts, public 
relations => let's make it clear, rename it as "Fusioninventory community".

- Remove empty project "FusionInventory Server" which has no utility

- Question : should we keep "Fusioninventory-ldap" which is still empty ? I 
would prefer we unpublish it and create it again when development is starting, 
so it becomes clear that the project has really started.


Cheers,

-- 
Fabrice Flore-Thébault



More information about the Fusioninventory-devel mailing list