I would say that in general, projects are not concerned that the https://en.wikipedia.org/wiki/BitKeeper situation with the Linux kernel from 20 years ago would be repeated by Microsoft/GitHub.
On Thursday, September 29, 2022 at 7:26:22 PM UTC-7 John H Palmieri wrote: > You would think that this would be a solved problem: others in the open > source community must have be in the practice of backing up their GitHub > info. > > On Thursday, September 29, 2022 at 6:55:44 PM UTC-7 Nils Bruin wrote: > >> A fair point made: an "exit strategy" from Github should exist and should >> ideally take into account that this exit may need to happen at a time where >> github is no longer able/willing to cooperate in this exit: in other words, >> we should ideally *back up* our issues and pull-request histories. The APIs >> are there; writing the scripts to pull this stuff (incrementally?) would be >> quite a bit of work, but then running it shouldn't be so bad. >> >> This is just common sense data security policy: to us github is a single >> point-of-failure. You want to store with some frequency snapshots of the >> data there. >> >>> >>>>> -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/e7293486-a8b2-4123-8470-3720fa945c79n%40googlegroups.com.
