←back to thread

Important open source projects should not use GitHub (2020)

(unixdigest.com)
68 points bitbasher | 5 comments | 15 Apr 25 02:18 UTC | HN request time: 0.839s | source
1. nottorp ◴[15 Apr 25 10:54 UTC] No.43691129[source]▶
To quote Joel Spolski, has anyone using a distributed VCS lost any significant amount of code?

If github annoys you you can concievably create a new repo elsewhere, change origin locally, push.

The real question is how long until they annoy you. And how easy it would be to set up an automatic mirror beforehand.

replies(1): >>43691189 #
2. guappa ◴[15 Apr 25 11:02 UTC] No.43691189[source]▶
You can't migrate the bug reports.
replies(2): >>43691228 #>>43691432 #
3. loloquwowndueo ◴[15 Apr 25 11:08 UTC] No.43691228[source]▶
Run a periodic script that slurps bug data via the API and updates a file in the repo with this information. If GitHub goes away you at least have a local copy of the raw data no more than a day old or so.

GitHub json data is horrible but not intractable to work with.

4. nottorp ◴[15 Apr 25 11:48 UTC] No.43691432[source]▶
Maybe you shouldn't use features that contribute to lock in indeed.
replies(1): >>43691636 #
5. guappa ◴[15 Apr 25 12:16 UTC] No.43691636{3}[source]▶
I don't use github at all…