Hi Sebastian,

You quoted the last of 3 posts in that thread.  To me, the most important
snippet is in the original post where the OP asks: "Jens, if you're still
around..."

The point of donating Swiz or Parsley or any existing code base to Apache
is that at Apache, there are mailing lists that you know people are
reading.  If I was a consumer of Parsley but didn't have the skills or
time to make changes to it, I would be worried about how to get
maintenance and support for it.  But if Parsley was donated to Apache, I
might not have that worry.

Jens is incorrect about whether Apache can just take a fork.  Legally it
can, it from a policy perspective, Apache does not "take" code.  I suppose
we could argue that Jens' post gives us permission, but it would be better
if he was more explicit, and if the code is copyrighted to Spice Factory
instead of Jens personally, we probably need a Software Grant from Spice
Factory.

Apache is a corporation and does come with more overhead than a GitHub
project probably does, but that overhead provides legal, process, and
infrastructural guarantees that should draw more corporate customers.

-Alex

On 6/27/13 4:23 AM, "Sebastian Mohr" <flex.masul...@gmail.com> wrote:

>Hi there,
>
>just wonder what you think about this forum post of the SpiceFactory forum
>[1]:
>
>"With all due respect, I don't believe Apache did anything good with Flex.
>They struggle with a lot of internal bureaucracy and I believe that
>without
>clear leadership, this "meritocracy" thing just doesn't work. For the past
>year, Apache Flex community debated whether they should move to Git and
>right now when they did, they figured out that most people don't know how
>to use it, etc. etc. In other words, to much "nerd" driven, not enough
>"business realistic" driven."
>
>[1] http://www.spicefactory.org/forum/viewtopic.php?t=3803
>
>
>-- 
>Sebastian (PPMC)
>Interaction Designer
>
>Looking for a Login Example with Apache Flex? Please check out this code:
>http://code.google.com/p/masuland/wiki/LoginExample

Reply via email to