flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nicholas Kwiatkowski <nicho...@spoon.as>
Subject Re: [PROPOSAL] Swiz Framework Donation to Apache Flex
Date Tue, 28 May 2013 17:57:01 GMT
I would prefer JIRA activity to be on another list.  I've heard from quite
a few people in my User Group that they dropped off dev@ people of the
noise of JIRA.   I think those of us who want to know what is committed
will subscribe to those (plus, it makes filtering those messages into a
separate folder easier ;P  )

-Nick


On Tue, May 28, 2013 at 1:48 PM, Alex Harui <aharui@adobe.com> wrote:

>
>
> On 5/28/13 10:25 AM, "Greg Reddin" <gredbug@gmail.com> wrote:
>
> >On Tue, May 28, 2013 at 11:18 AM, Alex Harui <aharui@adobe.com> wrote:
> >
> >>
> >> Greg, do you think donations like these need to have a goal of being
> >> integrated with Apache Flex or becoming its own project?  Personally,
> >>I'd
> >> be ok with Apache Flex being a warehouse of all kinds of Flex-related
> >>code
> >> even if there is no active development for it.
> >
> >
> >There's a couple of things to consider here:
> >
> >1) The board does not favor "umbrella" projects. Jakarta was an umbrella
> >project and it contained (at one time) Struts, Tomcat, Commons, JMeter,
> >and
> >a whole bunch of Java-related projects. It became clear that the Jakarta
> >community was too fragmented to get consensus so it spun off all those
> >projects into TLPs. That could easily start to happen here.
> That would make sense for Jakarta, especially if there was active
> development on all of those pieces.  I'm not sure that will be the case
> here.  I think there's a good chance that these application frameworks may
> not have much activity.
>
> For me, incubation was so much work that it seems easier to take these
> code donations and see if a community forms around it and then spin it off
> than going through the whole
> proposal/initial-committers/mentors/infra-setup/graduation process.
>
> >
> >2) This mailing list is already too high-traffic to follow. Practically,
> >we
> >could probably already split up the Flex project into multiple projects.
> >It
> >seems to me that folks are starting to gel around different efforts, like
> >getting new releases of the SDK, vs. compilers, etc. It could be that we
> >need to form new PMCs or it could be that we just need to enact
> >sub-projects. But we have to be careful with sub-projects to avoid point 1
> >above.
> What are your thoughts on just having more mailing lists?  We toyed with
> the notion of having all JIRA activity on a different list.  I haven't
> looked at the stats, but Erik and I haven't done much
> Falcon/FalconJX/FlexJS work over the last two weeks and I'm not sure
> there's been less activity on the dev list.
>
> -Alex
> >
>
>

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