From: Michael Niedermayer <michael@niedermayer.cc> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Cc: Baptiste Coudurier <baptiste.coudurier@gmail.com>, Timothy Gu <timothygu99@gmail.com> Subject: Re: [FFmpeg-devel] [RFC] fateserver Date: Sun, 25 Feb 2024 20:28:01 +0100 Message-ID: <20240225192801.GP6420@pb2> (raw) In-Reply-To: <CA+28BfCwns9h_cR1i+roGQf212Kcy9v2Pe_uXC+nNe6Pg9fq4A@mail.gmail.com> [-- 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".
next prev parent reply other threads:[~2024-02-25 19:28 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-24 17:49 Michael Niedermayer 2024-02-25 6:36 ` Marth64 2024-02-25 19:28 ` Michael Niedermayer [this message] 2024-02-26 0:21 ` Marth64 2024-02-26 2:57 ` Michael Niedermayer 2024-02-26 14:29 ` Michael Niedermayer 2024-03-08 1:08 ` Marth64
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=20240225192801.GP6420@pb2 \ --to=michael@niedermayer.cc \ --cc=baptiste.coudurier@gmail.com \ --cc=ffmpeg-devel@ffmpeg.org \ --cc=timothygu99@gmail.com \ /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