-
Notifications
You must be signed in to change notification settings - Fork 29
DRAFT: ePADD Committers
The ePADD software is open source and released under an Apache License, Version 2.0. The software and associated documentation is developed collectively by a community of contributors and committers. All interested community members are encouraged to contribute to the project. Contributors who demonstrate sustained engagement with the project through quality participation in meetings, mailing lists, documentation and code updates can be nominated by existing committers to also become a committer. It should be emphasized that committers need not be limited to software developers. Community members with skills in documentation and testing, for example, can also be committers.
Committers share the following rights:
- Write access to the codebase
- Nomination privileges of new committers
- Release management privileges
- Binding votes on procedural, code modification, and release issues
- Access to the private committers mailing list
Committers share the following responsibilities:
- Monitor and respond to project mailing lists
- Attend project and technical meetings
- Monitor and vet bug-tracker issues
- Review and commit code contributions
- Ensure code contributions are properly licensed
- Guide and mentor new committers
- Uphold the ePADD code of conduct
The following is an alphabetized list of the current ePADD committers:
| Name | Organization | |
|---|---|---|
| .. | .. | .. |
The ePADD project depends on the engagement and contributions of community stakeholders. As noted above, contributions can take the form of:
- Documentation review and curation
- Application testing
- Software development
Documentors contribute by reviewing, correcting, updating, and enhancing the project documentation found on this wiki targeting users of ePADD.
- Interest in technical writing
Testers contribute by performing and reporting on the outcomes of a wide range of tests, including performance, security, stress, regression, etc. on an on-going as well as release-time basis.
- Ability to deploy and configure ePADD
- Ability to document and communicate results
Developers contribute by writing functional and test code that fixes, hardens, and extends the ePADD codebase.
- Experience with software development practices
- Experience reading and tracing multi-module codebases
- Experience debugging issues