The survey/roadmap are definitely in line with your guidance and will
likely be called "Community Objectives and Priorities for Apache Flex"
and would be posted on the Spoon website. Although it cannot be binding
it does act as:
1) An expression of the community and their collective input to what
should be a objective/priority in the next 6 months (4.9/5.0 ?)
2) Feedback on the priorities of effort from Adobe (there was mention of
a 'delivery schedule', it would be good to expose that) as some elements
like Gravity may be of no interest and therefore not worth expending
limited resourses);
3) a vehicle to engage people in the project.
- in the short term people who want to work on things can use it
On 8/3/2012 5:01 AM, Bertrand Delacretaz wrote:
On Fri, Aug 3, 2012 at 1:56 PM, Justin Mclean <jus...@classsoftware.com> wrote:
...There nothing saying we can't have roadmaps (AFAIK) and several other Apache
projects do have them.
For example http://subversion.apache.org/roadmap.html...
Agreed - it''s just that such roadmaps can easily fail, if they're too
ambitions, and people are disappointed.
...We just need to be a little careful and make it clear that it's not a
roadmap in the traditional sense ie a list of
features that are planned to be done by a certain date....
Yes, it's more a list of goals and priorities IMO - as the amount of
effort that people put into an Apache project is unpredictable, and as
reaching consensus sometimes takes longer than expected, I wouldn't
put any dates on such a list.
If the roadmap is driven by an external entity, please use a distinct
name. If Spoon is driving a roadmap/wishlist, calling it "Spoon
Roadmap" as John suggests is perfectly fine, calling it "Apache Flex
roadmap" is not ok.
-Bertrand
