Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "WTP Permeability and Transparency Checklist"
(→Definitions) |
(→Mechanisms) |
||
| Line 7: | Line 7: | ||
A project is said to be '''transparent''' if the project team makes it easy for a member of the community, who is not part of the core team, to participate in all decisions that affect the project. The project should make it easy for a non-team member to find all the information used and the decisions made by the project team. | A project is said to be '''transparent''' if the project team makes it easy for a member of the community, who is not part of the core team, to participate in all decisions that affect the project. The project should make it easy for a non-team member to find all the information used and the decisions made by the project team. | ||
| − | ==Mechanisms== | + | ==Communication Mechanisms== |
| − | The following is a list of | + | The following is a list of mechanisms for communication about a project |
#Source Code Repository | #Source Code Repository | ||
| − | # | + | #Newsgroup |
| + | #Mailing List | ||
| + | #Wiki | ||
| + | #Bugzilla | ||
| + | #Conference Call | ||
| + | |||
| + | For each such mechanism, the WTP PMC will define the characteristics to be used to measure the ease of participation by a community member. | ||
| + | |||
| + | ==Ratings== | ||
Revision as of 02:06, 4 September 2007
Overview
The WTP PMC has recognized the need for all projects under its domain to actively promote the participation of the community. Such a participation is only possible if each project takes a proactive role in lowering the barriers to contribution from the community. Given the subjective nature of such a task, the WTP PMC has listed a set of concrete attributes that would serve as a measure of the ease with which a member of the WTP community is able to participate in the project. These attributes are derived from the principles of Open Source Rules of Engagement as detailed in the Eclipse Development process
Definitions
A project is said to be permeable if the project team is receptive to new ideas from the community and welcomes new committers to its team. This is a measure of the 'responsiveness', 'friendliness' or 'sociability' of the project towards a participant who is not part of the project team.
A project is said to be transparent if the project team makes it easy for a member of the community, who is not part of the core team, to participate in all decisions that affect the project. The project should make it easy for a non-team member to find all the information used and the decisions made by the project team.
Communication Mechanisms
The following is a list of mechanisms for communication about a project
- Source Code Repository
- Newsgroup
- Mailing List
- Wiki
- Bugzilla
- Conference Call
For each such mechanism, the WTP PMC will define the characteristics to be used to measure the ease of participation by a community member.