Post by Steve HoldenI suspect that postmaster at python.org would need to be involved in the
mechanics, though I have no idea whether there is any established
procedure for such an operation.
Added to CC.
Post by Steve HoldenI doubt it's necessary to merge content given the total archive size of
pydotorg-www is less than 50 kB. Wouldn't it just be easier to post a
message on that list telling people to subscribe instead to
pydotor-redesign (whose archives are under 200 kB), and then close
pydotorg-www down?
Post by anatoly techtonikI'd like to propose joining pydotorg-www and pydotorg-redesign in one
pydotorg mailing list to reduce clutter and provide single point of
collaboration to improve the web site. Concentrating efforts in one
place helps to keep people focused and increased activity attracts new
contributors.
?http://mail.python.org/pipermail/pydotorg-redesign/
?http://mail.python.org/pipermail/pydotorg-www/
it seems the lack of interest in both of these newsgroups might make
simply closing one or both down the most practical approach. Or do you
have a specific purpose in mind after a merge?
I think shutting them both down is the best approach, but this
requires pydotorg list to became public. Is there any reason why
pydotorg can't be made public taking into account that security issues
can be reported directly (or discussed in private
webmaster at python.org) and SVN is public already?
Post by Steve HoldenIn the past there has been a sort of "let's start a mailing list"
disease that people have used to persuade themselves that something will
happen. ?Sadly experience proves that this isn't often the case, and the
result is yet another moribund mailing list that doesn't result in any
action.
That's logical. The activity should be focused, not scattered.
Post by Steve HoldenSince there has been no response to your mail from anyone but Michael
and I (unless I have missed messages) I would suggest that both lists
are already pushing up the daisies.
I am, however, extremely interested in harnessing the energies of anyone
who is keen enough to take any sort of action. To that end I am making
Rich Leland, who has recently undertaken to look at the web site with a
view to modernization of both content management and design, aware of
this thread. He may contact you about this (but I am not committing him
to any specific action).
That's nice. I would start with focusing our efforts on making
python.org site contributions more open.
The top thing in my pydotorg next-things-to-be-done is merging the
mailing lists.
The proposed plan for it is:
1. open pydotorg to be public
2. open pydotorg-commits to be public - SVN repository is public anyway
3. close public pydotorg-redesign and pydotorg-www
4. publish an announcement to closed lists that all discussions now
take place in pydotorg
5. update mailman list description pages
6. move subscribers from old mailing lists to pydotorg
7. update http://www.python.org/dev/pydotorg/,
http://www.python.org/dev/pydotorg/website/,
http://www.python.org/about/website and the link "Help Maintain
Website"
Right now I do not have privileges to carry any of these tasks. Who is
able to do this?
--
anatoly t.