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 aharui@adobe.com designates
 64.18.1.208 as permitted sender)
From: Alex Harui <aharui@adobe.com>
To: "flex-dev@incubator.apache.org" <flex-dev@incubator.apache.org>,
        "peter.elst@gmail.com" <peter.elst@gmail.com>,
        "jeffry@dot-com-it.com"
	<jeffry@dot-com-it.com>
Date: Wed, 4 Jan 2012 12:11:15 -0800
Subject: Re: Committer duties and information
Thread-Topic: Committer duties and information
Thread-Index: AczLG1W/xQSGdCjOQy2S3SBgJCqdtAAAa0mr
Message-ID: <CB29F263.39052%aharui@adobe.com>
In-Reply-To: 
 <CAF2yXurpAryBBNUPPG+eXs3nKzrtnYG4bG__ypq2C1wPLu2RjQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-Entourage/13.11.0.110726
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

I'm not sure this made the video from the summit, but Roy Fielding gave me
the impression that there are no "roadmaps" in Apache.  You work on what yo=
u
want to work on and commit it.  If people don't like it, you get voted down
and you have to pull it and adjust it until people like it.  If I were you,
before I embarked on a significant amount of code, I would start a
discussion on the mailing list first to make sure there won't be a major
unexpected issue when you try to check in, and to see if anyone else wants
to join in.

I've been flip-flopping between requesting a "review-then-commit" workflow
vs the default "commit-then-review".  Past experience has shown that there
are lots of things to consider when modifying the Flex framework that many
folks don't consider (Marshall Plan, can't assume stage access, for
example).

Because it looks like we won't get JIRA up any time soon, we might start ou=
t
with commit-then-review and I'll just have to try to keep up with reviewing
all of the commits.

And because it looks like it will be a while before we get the test suite
running, I would like to discourage commits of anything significant until w=
e
have a way to verify your changes are safe.


On 1/4/12 11:58 AM, "peter.elst@gmail.com" <peter.elst@gmail.com> wrote:

> Thats a good point I've not been clear on either - is roadmap discussed o=
n
> the mailinglist and voted on so there's a bit of structure to what type o=
f
> things get worked on rather than a random collection of bug fixes and
> non-related features?
>=20
> - Peter
>=20
>=20
> On Wed, Jan 4, 2012 at 7:17 PM, Jeffry Houser <jeffry@dot-com-it.com> wro=
te:
>=20
>>=20
>>  Be sure to watch the "What it Means to be an Apache Project" from the
>> Flex Summit, here:
>>=20
>> http://tv.adobe.com/show/flex-**community-summit-december-**2011/<http:/=
/tv.a
>> dobe.com/show/flex-community-summit-december-2011/>
>>=20
>>  My understanding is that we do whatever we want.  I don't know how that
>> goes from "chaos" to "release" yet, though.
>>=20
>>=20
>> On 1/4/2012 2:12 PM, Michael Schmalle wrote:
>>=20
>>> Hi All,
>>>=20
>>> I was just curious if there was any Apache Flex specific information
>>> floating around about how duties might be divided on each others streng=
th
>>> in relation to our understanding of the SDK.
>>>=20
>>> I know there is the official committer information page that Alex
>>> provided but has there been any discussion on how an initial committer =
can
>>> prepare for whats to be expected in the Apache Flex project?
>>>=20
>>> Or is this just to soon to ask this question?
>>>=20
>>> Thanks,
>>> Mike
>>>=20
>>>=20
>>>=20
>>=20
>> --
>> Jeffry Houser
>> Technical Entrepreneur
>> 203-379-0773
>> --
>> http://www.flextras.com?c=3D104
>> UI Flex Components: Tested! Supported! Ready!
>> --
>> http://www.theflexshow.com
>> http://www.jeffryhouser.com
>> http://www.asktheflexpert.com
>> --
>> Part of the DotComIt Brain Trust
>>=20
>>=20

--=20
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui