Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: [FFmpeg-devel] Democratization work in progress draft v2
Date: Wed, 29 Jan 2025 21:33:21 +0100
Message-ID: <20250129203321.GB4991@pb2> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 4185 bytes --]

Hi all

Heres my current "work in progress": (sending that before fosdem, so people can discuss if they like)

Goals:
    The proposed changes aim to improve the General Assembly's structure to ensure inclusivity, fairness, and resilience against attacks. The key goals are as follows:
    Increase the Size of the General Assembly
        Inclusivity: Allow every contributor to have a vote, ensuring all voices are heard, regardless of their role or level of involvement.
        Enhanced Security: By increasing the number of voters, it becomes significantly harder for a malicious actor or group to influence decisions. A larger voting pool dilutes the impact of any single attack or coordinated effort.
    Make Voting Power Proportional to Contributions
        Fair Representation: Allocate voting power based on contributions, ensuring that those who dedicate substantial time and effort to the project have a stronger voice than those with minimal involvement. This creates a system where contribution equals influence.
        Resilience Against Attacks: Attackers would need not only a large number of people but also a comparable volume of meaningful contributions to influence the vote, further safeguarding the project.
        Motivating Participation: Encouraging higher levels of engagement by rewarding contributors with more influence in decision-making.
    Broaden the Definition of Contributions
        Previously everyone was a software developer. But really there are many people in the community, who are not software developers.


Shares in Alternative P
    1 release                               == 100 shares
    1 entry in MAINTAINERS                  == 100 shares
    1 commit in           git master branch ==  10 shares
    1 subscription in ffmpeg-devel          ==  10 shares
    1 subscription in ffmpeg-user           ==  10 shares
    1 fixed ticket in trac                  ==  10 shares
    1 reported issue in trac                ==   2 shares
    1 mail in ffmpeg-devel                  ==   2 shares
    1 mail in ffmpeg-user                   ==   2 shares
    1 (backported) commit in release branch ==   1 shares

    If the condorcet vote software fails due to the number of shares then
    all shares shall be divided by 2 before all rounding and non integer shares shall be rounded to nearest even
    this shall be repeated until the vote software no longer fails due to the number.

Shares in Alternative F
    Everyone who either has authored a commit in git master or sent a mail to ffmpeg-devel or user
    or fixed or reported an issue in trac has exactly the same vote power. This is a true classical democracy.
    It includes the nearly same people as the previous suggestion but without the
    proportionality. It is vulnerable to a group of a few thousand actual people joining and coordinating
    an attack. The proportionality raises the bar for such an attack by ~2 orders of magnitude.

    We need a list to remap multiple addresses to the same person (this is not needed for the proportional case)

Any single company collective vote power is limited to 10%, associated companies count as the same company here.

If anyone can show that specific activities are automated then the test used for detecting them
shall by confirmed by GA vote and then be added to a list of anti-bot tests. This vote shall be
performed by a GA that is on the closest first january prior to the event adding the disputed shares.

the list of mails on ffmpeg-devel and ffmpeg-user should be filtered by the current subscribers based on the
idea that someone who left by choice does not want to receive vote mails. If they want to vote they can
re-subcribe

In all cases, whenever possible decisions should be made by consensus on ffmpeg-devel.
Voting should only be used when consensus was tried at least twice and failed

A factor related to last activity will be in a seperate vote
A veto power may be in seperate vote

-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Some Animals are More Equal Than Others. - George Orwell's book Animal Farm

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 251 bytes --]

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

             reply	other threads:[~2025-01-29 20:33 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-29 20:33 Michael Niedermayer [this message]
2025-01-29 21:39 ` Leo Izen
2025-01-29 21:47   ` Nicolas George
2025-01-29 21:48   ` Soft Works
2025-01-30  6:38     ` Vittorio Giovara
2025-01-29 23:43 ` Niklas Haas
2025-01-30 18:04   ` Michael Niedermayer
2025-01-31 14:36     ` Nicolas George
2025-01-31 14:58   ` Nicolas George
2025-01-31 15:44     ` James Almer
2025-01-31 16:01       ` Soft Works
2025-02-02  2:25         ` Leo Izen
2025-02-02  3:37           ` Soft Works
2025-02-02  7:29           ` Vittorio Giovara
2025-02-01  0:49       ` Michael Niedermayer
2025-02-01  6:45         ` Zhao Zhili
2025-02-01 13:21           ` Ronald S. Bultje
2025-02-01 14:30             ` Vittorio Giovara
2025-02-01 14:11           ` Jean-Baptiste Kempf
2025-02-01 14:31             ` Vittorio Giovara
2025-02-02 11:34           ` Michael Niedermayer
2025-02-01 13:30         ` James Almer
2025-02-01 21:53           ` Michael Niedermayer
2025-02-02 18:14             ` James Almer
2025-02-03 18:08               ` Michael Niedermayer
2025-02-03 18:16                 ` Vittorio Giovara
2025-02-03 19:14               ` Michael Niedermayer
2025-02-03 20:45                 ` Nicolas George
2025-02-03  2:29             ` Ronald S. Bultje
2025-02-01 22:27           ` Michael Niedermayer
2025-02-01 22:29             ` Kieran Kunhya via ffmpeg-devel
2025-02-02 21:35             ` James Almer
2025-01-30  6:41 ` Vittorio Giovara
2025-02-01 20:44 ` Nicolas George
2025-02-02  0:01   ` Michael Niedermayer

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=20250129203321.GB4991@pb2 \
    --to=michael@niedermayer.cc \
    --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