From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-f42.google.com (mail-wm0-f42.google.com [74.125.82.42]) by dpdk.org (Postfix) with ESMTP id 7CB6F1075 for ; Tue, 14 Mar 2017 11:00:21 +0100 (CET) Received: by mail-wm0-f42.google.com with SMTP id t189so59444946wmt.1 for ; Tue, 14 Mar 2017 03:00:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=6wind-com.20150623.gappssmtp.com; s=20150623; h=from:to:subject:date:message-id; bh=0ub4OzCIxPcsFqbphTufZugKNSJbE907bpbZL5m8+O0=; b=NYzCPVnlupaKd4PS2EBLmV5nJxdF4JGdrMWSJ4nEM7VNOWMNc7aOHYFDuWzGWr7VeW tKh/HyzwN1dSfd9nC3hWKc7aiCDEE0OelqyscBOvoMXV+zcOddH0SV72gJyDdsC8QgTo M9QorR1c5kWOQsxsomXYfhubYWd3UUJRbjSe1IF/46DncX16Qt9IFqsLv3aQnBewHXLQ RDV9zC9hMdLks7nvykWl75C9X0CwFCtS/0VaYn3EOOHZlrhibVg5O3dtgmsuLSXlubvO mMWBxEnSYCzlJNevE7iopAQCylvujeXiwA+7+oe2pJ4z5FvrxJ4jT+x/khtCyOOwI1mc gyBg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:date:message-id; bh=0ub4OzCIxPcsFqbphTufZugKNSJbE907bpbZL5m8+O0=; b=BXnuo9kAzW7nV538Pxd5ODsahkE5VCMtRSgtgvLimp+61EOYZJhzMWsA+UX0hblccX KyV+y5JaQhSvM8zmFOioN1FG+FIfO2XDzVPJi4+dKXKxbJrYyhdXk72pCajJd6yuZzf2 Vr8yyVI+YTsKeYAsc/47AObDL4Cr+jQatq7jrjh1OgfcYf/UjVO6VVlzmlzw6hHoYEXr tjfdHH4EQSLsqPR7TLMC6yXlVcDvSwP81e0N2otINGBRenIwsqA2RvOiZMVeXPcBZ83C vnFyXoiWcyRu860lxtvaXzGlj3qe0RavNSgwSoFtqIhaVgOiDvORgN5cDqlSCZViG2iU h0qw== X-Gm-Message-State: AFeK/H2HoqjZut3ppH6R/xx12N1NogosewkdfkE2gfZwt8zJDBoBuF9QpNkCakW93mhkSNXO X-Received: by 10.28.10.70 with SMTP id 67mr14802838wmk.76.1489485620788; Tue, 14 Mar 2017 03:00:20 -0700 (PDT) Received: from XPS13.localdomain (184.203.134.77.rev.sfr.net. [77.134.203.184]) by smtp.gmail.com with ESMTPSA id b17sm14819649wma.33.2017.03.14.03.00.20 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 14 Mar 2017 03:00:20 -0700 (PDT) From: Thomas Monjalon To: dev@dpdk.org Date: Tue, 14 Mar 2017 11:00:16 +0100 Message-Id: <1489485616-30291-1-git-send-email-thomas.monjalon@6wind.com> X-Mailer: git-send-email 2.7.0 Subject: [dpdk-dev] [PATCH] doc: add maintainer role about replying questions X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Mar 2017 10:00:21 -0000 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 --- doc/guides/contributing/patches.rst | 1 + 1 file changed, 1 insertion(+) 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. -- 2.7.0