[FFmpeg-devel] [RFC] Vote STF/SPI 2024-02

[FFmpeg-devel] [RFC] Vote STF/SPI 2024-02

[Michael Niedermayer]

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

Hi all

To do the STF/SPI thing properly, and make sure we do what the Community wants.
We should do this vote: (unless lots of people reply and say we should skip the vote)
(i am also CCing jonatan to make sure the option in the vote actually ask the GA the
 right question)

The vote description will be as follows:
The STF/SPI has suggested us to submit an Application / Scope of work before their february meeting.
There are about 2 weeks left.
The minimum grant is 150 000 €
The next STF meeting is expected to be in may. If we submit in february and are not selected
we can probably try again in may. Which would increase our chances
If we do not submit in february we can probably submit in may.
There is no guarantee that money will be available in may, for example between october 2023
and february 2024 no funds where available AFAIK.
Wiki page is here: https://trac.ffmpeg.org/wiki/SponsoringPrograms/STF/2024


Option A. The Application and Scope of Work from the WIKI shall be submitted to STF/SPI before the february 2024 meeting, disagreements in it shall be decided by the TC. To achieve continuity, submission shall be done by the same person as previous if possible.

Option B. No Application and Scope of Work shall be submitted in february 2024


This is a RFC, so if you see errors in it please suggest changes

Thx

-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

If you fake or manipulate statistics in a paper in physics you will never
get a job again.
If you fake or manipulate statistics in a paper in medicin you will get
a job for life at the pharma industry.

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

Re: [FFmpeg-devel] [RFC] Vote STF/SPI 2024-02

[Vittorio Giovara]

On Thu, Feb 1, 2024 at 5:29 AM Michael Niedermayer <michael@niedermayer.cc>
wrote:

> Hi all
>
> To do the STF/SPI thing properly, and make sure we do what the Community
> wants.
> We should do this vote: (unless lots of people reply and say we should
> skip the vote)
> (i am also CCing jonatan to make sure the option in the vote actually ask
> the GA the
>  right question)
>
> The vote description will be as follows:
> The STF/SPI has suggested us to submit an Application / Scope of work
> before their february meeting.
> There are about 2 weeks left.
> The minimum grant is 150 000 €
> The next STF meeting is expected to be in may. If we submit in february
> and are not selected
> we can probably try again in may. Which would increase our chances
> If we do not submit in february we can probably submit in may.
> There is no guarantee that money will be available in may, for example
> between october 2023
> and february 2024 no funds where available AFAIK.
> Wiki page is here:
> https://trac.ffmpeg.org/wiki/SponsoringPrograms/STF/2024
>
>
> Option A. The Application and Scope of Work from the WIKI shall be
> submitted to STF/SPI before the february 2024 meeting, disagreements in it
> shall be decided by the TC. To achieve continuity, submission shall be done
> by the same person as previous if possible.
>
> Option B. No Application and Scope of Work shall be submitted in february
> 2024
>

Since all objections and requests for more time have been ignored, and this
is happening anyway, can we add a small amendment for the sake of
transparency and for avoiding any conflict of interest? Whoever was
involved with the STF/SPI talks cannot be the recipient of the sponsorship.
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.

I'm aware that would exclude Micheal, Thilo, and technically Jonatas, but
at this point it's the only way I can see this move forward in any
direction.

Jonatas any feedback on this possibility?
Thank you
-- 
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".

Re: [FFmpeg-devel] [RFC] Vote STF/SPI 2024-02

[Cosmin Stejerean via ffmpeg-devel]

> On Feb 1, 2024, at 9:45 AM, Vittorio Giovara <vittorio.giovara@gmail.com> wrote:
> 
> Since all objections and requests for more time have been ignored, and this
> is happening anyway, can we add a small amendment for the sake of
> transparency and for avoiding any conflict of interest? Whoever was
> involved with the STF/SPI talks cannot be the recipient of the sponsorship.
> 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.
> 
> I'm aware that would exclude Micheal, Thilo, and technically Jonatas, but
> at this point it's the only way I can see this move forward in any
> direction.

Why would anyone (qualified) who wants to work on maintenance be excluded? 

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

Re: [FFmpeg-devel] [RFC] Vote STF/SPI 2024-02

[Michael Niedermayer]

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

