Become Platinium or Gold Neogia Partner

• Welcome
• Fonctionalities
  • Party
  • Product (Catalog)
  • CRM - SFA
  • Sale/Purchase(Shipmnt./Recpt.)
  • Point of Sales Terminal
  • Stock
  • Manufacturing
  • Quality
  • Services
  • Finance/Accounting
  • eCommerce
  • Business Intelligence
• Documentation
  • videos
  • User Documentation
  • Contributor Doc.
  • Project Documentation
  • Developer Doc.
  • Administrator Doc.
• Download
• Demo
• Organization
• Site Map

Develop some new functionalities

Rules and process to development contribution

1. having a sourceforge user and be declared on the neogia project, to be able to see and declare all tasks which will be realized by the community (and you ;-), in FeatureRequest tracker.
2. declare a task (or a group of tasks) in sourceforge for each realization you want to do, (one task per 1-3 days realisations).
3. for larger task (up to 5 days), add a page in the wiki using the specification template, to detail realization analysis and plan (this rule appairs from May(2006)
4. for UML modification: having a poseidon community license (we will migrate to a Free sofware), it's not possible to manage concurrent modifications so
   1. all UML modifications should be done directly in head branch, so important modification must be previously discussed to be agreed by the component maintenor.
   2. all UML modifications must be done on the last cvs version, it is not possible to merge UML diagram, and we never merge generated code. It's always generated from the last generators version and last UML diagram version.
   3. after each UML modification (new entity, new attribute or new diagram, not new tag ;-) it's necessary to update the neogiawiki to put some documentations (this rule appairs from May(2006)
   4. after each UML modification, it's necessary to regenerate in head version in a dedicated commit
5. having a labs.libre-entreprise.org user, be declared on neogia project, put your public ssh key on your profil to be able to have a commit access on cvs
6. just before starting coding, upgrade your neogia version to the last cvs HEAD version to be sure to have last UML modification
7. when the task is finished:
   1. make a cvs synchronisation to manage possible conflict with the last commit
   2. make a selenium test, which test and valid your task, and which is very useful for the validator to see what you have done and where (this rule appairs in May(2006), very efficient)
   3. re-read and make correction if necessary in the wiki task-specification page
   4. write a functional documentation (maybe only 1-3 lines for a small task)
   5. generate a patch (it will include the selenium test)
   6. modify the task description to add [TBT] (To Be Tested)
   7. join the patch
   8. if you have discussed with a maintenor during the analysis step, you can ask him when he will try to validate your task in head
8. If you have delay constraint, you should order a Maintaineurs services to the Neogia organisation, with it the delay will be garanted. Usualy it cost 20% of development time.