Result [VOTE] Mailet API as sub-project

This vote has passed with 8 +1's and no -1s I will be in touch to get opinions about the best way to break the code out. d. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Mailet API as sub-project

Better Cast my own vote ;-) +1 On 1/8/07, Danny Angus <[EMAIL PROTECTED]> wrote: Hi, I'm calling this vote here and not on general@ because it affects James server. Because of interest in advancing the Mailet API and opinions already expressed in this thread (http://mail-archives.apache.org/mo

Re: [VOTE] Mailet API as sub-project

Danny Angus wrote: one step at a time... we've talked about this for so long it might be a mistake to bite off too much in the first go. +1 It is much better a small concrete step today than a hundred of discussion in the last years :-) Stefano -

Re: [VOTE] Mailet API as sub-project

On 1/10/07, Serge Knystautas <[EMAIL PROTECTED]> wrote: +1. I'd also think about moving our mailets into the mailet subproject, and that could serve as your testing ground or at least samples. At least the mailets that are not tied to James/Avalon APIs. I thought about that, having a /contrib

Re: [VOTE] Mailet API as sub-project

+1. I'd also think about moving our mailets into the mailet subproject, and that could serve as your testing ground or at least samples. At least the mailets that are not tied to James/Avalon APIs. -- Serge Knystautas Lokitech >> software . strategy . design >> http://www.lokitech.com p. 301.65

Re: [VOTE] Mailet API as sub-project

+1 On 1/8/07, Danny Angus <[EMAIL PROTECTED]> wrote: Hi, I'm calling this vote here and not on general@ because it affects James server. Because of interest in advancing the Mailet API and opinions already expressed in this thread (http://mail-archives.apache.org/mod_mbox/james-general/200610.m

Re: [VOTE] Mailet API as sub-project

Am Montag, den 08.01.2007, 09:58 + schrieb Danny Angus: > I would like to propose that the Mailet API be migrated into a new > sub-project with all its mail on [EMAIL PROTECTED] and its svn in > james/mailetapi +1 (non binding) I think it is important to show the public that james community

Re: [VOTE] Mailet API as sub-project

On 1/8/07, Stefano Bagnara <[EMAIL PROTECTED]> wrote: Do you propose to create a new JIRA project, too? Oh yeah, makes sense to I think. We could even make a standalone release from that release (so current projects using mailet apis can already use that) and add it as a dependency in james

Re: [VOTE] Mailet API as sub-project

+1 Norman Danny Angus schrieb: > Hi, > I'm calling this vote here and not on general@ because it affects > James server. > > Because of interest in advancing the Mailet API and opinions already > expressed in this thread > (http://mail-archives.apache.org/mod_mbox/james-general/200610.mbox/[EMAIL

Re: [VOTE] Mailet API as sub-project

On 1/8/07, Danny Angus <[EMAIL PROTECTED]> wrote: Hi, I'm calling this vote here and not on general@ because it affects James server. Because of interest in advancing the Mailet API and opinions already expressed in this thread (http://mail-archives.apache.org/mod_mbox/james-general/200610.mbox/

Re: [VOTE] Mailet API as sub-project

+1 Stefano PS: see the inline note. Danny Angus wrote: Hi, I'm calling this vote here and not on general@ because it affects James server. Because of interest in advancing the Mailet API and opinions already expressed in this thread (http://mail-archives.apache.org/mod_mbox/james-general/200

[VOTE] Mailet API as sub-project

Hi, I'm calling this vote here and not on general@ because it affects James server. Because of interest in advancing the Mailet API and opinions already expressed in this thread (http://mail-archives.apache.org/mod_mbox/james-general/200610.mbox/[EMAIL PROTECTED]) I would like to propose that t