In order to add a new committer you should:
Discuss a new committer
Create discuss email for a new committer:
To: private@datalab.apache.org Subject: [DISCUSS] New committer: ##Name Surname##
Hi all, We'd like to discuss the election of ##Name Surname## as a new committer.
Please refer to the following links to view his contributions:
1. Jira tasks: [link to to new committer's Jira tasks]
2. Pull requests [link to new committer's Github Pull request]
What do you think?
Vote for a new committer
If discussion is positive then create vote email for voting:
To: private@datalab.apache.org Subject: [VOTE] New committer: ##Name Surname## Hi all,
Following up the discussion thread ##link to email thread discussion##, I'd like to call a vote to elect ##Name Surname## as a new DataLab committer.
Voting ends one week from today, at midnight EET on YYYY-MM-DD
Voting to be Apache DataLab committer for ##Name surname## is open. Please discuss accordingly:
[] +1 approve
[] +0 no option
[] -1 disapprove with a reason
Summarize vote result
Let the Vote thread run for one week.
A positive result is achieved by Consensus Approval: i.e. at least 3 +1 votes and no vetoes.
Any veto must be accompanied by reasoning and the vetoer must be prepared to defend it. Other members can attempt to encourage them to change their minds.
New committers can be either quiet or active as they choose. If we find that certain people lapse and don’t ever contribute, then each project can take steps to retire them.
If voting is positive then result mail thread should be created on private@datalab.apache.org:
To: private@datalab.apache.org
Subject: [RESULT] [VOTE] New committer: ##Name Surname##
The vote has now closed. The results are:
Binding Votes: +1 [TOTAL BINDING +1 VOTES] 0 [TOTAL BINDING +0 VOTES] -1 [TOTAL BINDING -1 VOTES]
Voting thread:
[It should be link for vote emails thread] The vote is ##successful/not successful##
We'll ask ##Name Surname## if he wants to join the project as a committer.
Thank you all for voting!
Notice!
When adding a new PPMC member, there is no longer any requirement to wait for 72 hours after sending the NOTICE before adding the new PPMC member to your roster. The proposed PPMC member can be added after the NOTICE has been sent.
Send invitation to a new committer
Send an invitation after a positive result from the vote for a new committer.
To: newcommitter@foo.net Cc: private@datalab.apache.org Subject: Invitation to become DataLab committer: ##Name Surname## Hello [invitee name], The DataLab Project Management Committee hereby offers you committer privileges to the project . These privileges are offered on the understanding that you'll use them reasonably and with common
sense. We like to work on trust rather than unnecessary constraints. Being a committer enables you to more easily make changes without needing to go through the patch submission process. Being a committer does not require you to participate any more than you already do. It does tend to make one even more committed. You will probably find that you spend more time here. Of course, you can decline and instead remain as a contributor, participating as you do now. A. This personal invitation is a chance for you to accept or decline in private. Either way, please let us know in reply to the private@datalab.apache.org address only. B. If you accept, the next step is to register an iCLA: 1. Details of the iCLA and the forms are found through this link: http://www.apache.org/licenses/#clas 2. Instructions for its completion and return to the Secretary of the ASF are found at http://www.apache.org/licenses/#submitting 3. When you transmit the completed iCLA, request to notify the Apache DataLab. When recording of your iCLA is noticed, you will receive a follow-up message with the next steps for establishing you as a committer.
Yours, The Apache DataLab PMC
(g.e. https://lists.apache.org)
This is the follow-up email after the new committer has accepted the invitation:
To: newcommitter@foo.net Cc: private@datalab.apache.org Subject: Re: Invitation to become DataLab committer: ##Name Surname## Welcome. Here are the next steps. After that we will make an announcement to the datalab-dev list. You need to send a Contributor License Agreement to the ASF. Normally you would send an Individual CLA. If you also make contributions done in work time or using work resources then see the Corporate CLA. Ask us if you have any issues.
http://www.apache.org/licenses/#clas You need to choose a preferred ASF user name and alternatives. In order to ensure it is available you can view a list of taken ids at http://people.apache.org/committer-index.html Please notify us when you have submitted the CLA and by what means you did so. This will enable us to monitor its progress. We will arrange for your Apache user account when the CLA has been recorded. After that is done, please make followup replies to the datalab-dev list. We generally discuss everything there and keep the private@datalab.apache.org list for occasional matters which must be private. The developer section of the website describes the roles and provides other resources: http://www.apache.org/foundation/how-it-works.html http://www.apache.org/dev/ The incubator also has some useful information for new committers in incubating projects: http://incubator.apache.org/guides/committer.html http://incubator.apache.org/guides/ppmc.html Just as before you became a committer, participation in any ASF community requires adherence to the ASF Code of Conduct: https://www.apache.org/foundation/policies/conduct.html http://forrest.apache.org/guidelines.html Yours, The Apache DataLab PMC
Committer announcement
This is the email to announce to datalab-dev once the account has been created.
To: dev@datalab.apache.org Subject:[ANNOUNCE] New committer: ##Name Surname## The Project Management Committee (PMC) for Apache DataLab has invited [Name Surname] to become a committer and we are pleased to announce that he has accepted. ### add specific details here ### Being a committer enables easier contribution to the project since there is no need to go via the patch submission process. This should enable better productivity.
(g.e. https://lists.apache.org/thread)