Skip to main content

PMC members/Committer Related Permission Configuration

PMC ( Project Management Committee)/Committer member, bind github account process/and main email subscription

1. Binding github account process

1.1 Process overview

  1. Associate the apache account with the github account
  2. Securely enable 2FA authentication for github personal accounts
  3. Open permission application on gitbox

1.2 Associate apache Id with github account

Way 1 Log in to and set the [Your GitHub Username] field in LDAP to your own GitHub ID. Enter your password Click submit changes.


Way 2 Visit (replace with your apache id) to modify the corresponding data.

1.3 Enable 2FA authentication (login token)

github personal account security Enable 2FA authentication (login token)

Two-factor authentication (2FA) refers to a method of authenticating users by combining passwords and physical items (credit cards, SMS mobile phones, tokens, or biometric indicators such as fingerprints). To keep the committer account secure, we require you to enable 2FA on GitHub to authenticate logged in users and contribute code. For details, please refer to 2FA. You need to install TOTP software on the mobile phone, search for TOTP in the application market (Microsoft Authenticator is available for Android), and IOS Apple mobile phone personally recommends downloading the authy token software, which can be backed up in the cloud by binding the mobile phone. Mobile SMS is also supported, but the github configuration page does not have a mobile phone number +86 in China by default. For the front-end code bypass when you need to modify the configuration, see .

step1 Visit the personal account security settings page and select the fourth item [Account security]


step2 Select【Set up using an app】Next step


Step3 enter the qr code binding page, scan the code with the pre-downloaded totp type app (such as Google identity authenticator、Microsoft Authenticator), and input the 6 displayed on the mobile phone as the token


step4 Download recover codes, then enter the success page and click done to bind successfully


Notice When 2FA verification is turned on, you need to use the username/password + mobile phone authentication code to log in to GitHub. When 2FA authentication is enabled, a private access token needs to be generated for git submission and other operations. At this point, you will use username + private access token instead of username + password to submit code (subsequent configuration as needed). For details, see Creating a Private Token.

If 2FA is turned off in the future, you will be delisted from this project, and you will not be able to access our repository and the fork repository from our private repository.

1.4 Open permission application on gitbox

step1 Visit to authorize the associated apache account


step 2 Authorize the associated github account


step3 mfa status check


Notice After successful execution, the following figure is shown. After the success, the write permission will be activated within about an hour. If MFA Status says "User not a member of the ASF GitHub organisation. Please make sure you are a part of the ASF Organisation on GitHub and have 2FA enabled. Visit and set your GitHub ID to be invited to the org .” Please check whether [Associating apache and github accounts] is completed/2FA is enabled, if it is normal, please verify it later, because there is a delay in acquiring MFA status for new members.


After the successful invitation, the personal github account information can be seen that the affiliated organization has apache


[github uses TOTP to enable 2FA authentication]

[Create a private token]

[Introduction to gitbox]

[apache and github]

【git github &gitbox 】

2. Configure emails and email subscriptions

2.1 Associate your own mailbox

See for details

2.2 Configure forwarding address

You cannot use your Apache email address directly. You must set up forwarding for this address. When writing to your ASF address, the email will be forwarded to your forwarding address. When you reply, the message goes back through the ASF system, so people you write with will see it's coming from your ASF address . Configure in your email environment

Server: Port: 587 (STARTTLS), 465 (SSL) User/Pass: {Your LDAP credentials}


As a member of PMC, you need to actively participate in community construction, promote the healthy development of the community, undertake the responsibility and governance of the project, and this part of the work is often carried out by email (discussion/voting/answering questions, etc.), Every PMC member is required to subscribe to the following mailing lists:

NameDescriptionSubscribe MailUnsubscribe MailMail Archive
dev@linkis.apache.orgLinkis community activity information, project discussion announcements, etc.Subscribeunsubscribearchive
private@linkis.apache.orgThis mailing list is private, visible inside PMC members, mainly for internal discussions[Subscribe](mailto:private-subscribe@
general@incubator.apache.orgPublic emails from the incubator community, mainly related to incubation projects[Subscribe](mailto:general-subscribe@incubator.apache. org)unsubscribearchive

Subscription operations can be found in the guide Subscribe to the mailing list


Note: subscriptions need to be reviewed by the mail moderator (, so please attach personal name information to the content of the mail when subscribing for moderator review.

If the above subscription is unsuccessful, you can try to use the web-side tool:


Mailing list subscriptions, PMC members can view here: