Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "Tomas Härdin" <git@haerdin.se>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] VDD 2023, FFmpeg meeting notes, (23-11-2023, 4pm, Dublin)
Date: Wed, 27 Sep 2023 15:15:12 +0200
Message-ID: <2a9fe351c887133eabe541a3347dbd40c5d40ad8.camel@haerdin.se> (raw)
In-Reply-To: <CALbjRO+Mm=mFJG8cReYm+fnOcQbwkM0SKB3XEc1H13yFvodpEQ@mail.gmail.com>

sön 2023-09-24 klockan 09:37 +0100 skrev Kyle Swanson:
> Gitlab (or something like Gitlab)
> ---------------------------------
> -   J-B recommends against gitea, suggesting that we piggyback on the
> videolan Gitlab experience infra.

As someone who's tried to maintain a Gitlab instance I can also
recommend letting someone else do that. It might also be worthwhile
finding something that isn't as huge of a mess as Gitlab is, but I'm
not sure what's out there that's less of a pain.

> 
> DNS
> ---
> -   Michael: "i think fabrice should stay in ultimate control", "he
> has
> always acted in the best interests of the people".

A bus factor of 1 will sooner or later cause problems. At the very
least there needs to be some kind of plan in place to hand the domain
over if Fabrice disappears for one reason or another, lest it fall into
the hands of domain squatters.

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

  parent reply	other threads:[~2023-09-27 13:15 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-24  8:37 Kyle Swanson
2023-09-24  9:21 ` Matthias Dressel
2023-09-24 10:09 ` Michael Niedermayer
2023-09-24 10:13   ` Jean-Baptiste Kempf
2023-09-24 22:14     ` Derek Buitenhuis
2023-09-24 15:31   ` Ronald S. Bultje
2023-09-24 17:12   ` Nicolas George
2023-09-27 18:03   ` Michael Niedermayer
2023-10-04 14:51     ` Anton Khirnov
2023-09-24 12:36 ` Marton Balint
2023-09-24 13:46   ` Michael Niedermayer
2023-09-24 15:10   ` Ronald S. Bultje
2023-09-24 16:45     ` Michael Niedermayer
     [not found]       ` <119D9DAB-2F0B-427B-A7D1-063C0AF7C3BD@cosmin.at>
2023-09-25 13:16         ` Cosmin Stejerean via ffmpeg-devel
2023-09-26 13:21       ` Ronald S. Bultje
2023-09-27 10:00         ` Michael Niedermayer
2023-09-27 13:29           ` Vittorio Giovara
2023-10-03 18:50             ` Nicolas George
2023-10-03 19:13               ` Vittorio Giovara
2023-10-03 19:29               ` Kieran Kunhya via ffmpeg-devel
2023-10-04 14:23                 ` Michael Niedermayer
2023-10-04 15:06                   ` Anton Khirnov
2023-10-05 12:55                     ` Nicolas George
2023-10-05 17:32                       ` Vittorio Giovara
2023-10-05 18:33                         ` Michael Niedermayer
2023-10-05 19:45                           ` Rémi Denis-Courmont
2023-10-05 19:54                             ` Nicolas George
2023-10-05 19:00                         ` Nicolas George
2023-10-04 15:11                   ` Rémi Denis-Courmont
2023-10-03 19:29               ` Rémi Denis-Courmont
2023-10-03 19:36               ` Leo Izen
2023-09-26 19:26       ` Anton Khirnov
2023-09-26 18:44 ` Anton Khirnov
2023-09-27 13:15 ` Tomas Härdin [this message]
2023-10-02  9:55 ` Nicolas George
2023-10-03 18:41 ` Nicolas George

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=2a9fe351c887133eabe541a3347dbd40c5d40ad8.camel@haerdin.se \
    --to=git@haerdin.se \
    --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