incubator-flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Blaine Bradbury <>
Subject Re: Apache Flex roadmap page in the wiki [was: I was tired of waiting.]
Date Tue, 02 Oct 2012 01:10:30 GMT
On the Roadmap issue:

I think it would be EXTREMELY useful to have a device which could show the
current (as close to the present knowledge as is really manageable)
trajectory that the Apache Flex project is taking.  On any given day, there
are folks hard at work contributing new things with the intention to finish
them.  They may never do so.  In some cases, they may have
expressed commitment in their own right... beyond any Apache requirement
per se.  In other cases, the work could have a lot of support in the
community and therefore pretty likely to move forward.

Bottom line is that these ongoing efforts do tell a story and show a
certain geographical map toward an apparent goal that is shaped as it
happens.  I would love to see a Road map of this geography.  I would love
to share this story with customers and colleagues.  I also believe that
folks who wish simply to consume the software and develop applications out
in the market place could use this type of tool.  And those folks on some
level are the people who will give Apache Flex a future by keeping code in
production in the market place... possibly providing jobs.

A Road map shows details of roads in a handy overview where one can
rationalize roads according to existing geography, yes?  A Road map is a
device one might use to help one get from one place to another using roads.
 The information in a Road map is only as good as it as at the time of
publishing.  New Roads are created all the time.  New editions of a Road
map are published to show changes.  In our case, the Road map could show
intended paths... in italics or some such demarcation.  An idea list or a
wish list sounds hypothetical, not intentional.

Road map is easier to say than *"What we are planning to do at the moment
before we individually or collectively decide to change our minds List."*  But
I do think this disclaimer could be in nice obvious print just below the
heading :)

Also to note.  The content of the Road map will not magically post itself
somewhere, and it will probably have little value unless people contribute
or share.  This is very much like the rest of the Apache Flex ideal, yes?
 The folks who have wanted a Road map have only asked that it be allowed to
exist if they create it, so that they might try to make it work.  The more
obvious things being worked on are mostly likely the content targets
anyhow.  A single source for logging feature progress and showing revision
history is just easier for some than weeding through mountains of e-mail
and monthly status summaries.  Why not allow them to put a page up and
status how they see fit.  If it sucks... kill it later.

Lastly, I like the term "Road map", but I understand the objections.  I am
also very protective of language that might be under attack.  Corporate
america does not get to monopolize the term and force the image of
stressful project management and quarterly timelines onto the term for the
rest of us unless we let them.


On Thu, Sep 13, 2012 at 1:54 PM, Omar Gonzalez <>wrote:

> It looks like it generated a roadmap.html page that it didn't clean up when
> the page was renamed.
> Not sure if it can be removed.
> -omar
> On Thu, Sep 13, 2012 at 10:25 AM, Raju Bitter <
>> wrote:
> > Thanks, Omar. That's what I guessed, I remember that the roadmap wiki
> > page was changed long ago. Strange that the old page is still online.
> >
> > - Raju
> >

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message