You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by Carlos Rovira <ca...@apache.org> on 2013/05/28 16:52:36 UTC
[PROPOSAL] Swiz Framework Donation to Apache Flex
Hi,
I want to propose the donation of Swiz Framework to Apache Flex.
https://github.com/swiz/swiz-framework/
https://swizframework.jira.com/wiki/display/SWIZ/Home
The reasons behind the propossal are:
* Swiz Framework is a mature microarquitecure for Apache Flex that
complements it to build applications with MVC, DI and other commodities
needed today to be productive. (There's other frameworks out there that
could be used along Flex like RobotLegs, Parsley, ....)
* Swiz is not updated anymore since people behind it migrated from Flex
platform to HTML5 technologies and does not want to invest more time.
* Swiz stopped development in 2.0.0 beta that brings AOP to Flex Framework.
The problem with this implementation is that is not ready for producction
since it needs changes in Flex Compiler and in AS3 Commons ByteCode to get
it work properly.
Chris Scott, the creator of swiz respond on the list some minutes ago and
he approved the Swiz Framework Donation to Apache Flex.
If people doesn't have any issues with this donation I'll go through the
steps that, will require for actual production version. Taking into account
that * Swiz Framework already has Apache License 2.0, the steps to get
donation done should be only:
* Get Chris Scott email accepting the donation of the swiz source code and
wiki content.
* I'll request a "flex-swiz-framework" git repo where we can migrate the
source code.
In a second round, Chris will want to donate 2.0.0 Beta and we can disscuss
changes to Flex compiler and talk with as3commons to know enhancements to
bytecode project and see if it's viable or not.
Let me know what do you think about it and If I need to take into account
something else.
Thanks.
Carlos Rovira
Re: [PROPOSAL] Swiz Framework Donation to Apache Flex
Posted by Carlos Velasco <ca...@gmail.com>.
Top level application flex frameworks should be incubated at Apache as
independent projects to Apache FLEX to avoid missunderstandings and be
politically correct.
2013/5/28 Avi Kessner <ak...@gmail.com>
> I don't use swiz but it seems silly to reject a donation because of a fear
> of what might happen. It's easy enough to keep it separate, and if it's
> not supported anywhere projects using it will likely ditch the flex
> framework completely
> On 28 May 2013 18:49, "Carlos Velasco" <ca...@gmail.com>
> wrote:
>
> > Adding a top level applicaction framework to the APACHE FLEX project
> > suitcase will somehow set is as the "facto standard" accepted framework
> to
> > build applications using the FLEX SDK, or at least will create that
> > understanding between developers.
> >
> > So I think top level application frameworks must not be hosted by the
> > Apache FLEX letting each developer to choose the framework that best
> suits
> > his necessities at every moment. It is a matter of hosting none or
> hosting
> > all to avoid discrimination...
> >
> >
> >
> >
> > 2013/5/28 Carlos Rovira <ca...@codeoscopic.com>
> >
> > > Hi Greg,
> > >
> > > other people behind the project are Ben and Brian (maybe more other
> > > contributions), but all files are behind Apache License 2.0 and seems
> > > there's no authors specifications so maybe they already agreed with the
> > > Apache License 2.0, but I'll ask them on the swiz list to get it clear
> > >
> > > 2013/5/28 Greg Reddin <gr...@gmail.com>
> > >
> > > > On Tue, May 28, 2013 at 9:52 AM, Carlos Rovira <
> > carlosrovira@apache.org
> > > > >wrote:
> > > >
> > > > > Hi,
> > > > >
> > > > > I want to propose the donation of Swiz Framework to Apache Flex.
> > > > >
> > > >
> > > > This would be awesome in my opinion :-) Just remember that the
> > donation
> > > > process could get complicated if Chris doesn't hold the copyright to
> > all
> > > > the code to be donated.
> > > >
> > > > Greg
> > > >
> > >
> > >
> > >
> > > --
> > > Carlos Rovira
> > > Director de Tecnología
> > > M: +34 607 22 60 05
> > > F: +34 912 94 80 80
> > > http://www.codeoscopic.com
> > > http://www.directwriter.es
> > > http://www.avant2.es
> > >
> >
>
Re: [PROPOSAL] Swiz Framework Donation to Apache Flex
Posted by Avi Kessner <ak...@gmail.com>.
I don't use swiz but it seems silly to reject a donation because of a fear
of what might happen. It's easy enough to keep it separate, and if it's
not supported anywhere projects using it will likely ditch the flex
framework completely
On 28 May 2013 18:49, "Carlos Velasco" <ca...@gmail.com>
wrote:
> Adding a top level applicaction framework to the APACHE FLEX project
> suitcase will somehow set is as the "facto standard" accepted framework to
> build applications using the FLEX SDK, or at least will create that
> understanding between developers.
>
> So I think top level application frameworks must not be hosted by the
> Apache FLEX letting each developer to choose the framework that best suits
> his necessities at every moment. It is a matter of hosting none or hosting
> all to avoid discrimination...
>
>
>
>
> 2013/5/28 Carlos Rovira <ca...@codeoscopic.com>
>
> > Hi Greg,
> >
> > other people behind the project are Ben and Brian (maybe more other
> > contributions), but all files are behind Apache License 2.0 and seems
> > there's no authors specifications so maybe they already agreed with the
> > Apache License 2.0, but I'll ask them on the swiz list to get it clear
> >
> > 2013/5/28 Greg Reddin <gr...@gmail.com>
> >
> > > On Tue, May 28, 2013 at 9:52 AM, Carlos Rovira <
> carlosrovira@apache.org
> > > >wrote:
> > >
> > > > Hi,
> > > >
> > > > I want to propose the donation of Swiz Framework to Apache Flex.
> > > >
> > >
> > > This would be awesome in my opinion :-) Just remember that the
> donation
> > > process could get complicated if Chris doesn't hold the copyright to
> all
> > > the code to be donated.
> > >
> > > Greg
> > >
> >
> >
> >
> > --
> > Carlos Rovira
> > Director de Tecnología
> > M: +34 607 22 60 05
> > F: +34 912 94 80 80
> > http://www.codeoscopic.com
> > http://www.directwriter.es
> > http://www.avant2.es
> >
>
Re: [PROPOSAL] Swiz Framework Donation to Apache Flex
Posted by Carlos Velasco <ca...@gmail.com>.
Adding a top level applicaction framework to the APACHE FLEX project
suitcase will somehow set is as the "facto standard" accepted framework to
build applications using the FLEX SDK, or at least will create that
understanding between developers.
So I think top level application frameworks must not be hosted by the
Apache FLEX letting each developer to choose the framework that best suits
his necessities at every moment. It is a matter of hosting none or hosting
all to avoid discrimination...
2013/5/28 Carlos Rovira <ca...@codeoscopic.com>
> Hi Greg,
>
> other people behind the project are Ben and Brian (maybe more other
> contributions), but all files are behind Apache License 2.0 and seems
> there's no authors specifications so maybe they already agreed with the
> Apache License 2.0, but I'll ask them on the swiz list to get it clear
>
> 2013/5/28 Greg Reddin <gr...@gmail.com>
>
> > On Tue, May 28, 2013 at 9:52 AM, Carlos Rovira <carlosrovira@apache.org
> > >wrote:
> >
> > > Hi,
> > >
> > > I want to propose the donation of Swiz Framework to Apache Flex.
> > >
> >
> > This would be awesome in my opinion :-) Just remember that the donation
> > process could get complicated if Chris doesn't hold the copyright to all
> > the code to be donated.
> >
> > Greg
> >
>
>
>
> --
> Carlos Rovira
> Director de Tecnología
> M: +34 607 22 60 05
> F: +34 912 94 80 80
> http://www.codeoscopic.com
> http://www.directwriter.es
> http://www.avant2.es
>
Re: [PROPOSAL] Swiz Framework Donation to Apache Flex
Posted by Carlos Rovira <ca...@codeoscopic.com>.
Hi Greg,
other people behind the project are Ben and Brian (maybe more other
contributions), but all files are behind Apache License 2.0 and seems
there's no authors specifications so maybe they already agreed with the
Apache License 2.0, but I'll ask them on the swiz list to get it clear
2013/5/28 Greg Reddin <gr...@gmail.com>
> On Tue, May 28, 2013 at 9:52 AM, Carlos Rovira <carlosrovira@apache.org
> >wrote:
>
> > Hi,
> >
> > I want to propose the donation of Swiz Framework to Apache Flex.
> >
>
> This would be awesome in my opinion :-) Just remember that the donation
> process could get complicated if Chris doesn't hold the copyright to all
> the code to be donated.
>
> Greg
>
--
Carlos Rovira
Director de Tecnología
M: +34 607 22 60 05
F: +34 912 94 80 80
http://www.codeoscopic.com
http://www.directwriter.es
http://www.avant2.es
Re: [PROPOSAL] Swiz Framework Donation to Apache Flex
Posted by Greg Reddin <gr...@gmail.com>.
On Tue, May 28, 2013 at 9:52 AM, Carlos Rovira <ca...@apache.org>wrote:
> Hi,
>
> I want to propose the donation of Swiz Framework to Apache Flex.
>
This would be awesome in my opinion :-) Just remember that the donation
process could get complicated if Chris doesn't hold the copyright to all
the code to be donated.
Greg
Re: [PROPOSAL] Swiz Framework Donation to Apache Flex
Posted by Roland Zwaga <ro...@stackandheap.com>.
> * Swiz stopped development in 2.0.0 beta that brings AOP to Flex Framework.
> The problem with this implementation is that is not ready for producction
> since it needs changes in Flex Compiler and in AS3 Commons ByteCode to get
> it work properly.
>
>
Hi there,
I'm the author of as3commons-bytecode. The only hurdle that a runtime AOP
implementation faced
was the fact that the entire SWF needs to be parsed in order to gather
enough information to
generate the proxies. This was pretty much as optimzied as possible, but
could still take a second
or two/three when parsing really large SWF's (blocking the UI for that
moment).
Since Falcon is now in the hands of the community, I suggest that folks
start looking into implementing
compile-time weaving, this is probably a more realistic avenue than the
runtime proxy approach.
just my .02 cents,
cheers,
Roland
Re: [PROPOSAL] Swiz Framework Donation to Apache Flex
Posted by Jeffry Houser <je...@dot-com-it.com>.
On 5/28/2013 11:33 AM, dude wrote:
> Good luck, but I'd rather see Parsley integrated into Apache Flex.
I would not like to see either integrated into Apache Flex.
However, I have no qualms about it being donated and co-existing along
side Apache Flex.
--
Jeffry Houser
Technical Entrepreneur
203-379-0773
--
http://www.flextras.com?c=104
UI Flex Components: Tested! Supported! Ready!
--
http://www.theflexshow.com
http://www.jeffryhouser.com
http://www.asktheflexpert.com
--
Part of the DotComIt Brain Trust
Re: [PROPOSAL] Swiz Framework Donation to Apache Flex
Posted by Greg Reddin <gr...@gmail.com>.
On Tue, May 28, 2013 at 10:33 AM, dude <du...@atheist.com> wrote:
> Good luck, but I'd rather see Parsley integrated into Apache Flex.
>
That's the only concern I'd have about the donation. I know Swiz is one
framework among several. So we'd have to manage it carefully to keep from
alienating part of the community.
Greg
Re: [PROPOSAL] Swiz Framework Donation to Apache Flex
Posted by Erik de Bruin <er...@ixsoftware.nl>.
+1 on the JIRA on another list, do we need a vote on that, or can we
just ask INFRA for it?
Maybe this discussion should be in a separate thread, however...
EdB
On Tue, May 28, 2013 at 7:57 PM, Nicholas Kwiatkowski <ni...@spoon.as> wrote:
> 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 <ah...@adobe.com> wrote:
>
>>
>>
>> On 5/28/13 10:25 AM, "Greg Reddin" <gr...@gmail.com> wrote:
>>
>> >On Tue, May 28, 2013 at 11:18 AM, Alex Harui <ah...@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
>> >
>>
>>
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
Re: [PROPOSAL] Swiz Framework Donation to Apache Flex
Posted by Nicholas Kwiatkowski <ni...@spoon.as>.
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 <ah...@adobe.com> wrote:
>
>
> On 5/28/13 10:25 AM, "Greg Reddin" <gr...@gmail.com> wrote:
>
> >On Tue, May 28, 2013 at 11:18 AM, Alex Harui <ah...@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
> >
>
>
Re: [VOTE] Swiz Framework Donation to Apache Flex
Posted by Erik de Bruin <er...@ixsoftware.nl>.
+1 (binding)
EdB
On Wed, May 29, 2013 at 11:43 AM, Carlos Rovira <ca...@apache.org> wrote:
> After proposal thread (http://markmail.org/message/jtedmmx5djqen52l),comes
> the vote thread.
>
> This thread is to decide if we finally adopt Swiz Framework under Apache
> Flex, since there is multiple opinions in the Apache Flex community.
>
> points to take into account:
>
> * Swiz is a great addition to Apache Flex since it complements de SDK with
> a microarquitecture for application MVC, IOC, DI very simple and well
> designed.
> * This will be a project like flexunit or utilities. So it's optional a NOT
> part of the main sdk.
> * Swiz is already in 1.4.0 stable version, under Apache License 2.0, has
> its community and right now there's no maintenance or upgrade since people
> behind the project is no longer working with Flex technology.
> * Donation will be 1.4.0 source code and wiki content.
> * Future plans: if donation is successful, Chris Scott (creator of Swiz)
> will want to donate experimental 2.0.0 branch that brings AOP support, a
> feature that could bring a great benefit to Apache Flex since it brings
> something very new to client web technologies and that will require
> evolution at compiler level (introducing compile time weaving).
>
> Points that some people argument to not accept the donation:
> * There is other frameworks like Swiz out there in the same situation and
> this donation could make Swiz the preferred/recommended IOC framework of
> use.
>
> Points to take into account:
> * Erik de bruin stated that maybe the problem is "what to do with it" under
> Apache Flex umbrella.
>
>
> Please make your vote.
>
> Thanks
>
> Carlos Rovira
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
RE: [VOTE] Swiz Framework Donation to Apache Flex
Posted by Kessler CTR Mark J <ma...@usmc.mil>.
+1 Only if it's in a separate repo from the SDK and has different email prefixes(like we have asjs/utilities n such).
Would be nice if it was clear that we are hosting it, but not solely endorsing.
-Mark
-----Original Message-----
From: carlos.rovira@gmail.com [mailto:carlos.rovira@gmail.com] On Behalf Of Carlos Rovira
Sent: Wednesday, May 29, 2013 5:43 AM
To: dev@flex.apache.org
Subject: [VOTE] Swiz Framework Donation to Apache Flex
After proposal thread (http://markmail.org/message/jtedmmx5djqen52l),comes
the vote thread.
This thread is to decide if we finally adopt Swiz Framework under Apache
Flex, since there is multiple opinions in the Apache Flex community.
points to take into account:
* Swiz is a great addition to Apache Flex since it complements de SDK with
a microarquitecture for application MVC, IOC, DI very simple and well
designed.
* This will be a project like flexunit or utilities. So it's optional a NOT
part of the main sdk.
* Swiz is already in 1.4.0 stable version, under Apache License 2.0, has
its community and right now there's no maintenance or upgrade since people
behind the project is no longer working with Flex technology.
* Donation will be 1.4.0 source code and wiki content.
* Future plans: if donation is successful, Chris Scott (creator of Swiz)
will want to donate experimental 2.0.0 branch that brings AOP support, a
feature that could bring a great benefit to Apache Flex since it brings
something very new to client web technologies and that will require
evolution at compiler level (introducing compile time weaving).
Points that some people argument to not accept the donation:
* There is other frameworks like Swiz out there in the same situation and
this donation could make Swiz the preferred/recommended IOC framework of
use.
Points to take into account:
* Erik de bruin stated that maybe the problem is "what to do with it" under
Apache Flex umbrella.
Please make your vote.
Thanks
Carlos Rovira
Re: [VOTE] Swiz Framework Donation to Apache Flex
Posted by João Fernandes <jo...@gmail.com>.
+1 Non Binding
I think Swiz is a great framework and see fit as a "utility library" of the
flex SDK which would be totally optional. Swiz is as good as Parsley, Mate,
RobotLegs or any other advanced lib out there but does aren't proposing to
be donated, it doesn't mean they couldn't be donated too.
By making swiz (or any other framework) as a subset can bring more
awareness of it's existence and eventually having people working and
enhancing it. Clearly Swiz as is, isn't going evolve since their creators
have abandoned the project but I know some people have enhanced or fixed a
few bugs (like Carlos did) so I see that hosting it as a subset of the SDK
(again, optional lib), could revive the lib and it's development.
On 29 May 2013 15:04, Carlos Velasco <ca...@gmail.com>wrote:
> Yes, I do not find polite integrating swiz as part of Apache FLEX, but I
> agree that some of its capabilities could be studied to upgrade the SDK as
> generic libraries.
>
>
> 2013/5/29 Erik de Bruin <er...@ixsoftware.nl>
>
> > > -1 Agree with Ben Dalton
> >
> > But you vote the other way?
> >
> > EdB
> >
> >
> >
> > > 2013/5/29 Jose Barragan <jo...@codeoscopic.com>
> > >
> > >> +1
> > >>
> > >> --
> > >> Jose Barragan
> > >> Chief Software Architect
> > >> Codeoscopic Madrid
> > >> C/. Infanta Mercedes, 92.
> > >> Planta 5. 505.
> > >> 28020 Madrid.
> > >> Tel.: +34 912 94 80 80
> > >>
> > >> On May 29, 2013, at 3:05 PM, Jeffry Houser <je...@dot-com-it.com>
> > wrote:
> > >>
> > >> >
> > >> > 0 [Binding]
> > >> >
> > >> > On 5/29/2013 5:43 AM, Carlos Rovira wrote:
> > >> >> After proposal thread (
> http://markmail.org/message/jtedmmx5djqen52l
> > >> ),comes
> > >> >> the vote thread.
> > >> >>
> > >> >> This thread is to decide if we finally adopt Swiz Framework under
> > Apache
> > >> >> Flex, since there is multiple opinions in the Apache Flex
> community.
> > >> >>
> > >> >> points to take into account:
> > >> >>
> > >> >> * Swiz is a great addition to Apache Flex since it complements de
> SDK
> > >> with
> > >> >> a microarquitecture for application MVC, IOC, DI very simple and
> well
> > >> >> designed.
> > >> >> * This will be a project like flexunit or utilities. So it's
> > optional a
> > >> NOT
> > >> >> part of the main sdk.
> > >> >> * Swiz is already in 1.4.0 stable version, under Apache License
> 2.0,
> > has
> > >> >> its community and right now there's no maintenance or upgrade since
> > >> people
> > >> >> behind the project is no longer working with Flex technology.
> > >> >> * Donation will be 1.4.0 source code and wiki content.
> > >> >> * Future plans: if donation is successful, Chris Scott (creator of
> > Swiz)
> > >> >> will want to donate experimental 2.0.0 branch that brings AOP
> > support, a
> > >> >> feature that could bring a great benefit to Apache Flex since it
> > brings
> > >> >> something very new to client web technologies and that will require
> > >> >> evolution at compiler level (introducing compile time weaving).
> > >> >>
> > >> >> Points that some people argument to not accept the donation:
> > >> >> * There is other frameworks like Swiz out there in the same
> situation
> > >> and
> > >> >> this donation could make Swiz the preferred/recommended IOC
> > framework of
> > >> >> use.
> > >> >>
> > >> >> Points to take into account:
> > >> >> * Erik de bruin stated that maybe the problem is "what to do with
> it"
> > >> under
> > >> >> Apache Flex umbrella.
> > >> >>
> > >> >>
> > >> >> Please make your vote.
> > >> >>
> > >> >> Thanks
> > >> >>
> > >> >> Carlos Rovira
> > >> >>
> > >> >
> > >> >
> > >> > --
> > >> > Jeffry Houser
> > >> > Technical Entrepreneur
> > >> > 203-379-0773
> > >> > --
> > >> > http://www.flextras.com?c=104
> > >> > UI Flex Components: Tested! Supported! Ready!
> > >> > --
> > >> > http://www.theflexshow.com
> > >> > http://www.jeffryhouser.com
> > >> > http://www.asktheflexpert.com
> > >> > --
> > >> > Part of the DotComIt Brain Trust
> > >> >
> > >>
> > >>
> >
> >
> >
> > --
> > Ix Multimedia Software
> >
> > Jan Luykenstraat 27
> > 3521 VB Utrecht
> >
> > T. 06-51952295
> > I. www.ixsoftware.nl
> >
>
--
João Fernandes
Re: [VOTE] Swiz Framework Donation to Apache Flex
Posted by Carlos Velasco <ca...@gmail.com>.
Yes, I do not find polite integrating swiz as part of Apache FLEX, but I
agree that some of its capabilities could be studied to upgrade the SDK as
generic libraries.
2013/5/29 Erik de Bruin <er...@ixsoftware.nl>
> > -1 Agree with Ben Dalton
>
> But you vote the other way?
>
> EdB
>
>
>
> > 2013/5/29 Jose Barragan <jo...@codeoscopic.com>
> >
> >> +1
> >>
> >> --
> >> Jose Barragan
> >> Chief Software Architect
> >> Codeoscopic Madrid
> >> C/. Infanta Mercedes, 92.
> >> Planta 5. 505.
> >> 28020 Madrid.
> >> Tel.: +34 912 94 80 80
> >>
> >> On May 29, 2013, at 3:05 PM, Jeffry Houser <je...@dot-com-it.com>
> wrote:
> >>
> >> >
> >> > 0 [Binding]
> >> >
> >> > On 5/29/2013 5:43 AM, Carlos Rovira wrote:
> >> >> After proposal thread (http://markmail.org/message/jtedmmx5djqen52l
> >> ),comes
> >> >> the vote thread.
> >> >>
> >> >> This thread is to decide if we finally adopt Swiz Framework under
> Apache
> >> >> Flex, since there is multiple opinions in the Apache Flex community.
> >> >>
> >> >> points to take into account:
> >> >>
> >> >> * Swiz is a great addition to Apache Flex since it complements de SDK
> >> with
> >> >> a microarquitecture for application MVC, IOC, DI very simple and well
> >> >> designed.
> >> >> * This will be a project like flexunit or utilities. So it's
> optional a
> >> NOT
> >> >> part of the main sdk.
> >> >> * Swiz is already in 1.4.0 stable version, under Apache License 2.0,
> has
> >> >> its community and right now there's no maintenance or upgrade since
> >> people
> >> >> behind the project is no longer working with Flex technology.
> >> >> * Donation will be 1.4.0 source code and wiki content.
> >> >> * Future plans: if donation is successful, Chris Scott (creator of
> Swiz)
> >> >> will want to donate experimental 2.0.0 branch that brings AOP
> support, a
> >> >> feature that could bring a great benefit to Apache Flex since it
> brings
> >> >> something very new to client web technologies and that will require
> >> >> evolution at compiler level (introducing compile time weaving).
> >> >>
> >> >> Points that some people argument to not accept the donation:
> >> >> * There is other frameworks like Swiz out there in the same situation
> >> and
> >> >> this donation could make Swiz the preferred/recommended IOC
> framework of
> >> >> use.
> >> >>
> >> >> Points to take into account:
> >> >> * Erik de bruin stated that maybe the problem is "what to do with it"
> >> under
> >> >> Apache Flex umbrella.
> >> >>
> >> >>
> >> >> Please make your vote.
> >> >>
> >> >> Thanks
> >> >>
> >> >> Carlos Rovira
> >> >>
> >> >
> >> >
> >> > --
> >> > Jeffry Houser
> >> > Technical Entrepreneur
> >> > 203-379-0773
> >> > --
> >> > http://www.flextras.com?c=104
> >> > UI Flex Components: Tested! Supported! Ready!
> >> > --
> >> > http://www.theflexshow.com
> >> > http://www.jeffryhouser.com
> >> > http://www.asktheflexpert.com
> >> > --
> >> > Part of the DotComIt Brain Trust
> >> >
> >>
> >>
>
>
>
> --
> Ix Multimedia Software
>
> Jan Luykenstraat 27
> 3521 VB Utrecht
>
> T. 06-51952295
> I. www.ixsoftware.nl
>
Re: [VOTE] Swiz Framework Donation to Apache Flex
Posted by Erik de Bruin <er...@ixsoftware.nl>.
> -1 Agree with Ben Dalton
But you vote the other way?
EdB
> 2013/5/29 Jose Barragan <jo...@codeoscopic.com>
>
>> +1
>>
>> --
>> Jose Barragan
>> Chief Software Architect
>> Codeoscopic Madrid
>> C/. Infanta Mercedes, 92.
>> Planta 5. 505.
>> 28020 Madrid.
>> Tel.: +34 912 94 80 80
>>
>> On May 29, 2013, at 3:05 PM, Jeffry Houser <je...@dot-com-it.com> wrote:
>>
>> >
>> > 0 [Binding]
>> >
>> > On 5/29/2013 5:43 AM, Carlos Rovira wrote:
>> >> After proposal thread (http://markmail.org/message/jtedmmx5djqen52l
>> ),comes
>> >> the vote thread.
>> >>
>> >> This thread is to decide if we finally adopt Swiz Framework under Apache
>> >> Flex, since there is multiple opinions in the Apache Flex community.
>> >>
>> >> points to take into account:
>> >>
>> >> * Swiz is a great addition to Apache Flex since it complements de SDK
>> with
>> >> a microarquitecture for application MVC, IOC, DI very simple and well
>> >> designed.
>> >> * This will be a project like flexunit or utilities. So it's optional a
>> NOT
>> >> part of the main sdk.
>> >> * Swiz is already in 1.4.0 stable version, under Apache License 2.0, has
>> >> its community and right now there's no maintenance or upgrade since
>> people
>> >> behind the project is no longer working with Flex technology.
>> >> * Donation will be 1.4.0 source code and wiki content.
>> >> * Future plans: if donation is successful, Chris Scott (creator of Swiz)
>> >> will want to donate experimental 2.0.0 branch that brings AOP support, a
>> >> feature that could bring a great benefit to Apache Flex since it brings
>> >> something very new to client web technologies and that will require
>> >> evolution at compiler level (introducing compile time weaving).
>> >>
>> >> Points that some people argument to not accept the donation:
>> >> * There is other frameworks like Swiz out there in the same situation
>> and
>> >> this donation could make Swiz the preferred/recommended IOC framework of
>> >> use.
>> >>
>> >> Points to take into account:
>> >> * Erik de bruin stated that maybe the problem is "what to do with it"
>> under
>> >> Apache Flex umbrella.
>> >>
>> >>
>> >> Please make your vote.
>> >>
>> >> Thanks
>> >>
>> >> Carlos Rovira
>> >>
>> >
>> >
>> > --
>> > Jeffry Houser
>> > Technical Entrepreneur
>> > 203-379-0773
>> > --
>> > http://www.flextras.com?c=104
>> > UI Flex Components: Tested! Supported! Ready!
>> > --
>> > http://www.theflexshow.com
>> > http://www.jeffryhouser.com
>> > http://www.asktheflexpert.com
>> > --
>> > Part of the DotComIt Brain Trust
>> >
>>
>>
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
Re: [VOTE] Swiz Framework Donation to Apache Flex
Posted by Carlos Velasco <ca...@gmail.com>.
-1 Agree with Ben Dalton
2013/5/29 Jose Barragan <jo...@codeoscopic.com>
> +1
>
> --
> Jose Barragan
> Chief Software Architect
> Codeoscopic Madrid
> C/. Infanta Mercedes, 92.
> Planta 5. 505.
> 28020 Madrid.
> Tel.: +34 912 94 80 80
>
> On May 29, 2013, at 3:05 PM, Jeffry Houser <je...@dot-com-it.com> wrote:
>
> >
> > 0 [Binding]
> >
> > On 5/29/2013 5:43 AM, Carlos Rovira wrote:
> >> After proposal thread (http://markmail.org/message/jtedmmx5djqen52l
> ),comes
> >> the vote thread.
> >>
> >> This thread is to decide if we finally adopt Swiz Framework under Apache
> >> Flex, since there is multiple opinions in the Apache Flex community.
> >>
> >> points to take into account:
> >>
> >> * Swiz is a great addition to Apache Flex since it complements de SDK
> with
> >> a microarquitecture for application MVC, IOC, DI very simple and well
> >> designed.
> >> * This will be a project like flexunit or utilities. So it's optional a
> NOT
> >> part of the main sdk.
> >> * Swiz is already in 1.4.0 stable version, under Apache License 2.0, has
> >> its community and right now there's no maintenance or upgrade since
> people
> >> behind the project is no longer working with Flex technology.
> >> * Donation will be 1.4.0 source code and wiki content.
> >> * Future plans: if donation is successful, Chris Scott (creator of Swiz)
> >> will want to donate experimental 2.0.0 branch that brings AOP support, a
> >> feature that could bring a great benefit to Apache Flex since it brings
> >> something very new to client web technologies and that will require
> >> evolution at compiler level (introducing compile time weaving).
> >>
> >> Points that some people argument to not accept the donation:
> >> * There is other frameworks like Swiz out there in the same situation
> and
> >> this donation could make Swiz the preferred/recommended IOC framework of
> >> use.
> >>
> >> Points to take into account:
> >> * Erik de bruin stated that maybe the problem is "what to do with it"
> under
> >> Apache Flex umbrella.
> >>
> >>
> >> Please make your vote.
> >>
> >> Thanks
> >>
> >> Carlos Rovira
> >>
> >
> >
> > --
> > Jeffry Houser
> > Technical Entrepreneur
> > 203-379-0773
> > --
> > http://www.flextras.com?c=104
> > UI Flex Components: Tested! Supported! Ready!
> > --
> > http://www.theflexshow.com
> > http://www.jeffryhouser.com
> > http://www.asktheflexpert.com
> > --
> > Part of the DotComIt Brain Trust
> >
>
>
Re: [VOTE] Swiz Framework Donation to Apache Flex
Posted by Jose Barragan <jo...@codeoscopic.com>.
+1
--
Jose Barragan
Chief Software Architect
Codeoscopic Madrid
C/. Infanta Mercedes, 92.
Planta 5. 505.
28020 Madrid.
Tel.: +34 912 94 80 80
On May 29, 2013, at 3:05 PM, Jeffry Houser <je...@dot-com-it.com> wrote:
>
> 0 [Binding]
>
> On 5/29/2013 5:43 AM, Carlos Rovira wrote:
>> After proposal thread (http://markmail.org/message/jtedmmx5djqen52l),comes
>> the vote thread.
>>
>> This thread is to decide if we finally adopt Swiz Framework under Apache
>> Flex, since there is multiple opinions in the Apache Flex community.
>>
>> points to take into account:
>>
>> * Swiz is a great addition to Apache Flex since it complements de SDK with
>> a microarquitecture for application MVC, IOC, DI very simple and well
>> designed.
>> * This will be a project like flexunit or utilities. So it's optional a NOT
>> part of the main sdk.
>> * Swiz is already in 1.4.0 stable version, under Apache License 2.0, has
>> its community and right now there's no maintenance or upgrade since people
>> behind the project is no longer working with Flex technology.
>> * Donation will be 1.4.0 source code and wiki content.
>> * Future plans: if donation is successful, Chris Scott (creator of Swiz)
>> will want to donate experimental 2.0.0 branch that brings AOP support, a
>> feature that could bring a great benefit to Apache Flex since it brings
>> something very new to client web technologies and that will require
>> evolution at compiler level (introducing compile time weaving).
>>
>> Points that some people argument to not accept the donation:
>> * There is other frameworks like Swiz out there in the same situation and
>> this donation could make Swiz the preferred/recommended IOC framework of
>> use.
>>
>> Points to take into account:
>> * Erik de bruin stated that maybe the problem is "what to do with it" under
>> Apache Flex umbrella.
>>
>>
>> Please make your vote.
>>
>> Thanks
>>
>> Carlos Rovira
>>
>
>
> --
> Jeffry Houser
> Technical Entrepreneur
> 203-379-0773
> --
> http://www.flextras.com?c=104
> UI Flex Components: Tested! Supported! Ready!
> --
> http://www.theflexshow.com
> http://www.jeffryhouser.com
> http://www.asktheflexpert.com
> --
> Part of the DotComIt Brain Trust
>
Re: [VOTE] Swiz Framework Donation to Apache Flex
Posted by Jeffry Houser <je...@dot-com-it.com>.
0 [Binding]
On 5/29/2013 5:43 AM, Carlos Rovira wrote:
> After proposal thread (http://markmail.org/message/jtedmmx5djqen52l),comes
> the vote thread.
>
> This thread is to decide if we finally adopt Swiz Framework under Apache
> Flex, since there is multiple opinions in the Apache Flex community.
>
> points to take into account:
>
> * Swiz is a great addition to Apache Flex since it complements de SDK with
> a microarquitecture for application MVC, IOC, DI very simple and well
> designed.
> * This will be a project like flexunit or utilities. So it's optional a NOT
> part of the main sdk.
> * Swiz is already in 1.4.0 stable version, under Apache License 2.0, has
> its community and right now there's no maintenance or upgrade since people
> behind the project is no longer working with Flex technology.
> * Donation will be 1.4.0 source code and wiki content.
> * Future plans: if donation is successful, Chris Scott (creator of Swiz)
> will want to donate experimental 2.0.0 branch that brings AOP support, a
> feature that could bring a great benefit to Apache Flex since it brings
> something very new to client web technologies and that will require
> evolution at compiler level (introducing compile time weaving).
>
> Points that some people argument to not accept the donation:
> * There is other frameworks like Swiz out there in the same situation and
> this donation could make Swiz the preferred/recommended IOC framework of
> use.
>
> Points to take into account:
> * Erik de bruin stated that maybe the problem is "what to do with it" under
> Apache Flex umbrella.
>
>
> Please make your vote.
>
> Thanks
>
> Carlos Rovira
>
--
Jeffry Houser
Technical Entrepreneur
203-379-0773
--
http://www.flextras.com?c=104
UI Flex Components: Tested! Supported! Ready!
--
http://www.theflexshow.com
http://www.jeffryhouser.com
http://www.asktheflexpert.com
--
Part of the DotComIt Brain Trust
Re: [VOTE] Swiz Framework Donation to Apache Flex
Posted by Ben Dalton <be...@gmail.com>.
+1 non binding
While I don't wish for flex to integrate another meta framework for
application development, I WOULD like to see come of the components of Swiz
integrated as language features. Dependency injection is a powerful tool
that is a central part of most other frameworks in this space (web
application development). Well implemented AOP supported as a language
feature could also be a game changer and a reason why someone would adopt
the new Flex over other technologies.
On Wed, May 29, 2013 at 8:42 AM, Igor Costa <ig...@gmail.com> wrote:
> -1 (binding)
>
> ----------------------------
> Igor Costa
> www.igorcosta.com
> www.igorcosta.org
>
>
> On Wed, May 29, 2013 at 8:49 AM, Margo Powell <ma...@msn.com> wrote:
>
> > +1
> > I love using swiz as a complement to flex sdk!
> >
> > > Date: Wed, 29 May 2013 11:43:28 +0200
> > > Subject: [VOTE] Swiz Framework Donation to Apache Flex
> > > From: carlosrovira@apache.org
> > > To: dev@flex.apache.org
> > >
> > > After proposal thread (http://markmail.org/message/jtedmmx5djqen52l
> > ),comes
> > > the vote thread.
> > >
> > > This thread is to decide if we finally adopt Swiz Framework under
> Apache
> > > Flex, since there is multiple opinions in the Apache Flex community.
> > >
> > > points to take into account:
> > >
> > > * Swiz is a great addition to Apache Flex since it complements de SDK
> > with
> > > a microarquitecture for application MVC, IOC, DI very simple and well
> > > designed.
> > > * This will be a project like flexunit or utilities. So it's optional a
> > NOT
> > > part of the main sdk.
> > > * Swiz is already in 1.4.0 stable version, under Apache License 2.0,
> has
> > > its community and right now there's no maintenance or upgrade since
> > people
> > > behind the project is no longer working with Flex technology.
> > > * Donation will be 1.4.0 source code and wiki content.
> > > * Future plans: if donation is successful, Chris Scott (creator of
> Swiz)
> > > will want to donate experimental 2.0.0 branch that brings AOP support,
> a
> > > feature that could bring a great benefit to Apache Flex since it brings
> > > something very new to client web technologies and that will require
> > > evolution at compiler level (introducing compile time weaving).
> > >
> > > Points that some people argument to not accept the donation:
> > > * There is other frameworks like Swiz out there in the same situation
> and
> > > this donation could make Swiz the preferred/recommended IOC framework
> of
> > > use.
> > >
> > > Points to take into account:
> > > * Erik de bruin stated that maybe the problem is "what to do with it"
> > under
> > > Apache Flex umbrella.
> > >
> > >
> > > Please make your vote.
> > >
> > > Thanks
> > >
> > > Carlos Rovira
> >
> >
>
Re: [VOTE] Swiz Framework Donation to Apache Flex
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
Generally a -1 vote needs a reason can you explain why?
Thanks,
Justin
Re: [VOTE] Swiz Framework Donation to Apache Flex
Posted by Igor Costa <ig...@gmail.com>.
-1 (binding)
----------------------------
Igor Costa
www.igorcosta.com
www.igorcosta.org
On Wed, May 29, 2013 at 8:49 AM, Margo Powell <ma...@msn.com> wrote:
> +1
> I love using swiz as a complement to flex sdk!
>
> > Date: Wed, 29 May 2013 11:43:28 +0200
> > Subject: [VOTE] Swiz Framework Donation to Apache Flex
> > From: carlosrovira@apache.org
> > To: dev@flex.apache.org
> >
> > After proposal thread (http://markmail.org/message/jtedmmx5djqen52l
> ),comes
> > the vote thread.
> >
> > This thread is to decide if we finally adopt Swiz Framework under Apache
> > Flex, since there is multiple opinions in the Apache Flex community.
> >
> > points to take into account:
> >
> > * Swiz is a great addition to Apache Flex since it complements de SDK
> with
> > a microarquitecture for application MVC, IOC, DI very simple and well
> > designed.
> > * This will be a project like flexunit or utilities. So it's optional a
> NOT
> > part of the main sdk.
> > * Swiz is already in 1.4.0 stable version, under Apache License 2.0, has
> > its community and right now there's no maintenance or upgrade since
> people
> > behind the project is no longer working with Flex technology.
> > * Donation will be 1.4.0 source code and wiki content.
> > * Future plans: if donation is successful, Chris Scott (creator of Swiz)
> > will want to donate experimental 2.0.0 branch that brings AOP support, a
> > feature that could bring a great benefit to Apache Flex since it brings
> > something very new to client web technologies and that will require
> > evolution at compiler level (introducing compile time weaving).
> >
> > Points that some people argument to not accept the donation:
> > * There is other frameworks like Swiz out there in the same situation and
> > this donation could make Swiz the preferred/recommended IOC framework of
> > use.
> >
> > Points to take into account:
> > * Erik de bruin stated that maybe the problem is "what to do with it"
> under
> > Apache Flex umbrella.
> >
> >
> > Please make your vote.
> >
> > Thanks
> >
> > Carlos Rovira
>
>
RE: [VOTE] Swiz Framework Donation to Apache Flex
Posted by Margo Powell <ma...@msn.com>.
+1
I love using swiz as a complement to flex sdk!
> Date: Wed, 29 May 2013 11:43:28 +0200
> Subject: [VOTE] Swiz Framework Donation to Apache Flex
> From: carlosrovira@apache.org
> To: dev@flex.apache.org
>
> After proposal thread (http://markmail.org/message/jtedmmx5djqen52l),comes
> the vote thread.
>
> This thread is to decide if we finally adopt Swiz Framework under Apache
> Flex, since there is multiple opinions in the Apache Flex community.
>
> points to take into account:
>
> * Swiz is a great addition to Apache Flex since it complements de SDK with
> a microarquitecture for application MVC, IOC, DI very simple and well
> designed.
> * This will be a project like flexunit or utilities. So it's optional a NOT
> part of the main sdk.
> * Swiz is already in 1.4.0 stable version, under Apache License 2.0, has
> its community and right now there's no maintenance or upgrade since people
> behind the project is no longer working with Flex technology.
> * Donation will be 1.4.0 source code and wiki content.
> * Future plans: if donation is successful, Chris Scott (creator of Swiz)
> will want to donate experimental 2.0.0 branch that brings AOP support, a
> feature that could bring a great benefit to Apache Flex since it brings
> something very new to client web technologies and that will require
> evolution at compiler level (introducing compile time weaving).
>
> Points that some people argument to not accept the donation:
> * There is other frameworks like Swiz out there in the same situation and
> this donation could make Swiz the preferred/recommended IOC framework of
> use.
>
> Points to take into account:
> * Erik de bruin stated that maybe the problem is "what to do with it" under
> Apache Flex umbrella.
>
>
> Please make your vote.
>
> Thanks
>
> Carlos Rovira
[VOTE] Swiz Framework Donation to Apache Flex
Posted by Carlos Rovira <ca...@apache.org>.
After proposal thread (http://markmail.org/message/jtedmmx5djqen52l),comes
the vote thread.
This thread is to decide if we finally adopt Swiz Framework under Apache
Flex, since there is multiple opinions in the Apache Flex community.
points to take into account:
* Swiz is a great addition to Apache Flex since it complements de SDK with
a microarquitecture for application MVC, IOC, DI very simple and well
designed.
* This will be a project like flexunit or utilities. So it's optional a NOT
part of the main sdk.
* Swiz is already in 1.4.0 stable version, under Apache License 2.0, has
its community and right now there's no maintenance or upgrade since people
behind the project is no longer working with Flex technology.
* Donation will be 1.4.0 source code and wiki content.
* Future plans: if donation is successful, Chris Scott (creator of Swiz)
will want to donate experimental 2.0.0 branch that brings AOP support, a
feature that could bring a great benefit to Apache Flex since it brings
something very new to client web technologies and that will require
evolution at compiler level (introducing compile time weaving).
Points that some people argument to not accept the donation:
* There is other frameworks like Swiz out there in the same situation and
this donation could make Swiz the preferred/recommended IOC framework of
use.
Points to take into account:
* Erik de bruin stated that maybe the problem is "what to do with it" under
Apache Flex umbrella.
Please make your vote.
Thanks
Carlos Rovira
Re: [VOTE] Swiz Framework Donation to Apache Flex
Posted by Arnoud Bos <ar...@artim-interactive.nl>.
+1 (non binding), really like Swiz
On 29-05-2013, at 11:42, Carlos Rovira <ca...@apache.org> wrote:
> After proposal thread (http://markmail.org/message/jtedmmx5djqen52l),comes
> the vote thread.
>
> This thread is to decide if we finally adopt Swiz Framework under Apache
> Flex, since there is multiple opinions in the Apache Flex community.
>
> points to take into account:
>
> * Swiz is a great addition to Apache Flex since it complements de SDK with
> a microarquitecture for application MVC, IOC, DI very simple and well
> designed.
> * This will be a project like flexunit or utilities. So it's optional a NOT
> part of the main sdk.
> * Swiz is already in 1.4.0 stable version, under Apache License 2.0, has
> its community and right now there's no maintenance or upgrade since people
> behind the project is no longer working with Flex technology.
> * Donation will be 1.4.0 source code and wiki content.
> * Future plans: if donation is successful, Chris Scott (creator of Swiz)
> will want to donate experimental 2.0.0 branch that brings AOP support, a
> feature that could bring a great benefit to Apache Flex since it brings
> something very new to client web technologies and that will require
> evolution at compiler level (introducing compile time weaving).
>
> Points that some people argument to not accept the donation:
> * There is other frameworks like Swiz out there in the same situation and
> this donation could make Swiz the preferred/recommended IOC framework of
> use.
>
> Points to take into account:
> * Erik de bruin stated that maybe the problem is "what to do with it" under
> Apache Flex umbrella.
>
>
> Please make your vote.
>
> Thanks
>
> Carlos Rovira
Met vriendelijke groet,
Arnoud Bos
Artim interactive
E arnoud@artim-interactive.nl
W www.artim-interactive.nl
T +31 6 246 40 216
A Elisabeth Wolffstraat 77-3
1053TT Amsterdam
Re: [VOTE] Swiz Framework Donation to Apache Flex
Posted by Alex Harui <ah...@adobe.com>.
-1 (binding). See [DISCUSS] thread.
On 5/29/13 2:42 AM, "Carlos Rovira" <ca...@apache.org> wrote:
>After proposal thread (http://markmail.org/message/jtedmmx5djqen52l),comes
>the vote thread.
>
>This thread is to decide if we finally adopt Swiz Framework under Apache
>Flex, since there is multiple opinions in the Apache Flex community.
>
>points to take into account:
>
>* Swiz is a great addition to Apache Flex since it complements de SDK with
>a microarquitecture for application MVC, IOC, DI very simple and well
>designed.
>* This will be a project like flexunit or utilities. So it's optional a
>NOT
>part of the main sdk.
>* Swiz is already in 1.4.0 stable version, under Apache License 2.0, has
>its community and right now there's no maintenance or upgrade since people
>behind the project is no longer working with Flex technology.
>* Donation will be 1.4.0 source code and wiki content.
>* Future plans: if donation is successful, Chris Scott (creator of Swiz)
>will want to donate experimental 2.0.0 branch that brings AOP support, a
>feature that could bring a great benefit to Apache Flex since it brings
>something very new to client web technologies and that will require
>evolution at compiler level (introducing compile time weaving).
>
>Points that some people argument to not accept the donation:
>* There is other frameworks like Swiz out there in the same situation and
>this donation could make Swiz the preferred/recommended IOC framework of
>use.
>
>Points to take into account:
>* Erik de bruin stated that maybe the problem is "what to do with it"
>under
>Apache Flex umbrella.
>
>
>Please make your vote.
>
>Thanks
>
>Carlos Rovira
[VOTE] Swiz Framework Donation to Apache Flex
Posted by Carlos Rovira <ca...@apache.org>.
After proposal thread (http://markmail.org/message/jtedmmx5djqen52l),comes
the vote thread.
This thread is to decide if we finally adopt Swiz Framework under Apache
Flex, since there is multiple opinions in the Apache Flex community.
points to take into account:
* Swiz is a great addition to Apache Flex since it complements de SDK with
a microarquitecture for application MVC, IOC, DI very simple and well
designed.
* This will be a project like flexunit or utilities. So it's optional a NOT
part of the main sdk.
* Swiz is already in 1.4.0 stable version, under Apache License 2.0, has
its community and right now there's no maintenance or upgrade since people
behind the project is no longer working with Flex technology.
* Donation will be 1.4.0 source code and wiki content.
* Future plans: if donation is successful, Chris Scott (creator of Swiz)
will want to donate experimental 2.0.0 branch that brings AOP support, a
feature that could bring a great benefit to Apache Flex since it brings
something very new to client web technologies and that will require
evolution at compiler level (introducing compile time weaving).
Points that some people argument to not accept the donation:
* There is other frameworks like Swiz out there in the same situation and
this donation could make Swiz the preferred/recommended IOC framework of
use.
Points to take into account:
* Erik de bruin stated that maybe the problem is "what to do with it" under
Apache Flex umbrella.
Please make your vote.
Thanks
Carlos Rovira
Re: [PROPOSAL] Swiz Framework Donation to Apache Flex
Posted by Dave Fisher <da...@comcast.net>.
On May 28, 2013, at 10:25 AM, Greg Reddin wrote:
> On Tue, May 28, 2013 at 11:18 AM, Alex Harui <ah...@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.
Donations should go through an announcement / vote process in the incubator to accept IP.
>
>
> 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.
Apache Commons looks like Jakarta junior already.
The Incubator has decided to only incubate TLPs.
>
> 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.
>
> It's hard to know where the breaking point is. Probably it has to do with
> whether the community is having a hard time pushing out releases or just
> whether it "feels" fragmented. I'm not proposing that we break up now, but
> we should probably be thinking about whether the Falcon project, for
> example, has its own distinct community from the SDK.
Which has an interesting point as there is now a podling called Falcon in the Incubator. This means that the name Apache Falcon is currently taken.
Regards,
Dave
>
> Greg
Re: [PROPOSAL] Swiz Framework Donation to Apache Flex
Posted by Erik de Bruin <er...@ixsoftware.nl>.
Greg,
I see why you might be worried about future additional projects, but
the sub-projects you mention (Falcon, SDK, FlexJS) are very much part
of one and the same project. Other sub-projects are purely for
supporting the community and various workflows (Installer, Maven) and
are "too small" to make sense on their own.
I don't know much about Swiz, but what I know seems to points in the
direction of "should exist separate but next to the SDK".
As long as the various sub-projects are strongly tied to the central
project (FlexSDK), I don't think we are in danger of fragmenting and
I'm convinced that the synergy between them will bring additional
value to all of them.
EdB
On Tue, May 28, 2013 at 7:25 PM, Greg Reddin <gr...@gmail.com> wrote:
> On Tue, May 28, 2013 at 11:18 AM, Alex Harui <ah...@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.
>
> 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.
>
> It's hard to know where the breaking point is. Probably it has to do with
> whether the community is having a hard time pushing out releases or just
> whether it "feels" fragmented. I'm not proposing that we break up now, but
> we should probably be thinking about whether the Falcon project, for
> example, has its own distinct community from the SDK.
>
> Greg
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
Re: [PROPOSAL] Swiz Framework Donation to Apache Flex
Posted by OmPrakash Muppirala <bi...@gmail.com>.
I like the donation of the Swiz framework. I use both swiz(for work) and
parsley(personal projects) and I am ambivalent at this point. What I would
really like to see the best part of these frameworks (and maeby others like
spring-actionscript, robotlegs, etc.) integrated into Flex.
I am talking about things like an IOC container, DI, autowiring,
message/event handling etc.
The way I see it, these frameworks came about to fill a void in the Flex
framework. Now that we are Apache, there is nothing stopping us from
baking these paradigms into the framework, thereby making these frameworks
obsolete.
Thanks,
Om
On Tue, May 28, 2013 at 10:25 AM, Greg Reddin <gr...@gmail.com> wrote:
> On Tue, May 28, 2013 at 11:18 AM, Alex Harui <ah...@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.
>
> 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.
>
> It's hard to know where the breaking point is. Probably it has to do with
> whether the community is having a hard time pushing out releases or just
> whether it "feels" fragmented. I'm not proposing that we break up now, but
> we should probably be thinking about whether the Falcon project, for
> example, has its own distinct community from the SDK.
>
> Greg
>
Re: [PROPOSAL] Swiz Framework Donation to Apache Flex
Posted by Alex Harui <ah...@adobe.com>.
On 5/28/13 10:25 AM, "Greg Reddin" <gr...@gmail.com> wrote:
>On Tue, May 28, 2013 at 11:18 AM, Alex Harui <ah...@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
>
Re: [PROPOSAL] Swiz Framework Donation to Apache Flex
Posted by Greg Reddin <gr...@gmail.com>.
On Tue, May 28, 2013 at 11:18 AM, Alex Harui <ah...@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.
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.
It's hard to know where the breaking point is. Probably it has to do with
whether the community is having a hard time pushing out releases or just
whether it "feels" fragmented. I'm not proposing that we break up now, but
we should probably be thinking about whether the Falcon project, for
example, has its own distinct community from the SDK.
Greg
Re: Do we want Abandoned Code?
Posted by OmPrakash Muppirala <bi...@gmail.com>.
I like the idea of the contrib folder/repo that Bertrand mentioned where
we could collect these kind of libraries. If we make it clear to end users
that these components may not be updated a lot, we should be good.
Thanks,
Om
On Thu, May 30, 2013 at 12:12 PM, Doug McCune <do...@dougmccune.com> wrote:
> If there was any interest at all, I'm sure it would be easy to migrate the
> flexlib code. There are a handful of contributors (me being one of the
> largest), and I'm sure assuming we still have good email addresses for
> everyone they'd all sign whatever is needed.
>
> Note that flexlib is nearly all Flex 3 components. There was work done to
> get them working with the 4.x framework, but I don't think any spark stuff
> was ever really created fresh, although I could be wrong. I haven't been
> paying attention to the project for years. So maybe since it's all
> non-Spark components y'all wouldn't want it anyway.
>
> It's on github these days: https://github.com/flex-users/flexlib but the
> last commit was nearly a year ago. You won't find any interest from the
> original creators of the project, and the only person who seems to have
> been maintaining the project any more is Julien Nicoulaud (
> https://github.com/nicoulaj).
>
>
> On Wed, May 29, 2013 at 2:45 PM, Bertrand Delacretaz <
> bdelacretaz@apache.org
> > wrote:
>
> > On Tue, May 28, 2013 at 7:49 PM, Jeffry Houser <je...@dot-com-it.com>
> > wrote:
> > > ... I could get the Flextras components donated, but didn't because
> > assumed
> > > Apache Flex didn't want to be the dumping ground for 'abandoned
> code'...
> >
> > In general yes, but many Apache projects have a "contrib" source code
> > folder for modules that are not necessarily actively maintained.
> >
> > As long as the project clearly defines what "contrib" means, so as to
> > avoid wrong expectations, that's perfectly fine.
> >
> > -Bertrand
> >
>
Re: Do we want Abandoned Code?
Posted by Doug McCune <do...@dougmccune.com>.
If there was any interest at all, I'm sure it would be easy to migrate the
flexlib code. There are a handful of contributors (me being one of the
largest), and I'm sure assuming we still have good email addresses for
everyone they'd all sign whatever is needed.
Note that flexlib is nearly all Flex 3 components. There was work done to
get them working with the 4.x framework, but I don't think any spark stuff
was ever really created fresh, although I could be wrong. I haven't been
paying attention to the project for years. So maybe since it's all
non-Spark components y'all wouldn't want it anyway.
It's on github these days: https://github.com/flex-users/flexlib but the
last commit was nearly a year ago. You won't find any interest from the
original creators of the project, and the only person who seems to have
been maintaining the project any more is Julien Nicoulaud (
https://github.com/nicoulaj).
On Wed, May 29, 2013 at 2:45 PM, Bertrand Delacretaz <bdelacretaz@apache.org
> wrote:
> On Tue, May 28, 2013 at 7:49 PM, Jeffry Houser <je...@dot-com-it.com>
> wrote:
> > ... I could get the Flextras components donated, but didn't because
> assumed
> > Apache Flex didn't want to be the dumping ground for 'abandoned code'...
>
> In general yes, but many Apache projects have a "contrib" source code
> folder for modules that are not necessarily actively maintained.
>
> As long as the project clearly defines what "contrib" means, so as to
> avoid wrong expectations, that's perfectly fine.
>
> -Bertrand
>
Re: Do we want Abandoned Code?
Posted by Bertrand Delacretaz <bd...@apache.org>.
On Tue, May 28, 2013 at 7:49 PM, Jeffry Houser <je...@dot-com-it.com> wrote:
> ... I could get the Flextras components donated, but didn't because assumed
> Apache Flex didn't want to be the dumping ground for 'abandoned code'...
In general yes, but many Apache projects have a "contrib" source code
folder for modules that are not necessarily actively maintained.
As long as the project clearly defines what "contrib" means, so as to
avoid wrong expectations, that's perfectly fine.
-Bertrand
Re: Do we want Abandoned Code?
Posted by Jeffry Houser <je...@dot-com-it.com>.
The code in question is on GitHub:
https://github.com/Flextras/FlextrasComponents
On 5/28/2013 2:06 PM, Kessler CTR Mark J wrote:
> Or until they get enough interest in the abandoned code... run it out of a GitHub account outside of the formal apache process until it gains enough momentum.
>
> -Mark
>
> -----Original Message-----
> From: Erik de Bruin [mailto:erik@ixsoftware.nl]
> Sent: Tuesday, May 28, 2013 2:03 PM
> To: dev@flex.apache.org
> Subject: Re: Do we want Abandoned Code?
>
> +1, with the reservation that we don't want any and all code out there ;-)
>
> EdB
>
>
>
> On Tue, May 28, 2013 at 7:58 PM, aYo ~ <ay...@binitie.com> wrote:
>> If the donated assets are relevant to flex development I see no reason why
>> not. Development of those assets ceased mainly because there was a loss of
>> faith, we on the other hand believe in the project and are moving it on,
>> n'est pas ?
>> On 28 May 2013 18:50, "Jeffry Houser" <je...@dot-com-it.com> wrote:
>>
>>> On 5/28/2013 12:18 PM, Alex Harui wrote:
>>>
>>>> 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.
>>>>
>>> What do others think of this sentiment?
>>>
>>> I could get the Flextras components donated, but didn't because assumed
>>> Apache Flex didn't want to be the dumping ground for 'abandoned code'
>>>
>>>
>>> --
>>> Jeffry Houser
>>> Technical Entrepreneur
>>> 203-379-0773
>>> --
>>> http://www.flextras.com?c=104
>>> UI Flex Components: Tested! Supported! Ready!
>>> --
>>> http://www.theflexshow.com
>>> http://www.jeffryhouser.com
>>> http://www.asktheflexpert.com
>>> --
>>> Part of the DotComIt Brain Trust
>>>
>>>
>
>
--
Jeffry Houser
Technical Entrepreneur
203-379-0773
--
http://www.flextras.com?c=104
UI Flex Components: Tested! Supported! Ready!
--
http://www.theflexshow.com
http://www.jeffryhouser.com
http://www.asktheflexpert.com
--
Part of the DotComIt Brain Trust
Re: Do we want Abandoned Code?
Posted by Alex Harui <ah...@adobe.com>.
IMO, it depends on the definition of "abandoned". If nobody is using it,
then we don't want it.
The donation process is time-consuming enough to act as a filter. If the
donor wants to spend the energy to do the IP clearance and software grant
and one or more committers want to do the Apache-fication of the code
(which, besides headers, should include bugging infra for a repo, and
making sure that a build script runs and hopefully a test or two runs),
and the community votes in favor, then it isn't truly "abandoned" by the
community, just by the donor.
Then, maybe, if later some user runs into a serious bug, this community
will band together and help them out.
Having these things scattered about the internet or github is sufficient,
but users don't have a place to turn to for help so they're less likely to
use it, and it might be in the interest of Apache Flex to give folks
reasons to keep using these other bodies of code.
On 5/28/13 11:06 AM, "Kessler CTR Mark J" <ma...@usmc.mil>
wrote:
>Or until they get enough interest in the abandoned code... run it out of
>a GitHub account outside of the formal apache process until it gains
>enough momentum.
>
>-Mark
>
>-----Original Message-----
>From: Erik de Bruin [mailto:erik@ixsoftware.nl]
>Sent: Tuesday, May 28, 2013 2:03 PM
>To: dev@flex.apache.org
>Subject: Re: Do we want Abandoned Code?
>
>+1, with the reservation that we don't want any and all code out there ;-)
>
>EdB
>
>
>
>On Tue, May 28, 2013 at 7:58 PM, aYo ~ <ay...@binitie.com> wrote:
>> If the donated assets are relevant to flex development I see no reason
>>why
>> not. Development of those assets ceased mainly because there was a loss
>>of
>> faith, we on the other hand believe in the project and are moving it on,
>> n'est pas ?
>> On 28 May 2013 18:50, "Jeffry Houser" <je...@dot-com-it.com> wrote:
>>
>>> On 5/28/2013 12:18 PM, Alex Harui wrote:
>>>
>>>> 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.
>>>>
>>>
>>> What do others think of this sentiment?
>>>
>>> I could get the Flextras components donated, but didn't because
>>>assumed
>>> Apache Flex didn't want to be the dumping ground for 'abandoned code'
>>>
>>>
>>> --
>>> Jeffry Houser
>>> Technical Entrepreneur
>>> 203-379-0773
>>> --
>>> http://www.flextras.com?c=104
>>> UI Flex Components: Tested! Supported! Ready!
>>> --
>>> http://www.theflexshow.com
>>> http://www.jeffryhouser.com
>>> http://www.asktheflexpert.com
>>> --
>>> Part of the DotComIt Brain Trust
>>>
>>>
>
>
>
>--
>Ix Multimedia Software
>
>Jan Luykenstraat 27
>3521 VB Utrecht
>
>T. 06-51952295
>I. www.ixsoftware.nl
RE: Do we want Abandoned Code?
Posted by Kessler CTR Mark J <ma...@usmc.mil>.
Or until they get enough interest in the abandoned code... run it out of a GitHub account outside of the formal apache process until it gains enough momentum.
-Mark
-----Original Message-----
From: Erik de Bruin [mailto:erik@ixsoftware.nl]
Sent: Tuesday, May 28, 2013 2:03 PM
To: dev@flex.apache.org
Subject: Re: Do we want Abandoned Code?
+1, with the reservation that we don't want any and all code out there ;-)
EdB
On Tue, May 28, 2013 at 7:58 PM, aYo ~ <ay...@binitie.com> wrote:
> If the donated assets are relevant to flex development I see no reason why
> not. Development of those assets ceased mainly because there was a loss of
> faith, we on the other hand believe in the project and are moving it on,
> n'est pas ?
> On 28 May 2013 18:50, "Jeffry Houser" <je...@dot-com-it.com> wrote:
>
>> On 5/28/2013 12:18 PM, Alex Harui wrote:
>>
>>> 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.
>>>
>>
>> What do others think of this sentiment?
>>
>> I could get the Flextras components donated, but didn't because assumed
>> Apache Flex didn't want to be the dumping ground for 'abandoned code'
>>
>>
>> --
>> Jeffry Houser
>> Technical Entrepreneur
>> 203-379-0773
>> --
>> http://www.flextras.com?c=104
>> UI Flex Components: Tested! Supported! Ready!
>> --
>> http://www.theflexshow.com
>> http://www.jeffryhouser.com
>> http://www.asktheflexpert.com
>> --
>> Part of the DotComIt Brain Trust
>>
>>
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
Re: Do we want Abandoned Code?
Posted by Erik de Bruin <er...@ixsoftware.nl>.
+1, with the reservation that we don't want any and all code out there ;-)
EdB
On Tue, May 28, 2013 at 7:58 PM, aYo ~ <ay...@binitie.com> wrote:
> If the donated assets are relevant to flex development I see no reason why
> not. Development of those assets ceased mainly because there was a loss of
> faith, we on the other hand believe in the project and are moving it on,
> n'est pas ?
> On 28 May 2013 18:50, "Jeffry Houser" <je...@dot-com-it.com> wrote:
>
>> On 5/28/2013 12:18 PM, Alex Harui wrote:
>>
>>> 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.
>>>
>>
>> What do others think of this sentiment?
>>
>> I could get the Flextras components donated, but didn't because assumed
>> Apache Flex didn't want to be the dumping ground for 'abandoned code'
>>
>>
>> --
>> Jeffry Houser
>> Technical Entrepreneur
>> 203-379-0773
>> --
>> http://www.flextras.com?c=104
>> UI Flex Components: Tested! Supported! Ready!
>> --
>> http://www.theflexshow.com
>> http://www.jeffryhouser.com
>> http://www.asktheflexpert.com
>> --
>> Part of the DotComIt Brain Trust
>>
>>
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
Re: Do we want Abandoned Code?
Posted by aYo ~ <ay...@binitie.com>.
If the donated assets are relevant to flex development I see no reason why
not. Development of those assets ceased mainly because there was a loss of
faith, we on the other hand believe in the project and are moving it on,
n'est pas ?
On 28 May 2013 18:50, "Jeffry Houser" <je...@dot-com-it.com> wrote:
> On 5/28/2013 12:18 PM, Alex Harui wrote:
>
>> 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.
>>
>
> What do others think of this sentiment?
>
> I could get the Flextras components donated, but didn't because assumed
> Apache Flex didn't want to be the dumping ground for 'abandoned code'
>
>
> --
> Jeffry Houser
> Technical Entrepreneur
> 203-379-0773
> --
> http://www.flextras.com?c=104
> UI Flex Components: Tested! Supported! Ready!
> --
> http://www.theflexshow.com
> http://www.jeffryhouser.com
> http://www.asktheflexpert.com
> --
> Part of the DotComIt Brain Trust
>
>
Do we want Abandoned Code?
Posted by Jeffry Houser <je...@dot-com-it.com>.
On 5/28/2013 12:18 PM, Alex Harui wrote:
> 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.
What do others think of this sentiment?
I could get the Flextras components donated, but didn't because
assumed Apache Flex didn't want to be the dumping ground for 'abandoned
code'
--
Jeffry Houser
Technical Entrepreneur
203-379-0773
--
http://www.flextras.com?c=104
UI Flex Components: Tested! Supported! Ready!
--
http://www.theflexshow.com
http://www.jeffryhouser.com
http://www.asktheflexpert.com
--
Part of the DotComIt Brain Trust
Re: [PROPOSAL] Swiz Framework Donation to Apache Flex
Posted by Alex Harui <ah...@adobe.com>.
On 5/28/13 8:39 AM, "Greg Reddin" <gr...@gmail.com> wrote:
>On Tue, May 28, 2013 at 10:37 AM, Roland Zwaga
><ro...@stackandheap.com>wrote:
>
>> On 28 May 2013 17:33, dude <du...@atheist.com> wrote:
>>
>> > Good luck, but I'd rather see Parsley integrated into Apache Flex.
>> >
>> >
>>
>> Personally, the above response shows exactly the reason why I think
>>there
>> shouldn't be any
>> application framework integrated into Apache Flex. Too many opinions on
>> the matter...
>>
>
>But, there's no reason we can't integrate it as a sub-project or incubate
>it. If it develops a community it can become its own TLP.
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. That way folks looking for
the latest code can know that they can come to Apache to get a legal copy
and ask questions on the mailing list that have a chance of being
answered. Or do we have to commit to releasing this code on occasion?
I agree with not wanting to "integrate" any application-level framework
with the Apache Flex SDK releases. I don't think we want to appear to be
promoting one over the other. That said, I believe somewhere in the
archives, the person behind Parsley announced that he was no longer
maintaining it. Maybe it could also be donated to Apache.
Also, does a donation like Swiz need a whole Software Grant or is an email
trail sufficient?
-Alex
Re: [PROPOSAL] Swiz Framework Donation to Apache Flex
Posted by aYo ~ <ay...@binitie.com>.
I agree
On 28 May 2013 17:28, "dude" <du...@atheist.com> wrote:
> None of these frameworks should be integrated into Apache Flex, I guess
> everyone agrees with that.
>
> FYI: Parsley has been abandoned by its creator as well and there is no
> further development atm (afaik). It is licenced under Apache License 2.0
> and available here https://github.com/spicefactory
>
> Am 28.05.2013 17:44, schrieb Carlos Rovira:
> > I don't know the actual state of RobotLegs, Parsley or others... Swiz is
> > without maintenance and needs attention and 2.0 could bring a great
> > improvment not reached for any other framework. This doesn't mean any
> base
> > sdk integration and dependency. We could make the same with other
> projects
> > that need a home. This should be driven by community necessity and should
> > have people behind the effort.
> >
> > 2013/5/28 Greg Reddin <gr...@gmail.com>
> >
> >> On Tue, May 28, 2013 at 10:37 AM, Roland Zwaga <roland@stackandheap.com
> >>> wrote:
> >>
> >>> On 28 May 2013 17:33, dude <du...@atheist.com> wrote:
> >>>
> >>>> Good luck, but I'd rather see Parsley integrated into Apache Flex.
> >>>>
> >>>>
> >>>
> >>> Personally, the above response shows exactly the reason why I think
> there
> >>> shouldn't be any
> >>> application framework integrated into Apache Flex. Too many opinions
> on
> >>> the matter...
> >>>
> >>
> >> But, there's no reason we can't integrate it as a sub-project or
> incubate
> >> it. If it develops a community it can become its own TLP.
> >>
> >
> >
> >
>
Re: [PROPOSAL] Swiz Framework Donation to Apache Flex
Posted by Erik de Bruin <er...@ixsoftware.nl>.
I like the idea of a vote. I don't think the community is divided
about 'having' Swiz, it seems the division is more 'what to do with
it'. Please let the VOTE be clear about this.
EdB
On Tue, May 28, 2013 at 6:49 PM, Carlos Rovira
<ca...@codeoscopic.com> wrote:
> I think this would require a vote thread since it seems to have community
> opinion divided.
> I'll give a breath for some hours to open a VOTE thread if you all are ok
> with that.
>
>
>
> 2013/5/28 dude <du...@atheist.com>
>
>> None of these frameworks should be integrated into Apache Flex, I guess
>> everyone agrees with that.
>>
>> FYI: Parsley has been abandoned by its creator as well and there is no
>> further development atm (afaik). It is licenced under Apache License 2.0
>> and available here https://github.com/spicefactory
>>
>> Am 28.05.2013 17:44, schrieb Carlos Rovira:
>> > I don't know the actual state of RobotLegs, Parsley or others... Swiz is
>> > without maintenance and needs attention and 2.0 could bring a great
>> > improvment not reached for any other framework. This doesn't mean any
>> base
>> > sdk integration and dependency. We could make the same with other
>> projects
>> > that need a home. This should be driven by community necessity and should
>> > have people behind the effort.
>> >
>> > 2013/5/28 Greg Reddin <gr...@gmail.com>
>> >
>> >> On Tue, May 28, 2013 at 10:37 AM, Roland Zwaga <roland@stackandheap.com
>> >>> wrote:
>> >>
>> >>> On 28 May 2013 17:33, dude <du...@atheist.com> wrote:
>> >>>
>> >>>> Good luck, but I'd rather see Parsley integrated into Apache Flex.
>> >>>>
>> >>>>
>> >>>
>> >>> Personally, the above response shows exactly the reason why I think
>> there
>> >>> shouldn't be any
>> >>> application framework integrated into Apache Flex. Too many opinions
>> on
>> >>> the matter...
>> >>>
>> >>
>> >> But, there's no reason we can't integrate it as a sub-project or
>> incubate
>> >> it. If it develops a community it can become its own TLP.
>> >>
>> >
>> >
>> >
>>
>
>
>
> --
> Carlos Rovira
> Director de Tecnología
> M: +34 607 22 60 05
> F: +34 912 94 80 80
> http://www.codeoscopic.com
> http://www.directwriter.es
> http://www.avant2.es
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
Re: [PROPOSAL] Swiz Framework Donation to Apache Flex
Posted by Carlos Rovira <ca...@codeoscopic.com>.
I think this would require a vote thread since it seems to have community
opinion divided.
I'll give a breath for some hours to open a VOTE thread if you all are ok
with that.
2013/5/28 dude <du...@atheist.com>
> None of these frameworks should be integrated into Apache Flex, I guess
> everyone agrees with that.
>
> FYI: Parsley has been abandoned by its creator as well and there is no
> further development atm (afaik). It is licenced under Apache License 2.0
> and available here https://github.com/spicefactory
>
> Am 28.05.2013 17:44, schrieb Carlos Rovira:
> > I don't know the actual state of RobotLegs, Parsley or others... Swiz is
> > without maintenance and needs attention and 2.0 could bring a great
> > improvment not reached for any other framework. This doesn't mean any
> base
> > sdk integration and dependency. We could make the same with other
> projects
> > that need a home. This should be driven by community necessity and should
> > have people behind the effort.
> >
> > 2013/5/28 Greg Reddin <gr...@gmail.com>
> >
> >> On Tue, May 28, 2013 at 10:37 AM, Roland Zwaga <roland@stackandheap.com
> >>> wrote:
> >>
> >>> On 28 May 2013 17:33, dude <du...@atheist.com> wrote:
> >>>
> >>>> Good luck, but I'd rather see Parsley integrated into Apache Flex.
> >>>>
> >>>>
> >>>
> >>> Personally, the above response shows exactly the reason why I think
> there
> >>> shouldn't be any
> >>> application framework integrated into Apache Flex. Too many opinions
> on
> >>> the matter...
> >>>
> >>
> >> But, there's no reason we can't integrate it as a sub-project or
> incubate
> >> it. If it develops a community it can become its own TLP.
> >>
> >
> >
> >
>
--
Carlos Rovira
Director de Tecnología
M: +34 607 22 60 05
F: +34 912 94 80 80
http://www.codeoscopic.com
http://www.directwriter.es
http://www.avant2.es
Re: [PROPOSAL] Swiz Framework Donation to Apache Flex
Posted by dude <du...@atheist.com>.
None of these frameworks should be integrated into Apache Flex, I guess
everyone agrees with that.
FYI: Parsley has been abandoned by its creator as well and there is no
further development atm (afaik). It is licenced under Apache License 2.0
and available here https://github.com/spicefactory
Am 28.05.2013 17:44, schrieb Carlos Rovira:
> I don't know the actual state of RobotLegs, Parsley or others... Swiz is
> without maintenance and needs attention and 2.0 could bring a great
> improvment not reached for any other framework. This doesn't mean any base
> sdk integration and dependency. We could make the same with other projects
> that need a home. This should be driven by community necessity and should
> have people behind the effort.
>
> 2013/5/28 Greg Reddin <gr...@gmail.com>
>
>> On Tue, May 28, 2013 at 10:37 AM, Roland Zwaga <roland@stackandheap.com
>>> wrote:
>>
>>> On 28 May 2013 17:33, dude <du...@atheist.com> wrote:
>>>
>>>> Good luck, but I'd rather see Parsley integrated into Apache Flex.
>>>>
>>>>
>>>
>>> Personally, the above response shows exactly the reason why I think there
>>> shouldn't be any
>>> application framework integrated into Apache Flex. Too many opinions on
>>> the matter...
>>>
>>
>> But, there's no reason we can't integrate it as a sub-project or incubate
>> it. If it develops a community it can become its own TLP.
>>
>
>
>
Re: [PROPOSAL] Swiz Framework Donation to Apache Flex
Posted by Carlos Rovira <ca...@codeoscopic.com>.
I don't know the actual state of RobotLegs, Parsley or others... Swiz is
without maintenance and needs attention and 2.0 could bring a great
improvment not reached for any other framework. This doesn't mean any base
sdk integration and dependency. We could make the same with other projects
that need a home. This should be driven by community necessity and should
have people behind the effort.
2013/5/28 Greg Reddin <gr...@gmail.com>
> On Tue, May 28, 2013 at 10:37 AM, Roland Zwaga <roland@stackandheap.com
> >wrote:
>
> > On 28 May 2013 17:33, dude <du...@atheist.com> wrote:
> >
> > > Good luck, but I'd rather see Parsley integrated into Apache Flex.
> > >
> > >
> >
> > Personally, the above response shows exactly the reason why I think there
> > shouldn't be any
> > application framework integrated into Apache Flex. Too many opinions on
> > the matter...
> >
>
> But, there's no reason we can't integrate it as a sub-project or incubate
> it. If it develops a community it can become its own TLP.
>
--
Carlos Rovira
Director de Tecnología
M: +34 607 22 60 05
F: +34 912 94 80 80
http://www.codeoscopic.com
http://www.directwriter.es
http://www.avant2.es
Re: [PROPOSAL] Swiz Framework Donation to Apache Flex
Posted by Greg Reddin <gr...@gmail.com>.
On Tue, May 28, 2013 at 10:37 AM, Roland Zwaga <ro...@stackandheap.com>wrote:
> On 28 May 2013 17:33, dude <du...@atheist.com> wrote:
>
> > Good luck, but I'd rather see Parsley integrated into Apache Flex.
> >
> >
>
> Personally, the above response shows exactly the reason why I think there
> shouldn't be any
> application framework integrated into Apache Flex. Too many opinions on
> the matter...
>
But, there's no reason we can't integrate it as a sub-project or incubate
it. If it develops a community it can become its own TLP.
Re: [PROPOSAL] Swiz Framework Donation to Apache Flex
Posted by Roland Zwaga <ro...@stackandheap.com>.
On 28 May 2013 17:33, dude <du...@atheist.com> wrote:
> Good luck, but I'd rather see Parsley integrated into Apache Flex.
>
>
Personally, the above response shows exactly the reason why I think there
shouldn't be any
application framework integrated into Apache Flex. Too many opinions on
the matter...
Re: [PROPOSAL] Swiz Framework Donation to Apache Flex
Posted by dude <du...@atheist.com>.
Good luck, but I'd rather see Parsley integrated into Apache Flex.
Am 28.05.2013 16:52, schrieb Carlos Rovira:
> Hi,
>
> I want to propose the donation of Swiz Framework to Apache Flex.
>
> https://github.com/swiz/swiz-framework/
> https://swizframework.jira.com/wiki/display/SWIZ/Home
>
> The reasons behind the propossal are:
>
> * Swiz Framework is a mature microarquitecure for Apache Flex that
> complements it to build applications with MVC, DI and other commodities
> needed today to be productive. (There's other frameworks out there that
> could be used along Flex like RobotLegs, Parsley, ....)
>
> * Swiz is not updated anymore since people behind it migrated from Flex
> platform to HTML5 technologies and does not want to invest more time.
>
> * Swiz stopped development in 2.0.0 beta that brings AOP to Flex Framework.
> The problem with this implementation is that is not ready for producction
> since it needs changes in Flex Compiler and in AS3 Commons ByteCode to get
> it work properly.
>
> Chris Scott, the creator of swiz respond on the list some minutes ago and
> he approved the Swiz Framework Donation to Apache Flex.
>
> If people doesn't have any issues with this donation I'll go through the
> steps that, will require for actual production version. Taking into account
> that * Swiz Framework already has Apache License 2.0, the steps to get
> donation done should be only:
>
> * Get Chris Scott email accepting the donation of the swiz source code and
> wiki content.
> * I'll request a "flex-swiz-framework" git repo where we can migrate the
> source code.
>
> In a second round, Chris will want to donate 2.0.0 Beta and we can disscuss
> changes to Flex compiler and talk with as3commons to know enhancements to
> bytecode project and see if it's viable or not.
>
> Let me know what do you think about it and If I need to take into account
> something else.
>
> Thanks.
>
> Carlos Rovira
>