Donating BlazeDS to Apache Software Foundation

Hello Friends,

As you may already 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, we wanted to know:
1. Do you want to contribute to BlazeDS?
2. What changes would you want to make to BlazeDS?
3. How often do you think you would be able to contribute?

Thanks,
BlazeDS Team

10 Responses to Donating BlazeDS to Apache Software Foundation

  1. Hmm, no comments so far! 🙂 Strange because blaze DS is great in my opinion and should benefit of more attention from Adobe + The Community.
    Even if I am not an Expert in Java or Spring here are my answers to the questions:

    1. Yes
    2. Currently it is very difficult to get started and setup the development environment (even using the turnkey) so I would try to improve this initial steps at first sight and make life easier for people coming from PHP or .Net
    3. Most probably once a week (weekend)

    • Rohit Kumar says:

      Hi Adrian,

      Great! Once we roll out the process for donating the code to ASF, you are welcome to join as an external contributor.

      Rohit

  2. Murat Yener says:

    I want to contribute to blazeds. There are still a lot of places to improve in blaze.

    • Rohit Kumar says:

      Hi Murat,

      Great! Once we roll out the process for donating the code to ASF, you are welcome to join as an external contributor.

      Rohit

  3. Bergsma says:

    First of all, the BlazeDS Team should get rid of some well known performance limitations of BlazeDS (such as replacing the servlet-based feature with the nio one) before contributing it to Apache.
    Why ? BlazeDS should be as compelling as Flex to attract the momentum, you shouldn’t contributed a product with limitted potential because of its positionning against LCDS.
    I for one will not waste my time on enhancing a congenitally handicapped product, like many I’m more interrested in making better product in feature and in performance.

  4. Carlos says:

    I want to contribute to Blazeds. There should be some kind of support in th server side besides de Adobe commercial offers. AFMphp has many limitations. I think that Apache Flex is going to be lame without a clear and supported server technology. AMF3 is a great technoloy.

  5. techfuser says:

    1. Do you want to contribute to BlazeDS? NO
    2. What changes would you want to make to BlazeDS? NONE
    3. How often do you think you would be able to contribute? NONE

    Because of Websocket!

    • Rohit Kumar says:

      WebSockets is really a channel for communication. BlazeDS allows you to build remoting and messaging applications. All said, we support WebSocket channel in Data Services v4.6 with our HTML5/JS client. Take a look at the feature set for how that can be done.

      Rohit

  6. Nikhil says:

    1). Yes
    2). Bring it to compete with Livecycle
    3) Once a week.

  7. migueldiab says:

    1. Do you want to contribute to BlazeDS? YES!
    2. What changes would you want to make to BlazeDS? Fix deadlocks bugs, etc. Add Push
    3. How often do you think you would be able to contribute? 4 to 8 hours monthly