incubator-flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Greg Reddin <gred...@gmail.com>
Subject Re: Committer duties and information
Date Wed, 04 Jan 2012 20:40:16 GMT
Thanks!

On Wed, Jan 4, 2012 at 2:38 PM, Jonathan Campos <jonbcampos@gmail.com> wrote:
> @Greg
>
> http://www.spoon.as/
>
> Spoon is a nonprofit corporation created by some community members to
> promote, educate, and contribute to the Flex framework. From the link you
> can see basic bits of information and specifically read the core values.
> Some of this data needs to be updated as it was written before the Flex
> Summit but I'm sure you can get more than the gist of it.
>
> HTH
>
> On Wed, Jan 4, 2012 at 2:34 PM, Alex Harui <aharui@adobe.com> wrote:
>
>> So for practical reasons, I think we're going to start with
>> commit-then-review.
>>
>> If you try to commit a new component, that commit will be reviewed and
>> vetoed out if there is a problem.
>>
>> So let's get specific.  Let's say you want to contribute your version of a
>> Spark TabNavigator component.  Adobe has almost finished its version and
>> promised to commit it.  I would recommend starting a discussion on this
>> list
>> about whether to take yours vs Adobe's.  That way you'll at least have an
>> idea whether folks are willing to review your version or want to wait for
>> Adobe.  Then if you do decide to commit, we'll take a harder look at the
>> code and maybe you'll get rejected if we find some major problem, but
>> otherwise it gets in.  And if folks want to wait for Adobe and you
>> disagree,
>> you can offer it up under a different package name.  I suppose someone
>> might
>> still try to veto that based on confusing folks about which TabNavigator to
>> use, so that might be worth discussing up front as well, but I personally
>> don't have a problems with different flavors of components.
>>
>> -Alex
>>
>>
>> On 1/4/12 12:19 PM, "Michael Schmalle" <mike@teotigraphix.com> wrote:
>>
>> > Quoting Jonathan Campos <jonbcampos@gmail.com>:
>> >
>> >> That is an exact question that I asked at the Flex Summit specifically
>> for
>> >> the group.
>> >>
>> >> Roy Fielding had a great analogy/answer.
>> >> The main idea is that this is that we are throwing a party, not running
>> a
>> >> business with free labor. So people need to be energized about what they
>> >> are doing, they aren't there to be given tasks.
>> >>
>> >> As such there is no roadmap. You may come up with a great idea and start
>> >> working on it, then when other people see what you are doing they may
>> join.
>> >> Over time your idea snowballs and gets added in, but this doesn't mean
>> that
>> >> there is a formal roadmap for people to sit at and program away against.
>> >>
>> >> However this is where Spoon comes in. We do have plans and roadmaps of
>> >> features we want to add. Some take time and require people. If you are
>> >> interested in our roadmap (our party) you and anyone else is free to
>> join.
>> >>
>> >> Make sense?
>> >>
>> >> J
>> >
>> > This actually does make sense for features.
>> >
>> > So can I ask this, am I to then just look at the bug base, say hey
>> > that looks like something I can fix, fix it then commit it?
>> >
>> > Don't jump on this to quick, I am saying there needs to be a unit
>> > test? I remember Alex saying that Apache is usually commit & review
>> > but that they were trying for a review and commit in the beginning.
>> > Has anybody else heard this?
>> >
>> > Does there have to be votes on say a new component that would be added
>> > to the SDK? I'm really just trying to understand the algorithm of
>> > develop/test/fix/commit for an initial committer.
>> >
>> > Thanks,
>> > Mike
>> >
>> >
>> >
>> >
>> >
>>
>> --
>> Alex Harui
>> Flex SDK Team
>> Adobe Systems, Inc.
>> http://blogs.adobe.com/aharui
>>
>>
>
>
> --
> Jonathan Campos
> Dallas Flex User Group Manager
> http://www.d-flex.org/
> blog: http://www.unitedmindset.com/jonbcampos
> twitter: http://www.twitter.com/jonbcampos

Mime
View raw message