Re:GitHub Package Registry
by soulofmischief on Saturday May 11, 2019 @05:42AM
(#19885398)
Your sister comment had another project to share based on IPFS: https://radicle.xyz/
One thing that seems clear is that there needs to be a standard interchangeable format for storing PRs and issues, so that it's not just the point of origin that's decentralized, but the data itself (in case the maintainers vanish).
I'm not really sure how to go about that sort of thing either myself or as a community effort but I'd appreciate any advice from the HN community.
Re:GitHub Package Registry
by chriswarbo on Sunday May 12, 2019 @09:08AM
(#19891636)
> One thing that seems clear is that there needs to be a standard interchangeable format for storing PRs and issues, so that it's not just the point of origin that's decentralized, but the data itself (in case the maintainers vanish).
I use Artemis for issue tracking, and that uses maildir (a widely supported standard). I compose issues with Emacs message-mode and render them to HTML using mhonarc.
> anybody can push to anybody else's git repository. [...]
The nomenclature is to treat the ssb remote as the "true" remote, and work off of a branch called @your-username/master as your own master, emulating a forked repo. This seems to work well: the SSB network thrives off of being a group of kind, respectful folks who don't push to each other's master branch. :)
Uh, thanks but no thanks. I thought we had learnt that the honor system does not scale.
https://github.com/noffle/git-ssb-intro