[Buildbot-devel] Volunteering and some suggestions.

[Gavin]

> -----Original Message-----
> From: Dustin J. Mitchell [mailto:dustin at zmanda.com]
> Sent: Tuesday, 8 December 2009 6:27 AM
> To: Marc-Antoine Ruel
> Cc: buildbot maillist
> Subject: Re: [Buildbot-devel] Volunteering and some suggestions.
> 
> On Mon, Dec 7, 2009 at 8:38 AM, Marc-Antoine Ruel <maruel at chromium.org>
> wrote:
> > I agree automated issue tracker emails are better sent to a separate
> list.
> > (Like review emails and commit emails if they would ever be done)
> 
> Good point.  I've attached a github commit email below for reference.
> 
> I think Gavin's original suggestion was intended to centralize
> development traffic in one place, so an additional mailing list
> wouldn't quite meet his goal.
> 
> While I'll leave the means open for debate, I very much support this
> goal.  We have a great community of contributors right now, and a good
> culture of support both here and on #buildbot, but I think the weak
> point is in *maintenance* - relatively fewer people are watching
> bugzilla or tending the metabuildbot.
> 
> So, any other suggestions to that end would be warmly appreciated!

Ok, well consensus so far suggests that a separate email list is needed. I'm
actually ok with that, as it is what the majority of Apache projects for
instance do and seems to work well for them.

They have lists like user.at.project.a.o , dev.at.project.a.o ,
issues.at.project.a.o and commits.at.project.a.o.

So even issues and commits are sent to separate lists from each other, I
don't think we need to go that far but I'm happy separating dev talk away
from issues and commits.

Calling our extra list something buildbot-notifications.at.s.n sounds good
and we can get the issues changes going there straight away and even send
commits notifications there too if we want that.

Therefore those that want to continue with their RSS feeds can without
getting doubled up information on the list, whilst the rest can choose to
subscribe to the new list.

Regarding getting Trac to send us emails I understand the default can be
changed to add the new list in the CC: field for all issues - might need to
manually add it to existing issues though not sure till we try it. The
alterative is to migrate to something like Jira issue tracker which is much
more configurable and as an open source project we get that for free.

Gav...

> 
> Dustin
> 
> --
> Open Source Storage Engineer
> http://www.zmanda.com
> 
> ---------- Forwarded message ----------
> From:  <noreply at github.com>
> Date: Mon, Dec 7, 2009 at 9:38 AM
> Subject: [djmitche/buildbot] 08172a: trivial change to test notification
> To: djmitche at gmail.com
> 
> 
> Branch: refs/heads/master
> Home:   http://github.com/djmitche/buildbot
> 
> Commit: 08172aba45ebd827fe3351329a310403ca0f42a5
> 
> http://github.com/djmitche/buildbot/commit/08172aba45ebd827fe3351329a31040
> 3ca0f42a5
> Author: Dustin J. Mitchell <dustin at zmanda.com>
> Date:   2009-12-07 (Mon, 07 Dec 2009)
> 
> Changed paths:
>  M docs/buildbot.texinfo
> 
> Log Message:
> -----------
> trivial change to test notification
> 
> --------------------------------------------------------------------------
> ----
> Join us December 9, 2009 for the Red Hat Virtual Experience,
> a free event focused on virtualization and cloud computing.
> Attend in-depth sessions from your desk. Your couch. Anywhere.
> http://p.sf.net/sfu/redhat-sfdev2dev
> _______________________________________________
> Buildbot-devel mailing list
> Buildbot-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/buildbot-devel
> No virus found in this incoming message.
> Checked by AVG - www.avg.com
> Version: 9.0.709 / Virus Database: 270.14.87/2536 - Release Date: 12/07/09
> 05:37:00