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 StartedAs 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.
How We Keep In TouchThe team keeps in touch on a day-to-day basis via Skype and the development list. We also have bi-weekly Committer Meetings 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 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. |