[dpdk-dev] doc: add maintainer role about replying questions

Message ID 1489485616-30291-1-git-send-email-thomas.monjalon@6wind.com (mailing list archive)
State Accepted, archived
Delegated to: Thomas Monjalon
Headers

Checks

Context Check Description
ci/Intel-compilation success Compilation OK
ci/checkpatch success coding style OK

Commit Message

Thomas Monjalon March 14, 2017, 10 a.m. UTC
  The first line of the MAINTAINERS file are:
"
The intention of this file is to provide a set of names that we can rely on
for helping in patch reviews and questions.
"

Unfortunately, some maintainers do not endorse their role for questions
asked on the mailing list.
Hope making it clear in the contribution guide will enforce more
responsive maintainer participation.

Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com>
---
 doc/guides/contributing/patches.rst | 1 +
 1 file changed, 1 insertion(+)
  

Comments

John McNamara March 22, 2017, 11:18 p.m. UTC | #1
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Thomas Monjalon
> Sent: Tuesday, March 14, 2017 10:00 AM
> To: dev@dpdk.org
> Subject: [dpdk-dev] [PATCH] doc: add maintainer role about replying
> questions
> 
> The first line of the MAINTAINERS file are:
> "
> The intention of this file is to provide a set of names that we can rely
> on for helping in patch reviews and questions.
> "
> 
> Unfortunately, some maintainers do not endorse their role for questions
> asked on the mailing list.
> Hope making it clear in the contribution guide will enforce more
> responsive maintainer participation.
> 
> Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com>

Acked-by: John McNamara <john.mcnamara@intel.com>
  
Thomas Monjalon April 6, 2017, 8:37 p.m. UTC | #2
> > The first line of the MAINTAINERS file are:
> > "
> > The intention of this file is to provide a set of names that we can rely
> > on for helping in patch reviews and questions.
> > "
> > 
> > Unfortunately, some maintainers do not endorse their role for questions
> > asked on the mailing list.
> > Hope making it clear in the contribution guide will enforce more
> > responsive maintainer participation.
> > 
> > Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com>
> 
> Acked-by: John McNamara <john.mcnamara@intel.com>

Applied, please share with maintainers.
  

Patch

diff --git a/doc/guides/contributing/patches.rst b/doc/guides/contributing/patches.rst
index fe71381..84a5dab 100644
--- a/doc/guides/contributing/patches.rst
+++ b/doc/guides/contributing/patches.rst
@@ -67,6 +67,7 @@  The role of the component maintainers is to:
 * Review patches for the component or delegate the review.
   The review should be done, ideally, within 1 week of submission to the mailing list.
 * Add an ``acked-by`` to patches, or patchsets, that are ready for committing to a tree.
+* Reply to questions asked about the component.
 
 Component maintainers can be added or removed by submitting a patch to the ``MAINTAINERS`` file.
 Maintainers should have demonstrated a reasonable level of contributions or reviews to the component area.