[FFmpeg-devel] [RFC] fateserver

[FFmpeg-devel] [RFC] fateserver

[Michael Niedermayer]

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

Hi all

Both fateserver and the fateserver rewrite lack a mainteiner

The original:
https://fate.ffmpeg.org/
perl code here:
https://git.ffmpeg.org/fateserver

The rewrite (from Timothy Gu unmaintained since 2016)
https://fatebeta.ffmpeg.org/
https://github.com/TimothyGu/fateserver-node

Really only one of these need to be maintained, but one needs to be

If you know someone who may be interersted in this, please tell me

The situation ATM, where when someone reports an issue, theres noone
responsible, noone taking care of it even with simple issues. Is really
not good

thx

-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Complexity theory is the science of finding the exact solution to an
approximation. Benchmarking OTOH is finding an approximation of the exact

[-- 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] fateserver

[Marth64]

I'm willing to help. I have experience with Node.JS and Express (the
rewrite).

Thank you,

On Sat, Feb 24, 2024 at 11:49 AM Michael Niedermayer <michael@niedermayer.cc>
wrote:

> Hi all
>
> Both fateserver and the fateserver rewrite lack a mainteiner
>
> The original:
> https://fate.ffmpeg.org/
> perl code here:
> https://git.ffmpeg.org/fateserver
>
> The rewrite (from Timothy Gu unmaintained since 2016)
> https://fatebeta.ffmpeg.org/
> https://github.com/TimothyGu/fateserver-node
>
> Really only one of these need to be maintained, but one needs to be
>
> If you know someone who may be interersted in this, please tell me
>
> The situation ATM, where when someone reports an issue, theres noone
> responsible, noone taking care of it even with simple issues. Is really
> not good
>
> thx
>
> --
> Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
>
> Complexity theory is the science of finding the exact solution to an
> approximation. Benchmarking OTOH is finding an approximation of the exact
> _______________________________________________
> 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] fateserver

[Michael Niedermayer]

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

Hi Marth64

adding Timothy and baptiste to the CC

On Sun, Feb 25, 2024 at 12:36:08AM -0600, Marth64 wrote:
> I'm willing to help. I have experience with Node.JS and Express (the
> rewrite).

great.

So i guess the first goal would be to make it possible to switch
fate.ffmpeg.org to the rewrite thats ATM available on fatebeta.ffmpeg.org

Does anyone know whats missing in teh rewrite ?
I do know it doesnt start automatically, i have to after every reboot manually
cd into its directory and do a npm start
(this obviously should be automatic and maybe it should be restarted if it dies)

the rewrite really runs under the fate account ATM.

So what are the next steps here ?
* we need to have it come up automatic on reboots (whats the proper way for
  this node js stuff to autostart?)
* we need to know whats missing in the rewrite relative to the old code
* things need to be documented (if they are not)
* missing things need to be implemented
* all things need to be tested
  what i mean by this is a simple test setup of the fateserver + a fate
  client + the showing up properly in a browser.
* missing things need to be deployed (and verified that they work)
  for this i think the easiest will be to give you ssh access to the
  fate account on the fateserver (and root if needed and baptiste agrees)
* and then we just rename the fatebeta thing with fate

If i am missing anything please someone correct me.
Otherwise, i think you can start working anytime you like and if theres
anything you need please tell me or reply here or in a new thread.

thx

> 
> Thank you,
> 
> On Sat, Feb 24, 2024 at 11:49 AM Michael Niedermayer <michael@niedermayer.cc>
> wrote:
> 
> > Hi all
> >
> > Both fateserver and the fateserver rewrite lack a mainteiner
> >
> > The original:
> > https://fate.ffmpeg.org/
> > perl code here:
> > https://git.ffmpeg.org/fateserver
> >
> > The rewrite (from Timothy Gu unmaintained since 2016)
> > https://fatebeta.ffmpeg.org/
> > https://github.com/TimothyGu/fateserver-node
> >
> > Really only one of these need to be maintained, but one needs to be
> >
> > If you know someone who may be interersted in this, please tell me
> >
> > The situation ATM, where when someone reports an issue, theres noone
> > responsible, noone taking care of it even with simple issues. Is really
> > not good
> >
> > thx
> >
> > --
> > Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
> >
> > Complexity theory is the science of finding the exact solution to an
> > approximation. Benchmarking OTOH is finding an approximation of the exact
> > _______________________________________________
> > 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".

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

[Marth64]

Thank you Michael, for the opportunity.  I have some initial questions
while others add the remaining detail.

1) What is the flow of test result data like? e.g.  do individual test
servers send the data via API? Or does this tool query them directly.
2) Are you open to Docker containerization (with rootless)? In this way,
the application is jailed and can restart automatically on its own. Also,
more flexibility on the host machine itself.

On Sun, Feb 25, 2024 at 1:28 PM Michael Niedermayer <michael@niedermayer.cc>
wrote:

