On 01/06/11 09:05, Sascha Peilicke wrote:
Otherwise the next commiter might be tempted to add his personal 'osc scratchmyback' command w/o communication too.
I agree.
@suse-tux: For the osc rewrite, I strongly urge you to enforce peer-reviews for commits. Or even better, don't let anyone commit directly but let them file merge requests, which can be reviewed and commented appropriatly. Otherwise the new osc will end up exactly like the current one, as an unmaintainable pile of crap code.
As a user of OBS who has multiple teams who want different workflows I'm very concerned about hardcoding workflow into osc.
We also should think about adapting a similar policy for OBS code, but I fear this would break quite some odd habbits...
This is a reasonable thing to want to do. In Nokia and MeeGo we've been working on BOSS to abstract the workflow out of OBS and into a small and focused workflow system. It allows users of different OBS installations (or even different project areas on the same OBS) to use discrete workflows that interact with other systems like bugzilla or Hermes. David -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org