Community:SummerOfCode10 - Revision history

Gerv: Changed protection level for "Community:SummerOfCode10" ([Edit=Allow only autoconfirmed users] (indefinite) [Move=Allow only autoconfirmed users] (indefinite))

2014-10-07T08:14:56Z

Changed protection level for "Community:SummerOfCode10" ([Edit=Allow only autoconfirmed users] (indefinite) [Move=Allow only autoconfirmed users] (indefinite))

← Older revision	Revision as of 08:14, 7 October 2014
(No difference)

Gerv at 17:20, 9 March 2012

2012-03-09T17:20:28Z

← Older revision		Revision as of 17:20, 9 March 2012
Line 1:		Line 1:
			<span style="color: red; font-weight: bold">Looking for this year's Summer of Code information? [[SummerOfCode\|Step right this way.]]</span>

	This page lists all the Google Summer of Code 2010 projects with confirmed mentors, and which have been approved by the SoC administrator. New suggestions can be made on [[Community:SummerOfCode10:Brainstorming\|the Brainstorming page]].		This page lists all the Google Summer of Code 2010 projects with confirmed mentors, and which have been approved by the SoC administrator. New suggestions can be made on [[Community:SummerOfCode10:Brainstorming\|the Brainstorming page]].

Gerv at 21:32, 8 April 2010

2010-04-08T21:32:45Z

← Older revision		Revision as of 21:32, 8 April 2010
Line 10:		Line 10:
	* Read [http://weblogs.mozillazine.org/gerv/archives/2006/05/how_not_to_apply_for_summer_of.html How Not To Apply For Summer Of Code] and avoid doing the things listed there.		* Read [http://weblogs.mozillazine.org/gerv/archives/2006/05/how_not_to_apply_for_summer_of.html How Not To Apply For Summer Of Code] and avoid doing the things listed there.
	* Read our examples of good applications: [[SummerOfCode/SampleApplications/1\|1]], [[SummerOfCode/SampleApplications/2\|2]], [[SummerOfCode/SampleApplications/3\|3]].		* Read our examples of good applications: [[SummerOfCode/SampleApplications/1\|1]], [[SummerOfCode/SampleApplications/2\|2]], [[SummerOfCode/SampleApplications/3\|3]].
	* ~~Sign up to apply~~ [http://~~code~~.~~google~~.com/~~soc~~/~~student_step1.html~~ here] ~~(you'll need a Google Account)~~.		* Apply [http://socghop.appspot.com/gsoc/student/apply/google/gsoc2010 here].

	Questions of any sort? Send mail to [mailto:gerv@mozilla.org Gerv] and/or [mailto:chofmann@mozilla.org chofmann]. We will try and respond as soon as possible and get your questions directed to the right person. Please allow at least 48 hours for a reply.		Questions of any sort? Send mail to [mailto:gerv@mozilla.org Gerv] and/or [mailto:chofmann@mozilla.org chofmann]. We will try and respond as soon as possible and get your questions directed to the right person. Please allow at least 48 hours for a reply.

Gerv: /* Mobile/Fennec */

2010-04-05T16:55:51Z

Mobile/Fennec

← Older revision		Revision as of 16:55, 5 April 2010
Line 252:		Line 252:
	\|Joel Maher		\|Joel Maher
	\|The test would be most likely related to bookmarks, tabs, preferences, alerts, panning and zooming. This benefits Mozilla by giving a better testing coverage each day for the mobile browsers. Currently testing is done on lower level stuff, but not the front end. This would primarily be in xul and js code.		\|The test would be most likely related to bookmarks, tabs, preferences, alerts, panning and zooming. This benefits Mozilla by giving a better testing coverage each day for the mobile browsers. Currently testing is done on lower level stuff, but not the front end. This would primarily be in xul and js code.
			\|-
			\|Automate Fennec Performance Tests
			\|Fennec currently has two tests that test the performance of the mobile browser. New set of test will test other features like awesome bar, new tab load, setting preferences etc.
			\|Aditya Rao
			\|Joel Maher
			\|This would be a great benefit to Mozilla as it would help set better goals for overall performance. This would primarily be in xul and js code.
	\|}		\|}

Gerv at 14:24, 30 March 2010

2010-03-30T14:24:58Z

← Older revision		Revision as of 14:24, 30 March 2010
Line 86:		Line 86:
	\| David Bienvenu		\| David Bienvenu
	\|		\|
			\|-
			\|Add Quicklook support for attachments
			\|https://bugzilla.mozilla.org/show_bug.cgi?id=457546
			\|Libras2909 (irc: Libras2909 #nus)
			\|bwinton
			\|This would save MacOSX time skimming through attachments. Thus it would encourage more MacOSx users to move to Thunderbird. Moreover, there has been a lot of Quicklook plugin supports for displaying several different file types. [http://www.qlplugins.com/browse/]. Thus all we have to do is implementing a way to allow Finder to get the attachment from Thunderbird for display purpose.
	\|}		\|}

