This is the part of the wiki where people willing to contribute to Sympa can find the informations they need to start working on Sympa.
Anybody subscribed to the sympa-dev mailing list can edit the pages in this space.Not subscribed yet? Click here!.
If you have a neat feature in mind that would improve Sympa and that you would be willing to develop, here is the place to go!
Here, your projects will be warm and comfortable until they are ready to fly. We will grant them their own wiki page and a branch where to learn flying on our subversion tree.
If you have a good idea but no clue on how to implement it, please fill in a feature request in the Sympa tracker. we'll handle it as soon as possible.
Here is a suggested way to contribute to start contributing to Sympa.
This is just a suggestion. If you already have done all the planning / architecture of your Sympa feature, you can go directly to the last point and request a development branch.
><a href="mailto:firstname.lastname@example.org?subject=sub%20sympa-dev">Click here to subscribe to sympa-dev</a>.</HTML> By discussing with other people, you can narrow what the right way to implement your feature is;
We will create a development branch for you on our subversion repository. this is probably the quickest way to see your feature added to the main Sympa distribution.
=== Birds in the nest ====
Here is a list of the current projects in the incubator.
You want to add your own project? just edit this page, copy the last line of the list above and modify it to set your project name. Save the page and then click the link you created. All done!
We filed a set of recommendations on how to properly modify the Sympa code. It is important to be as fair as possible to these recommendations to keep the code maintainable.
Here are the basis on which we open the subversion repositories :
When creating a new version, the NEWS file is performed automatically using svn changes informations.This is possible if the following rules are applied when editing svn ci comments.
[tag][#ticket_number][Information about the person who submit a feature request or report a bug] Description text.
Where [tag] is:
Insert a “” in order to specify a non reversible change
Example : [change] Inset a ”-” in order to specify a minor change that should not be listing in the NEWS file
Example : [-bug] === Example === <code> [*change][#3917][Reported by S. Kounachenriko, no-spammers-honest.ru] It is now possible to send viagra ads with Sympa. </code> would appear in NEWS as: <code> Changes: * src/sympa.pl: [#3917][Reported by S. Kounachenriko, no-spammers-honest.ru] It is now possible to send viagra ads with Sympa. </code> === Application === Changes are controled by a script on the svn server1)