On Thu, Feb 01, 2024 at 06:45:52PM +0100, Vittorio Giovara wrote:
> On Thu, Feb 1, 2024 at 5:29 AM Michael Niedermayer <michael@niedermayer.cc>
> wrote:
> 
> > Hi all
> >
> > To do the STF/SPI thing properly, and make sure we do what the Community
> > wants.
> > We should do this vote: (unless lots of people reply and say we should
> > skip the vote)
> > (i am also CCing jonatan to make sure the option in the vote actually ask
> > the GA the
> >  right question)
> >
> > The vote description will be as follows:
> > The STF/SPI has suggested us to submit an Application / Scope of work
> > before their february meeting.
> > There are about 2 weeks left.
> > The minimum grant is 150 000 €
> > The next STF meeting is expected to be in may. If we submit in february
> > and are not selected
> > we can probably try again in may. Which would increase our chances
> > If we do not submit in february we can probably submit in may.
> > There is no guarantee that money will be available in may, for example
> > between october 2023
> > and february 2024 no funds where available AFAIK.
> > Wiki page is here:
> > https://trac.ffmpeg.org/wiki/SponsoringPrograms/STF/2024
> >
> >
> > Option A. The Application and Scope of Work from the WIKI shall be
> > submitted to STF/SPI before the february 2024 meeting, disagreements in it
> > shall be decided by the TC. To achieve continuity, submission shall be done
> > by the same person as previous if possible.
> >
> > Option B. No Application and Scope of Work shall be submitted in february
> > 2024
> >
> 
> Since all objections and requests for more time have been ignored, and this
> is happening anyway, can we add a small amendment for the sake of
> transparency and for avoiding any conflict of interest? Whoever was
> involved with the STF/SPI talks cannot be the recipient of the sponsorship.
> 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.
> 
> I'm aware that would exclude Micheal, Thilo, and technically Jonatas, but
> at this point it's the only way I can see this move forward in any
> direction.

Its very easy to add a Option C to the vote

but there are 2 things that needs to be pointed out
First, this may be considered "not fair" by STF, fairness being one thing
that was explicitly mentioned in some of the mails from STF

Second we currently dont have enough people on the wiki page to even get close
to the minimum. So excluding from the few that are interrested in this is a strange
move. Unless one just wants this to fail.

thx

[...]
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

"I am not trying to be anyone's saviour, I'm trying to think about the
 future and not be sad" - Elon Musk


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

Re: [FFmpeg-devel] [RFC] Vote STF/SPI 2024-02

[Jonatas L. Nogueira via ffmpeg-devel]

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

I honestly didn't understood this part. Maybe because I'm not involved with
FFmpeg internal workings and policies, but could you clarify the exact
differences, here? (How it would work, etc.)

As for the other part of the request, I can't comment on the inclusion or
not of the restriction as that's still FFmpeg internal policies, but from
SPI side, we try to avoid having the liaison approving their own expenses
when it could indeed pose such risk (so if it's a purchase of hardware for
example, there's no need as there are already two other peers reviewing
it). Although usually liaisons avoid such situations on their own and often
provide additional documentation in those cases. This avoids neatly
conflicts of interest, as far as someone approving their own expense goes.
I'm not sure why blocking them from participating altogether would be
necessary, it sounds a bit like an intent to be a punishment and I really
think in such case it should be dealt with separately.

As Michael said, STF expect the procedure to be fair, a restriction which
might look like a witch hunt could be refused regardless of the actual
reason, so in my opinion there are two better ways to make such restriction
and have a better chance of STF accepting it.

1. if Michael, Thilo and me received a penalty from FFmpeg which prevents
them (us?) from doing contractor work for FFmpeg instead of approving the
contract work with restrictions on who can participate, that would remain
fair and be better documented altogether. As another poll, it would also
ensure a right for defense and a well documented motivation. STF would be
more likely to accept in such form. It also maintains the discussion over
sponsorship impartial.

2. Another alternative is making a permanent governance that whoever
procures sponsorships are not able to participate on them. This would
almost definitely be accepted by STF and address better the concerns,
although it might severely hinder FFmpeg capability to procure sponsorships
in future as it serves as a strong incentive to NOT seek sponsorships in
future (and is the main reason why some projects or entities make similar
rules).

Both alternatives should be considered fair by STF unless you really mess
them up, so don't let their demand for fairness to escalate into a "you
must let Jonatas to participate or no money for you!" or similar nonsense.

