From patchwork Sat Dec 5 14:30:48 2020 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Jean-Baptiste Kempf X-Patchwork-Id: 24354 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 EF75444AC43 for ; Sat, 5 Dec 2020 16:59:28 +0200 (EET) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id D067068A774; Sat, 5 Dec 2020 16:59:28 +0200 (EET) X-Original-To: ffmpeg-devel@ffmpeg.org Delivered-To: ffmpeg-devel@ffmpeg.org Received: from mail-lf1-f42.google.com (mail-lf1-f42.google.com [209.85.167.42]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 9FEA268A4AE for ; Sat, 5 Dec 2020 16:59:22 +0200 (EET) Received: by mail-lf1-f42.google.com with SMTP id l11so11834833lfg.0 for ; Sat, 05 Dec 2020 06:59:22 -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=a77go2SgJZu2u5h5qX8t2QAn8nELSLSy4wIhgBNjHag=; b=vDAKHzbS9NnV/0MNJ7CbRsviib/0DRowtiPbR067C3vgjFewt/aSzDEoZM4XmFXt45 CzPm7OguK9eMiQ2L5ifDFWbevF4V11iKP0Iqdz/EPnXAVCHuYItocNfmj+fanlUIZ02L OA2WLr5nhSzD7xtaxbzv23h/hw9bd689f1esTU+08c59EMd5ffKJiuiTnz0Nk8NZ0Sjc UG3JrCrELS2aG5/s78OdLu80oT+D8jbKFmsKZdbXTS7Z/99ysqSWRHAaJqJu0IZkFfLz FWILmJNbVJ45P9Yovobd07qPeFemWNeUPR/MeHHXrp5/e1q7yESWeN7yOcRU5Q9GJV1a V+ZA== 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=a77go2SgJZu2u5h5qX8t2QAn8nELSLSy4wIhgBNjHag=; b=D6GmeyuFfjghBkJO04itIwvWAsx25QvdYak357qKm184seEu/omdur8V1Cu2KKTCRp +5o92i0X+LY6w3Rf8CzHoQdNLXTPugvgEb49s6QzmRMxkQu+EIaXDd7snwx7X0P1qE39 8uIzL886wk3P/w5LfUi0vUWKWZg7rgYcVfQ2NHNt6fP639gvOHa9Vv0EDXG2adbzg3wL esY2CQ3gACJkJkAQUBz7c/KYjb6WV7gJnfGNwYqnwo3UyTUdvTV1Sdi70bdbtwsgZjyd 3JyH7pAsSz3bRChQ8oXwhx8outLMKn5Lx+XQMkSCtBlr41eE9g+7VESYhSG8kR12CAtf q4OQ== X-Gm-Message-State: AOAM532WEHhN55DjvEfKBCcmYIoEYRlGUQT5rhnCpjoa5L5ZXytWDuYO JQa0i99TYb72LOzy/KKWqk6zT1OwsThxRyd6 X-Google-Smtp-Source: ABdhPJwlV7kho8HDgY+G7OrlTi+BLU8XEa/fvywfzIQd12ajZK3UccSuLBsTPyIoZ6MtGbzpxg/I3A== X-Received: by 2002:adf:e5cb:: with SMTP id a11mr10655430wrn.15.1607178653431; Sat, 05 Dec 2020 06:30:53 -0800 (PST) Received: from localhost.localdomain ([2a01:e35:2fde:e440:6edd:ad97:e98f:a232]) by smtp.gmail.com with ESMTPSA id f23sm6847205wmb.43.2020.12.05.06.30.52 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sat, 05 Dec 2020 06:30:52 -0800 (PST) From: Jean-Baptiste Kempf To: ffmpeg-devel@ffmpeg.org Date: Sat, 5 Dec 2020 15:30:48 +0100 Message-Id: <20201205143048.58784-1-jb@videolan.org> X-Mailer: git-send-email 2.29.2 MIME-Version: 1.0 Subject: [FFmpeg-devel] [PATCH] [RFC] 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 | 83 +++++++++++++++++++++++++ 1 file changed, 83 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..0df584bae4 --- /dev/null +++ b/doc/dev_community/resolution_process.md @@ -0,0 +1,83 @@ +# 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. + +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 give a ban of the mailing-list. + +After all the emails are in, the TC has 96 hours to give its final decision. + +### Within TC + +In the internal case, the TC has 96 hours to give its final decision. + + +## 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 reasons for the decisions from the TC can be kept internal by the TC, +if deemed necessary. + +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.