Federico Barbieri wrote:
Stephen McConnell wrote:Federico Barbieri wrote:Afaik there is not *one* line about how to restructure jakarta.
This is totally true - our area of interest and scope of concern is Avalon, not Jakarta.
:-)
these words enforce my feeling you're "forking".
:-)
As Pete pointed out in an earlier reply, a context was established under the reorg list during which the Avalon project was referenced on several occations. During this process, members of the Jakarta PMC and the Apache Board encoraged the Avalon community members to assess the project and its relationship to the overall Apache community. Throught this process there has been a constructive relationship betwen this community and its PMC with the open exchange of opinions, concerns and constructive comments as we have moved forward. I think that on review you will find a solid and consistent platform of people working together towards a common objective.
Two threads that I make good brackground reading include the following:
http://marc.theaimsgroup.com/?t=103681137000001&r=1&w=2
http://marc.theaimsgroup.com/?t=103691454800002&r=1&w=2
If you think the apache community avalon framework wise, what you are doing is forking the framework specification because you want to have a different container implementation.
just my thought
If you review the threads on the Avalon PMC, I think you will arrive at the conclusion that the avalon framework is the fundamental backbone, however, I think you will also find that discussions about the framework, containers, etc., are largely technical in nature and as such are matters for the committer comunity. What the PMC has to address is a charter, rationalization, and overarching objective of deliving good quality open source solutions within our area of concern.
Cheers, Steve.
Not sure I got your point here. Maybe I've used the wrong example. Let the code speak... :)
public abstract class JakartaProject { /** author: Jakrta PMC **/ /*this could extend ApacheProject but... */
public static final boolean isOpenSouce = true;
public static final String licence = ApacheProject.APACHE_LICENCE;
public abstract String getName();
public abstract String getCharter();
public synchronized void addCvsCommitter(Developer developer) {
/* place reference implementation here */
}
}
public class Avalon extend JakartaProject { /** author: Avalon committers **/
.....
public synchronized void addCvsCommitter(Developer developer) {
/* place avalon optimized implementation here */
}
}
What you're saying is there are methods in the JakartaProject class that are final and you don't like so you don't want to extend JakartaProject anymore.
Actually, extension of the Jakarta project was the subject of a thread on the rorg list which subsequently migrated to the Avalon dev list - however, the reality of building the notion of a sub-structure proved productive. As discussions continued (involving the Jakarata PMC, Incubator PMC and members of the Board), the concept of an Avalon PMC become more focussed. I think you will will find lots of evidence of loyalty from member of Avalon towards Jakarta and from Jakarta towards Avalon in both the process and the vision (as opposed to forks or approaches). This is something that involves several communities and I'm very please to say that their representation in this process has been suprisingly open.
What I'm saying is to take away the final word and overwrite them. If the getNewCvsModule method implemented in the JakartaProject class is synchronized and it's too damn slow then write a multithreaded one for all subclass to benefit.
I'm code addicted... sorry about that! :)
:-) Think of this more along the lines of refactoring a part of your code base.
Anyow could you give me a more specific example of what would be different in the Jakarta and Avalon PMC?
A PMC by the people, for the people.
By this I mean a PMC composed of members of the Avalon community working to better server the members of the Avalon Community, and the development of that community in the context of Apache goals and culture.
Cheers, Steve.
--
Stephen J. McConnell
OSM SARL
digital products for a global economy
mailto:mcconnell@;osm.net
http://www.osm.net
--
To unsubscribe, e-mail: <mailto:avalon-dev-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:avalon-dev-help@;jakarta.apache.org>
