Account confirmers, Anti-spam team, Confirmed users, Bureaucrats and Sysops emeriti
4,925
edits
Community:SummerOfCode07: Difference between revisions
no edit summary
(Split into application sections; add Seamonkey items) |
No edit summary |
||
| Line 5: | Line 5: | ||
You may wish to consider [http://weblogs.mozillazine.org/gerv/archives/2006/05/how_not_to_apply_for_summer_of.html How Not To Apply For Summer Of Code] before making your application. | You may wish to consider [http://weblogs.mozillazine.org/gerv/archives/2006/05/how_not_to_apply_for_summer_of.html How Not To Apply For Summer Of Code] before making your application. | ||
== | ==Firefox== | ||
{| border="1" cellpadding="3" width="100%" valign="top" | {| border="1" cellpadding="3" width="100%" valign="top" | ||
| Line 15: | Line 15: | ||
| style="background-color: #efefef;" | '''Comments''' | | style="background-color: #efefef;" | '''Comments''' | ||
|- | |- | ||
| valign="top" | | | valign="top" | Implement link fingerprints | ||
| valign="top" | | | valign="top" | Link fingerprints are a method of making an HTTP or HTTPS URL reference not only a particular resource, but a particular version of that resource, in a way that the fetching client can validate. This would make it harder (not impossible) for crackers to change downloadable software packages without any user (and the site owner) noticing it. Further details can be found in [http://www.gerv.net/security/link-fingerprints/ the proposal by Gervase Markham], Gerv's [http://weblogs.mozillazine.org/gerv/archives/2007/03/wordpress_download_tarball_com.html blog post about the recent Wordpress tarball attack] and [https://bugzilla.mozilla.org/show_bug.cgi?id=292481 bug 292481] | ||
| valign="top" | | | valign="top" | [[User:Jens.b|Jens.b]] | ||
| valign="top" | | | valign="top" | Gerv | ||
| valign="top" | I | | valign="top" | This is similar to Heikki's proposal above and could be done as part of that larger activity, but I think it deserves separate mention as its scope is specified more precisely, and it might be faster to implement. - Jens<br><br>There is already an extension which does some of this; a proper patch for the trunk would be required - Gerv | ||
|} | |} | ||
| Line 39: | Line 39: | ||
|} | |} | ||
== | ==Camino== | ||
{| border="1" cellpadding="3" width="100%" valign="top" | {| border="1" cellpadding="3" width="100%" valign="top" | ||
| Line 49: | Line 49: | ||
| style="background-color: #efefef;" | '''Comments''' | | style="background-color: #efefef;" | '''Comments''' | ||
|- | |- | ||
| valign="top" | | | valign="top" | Camino: Tabspose | ||
| valign="top" | | | valign="top" | Expose for tabs, but in the browser window ({{bug|312007}}) | ||
| valign="top" | pinkerton | |||
| valign="top" | pinkerton | |||
| valign="top" | I've wanted to do this for years... | |||
| valign="top" | | |||
| valign="top" | | |||
| valign="top" | | |||
|} | |} | ||
| Line 91: | Line 83: | ||
| valign="top" | Mnyromyr | | valign="top" | Mnyromyr | ||
| valign="top" | UI stuff would be for SeaMonkey, but should be portable to Thunderbird easily. Both would profit from backend fixes. | | valign="top" | UI stuff would be for SeaMonkey, but should be portable to Thunderbird easily. Both would profit from backend fixes. | ||
|} | |||
==Bugzilla== | |||
{| border="1" cellpadding="3" width="100%" valign="top" | |||
|- align="center" | |||
| style="background-color: #efefef;" | '''Title''' | |||
| style="background-color: #efefef;" | '''Abstract - links to details/bugs/etc''' | |||
| style="background-color: #efefef;" | '''Reporter''' | |||
| style="background-color: #efefef;" | '''Mentor(s)''' | |||
| style="background-color: #efefef;" | '''Comments''' | |||
|- | |||
| valign="top" | Bugzilla: Plugin System | |||
| valign="top" | [https://bugzilla.mozilla.org/show_bug.cgi?id=371333 bug 371333]: Bugzilla has many methods for being extended, but they are not always clearly documented or coordinated. There is also no central repository for downloading plugins, or a standard way to install them. This task would be to make it easy for developers to write plugins, make it easy for administrators to install them, and write a useful sample plugin that demonstrates all of this. | |||
| valign="top" | [[User:MaxKanatAlexander|mkanat]] | |||
| valign="top" | [[User:MaxKanatAlexander|mkanat]] | |||
| valign="top" | | |||
|- | |||
| valign="top" | Bugzilla: Overhaul Charting System | |||
| valign="top" | Bugzilla currently has two charting systems, the Old Charts and the New Charts. Old Charts are very simple, and work. New Charts are very complex, and the code has been abandoned for several years. However, charting is a feature that many users want in a bug-tracking system. | |||
This task would be to implement a charting system that is simple to use, respects Bugzilla's built-in security, and provides the flexibility that administrators want. In particular, the ability to go "back in time" and chart data about the past would be very welcome. (Our current system only starts charting data as soon as you set up a chart, so you can't find out anything about last month, or even yesterday.) | |||
| valign="top" | [[User:MaxKanatAlexander|mkanat]] | |||
| valign="top" | Gerv | |||
| valign="top" | There may be some questions about importing data from the old systems. I think that New Charts are not in much use, since they aren't complete. The system would have to be able to import Old Charts, but the New Charts system could be entirely replaced by the system built in this project. (However, any left-over New Charts would have to be exported as CSV so that users wouldn't lose their data.) | |||
|} | |} | ||