Summer Coding SIG

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(interim save)
(41 intermediate revisions by 5 users not shown)
Line 1: Line 1:
'''Purpose:''' Oversee, define, and improve on the Fedora Project's work with students contributing as part of their classwork or summer internship.
+
'''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.
  
== Schedule ==
+
{{admon/note|Students need to get on the mailing list and write applications!|[http://lists.fedoraproject.org/mailman/listinfo/summer-coding Mailing list] and [https://www.google-melange.com/gsoc/homepage/google/gsoc2012 GSoC website].}}
  
 +
== What are we doing? ==
  
* [09 Dec] - Schedule ready to work with and publicize
+
* We are on the [[GSOC_2013|GSoC 2013 program]]
* [06 Dec] - Draft process proposal to summer-coding@lists.fedoraproject.org
+
* [16 Dec] - roll out publicity across Fedora Project, JBoss.org, and upstreams -- give people work to do for Dec.
+
* [30 Dec] - needed infra in place (wiki pages, etc.)
+
* [06 Jan] - first round of mentor ... commitment?
+
  
 +
== How can you help? ==
  
== Processs ==
+
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.
  
# Organize a team to vet mentoring sub-projects
+
== Communication ==
#* 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.
+
# 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
+
#* 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)
+
#* 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
+
  
 +
=== Mailing List ===
  
 +
* The project mailing list is the main discussion location for all students and mentors: http://lists.fedoraproject.org/mailman/listinfo/summer-coding
 +
* The mentors use one or either of these lists:
 +
** http://lists.fedoraproject.org/mailman/listinfo/summer-coding-mentors
 +
** https://groups.google.com/group/redhat-summer-mentors
  
== Groups participating ==
+
=== IRC ===
== Projects ==
+
 
== Community ==
+
You can find SIG members regularly on IRC in:
== Communication ==
+
 
 +
* irc://irc.freenode.net/#fedora-summer-coding
 +
*: Web access is available at: http://webchat.freenode.net/?channels=fedora-summer-coding
 +
*: ''Channel currently on hold until we sort out logistics in 24 March meeting.''
 +
 
 +
Joint work performed across teams, such as with JBoss.org, is discussed in:
 +
 
 +
* irc://irc.freenode.net/#redhat-summer
 +
*: Web access is available at: http://webchat.freenode.net/?channels=redhat-summer
 +
*: ''Existing channel being used for discussion until we sort out logistics in 24 March meeting.''
 +
 
 +
=== Meetings ===
 +
 
 +
No meetings are currently set.
 +
 
 +
==== Agenda ====
 +
 
 +
== Schedule ==
 +
 
 +
https://www.google-melange.com/gsoc/events/google/gsoc2012
  
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.
+
== Past years ==
  
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'.
+
* [[GSOC_2012]]
 +
* [[Summer coding 2011]]
 +
* [[Summer coding 2010]]
 +
* [[Summer coding 2009]]
 +
* [[Summer coding 2008]]
 +
* [[Summer of Code 2007]]
 +
* [[Summer of Code 2006]]
 +
* [[Summer of Code 2005]]
  
Platform requirements and suggestions:
+
=== Past project ideas ===
  
* Low Bandwidth
+
* [[Summer coding ideas for 2012]]
* Both Real Time and Stored communication
+
* [[Summer coding ideas for 2011]]
* English - we all assume the participants have some base level of english skills
+
* [[Summer coding ideas for 2010]]
* Free Software
+
* [[Summer coding ideas for 2009]]
* Source Code can be fixed by the students, increase a sense of ownership
+
* [[Summer coding ideas for 2008]]
* 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.
+
=== Past project participation ===
  
 +
* Google's [[Summer of Code]] participation
 +
* [http://www.redhat.com/about/careers/recruiting/ Internships]  from Red Hat
 +
* [http://wiki.laptop.org/go/Summer_of_Content_2007 OLPC Summer of Content]
 +
* [http://www.coss.fi/web/coss/developers/summercode COSS Summer Code] of Finland
  
 
[[Category:Summer coding]]
 
[[Category:Summer coding]]
 
[[Category:Summer Coding SIG]]
 
[[Category:Summer Coding SIG]]

Revision as of 03:27, 8 May 2013

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.

Note.png
Students need to get on the mailing list and write applications!
Mailing list and GSoC website.

Contents

What are we doing?

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

Mailing List

IRC

You can find SIG members regularly on IRC in:

Joint work performed across teams, such as with JBoss.org, is discussed in:

Meetings

No meetings are currently set.

Agenda

Schedule

https://www.google-melange.com/gsoc/events/google/gsoc2012

Past years

Past project ideas

Past project participation