Return-Path: 
 <infrastructure-dev-return-1952-apmail-infrastructure-dev-archive=apache.org@apache.org>
X-Original-To: apmail-infrastructure-dev-archive@minotaur.apache.org
Delivered-To: apmail-infrastructure-dev-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 00200C5BD
	for <apmail-infrastructure-dev-archive@minotaur.apache.org>;
 Thu, 24 May 2012 11:40:38 +0000 (UTC)
Received: (qmail 75121 invoked by uid 500); 24 May 2012 11:40:37 -0000
Delivered-To: apmail-infrastructure-dev-archive@apache.org
Received: (qmail 75010 invoked by uid 500); 24 May 2012 11:40:36 -0000
Mailing-List: contact infrastructure-dev-help@apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:infrastructure-dev-help@apache.org>
List-Unsubscribe: <mailto:infrastructure-dev-unsubscribe@apache.org>
List-Post: <mailto:infrastructure-dev@apache.org>
List-Id: <infrastructure-dev.apache.org>
Reply-To: infrastructure-dev@apache.org
Delivered-To: mailing list infrastructure-dev@apache.org
Received: (qmail 74989 invoked by uid 99); 24 May 2012 11:40:36 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 24 May 2012 11:40:36 +0000
X-ASF-Spam-Status: No, hits=-0.7 required=10
	tests=RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of jukka.zitting@gmail.com
 designates 209.85.212.182 as permitted sender)
Received: from [209.85.212.182] (HELO mail-wi0-f182.google.com)
 (209.85.212.182)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 24 May 2012 11:40:32 +0000
Received: by wibhm6 with SMTP id hm6so4493342wib.5
        for <multiple recipients>; Thu, 24 May 2012 04:40:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:sender:in-reply-to:references:from:date
         :x-google-sender-auth:message-id:subject:to:cc:content-type;
        bh=GiWrJQQWDoMlVWcrAVVw1l00qNmzD81utS7WPpf0fKE=;
        b=QOdLX6ayenHlyfG0ZoSSPnDlrLMZXebnl2Lq/oyMYmQi2sfkk9mkb3302Ae755Iuur
         8+mpb2bNziIfHNsxCpNmGxRSvVPEb5fVYcDV+xqHeENACPm0ZLlg03wCKnhGTfAx0oUU
         av0TVRLChBtaiPCSKW5dh2M71dIqbP+SxuEwuJjd5y+H8mTxU+yzQmxfGvoY5N+vqXBG
         U+K05uGx/2sTkNEwgjZeSRCv9Os/ZkNjqHrkIEpqgvzWuBrwZjMq1LTp4hltK7kIVh5U
         45eoiAxRigWv+SPtGDCJTebPzz6RSgQtmW9YqgHutQiNVSPAyyHE9BTwy2LtABVyMkkB
         DVsA==
Received: by 10.216.228.224 with SMTP id f74mr3280018weq.217.1337859610560;
 Thu, 24 May 2012 04:40:10 -0700 (PDT)
MIME-Version: 1.0
Sender: jukka.zitting@gmail.com
Received: by 10.180.85.167 with HTTP; Thu, 24 May 2012 04:39:48 -0700 (PDT)
In-Reply-To: 
 <CABD8fLUQSCNHcK8ReCMfnwLvvySsc1T-DBqO1cJ66CUbQYtp5Q@mail.gmail.com>
References: <20120524081221.5B18517A2E@tyr.zones.apache.org>
 <CABD8fLUQSCNHcK8ReCMfnwLvvySsc1T-DBqO1cJ66CUbQYtp5Q@mail.gmail.com>
From: Jukka Zitting <jukka@apache.org>
Date: Thu, 24 May 2012 13:39:48 +0200
X-Google-Sender-Auth: MdTD-oIA2tUbMGOSzYolLs0IPt8
Message-ID: 
 <CAOFYJNYEzjMth8TYAVSxoFMA2rX+7MeK_2iOBNMpu5WC3eCUdg@mail.gmail.com>
Subject: Re: subversion pull request: port to new style classes -
 http://stackoverflow.c...
To: Greg Stein <gstein@gmail.com>
Cc: Git at Apache <git@git.apache.org>, infrastructure-dev@apache.org,
 davisp@apache.org,
	dev@subversion.apache.org
Content-Type: text/plain; charset=ISO-8859-1
X-Virus-Checked: Checked by ClamAV on apache.org

Hi,

On Thu, May 24, 2012 at 10:54 AM, Greg Stein <gstein@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