Summer of Code Mentoring - Revision history

Rillian: /* Questionaire for 2015 */ Move answer to the correct question.

2015-02-20T06:42:41Z

Questionaire for 2015: Move answer to the correct question.

← Older revision		Revision as of 06:42, 20 February 2015
Line 192:		Line 192:

	=== Are you a new organization who has a Googler or other organization to vouch for you? If so, please list their name(s) here. ===		=== Are you a new organization who has a Googler or other organization to vouch for you? If so, please list their name(s) here. ===

			We are a well established organization and participated in GSoC in the past.

	=== Are you an established or larger organization who would like to vouch for a new organization applying this year? If so, please list their name(s) here. ===		=== Are you an established or larger organization who would like to vouch for a new organization applying this year? If so, please list their name(s) here. ===

	~~We are a well established organization and participated in GSoC in the past.~~

	=== Is there anything else we should know or you'd like to tell us that doesn't fit anywhere else on the application? ===		=== Is there anything else we should know or you'd like to tell us that doesn't fit anywhere else on the application? ===

Rillian: /* How many potential mentors do you have for this year's program? What criteria did you use to select them? */ stephenj has also volunteered to mentor.

2015-02-20T06:32:01Z

How many potential mentors do you have for this year's program? What criteria did you use to select them?: stephenj has also volunteered to mentor.

← Older revision		Revision as of 06:32, 20 February 2015
Line 157:		Line 157:
	=== How many potential mentors do you have for this year's program? What criteria did you use to select them? ===		=== How many potential mentors do you have for this year's program? What criteria did you use to select them? ===

	~~Two~~ mentors have volunteered.		Three mentors have volunteered.

	We selected our mentors from the 'core' developers and contributors within Xiph. Mentors were selected based on how well they know the code area they're volunteering to mentor, how long they've been part of Xiph, how well they interact with others (particularly in terms of building community around our projects).		We selected our mentors from the 'core' developers and contributors within Xiph. Mentors were selected based on how well they know the code area they're volunteering to mentor, how long they've been part of Xiph, how well they interact with others (particularly in terms of building community around our projects).

	The majority of the mentors we've selected are core developers on the various Xiph sub-projects that they've volunteered to mentor for. They have been contributing to the Xiph.Org Foundation for at least several years, and have shown a persistent interest both in the software we develop, and in helping to create a community around it. We have also made sure that each mentor has sufficient time available to adequately mentor their student(s).		The majority of the mentors we've selected are core developers on the various Xiph sub-projects that they've volunteered to mentor for. They have been contributing to the Xiph.Org Foundation for at least several years, and have shown a persistent interest both in the software we develop, and in helping to create a community around it. We have also made sure that each mentor has sufficient time available to adequately mentor their student(s).

	=== What is your plan for dealing with disappearing students? ===		=== What is your plan for dealing with disappearing students? ===

Rillian: /* Why is your organization applying to participate in Google Summer of Code 2015? What do you hope to gain by participating? */

2015-02-20T06:27:37Z

Why is your organization applying to participate in Google Summer of Code 2015? What do you hope to gain by participating?

← Older revision		Revision as of 06:27, 20 February 2015
Line 153:		Line 153:
	We believe that Xiph's mandate to develop multimedia standards and software is an important one, but as a small non-profit with no official staff we—of course—have limited resources. We hope that the results of GSoC will include the direct benefit of new software development, but also help grow the number of active participants in a long-term manner. Most of our core developers started as students, but have since moved on from their student days. Attracting and retaining students is essential to the health and sustainability of our project and is an important goal for all of us.		We believe that Xiph's mandate to develop multimedia standards and software is an important one, but as a small non-profit with no official staff we—of course—have limited resources. We hope that the results of GSoC will include the direct benefit of new software development, but also help grow the number of active participants in a long-term manner. Most of our core developers started as students, but have since moved on from their student days. Attracting and retaining students is essential to the health and sustainability of our project and is an important goal for all of us.

	The Icecast multimedia streaming project has recently regained development momentum, but we are looking to involve more people, especially students. This should help us sustain momentum and strengthen our team.		The Icecast multimedia streaming project has recently regained development momentum, but we are looking to involve more people, especially students. This should help us sustain momentum and strengthen our team. This focus will avoid the previous emphasis on codecs, which proved very challenging to most student participants.

	This focus will ~~avoiding~~ the previous emphasis on codecs, which proved very challenging to most student participants.


	=== How many potential mentors do you have for this year's program? What criteria did you use to select them? ===		=== How many potential mentors do you have for this year's program? What criteria did you use to select them? ===

