On Wed, May 2, 2012 at 12:06 PM, Ezio Melotti <ezio.melotti at gmail.com> wrote: > On 02/05/2012 19.33, Michael Foord wrote: >> >> On 2 May 2012, at 16:55, Terry Reedy wrote: >>> >>> I would send the above to webmaster at python.org (should be at the bottom >>> of pages). We develop CPython but do not directly manage the website. >> >> Not true. The download pages are administered by the release managers not >> the web team. >> >> For the record, the best way of contacting the web team (such as it is) is >> the pydotorg-www mailing list. There are precious few people (even fewer >> than there are in the web team...) responding to emails on the webmaster >> alias. :-) >> >> Michael > > > I'm pretty sure that several core devs are able (and possibly willing) to > help out with the website, but AFAIU they have to request commit right for a > separate repo where the website lives or report issues via mail. Is there > any practical reason why the repo for the website is not on hg with all the > other repos (cpython/devguide/peps/etc.) except that no one ported it yet? I don't know if there's a practical reason, but given that the website will eventually be changing anyway, I think it's a waste of time to port it to hg. You'd also have to port the build chain to hg, since it rebuilds the site when svn is updated. Then by the time you're done, there's zero net gain and it all gets thrown away.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4