On Mon, Aug 4, 2008 at 7:06 PM, Stefano Bagnara <[EMAIL PROTECTED]> wrote: > Robert Burrell Donkin ha scritto: >> >> On Mon, Aug 4, 2008 at 5:13 PM, Stefano Bagnara <[EMAIL PROTECTED]> wrote: >>> >>> Robert Burrell Donkin ha scritto: >>>> >>>> On Sun, Aug 3, 2008 at 1:16 PM, Stefano Bagnara <[EMAIL PROTECTED]> wrote: >>>>> >>>>> Robert Burrell Donkin ha scritto: >>>>>> >>>>>> On 7/28/08, Norman Maurer <[EMAIL PROTECTED]> wrote: >>>>>>> >>>>>>> Am Sonntag, den 27.07.2008, 22:20 +0200 schrieb Stefano Bagnara: >>>>>>>> >>>>>>>> Is there any mailing list notification? >>>>>>> >>>>>>> I not enabled it yet because I wanted to talk about it first on ml. >>>>>>> MAybe we should add a new ml for the notifications so we don't flood >>>>>>> the >>>>>>> dev list ? >>>>>> >>>>>> Providing that mail is only sent on failure, I think this list should >>>>>> be ok. If we need to reduce traffic all the admin stuff (commits, JIRA >>>>>> etc) should be moved together. We've had 600ish messages this month so >>>>>> maybe that's worth considering. >>>>> >>>>> Moving "admin stuff" to a separate list could help not loosing >>>>> important >>>>> discussion and procedural threads between svn committs and JIRA >>>>> updates. >>>>> >>>>> On the other hand we tend to mix discussions in JIRA and the mailing >>>>> list >>>>> so >>>>> we should agree on the way to deal with it before planning a switch, >>>>> IMHO. >>>> >>>> set an appropriate reply-to usually works ok for most clients >>> >>> My concern was about discussions happening via JIRA comments, they would >>> not >>> go through the discussion list, but only the admin list. Currently a JIRA >>> comment is the substitute for a mailing list post. If we move JIRA >>> notifications to an admin list beside svn comments they will loose >>> visibility to developers not subscribed to the notification list. >> >> makes sense >> >>>>> Maybe we could move svn commits and the notifications to their own list >>>>> as a >>>>> first step while keep JIRAs on server-dev... WDYT? >>>> >>>> fine by me >>> >>> What is the list name used by other projects in this cases? >>> [EMAIL PROTECTED] >> >> probably commits. see http://mail-archives.apache.org/mod_mbox/ > > commits is the most common (hundreds of them). Then I see 9 "notifications" > lists. > > It seems we agree on this. What is the procedure? Should we open a proposal > thread so more people will be aware of this discussion?
for a new mailing list, it's best to have a VOTE > I prefer "notifications@" because we'll put there more than commits but I'm > fine with "commits@" too. i'd recommend a POLL: the idea is to gauge support for various alternatives so that it's possible to call a good binary VOTE. see below for example - robert <example> [POLL] Development Mailing Lists Please cross as many as you like! ---8<--------------------------------------------- [ ] Leave My Lists Alone! [ ] Send commits and reminders to notifications@ [ ] Send commits and reminders to commits@ --------------------------------------------------- </example> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
