[Python-3000] Merging mailing lists

["Martin v. Löwis"]

I would like to merge mailing lists, now that the design and first
implementation of Python 3000 is complete. In particular, I would
like to merge the python-3000 mailing list back into python-dev,
and the python-3000-checkins mailing list back into python-checkins.
The rationale is to simplify usage of the lists, and to avoid
cross-postings.

To implement this, all subscribers of the 3000 mailing lists would
be added to the trunk mailing lists (avoiding duplicates, of course),
and all automated messages going to python-3000-checkins would then
be directed to the trunk lists. The 3000 mailing lists would change
into read-only mode (i.e. primarily leaving the archives behind).

Any objections?

Regards,
Martin
_______________________________________________
Python-3000 mailing list
Pytho...@python.org
http://mail.python.org/mailman/listinfo/python-3000
Unsubscribe: http://mail.python.org/mailman/options/python-3000/python-3000-garchive-63646%40googlegroups.com

[Fred Drake]

On Thu, Dec 4, 2008 at 2:36 AM, "Martin v. Löwis" <mar...@v.loewis.de> wrote:
> I would like to merge mailing lists, now that the design and first
> implementation of Python 3000 is complete. In particular, I would

+1

-Fred

--
Fred L. Drake, Jr. <fdrake at gmail.com>
"Chaos is the score upon which reality is written." --Henry Miller

[Jeremy Hylton]

On Thu, Dec 4, 2008 at 2:36 AM, "Martin v. Löwis" <mar...@v.loewis.de> wrote:

> I would like to merge mailing lists, now that the design and first
> implementation of Python 3000 is complete. In particular, I would
> like to merge the python-3000 mailing list back into python-dev,
> and the python-3000-checkins mailing list back into python-checkins.
> The rationale is to simplify usage of the lists, and to avoid
> cross-postings.

+1

> To implement this, all subscribers of the 3000 mailing lists would
> be added to the trunk mailing lists (avoiding duplicates, of course),
> and all automated messages going to python-3000-checkins would then
> be directed to the trunk lists. The 3000 mailing lists would change
> into read-only mode (i.e. primarily leaving the archives behind).
>
> Any objections?

No

Jeremy

> Regards,
> Martin
> _______________________________________________
> Python-3000 mailing list
> Pytho...@python.org
> http://mail.python.org/mailman/listinfo/python-3000

> Unsubscribe: http://mail.python.org/mailman/options/python-3000/jeremy%40alum.mit.edu

[Brett Cannon]

On Wed, Dec 3, 2008 at 23:36, "Martin v. Löwis" <mar...@v.loewis.de> wrote:
> I would like to merge mailing lists, now that the design and first
> implementation of Python 3000 is complete. In particular, I would
> like to merge the python-3000 mailing list back into python-dev,
> and the python-3000-checkins mailing list back into python-checkins.
> The rationale is to simplify usage of the lists, and to avoid
> cross-postings.
>
> To implement this, all subscribers of the 3000 mailing lists would
> be added to the trunk mailing lists (avoiding duplicates, of course),
> and all automated messages going to python-3000-checkins would then
> be directed to the trunk lists. The 3000 mailing lists would change
> into read-only mode (i.e. primarily leaving the archives behind).
>
> Any objections?
>

Nope; +1.

-Brett

[Paul Moore]

2008/12/4 "Martin v. Löwis" <mar...@v.loewis.de>:
> Any objections?

The timing is right, go for it.
Paul

[Dmitry Vasiliev]

Martin v. Löwis wrote:
> I would like to merge mailing lists, now that the design and first
> implementation of Python 3000 is complete. In particular, I would

+1

--
Dmitry Vasiliev (dima at hlabs.spb.ru)
http://hlabs.spb.ru

["Martin v. Löwis"]

> I like the general sentiment, but I think it may be a bad idea to
> automatically bring all the subscribers from the -3000 lists over to the
> more general lists. For instance if someone has an address subscribed
> specifically to archive the -3000 list suddenly it will begin archiving
> the other. I would rather just see a final announcement to switch to the
> other list and then close the list to further submissions. Let people
> join the new appropriate list manually if needed.

That sounds reasonable. So no transfer of membership will be done;
people have to explicitly subscribe to python-dev and python-checkins
if they want to continue to follow the discussion.

[Janzert]

Martin v. Löwis wrote:
> I would like to merge mailing lists, now that the design and first
> implementation of Python 3000 is complete. In particular, I would
> like to merge the python-3000 mailing list back into python-dev,
> and the python-3000-checkins mailing list back into python-checkins.
> The rationale is to simplify usage of the lists, and to avoid
> cross-postings.
>
> To implement this, all subscribers of the 3000 mailing lists would
> be added to the trunk mailing lists (avoiding duplicates, of course),
> and all automated messages going to python-3000-checkins would then
> be directed to the trunk lists. The 3000 mailing lists would change
> into read-only mode (i.e. primarily leaving the archives behind).
>
> Any objections?
>
> Regards,
> Martin

I like the general sentiment, but I think it may be a bad idea to

automatically bring all the subscribers from the -3000 lists over to the
more general lists. For instance if someone has an address subscribed
specifically to archive the -3000 list suddenly it will begin archiving
the other. I would rather just see a final announcement to switch to the
other list and then close the list to further submissions. Let people
join the new appropriate list manually if needed.

Otherwise +1 on getting the discussion and checkins back into combined
lists.

Janzert