> Why not? Although I'd agree that a to-do list should better be a metaticket on Trac, and discussions should happen on sage-devel or sage-combinat-devel.
The wiki is hard to track down for pages if one doesn't know what to look for. So, for prospective contributors, it's hard to see if a problem has been fixed... some are from Nov. 2008 (which I assume is when the Wiki was initiated), and some less old. I've been browsing through TitleIndex, and the newest page of this type is https://wiki.sagemath.org/DenseLinearAlgebra. Other "categories" of pages- ex. under combinat/*, and each SEP, freebsd/*, "hardware <https://wiki.sagemath.org/hardware>" , i18n/* , osx64/*, padics/*, etc. - exist without updates. Most of these are also duplicated/duplicates something. Would moving these to say, their own page on the Trac wiki, help? > -1 for several reasons. 1) Tutorials *document* how to solve problems that typically arise when first using sage, and how to implement stuff that typically arises in SageMath development. So, it is documentation. 2) If a user has a problem that is solved in one of the tutorials, it currently is possible to access the solution *locally*, whereas with your suggestion it would be needed to have internet access. 3) The education-based wiki, if I understand correctly, is about how to use SageMath to teach people maths. It is *not* about how to teach mathematicians the usage of SageMath. "Tutorial", "Thematic Tutorial", "PREP Tutorial", "A Tour of Sage". and "Constructions" are mostly the same Tutorial. As far as I know, these all answer questions of "how do I do this?" style. My use of "education-based" referred to the style of tutorials seeming to aid the undergrad-level lecturer not confuse a Mathematical command with a Sage command. So, I propose reducing the online documentation to 1) keep "Tutorial" for its translations, 2) move installation instructions and "FAQ: Contributing to Sage" to Developer Guide, and 3) keep what is useful (subjective) in FAQ's. Side note: just now discovered https://wiki.sagemath.org/DocumentationProject, and I think that it sums up thinking process. > -1. Trac is where development happens. A user who doesn't do development yet won't have a trac account and thus can't open a trac ticket. But of course such user should still be able to formulate a feature request. And voilà, (s)he can contact sage-devel or sage-support or AskSage to formulate the request. If I recall correctly, at some point we had Trac open, so that anybody could open tickets. It didn't work. I don't know much about if there is any single page to track feature requests before they become tickets (or to decide if they become one), so TBH I don't know what to do. Single feature requests can be made in sage-devel (eg. upgrading Python to 3), but groups of requests (ie. a "wishlist") probably shouldn't be on SageWiki. > I agree that this currently is the case. Do you have suggestions for improving sagemath.org? I do. If you see the theme of this post, it involves reducing the size. Things to keep (by order of importance): 1. Links to major sites: (basically /index.html) 1. Trac , git.sagemath.org , GitHub - developing 2. doc.sagemath.org and wiki.sagemath.org - using / contributing 3. social media - more active than the blog 4. Cloud and Cell - [obvious] 5. ask.sagemath.org and mailing lists 2. Show usefulness (single page) 1. correctness and speed - top two benchmarks for research (if still will do benchmarks often) 2. advantages of being open-source and GPL 3. using Sage for teaching, as well as research 3. Developer / Contributing (single page) 1. I'm biased, but basically duplicate https://fedoraproject.org/wiki/Join. This should get users to identify ways to help. If it looks simple and appealing, then hopefully they will think contributing is simple and easy. 2. Give examples of specialized groups: Combinat and Manifolds 4. Downloading (single page) 1. clone git / install from source 2. pre-packaged; each OS 3. mirrors and distributed / P2P -- 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.