Of course, if they voluntarily renounce the right to participate that's an
entirely different story. Anyone can do that, but that's entirely up to
them and trying to coerce them into doing so (or not doing so) would be
really frowned upon.

Att.,

Jonatas L. Nogueira (“Jesusalva”)

On Thu, Feb 1, 2024, 14:46 Vittorio Giovara <vittorio.giovara@gmail.com>
wrote:

>
>
> On Thu, Feb 1, 2024 at 5:29 AM Michael Niedermayer <michael@niedermayer.cc>
> wrote:
>
>> Hi all
>>
>> To do the STF/SPI thing properly, and make sure we do what the Community
>> wants.
>> We should do this vote: (unless lots of people reply and say we should
>> skip the vote)
>> (i am also CCing jonatan to make sure the option in the vote actually ask
>> the GA the
>>  right question)
>>
>> The vote description will be as follows:
>> The STF/SPI has suggested us to submit an Application / Scope of work
>> before their february meeting.
>> There are about 2 weeks left.
>> The minimum grant is 150 000 €
>> The next STF meeting is expected to be in may. If we submit in february
>> and are not selected
>> we can probably try again in may. Which would increase our chances
>> If we do not submit in february we can probably submit in may.
>> There is no guarantee that money will be available in may, for example
>> between october 2023
>> and february 2024 no funds where available AFAIK.
>> Wiki page is here:
>> https://trac.ffmpeg.org/wiki/SponsoringPrograms/STF/2024
>>
>>
>> Option A. The Application and Scope of Work from the WIKI shall be
>> submitted to STF/SPI before the february 2024 meeting, disagreements in it
>> shall be decided by the TC. To achieve continuity, submission shall be done
>> by the same person as previous if possible.
>>
>> Option B. No Application and Scope of Work shall be submitted in february
>> 2024
>>
>
> Since all objections and requests for more time have been ignored, and
> this is happening anyway, can we add a small amendment for the sake of
> transparency and for avoiding any conflict of interest? Whoever was
> involved with the STF/SPI talks cannot be the recipient of the sponsorship.
> 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.
>
> I'm aware that would exclude Micheal, Thilo, and technically Jonatas, but
> at this point it's the only way I can see this move forward in any
> direction.
>
> Jonatas any feedback on this possibility?
> Thank you
> --
> 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".

Re: [FFmpeg-devel] [RFC] Vote STF/SPI 2024-02

[Michael Niedermayer]

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

Hi Jonatas

On Thu, Feb 01, 2024 at 04:42:34PM -0300, Jonatas L. Nogueira via ffmpeg-devel wrote:
[...]

> Of course, if they voluntarily renounce the right to participate that's an
> entirely different story. Anyone can do that, but that's entirely up to
> them and trying to coerce them into doing so (or not doing so) would be
> really frowned upon.

In this first iteration of STF i mainly want to participate for 2 reasons

1. to fill the lack of people (ATM we have just one guy who isnt sure he
even has time for his project) on the wiki

2. to troll people into adding themself (as in, if you dont, ill be there and
will take the opertunity)

So iam happy to renounce my participation in STF 2024-02 conditional we reach 200k €
which is the target iam aiming at for the whole submission and noone else
drops out and we arent in need of more developers for STF.

It seems really dumb not to participate if we cant reach enough people to ask
for a minimum of 150k and i think we should aim a tiny bit above that

thx

[...]
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Old school: Use the lowest level language in which you can solve the problem
            conveniently.
New school: Use the highest level language in which the latest supercomputer
            can solve the problem without the user falling asleep waiting.

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

Re: [FFmpeg-devel] [RFC] Vote STF/SPI 2024-02

[Rémi Denis-Courmont]

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.


Frankly, if Thilo secures the funding, it's between him and the German 
authorities what they want to spend it on, as long as it remains within the 
boundaries of applicable laws. If he can come with a project to fund Michael 
to maintain FFmpeg for a while, FFmpeg will be no worse off.

Nobody should claim to represent FFmpeg without any kind of preexisting 
delegation to do so. If that was done, then that is very morally wrong. But 
realistically, we cannot enforce that. Some people did it in the past and will 
continue to do it in the future. It is effectively up the other parties to 
perform due diligence and not get fooled - if they even care. STF probably 
does not care; NAB most certainly does not care.

