From: Vittorio Giovara <vittorio.giovara@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [RFC] Vote STF/SPI 2024-02
Date: Tue, 6 Feb 2024 16:14:55 +0100
Message-ID: <CABLWnS9wvNPH1uk1aB64x+m3=ac6PNKa=GFuhH1zpZrV5mkPRQ@mail.gmail.com> (raw)
In-Reply-To: <2785693.8HhBItc6dF@basile.remlab.net>
On Thu, Feb 1, 2024 at 9:11 PM Rémi Denis-Courmont <remi@remlab.net> wrote:
> Le torstaina 1. helmikuuta 2024, 19.45.52 EET Vittorio Giovara a écrit :
> > The same of course should apply to any other future funding, it must be
> > either the community (via GA) or a third party setting up the
> sponsorship.
>
> Neither the community or the GA can forbid people from seeking funding for
> themselves. I suppose that, in theory, developers could be required to
> sign an
> agreement to that effect before they are allowed to submit code for
> inclusion,
> but that seems neither practical, nor desirable to me.
>
> That is probably not what you meant, but that is what this reads like.
>
Yeah that's not what I meant, sorry for the confusion: what I meant was
whoever secures the funding, then cannot be directly funded for any of the
projects attributed in the current funding.
This might be counterintuitive and possibly controversial, but the goal
here is to distinguish benefiting the community and benefiting oneself as
well as avoid losing a possible funding: I would really like to avoid that
we miss out on funding out of fear that whoever found the funding will
strongarm the community into accepting something that the community may
reject.
In other words, this is both protection for the community and for whoever
finds the funding.
I don't know how enforce-able it is, or if it is something that can
actually facilitate accepting future funding for the community, but since
we're in a time crunch and we're voting with unanswered open questions, it
is something we should at least consider.
--
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:[~2024-02-06 15:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-01 4:29 Michael Niedermayer
2024-02-01 17:45 ` Vittorio Giovara
[not found] ` <686A824A-CF8F-4D38-ADFA-C84362DE866F@cosmin.at>
2024-02-01 17:49 ` Cosmin Stejerean via ffmpeg-devel
2024-02-01 19:13 ` Michael Niedermayer
2024-02-01 19:42 ` Jonatas L. Nogueira via ffmpeg-devel
2024-02-01 21:04 ` Michael Niedermayer
2024-02-01 20:10 ` Rémi Denis-Courmont
2024-02-06 15:14 ` Vittorio Giovara [this message]
2024-02-03 3:37 ` Michael Niedermayer
2024-02-03 12:13 ` Stefano Sabatini
2024-02-04 0:42 ` Michael Niedermayer
2024-02-04 10:11 ` Paul B Mahol
2024-02-11 12:38 ` 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='CABLWnS9wvNPH1uk1aB64x+m3=ac6PNKa=GFuhH1zpZrV5mkPRQ@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