Roberto Nobrega wrote: > 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.
I agree with most of your ideas. However, it would be nice to have a developers guide in sphinx too. It could contain the patches tutorial and a documentation tutorial. I find the sphinx documentation far more accessible in terms of reading, but not in terms of writing. Therefore the more 'static' documentation fits better in sphinx, while the more 'dynamic' belongs in the wiki. I would consider a patches tutorial and a documentation tutorial as static. These should be written by a few smart guys and the rest should just adhere. :-) cheers, Toon --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sympy" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/sympy?hl=en -~----------~----~----~----~------~----~------~--~---
begin:vcard fn:Toon Verstraelen n:Verstraelen;Toon org:Ghent University;Center for Molecular Modeling adr:;;Proeftuinstraat 86;Ghent;;9000;Belgium email;internet:[email protected] title:ir. tel;work:+32 (0) 9 264 65 56 tel;home:+32 (0) 9 351 56 05 x-mozilla-html:FALSE url:http://molmod.ugent.be version:2.1 end:vcard
