4 ms·
If you think about it, there's no particular reasons why the metadata can't live in (and be tracked by) the repo itself. Issues could live in /issues. Simple
by zeveb 9y ago
If you think about it, there's no particular reasons why the metadata can't live in (and be tracked by) the repo itself.
Issues could live in /issues. Simple command-line (or GUI) tools could edit them. I'm thinking in particular of how password-store[0] makes tracking history in a git repo invisible: it Just Works™.
Discussions could live in /discussions, stored in something like RFC822 format. Again, simple CLI (or GUI, if you swing that way) tools could manipulate this easily.
A wiki can, again, live in the same repo.
PRs are a little different, since they really do need to live outside the repo. But what is a PR other than someone saying, 'hey, please pull my branch into yours'?
[0] https://www.passwordstore.org/ https://www.passwordstore.org/
- Klathmon 9y agoPRs and other things could also just live in a "shadow repo". Even if just by convention. You have a `Product` repo and a `Product-meta` repo. The biggest issue I have with using git as a truly decentralized system is remote management. Unless you want to be manually futzing with remotes on every single client and pushing/fetching from others correctly, you need some kind of central server. I really think there is a hole here for a product that works with git underneath, but gives a nice easy way to manage all that complexity.