> Hi Marth64
>
> adding Timothy and baptiste to the CC
>
> On Sun, Feb 25, 2024 at 12:36:08AM -0600, Marth64 wrote:
> > I'm willing to help. I have experience with Node.JS and Express (the
> > rewrite).
>
> great.
>
> So i guess the first goal would be to make it possible to switch
> fate.ffmpeg.org to the rewrite thats ATM available on fatebeta.ffmpeg.org
>
> Does anyone know whats missing in teh rewrite ?
> I do know it doesnt start automatically, i have to after every reboot
> manually
> cd into its directory and do a npm start
> (this obviously should be automatic and maybe it should be restarted if it
> dies)
>
> the rewrite really runs under the fate account ATM.
>
> So what are the next steps here ?
> * we need to have it come up automatic on reboots (whats the proper way for
>   this node js stuff to autostart?)
> * we need to know whats missing in the rewrite relative to the old code
> * things need to be documented (if they are not)
> * missing things need to be implemented
> * all things need to be tested
>   what i mean by this is a simple test setup of the fateserver + a fate
>   client + the showing up properly in a browser.
> * missing things need to be deployed (and verified that they work)
>   for this i think the easiest will be to give you ssh access to the
>   fate account on the fateserver (and root if needed and baptiste agrees)
> * and then we just rename the fatebeta thing with fate
>
> If i am missing anything please someone correct me.
> Otherwise, i think you can start working anytime you like and if theres
> anything you need please tell me or reply here or in a new thread.
>
> thx
>
> >
> > Thank you,
> >
> > On Sat, Feb 24, 2024 at 11:49 AM Michael Niedermayer <
> michael@niedermayer.cc>
> > wrote:
> >
> > > Hi all
> > >
> > > Both fateserver and the fateserver rewrite lack a mainteiner
> > >
> > > The original:
> > > https://fate.ffmpeg.org/
> > > perl code here:
> > > https://git.ffmpeg.org/fateserver
> > >
> > > The rewrite (from Timothy Gu unmaintained since 2016)
> > > https://fatebeta.ffmpeg.org/
> > > https://github.com/TimothyGu/fateserver-node
> > >
> > > Really only one of these need to be maintained, but one needs to be
> > >
> > > If you know someone who may be interersted in this, please tell me
> > >
> > > The situation ATM, where when someone reports an issue, theres noone
> > > responsible, noone taking care of it even with simple issues. Is really
> > > not good
> > >
> > > thx
> > >
> > > --
> > > Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
> > >
> > > Complexity theory is the science of finding the exact solution to an
> > > approximation. Benchmarking OTOH is finding an approximation of the
> exact
> > > _______________________________________________
> > > 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".
>
> --
> 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
> ..."
> _______________________________________________
> 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] fateserver

[Michael Niedermayer]

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

On Sun, Feb 25, 2024 at 06:21:14PM -0600, Marth64 wrote:
> Thank you Michael, for the opportunity.  I have some initial questions
> while others add the remaining detail.
> 

> 1) What is the flow of test result data like? e.g.  do individual test
> servers send the data via API? Or does this tool query them directly.

fate clients send data via ssh to fate-recv.sh from fateserver

the way this is triggered is up to the person running teh individual fate client
it can be a simple for loop in a shell script

thx

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

Concerning the gods, I have no means of knowing whether they exist or not
or of what sort they may be, because of the obscurity of the subject, and
the brevity of human life -- Protagoras

[-- 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] fateserver

[Michael Niedermayer]

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

Hi

On Sun, Feb 25, 2024 at 06:21:14PM -0600, Marth64 wrote:
> Thank you Michael, for the opportunity.  I have some initial questions
> while others add the remaining detail.
> 
[...]
> 2) Are you open to Docker containerization (with rootless)? In this way,
> the application is jailed and can restart automatically on its own. Also,
> more flexibility on the host machine itself.

This depends on who maintains the setup. I dont volunteer to maintain
a extra container layer. But if someone else does it and i never have
to deal with it (and assuming baptiste has no objections) thats perfectly
fine with me. But for example if you setup ssh (for the fate client
connections) in a docker, apache / nginx in a docker, ...
all this needs to get security updates.

thx

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

If a bugfix only changes things apparently unrelated to the bug with no
further explanation, that is a good sign that the bugfix is wrong.

[-- 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] fateserver

[Marth64]

Hi Michael, all,

While awaiting direction I will go ahead and study this process further.
From an overall view, it is something I am comfortable to help maintain.
Perhaps my focus can be to get the current version in a stable place, and
work on a long term improvement strategy to the rewrite version.

If Docker is allowed, with regard to security updates within the Docker
container: I have known processes to do this and will be transparent with,
I also have experience with vulnerability management so I will apply that
lens proactively.

Thanks,


On Mon, Feb 26, 2024 at 8:30 AM Michael Niedermayer <michael@niedermayer.cc>
wrote:

> Hi
>
> On Sun, Feb 25, 2024 at 06:21:14PM -0600, Marth64 wrote:
> > Thank you Michael, for the opportunity.  I have some initial questions
> > while others add the remaining detail.
> >
> [...]
> > 2) Are you open to Docker containerization (with rootless)? In this way,
> > the application is jailed and can restart automatically on its own. Also,
> > more flexibility on the host machine itself.
>
> This depends on who maintains the setup. I dont volunteer to maintain
> a extra container layer. But if someone else does it and i never have
> to deal with it (and assuming baptiste has no objections) thats perfectly
> fine with me. But for example if you setup ssh (for the fate client
> connections) in a docker, apache / nginx in a docker, ...
> all this needs to get security updates.
>
> thx
>
> [...]
> --
> Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
>
> If a bugfix only changes things apparently unrelated to the bug with no
> further explanation, that is a good sign that the bugfix is wrong.
> _______________________________________________
> 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".