From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] review process
Date: Sat, 28 Aug 2010 12:25:42 +0200 [thread overview]
Message-ID: <i5ao76$sja$1@dough.gmane.org> (raw)
In-Reply-To: <AANLkTin5LRCz6PU_x6Mw+V2Xf8W=i+n4RLqQjwON1R7+@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 27-08-10 14:15, Frans Meulenbroeks wrote:
> It is a good rule that important changes (toolchain, infrastructure)
> are reviewed before being committed.
> This is e.g. also specified in
> http://wiki.openembedded.net/index.php/Commit_Policy
>
> However, recently I've seen some issues that our review process does
> not seem to work or is abused.
>
> I see two things happening.
> - patches are submitted for review but do not gain any feedback in a
> reasonable time. I have several patches in the queue that did not get
> any feedback.
> - people are abusing their powers by rejecting changes without
> motivation. See e.g [1] and [2]. I feel if you reject a patch you have
> an obligation to explain why you rejected it.
If you want to delete a recipe I maintain, the burden is on you or are
you saying that maintainers aren't in charge of their recipes anymore?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFMeOQmMkyGM64RGpERAu7PAKCgv9CNgRClgz28jyNeHqANqgBsdwCgr4Lp
g5tptYYjCTFtUZnOukdJ3Kg=
=wUcg
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-08-28 10:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-27 12:15 [RFC] review process Frans Meulenbroeks
2010-08-27 12:24 ` Graeme Gregory
2010-08-27 12:29 ` Gary Thomas
2010-08-27 12:33 ` Frans Meulenbroeks
2010-08-27 12:37 ` Dr. Michael Lauer
2010-08-27 13:46 ` Execution of Build Output Failing (Testing) openembedded
2010-08-27 17:41 ` Khem Raj
2010-08-27 19:37 ` openembedded
2010-08-27 15:11 ` [RFC] review process Roman I Khimov
2010-08-28 10:25 ` Koen Kooi [this message]
2010-08-28 12:17 ` Frans Meulenbroeks
2010-09-06 18:54 ` Frans Meulenbroeks
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='i5ao76$sja$1@dough.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox