I am pleased to announce that Flex as been accepted into the Apache Incubator. With weekends and holidays, I suspect that it will still be several days before we get up and running with mailing lists, bug base, source control, etc, so we continue to appreciate your patience. However, I’m really looking forward to 2012 and beyond, and I hope you are too.
We received a whopping 65 requests to be on the initial committers list for the proposal to become a Podling in the Apache Incubator! It is great to see such enthusiasm from the community.
We are discussing with Apache experts as to how many folks we can put on the list. I think it will be at least 24. Initial committers also form the Podling’s Project Management Committee and can vote in other committers who establish a track record by submitting patches that get accepted. I am not looking forward to having to deny so many of these requests. Once we pick a number, I will send each of you an email of whether your request was accepted or denied.
If you requested to be a committer and are not chosen to be on the initial list, please continue to show your support by contributing patches via the JIRA bug base that will be set up. That way you can be promoted to committer as soon as possible.
Thank you to all who requested to be a committer. I look forward to working with you on Flex.
One of the requirements for a proposal to incubate a new project in the Apache Software Foundation is to have an initial set of committers. A committer has to sign a license agreement with Apache in order to obtain write access to the source code repository. A committer’s responsibilities are listed at http://www.apache.org/dev/committers.html#committer-responsibilities.
As we announced at the Flex Community Summit earlier this week, we are looking to identify the initial committers for the Flex SDK incubation proposal. If you want to be on this list of initial committers, please email me at email@example.com by noon PST Friday, December 16, 2011. We may limit the initial set to around 12, but you can still become a committer after that by following the process outlined by Apache. And remember, if you don’t want to be a committer, you can still contribute in many ways.
We are excited to be engaging the community in the shaping of Flex, and look forward to your future contributions.
Flex SDK Team
Adobe Systems, Inc.
I wanted to share a brief update on where we are with our preparation of proposals for incubation of Flex SDK and BlazeDS to the Apache Software Foundation as well as our commitment to engaging with the Flex community further.
Regarding the incubation proposals, we have received all of the necessary Adobe legal clearance in order to contribute the full Flex SDK (including MXML compiler, automation libraries and data visualization components) to Apache. As such we have a draft incubation proposal for Flex SDK prepared and are aiming to post that to the Apache incubation mailing list within the next 1-2 weeks. Once the proposal has been posted, the normal process is that community members review the proposal for a period of time (normally 72 hours) after which the ASF votes. A positive vote means the project has been accepted as an incubation podling into Apache. Keep an eye out on this blog for regular status updates, including a link to the proposal once its been posted to the Apache incubation mailing list.
As for BlazeDS, at this time we are still working on legal clearance but aim to have that before the end of the year such that we can post the BlazeDS incubation proposal to the Apache mailing list at the start of the new year.
In order to better facilitate discussion with our broad developer community, next Monday (12/12/11) and Tuesday (12/13/11) Adobe is hosting a Flex Community Summit where we are inviting a number of Flex community leaders and enterprise developers to participate in a discussion on a variety of topics. We will be discussing the recent announcements regarding Flex and the Flash Platform as well as educating all attendees about the Apache process and what it takes for a project to thrive within Apache. Unfortunately, due to budget, we were unable to invite everyone we would have liked to the summit. Most of the summit sessions and ensuing discussions will be video-taped and posted publicly after the summit. Additionally, we are working on a Flex Whitepaper that we will publish on the Adobe Developer Center which will recap much of the content covered in the summit.
And lastly, in order to replicate the same discussions that will happen at the summit, we are organizing a multi-city international Flex User Group tour that we are looking to kick off in early 2012.
We’ll be sure to share regular updates on this blog as the Apache proposals progress, the Flex Community Summit content is posted and cities/dates are finalized for the 2012 Flex User Group tour.
Group Product Manager, Adobe
A security patch for the Flex SDK is now available to address a vulnerability that will cause many Flex applications to be vulnerable to cross-site scripting (XSS) attacks. These applications must be patched in order to protect user data. Please review this bulletin to determine if your applications are at risk and to obtain instructions on how to patch your applications.
If you have any questions about the security bulletin, please email PSIRT@adobe.com