Mailing List Change Proposal

[Tim Flink]

There was discussion about where qa development related emails should
go and whether we should create a new qa-devel list for qa tools
discussion or just use autoqa-devel@.

Instead of doing either of those, I propose that we depreciate the
autoqa-devel@ list and move everything related to qa development
(autoqa, blocker tracking app, any other tools) to a new qa-devel@
list. It keeps development discussion off of test@ and doesn't create
another mailing list for people to keep track of since many of us are
involved in more than one area of qa devel.

Thoughts?

Tim

[Martin Krizek]

----- Original Message -----
> From: "Tim Flink" 
> To: [e-mail]
> Sent: Monday, February 25, 2013 6:24:51 PM
> Subject: Mailing List Change Proposal
>
> There was discussion about where qa development related emails should
> go and whether we should create a new qa-devel list for qa tools
> discussion or just use autoqa-devel@.
>
> Instead of doing either of those, I propose that we depreciate the
> autoqa-devel@ list and move everything related to qa development
> (autoqa, blocker tracking app, any other tools) to a new qa-devel@
> list. It keeps development discussion off of test@ and doesn't create
> another mailing list for people to keep track of since many of us are
> involved in more than one area of qa devel.
>
> Thoughts?

Makes sense. I don't have any objections. +1

Martin

[Kamil Paral]

> There was discussion about where qa development related emails should
> go and whether we should create a new qa-devel list for qa tools
> discussion or just use autoqa-devel@.
>
> Instead of doing either of those, I propose that we depreciate the
> autoqa-devel@ list and move everything related to qa development
> (autoqa, blocker tracking app, any other tools) to a new qa-devel@
> list. It keeps development discussion off of test@ and doesn't create
> another mailing list for people to keep track of since many of us are
> involved in more than one area of qa devel.
>
> Thoughts?

I agree.

Can Fedora Infra just rename the mailing list, so that all the history, settings and member list is kept intact?

[Tim Flink]

On Tue, 26 Feb 2013 04:44:49 -0500 (EST)
Kamil Paral  wrote:
> > There was discussion about where qa development related emails
> > should go and whether we should create a new qa-devel list for qa
> > tools discussion or just use autoqa-devel@.
> >
> > Instead of doing either of those, I propose that we depreciate the
> > autoqa-devel@ list and move everything related to qa development
> > (autoqa, blocker tracking app, any other tools) to a new qa-devel@
> > list. It keeps development discussion off of test@ and doesn't
> > create another mailing list for people to keep track of since many
> > of us are involved in more than one area of qa devel.
> >
> > Thoughts?
>
> I agree.
>
> Can Fedora Infra just rename the mailing list, so that all the
> history, settings and member list is kept intact?

I asked the same question a couple of weeks ago and the problem with
moving a mailing list is that all of the existing links to
archives on that list would be broken. From what I understand, creating
a new list is a better way forward.

It shouldn't be too hard to extract the membership list of
autoqa-devel@ and add it to the new list unless there are objections to
doing so.

Tim

[Tim Flink]

On Tue, 26 Feb 2013 08:35:34 -0700
Tim Flink  wrote:

<snip>
> > Can Fedora Infra just rename the mailing list, so that all the
> > history, settings and member list is kept intact?
>
> I asked the same question a couple of weeks ago and the problem with
> moving a mailing list is that all of the existing links to
> archives on that list would be broken. From what I understand,
> creating a new list is a better way forward.
>
> It shouldn't be too hard to extract the membership list of
> autoqa-devel@ and add it to the new list unless there are objections
> to doing so.

Just to be clear, the process I'm talking about would end up being:
 - request new qa-devel@ list
 - migrate current autoqa-devel@ membership to qa-devel@
 - disable new posts to autoqa-devel@
   * change list description to show closed list, request to keep it
     around for archives
 - change all the trac instances currently using autoqa-devel@ to use
   qa-devel@
 - change the reviewboard instance to point at qa-devel@
 - hunt for links and references to autoqa-devel@ in the wikis and
   update them

This way, no current subscribers to autoqa-devel@ would have to worry
about subscribing to a new list, the old autoqa-devel@ archives would
stick around, new posts to autoqa-devel@ would be disabled and the
transition should be relatively painless.

Tim

[Tim Flink]

On Mon, 25 Feb 2013 10:24:51 -0700
Tim Flink  wrote:
> There was discussion about where qa development related emails should
> go and whether we should create a new qa-devel list for qa tools
> discussion or just use autoqa-devel@.
>
> Instead of doing either of those, I propose that we depreciate the
> autoqa-devel@ list and move everything related to qa development
> (autoqa, blocker tracking app, any other tools) to a new qa-devel@
> list. It keeps development discussion off of test@ and doesn't create
> another mailing list for people to keep track of since many of us are
> involved in more than one area of qa devel.

The feedback thus far has been positive, so I'd like to get this done
in the next couple of days - if you have any objections, please speak
up soon - I'll start the migration process on Thursday morning (US time)
otherwise.

Tim

[Tim Flink]

On Tue, 26 Feb 2013 15:44:08 -0700
Tim Flink  wrote:
> On Mon, 25 Feb 2013 10:24:51 -0700
> Tim Flink  wrote:
> > There was discussion about where qa development related emails
> > should go and whether we should create a new qa-devel list for qa
> > tools discussion or just use autoqa-devel@.
> >
> > Instead of doing either of those, I propose that we depreciate the
> > autoqa-devel@ list and move everything related to qa development
> > (autoqa, blocker tracking app, any other tools) to a new qa-devel@
> > list. It keeps development discussion off of test@ and doesn't
> > create another mailing list for people to keep track of since many
> > of us are involved in more than one area of qa devel.
>
> The feedback thus far has been positive, so I'd like to get this done
> in the next couple of days - if you have any objections, please speak
> up soon - I'll start the migration process on Thursday morning (US
> time) otherwise.

I requested a new mailing list and the request has now gone through.
I'm in the process of adding all the autoqa-devel@ subscribers to the
new list - you should be seeing a mail from the new qa-devel@ list
shortly.

Once we get the trac instances pointing to the new list, we can start
the process of depreciating this list.

Tim