[FFmpeg-devel] [WIP] Organisation process

[Anton Khirnov]

Quoting Jean-Baptiste Kempf (2020-10-02 00:41:34)
> Hello folks,
>
> I've documented what has been decided/discussed about the voting process and the committees.
>
> I'd like to know where should I commit this .md. In doc/? In a subfolder? somewhere else?

doc/ is getting pretty crowded, so a subfolder seems preferable to me
something like doc/dev_process, could also hold some other stuff already
in there.

>
> I'd also like to have remarks about things that don't really match reality or are just wrong.
>
> (yes, the conduct document and the tech resolution documents are not here, but they will be shared here soon.
> and they might be trickier, yes)
>
> Best,
>
> ----
>
> # FFmpeg project
>
> ## Organisation
>
> The FFmpeg project is organized through a community working on global consensus.
>
> Decisions are taken by the ensemble of active members, through voting and are aided by two committees.
>
> ## General Assembly
>
> The ensemble of active members is called the General Assembly (GA).
>
> The General Assembly is sovereign and legitimate for all its decisions regarding the FFmpeg project.
>
> The General Assembly is made up of active contributors and the people who are added to this General Assembly through a vote.
>
> Contributors are considered "active contributors" if they have pushed more than 20 patches in the last 36 months in the main FFmpeg repository.

My understanding was that the extra people are also active contributors,
except their active contribution is in form other than patches.

So I'd suggest rephrasing this along the lines of:
- GA are active contributors
- active contributors are people with X patchs in Y months + extra
  people who are voted on

>
> Additional members are added to the General Assembly through a vote after being proposed by a member of the General Assembly.
>
> ## Voting
>
> Voting is done using a ranked voting system, currently running on https://vote.ffmpeg.org/ .
>
> Majority vote means more than 50% of the expressed ballots.
>
> ## Technical Committee
>
> The Technical Committee (TC) is here to arbitrage and take decisions when technical conflicts occur in the project. They will consider the merits of all the positions, judge them and take a decision.
>
> The TC is resolving technical conflicts but is not a technical steering committee.
>
> Decisions by the TC are binding for all the contributors.
>
> Decisions taken by the TC can be re-opened after 1 year or by a majority vote of the General Assembly, requested by one of the member of the GA.
>
> The TC is elected by the General Assembly for a duration of 1 year, and is composed of 5 members.
> Members can be reelected if they wish. A majority vote in the General Assembly can trigger a new election of the TC.
>
> The conflict resolution process is detailed in the [resolution process] document.

Maybe mention that members can be from outside the GA and are
self-nominated.

>
> ## Community committee
>
> The Community Committee (CC) is here to arbitrage and take decisions when inter-personal conflicts occur in the project. It will decide quickly and take actions, for the sake of the project.
>
> The CC can remove privileges of offending members, including removal of commit access and temporary ban from the community.
>
> Decisions taken by the CC can be re-opened after 1 year or by a majority vote of the General Assembly. Indefinite bans from the community must be confirmed by the General Assembly, in a majority vote.
>
> The CC is elected by the General Assembly for a duration of 1 year, and is composed of 5 members.
> Members can be reelected if they wish. A majority vote in the General Assembly can trigger a new election of the CC.
>
> The CC is governed by and responsible for the Code of Conduct.

"reponsible for enforcing"?

> --
> Jean-Baptiste Kempf -  President

Overall sounds good, this is great progress.

-- 
Anton Khirnov