Summer Coding SIG
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?
- Summer Coding 2010
- 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.
- For a 7-minute video explanation, see Summer Of Code Swimchart: Now With More Generic.
While our efforts began with the Google Summer of Code, we are now working with several other sponsoring organizations to maximize the opportunities for students to work on free and open source projects under our guidance.
Refer to the Summer Coding Sponsors page for more.
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.
- Complete Summer Coding 2010 plan so that we can ...
- Complete Summer Coding 2010.
- Communicate based on the plan.
- Define further tasks.
- Trac instance
The project mailing list is the main discussion location:
You can find SIG members regularly on IRC in:
- 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:
- 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 are every week on Wednesday at 1500 UTC in:
- Web access is available at: http://webchat.freenode.net/?channels=fedora-meeting
- Goal of measuring all content as defined in Summer Coding 2010 plan:
- Does it make sense for the target audience?
- Is it complete?
- Is it too much?
- What needs fixing?
- Make actions.
- Review of messaging content - Go/No Go for:
- Category:Summer Coding 2010 -- all pages
- List all actions that can be completed immediately following the meeting.
- Note other actions to input in Trac for project management.
- Directly after meeting, finish all changes to program pages.
- Launch messaging for all audiences via various methods described in Summer Coding 2010 plan how sections.
- Focus on participating schools:
- Bite off what we can chew and do it well.
- Likely to attract a few more schools this way.
- Stronger co-branding with the school, building communities of open source practitioners at each school v. one-offs spread all over.
- Schools can provide housing (& board), hack space, and on the ground mentoring as part of the stipend to students.
- Bring in corporate sponsors who do the following:
- Provide money for any efforts that occur within Fedora, or
- Provide money that focuses on a specific set of FOSS projects important to the sponsor (which must be in Fedora or able to be brought in by the student,) and
- Provide logistical support as part of a global volunteer team within the SIG - from t-shirts to payments.
- Students come from the participating schools and work on:
- Fedora Project efforts, or
- Other participating upstreams, such as where the school maintains its own upstream relationships, or
- JBoss.org upstreams, or
- Other upstream proposals running through our umbrella, requiring careful consideration by proposal committee.
- An important part of this is exposing the projects needs via something automagic, such as OpenHatch.org.
Currently open until we decide the scope of what we are doing for 2010.
- Pre-meeting discussion on email@example.com.
- 24 March Wed. 1500 UTC - #fedora-meeting.
- 24 March call for sub-projects and ideas.
- 27 March OpenHatch.org analysis to mailing list.
- 31 March call for sponsors?
- 31 March call for students/schools.