8 ms·

How is it at all odd? Github offers a convenient platform for using git. People use it. If Github were to explode forever tomorrow, active projects would jus

How is it at all odd? Github offers a convenient platform for using git. People use it. If Github were to explode forever tomorrow, active projects would just take their locally cloned repositories, and put them online somewhere else and carry on committing (albeit sans github's awesome social tools). That's the real power git offers us. It's just a fact of reality that most projects centrally organize through a few bottlenecks. It's easier for people to remember where to go, if there's only one place to go to. But if you're really concerned about it, i suppose you could build a tool to automatically sync a github repo w/ another 3rd party host if you wanted (or visaversa).

appplemac 13y ago
Yes, but Github is not just about Git hosting, it's about all those awesome social tools. If you use Issues as the main bug tracker, for example, you've got a problem.
- justizin 13y ago
  Please point me at your distributed issue tracker project. I'd love to contribute!
  - ryanpetrich 13y ago
    Fossil includes distributed issue tracking: http://www.fossil-scm.org http://www.fossil-scm.org
  - mpyne 13y ago
    At KDE we use Bugzilla with automatic status emails to various mailing lists and projects. So even if bugs.kde.org were to go down, we'd still be able to fix code at git.kde.org, and use the lists.kde.org mailing list archives to lookup bug details as a backup. We'd probably use a mailing list system that doesn't suck like kde.markmail.org or GMANE for that last part, but that's just shaving the yak...
  - kanzure 13y ago
    http://bugseverywhere.org/ http://bugseverywhere.org/ does distributed bug tracking.
  - dkubb 13y ago
    I've often wondered if we could store issues in a separate branch.
  - elviejo 13y ago
    Also http://www.onveracity.com/ http://www.onveracity.com/ offers distributed version control, and distributed tickets, and wiki.
- bsimpson 13y ago
  mpyne mentions bugs.kde.org's mailings as a fallback, but GitHub issues e-mails too.
phaer 13y ago
Yes, there is nothing wrong with using Github, but with using only Github as your git remote. Git (in theory) makes it easy to use multiple servers. Add some scripts/utilities and you get Github with all their "social" stuff, wikis and issue trackers plus higher availability if Github goes down; just use your other remotes. Is there a git tool to share your remotes in a repository? One could use a distributed issue tracker like "Bugs Everywhere"[1] or git-issues[2]. Are there ways to "sync" them with Github's issues? [1]: http://bugseverywhere.org/ http://bugseverywhere.org/ [2]: https://github.com/jwiegley/git-issues https://github.com/jwiegley/git-issues
- ianstormtaylor 13y ago
  "Add some scripts/utilities and you get Github with all their "social" stuff, wikis and issue trackers ..." It's crazy how GitHub's entire product is so easily marginalized by comments like this. I don't know if you meant to do it, but I think it is a serious problem with hacker culture. It's the kind of thinking that tricks startups into "knowing" they can do a better job than established competitors in spaces they know close to nothing about, because they "know" they can execute better. I speak from personal experience here. I can guarantee that no amount of "adding some scripts/utilities" will get near what GitHub's service offers.
  - saraid216 13y ago
    Here's the relevant HN link: https://news.ycombinator.com/item?id=5807770 https://news.ycombinator.com/item?id=5807770
  - k3n 13y ago
    I'd disagree, on paper Github has a nice suite of services, arguably best-in-class for some of them, but that doesn't make them untouchable. Github is only the latest in a line of code-hosting services. Just because you tried and failed, doesn't mean every try will fail.
  - IanCal 13y ago
    You may have misunderstood the comment (or I have). I don't think they were saying that a few scripts and utilities would get you what github offers. I think they were saying with some scripts you could automatically fall over to another mirror when github goes down, then switch back when it's up (updating the repo on github when it's available again).

appplemac 13y ago

Yes, but Github is not just about Git hosting, it's about all those awesome social tools. If you use Issues as the main bug tracker, for example, you've got a problem.

justizin 13y ago
Please point me at your distributed issue tracker project. I'd love to contribute!
- ryanpetrich 13y ago
  Fossil includes distributed issue tracking: http://www.fossil-scm.org http://www.fossil-scm.org
- mpyne 13y ago
  At KDE we use Bugzilla with automatic status emails to various mailing lists and projects. So even if bugs.kde.org were to go down, we'd still be able to fix code at git.kde.org, and use the lists.kde.org mailing list archives to lookup bug details as a backup. We'd probably use a mailing list system that doesn't suck like kde.markmail.org or GMANE for that last part, but that's just shaving the yak...
- kanzure 13y ago
  http://bugseverywhere.org/ http://bugseverywhere.org/ does distributed bug tracking.
- dkubb 13y ago
  I've often wondered if we could store issues in a separate branch.
- elviejo 13y ago
  Also http://www.onveracity.com/ http://www.onveracity.com/ offers distributed version control, and distributed tickets, and wiki.
bsimpson 13y ago
mpyne mentions bugs.kde.org's mailings as a fallback, but GitHub issues e-mails too.

phaer 13y ago

Yes, there is nothing wrong with using Github, but with using only Github as your git remote. Git (in theory) makes it easy to use multiple servers. Add some scripts/utilities and you get Github with all their "social" stuff, wikis and issue trackers plus higher availability if Github goes down; just use your other remotes. Is there a git tool to share your remotes in a repository? One could use a distributed issue tracker like "Bugs Everywhere"[1] or git-issues[2]. Are there ways to "sync" them with Github's issues? [1]: http://bugseverywhere.org/ http://bugseverywhere.org/ [2]: https://github.com/jwiegley/git-issues https://github.com/jwiegley/git-issues

ianstormtaylor 13y ago
"Add some scripts/utilities and you get Github with all their "social" stuff, wikis and issue trackers ..." It's crazy how GitHub's entire product is so easily marginalized by comments like this. I don't know if you meant to do it, but I think it is a serious problem with hacker culture. It's the kind of thinking that tricks startups into "knowing" they can do a better job than established competitors in spaces they know close to nothing about, because they "know" they can execute better. I speak from personal experience here. I can guarantee that no amount of "adding some scripts/utilities" will get near what GitHub's service offers.
- saraid216 13y ago
  Here's the relevant HN link: https://news.ycombinator.com/item?id=5807770 https://news.ycombinator.com/item?id=5807770
- k3n 13y ago
  I'd disagree, on paper Github has a nice suite of services, arguably best-in-class for some of them, but that doesn't make them untouchable. Github is only the latest in a line of code-hosting services. Just because you tried and failed, doesn't mean every try will fail.
- IanCal 13y ago
  You may have misunderstood the comment (or I have). I don't think they were saying that a few scripts and utilities would get you what github offers. I think they were saying with some scripts you could automatically fall over to another mirror when github goes down, then switch back when it's up (updating the repo on github when it's available again).