Moreover pretenses of this process being open need to be dropped. It's not 
open if any and all objections are summarily rejected to put it politely. A 
short deadline is not an excuse, even if it was unavoidable. (And I remain 
unconvinced that public discussion could not start earlier than they did.)

Ultimately, whatever comes out of this does not get any special exemption from 
code review standards and TC oversight, but that should be a given. Therefore 
this funding should much preferably be used toward as uncontroversial tasks as 
possible: Maintainance is a good example. SDR is a counter-example.


With that long side note, while I agree with most of what you said otherwise, 
I don't think that there is any merit to excluding Michael from this process, 
doubly so if there are too few viable proposals.

-- 
雷米‧德尼-库尔蒙
http://www.remlab.net/



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

Re: [FFmpeg-devel] [RFC] Vote STF/SPI 2024-02

[Vittorio Giovara]

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

Re: [FFmpeg-devel] [RFC] Vote STF/SPI 2024-02

[Michael Niedermayer]

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

On Thu, Feb 01, 2024 at 05:29:26AM +0100, Michael Niedermayer wrote:
> Hi all
> 
> To do the STF/SPI thing properly, and make sure we do what the Community wants.
> We should do this vote: (unless lots of people reply and say we should skip the vote)
> (i am also CCing jonatan to make sure the option in the vote actually ask the GA the
>  right question)
> 
> The vote description will be as follows:
> The STF/SPI has suggested us to submit an Application / Scope of work before their february meeting.
> There are about 2 weeks left.
> The minimum grant is 150 000 €
> The next STF meeting is expected to be in may. If we submit in february and are not selected
> we can probably try again in may. Which would increase our chances
> If we do not submit in february we can probably submit in may.
> There is no guarantee that money will be available in may, for example between october 2023
> and february 2024 no funds where available AFAIK.
> Wiki page is here: https://trac.ffmpeg.org/wiki/SponsoringPrograms/STF/2024
> 
> 
> Option A. The Application and Scope of Work from the WIKI shall be submitted to STF/SPI before the february 2024 meeting, disagreements in it shall be decided by the TC. To achieve continuity, submission shall be done by the same person as previous if possible.
> 
> Option B. No Application and Scope of Work shall be submitted in february 2024
> 
> 
> This is a RFC, so if you see errors in it please suggest changes

I intend to start the vote in teh next 24h or so.
If someone wants a option C or sees something that needs correcting
please speak up soon and be precisse what/why should be changed
(for an option C, if you want one please suggest an exact text)

thx

[...]

-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Any man who breaks a law that conscience tells him is unjust and willingly 
accepts the penalty by staying in jail in order to arouse the conscience of 
the community on the injustice of the law is at that moment expressing the 
very highest respect for law. - Martin Luther King Jr

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

Re: [FFmpeg-devel] [RFC] Vote STF/SPI 2024-02

[Stefano Sabatini]

On date Saturday 2024-02-03 04:37:54 +0100, Michael Niedermayer wrote:
> On Thu, Feb 01, 2024 at 05:29:26AM +0100, Michael Niedermayer wrote:
> > Hi all
> > 
> > To do the STF/SPI thing properly, and make sure we do what the Community wants.
> > We should do this vote: (unless lots of people reply and say we should skip the vote)
> > (i am also CCing jonatan to make sure the option in the vote actually ask the GA the
> >  right question)
> > 
> > The vote description will be as follows:
> > The STF/SPI has suggested us to submit an Application / Scope of work before their february meeting.
> > There are about 2 weeks left.
> > The minimum grant is 150 000 €
> > The next STF meeting is expected to be in may. If we submit in february and are not selected
> > we can probably try again in may. Which would increase our chances
> > If we do not submit in february we can probably submit in may.
> > There is no guarantee that money will be available in may, for example between october 2023
> > and february 2024 no funds where available AFAIK.
> > Wiki page is here: https://trac.ffmpeg.org/wiki/SponsoringPrograms/STF/2024
> > 
> > 

> > Option A. The Application and Scope of Work from the WIKI shall be
> > submitted to STF/SPI before the february 2024 meeting,
> > disagreements in it shall be decided by the TC. To achieve
> > continuity, submission shall be done by the same person as
> > previous if possible.


> > 
> > Option B. No Application and Scope of Work shall be submitted in
> > february 2024

