The thing I don't fully understand is this:
Swiz is already licensed under the Apache License (
https://github.com/swiz/swiz-framework/blob/develop/LICENSE ). If people
want to contribute, use, or modify then what is stopping them?
How will bringing the Swiz framework into the Apache Flex project help
Apache Flex?
How will bringing the Swiz framework into the Apache Flex project help
the Swiz framework?
I don't have an answer to either.
I don't understand why the union is needed; which is why I voted 0.
On 5/31/2013 12:30 PM, Alex Harui wrote:
I'd like to vote in favor, but I'm not liking the quantity of -1's we're
seeing.
Can we cancel this vote and draft a more detailed proposal, maybe after
some discussing with those voting -1?
I think the new proposal should be explicit about the name of the repo.
I think the new proposal should state that Swiz would have its own
releases and not be part of an SDK release.
One thing I'm not quite understanding is how the future would look if a
committer did try to add AOP into the SDK. Would that conflict with the
implementations in Swiz or other frameworks? Or is the expectation that
some set of committers will update Swiz to use that implementation of AOP?
Committers are free to do whatever they want, but if Swiz gets more love
than the other frameworks it could appear to be the "endorsed" framework,
which is what I think we are trying to avoid.
-Alex
On 5/29/13 6:16 PM, "Jeff Tapper" <j...@spoon.as> wrote:
-1 Binding, unless there are assurances that this will not be part of the
main branch, but instead live in a separate repo.
-----Original Message-----
From: Greg Reddin [mailto:gred...@gmail.com]
Sent: Wednesday, May 29, 2013 12:12 PM
To: dev@flex.apache.org
Subject: Re: [VOTE] Swiz Framework Donation to Apache Flex
+1 (binding)
On Wed, May 29, 2013 at 4:43 AM, Carlos Rovira
<carlosrov...@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
--
Jeffry Houser
Technical Entrepreneur
http://www.jeffryhouser.com
203-379-0773
