danny 2003/01/18 07:44:02
Modified: proposals/TLP proposal-letter.txt proposal-template.txt
Log:
I think that these are now ready, pending the result of the PMC vote.. if you have a
vote use it NOW pls :)
Revision Changes Path
1.4 +30 -16 jakarta-james/proposals/TLP/proposal-letter.txt
Index: proposal-letter.txt
===================================================================
RCS file: /home/cvs/jakarta-james/proposals/TLP/proposal-letter.txt,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- proposal-letter.txt 18 Jan 2003 02:33:41 -0000 1.3
+++ proposal-letter.txt 18 Jan 2003 15:44:02 -0000 1.4
@@ -1,3 +1,4 @@
+
Jakarta-James Proposal for adoption as an Apache top-level project
----------------------------------------------------------------------
@@ -50,9 +51,9 @@
feel that top level project status, emphasisng its function rather
than its platform, would suit James well.
-The proposals being discussed on reorg & community include the notion
-of federated projects. We would like to think that we wouldn't be
-leaving Jakarta, just growing up.
+The proposals discussed and being discussed on reorg & community
+include the notion of federated projects. We would like to think that
+we wouldn't be leaving Jakarta, just growing up.
We also know that James would continue to rely on Jakarta for code,
insight and knowekdge, but we don't need to be a Jakarta sub-project
@@ -64,7 +65,7 @@
This proposal is more about management than web-site and mail
addresses. We don't expect that james.apache.org will bring many
direct benefits, but we do think that normalising our relationship
-with Jakarta by becoming a sibling rather than a child, and taking
+with Jakarta by becoming a peer rather than a child, and taking
official control of all the issues we currently inherit and
"interpret" from Jakarta would benefit James.
@@ -72,7 +73,8 @@
recourse to the Jakarta PMC, and equally seldom are we scrutinised by
them. We are perhaps not the most active project, and some of us may
feel that this sometimes causes James to be disregarded. Likewise,
-apart from Avalon, we have few direct ties with other Jakarta projects.
+apart from Avalon (iteslf now a top-level project), we have few direct
+ties with other Jakarta projects.
----------------------------------------------------------------------
Profile:
@@ -92,7 +94,7 @@
java.apache.org, before Jakarta was organized. Individuals
(unfortunately names forgotten at this point) had submitted a proposal
to the (HTTP) servlets group at Sun to provide mail handling. They
-rejected the proposal due to technical reasons.
+rejected the proposal for technical reasons.
Serge Knystautas later donated a Java SMTP server implementation that
became the original codebase for JAMES. The mailet API was heavily
@@ -102,7 +104,7 @@
JAMES was later refactored to use the new Avalon codebase. JAMES also
received a donation of an NNTP implementation. JAMES has slowly added
new mailets, improved reliability and scalability, SMTP AUTH,
-FetchPOP, and other small feature enhancements since then.
+FetchPOP, and other feature enhancements since then.
----------------------------------------------------------------------
Future:
@@ -110,7 +112,7 @@
Our vision of the future for James contains three main foci,
1/ To continually improve the performance and functionality of the
-core services. Currently focusing on making IMAP stable and
+core messaging services. Currently focusing on making IMAP stable and
increasing fault tolerance across the board.
2/ To promote the Mailet API as a standard API (providing portability
@@ -130,7 +132,7 @@
ezmlm.
- Implementing a number of related services defined by RFC's, such as
the email aspects of Icalendar, Vcard to name but two.
-- And offering greater interoperability with other mail applications,
+- And offering greater interoperability with other mail applications,
such as sendmail.
----------------------------------------------------------------------
@@ -138,10 +140,10 @@
----------------------------------------------------------------------
The James community is small, but focused and self-sustaining,
comprised of six active commiters, and six currently inactive.
-Only one of the active commiters, Serge Knystautas has been associated
-with the project since it started, and the continued success of James
-is no longer dependant on his continued participation.
-(DA: Sorry Serge, mate, but thats a *good* thing! SK: Amen!)
+Only one of the active commiters, Serge Knystautas, has been
+associated with the project since it started, and the continued
+success of James is no longer dependant on his continued
+participation.
Our developer community includes a number of Avalon contributers and
commiters, and a number of people who are working with or on James in
@@ -150,11 +152,23 @@
Our user base is hard to quantify, but includes a wide cross section
of different classes of users, from individuals through small
enterprises looking for big enterprise mail functionality, commercial
-users adapting James or using James to provide bespoke services
+users adapting James or using James to provide bespoke services
through to students using James in their coursework.
We believe that this represents a healthy interest in James, and the
fact that James continues to be of interest to so many groups inspite
of the existence of email server software with much higer profiles,
-sendmail, exchange etc, is perhaps better proof of its worth than is
-its market share in comparison with those goliaths.
+sendmail, Microsoft Exchange etc, is perhaps better proof of its worth
+than is its market share in comparison with those goliaths.
+
+
+----------------------------------------------------------------------
+Conclusion
+----------------------------------------------------------------------
+We believe, as we hope we have shown, that James is a mature and
+worthwile candidate for inclusion as a top level Apache project, and
+hereby take the opportunity of presenting our proposal for
+consideration by the Board of Directors.
+
+On behalf of The James commiters,
+Danny Angus
\ No newline at end of file
1.2 +24 -22 jakarta-james/proposals/TLP/proposal-template.txt
Index: proposal-template.txt
===================================================================
RCS file: /home/cvs/jakarta-james/proposals/TLP/proposal-template.txt,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- proposal-template.txt 21 Nov 2002 10:40:53 -0000 1.1
+++ proposal-template.txt 18 Jan 2003 15:44:02 -0000 1.2
@@ -1,54 +1,56 @@
- <name>
- <scope-statement>
- <list-of-PMC-members>
- <chair>
WHEREAS, the Board of Directors deems it to be in
the best interests of the Foundation and consistent with
the Foundation's purpose to establish a Project Management
Committee charged with the creation and maintenance of
- open-source software related to component and service
- management, for distribution at no charge to the public.
+ open-source software related to the Apache James E-Mail server and
+ the Apache Mailet API, for distribution at no charge to the public.
NOW, THEREFORE, BE IT RESOLVED, that a Project Management
- Committee (PMC), to be known as the "|<name> PMC", be and
+ Committee (PMC), to be known as the "Apache James PMC", be and
hereby is established pursuant to Bylaws of the Foundation;
and be it further
- RESOLVED, that the <name> PMC be and hereby is responsible
+ RESOLVED, that the James PMC be and hereby is responsible
for the creation and maintenance of software related to
- <scope-statement>, based on software licensed
- to the Foundation; and be it further
+ the Apache James Mail and News server, the Apache Mailet message
+ processing API, and related software components based on software
+ licensed to the Foundation; and be it further
- RESOLVED, that the office of "Vice President, <name>" be and
+ RESOLVED, that the office of "Vice President, Apache James" be and
hereby is created, the person holding such office to serve
at the direction of the Board of Directors as the chair of the
- <name> PMC, and to have primary responsibility for management
+ Apache James PMC, and to have primary responsibility for management
of the projects within the scope of responsibility of the
- <name> PMC; and be it further
+ Apache James PMC; and be it further
RESOLVED, that the persons listed immediately below be and hereby
- are appointed to serve as the initial members of the <name> PMC:
+ are appointed to serve as the initial members of the
+ Apache James PMC:
- <list-of-PMC-members>
+ Serge Knystautas
+ Danny Angus
+ Peter Goldstein
+ Noel Bergman
+ Charles Bennet
- NOW, THEREFORE, BE IT FURTHER RESOLVED, that <chair/>
- be and hereby is appointed to the office of Vice President, <name>,
+ NOW, THEREFORE, BE IT FURTHER RESOLVED, that Serge Knystautas
+ be and hereby is appointed to the office of Vice President, James,
to serve in accordance with and subject to the direction of the
Board of Directors and the Bylaws of the Foundation until death,
resignation, retirement, removal or disqualification, or until a
successor is appointed; and be it further
- RESOLVED, that the initial <name> PMC be and hereby is tasked
+ RESOLVED, that the initial Apache James PMC be and hereby is tasked
with the creation of a set of bylaws intended to encourage open
- development and increased participation in the <name> Project;
+ development and increased participation in the James Project;
and be it further
- RESOLVED, that the initial <name> PMC be and hereby is tasked
+ RESOLVED, that the initial Apache James PMC be and hereby is tasked
with the migration and rationalization of the Jakarta PMC
- <name> subproject; and be it further
+ James subproject; and be it further
RESOLVED, that all responsibility pertaining to the Jakarta
- <name> sub-project and encumbered upon the Jakarta PMC are
+ James sub-project and encumbered upon the Jakarta PMC are
hereafter discharged.
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
