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
How We Keep In TouchThe team keeps in touch on a day-to-day basis via the development list and Skype. We generally try to keep significant discussions on the list, but prefer Skype for higher-bandwidth discussions. We also have bi-weekly, virtual Committer Meetings where we share what we're working on as it relates to the FCRepo project. This also gives us a way to share what we're working on with interested members 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 their time allows. What To Work OnWhile 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 IssueOnce 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 BranchIf you're a new committer, or you're working on a substantial body of code, you should create a branch to work on it. Here's a guide to branching in subversion if you're not already familiar. Branches should be created as fedora/branches/fcrepo-123, where "fcrepo-123 is the JIRA id of the issue you're working on. Sometimes it's convenient to work on multiple issues in a single development branch. In these cases, you should make sure you've claimed each issue, and create a "Code Task" in JIRA that links to each issue via "addresses" relationship. This helps us keep track of who is working on what, and where. |