| Info | ||||
|---|---|---|---|---|
| If you'd like to help with testing or documentation, please see:
| |||
Fedora 3.3 Test PlanFedorahas been released! Find out more in the 3.3 Documentation Plan |
Community contributor's page
Welcome to the community contributercontributor's page. The intent of this page is to provide an entry point that makes it easier for community contributors to participate in the development process of the Fedora 3.3 release.
We are excited about the current scope of the release and to make it even bigger better we'd like you to get involved.
Any contribution is most appreciated.
If you feel like helping out with a particular issue listed out below don't hesitate to get in contact. If you would like to contribute something that's not on the list, but you want to see addressed, you are also very welcome to contribute.Note: Code Freeze for Fedora 3.3 started on December 7th, 2009. The release is now planned for December 18th.
What
...
has been done so far?
A wiki page with all the resolved issues and release notes has been set up here.
One of the biggest chunks of work currently unassigned is the completion of the REST API. The REST API should be equal to the Soap API in terms of functionality and therefore has the hightest priority among all open issues.
In order to achieve functional equality the missing methods must be implemented and open bugs fixed. The issue consists of the following unassigned subtasks:
Complete API-A-Lite in REST API
- FCREPO-555 describeRepository
- FCREPO-556 getDissemination
Complete API-M-Lite in REST API
- FCREPO-557 upload
Complete API-M-SOAP in REST API)
- FCREPO-558 compareDatastreamChecksum
- FCREPO-559 addRelationship
- FCREPO-560 getRelationships
- FCREPO-561 purgeRelationship
FCREPO-522 (DSIDs can now no longer terminate in .xml and behave properly)
FCREPO-532 (Get rid of ".xml" shortcut on REST API)
FCREPO-523 (POST to /objects/pid/datastreams/dsid is counter-intuitive)
For a more detailed list with other all issues scoped for 3.3 see the version summary page on the bug tracker. A wiki page with all the resolved issues and release notes has been set up here .
How can you help ?
How can you help ?
As of December 7th, we are in code freeze. This means that until release, no further features will be added. During this time, we are verifying correct functionality of all the new features, verifying no new bugs were introduced, and completing the documentation.
Right now, there are two main ways you can help:
If you see an item on either of the plans that doesn't currently have a name next to it, and you'd like to help, please let us know. Either post to the developers If you'd like to contribute just pick something out you might want to get involved with and submit a patch. You can also pick an issue that's already been assigned - in that case just contact the asignee. If you haven't done any development with Fedora, the page "Building Fedora from Source" should help you get started.
Then either post to the mailing list or contact one of the committers. If you haven't signed up to the mailing lists yet you may want to read the Committer's Guide page for instructions on how to subscribe.You can also sign up for a tracker account and directly attach your contribution to the respective tracker item.If you feel like having a direct discussion over phone or just want to lurk you are always welcome to attend the weekly committer meetings.
In any case you can also contact the current release manager for Fedora 3.3, Kai Strnad, at: kai <dot> strnad <at> fiz-karlsruhe.de
...