From: "Frank Schäfer" <fschaefer.oss@googlemail.com>
To: Mauro Carvalho Chehab <mchehab@redhat.com>
Cc: linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: RFC: First draft of guidelines for submitting patches to linux-media
Date: Tue, 11 Dec 2012 21:41:17 +0100 [thread overview]
Message-ID: <50C79A6D.9010008@googlemail.com> (raw)
In-Reply-To: <20121210174036.03dd521c@redhat.com>
Am 10.12.2012 20:40, schrieb Mauro Carvalho Chehab:
[snip]
>> And people beeing subsystem maintainers AND driver maintainers have to
>> find a balance between processing pull requests and reviewing patches.
>> I'm not sure if I have understood yet how this balance should look
>> like... Can you elaborate a bit on this ?
>> At the moment it's ~12 weeks / ~2 weeks. What's the target value ? ;)
> Please wait for it to be implemented before complaining it ;) The
> sub-maintainers new schema will start to work likely by Feb/Mar 2013.
I don't want to complain (yet ;) ). I'm just trying to understand what
is supposed to reduce the review times...
Haven't succeeded yet, because the same amount work seems to be
redivided among the same amount of maintainer/reviewer resources (=people).
Anyway, I will be patient and hope that things will evolve as planed.
I will also try to test and/or review patches from other if possible.
[snip]
>> So who can get an account / is supposed to access patchwork ?
>> - subsystem maintainers ?
>> - driver maintainers ?
>> - patch creators ?
> Subsystem maintainers only, except if someone can fix patchwork, adding
> proper ACL's there to allow patch creators to manage their own patches
> and sub-system maintainers to delegate work to driver maintainers, without
> giving them full rights, and being notified about status changes on
> those driver's patches.
Ok, thanks, I think this should be mentioned in the document.
Regards,
Frank
next prev parent reply other threads:[~2012-12-11 20:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-10 13:07 RFC: First draft of guidelines for submitting patches to linux-media Hans Verkuil
2012-12-10 15:56 ` Frank Schäfer
2012-12-10 16:27 ` Hans Verkuil
2012-12-10 17:38 ` Mauro Carvalho Chehab
2012-12-10 17:45 ` Antti Palosaari
2012-12-10 18:43 ` Mauro Carvalho Chehab
2012-12-10 19:17 ` Frank Schäfer
2012-12-10 19:40 ` Mauro Carvalho Chehab
2012-12-11 20:41 ` Frank Schäfer [this message]
2012-12-10 18:33 ` Mauro Carvalho Chehab
2012-12-10 23:52 ` Laurent Pinchart
2012-12-11 10:29 ` Mauro Carvalho Chehab
2012-12-11 11:39 ` Laurent Pinchart
2012-12-11 12:59 ` Mauro Carvalho Chehab
2012-12-11 11:50 ` Hans Verkuil
2012-12-11 12:20 ` Laurent Pinchart
2012-12-11 15:13 ` Mauro Carvalho Chehab
2012-12-11 14:31 ` Mauro Carvalho Chehab
2012-12-11 13:15 ` Hans Verkuil
2012-12-11 15:17 ` Mauro Carvalho Chehab
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=50C79A6D.9010008@googlemail.com \
--to=fschaefer.oss@googlemail.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.