mailet api list

[Danny Angus <Da...@slc.co.uk>]

I'm slightly concerned that the "we" who created the new mailet list don't
appear to have consulted the James PMC on either pmc@ or general@ or even
on server-dev@ before creating the list.

I know it isn't a very contentious issue, but at the very least lazy
consensus of the PMC should be seen to have been sought.

There are those at the ASF who feel that splitting topics onto separate
lists is counter productive to maintaining an integrated community; it
might have been worth airing the pro's & con's before acting, particularly
as James pmc hasn't visited this issue before (IIRC) prefering to defer the
decision on sub-projects until the time it became relevant.

I would now like to ask what the proponents of the new list intend with
regard to the API itself.
Is the API maintenance to be carried out on the new list or on server-dev@?
Where will mail regarding mailet svn commits & JIRA defects go?
Is there a proposal being brought forward to establish Mailet as a distinct
sub-project?
Is there any intention of applying the same criteria to sieve &
mime-parser?

FWIW I'm not opposed to the new list, but I think it should have been
proposed properly, which would have allowed consideration of the impact on
the developer community and the management of the API code & issues.


d.


---
Danny Angus
Lead Technical Consultant
Front Office Development
4W
3257




***************************************************************************
The information in this e-mail is confidential and for use by the addressee(s) only. If you are not the intended recipient (or responsible for delivery of the message to the intended recipient) please notify us immediately on 0141 306 2050 and delete the message from your computer. You may not copy or forward it or use or disclose its contents to any other person. As Internet communications are capable of data corruption Student Loans Company Limited does not accept any  responsibility for changes made to this message after it was sent. For this reason it may be inappropriate to rely on advice or opinions contained in an e-mail without obtaining written confirmation of it. Neither Student Loans Company Limited or the sender accepts any liability or responsibility for viruses as it is your responsibility to scan attachments (if any). Opinions and views expressed in this e-mail are those of the sender and may not reflect the opinions and views of The Student Loans Company Limited.

This footnote also confirms that this email message has been swept for the presence of computer viruses.

**************************************************************************

RE: mailet api list

["Noel J. Bergman" <no...@devtech.com>]

Danny,

Actually, I had pinged Serge because I had a few minutes of time to do the
list, and we were both under the impression that we DID have a lazy
consensus from the server-dev discussion with Andrew C. Oliver, in which the
mailing list had been discussed.  You may be correct that we were mistaken,
but the intent was present.

With respect to your specific questions:

> Is the API maintenance to be carried out on the new list or on
server-dev@?

I presume that the list would be for discussing the API, not implementation.

> Where will mail regarding mailet svn commits & JIRA defects go?

JIRA goes to server-dev for now, since we don't have a separate Mailet
project.  We could modify the SVN mailer, but I don't really see the point
at this time.

> Is there a proposal being brought forward to establish Mailet
> as a distinct sub-project?

All we were trying to do was provide an implementation neutral area for
discussing the API, as per the aforementioned discussion on server-dev.

I can already see that it is going to cause us some grown pain, because it
makes it a bit clearer that the Mailet API isn't just JAMES internal, which
means that we can't just change it without some consideration, and we're
providing a place for others to collaborate on what API changes do occur.
Pains and all, this may be a good thing.

> Is there any intention of applying the same criteria to sieve &
> mime-parser?

For now, they are captive to the server.  Over time, who knows?

	--- Noel