[Pydotorg-redesign] Following directions
Aahz
aahz at pythoncraft.com
Sun Aug 24 16:32:27 EDT 2003
On Fri, Aug 22, 2003, Michael McLay wrote:
> On Saturday 23 August 2003 06:14 pm, Aahz wrote:
>>
>> [This was supposed to go out a couple of days ago, but I didn't see the
>> point while the virus storm was at its highest. If you reply to this,
>> please keep it on *one* list.]
>
> [....]
This is not quite a flame, but I am not happy that people are ignoring
my clear and explicit request to keep replies to one list. I (perhaps
foolishly) did not set Reply-To: because each list has a different
purpose. I've set Reply-To: on this message to marketing-python,
because I think that's where the traffic has been coming from.
For the record, here are brief mandates for several important lists:
* pydotorg-pwc: The Python Website Committee serves as a decision-making
body for the website, under the PSF board. This is not a public list.
* psc: The list for the Public Support Committee -- if you're trying to
suggest ways for the PSF to raise money, this is the place. This is not
a public list.
* pydotorg: the working list for people actively maintaining the
python.org servers (primarily the website, but also the mailing lists);
in other words, people with checkin privs. This list should be used for
current work *ONLY*. This is not a public list.
* pydotorg-redesign: the list for discussing medium-term and blue-sky
proposals for updating the python.org website. This list does not have
a PSF mandate, but should be considered to have implicit approval
because it was created with the advice and consent of Guido. This is a
public list.
* marketing-python: the list for discussing general marketing issues
related to expanding the Python userbase. It does not have a PSF
mandate, but the PSF has been working closely with many of the key
people on marketing-python. This is a public list.
--
Aahz (aahz at pythoncraft.com) <*> http://www.pythoncraft.com/
This is Python. We don't care much about theory, except where it intersects
with useful practice. --Aahz
More information about the Pydotorg-redesign
mailing list