In theory, Apache is more about community than code. Source code in Apache is supposed to be there because the original contributor feels like it would be better for more folks to contribute to continued development of the source code.
Certainly you could argue that code being donated from Adobe doesn't conform perfectly to these guidelines. Apache Flex is warehousing source code that you could argue is not going to see active development, but that's because I think it is better to have the source code in Apache just in case someone does need to fix a bug in it. So for your code, the question is whether you want other folks to contribute to it. If you want to maintain some sort of control over what gets checked in, then maybe it isn't a good fit for Apache. And then there is the question of whether there are is a community of folks who want to contribute to your code. I have no problem putting links on the Apache Flex site pointing to your site as a member of the greater ecosystem of Flex and ActionScript. Apache Flex doesn't need to own every line of code anyone ever puts in their apps. Now, if you want to start over with a new text layout engine, the FlexJS framework I am working on will need something like that eventually. Over time it will need to achieve parity with what is possible in HTML and Adobe is demoing the CSS Regions capability and we will need to match it. TLF is too heavy for my liking and I want to have fewer mismatches with HTML text layout. And when I get started on that, someone like you with experience will be welcomed. Also, you don't have to wait for me, you are welcome to start on it yourself by offering up code. HTH, -Alex On 2/26/13 5:54 AM, "Daniel Freeman" <madcompone...@gmail.com> wrote: >> How do you see the project as a whole being useful as a donation... from > the perspective of Apache? > > Possibly as a cool showpiece for the capabilities of TLF. But I'm ok if > Apache doesn't want to receive this. If there's enough interest in it - I > might release the code as open source anyway - on github or google-code. > > As I said, I can lend some advice and guidance to the development of your > text wrapping Flex component. > > I'd just like to explore - - do you think there would be any interest from > Apache for my other projects? MadComponents and MC3D. > > MadComponents is a popular alternative to mobile Flex. > http://madskool.wordpress.com/2012/01/23/why-developers-are-using-madcomponent > s/ > > MC3D is my Stage3D enhancement to MadComponents, transitions and effects. > See: http://www.youtube.com/watch?v=S5mx9YVDmyo > > The justification in Apache managing these would probably be that they are > popular with AIR/Flash-Platform developers. I'm almost ready to let go a > bit, and allow other developers more contribution. Apache would be a great > way to manage this transition - if you feel it comes under your remit. > Just an idea. > > > > On Tue, Feb 26, 2013 at 10:45 PM, Harbs <gavha...@gmail.com> wrote: > >> Here's all issues sorted by popularity: >> >> https://issues.apache.org/jira/browse/FLEX#selectedTab=com.atlassian.jira.plu >> gin.system.project%3Apopularissues-panel >> >> Number 1 is a Maven/Flexmojos build: >> https://issues.apache.org/jira/browse/FLEX-33086 >> >> On Feb 26, 2013, at 2:20 PM, Daniel Freeman wrote: >> >>> Out of interest, what new feature has the most number of votes ? >> >> -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
