Projects/Summer of Code/2007/Participation - Revision history

Thiago: Google extended the deadline by two days

2007-03-21T05:54:08Z

Google extended the deadline by two days

Zander: /* Hints */ fix language

2007-03-15T12:04:21Z

‎Hints: fix language

Jstaniek: /* Subscribing as mentor */ URL fixed

2007-03-15T11:32:37Z

‎Subscribing as mentor: URL fixed

Thiago: Add section on how to subscribe as a mentor

2007-03-15T09:04:29Z

Add section on how to subscribe as a mentor

Thiago: Add links to submitting

2007-03-15T08:42:39Z

Add links to submitting

Thiago: Add link to the postgresql hints

2007-03-13T22:48:34Z

Add link to the postgresql hints

Rich: /* Mentoring */

2007-03-09T13:32:14Z

‎Mentoring

Thiago: Bump up talking about the code in question

2007-03-06T10:34:13Z

Bump up talking about the code in question

Thiago: Typo

2007-03-04T15:06:19Z

Typo

Jstaniek at 09:34, 26 February 2007

2007-02-26T09:34:28Z

@@ Line 13: / Line 13: @@
 * March 12: Mentoring organization application deadline
 * March 14: List of accepted mentoring organizations published on code.google.com;<br>'''student application period opens'''
-* March 24: '''Student application deadline'''
+* March 26: '''Student application deadline'''
 * ''Interim Period'': Mentoring organizations review and rank student proposals; where necessary, mentoring organizations may request further proposal detail from the student applicant
-* April 9: List of accepted student applications published on code.google.com
+* April 11: List of accepted student applications published on code.google.com
 * May 28: '''Students begin coding for their GSoC projects'''; Google begins issuing initial student payments

@@ Line 92: / Line 92: @@
 '''Keep it simple''': we don't need a 10-page essay on the project and on you (Google won't even let you submit a text that long). You just need to be concise and precise.
-'''Know what you are talking about''': the least we need is for students to submit ideas that cannot be accomplished realistically or ideas that aren't even remotely related to KDE. If your idea is unusual, be sure to explain why you have chosen KDE to be your mentoring organisation.
+'''Know what you are talking about''': the last thing we need is for students to submit ideas that cannot be accomplished realistically or ideas that aren't even remotely related to KDE. If your idea is unusual, be sure to explain why you have chosen KDE to be your mentoring organisation.
 '''Aim wide''': submit more than one proposal, to different areas of KDE. We also recommend submitting to more than one organisation too. This will increase your chances of being chosen.

@@ Line 126: / Line 126: @@
 :# Contact the maintainer of your project and let him know you're interested
 :# Log in to your [http://www.google.com/accounts Google Account]
-:# Subscribe via the [http://code.google.com/mentor_step1.html Google interface] (you will be required to accept the Terms of Service)
+:# Subscribe via the [http://code.google.com/soc/mentor_step1.html Google interface] (you will be required to accept the Terms of Service)
 :# When you get to the [http://code.google.com/soc/mentor.html Profile page], select KDE as (one of) your mentor organization(s).
 :# Bookmark the URL for the dashboard: http://code.google.com/soc/mentor_home.html

