Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] Fw: GSoC 2025: Please review your Project Ideas lists
Date: Sun, 16 Feb 2025 03:47:01 +0100
Message-ID: <20250216024701.GA4991@pb2> (raw)
In-Reply-To: <CADxeRwnV2YjK+9hkQ3xuV3ZnXFuvqbR5TRgVeu4fuoD=U8sskA@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1540 bytes --]

Hi Steven

On Sat, Feb 15, 2025 at 11:41:46PM +0800, Steven Liu wrote:
> Michael Niedermayer <michael@niedermayer.cc> 于2025年2月15日周六 23:14写道:
> >
> > Hi Steven
> >
> > On Sat, Feb 15, 2025 at 07:30:40AM +0800, Steven Liu wrote:
> > [...]
> > > That’s not whole WebRTC, just push streams to server, we can implement a
> > > tiny function, I know WebRTC is too huge and there have lots of algorithms
> > > geek want injection their selves algorithms, I think we should just
> > > implement a smaller WHIP is ok, let stream publish users have more choose,
> > > there should not only rtmp can push streams.
> > > Let try do that. Not need implement full and perfect functions, just can
> > > push streams by WHIP is ok.
> >
> > Also the long list of RFCs looks like the student would have to learn/understand
> > all of them.
> > If the tiny part the students project is about only needs a subset then its
> > better to list only what is needed.
> Hi Kieran and Michael,
> 
> Ok, Based on Michael and Kieran's suggestions, some changes have been
> made. Could you please review whether the current description is now
> concise enough?

Given that i dont know WHIP, and that iam not a native english speaker
I think there are many other people better suited on this mailing list
to review this text.

But to me it sounds fine

thx

-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

No great genius has ever existed without some touch of madness. -- Aristotle

[-- 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".

  reply	other threads:[~2025-02-16  2:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-14 19:28 Michael Niedermayer
2025-02-14 20:20 ` Kieran Kunhya via ffmpeg-devel
2025-02-14 20:30   ` Michael Niedermayer
2025-02-14 21:29   ` Steven Liu
2025-02-14 22:14     ` Kieran Kunhya via ffmpeg-devel
2025-02-14 23:30       ` Steven Liu
2025-02-15 15:06         ` Michael Niedermayer
2025-02-15 15:14         ` Michael Niedermayer
2025-02-15 15:41           ` Steven Liu
2025-02-16  2:47             ` Michael Niedermayer [this message]
2025-02-16 19:42 ` Soft Works
2025-02-17  0:25   ` Michael Niedermayer
2025-02-17  1:00     ` Soft Works
2025-02-17  2:36   ` [FFmpeg-devel] " Zhao Zhili
2025-02-17  3:31     ` Soft Works

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=20250216024701.GA4991@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