Gerv: /* Mozilla Platform */

2010-03-29T18:25:34Z

Mozilla Platform

@@ Line 40: / Line 40: @@
 |roc
 |jrmuizel
+|
 |}

Gerv: /* Calendar */

2010-03-26T18:30:41Z

Calendar

← Older revision		Revision as of 18:30, 26 March 2010
Line 116:		Line 116:
	\|Fallen		\|Fallen
	\|[mailto:lmarcotte@inverse.ca Ludovic Marcotte]		\|[mailto:lmarcotte@inverse.ca Ludovic Marcotte]
	\|~~No confirmed mentor yet~~		\|
	\|-		\|-
	\|Improved automated UI testing for Lightning		\|Improved automated UI testing for Lightning

Gerv: /* Calendar */

2010-03-26T18:30:13Z

Calendar

@@ Line 87: / Line 87: @@
 !Comments
 |-
-|Improve Email Invitations
+|Hooks / stubs mechanisms for Mozilla Lightning + Improve event/tasks alarms support
-|Our Email Invitations have been greatly improved since 0.9, but there are still some remaining regressions and new bugs to be fixed here. Also, it would be swell to implement some of the remaining iTIP/iMIP specs, like COUNTER and delegation.[http://tools.ietf.org/html/rfc2447 rfc2447 Email Scheduling (rfc2447)]
+|Subproject #1 - Hooks / stubs mechanisms for Mozilla Lightning
 |Fallen
-|Simon V. ? Ludovic?
+|[mailto:lmarcotte@inverse.ca Ludovic Marcotte]
 |No confirmed mentor yet
 |-
-|Further mozmill tests/improvements
+|Improved automated UI testing for Lightning
-|Merike has done a great job working on Mozmill and I think its a good idea to continue this effort. [https://developer.mozilla.org/en/Mozmill Mozmill] is an automatic testing framework that immitates user actions to check if the application is doing what it is supposed to. The student would be making sure mozmill tests run with our build system ({{bug|545838}}) and writing further tests.
+|Mozmill is a UI Automation tool for the Mozilla Platform. Calendar
 |Fallen
-|Clint? Merike?
+|[mailto:merikes@gmail.com Merike Sell]
-|No confirmed mentor yet
 |-
 |}

Gerv: Remove resource packages - someone is working on it

2010-03-24T16:57:29Z

Remove resource packages - someone is working on it

← Older revision		Revision as of 16:57, 24 March 2010
Line 23:		Line 23:
	!Mentor(s)		!Mentor(s)
	!Comments		!Comments
	\|-
	~~\|Implement resource packages~~
	\|A [http://limi.net/articles/resource-packages-spec-ready-for-prototyping/ specification is ready for prototyping] resource packages ({{bug\|529208}}), which provide a backwards-compatible, simple, efficient way to bundle up resources in a single file to make transfers faster and reduce HTTP overhead.
	~~\|beltzner~~
	~~\|limi,bz(?)~~
	~~\|need to make sure bz/someone from the platform team can mentor~~
	\|-		\|-
	\|Improve Cairo performance to match Skia		\|Improve Cairo performance to match Skia

Gerv at 12:40, 22 March 2010

2010-03-22T12:40:00Z

← Older revision		Revision as of 12:40, 22 March 2010
Line 1:		Line 1:
	This page lists all the Google Summer of Code 2010 projects with confirmed mentors, and which have been approved by the SoC administrator. New suggestions can be made on [[Community:SummerOfCode10:Brainstorming\|the Brainstorming page]].		This page lists all the Google Summer of Code 2010 projects with confirmed mentors, and which have been approved by the SoC administrator. New suggestions can be made on [[Community:SummerOfCode10:Brainstorming\|the Brainstorming page]].

	'''Potential students''': you may choose from the list below, '''but you do not have to''' ~~- feel~~ free to submit a proposal for your own idea. However, before you do so, see the [[Community:SummerOfCode10:Brainstorming\|guidelines for good ideas]]. You can also discuss your ideas or application in the #developers channel on IRC: irc://irc.mozilla.org/#developers .		'''Potential students''': you may choose from the list below, '''but you do not have to'''. Feel free to submit a proposal for your own idea. However, before you do so, see the [[Community:SummerOfCode10:Brainstorming\|guidelines for good ideas]]. You can also discuss your ideas or application in the #developers channel on IRC: irc://irc.mozilla.org/#developers .

	In addition to the specifically-named projects below, we have also tagged a number of bugs in Bugzilla with the keyword [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=student-project&resolution=---&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= student-project]. However, as the idea of a "student project" is wider than just the Summer of Code, students looking through the list will need to decide whether any particular bug listed there is actually the right size and scope for Summer of Code.		In addition to the specifically-named projects below, we have also tagged a number of bugs in Bugzilla with the keyword [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=student-project&resolution=---&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= student-project]. However, as the idea of a "student project" is wider than just the Summer of Code, students looking through the list will need to decide whether any particular bug listed there is actually the right size and scope for Summer of Code.