From: Gyan Doshi <ffmpeg@gyani.pro>
To: ffmpeg-devel@ffmpeg.org
Subject: [FFmpeg-devel] [PATCH] doc/community: rule to avoid conflict of interest and prejudice in TC
Date: Sun, 3 Mar 2024 12:52:25 +0530
Message-ID: <20240303072225.4095-1-ffmpeg@gyani.pro> (raw)
---
| 15 ++++++++++++++-
1 file changed, 14 insertions(+), 1 deletion(-)
--git a/doc/community.texi b/doc/community.texi
index 90d2b6f366..8d5722bd7f 100644
--- a/doc/community.texi
+++ b/doc/community.texi
@@ -82,7 +82,20 @@ 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.
+Any member of the TC who has
+
+@itemize @bullet
+@item
+had a major participation in the discussion or demonstrated a partisan disposition on a disputed matter at any public venue, or
+@item
+a material interest in the resolution of the dispute, either directly or via current or anticipated employment or consideration
+@end itemize
+
+should be recused from participation in the TC activities related to the concerned matter.
+This recusal may be effected either directly by the TC member, or failing which, by a vote of the
+Community Committee (CC) - the TC member must not participate in any such vote. Failure by the TC member
+to reveal any such involvement as described above, if judged intentional and material by the CC, shall
+result in exclusion of said member from all FFmpeg governance bodies for a period of no less than two years.
The decision to use a RFC process or an internal discussion is a discretionary decision of the TC.
--
2.44.0
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next reply other threads:[~2024-03-03 7:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-03 7:22 Gyan Doshi [this message]
2024-03-22 4:24 ` Gyan Doshi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240303072225.4095-1-ffmpeg@gyani.pro \
--to=ffmpeg@gyani.pro \
--cc=ffmpeg-devel@ffmpeg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git