[CentOS-devel] Congratulations for selection in GSOC-2015

Thu Apr 2 16:00:04 UTC 2015
Karsten Wade <kwade at redhat.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 03/24/2015 05:42 AM, Lars Kurth wrote:
> Karsten,
> 
> what I really wanted to ask is how the CentOS community wants to 
> handle 7, assuming there are always too many GSoC applicants. All
> the other steps are understood.

Thanks, & just getting around to replying, sorry for the delay.

> What I did in the past was to organize 1-3 private meetings with 
> mentors to come up with a shortlist and figure out how many slots
> to allocate. The scoring mechanism is OK, but people tend to give
> their proposals often a higher score than they should and mentors
> have different expectations. Coming up with a shortlist (or ordered
> list of applicants) can be a bit of a chore for larger projects and
> there could be disagreements between mentors of course.

I don't really have any issues with that approach, it's different than
what I've done in the past. I haven't had too many issues with not
being able to sort out the priority order -- mentors are usually
honest when they are up-voting for personal desire v. because they
like/dislike other proposals.

> And from past experience I found that it is better to focus on the
> best students and the ones who engage with the mailing list very
> publicly straight from the beginning. Those who don't rarely tend
> to engage more during the program.

This is quite true.

Anyway, I'm glad we discussed this transparently here, but as it's
about GSoC process (v. technical discussion), I'm going to start a new
thread on centos-gsoc@ list to discuss our proposal finalizing process.

- - Karsten--
Karsten 'quaid' Wade        .^\          CentOS Doer of Stuff
http://TheOpenSourceWay.org    \  http://community.redhat.com
@quaid (identi.ca/twitter/IRC)  \v'             gpg: AD0E0C41
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iEYEARECAAYFAlUdZ4QACgkQ2ZIOBq0ODEFV+gCeIpjgxA98v0ZSNPrXcJcKJNtc
aXsAniJ9f54eaKoO4JUzVJ4/VvOhxRyE
=YWre
-----END PGP SIGNATURE-----