From patchwork Mon Jan 11 13:03:42 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: 24894 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 4EFCC449B4C for ; Mon, 11 Jan 2021 15:10:33 +0200 (EET) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 1C7A468AB17; Mon, 11 Jan 2021 15:10:33 +0200 (EET) X-Original-To: ffmpeg-devel@ffmpeg.org Delivered-To: ffmpeg-devel@ffmpeg.org Received: from mail-wr1-f49.google.com (mail-wr1-f49.google.com [209.85.221.49]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id BA45E6883B3 for ; Mon, 11 Jan 2021 15:10:26 +0200 (EET) Received: by mail-wr1-f49.google.com with SMTP id t30so16393069wrb.0 for ; Mon, 11 Jan 2021 05:10:26 -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=8sokLPj1qMZKSBTeNLPmP9WlYE1Hxl98WJXEY1DISMQ=; b=SSAw7uPw3BHu7GXqmI6wZtj95TnfBwRLXJBXZlL2oEbg3NDWxrE2nRhVBmmA+qiHB8 WHJzTM1wwCrB3ZRlwBCpDdL8zbi4uVcFZj9qStRfHuyYIvtdKumoFe+APG5elYvHvlAA 8ee9lw4qqQqg2oRQtZtIj5iRGWWff58nyJlxR3L3IDZomeY3NO3fTp/GN9D9cad+rGqG GjCYPop5amzbr0ofSgk3NpLHuvqc+fYl6oMew17rVnjxZNmwcw+kucx3qQWa/GD5cQn1 cFvBVSak5FYAu7UJzf5QzStnn+5NS8QoWF9CAinzMO9YSJvxlc0i8dKYMgGGpKh3cVRo CibQ== 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=8sokLPj1qMZKSBTeNLPmP9WlYE1Hxl98WJXEY1DISMQ=; b=nqFiUsn3LGm99tIaT18iKicydQhvatnasoANkm7QEp5dgmWsl5n8YTWkBMnywxcM5a kF9yXJOrNxGM9VzSsd3/YAyWlkv3+bLBjRRQpuOl11JcBhubNsbx5unx/4neqmybC9SK EQLwAyQrvrtZtPmVvvb+qL2jIC4jEPOgjaBA4vp+3VVBg7d2clyoC7WHtykCbW3XKj0A YT+JdE5LoQB8kdQDKiREwBf0BOoFzIRqK3w4W/SCqWzpUezlwRAsfbgGICiXfYV+a6zD PpUift3XvnO34vcjVTI+5R7t8ASKAB5LWFdZTfxbVCw8tuKuW2MLdR/bDFh43hLhWP1o fgPw== X-Gm-Message-State: AOAM533VxvbNxDzOyunKrFcfeMCER2abb7WEkEV7n99zRNM1e1z2NIbB U1UScDSYueCR0vaoTivLUjiu6qNrSQY4+uOE X-Google-Smtp-Source: ABdhPJz/UyvArBLTVbmLjUhhEwWg9PAA5N7i+hN57H96BGmeb/XfC4zF4CIx8+7E5FdHQx85iJ0lZg== X-Received: by 2002:a5d:67c3:: with SMTP id n3mr16080043wrw.297.1610370225804; Mon, 11 Jan 2021 05:03:45 -0800 (PST) Received: from localhost.localdomain ([2a01:e0a:14f:f4d0:b6f6:3586:2cb8:f384]) by smtp.gmail.com with ESMTPSA id n8sm23963377wrs.34.2021.01.11.05.03.44 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 11 Jan 2021 05:03:44 -0800 (PST) From: Jean-Baptiste Kempf To: ffmpeg-devel@ffmpeg.org Date: Mon, 11 Jan 2021 14:03:42 +0100 Message-Id: <20210111130342.17759-1-jb@videolan.org> X-Mailer: git-send-email 2.30.0 MIME-Version: 1.0 Subject: [FFmpeg-devel] [PATCH] [RFC][v2] 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 | 89 +++++++++++++++++++++++++ 1 file changed, 89 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..91999202cb --- /dev/null +++ b/doc/dev_community/resolution_process.md @@ -0,0 +1,89 @@ +# 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 +* 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, no mail on the thread is accepted. + +Violations of this rule will 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. + +### 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, the GA or the TC auto-seizing. +