flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Omar Gonzalez <omarg.develo...@gmail.com>
Subject Re: Creating Working Groups [Was: Apache Flex suggestion - dumping SWF support in favor of HTML5 - listen to Steve]
Date Mon, 06 Feb 2012 19:37:19 GMT
On Mon, Feb 6, 2012 at 11:27 AM, Martin Heidegger <mh@leichtgewicht.at>wrote:

> The workflow is okay to me. I just came to the conclusion that we don't
> have a good platform here to talk about code that might not be commited
> (what is momentarily done in the whiteboard folder. I think omars
> suggestion to do this sort of community work "not here" is not a bad idea.
> The day before yesterday
> Spoon.as team said that they want to do community work (like listing the
> things that are going on). I think that Spoon.as could jump in and give
> those rants a place to feel home.
> yours
> Martin.
Its not so much that we can't have discussions about code here, this is
where we should be having those discussions. The thing is that with
something like a whiteboard where you want to develop ideas in an adhoc
manner where you are open to accept code patches/commits from anyone that
wants to including non-committers than you need a way to manage all of
that. Giving SVN access to thousands of developers is just not the way
things are done at Apache, so trying to allow for that level of
collaboration doesn't fit the model.

However, as a non-committer, this is exactly why I would turn to GitHub. On
GitHub you have the ability to include anyone as you see fit and
collaborate with as many people as you want. There are facilities for
sending and receiving patch requests, code reviews, messaging between devs,
etc, that can be easily managed by you without the overhead of having to
try to add hundreds if not thousands of SVN committers to the Apache
repository. Once you have an idea fleshed out to a point where it can be
discussed you can create Gists on GitHub or commit examples and everyone
can discuss it on the mailing list if you a.) need feedback from the entire
community, or b.) want to contribute it to the Apache Flex repository
because you've set up an idea far enough where we can bring it in to the
SDK. You would have Wikis to add as much info and documentation as you
want, collaboratively, easily as well.

What I think would make finding all of these projects would then to list
those somewhere on the Apache Flex site as maybe an ideas in progress
section or something along those lines that indicates here are a bunch of
community projects in progress that are trying to solidify themselves
enough to get included either into a committer's whiteboard or as a
donation to the SDK. If you do this enough eventually you will end up
getting voted in as a new committer and then you can work directly in your
own whiteboard.

This is just my understanding of how Apache works and what I would do if I
had not been selected as a committer from the start. As they say, just my


> On 07/02/2012 04:11, João Fernandes wrote:
>> Am I the only non-committer that finds the current Apache workflow
>> acceptable?
>> Whiteboards should only be managed by PPMC in my opinion and
>> non-committers
>> should propose patches to existing whiteboards. If there isn't any
>> whiteboard working on what they want to contribute, they should create
>> some
>> repository (github or svn) elsewhere and announce in the mailinglist to
>> see
>> if there are people interested in working in the same project.
>> I agree that eventually a list of "community whiteboards" could be listed
>> in the flex wiki page as long it doesn't become a burden to maintain.
>> João Fernandes

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