From Fedora Project Wiki
(first merge of content from old GSoC 2010 plan page) |
(Good enough to start working with) |
||
| Line 5: | Line 5: | ||
== Publicity plan == | == Publicity plan == | ||
Generate and direct interest between Fedora and JBoss.org sub-projects, student contributors, their academic institutions, and sponsoring organizations. | |||
Goal: Sponsoring orgs fund/resource for students to work on code for Fedora and JBoss.org sub-projects. Sponsoring orgs can be corporations, universities, foundations, individuals, and so forth. | |||
There are different audiences we need to speak with: students; mentors; sub-projects; upstreams; sponsoring orgs; academia. | There are different audiences we need to speak with: students; mentors; sub-projects; upstreams; sponsoring orgs; academia. | ||
| Line 11: | Line 13: | ||
Each audience needs to understand slightly different parts of the effort. This publicity plan outlines what each audience needs to read. The actual publicity is put on the page [[Summer Coding 2010]]. | Each audience needs to understand slightly different parts of the effort. This publicity plan outlines what each audience needs to read. The actual publicity is put on the page [[Summer Coding 2010]]. | ||
Advertise pre-proposal | === All audiences === | ||
This section covers information that all audiences need to know. | |||
* Advertise pre-proposal timeline. | |||
* Advertise what we are doing and where to learn more. | |||
=== Students === | === Students === | ||
| Line 20: | Line 27: | ||
* We have lists of ideas you can look at | * We have lists of ideas you can look at | ||
** | ** Use cases so you can design your own solution, or | ||
** The best ideas are student generated | ** Fully scoped ideas. | ||
** But taking our ideas and working with them is also very successful | ** The best ideas are student generated. | ||
* We are experienced working with new contributors | ** But taking our ideas and working with them is also very successful. | ||
** Helping new people be successful | * We are experienced working with new contributors. | ||
** Many long time contributors are around | ** Helping new people be successful. | ||
** People who stay around and do good work are noticed; people get hired by e.g. Red Hat all the time from the communities, including 4 former GSoC students | ** Many long time contributors are around. | ||
** People who stay around and do good work are noticed; people get hired by e.g. Red Hat all the time from the communities, including 4 former GSoC students. | |||
* You can bring many, many different types of ideas to Fedora and they may fit. | * You can bring many, many different types of ideas to Fedora and they may fit. | ||
** Fedora may be a place to work through integrating ideas with other upstream projects with the assistance of Fedora experts helping with upstream communication. | ** Fedora may be a place to work through integrating ideas with other upstream projects with the assistance of Fedora experts helping with upstream communication. | ||
| Line 47: | Line 55: | ||
* Fliers at events leading up to the summer (LFNW, TLF) | * Fliers at events leading up to the summer (LFNW, TLF) | ||
* Word of mouth | * Word of mouth | ||
* Specific links: | |||
** [[Summer Coding 2010#You are a student]] | |||
** [[Summer Coding ideas for 2010]] | |||
=== Mentors === | === Mentors === | ||
| Line 68: | Line 78: | ||
==== How ==== | ==== How ==== | ||
* FWN | |||
* devel@lists | |||
* Fedora Planet | |||
* devel-announce@ | |||
* Specific links: | |||
** [[Summer Coding 2010#You are a mentor]] | |||
** [[Summer Coding ideas for 2010]] | |||
=== Sub-projects === | === Sub-projects === | ||
| Line 89: | Line 108: | ||
* (devel-)sub-project@ | * (devel-)sub-project@ | ||
* IRC | * IRC | ||
* devel-announce@ | |||
* opensource.com article derived from [[GSoC report 2009]] | * opensource.com article derived from [[GSoC report 2009]] | ||
* Specific links: | |||
** [[Summer Coding 2010#You are a sub-project]] | |||
** [[Summer Coding ideas for 2010]] | |||
=== Upstreams === | === Upstreams === | ||
| Line 99: | Line 122: | ||
==== What ==== | ==== What ==== | ||
* If you have a student with an idea | * If you have a student with an idea you can have the student propose the idea through Fedora or JBoss.org '''if''' your project is already integrated with Fedora/JBoss. | ||
* If you want your project part of Fedora/JBoss, a student working for Summer Coding may be able to do that. | * If you want your project part of Fedora/JBoss, a student working for Summer Coding may be able to do that. | ||
** However, you may need to be the main, long term contact with Fedora/JBoss if the student doesn't stay on as a maintainer. | ** However, you may need to be the main, long term contact with Fedora/JBoss if the student doesn't stay on as a maintainer. | ||
*** Another option is a handoff to another packager, | *** Another option is a handoff to another packager, as well as other options you should explore. | ||
==== How ==== | ==== How ==== | ||
| Line 110: | Line 133: | ||
* Word of mouth | * Word of mouth | ||
* opensource.com? | * opensource.com? | ||
* Specific links: | |||
** [[Summer Coding 2010#You are an upstream]] | |||
** [[Summer Coding ideas for 2010]] | |||
=== Campus Ambassadors === | === Campus Ambassadors === | ||
Campus Ambassadors should work to guide new interests through this process. They should work in both generating interest in Summer | Campus Ambassadors should work to guide new interests through this process. They should work in both generating interest in Fedora Summer Coding within the Fedora Community and also generating interest in Fedora within student contributors. | ||
Campus Ambassadors should then guide new contributors in helping them get set up with mentors and helping submit their Summer Coding proposal. | Campus Ambassadors should then guide new contributors in helping them get set up with mentors and helping submit their Summer Coding proposal. | ||
| Line 124: | Line 150: | ||
* This is right in your pocket, you can run with Summer Coding participation and make your school very successful. | * This is right in your pocket, you can run with Summer Coding participation and make your school very successful. | ||
* You can make more students successful by being an additional mentor for students through the process. | * You can make more students successful by being an additional mentor for students through the process. | ||
* Do you know someone at the university/college who wants to talk about partnering with Fedora Summer Coding? | |||
==== How ==== | ==== How ==== | ||
| Line 129: | Line 156: | ||
* Ambassadors mailing lists | * Ambassadors mailing lists | ||
* Fedora Planet | * Fedora Planet | ||
* Specific links: | |||
** [[Summer Coding 2010#You are a Campus Ambassador]] | |||
** [[Summer Coding ideas for 2010]] | |||
== Workflow plan == | == Workflow plan == | ||
# Mentors with ideas/problems | # Mentors with ideas/problems put them in the [[Summer Coding ideas for 2010]] | ||
# Mentors and sub-projects who want students from Summer Coding. | #* ''Potential goal of moving to OpenHatch.org.'' | ||
# | # Mentors and sub-projects who want students from Summer Coding help in publicity. | ||
#* Goal is to send students to individual sub-projects or mentors immediately | # Students may have pre-proposal discussion in #fedora-summer-coding or other IR channel. | ||
#* Goal is to send students to individual sub-projects or mentors immediately. | |||
# Mentor contacts student to conduct coding test. | # Mentor contacts student to conduct coding test. | ||
# Students take coding test; passing is a requirement to have proposal considered. | # Students take coding test; passing is a requirement to have proposal considered. | ||
# Mentors review proposals. | # Mentors review proposals. | ||
# Students iterate on proposals based on mentor input. | # Students iterate on proposals based on mentor input. | ||
# Mentors have discussions in private mentor list to reach consensus on | # Mentors have discussions in private mentor list to reach consensus on which proposals fit which sponsored slots. | ||
# Final proposal list order is made by mentors. | # Final proposal list order is made by mentors. | ||
#* Where mentors cannot reach consensus, admins make the decision. | |||
# Students whose proposals are accepted begin working with mentors. | # Students whose proposals are accepted begin working with mentors. | ||
# (Extrapolate out standard Summer Coding workflow from here.) | # (Extrapolate out standard Summer Coding workflow from here.) | ||
| Line 150: | Line 180: | ||
* Plan | * Plan | ||
* FAQ | |||
* How to for sub-projects | * How to for sub-projects | ||
* Admin help docs | * Admin help docs | ||
== Infrastructure needs == | == Infrastructure needs == | ||
* | * Private mentors list, year-specific: summer-coding-mentors-2010? | ||
* Public list for students, mentors, sub-projects, sponsoring orgs to interact: summer-coding-discuss? | |||
* Test servers (a lot)? - special needs for more? | |||
* | * | ||
[[Category:Summer Coding SIG]] | [[Category:Summer Coding SIG]] | ||
[[Category:Summer Coding 2010]] | [[Category:Summer Coding 2010]] | ||
Revision as of 06:20, 2 April 2010
This document is the plan for project administrators and mentors to understand how Summer Coding 2010 is working in the Fedora Project.
Publicity plan
Generate and direct interest between Fedora and JBoss.org sub-projects, student contributors, their academic institutions, and sponsoring organizations.
Goal: Sponsoring orgs fund/resource for students to work on code for Fedora and JBoss.org sub-projects. Sponsoring orgs can be corporations, universities, foundations, individuals, and so forth.
There are different audiences we need to speak with: students; mentors; sub-projects; upstreams; sponsoring orgs; academia.
Each audience needs to understand slightly different parts of the effort. This publicity plan outlines what each audience needs to read. The actual publicity is put on the page Summer Coding 2010.
All audiences
This section covers information that all audiences need to know.
- Advertise pre-proposal timeline.
- Advertise what we are doing and where to learn more.
Students
This section is about what we are telling students and how we are telling it.
What
- We have lists of ideas you can look at
- Use cases so you can design your own solution, or
- Fully scoped ideas.
- The best ideas are student generated.
- But taking our ideas and working with them is also very successful.
- We are experienced working with new contributors.
- Helping new people be successful.
- Many long time contributors are around.
- People who stay around and do good work are noticed; people get hired by e.g. Red Hat all the time from the communities, including 4 former GSoC students.
- You can bring many, many different types of ideas to Fedora and they may fit.
- Fedora may be a place to work through integrating ideas with other upstream projects with the assistance of Fedora experts helping with upstream communication.
- If you are involved in Fedora or JBoss.org already, your chances of success at having a winning proposal are much greater.
- Here is the timeline on working with JBoss.org/Fedora, including the pre-proposal time period.
How
- Campus Ambassadors
- users@lists, devel@lists,
- Point at Summer Coding 2010
- IRC, #fedora-devel, #fedora-* (any channels relevant in particular?)(#fedora-campusamb)
- Campus LUGs
- Campus JUGs
- Fedora main page during the application window
- Fedora banners on rotation during the application window
- Fedora Planet
- JBoss.org front page
- JBoss.org blogs
- Fliers at events leading up to the summer (LFNW, TLF)
- Word of mouth
- Specific links:
Mentors
This section is about what we are telling mentors and how we are telling it.
Mentors are the people who interact directly with the students, making evaluatations, and being responsible for helping with communication between the student and other parts of the project.
What
- Get your ideas out in front of students soonest.
- You may be able to find a student who works as a sort-of intern who an implement a solution to an use case you have
- It is harder to find success where you are completely certain of how an idea needs to be implemented; finding a student with the skills and interest to implement a specific solution is a lot harder than finding a student with enough skills to respond to a use case need.
- You are an essential part of the student's success, the project's success, and the success for your overall organization (Fedora, JBoss.org, or another).
- You may be an interface for an identified sub-project or SIG in Fedora or JBoss.org.
- You help students communicate with the overall project and any upstreams.
- You are the final, accountable person for deciding if the student is successful or not, which affects payment.
- There is a timeline for working with Fedora/JBoss.
- There is a pre-proposal time that you should be involved with..
How
- FWN
- devel@lists
- Fedora Planet
- devel-announce@
- Specific links:
Sub-projects
This section is about what we are telling sub-projects and how we are telling it.
Sub-projects are the parts of Fedora and JBoss.org such as: packaging, infrastructure, Hibernate.
What
- You can gain a lot of value from students working via GSoC in your sub-project area; take a look at GSoC report 2009 for details.
- Your sub-project may need to identify a single mentor to work with the student, if the mentor doesn't come from somewhere else in Fedora/JBoss.
- If you have ideas/problems you want students to work on, they are best served to the students as use cases
- Student projects have a higher success rate for all involved when more of the initial idea is from the student.
How
- Fedora Planet
- FWN
- devel@
- (devel-)sub-project@
- IRC
- devel-announce@
- opensource.com article derived from GSoC report 2009
- Specific links:
Upstreams
This section is about what we are telling upstreams and how we are telling it.
Upstreams are any project where the code/content output is integrated in the Fedora Project or JBoss.org. Student projects may draw upon or contribute to your code, through Fedora or JBoss.org.
What
- If you have a student with an idea you can have the student propose the idea through Fedora or JBoss.org if your project is already integrated with Fedora/JBoss.
- If you want your project part of Fedora/JBoss, a student working for Summer Coding may be able to do that.
- However, you may need to be the main, long term contact with Fedora/JBoss if the student doesn't stay on as a maintainer.
- Another option is a handoff to another packager, as well as other options you should explore.
- However, you may need to be the main, long term contact with Fedora/JBoss if the student doesn't stay on as a maintainer.
How
- Via packagers
- Fedora Planet
- Word of mouth
- opensource.com?
- Specific links:
Campus Ambassadors
Campus Ambassadors should work to guide new interests through this process. They should work in both generating interest in Fedora Summer Coding within the Fedora Community and also generating interest in Fedora within student contributors.
Campus Ambassadors should then guide new contributors in helping them get set up with mentors and helping submit their Summer Coding proposal.
What
- Students can have a quality intern-like experience working with Fedora/JBoss.org.
- Money! Code! Fame! Success! Community!
- Sub-projects in JBoss.org and Fedora are ready to work with students.
- This is right in your pocket, you can run with Summer Coding participation and make your school very successful.
- You can make more students successful by being an additional mentor for students through the process.
- Do you know someone at the university/college who wants to talk about partnering with Fedora Summer Coding?
How
- Ambassadors mailing lists
- Fedora Planet
- Specific links:
Workflow plan
- Mentors with ideas/problems put them in the Summer Coding ideas for 2010
- Potential goal of moving to OpenHatch.org.
- Mentors and sub-projects who want students from Summer Coding help in publicity.
- Students may have pre-proposal discussion in #fedora-summer-coding or other IR channel.
- Goal is to send students to individual sub-projects or mentors immediately.
- Mentor contacts student to conduct coding test.
- Students take coding test; passing is a requirement to have proposal considered.
- Mentors review proposals.
- Students iterate on proposals based on mentor input.
- Mentors have discussions in private mentor list to reach consensus on which proposals fit which sponsored slots.
- Final proposal list order is made by mentors.
- Where mentors cannot reach consensus, admins make the decision.
- Students whose proposals are accepted begin working with mentors.
- (Extrapolate out standard Summer Coding workflow from here.)
Documentation needs
- Plan
- FAQ
- How to for sub-projects
- Admin help docs
Infrastructure needs
- Private mentors list, year-specific: summer-coding-mentors-2010?
- Public list for students, mentors, sub-projects, sponsoring orgs to interact: summer-coding-discuss?
- Test servers (a lot)? - special needs for more?