Re: [jira] [Commented] (INFRA-14376) Pulsar GitHub Integration
Hi Matteo, Thanks. I’ll be trying this out for myself tomorrow. Regards, Dave > On Jun 29, 2017, at 3:42 PM, Matteo Merli wrote: > > The GitBox integration is complete. > > I can see the "pulsar committers" teams in the Apache org in GitHub. > > All the committers should now link their GitHub with the Apache account and > they will be automatically granted write permissions on the repository. > I can see 4 of us so far are enabled. > > Visit https://gitbox.apache.org/setup/ <https://gitbox.apache.org/setup/> to > link the accounts. > > Notice that it might take a while to reflect the permission (I think there's > a cron job that periodically syncs up the accounts permissions). > > -- > Matteo Merli > mailto:mme...@apache.org>> > > -- Forwarded message -- > From: Chris Thistlethwaite (JIRA) mailto:j...@apache.org>> > Date: Thu, Jun 29, 2017 at 1:01 PM > Subject: [jira] [Commented] (INFRA-14376) Pulsar GitHub Integration > To: mme...@apache.org <mailto:mme...@apache.org> > > > Chris Thistlethwaite > <https://issues.apache.org/jira/secure/ViewProfile.jspa?name=cthistle> > commented on INFRA-14376 <https://issues.apache.org/jira/browse/INFRA-14376> > > Re: Pulsar GitHub Integration > <https://issues.apache.org/jira/browse/INFRA-14376> > GitBox has been enabled > > g...@github.com <mailto:g...@github.com>:apache/incubator-pulsar.git > > https://gitbox.apache.org/repos/asf?p=incubator-pulsar.git;a=summary > <https://gitbox.apache.org/repos/asf?p=incubator-pulsar.git;a=summary> ><https://issues.apache.org/jira/browse/INFRA-14376#add-comment> > Add Comment > <https://issues.apache.org/jira/browse/INFRA-14376#add-comment> > > This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) > > signature.asc Description: Message signed with OpenPGP
Fwd: [jira] [Commented] (INFRA-14376) Pulsar GitHub Integration
The GitBox integration is complete. I can see the "pulsar committers" teams in the Apache org in GitHub. All the committers should now link their GitHub with the Apache account and they will be automatically granted write permissions on the repository. I can see 4 of us so far are enabled. Visit https://gitbox.apache.org/setup/ to link the accounts. Notice that it might take a while to reflect the permission (I think there's a cron job that periodically syncs up the accounts permissions). -- Matteo Merli -- Forwarded message -- From: Chris Thistlethwaite (JIRA) Date: Thu, Jun 29, 2017 at 1:01 PM Subject: [jira] [Commented] (INFRA-14376) Pulsar GitHub Integration To: mme...@apache.org Chris Thistlethwaite <https://issues.apache.org/jira/secure/ViewProfile.jspa?name=cthistle> *commented* on [image: Github Integration] INFRA-14376 <https://issues.apache.org/jira/browse/INFRA-14376> Re: Pulsar GitHub Integration <https://issues.apache.org/jira/browse/INFRA-14376> GitBox has been enabled g...@github.com:apache/incubator-pulsar.git https://gitbox.apache.org/repos/asf?p=incubator-pulsar.git;a=summary [image: Add Comment] <https://issues.apache.org/jira/browse/INFRA-14376#add-comment> Add Comment <https://issues.apache.org/jira/browse/INFRA-14376#add-comment> This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) [image: Atlassian logo]
Re: [jira] [Commented] (INFRA-14376) Pulsar GitHub Integration
> >> > >>> *apache id - GitHub id * > >> > >>> andrews - saandrews > >> > >>> joef - joefk > >> > >>> rdhabalia - rdhabalia > >> > >>> > >> > >>> Thanks, > >> > >>> Andrews. > >> > >>> > >> > >>> On Wed, Jun 21, 2017 at 3:08 PM, Sahaya Andrews < > >> > sahaya.andr...@gmail.com <mailto:sahaya.andr...@gmail.com>> > >> > >>> wrote: > >> > >>> > >> > >>>> I have updated my GitHub id in profile. > >> > >>>> > >> > >>>> What does the "reporeq" step meant to do? > >> > >>>> > >> > >>>> On Wed, Jun 21, 2017 at 2:56 PM, Matteo Merli >> > >>>> <mailto:mme...@apache.org>> > >> > wrote: > >> > >>>> > >> > >>>>> The repo location has now been transferred to > >> > >>>>> https://github.com/apache/incubator-pulsar > >> > >>>>> <https://github.com/apache/incubator-pulsar> > >> > >>>>> > >> > >>>>> I think the next step would be to do the "reporeq" at > >> > >>>>> https://reporeq.apache.org <https://reporeq.apache.org/> > >> > >>>>> And that should be done by someone in IPMC :) > >> > >>>>> I am not sure wether it was already done though. > >> > >>>>> > >> > >>>>> For all the committers: you should go to id.apache.org > >> > >>>>> <http://id.apache.org/> and enter > >> > your > >> > >>>>> github account there, so that you can link that account to the > >> > >>>>> apache > >> > >>>>> account. > >> > >>>>> > >> > >>>>> Matteo > >> > >>>>> > >> > >>>>> > >> > >>>>> -- Forwarded message - > >> > >>>>> From: Daniel Takamori (JIRA) >> > >>>>> <mailto:j...@apache.org>> > >> > >>>>> Date: Wed, Jun 21, 2017 at 2:11 PM > >> > >>>>> Subject: [jira] [Commented] (INFRA-14376) Pulsar GitHub > >> > >>>>> Integration > >> > >>>>> To: mailto:mme...@apache.org>> > >> > >>>>> > >> > >>>>> > >> > >>>>> Daniel Takamori > >> > >>>>> <https://issues.apache.org/jira/secure/ViewProfile.jspa?name=pono > >> > >>>>> <https://issues.apache.org/jira/secure/ViewProfile.jspa?name=pono>> > >> > >>>>> *commented* on [image: Github Integration] INFRA-14376 > >> > >>>>> <https://issues.apache.org/jira/browse/INFRA-14376 > >> > >>>>> <https://issues.apache.org/jira/browse/INFRA-14376>> > >> > >>>>> > >> > >>>>> Re: Pulsar GitHub Integration > >> > >>>>> <https://issues.apache.org/jira/browse/INFRA-14376 > >> > >>>>> <https://issues.apache.org/jira/browse/INFRA-14376>> > >> > >>>>> Imported the repo to Apache and set the hooks, now your PMC can go > >> > >>>>> to > >> > >>>>> https://reporeq.apache.org <https://reporeq.apache.org/> to clone > >> > >>>>> the Apache repo and we can > >> > >>>>> move > >> > on > >> > >>>>> from there :) > >> > >>>>> > >> > >>>>> <https://issues.apache.org/jira/browse/INFRA-14376#add-comment > >> > >>>>> <https://issues.apache.org/jira/browse/INFRA-14376#add-comment>> > >> > >>>>> Add > >> > >>>>> Comment <https://issues.apache.org/jira/browse/INFRA-14376#add- > >> > >>>>> <https://issues.apache.org/jira/browse/INFRA-14376#add-> > >> > comment> > >> > >>>>> > >> > >>>>> This message was sent by Atlassian JIRA > >> > >>>>> (v6.4.14#64029-sha1:ae256fe) > >> > >>>>> > >> > >>>> > >> > >>>> > >> > >>> > >> > > >> > signature.asc Description: Message signed with OpenPGP
Re: [jira] [Commented] (INFRA-14376) Pulsar GitHub Integration
Dave, I think we need to open an INFRA ticket with the type "GitBox request" to have that started. Can you create that? Or can I do that? (I don't know whether that request needs to come from an IPMC member). Thanks, Matteo On Thu, Jun 22, 2017 at 11:46 PM Sahaya Andrews wrote: > Thank you everyone for taking time to respond. I guess we will wait > till the gitbox integration to complete. > > On Thu, Jun 22, 2017 at 6:06 PM, Matteo Merli wrote: > > I think the gitbox integration is still not active. If I go on > > https://gitbox.apache.org/setup/ > > > > I can see that : > > > > According to LDAP, you will have access to the following repositories: > > > > bookkeeper: > > No repositories for the bookkeeper project served from gitbox yet... > > incubator: > > No repositories for the incubator project served from gitbox yet... > > pulsar: > > No repositories for the pulsar project served from gitbox yet... > > > > > > > > On Thu, Jun 22, 2017 at 6:03 PM Rajan Dhabalia > > wrote: > >> > >> Hi Dave, > >> > >> > Everyone who has provided an iCLA and has setup their Apache ID to > point > >> to their GitHub ID should have Write access as you see. > >> Actually, I have verified that my Apache ID is pointing to GitHub-ID > >> (username) and I have also submitted the iCLA earlier. I think it's same > >> for Andrews as well. So, not sure if write-access is not provided due to > >> other incomplete process for which we might have to wait for some more > >> time. > >> > >> Thanks, > >> Rajan > >> > >> > >> On Thu, Jun 22, 2017 at 5:49 PM, Dave Fisher > >> wrote: > >> > >> > Hi Andrews, > >> > > >> > > On Jun 22, 2017, at 3:40 PM, Sahaya Andrews < > sahaya.andr...@gmail.com> > >> > wrote: > >> > > > >> > > When can we expect the setup to be finalized? We are still waiting > to > >> > > get write access. Some of us who were part of the dev group in the > old > >> > > repo got write access automatically. But the rest who were part of > >> > > admin group did not :) > >> > > >> > Everyone who has provided an iCLA and has setup their Apache ID to > point > >> > to their GitHub ID should have Write access as you see. > >> > > >> > Daniel - would you comment on Admin privilege setup with Gitbox > >> > integration. What can the podling expect? How do we control the group? > >> > Do > >> > we do JIRA tickets? I know the Gitbox integration is new and the > >> > documentation that you pointed me to is out of date and not on point > >> > with > >> > the new. > >> > > >> > Regards, > >> > Dave > >> > > >> > > > >> > > Andrews. > >> > > > >> > > On Wed, Jun 21, 2017 at 4:36 PM, Matteo Merli > >> > > wrote: > >> > >> Andrews, > >> > >> > >> > >> once the setup is finalized, all the committers will have write > >> > >> access > >> > if > >> > >> the github account is linked to the Apache account. > >> > >> > >> > >> > >> > >> > >> > >> On Wed, Jun 21, 2017 at 3:32 PM Sahaya Andrews < > >> > sahaya.andr...@gmail.com> > >> > >> wrote: > >> > >> > >> > >>> Hi Daniel, > >> > >>> > >> > >>> Could you add pulsar repo write access to the following GitHub > >> > account? > >> > >>> These folks were part of admin account before moving the repo. > >> > >>> *apache id - GitHub id * > >> > >>> andrews - saandrews > >> > >>> joef - joefk > >> > >>> rdhabalia - rdhabalia > >> > >>> > >> > >>> Thanks, > >> > >>> Andrews. > >> > >>> > >> > >>> On Wed, Jun 21, 2017 at 3:08 PM, Sahaya Andrews < > >> > sahaya.andr...@gmail.com> > >> > >>> wrote: > >> > >>> > >> > >>>> I have updated my GitHub id in profile. > >> > >>>> > >> > >>>> What does the "reporeq" step meant to do? > >> > &
Re: [jira] [Commented] (INFRA-14376) Pulsar GitHub Integration
Thank you everyone for taking time to respond. I guess we will wait till the gitbox integration to complete. On Thu, Jun 22, 2017 at 6:06 PM, Matteo Merli wrote: > I think the gitbox integration is still not active. If I go on > https://gitbox.apache.org/setup/ > > I can see that : > > According to LDAP, you will have access to the following repositories: > > bookkeeper: > No repositories for the bookkeeper project served from gitbox yet... > incubator: > No repositories for the incubator project served from gitbox yet... > pulsar: > No repositories for the pulsar project served from gitbox yet... > > > > On Thu, Jun 22, 2017 at 6:03 PM Rajan Dhabalia > wrote: >> >> Hi Dave, >> >> > Everyone who has provided an iCLA and has setup their Apache ID to point >> to their GitHub ID should have Write access as you see. >> Actually, I have verified that my Apache ID is pointing to GitHub-ID >> (username) and I have also submitted the iCLA earlier. I think it's same >> for Andrews as well. So, not sure if write-access is not provided due to >> other incomplete process for which we might have to wait for some more >> time. >> >> Thanks, >> Rajan >> >> >> On Thu, Jun 22, 2017 at 5:49 PM, Dave Fisher >> wrote: >> >> > Hi Andrews, >> > >> > > On Jun 22, 2017, at 3:40 PM, Sahaya Andrews >> > wrote: >> > > >> > > When can we expect the setup to be finalized? We are still waiting to >> > > get write access. Some of us who were part of the dev group in the old >> > > repo got write access automatically. But the rest who were part of >> > > admin group did not :) >> > >> > Everyone who has provided an iCLA and has setup their Apache ID to point >> > to their GitHub ID should have Write access as you see. >> > >> > Daniel - would you comment on Admin privilege setup with Gitbox >> > integration. What can the podling expect? How do we control the group? >> > Do >> > we do JIRA tickets? I know the Gitbox integration is new and the >> > documentation that you pointed me to is out of date and not on point >> > with >> > the new. >> > >> > Regards, >> > Dave >> > >> > > >> > > Andrews. >> > > >> > > On Wed, Jun 21, 2017 at 4:36 PM, Matteo Merli >> > > wrote: >> > >> Andrews, >> > >> >> > >> once the setup is finalized, all the committers will have write >> > >> access >> > if >> > >> the github account is linked to the Apache account. >> > >> >> > >> >> > >> >> > >> On Wed, Jun 21, 2017 at 3:32 PM Sahaya Andrews < >> > sahaya.andr...@gmail.com> >> > >> wrote: >> > >> >> > >>> Hi Daniel, >> > >>> >> > >>> Could you add pulsar repo write access to the following GitHub >> > account? >> > >>> These folks were part of admin account before moving the repo. >> > >>> *apache id - GitHub id * >> > >>> andrews - saandrews >> > >>> joef - joefk >> > >>> rdhabalia - rdhabalia >> > >>> >> > >>> Thanks, >> > >>> Andrews. >> > >>> >> > >>> On Wed, Jun 21, 2017 at 3:08 PM, Sahaya Andrews < >> > sahaya.andr...@gmail.com> >> > >>> wrote: >> > >>> >> > >>>> I have updated my GitHub id in profile. >> > >>>> >> > >>>> What does the "reporeq" step meant to do? >> > >>>> >> > >>>> On Wed, Jun 21, 2017 at 2:56 PM, Matteo Merli >> > wrote: >> > >>>> >> > >>>>> The repo location has now been transferred to >> > >>>>> https://github.com/apache/incubator-pulsar >> > >>>>> >> > >>>>> I think the next step would be to do the "reporeq" at >> > >>>>> https://reporeq.apache.org >> > >>>>> And that should be done by someone in IPMC :) >> > >>>>> I am not sure wether it was already done though. >> > >>>>> >> > >>>>> For all the committers: you should go to id.apache.org and enter >> > your >> > >>>>> github account there, so that you can link that account to the >> > >>>>> apache >> > >>>>> account. >> > >>>>> >> > >>>>> Matteo >> > >>>>> >> > >>>>> >> > >>>>> -- Forwarded message - >> > >>>>> From: Daniel Takamori (JIRA) >> > >>>>> Date: Wed, Jun 21, 2017 at 2:11 PM >> > >>>>> Subject: [jira] [Commented] (INFRA-14376) Pulsar GitHub >> > >>>>> Integration >> > >>>>> To: >> > >>>>> >> > >>>>> >> > >>>>> Daniel Takamori >> > >>>>> <https://issues.apache.org/jira/secure/ViewProfile.jspa?name=pono> >> > >>>>> *commented* on [image: Github Integration] INFRA-14376 >> > >>>>> <https://issues.apache.org/jira/browse/INFRA-14376> >> > >>>>> >> > >>>>> Re: Pulsar GitHub Integration >> > >>>>> <https://issues.apache.org/jira/browse/INFRA-14376> >> > >>>>> Imported the repo to Apache and set the hooks, now your PMC can go >> > >>>>> to >> > >>>>> https://reporeq.apache.org to clone the Apache repo and we can >> > >>>>> move >> > on >> > >>>>> from there :) >> > >>>>> >> > >>>>> <https://issues.apache.org/jira/browse/INFRA-14376#add-comment> >> > >>>>> Add >> > >>>>> Comment <https://issues.apache.org/jira/browse/INFRA-14376#add- >> > comment> >> > >>>>> >> > >>>>> This message was sent by Atlassian JIRA >> > >>>>> (v6.4.14#64029-sha1:ae256fe) >> > >>>>> >> > >>>> >> > >>>> >> > >>> >> > >> >
Re: [jira] [Commented] (INFRA-14376) Pulsar GitHub Integration
I think the gitbox integration is still not active. If I go on https://gitbox.apache.org/setup/ I can see that : According to LDAP, you will have access to the following repositories: bookkeeper: No repositories for the bookkeeper project served from gitbox yet... incubator: No repositories for the incubator project served from gitbox yet... pulsar: No repositories for the pulsar project served from gitbox yet... On Thu, Jun 22, 2017 at 6:03 PM Rajan Dhabalia wrote: > Hi Dave, > > > Everyone who has provided an iCLA and has setup their Apache ID to point > to their GitHub ID should have Write access as you see. > Actually, I have verified that my Apache ID is pointing to GitHub-ID > (username) and I have also submitted the iCLA earlier. I think it's same > for Andrews as well. So, not sure if write-access is not provided due to > other incomplete process for which we might have to wait for some more > time. > > Thanks, > Rajan > > > On Thu, Jun 22, 2017 at 5:49 PM, Dave Fisher > wrote: > > > Hi Andrews, > > > > > On Jun 22, 2017, at 3:40 PM, Sahaya Andrews > > wrote: > > > > > > When can we expect the setup to be finalized? We are still waiting to > > > get write access. Some of us who were part of the dev group in the old > > > repo got write access automatically. But the rest who were part of > > > admin group did not :) > > > > Everyone who has provided an iCLA and has setup their Apache ID to point > > to their GitHub ID should have Write access as you see. > > > > Daniel - would you comment on Admin privilege setup with Gitbox > > integration. What can the podling expect? How do we control the group? Do > > we do JIRA tickets? I know the Gitbox integration is new and the > > documentation that you pointed me to is out of date and not on point with > > the new. > > > > Regards, > > Dave > > > > > > > > Andrews. > > > > > > On Wed, Jun 21, 2017 at 4:36 PM, Matteo Merli > wrote: > > >> Andrews, > > >> > > >> once the setup is finalized, all the committers will have write access > > if > > >> the github account is linked to the Apache account. > > >> > > >> > > >> > > >> On Wed, Jun 21, 2017 at 3:32 PM Sahaya Andrews < > > sahaya.andr...@gmail.com> > > >> wrote: > > >> > > >>> Hi Daniel, > > >>> > > >>> Could you add pulsar repo write access to the following GitHub > > account? > > >>> These folks were part of admin account before moving the repo. > > >>> *apache id - GitHub id * > > >>> andrews - saandrews > > >>> joef - joefk > > >>> rdhabalia - rdhabalia > > >>> > > >>> Thanks, > > >>> Andrews. > > >>> > > >>> On Wed, Jun 21, 2017 at 3:08 PM, Sahaya Andrews < > > sahaya.andr...@gmail.com> > > >>> wrote: > > >>> > > >>>> I have updated my GitHub id in profile. > > >>>> > > >>>> What does the "reporeq" step meant to do? > > >>>> > > >>>> On Wed, Jun 21, 2017 at 2:56 PM, Matteo Merli > > wrote: > > >>>> > > >>>>> The repo location has now been transferred to > > >>>>> https://github.com/apache/incubator-pulsar > > >>>>> > > >>>>> I think the next step would be to do the "reporeq" at > > >>>>> https://reporeq.apache.org > > >>>>> And that should be done by someone in IPMC :) > > >>>>> I am not sure wether it was already done though. > > >>>>> > > >>>>> For all the committers: you should go to id.apache.org and enter > > your > > >>>>> github account there, so that you can link that account to the > apache > > >>>>> account. > > >>>>> > > >>>>> Matteo > > >>>>> > > >>>>> > > >>>>> -- Forwarded message - > > >>>>> From: Daniel Takamori (JIRA) > > >>>>> Date: Wed, Jun 21, 2017 at 2:11 PM > > >>>>> Subject: [jira] [Commented] (INFRA-14376) Pulsar GitHub Integration > > >>>>> To: > > >>>>> > > >>>>> > > >>>>> Daniel Takamori > > >>>>> <https://issues.apache.org/jira/secure/ViewProfile.jspa?name=pono> > > >>>>> *commented* on [image: Github Integration] INFRA-14376 > > >>>>> <https://issues.apache.org/jira/browse/INFRA-14376> > > >>>>> > > >>>>> Re: Pulsar GitHub Integration > > >>>>> <https://issues.apache.org/jira/browse/INFRA-14376> > > >>>>> Imported the repo to Apache and set the hooks, now your PMC can go > to > > >>>>> https://reporeq.apache.org to clone the Apache repo and we can > move > > on > > >>>>> from there :) > > >>>>> > > >>>>> <https://issues.apache.org/jira/browse/INFRA-14376#add-comment> > Add > > >>>>> Comment <https://issues.apache.org/jira/browse/INFRA-14376#add- > > comment> > > >>>>> > > >>>>> This message was sent by Atlassian JIRA > (v6.4.14#64029-sha1:ae256fe) > > >>>>> > > >>>> > > >>>> > > >>> > > > > >
Re: [jira] [Commented] (INFRA-14376) Pulsar GitHub Integration
Hi Dave, > Everyone who has provided an iCLA and has setup their Apache ID to point to their GitHub ID should have Write access as you see. Actually, I have verified that my Apache ID is pointing to GitHub-ID (username) and I have also submitted the iCLA earlier. I think it's same for Andrews as well. So, not sure if write-access is not provided due to other incomplete process for which we might have to wait for some more time. Thanks, Rajan On Thu, Jun 22, 2017 at 5:49 PM, Dave Fisher wrote: > Hi Andrews, > > > On Jun 22, 2017, at 3:40 PM, Sahaya Andrews > wrote: > > > > When can we expect the setup to be finalized? We are still waiting to > > get write access. Some of us who were part of the dev group in the old > > repo got write access automatically. But the rest who were part of > > admin group did not :) > > Everyone who has provided an iCLA and has setup their Apache ID to point > to their GitHub ID should have Write access as you see. > > Daniel - would you comment on Admin privilege setup with Gitbox > integration. What can the podling expect? How do we control the group? Do > we do JIRA tickets? I know the Gitbox integration is new and the > documentation that you pointed me to is out of date and not on point with > the new. > > Regards, > Dave > > > > > Andrews. > > > > On Wed, Jun 21, 2017 at 4:36 PM, Matteo Merli wrote: > >> Andrews, > >> > >> once the setup is finalized, all the committers will have write access > if > >> the github account is linked to the Apache account. > >> > >> > >> > >> On Wed, Jun 21, 2017 at 3:32 PM Sahaya Andrews < > sahaya.andr...@gmail.com> > >> wrote: > >> > >>> Hi Daniel, > >>> > >>> Could you add pulsar repo write access to the following GitHub > account? > >>> These folks were part of admin account before moving the repo. > >>> *apache id - GitHub id * > >>> andrews - saandrews > >>> joef - joefk > >>> rdhabalia - rdhabalia > >>> > >>> Thanks, > >>> Andrews. > >>> > >>> On Wed, Jun 21, 2017 at 3:08 PM, Sahaya Andrews < > sahaya.andr...@gmail.com> > >>> wrote: > >>> > >>>> I have updated my GitHub id in profile. > >>>> > >>>> What does the "reporeq" step meant to do? > >>>> > >>>> On Wed, Jun 21, 2017 at 2:56 PM, Matteo Merli > wrote: > >>>> > >>>>> The repo location has now been transferred to > >>>>> https://github.com/apache/incubator-pulsar > >>>>> > >>>>> I think the next step would be to do the "reporeq" at > >>>>> https://reporeq.apache.org > >>>>> And that should be done by someone in IPMC :) > >>>>> I am not sure wether it was already done though. > >>>>> > >>>>> For all the committers: you should go to id.apache.org and enter > your > >>>>> github account there, so that you can link that account to the apache > >>>>> account. > >>>>> > >>>>> Matteo > >>>>> > >>>>> > >>>>> -- Forwarded message - > >>>>> From: Daniel Takamori (JIRA) > >>>>> Date: Wed, Jun 21, 2017 at 2:11 PM > >>>>> Subject: [jira] [Commented] (INFRA-14376) Pulsar GitHub Integration > >>>>> To: > >>>>> > >>>>> > >>>>> Daniel Takamori > >>>>> <https://issues.apache.org/jira/secure/ViewProfile.jspa?name=pono> > >>>>> *commented* on [image: Github Integration] INFRA-14376 > >>>>> <https://issues.apache.org/jira/browse/INFRA-14376> > >>>>> > >>>>> Re: Pulsar GitHub Integration > >>>>> <https://issues.apache.org/jira/browse/INFRA-14376> > >>>>> Imported the repo to Apache and set the hooks, now your PMC can go to > >>>>> https://reporeq.apache.org to clone the Apache repo and we can move > on > >>>>> from there :) > >>>>> > >>>>> <https://issues.apache.org/jira/browse/INFRA-14376#add-comment> Add > >>>>> Comment <https://issues.apache.org/jira/browse/INFRA-14376#add- > comment> > >>>>> > >>>>> This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) > >>>>> > >>>> > >>>> > >>> > >
Re: [jira] [Commented] (INFRA-14376) Pulsar GitHub Integration
Hi Andrews, > On Jun 22, 2017, at 3:40 PM, Sahaya Andrews wrote: > > When can we expect the setup to be finalized? We are still waiting to > get write access. Some of us who were part of the dev group in the old > repo got write access automatically. But the rest who were part of > admin group did not :) Everyone who has provided an iCLA and has setup their Apache ID to point to their GitHub ID should have Write access as you see. Daniel - would you comment on Admin privilege setup with Gitbox integration. What can the podling expect? How do we control the group? Do we do JIRA tickets? I know the Gitbox integration is new and the documentation that you pointed me to is out of date and not on point with the new. Regards, Dave > > Andrews. > > On Wed, Jun 21, 2017 at 4:36 PM, Matteo Merli wrote: >> Andrews, >> >> once the setup is finalized, all the committers will have write access if >> the github account is linked to the Apache account. >> >> >> >> On Wed, Jun 21, 2017 at 3:32 PM Sahaya Andrews >> wrote: >> >>> Hi Daniel, >>> >>> Could you add pulsar repo write access to the following GitHub account? >>> These folks were part of admin account before moving the repo. >>> *apache id - GitHub id * >>> andrews - saandrews >>> joef - joefk >>> rdhabalia - rdhabalia >>> >>> Thanks, >>> Andrews. >>> >>> On Wed, Jun 21, 2017 at 3:08 PM, Sahaya Andrews >>> wrote: >>> >>>> I have updated my GitHub id in profile. >>>> >>>> What does the "reporeq" step meant to do? >>>> >>>> On Wed, Jun 21, 2017 at 2:56 PM, Matteo Merli wrote: >>>> >>>>> The repo location has now been transferred to >>>>> https://github.com/apache/incubator-pulsar >>>>> >>>>> I think the next step would be to do the "reporeq" at >>>>> https://reporeq.apache.org >>>>> And that should be done by someone in IPMC :) >>>>> I am not sure wether it was already done though. >>>>> >>>>> For all the committers: you should go to id.apache.org and enter your >>>>> github account there, so that you can link that account to the apache >>>>> account. >>>>> >>>>> Matteo >>>>> >>>>> >>>>> -- Forwarded message - >>>>> From: Daniel Takamori (JIRA) >>>>> Date: Wed, Jun 21, 2017 at 2:11 PM >>>>> Subject: [jira] [Commented] (INFRA-14376) Pulsar GitHub Integration >>>>> To: >>>>> >>>>> >>>>> Daniel Takamori >>>>> <https://issues.apache.org/jira/secure/ViewProfile.jspa?name=pono> >>>>> *commented* on [image: Github Integration] INFRA-14376 >>>>> <https://issues.apache.org/jira/browse/INFRA-14376> >>>>> >>>>> Re: Pulsar GitHub Integration >>>>> <https://issues.apache.org/jira/browse/INFRA-14376> >>>>> Imported the repo to Apache and set the hooks, now your PMC can go to >>>>> https://reporeq.apache.org to clone the Apache repo and we can move on >>>>> from there :) >>>>> >>>>> <https://issues.apache.org/jira/browse/INFRA-14376#add-comment> Add >>>>> Comment <https://issues.apache.org/jira/browse/INFRA-14376#add-comment> >>>>> >>>>> This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) >>>>> >>>> >>>> >>> signature.asc Description: Message signed with OpenPGP
Re: [jira] [Commented] (INFRA-14376) Pulsar GitHub Integration
Hi Andrews, I completely understand your excitement, which s a good thing! But one of the things you'll learn during incubation is the need to be patient. The infrastructure team has a lot of podlings, TLPs, and other matters to attend to in a largely volunteer organization. You'll also likely experience some slow down in the pace of development as the community grows to include those in other time zones which you'll have to accommodate (e.g. Waiting 24 hours or more to merge a patch so others have ample time to review). Apache projects are about community more so than code (you will likely hear the phrase "community over code" repeated a lot). There's a lot of tried and true experience behind that mantra. Is there an associated "speed of development tax" associated with that? Yes, but the tax is worth it. Apache projects work differently than internally developed and controlled projects in a corporate environment. Don't take any of this as negative, I'm mainly trying to set the appropriate expectations. -Taylor > On Jun 22, 2017, at 6:40 PM, Sahaya Andrews wrote: > > When can we expect the setup to be finalized? We are still waiting to > get write access. Some of us who were part of the dev group in the old > repo got write access automatically. But the rest who were part of > admin group did not :) > > Andrews. > >> On Wed, Jun 21, 2017 at 4:36 PM, Matteo Merli wrote: >> Andrews, >> >> once the setup is finalized, all the committers will have write access if >> the github account is linked to the Apache account. >> >> >> >> On Wed, Jun 21, 2017 at 3:32 PM Sahaya Andrews >> wrote: >> >>> Hi Daniel, >>> >>> Could you add pulsar repo write access to the following GitHub account? >>> These folks were part of admin account before moving the repo. >>> *apache id - GitHub id * >>> andrews - saandrews >>> joef - joefk >>> rdhabalia - rdhabalia >>> >>> Thanks, >>> Andrews. >>> >>> On Wed, Jun 21, 2017 at 3:08 PM, Sahaya Andrews >>> wrote: >>> >>>> I have updated my GitHub id in profile. >>>> >>>> What does the "reporeq" step meant to do? >>>> >>>>> On Wed, Jun 21, 2017 at 2:56 PM, Matteo Merli wrote: >>>>> >>>>> The repo location has now been transferred to >>>>> https://github.com/apache/incubator-pulsar >>>>> >>>>> I think the next step would be to do the "reporeq" at >>>>> https://reporeq.apache.org >>>>> And that should be done by someone in IPMC :) >>>>> I am not sure wether it was already done though. >>>>> >>>>> For all the committers: you should go to id.apache.org and enter your >>>>> github account there, so that you can link that account to the apache >>>>> account. >>>>> >>>>> Matteo >>>>> >>>>> >>>>> -- Forwarded message - >>>>> From: Daniel Takamori (JIRA) >>>>> Date: Wed, Jun 21, 2017 at 2:11 PM >>>>> Subject: [jira] [Commented] (INFRA-14376) Pulsar GitHub Integration >>>>> To: >>>>> >>>>> >>>>> Daniel Takamori >>>>> <https://issues.apache.org/jira/secure/ViewProfile.jspa?name=pono> >>>>> *commented* on [image: Github Integration] INFRA-14376 >>>>> <https://issues.apache.org/jira/browse/INFRA-14376> >>>>> >>>>> Re: Pulsar GitHub Integration >>>>> <https://issues.apache.org/jira/browse/INFRA-14376> >>>>> Imported the repo to Apache and set the hooks, now your PMC can go to >>>>> https://reporeq.apache.org to clone the Apache repo and we can move on >>>>> from there :) >>>>> >>>>> <https://issues.apache.org/jira/browse/INFRA-14376#add-comment> Add >>>>> Comment <https://issues.apache.org/jira/browse/INFRA-14376#add-comment> >>>>> >>>>> This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) >>>>> >>>> >>>> >>>
Re: [jira] [Commented] (INFRA-14376) Pulsar GitHub Integration
When can we expect the setup to be finalized? We are still waiting to get write access. Some of us who were part of the dev group in the old repo got write access automatically. But the rest who were part of admin group did not :) Andrews. On Wed, Jun 21, 2017 at 4:36 PM, Matteo Merli wrote: > Andrews, > > once the setup is finalized, all the committers will have write access if > the github account is linked to the Apache account. > > > > On Wed, Jun 21, 2017 at 3:32 PM Sahaya Andrews > wrote: > >> Hi Daniel, >> >> Could you add pulsar repo write access to the following GitHub account? >> These folks were part of admin account before moving the repo. >> *apache id - GitHub id * >> andrews - saandrews >> joef - joefk >> rdhabalia - rdhabalia >> >> Thanks, >> Andrews. >> >> On Wed, Jun 21, 2017 at 3:08 PM, Sahaya Andrews >> wrote: >> >> > I have updated my GitHub id in profile. >> > >> > What does the "reporeq" step meant to do? >> > >> > On Wed, Jun 21, 2017 at 2:56 PM, Matteo Merli wrote: >> > >> >> The repo location has now been transferred to >> >> https://github.com/apache/incubator-pulsar >> >> >> >> I think the next step would be to do the "reporeq" at >> >> https://reporeq.apache.org >> >> And that should be done by someone in IPMC :) >> >> I am not sure wether it was already done though. >> >> >> >> For all the committers: you should go to id.apache.org and enter your >> >> github account there, so that you can link that account to the apache >> >> account. >> >> >> >> Matteo >> >> >> >> >> >> -- Forwarded message - >> >> From: Daniel Takamori (JIRA) >> >> Date: Wed, Jun 21, 2017 at 2:11 PM >> >> Subject: [jira] [Commented] (INFRA-14376) Pulsar GitHub Integration >> >> To: >> >> >> >> >> >> Daniel Takamori >> >> <https://issues.apache.org/jira/secure/ViewProfile.jspa?name=pono> >> >> *commented* on [image: Github Integration] INFRA-14376 >> >> <https://issues.apache.org/jira/browse/INFRA-14376> >> >> >> >> Re: Pulsar GitHub Integration >> >> <https://issues.apache.org/jira/browse/INFRA-14376> >> >> Imported the repo to Apache and set the hooks, now your PMC can go to >> >> https://reporeq.apache.org to clone the Apache repo and we can move on >> >> from there :) >> >> >> >> <https://issues.apache.org/jira/browse/INFRA-14376#add-comment> Add >> >> Comment <https://issues.apache.org/jira/browse/INFRA-14376#add-comment> >> >> >> >> This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) >> >> >> > >> > >>
Re: [jira] [Commented] (INFRA-14376) Pulsar GitHub Integration
Andrews, once the setup is finalized, all the committers will have write access if the github account is linked to the Apache account. On Wed, Jun 21, 2017 at 3:32 PM Sahaya Andrews wrote: > Hi Daniel, > > Could you add pulsar repo write access to the following GitHub account? > These folks were part of admin account before moving the repo. > *apache id - GitHub id * > andrews - saandrews > joef - joefk > rdhabalia - rdhabalia > > Thanks, > Andrews. > > On Wed, Jun 21, 2017 at 3:08 PM, Sahaya Andrews > wrote: > > > I have updated my GitHub id in profile. > > > > What does the "reporeq" step meant to do? > > > > On Wed, Jun 21, 2017 at 2:56 PM, Matteo Merli wrote: > > > >> The repo location has now been transferred to > >> https://github.com/apache/incubator-pulsar > >> > >> I think the next step would be to do the "reporeq" at > >> https://reporeq.apache.org > >> And that should be done by someone in IPMC :) > >> I am not sure wether it was already done though. > >> > >> For all the committers: you should go to id.apache.org and enter your > >> github account there, so that you can link that account to the apache > >> account. > >> > >> Matteo > >> > >> > >> -- Forwarded message - > >> From: Daniel Takamori (JIRA) > >> Date: Wed, Jun 21, 2017 at 2:11 PM > >> Subject: [jira] [Commented] (INFRA-14376) Pulsar GitHub Integration > >> To: > >> > >> > >> Daniel Takamori > >> <https://issues.apache.org/jira/secure/ViewProfile.jspa?name=pono> > >> *commented* on [image: Github Integration] INFRA-14376 > >> <https://issues.apache.org/jira/browse/INFRA-14376> > >> > >> Re: Pulsar GitHub Integration > >> <https://issues.apache.org/jira/browse/INFRA-14376> > >> Imported the repo to Apache and set the hooks, now your PMC can go to > >> https://reporeq.apache.org to clone the Apache repo and we can move on > >> from there :) > >> > >> <https://issues.apache.org/jira/browse/INFRA-14376#add-comment> Add > >> Comment <https://issues.apache.org/jira/browse/INFRA-14376#add-comment> > >> > >> This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) > >> > > > > >
Re: [jira] [Commented] (INFRA-14376) Pulsar GitHub Integration
Hi Daniel, Could you add pulsar repo write access to the following GitHub account? These folks were part of admin account before moving the repo. *apache id - GitHub id * andrews - saandrews joef - joefk rdhabalia - rdhabalia Thanks, Andrews. On Wed, Jun 21, 2017 at 3:08 PM, Sahaya Andrews wrote: > I have updated my GitHub id in profile. > > What does the "reporeq" step meant to do? > > On Wed, Jun 21, 2017 at 2:56 PM, Matteo Merli wrote: > >> The repo location has now been transferred to >> https://github.com/apache/incubator-pulsar >> >> I think the next step would be to do the "reporeq" at >> https://reporeq.apache.org >> And that should be done by someone in IPMC :) >> I am not sure wether it was already done though. >> >> For all the committers: you should go to id.apache.org and enter your >> github account there, so that you can link that account to the apache >> account. >> >> Matteo >> >> >> ------ Forwarded message ----- >> From: Daniel Takamori (JIRA) >> Date: Wed, Jun 21, 2017 at 2:11 PM >> Subject: [jira] [Commented] (INFRA-14376) Pulsar GitHub Integration >> To: >> >> >> Daniel Takamori >> <https://issues.apache.org/jira/secure/ViewProfile.jspa?name=pono> >> *commented* on [image: Github Integration] INFRA-14376 >> <https://issues.apache.org/jira/browse/INFRA-14376> >> >> Re: Pulsar GitHub Integration >> <https://issues.apache.org/jira/browse/INFRA-14376> >> Imported the repo to Apache and set the hooks, now your PMC can go to >> https://reporeq.apache.org to clone the Apache repo and we can move on >> from there :) >> >> <https://issues.apache.org/jira/browse/INFRA-14376#add-comment> Add >> Comment <https://issues.apache.org/jira/browse/INFRA-14376#add-comment> >> >> This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) >> > >
Re: [jira] [Commented] (INFRA-14376) Pulsar GitHub Integration
I have updated my GitHub id in profile. What does the "reporeq" step meant to do? On Wed, Jun 21, 2017 at 2:56 PM, Matteo Merli wrote: > The repo location has now been transferred to > https://github.com/apache/incubator-pulsar > > I think the next step would be to do the "reporeq" at > https://reporeq.apache.org > And that should be done by someone in IPMC :) > I am not sure wether it was already done though. > > For all the committers: you should go to id.apache.org and enter your > github account there, so that you can link that account to the apache > account. > > Matteo > > > -- Forwarded message - > From: Daniel Takamori (JIRA) > Date: Wed, Jun 21, 2017 at 2:11 PM > Subject: [jira] [Commented] (INFRA-14376) Pulsar GitHub Integration > To: > > > Daniel Takamori > <https://issues.apache.org/jira/secure/ViewProfile.jspa?name=pono> > *commented* on [image: Github Integration] INFRA-14376 > <https://issues.apache.org/jira/browse/INFRA-14376> > > Re: Pulsar GitHub Integration > <https://issues.apache.org/jira/browse/INFRA-14376> > Imported the repo to Apache and set the hooks, now your PMC can go to > https://reporeq.apache.org to clone the Apache repo and we can move on > from there :) > > <https://issues.apache.org/jira/browse/INFRA-14376#add-comment> Add > Comment <https://issues.apache.org/jira/browse/INFRA-14376#add-comment> > > This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) >
Fwd: [jira] [Commented] (INFRA-14376) Pulsar GitHub Integration
The repo location has now been transferred to https://github.com/apache/incubator-pulsar I think the next step would be to do the "reporeq" at https://reporeq.apache.org And that should be done by someone in IPMC :) I am not sure wether it was already done though. For all the committers: you should go to id.apache.org and enter your github account there, so that you can link that account to the apache account. Matteo -- Forwarded message - From: Daniel Takamori (JIRA) Date: Wed, Jun 21, 2017 at 2:11 PM Subject: [jira] [Commented] (INFRA-14376) Pulsar GitHub Integration To: Daniel Takamori <https://issues.apache.org/jira/secure/ViewProfile.jspa?name=pono> *commented* on [image: Github Integration] INFRA-14376 <https://issues.apache.org/jira/browse/INFRA-14376> Re: Pulsar GitHub Integration <https://issues.apache.org/jira/browse/INFRA-14376> Imported the repo to Apache and set the hooks, now your PMC can go to https://reporeq.apache.org to clone the Apache repo and we can move on from there :) <https://issues.apache.org/jira/browse/INFRA-14376#add-comment> Add Comment <https://issues.apache.org/jira/browse/INFRA-14376#add-comment> This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
