Hi everyone, I think it is important that we can agree a basic set of documented processes. I'm proposing a small set of processes that lay a basic framework for collaboration. We only have a small number of regular contributors and another fairly small set of less frequent contributors so we need to have processes that require some oversight of changes without making the bar too high. I think my proposal [1] tries to make it easy for anyone to get involved and to avoid making the process too rigid for a small set of volunteer contributors to accept and apply changes.
The doc reflects the informal processes that we currently follow. I am hoping for an open discussion. It's a year since we last discussed this. See the initial conversation [2]. The ASF lists web site doesn't seem to display the follow-up conversation properly its permalink is used. Have a look here [3[ and see the conversation starting on 1 Nov 2022 (Re: [DISCUSS] Apache Pekko processes). I would like to get something agreed over the next few weeks. We can always agree to make changes to the processes as the focus of the project and/or the structure of the project team changes. I think getting the processes documented is one of final steps that we need to make before applying to graduate to become an ASF Top Level Project. [1] https://cwiki.apache.org/confluence/display/PEKKO/Processes [2] https://lists.apache.org/thread/0hohnn9v0xhxn0qblb196p7mcq7jzz00 [3] https://lists.apache.org/[email protected]:2022-11 --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
