Doug> In the interest of making sure the interested parties see all the
Doug> messages related to the migration project, Noah and I agreed to
Doug> use the infrastruct...@python.org mailing list to communicate, for
Doug> now. That gives us a single archive, and most of the interested
Doug> parties are already on that list. (If/when we move the python.org
Doug> mail server we may need some other list for a short time, but
Doug> we'll deal with that when the time comes.)
Doug> If you are interested in participating or following the project,
Doug> please join infrastruct...@python.org. When we need specific
Doug> information, we will contact other teams via their "native"
Doug> mailing lists, or one-on-one, so don't worry about being left out
Doug> if you *aren't* interesting in following the whole thing.
Sorry, what is "the project"? Why would pydotorg or pydotorg-www have not
been good enough to discuss website topics?
Can we please stop increasing the number of mailing lists which deal with
python.org web presence? We've managed pretty well with a single mailing
list, python-dev, for discussing all concrete matters of Python
development. I can't see that the web sites need more than that.
Skip
_______________________________________________
pydotorg-www mailing list
pydotorg-www@python.org
http://mail.python.org/mailman/listinfo/pydotorg-www
