[Python-Dev] New canonical location for PEPs
Stephen J. Turnbull
04 Apr 2002 10:10:16 +0900
>>>>> "Sean" == Sean Reifschneider <email@example.com> writes:
Sean> There is some reasonable mechanism for [automatically
Sean> pushing content from CVS to the Web], as it *IS* done in
Sean> some places.
I know XEmacs's is not perfect, but I'm fairly sure host config
changes at SourceForge and SunSITE.de have been responsible for most
of the attention the webmaster has paid to the auto-update mechanism
over the last two years. Attention has been paid to the lock issue,
but I don't recall the resolution.
We currently keep the website content in CVS at SunSITE.de. A CVS
commit to the website module triggers updates of the SourceForge, Tux,
and SunSITE "primary" homepages, typically taking 10-15 seconds to
propagate to all three sites, including a "genpage" run.
Adrian Aichner <firstname.lastname@example.org> is the guy to talk to about the
website experience (eg, admin resources consumed since original
setup). I believe Martin Buchholz <email@example.com> designed the
mechanism and did the original implementation. Karl Hegbloom
<firstname.lastname@example.org> adapted it for a project he works on, and was the
one who brought up the lock issue most recently. You may be able to
browse the implementation in CVSROOT at cvs.xemacs.org. If not, I'm
sure Adrian would be willing to show it to you.
Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Don't ask how you can "do" free software business;
ask what your business can "do for" free software.