The component list was developed reviewing the emails on the mailing
list as we as the Flex White Paper. The component list was provided
earlier with the request for corrections but none were forthcoming.
Given that Adobe's resource commitment is not indefinite it would be
most appropriate to dedicate the remaining time (it would be nice to
have some idea what that is) on things that are considered a priority
(do we want effort to be spent on Gravity?). The same can be said for
non-Adobe contributors, many of whom have are fighting to retain the
businesses they have built over the past 4-5 years. At the vary least
the survey will provide a concrete frame of reference based on community
opinion that can guide day-to-day passions/swings. Apache Flex isn't
your average open source project with no customer base that can afford
to spend the next few years defining and developing the technology.
On 8/1/2012 7:25 PM, Jeffry Houser wrote:
On 8/1/2012 8:22 PM, Alex Harui wrote:
Keith,
I appreciate the effort, and more data is welcome, but I don't think
Apache
projects have roadmaps or make commitments on what is going to be
delivered
next. No consensus has to be reached on what will be worked on.
Folks are
free to do what they want.
Thanks for saying that. :-) I think a lot of folks are having
trouble getting their head around the "no roadmap / do what you want"
approach of Apache.
I can see, however, that this could be a good (or at least different)
way to collect information than the Jira bug base. If a lot of people
are asking for "X" or "Y" it may motivate some people to work on "X"
or "Y".
I also don't understand the items on the survey. Automation, Samples
Themes, FABridge and Flash Integration were all donated and are the 4.8
release. The MXMLC compiler code is as well.
And in my own experience, FXG works just as well with Apache Flex 4.8
as it did with Adobe Flex 4.6 .
I have no idea what "Gravity" is from that list. I assume the code
name to some Adobe pre-release that I never heard of.
