On Fri, Nov 19, 2010 at 6:33 PM, Aaron Meurer <[email protected]> wrote: > I basically agree with what you are saying. We should have the main > documentation in the Sphinx, so that it can be doctested (maybe even > most of it should actually be in the docstrings, so you can get to it > from the interpreter using help()). Then, the more transient stuff > should go in a wiki, which I guess should be GitHub (after only 5 min > in the GitHub wiki, I already like it way better than the Google Code > one: the markup is better, the previews are better, you can > download/edit via git, etc.). This transient stuff is exactly the sort > of thing that is in Google Code right now---GSoC, HowTos (like > GettingTheBleedingEdge and UpdateMpmath), notes, etc.. > > So I vote to actually move some of the pages to the main documentation > (the ones, like I said, that should be doctested), and the rest, > including the ones in the Google Code wiki, to GitHub. But the > MediaWiki is the priority, because it is costing Ondrej and is > becoming overwhelmed with spam, not to mention that things like code > blocks and LaTeX math do not work. And these should be the only two > documentation sites.
Yes, definitely. Don't worry about the cost, that's not an issue. The issues are that I don't have time and don't want to maintain the wiki, and that the github wiki will be archived more (due to git), as well as it's actually better than both media wiki and google code. > > By the way, some pages could probably be thrown out completely if they > are completely outdated. > > Was http://code.google.com/p/sfepy/w/list really supposed to be > included in that list? That's a mistake. Ondrej -- 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.
