Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Marth64 <marth64@proxyid.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [RFC] fateserver
Date: Thu, 7 Mar 2024 19:08:20 -0600
Message-ID: <CA+28BfDchBqZex+hz7Zis8VdkDD+ezK4fgJuSNYrRA4iMmKVvw@mail.gmail.com> (raw)
In-Reply-To: <20240226142951.GS6420@pb2>

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

      reply	other threads:[~2024-03-08  1:08 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
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 [this message]

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=CA+28BfDchBqZex+hz7Zis8VdkDD+ezK4fgJuSNYrRA4iMmKVvw@mail.gmail.com \
    --to=marth64@proxyid.net \
    --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