When I was a teacher at the university I wrote a proof-of-concept website with this idea in mind:
- The sage developer workflow is too complicated for most university professors teaching Mathematics. Not every mathematician can contribute quality code to sage, but many could contribute quality teaching material. I didn't find reasonable that in order to contribute a translation to a tutorial, or a new lesson/course/thematic tutorial, a teacher would have to learn version control, pass all tests, wait for a review, etc. I mean, Sage keeps working fine if one of the thematic tutorials has a bug in the code. So I wrote a website inspired by wikibooks, where any user could sign up, drop in a sws file, that would be converted to rst text, or directly the rst files, with chapters and all that. Then the website would compile that into docs, warn of mistakes, run the tests against all active versions of sage, and keep track of translations of that tutorial/course/lesson/whatever. I presented a prototype to the Sage community in Spain and the idea didn't spark a lot of interest, so I forgot about it. Probably, I didn't sell ReStructuredText fine enough, I think latex is too popular in Spain. I don't think the code is worth much, but what do you think about the idea? It's somewhere between the old "publish notebook" button, that was too chaotic, and the "contribute to the sage codebase", which was too complicated. -- You received this message because you are subscribed to the Google Groups "sage-edu" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-edu+unsubscr...@googlegroups.com. To post to this group, send email to sage-edu@googlegroups.com. Visit this group at http://groups.google.com/group/sage-edu. For more options, visit https://groups.google.com/d/optout.