You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by se...@apache.org on 2003/01/18 03:33:41 UTC
cvs commit: jakarta-james/proposals/TLP proposal-letter.txt
serge 2003/01/17 18:33:41
Modified: proposals/TLP proposal-letter.txt
Log:
Made small edits and wrote the history section.
Revision Changes Path
1.3 +34 -14 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.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- proposal-letter.txt 21 Nov 2002 11:26:21 -0000 1.2
+++ proposal-letter.txt 18 Jan 2003 02:33:41 -0000 1.3
@@ -17,7 +17,7 @@
Introduction to James:
----------------------------------------------------------------------
-James is a 100% java Mail and news server.
+James is a 100% Java mail and news server.
James provides highly configurable SMTP mail transport and local
delivery into POP3 or IMAP accounts, utilising file system or database
@@ -28,7 +28,7 @@
processing of mail and news messages.
James implements the Mailet API, and as such is itself a platform for
-Mailet applications. Applications providing bespoke/custom mail
+Mailet applications. Applications providing custom mail
processing, such as listservers, or providing gateways into other
systems, messaging systems such as NNTP, SMS or proprietery messaging,
or insertion into non-standard storage media.
@@ -53,39 +53,57 @@
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.
+
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
to benefit from that.
+
----------------------------------------------------------------------
Project Management:
----------------------------------------------------------------------
This proposal is more about management than web-site and mail
-addresses, we don't believe that james.apache.org will bring many
+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
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 scrutinised 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, we have few direct ties with other jakarta projects.
+apart from Avalon, we have few direct ties with other Jakarta projects.
----------------------------------------------------------------------
Profile:
----------------------------------------------------------------------
-As outline above James is composed of three main
+As outline above James is composed of three main areas.
+ JAMES server
Sub-Projects:
- Mailet API:
- Mailet Applications:
+ Mailet API
+ Mailet Applications
----------------------------------------------------------------------
History:
----------------------------------------------------------------------
-### TODO: SERGE you must know most of the history..? ###
+JAMES was originally envisioned and placed as a holding page on
+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.
+
+Serge Knystautas later donated a Java SMTP server implementation that
+became the original codebase for JAMES. The mailet API was heavily
+discussed and finalized, the original code was massively refactored
+and improved, and a POP3 implementation was added.
+
+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.
+
----------------------------------------------------------------------
Future:
----------------------------------------------------------------------
@@ -105,14 +123,16 @@
3/ To build on James' Mailet packages in order to provide more, and
more sophisticated, behaviours which would be available to any
application implementing the Mailet API.
+
These plans include:
-Providing functionality capable of reproducing services provided by
+- Providing functionality capable of reproducing services provided by
commercial and open source competitors such as Microsoft Exchange, or
ezmlm.
-Implementing a number of related services defined by RFC's, such as
+- 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.
+
----------------------------------------------------------------------
Our Community:
----------------------------------------------------------------------
@@ -121,7 +141,7 @@
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.
-(Sorry Serge, mate, but thats a *good* thing!)
+(DA: Sorry Serge, mate, but thats a *good* thing! SK: Amen!)
Our developer community includes a number of Avalon contributers and
commiters, and a number of people who are working with or on James in
@@ -137,4 +157,4 @@
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.
\ No newline at end of file
+its market share in comparison with those goliaths.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: cvs commit: jakarta-james/proposals/TLP proposal-letter.txt
Posted by Danny Angus <da...@apache.org>.
Sounds reasonable.
> I would suggest substituting the word "peer" for "sibling" in the
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: cvs commit: jakarta-james/proposals/TLP proposal-letter.txt
Posted by Stephen McConnell <mc...@apache.org>.
From them revised text:
.... 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
official control of all the issues we currently inherit and
"interpret" from Jakarta would benefit James.
I would suggest substituting the word "peer" for "sibling" in the above. From the point of view of the Board you would be taking on management responsibilities equivialent to Jakarta concerning the autiting of the James project - as such you are a peer.
Cheers, Steve.
serge@apache.org wrote:
>serge 2003/01/17 18:33:41
>
> Modified: proposals/TLP proposal-letter.txt
> Log:
> Made small edits and wrote the history section.
>
> Revision Changes Path
> 1.3 +34 -14 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.2
> retrieving revision 1.3
> diff -u -r1.2 -r1.3
> --- proposal-letter.txt 21 Nov 2002 11:26:21 -0000 1.2
> +++ proposal-letter.txt 18 Jan 2003 02:33:41 -0000 1.3
> @@ -17,7 +17,7 @@
> Introduction to James:
> ----------------------------------------------------------------------
>
> -James is a 100% java Mail and news server.
> +James is a 100% Java mail and news server.
>
> James provides highly configurable SMTP mail transport and local
> delivery into POP3 or IMAP accounts, utilising file system or database
> @@ -28,7 +28,7 @@
> processing of mail and news messages.
>
> James implements the Mailet API, and as such is itself a platform for
> -Mailet applications. Applications providing bespoke/custom mail
> +Mailet applications. Applications providing custom mail
> processing, such as listservers, or providing gateways into other
> systems, messaging systems such as NNTP, SMS or proprietery messaging,
> or insertion into non-standard storage media.
> @@ -53,39 +53,57 @@
> 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.
> +
> 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
> to benefit from that.
> +
> ----------------------------------------------------------------------
> Project Management:
> ----------------------------------------------------------------------
> This proposal is more about management than web-site and mail
> -addresses, we don't believe that james.apache.org will bring many
> +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
> 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 scrutinised 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, we have few direct ties with other jakarta projects.
> +apart from Avalon, we have few direct ties with other Jakarta projects.
>
> ----------------------------------------------------------------------
> Profile:
> ----------------------------------------------------------------------
> -As outline above James is composed of three main
> +As outline above James is composed of three main areas.
>
> + JAMES server
> Sub-Projects:
> - Mailet API:
> - Mailet Applications:
> + Mailet API
> + Mailet Applications
>
>
> ----------------------------------------------------------------------
> History:
> ----------------------------------------------------------------------
> -### TODO: SERGE you must know most of the history..? ###
> +JAMES was originally envisioned and placed as a holding page on
> +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.
> +
> +Serge Knystautas later donated a Java SMTP server implementation that
> +became the original codebase for JAMES. The mailet API was heavily
> +discussed and finalized, the original code was massively refactored
> +and improved, and a POP3 implementation was added.
> +
> +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.
> +
> ----------------------------------------------------------------------
> Future:
> ----------------------------------------------------------------------
> @@ -105,14 +123,16 @@
> 3/ To build on James' Mailet packages in order to provide more, and
> more sophisticated, behaviours which would be available to any
> application implementing the Mailet API.
> +
> These plans include:
> -Providing functionality capable of reproducing services provided by
> +- Providing functionality capable of reproducing services provided by
> commercial and open source competitors such as Microsoft Exchange, or
> ezmlm.
> -Implementing a number of related services defined by RFC's, such as
> +- 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.
> +
> ----------------------------------------------------------------------
> Our Community:
> ----------------------------------------------------------------------
> @@ -121,7 +141,7 @@
> 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.
> -(Sorry Serge, mate, but thats a *good* thing!)
> +(DA: Sorry Serge, mate, but thats a *good* thing! SK: Amen!)
>
> Our developer community includes a number of Avalon contributers and
> commiters, and a number of people who are working with or on James in
> @@ -137,4 +157,4 @@
> 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.
> \ No newline at end of file
> +its market share in comparison with those goliaths.
>
>
>
>
>--
>To unsubscribe, e-mail: <ma...@jakarta.apache.org>
>For additional commands, e-mail: <ma...@jakarta.apache.org>
>
>
>
>
>
--
Stephen J. McConnell
mailto:mcconnell@apache.org
http://www.osm.net
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>