Without a doubt getting access to the project mirrors on GitHub is a must-have. Setting up different teams on GitHub is trivial. Could have a "committers" team, and any other team deemed necessary. We can then add permissions such as ability to administer the github project to these teams.
As for sending the patch, I don't see anything wrong with accepting a patch via GitHub. I fail to see the difference between accepting a patch via e-mail on dev lists vs. doing so via GitHub. In fact, I would say that accepting the patch on GitHub is *easier* than any other approved method in Apache so far (that I've experienced). You can comment on specific lines of code in a clearer fashion, keep track of changes to the patch (if necessary) also very cleanly, in a timeline sort of fashion, where changes to the patch as well as overall comments are chronologically ordered. Very easy to see how a patch evolves. As a current committer on an incubating project that went from a GitHub-based project to an Apache project (incubator-apache-cordova), this issue resounds very strongly in me. I would love to help out in any way I can to get this figured out. Cheers, Fil Maj On 5/24/12 10:54 AM, "Greg Stein" <gst...@gmail.com> wrote: >Git people, > >The community is discussing what to do about this particular approach >for sending a patch (we have a defined and published method for >sending a patch to our community). That is a separate thread, but >pending that... I have a separate meta/infra issue for you. > >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. > >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. > >Please let us know our options for managing our GitHub presence. > >Thanks, >Greg Stein >VP, Apache Subversion > >On Thu, May 24, 2012 at 4:12 AM, Git at Apache <g...@git.apache.org> wrote: >> GitHub user techtonik opened a pull request: >> >> https://github.com/apache/subversion/pull/1 >> >> port to new style classes - >>http://stackoverflow.com/questions/54867/old... >> >> >>http://stackoverflow.com/questions/54867/old-style-and-new-style-classes- >>in-python >> >> You can merge this pull request into a Git repository by running: >> >> $ git pull https://github.com/techtonik/subversion patch-1 >> >> Alternatively you can review and apply these changes as the patch at: >> >> https://github.com/apache/subversion/pull/1.patch >> >> ---- >> commit cb3fa71cceef1060b1074299dbdbd4fcf8fd6869 >> Author: anatoly techtonik <techto...@gmail.com> >> Date: 2012-05-24T01:12:03-07:00 >> >> port to new style classes - >>http://stackoverflow.com/questions/54867/old-style-and-new-style-classes- >>in-python >> >> ---- >>
