From: Vittorio Giovara <vittorio.giovara@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] Democratization work in progress draft v2
Date: Thu, 30 Jan 2025 07:38:21 +0100
Message-ID: <CABLWnS_gMO7CngcFnNpF+tsOarp9VJnedGw_0_Z_E7aVZ0nbDg@mail.gmail.com> (raw)
In-Reply-To: <DM8P223MB0365B166352FD9247EBEA900BAEE2@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM>
On Wed, Jan 29, 2025 at 10:49 PM Soft Works <
softworkz-at-hotmail.com@ffmpeg.org> wrote:
>
>
> > -----Original Message-----
> > From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Leo
> > Izen
> > Sent: Wednesday, January 29, 2025 10:39 PM
> > To: ffmpeg-devel@ffmpeg.org
> > Subject: Re: [FFmpeg-devel] Democratization work in progress draft v2
> >
> > On 1/29/25 3:33 PM, Michael Niedermayer wrote:
> > > 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
> > >
> >
> > I have been silent on this for a very long time, but I would like to
> > point out at this point that Michael has approximately five times as
> > many commits as the next-most prolific contributor (Andreas).
> >
> > (for those curious, navigate to git master and run: git shortlog -s -
> > n)
> >
> > If you draft language that gives you five times as much voting power
> > as
> > anybody else it does not realistically make it appear as though you
> > are
> > interested in handing over reigns to anybody.
>
> Am I the only one who has read that (probably so far most important)
> message where Michael has clearly said that such "handing over reigns" (he
> said "keys") is not going to happen as - would it burn down to that -
> people should rather fork?
>
> I think it's important to be clear about that, as it might save a lot of
> wasted energy.
>
We should be all running Windows XP, and never have switched away from
Monarchy after the French revolution, it might have saved a lot of wasted
energy.
--
Vittorio
_______________________________________________
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".
next prev parent reply other threads:[~2025-01-30 6:38 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-29 20:33 Michael Niedermayer
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 [this message]
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=CABLWnS_gMO7CngcFnNpF+tsOarp9VJnedGw_0_Z_E7aVZ0nbDg@mail.gmail.com \
--to=vittorio.giovara@gmail.com \
--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