From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: kieran@kunhya.com, pal@palemieux.com
Subject: Re: [FFmpeg-devel] Too many project ideas in GSOC 2022 FFmpeg
Date: Wed, 23 Feb 2022 17:22:34 +0100
Message-ID: <20220223162234.GD2829255@pb2> (raw)
In-Reply-To: <20220221182415.GA2829255@pb2>
[-- Attachment #1.1: Type: text/plain, Size: 1767 bytes --]
On Mon, Feb 21, 2022 at 07:24:15PM +0100, Michael Niedermayer wrote:
> On Mon, Feb 21, 2022 at 08:59:16AM -0800, Pierre-Anthony Lemieux wrote:
> > Hi Michael,
> >
> > What is the typical size of a successful GSOC project? Any good
> > example(s) from the past?
>
> for past Results
> see: (and replace teh year by other years)
> https://trac.ffmpeg.org/wiki/SponsoringPrograms/GSoC/2020/Results
>
> but also keep in mind it makes a big difference if the student had
> previously outside gsoc contributed to FFmpeg
>
> also this year there are multiple changes in GSOC
> there will be 2 project sizes and more people will be eligible IIUC
Note to everyone, please add the project duration to your entry on trac
this year there are 2 sizes, so we should say something about that.
It may be possible to also leave that open for now, ive seen other
organizations do that. But we should say something for each project.
Ive also reorganized my 2 projects so there is now a long and a short
one
and about the checkasm project, i think its a really good idea and i
hope someone will mentor it.
But as long as noone mentors it it should be moved to a section
for projects without mentors
I took the liberty to CC the people who added the other entries, as
the time before google reviews this is unknown to me
PS: And we need backup mentors for all projects, google has been allergic
to projects which do not list a backup mentor
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Many that live deserve death. And some that die deserve life. Can you give
it to them? Then do not be too eager to deal out death in judgement. For
even the very wise cannot see all ends. -- Gandalf
[-- 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:[~2022-02-23 16:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-21 12:12 Michael Niedermayer
2022-02-21 16:59 ` Pierre-Anthony Lemieux
2022-02-21 18:24 ` Michael Niedermayer
2022-02-23 16:22 ` Michael Niedermayer [this message]
2022-02-23 17:07 ` Mark Gaiser
2022-03-01 7:46 ` Michael Koch
2022-03-01 8:09 ` Paul B Mahol
2022-03-01 17:49 ` Marvin Scholz
2022-03-02 11:46 ` Paul B Mahol
2022-03-01 15:17 ` Michael Niedermayer
2022-03-03 19:47 ` Paul B Mahol
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=20220223162234.GD2829255@pb2 \
--to=michael@niedermayer.cc \
--cc=ffmpeg-devel@ffmpeg.org \
--cc=kieran@kunhya.com \
--cc=pal@palemieux.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