On 2/6/2001 at 11:45 PM Ceki Gülcü wrote:
>My guess is that when all strictly sub-project related tasks are
delegated to the committers, the PMC could fulfill its role even in the
presence of many, say 10 to 20 sub-projects. Am I missing anything
obvious? Cheers, Ceki
Counting what's coming over from Java Apache, we already over 20
subprojects -- and there's talk of dividing Avalon up into at least
three subprojects, and Tomcat into two. ;-).
There's also a feeling that the PMC should have a working knowledge on
what each subproject is doing, to be sure they retain scope, and to
suggest linkages between the products. With seven PMC members, that's
three unique products each. Though, given the calibre of people on the
PMC now, that's actually within tolerance.
Using Brian Behlendorf 's hierarchy:
< Servlet API >
JServ - a servlet engine implementating the Java Servlet 2.0 API.
Tomcat - the Reference Implementation for the Java Servlet 2.2 and
JavaServer Pages 1.1 APIs.
Watchdog - validation tests for the Servlet and JavaServer Pages
specifications
< Template Engines >
Taglib - a JSP taglib repository.
Velocity - a template engine providing an alternative to Java Server
Pages (JSPs) or PHP.
ECS - the Element Construction Set generates elements for various
markup languages.
JSSI - a Java servlet that implements the <SERVLET> tag as specified by
the Java Web Server.
SPFC*
< Development Tools >
Alexandria - a CVS/Javadoc/Source code/Documentation management system.
Ant - a Java based build tool.
ORO - a set of text-processing Java classes that provide Perl5
compatible regular expressions.
RegEx - a regular expression package for Java.
JMeter - a desktop application load test functional behavior and
measure performance.
Logj4 - a tool to help the programmer output log statements to a
variety of output targets.
Jyve - a servlet-based FAQ-O-Matic system.
< Frameworks >
Jetspeed - an enterprise information portal.
Struts - a Model 2 (MVC) application framework.
Turbine - a servlet-based framework for experienced Java developers.
< "Other Server-Based" >
Avalon - a common framework for server applications
JAMES - an enterprise mail server (Java Apache Mail Enterprise Server).
Slide - a WebDAV content management system.
Picoserver - lightweight 100% Java HTTP/1.0 server
Cocoon - publishing framework using new W3C technologies (such as DOM,
XML, and XSL) to provide web content.
*********** REPLY SEPARATOR ***********
On 2/6/2001 at 11:45 PM Ceki Gülcü wrote:
>At 16:01 06.02.2001 -0500, you wrote:
>>On 2/6/2001 at 9:13 PM Ceki Gülcü wrote:
>>
>>>What would be gained by refining the charter of Jakarta and pruning
>>projects?
>>
>>Roy Fielding has indicated that some action is necessary. His two
>>suggestions were to either ask the board to create additional PMCs,
or
>>to broaden the scope of the existing PMC.
>>
>>> What decisions does the PMC take?
>>
>>Part of the problem is that the ASF PMC's are a recent invention, so
no
>>one is entirely sure how they should work
>>
>>We are working on that as part of the update to the guidelines at <
>>http://jakarta.apache.org/site/proposal.html#management >.
>
>Thanks for the link. Here is an excerpt from that document:
>
> Responsibilities of the PMC include:
>
> - the active discussion of Project issues, strategic direction, and
forward progress,
>
> - the consideration and approval of new subprojects,
>
> - retiring inactive subprojects and Committers as necessary,
>
> - arbitrating otherwise intractable disputes regarding subproject
voting and vetos,
>
> - the security and reliability of the Project's Web site, mailing
> lists, code repositories, and related services,
>
> - legal issues involving the Project and its subprojects, and
> maintaining Project and subproject scope as chartered by the ASF
corporation
>
>
>As I understand it, the main responsibility of the PMC is to decide
whether to include a sub-project under the Jakarta label and possibly
act as an arbitrator in case of conflicts within a sub-project. There
is also the task of managing the Jakarta web-site + mailing lists but
that is probably less strategic a task (read: a chore). :)
>
>My guess is that when all strictly sub-project related tasks are
delegated to the committers, the PMC could fulfill its role even in the
presence of many, say 10 to 20 sub-projects. Am I missing anything
obvious? Cheers, Ceki
>
>
>----
>Ceki Gülcü e-mail: [EMAIL PROTECTED] (preferred)
>av. de Rumine 5 [EMAIL PROTECTED]
>CH-1005 Lausanne
>Switzerland Tel: ++41 21 351 23 15
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
-- Ted Husted, Husted dot Com, Fairport NY USA.
-- Custom Software ~ Technical Services.
-- Tel 716 425-0252; Fax 716 223-2506.
-- http://www.husted.com/about/struts/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
