10 ms·

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/

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 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/ https://developer.github.com/v3/issues/)

organsnyder 7y ago
I'd love to see a standard develop for storing this information in-repo. GitHub could certainly drive such an initiative.
- Ironchefpython 7y ago
  You might be thinking about fossil. Every feature is in-repo. https://fossil-scm.org/home/doc/trunk/www/index.wiki https://fossil-scm.org/home/doc/trunk/www/index.wiki
  - carlmr 7y ago
    That looks really cool. Is anybody already using this?
    - rkeene2 7y ago
      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/ http://chiselapp.com/user/rkeene/
- Pawamoy 7y ago
  There's git-bug: https://github.com/MichaelMure/git-bug https://github.com/MichaelMure/git-bug
erk__ 7y ago
Well I guess they also have to make this possible as it is one of the principles in GDPR. Data portability