On Tue, Jan 13, 2009 at 20:21, Stefano Bagnara <[email protected]> wrote: > Robert Burrell Donkin ha scritto: >> On Mon, Jan 12, 2009 at 6:56 PM, Bernd Fondermann >> <[email protected]> wrote: >>> On Mon, Jan 12, 2009 at 17:38, Stefano Bagnara <[email protected]> wrote: >>>> Bernd Fondermann ha scritto: >>>>> Hi, >>>>> >>>>> Development of mime4j has considerably gained speed, with added >>>>> committers and successful releases. >>>>> >>>>> Mime4j discussions comprise a large part of the mail on server-dev. >>>>> >>>>> Mime4j is independent of our server product and used outside of JAMES. >>>>> >>>>> While we do not know whether or not mime4j will really become a project >>>>> of its own, it seems due time to give it more space to expand on a >>>>> seperate mailing list to foster this ongoing process. >>>>> >>>>> So I propose to establish the mailing list >>>>> >>>>> [email protected] >>>>> >>>>> for all mime4j product related discussion. >>>> [X] +/-0, I don't care >>>> >>>> In fact "I do care", but I'm fine with what active people need. >>>> >>>> Will svn notifications for the mime4j tree be moved there, too? >>> Good question. I think we should move that, too. Just like for mailet-api. >>> But I'm open to other opinions here. If anybody wants to separate this >>> from this vote, we can do so. >> >> i don't have strong feelings about this one > > IMHO moving discussions to its own list while leaving svn notification > (and JIRA notifications!?!) to server-dev is the worst scenario at all. > > Either we have: > 1) mime4j-dev@ receving discussions/JIRA/svn for mime4j > server-dev@ receving discussions/JIRA/svn for every other product but > mailets. > > or > 2) we introduce the already discussed "notifications" list where we > redirect all of the JIRA/svn/continuous integration notifications for > all of the james products. > > I think #1 should be the direct result of this vote if/when it passes.
I'm fine with #1. Bernd --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
