[FFmpeg-devel] [PATCH] [RFC][v2] Tech Resolution Process

[Anton Khirnov]

Quoting Jean-Baptiste Kempf (2021-01-11 14:03:42)
> ---
>  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.

This wasn't in the previous version IIRC, and does not seem reasonable
to me.
For one thing, it adds a possibility of a tie, which was impossible with
odd number of TC members.
For another, they are excluded from having a say precisely in those
matters where they have most expertise.

-- 
Anton Khirnov