From: Michael Niedermayer <michael@niedermayer.cc>
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: Sun, 24 Sep 2023 15:46:13 +0200
Message-ID: <20230924134613.GI3543730@pb2> (raw)
In-Reply-To: <34c68bd0-54ae-e846-b954-28a8f592f8c5@passwd.hu>
[-- Attachment #1.1: Type: text/plain, Size: 1659 bytes --]
On Sun, Sep 24, 2023 at 02:36:20PM +0200, Marton Balint wrote:
>
>
> On Sun, 24 Sep 2023, Kyle Swanson wrote:
>
> > DNS
> > ---
> >
> > - Currently the DNS of ffmpeg.org is managed by Fabrice
> > - Michael was asked if he has control over the ffmpeg.org DNS register.
> > - Michael says he thinks he has some.
> > - Ronald would be curious to know what "some" means.
> > - Ronald proposes current project owners should have control over DNS and
> > trademark.
> > - Ronald: Fabrice is not active, DNS and trademark should be in the
> > control of project members.
> > - Michael: "i think fabrice should stay in ultimate control", "he has
> > always acted in the best interests of the people".
> > - Ronald took a poll in the room, most agreed current project developers
> > should have control of this.
>
> I think you should define what you are aiming for exactly. Having more
> people control the domain zone, [...]
currently all the root admins can update the zone file on the main
DNS server and it will then get pulled to the DNS slaves from there
I guess i have been the one updating it most of the time but the other
admins can too. I also think updates have always been done quickly
And its rare that something needs to be changed in it.
like if between https://fatebeta.ffmpeg.org/ and http://coverage.ffmpeg.org/
you want to setup a fategamma.ffmpeg.org ...
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety -- Benjamin Franklin
[-- 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:[~2023-09-24 13:46 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 [this message]
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
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=20230924134613.GI3543730@pb2 \
--to=michael@niedermayer.cc \
--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