-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
I'd like to propose a process, let's work through any ideas and fixes to it.
At this point mentors need to be communicating with students about their proposals via the Melange tool.
The goal is to help students get their proposals to be as good as possible. We are not accepting/denying any proposals at this point.
Mentors need to rank and finalize the list for slot requests by 13 April, so let's make the deadline for that 10 April. This will include accepting top proposals, ranking them in order of quality, as that will help determine how many student slots we get.
Mentors should be watching for how students communicate and respond around the proposals. This is an indication of how well they will fit in working in an open source project. Of course, there is always a lot to learn, and the mentors should be showing the students how to act in an open source project.
The mentors need to decide ourselves how we want to do the final ranking of proposals and request for student slots.
My thinking here is:
1. Mentors discuss on their private list about the ranking. 2. If we can't come to a clear consensus, then the admins (Jeff & I) can have 1:1 discussions with the mentors. 3. Then admins propose a final ranking to the mentors. 4. Discuss and come to consensus.
Lars has suggested that we start with step 2 to avoid conflict of interest in the ranking.
Any other ideas or thoughts there?
Thanks - Karsten - -- Karsten 'quaid' Wade .^\ CentOS Doer of Stuff http://TheOpenSourceWay.org \ http://community.redhat.com @quaid (identi.ca/twitter/IRC) \v' gpg: AD0E0C41
On Thu, Apr 02, 2015 at 09:21:57AM -0700, Karsten Wade wrote:
At this point mentors need to be communicating with students about their proposals via the Melange tool.
My mentor and I have been communicating over IRC, which has been working well for us. Should we also move some of these discussions over to the Melange tool?
The goal is to help students get their proposals to be as good as possible. We are not accepting/denying any proposals at this point.
Is the thought here that student will edit their proposals? If so, editing must be enabled for CentOS proposals in Melange. Currently it is not possible to amend them. If not, where should the amended versions live?
Cheers, Louis
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 04/02/2015 01:58 PM, Louis Taylor wrote:
On Thu, Apr 02, 2015 at 09:21:57AM -0700, Karsten Wade wrote:
At this point mentors need to be communicating with students about their proposals via the Melange tool.
My mentor and I have been communicating over IRC, which has been working well for us. Should we also move some of these discussions over to the Melange tool?
It would be good for your mentor (at least) to comment on your proposal in the Melange tool for the benefit of the other mentors helping to work on proposals. A summary of discussions so far would be good.
If you talk via IRC, it would be good to put a summary of that discussion in the proposal comments each time.
The goal is to help students get their proposals to be as good as possible. We are not accepting/denying any proposals at this point.
Is the thought here that student will edit their proposals? If so, editing must be enabled for CentOS proposals in Melange. Currently it is not possible to amend them. If not, where should the amended versions live?
Ah, yes, there is a switch "Editable post deadline" per proposal. Mentors should be able to change that to "YES" so that you can keep the proposal up-to-date. The change discussion in the comments would help to understand the changes made in the proposal when other mentors (or students) read the changes. (We want to share transparently not only what we're doing but why we're doing it, which is why discussions need to be transparent. I know you are doing IRC logs, but it would be good to have all the discussions at least be summarized in Melange for efficiency sake for all.)
Regards,
- - Karsten - -- Karsten 'quaid' Wade .^\ CentOS Doer of Stuff http://TheOpenSourceWay.org \ http://community.redhat.com @quaid (identi.ca/twitter/IRC) \v' gpg: AD0E0C41
Louis,
I'm unavailable tonight but I'll be online tomorrow night and will do the things Karsten mentions below.
Sent from my iPhone
On Apr 2, 2015, at 3:14 PM, Karsten Wade kwade@redhat.com wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 04/02/2015 01:58 PM, Louis Taylor wrote:
On Thu, Apr 02, 2015 at 09:21:57AM -0700, Karsten Wade wrote: At this point mentors need to be communicating with students about their proposals via the Melange tool.
My mentor and I have been communicating over IRC, which has been working well for us. Should we also move some of these discussions over to the Melange tool?
It would be good for your mentor (at least) to comment on your proposal in the Melange tool for the benefit of the other mentors helping to work on proposals. A summary of discussions so far would be good.
If you talk via IRC, it would be good to put a summary of that discussion in the proposal comments each time.
The goal is to help students get their proposals to be as good as possible. We are not accepting/denying any proposals at this point.
Is the thought here that student will edit their proposals? If so, editing must be enabled for CentOS proposals in Melange. Currently it is not possible to amend them. If not, where should the amended versions live?
Ah, yes, there is a switch "Editable post deadline" per proposal. Mentors should be able to change that to "YES" so that you can keep the proposal up-to-date. The change discussion in the comments would help to understand the changes made in the proposal when other mentors (or students) read the changes. (We want to share transparently not only what we're doing but why we're doing it, which is why discussions need to be transparent. I know you are doing IRC logs, but it would be good to have all the discussions at least be summarized in Melange for efficiency sake for all.)
Regards,
- 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)
iEYEARECAAYFAlUdsTwACgkQ2ZIOBq0ODEFmzgCdEhbOQHuR/Plcnp2xwlEf8MxI Vb4An3HplJgT3yqWfuShfsQIOfvYHwx7 =IiV3 -----END PGP SIGNATURE----- _______________________________________________ CentOS-gsoc mailing list CentOS-gsoc@centos.org http://lists.centos.org/mailman/listinfo/centos-gsoc
-
Corey Henderson -
Karsten Wade -
Louis Taylor