Getting Involved as a Contributor
There are three different levels of involvement for developers interested in contributing to FDO. These levels of involvement are as follows:
- Project Contributor - A Project Contributor is a developer who contributes patches, code, and/or documentation indirectly through the project tracker or via existing project developers. Project Contributors do not have Subversion check-in access. Integration of a developer's contributions is at the discretion of the FDO Project Steering Comittee (PSC) and individuals holding the Project Developer role. This is typically an iterative, communicative process.
- Project Developer - A Project Developer has full commit access to the trunk of the source tree and has a signed Contributor License Agreement on file with OSGeo. Project Developers can directly make changes to the source of the development branch, from which the nightly builds are made. Project Developers review and accept code submitted by Project Contributors. Project Developers are elected by the PSC.
- Project Steering Committee (PSC) Member – The FDO PSC is the entity that manages the project. A PSC Member is a Project Developer or end user in the community that was elected to the FDO PSC due to their merit and active participation in the project. PSC Members have the responsibility to vote for project-related decisions and the responsibility to nominate individuals for Project Developer status. Note that most PSC members are also Project Developers, but they do not have to be.
All developers on the project start out as Project Contributors. A developer who has sent in solid, useful patches can be elevated to the Project Developer role by the Project Steering Committee (PSC).
Join the Mailing List
Join the mailing list to participate in development activities. The fdo-internals list is the primary channel of communication for developers working on the project.
- Subscribe to FDO-Internals
- View FDO-Internals Archives
- View / Search FDO-Internals Forum Interface (by Nabble)
The following resources are available to help developers get started working on FDO Open Source:
- Project Steering Committee
- Individual Contributor Agreement
- Corporate Contributor Agreement
- Coding Guidelines : NOTE: The FDO project shares its coding guidelines with the OSGeo MapGuide Project.
- Project Artifacts
- Artifact Lifecycle
- Submitting Defects
- Contributing Patches
- Subversion Client Configuration
Areas of Need
If you are looking to get involved the following aspects of FDO Open Source could use your help:
- Bug Fixes - FDO Open Source is a 3.2.3 release and as such, probably contains a bug or two that needs to be fixed.
- Platform Expansion - FDO Open Source is currently only being built and tested on Red Hat Enterprise 4 and Fedora Core 6. Updates to the code and make files to support as many Linux distributions as possible is greatly encouraged.
- Localization into new Languages - FDO Open Source is globalized and has been localized in English. Support for additional locales is very desirable.