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.
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:
> port to new style classes - http://stackoverflow.com/questions/54867/old...
> 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:
> 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
Received on 2012-05-24 10:55:19 CEST