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>
Cc: Thilo Borgmann <thilo.borgmann@mail.de>,
	kieran@kunhya.com,
	"Reynaldo H. Verdejo Pinochet" <rverdejo@gmail.com>,
	Carl Eugen Hoyos <cehoyos@gmail.com>,
	pal@palemieux.com
Subject: [FFmpeg-devel] GSoC 2022 ideas page
Date: Sat, 26 Feb 2022 01:11:37 +0100
Message-ID: <20220226001137.GN2829255@pb2> (raw)


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

Hi all

CCing other admins and mentors on the page

Our ideas page is this year in exceptionally poor condition
I am not sure why this happened. I did actually intend to be just
backup admin for it this year. and that kind of worked last one.
But now today I get a warning from google about the page
And ive already started to clean it up a bit but if you have time
a 2nd pair of eyes surely is a good idea. Also if you are mentor this
year please check your entry.
And if you arent mentor, please ask yourself if maybe you want to
mentor, because we have relativly few ideas on the page compared to
previous years.
And we still need backup mentors!

The mail is below:

Hello GSoC 2022 Org Admin Applicants,

We are busy reviewing all the GSoC 2022 Org Apps and are finding a large
number of organizations that are missing information from their Ideas list.
Rather than individually emailing each org separately with issues I am
sending an email to all orgs that applied to ask you all to please look at
your ideas list and be sure you have done the following things:

1. Be sure to include whether the project is a 175 hour (medium sized) or
350 hour (large project). If it can be either please state that - per idea.
This is missing from about 25% of the org apps right now. Please use the
175 hour and 350 hour designations instead of full time, half time, large,
medium, or any other term.

2. Your Ideas Page URL should be accessible to all and not require login.
This is the same URL contributors will be using if your org is
selected. Test using Chrome Incognito or Firefox Private Browsing modes.

3. As we state in the Defining a Project Idea List
<https://google.github.io/gsocguides/mentor/defining-a-project-ideas-list>
section of the Mentor guide, please provide the following information for
each idea:

a) a project title/description

b) more detailed description of the project (2-5+ sentences)

c) expected outcomes

d) skills required/preferred

e) possible mentors

f) expected size of project (175 or 350 hour)

g) an easy, medium or hard difficulty rating of each project.

4. Some of you are still working on your ideas.  Adding and refining ideas
is fine, but we are reviewing them between now and Monday. We can only make
decisions based on what we see when we review your application. For
example, if you only have 2 ideas when we review your org app, your org
will be rejected.

If you want to be selected this year I strongly suggest you make sure your
Project Ideas list meets the above requirements ASAP.




-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

During times of universal deceit, telling the truth becomes a
revolutionary act. -- George Orwell

[-- 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:[~2022-02-26  0:11 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20220226001137.GN2829255@pb2 \
    --to=michael@niedermayer.cc \
    --cc=cehoyos@gmail.com \
    --cc=ffmpeg-devel@ffmpeg.org \
    --cc=kieran@kunhya.com \
    --cc=pal@palemieux.com \
    --cc=rverdejo@gmail.com \
    --cc=thilo.borgmann@mail.de \
    /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