Community:SummerOfCode13:Brainstorming: Difference between revisions

Jump to navigation Jump to search

Community:SummerOfCode13:Brainstorming (view source)

Revision as of 13:59, 16 April 2013

2,869 bytes removed ,  16 April 2013
Move to main page
(Move to main page)
Line 88: Line 88:
| Chris McAvoy
| Chris McAvoy
|
|
|}
== Calendar ==
{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Performance: Make Lightning "Lightning Fast"
| The Lightning Extension has a few performance problems, especially with lots of calendars. Now that the [http://mikeconley.ca/blog/2012/06/15/gecko-profiler-now-works-in-thunderbird-daily/ Gecko Profiler] works in Thunderbird Daily, its a great time to harness its power and improve Lightning's performance. A Student working on this project should:
# [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=keyword%3Aperf%20prod%3Acalendar&list_id=6253887 Browse Bugzilla] to get an overview of reported performance problems.
# Use the Gecko Profiler to identify performance bottlenecks, for example occurrence calculation.
# Propose a method to improve performance in a way that would move the bottleneck elsewhere and discuss with mentor.
# Fix the bottleneck.
# Continue with (2).
Depending on remaining time and student experience, adding performance tests to Lightning would be a bonus.
| Javascript in any case, python and make for perf tests
| Philipp (:Fallen)
| Ludovic (:ludovic)
| 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.
|-
| Improve Calendar Backends
| Lightning has historically supported two modes for calendar providers: cached and uncached. In uncached mode, each request is directly relayed to the remote end, causing a lot of traffic. Therefore, cached mode was introduced, which is close to a "real" synchronization, where only changes are transferred. In the future it would be nice to use cached mode exclusively. To do so, there need to be some changes in the backend. This project consists of a combination of the following bugs, depending on time and student skill:
* Finish the patch I started for async storage ({{bug|501689}})
* Move calendar metadata from the [http://mxr.mozilla.org/comm-central/source/calendar/base/public/calIChangeLog.idl#83 provider inteface] to the [http://mxr.mozilla.org/comm-central/source/calendar/base/public/calIItemBase.idl item interface] (no bug yet)
* Turn the ICS calendar into a cache-only provider ({{bug|780992}})
* Turn the CalDAV calendar into a cache-only provider (no bug yet)
| Javascript, SQL,
| Philipp (:Fallen)
| 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.
|}
|}


Gerv
Account confirmers, Anti-spam team, Confirmed users, Bureaucrats and Sysops emeriti
4,925

edits

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

Navigation menu