Calendar:Roadmap: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Update roadmap to 2014)
 
(49 intermediate revisions by 9 users not shown)
Line 1: Line 1:
The internal code that sunbird uses has been rewritten to allow for greater flexibility and speed. In order to get an useful release, the new backend code needs to be tested. A lot.
'''Please don't edit this page, unless you are a member of the calendar team.'''
=High Level Goals=


Besides this, the lightning guys have been doing great work on the UI front. Sunbird doesn't include this yet, because it would delay a release with the new backend code.
The Mozilla Calendar Team mostly consists of volunteer developers, therefore we don't have a fixed schedule per release. Each contributor is free to work on whatever they think is most fun. We do have a set of high level goals to follow:


To allow for this split testing, the following roadmap can be used:
* Performance
* Test coverage
* Standards compatibility


=Sunbird0.3a1=
Of course new features or other items not mentioned are always welcome, but with the small team size we have, stability is very important.
Released 2005-11-04


Release Goals:
= Current Work =
* Fix regressions from the API rewrite, in a way that Sunbird gets usable again. * Not all bugs need to be fixed in the cleanest way.
* Continue to use old (non-XBL) views and UI.
* '''Intet is to get testing of the providers, and to be able to close old bugs that are fixed by the new ics provider or the new libical.'''


'''Notes for Sunbird0.3a1:'''
For tracking current work, the priority field is used:
This release has old views and stuff. Those views are fixed to a point where the events show up, but there might be glitches in the display. This release was not meant to test the views, but to test the calendar backend code. Please don't file bugs on misaligned event boxes, wrong colours, or whatever else looks wrong. Please do file bugs on events not showing up, events showing up with wrong times, crashes, hangs, errors etc.
* P1: The top 1-2 bugs assigned to you and you are currently working on.
* P2: Whats up next once you've fixed your P1 bugs.
* P3: Bugs that should be part of the Lightning roadmap or are nice to have.  


You are eligible to set P3 bugs if you are working on P1/P2 issues and have landed at least one bug. It should be avoided to make the list of P3 bugs too long, otherwise it ends up being yet another bug list. If in doubt about making a bug P3, feel free to leave a comment first.


=Sunbird0.3a2=
'''List of currently prioritized bugs''': [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=-prio%3A--%20prod%3Acalendar&columnlist=priority%2Cassigned_to%2Cbug_status%2Cshort_desc&order=priority%2Cassigned_to&list_id=11618442 click here]
Released 2006-05-11


Release Goals:
= Contributing =
* Switch to new XBL views.
I would really like to set up a more complete guide on how to contribute, but for now a few basics.
* Sync the UI as much as possible with Lightning 0.1.
* '''Intent is to test the new views and associated UI.'''
*[[Calendar:0.3a2_Task_List|Tentative Goals]]


lilmatt sez: jminta should take outstanding items from the 0.3a2 list and figure out where they go so they don't get lost or forgotten.
If you are interested in helping out or working on your own feature and you don't have a lot of experience with the Mozilla codebase, the first thing you can do is check out one of the following queries:


'''Notes for Sunbird0.3a2:'''
* [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=whiteboard%3A%22%5Bgood%20first%20bug%5D%22%20prod%3Acalendar&list_id=11618494 good first bugs]
These views what we plan to use moving forward. Now is the time to file bugs on misaligned event boxes, wrong colours, or whatever else looks wrong.
* [http://www.joshmatthews.net/bugsahoy/?calendar=1 all mentored bugs]


=Sunbird0.3b=
Once you have found an issue, you should get your build environment set up. To build Lightning, you will be building Thunderbird with Lightning enabled, therefore check the [https://developer.mozilla.org/En/Simple_Thunderbird_build Thunderbird build guide] and make sure you enable Lightning as mentioned on that page. If you prefer, you can also make changes to the Lightning .xpi file instead or use an [https://developer.mozilla.org/en-US/Add-ons/Setting_up_extension_development_environment#Firefox_extension_proxy_file extension proxy file] at first, but eventually you will need to work with the build environment.


Release Goals:
If you have questions, the quickest way to contact someone is to visit the  [[IRC|IRC channel #calendar on irc.mozilla.org]]. If no one is available, you can also check the [https://groups.google.com/forum/#!forum/mozilla.dev.apps.calendar newsgroup] or contact the [mailto:mozilla@kewis.ch project leader] directly.
* '''Bugfixes.'''
* Installers?
* Move locales into l10n repository.
* Easily installable language packs?
* Generic branding except for release?
* Toolkit-based preferences?
* Released from Gecko 1.8 branch?


=Sunbird0.3 - Final release=
Please don't hesitate to get in touch!
 
 
=Sunbird0.4 - Possible Ideas=
'''Disclaimer:''' These are entirely ideas. Don't bet the farm on the fact that they're listed here. They may, and some likely will, never actually make it into a shipping product.
 
* Make Sunbird a child app of XULRunner.
* Integration with Mozilla Software Update
* Possible view eye candy using Cairo?
* Ability to consume Google Gdata?

Latest revision as of 00:02, 24 November 2014

Please don't edit this page, unless you are a member of the calendar team.

High Level Goals

The Mozilla Calendar Team mostly consists of volunteer developers, therefore we don't have a fixed schedule per release. Each contributor is free to work on whatever they think is most fun. We do have a set of high level goals to follow:

  • Performance
  • Test coverage
  • Standards compatibility

Of course new features or other items not mentioned are always welcome, but with the small team size we have, stability is very important.

Current Work

For tracking current work, the priority field is used:

  • P1: The top 1-2 bugs assigned to you and you are currently working on.
  • P2: Whats up next once you've fixed your P1 bugs.
  • P3: Bugs that should be part of the Lightning roadmap or are nice to have.

You are eligible to set P3 bugs if you are working on P1/P2 issues and have landed at least one bug. It should be avoided to make the list of P3 bugs too long, otherwise it ends up being yet another bug list. If in doubt about making a bug P3, feel free to leave a comment first.

List of currently prioritized bugs: click here

Contributing

I would really like to set up a more complete guide on how to contribute, but for now a few basics.

If you are interested in helping out or working on your own feature and you don't have a lot of experience with the Mozilla codebase, the first thing you can do is check out one of the following queries:

Once you have found an issue, you should get your build environment set up. To build Lightning, you will be building Thunderbird with Lightning enabled, therefore check the Thunderbird build guide and make sure you enable Lightning as mentioned on that page. If you prefer, you can also make changes to the Lightning .xpi file instead or use an extension proxy file at first, but eventually you will need to work with the build environment.

If you have questions, the quickest way to contact someone is to visit the IRC channel #calendar on irc.mozilla.org. If no one is available, you can also check the newsgroup or contact the project leader directly.

Please don't hesitate to get in touch!

Retrieved from "https://wiki.allizom.org/index.php?title=Calendar:Roadmap&oldid=1035765"