Changes

Jump to: navigation, search

Potential Projects

259 bytes removed, 14:17, 17 April 2013
m
Reverted edits by Saoagent (Talk) to last revision by Chris Tyler
'''Students:''' If you'd like to work on one of these, move the chosen project to the [[Project List]] and create a page for your work based on the [[Sample Project]] template.
<span style="background: #ffff00">'''NoteOpen Source Community Members:'''</span> OSD/DPS students are encouraged to select We welcome your recommendations for potential projects. Please create an account on this Wiki and create a Mozilla or OOo description for your proposed projectbelow. LUX students are encouraged Please list your contact info (just an IRC or FAS2 name is OK) as well as links to select a Fedora any related web pages as Resources for the proposed project. If you are interested in a project from the other community, please discuss it with your professor(Questions? Ask [[user:Chris Tyler | Chris Tyler]] or [[user:David.humphrey | David Humphrey]])= SBR600 Potential Projects =
'''Open Source Community Members:''' We welcome your recommendations For possible projects for potential projects. Please create an account on this Wiki the SBR600 Software Build and create a description for your proposed project below. Please list your contact info (just an IRC or FAS2 name is OK) as well as links to any related web pages as Resources for Release Course, lease see the proposed project. (Questions? Ask [[user:Chris Tyler | Chris Tyler]] or [[user:David.humphrey | David HumphreySBR600 Potential Projects]])page.
= Potential Eclipse WTP Projects =
See the list of potential bugs [https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=priority&y_axis_field=product&z_axis_field=bug_severity&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&classification=WebTools&product=WTP+Common+Tools&product=WTP+ServerTools&product=WTP+Source+Editing&product=WTP+Webservices&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=NEW&bug_status=REOPENED&bug_severity=major&bug_severity=normal&bug_severity=minor&bug_severity=trivial&priority=P2&priority=P3&priority=P4&priority=P5&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=assigned_to&type0-0-0=regexp&value0-0-0=.@ca.ibm.com&field0-0-1=noop&type0-0-1=noop&value0-0-1= here].
 
<!--
= Potential Fedora Projects =
* https://fedorahosted.org/bodhi/ticket/160
 
 
== Benchmark Nightlife Scalability Issues ==
Using Puppet, or some other management tool, create a grid of a
dozen machines, then turn that into 12,000 machinemachines. Address the network
characteristics - how much bandwidth do you need on different
components, the communication mechanisms - does UDP work at such a
Resource: [[:fedora:Nightlife|Nightlife wiki page]], Matthew Farrellee
<!-- - Below: Commented out by Chris Tyler 2008-08-31 -- I think we'll get all the students doing this.
== Review Packages ==
* Approved review requests - http://fedoraproject.org/wiki/PackageMaintainers/ApprovedReviewRequests
-->
 
= Potential Fedora+Mozilla Projects =
 
== [[Sample Project]] ==
 
This is a sample project stub. You can use the template for [[Sample Project]] in order to create a project page for one of the stubs below. This is how you 'sign-up' for a project.
 
NOTE: if someone has already created the project page, speak to this person and see if you can join them. If so, simply add your name to the '''Project Leader(s)''' page. Otherwise, you can become a contributor later.
= Potential Mozilla Projects =
NOTE: if someone has already created the project page, speak to this person and see if you can join them. If so, simply add your name to the '''Project Leader(s)''' page. Otherwise, you can become a contributor later.
== Autoload language packs Improve Localization build system ==
Create an add-on that will be able Currently it requires many many steps to tell which are the official produce another language packages for each release and allow the user of Firefox.It would really easy to select which ones package these many steps to download and allow reduce the user to select from the language packages that have been downloaded.The extension should allow required knowledge to provide custom URLs pointing to unofficial language packages.Once this extension proves its usability we can generate a custom build that includes this extension and therefore a user would be able to choose their new language upon first start.
References: armenzgAdding a few make steps to wrap this process would help everyone.This is a very easy project to tackle but very benefitial if the time and love is given to it.
== Automate generation of regionalized locales ==Reference: armenzg
== Create a cross-repo pushlog to see all locales's checkins ==We have currently check many different repositories to trigger builds when a script from developer makes a previous Moz-Seneca project change. We also check the localizer's repositories to see if they have pushed any changes. The problem is that we have close to eighty different localization repositories and that can generate a new locale by providing takes a set long time to check each one of rules in a filethem. If we can generate new locales by providing an automated way with buildbot, we could had a joint view that would improve our systems. An example of that view is:https://l10n-stage-sj.mozilla.org/pushes/but the format should be generating locales more like enthis:http://hg.mozilla.org/mozilla-CA central/pushlogwhich is what our release engineering systems check for.This project would require you to hack hg and leverage the dependence for official approvalspushlog to make it work.armenzg has many blog posts explaining how to setup pushlog in your local machine.
ReferencesReference: armenzg- Bug 498641
== Thunderbird SMTP Auto-Sensing ==
Resources: ted
== <strike>== Add OpenLayers test suite to Mozilla ==</strike>==
<strike>Mozilla [http://mxr.mozilla.org/mozilla-central/source/dom/tests/mochitest/ajax/ uses] many common JavaScript library test suites to add additional coverage to it's JavaScript implementation. One test suite that is not currently used by Mozilla, but could be, is the [http://openlayers.org OpenLayer's] js [http://trac.openlayers.org/browser/trunk/openlayers/tests test suite]. See [https://bugzilla.mozilla.org/show_bug.cgi?id=399311 bug# 399311].
3
edits

Navigation menu