[FFmpeg-devel] [PATCH] [RFC] doc/community: Add a policy about using FFmpeg name in public events

Vittorio Giovara vittorio.giovara at gmail.com
Mon Nov 25 22:24:32 EET 2024


On Mon, Nov 25, 2024 at 2:32 PM Rémi Denis-Courmont <remi at remlab.net> wrote:

> Le maanantaina 25. marraskuuta 2024, 21.27.13 EET Vittorio Giovara a écrit
> :
> > ---
> > Here are some initial talking points, I wasn't sure where to put this so
> I
> > thought community.texi was ok, please let me know your thoughts.
> > Ideally we should have the GA vote on this when we reach consensus (or
> get
> > close to it).
> > Thanks
> > Vittorio
> >
> >  doc/community.texi | 33 +++++++++++++++++++++++++++++++++
> >  1 file changed, 33 insertions(+)
> >
> > diff --git a/doc/community.texi b/doc/community.texi
> > index 97a49f15ed..852db9a197 100644
> > --- a/doc/community.texi
> > +++ b/doc/community.texi
> > @@ -179,4 +179,37 @@ instead and point them in the right direction.
> >  Finally, keep in mind the immortal words of Bill and Ted,
> >  "Be excellent to each other."
> >
> > + at anchor{Brand}
> > + at chapter Brand
> > +
> > +FFmpeg is a legally protected trademark.
>
> Yes but
>
> > This means that it is not
> > possible to act on behalf of FFmpeg without explicit permission from the
> > community.
>
> The first does *not* "mean" the second since (perhaps unfortunately but
> nevertheless) the community does not control the trademark anywhere.
>
> I don't dislike the spirit but we should refrain from making factually
> wrong
> statements in the documentation IMO.
>

That's fair, should we reword the two statements more disconnected or do
you think we should just request that the process be followed?
I feel like without repercussions, people will just ignore this rule and do
what they want with the name (like as of now).
-- 
Vittorio


More information about the ffmpeg-devel mailing list