infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Lambertus (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (INFRA-15676) GitBox for kafka and kafka-site
Date Tue, 19 Dec 2017 17:30:00 GMT

     [ https://issues.apache.org/jira/browse/INFRA-15676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Chris Lambertus updated INFRA-15676:
------------------------------------
    Status: Waiting for user  (was: Waiting for Infra)

Yes, that's correct. Please make sure your committers have associated their github ID with
their a.o account via id.apache.org, and make sure that they have 2fa enabled on github. 

Is there any coordination that needs to take place or can we move forward with the conversion
anytime?

> GitBox for kafka and kafka-site
> -------------------------------
>
>                 Key: INFRA-15676
>                 URL: https://issues.apache.org/jira/browse/INFRA-15676
>             Project: Infrastructure
>          Issue Type: GitBox Request
>          Components: GitBox
>            Reporter: Ismael Juma
>
> The Apache Kafka project would like to enable GitBox for the kafka and kafka-site Git
repositories.
> The successful vote can be found in the following mailing list thread:
> https://lists.apache.org/thread.html/3ef19c439e978993d1e40f0f30cc0126e79761b7b8910400fb7f18bb@%3Cdev.kafka.apache.org%3E
> Is it correct that for changes that require Admin access (like setting protected branches
and configuring the allowed merge options), we would still need Infra help?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message