> > 
> > 
> > This is a RFC, so if you see errors in it please suggest changes

Looks good to me.

I was wondering it it would make sense to consider the next deadline
as a different option, but this would add complexity to the vote and
we don't even know if the grant would still be available by then, so
it's best not to consider it for the moment.
_______________________________________________
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".

Re: [FFmpeg-devel] [RFC] Vote STF/SPI 2024-02

[Michael Niedermayer]

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

On Sat, Feb 03, 2024 at 04:37:54AM +0100, Michael Niedermayer wrote:
> On Thu, Feb 01, 2024 at 05:29:26AM +0100, Michael Niedermayer wrote:
> > Hi all
> > 
> > To do the STF/SPI thing properly, and make sure we do what the Community wants.
> > We should do this vote: (unless lots of people reply and say we should skip the vote)
> > (i am also CCing jonatan to make sure the option in the vote actually ask the GA the
> >  right question)
> > 
> > The vote description will be as follows:
> > The STF/SPI has suggested us to submit an Application / Scope of work before their february meeting.
> > There are about 2 weeks left.
> > The minimum grant is 150 000 €
> > The next STF meeting is expected to be in may. If we submit in february and are not selected
> > we can probably try again in may. Which would increase our chances
> > If we do not submit in february we can probably submit in may.
> > There is no guarantee that money will be available in may, for example between october 2023
> > and february 2024 no funds where available AFAIK.
> > Wiki page is here: https://trac.ffmpeg.org/wiki/SponsoringPrograms/STF/2024
> > 
> > 
> > Option A. The Application and Scope of Work from the WIKI shall be submitted to STF/SPI before the february 2024 meeting, disagreements in it shall be decided by the TC. To achieve continuity, submission shall be done by the same person as previous if possible.
> > 
> > Option B. No Application and Scope of Work shall be submitted in february 2024
> > 
> > 
> > This is a RFC, so if you see errors in it please suggest changes
> 
> I intend to start the vote in teh next 24h or so.

Vote started, you should have received a mail if you are in the GA
and you should not have received a mail if you are not in the GA
50 mails where sent and there are 50 in the script output.
I hope that no messup happened in this vote

Please Vote!

thx

[...]

-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

The bravest are surely those who have the clearest vision
of what is before them, glory and danger alike, and yet
notwithstanding go out to meet it. -- Thucydides

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

Re: [FFmpeg-devel] [RFC] Vote STF/SPI 2024-02

[Paul B Mahol]

On Sun, Feb 4, 2024 at 1:42 AM Michael Niedermayer <michael@niedermayer.cc>
wrote:

> On Sat, Feb 03, 2024 at 04:37:54AM +0100, Michael Niedermayer wrote:
> > On Thu, Feb 01, 2024 at 05:29:26AM +0100, Michael Niedermayer wrote:
> > > Hi all
> > >
> > > To do the STF/SPI thing properly, and make sure we do what the
> Community wants.
> > > We should do this vote: (unless lots of people reply and say we should
> skip the vote)
> > > (i am also CCing jonatan to make sure the option in the vote actually
> ask the GA the
> > >  right question)
> > >
> > > The vote description will be as follows:
> > > The STF/SPI has suggested us to submit an Application / Scope of work
> before their february meeting.
> > > There are about 2 weeks left.
> > > The minimum grant is 150 000 €
> > > The next STF meeting is expected to be in may. If we submit in
> february and are not selected
> > > we can probably try again in may. Which would increase our chances
> > > If we do not submit in february we can probably submit in may.
> > > There is no guarantee that money will be available in may, for example
> between october 2023
> > > and february 2024 no funds where available AFAIK.
> > > Wiki page is here:
> https://trac.ffmpeg.org/wiki/SponsoringPrograms/STF/2024
> > >
> > >
> > > Option A. The Application and Scope of Work from the WIKI shall be
> submitted to STF/SPI before the february 2024 meeting, disagreements in it
> shall be decided by the TC. To achieve continuity, submission shall be done
> by the same person as previous if possible.
> > >
> > > Option B. No Application and Scope of Work shall be submitted in
> february 2024
> > >
> > >
> > > This is a RFC, so if you see errors in it please suggest changes
> >
> > I intend to start the vote in teh next 24h or so.
>
> Vote started, you should have received a mail if you are in the GA
> and you should not have received a mail if you are not in the GA
> 50 mails where sent and there are 50 in the script output.
> I hope that no messup happened in this vote
>
> Please Vote!
>

