[OE-core] Patch merge process

[Khem Raj]

Hi All,

I thought of bringing this up for discussions, I am seeing that, in some pull requests some patches get dropped and I understand
that there might be a reason for that but that reason is not communicated in proposed patch mail often. I have experienced with some of the
pull requests myself and seen it with some others. I think we are not responding to patches as it should be. Since we follow
just mailing list as upstreaming process thats the only channel that developer is engaged w.r.t. patches and there should be a conclusion
on the mailing list itself for a given patch. So I would request to whoever along with Richard is validating the patches and bringing them to OE-Core from mailing lists to respond to the patches especially the ones that are not applied with reasons why its not applied and similarly to the ones that are applied but has been rejected by some reviewers. It would also be good to document the commit criteria somewhere, so developer can do rework and ease the pressure on maintainers. Can we explore some tools that can help here ? May be failed errors.yp.org output can be sent to list of developers whose patches has been part of staging ?

I think its extremely important to keep a developer informed and engaged about the upstreaming if we want to encourage more voluntary participation in the project.

It would be good to identify where we have bottlenecks and how can we improve upon the situation, ideas are welcome.

Thanks
-Khem

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 204 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20150901/22f610cc/attachment-0002.sig>