5 ms·

I see where you're coming from, but that does create a big barrier to decentralization. The youtube-dl source code is safe and sound but as far as I know all th

• kevincox 6y ago
  > all the issues, discussions, unmerged PRs and more are lost forever I don't see your argument here. Any decentralized solution wouldn't really help here if it wasn't used. And if it was used any decentralized solution would have helped even if it wasn't built into git. Is the argument that if we bundled it together people would be more likely to use it?
  • simias 6y ago
    Of course, that's precisely the argument. Currently cloning a git repository is trivial, you can have different branches targeting different remotes etc... It's decentralized at the core. An issue solution that built on top of this architecture would be very powerful and "just work" while a solution built on the side will face an uphill battle for adoption. Basically my point is that I consider issues to be an integral part of a repository's history, and it's a weakness of VCSs not to integrate it. A lot of the time I find Github comments on a feature/issue to be vastly more interesting and important than the resulting commit message.
    • kevincox 6y ago
      That makes sense. My counter argument is that even if it was built in it is unlikely to be good enough to be used by the majority of projects. But maybe I'm over estimating the difficulty of making a top quality issue tracker and code review tool.