5 ms·

From what I've gathered and seen around the web the problem isn't really that git isn't decentralized, it's that it's purely a code versioning tool. With GitHub

by sondr3 9y ago

From what I've gathered and seen around the web the problem isn't really that git isn't decentralized, it's that it's purely a code versioning tool. With GitHub you have a community, an issue tracker, a wiki, possibly a website hosted with them and so on. Honestly, the biggest hurdle is just community. By not using GitHub you are losing a ton of potential contributors and users just by lack of exposure. It saddens me a bit, but I can live with it. I host my own Git, am setting up a Drone testing server but still mirror everything to GitHub.

zokier 9y ago
It is unfortunate that project management tools that build on top of git instead of around git haven't really managed to succeed enough on a wider scale to coalesce into a some degree of defacto standard.
- TillE 9y ago
  It's pretty surprising to me that there's only one or two serious attempts (eg, Fossil) at bundling a bug tracker and stuff inside a DVCS repository, so you keep everything together with the code. I was looking at this a year or two ago and couldn't find anything which met my particular requirements. It doesn't even need to be standardized, just reasonably portable.
  - zokier 9y ago
    I haven't kept count, but I think I've seen like a dozen attempts of making git-based issue trackers over the times. Of course it is debatable how "serious" these attempts ever have been.
    - pknopf 9y ago
      http://sit-it.org/ http://sit-it.org/ > Of course it is debatable how "serious" these attempts ever have been. I doubt things like this will really gain traction. I mean, you could always host your own GitLab instance for free if you are worried about GitHub ever going down. The ergonomics are terrible. For me to submit a bug, are you really telling me that I need to fork a repository, commit my issue and then submit a pull-request? Ughh, pass...
      - db48x 9y ago
        Most in-repository bug trackers have (or plan to have) a way to get bug reports committed to the repository automatically, usually via email or a web site.
        pknopf 9y ago
        So now your decentralized solution requires a server running somewhere. Why not just install GitLab or Bugzilla on that server? This reminds me of something someone (forgot who) said, "If it can be built with JavaScript, for better or for worse, it will be." I think the same thing applies blockchain and edge-computing.
        db48x 9y ago
        For the same reason that you could use cvs or svn, but choose to use git: if the bug database is part of the source-code repository (or is checked into the repository, which is much the same thing), then it goes with you when you're offline. You might be riding a train through the Rockies, but you can still add new bug reports, and mark existing ones fixed, as part of your normal work and then push those commits to the server when the train stops in Denver. You probably still have a server holding a copy of the repository that you can push your commits to simply because it simplifies the logistics. Likewise you would want a server hosting a web view of the bug database, because it simplifies the logistics. Think of the layers of management who you would have to teach git commands to, or the QA department who were still using spreadsheets a few years ago.
        pknopf 9y ago
        > You might be riding a train through the Rockies, but you can still add new bug reports So, you want to loose-out on the many benefits of having <best-in-class> issue system because of that one time you decide to dev on a moving train? Open up notepad, man. Your next stop is only a few hours away.
        9y ago
  - pknopf 9y ago
    http://sit-it.org/ http://sit-it.org/

by sondr3 9y ago

zokier 9y ago

It is unfortunate that project management tools that build on top of git instead of around git haven't really managed to succeed enough on a wider scale to coalesce into a some degree of defacto standard.

TillE 9y ago
It's pretty surprising to me that there's only one or two serious attempts (eg, Fossil) at bundling a bug tracker and stuff inside a DVCS repository, so you keep everything together with the code. I was looking at this a year or two ago and couldn't find anything which met my particular requirements. It doesn't even need to be standardized, just reasonably portable.
- zokier 9y ago
  I haven't kept count, but I think I've seen like a dozen attempts of making git-based issue trackers over the times. Of course it is debatable how "serious" these attempts ever have been.
  - pknopf 9y ago
    http://sit-it.org/ http://sit-it.org/ > Of course it is debatable how "serious" these attempts ever have been. I doubt things like this will really gain traction. I mean, you could always host your own GitLab instance for free if you are worried about GitHub ever going down. The ergonomics are terrible. For me to submit a bug, are you really telling me that I need to fork a repository, commit my issue and then submit a pull-request? Ughh, pass...
    - db48x 9y ago
      Most in-repository bug trackers have (or plan to have) a way to get bug reports committed to the repository automatically, usually via email or a web site.
      - pknopf 9y ago
        So now your decentralized solution requires a server running somewhere. Why not just install GitLab or Bugzilla on that server? This reminds me of something someone (forgot who) said, "If it can be built with JavaScript, for better or for worse, it will be." I think the same thing applies blockchain and edge-computing.
        db48x 9y ago
        For the same reason that you could use cvs or svn, but choose to use git: if the bug database is part of the source-code repository (or is checked into the repository, which is much the same thing), then it goes with you when you're offline. You might be riding a train through the Rockies, but you can still add new bug reports, and mark existing ones fixed, as part of your normal work and then push those commits to the server when the train stops in Denver. You probably still have a server holding a copy of the repository that you can push your commits to simply because it simplifies the logistics. Likewise you would want a server hosting a web view of the bug database, because it simplifies the logistics. Think of the layers of management who you would have to teach git commands to, or the QA department who were still using spreadsheets a few years ago.
        pknopf 9y ago
        > You might be riding a train through the Rockies, but you can still add new bug reports So, you want to loose-out on the many benefits of having <best-in-class> issue system because of that one time you decide to dev on a moving train? Open up notepad, man. Your next stop is only a few hours away.
        9y ago
- pknopf 9y ago
  http://sit-it.org/ http://sit-it.org/