Never vote for dead project. Controlled by money.


>
> thx
>
> [...]
>
> --
> Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
>
> The bravest are surely those who have the clearest vision
> of what is before them, glory and danger alike, and yet
> notwithstanding go out to meet it. -- Thucydides
> _______________________________________________
> 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".
>
_______________________________________________
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".

Re: [FFmpeg-devel] [RFC] Vote STF/SPI 2024-02

[Michael Niedermayer]

[-- Attachment #1.1.1: Type: text/plain, Size: 3412 bytes --]

On Sun, Feb 04, 2024 at 01:42:31AM +0100, Michael Niedermayer wrote:
> On Sat, Feb 03, 2024 at 04:37:54AM +0100, Michael Niedermayer wrote:
> > On Thu, Feb 01, 2024 at 05:29:26AM +0100, Michael Niedermayer wrote:
> > > Hi all
> > > 
> > > To do the STF/SPI thing properly, and make sure we do what the Community wants.
> > > We should do this vote: (unless lots of people reply and say we should skip the vote)
> > > (i am also CCing jonatan to make sure the option in the vote actually ask the GA the
> > >  right question)
> > > 
> > > The vote description will be as follows:
> > > The STF/SPI has suggested us to submit an Application / Scope of work before their february meeting.
> > > There are about 2 weeks left.
> > > The minimum grant is 150 000 €
> > > The next STF meeting is expected to be in may. If we submit in february and are not selected
> > > we can probably try again in may. Which would increase our chances
> > > If we do not submit in february we can probably submit in may.
> > > There is no guarantee that money will be available in may, for example between october 2023
> > > and february 2024 no funds where available AFAIK.
> > > Wiki page is here: https://trac.ffmpeg.org/wiki/SponsoringPrograms/STF/2024
> > > 
> > > 
> > > Option A. The Application and Scope of Work from the WIKI shall be submitted to STF/SPI before the february 2024 meeting, disagreements in it shall be decided by the TC. To achieve continuity, submission shall be done by the same person as previous if possible.
> > > 
> > > Option B. No Application and Scope of Work shall be submitted in february 2024
> > > 
> > > 
> > > This is a RFC, so if you see errors in it please suggest changes
> > 
> > I intend to start the vote in teh next 24h or so.
> 
> Vote started, you should have received a mail if you are in the GA
> and you should not have received a mail if you are not in the GA
> 50 mails where sent and there are 50 in the script output.
> I hope that no messup happened in this vote
> 
> Please Vote!

As the specified end date of 2024-02-11 has come, and we are over high noon, the
contestants are standing in front of each other, tense with their hands over their
pistols, who will walk away today and who will not.

The winner is miss february, she drew her gun first, shot and hit
    "The Application and Scope of Work from the WIKI shall be submitted to STF/SPI before the february 2024 meeting, disagreements in it shall be decided by the TC. To achieve continuity, submission shall be done by the same person as previous, if possible." Won

Miss may lost this round, she recieves a free hankachief to wipe the water from miss february water pistol off
    "No Application and Scope of Work shall be submitted in february 2024", Lost


The CSV file with details is attached

Announced end of poll: 2024-02-11
Actual time poll closed: 2/11/2024, 1:27:15 PM
Private poll (50 authorized voters)
Actual votes cast: 23

I wish all contestants good luck and please soon come and play again!

thx

[...]

-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

The real ebay dictionary, page 1
"Used only once"    - "Some unspecified defect prevented a second use"
"In good condition" - "Can be repaird by experienced expert"
"As is" - "You wouldnt want it even if you were payed for it, if you knew ..."

[-- Attachment #1.1.2: civs_ballots_february_may.csv --]
[-- Type: text/csv, Size: 414 bytes --]

The Application and Scope of Work from the WIKI shall be submitted to STF/SPI before the february 2024 meeting, disagreements in it shall be decided by the TC. To achieve continuity, submission shall be done by the same person as previous, if possible.,No Application and Scope of Work shall be submitted in february 2024
1,2
1,2
1,2
1,2
1,2
2,1
2,1
1,2
2,1
1,2
1,2
1,2
1,2
1,2
2,1
1,2
1,2
1,2
1,2
1,2
1,2
1,2
2,1

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