FreeLists / openbeos / [openbeos] Re: Organizational question

[Niels Reedijk <Niels.Reedijk@xxxxxxxxx>]

> > IMHO, if the main devs get the same "instant-commit" feature and
> > functionality of CVS they are happier (does arch allow this, too?).
> > The problem is that non-members cannot commit changes easily which
> > often prevents them from fixing a bug. Does p4 solve that issue (or
> > could we
> > use two separate branches or repositories and sync them?)?
> >
> This says more about branching:
>
> http://www.perforce.com/perforce/doc.042/manuals/p4guide/
> 09_branching.html
> http://www.perforce.com/perforce/doc.042/manuals/cmdref/integrate.html
>
> 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.

Niels Reedijk