Actually, it's not fault of git. Workflow of git takes place through email and patches.
But,github wanted to make this process easier for the people,hence they included issues,fork and PR model. It was easily done with intuitive interface without necessity of email for workflow, but if you have asked me, i would have issues,wiki,etc. integrated within repo just like Fossil VCS.
p2p is cool but not solution to this . gitea/gitlab/etc. already provide importing of issues with repos and if not,they must provide that feature.
> Actually, it's not fault of git. Workflow of git takes place through email and patches.
This invokes the "it's not a bug, it's a feature" mechanism. E.g. Fossil has no problem integrating issues, merge requests, and wiki pages inside its repositories.
Yes, but that's a problem for the users which GitHub has every incentive to never solve. It is a problem of github and projects like radicle are a solution.
But,github wanted to make this process easier for the people,hence they included issues,fork and PR model. It was easily done with intuitive interface without necessity of email for workflow, but if you have asked me, i would have issues,wiki,etc. integrated within repo just like Fossil VCS.
p2p is cool but not solution to this . gitea/gitlab/etc. already provide importing of issues with repos and if not,they must provide that feature.