Anyome with write access to the git repo should be able to merge pull requests :)
So any committer should be able to do that On Apr 21, 2016 12:33 AM, "David Ash" <[email protected]> wrote: > That's a good question. Does anyone know the answer to that? Can any > committer merge a pull request on github, or how does that happen? We'd > like to make sure we can move quickly, so the more people capable of doing > it the better, particularly regarding the website. > On Apr 20, 2016 12:58 PM, "Sam Barrett" <[email protected]> wrote: > > > Sounds good. We can start working on the website, and then commit it and > > submit a pull request once we have the address for the website github > repo. > > But who merges the pull request on github? Will we be able to do that > once > > we're committers? > > > > On Wed, Apr 20, 2016 at 12:50 PM, David Ash <[email protected]> > wrote: > > > > > I spoke with our new developers, and they just got subscribed to the > > > mailing list, so I'm re-sending what I sent earlier. If you already > saw > > > this, please ignore: > > > > > > > > > I think first priority is getting the new team promoted to committers, > > and > > > > probably set as initial-commiters so we can utilize the private email > > > list > > > > in the future. But that can be done by the PMC I think. > > > > > > > > First up for the devs is the website in my opinion, because that will > > > help > > > > us organize better. I think we should go with the Apache CMS > solution > > > > because that will get us up and running quickly, and free us up to do > > > other > > > > tasks. If anyone disagrees about priority or direction, please chime > > in. > > > > > > > > Information for setting up a podling website is at: > > > > http://incubator.apache.org/guides/sites.html > > > > > > > > Regarding podling websites, this guide says: > > > > > > > > Regardless of which tool you use, the web site should be maintained > in > > > the > > > >> svn repository, and include the site generation tool as a binary > file. > > > This > > > >> simplifies the process of site generation and enables changes to the > > > site > > > >> to be made by any committer. The generated site should also be > checked > > > into > > > >> svn. This allows the generated site to be relocated to any part of > the > > > >> Apache site after incubation is complete. > > > > > > > > Since the site is independent of the code, it should exist high in > the > > > svn > > > >> repository, e.g. parallel to the trunk of the source tree. > > > > > > > > > > > > Previously we were going to make a github repo for the website, > commit > > > > there, and then merge that into the apache repo. Has a github repo > > been > > > > created yet? If so, what is the URL? If not, please respond quickly > > so > > > we > > > > can make one. > > > > > > > > Once we have committers, we can commit it - or an existing committer > > can > > > > commit it if they can do so quickly. > > > > > > > > Also, until we have a website, there's some important URLs for the > > > project > > > > that I guess we should just post here for now. Here's what I know, > > > please > > > > add anything I'm missing. > > > > > > > > *General* > > > > Incubator page: http://incubator.apache.org/projects/openaz.html > > > > Website: http://openaz.incubator.apache.org/ > > > > Project management: > > > > > > > > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20OPENAZ%20ORDER%20BY%20status%20DESC > > > > > > > > *Source code* > > > > Official Repo: > > > > https://git-wip-us.apache.org/repos/asf?p=incubator-openaz.git > > > > Github Repo: https://github.com/apache/incubator-openaz > > > > > > > > *Website* > > > > Official Repo: (same as source code, branching at top level?) > > > > Github Repo: ??? > > > > > > > > *Other ASF / Useful Links:* > > > > http://www.apache.org/dev/new-committers-guide.html > > > > http://incubator.apache.org/guides/sites.html > > > > http://www.apache.org/dev/cms.html > > > > > > > > > > *Mailing list subscription addresses:* > > > > > > Everyone should subscribe to the dev list and commits list by sending > an > > > > email to the following: > > > > > > > > dev-subscribe at openaz.incubator.apache.org > > > > users-subscribe at openaz.incubator.apache.org > > > > commits-subscribe at openaz.incubator.apache.org > > > > > > > > The folks on the initial committers list should also subscribe to the > > > > private list by sending an email to: > > > > private-subscribe at openaz.incubator.apache.org > > > > > > > > > > > > > > > > > > > > > > > > > Any other thoughts for moving forward? Let's keep the conversation > > > > rolling! > > > > > > > > David > > > > > > > > > >