Rillian: /* Questionaire for 2015 */ Move codec sentence to goals section

2015-02-20T06:27:06Z

Questionaire for 2015: Move codec sentence to goals section

← Older revision		Revision as of 06:27, 20 February 2015
Line 145:		Line 145:
	We participated in 2008 and 2009. Sadly at this time we're unable to locate a report about both years and must assume that both were unsuccessful.		We participated in 2008 and 2009. Sadly at this time we're unable to locate a report about both years and must assume that both were unsuccessful.

	We enjoyed our participation during past years. It provided needed external input, energizing our project and improving our connections to the rest of the open source community. We'd like to take the opportunity to reset and be part in this year's Summer of Code with a focus on Icecast~~. This focus will avoiding the previous emphasis on codecs, which proved very challenging to most student participants~~.		We enjoyed our participation during past years. It provided needed external input, energizing our project and improving our connections to the rest of the open source community. We'd like to take the opportunity to reset and be part in this year's Summer of Code with a focus on Icecast.

	=== Why is your organization applying to participate in Google Summer of Code 2015? What do you hope to gain by participating? ===		=== Why is your organization applying to participate in Google Summer of Code 2015? What do you hope to gain by participating? ===
Line 153:		Line 153:
	We believe that Xiph's mandate to develop multimedia standards and software is an important one, but as a small non-profit with no official staff we—of course—have limited resources. We hope that the results of GSoC will include the direct benefit of new software development, but also help grow the number of active participants in a long-term manner. Most of our core developers started as students, but have since moved on from their student days. Attracting and retaining students is essential to the health and sustainability of our project and is an important goal for all of us.		We believe that Xiph's mandate to develop multimedia standards and software is an important one, but as a small non-profit with no official staff we—of course—have limited resources. We hope that the results of GSoC will include the direct benefit of new software development, but also help grow the number of active participants in a long-term manner. Most of our core developers started as students, but have since moved on from their student days. Attracting and retaining students is essential to the health and sustainability of our project and is an important goal for all of us.

	The Icecast multimedia streaming project has recently regained development momentum, but we are looking to involve more people, especially students. This should help us sustain momentum and strengthen our team.		The Icecast multimedia streaming project has recently regained development momentum, but we are looking to involve more people, especially students. This should help us sustain momentum and strengthen our team.

			This focus will avoiding the previous emphasis on codecs, which proved very challenging to most student participants.


	=== How many potential mentors do you have for this year's program? What criteria did you use to select them? ===		=== How many potential mentors do you have for this year's program? What criteria did you use to select them? ===

Rillian: copy remaining answers from above

2015-02-20T06:22:54Z

copy remaining answers from above

