[PATCH] drm-misc.rst: Document commit rights

[Daniel Vetter]

On Thu, Apr 26, 2018 at 4:25 PM, Daniel Vetter <daniel.vetter at ffwll.ch> wrote:
> This is the exact same text as proposed&merged for igt:
>
> https://patchwork.kernel.org/patch/10339739/
>
> With one minor change: Both regular contributions to the kernel
> overall and to userspace graphics counts. We've gained a few
> committers in the past who are coming from arm-soc platform work and
> similar areas, to upstream&maintain drm drivers for their platform.
>
> For simplicity I've kept the same massive Cc: list.
>
> Cc: Alex Deucher <alexander.deucher at amd.com>
> Cc: Arkadiusz Hiler <arkadiusz.hiler at intel.com>
> Cc: Ben Widawsky <ben at bwidawsk.net>
> Cc: Daniel Stone <daniel at fooishbar.org>
> Cc: Dave Airlie <airlied at gmail.com>
> Cc: Eric Anholt <eric at anholt.net>
> Acked-by: Gustavo Padovan <gustavo at padovan.org>
> Cc: Gustavo Padovan <gustavo at padovan.org>
> Cc: Jani Nikula <jani.nikula at intel.com>
> Cc: Joonas Lahtinen <joonas.lahtinen at linux.intel.com>
> Cc: Keith Packard <keithp at keithp.com>
> Cc: Kenneth Graunke <kenneth at whitecape.org>
> Cc: Kristian H. Kristensen <hoegsberg at google.com>
> Acked-by: Maarten Lankhorst <maarten.lankhorst at linux.intel.com>
> Cc: Maarten Lankhorst <maarten.lankhorst at linux.intel.com>
> Cc: Petri Latvala <petri.latvala at intel.com>
> Cc: Rodrigo Vivi <rodrigo.vivi at intel.com>
> Acked-by: Sean Paul <seanpaul at chromium.org>
> Cc: Sean Paul <seanpaul at chromium.org>
> Cc: Keith Packard <keithp at keithp.com>
> Signed-off-by: Daniel Vetter <daniel.vetter at intel.com>

So after pushing this patch accidentally instead of the dim bugfix I
also forgot to cc dim-tools when sending it out.

Really not the best day today ...
-Daniel
> ---
>  drm-misc.rst | 48 ++++++++++++++++++++++++++++++++++++++++++++++++
>  1 file changed, 48 insertions(+)
>
> diff --git a/drm-misc.rst b/drm-misc.rst
> index 187a4df07ad4..21cbaefda9aa 100644
> --- a/drm-misc.rst
> +++ b/drm-misc.rst
> @@ -174,6 +174,54 @@ Maintainers mostly provide services to keep drm-misc running smoothly:
>  * Take the blame when something goes wrong. Maintainers interface and represent
>    the entire group of committers to the wider kernel community.
>
> +Commit Rights
> +=============
> +
> +Commit rights will be granted to anyone who requests them and fulfills the
> +below criteria:
> +
> +- Submitted a few (5-10 as a rule of thumb) non-trivial (not just simple
> +  spelling fixes and whitespace adjustment) patches that have been merged
> +  already.
> +
> +- Are actively participating on discussions about their work (on the mailing
> +  list or IRC). This should not be interpreted as a requirement to review other
> +  peoples patches but just make sure that patch submission isn't one-way
> +  communication. Cross-review is still highly encouraged.
> +
> +- Will be regularly contributing further patches. This includes regular
> +  contributors to other parts of the linux kernel or the open source graphics
> +  stack who only do the oddball rare patch within drm-misc itself.
> +
> +- Agrees to use their commit rights in accordance with the documented merge
> +  criteria, tools, and processes.
> +
> +Apply for an account (and any other account change requests) through
> +
> +https://www.freedesktop.org/wiki/AccountRequests/
> +
> +and please ping the maintainers if your request is stuck.
> +
> +Committers are encouraged to request their commit rights get removed when they
> +no longer contribute to the project. Commit rights will be reinstated when they
> +come back to the project.
> +
> +Maintainers and committers should encourage contributors to request commit
> +rights, especially junior contributors tend to underestimate their skills.
> +
> +Code of Conduct
> +===============
> +
> +Please be aware the fd.o Code of Conduct also applies to drm-misc:
> +
> +https://www.freedesktop.org/wiki/CodeOfConduct/
> +
> +See the MAINTAINERS file for contact details of the drm-misc maintainers.
> +
> +Abuse of commit rights, like engaging in commit fights or willfully pushing
> +patches that violate the documented merge criteria, will also be handled through
> +the Code of Conduct enforcement process.
> +
>  Tooling
>  =======
>
> --
> 2.17.0
>



-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch