Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Soft Works <softworkz-at-hotmail.com@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] Democratization work in progress draft v2
Date: Fri, 31 Jan 2025 16:01:13 +0000
Message-ID: <DM8P223MB036599378928F09319DE30C7BAE82@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <9dacff42-0536-4736-922b-0d791d63ef61@gmail.com>



> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of
> James Almer
> Sent: Friday, January 31, 2025 4:45 PM
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] Democratization work in progress draft v2
> 
> > Past involvement, including long-past involvement, is not only
> past, it
> > is both indication of knowledge about the project and prediction of
> > future involvement.
> >
> > For that reason, I believe that if this plan goes forward, it
> should
> > include all past involvement, but possibly with the condition that
> the
> > involvement continues presently.

How about a quadratic attenuation of past commit counts, so that older commits count less than more recent ones?

Here are some examples with different base values:

+------+-----+-----------------------------------+
| Year | Y-T |                Base               |
+------+-----+------+-------+------+------+------+
|      |     | 0.85 | 0.825 |  0.8 | 0.75 |  0.7 |
+------+-----+------+-------+------+------+------+
| 2023 |   0 | 100% |  100% | 100% | 100% | 100% |
+------+-----+------+-------+------+------+------+
| 2022 |  -1 |  85% |   83% |  80% |  75% |  70% |
+------+-----+------+-------+------+------+------+
| 2021 |  -2 |  72% |   68% |  64% |  56% |  49% |
+------+-----+------+-------+------+------+------+
| 2020 |  -3 |  61% |   56% |  51% |  42% |  34% |
+------+-----+------+-------+------+------+------+
| 2019 |  -4 |  52% |   46% |  41% |  32% |  24% |
+------+-----+------+-------+------+------+------+
| 2018 |  -5 |  44% |   38% |  33% |  24% |  17% |
+------+-----+------+-------+------+------+------+
| 2017 |  -6 |  38% |   32% |  26% |  18% |  12% |
+------+-----+------+-------+------+------+------+
| 2016 |  -7 |  32% |   26% |  21% |  13% |   8% |
+------+-----+------+-------+------+------+------+
| 2015 |  -8 |  27% |   21% |  17% |  10% |   6% |
+------+-----+------+-------+------+------+------+
| 2014 |  -9 |  23% |   18% |  13% |   8% |   4% |
+------+-----+------+-------+------+------+------+
| 2013 | -10 |  20% |   15% |  11% |   6% |   3% |
+------+-----+------+-------+------+------+------+
| 2012 | -11 |  17% |   12% |   9% |   4% |   2% |
+------+-----+------+-------+------+------+------+
| 2011 | -12 |  14% |   10% |   7% |   3% |   1% |
+------+-----+------+-------+------+------+------+
| 2010 | -13 |  12% |    8% |   5% |   2% |   1% |
+------+-----+------+-------+------+------+------+
| 2009 | -14 |  10% |    7% |   4% |   2% |   1% |
+------+-----+------+-------+------+------+------+
| 2008 | -15 |   9% |    6% |   4% |   1% |   0% |
+------+-----+------+-------+------+------+------+
| 2007 | -16 |   7% |    5% |   3% |   1% |   0% |
+------+-----+------+-------+------+------+------+
| 2006 | -17 |   6% |    4% |   2% |   1% |   0% |
+------+-----+------+-------+------+------+------+
| 2005 | -18 |   5% |    3% |   2% |   1% |   0% |
+------+-----+------+-------+------+------+------+
| 2004 | -19 |   5% |    3% |   1% |   0% |   0% |
+------+-----+------+-------+------+------+------+
| 2003 | -20 |   4% |    2% |   1% |   0% |   0% |
+------+-----+------+-------+------+------+------+

sw
_______________________________________________
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-31 16:01 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
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 [this message]
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=DM8P223MB036599378928F09319DE30C7BAE82@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM \
    --to=softworkz-at-hotmail.com@ffmpeg.org \
    --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