So I was looking at GitHub and its various ‘tabs’ at the top of the body of the repo: Many of those items can be toggled on and off, and I started to get the sense that these things were basically plugins; so it occurred to me that in decentralized implementation, these items would not have to be built-in or even determinant for every given repo. For instance, a wiki does not have to be included for every repo, but for those that do, they might wish to use a different sort of template or structure or syntax for that wiki, or else they may want to decide whether that wiki should be its own repo, a branch, or merely a directory within their main repo or even built from the very root of the master branch (similar to options available for GitHub Pages). I would imagine much the same approach would prove desirable for discussions, issues, project management, or even features well beyond the scope of what GitHub et al offers.
This would of course allow folks to build their own plugins, which could of course be produced and distributed right on the Radicle protocol.
Expanding on this idea, I’ve recently become quite intrigued with Satellite and got to thinking that this sort of a social instance could prove powerful when attached to a repo: For instance, I imagine anyone following a repo being able to post on its discussion board (if configured that way) but where peers only seed the discussions they decide to seed (the one’s they ‘star’, or else perhaps the ones starred by peers they track) with the repo maintainer(s) ultimately bearing power of moderation.
Anyway, it is opensource, so I imagine it may be possible to adapt to such a purpose:
Hey @RMBLRX - love the idea! I think plugins will probably be very possible in the future. Since Radicle is open-source, people are free to build clients on top of it with different user experiences. Seems like the approach right now is generalizing the protocol so it can be built on as easy as possible
I’ve never heard of Satellite - it looks super cool. I wonder if it could be integrated into Radicle someway…
Yeah, Satellite is one possible example that occurs to me, but another would maybe be an Akasha world (or some adaptation of the Akasha framework, whatever that will ultimately prove to be) being attached to a repo or even somehow linking up to Ethereum World for repos or teams utilizing Ethereum’s functionality in Radicle. As to the former, from what little I understand, it may prove possible to adapt for a variety of tasks beyond, say, discussion.
Just spitballing here, but this sort of extensibility (perhaps somehow accounted for at the level of protocol) would render Radicle into a one-stop shop for the back-end of virtually every aspect of any project presently or prospectively on my plate, which should likely always have git at their core; I suspect also that I’m not alone in this sentiment.