4 ms·

Sad day. Don't forget that github is a closed source tool. This is equivalent to them announcing they are switching to Jira.

• Karunamon 10y ago
  Both of those products allow for trivial data import/export. What exactly is the problem?
  • hueving 10y ago
    They are closed source. People that are really serious about open source software from top to bottom have issues with dependencies on closed source tooling because it promotes an ethos they don't support.
    • Karunamon 10y ago
      Ah.. I was hoping there was a substantial practical reason that I had overlooked.
      • hueving 10y ago
        Ah, the classic open source freerider. Only support it when convenient, ignore every other situation.
    • deleted 10y ago
      [deleted]
  • a3_nm 10y ago
    They are using pull requests on Github, and I don't think that these are trivial to import/export.
    • emidln 10y ago
      This is well-documented[1] in their API. You can list a repo's PRs and the associated metadata/links that make most of the github ui work (code reviews, linked comments, commit statuses, etc). [1] https://developer.github.com/v3/pulls/ https://developer.github.com/v3/pulls/
      • a3_nm 10y ago
        Having a documented API is nice, but I still wouldn't call it "trivial" to migrate out of. Besides, we don't know if this API is going to stay around forever or whether it will be discontinued. (Unlike, e.g., the git repository itself, which will always be self-contained so easy to migrate away if needed.)