← Older revision		Revision as of 06:22, 20 February 2015
Line 164:		Line 164:

	=== What is your plan for dealing with disappearing students? ===		=== What is your plan for dealing with disappearing students? ===

			Our first goal will be to provide necessary support from the community such that our students do not want to suddenly vanish. We want our students to become well integrated members of the community, with ongoing contributions. That said, we're well aware of the possibility of a student disappearing.

			We intend to be reasonably strict with requiring students to keep in touch - whilst we're quite happy for them to be absent for a while if they let us know in advance, we will intend to get at least twice-weekly updates from each student.

			The mentors will have primary responsibility for their students, but the admins are also going to ensure that the mentors are indeed keeping track of what their students are up to. We'll ask our students to provide means for us to get in touch beyond email, where possible - phone, etc - in case we need to get in touch urgently.

	=== What is your plan for dealing with disappearing mentors? ===		=== What is your plan for dealing with disappearing mentors? ===

			Our mentors are all people who are major contributors to the Xiph projects - and have generally been contributing for many years. So, we think it's pretty unlikely that a mentor will disappear. However, we do have more mentors available than we expect to eventually have students (based on past years), so we're well able to take up the slack if a mentor becomes unavailable for any reason.

			Our admins will ensure that the mentors are keeping up with the students appropriately, and should it be absolutely necessary, we will either find another appropriate mentor, or the admins will take over mentoring the students directly.

	=== What steps will you take to encourage students to interact with your project's community before and during the program? ===		=== What steps will you take to encourage students to interact with your project's community before and during the program? ===

			The Xiph.Org Founation conducts much of its development discussion and community-building on our IRC channels. We'll ask that the students be present there while they're working, where adequate network access makes that possible. We hope to make them feel that they're an important part of our community; that their contributions are really making a difference towards the goals of Xiph.

			We intend to be open to their contributions - whilst we're aware that initially their work may not be of a quality sufficient to go into our core codebase immediately, we'll give them write access to our repositories to work on a branch. We'll ask them to be open in discussing and designing their contributions on IRC and our mailing lists. Our application template welcomes them to come and ask us questions when they're trying to write up their application. We hope that some, or even all, of the students will continue to be part of the Xiph community after SoC concludes. For those students who have not previously contributed to open source software, we'll teach them about how important community building is for the ongoing health of such projects.

	=== What will you do to encourage your accepted students to stick with the project after Google Summer of Code concludes? ===		=== What will you do to encourage your accepted students to stick with the project after Google Summer of Code concludes? ===

			We hope that the mentoring process and the experiences they have as part of GSoC will make the students interested in remaining part of Xiph, continuing development on the software they've been working on, and perhaps nurturing their patches towards inclusion in an actual release.

			A very important part of GSoC is for us to make them active members of the community, in particular on the irc channels and the mailing lists. Past experience tells that once they have become part of that community, they will stick around for longer.

			We will encourage them not to consider this just "a summer job", but as being part of a real community — and doing something that is both interesting, and useful to the wider world.

	=== Are you a new organization who has a Googler or other organization to vouch for you? If so, please list their name(s) here. ===		=== Are you a new organization who has a Googler or other organization to vouch for you? If so, please list their name(s) here. ===

	=== Are you an established or larger organization who would like to vouch for a new organization applying this year? If so, please list their name(s) here. ===		=== Are you an established or larger organization who would like to vouch for a new organization applying this year? If so, please list their name(s) here. ===

			We are a well established organization and participated in GSoC in the past.

	=== Is there anything else we should know or you'd like to tell us that doesn't fit anywhere else on the application? ===		=== Is there anything else we should know or you'd like to tell us that doesn't fit anywhere else on the application? ===

Rillian: Answers so far, copied from above with some minor modifications.

2015-02-20T06:19:28Z

Answers so far, copied from above with some minor modifications.

@@ Line 130: / Line 130: @@
 === If you did not choose "veteran" in the checkbox, have you applied in the past? If so, for what year(s)? ===
 === If you chose "veteran" in the checkbox, please summarize your involvement in Google Summer of Code and the successes and challenges of your participation. Please also list your pass/fail rate for each year. ===
 === Why is your organization applying to participate in Google Summer of Code 2015? What do you hope to gain by participating? ===
 === How many potential mentors do you have for this year's program? What criteria did you use to select them? ===
 === What is your plan for dealing with disappearing students? ===

Rillian: Dump questionaire from the 2015 organization application

2015-02-20T06:17:49Z

Dump questionaire from the 2015 organization application

