From: "Jonatas L. Nogueira via ffmpeg-devel" <ffmpeg-devel@ffmpeg.org>
To: Kieran Kunhya <kierank@obe.tv>
Cc: "Jonatas L. Nogueira" <jesusalva@spi-inc.org>,
Michael Niedermayer <michael@niedermayer.cc>,
FFmpeg development discussions and patches
<ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] Sovereign Tech Fund
Date: Mon, 29 Jan 2024 18:46:27 +0000
Message-ID: <CALE=2=_oFqmFJWe53iHENBPe8UP_8gKkwLiHYSGXVwv1r0z2iQ@mail.gmail.com> (raw)
In-Reply-To: <CAK+ULv5Dyg2KbMwgm5a=R6MAoWoCzuNN5k9XT-T2OKuNvkH2Og@mail.gmail.com>
Please keep in mind we're a public charity using public money from
taxpayers, which means we need a criteria for payments and that said
payments must be issued objectively. The GA might be able to distribute
money with subjective criterias... But not this specific money which is
being discussed. I mean, anyone would get mad if their elected officials
did that with tax money, so obviously the same will extend here. (Remember
the time when an infamous mayor used public money to fix only the roads
surrounding his home? Yeah, let's not do this, alright?)
If commits are a no-go because FFmpeg has internal governance issues on how
those happen, we can think of something else, as long as it retains the
objectiveness expected from the use of public money. But we're putting the
cart ahead of the horse. Please don't get bogged down by the details, move
forward with the scope of work — that's the written version of how STF
funds can serve both STF as FFmpeg's purposes. A journey of a thousand
miles begins with a single step, if you focus on the future steps you'll
trip, fall, and lose the opportunity for the sponsorship.
There are only a couple weeks longer to finish the Scope of Work, and that
blocks pretty much everything. STF said itself that the other details can
be discussed later.
Michael: It's not very dissimilar, no. X.Org recently made something
similar to Outreachy, the Endless Vacations of Code program (EVoC), if you
prefer to make it more similar to that it might be possible.
A few things to keep in mind in such a case: The stipend is fixed and
agreed beforehand, there are less reports and payments to make, you can
only hire in an educational capability (so not the staff you're looking
for), it is less suitable for continuous tasks (which was the original
issue), and you still need the Scope of Work before it begins.
I believe you can actually do both via contracts as via education programs
if you wanted, but the latter might be of limited use to you.
Att.,
--
Jonatas L. Nogueira (“jesusalva”)
Board of Directors Member
Software in the Public Interest, Inc.
On Mon, Jan 29, 2024 at 3:32 PM Kieran Kunhya <kierank@obe.tv> wrote:
>
>
> On Sun, 28 Jan 2024 at 21:47, Michael Niedermayer <michael@niedermayer.cc>
> wrote:
>
>> Hi Kieran
>>
>> On Sun, Jan 28, 2024 at 08:42:00PM +0000, Kieran Kunhya wrote:
>> > On Sun, 28 Jan 2024, 20:37 Kieran Kunhya, <kierank@obe.tv> wrote:
>> >
>> > > Both work fine really. For example iam not employed by FFlabs and the
>> work
>> > >> i did for them is just by sending invoices, while what i do qualifies
>> > >> maintenance probably close to 100%.
>> > >>
>> > >
>> > > Fflabs is a private company that can choose however it likes how to
>> > > distribute its funds. STF/SPI/FFmpeg are not the same.
>> > >
>> > > Would you like every invoice you make to be on this mailing list and
>> > > discussed in depth in public? And if that invoice was voted against
>> by the
>> > > GA what would you do?
>> > >
>> > > Kieran
>> > >
>> >
>> > Remember the outcry about SDR that literally drove people away from the
>> > project? Well imagine that for one of your invoices.
>>
>> Do you mean it would drive them away because of how much or how little i
>> work for ?
>> Or becuase of what i work for ?
>>
>
> You refused to acknowledge the public outcry over SDR for months and
> pushed patches the community clearly objected to (see andreas thread).
>
> That could clearly apply to invoiced work that the community disagreed
> with. What would you do then? You weren't willing to compromise last time
> for your hobby, what makes you willing to compromise in that situation?
>
> I mean it basically happened already with SDR, just without an invoice.
>
> "I think you should try to bring the work you want funded into the
> framework
> that they told us to use. Instead of complaining"
>
> And now you follow the same tactics with Derek. Accusing people of
> disagree with you of spreading resentment.
>
> Kieran
>
> Sent from my mobile device
>
_______________________________________________
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-01-29 18:47 UTC|newest]
Thread overview: 123+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-28 3:25 Michael Niedermayer
2024-01-28 15:54 ` Kieran Kunhya
2024-01-28 17:12 ` Michael Niedermayer
2024-01-28 18:59 ` Kieran Kunhya
2024-01-28 19:20 ` Jonatas L. Nogueira via ffmpeg-devel
2024-01-28 19:30 ` Jonatas L. Nogueira via ffmpeg-devel
2024-01-28 19:34 ` Kieran Kunhya
2024-01-28 21:18 ` Jonatas L. Nogueira via ffmpeg-devel
2024-01-28 21:33 ` Kieran Kunhya
2024-01-29 21:27 ` Anton Khirnov
2024-01-28 20:06 ` Michael Niedermayer
2024-01-28 20:32 ` Kieran Kunhya
2024-01-28 20:34 ` Kieran Kunhya
2024-01-28 20:37 ` Kieran Kunhya
2024-01-28 20:42 ` Kieran Kunhya
2024-01-28 21:47 ` Michael Niedermayer
2024-01-29 18:31 ` Kieran Kunhya
2024-01-29 18:46 ` Jonatas L. Nogueira via ffmpeg-devel [this message]
2024-01-29 18:54 ` Michael Niedermayer
2024-01-29 19:02 ` Kieran Kunhya
2024-01-29 20:04 ` Michael Niedermayer
2024-01-29 22:54 ` Kieran Kunhya
2024-01-30 9:20 ` Tomas Härdin
2024-01-28 21:34 ` Michael Niedermayer
2024-01-28 21:39 ` Kieran Kunhya
2024-01-29 2:26 ` Jonatas L. Nogueira via ffmpeg-devel
2024-01-29 14:52 ` Derek Buitenhuis
2024-01-29 15:02 ` Kieran Kunhya
2024-01-29 15:05 ` Derek Buitenhuis
2024-01-29 16:40 ` Jonatas L. Nogueira via ffmpeg-devel
2024-01-29 17:05 ` Kieran Kunhya
2024-01-29 17:27 ` Michael Niedermayer
2024-01-29 17:36 ` Kieran Kunhya
2024-01-29 17:43 ` Rémi Denis-Courmont
2024-01-29 18:11 ` Michael Niedermayer
2024-01-29 21:01 ` Rémi Denis-Courmont
2024-01-29 22:43 ` Michael Niedermayer
2024-01-30 6:30 ` Rémi Denis-Courmont
2024-01-30 17:15 ` Michael Niedermayer
2024-01-30 18:00 ` Michael Niedermayer
[not found] ` <A40E9FF7-EC74-458A-A195-26EE8062992E@cosmin.at>
2024-01-29 22:23 ` Cosmin Stejerean via ffmpeg-devel
2024-01-29 22:31 ` Kieran Kunhya
2024-01-30 10:12 ` Nicolas George
2024-01-30 10:19 ` Kieran Kunhya
2024-01-30 10:31 ` Nicolas George
2024-01-30 10:44 ` Kieran Kunhya
2024-01-30 10:46 ` Nicolas George
2024-01-30 10:53 ` Kieran Kunhya
2024-01-30 11:47 ` Anton Khirnov
2024-01-28 19:17 ` Rémi Denis-Courmont
2024-01-28 20:33 ` Michael Niedermayer
2024-01-29 14:38 ` Derek Buitenhuis
2024-01-29 18:25 ` Michael Niedermayer
2024-01-29 18:37 ` Derek Buitenhuis
2024-01-29 19:21 ` Michael Niedermayer
2024-01-29 20:09 ` Vittorio Giovara
2024-01-29 20:15 ` Derek Buitenhuis
2024-01-30 6:48 ` Rémi Denis-Courmont
2024-01-29 20:19 ` Anton Khirnov
2024-01-29 20:20 ` Derek Buitenhuis
2024-01-29 20:36 ` Vittorio Giovara
2024-01-29 21:27 ` Michael Niedermayer
2024-01-31 11:19 ` Anton Khirnov
2024-01-29 20:41 ` Diederick C. Niehorster
2024-01-29 21:19 ` Anton Khirnov
2024-01-29 21:11 ` Anton Khirnov
2024-01-29 23:41 ` Jonatas L. Nogueira via ffmpeg-devel
2024-01-29 23:53 ` Stefano Sabatini
2024-01-31 12:30 ` Anton Khirnov
2024-01-31 21:26 ` Stefano Sabatini
2024-01-30 0:15 ` Michael Niedermayer
2024-01-30 0:19 ` Michael Niedermayer
2024-01-31 12:59 ` Anton Khirnov
2024-01-31 14:10 ` Jonatas L. Nogueira via ffmpeg-devel
2024-01-31 15:17 ` Anton Khirnov
2024-01-31 15:17 ` Kieran Kunhya
2024-01-31 16:00 ` Jonatas L. Nogueira via ffmpeg-devel
2024-01-31 16:03 ` Jonatas L. Nogueira via ffmpeg-devel
2024-01-31 16:10 ` Rémi Denis-Courmont
2024-01-31 17:04 ` Jonatas L. Nogueira via ffmpeg-devel
2024-01-31 18:03 ` Michael Niedermayer
2024-01-31 18:22 ` Kieran Kunhya
2024-01-31 18:40 ` Jonatas L. Nogueira via ffmpeg-devel
2024-01-31 18:48 ` Kieran Kunhya
2024-01-31 19:07 ` Michael Niedermayer
[not found] ` <A7F30D96-F8DB-45EA-9CDB-3545E3ECE0C9@cosmin.at>
2024-01-31 19:16 ` Cosmin Stejerean via ffmpeg-devel
2024-01-31 20:19 ` Kieran Kunhya
2024-01-31 21:43 ` Michael Niedermayer
2024-01-31 21:54 ` Kieran Kunhya
2024-01-31 22:40 ` Michael Niedermayer
2024-01-31 22:45 ` Kieran Kunhya
2024-02-02 13:52 ` Michael Niedermayer
2024-02-02 13:58 ` Kieran Kunhya
2024-01-31 19:20 ` Jonatas L. Nogueira via ffmpeg-devel
2024-01-31 17:58 ` Michael Niedermayer
2024-01-31 23:15 ` Stefano Sabatini
2024-02-01 0:16 ` Stefano Sabatini
2024-02-06 0:00 ` Jonatas L. Nogueira via ffmpeg-devel
2024-01-30 1:48 ` Michael Niedermayer
2024-01-30 9:32 ` Vittorio Giovara
2024-01-30 10:07 ` Nicolas George
2024-01-30 10:13 ` Vittorio Giovara
2024-01-30 10:15 ` Nicolas George
2024-01-30 10:56 ` Vittorio Giovara
2024-01-31 1:07 ` Michael Niedermayer
2024-01-31 21:44 ` Derek Buitenhuis
2024-01-31 21:55 ` Kieran Kunhya
2024-01-31 23:07 ` Michael Niedermayer
2024-02-01 17:59 ` Anton Khirnov
2024-02-01 18:14 ` Rémi Denis-Courmont
2024-02-01 22:55 ` Michael Niedermayer
2024-02-05 10:21 ` Michael Niedermayer
2024-02-05 11:53 ` Kieran Kunhya
2024-02-05 13:10 ` Zhao Zhili
2024-02-01 19:22 ` Derek Buitenhuis
2024-02-04 9:49 ` Rémi Denis-Courmont
2024-02-04 10:02 ` J. Dekker
2024-02-04 10:09 ` Paul B Mahol
2024-02-04 13:41 ` Michael Niedermayer
2024-02-04 14:38 ` Rémi Denis-Courmont
2024-02-04 19:28 ` Michael Niedermayer
2024-02-04 21:21 ` Rémi Denis-Courmont
2024-04-12 23:43 ` Thilo Borgmann via ffmpeg-devel
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='CALE=2=_oFqmFJWe53iHENBPe8UP_8gKkwLiHYSGXVwv1r0z2iQ@mail.gmail.com' \
--to=ffmpeg-devel@ffmpeg.org \
--cc=jesusalva@spi-inc.org \
--cc=kierank@obe.tv \
--cc=michael@niedermayer.cc \
/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