From Fedora Project Wiki

No edit summary
(Added outdated warning)
 
(46 intermediate revisions by 10 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.
{{Admon/warning|This page is outdated|For info about GSoC head over to the GSoC 2017 page: https://fedoraproject.org/wiki/GSOC_2017}}


== You are a student ==
== Purpose ==


=== Are you already working in the Fedora or JBoss communities? ===
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.


=== Do you have an idea you need a mentor for? ===
<!--
{{admon/note|Google has announced the projects for this year!| Announcements : [https://communityblog.fedoraproject.org/fedora-google-summer-of-code-2016/ Community Blog] and [https://summerofcode.withgoogle.com/organizations/5630777857409024/ GSoC website].}}
-->


=== Do you want to start from ideas mentors already have? ===
== What are we doing? ==


== You are a mentor ==
* We are on the [https://fedoraproject.org/wiki/GSOC_2017 GSoC 2017 program]. The list of projects, students and their mentors can be found at the [https://fedoraproject.org/wiki/Summer_coding_2017 GSoC 2017 Projects wiki]


=== Are you committed to working with all parties? ===
== 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 ==


== You are an upstream ==
=== Mailing List ===
 
=== Has a student brought a project idea to you? ===
 
=== Do you have one or more ideas you want exposed to students? ===
 
=== Are you committed to working with all parties? ===
 
<!--
== Schedule ==


* The project mailing list is the main discussion location for all students and mentors:
** [http://lists.fedoraproject.org/mailman/listinfo/summer-coding summer-coding@lists.fedoraproject.org]
* The mentors use one or either of these lists:
** [http://lists.fedoraproject.org/mailman/listinfo/summer-coding-mentors summer-coding-mentors@lists.fedoraproject.org]


* [09 Dec] - Schedule ready to work with and publicize
=== IRC ===
* [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?
-->


== Process ==
You can find SIG members regularly on IRC in:


# Organize a team to vet mentoring sub-projects - [[Selecting GSoC 2010 mentoring sub-projects]].
* irc://irc.freenode.net/#fedora-summer-coding
#* Mentors need to commit to working with students to develop the student's proposal.
*: Web access is available at: http://webchat.freenode.net/?channels=fedora-summer-coding
#* 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:
=== Meetings ===


http://admin.fedoraproject.org/mailman/listinfo/summer-coding
No meetings are currently set.


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


== FAQ ==
== Schedule ==


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.
[https://summerofcode.withgoogle.com/how-it-works/ GSoC 2016 Timeline]
== Past years ==
* [https://fedoraproject.org/wiki/GSOC_2016 Summer Coding 2016]
* [https://fedoraproject.org/wiki/GSOC_2015 Summer Coding 2015]
* [https://fedoraproject.org/wiki/GSOC_2014 Summer Coding 2014]
* [https://fedoraproject.org/wiki/GSOC_2013 Summer coding 2013]
* [[Summer coding 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]]


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'.
=== Past project ideas ===


Platform requirements and suggestions:
* [[Summer coding ideas for 2016]]
* [[Summer coding ideas for 2015]]
* [[Summer coding ideas for 2014]]
* [[Summer coding ideas for 2013]]
* [[Summer coding ideas for 2012]]
* [[Summer coding ideas for 2011]]
* [[Summer coding ideas for 2010]]
* [[Summer coding ideas for 2009]]
* [[Summer coding ideas for 2008]]


* Low Bandwidth
=== Past project participation ===
* 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.
* 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 2017]]
[[Category:Summer coding 2016]]
[[Category:Summer coding 2015]]
[[Category:Summer coding 2014]]
[[Category:Summer coding 2013]]
[[Category:Summer coding 2012]]
[[Category:Summer coding 2011]]
[[Category:Summer coding 2010]]
[[Category:Summer coding 2009]]
[[Category:Summer Coding SIG]]
[[Category:Summer Coding SIG]]

Latest revision as of 16:06, 6 February 2017

This page is outdated
For info about GSoC head over to the GSoC 2017 page: https://fedoraproject.org/wiki/GSOC_2017

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.


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:


Meetings

No meetings are currently set.

Agenda

Schedule

GSoC 2016 Timeline

Past years

Past project ideas

Past project participation

Retrieved from "https://fedoraproject.org/w/index.php?title=Summer_Coding_SIG&oldid=485572"