That is a coincidence - I was looking at james last night (http://twitter.com/rhirsch/status/1032899174) in terms of a bridge for ESME. I liked the idea of mailets and was looking into the possibility of using one to allow users to send an email to james and having a mailet create an ESME message based on the contents of the email.
Regards, Dick ____________________________ Mag. Richard Hirsch Senior Consultant / Enterprise Portal Solutions Siemens AG Österreich Siemens IT Solutions and Services SIS PSE IND SG Werner-von-Siemens-Platz 1 A-5021 SALZBURG Phone +43 (0)5 1707 66794 Mobil: +43 (0) 676 3537770 Fax +43 (0)5 1707 53211 mailto:[EMAIL PROTECTED] Blog: https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/u/10448 Important Note: This e-mail may contain trade secrets or privileged, undisclosed or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. Company Name: Siemens Aktiengesellschaft Österreich Legal Form: Stock Corporation, Company Seat: Vienna, Register Number: FN 60562 m, registered at: Commercial Court Vienna, DVR-Number: 0001708 -----Ursprüngliche Nachricht----- Von: Robert Burrell Donkin [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 02. Dezember 2008 08:50 An: general@incubator.apache.org Betreff: Re: [VOTE] Accept ESME into the Apache Incubator i'm +1 with comments (see below) On Thu, Nov 27, 2008 at 9:55 PM, Craig L Russell <[EMAIL PROTECTED]> wrote: > > On Nov 27, 2008, at 9:59 AM, Daniel Kulp wrote: > >> On Wednesday 26 November 2008 3:49:09 pm Craig L Russell wrote: >>> >>> Apologies. My inbox never received the messages with the attachment. >>> >>> My only concern is that from the description, the project appears to >>> be run in real time, with decisions made "through collaborative >>> decision-making on the mailing list, through daily scrum calls, via >>> Twitter and using open discussion on ESME itself." >>> >>> The risk is that decisions go by so quickly that it's difficult for >>> someone not totally immersed in the real-time discussions to have a >>> voice. +1 there is also the issue of creating a public record of the process used to develop the product. for mailing lists, this is done through the numerous archives maintained at apache and elsewhere. it should be possible to bridge ESME to RFC822 mail (eg. by using James) on a hudson zone (say). this is an area i'm very interested in so if this is of interest to the ESME team and they haven't done it already, i'd be glad to help out. >>> I expect that the mentors will keep an eye on this so as to avoid >>> excluding potential contributors who don't have the bandwidth to keep >>> up in real time but might have useful things to say. >> >> As a mentor, this is on my "concern list", but isn't something that's a >> concern for ENTERING incubation. great >> It's something that will be learned and >> addressed during incubation and will be resolved before they graduate. >> If >> this was graduation vote, definitely a -1, but for an entering vote, >> nope. > > I agree. +1 - robert --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
