From what I have understood today, this seems like a nice option to me to straighten things out.

+1

-Harish

Dirk Verbeeck wrote:

+1

If this is acceptable by the board then it's the ideal solution.
No changes to the email/website structure, jakarta remains the center of the apache java development with a shared announcement list, general list, news and download pages, ...


The only change is that the board gets a list of members overseeing each project (=PMC) and additionally a "Jakarta Community" project building a java community at Apache. (assisting the java projects)
The board will not get one big report from jakarta but many small ones and can see witch (sub)projects needs more members.


Of course many members will be joining multiple PMCs.
Is this possible?

-- Dirk



Noel J. Bergman wrote:

There is a difference between a hierarchy and a confederation.  There is
absolutely nothing that says that we cannot have:

  Jakarta PMC: responsible for jakarta-site/jakarta-site2
  Tomcat PMC: tomcat and related code
  Struts PMC: struts and related code
  Jakarta Commons PMC: ...
  Tapestry PMC: ...
  ...

All without a single change to the Jakarta domain.

No one should feel that there is any relationship between the Foundation's
legal structure, and e-mail/web addresses. We have had this confirmed
already by both Greg and Sam. The above *is* an acceptable solution to the
Board. The question is whether or not it is an acceptable one to us.


--- Noel





--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to