Excellent feedback! Thank you! We sorta already do #1, but you are right, we don’t have it documented as part of the process. We are still pretty small, and it didn’t occur to us to write it down, but we clearly could.
#2 has occurred to me as well and separating the requirements from the details of the process is cleaner. I had to document the process, because the ASF and Incubator documentation is rather scattered, lacking critical information, and hard to find. I also noticed that several other projects have done the same thing. Cheers and stay healthy. Lee. On Mon, Dec 21, 2020 at 9:10 AM Kenneth Knowles <[email protected]> wrote: > I like it! Couple thoughts, having authored a similar doc: > > 1. You may also want to have some process or practice that comes prior to > the proposal, for discussing new or repeat contributors. Often an initial > discussion may result in "wait and see" or "let's reach out to them". For > Beam it has been very effective to send a thank you email with > encouragement. Of course, just getting a nice email isn't going to > magically change their job or personal interest/availability. I think it > helps a contributor realize that they *can* become a committer, rather than > thinking they are permanently "outside" the project. > > 2. Another note is that this process is good PMC-facing documentation but > obviously also serves for contributors to understand the expectations. You > may want to either phrase it to serve both purposes well, or have two > separate docs. In Beam the expectations are largely contributor-focused ( > https://beam.apache.org/contribute/become-a-committer/). The official > process is not actually documented AFAIK but if it were it would focus on > procedures and simply reference the contributor-focused list of > expectations. > > That's all just ideas from a quite different project. This is a nice doc > already. > > Kenn > > On Wed, Nov 4, 2020 at 12:03 PM leerho <[email protected]> wrote: > >> Evans, >> Yes, it will remain somewhat "hidden" until we have a consensus, then it >> will be reachable from the ToC. >> >> Thanks for your suggestion, that is a good one to add :) >> >> Lee. >> >> On Wed, Nov 4, 2020 at 10:38 AM Evans Ye <[email protected]> wrote: >> >>> For the Community Contributions section, you can consider whether to add >>> marketing, tech evangelist kind of things as recognized contributions. In >>> Bigtop we had a committer/PMC who's mainly organizing workshops/meetups, >>> doing tech talks, writing blogposts for community growth. >>> >>> I can't find the link via the website's navigation tabs. So once >>> finalized it will be added? >>> >>> >>> leerho <[email protected]> 於 2020年11月3日 週二 上午6:08寫道： >>> >>>> Folks, >>>> I have written a New Committer Process for our project. It is a bit >>>> more focused than the ASF material also online, and includes a more >>>> specific set of guidelines for accepting candidates for our project. This >>>> document focuses on new committers and not new PMC members, which is a >>>> slightly different process. >>>> >>>> I tried to pen templates that would be relevant to our project as well, >>>> to save our PMC members time in constructing the letters. >>>> >>>> Please review and provide feedback as I would like to add this to our >>>> Website in the Community / Contributing section. >>>> >>>> https://datasketches.apache.org/docs/Community/NewCommitterProcess.html >>>> >>>> Thanks, >>>> >>>> Lee. >>>> >>> -- >From my cell phone.
