News for hackers. Stuff that matters.
Re:What is a fork, and how GitHub changed its meaning by perennate on Friday May 24, 2019 @05:55PM (#20005631)
I'd argue that at least their API indicates they try to reduce rather than reinforce this lock-in. The API lets you build tools like https://github.com/colmsjo/github-issues-export to automatically export data from issues and other project data stored outside of git.

Moving this data is still not trivial but I don't think GitHub could unilaterally make it much easier.

(https://developer.github.com/v3/issues/)

Re:What is a fork, and how GitHub changed its meaning by organsnyder on Friday May 24, 2019 @09:07PM (#20006524)
I'd love to see a standard develop for storing this information in-repo. GitHub could certainly drive such an initiative.
Re:What is a fork, and how GitHub changed its meaning by Ironchefpython on Friday May 24, 2019 @11:45PM (#20006981)
You might be thinking about fossil. Every feature is in-repo.

https://fossil-scm.org/home/doc/trunk/www/index.wiki

Re:What is a fork, and how GitHub changed its meaning by carlmr on Saturday May 25, 2019 @04:59AM (#20007846)
That looks really cool. Is anybody already using this?
Re:What is a fork, and how GitHub changed its meaning by rkeene2 on Saturday May 25, 2019 @09:49AM (#20009023)
Well, SQLite is using it of course ;-)

Other large projects include Tcl/Tk and many related extensions, as well as all the cool stuff I write:

http://chiselapp.com/user/rkeene/

Re:What is a fork, and how GitHub changed its meaning by Pawamoy on Saturday May 25, 2019 @07:32AM (#20008401)
Re:What is a fork, and how GitHub changed its meaning by erk__ on Saturday May 25, 2019 @07:13AM (#20008323)
Well I guess they also have to make this possible as it is one of the principles in GDPR. Data portability