Let writers generate N-use invite codes, CODE, and then new users can do git clone hypergit://KEY+CODE to do a fresh clone and have write access instantly.
While running hypergit seed writers could receive requests from other peers to be granted write permissions at replication-time.
OK, I'm leaning away from this model. I think a model that encourages no-hierarchy will work better. I'll try and get some workflow write-ups on here soon!
Ideas from pvh on
#dat
freenode:CODE
, and then new users can dogit clone hypergit://KEY+CODE
to do a fresh clone and have write access instantly.hypergit seed
writers could receive requests from other peers to be granted write permissions at replication-time.