From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [RFC] GSoC 2025 SDR Cleanup
Date: Wed, 12 Feb 2025 13:56:45 +0100
Message-ID: <20250212125645.GN4991@pb2> (raw)
In-Reply-To: <838b42e0-d8d7-4a5f-9938-fd14c6aea5e0@frankplowman.com>
[-- Attachment #1.1: Type: text/plain, Size: 1838 bytes --]
Hi Frank
On Wed, Feb 12, 2025 at 08:20:43AM +0000, Frank Plowman wrote:
> On 12/02/2025 01:21, Michael Niedermayer wrote:
> > Hi all
> >
> > Ive added SDR to our GSoC 2025 page as there was just a single project
> > on that page and the page needs to be more complete yesterday
> >
> > If people are against this say this NOW do not wait until we have accepted
> > a student and then start some drama
> > It can be removed now easily but not once someone is working on it
> >
> > What is this project about ?
> > It is about YOU, the community, you disliked how libavradio is interfaced.
> > It bascially was just a demuxer/input device
> >
> > So this Project is about someone within GSoC re structuring libavradio
> > and interfacing with a demuxer/input device as was previously suggested.
> >
> > Please clearly list all requirements you have for this to get into git master
> >
>
> I don't think this is a good idea. Regardless of one's opinion
> regarding SDR, it is evidently a contentious project. It is unlikely
> that the collective community arrive at a unambiguous set of criteria
> for adoption before the project list goes live. As such, I think it is
> likely that SDR would continue to be the subject of critique if it were
> a GSoC project. Having a (potentially unsuspecting) student inserted
> right in the middle of this messy situation seems very unfair.
Yeah, i agree, i am thinking the same after sleeping over it.
It could be very bad for the student to be drawn into this
I will remove SDR from the page before accepted
organizations are announced, that way no student can start
working on it or even pick the task
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
You can kill me, but you cannot change the truth.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 251 bytes --]
_______________________________________________
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:[~2025-02-12 12:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-12 1:21 Michael Niedermayer
2025-02-12 1:23 ` Kieran Kunhya via ffmpeg-devel
2025-02-12 2:11 ` Michael Niedermayer
2025-02-12 2:17 ` Kieran Kunhya via ffmpeg-devel
2025-02-12 8:20 ` Frank Plowman
2025-02-12 12:56 ` Michael Niedermayer [this message]
2025-02-12 13:16 ` Nicolas George
2025-02-12 13:45 ` Michael Niedermayer
2025-02-12 16:38 ` Marth64
2025-02-12 10:58 ` Vittorio Giovara
2025-02-12 11:14 ` Tomas Härdin
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=20250212125645.GN4991@pb2 \
--to=michael@niedermayer.cc \
--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