SoC 2008 Rules - Revision history

DoesItReallyMatter: -:Category:SoC, +:Category:SoC 2008 Project

2019-02-05T06:58:09Z

2009-03-13T10:46:20Z

2008-03-23T08:40:07Z

Selection

@@ Line 29: / Line 29: @@
 * Be able to compile a VLC for your platform (for VLC development) and learn how to use [[Git]].
 * Show the team that you compiled VLC, by probably provide a small patch and a build. You can send the patch to an admin or to vlc-devel@
 * Complete the Google admission and give a planning idea.

2008-03-19T22:35:28Z

Selection

← Older revision		Revision as of 22:35, 19 March 2008
Line 28:		Line 28:
	* Learn about the code you should modify (where in the source, what is the idea...),		* Learn about the code you should modify (where in the source, what is the idea...),
	* Be able to compile a VLC for your platform (for VLC development) and learn how to use [[Git]].		* Be able to compile a VLC for your platform (for VLC development) and learn how to use [[Git]].
	* Show the team that you compiled VLC, by probably provide a small patch and a build.		* Show the team that you compiled VLC, by probably provide a small patch and a build. You can send the patch to an admin or to vlc-devel@

	* Complete the Google admission and give a planning idea.		* Complete the Google admission and give a planning idea.

2008-03-18T18:50:25Z

Selection

← Older revision		Revision as of 18:50, 18 March 2008
Line 28:		Line 28:
	* Learn about the code you should modify (where in the source, what is the idea...),		* Learn about the code you should modify (where in the source, what is the idea...),
	* Be able to compile a VLC for your platform (for VLC development) and learn how to use [[Git]].		* Be able to compile a VLC for your platform (for VLC development) and learn how to use [[Git]].
	* Show the team that you compiled VLC :D		* Show the team that you compiled VLC, by probably provide a small patch and a build.

	* Complete the Google admission and give a planning idea.		* Complete the Google admission and give a planning idea.

2008-03-18T17:37:08Z

Advices

← Older revision		Revision as of 17:37, 18 March 2008
Line 57:		Line 57:
	= Advices =		= Advices =

			== To get selected ==

			* Be nice
			* Show us some code on VLC, that shows us sure you know how to compile VLC.
			* Show us some code on VLC, that shows us that you understand the VLC architecture.
			* Come on IRC.

			== During the SoC ==
	'''''COMMIT EARLY, COMMIT OFTEN'''''		'''''COMMIT EARLY, COMMIT OFTEN'''''

	Ask questions		Ask questions

2008-03-18T07:22:24Z

Selection

← Older revision		Revision as of 07:22, 18 March 2008
Line 28:		Line 28:
	* Learn about the code you should modify (where in the source, what is the idea...),		* Learn about the code you should modify (where in the source, what is the idea...),
	* Be able to compile a VLC for your platform (for VLC development) and learn how to use [[Git]].		* Be able to compile a VLC for your platform (for VLC development) and learn how to use [[Git]].
			* Show the team that you compiled VLC :D

	* Complete the Google admission and give a planning idea.		* Complete the Google admission and give a planning idea.

2008-03-18T06:45:08Z

Student expectations

← Older revision		Revision as of 06:45, 18 March 2008
Line 36:		Line 36:
	* Student should explain his planning to his mentor and to an admin (not everyone has the same vacations)		* Student should explain his planning to his mentor and to an admin (not everyone has the same vacations)
	* Student should report with a small mail once a week to both mentor and admin during the time agreed (failure to do that will fail the application)		* Student should report with a small mail once a week to both mentor and admin during the time agreed (failure to do that will fail the application)
	* Student should commit on his personal git branch once a week, except the first week of your schedule (or more if your project is complex)		* Student should commit on his personal ''git branch'' once a week, except the first week of your schedule (or more if your project is complex).
	'''Explaining why you can't work one week is fine. Disappearing without notice is not.'''		'''Explaining why you can't work one week is fine. Disappearing without notice is not.'''
	* Update wiki status page.		* Update wiki status page.

2008-03-18T06:43:47Z

Student expectations

← Older revision		Revision as of 06:43, 18 March 2008
Line 36:		Line 36:
	* Student should explain his planning to his mentor and to an admin (not everyone has the same vacations)		* Student should explain his planning to his mentor and to an admin (not everyone has the same vacations)
	* Student should report with a small mail once a week to both mentor and admin during the time agreed (failure to do that will fail the application)		* Student should report with a small mail once a week to both mentor and admin during the time agreed (failure to do that will fail the application)
	* Student should commit ~~one your~~ personal git branch once a week, except the first week of your schedule (or more if your project is complex)		* Student should commit on his personal git branch once a week, except the first week of your schedule (or more if your project is complex)
	'''Explaining why you can't work one week is fine. Disappearing without notice is not.'''		'''Explaining why you can't work one week is fine. Disappearing without notice is not.'''
	* Update wiki status page.		* Update wiki status page.

2008-03-18T06:32:23Z

Mentor expectations

← Older revision		Revision as of 06:32, 18 March 2008
Line 48:		Line 48:

	=== Mentor expectations ===		=== Mentor expectations ===
	* Mentor should ~~talk~~ to admins to any problems as ~~fast~~ as noticed		* Mentor should report to admins any problems as soon as noticed,
	* Mentor should tell admins if they can't make it to have another mentor.		* Mentor should tell admins if they can't make it in order to have another mentor for the student.

	=== Mentor rights ===		=== Mentor rights ===