Am Samstag, den 27.05.2006, 13:06 +0200 schrieb Stefano Bagnara:
> Serge Knystautas wrote:
> > I've noticed we have/are rapidly added/ing many "subprojects" to
> > James.  The term "subproject" is something of a loaded term at Apache,
> > so wanted to a) have group discuss how they see these as related and
> > b) be intentional in the term we're using.
> > 
> > 1. How these code bases are related
> > My 2 cents... these are code bases with separate code bases, separate
> > (but hopefully similar) build processes, separate (but visually
> > similar) websites.  For me, the most important issue is that we have
> > only one committer base across all these.  i.e., we're not going to
> > add someone exclusively to mime4j or postage.
> 
> Already posted my +1 to the shared committer base in the previour reply.
> I would also add more informations on the relations between James, jSPF 
> and the newly proposed Postage.
> 
> jSPF is a standalone library.
> Norman already worked to add an SPFHandler to james, using this library. 
> I hope (I will propose this) we will bundle jspf by default in James 
> 2.4/3.0. So jSPF could be a dependency for James.

I hope this too.. But the current SPFHandler is not well integrated by
now. This will be better done when we refactor the SMTPHandler chain to
support "pluggable" features.

> 
> Postage will be a standalone tool having dependencies on few parts of 
> James. So James does not depend on Postage, even if we could plan 
> integration tests for James using Postage. So maybe a set of James tests 
>   will depend on Postage in future.
> 
> jSieve and Mime4j are standalone libraries: I would also like to see 
> future efforts to integrate jSieve and Mime4j with James. If I 
> understood it right jSieve integration would become much more appealing 
> when we finally will introduce IMAP support.
> 
You are right.

> > 2. Intentional with terms we're using
> > Here are some sample terms...
> > 
> > subproject - jakarta terminology
> > project - xml.apache.org's terminology
> > plugin - maven.apache.org's terminology
> > module - ?
> > codebase - ?
> > 
> > Others?
> > 
> > What do you think?
> 
> Imho the better name would be project. Under the James "TLP" Umbrella we 
> produce the following projects:
> - Server: SMTP/POP3/NNTP daemon
> - jSieve: SIEVE library in java
> - Mime4j: MIME library in java
> - jSPF: SPF library in java
> - Postage: SMTP/POP3 stress test tool in java
> 
> Stefano
> 
Fully agree.

bye 
Norman

Attachment: signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil

Reply via email to