Keith, I'm sorry I did not respond to your first roadmap email. Honestly, I stopped reading after your first bullet point raising FUD about whether Adobe would live up to its commitments without any quoting of the statements behind your logic. I almost responded, but when nobody else did, I just hoped it would die. Yes, I could end up being very surprised in November 2012, but Adobe has put a stake in the ground in their roadmap document and I expect to see us live up to it.
I know lots of folks have an instinctive desire to organize Apache Flex, but to me, the key to success is that the Apache Way does not require this level of organization and decision making and we will save time and make more progress by not trying to get that organized. It isn't total anarchy either, it is a proven way of managing a group of volunteers spread across the world. I certainly wish more committers were committing more stuff, and surveys are great, but surveys have the limitation of limiting the discussion to the content of the survey. Yes, you can have your open questions, but you've already led the witness. For example, Maven support was the #1 vote getter at Adobe and I have trouble believing it isn't important anymore, but it wasn't a choice on the survey. The Apache Way as I understand it, is that folks who have a need can file a JIRA issue and/or ask on the mailing lists about it. Then there is no cut-off for answering a survey, and folks can talk about what is bugging them when it is bugging them. On 8/1/12 10:26 PM, "Keith Sutton" <ke...@spoon.as> wrote: > 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. >> >> >> >> > -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
