noel 2003/01/20 18:48:40
Modified: proposals/TLP proposal-letter.txt proposal-template.txt
Log:
Emphasis positive aspects of TLP, recognize broader scope of messaging
Revision Changes Path
1.8 +36 -32 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.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- proposal-letter.txt 19 Jan 2003 21:40:14 -0000 1.7
+++ proposal-letter.txt 21 Jan 2003 02:48:40 -0000 1.8
@@ -1,10 +1,10 @@
-
Jakarta-James Proposal for adoption as an Apache top-level project
----------------------------------------------------------------------
----------------------------------------------------------------------
Preamble:
----------------------------------------------------------------------
+
To the Board of the Apache Software Foundation.
We, the committers of the Jakarta sub-project jakarta-james have held a
@@ -18,7 +18,10 @@
Introduction to James:
----------------------------------------------------------------------
-James is a 100% Java mail and news server.
+James is a 100% Java mail and news server, evolving into a complete
+electronic messaging solution that integrates the range of IETF
+protocols, such as SMTP, POP3, IMAP, NNTP, and XXMP with unified user
+account management and open storage mechanisms.
James provides highly configurable SMTP mail transport and local
delivery into POP3 or IMAP accounts, utilizing file system or database
@@ -26,7 +29,7 @@
The jakarta-james sub-project hosts the Apache Mailet API specification
The Mailet API is a Java API providing a framework for the conditional
-processing of mail and news messages.
+processing of electronic messages.
James implements the Mailet API, and as such is itself a platform for
Mailet applications. Applications providing custom mail
@@ -42,39 +45,37 @@
----------------------------------------------------------------------
General:
----------------------------------------------------------------------
-Some believe that Jakarta is becoming too big to function as a single
-project, that community and culture become diluted as you descend the
-hierarchy and that one solution is for mature projects leave the nest.
-
-Of course other projects are free to make their own choices but as
-James consists primarily of the server which is an end-user product we
-feel that top level project status, emphasizing its function rather
-than its platform, would suit James well.
-
-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 knowledge, but we don't need to be a Jakarta sub-project
-to benefit from that.
+
+James is a mature, self-determining project that is able to govern
+itself under the auspices of the ASF Board in accordance with ASF
+bylaws and guidelines.
+
+As James consists primarily of the server which is an end-user product
+we feel that top level project status, emphasisng its function rather
+than its platform, would suit James well. Top level project status
+would also facilitate the ability to offer the Mailet API as an
+separate specification, of which James would represent only a
+reference implementation.
+
+James would continue to work closely with the Avalon Project, and is
+establishing ties with the Cocoon and BSF projects to integrate some
+of their technologies within James.
----------------------------------------------------------------------
Project Management:
----------------------------------------------------------------------
-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 normalizing our relationship
-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.
James has a small yet mature self-sustaining community, we seldom seek
-recourse to the Jakarta PMC, and equally seldom are we scrutinized by
+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 (itself now a top-level project), we have few direct
-ties with other Jakarta projects.
+apart from Avalon, we have few direct ties with other jakarta projects.
+
+We believe think that normalizing our relationship with the ASF Board
+by becoming a direct subordinate rather than a distant step-child, and
+taking official control of all the issues we currently inherit and
+"interpret" from Jakarta would benefit James.
+
----------------------------------------------------------------------
Profile:
@@ -109,7 +110,7 @@
----------------------------------------------------------------------
Future:
----------------------------------------------------------------------
-Our vision of the future for James contains four main foci,
+Our vision of the future for James contains five main foci,
1/ To continually improve the performance and functionality of the
core messaging services. Currently focusing on making IMAP stable and
@@ -126,10 +127,13 @@
more sophisticated, behaviors which would be available to any
application implementing the Mailet API.
-4/ Provide a common repository abstraction to all of James' protocol
-servers (SMTP, POP3, NNTP and IMAP) and support standard repository
+4/ Provide a common message repository abstraction to all of James' protocol
+servers (e.g, SMTP, POP3, NNTP and IMAP) and support standard repository
data formats like maildir and mbox to ease migration to James.
+5/ Provide a common user repository abstraction to all of James' protocol
+servers.
+
These plans include:
- Providing functionality capable of reproducing services provided by
commercial and open source competitors such as Microsoft Exchange, or
@@ -175,4 +179,4 @@
consideration by the Board of Directors.
On behalf of The James committers,
-Danny Angus
\ No newline at end of file
+Danny Angus
1.3 +0 -2 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.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- proposal-template.txt 18 Jan 2003 15:44:02 -0000 1.2
+++ proposal-template.txt 21 Jan 2003 02:48:40 -0000 1.3
@@ -1,4 +1,3 @@
-
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
@@ -53,4 +52,3 @@
RESOLVED, that all responsibility pertaining to the Jakarta
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]>
