Ping.

Anton announced to have a vote on 4th Mar for changing the rule [1]. That's long past.
It is holding up the consideration of the matter I raised [2] to the TC.

Regards,
Gyan

[1]: https://ffmpeg.org/pipermail/ffmpeg-devel/2024-March/322464.html
[2]: https://ffmpeg.org/pipermail/ffmpeg-devel/2024-February/321564.html

On 2024-03-03 12:52 pm, Gyan Doshi wrote:
---
  doc/community.texi | 15 ++++++++++++++-
  1 file changed, 14 insertions(+), 1 deletion(-)

diff --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.

_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".

Reply via email to