From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: [FFmpeg-devel] [RFC] GSoC 2025 SDR Cleanup
Date: Wed, 12 Feb 2025 02:21:09 +0100
Message-ID: <20250212012109.GL4991@pb2> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 896 bytes --]
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
thx
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
I am the wisest man alive, for I know one thing, and that is that I know
nothing. -- Socrates
[-- 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 reply other threads:[~2025-02-12 1:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-12 1:21 Michael Niedermayer [this message]
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
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=20250212012109.GL4991@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