flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Harui <aha...@adobe.com>
Subject Re: State of the Project
Date Mon, 23 Jan 2012 20:52:50 GMT

On 1/23/12 12:42 PM, "Martin Heidegger" <mh@leichtgewicht.at> wrote:

> On 24/01/2012 05:03, Alex Harui wrote:
>> Yes, there can be separate branches and release.
> Then that should be mentioned in the "versioning" thread, shouldn't it?
It has been mentioned in past versioning threads.

>> IMHO, Apache is more about what actually happens, not so much about promises
>> and visions and missions.  The missions can get changed, forked, killed,
>> whatever.  It all depends on who actually gets something done.
> If its like that: Why do we need memberships then? I mean seriously:
> Libspark is such a platform.
> They allow the project to go into the direction that the various members
> choose, basically everyone
> can become commiter. Releases are purely interest driven and we do not
> need discussions like "do we need that".
You can read up on Apache history.  Other than the initial committers, other
committers earn their rights to be a committer.  It isn't completely open,
which I am thankful for.
> As far as I can tell though: that is not what many people see in the
> responsibility of Apache Flex. Many companies (i guess including Adobe)
> expect Apache Flex to maintain/improve on to the former releases as they
> built their businesses on flex as a platform.
I think that's true, but I also heard loud and clear at the summit that a
migration strategy is important so it is on my list of things to do, and it
sounds like others are willing to join in.

> On 24/01/2012 05:20, Greg Reddin wrote:
>> You nailed it Alex! An Apache project is all about what we make it. It
>> is nothing about what we say we might make it someday :-)
> Many threads are motivational nature i.e: "Would <x> be interesting?"
> "Would <z> make sense?" etc. Those are questions that programmers that
> think ahead put in before they write code. Before investing times and heart.
>> Let's figure out what a release contains, then we can figure out what
>> to call it. 
> That is what I was talking about. How can you select something for a
> release without knowing what kind of thing it is you want to release at
> first place?
Read the Apache docs on releasing.  Anyone can volunteer to be a release
manager, it apparently we don't have to release the entire source code
repository each time.
> Also: Apache seems to be rather picky about what things are. There is a
> apache project and a apache tomcat project. Both webservers, could be
> hosted as the same project, right, but isn't? So, again: what does this
> Flex now stand for anyways? Anything people work on? Would Apache be
> okay with that?
My goal is to make Flex useful for those with short term needs by fixing
bugs and making incremental improvements, and to get going on a longer term
future that might involve alternative technology stacks.  And so far, Apache
is ok with that.

Alex Harui
Flex SDK Team
Adobe Systems, Inc.

View raw message