4 ms·

> Github can shut down next year all the sudden and you can lose everything… This is entirely false, if github shuts down tomorrow you don't lose everything. I

> Github can shut down next year all the sudden and you can lose everything… This is entirely false, if github shuts down tomorrow you don't lose everything. In fact, most likely you don't lose anything, since the git repo on your computer has everything. This is the only reason I use Github, myself. It's not like the old days of Sourceforge hosted CVS servers where you didn't actually have access to your data.

anko 12y ago
How about github issues? Is there a way to export that info? I'm not against github (in fact i like it very much) but issues does seem to impose a little lockin.
- mbleigh 12y ago
  The GitHub API is extremely robust. You can export issues, including comments etc. to JSON with a script that will take you maybe 10 minutes to write, max.
  - sharyanto 12y ago
    There should be (or is there already?) a script that automatically downloads an issue and its conversation in text or JSON format and commits it so the data/archive is in the git repo.
yeukhon 12y ago
As someone else already mentioned, this is not entirely false. You will lose your issues which is a huge reason why big projects don't move to Github. You lose your wikis. You don't run backup of your issues every day, do you? In fact, how many of you do that? I bet the number is almost zero. Source code is one thing, but the history of discussion? That worth something. Also, sometimes some repos just don't exist on your computer anymore or out of sync because you done work on multiple computers. Or if your computer is stolen.
- __david__ 12y ago
  I don't care about issues or wikis. I don't use either feature in the projects that originate from me (people send me issues but I don't use them to organize development). The code is the important part. Any discussion is already backed up in my email. And even if I did care about issues I could download them through the api, as was pointed out elsewhere.

anko 12y ago

How about github issues? Is there a way to export that info? I'm not against github (in fact i like it very much) but issues does seem to impose a little lockin.

mbleigh 12y ago
The GitHub API is extremely robust. You can export issues, including comments etc. to JSON with a script that will take you maybe 10 minutes to write, max.
- sharyanto 12y ago
  There should be (or is there already?) a script that automatically downloads an issue and its conversation in text or JSON format and commits it so the data/archive is in the git repo.

yeukhon 12y ago

As someone else already mentioned, this is not entirely false. You will lose your issues which is a huge reason why big projects don't move to Github. You lose your wikis. You don't run backup of your issues every day, do you? In fact, how many of you do that? I bet the number is almost zero. Source code is one thing, but the history of discussion? That worth something. Also, sometimes some repos just don't exist on your computer anymore or out of sync because you done work on multiple computers. Or if your computer is stolen.

__david__ 12y ago
I don't care about issues or wikis. I don't use either feature in the projects that originate from me (people send me issues but I don't use them to organize development). The code is the important part. Any discussion is already backed up in my email. And even if I did care about issues I could download them through the api, as was pointed out elsewhere.