HowToContribute

How to Contribute to CSS

If you want to ...

... contribute to the documentation

Get a SourceForge account to get access to this wiki and contribute content.

... report problems

You should open a ticket and select the appropriate component. If the component is not there, use the mailing list.

... contribute a patch

The first thing you do is contact the plug-in maintainer (don't commit to a plug-in you do not maintain, please).

The maintainer is found in the Bundle-Vendor property of the manifest file of each plug-in (also visible in Eclipse in Overview/General Information/Provider), and if you are unsure you can always write to the list. The maintainer will then decide whether you need to:

• Send him a patch file
• Open a Ticket with an attached patch
• Commit in a separate branch
• Commit on trunk
• ... The maintainer will make that determination based on different factors (such as the size of the patch, the current state of development of the plug-in, the past history of contribution of the submitter, ...) and therefore it is not possible to give a single process for all cases. The single rule that always apply is contact the maintainer.

... contribute a new plug-in

You can add your plug-in in the application/plugin folder, if the plug-in is of general usefulness, or in the products/yoursite/plugin folder, if you either don't provide support or it has feature currently specific to your site.

Use the Bundle-Vendor property of the manifest file of each plug-in (also visible in Eclipse in Overview/General Information/Provider) to record the author/mainter in the following form:

Name Surname <email>[[Name Surname <email>|,]] - Site

For example: Gabriele Carcassi <[email protected]>, Kunal Shroff <[email protected]> - Brookhaven National Lab