flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ben Dalton <bendal...@gmail.com>
Subject Re: [MENTORS] Current Branching Strategy Vote Results
Date Wed, 15 Aug 2012 14:07:13 GMT
I agree with Omar 100%.

Git is a bit better of a SCM, but the flexibility the use of GitHub affords really lends itself
to a more engaged community.

If we want an engaged community, and the challenges we face with Apache's non-support of Git
aren't too severe, Git is the only good choice for future growth.

All that being said, there's still a ton of work to do before we can have an extremely active
community of contributors. Until we have a test suite that runs in minutes (and not hours)
with CI, it's going to be labor and time intensive to incorporate contributions.  

So if the mentors FIRMLY believe that it is a better decision to stick with SVN in the near
term, then I support that. As long as we realize that it will be a limiting factor for community
contributions and we should plan on moving to Git once we are fully prepared to handle changes
from the community. We certainly don't want to end up in the same situation as Adobe in the
Flex 2 days and become overwhelmed with patches having limited/no capacity to handle them.

Just my 2cents..

On Wednesday, August 15, 2012 at 9:46 AM, Omar Gonzalez wrote:

> On Wednesday, August 15, 2012, Bertrand Delacretaz wrote:
> > Hi,
> >  
> > On Wed, Aug 15, 2012 at 12:24 AM, Alex Harui <aharui@adobe.com (mailto:aharui@adobe.com)<javascript:;>>
> > wrote:
> > > ...We’re just past the halfway mark (and some folks who voted in the
> >  
> > poll have not yet voted)
> > > but if I culled the votes properly (see below), there is a significant
> >  
> > difference of opinion
> > > between the PPMC and the community...
> >  
> >  
> > This is about which tools the committers use (and might have to
> > partially support in case of Git, for now) so I wouldn't give much
> > weight to the community's opinion in this particular case. Those who
> > do the work decide IMO.
> >  
> It's not only the pull requests. It's the easy forking, the commenting on
> commits (directly inline with code) enabling much easier to handle
> patch/code reviews.
> It's all about how Git/GitHub promotes community and collaboration. It
> promotes it much better and handles it much smoother via pull requests and
> code reviews than submitting patches thru JIRA and having back and forth
> discussions via email which are hard to keep track of when u can comment
> directly on code in GitHub.
> -omar
> That just seems pretty messed up to not consider the community. Git enables
> a lot more collaboration, especially when used with GitHub. This is largely
> why so many developers have moved to GitHub. To dismiss this as "This is
> about which tools the committers use" is a mistake. As this tool is also
> how we interface with contributions from the community.
> > From the community point of view, one big advantage of github IMO is
> > that it makes "drive-by contributions" easier, as you don't need to
> > subscribe to anything to create a pull request - but it's totally
> > possible for Flex committers to commit the occasional pull requests
> > that come in against the existing mirrors listed at
> > http://git.apache.org/ - and if/when those become too frequent, that
> > would be the time to revisit the tooling.
> >  
> > -Bertrand  

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message