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>
Subject: Re: [FFmpeg-devel] FFmpeg release 6.1 (SDR Plans)
Date: Thu, 21 Sep 2023 15:18:35 -0400
Message-ID: <CABLWnS99xLWMey4Ms_WTgAYR5zd2tZJDxtm75WQqZnC+YGBkwA@mail.gmail.com> (raw)
In-Reply-To: <ZQyT1q6/dlE3LmwF@phare.normalesup.org>

On Thu, Sep 21, 2023 at 3:05 PM Nicolas George <george@nsup.org> wrote:

> Vittorio Giovara (12023-09-21):
> > What about other developers' time for maintenance?
>
> Yes, what about it?
>
> How much time did YOU spend maintaining libavfilter or libavdevice?
> Zero.
>
> How much time will you spend maintaining SDR? Zero.
>
> What does it change for you and everybody who thinks like you? NOTHING.
>
> Michael wants to invest his time in a features that integrates
> beautifully in FFmpeg and that some users are glad to expect. That is a
> good thing.
>
> People who are not interested in it but have no practical arguments
> against it have absolutely no right to oppose or put so much roadblock
> it becomes discouraging just because they would like it better if
> Michael spent his time on things that they find useful rather than
> things that he finds fun.
>
> > And for users installing a library nowadays is a one liner, not really a
> > big deal
>
> Only if it is packaged by a distribution. I am guessing you are not
> volunteering to package it yourself, so you are again proposing to waste
> somebody else's time.
>

So this is an example of accusatory tone - discrediting the previous author
in order to make your arguments have more weight. It's a bad move and
easily spottable, you should argue with better elements at your disposal,
not by claiming that I don't package software or don't contribute to
libavfilter. Really, have you thought how many contributors have we lost
only because of the tone (and length) of your emails? You said you stopped
contributing patches because you don't like the development environment,
but maybe you should consider stopping sending emails too, just as a
friendly advice.

I will stop replying to any further baseless accusation, and going back on
topic, regardless who wrote what or how many users are requesting it, my
opinion on this release still stands: either a release with everything or a
release without the contentious piece of code, but not both. It's confusing
to the end users, and shows lack of direction of the project. End of
transmission.
-- 
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".

  parent reply	other threads:[~2023-09-21 19:18 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-10 22:14 [FFmpeg-devel] FFmpeg release 6.1 Michael Niedermayer
2023-04-10 22:16 ` James Almer
2023-04-11  8:46 ` Neal Gompa
2023-09-19 17:18 ` Niklas Haas
2023-09-19 19:16   ` Michael Niedermayer
2023-09-19 21:58     ` Lynne
2023-09-20  0:38       ` Neal Gompa
2023-09-20  2:24         ` Xiang, Haihao
2023-09-20 17:24       ` Michael Niedermayer
2023-09-20 17:43         ` Kieran Kunhya
2023-09-20 18:10           ` Michael Niedermayer
2023-09-20 22:47             ` Kieran Kunhya
2023-09-21  3:19               ` Jean-Baptiste Kempf
2023-09-21 12:51               ` Michael Niedermayer
2023-09-20 12:47     ` Niklas Haas
2023-09-20 18:00       ` Michael Niedermayer
2023-09-21 11:46     ` Dawid Kozinski/Multimedia (PLT) /SRPOL/Staff Engineer/Samsung Electronics
2023-09-21 16:21 ` [FFmpeg-devel] FFmpeg release 6.1 (SDR Plans) Michael Niedermayer
2023-09-21 16:33   ` Kieran Kunhya via ffmpeg-devel
2023-09-21 17:16     ` Nicolas George
2023-09-21 18:14       ` Vittorio Giovara
2023-09-21 18:19         ` Nicolas George
2023-09-21 18:47           ` Vittorio Giovara
2023-09-21 18:51             ` Nicolas George
2023-09-21 18:54               ` Vittorio Giovara
2023-09-21 19:04                 ` Nicolas George
2023-09-21 19:08                   ` Paul B Mahol
2023-09-26 18:14                     ` Nicolas George
2023-09-21 19:18                   ` Vittorio Giovara [this message]
2023-09-21 19:37                     ` Nicolas George
2023-09-21 19:44                       ` Paul B Mahol
2023-09-21 18:56     ` Michael Niedermayer
2023-09-26 19:59       ` Rémi Denis-Courmont
2023-09-21 16:39   ` Paul B Mahol
2023-09-22 13:55   ` Gijs Peskens
2023-09-22 16:32     ` Michael Niedermayer
2023-09-23  6:49       ` Neal Gompa
2023-09-23 10:55         ` Michael Niedermayer
2023-09-23 23:31           ` Neal Gompa
2023-09-24  9:12         ` Nicolas George
2023-09-24 11:56           ` Paul B Mahol
2023-09-24 12:17             ` Nicolas George
2023-09-24 17:33               ` Paul B Mahol
2023-09-24 17:45                 ` [FFmpeg-devel] libavdevice (was: FFmpeg release 6.1 (SDR Plans)) Nicolas George
2023-09-24 17:49                   ` Paul B Mahol
2023-09-24 17:54                     ` Nicolas George
2023-09-24 18:05                       ` Paul B Mahol
2023-09-24 18:09                         ` Nicolas George
2023-09-25 11:20                           ` Paul B Mahol
2023-09-26 18:12                             ` Nicolas George
2023-09-25  8:24                 ` [FFmpeg-devel] FFmpeg release 6.1 (SDR Plans) Kieran Kunhya
2023-09-26 20:17         ` Rémi Denis-Courmont

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=CABLWnS99xLWMey4Ms_WTgAYR5zd2tZJDxtm75WQqZnC+YGBkwA@mail.gmail.com \
    --to=vittorio.giovara@gmail.com \
    --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