Just chiming into this dead horse.
The problem with projects that get donated to Apache from an
established Enterprise is what has previously happened in this
project, warped perspectives.
Roadmaps in the English language say "there are roads to travel". In
Apache, we say "roads, who needs roads where we are going there are no
roads...". Oh I know that was cheesy and I'm not that geekey but the
sentiment is true.
I look at my experience, I have developed Flex components for about 8
years. Hum, my road map in life says, keep developing Flex components.
But the great thing about this project is I can do whatever I want to
do and right now I am working with the new Falcon compiler.
In the enterprise world, smart educated university graduates would
look at me and say, he is wasting time, killing the project since he
is not giving us the "Missing Flex components", that is priority over
a compiler that doesn't even parse MXML correctly yet!
I left this project for 8 months thinking my days of Flex was over.
Mysteriously life brought me back right when the compiler was donated.
You see, opensource at Apache has to do with innovation and
experimentation with no rules.
In the spirit of honesty, sometimes I look at all the component bugs
and requests and say to myself, you know I could do a lot here. I have
a lot of experience to move this forward. But the renegade in me says,
I'm working on the compiler because it brings joy to me. This is why
Apache does not use roadmaps, they know taking away developers joy in
project means certain death and a ghost town soon to follow.
Mike
Quoting Omar Gonzalez <omarg.develo...@gmail.com>:
On Mon, Oct 1, 2012 at 11:21 PM, Métairie, Stéphane <serial...@ebu.ch>wrote:
This page shown a rudimentary but interesting Roadmap that doesn't come
magically by itself there ;)
https://cwiki.apache.org/confluence/display/FLEX/Status+of+Project
No, it doesn't automatically appear there. People that are working on Flex
have to update it, but guess what? Nobody is updating it. They're probably
not updating it because they would rather spend their time working on Flex.
As a committer I hardly have time to mess with Flex, when I do have that
time, I am not going to spend it playing with a Wiki. I'm going to spend it
playing with Flex. I'm sure others feel similar, or this status page would
have more information in it.
I'm insisting that Decision Maker won't drill down the web site to reach
the confluence wiki to find this page, won't subscribe to this list, etc.
So if a decision maker isn't going to look for the "Status of Project" page
then what makes you think they'll drill down the web site to search for a
roadmap?
The final aim (for a volunteer-based project too) is the Flex life
continue, isn't it?
Yes. A roadmap isn't going to prolong the life of Flex. But people
committing, making patches and contributing will.
Omar Gonzalez
s9tpep...@apache.org
Apache Flex PPMC
--
Michael Schmalle - Teoti Graphix, LLC
http://www.teotigraphix.com
http://blog.teotigraphix.com
