alamb commented on code in PR #10778: URL: https://github.com/apache/datafusion/pull/10778#discussion_r1624248642
########## docs/source/contributor-guide/inviting.md: ########## @@ -0,0 +1,427 @@ +<!--- + Licensed to the Apache Software Foundation (ASF) under one + or more contributor license agreements. See the NOTICE file + distributed with this work for additional information + regarding copyright ownership. The ASF licenses this file + to you under the Apache License, Version 2.0 (the + "License"); you may not use this file except in compliance + with the License. You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, + software distributed under the License is distributed on an + "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY + KIND, either express or implied. See the License for the + specific language governing permissions and limitations + under the License. +--> + +# Inviting New Committers and PMC Members + +This is a cookbook of the recommended DataFusion specific process for inviting +new committers and PMC members. It is intended to follow the [Apache Project +Management Committee guidelines], which takes precedence over this document if +there is a conflict. + +This process is intended for PMC members. While the process is open, the actual +discussions and invitations are not (one of the very few things that we do not +do in the open). + +When following this process, in doubt, check the `priv...@datafusion.apache.org` +[mailing list archive] for examples of previous emails. + +The general process is: + +1. A PMC member starts a discussion on `priv...@datafusion.apache.org` + about a candidate they feel should be considered who would use the additional + trust granted to a committer or PMC member to help the community grow and thrive. +2. When consensus is reached a formal [vote] occurs +3. Assuming the vote is successful, that person is granted the appropriate + access via ASF systems. + +[apache project management committee guidelines]: https://www.apache.org/dev/pmc.html +[mailing list archive]: https://lists.apache.org/list.html?d...@datafusion.apache.org +[vote]: https://www.apache.org/foundation/voting + +## New Committers + +### Step 1: Start a Discussion Thread + +The goal of this step is to allow free form discussion prior to calling a vote. +This helps the other PMC members understand why you are proposing to invite the +person to become a committer and makes the voting process easier. + +Best practice is to include some details about why you are proposing to invite +the person. Here is an example: + +``` +To: priv...@datafusion.apache.org +Subject: [DISCUSS] $PERSONS_NAME for Committer + +$PERSONS_NAME has been an active contributor to the Datafusion community for the +last 6 months[1][2], helping others, answering questions, and improving the +project's code. + +Are there any thoughts about inviting $PERSONS_NAME to become a committer? + +Thanks, +Your Name + +[1]: https://github.com/apache/datafusion/issues?q=commenter%3A<github id> +[2]: https://github.com/apache/datafusion/commits?author=<github id> +``` + +### Step 2: Formal Vote + +Assuming the discussion thread goes well, start a formal vote, with an email like: + +``` +To: priv...@datafusion.apache.org +Subject: [VOTE] $PERSONS_NAME for DataFusion Committer +I propose to invite $PERSONS_NAME to be a committer. See discussion here [1]. + +[ ] +1 : Invite $PERSONS_NAME to become a committer +[ ] +0: ... +[ ] -1: I disagree because ... + +The vote will be open for at least 48 hours. + +My vote: +1 + +Thanks, +Your Name + +[1] LINK TO DISCUSSION THREAD (e.g. https://lists.apache.org/thread/7rocc026wckknrjt9j6bsqk3z4c0g5yf) +``` + +If the vote passes (requires 3 `+1`, and no `-1` voites) , send a result email +like the following (substitute `N` with the number of `+1` votes) + +``` +to: priv...@datafusion.apache.org +subject: [RESULT][VOTE] $PERSONS_NAME for DataFusion Committer + +The vote carries with N +1 votes. +``` + +### Step 3: Send Invitation to the Candidate + +Once the vote on `private@` has passed and the `[RESULT]` e-mail sent, send an +invitation to the new committer and cc: `priv...@datafusion.apache.org` + +In order to be given write access, the committer needs an apache.org account (e.g. `n...@apache.org`). To get one they need: + +1. An [ICLA] on file. Note that Sending an ICLA to `secret...@apache.org` will trigger account creation. If they already have an ICLA on file, but no Apache account, see instructions below. +2. Add GitHub username to the account at [id.apache.org](http://id.apache.org/) +3. Connect [gitbox.apache.org] to their GitHub account +4. Follow the instructions at [gitbox.apache.org] to link your GitHub account with your + +[gitbox.apache.org]: https://gitbox.apache.org + +If the new committer is already a committer on another Apache project (so they +already had an Apache account), The PMC Chair (or an ASF member) simply needs to +explicitly add them to the roster on the [Whimsy Roster Tool]. + +### Step 4: Announce and Celebrate the New Committer Review Comment: While working on this document it seems like maybe we haven't announced @kazuyukitanimura or @huaxingao yet to dev @viirya is that something you would like me to do? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: github-unsubscr...@datafusion.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: github-unsubscr...@datafusion.apache.org For additional commands, e-mail: github-h...@datafusion.apache.org
