From: Jani Nikula <jani.nikula@intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: dim-tools@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org, rodrigo.vivi@intel.com
Subject: Re: [maintainer-tools PATCH] doc: how to become a drm-intel committer
Date: Thu, 15 Mar 2018 17:32:53 +0200 [thread overview]
Message-ID: <87lgetl5ga.fsf@intel.com> (raw)
In-Reply-To: <20180315140247.GD25297@phenom.ffwll.local>
On Thu, 15 Mar 2018, Daniel Vetter <daniel@ffwll.ch> wrote:
> On Wed, Mar 14, 2018 at 05:11:02PM +0200, Jani Nikula wrote:
>> Until now, the drm-intel commit access have been handed out ad hoc,
>> without transparency, consistency, or fairness. With pressure to add
>> more committers, this is no longer tenable, if it ever was. Document the
>> requirements and expectations around becoming a drm-intel committer.
>>
>> The Linux kernel operates in a model where, by and large, only
>> maintainers commit patches. Maintainer teams are no longer rare, but the
>> drm-intel and drm-misc maintainer/committer model is definitely an
>> outlier.
>>
>> The drm-intel maintainers believe that a reasonable level of experience
>> and track record of working on the driver, as well as actively engaging
>> in the community upstream, are necessary before becoming a
>> committer. While the requirements outlined here may seem strict in
>> contrast with many projects, they are extremely liberal by kernel
>> standards.
>>
>> Finally, no rules are carved in stone. We fully expect the requirements
>> to be adjusted later. However, it will be much easier to start strict
>> and relax the requirements later than the other way round.
>>
>> Cc: Gustavo Padovan <gustavo@padovan.org>
>> Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
>> Cc: Sean Paul <seanpaul@chromium.org>
>> Cc: Dave Airlie <airlied@gmail.com>
>> Cc: dim-tools@lists.freedesktop.org
>> Cc: dri-devel@lists.freedesktop.org
>> Cc: intel-gfx@lists.freedesktop.org
>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>> Signed-off-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
>> Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
>
> I've chatted for a few hours with Joonas, and I think before we can
> discuss the proposed document here itself, we first need to reach some
> agreement on why we even have commit rights. I think there's a very wide
> range of answers to that questions, and of course with different goals you
> end up with completely different rules about how to handle commit rights.
>
> Joonas suggested we first discuss this internally, perhaps with the
> maintainers, Kimmo and me.
Fine. I would rather have discussed this transparently out in the
open. That was, after all, the purpose of sending this out.
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-03-15 15:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-14 15:11 [maintainer-tools PATCH] doc: how to become a drm-intel committer Jani Nikula
2018-03-15 14:02 ` Daniel Vetter
2018-03-15 15:32 ` Jani Nikula [this message]
2018-03-15 18:27 ` Daniel Vetter
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=87lgetl5ga.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=daniel@ffwll.ch \
--cc=dim-tools@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=rodrigo.vivi@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox