Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of omarg.developer@gmail.com
 designates 209.85.220.175 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CC4A0915.4442B%aharui@adobe.com>
References: <CC4A0915.4442B%aharui@adobe.com>
Date: Fri, 10 Aug 2012 00:53:08 -0700
Message-ID: 
 <CAEFz_vuvsj6pJV2pG1OOz599Mar_-qVeh7fSwbHuu3S+X0oHag@mail.gmail.com>
Subject: Re: What would it take to move to Git?
From: Omar Gonzalez <omarg.developer@gmail.com>
To: flex-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=20cf307abeed86f1a304c6e4a20a

--20cf307abeed86f1a304c6e4a20a
Content-Type: text/plain; charset=ISO-8859-1

On Fri, Aug 10, 2012 at 12:40 AM, Alex Harui <aharui@adobe.com> wrote:

> Would we be working off of github.com?
>
> Who controls who has write-access?
>
> What else do we need to worry about?
>
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>

I'm not sure how the other Apache projects are doing it, but I will take a
look.

Ideally, if we went through GitHub we would create an ApacheFlex
organization that we can add all of the committers to. Then we would be
able to administer Issues posted on GitHub, pull request, etc. We can all
then just fork the main repo and do all of our own experiments there and
Pull Request them back to the main fork. The Pull Request then serves as
the place where the community can give feedback even on committer
contributions that want to make their way into the main line.

So I would imagine the PPMC can control who has write access if we
establish the GitHub organization.

Git also has SVN commands, so we can still push to the SVN repository, like
when we do a release if we wanted to also make release tags available on
SVN they can be pushed to SVN from the Git cli.

-omar

--20cf307abeed86f1a304c6e4a20a--