On Friday, May 29, 2015 at 3:11:14 PM UTC-4, William wrote: > > Hi, > > I don't know anything about http://sage.lacim.uqam.ca/, but I'm > starting to get emails directly to me asking for help about it > vanishing. Of course, I'll refer people to this thread. >
I'm sorry about that. It took us a while to get it sorted out, but the server is back up and running now. (The person who set up and maintained the server is no longer working for us.) > Thoughts: > > This is a very interesting example of how our past approach of > encouraging a lot of people we don't know to run random Sage notebook > servers all over has the potential to confuse users and significantly > harm the reputation of Sage. I had never considered this before. I did not realize until this incident how many people were using our server. I thought it was mainly used by our students and a few collaborators. > If > I had, I might have wanted to have a requirement like: > > - either (1) don't call it Sage, or (2) we provide a backup system > that periodically rsync's a copy of your notebook's file to a central > server, just in case. > What about making it so that worksheets can be easily saved to a github project or to Dropbox (or similar service)? This way, a user can control where the backups are saved. It might be interesting to discuss technically how (2) would work. It > could, e.g., pre-encrypt the backups for each user separately using > their login credentials as a key, so as long as they can login they > could get their data out of this central backup. > One issue with that comes to mind is how to handle a password change; either intentionally, or if the password is reset when it is forgotten. I will very likely do something like the above with Sagemathcloud, > when instances start popping up all over. Make them choose a clearly > very different name to avoid confusion, or somehow link with a central > service to avoid hurting our poor users. To me the needs of our users > are by far the top priority. In particular, though "Stories about > student losing against their will "all hard work" make only their > teachers smile ...", I think instead that when this happens it is a > failure of the Sage community, and we should try to do better. > > -- William > > > > > 2015-05-28 12:12 GMT-07:00 Dominique Laurain <dominique...@orange.fr > <javascript:>>: > > Ouf, > > > > Merci..a vous pour avoir compris qu'il faut etre rapide... et surtout et > a > > Franco. > > > > Attendons un peu avant de crier victoire > > > > En tout cas, l'informaticien que je suis, va vous rappeler les bases : > > FAITES DES SAUVEGARDES VOUS-MEME ET REGULIEREMENT > > > > Les fichiers SAGE sont en gros des fichiers texte ...si il n'est pas > > immédiat de les convertir, ils sont quand meme exploitables sous un > éditeur > > de texte. > > > > Et puis organisez VITE votre migration sur le cloud SAGE..dés que le > serveur > > est reparti, vous téléchargez tout sur votre PC..1er sauvegarde > donc...puis > > rechargez tous sous le cloud...puis RAPIDEMENT les tests pour voir ce > qui > > est bon, et enfin pour finir un export en fichier PDF > > > > Dominique. > > > > -- > > You received this message because you are subscribed to the Google > Groups > > "sage-support" group. > > To unsubscribe from this group and stop receiving emails from it, send > an > > email to sage-support...@googlegroups.com <javascript:>. > > To post to this group, send email to sage-s...@googlegroups.com > <javascript:>. > > Visit this group at http://groups.google.com/group/sage-support. > > For more options, visit https://groups.google.com/d/optout. > > > > -- > William (http://wstein.org) > -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-support+unsubscr...@googlegroups.com. To post to this group, send email to sage-support@googlegroups.com. Visit this group at http://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout.
