On 3/1/12 8:00 AM, "Rafael Santos" <rsan...@spectacompany.com.br> wrote:
>
> Mike, I agree with you that the core framework should stay simple, but
> maybe we could have some complementary projects don't you think?
What I think I've learned so far, is that Apache is about community as well
as technology. If there is a noticeable different set of folks who want to
work on something, it should be its own project.
The interesting thing about this is that it seems to make it hard to donate
stuff that is mature or stable since there won't be a lot of development
action on it.
I can't rule on whether BlazeDS is mature or stable, but we haven't found a
lot of people who want to do lots of work on it, so instead of creating a
top-level project for it, we will stick it into the Flex project somehow.
I'm still thinking we'll contribute Falcon under Flex, but it isn't totally
clear. There seems to be high overlap between the Falcon and Flex folks and
for a little while there might be release dependencies between the code
bases.
We could do that for application frameworks that need a home and don't have
a separate community as well. The real question is who plans to work on it.
I probably wouldn't work on the application frameworks.
And, you can always fork off a technology later if it does get its own
community.
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
