Added by Jonathan Nolen, last edited by KC Baltz on Apr 29, 2008  (view change) show comment

Labels

 

How to begin

Fisheye 1.5 and Crucible 1.5 are due to be released very shortly, and include the atlassian-plugin library.

  • If you have a commercial license, you are free to use it for development purposes. If you don't, you may request a developer license(s) for the purposes of the contest.
  • If you have a commercial license, you may also download the source code of each product, also from http://my.atlassian.com
  • Be sure to look at the Development Hub Docs for docs and tutorials about creating plugins. You are also encouraged to look at the plugins in subversion and the Plugin Libraries for other examples.

What to write

Check out the Plugin Wishlist for some plugin ideas that our customers have been asking for. You can also look at the already submitted plugins, if you're interested in extending one of those. Or use your imagination and start from scratch.

What to submit

  • Working plugin, as a jar ready to install into a standalone JIRA, Confluence, Bamboo or Crowd for testing, or an application that integrates with our products, ready to run.
  • Complete source code, including build files and dependencies.
  • Unit and functional tests as appropriate.
  • A plugin page on the wiki, including a brief description, installation instructions and usage documentation. Make sure that you fully document the installation and usage of your plugin. Use your page to highlight the features of your plugin. Screenshots and examples are encouraged.
  • Any feedback on how we can improve the process of building plugins.

How to submit it

  1. When you are ready to submit your plugin, create a new child page on the Entries page. You may create your page at any time after the contest begins, and continue to make changes to your submission until the contest deadline.
  2. Using this Plugin template, fill out all the information about the plugin.
  3. Be sure that your plugin source is licensed under the BSD License. Usually, including a LICENSE.TXT file with your submission is sufficient.
  4. Attach your plugin (jar and source code) to the page.
  5. Link directly to any dependencies.
  6. If your entry is a Confluence plugin, submit it to the Confluence Plugin Repository.

At 11:00am, May 9th (UTC/GMT -10) we will change the permissions on all plugin submission page so that nothing else can be added or edited. Be sure that all of your work is complete and all of your files are added before that time. That is the final deadline - there will be no exceptions.