-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi there, are there any objections to retire the old dev.zope.org site together with its wiki? I propose that we move the relevant parts to wiki.zope.org. The relevant information in the wiki as basically: SVN/CVS related docs + contributor/membership related information. This would be a long-hanging fruit for a volunteer :-) Andreas - -- ZOPYX Ltd. & Co. KG - Charlottenstr. 37/1 - 72070 Tübingen - Germany Web: www.zopyx.com - Email: info@zopyx.com - Phone +49 - 7071 - 793376 Registergericht: Amtsgericht Stuttgart, Handelsregister A 381535 Geschäftsführer/Gesellschafter: ZOPYX Limited, Birmingham, UK - ------------------------------------------------------------------------ E-Publishing, Python, Zope & Plone development, Consulting -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkmhgigACgkQCJIWIbr9KYyDXACePzYT2K2zIwP7XDm9L5QVzWsS e98AoJtOV4ba/uqjPIoqM63u4rdSgO3L =Ponu -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 22.02.2009 17:49 Uhr, Andreas Jung wrote:
Hi there,
are there any objections to retire the old dev.zope.org site together with its wiki? I propose that we move the relevant parts to wiki.zope.org. The relevant information in the wiki as basically: SVN/CVS related docs + contributor/membership related information.
This would be a long-hanging fruit for a volunteer :-)
One other option would to convert the related stuff to reST, import it to svn.zope.org and generate nice looking HTML using Sphinx on docs.zope.org. This is perhaps the best solution for "old" static content that does not change often and for which we don't need a CMS. Thoughts? Andreas -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkmhmC4ACgkQCJIWIbr9KYy7dgCeJ0Rfuue68FGwKG+WmuJOOLAX 7WcAnRPmPvJzxRrid+XqzsxYVYXpa3Au =fzUZ -----END PGP SIGNATURE-----
On 2009-02-22, Andreas Jung <lists@zopyx.com> wrote:
One other option would to convert the related stuff to reST, import it to svn.zope.org and generate nice looking HTML using Sphinx on docs.zope.org. This is perhaps the best solution for "old" static content that does not change often and for which we don't need a CMS.
Thoughts?
Yeah, using svn/sphinx for this is a good idea. The sort of documentation in there seems the sort of stuff svn-access-wielding developers write. And: I don't mind doing a bit of this work. But: I'm getting a bit lost in the various websites (old/new/unfinished/never_started). Could someone chime in with a bit of an overview: http://docs.zope.org/ Where is the svn source? http://zode01.lovelysystems.com/.... That's the now-stopped zope.org refactoring, right? http://www.zope.org/DevHome/ The stuff to be moved to svn. http://wiki.zope.org/zope3/Zope3Wiki Sounds like it was meant to end up on the refactored zope.org? Is this also fodder for sphinx on docs.zope.org? Preparing my fingers for some typing... :-) Reinout -- Reinout van Rees reinout@vanrees.org http://reinout.vanrees.org Blog: http://reinoutvanrees.org/weblog/
Previously Reinout van Rees wrote:
Could someone chime in with a bit of an overview:
http://docs.zope.org/ Where is the svn source?
svn.zope.org/zope2docs and /zope3docs
http://zode01.lovelysystems.com/.... That's the now-stopped zope.org refactoring, right?
Right. It's the internal hostname for the machine that run/ran new.zope.org. Wichert. -- Wichert Akkerman <wichert@wiggy.net> It is simple to make things. http://www.wiggy.net/ It is hard to make things simple.
Reinout van Rees wrote:
And: I don't mind doing a bit of this work. But: I'm getting a bit lost in the various websites (old/new/unfinished/never_started).
Absolutely, we need a map.
http://www.zope.org/DevHome/ The stuff to be moved to svn.
Andreas, fwiw I don't think that is a wiki, but http://zope.org/DevHome/Subversion is. I have a list of http://wiki.zope.org/WikisStillOnZopeOrg . Perhaps more of these, at least the non-member ones, should move either to sphinx/svn or to wiki.zope.org. Consolidation is good. Incidentally, with help from Michael Haubenwallner last week I was able to install a better redirection script in /Wikis and delete the duplicated old wiki content under there.
http://wiki.zope.org/zope3/Zope3Wiki Sounds like it was meant to end up on the refactored zope.org? Is this also fodder for sphinx on docs.zope.org?
That's just my attempt to bring some organisation to the zope 3 wiki. For a new zope 3 portal, I would take only the best, skip all the out of date stuff.
On Sun, Feb 22, 2009 at 07:23:42PM +0100, Andreas Jung wrote:
One other option would to convert the related stuff to reST, import it to svn.zope.org and generate nice looking HTML using Sphinx on docs.zope.org. This is perhaps the best solution for "old" static content that does not change often and for which we don't need a CMS.
Thoughts?
+1 Marius Gedminas -- http://pov.lt/ -- Zope 3 consulting and development
participants (5)
-
Andreas Jung -
Marius Gedminas -
Reinout van Rees -
Simon Michael -
Wichert Akkerman