On Thu, May 24, 2012 at 3:54 AM, Greg Stein <gstein_at_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.
> Greg Stein
> VP, Apache Subversion
> On Thu, May 24, 2012 at 4:12 AM, Git at Apache <git_at_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 <techtonik_at_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
As I see it, there are basically two main parts to this question.
First is the ability to allow PMC members (or all committers?) for a
given project to manage various parts of the GitHub repository. As far
as I'm aware the end result is a forgone conclusion and the only
sticking point is the underlying infrastructure to make it happen. My
basic goal here is to have a script that'll query ldap to get the list
of authorized people and mirror that using the "GitHub Organization
Teams" API. That should allow us to have a fairly natural mapping of
ASF privileges to GH privileges.
The second half is in monitoring interaction with the GH account from
dev@ mailing lists. Jukka has done some initial work to at least make
projects aware of their PR's but as people are starting to see they're
still a bit lacking because of things like continued discussion on the
PR. There's more to the PR API that we can use to mirror these bits of
discussion over to the dev@ list but that type of integration is only
in a single direction. Ie, it should be just a bit of work to echo all
GH discussion to the dev@ lists, but the follow up question is how we
might respond to people on GH that aren't necessarily subscribed to
dev@. That might just be a matter of including links back to GH where
people can respond, or perhaps figuring out GH's email reply system.
In the end I also think this is mostly a technical issue as the
process/meta issue is pretty clear that it all needs to go through
dev@ so its just a matter of making that happen in a way that people
agree upon (or making it configurable to make projects happy).
Received on 2012-05-25 08:41:47 CEST