Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Vittorio Giovara <vittorio.giovara@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: "Satter, Raphael \(Reuters\)" <Raphael.Satter@thomsonreuters.com>,
	Kieran Kunhya <kieran618@googlemail.com>
Subject: Re: [FFmpeg-devel] Query from Reuters on XZ, open source, and Microsoft
Date: Mon, 8 Apr 2024 17:29:56 -0400
Message-ID: <CABLWnS8b3Vpr54CqaNLTdiE6-msJdECEBd-yW3Co-FrwewRGoA@mail.gmail.com> (raw)
In-Reply-To: <CABWZ6OSwhmWsc5YUt38XeDo6=_-Vs2FdfL=-5zS_tfR-5qFWog@mail.gmail.com>

On Mon, Apr 8, 2024 at 2:14 PM Romain Beauxis <romain.beauxis@gmail.com>
wrote:

> I would like to offer a constructive feedback really not intended as
> trolling. I believe that supporting a more modern development workflow such
> as the GitHub PR or gitlab MR would go very long way in helping onboarding
> new developers.
>

Plus one(thousdand). While I don't think using MR or mailing list for
patches will immediately convince big tech corps to sponsor ffmpeg, it
would definitely help the developer community and make sure we don't lose
patchsets.

The other open source community that I am involved with, the OCaml
> compiler, moved to GitHub maybe 5/6 years ago and this has really done
> wonders bringing in new contributors. And, you know, this is a niche
> compiler that is also not getting much attention from AI/Machine Learning
> people.
>

Other open source projects are probably less plagued by patents.
-- 
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-request@ffmpeg.org with subject "unsubscribe".

  reply	other threads:[~2024-04-08 21:30 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-03 15:51 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
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 [this message]
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=CABLWnS8b3Vpr54CqaNLTdiE6-msJdECEBd-yW3Co-FrwewRGoA@mail.gmail.com \
    --to=vittorio.giovara@gmail.com \
    --cc=Raphael.Satter@thomsonreuters.com \
    --cc=ffmpeg-devel@ffmpeg.org \
    --cc=kieran618@googlemail.com \
    /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