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 <[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 :) > > 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) >>>>> >>>> >>>> >>>
