MozillaWiki

Community:SummerOfCode14: Difference between revisions

Page Discussion

Community:SummerOfCode14 (view source)

Revision as of 14:02, 19 March 2014

774 bytes added ,  19 March 2014
no edit summary
No edit summary
No edit summary
 
(12 intermediate revisions by 8 users not shown)
Line 1: Line 1:
This page lists all the [[SummerOfCode|Google Summer of Code]] 2014 projects with confirmed mentors, and which have been approved by the SoC administrator. New suggestions can be made on [[Community:SummerOfCode14:Brainstorming|the Brainstorming page]]. Do not edit this page yourself; contact Florian for edits.
This page lists all the [[SummerOfCode|Google Summer of Code]] 2014 projects with confirmed mentors, and which have been approved by the SoC administrator. New suggestions can be made on [[Community:SummerOfCode14:Brainstorming|the Brainstorming page]]. Do not edit this page yourself; contact Florian for edits.


'''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:SummerOfCode14:Brainstorming|guidelines for good ideas]]. You can also discuss your ideas or application in the #developers channel on IRC: irc://irc.mozilla.org/#developers . Your idea will have a significantly greater chance of being chosen if you can find an existing member of the Mozilla community who is willing to evaluate or mentor it. (You should name that person in your application.)
'''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:SummerOfCode14:Brainstorming|guidelines for good ideas]]. You can also discuss your ideas or application in the #introduction channel on IRC: irc://irc.mozilla.org/#introduction . Your idea will have a significantly greater chance of being chosen if you can find an existing member of the Mozilla community who is willing to evaluate or mentor it. (You should name that person in your application.)


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&keywords_type=allwords&keywords=student-project&resolution=--- 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&keywords_type=allwords&keywords=student-project&resolution=--- 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.
Line 63: Line 63:
| [https://mozillians.org/u/gasolin/ Fred Lin]
| [https://mozillians.org/u/gasolin/ Fred Lin]
[https://mozillians.org/en-US/u/gweng/ Greg Weng]
[https://mozillians.org/en-US/u/gweng/ Greg Weng]
|-
|}
== Mozilla Platform (Gecko) ==
{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Provide proper WebRTC testing and integration on BSD systems
| As of now, WebRTC is enabled by default on BSD systems but needs more testing and bugfixes in real-life situations to make it rock-solid and usable, on par with Tier1 platforms. The WebRTC code that already landed for *BSD needs proper integration upstream too.
| Good knowledge of C and IPC.
| Gaston
| Gaston
| Tasks would include finishing the sndio backend for OpenBSD (Bug #911450), upstreaming to webrtc.org the patches already commited to mozilla (#807492 and its dependencies), and make sure the webrtc integration tests also run fine on major BSDs. The project will be successful if an A/V call can be done from firefox nightly from a BSD to another firefox instance on Linux or Windows, and also in-between different BSDs, using the tests from http://mozilla.github.io/webrtc-landing/ and https://apprtc.appspot.com/.
|-
|-
|}
|}
Line 121: Line 141:
| Patrick Cloke
| Patrick Cloke
| IRC, XMPP, Twitter and Yahoo have already been implemented in JavaScript and should not be considered; Some base code exists for OSCAR (AIM/ICQ); SIP, Bonjour and OSCAR are probably the most wanted protocols.
| IRC, XMPP, Twitter and Yahoo have already been implemented in JavaScript and should not be considered; Some base code exists for OSCAR (AIM/ICQ); SIP, Bonjour and OSCAR are probably the most wanted protocols.
|-
| Off-The-Record messaging integration
| ''Goal: Integrate OTR in an easy to use fashion.''
OTR is an often requested feature, but must be integrated in such a way to require little user interaction. Furthermore, the student could try to make Instantbird compliant with the secure messaging checklist suggested by Saint-Andre (link?)
| JavaScript, XUL, XPCOM, maybe js-ctypes or C++
| Patrick Cloke
| Patrick Cloke
|}
|}


Line 151: Line 164:
Depending on remaining time and student experience, adding performance tests to Lightning would be a bonus.
Depending on remaining time and student experience, adding performance tests to Lightning would be a bonus.
| Javascript; Python and make for perf tests
| Javascript; Python and make for perf tests
| Philipp (:Fallen)
| [http://mozillians.org/u/kewisch Philipp (:Fallen)]
| Ludovic (:ludovic) / Mohit(:redDragon)
| Ludovic (:ludovic) / [https://mozillians.org/en-US/u/redDragon/ Mohit(:redDragon)]
| A student applying for this project should be able to work with large codebases. Getting familiar with the Lightning source code early improves chances of being accepted. Look for Fallen on irc.mozilla.org / #calendar if you need help getting started.
| A student applying for this project should be able to work with large codebases. Getting familiar with the Lightning source code early improves chances of being accepted. Look for Fallen on irc.mozilla.org / #calendar if you need help getting started.
|-
|-
Line 162: Line 175:
* Turn the CalDAV calendar into a cache-only provider (no bug yet)
* Turn the CalDAV calendar into a cache-only provider (no bug yet)
| Javascript, SQL,  
| Javascript, SQL,  
| Philipp (:Fallen)
| [http://mozillians.org/u/kewisch Philipp (:Fallen)]
| Mohit (:redDragon)
| [https://mozillians.org/en-US/u/redDragon/ Mohit(:redDragon)]
| As these changes will partially require some migration steps, it is important to write unit tests for the code produced during the Summer of Code. Not all of the mentioned bugs need to be fixed for passing mid-terms and finals, please read through the bugs and consult with mentor or reporter with your suggestion when applying.
| As these changes will partially require some migration steps, it is important to write unit tests for the code produced during the Summer of Code. Not all of the mentioned bugs need to be fixed for passing mid-terms and finals, please read through the bugs and consult with mentor or reporter with your suggestion when applying.
|-
|-
Line 173: Line 186:
* udpate the caldav provider to the latest spec chunk by chunk
* udpate the caldav provider to the latest spec chunk by chunk
| Javascript, SQL,  
| Javascript, SQL,  
| Philipp (:Fallen)
| [http://mozillians.org/u/kewisch Philipp (:Fallen)]
| Mohit (:redDragon) / Philipp(:Fallen)
| [https://mozillians.org/en-US/u/redDragon/ Mohit(:redDragon)] / [http://mozillians.org/u/kewisch Philipp(:Fallen)]
| The work involved will be significantly more and would require deep analysis of the calendar code base. However, the end-product would bring cheers to a lot of users and end complaints of lightning not functioning with a particular server. As a start dive into the RFC and the buglist to find out some of the easy cases which can be solved to gauge the difficulty of the project.
| The work involved will be significantly more and would require deep analysis of the calendar code base. However, the end-product would bring cheers to a lot of users and end complaints of lightning not functioning with a particular server. As a start dive into the RFC and the buglist to find out some of the easy cases which can be solved to gauge the difficulty of the project.
|}
|}
Line 202: Line 215:
| [https://mozillians.org/u/glob/ Byron Jones]
| [https://mozillians.org/u/glob/ Byron Jones]
| Yahoo [https://code.launchpad.net/~evan-goer/bugzilla-yui3/yui3 started the work] however progress has stalled.
| Yahoo [https://code.launchpad.net/~evan-goer/bugzilla-yui3/yui3 started the work] however progress has stalled.
|}
== Accessibility ==
{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Implement speech synthesis on desktop Firefox
| We have an implementation of speech synthesis via the [https://dvcs.w3.org/hg/speech-api/raw-file/tip/speechapi.html Web Speech API]. Currently, only Firefox OS devices have an engine via SVOX Pico. It would be good to have speech synthesis supported on Firefox for desktop OSs as well. Also, the current implementation should be tested and updated to interop with other browsers that support speech synthesis, such as Safari and Chrome.
| Knowledge of C/C++, and perhaps Objective C.
| [https://mozillians.org/en-US/u/eeejay/ eeejay]
| [https://mozillians.org/en-US/u/eeejay/ eeejay] (and probably [https://mozillians.org/en-US/u/smaug/ smaug] doing the bulk of the reviewing).
| We should also explore how far along in the specs [https://dvcs.w3.org/hg/speech-api/raw-file/tip/speechapi-errata.html errata] we could go.
|-
|}
|}


Line 227: Line 260:
| [https://mozillians.org/en-US/u/jgriffin/ Jonathan Griffin]
| [https://mozillians.org/en-US/u/jgriffin/ Jonathan Griffin]
| [https://mozillians.org/en-US/u/jgraham/ James Graham]
| [https://mozillians.org/en-US/u/jgraham/ James Graham]
|
| [https://wiki.mozilla.org/Auto-tools/GSoC/2014#Structured_Logging_for_Mochitest Detailed Outline]
|-
|-
| Mochitest failure investigator
| Mochitest failure investigator
Line 254: Line 287:
| Having {apt-get,yum} install rust
| Having {apt-get,yum} install rust
| deb packaging / Rust (LLVM appreciated)
| deb packaging / Rust (LLVM appreciated)
Must have demonstrated packaging capabilities (packages in Debian or Ubuntu, bug fixes, etc).
|  
|  
| [https://mozillians.org/en-US/u/sylvestre/ Sylvestre Ledru] & Luca Bruno
| [https://mozillians.org/en-US/u/sylvestre/ Sylvestre Ledru] & Luca Bruno
Line 272: Line 306:
|-
|-
| Implement [https://developer.mozilla.org/en-US/docs/XMLHttpRequest XMLHttpRequest]
| Implement [https://developer.mozilla.org/en-US/docs/XMLHttpRequest XMLHttpRequest]
| Make common sites using XHR work in Servo.
| Make common sites using XHR work in [https://github.com/mozilla/servo/ Servo].
| Linux or OS X only; familiarity with XMLHttpRequest; desire to write [http://www.rust-lang.org Rust] code (C++ experience helpful)
| Linux or OS X only; familiarity with XMLHttpRequest; desire to write [http://www.rust-lang.org Rust] code (C++ experience helpful)
| [https://mozillians.org/u/jdm/ Josh Matthews]
| [https://mozillians.org/u/jdm/ Josh Matthews]
Line 307: Line 341:
| {{mozillian|gueroJeff|Jeff Beatty}}
| {{mozillian|gueroJeff|Jeff Beatty}}
|  
|  
* [https://intellego.etherpad.mozilla.org/GSOC-proposal Week by week timeline for GSoC]
* [[Intellego|Project wiki]]
* [[Intellego|Project wiki]]
* [https://wiki.mozilla.org/Intellego/GSoC GSoC wiki ]
* [[Intellego/Meetings/Status|Weekly status meetings]]
* [[Intellego/Meetings/Status|Weekly status meetings]]
* IRC: {{IRC|intellego}}
* IRC: {{IRC|intellego}}
|-
|-
| Mozilla Verbatim and Pootle
| Implement APIs on Verbatim for retrieving the untranslated string information and existing translations if any. Use machine learning and data mining concepts to translate the strings using existing localization intelligence from the large amount of tranlated strings and implement a web application to translate the strings.
Localization plays a major role in Mozilla in spreading its vision of an open and literate web. Localizers are major contributors in making the open source products from Mozilla like Firefox and websites available in 30+ languages, this involves a lot of data being generated in the translation followed by a review process of these translated string. The project aims to use existing database of translations for a particular string and use rating factors and other rating methods to figure out the best translation to a particular string. Also this project can use automatic translation since the data generated by the users over many years can be used for mining and then processing for translation of strings.
This project could also be used in localization of the documentation present on MDN into different languages for the world to use. A feed can be built onto MDN requesting the to be localized content as paragraphs of data and then localizing them using the automatic localization features.
'''Benefits'''
Localization time can be saved More time can be spent in localized string verification than in localization thus giving higher quality localizations.
'''Short Term Goals'''
To make a machine learning integration with Mozilla’s localization platform.
'''Long Term Goal'''
To export the project into a full fledged stand alone application with links to various localization platforms like Transifex, Pootle etc.., thus enhancing the localization features of many open source software projects.
An enhancement to the 2010 Localization machine learning project implemented by Gautam Akiwate.
|
* Understanding of open webservices APIs
* Python (Django) / JavaScript
* Familiarity with a library used for quickly generating a web UI to a server-side Python script
*
| {{mozillian|sudheesh|Sudheesh Singanamalla}}
| {{mozillian|Debloper|Soumya Deb}}
|
* [https://docs.google.com/document/d/1wn_MNzW7qeipU9f6Gp5mkNOo0dV6ja1Sb3suNdaDM2s/edit?usp=sharing Documentation of Project]
|-
|-
|}
|}


== Security Engineering ==
== Security ==


{| class="standard-table" border="1" style="border-collapse: collapse"
{| class="standard-table" border="1" style="border-collapse: collapse"
Line 364: Line 365:
| [https://mozillians.org/en-US/u/mgoodwin/ Mark Goodwin], [https://mozillians.org/en-US/u/psiinon/ Simon Bennetts]
| [https://mozillians.org/en-US/u/mgoodwin/ Mark Goodwin], [https://mozillians.org/en-US/u/psiinon/ Simon Bennetts]
|  
|  
|-
| Kitherder
| Kitherder is a web application that is designed to facilitate participation in the Mentorships program. Note that while this program is currently limited to security projects, the goal of KitHerder is to provide the matchmaking and relationship management features required to open the program to the Mozilla community.<br>
The requirements here are driven by the documentation from the mentorship program and it is expected that the system will leverage Mozillians.org accounts to reduce the amount of personal data stored in Kitherder, and issue badges using the Mozilla Foundation badge system based on participation criteria.<br>
<br><b>Goals</b>: To take Kitherder to a level where it can be deployed to allow the matching of mentors and mentees and manage the basic relationship work.
<br> GitHub Source: https://github.com/ygjb/kitherder
<br> Gist: https://gist.github.com/ygjb/4543418
| Python, HTML, CSS, JavaScript
| Curtis Koenig
| Yvan Boily
|
|-
|}
|}


== Open(Art) ==
== Open(Art) ==
Florian
Confirmed users
87

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/937791...953011"