← Older revision		Revision as of 06:17, 20 February 2015
Line 124:		Line 124:
	* '''Thomas B. Rücker''' - IRC nick: ''tbr''		* '''Thomas B. Rücker''' - IRC nick: ''tbr''
	* '''NN''' - IRC nick:		* '''NN''' - IRC nick:


			== Questionaire for 2015 ==


			=== If you did not choose "veteran" in the checkbox, have you applied in the past? If so, for what year(s)? ===

			=== If you chose "veteran" in the checkbox, please summarize your involvement in Google Summer of Code and the successes and challenges of your participation. Please also list your pass/fail rate for each year. ===

			=== Why is your organization applying to participate in Google Summer of Code 2015? What do you hope to gain by participating? ===

			=== How many potential mentors do you have for this year's program? What criteria did you use to select them? ===

			=== What is your plan for dealing with disappearing students? ===

			=== What is your plan for dealing with disappearing mentors? ===

			=== What steps will you take to encourage students to interact with your project's community before and during the program? ===

			=== What will you do to encourage your accepted students to stick with the project after Google Summer of Code concludes? ===

			=== Are you a new organization who has a Googler or other organization to vouch for you? If so, please list their name(s) here. ===

			=== Are you an established or larger organization who would like to vouch for a new organization applying this year? If so, please list their name(s) here. ===

			=== Is there anything else we should know or you'd like to tell us that doesn't fit anywhere else on the application? ===

Dm8tbr: edited to cover 2008/2009 which apparently didn't go well.

2015-02-19T17:52:29Z

edited to cover 2008/2009 which apparently didn't go well.

← Older revision		Revision as of 17:52, 19 February 2015
Line 31:		Line 31:
	In 2007, we were given 2 project slots. One was an extension of the hardware decoder effort from last year. The other was helping to do R&D on Xiph's next-generation audio codec, Ghost. Both were marginally successful — the students reached the minimum goals set, but little more, and did not maintain contact with Xiph after the program.		In 2007, we were given 2 project slots. One was an extension of the hardware decoder effort from last year. The other was helping to do R&D on Xiph's next-generation audio codec, Ghost. Both were marginally successful — the students reached the minimum goals set, but little more, and did not maintain contact with Xiph after the program.

	We ~~enjoyed our participation over the last two years. It provided needed external input, energizing our project~~ and ~~improving our connections to the rest of the open source community~~. ~~We think~~ we'~~ve learnt~~ a ~~lot~~ about ~~how to mentor new and upcoming contributors,~~ and ~~how to best screen the applications we do receive~~.		We participated in 2008 and 2009. Sadly at this time we're unable to locate a report about both years and must assume that both were unsuccessful.

			We enjoyed our participation over the last years. It provided needed external input, energizing our project and improving our connections to the rest of the open source community. We'd like to take the opportunity, reset and be part in this years Summer of code with a focus on Icecast, also avoiding the previous emphasis on codecs, as it proved very challenging to most student participants.
	~~'''TODO: In 2008'''~~

	~~'''TODO: In 2009''~~'

	==== If your organization has not previously participated in Google Summer of Code, have you applied in the past? If so, for what year(s)? ====		==== If your organization has not previously participated in Google Summer of Code, have you applied in the past? If so, for what year(s)? ====

Dm8tbr: removed annodex mentions, this year there is main interest from Icecast within Xiph.org. reworked existing list to fit current FAQ, left a few blanks where we still need to decide things.

2015-01-18T14:50:45Z

removed annodex mentions, this year there is main interest from Icecast within Xiph.org. reworked existing list to fit current FAQ, left a few blanks where we still need to decide things.

Show changes

Saoshyant: /* Who will your mentors be? Please include Google Account information. */ removing myself from the mentor list

2009-08-26T10:24:50Z

Who will your mentors be? Please include Google Account information.: removing myself from the mentor list

← Older revision		Revision as of 10:24, 26 August 2009
Line 77:		Line 77:
	* '''Arek Korbik''': google account arkadini@gmail.com		* '''Arek Korbik''': google account arkadini@gmail.com
	* '''Michael Dale''': google account bigmammoth@gmail.com		* '''Michael Dale''': google account bigmammoth@gmail.com
	* '''Ivo Emanuel Gonçalves''': google account justivo@gmail.com

	==== What criteria did you use to select these individuals as mentors? Please be as specific as possible. ====		==== What criteria did you use to select these individuals as mentors? Please be as specific as possible. ====