Hi, On Thu, May 24, 2012 at 10:54 AM, Greg Stein <gst...@gmail.com> wrote: > The Subversion PMC does not seem to have access to manage our presence > on GitHub, yet people seem to believe it is a viable approach to send > us patches. At a minimum, the PMC needs a way to manage our presence > on GitHub: the description, the readme, pull requests, etc.
We have quite a bit of control over that, though access to the github.com/apache settings is limited to just a few admins (currently me, Gavin and Tony). Do you already have specific changes that you'd like implemented? > I doubt that the PMC and community wants to shut this down, but *we* > are the ones to define our presence to the larger community. The > Subversion PMC is the group to manage pull requests, and other aspects > of our project. In short, this GitHub repository is representing > "Apache Subversion" without the PMC providing any actual oversight or > any mechanism to manage it. As mentioned by Daniel, the Git mirror was created as a response to http://markmail.org/message/gachaz3dcxukrpph. By default all git.apache.org mirrors also show up on github.com/apache, but we can change that per-project if needed. The GitHub pull request notification you saw on dev@subversion, is a result of our work to better integrate GitHub workflows with those at Apache. The idea here is to send the issue to dev@ from where the project community can deal with it in whichever way it prefers, for example by telling the contributor to use other channels, by filing a bug for the issue, or by simply directly applying the contributed patch. Currently the pull request notification doesn't come with a full diff, but we can add that if desired. > Please let us know our options for managing our GitHub presence. Just let us know what you want changed and we'll take care of it. BR, Jukka Zitting
