On Mon, Nov 25, 2024 at 5:09 PM compn <f...@hawaiiantel.net> wrote:
> On Mon, 25 Nov 2024 17:01:47 -0500 > Vittorio Giovara <vittorio.giov...@gmail.com> wrote: > > > On Mon, Nov 25, 2024 at 4:52 PM compn <f...@hawaiiantel.net> wrote: > > > > > On Mon, 25 Nov 2024 14:27:13 -0500 > > > Vittorio Giovara <vittorio.giov...@gmail.com> wrote: > > > > > > > +* To represent FFmpeg in any product, conference, or tradeshow, you > must > > > > obtain > > > > > > you'll have to get the trademark owners agreement to publish any rules > > > of his trademark like this. > > > > > > if you want a community owned trademark, then start a thread about > > > coming up with a community trademark name. and what legal entity will > > > own said community trademark, which countries it will be registered in > , > > > etc. > > > > > > > Shouldn't the ones that have been using the logo at various trade shows > be > > seeking permission every time then? :thinking-emoji: > > > > The logo itself was made and picked by the community, so not sure what > > point you're trying to make. I mostly want to regulate and have a fair > > process for everybody, > > in your patch, are you talking about the logo or the trademarked ffmpeg > name? your patch didnt mention a logo. > You're right, those are two separate things that should be treated differently. I'll send an edit. Maybe the trademark is not enforceable but the logo violation is. >without having to request in-writing permission every time. > > didnt your patch specify must get in-writing permission every time on > the mailing list ? did i read it incorrectly? > I mean in-writing as in having a formal legal procedure (form submission etc) to the owner, vs sending a request email to the community. -- Vittorio _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
