Bernd Fondermann ha scritto: > Serge Knystautas wrote: >> On 6/9/07, Bernd Fondermann <[EMAIL PROTECTED]> wrote: >>> Let's have a mission statement for our project. >>> This apparently has proved to be a good thing[1]. >>> >>> It should be one sentence representing all aspects and parts of our >>> community. A claim-like phrase would be ok for me. It should not be for >>> pure marketing or for representing a current state, but more like a goal >>> we want to achieve over the next months. >> >> I think it would be good to survey what people want out of James, >> though I don't think it needs to be summarized to one sentence. A few > >> deciding whether to use James > years back we had such a discussion >> and the debate came down tomore for sysadmin stuff or to make it >> more developer friendly. At the time we went with sysadmin stuff, >> which increased the number of features in that area and ease of use, >> though it deprioritized any refactoring that is (was) needed. >> >> I just like using Java to process email in real-time. > > Obviously, as the discussion died down early ;-), the vast majority sees > no need for something like that... > > Thanks for replying anyway,
I was on the way to reply at least a couple of times but I decided to wait other's opinions. I don't think this is much important to the project, and I don't have strong preferences between your suggested mission statement, but if the mission statement has to be applied to the JAMES project then I would like to have a really generic EMAIL related statement. Otherwise, if it is related only to JAMES Server then we can discuss whether our goal is to have performance vs features, if we target developers vs sysadmins and so on: I think we will find diverging opinions on this last thing. Where would you add this mission statement ? should it appear in large versions of our logo? Stefano --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
