Difference between revisions of "Summer Coding SIG"

Revision as of 21:17, 4 March 2010

Purpose: Oversee, define, and improve on the Fedora Project's work with students contributing as part of their classwork or summer internship, and do so in a way that provides a general framework re-deployable by other open source projects seeking to do the same.

If you are looking for the Google Summer of Code 2010 information ...
... look over here at GSoC 2010. This is a page for students, mentors, mentoring sub-projects, and upstream projects.

1 What are we doing?
2 How can you help?
3 Communication
4 Schedule

What are we doing?

We're working on the execution of summer coding initiatives within Fedora. Effectively, what we're trying to do is take the Google Summer of Code (GSoC) model and generalize and expand it to the notion of $FUNDING_SOURCE Summer of Code by providing sample implementations of alternative values of $FUNDING_SOURCE alongside our continued participation in GSoC.

How can you help?

Right now, join our #Communication channels and introduce yourself and what you're interested in - we're working together to define more formal roles for those who want to know their time investment beforehand. That discussion will be carried out on the list, and the more formal roles will be announced on the Fedora mailing lists and planet when they are ready.

Communication

The project mailing list is the main discussion location:

http://admin.fedoraproject.org/mailman/listinfo/summer-coding

Meetings are every week on Wednesday at 1500 UTC in irc://irc.freenode.net/#fedora-meeting.

Schedule

Date	Task	Owner	Notes
08 Mar ~1900 UTC	Mentoring org. applications open	Owner	Notes
12 Mar 2300 UTC	Mentoring org. appplication closed	Owner	Notes
29 Mar 1900 UTC	Student applications open	Owner	Notes
09 Apr 1900 UTC	Student applications closed	Owner	Notes

@@ Line 2: / Line 2: @@
 {{admon/note|If you are looking for the [[GSoC 2010|Google Summer of Code 2010]] information ...|... look over here at [[GSoC 2010]].  This is a page for students, mentors, mentoring sub-projects, and upstream projects.}}
+== What are we doing? ==
+We're working on the execution of [http://blog.melchua.com/2010/03/04/summer-of-code-swimchart-now-with-more-generic/ summer coding initiatives] within Fedora. Effectively, what we're trying to do is take the [http://socghop.appspot.com/ Google Summer of Code (GSoC)] model and generalize and expand it to the notion of $FUNDING_SOURCE Summer of Code by providing sample implementations of alternative values of $FUNDING_SOURCE alongside our continued participation in GSoC.
+== How can you help? ==
+Right now, join our [[#Communication]] channels and introduce yourself and what you're interested in - we're working together to define more formal roles for those who want to know their time investment beforehand. That discussion will be carried out on the list, and the more formal roles will be announced on the Fedora mailing lists and planet when they are ready.
+== Communication ==
+The project mailing list is the main discussion location:
+http://admin.fedoraproject.org/mailman/listinfo/summer-coding
+Meetings are every week on Wednesday at 1500 UTC in irc://irc.freenode.net/#fedora-meeting.
 == Schedule ==
@@ Line 39: / Line 56: @@
 * [06 Jan] - first round of mentor ... commitment?
 -->
-== Process ==
-# Organize a team to vet mentoring sub-projects - [[Selecting GSoC 2010 mentoring sub-projects]].
-#* Mentors need to commit to working with students to develop the student's proposal.
-#* Raw ideas around a use case are good to have to interest the students, but don't represent the end-point of the idea.
-#* All of this needs to be in a visible location, such as a wiki table with links to fuller use cases, etc. - [[Potential GSoC 2010 mentoring sub-projects]].
-# Mentoring sub-projects may include upstreams.
-#* Work with JBoss/Fedora sub-projects to identify, contact, and get commitment from the upstream in advance.
-# The team vets the raw use case ideas from sub-projects to ensure:
-#* They are doable in the project time allowed (bounding limit).
-#* Even if peripheral to project missions, they are not entirely oppositional to the communities involved.
-# The SIG defines and administers pre-qualifying coding/community tests to interested students - [[Student pre-quals for GSoC 2010]].
-#* In general, passing the test is a pre-requisite to being allowed to submit a proposal for an existing or new idea.
-#* People developing and running the test could be the same team or a new one.
-# By the time students are able to use Melange for proposals:
-#* Students should be pre-qualified.
-#* Their project ideas should be pre-discussed with the identified mentoring sub-project(s) - [[GSoC 2010 mentoring sub-projects]].
-#* At least one mentor should be ready to work with the project.
-# From that point, Melange and the private mentor list are used for final project choosing.
-#* Only projects really ready to go are approved by the committee to be voted on by mentors.
-#* Mentors work in an open discussion on the private list to sort the viability of projects in to an acceptance order.
-#** Work includes upstream, cross-stream; this keeps sub-project loyalties in check; focus on quality projects produce better results for your favorite project.
-#* Admins are the final arbiters of setting the order of proposals in Melange - [[GSoC 2010 SIG team#Admins]].
-== Groups participating ==
-== Projects ==
-== Community ==
-== Communication ==
-The project mailing list is the main discussion location:
-http://admin.fedoraproject.org/mailman/listinfo/summer-coding
-Meetings are every week on Wednesday at 1500 UTC in irc://irc.freenode.net/#fedora-meeting.
-== FAQ ==
-One thing we need to do is build up a bit of a community between all the participants. Since all our students and mentorees are working on widely different projects, there isn't alot of social common ground. Finding icebreakers and neutral conversation points will help create a better community between the mentors and the students. This will also encourage better cultural awareness from the students from different backgrounds.
-If we get the students on the platform right after they are accepted, it can be a great tool to help in the community bonding process. We could have an open space where other community members can join and 'meet the new students'.
-Platform requirements and suggestions:
-* Low Bandwidth
-* Both Real Time and Stored communication
-* English - we all assume the participants have some base level of english skills
-* Free Software
-* Source Code can be fixed by the students, increase a sense of ownership
-* Ice breakers and other catches to keep the conversation moving
-* Incentives to encourage usage at least once a week
-* Continue to be open after the summer so that students can check up on each other socially.
-We may also want to encourage integration with other social networking platforms. Remember, this is where all the cool kids hang out.
 [[Category:Summer coding]]
 [[Category:Summer Coding SIG]]

Search