Fedora Summer Coding community April 2010

summer-coding@lists.fedoraproject.org

10 participants
22 discussions

help with admin & organizing stuff
by Karsten Wade 05 Apr '10

05 Apr '10

Is anyone interested in helping with the administrivia aspects of Summer Coding 2010? I'd like a pool of people to put in as admin-control level for e.g.: * Mailing lists (esp. mentor list) - Includes confirming that requestors are actually former mentors or have passed discussion on 'summer-coding-discuss'. * Trac instance (fedorahosted.org/summer-coding) * Willing and able to ask for various Fedora Infrastructure needs Patrick, are you interested in keeping on with these similar duties as you did for GSoC? I didn't want to presume. :) Also, we need a sane way to pick _this_year's_ Admin team. Main duty is arbitration and final-decision on which proposals get funded, _if_ the mentors are unable to decide. (This is a granular task, it could be a decision about one proposal v. another, or the entire list.) Out tasks could fall out of that. In the past, Patrick and myself were doing that role. I feel I need to continue in that role this year (and I figure it's a failure on my part if we're unable to replace me easily for next year.) I nominate Heiko Rupp as a third Admin. Heiko has been filling that role since last summer, being involved in all the discussions and decisions. Not sure if Heiko wants that duty, but it also works out well that he's known in the JBoss.org community. Finally, as part of the messaging index we're working on, we need stuff for people who want to help organize Fedora Summer Coding 2010. Your ideas for that are appreciated: https://fedoraproject.org/wiki/Summer_Coding_2010_plan#Organizers - Karsten -- name: Karsten 'quaid' Wade, Sr. Community Gardener team: Red Hat Community Architecture uri: http://TheOpenSourceWay.org/wiki gpg: AD0E0C41

2 1

two new mailing lists
by Karsten Wade 03 Apr '10

03 Apr '10

We need a general discussion list where students and mentors can come and ask questions, discuss proposals, etc. I didn't want that to be this list, so we can continue to have a place for SIG business and not have it be noisy. This is based on my GSoC experience of how many students drop in to ask questions, etc., on the general discussion list. https://admin.fedoraproject.org/mailman/listinfo/summer-coding-discuss * Open subscription (confirm only) * Open archives * List membership visible to list members * Topics -- anything related to the current year's Summer Coding program https://admin.fedoraproject.org/mailman/listinfo/summer-coding-mentors * Closed subscription (confirm + approval) * Closed archives (subscribers only) * List membership visible only to admins (debatable idea!) * Topics -- anything that should be private: proposals, performance, financials, student/mentor problems, etc. Does that make sense? Join away, please. If you were a mentor previously or seriously plan on mentoring for this year, you are invited to the mentor list. I'll be sending a copy of this to the redhat-summer-mentors list as the last location where the most mentors were together. In that message I explain why a Fedora-specific list for discussion and mentors. Essentially, it is because student and mentor interaction for JBoss.org and Fedora Project are going to be very different during the actual running of the program, and we will create confusion for everyone if we have all the work happening on one list. Just as we ask students to interact directly with upstreams, any students working on JBoss.org needs to have their non-administrivia discussions happening there. - Karsten -- name: Karsten 'quaid' Wade, Sr. Community Gardener team: Red Hat Community Architecture uri: http://TheOpenSourceWay.org/wiki gpg: AD0E0C41

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

Fedora Summer Coding community April 2010