[oe] Getting patches committed

[Stanislav Brabec]

Rolf Leggewie wrote:

> 2) although generally not a good idea, would it be possible to rebase
>    this branch frequently so that the unapplied patches always come
>    up first in "git log"?

Just a rough idea:


mailing list

Anybody can send a mail with:

[DRAFT] ... controversial patch that needs discussion

[REVIEW] ... core patch or patch that needs review or ACK

[RFC] ... request for comments for large change before starting to do
anything.

[PATCH] ... patch from people that afraid of submitting to git or first
attempts. If no one complies, script auto-moves the patch to
org.openembedded.open


org.openembedded.open (or .staging or .public)

Tree for changes expected to be safe (by the submitter).

Anybody can submit to org.openembedded.open tree.

Anybody can veto (bad approach), amend (fix added to the commit) or
postpone (needs fix) any change in org.openembedded.open. Email will be
generated to discuss and learn submitter.

Changes that did not get veto or postponed will be pushed to
org.openembedded.dev (in most cases with a defined delay, in specific
cases (bug fixes) manually).

Is there any git expert that can comment, whether git makes something
like this possible?


org.openembedded.dev

Users with commit access can commit directly patches expected to be
save.

Everything other goes through .open.

> OE needs a stronger community culture.  Too many devs are just contempt
> with "my stuff works fine for me".

Not as easy as it sounds. OE is a heterogeneous environment. Knowing
that things may break on some platform need non-trivial knowledge.



________________________________________________________________________
Stanislav Brabec
http://www.penguin.cz/~utx/zaurus