Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
* [FFmpeg-devel] [PATCH] doc/community: rule to avoid conflict of interest and prejudice in TC
@ 2024-03-03  7:22 Gyan Doshi
  2024-03-22  4:24 ` Gyan Doshi
  0 siblings, 1 reply; 2+ messages in thread
From: Gyan Doshi @ 2024-03-03  7:22 UTC (permalink / raw)
  To: ffmpeg-devel

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [FFmpeg-devel] [PATCH] doc/community: rule to avoid conflict of interest and prejudice in TC
  2024-03-03  7:22 [FFmpeg-devel] [PATCH] doc/community: rule to avoid conflict of interest and prejudice in TC Gyan Doshi
@ 2024-03-22  4:24 ` Gyan Doshi
  0 siblings, 0 replies; 2+ messages in thread
From: Gyan Doshi @ 2024-03-22  4:24 UTC (permalink / raw)
  To: ffmpeg-devel

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-request@ffmpeg.org with subject "unsubscribe".

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2024-03-22  4:24 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-03-03  7:22 [FFmpeg-devel] [PATCH] doc/community: rule to avoid conflict of interest and prejudice in TC Gyan Doshi
2024-03-22  4:24 ` Gyan Doshi

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