You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Table of Contents

Welcome, New Committers!

We'd like formal permission to distribute your code contributions. To make this process easy, we'll accept an emailed copy of your signed CLA.  For further instructions, see the Fedora Commons Licenses Page.

Getting Started

As a committer, you should already have a fedora-commons.org login, and you will have been placed into the fcrepo-committer LDAP group.  This gives you the necessary permissions to work on parts of the project that are hosted at Fedora Commons.

  • You will also need a Sourceforge.net account.  This is necessary because the Fedora project's subversion repository is currently hosted there.
  • Send your Sourceforge.net id to cwilper (at) fedora-commons.org and he will give you subversion write permission.
  • Sign up to the Fedora Codewatch list using your username@sourceforge.net address.  This is a public list that all committers subscribe to.  It's used solely for email notification of subversion commits.  It is necessary to sign up using your sourceforge.net id; commit notification will not work otherwise.  Make sure you have set up your Sourceforge account so that emails to username@sourceforge.net are forwarded to your usual address.
  • Get familiar with compiling and testing Fedora.  Pay special attention to the section on setting up Eclipse.  Our coding conventions are embodied by the settings you will import into Eclipse.

How We Work

The team keeps in touch on a day-to-day basis via Skype and the development list.

We also have bi-weekly http://fedora-commons.org/confluence/x/YIBn where we share what we're working on as it relates to the FCRepo project.  This allows us to communicate in a high-bandwidth way and also gives us a way to share what we're working on with the rest of the community (the meeting minutes are public).  Generally, committers employed by Fedora Commons are present at these meetings, and committers from other organizations may attend as the time/need dictates.

What To Work On

While we collectively prefer the high-priority tracker items (as determined by the community and committers) to be worked on first, all contributions are appreciated.  Please only work on unclaimed items that exist in the FCREPO tracker in JIRA.  If you have verified a pre-existing bug in the Community Support tracker, please move it to the FCREPO tracker before starting the work.  If you have identified and verified a new issue, you may submit it directly to the FCREPO tracker.

Claiming an Issue

Once you've found an issue to work on, simply assign yourself as the owner in JIRA.  This lets everyone know that you plan to begin working on the issue soon.  If you find that you cannot complete an issue, please remove yourself as the owner to give other developers an opportunity to work on it.

Creating a Branch

If you're a new committer, or you're working on a substantial body of code, you should create a branch to work on it.
#trackbackRdf ($trackbackUtils.getContentIdentifier($page) $page.title $trackbackUtils.getPingUrl($page))
  • No labels