OSLC Project Guidelines DRAFT
Working Draft - collecting feedback from potential participants
The purpose of this document is to draft the project guidelines for the
OslcOpenSourceProjectProposal.
Roles and Responsibilities
The roles and responsibilities that people can assume in the project are based on merit. Everybody can help no matter what their role. Those who have been long term or valuable contributors to the project obtain the right to vote and commit directly to the source repository.
Users
Users
Users are the people who use the products of the Project. People in this role aren't contributing code, but they are using the products, reporting bugs, making feature requests, and such. This is by far the most important category of people as, without users, there is no reason for the Project.
When a user starts to contribute code or documentation patches, they become a Contributor.
Contributors
Contributors are the people who write code or documentation patches or contribute positively to the project in other ways. A volunteer's contribution is always recognized. In source code, all volunteers who contribute to a source file may add their name to the list of authors for that file.
Committers
Contributors who give frequent and valuable contributions to a subproject of the Project can have their status promoted to that of a "Committer" for that subproject. A Committer has write access to the source code repository and gains voting rights allowing them to affect the future of the subproject.
In order for a Contributor to become a Committer, another Committer can nominate that Contributor or the Contributor can ask for it.
Proposed initial committers:
- SteveSpeicher (IBM)
- DaveJohnson (IBM)
- OlivierBerger (Institut TELECOM)
- SofiaYeung (Oracle)
Admins
Project administrators and web site maintenance will be the responsibility of the Committers
Communication
All communication will done over mailing lists, discussion forums and bug comments.
Decision Making
Will be determined by the Committers.
Contribution Guidelines
Will be determined by the Committers
Contributors will submit ....
Committers will review and commit. Review guidelines are...
Coding Guidelines
No specific coding guidelines are needed at this time. They will be defined as needed.
Source Code Header Template
Following the process defined at
Apache License, Version 2.0 APPENDIX: How to apply the Apache License to your work
Dependencies
Any dependencies on new 3rd party libraries will need to be reviewed and approved by a Committer. Guidelines for 3rd party libraries are...
References