Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Nicolas George <george@nsup.org>
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: Tue, 3 Oct 2023 20:41:21 +0200
Message-ID: <ZRxgUae2FOwT7IJr@phare.normalesup.org> (raw)
In-Reply-To: <CALbjRO+Mm=mFJG8cReYm+fnOcQbwkM0SKB3XEc1H13yFvodpEQ@mail.gmail.com>


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

Kyle Swanson (12023-09-24):
> 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.
> -   This will need a vote, Fabrice will need to be contacted.
> -   We would prefer to bring voting results to Fabrice, hopeful that
> Fabrice would be amicable to handover.

Hi.

For an impartial arbiter, NOT being involved in the project, not being
part of the current drama, is a significant plus.

But first, we must ask what we want: do we want an impartial arbiter,
somebody who is trusted to have the best interest of a certain
conception of the project in mind and who can step in in case of a
failure of project democracy? Or do we not want that, just direct
control over the DNS by the admins.

Impartial and benevolent arbiters are hard to come by. We are lucky that
we have somebody who can be considered impartial and benevolent by
definition. I think we would be mad not to rejoice of it.

It is worth remembering that, IIRC, if Fabrice was not the ultimate
arbiter for the name FFmpeg, then the fork from >10 years ago would not
have been a fork, it would have been a successful coup. And then, since
the same causes lead to the same results, it would have progressively
died like it did, just more slowly, because having the recognized name
does override removing features that users enjoy.

Since we are FFmpeg, not avconv, we are happy that the coup was thwarted
by Fabrice's authority. We should look with a lot of suspicion any
attempt to weaken this last line of defence. By the way, I think it is
worth re-reading the mail announcing the coup:
http://ffmpeg.org/pipermail/ffmpeg-devel/2011-January/106403.html
There is a name that sticks out with regard to the present discussion.


Another point. Fabrice chose to give us the code, he chose not to give
us the name but only to lend it. That is his choice. Both the code and
the name belong to him, to do as he will. As members of the Libre
Software movement, we should rejoice he gave the code. But the name is
something different entirely: code is about skill, names are about
emotions.

Even if he has not contributed for more than a decade, Fabrice still has
the reputation for being the author of FFmpeg and FFmpeg still has the
reputation for being one of Fabrice's projects, and unless I am
mistaken, the first F still means Fabrice.

So if Fabrice were to believe that what the projects would be becoming
reflects poorly on him, hurts his reputation, he is entirely within his
rights, moral and legal, to refuse to be associated with it any longer.
“Sorry guys, you've turned my code to shit, I'm taking the name back.”

(It also matches somewhat the way French copyright law: patrimonial can
be ceded, but moral rights cannot.)

So, if the General Assembly were to decide to try to get control over
the trademark and DNS, it would be entirely within its rights, but I
believe both the good of the project and Fabrice's own interest would
suggest he should refuse. And I firmly reserve the right to make that
point to him, privately.

Regards,

-- 
  Nicolas George

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 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".

      parent reply	other threads:[~2023-10-03 18:41 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
2023-10-02  9:55 ` Nicolas George
2023-10-03 18:41 ` Nicolas George [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=ZRxgUae2FOwT7IJr@phare.normalesup.org \
    --to=george@nsup.org \
    --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