[openbeos] Re: Organizational question

> >
> > For non-members, we'd have a similar scheme to what OpenTracker had
> > back in the day; have a user called "readonly", and then each 
> > member
> > would set their client to "FirstnameLastname_computer". In the
> > protections table, one could set it up so such that the wouldn't be
> > able to clobber the main branch, but instead only be able to play
> > within some protected branch, say //depot/exp/user/... After that,
> > someone could use p4 integrate to merge their changes with the main
> > line.
> 
> To be honest, this seems like an (ugly) workaround, instead of a 
> final
> solution. You are giving complete strangers full commit status to 
> your
> source control system, which is bad. Rather let them make local
> branches that a maintainer (who has to merge anyway) can merge in.
> 
Yeah, exactly what I said.  The local branch would still have to be on 
the server, because of the way Perforce is set up.

--
Mikael Jansson
http://mikael.jansson.be

Other related posts: