[oe] A question of workflow

[Matthew Palmer]

On Sun, Jan 07, 2007 at 11:16:32PM +0200, Paul Sokolovsky wrote:
>   Well, why would OE core developers (err, what about non-core
> developers - we also care for contributed patches - after all, to get
> commit access to OE, you first contribute bunch of patches) - well, why
> would they do that? OE is open-source project, there's no position of
> "patch processor", and people do what they find useful, leaving some
> share of their for patch processing. Any complex and artificial rules
> won't work.

The only reason I can think of for the core devs to follow a particular
workflow is to make it ultimately easier for external contributors to
produce and submit patches.  The more external patches that come in, the
less work the core devs have to do (or the more 'other' things they can do). 
For example, a few days ago Marcin asked for a patch to make a build of a
newer version of fakeroot; I'd have whipped that patch up by now except that
I know that it's going to cause a conflict when the change comes back down,
so I'm loathe to make the change until I work out how I can manage the patch
flow, because it's going to cause me pain without any benefit.  I'm just not
that masochistic.

- Matt