Contribute to Wikengo
Wikengo is a big project, that means lot of ways to contribute.E-commerce professional
The final product is made for you. So you can help Columbus team determinating the needs that the software have to respond to. The best way to do it is to read Columbus documentation on this wiki and participate to workshops. You can also contact Columbus team via the mailing-listUser/Tester
A user/tester can help different ways :As a tester, you can try the product thoroughly in order to find bugs. A complete procedure is developed here.
As a user, you can write documentation on this wiki, help other users via the mailing-list, or speak of the application with great enthusiasm (in fact, everybody can do that ;) )
Developer
Developer, your help will be well valued by Wikengo teams.Documentation :
To contribute, the easiest way is to first read all Wikengo development documentation on this wiki, then you can download the sources from the svn to see what it looks like.SVN repository :
http://svn.sharengo.org/svn/ (user anonymous, pwd : anon)If you want to do modifications on svn, ask developer team for an account.
Best practices :
In order to be well integrated in the team, you have to respect the best practices put in place. They can be found here.Contact the team :
You are also well advised to contact the developers team to understand more quickly the project.Architecture
If you are interested in software architecture, you can also help trinity team make the architecture choices. One advice is to read Trinity's documentation on this wiki and to subscribe to Trinity's mailing list
Version 4.1 last modified by Jean Couteau on 11/06/2009 at 14:57
Document data
No comments for this document
No attachments for this document