From patchwork Mon Feb 8 14:23:04 2021 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Jean-Baptiste Kempf X-Patchwork-Id: 25513 Return-Path: X-Original-To: patchwork@ffaux-bg.ffmpeg.org Delivered-To: patchwork@ffaux-bg.ffmpeg.org Received: from ffbox0-bg.mplayerhq.hu (ffbox0-bg.ffmpeg.org [79.124.17.100]) by ffaux.localdomain (Postfix) with ESMTP id DBD48447BA0 for ; Mon, 8 Feb 2021 16:23:15 +0200 (EET) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id A5537688321; Mon, 8 Feb 2021 16:23:15 +0200 (EET) X-Original-To: ffmpeg-devel@ffmpeg.org Delivered-To: ffmpeg-devel@ffmpeg.org Received: from mail-wr1-f51.google.com (mail-wr1-f51.google.com [209.85.221.51]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 7B67E688198 for ; Mon, 8 Feb 2021 16:23:09 +0200 (EET) Received: by mail-wr1-f51.google.com with SMTP id z6so17282717wrq.10 for ; Mon, 08 Feb 2021 06:23:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=tlPbWBAC1wkhKpJN+1rTei2WenTlDcF6GNWxosvHU1c=; b=LY9O2NXpBSSeir25/e/R6mOs+yfDD1fgRCDtMcQKEPoh/BPHEuYrji1dGPzmeSNjN1 8s9F9JXzkNypNz6OFjx2GxggHbEeSVSuN7O7gHx99JBUtojgaJpnNpkRcF+dn7gTafq5 xSgwfhjopfZb4WdlNTZbJoJMNn6IzZVl7jANJX9mjw2f9CPLeGzyMyn3jPYngdyTueJw L8bYrI1+G5a23WkIr4ch+YzvVE8oJD/UmHtBLoju+3eYM7CajtgtTvujemkVRCPzms+I E9h4WN7kn1eX4d/dBjKGxZe49sGpbavFvp4IDwZJ3n1w04MBhivMWGu/SfOGnvwQx71l tcdA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:from:to:cc:subject:date:message-id :mime-version:content-transfer-encoding; bh=tlPbWBAC1wkhKpJN+1rTei2WenTlDcF6GNWxosvHU1c=; b=CIqYD0swKX4+7c3wn5d39HGBmM4wug3ADhoYGxuVC7+9GQ3T7S1yH6Brd4Yx6LcoZy 9fquddow5irtHJcaZo8rQWdFjIiVAH/QkPtX85s6Xb7SWX5eJgR8ifUW8rxwRF17nMVn +fQgpqE1Z/FzfQgfShJwAeKFfQ4X63Koeu8ygJ8UWwpr08rp1QWTg79Qvs8dFdSNESVL jWkZYEjRSjGL3je8nysT7nfitJtS/qVpsB7QcytWt8pnVKbRsBwn8LeqIhXCsx/NQEED 91VjvX3LVMdPQJ1uxD2cJlw6HL8Udd5EOguZ5KK8YEB7++N0VqdjOcUISFZwsZHAYMpt DwIA== X-Gm-Message-State: AOAM531YYElzJOV+xe2w/+R6cnwD3jxheNvGhdyv2r1U8AW2l+z6biZF JA7hE2lGTzGa/mdmlZli0y80y+DFTV0+eQ== X-Google-Smtp-Source: ABdhPJxlkag8wAznXOeMnOGpS69cn8nU2KdigVunZvEhl9kMTI0PfxYcUNKDis1xhTb1dd78n2qTlQ== X-Received: by 2002:adf:f90d:: with SMTP id b13mr21174893wrr.198.1612794188635; Mon, 08 Feb 2021 06:23:08 -0800 (PST) Received: from localhost.localdomain ([2a01:e0a:14f:f4d8::10]) by smtp.gmail.com with ESMTPSA id z15sm27538602wrt.8.2021.02.08.06.23.07 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 08 Feb 2021 06:23:07 -0800 (PST) From: Jean-Baptiste Kempf To: ffmpeg-devel@ffmpeg.org Date: Mon, 8 Feb 2021 15:23:04 +0100 Message-Id: <20210208142304.78634-1-jb@videolan.org> X-Mailer: git-send-email 2.30.0 MIME-Version: 1.0 Subject: [FFmpeg-devel] [PATCH] [RFC][v3] Tech Resolution Process X-BeenThere: ffmpeg-devel@ffmpeg.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: FFmpeg development discussions and patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: FFmpeg development discussions and patches Cc: Jean-Baptiste Kempf Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" --- doc/dev_community/resolution_process.md | 91 +++++++++++++++++++++++++ 1 file changed, 91 insertions(+) create mode 100644 doc/dev_community/resolution_process.md diff --git a/doc/dev_community/resolution_process.md b/doc/dev_community/resolution_process.md new file mode 100644 index 0000000000..6da3e8ffb2 --- /dev/null +++ b/doc/dev_community/resolution_process.md @@ -0,0 +1,91 @@ +# Technical Committee + +_This document only makes sense with the rules from [the community document](community)_. + +The Technical Committee (**TC**) is here to arbitrate and make decisions when +technical conflicts occur in the project. + +The TC main role is to resolve technical conflicts. +It is therefore not a technical steering committee, but it is understood that +some decisions might impact the future of the project. + +# Process + +## Seizing + +The TC can take possession of any technical matter that it sees fit. + +To involve the TC in a matter, email tc@ or CC them on an ongoing discussion. + +As members of TC are developers, they also can email tc@ to raise an issue. + +## Announcement + +The TC, once seized, must announce itself on the main mailing list, with a _[TC]_ tag. + +The TC has 2 modes of operation: a RFC one and an internal one. + +If the TC thinks it needs the input from the larger community, the TC can call +for a RFC. Else, it can decide by itself. + +If the disagreement involves a member of the TC, that member should recuse +themselves from the decision. + +The decision to use a RFC process or an internal discussion is a discretionary +decision of the TC. + +The TC can also reject a seizure for a few reasons such as: +the matter was not discussed enough previously; it lacks expertise to reach a +beneficial decision on the matter; or the matter is too trivial. + +### RFC call + +In the RFC mode, one person from the TC posts on the mailing list the +technical question and will request input from the community. + +The mail will have the following specification: +* a precise title +* a specific tag [TC RFC] +* a top-level email +* contain a precise question that does not exceed 100 words and that is answerable by developers +* may have an extra description, or a link to a previous discussion, if deemed necessary, +* contain a precise end date for the answers. + +The answers from the community must be on the main mailing list and must have +the following specification: +* keep the tag and the title unchanged +* limited to 400 words +* a first-level, answering directly to the main email +* answering to the question. + +Further replies to answers are permitted, as long as they conform to the +community standards of politeness, they are limited to 100 words, and are not +nested more than once. (max-depth=2) + +After the end-date, mails on the thread will be ignored. + +Violations of those rules will be escalated through the Community Committee. + +After all the emails are in, the TC has 96 hours to give its final decision. +Exceptionally, the TC can request an extra delay, that will be notified on the +mailing list. + +### Within TC + +In the internal case, the TC has 96 hours to give its final decision. +Exceptionally, the TC can request an extra delay. + + +## Decisions + +The decisions from the TC will be sent on the mailing list, with the _[TC]_ tag. + +Internally, the TC should take decisions with a majority, or using +ranked-choice voting. + +The decision from the TC should be published with a summary of the reasons that +lead to this decision. + +The decisions from the TC are final, until the matters are reopened after +no less than one year, by either the GA or the TC auto-seizing. +