How to contribute a Plug-in to uDig?

Once completed, many community plug-ins will make their included in the uDig application.

Inclusion is based on:

1. Interest!
2. Quality Assurance testing
   • requirements
   • guidelines
   • run Find Bugs on your plugin. (An eclipse plugin is available and can be ran by right clicking on your plugin and selecting Find Bugs)
3. Documentation
   • Online Help
   • Internationalization
4. [Source License]
   Unable to render {include} Couldn't find a page to include called: Header
5. Code Review

How does this Work

Well you send email, or bring it up in an IRC meeting, and arrange a time to go over your code with some community members. At the end of the day your code will be sorted into one of the core modules (or a new core module created), the packages will be an extension of net.refractions.udig, the wiki page an headers updated, etc...

Please pay attention to the requirements and guidelines - if something like "sensible defaults" is not paid attention to it will be a very short review.

Community Modules and SDK Stability

Contributions directly to the uDig application are welcome, but it is often fun to try out an idea in a community module first. You will notice many of the core uDig developers playing on the community pages, this is how we keep the SDK stable.

If you have requested a feature, chances are one of the core developers will ask you to download a prototype from a community page. After all if it does not meet your needs there is no reason to add it to the SDK until it is ready.