← Older revision		Revision as of 09:04, 15 March 2007
Line 119:		Line 119:

	Finally, know that we will never assign you to a project you do not want to work on. We will not assign you more projects than you can/want to take on either. And you will have a backup mentor, just in case something unforeseen takes place.		Finally, know that we will never assign you to a project you do not want to work on. We will not assign you more projects than you can/want to take on either. And you will have a backup mentor, just in case something unforeseen takes place.
		+
		+	=== Subscribing as mentor ===
		+
		+	To subscribe as mentor, you need to complete a few easy steps.
		+
		+	:# Contact the maintainer of your project and let him know you're interested
		+	:# Log in to your [http://www.google.com/accounts Google Account]
		+	:# Subscribe via the [http://code.google.com/mentor_step1.html Google interface] (you will be required to accept the Terms of Service)
		+	:# When you get to the [http://code.google.com/soc/mentor.html Profile page], select KDE as (one of) your mentor organization(s).
		+	:# Bookmark the URL for the dashboard: http://code.google.com/soc/mentor_home.html
		+
		+	(See [http://groups.google.com/group/google-summer-of-code-announce/web/guide-to-the-gsoc-web-app-for-mentors-and-organization-administrators the official Google page] on how to subscribe)

	== Instructions for module/application maintainers ==		== Instructions for module/application maintainers ==

@@ Line 57: / Line 57: @@
 === Recommended steps ===
-# Read the instructions for participating
+# Read the [http://groups.google.com/group/google-summer-of-code-announce/web/guide-to-the-gsoc-web-app-for-student-applicants instructions] for participating
 # Take a look at the [[Projects/Summer of Code/2007/Ideas|list of ideas]]
 # Come up with project that you're interested in
 # Write a first draft [[#Student proposal guidelines|proposal]] and get someone to review it for you
-# Submit it using the web interface (not available yet)
+# Submit it using the [http://code.google.com/soc/student_step1.html web interface]
 Coming up with an interesting idea is probably the most difficult part of all. It should be something interesting for KDE, for Open Source in general and the Linux/Unix desktop in particular and for you. And it also has to be something that you can realistically achieve in the time available to you.

← Older revision		Revision as of 22:48, 13 March 2007
Line 95:		Line 95:

	'''Aim wide''': submit more than one proposal, to different areas of KDE. We also recommend submitting to more than one organisation too. This will increase your chances of being chosen.		'''Aim wide''': submit more than one proposal, to different areas of KDE. We also recommend submitting to more than one organisation too. This will increase your chances of being chosen.
		+
		+	The PostgreSQL project has also released a [http://www.postgresql.org/developer/summerofcodeadvice.html list of hints] that you can take a look.

	== Instructions for mentors ==		== Instructions for mentors ==

← Older revision		Revision as of 13:32, 9 March 2007
Line 111:		Line 111:

	When subscribing yourself as a mentor, please make sure that your application or module maintainer is aware of that. Ask him/her to send the Summer of Code KDE Administrators an email confirming to know you. This is just a formality to make sure you are a real person we can trust -- the administrators cannot know all active developers by their Google account ID.		When subscribing yourself as a mentor, please make sure that your application or module maintainer is aware of that. Ask him/her to send the Summer of Code KDE Administrators an email confirming to know you. This is just a formality to make sure you are a real person we can trust -- the administrators cannot know all active developers by their Google account ID.
		+
		+	If you would like to get an idea of what is involved in being a good mentor, Federico Mena-Quintero has written some helpful information based on his experiences in previous years. His HOWTO has some useful suggestions for anyone planning to mentor this year, and is located at http://primates.ximian.com/~federico/docs/summer-of-code-mentoring-howto/index.html.

	You will be subscribed to a mailing list to discuss ideas. We will also require you to read the proposals as they come in and you will be allowed to vote on the proposals, according to rules we will publish later.		You will be subscribed to a mailing list to discuss ideas. We will also require you to read the proposals as they come in and you will be allowed to vote on the proposals, according to rules we will publish later.

@@ Line 76: / Line 76: @@
 * What exactly do you intend to do? What will '''not''' be done?
 * Why are you the right person for this task?
 * How many hours are you going to work on this a week? 10? 20? 30? 40? Do you have other commitments that we should know about?
 * Are you comfortable working independently under a supervisor or mentor who is several thousand miles away, not to mention 12 time zones away? How will you work with your mentor to track your work? Have you worked in this style before?
 * If your native language is not English, are you comfortable working closely with a supervisor whose native language is English? What is your native language, as that may help us find a mentor who has the same native language?
 * Where do you live, and can we assign a mentor who is local to you so you can meet in a coffee shop for lunch?
 After you have written your proposal, you should get it reviewed. Do not rely on the KDE mentors to do it for you via the web interface: they will only send back a proposal if they find it lacking. Instead, ask a colleague or a developer to do it for you.

@@ Line 112: / Line 112: @@
 When subscribing yourself as a mentor, please make sure that your application or module maintainer is aware of that. Ask him/her to send the Summer of Code KDE Administrators an email confirming to know you. This is just a formality to make sure you are a real person we can trust -- the administrators cannot know all active developers by their Google account ID.
-You will be subscribed to a mailing list to discuss ideas. We will also require you to read the proposals as they come in and uou will be allowed to vote on the proposals, according to rules we will publish later.
+You will be subscribed to a mailing list to discuss ideas. We will also require you to read the proposals as they come in and you will be allowed to vote on the proposals, according to rules we will publish later.
 Finally, know that we will never assign you to a project you do not want to work on. We will not assign you more projects than you can/want to take on either. And you will have a backup mentor, just in case something unforeseen takes place.

@@ Line 58: / Line 58: @@
 # Read the instructions for participating
-# Take a look at the [[Projects/SummerOfCode/Ideas2007|list of ideas]]
+# Take a look at the [[Projects/Summer of Code/2007/Ideas|list of ideas]]
 # Come up with project that you're interested in
 # Write a first draft [[#Student proposal guidelines|proposal]] and get someone to review it for you
@@ Line 99: / Line 99: @@
 === Ideas ===
-If you're a developer (KDE developer or not) and you wish to participate in Summer of Code, you can do it in two ways: the first and easiest is to make a proposal in the [[Projects/SummerOfCode/Ideas2007|ideas page]]. Take a look at what your KDE project needs or what you feel KDE 4 should have. Feel free to submit ideas even if you cannot elaborate too much on them.
+If you're a developer (KDE developer or not) and you wish to participate in Summer of Code, you can do it in two ways: the first and easiest is to make a proposal in the [[Projects/Summer of Code/2007/Ideas|ideas page]]. Take a look at what your KDE project needs or what you feel KDE 4 should have. Feel free to submit ideas even if you cannot elaborate too much on them.
-The second possibility is to be a mentor for a more specific idea. If you wish to do that, please read the [[#Instructions common to all participants|instructions common to all participants]] and the  [http://code.google.com/support/bin/topic.py?topic=10442 Summer of Code FAQ]. Also, please contact the maintainer for your application or module and get the go-ahead from him/her. Then edit the [[Projects/SummerOfCode/Ideas2007|ideas page]], adding your idea.
+The second possibility is to be a mentor for a more specific idea. If you wish to do that, please read the [[#Instructions common to all participants|instructions common to all participants]] and the  [http://code.google.com/support/bin/topic.py?topic=10442 Summer of Code FAQ]. Also, please contact the maintainer for your application or module and get the go-ahead from him/her. Then edit the [[Projects/Summer of Code/2007/Ideas|ideas page]], adding your idea.
 Your idea proposal should be a brief description of what the project is, what the desired goals would be, what the student should know and your email address for contact. Please note, though, that the students are not required to follow your idea to the letter, so regard your proposal as just a suggestion.