Flex 3 Contributions

One of the exciting things about an open source project is the many ways to contribute to it. The most visible method of course is to contribute code, and there are plenty of places to do that. While the Flex team itself does work to fix bugs, we also are hard at work innovating on the next release, which means we may not fix as many bugs as we'd like. Therefore, there are plenty of opportunities to get your feet wet in understanding the details of the SDK by fixing a bug or two (or 10). In fact, almost all new members of the Flex team start out by fixing some bugs in order to learn the framework.

To make it easier to know what bugs are good candidates for community fixes, we've created a new milestone in JIRA. There is now a shared filter that you can use to see any bug that might be a good one for a community member to fix. We encourage you to review the Submitting a Patch page and file a contributor agreement, then go ahead and fix a bug or two (remember to indicate in a bug comment that you're starting a fix so that folks don't overlap)!

As an extra incentive we're implementing the following program.

• For every 3 bugs where we accept and commit your submitted patch, we will purchase an Adobe-related book from your Amazon wish list (once you've had your 3rd patch accepted we'll reach out to you to find your wish list).
• For the first two contributors to have 10 patches committed, we'll pay for your MAX 2008 registration (any region).

There are milestone releases of the Flex 3 SDK planned for the Summer and Fall of 2008. Wouldn't it be cool if you were able to say that you had a part in them?

Feel free to ask any questions about this program on the General Discussion forum. If you're working on a specific bug and want to float some ideas by the developers, go ahead and reach out on the Developers forum.

See the bugs

Incentive Program Rules (subject to adjustment at any time)

• You must follow our Coding Conventions
• You must be a citizen of Earth (no proof required)
• You must be helpful in providing book options in your wish list that won't get the Flex team fired if we buy it
• You must not deluge the system with silly bugs in an attempt to provide fixes