flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Reicher <danreic...@gmail.com>
Subject Re: Commit process for new component (non-committer)
Date Wed, 07 Mar 2012 23:57:18 GMT

Thanks for the guidance. I'll give it a go and see what comes.

On Wed, Mar 7, 2012 at 3:14 PM, Justin Mclean <justin@classsoftware.com>wrote:

> Hi,
> > Maybe I'm just thick but I'm trying to understand the process for trying
> to
> > add a component to the SDK.
> I'm not sure there is an "official" process yet.
> > 1. Where does the code go?
> Anywhere you want to put it. As long you you mail the list with a link to
> it's all good.
> If you would like to have it the whiteboard area just ask a friendly
> committer to put it there for you.
> > 2. What level of discussion should be taking place? Do I kick off a new
> > thread on the list? Is it labeled [PROPOSAL] or something else - or
> nothing
> > at all?
> It needs be discussed on list yes, but up to you if you want to label the
> thread [Proposal] or not. More people will probably take notice of it if
> you label it.
> > 3. There are questions that need to be dealt with about the component
> > itself: does this belong in the SDK, is the code good enough to warrant
> > inclusion, should this be a mobile-only component, etc.?
> The on list discussion should sort all these details out.
> >  but the current process for setting up the SDK in FB leaves a lot to be
> desired
> What are you having issues with? Anyway I can help?
> > 5. Are things like this really going to be held out of the SDK until 5.0
> Up to what the community as a whole to agree on that. Personally I don't
> see why we should hold off new features but other people may have other
> views on that.
> Thanks,
> Justin

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