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 <[email protected]>
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 <[email protected]> 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 <[email protected]>
> > 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 <[email protected]>
> >> wrote:
> >>
> >> > Hi Andrews,
> >> >
> >> > > On Jun 22, 2017, at 3:40 PM, Sahaya Andrews <
> [email protected]>
> >> > 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 <[email protected]>
> >> > > 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 <
> >> > [email protected]>
> >> > >> 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 <
> >> > [email protected]>
> >> > >>> 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 <[email protected]
> >
> >> > 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) <[email protected]>
> >> > >>>>> Date: Wed, Jun 21, 2017 at 2:11 PM
> >> > >>>>> Subject: [jira] [Commented] (INFRA-14376) Pulsar GitHub
> >> > >>>>> Integration
> >> > >>>>> To: <[email protected]>
> >> > >>>>>
> >> > >>>>>
> >> > >>>>> 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)
> >> > >>>>>
> >> > >>>>
> >> > >>>>
> >> > >>>
> >> >
> >> >
>

Reply via email to