Mailing-List: contact dev-help@airavata.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@airavata.apache.org
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: git repo for airavata web clients
From: Suresh Marru <smarru@apache.org>
In-Reply-To: <535FD8DB.1030506@iu.edu>
Date: Tue, 29 Apr 2014 14:46:21 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <8E96A1AC-3624-4A6A-A542-A673A802CA4E@apache.org>
References: <92A5BD3F-EDD0-43A5-BBD9-9698A7E7D8B0@apache.org>
 <983D8562-A858-4F3A-A3BE-1F841673CB65@apache.org> <535FD8DB.1030506@iu.edu>
To: Airavata Dev <dev@airavata.apache.org>

Just to clarify, to commit to any repo on ASF infrastructure a =
committtership will be a pre-requisite. But as a PMC we can granularly =
control any of our repos.=20

To answer the question, I personally do not see any need to control =
access among committters. I agree this need if we are opening up to =
contributors (which I do not think is legally complaint).=20

Just FYI, subversion project allows any ASF committer to have write =
access to their repos, they believe in social trust rather then ACL=92s, =
I like this boldness it makes us feel welcome. Ofcouse, I doubt any one =
will commit without a consent on the mailing list, but thats the point. =20=


Suresh

On Apr 29, 2014, at 12:52 PM, Marlon Pierce <marpierc@iu.edu> wrote:

> Would we want to have the option to restrict committership to a =
specific
> repo?
>=20
> Marlon
>=20
> On 4/29/14 12:32 PM, Suresh Marru wrote:
>> For reference, please see what other projects are doing - =
https://git-wip-us.apache.org/repos/asf
>>=20
>> Projects like cloudstack, cordova, couchdb jclouds and others pretty =
much add a new repo for lots of components. Other projects choose to =
have one repo for everything.=20
>>=20
>> I am not yet weighing one option over other and soliciting everyone=92s=
 input.
>>=20
>> Suresh
>>=20
>> On Apr 29, 2014, at 12:27 PM, Suresh Marru <smarru@apache.org> wrote:
>>=20
>>> Hi All,
>>>=20
>>> Since the transition to git was uneventful and seems to work well, I =
want to resurrect the discussion of a code repos.
>>>=20
>>> To demonstrate Airavata we will need reference implementations of =
API. Previous web implementations are all over the place. Can we discuss =
what is the good place to consolidate these examples and indeed release =
them periodically?=20
>>>=20
>>> Two options to consider:
>>>=20
>>> * Have these web implementations as a module within main trunk and =
release them along with Airavata.
>>> * Create a separate repo and have a separate release cycle.
>>>=20
>>> Any opinions?
>>>=20
>>> Suresh
>>>=20
>=20