Berin Loritsch wrote:
I am glad we are finally considering a true Avalon PMC.
:-)
+1I have long thought that we would be a good candidate for a top level project, maybe even more than one. Other than standard legalese for all PMC charters, we should look at what we explicitly desire for the Avalon PMC.
I recall posts on the reorg and the community mailing lists about starting a new Avalon from the basics, aka framework, and build up.
My comments below follow this line of reasoning.
As to the explicit wording, I am not shure. However, I am looking at it in this way: Avalon Framework: establishes the contracts, rules, and expectations of Avalon components. (note that those intangible qualities can be expressed in code)
This is where we should start from.
> Avalon Cornerstone: collection of Avalon componentsAvalon LogKit: the logging toolkit it always has been. Avalon Excalibur: enabling technologies for Avalon components.
> (since we should have one definition)
>
These three contain stuff that can be divided into three categories: Components/services, utility stuff and containers.
Part of our problems has come from dividing implementations and creating feuds, so I would propose that:
1) the Components/services would eventually migrate to Apache Commons.
not now, not tomorrow, but the path is set, and other projects
like Turbine will follow :-)
2) we keep only *one* set of utility classes called avalon-util
(no more fancy names, pleeease)
3) all containers in the making, like Merlin2 and Fortress
go in the scratchpad dir.
This should *not* be done hastly, it will take time. But we'll get there.
In the end we will have *one* avalon CVS repo, with
./src/framework/**.java
./src/util/**.java
./scratchpad/src/merlin2/**.java
./scratchpad/src/fortress/**.java
Some classes now in framework will go in util too probably, we'll have to vote case by case.
We will start with an empty CVS repo and I will ask votes on all packages and eventually classes, and put in only what we agree on.
This is a very delicate point.Avalon Phoenix: establishes the server, rules, and contracts for hosting server applications.
Phoenix is big, really big. IMV it's at the same level of Avalon, and should be a project in its own right.
I dunno, what do the Phoenix guys think that should be done, given that we should unite?
Anything else is not really fit for the Avalon PMC/direct Avalon umbrella.
Ad we should be *very* clear about what to accept. All tentative stuff goes in /scratchpad, and no individual releases.
I'd defer the decision of Avalon Apps for now, but would suggest Apache Commons for common apps that can be used as components or the incubator for bigger stuff.It was a nice gesture for Avalon Apps, but IMO something like Incubator or SourceForge would have been a better location. Eventually they could have been made top level projects (and some can, like FTP server or proxy server).
It's up to the interested committers though to lead the show on this.
Oh, BTW, I would take up the PMC chair job, and fulfill the role in the most neutral way possible, as a sort of Avalon re-incubation process.
I would resign as soon as the "porting" will be done.
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
--
To unsubscribe, e-mail: <mailto:avalon-dev-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:avalon-dev-help@;jakarta.apache.org>
