Can I suggest these amendments to https://cwiki.apache.org/confluence/display/PEKKO/Processes ? I'm happy for any of these proposed changes to be adjusted or discussed further.
Change 1. Defects are recorded in the git issue for the associated Pekko module. to 1. Defects are recorded in the Github issue tracker for the associated Pekko module. New point 3 (pushing down existing point 3 to 4, etc.) 3. For major/breaking changes, we require that a Pekko Improvement Process (PIP) proposal is submitted on the dev mailing list before a PR is made. After allowing some time for discussion, a vote will be required on the dev mailing list using the code modifications process documented in the Apache voting process document. When we have general agreement on the proposal, we can proceed to submitting PRs. Examples of such issues include: a. new Pekko features/libraries b. changes to public APIs c. significant upgrades to jar dependencies d. changes to wire protocol e. large changes across many Pekko components Change 3c (which becomes 4c because of new point 3 above) c. if a Pekko committer requests that the PR changes should be discussed more widely, the changes should be discussed on the dev mailing list and voted on using the code modifications process documented in the Apache voting process document. Change 5c (which becomes 6c because of new point 3 above) c. if a Pekko committer requests that the PR changes should be discussed more widely, the changes should be discussed on the dev mailing list and voted on using the code modifications process documented in the Apache voting process document. On Thu, 27 Oct 2022 at 09:55, Claude Warren, Jr <[email protected]> wrote: > > One of the first things this team needs to do is to decide how development > will be done. I have drafted a process document to kick this discussion > off. > > The draft document is found at > https://cwiki.apache.org/confluence/display/PEKKO/Processes > > For purposes of this discussion: > > 1. No changes will be made until a code modification vote is taken. See > https://www.apache.org/foundation/voting.html for requirements. For > those of you who have edit access to the document please do not change it > until we have a vote. > 2. Committers and Mentors have binding votes. All other votes are > advisory. > 3. Discussions of proposed changes must be posted to the > [email protected] mailing list and the subject should be prefixed > with "[DISCUSS]". > 4. Calls for votes on the proposed changes must be made on the > [email protected] mailing list and the subject should be prefixed > with "[VOTE]" to make it easy to identify. > 5. Results of votes will be published on the dev mailing list with > "[RESULT]" prefixing the subject. > 6. A vote to accept the document may be taken once all proposed changes > are voted on. > 7. A vote to accept the document will close all discussion under the > process documented in this email > 8. Once the document is accepted any subsequent changes will be > performed as specified in the accepted process document. > > The purpose of this exercise is to arrive at a consensus for how this > project will operate within the guidelines and requirements of the Apache > organization. > > Thanks for participating, > Claude --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
