I agree with all of this. Get rid of the Google Code wiki, which is a non-standard wiki, except for a page that links to the mediawiki wiki and the docs. And as Toon said, we should put static pages in the docs and dynamic pages on the wiki. Therefore, things like GSoC project ideas, which is very dynamic right before applying for the program, should be on the wiki. On the other hand, maybe we should keep links to stuff from the wiki in the docs. For example, if we keep the FAQ on the wiki, we definitely want a link to it in the docs.
As for the unicode bug, it needs to be fixed if we are going to use the wiki for anything at all. Does anyone on this list know what is causing it, or is anyone familiar with mediawiki software who can go in and try to fix it (Ondrej will create an account on the server for you if you think you can fix it). I created a test page here (http://wiki.sympy.org/wiki/User:Asmeurer/unicode_test ) to demonstrate it. My feeling is that the MediaWiki software on his server needs to be upgraded, or some extension or font needs to be installed, because the bug doesn't seem to exist on Wikipedia. Aaron Meurer On Jul 1, 2009, at 1:55 AM, Roberto Nobrega wrote: > > The following was raised after SymPy documentation day. > > > Currently we have 3 main sources of documentation: > > - GoogleCode Wiki. > - MediaWiki (wiki.sympy.org). > - Sphinx (docs.sympy.org). > > The current state is very messy. In my opinion, there must be no > repeated information, and we should define what goes where. (Related > issue: http://code.google.com/p/sympy/issues/detail?id=707) > > > Sphinx has the following advantages, pointed by Ondrej: > > <ondrek> the .rst is nice, that we ship it in the release tarball > <ondrej> and it imho looks better than the wiki > <ondrej> plus we can use autodoc feature of sphinx, that extracts > docstrings from inside sympy > <ondrej> plus once we fix it, a pdf documentation will be possible to > > MediaWiki and GoogleCode Wiki are far more accessible to newcomers and > changes are committed instantaneously. > > > Just for example, I see no reason for this to be on Sphinx: > > http://docs.sympy.org/outreach.html#google-summer-of-code > > Also, there is GSoC info on GoogleCode Wiki and MediaWiki as well: > > http://wiki.sympy.org/wiki/GSoC2009Application > http://code.google.com/p/sympy/wiki/GSoC2009 > > > As we discussed on IRC, I propose: > > - GoogleCode: Burn it. Except for FrontPage, Downloads, etc. > > - Sphinx: Only for Tutorial, User Guide and Modules Reference. > > - MediaWiki: Everything else. Including: Patches tutorial, GSoC info, > Development tips, Bibliographical references, Quick examples / > cookbooks, Future plans, Project reports. > > > So, I propose the following actions: > > - Move (and then delete) all wikis from GoogleCode to MediaWiki. I > started some work on this. > > - Delete from MediaWiki repeated stuff already on Sphinx and vice- > versa. > > > Some remarks: > > - We must be sure no information will be lost on this process. > > - We need some way to tell people our choices (e.g., not to use > GoogleCode Wiki). > > - There is a very annoying Unicode bug in MediaWiki that must be fixed > if we opt for using it. > > > Is that subject too much preciosity of my part? What do you people > think? Ondrej, for example, is against moving Patches tutorial from > Sphinx to MediaWiki. Let's try to reach a consensus. > > > Regards, > > Roberto. > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sympy" group. To post to this group, send email to sympy@googlegroups.com To unsubscribe from this group, send email to sympy+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sympy?hl=en -~----------~----~----~----~------~----~------~--~---
