[Reposting the message once again]
As you may know, Adobe has promised to contribute BlazeDS to Apache. It could be a separate project (which would make sense technically), but an Apache project also needs an active community. An alternative plan would be to add the code to the Flex project in Apache. So, I want to know: Do you want to contribute to BlazeDS? What changes would you want to make to BlazeDS? How often do you think you would be able to contribute?
+1 for adding BlazeDS to the Apache Flex codebase. I think our community will be best suited to make contributions to BlazeDS as it comprises folks who use both these technologies extensively.
Personally, my goal is to contribute to BlazeDS as much as my time permits.
I think you will find it hard to recruit a 'community' to support BlazeDS. BlazeDS is a useful component of an architecture that includes Flex, both for beginners and for those on a budget. There have been many modifications/hacks made to allow BlazeDS to run in different environments and there would no doubt be people/companies (some of who I have talked to) that would like to contribute their code, at least to have things consolidated. Having this be visibile and accessible to the Apache Flex community would likely draw more support/contributions.
Posting BlazeDS to the Aphace Foundation under an Apache License is one of the best ways to ensure its survival.
One of the reason many entities are put off from using it is the LGPL License which many legal depts see as prohibiting its use alongside proprietry code.
The removal of this might widen its use and cause those of us who build and recomend such systems to use and contribute to it.
Flashmobile (FlexMobile) Air solutions for android/ios have amazing potential. We use a C# asp.net backend with fluorine and blazeDS on the client side. I'm not aware of a better rapid development approach to get business applications available on mobile apps that also easily talk back to an enterprise/corporate server. I'm absolutely interested in the survival, prosperity, and growth of this product.
You can find there the latest branches for BlazeDS in Sourceforge... I'm afraid it could be a little outdated, still it's a very relevant communication solution and we are using it in PROD with several thousand connections with both, Push messages and Polling...