Google Summer of Code/Application 2008 - Revision history

Popcorndude at 19:50, 12 April 2021

2021-04-12T19:50:08Z

Francis Tyers: Google Summer of Code/Application, 2008 moved to Google Summer of Code/Application 2008

2009-03-12T16:54:03Z

Google Summer of Code/Application, 2008 moved to Google Summer of Code/Application 2008

Francis Tyers: Protected "Google Summer of Code/Application, 2008" [edit=sysop:move=sysop]

2008-03-17T21:48:14Z

Protected "Google Summer of Code/Application, 2008" [edit=sysop:move=sysop]

Francis Tyers at 21:48, 17 March 2008

2008-03-17T21:48:08Z

Francis Tyers: Google Summer of Code moved to Google Summer of Code/Application, 2008

2008-03-10T12:18:31Z

Google Summer of Code moved to Google Summer of Code/Application, 2008

Francis Tyers: Google Summer of Code/Application, 2008 moved to Google Summer of Code

2008-03-10T12:17:31Z

Google Summer of Code/Application, 2008 moved to Google Summer of Code

Francis Tyers: Google Summer of Code moved to Google Summer of Code/Application, 2008

2008-03-10T11:03:50Z

Google Summer of Code moved to Google Summer of Code/Application, 2008

172.16.242.161 at 10:06, 10 March 2008

2008-03-10T10:06:14Z

172.16.242.161 at 09:59, 10 March 2008

2008-03-10T09:59:43Z

Francis Tyers: /* Application */

2008-03-09T16:09:48Z

Application

← Older revision		Revision as of 19:50, 12 April 2021
Line 109:		Line 109:
	* Whenever there is a relevant research or development component in their work, we will make sure they can use it as part of their undergraduate or graduate work, and offer guidance when writing papers.		* Whenever there is a relevant research or development component in their work, we will make sure they can use it as part of their undergraduate or graduate work, and offer guidance when writing papers.

	[[Category:Google Summer of Code]]		[[Category:Google Summer of Code\|Application 2008]]

@@ Line 1: / Line 1: @@
+<div style="align: center; border-collapse: collapse; background: #fbfbfb; border: 1px solid #aaa; border-left: 10px solid #1e90ff;">
+&nbsp;&nbsp;This application is closed.
+</div>
 Notes for applicants here: [http://groups.google.com/group/google-summer-of-code-announce/web/notes-on-organization-selection-criteria selection criteria], and [http://code.google.com/p/google-summer-of-code/wiki/AdviceforMentors advice for mentors]

@@ Line 47: / Line 47: @@
 ;Does your organization have an application template you would like to see students use? If so, please provide it now.
+* We expect students to contact us using IRC or e-mail; we will make sure we get the following information from all applicants:
-* We are preparing one, along these lines:
-:* What's your name and e-mail address?
+:* Name and e-mail address
+:* Current field of study / major
-:* What is your current education?
-:* Have you programmed before in an open-source project?
+:* Whether they have programmed before in an open-source project
-:* Why is it that you are interested in machine translation?
+:* Why is it that they are interested in machine translation
-:* Why is it that you are interested in the apertium project?
+:* Why is it that they are interested in the Apertium project
-:* Which task are you interested in, and why?
+:* Which task they are interested in, and why
 ;Who will be your backup organization administrator? Please include Google Account information.

@@ Line 15: / Line 15: @@
 * Both organizations are very interested in seeing Apertium improve in many different directions. The Universitat, mainly because most of its research in the field of machine translation is based on Apertium components. Prompsit, because it bases its business in providing Apertium-based services.
+* Apertium as a whole will benefit from increased participation from outside the core group of developers: we will get new or improved tools which will help to improve translation quality for users and developers alike.
-* ''[Write something more about how it will gain Apertium as well...]''
 ;Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation.

@@ Line 87: / Line 87: @@
 ;What is your plan for dealing with disappearing students?
-Students will be encouraged to let us know how they want to break up their time, and to try and plan for holidays and absences. This will avoid mentors wasting time. If a mentor reports the unscheduled disappearance of a student (72-hour silence), he will be contacted by the administrators. If silence persists, his task will be frozen and we will report to Google.
+Students will be encouraged to let us know how they want to break up their time, and to try and plan for holidays and absences. This will avoid both mentors and students wasting time. If a mentor reports the unscheduled disappearance of a student (72-hour silence), he will be contacted by the administrators. If silence persists, his task will be frozen and we will report to Google.
 ;What is your plan for dealing with disappearing mentors?
@@ Line 93: / Line 93: @@
 It is quite unlikely, since all of the mentors are very active developers, with long term commitment to the project. We originally had "call the police" here, but a more down to earth strategy would be the following:
 If a mentor fails to respond adequately to a student, he or she will have been instructed to contact the administrators. The administrators will examine the situation; if disappearance (48 hour silence) is confirmed, they will assign a different mentor to them, and inform Google.
 ;What steps will you take to encourage students to interact with your project's community before, during and after the program?

← Older revision	Revision as of 16:54, 12 March 2009
(No difference)

← Older revision	Revision as of 21:48, 17 March 2008
(No difference)

← Older revision	Revision as of 12:18, 10 March 2008
(No difference)

← Older revision	Revision as of 12:17, 10 March 2008
(No difference)

← Older revision	Revision as of 11:03, 10 March 2008
(No difference)