From: "Tomas Härdin" <git@haerdin.se>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [EXT] Re: Query from Reuters on XZ, open source, and Microsoft
Date: Mon, 08 Apr 2024 13:02:50 +0200
Message-ID: <205cfba2c3ebb88af0fa3c4017d9e6d4b7c4fb7d.camel@haerdin.se> (raw)
In-Reply-To: <PH0PR03MB5752CC4227A444518077631FE33D2@PH0PR03MB5752.namprd03.prod.outlook.com>
ons 2024-04-03 klockan 19:26 +0000 skrev Satter, Raphael (Reuters) via
ffmpeg-devel:
> * What’s the solution here? Your talk mentioned paying
> developers, getting an SLA, or hiring them as consultants … but why
> would companies bother when they can just free ride? I asked the same
> question to CISA’s Jack Cable when he told me that companies need to
> “contribute back and help build the sustainable open source ecosystem
> that we get so much value from.” Sure, they “need” to do it, but who
> will punish them if they don’t?
We could always start licensing the project under a less permissive
license like the GPL or the AGPL and then charge for exceptions. This
tactic goes by the name of license trolling, and was successfully used
by FFmbc for a while.
We also don't need to support every use case. I've been making the case
that we should be far more restrictive with what kind of input we
allow, especially for formats mainly used by professionals such as MXF.
Every feature carries with it a maintenance burden.
/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".
next prev parent reply other threads:[~2024-04-08 11:03 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-03 15:51 [FFmpeg-devel] " Satter, Raphael (Reuters) via ffmpeg-devel
2024-04-03 16:38 ` Kieran Kunhya via ffmpeg-devel
2024-04-03 16:42 ` [FFmpeg-devel] [EXT] " Satter, Raphael (Reuters) via ffmpeg-devel
2024-04-03 19:26 ` Satter, Raphael (Reuters) via ffmpeg-devel
2024-04-03 19:43 ` Kieran Kunhya via ffmpeg-devel
2024-04-08 11:02 ` Tomas Härdin [this message]
2024-04-08 14:40 ` Nicolas George
2024-04-08 17:56 ` Paul B Mahol
2024-04-09 19:08 ` Tomas Härdin
2024-04-17 19:05 ` [FFmpeg-devel] Mailinglist conduct (was: [EXT] Re: Query from Reuters on XZ, open source, and Microsoft) Ronald S. Bultje
2024-04-08 18:13 ` [FFmpeg-devel] Query from Reuters on XZ, open source, and Microsoft Romain Beauxis
2024-04-08 21:29 ` Vittorio Giovara
2024-04-09 3:09 ` Rémi Denis-Courmont
2024-04-09 8:36 ` Nicolas George
2024-04-10 9:27 ` Stefano Sabatini
2024-04-10 13:15 ` Gyan Doshi
2024-04-09 19:05 ` Tomas Härdin
2024-04-09 20:57 ` Romain Beauxis
2024-04-09 23:46 ` Paul B Mahol
2024-04-10 1:43 ` Romain Beauxis
2024-04-10 12:40 ` Ronald S. Bultje
2024-04-10 11:38 ` Tomas Härdin
2024-04-11 1:19 ` Michael Niedermayer
2024-04-11 3:59 ` Vittorio Giovara
2024-04-11 7:27 ` Paul B Mahol
2024-04-17 19:24 ` epirat07
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=205cfba2c3ebb88af0fa3c4017d9e6d4b7c4fb7d.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