On Mon, Nov 24, 2014 at 6:16 PM, Stephan Beal <sgb...@googlemail.com> wrote:
> Do they have one big shared branch or does each have his own? If the > latter, how do we differentiate the N anonymous users? Maybe give each one > a token (a UUID) unique to his branch? He can share that token with others > to allow pushing to that (anonymous) branch. That would give us a > "mob-branch" style of workflow: a branch using a public login token where > anyone could push to. > On second thought, that would require one level further of authentication, namely against a branch/user/password combination, as opposed to user/password. That would probably be best modeled more generically, not specific to the anonymous user, as once the anonymous user could do such a thing, other people would want to share branches, too. i can conceive of something like this: Bob shares a repo with Alice and Mike, each with their own branch off the trunk. Bob (via some mechanism as yet undefined) has admin rights to that branch (either b/c he is-a Admin or created the branch). With those rights, we visits some new web page and selects "create login token" for his branch. He sends the token to Alice and some buddy of his who is not in the project (an anonymous user). Now Alice and Buddy can commit to Bob's branch, but Mike can't. Bob resp. an Admin can regenerate the login token at any time, invaliding Alice and Buddy's access. Yes, it's fiction, but Richard started it ;). i think this is an idea worth bouncing around. -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal "Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
_______________________________________________ fossil-dev mailing list fossil-dev@lists.fossil-scm.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/fossil-dev
