Well, the topic went to documentation very quickly.
I think we've all decided that documentation in the source code generally
shouldn't be messed with. To exend the statement, we have decided that we
should make our directions to new users clearer.
If that's all you read, then we should probably figure out who will work on
1. Redesigning www.sagemath.org
2. Finding all internal and external documentation, and classify as
1. *Reference* and/or man pages (includes Wikipedia and the like)
2. *Change log*: We already have on website, and the Trac wiki
3. *Code Samples*: anything like wiki.sagemath.org/art , etc.
4. *Interactives*: not needed, but fun to see...
5. *Devel guide*: A conversational written guide to using the API.
6. *Tutorials*: full-blown. Books, wikis, source code, blogs, etc.?
3. Update anything within our domain to reflect design
4. Figure out how it will be maintained.
I have access to old files that were on sage.math.washington.edu, and also
combinat.sagemath.org.... Basically, I'm doing this anyway.
There are things that I want to see done, like moving SageWiki
<http://wiki.sagemath.org> "wishlists" and the SEP's
<https://wiki.sagemath.org/devel/SEP> to Trac.
Moving these will require contributors to be convinced that it should be
done, and then help with migrating to appropriate spots.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
