Processes

1 Communication

1. The communication channel of record is dev@pekko.apahce.org which is archived at https://lists.apache.org/list.html?dev@pekko.apache.org
2. All discussion concerning changes must occur on the dev@pekko.apache.org mailing list.  If it is not on the mailing list it did not happen.
3. Apache Pekko follows the Apache voting rules:  https://www.apache.org/foundation/voting.html

2 Development

1. Defects are recorded in the git issue for the associated Pekko module.
2. All changes to release branches must be made via pull requests.
3. All pull requests for code changes (e.g. changes that modify the code execution)
   1. must be associated with an issue.
   2. must be reviewed and approved by at least two committers who are not the developer(s).  
   3. must be voted on in the development list using the code modifications process documented in the Apache voting process document
4. Trivial documentation changes (e.g. spelling errors, javadoc errors) are changes that do not affect code execution. 
   1. Trivial documentation changes may be approved by one committer who may also be the editor.
   2. Trivial documentation changes do not require discussion in the mailing list.
5. Substantive documentation changes (e.g. not trivial)
   1. must be associated with an issue
   2. must be reviewed and approved by at least two committers who are not the editor(s).
   3. must be voted on in the development list using the code modifications process documented in the Apache voting process document.

3 Process Changes

1. All processes are recorded in this wiki.
2. Processes may be changed by the process specified in the Apache voting process document section on  procedural issues.