[CentOS-gsocadmin] Sorting proposals

Mon Apr 6 15:47:54 UTC 2015
Karsten Wade <kwade at redhat.com>

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

I wanted to start a thread to provide new mentors with some insight in
to the sorting process and how that results in the number of student
slots that Google assigns us.

Admins have ultimate control over the sorting of proposals. We'll end
up coming to a combination of consensus and admin-decree about the
order of proposals.

What does it mean to order the proposals?

* We want the strongest seeming students and proposals toward the top
of the list.

* Strongest is going to be a combination of strength of the proposal
and work done so far, and how the student interaction is. We are
looking for two main things:
  1. Have they been quickly picking up on the open source way of doing
things? (Tip:  Some students are already experienced in open source,
don't hold this against them, but be aware so you aren't overly
influenced by their prowess.)
  2. Do they seem as if they can pick up on the open source way within
a combination of the 'getting to know the community'-period (27 April
- - 25 May) and the first few weeks of coding (25 May ff).
  - Are we thinking we might be able to get people across a line in
terms of understanding how-to? Consider for each student.

For our slot count, AIUI the Google team looks at our ranking & other
factors and assigns us Y slots that is X-($factor) where X == the
number of proposals that we accept as good to go and $factor is some
algorithm we don't know. So sorting is important, we may have 13 we
like but only get 9 slots (for example), so we want to be able to make
sure the top of our list are the best.

Other thoughts?

- - 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)

iEYEARECAAYFAlUiqqkACgkQ2ZIOBq0ODEElBwCePlnQwWSVXFVC3Frvtj73IE85
3cYAn0ZaC20i/yKFftzP4Y5FLqpuszJi
=Zk1b
-----END PGP SIGNATURE-----