BioQuery Policy for Contributors
This policy explains the different roles contributors can play in the BioQuery project, and defines our policy for granting access to the source code and project files.
There are four Roles played by the people involved in BioQuery:
Users
The end users of BioQuery are the most important category of people involved with the project, and their needs are the ultimate driving force behind all project activities. End users include both users of the full BioQuery application, and of libraries produced by the project. End users can always make suggestions, request features, and report bugs.
Contributors
Anyone can become a contributor by learning about the project and the application, and creating a piece of work that they submit to the project. Potential contributors should follow the introduction on the Get Involved page. Contributors work with source code checked out by anonymous CVS access. To check their work back in, they should send the modified files to a Developer, who will look it over and commit the changes. All contributors can add their names to the list of authors in the source file. Once a contributor has made useful contributions, they can request to become a developer.
Developers
Developers have direct (non-anonymous) CVS access via SSH and can check in code. They are listed as team members in the sourceforge site. They review other's code before checking it in, and vote on which contributors to promote to developers. Any committed and talented contributor can become a developer, but you'll have to send us some information about yourself (such as a resume) so we know who our developers are.
Administrators
Have administrator access on the sourceforge project site and the BioQuery website. They manage the task list and control developer access to the code. Most developers probably won't want to be administrators, but particularly committed individuals with 'deep' knowledge of the application may get sucked in to help with these central tasks.
BioQuery Home.
