MozillaWiki - User contributions [en]

User:Dmose:Full Text Indexing Meeting

2008-08-13T18:00:05Z

Lilmatt: /* Existing Engines */

'''Full Text Indexing Meeting Details'''

The intent of this meeting is to discuss full-text indexing in and around the Mozilla platform. A number of different Mozilla-platform based projects either currently have or plan to have full-text indexing. We'd like to talk about existing experience, available engines, and ways to work together on this stuff.

Currently Proposed Time:

[http://timeanddate.com/worldclock/fixedtime.html?year=2008&month=8&day=19&hour=20&min=30&sec=0 Tuesday August 19, 20:30 UTC (1:30pm Pacific, 4:30pm Eastern)]

Possible fallback times:

[http://timeanddate.com/worldclock/fixedtime.html?year=2008&month=8&day=20&hour=17&min=0&sec=0 Wednesday August 20, 17:00 UTC (10:00am Pacific, 1:00pm Eastern)]

[http://timeanddate.com/worldclock/fixedtime.html?year=2008&month=8&day=19&hour=18&min=0&sec=0 Thursday, August 21, 18:00 UTC (11:00am Pacific, 2:00pm Eastern)]

If you're interested in attending and the currently proposed time doesn't work for you, please email [mailto:dmose@mozilla.org dmose@mozilla.org] about which fallback times you could make.

IRC backchannel: #fulltext

[[Thunderbird/StatusMeeting/DialInInfo|How to dial-in]]

Feel free to add items to the agenda that you wish to discuss.

== Agenda ==
* Find a volunteer to take notes

=== Use Cases of Attendees ===
* [[User:Beckley/Indexed_Search_Proposal|Thunderbird]]
* Flock
* Firefox
* Snowl
* ...

=== [[User:Beckley/Indexed_Search_Proposal#Incorporating_an_Indexing_Engine|Existing Engines]] ===
* SQLite (FTS3/4)
* CLucene
** [http://doxygen.flock.com/doxygen/flock/trunk/interfaceflock_i_lucene.html As used by Flock]
* ...

=== Attendees ===

__NOTOC__

* Myk (I may be a bit late, as I have a conflicting meeting until 1:45pm PT)
* asuth
* bienvenu
* dmose
* lilmatt
* yosh
* (Various other who folks have confirmed via other channels)

User:Dmose:Full Text Indexing Meeting

2008-08-13T17:53:40Z

Lilmatt: /* Attendees */

'''Full Text Indexing Meeting Details'''

The intent of this meeting is to discuss full-text indexing in and around the Mozilla platform. A number of different Mozilla-platform based projects either currently have or plan to have full-text indexing. We'd like to talk about existing experience, available engines, and ways to work together on this stuff.

Currently Proposed Time:

[http://timeanddate.com/worldclock/fixedtime.html?year=2008&month=8&day=19&hour=20&min=30&sec=0 Tuesday August 19, 20:30 UTC (1:30pm Pacific, 4:30pm Eastern)]

Possible fallback times:

[http://timeanddate.com/worldclock/fixedtime.html?year=2008&month=8&day=20&hour=17&min=0&sec=0 Wednesday August 20, 17:00 UTC (10:00am Pacific, 1:00pm Eastern)]

[http://timeanddate.com/worldclock/fixedtime.html?year=2008&month=8&day=19&hour=18&min=0&sec=0 Thursday, August 21, 18:00 UTC (11:00am Pacific, 2:00pm Eastern)]

If you're interested in attending and the currently proposed time doesn't work for you, please email [mailto:dmose@mozilla.org dmose@mozilla.org] about which fallback times you could make.

IRC backchannel: #fulltext

[[Thunderbird/StatusMeeting/DialInInfo|How to dial-in]]

Feel free to add items to the agenda that you wish to discuss.

== Agenda ==
* Find a volunteer to take notes

=== Use Cases of Attendees ===
* [[User:Beckley/Indexed_Search_Proposal|Thunderbird]]
* Flock
* Firefox
* Snowl
* ...

=== [[User:Beckley/Indexed_Search_Proposal#Incorporating_an_Indexing_Engine|Existing Engines]] ===
* SQLite (FTS3/4)
* C Lucene
** [http://doxygen.flock.com/doxygen/flock/trunk/interfaceflock_i_lucene.html As used by Flock]
* ...

=== Attendees ===

__NOTOC__

* Myk (I may be a bit late, as I have a conflicting meeting until 1:45pm PT)
* asuth
* bienvenu
* dmose
* lilmatt
* yosh
* (Various other who folks have confirmed via other channels)

Calendar:Who is who

2008-04-09T16:18:27Z

Lilmatt: /* Past contributors */

== Active contributors ==

{| class="fullwidth-table"
| style="background:#efefef" | '''Name'''
| style="background:#efefef" | '''Location'''
| style="background:#efefef" | '''Job'''
| style="background:#efefef" | '''IRC'''
| style="background:#efefef" | '''Mail'''
| style="background:#efefef" | '''Bugzilla'''
| style="background:#efefef" | '''Litmus'''
| style="background:#efefef" | '''Web'''
| style="background:#efefef" | '''Photo'''
|-
| Daniel Boelzle
| Germany
| Project Lead and Developer
| dbo, daniel
| daniel.boelzle (AT) sun.com
| daniel.boelzle (AT) sun.com
|
|
|
|-
| Clint Talbert
| USA
| Developer and QA
| ctalbert
| ctalbert (AT) mozilla (DOT) com
| ctalbert (AT) mozilla (DOT) com
| cmtalbert (AT) mozilla (DOT) com
| [http://cmtalbert.googlepages.com/mozillalinks]
|
|-
| Martin Schroeder
| Germany
| QA Team Lead and Developer
| mschroeder
| mschroeder (AT) mozilla (DOT) x-home (DOT) org
| mschroeder (AT) mozilla (DOT) x-home (DOT) org
|
| [http://www.x-home.org/]
|
|-
| Sebastian Schwieger
| Germany
| QA and Developer
| Sebo
| sebo.moz (AT) googlemail (DOT) com
| sebo.moz (AT) googlemail (DOT) com
|
|
|
|-
| Lars Wohlfahrt
| Germany
| QA
| thetux
| thetux.moz (AT) googlemail (DOT) com
| thetux.moz (AT) googlemail (DOT) com
| thetux
| [http://www.eviltux.de]
|
|-
| Gary Kwong
| Singapore
| QA
| nth10sd
| nth10sd (AT) gmail (DOT) com
| nth10sd (AT) gmail (DOT) com
|
|
|
|-
| Michael Buettner
| Germany
| Developer
| mickey
| michael.buettner (AT) sun (DOT) com
| michael.buettner (AT) sun (DOT) com
|
|
|
|-
| Philipp Kewisch
| Germany
| Developer
| Fallen
| mozilla (AT) kewis (DOT) ch
|
|
|
|
|-
| Simon Paquet
| Germany
| Project Lead, Website/Localization coordinator and Developer
| sipaq
| bugzilla (AT) babylonsounds (DOT) com
|
|
|
|
|-
| Michiel van Leeuwen
| Netherlands
| Developer
| mvl
| mvl (AT) exedo (DOT) nl
|
|
|
|
|-
| Bruno Browning
| USA
| Developer
| bbbrowning
| browning (AT) uwalumni (DOT) com
|
|
|
|
|-
| Christian Jansen
| Germany
| User Experience Lead
| christian, chris-j
| christian.jansen (AT) sun (DOT) com
|
|
|
|
|-
| Andreas Treumann
| Germany
| QA Engineer
| andreas
| andreas.treumann (AT) sun (DOT) com
|
|
|
|
|-
| Mark Carson
| USA
| Graphic Artist
|
| Mark (AT) MarkCarson (DOT) com
|
|
| [http://www.MarkCarson.com]
|
|-
| Stefan Sitter
| Germany
| QA and Developer
| ssitter
| ssitter (AT) gmail (DOT) com
|
|
|
|
|-
| Celina Beach
| USA
| QA
|
|
|
|
|
|
|-
| Sebastian Hengst
| Germany
| QA
| Archaeopteryx
|
|
|
|
|
|-
| Berend Cornelius
| Germany
| UI development
| berend
|
|
|
|
|
|-
| Omar Bajraszewski
| Poland
| QA
| Omar
|
|
|
|
|
|-
| Dan Mosedale
| USA
| Calendar Project Lead
| dmose
|
|
|
|
|
|-
| Damian ?
| Poland
| QA and Litmus Administrator
| Damian
|
|
|
|
|
|-
| Myk Melez
|
|
| myk
| myk (AT) mozilla (DOT) org
|
|
|
|
|-
| Bas van den Bosch
|
|
|
| bvdbos (AT) chello (DOT) nl
|
|
|
|
|}

== Past contributors ==

{| class="fullwidth-table"
| style="background:#efefef" | '''Name'''
| style="background:#efefef" | '''Location'''
| style="background:#efefef" | '''Job'''
| style="background:#efefef" | '''IRC'''
| style="background:#efefef" | '''Mail'''
| style="background:#efefef" | '''Bugzilla'''
| style="background:#efefef" | '''Litmus'''
| style="background:#efefef" | '''Web'''
| style="background:#efefef" | '''Photo'''
|-
| Stephan Schafer
| Germany
| Developer
| ssa
|
|
|
|
|
|-
| Joey Minta
| USA
| Developer
| jminta
|
|
|
|
|
|-
| Matt Willis
| USA
| Developer
| lilmatt
| mattwillis@gmail.com
| lilmatt@flock.com
|
|
|
|-
| Ulf Ströhler
| Germany
| QA
| Ulf
|
|
|
|
|
|-
| Thomas Benisch
| Germany
| Developer
| tbe
|
|
|
|
|
|}

Calendar:Module Ownership

2007-08-08T16:14:14Z

Lilmatt: move lilmatt to backup status

This is the current list of owners and peers of the calendar modules. '''Don't edit this file. Just don't.'''

Items without any owners at all are generally handled by those under "Default." However, in general, they could benefit from being their own strongly-owned modules at some point.

{| border="1" cellpadding="4"
!Module
!Owner
!Peers (alpha order)
|-
|Default (stuff under /mozilla/calendar not otherwise listed here)
|mvl*
|lilmatt*, daniel, mickey, ctalbert
|-
|colspan="3"|'''Applications/Extensions'''
|-
|Sunbird (calendar/sunbird)
|mvl*
|daniel, lilmatt*, ctalbert
|-
|Lightning (calendar/lightning)
|mvl*
|daniel, lilmatt*, ctalbert
|-
|colspan="3"|'''Components'''
|-
|Accessibility
|?
|?
|-
|Alarms
|?
|daniel, philipp
|-
|Art & Branding
|lilmatt*
|MarkCarson
|-
|Calendar Manager
|mvl*
|daniel, ctalbert
|-
|Import/Export (calendar/import-export)
|mvl*
|mickey
|-
|Installer (calendar/installer)
|lilmatt*
|rob_strong, ctalbert
|-
|i18n/l10n (calendar/locales)
|lilmatt*
|sipaq
|-
|libical (calendar/libical)
|mvl*
|daniel, mickey
|-
|Recurrence
|daniel
|mvl*, mickey, ctalbert
|-
|Timezones
|ctalbert
|mvl*, lilmatt*, daniel
|-
|Views & Dialogs (calendar/{sunbird/}base/content)
|mickey
|philipp
|-
|iTIP
|ctalbert
|lilmatt*, daniel
|-
|Printing
|lilmatt*
|daniel
|-
|Website
|sipaq
|lilmatt*
|-
|User Interface (UI)
|christian
|mvl*
|-
|colspan="3"|'''Providers'''
|-
|CalDAV
|bbrowning
|lilmatt*, daniel
|-
|Composite
|mvl*
|daniel, mickey
|-
|ICS
|mvl*
|daniel, mickey
|-
|Memory
|mvl*
|daniel
|-
|Storage
|mvl*
|daniel
|-
|WCAP
|daniel
|?
|-
|GDATA
|philipp
|daniel
|-
|colspan="3"|'''Tier-1 platform-specific stuff'''
|-
|Linux
|daniel
|?
|-
|Mac OS X
|lilmatt*
|ctalbert
|-
|Windows
|ctalbert
|ssitter, daniel
|}

* Backup reviewer. Assign to them rarely.

{| border="0"
! colspan="2" align="center" | Legend
|-
|
{| border="1"
!Reviewer
!Bugzilla ID
|-
|bbrowning
|browning at uwalumni dot com
|-
|christian
|christian.jansen at sun dot com
|-
|ctalbert
|ctalbert at mozilla dot com
|-
|daniel
|daniel.boelzle at sun dot com
|-
|lilmatt
|lilmatt at flock dot com
|-
|MarkCarson
|mark at markcarson dot com
|}
|
{| border="1"
!Reviewer
!Bugzilla ID
|-
|mickey
|michael.buettner at sun dot com
|-
|mvl
|mvl at exedo dot nl
|-
|philipp
|philipp at bugzilla dot kewis dot ch
|-
|rob_strong
|robert.bugzilla at gmail dot com
|-
|sipaq
|bugzilla at babylonsounds dot com
|-
|ssitter
|ssitter at gmail dot com
|}
|}

=== Review Process ===

Calendar does not require super-review. The only review is needed is the review of a module owner or peer of the involved module. (If a patch spans multiple modules, you need review from an owner or peer from each module. That sounds problematic, but due to the huge overlap in owners and peers, in most cases it can be done by one person.)

If the module owner and their peers are all busy and don't have time to do a complete review, you can ask someone else to review the code. This must be 'known hacker', somebody who has done calendar work himself, but does not need to be a module owner or peer. If you have code review, you can ask a owner or peer of the module your code touches to give module-owner-approval. Giving this approval only means that the code is good from a high level point of view. Because this is a lot less work, it should be easier to get this approval.

[[category:calendar|Module Ownership]]

Calendar:Home Page

2007-08-08T16:12:22Z

Lilmatt: /* For developers */

__NOTOC__
'''Welcome to the wiki of the Mozilla Calendar Project.'''

This [http://en.wikipedia.org/wiki/Wiki wiki] represents a collection of easily-editable pages providing a variety of information on both the standalone calendar application [http://www.mozilla.org/projects/calendar/sunbird/ Sunbird], and the calendaring extension for [http://www.mozilla.com/thunderbird/ Mozilla Thunderbird], code-named [http://www.mozilla.org/projects/calendar/lightning/ Lightning].

Please keep in mind that while every effort is made to keep these pages up-to-date, sometimes pages do become obsolete.

== Latest Releases ==
*'''[http://www.mozilla.org/projects/calendar/releases/lightning0.5.html Lightning 0.5]''' - The calendaring extension for [http://www.mozilla.com/thunderbird/ Mozilla Thunderbird]
*'''[http://www.mozilla.org/projects/calendar/releases/sunbird0.5.html Sunbird 0.5]''' - Our standalone calendar application for Linux, Mac OS X, and Windows.

== For end-users ==
These pages contain information that end-users (that's you!) will hopefully find useful.

*[[Calendar:FAQ | FAQ]] - "Frequently Asked Questions" concerning Sunbird and Lightning
* How to contribute - Looking to get involved? Look here for some good starting points.
*[[Calendar:Charter]] (draft) - The overall mission of the calendar project
*[[Calendar:Target Users|Target Users]] - Who we're writing software for
*[[Calendar:Lightning]] - (jminta-will probably move?) Links to all pages related to Lightning
*[[Calendar:Past_Releases|Past Releases]] - Where we've been.
*[[Calendar:Roadmap|Roadmap]] - Where we're going.
*[[Calendar:For_Everyone:Blocking Flags|Blocking Flags]] - How we choose what makes it into each release.

== For developers ==
These are pages for people interested in contributing in a more formal way to Sunbird and Lightning development, whether through testing (QA), or coding.
*[[Calendar:F2F Meeting]] - The July 2006 Toronto face-to-face meeting.
*[[Calendar:Hamburg F2F Meeting]] - The April 2007 Hamburg face-to-face meeting.
*[[Calendar:Localization]] - Information for translators on how to localize Sunbird and Lightning.
*[[Calendar:Hacking|Beginner's Guide to Hacking Sunbird/Lightning]] (in progress) Information for someone looking to get their feet wet in the mozilla codebase for the first time
*[[Calendar:Dev Guide|New Sunbird/Lightning Developer's Guide]] (draft)- A bird's eye view of the calendar codebase
*[[Calendar:Status Meetings|Meeting notes]] - Notes from past meetings held on IRC. Also includes the schedule and agenda for the next meeting
*[[Calendar: Feature Implementations |Feature Implementations]] - proposals and overviews of past, present, and possible future features in Sunbird and Lightning.
*[[Calendar:QA Home|Calendar QA and Testing]] - Information for those wishing to help test development builds, in an effort to improve quality.
*Administration ([[Calendar: Module Ownership]], [[Calendar:Updating libical]], [[Calendar: Development Strategies]], [[Calendar:Build Team Requests]]) - pages related to administrative tasks in calendar development (reviews, release cycles, etc)
**[[Calendar: UI Ownership]]
**[[Calendar: Review Process]]

[[category:Calendar|*]]

Calendar:Next Release

2007-08-08T16:11:24Z

Lilmatt: Deprecated - add redirect

#REDIRECT [[Calendar:Roadmap]]

WeeklyUpdates/2007-07-09

2007-07-09T20:01:40Z

Lilmatt: /* Other Business */

[[WeeklyUpdates/2007-07-02| « previous week]] | [[WeeklyUpdates|index]] | [[WeeklyUpdates/2007-07-16|next week »]]

'''Meeting Details'''
* 1:00pm Pacific time (20:00 UTC until November 4, 2007)
* Mozilla HQ, 1st floor conference table
* +1 650 903 0800 x91 Conf# 8600 (US/International)
* +1 416 848 3114 x91 Conf# 8600 (Canada)
* +1 800 707 2533 (pin 369) Conf# 8600 (US Toll Free)
* [Use *1 to mute yourself]
* join irc.mozilla.org #staffmeeting for attendance taking

Use "*1" (including the star) to mute yourself, if desired, to keep phone noise down.

= In Attendance =

= Development Updates =

== Fx/TB 1.5.0.13/2.0.0.5 ==
* Code Freeze: This Friday 7/13
** Please land approved patches ASAP!
** Continue triaging bugs that need patches
*** A lot of bugs with no Trunk bake time or recent traction will be pushed out
*** We will help prioritize blockers for devs that have a lot of bugs assigned (jst, mrbkap, sicking, bz, dvedtiz)
* QA starting bug verifications on 2.0.0.5pre builds
* Still targeting 7/31 for release date (to avoid conflict with FF3b1 milestone)

== TB 3 ==
* Thunderbird trunk builds will be moving to Breakpad this week and we'll be removing talkback. Thanks to Ted Mielczarek, bsmedberg, aravind and coop for their help in making this possible.

== Gecko 1.9 ==

* Continued Blocker focus.
* Wrapping goals up by the end of Tuesday (See: [http://wiki.mozilla.org/Platform/2007-Q3-Goals Platform Q3 Goals] )
* [http://wiki.mozilla.org/Firefox3/Schedule Announce updated schedule] and the [http://tinyurl.com/29e63o related discussion].

== Firefox 3 ==

* Alpha 6 Released ([http://www.mozilla.org/projects/firefox/3.0a6/releasenotes/ release notes)

* Lots of UI work in progress:
** protocol handling
** malware UI (landed)
** plugins in the addons manager
** download manager
** Places UI for adding tags and bookmarks

== IT ==
* Build VM performance issues
** Migration needed to a new LUN - planning for Tuesday
** should significantly improve performance
* Mozilla-eu migrated to San Jose
* Pageload server re-write work continues

== Build ==
* There will be a 12-hour outage window on Tuesday to move the most critical VMs around on the Netapp to help solve some performance problems. It will start at 10 am.
* Planning this week to deploy the new linux ref platform, which is based on CentOS 5.0; Win32 ref platform bump is up next.
* We'll be handing off the community build tinderboxen tomorrow during tomorrow evening's outage window.

== QA ==

== Security ==

== Marketing/PR ==
* OSCON:
**Last call for travel!
**Please help get the word out for [http://wiki.mozilla.org/Conferences:oscon07/ office hours] and our [http://www.spreadfirefox.com/node/27794/ community party]

* Firefox eBay Edition launched for UK/DE/FR last Wednesday, July 4. Details [http://www.mozilla.com/en-US/press/mozilla-2007-07-04.html here].

== Community ==
*Wednesday, July 11th at 12 noon in Bldg. K: JT, Asa & Seth B will present a re-cap of South American Trip & Global community engagement, marketing, localization, etc. See http://jtbatson.blogspot.com/ for highlights! Webcast will be Available
*Wednesday, July 11th at 2 PM: Air Mozilla returns. Asa working with Marcia, Jay, Zach Lipton, pkim and producer Rainer Cvillink to host a community meeting with guest Mitchell Baker. Details [http://www.spreadfirefox.com/node/27885 here].

== Mozilla Labs ==

== Developer Relations ==

== Webdev, Add-ons, AMO ==
* AMO
** Facebook app planned for launch by end of July
** Load testing for supporting Facebook app this and next week
** Working with IT on planning release and deployment
** Download and update ping stats will be made available for developers
** Add-ons not compatible with Firefox 2 will be "sandboxed" today (about 800)
* Breakpad
** Breakpad hackathon this week
* Mozilla Support
** Worked with JT and choffman to pick groupware
** We'll be working with TikiWiki and its community to produce a beta Mozilla Support knowledgebase
* mozilla-europe.org & mozilla-world.org
** On new hardware

= Foundation Updates =

= Roundtable =

= Other Business =
* Flock 0.9.0 will be released tomorrow.
** Based off of Fx 2.0.0.4

WeeklyUpdates/2007-07-02

2007-07-02T20:06:13Z

Lilmatt: /* Other Business */

[[WeeklyUpdates/2007-06-25| « previous week]] | [[WeeklyUpdates|index]] | [[WeeklyUpdates/2007-07-09|next week »]]

'''Meeting Details'''
* 1:00pm Pacific time (20:00 UTC until November 4, 2007)
* Mozilla HQ, 1st floor conference table
* +1 650 903 0800 x91 Conf# 8600 (US/International)
* +1 416 848 3114 x91 Conf# 8600 (Canada)
* +1 800 707 2533 (pin 369) Conf# 8600 (US Toll Free)
* [Use *1 to mute yourself]
* join irc.mozilla.org #staffmeeting for attendance taking

Use "*1" (including the star) to mute yourself, if desired, to keep phone noise down.

= In Attendance =

= Development Updates =

== Fx/TB 1.5.0.13/2.0.0.5 ==
* Fx 1.5.0.12 major updates were rolled out
** IT has some numbers, but approximately 3 million have updated
** There was almost no feedback regarding major update on newsgroups.
* Fx 2.0.0.5 triage on-going

== TB 3 ==
* hunspell is now on the trunk but not part of the build yet. Thanks to Ryan and Nemeth for their work on this. Hunspell will eventually replace myspell as our spell check engine.

== Gecko 1.9 ==

== Firefox 3 ==

* Wrapped up Alpha 6:
** Updated SQLite
** Improved cookie performance
** Support for site-specific preferences
** Miscellaneous fixes and UI improvements to the Add-ons manager, download manager, bookmarks and history.
* Work on Beta 1 is commencing:
** Places UI changes
** Bookmarks sync
** Web-based protocol handling (first UI maybe this week)
** Identity UI

== IT ==
* Major update
** Went well - continues at a rate of ~13 updates/sec, topped out at a rate of 30 updates/sec
** just under 3 million major updates
** no negative impact on infrastructure
* [http://people.mozilla.com/~justin/images/Firefox2004MajorUpgradesByLatestVersion.png Downloads Graph]

== Build ==
* Talkback has been removed from all nightly trunk builds, replaced by breakpad; breakpad is also shipping in all 1.9a6 builds.
* We'll be updating linux nightly builds to the new reference platform this week; [https://bugzilla.mozilla.org/show_bug.cgi?id=384035 bug 384035] tracks the work.
* VMware migrations were finished last week, but performance on the Netapp isn't what we thought it would be based on tests; we're actively trying different configurations and talking with Netapp and VMware to work through the problems; [https://bugzilla.mozilla.org/show_bug.cgi?id=386074 bug 386074] tracks the issue.
* Build team is now triaging bugs on two week cycles; we're doing a triage tomorrow, which begins the next cycle. We'll be posting more details shortly about what priorities mean and how we're using them.

== QA ==
* Test Execution
** Major Updates testing
** Alpha6 Smoketests and focus testing

* Test Development
** Fx3 on-going functional tests development

* Tools and Automation
**tbd

* Community
** tbd

== Security ==

== Marketing/PR ==
* OSCON:
**Book your travel!
**[https://intranet.mozilla.org/ConferencesSchedule/OSCON2007/#Attendees/ Sign up for booth duty]

* Successful community building in Brazil -- check out [http://jtbatson.blogspot.com JT's blog] for details
** Brazil brown bag later this week

* Vendor selection meeting Tuesday at 2pm for support system. Dial in info:
** Tuesday, July 3, 2:00 pm PDT
** +1 650-903-0800 x91 Conf #284
** 1-800-707-2533 (pin 369) Conf #284 (US)
** Join #customersupport on irc.mozilla.org for the IRC back-channel

== Community ==

== Mozilla Labs ==

== Developer Relations ==

== Webdev, Add-ons, AMO ==
* AUS
** Last round of testing throttle patch. [http://people.mozilla.com/~morgamic/aus2-tests/ see results].
* AMO
** Download count patch deployed [http://blog.mozilla.com/webdev/ read about results on the webdev blog]
** [http://wiki.mozilla.org/Update:Remora_UI_Review/Mockups/Home_Page/ Check out UI progress]
* Mozilla Support
** Evaluation of possible groupware
* moz-eu CMS
** Going live today

= Foundation Updates =

Note that Frank is traveling on Monday, July 2, during the weekly call, and won't be able to participate.

* Grants
** We'll be funding a project to enhance the [http://www.nvda-project.org/ NVDA open source screen reader] for Windows to better support Firefox. WebAIM has officially completed its project to produce revised [http://developer.mozilla.org/en/docs/Accessible_XUL_Authoring_Guidelines XUL accessibility guidelines] and create a [http://developer.mozilla.org/en/docs/XUL_accessibility_tool XUL accessibility evaluation tool]. Henri Sivonen completed the third milestone on his current HTML5 conformance checker project.
* Legal
** We're going to be pursuing formal trademark registration for the Camino logo.
* Miscellaneous
** Gerv is continuing evaluation of CAs for inclusion in Mozilla products, and has two candidates ([https://bugzilla.mozilla.org/show_bug.cgi?id=373746 A-Trust] and [https://bugzilla.mozilla.org/show_bug.cgi?id=382352 Entrust]) for approval.
** Gerv continued work on a bugzilla.mozilla.org [https://bugzilla.mozilla.org/show_bug.cgi?id=384721 Product/Component reorganisation plan]; discussion is occurring in [http://groups.google.com/group/mozilla.dev.planning/browse_frm/thread/7b27e453a2e38b90/7259ca3d163a120e#7259ca3d163a120e mozilla.dev.planning].
** David is continuing to get up to speed; in the short term he's looking at helping out with the www.mozilla.org web site and tracking of Mozilla Foundation donations.

For more information see the individual status reports:

* [http://davidwboswell.wordpress.com/ David Boswell]
* [http://zak.greant.com/ Zak Greant]
* [http://hecker.org/mozilla/foundation-activities-2007-06-29 Frank Hecker]
* [http://weblogs.mozillazine.org/gerv/archives/2007/06/weekly_status_20070629.html Gerv Markham]

= Roundtable =

= Other Business =
* Sunbird and Lightning 0.5 released this week
** based off MOZILLA_1_8_BRANCH
** uses AUS for future updates
** Sunbird and Lightning 0.7 in planning - Driver: Daniel Boezle from Sun Germany

* Flock 0.9 went into public beta this past week
** based off of Fx 2.0.0.4
** scheduled to release within next two weeks

WeeklyUpdates/2007-07-02

2007-07-02T20:04:35Z

Lilmatt:

[[WeeklyUpdates/2007-06-25| « previous week]] | [[WeeklyUpdates|index]] | [[WeeklyUpdates/2007-07-09|next week »]]

'''Meeting Details'''
* 1:00pm Pacific time (20:00 UTC until November 4, 2007)
* Mozilla HQ, 1st floor conference table
* +1 650 903 0800 x91 Conf# 8600 (US/International)
* +1 416 848 3114 x91 Conf# 8600 (Canada)
* +1 800 707 2533 (pin 369) Conf# 8600 (US Toll Free)
* [Use *1 to mute yourself]
* join irc.mozilla.org #staffmeeting for attendance taking

Use "*1" (including the star) to mute yourself, if desired, to keep phone noise down.

= In Attendance =

= Development Updates =

== Fx/TB 1.5.0.13/2.0.0.5 ==
* Fx 1.5.0.12 major updates were rolled out
** IT has some numbers, but approximately 3 million have updated
** There was almost no feedback regarding major update on newsgroups.
* Fx 2.0.0.5 triage on-going

== TB 3 ==
* hunspell is now on the trunk but not part of the build yet. Thanks to Ryan and Nemeth for their work on this. Hunspell will eventually replace myspell as our spell check engine.

== Gecko 1.9 ==

== Firefox 3 ==

* Wrapped up Alpha 6:
** Updated SQLite
** Improved cookie performance
** Support for site-specific preferences
** Miscellaneous fixes and UI improvements to the Add-ons manager, download manager, bookmarks and history.
* Work on Beta 1 is commencing:
** Places UI changes
** Bookmarks sync
** Web-based protocol handling (first UI maybe this week)
** Identity UI

== IT ==
* Major update
** Went well - continues at a rate of ~13 updates/sec, topped out at a rate of 30 updates/sec
** just under 3 million major updates
** no negative impact on infrastructure
* [http://people.mozilla.com/~justin/images/Firefox2004MajorUpgradesByLatestVersion.png Downloads Graph]

== Build ==
* Talkback has been removed from all nightly trunk builds, replaced by breakpad; breakpad is also shipping in all 1.9a6 builds.
* We'll be updating linux nightly builds to the new reference platform this week; [https://bugzilla.mozilla.org/show_bug.cgi?id=384035 bug 384035] tracks the work.
* VMware migrations were finished last week, but performance on the Netapp isn't what we thought it would be based on tests; we're actively trying different configurations and talking with Netapp and VMware to work through the problems; [https://bugzilla.mozilla.org/show_bug.cgi?id=386074 bug 386074] tracks the issue.
* Build team is now triaging bugs on two week cycles; we're doing a triage tomorrow, which begins the next cycle. We'll be posting more details shortly about what priorities mean and how we're using them.

== QA ==
* Test Execution
** Major Updates testing
** Alpha6 Smoketests and focus testing

* Test Development
** Fx3 on-going functional tests development

* Tools and Automation
**tbd

* Community
** Community test day held last Friday, Alpha 6-pre

== Security ==

== Marketing/PR ==
* OSCON:
**Book your travel!
**[https://intranet.mozilla.org/ConferencesSchedule/OSCON2007/#Attendees/ Sign up for booth duty]

* Successful community building in Brazil -- check out [http://jtbatson.blogspot.com JT's blog] for details
** Brazil brown bag later this week

* Vendor selection meeting Tuesday at 2pm for support system. Dial in info:
** Tuesday, July 3, 2:00 pm PDT
** +1 650-903-0800 x91 Conf #284
** 1-800-707-2533 (pin 369) Conf #284 (US)
** Join #customersupport on irc.mozilla.org for the IRC back-channel

== Community ==

== Mozilla Labs ==

== Developer Relations ==

== Webdev, Add-ons, AMO ==
* AUS
** Last round of testing throttle patch. [http://people.mozilla.com/~morgamic/aus2-tests/ see results].
* AMO
** Download count patch deployed [http://blog.mozilla.com/webdev/ read about results on the webdev blog]
** [http://wiki.mozilla.org/Update:Remora_UI_Review/Mockups/Home_Page/ Check out UI progress]
* Mozilla Support
** Evaluation of possible groupware
* mozilla.com
* CMS

= Foundation Updates =

Note that Frank is traveling on Monday, July 2, during the weekly call, and won't be able to participate.

* Grants
** We'll be funding a project to enhance the [http://www.nvda-project.org/ NVDA open source screen reader] for Windows to better support Firefox. WebAIM has officially completed its project to produce revised [http://developer.mozilla.org/en/docs/Accessible_XUL_Authoring_Guidelines XUL accessibility guidelines] and create a [http://developer.mozilla.org/en/docs/XUL_accessibility_tool XUL accessibility evaluation tool]. Henri Sivonen completed the third milestone on his current HTML5 conformance checker project.
* Legal
** We're going to be pursuing formal trademark registration for the Camino logo.
* Miscellaneous
** Gerv is continuing evaluation of CAs for inclusion in Mozilla products, and has two candidates ([https://bugzilla.mozilla.org/show_bug.cgi?id=373746 A-Trust] and [https://bugzilla.mozilla.org/show_bug.cgi?id=382352 Entrust]) for approval.
** Gerv continued work on a bugzilla.mozilla.org [https://bugzilla.mozilla.org/show_bug.cgi?id=384721 Product/Component reorganisation plan]; discussion is occurring in [http://groups.google.com/group/mozilla.dev.planning/browse_frm/thread/7b27e453a2e38b90/7259ca3d163a120e#7259ca3d163a120e mozilla.dev.planning].
** David is continuing to get up to speed; in the short term he's looking at helping out with the www.mozilla.org web site and tracking of Mozilla Foundation donations.

For more information see the individual status reports:

* [http://davidwboswell.wordpress.com/ David Boswell]
* [http://zak.greant.com/ Zak Greant]
* [http://hecker.org/mozilla/foundation-activities-2007-06-29 Frank Hecker]
* [http://weblogs.mozillazine.org/gerv/archives/2007/06/weekly_status_20070629.html Gerv Markham]

= Roundtable =

= Other Business =
* Sunbird and Lightning 0.5 released this week
** based off MOZILLA_1_8_BRANCH
** uses AUS for future updates
** Sunbird and Lightning 0.7 in planning - Driver: Daniel Boezle from Sun Germany

Calendar:HowToRelease

2007-06-06T16:42:03Z

Lilmatt:

= Release Process =

NOTES:
* ${PRODUCT_TAG} is the header for the BRANCH - for sunbird 0.5 this was SUNBIRD_0_5, other releases should follow the same convention
* ${BRANCH_TAG} is made by appending _BRANCH to the ${PRODUCT_TAG} for example, SUNBIRD_0_5_BRANCH

== Create a branch ==
1. Create a branch from the branch you are releasing from this creates a ${PRODUCT_TAG}_BRANCH from the MOZILLA_1_8_BRANCH, you also need to note the time this was done on a page like [[Calendar:Release:Sunbird_0.5]].
<pre>
cvs rtag -r MOZILLA_1_8_BRANCH -b ${PRODUCT_TAG}_BRANCH mozilla
Note time this is done: May 22, 21:37 CDT</pre>
2. Test that the branch was properly created by checking out from the branch.
<pre> cvs co -r ${BRANCH_TAG}_BRANCH mozilla/calendar </pre>

== Change the Version Number ==
* You check out the branch you just created - use standard "check out code from mozilla cvs method", just substitute in the new branch for your branch parameter
* On this branch, you change the follwing:
* calendar/sunbird/app/module.ver
* calendar/sunbird/config/version.txt
* Then you:
<pre>cvs -d ${CVSROOT} co -r ${PRODUCT_TAG}_BRANCH\
mozilla/calendar/sunbird/app/module.ver mozilla/calendar/sunbird/config/version.txt
</pre>

==Create a minibranch==
<pre>
cvs tag -b ${PRODUCT_TAG}_MINIBRANCH calendar/sunbird/app/module.ver \
calendar/sunbird/config/version.txt
cvs up -r ${PRODUCT_TAG}_MINIBRANCH calendar/sunbird/app/module.ver \
calendar/sunbird/config/version.txt
cvs ci -m"bumping version number on calendar/sunbird on minibranch only"
</pre>

* remove firefox stuff from calendar/lightning/install.rdf

== Tag the release ==
* run "date" before you start and use this as date stamp.
* the date should be in UTC and have this format: "yyyy-mm-dd hh:mm +0000"
* You need to use an RC here in case we have RC builds that way RCs will move forward to the release (you can have multiple RC's but there is only one release) so ${RC} becomes 1 for the first attempt to release 0.5
<pre>
screen
cd .. (one up from mozilla)
mkdir -p tags/${PRODUCT_TAG}_RC${RC}
cd tags && ln -s ${PRODUCT_TAG}_RC${RC} ${PRODUCT_TAG}_RELEASE && \
ln -s ${PRODUCT_TAG}_RC${RC} ${PRODUCT_TAG}_RELEASE
</pre>
* Next, check out mozilla/client.mk and any <something>/config/mozconfig files you need with statements like this:
<pre>
cvs co \
-r $BRANCH_TAG \
-D "$PULL_DATE" \
mozilla/client.mk
becomes: cvs co -r ${PRODUCT_TAG}_BRANCH -D "2007-05-23 04:00 +0000" mozilla/client.mk
</pre>
* Next, you follow these steps:
<pre>
# pull version files from the version bump minibranch
cvs up -r ${PRODUCT_TAG}_MINIBRANCH ${APP}/app/module.ver \
${APP}/config/version.txt config/milestone.txt

# Create the tag.
cvs tag ${PRODUCT_TAG}_RELEASE 2>&1 | tee ../${PRODUCT_TAG}_RELEASE.log
# Look for errors
grep -v "^T" ../${PRODUCT_TAG}_RELEASE.log

# Create the RC tag.
cvs tag ${PRODUCT_TAG}_RC${RC} 2>&1 | tee ../${BRANCH_TAG}_RC${RC}.log
# Look for errors
grep -v "^T" ../${PRODUCT_TAG}_RC${RC}.log

# Create a minibranch for the pull scripts so we can change them without
# changing anything on the original branch.
cvs tag -b ${PRODUCT_TAG}_MINIBRANCH client.mk

# Update client.mk to the minibranch you just created.
cvs up -r ${PRODUCT_TAG}_MINIBRANCH client.mk

# Add the new product tag to the client.mk - need to replace the current branch ID
sed "s/${MOZILLA_1_8_BRANCH}/${PRODUCT_TAG}_RELEASE/g" client.mk > client.mk.tmp
mv client.mk.tmp client.mk

# Verify that client.mk only has the changes you expect
cvs diff -u client.mk
# Verify that client.mk has its sticky tag set properly.
cvs status client.mk
cvs commit -m "For $PRODUCT $VERSION, redirect client.mk onto the ${PRODUCT_TAG}_RELEASE tag." client.mk

# Move the release tag onto the modified version of the pull scripts.
# Note that you may have to wait to gain a lock, that is normal.
cvs tag -F ${PRODUCT_TAG}_RELEASE client.mk
cvs tag -F ${PRODUCT_TAG}_RC${RC} client.mk
</pre>

=== Tag Talkback===
* '''NOTE:''' to do this, you need access to talkback, currently only lilmatt has that access on our team.
<pre>
# Create the mofo tag directory.
cd ~cltbld/tags/${PRODUCT_TAG}_RC${RC}
mkdir mofo/
cd mofo/

# Branch Talkback like we did for the SUNBIRD_0_5_RELEASE earlier:
cvs -d ${CVSROOT}/mofo rtag -r MOZILLA_1_8_BRANCH -b ${PRODUCT_TAG}_BRANCH mofo

# Check out the talkback files from the branch you want to tag.
cvs -d :ext:cltbld@cvs.mozilla.org:/mofo co \
-r $BRANCH_TAG \
-D "$PULL_DATE" \
talkback/fullsoft 2>&1 | tee checkout-output.log

# Create the tag.
cd talkback/fullsoft/
cvs tag ${PRODUCT_TAG}_RELEASE 2>&1 | tee ../${PRODUCT_TAG}_RELEASE.log

# Look for errors
grep -v "^T" ../${PRODUCT_TAG}_RELEASE.log
</pre>

=== Tag L10N ===
* Note that you will need L10N access to do this
<pre>
# Create the l10n tag directory.
cd ~cltbld/tags/${PRODUCT_TAG}_RELEASE
mkdir l10n/
cd l10n/

# Branch Locales like we did for the SUNBIRD_0_5_RELEASE earlier:
cvs -d ${CVSROOT}/l10n rtag -r MOZILLA_1_8_BRANCH -b ${PRODUCT_TAG}_BRANCH l10n

# Grab list of shipped locales
LOCALES=`awk '{print $1}' < ../cvsroot/mozilla/calendar/locales/shipped-locales`

# Check out the l10n files from the branch you want to tag.
(for l in $LOCALES
do
cvs -d ${CVSROOT}/l10n co \
-r $BRANCH_TAG \
-D "$PULL_DATE" \
l10n/${l}
done) 2>&1 | tee checkout-output.log

cd l10n/
</pre>

Use lilmatt's magic L10N script to compile Lightning into Locales. You can find the script in {{bug|352546}}. We will check it into the main tree somewhere (suggested name: m/c/lilmattsmagicbuildtricks). You need to update the .dtd and .properties filenames for the current release.

==Push tag forward on updated l10n files==
In the <code>l10n</code> directory where you originally tagged l10n...
cvs up -r SUNBIRD_0_5_BRANCH
cvs tag -F SUNBIRD_0_5_RELEASE

Calendar:Release:Sunbird 0.5

2007-05-24T01:21:18Z

Lilmatt: /* Build data */

(Following procedure in [[Build:Unified_Release_Process]])

==Build Engineers==

* Matthew Willis <lilmatt@flock.com>
* Clint Talbert <ctalbert@mozilla.com>

==Bonsai queries==

[https://bugzilla.mozilla.org/buglist.cgi?product=Calendar&status_whiteboard_type=anywordssubstr&status_whiteboard=fixed0.3.1+verified0.3.1 Blocker Bugs for this release from Bugzilla]

==Tags==

{| class="fullwidth-table"
| style="background:#efefef" | '''Module'''
| style="background:#efefef" | '''Tag'''
| style="background:#efefef" | '''Pull date'''

|-
| rowspan="2" | cvsroot/mozilla
| SUNBIRD_0_5_RELEASE
| 2007-05-22 21:37 CDT
|-
| SUNBIRD_0_5_RC1
| 2007-05-22 21:37 CDT
|-
| rowspan="1" | mofo/talkback/fullsoft
| SUNBIRD_0_5_RELEASE
| 2007-05-23 21:00 EDT
|-
| rowspan="2" | l10n/l10n
| SUNBIRD_0_5_RELEASE
| 2007-05-23 21:00 CDT
|-
| SUNBIRD_0_5_RC1
| 2007-05-23 21:00 CDT
|}

==Build data==

{| class="fullwidth-table"
| style="background:#efefef" | '''Type'''
| style="background:#efefef" | '''Build ID'''
| style="background:#efefef" | '''SHA1'''
| style="background:#efefef" | '''Push date'''
| style="background:#efefef" | '''Build machine'''
|-
| [Windows installer]
|build_id_goes_here
|sha1_goes_here
|push_date_goes_here
|sb-win32-tbox
|-
| [Windows zip]
|build_id_goes_here
|sha1_goes_here
|push_date_goes_here
|sb-win32-tbox
|-
| [Mac dmg]
|build_id_goes_here
|sha1_goes_here
|push_date_goes_here
|bm-xserve07
|-
| [Linux bz2]
|build_id_goes_here
|sha1_goes_here
|push_date_goes_here
|galactica
|}

==Timing==

All times are for each RC, except for "Overall release process".

{| class="fullwidth-table"
| style="background:#efefef" | '''Activity'''
| style="background:#efefef" | '''Begin'''
| style="background:#efefef" | '''End'''

|-
| Overall release process
| 2007-02-08 23:15 EST
|
|-
| RC1 Tagging
| 2007-02-08 23:30 EST
| 2007-02-09 00:36 EST
|-
| RC1 Building
| 2007-02-09 00:40 EST
| 2007-02-09 02:30 EST
|-
| RC1 Source archival
| 2007-02-09 01:15 EST
| 2007-02-09 01:37 EST
|-
| RC1 l10n repackaging
| 2007-02-09 02:30 EST
| 2007-02-09 03:45 EST
|-
| RC1 l10n repack verification
| n/a
| n/a
|-
| RC1 Update generation
| n/a
| n/a
|-
| RC1 Signing
| n/a
| n/a
|}

==Configuration==

TBOX_TREE="Sunbird"
PRODUCT_TAG="SUNBIRD_0_5"
PLATFORM_TAG="HEAD"
BRANCH_TAG="SUNBIRD_0_5_BRANCH"
PULL_DATE="2007-05-23 04:00 +0000"
BUILD_DIR=
PRODUCT=sunbird
AUS_PRODUCT=Sunbird
SHORT_PRODUCT=Sb
APP=calendar
VERSION=0.5
RC=1
PREVIOUS_VERSION=0.3.1
PREVIOUS_RC=
PUSH_DATE=

==Notes==

Calendar:Release:Sunbird 0.5

2007-05-24T01:08:14Z

Lilmatt: /* Build data */

(Following procedure in [[Build:Unified_Release_Process]])

==Build Engineers==

* Matthew Willis <lilmatt@flock.com>
* Clint Talbert <ctalbert@mozilla.com>

==Bonsai queries==

[https://bugzilla.mozilla.org/buglist.cgi?product=Calendar&status_whiteboard_type=anywordssubstr&status_whiteboard=fixed0.3.1+verified0.3.1 Blocker Bugs for this release from Bugzilla]

==Tags==

{| class="fullwidth-table"
| style="background:#efefef" | '''Module'''
| style="background:#efefef" | '''Tag'''
| style="background:#efefef" | '''Pull date'''

|-
| rowspan="2" | cvsroot/mozilla
| SUNBIRD_0_5_RELEASE
| 2007-05-22 21:37 CDT
|-
| SUNBIRD_0_5_RC1
| 2007-05-22 21:37 CDT
|-
| rowspan="1" | mofo/talkback/fullsoft
| SUNBIRD_0_5_RELEASE
| 2007-05-23 21:00 EDT
|-
| rowspan="2" | l10n/l10n
| SUNBIRD_0_5_RELEASE
| 2007-05-23 21:00 CDT
|-
| SUNBIRD_0_5_RC1
| 2007-05-23 21:00 CDT
|}

==Build data==

{| class="fullwidth-table"
| style="background:#efefef" | '''Type'''
| style="background:#efefef" | '''Build ID'''
| style="background:#efefef" | '''SHA1'''
| style="background:#efefef" | '''Push date'''
| style="background:#efefef" | '''Build machine'''
|-
| [Windows installer]
|build_id_goes_here
|sha1_goes_here
|push_date_goes_here
|sb-win32-tbox
|-
| [Windows zip]
|build_id_goes_here
|sha1_goes_here
|push_date_goes_here
|sb-win32-tbox
|-
| [Mac dmg]
|build_id_goes_here
|sha1_goes_here
|push_date_goes_here
|cg-xserve04
|-
| [Linux bz2]
|build_id_goes_here
|sha1_goes_here
|push_date_goes_here
|galactica
|}

==Timing==

All times are for each RC, except for "Overall release process".

{| class="fullwidth-table"
| style="background:#efefef" | '''Activity'''
| style="background:#efefef" | '''Begin'''
| style="background:#efefef" | '''End'''

|-
| Overall release process
| 2007-02-08 23:15 EST
|
|-
| RC1 Tagging
| 2007-02-08 23:30 EST
| 2007-02-09 00:36 EST
|-
| RC1 Building
| 2007-02-09 00:40 EST
| 2007-02-09 02:30 EST
|-
| RC1 Source archival
| 2007-02-09 01:15 EST
| 2007-02-09 01:37 EST
|-
| RC1 l10n repackaging
| 2007-02-09 02:30 EST
| 2007-02-09 03:45 EST
|-
| RC1 l10n repack verification
| n/a
| n/a
|-
| RC1 Update generation
| n/a
| n/a
|-
| RC1 Signing
| n/a
| n/a
|}

==Configuration==

TBOX_TREE="Sunbird"
PRODUCT_TAG="SUNBIRD_0_5"
PLATFORM_TAG="HEAD"
BRANCH_TAG="SUNBIRD_0_5_BRANCH"
PULL_DATE="2007-05-23 04:00 +0000"
BUILD_DIR=
PRODUCT=sunbird
AUS_PRODUCT=Sunbird
SHORT_PRODUCT=Sb
APP=calendar
VERSION=0.5
RC=1
PREVIOUS_VERSION=0.3.1
PREVIOUS_RC=
PUSH_DATE=

==Notes==

Calendar:Release:Sunbird 0.5

2007-05-24T01:07:19Z

Lilmatt: removing old data

(Following procedure in [[Build:Unified_Release_Process]])

==Build Engineers==

* Matthew Willis <lilmatt@flock.com>
* Clint Talbert <ctalbert@mozilla.com>

==Bonsai queries==

[https://bugzilla.mozilla.org/buglist.cgi?product=Calendar&status_whiteboard_type=anywordssubstr&status_whiteboard=fixed0.3.1+verified0.3.1 Blocker Bugs for this release from Bugzilla]

==Tags==

{| class="fullwidth-table"
| style="background:#efefef" | '''Module'''
| style="background:#efefef" | '''Tag'''
| style="background:#efefef" | '''Pull date'''

|-
| rowspan="2" | cvsroot/mozilla
| SUNBIRD_0_5_RELEASE
| 2007-05-22 21:37 CDT
|-
| SUNBIRD_0_5_RC1
| 2007-05-22 21:37 CDT
|-
| rowspan="1" | mofo/talkback/fullsoft
| SUNBIRD_0_5_RELEASE
| 2007-05-23 21:00 EDT
|-
| rowspan="2" | l10n/l10n
| SUNBIRD_0_5_RELEASE
| 2007-05-23 21:00 CDT
|-
| SUNBIRD_0_5_RC1
| 2007-05-23 21:00 CDT
|}

==Build data==

{| class="fullwidth-table"
| style="background:#efefef" | '''Type'''
| style="background:#efefef" | '''Build ID'''
| style="background:#efefef" | '''SHA1'''
| style="background:#efefef" | '''Push date'''
| style="background:#efefef" | '''Build machine'''
|-
| [Windows installer]
|build_id_goes_here
|sha1_goes_here
|
|sb-win32-tbox
|-
| [Windows zip]
|build_id_goes_here
|sha1_goes_here
|
|sb-win32-tbox
|-
| [Mac compressed]
|build_id_goes_here
|sha1_goes_here
|
|cg-xserve04
|-
| [Linux compressed]
|build_id_goes_here
|sha1_goes_here
|
|galactica
|}

==Timing==

All times are for each RC, except for "Overall release process".

{| class="fullwidth-table"
| style="background:#efefef" | '''Activity'''
| style="background:#efefef" | '''Begin'''
| style="background:#efefef" | '''End'''

|-
| Overall release process
| 2007-02-08 23:15 EST
|
|-
| RC1 Tagging
| 2007-02-08 23:30 EST
| 2007-02-09 00:36 EST
|-
| RC1 Building
| 2007-02-09 00:40 EST
| 2007-02-09 02:30 EST
|-
| RC1 Source archival
| 2007-02-09 01:15 EST
| 2007-02-09 01:37 EST
|-
| RC1 l10n repackaging
| 2007-02-09 02:30 EST
| 2007-02-09 03:45 EST
|-
| RC1 l10n repack verification
| n/a
| n/a
|-
| RC1 Update generation
| n/a
| n/a
|-
| RC1 Signing
| n/a
| n/a
|}

==Configuration==

TBOX_TREE="Sunbird"
PRODUCT_TAG="SUNBIRD_0_5"
PLATFORM_TAG="HEAD"
BRANCH_TAG="SUNBIRD_0_5_BRANCH"
PULL_DATE="2007-05-23 04:00 +0000"
BUILD_DIR=
PRODUCT=sunbird
AUS_PRODUCT=Sunbird
SHORT_PRODUCT=Sb
APP=calendar
VERSION=0.5
RC=1
PREVIOUS_VERSION=0.3.1
PREVIOUS_RC=
PUSH_DATE=

==Notes==

Calendar:Release:Sunbird 0.5

2007-05-24T01:06:17Z

Lilmatt: updating tags

(Following procedure in [[Build:Unified_Release_Process]])

==Build Engineers==

* Matthew Willis <lilmatt@flock.com>
* Clint Talbert <ctalbert@mozilla.com>

==Bonsai queries==

[https://bugzilla.mozilla.org/buglist.cgi?product=Calendar&status_whiteboard_type=anywordssubstr&status_whiteboard=fixed0.3.1+verified0.3.1 Blocker Bugs for this release from Bugzilla]

==Tags==

{| class="fullwidth-table"
| style="background:#efefef" | '''Module'''
| style="background:#efefef" | '''Tag'''
| style="background:#efefef" | '''Pull date'''

|-
| rowspan="2" | cvsroot/mozilla
| SUNBIRD_0_5_RELEASE
| 2007-05-22 21:37 CDT
|-
| SUNBIRD_0_5_RC1
| 2007-05-22 21:37 CDT
|-
| rowspan="1" | mofo/talkback/fullsoft
| SUNBIRD_0_5_RELEASE
| 2007-05-23 21:00 EDT
|-
| rowspan="2" | l10n/l10n
| SUNBIRD_0_5_RELEASE
| 2007-05-23 21:00 CDT
|-
| SUNBIRD_0_5_RC1
| 2007-05-23 21:00 CDT
|}

==Build data==

{| class="fullwidth-table"
| style="background:#efefef" | '''Type'''
| style="background:#efefef" | '''Build ID'''
| style="background:#efefef" | '''SHA1'''
| style="background:#efefef" | '''Push date'''
| style="background:#efefef" | '''Build machine'''
|-
| [Windows installer]
|2007020822
|cb66aa802d6215035e2685c95e946528985eb78b
|
|sb-win32-tbox
|-
| [Windows zip]
|2007020822
|9b53654abc6f86eeec67b61410514b1354c12eca
|
|sb-win32-tbox
|-
| [Mac compressed]
|2007020821
|941d88847e864119c6d4a787105f6a43ba86783c
|
|cg-xserve01
|-
| [Linux compressed]
|2007020821
|ac31b2083c0cd4370af1554dbdf6eee7ebf13f9b
|
|galactica
|}

==Timing==

All times are for each RC, except for "Overall release process".

{| class="fullwidth-table"
| style="background:#efefef" | '''Activity'''
| style="background:#efefef" | '''Begin'''
| style="background:#efefef" | '''End'''

|-
| Overall release process
| 2007-02-08 23:15 EST
|
|-
| RC1 Tagging
| 2007-02-08 23:30 EST
| 2007-02-09 00:36 EST
|-
| RC1 Building
| 2007-02-09 00:40 EST
| 2007-02-09 02:30 EST
|-
| RC1 Source archival
| 2007-02-09 01:15 EST
| 2007-02-09 01:37 EST
|-
| RC1 l10n repackaging
| 2007-02-09 02:30 EST
| 2007-02-09 03:45 EST
|-
| RC1 l10n repack verification
| n/a
| n/a
|-
| RC1 Update generation
| n/a
| n/a
|-
| RC1 Signing
| n/a
| n/a
|}

==Configuration==

TBOX_TREE="Sunbird"
PRODUCT_TAG="SUNBIRD_0_5"
PLATFORM_TAG="HEAD"
BRANCH_TAG="SUNBIRD_0_5_BRANCH"
PULL_DATE="2007-05-23 04:00 +0000"
BUILD_DIR=
PRODUCT=sunbird
AUS_PRODUCT=Sunbird
SHORT_PRODUCT=Sb
APP=calendar
VERSION=0.5
RC=1
PREVIOUS_VERSION=0.3.1
PREVIOUS_RC=
PUSH_DATE=

==Notes==

Calendar:Status Meetings:2007-05-23

2007-05-23T05:52:06Z

Lilmatt: /* Agenda Items */

__NOTOC__
<<[[Calendar:Status Meetings:2007-05-16| previous meeting]] | [[Calendar:Status Meetings|index]] | [[Calendar:Status Meetings:2007-05-30| next meeting >>]]

== Meeting Details ==
*[http://www.timeanddate.com/worldclock/meetingdetails.html?year=2007&month=5&day=23&hour=16&min=0&sec=0&p1=16&p2=37&p3=64&p4=179&p5=224 Wednesday, May 23th, 16:00 UTC]
* Phone meeting
* Join #calendar-mtg on irc.mozilla.org for attendance

=== Telephone Info ===
* Toll free numbers
** US/Canada: 866-692-3163
** Netherlands: 0800-020-1392
** Germany: 0800-000-3441
*Participant Passcode
** 3182189
*Conference controls
** Press *1 private help menu
** Press *6 mute or un-mute individual line
* Each time you say something, please say your name first so people know who's speaking

=== Agenda Items ===
* 0.5 Shipping schedule
* ctalbert will not be able to make the meeting, so he left these notes...
** lilmatt and I worked through most of the night on the release. (He may be late to the meeting.)
** We got about half-way to a release and hit blocking bug 381683
** We're waiting on the fix to that before moving forward with the release.
** Current release "how to" documentation (documents up to our current step) is in progress at: [[Calendar:HowToRelease]] Be warned! It is not for the feint-hearted.
** Once we have a release, we'll have a L10N and functional-focused test day

Calendar:Hamburg F2F Meeting

2007-04-23T15:58:43Z

Lilmatt: /* Meeting Notes and Decisions */

Information regarding the 2. Mozilla Calendar Developers Face-to-Face Meeting

Americans should read [http://www.tobsy.de/?p=22 20 things to keep in mind when visiting Germany] first :-)
__NOTOC__
=Who=

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"

|- align="left"
| colspan="2" bgcolor="#cccccc" | '''Tentative Attendees'''
|-
|
*Matthew Willis (lilmatt)
*Philipp Kewisch (xFallenAngel)
*Clint Talbert (ctalbert)
*Simon Paquet (sipaq)
*Christian Jansen (chris-j)
*Daniel Boelzle (daniel)

|
*Michael Büttner (mickey)
*Stephan Schäfer (ssa)
*Thomas Benisch (tbe)
*Andreas Treumann (Andreas)
*Ulf Stroehler (ulf)
*Berend Cornelius (Berend)
|-
|}

=Where=
'''Meeting:''' 
Sun Microsystems GmbH 
Nagelsweg 55 
20097 Hamburg 
Germany 

[http://www.google.com/maps?hl=en&client=firefox-a&rls=org.mozilla:en-US:official&hs=rEP&q=sun+microsystems&near=Hamburg,+Germany&sa=X&oi=local&ct=title Map]

'''Lodging:''' 
[http://www.jungeshotel.de/index_en.html Junges Hotel]
* Approx. 70,- € with Sun Discount, near by Sun's Office

Between 100 € - 130 €
* [http://www.apartmentservice.de/en/house/79-hanse-clipper-haus.html Hanse Clipper Haus Boardinghouse] nice location

* [http://www.wedina.de/ Wedina] nice location

* [http://sas.radisson.com/reservation/itineraryEntrance.do?rmcCode=&startDate=20070421&numberChildren=0&a_month_year=200704&language=en&numberAdults=1&hotelCode=&country=DE&promotionalCode=&paclink=Y&ref=/reservation/itineraryEntrance.do&CSbridge=94.u%1115fa6070808ea64e9765be8c7fc7b099c553ae3d%12s%11146%13ss%11%111174397046656%111174396000906&a_date=21&endDate=20070424&d_date=24&city=hamburg&d_month_year=200704 SAS Radisson] (Favorite, good public transportation)

* [http://www.novotel.com/novotel/fichehotel/gb/nov/3737/fiche_hotel.shtml Dorint Novotel] Hamburg Alster

=Public Transportation=
== Airport -> [http://maps.google.com/maps?f=q&hl=en&q=MARSEILLER+STRASSE+2+Hamburg&layer=&sll=53.561533,9.984899&sspn=0.008501,0.020342&ie=UTF8&z=16&ll=53.561125,9.987431&spn=0.008501,0.020342&t=h&om=1&iwloc=addr SAS Radission] ==

* At the Airport take the '''Bus''' with the number '''110'''
* '''Get out''' at the Station called '''Ohlsdorf'''
* Transfer to the Subway
* Take the '''S11''' (direction: Blankenese)
* Get out at '''Dammtor (Messe/CCH)'''

== SAS Radission -> Sun ==
* At '''Dammtor (Messe/CCH)''' take the '''S31''' (direction: Harburg Rathaus)
* Get out at '''Hammerbrook (City Süd)'''
* this is a 6 Minutes ride.

[[Image:Sun-hh.jpg]].

=When=
<table border="0" cellspacing="0" cellpadding="4">
<tr>
<td align="right">From:</td>
<td align="left">Saturday</td><td>2007-04-21</td><td>10:00AM</td>
</tr><tr>
<td align="right">To:</td>
<td align="left">Tuesday</td><td>2007-04-24</td><td>3:00PM</td>
</tr>
</table>

== Agenda (Draft) ==
=== Day 1 (Saturday) ===
{| border="1" cellpadding="3" width="100%" valign="top"

|- align="left"
| style="background-color: #efefef; width: 20%" | '''Time'''
| style="background-color: #efefef; width: 20%" | '''Topic'''
| style="background-color: #efefef; width: 60%" | '''Description'''
|-
| 10:00-12:30 || Brunch || Meet-and-greet
|-
| 1:00-1:30 || Welcome || ('''Daniel''') Agenda overview, goals
|-
| 1:30-2:15 || User Feedback || ('''chris-j''')
|-
| 2:30-4:00 || Product and Release Strategy || done by sipaq What is our current situation (strengths, weaknesses)? Where do we go from here (Integration into TB/SM? Two product strategy?)? How can we do our releases better.
|-
| 4:15-5:30 || Sunbird and Lightning || ('''chris-j''') discussion on designing features for both Apps
|-
|}

=== Day 2 (Sunday) ===
{| border="1" cellpadding="3" width="100%" valign="top"

|- align="left"
| style="background-color: #efefef; width: 20%" | '''Time'''
| style="background-color: #efefef; width: 20%" | '''Topic'''
| style="background-color: #efefef; width: 60%" | '''Description'''
|-
| 10:00-10:45 || Feature Discussion Shorts* || Off-line Mode ('''Daniel''')
|-
| 11:00-11:45 || Feature Discussion Shorts* || Searching Calendars ('''ctalbert''')
|-
| 12:00-12:30 || Project Ownership || ('''All''')
|-
| 12:30-3:30 || Lunch ||
|-
| 4:00-4:45 || Feature Discussion Shorts* || Pluggable Provider Packaging ('''Matt, Daniel''', '''Philipp?''')
|-
| 5:00-6:00 || Milestone& Roadmap Planning, Wrap-Up ||
|-
|}

=== Day 3 (Monday) ===
{| border="1" cellpadding="3" width="100%" valign="top"

|- align="left"
| style="background-color: #efefef; width: 20%" | '''Time'''
| style="background-color: #efefef; width: 20%" | '''Topic'''
| style="background-color: #efefef; width: 60%" | '''Description'''
|-
| 10:00-12:00 || Milestone& Roadmap Planning Continued, Cont. ||
|-
| 12:00-1:00 || Lunch ||
|-
| 1:15-1:45 || Test Strategies || align forces, prevent regression ('''ulf''')
|-
| 2:00-3:00 || Automated GUI Testing || ('''Thorsten Z.''')
|-
| 3:15-3:45|| Thunderbird Integration || ('''chris-j''')
|-
| 4:00-4:45 || Feature Discussion Shorts* || Group scheduling ('''ctalbert, Daniel''')
|-
| 5:00-6:00 || Automated Builds & Tinderbox || ('''Ause, Matt''')
|-
|}

=== Day 4 (Tuesday) ===
{| border="1" cellpadding="3" width="100%" valign="top"

|- align="left"
| style="background-color: #efefef; width: 20%" | '''Time'''
| style="background-color: #efefef; width: 20%" | '''Topic'''
| style="background-color: #efefef; width: 60%" | '''Description'''
|-
| 10:00-12:00 || QA-Track Shorts* ||
('''ctalbert''') 
* Test coverage
* Test case organization
* Test automation
** Joey's test extension
** xpcshell unit tests
** chrome based mochitest
* Ways to improve and recruit more people to help with calendar-qa
** redesigning the QA wiki site
** improving the QA test day
** streamlining the ramp up to release and the final find/fix cycle
|-
| 12:15-1:30 || Lunch ||
|-
| 1:30-2:30 || Feature Discussion Shorts* || Time zones ('''ctalbert''')
|-
| 3:00 || End ||
|-
|}

Note on "Shorts": These are intended to be '''45min''' segments on a particular topic/idea. They can be demos/prototypes, architecture problems/ideas, short talks, or really almost anything. Ideally, they should be split 15min for the presenter and 30min for discussion, but this is flexible. If you wish to present here, please sign up for an open slot. More slots can be created if the need arises.

== Meeting Notes and Decisions ==
=== Day 1 Saturday ===
* We need to focus on our testing on Lightning and because many of our new features are landing there (iTIP WCAP etc). So need to make testing easier on Lightning possibly by having an RDF to autoscript a dummy mail account so that it will be easier to install Thunderbird and run lightning without worrying about your private data.
* Philipp (xFallenAngel) has scripts to help ensure that patches have the proper style and there are no "compile" typo errors in your javascript.
* Need to talk to David B and M Scott to find out if we can make a "Thunderbird now with Calendaring" sort of idea and incorporate calendar by default into Tbird.
* Decided that there will be a tasks view because you cannot properly display tasks in the calendar view because tasks may not always have dates and will not easily be displayable. Specifically this means:
** Integrate Lightning into Thunderbird with the "today button" in toolbar. Also add set of three buttons in lower left to switch to different modes for the application: the modes are Mail, Calendar and Tasks.
** Clicking on "today button" toggles on a today column that shows you a summary of the current events and possibly another small window displaying tasks (todo: define how to decide which tasks to display). This also allows you to create simple events and tasks
** Clicking on tasks button will show a new task view with all task details available. A sort of "spreadsheet" format.
** Clicking calendar view does not show mail folders and shows essentially like the mockups that Christian has proposed.
** There will be noo merge of tasks into the calendar views at all (or that may be a preference, but this is done to remove the dependency on the spurious nature of dates inside of tasks).

=== Day 2 Sunday ===
* Discussed with mvl and the team and came to the conclusion that the project "head" should be a person that is working on the project full time. We decided that Daniel is the best person for this. Additionally, Clint will be starting at Mozilla next week (primarily working on Firefox). Daniel and Clint will work together to ensure that the project maintains a link to Mozilla and the Mozilla community.
* We will support "Lightning in Sea Monkey" but only if we can do this simply without #ifdef'ing the code in some kind of terrible way.
* Discussed offline issues with mvl. Decided several items about the offline support
** We will start out by better optimizing the recurrence lookups in the storage calendar so that storage calendar can be used as a caching mechanism.
** This will be useful in conjunction with the change-log mechanism that mvl and antonio are working on.
** offline support will also need synchronization interfaces that will encapsulate the conflict handling and will launch any conflict handling UIs that we create.
** There was some discussion on how to get changes down between the cache and the server. We believe that this can be done with etags on CalDav and WebDav. it is done via a specific server call on WCAP and a specific XML command in GData. For flat-file ICS, we are not exactly sure how this would work.
* We decided that we want to support searching for other people's calendars on the same calendar "server" type. That means we'd want to support the ability to find other WCAP or Google or Caldav users. This of course will depend on server capabilities.
** Discussed using a calISearchable interface that providers that have this capability will implement.
* Philipp gave us an update on the GData extension for Google Calendar
** Alarms will be in soon
** Attendees will be in soon - the responses and invitations are sent and processed by google. Changes to the events will come down during normal refresh events.
** Recurrence - Cannot complete this patch because of the way that the provider interface handles the deletions of occurrences. WCAP has the same problem. Essentially, removing a recurrence is seen as a "modify" by the provider. This breaks undo/redo capability because you actually performed a "delete" as far as the server is concerned. So, to undo you have to remember to tell the server to "add" the occurrence back in. '''Need to work out a fix to this, possibly changing the provider interface to handle this.'''
** Comments - Guests (attendees of an event) can leave a comment on an event. It might or might not be useful to reflect these in events. But, there is no mirror for these comments in RFC 2445. One option would be to have the GData provider create an attachment from these comments. This is low priority
** Optimistic Concurrency - Ensure that two users do not change the same event. We need to throw a conflict message if we detect that this has happened. WCAP has the same issue, and simply overwrites what is on the server in this case. This is another item that would be handled by synchronization interfaces that were mentioned w.r.t. the offline support.
** Subscription - Philipp has proposed a subscription dialog to find other people's google calendars that is very similar to the WCAP subscription dialog. The user would enter someone's google email address and the dialog would display the possible google calendars that the user has made public so that you can subscribe to those. You also get to pick the calendar color for the subscribed calendar.
** Group Scheduling - Google has a way to get a FreeBusy feed, and this could be used to populate the new prototype event dialog event F/B information.
* Providers '''must''' have a mechanism to publish their capabilities - perhaps as some kind of flag that can be checked by items like the event dialog. This would enable items to be removed based on what the provider cannot support. This capabilities querying feature will become more and more important as we expand our provider offerings.
* We began product roadmap discussions. We decided that we want a 1.0 '''as soon as possible''' that makes sense from a feature standpoint. Our philosophy here was that we wanted to only take changes that create a workable basic set of functionality that will be rich enough for end users to use, as well as being rich enough for people to create good extensions from.
** An example here is the support for SMS alarms. We decided it was a "nice to have" (NTH) because that support can be easily added either by users (sending SMS email to themselves) or by extension writers once we have the ability to send an email alarm. Therefore, the feature for email alarms will block, but SMS will not block the release. We applied this type of logic to everything.

=== Day 3 Monday ===
* Continued and completed the provider discussion. You can download a spreadsheet of it here. We will also update the wiki roadmap in the future.
* Discussed Test automation with the test automation guru at Sun. Unfortunately the test automation for Star Office will not port into the Mozilla stack. So, we decided to investigate the MochiTest (link) to see if this can be used from within calendar in the same way that it is used in Firefox. Clint and Ulf will take this on. Others are of course welcome to help out in this effort.
* We also decided that until the new UI lands, we should begin writing API tests that use XPCShell. This will be re-discussed tomorrow at the morning quick QA Session. We unfortunately could not invite others to this because of time-constraints of Thornsten, the Sun QA automation guru.

Calendar:Next Release

2007-04-23T11:46:57Z

Lilmatt: /* Navigation */

<div style="border: thin dotted #aaa; padding: 10px;">
'''Do not edit this page unless you are a member of the Mozilla Calendar team!''' To join in the discussion regarding the next calendar release, please see [http://groups.google.com/group/mozilla.dev.apps.calendar/browse_thread/thread/5adb513f0ade569e/e057ef42c42cf042#e057ef42c42cf042 this newsgroup thread].</div>

== Overview==
Sunbird and Lightning are aiming for a simultaneous release of their next version (0.5) in early 2007. This page is meant to provide an overview of the status of that release.

== Schedule ==
* March 12 - string freeze - l10n begins
* March 24 - code freeze (If it's not in by now, it's missing the bus.)
* March 26 - functional testing by #calendar-qa, localizers check their work using nightlies
* March 30 - l10n freeze
* April 02 - first RC
* April 08 - release date or second RC, in case RC 1 was not good enough
* April 14 - release date, in case we need an RC 2

==Key Development Areas==
Items with a red background were originally targetted for version 0.3

===Core Architecture===
Develop Sunbird and Lightning's core architecture to be robust enough for new feature support and ease of future development.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P1 || Editing / viewing of events: Complete the move to using a controller to act on the data, instead of having the views do that directly. || style="color: green; white-space: nowrap;"| Complete
|}

===Performance===
Sunbird and Lightning will display all events and tasks with the correct information and in the correct places.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P1 || Improve performance of storage provider (daniel/mvl) || style="color: blue; white-space: nowrap;" | In progress
|-
| P1 || Improve performance of other providers (Sun team) || style="color: blue;" | In queue
|-
| P1 || Improve performance of views (mickey) || style="color: blue;" | In queue
|}

===Zoom/Scroll===
Sunbird and Lightning should allow easy navigation of calendars.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|<strike>P2</strike>||<strike>Investigate zoom scroll</strike> ||style="color: grey; white-space: nowrap;"| Dropped for 0.5
|}

===Navigation===
Sunbird and Lightning should allow users to move to any display they want.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|style="background-color: #fdd;"| P1 ||style="background-color: #fdd;"| A 'Go to Date' functionality should be exposed. (Lightning) || style="color: green; white-space: nowrap;"| Complete
|}

===Workflow (user experience)===
Sunbird and Lightning should have an easy and intuitive user interface, allowing the user to get things done as effortlessly as possible.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P1 || [[Calendar:Improving_the_Calendar_Views|Determine major pain points]] (christian) || style="color: blue; white-space: nowrap;" | In progress
|-
| P1 || Come up with sketches for solutions (christian) || style="color: blue; white-space: nowrap;" | In progress
|-
| P2 || Implement Agenda View improvements || style="color: red;" | Unknown
|}

===Item Creation/Modification===
Sunbird and Lightning should allow users to create, modify, and interact with tasks and events easily.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|<strike>P1</strike>||<strike>Event vs. Task semantics - Determine what is require for usability and RFC2445 conformance</strike> ||style="color: grey; white-space: nowrap;"| Dropped for 0.5
|-
| P1 || Editting recurring events: "Edit just this" vs. "Edit this and all occurrences after" ||style="color: blue; white-space: nowrap;"| In progress
|-
| P2 || We should be registered to handle .ICS files - Mac||style="color: green; white-space: nowrap;"| Complete
|-
| P2 || We should be registered to handle .ICS files - Windows||style="color: blue; white-space: nowrap;"| In progress
|-
| P2 || We should be registered to handle .ICS files - Unix||style="color: red;"| Unknown
|-
| P2 || We should be registered to handle webcal:// URLs - Mac||style="color: green; white-space: nowrap;"| Complete
|-
| P2 || We should be registered to handle webcal:// URLs - Windows ||style="color: blue; white-space: nowrap;"| In progress
|-
| P2 || We should be registered to handle webcal:// URLs - Unix||style="color: red;"| Unknown
|-
| P2 || Double-clicking an .ICS file should open it (or subscribe, or offer to import it) ||style="color: green; white-space: nowrap;"| Complete
|-
| P2 || Launching a webcal:// URL should add that subscription to the calendar list ||style="color: red;"| Unknown
|-
| P1 || Copying and pasting ICS from the clipboard should create an appropriate new item ||style="color: blue; white-space: no-wrap;"| In progress
|-
| P3 || Copying and pasting hCalendar data from the clipboard should create an appropriate new item ||style="color: red;"| Unknown
|-
| P3 || Copying and pasting events between Lightning and Sunbird should work properly ||style="color: red;"| Unknown
|}

===ICS Export===
Sunbird and Lightning should provide a way for users to export their data in a standards compliant format. This allows users to not need to enter a 'walled garden' when using Sunbird/Lightning

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|style="background-color: #fdd;"| P2 ||style="background-color: #fdd;"| Export of particular items/sets of items should be possible. (Lightning) || style="color: red;"| Unknown
|}

===Conflict Resolution===
Sunbird and Lightning should intelligently handle data conflicts, and present the user with a clear interface for the user to resolve any that it can't do itself.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P2 || Share an .ICS file on the network without dataloss ||style="color: red;"| Unknown
|-
| P2 || Offline storage of remote calendars ||style="color: red;"| Unknown
|-
| P2 || Gracefully handle conflicts between local and network data ||style="color: red;"| Unknown
|}

===Printing===
Sunbird and Lightning should provide an easy to use way for users to get their data in a paper format, through their printer.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|style="background-color: #fdd;"| P1 ||style="background-color: #fdd;"| Printing should be possible. (Lightning) || style="color: green;" | Complete
|-
|style="background-color: #fdd;"| P2 ||style="background-color: #fdd;"| Printing a week's view of items should be possible. || style="color: green;" | Complete
|}

===Publishing===
Sunbird and Lightning should allow users to publish their calendar information to a web server.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|style="background-color: #fdd;"| P2 ||style="background-color: #fdd;"| Publishing a specific set of items should be possible. (Lightning) || style="color: red;" | Unknown
|}

===Get Data In===
Users should be able to get calendar data from multiple sources into the application.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|style="background-color: #fdd;"| P1 ||style="background-color: #fdd;"| Standards compliant data should always be successfully read/preserved. || style="color: red;" | Unknown
|-
|style="background-color: #fdd;"| P1 ||style="background-color: #fdd;"| Errors in standards compliance should be gracefully handled. || style="color: red;" | Unknown
|-
| P2 || Import data from the user's existing calendar applications || style="color: green; white-space: nowrap;" | Complete
|}

===Thunderbird Integration===
Lightning should be integrated as seamlessly as possible into Thunderbird.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P2 || Integrate into Thunderbird's undo/redo queue || style="color: green;" | Complete
|-
| P2 || Integrate into Thunderbird's copy/paste || style="color: green;" | Complete
|-
| P2 || Integrate into Thunderbird's print command || style="color: green;" | Complete
|}

===Calendar Interoperation===
Users should be able to send and receive meeting invitations received via email.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P1 || Allow sending iMIP/iTIP invitations. || style="color: green;" | Complete
|-
| P1 || Allow sending decline/accept iMIP/iTIP responses. || style="color: green;" | Complete
|}

===Backup===
Sunbird and Lightning should provide functionality for users to easily backup and restore their data.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P3 || Make backups of data || style="color: red;" | Unknown
|}

===Dataloss===
Users should be able to use Sunbird/Lightning with confidence that their data will be preserved.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|style="background-color: #fdd;"| P1 ||style="background-color: #fdd;"| Subscribing to a calendar with unexpected data should preserve the data || style="color: red;" | Unknown
|-
|style="background-color: #fdd;"| P2 ||style="background-color: #fdd;"| Standards compliant data should be preserved when edited. || style="color: red;" | Unknown
|}

===Misc Regressions===
Users upgrading from past versions should not notice significant loss of functionality/usability.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P1 || "Misc Regressions" is provided to give it visibility during discussions. Individual elements do not exist at this time.
|}

===User pain-points from 0.3===
Wherever possible, we should attempt to address pain-points in 0.3 identified by our users. These were not determined scientifically. They're a "gut feeling" based on IRC, bugmail, and newsgroups.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee;"| '''Bug(s)'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee;"| '''Status'''
|-
|{{bug|349048}}||<strike>Having CalExt installed</strike>||FIXED
|-
|{{bug|349520}}||<strike>24 hour views (and no way to make them smaller)</strike>||FIXED
|-
|{{bug|345643}}||<strike>Date formatting (MM/DD vs DD/MM)</strike>||FIXED
|-
|{{bug|343792}}||<strike>Data import errors - invalid or atypical ICS</strike>||FIXED
|-
|{{bug|354951}}||Data import errors - charset||
|-
|{{bug|310258}}||<strike>Hide completed tasks is missing from Lightning</strike>||FIXED
|}

Calendar:Hamburg F2F Meeting

2007-03-21T18:03:16Z

Lilmatt: /* Who */

Information regarding the 2. Mozilla Calendar Developers Face-to-Face Meeting
__NOTOC__
=Who=
<table border="0" cellspacing="5" cellpadding="0">
<tr>
<td colspan="2">'''Tentative Attendees:'''</td>
</tr><tr>
<td valign="top">
*Matthew Willis (lilmatt)
</td><td valign="top">
*Your name here
</td>
</tr>
</table>

=Where=
'''Meeting:''' 
Sun Microsystems GmbH 
Nagelsweg 55, 
20097 Hamburg, Germany 

[http://www.google.com/maps?hl=en&client=firefox-a&rls=org.mozilla:en-US:official&hs=rEP&q=sun+microsystems&near=Hamburg,+Germany&sa=X&oi=local&ct=title Map]]

'''Lodging:''' 

TBD

=When=
<table border="0" cellspacing="0" cellpadding="4">
<tr>
<td align="right">From:</td>
<td align="left">Saturday</td><td>2007-04-21</td><td>TBD</td>
</tr><tr>
<td align="right">To:</td>
<td align="left">Tuesday</td><td>2007-04-24</td><td>afternoon</td>
</tr>
</table>

== Agenda ==
=== Day 1 (Saturday) ===
=== Day 2 (Sunday) ===
=== Day 3 (Monday) ===
=== Day 4 (Tuesday) ===

Calendar:Status Meetings:2007-03-21

2007-03-21T12:58:26Z

Lilmatt: /* Agenda Items */

__NOTOC__
<<[[Calendar:Status Meetings:2007-03-14| previous meeting]] | [[Calendar:Status Meetings|index]] | [[Calendar:Status Meetings:2007-03-28| next meeting >>]]

== Meeting Details ==
*[http://www.timeanddate.com/worldclock/meetingdetails.html?year=2007&month=3&day=21&hour=17&min=0&sec=0&p1=16&p2=37&p3=64&p4=179&p5=224 Wednesday, March 21th, 17:00 UTC]
** '''U.S. FOLKS: NOTE THE TIME!'''
* Phone meeting
* Join #calendar-mtg on irc.mozilla.org for attendance

=== Telephone Info ===
* Toll free numbers
** US/Canada: 800 867 8609
** Netherlands: 08002658232
** Germany: 08001014546
** Poland: 008001114706
** Sun: x44444
** More numbers (toll/toll free): [https://g8.cfer.com/g8.jsp?an=8008678609&ac=6064554&login=true Sun Worldwide Ready-Access numbers]
*Access Code
** 3646989
*Conference controls
** *6 mute line
** *7 unmute line
* Each time you say something, please say your name first so people know who's speaking

=== Agenda Items ===
* 0.5 Status Update
** Check out [[Calendar:Roadmap]] and [[Calendar:Next_Release]] for more details.
** Bugs we may want, but would break string freeze: {{bug|362698}} and {{bug|374757}}
* F2F Meeting Logistics
** Which hotel? Who's renting a car? etc.

Calendar:Status Meetings:2007-03-21

2007-03-21T12:17:46Z

Lilmatt: /* Agenda Items */

__NOTOC__
<<[[Calendar:Status Meetings:2007-03-14| previous meeting]] | [[Calendar:Status Meetings|index]] | [[Calendar:Status Meetings:2007-03-28| next meeting >>]]

== Meeting Details ==
*[http://www.timeanddate.com/worldclock/meetingdetails.html?year=2007&month=3&day=21&hour=17&min=0&sec=0&p1=16&p2=37&p3=64&p4=179&p5=224 Wednesday, March 21th, 17:00 UTC]
** '''U.S. FOLKS: NOTE THE TIME!'''
* Phone meeting
* Join #calendar-mtg on irc.mozilla.org for attendance

=== Telephone Info ===
* Toll free numbers
** US/Canada: 800 867 8609
** Netherlands: 08002658232
** Germany: 08001014546
** Poland: 008001114706
** Sun: x44444
** More numbers (toll/toll free): [https://g8.cfer.com/g8.jsp?an=8008678609&ac=6064554&login=true Sun Worldwide Ready-Access numbers]
*Access Code
** 3646989
*Conference controls
** *6 mute line
** *7 unmute line
* Each time you say something, please say your name first so people know who's speaking

=== Agenda Items ===
* 0.5 Status Update
** Check out [[Calendar:Roadmap]] and [[Calendar:Next_Release]] for more details.
* F2F Meeting Logistics
** Which hotel? Who's renting a car? etc.

Calendar:Calendar View

2007-03-16T13:03:45Z

Lilmatt: Reverting to previous version

= Lightning Calendar View Proposal =

'''State:''' Draft 
'''Author:''' Christian Jansen 
'''Last Change:''' --[[User:Chris281|Chris]] 23:35, 11 May 2006 (PDT) 

The calendar view is the most prominent part of Lightning. Users have direct access to several panes.

===One Day View===
===Work Week View===
[[Image:5-Day.png|Proposal of an improved week view]]

===Week View===
===Month View===
[[Image:Month-View.png|Proposal of an improved month view]]

=== Year View===
* A Month Pane containing a control called Mini Month for providing an overview about a whole month.
* The Calendar Subscription Pane gives users an overview about calendar subscriptions and about users own calendar(s).
* The Agenda Pane provides a cumulative view of To-Dos & Events for the current day.
* The To-Do Pane lists the To-Dos of today, the upcoming days & weeks.

=== Visualization of Conflicting Events ===

=== Calendar View Items ===

Figure 2 gives an impression how the Calendar could look like.

Details of each pane, and other window elements are described in detail in the sections below. The figure below shall provide an overview where each pane is located.
[[Image:Areas.png|thumb|Overview where each pane is located]]

= General Thoughts =
The Calendar View provides a dynamic layout, thus each pane can be scaled in size.
Each pane can be closed. This applies not to the main Calendar Pane.
== Menu Bar ==
=== File ===
=== Edit ===
=== View ===
=== Calendar ===
=== Tools ===
=== Help ===

== Tool Bar ==
=== New Event ===
=== New Task ===
=== Print ===
=== Delete ===
=== Go To Today ===
=== Address Book ===

== Mini Month Pane==
The Mini Month Pane comprises as minimum one Mini Month

[[Image:minimonth.png|thumb|Lightning Mini Month]]

Resizing the Mini Month Pane shows up additional Mini Months.

+----------------+ +----------------+
| < March 2006 | | April 2006 > |
| S M D M D F S | | S M D M D F S |
| 1 2 3 4 5 6 7 | | 1 2 3 4 5 6 7 |
| ... | | ... |
+----------------+ +----------------+
+----------------+ +----------------+
| June 2006 | | July 2006 |
| S M D M D F S | | S M D M D F S |
| 1 2 3 4 5 6 7 | | 1 2 3 4 5 6 7 |
| ... | | ... |
+----------------+ +----------------+

The title bar of the Mini Month Pane provides information about the time zone specified in Lightning

* A double click on the Time Zone info may open a Time Zone Config dialog

=== The Mini Month ===

A Mini Month should allow to:

* Jump with one click from one month to another
* Direct access to different days
* Direct access to different months
* Direct access to different years
* Jump with one click to the current day
* Highlighting of the current day
* Highlighting of the current week
* Highlighting of the current month
* Highlighting of days containg an event
* The control should allow to display previous/upcoming day/month in a different color
* It should always display 6 week rows (this prevents the layout from jumping)
* It should allow to preview parts of the privious and the next month
* It should reflect first day of the week configurations:
e.g: "'''Mon''', Tue, Wed, Thu, Fri, Sat, Sun" or "'''Sun''', Mon, Tue, Wed, Thu, Fri, Sat"
* The control should '''not''' change its size while switching between months.

==== Syncronisation Between Mini Month & Calendar View ====

In general the mini month and the calendar views should run in sync. For example, if the user changes the month from May to June in the Calendar View the Mini Month should reflect that change.

The only exception are four buttons. These are located in the upper left and right of the Mini Month and are intended to preview month. Given that changing the Month from May to June by using the Navigation wouldn't have any effect on the Calendar View.

[[Image:nav-arrows.png|Navigation Arrows]]

* Navigation in Calendar View should sync the Mini Month
* The date range displayed in the Calendar View (Day, Week, Working Week, Month) should be highlighted in the Mini Month.
** '''In Calendars Day View''': The corresponding Mini Month day needs to be highlighted.
** '''In Calendars Week View''': The corresponding days of the Mini Month week needs to be highlighted.
** '''In Calendars Working Week View''': The corresponding days of the Mini Month working week needs to be highlighted.
** '''In Calendars Month View''': The corresponding days of the Mini Month month needs to be highlighted.
* Clicking the Mini Month "Go To Today" button selects the current day in the Mini Month and chages the view in the calendar to the current date.
* Selecting one explicit Day, Week, Working Week, Month, Year should change the date range displayed in the Calendar View.

==== The Year Panel ====
The Year Panel can be reached by clicking the Month & Year area of the Mini Month.
The panel allows users to navigate from one year to another by using the left or right buttons.

In addition it should be possible to navigate quickly to a specific month within the next 12 month from the current month on.

The panel should indicate month which relate to the previous or the next year differently.

The figure below shows a proposal of the Year Panel.

[[Image:Mini-month_with_year_panel.png]]

== Calendar Subscription Pane ==

The Calendar Subscription Pane lists all subscribed calendars. Subscribed calendars can be stored locally or remotely. The graphical representation should be in both cases the same.

From the Pane users should have the possibility to

* Publish calendars
* Subscribe calendars
* Create calenders
* Create calendars groups
* Manually update subscribed calenders
* Notify users that a calendar has been published
* Switch visibility of calendars on or off
* Delete calendars
* Move calendars from one group to another

Creation and the subscription of calendars shaould also be intergrated into the menus & maybe in the tool bar.

The figure below shows a rough sketch of the Calendars & Groups
+-------------------------+
| My Calendars X |
+-------------------------+
| [X] [Green ] Work |
| [+] [X] [Blue ] Fares |
| [-] [X] [Red ] Team |
| [X] [Black ] Jeff |
| [X] [Mauve ] Bob |
| [X] [Yellow] Lisa |
+-------------------------+

The figure below gives a more detailed impression of the features set which is needed for creating, subscribing, and publishing calendars.

[[Image:Calendar-Subscribtions-Map.png|thumb|600px]]

== Calendar Pane ==
=== Tabs ===
=== Day, Week, Month Informer ===
=== All Day Event Pane ===
=== Time Scale ===
== Search Field ==
== Agenda Pane ==
== To-Do Pane ==
== Status Bar ==

Calendar:Next Release

2007-03-16T12:56:18Z

Lilmatt: Reverting to previous version

<div style="border: thin dotted #aaa; padding: 10px;">
'''Please don't edit this page unless you are a member of the calendar team.''' To join in the discussion regarding the next calendar release, please see [http://groups.google.com/group/mozilla.dev.apps.calendar/browse_thread/thread/5adb513f0ade569e/e057ef42c42cf042#e057ef42c42cf042 this newsgroup thread].</div>

== Overview==
Sunbird and Lightning are aiming for a simultaneous release of their next version (0.5) in early 2007. This page is meant to provide an overview of the status of that release.

== Schedule ==
* March 12 - string freeze - l10n begins
* March 24 - code freeze (If it's not in by now, it's missing the bus.)
* March 26 - functional testing by #calendar-qa, localizers check their work using nightlies
* March 30 - l10n freeze
* April 02 - first RC
* April 08 - release date or second RC, in case RC 1 was not good enough
* April 14 - release date, in case we need an RC 2

==Key Development Areas==
Items with a red background were originally targetted for version 0.3

===Core Architecture===
Develop Sunbird and Lightning's core architecture to be robust enough for new feature support and ease of future development.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P1 || Editing / viewing of events: Complete the move to using a controller to act on the data, instead of having the views do that directly. || style="color: green; white-space: nowrap;"| Complete
|}

===Performance===
Sunbird and Lightning will display all events and tasks with the correct information and in the correct places.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P1 || Improve performance of storage provider (daniel/mvl) || style="color: blue; white-space: nowrap;" | In progress
|-
| P1 || Improve performance of other providers (Sun team) || style="color: blue;" | In queue
|-
| P1 || Improve performance of views (mickey) || style="color: blue;" | In queue
|}

===Zoom/Scroll===
Sunbird and Lightning should allow easy navigation of calendars.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|<strike>P2</strike>||<strike>Investigate zoom scroll</strike> ||style="color: grey; white-space: nowrap;"| Dropped for 0.5
|}

===Navigation===
Sunbird and Lightning should allow users to move to any display they want.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|style="background-color: #fdd;"| P1 ||style="background-color: #fdd;"| A 'Go to Date' functionality should be exposed. (Lightning) || style="color: blue; white-space: nowrap;"| In progress
|}

===Workflow (user experience)===
Sunbird and Lightning should have an easy and intuitive user interface, allowing the user to get things done as effortlessly as possible.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P1 || [[Calendar:Improving_the_Calendar_Views|Determine major pain points]] (christian) || style="color: blue; white-space: nowrap;" | In progress
|-
| P1 || Come up with sketches for solutions (christian) || style="color: blue; white-space: nowrap;" | In progress
|-
| P2 || Implement Agenda View improvements || style="color: red;" | Unknown
|}

===Item Creation/Modification===
Sunbird and Lightning should allow users to create, modify, and interact with tasks and events easily.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|<strike>P1</strike>||<strike>Event vs. Task semantics - Determine what is require for usability and RFC2445 conformance</strike> ||style="color: grey; white-space: nowrap;"| Dropped for 0.5
|-
| P1 || Editting recurring events: "Edit just this" vs. "Edit this and all occurrences after" ||style="color: blue; white-space: nowrap;"| In progress
|-
| P2 || We should be registered to handle .ICS files - Mac||style="color: green; white-space: nowrap;"| Complete
|-
| P2 || We should be registered to handle .ICS files - Windows||style="color: blue; white-space: nowrap;"| In progress
|-
| P2 || We should be registered to handle .ICS files - Unix||style="color: red;"| Unknown
|-
| P2 || We should be registered to handle webcal:// URLs - Mac||style="color: green; white-space: nowrap;"| Complete
|-
| P2 || We should be registered to handle webcal:// URLs - Windows ||style="color: blue; white-space: nowrap;"| In progress
|-
| P2 || We should be registered to handle webcal:// URLs - Unix||style="color: red;"| Unknown
|-
| P2 || Double-clicking an .ICS file should open it (or subscribe, or offer to import it) ||style="color: green; white-space: nowrap;"| Complete
|-
| P2 || Launching a webcal:// URL should add that subscription to the calendar list ||style="color: red;"| Unknown
|-
| P1 || Copying and pasting ICS from the clipboard should create an appropriate new item ||style="color: blue; white-space: no-wrap;"| In progress
|-
| P3 || Copying and pasting hCalendar data from the clipboard should create an appropriate new item ||style="color: red;"| Unknown
|-
| P3 || Copying and pasting events between Lightning and Sunbird should work properly ||style="color: red;"| Unknown
|}

===ICS Export===
Sunbird and Lightning should provide a way for users to export their data in a standards compliant format. This allows users to not need to enter a 'walled garden' when using Sunbird/Lightning

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|style="background-color: #fdd;"| P2 ||style="background-color: #fdd;"| Export of particular items/sets of items should be possible. (Lightning) || style="color: red;"| Unknown
|}

===Conflict Resolution===
Sunbird and Lightning should intelligently handle data conflicts, and present the user with a clear interface for the user to resolve any that it can't do itself.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P2 || Share an .ICS file on the network without dataloss ||style="color: red;"| Unknown
|-
| P2 || Offline storage of remote calendars ||style="color: red;"| Unknown
|-
| P2 || Gracefully handle conflicts between local and network data ||style="color: red;"| Unknown
|}

===Printing===
Sunbird and Lightning should provide an easy to use way for users to get their data in a paper format, through their printer.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|style="background-color: #fdd;"| P1 ||style="background-color: #fdd;"| Printing should be possible. (Lightning) || style="color: green;" | Complete
|-
|style="background-color: #fdd;"| P2 ||style="background-color: #fdd;"| Printing a week's view of items should be possible. || style="color: green;" | Complete
|}

===Publishing===
Sunbird and Lightning should allow users to publish their calendar information to a web server.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|style="background-color: #fdd;"| P2 ||style="background-color: #fdd;"| Publishing a specific set of items should be possible. (Lightning) || style="color: red;" | Unknown
|}

===Get Data In===
Users should be able to get calendar data from multiple sources into the application.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|style="background-color: #fdd;"| P1 ||style="background-color: #fdd;"| Standards compliant data should always be successfully read/preserved. || style="color: red;" | Unknown
|-
|style="background-color: #fdd;"| P1 ||style="background-color: #fdd;"| Errors in standards compliance should be gracefully handled. || style="color: red;" | Unknown
|-
| P2 || Import data from the user's existing calendar applications || style="color: green; white-space: nowrap;" | Complete
|}

===Thunderbird Integration===
Lightning should be integrated as seamlessly as possible into Thunderbird.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P2 || Integrate into Thunderbird's undo/redo queue || style="color: green;" | Complete
|-
| P2 || Integrate into Thunderbird's copy/paste || style="color: green;" | Complete
|-
| P2 || Integrate into Thunderbird's print command || style="color: green;" | Complete
|}

===Calendar Interoperation===
Users should be able to send and receive meeting invitations received via email.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P1 || Allow sending iMIP/iTIP invitations. || style="color: green;" | Complete
|-
| P1 || Allow sending decline/accept iMIP/iTIP responses. || style="color: green;" | Complete
|}

===Backup===
Sunbird and Lightning should provide functionality for users to easily backup and restore their data.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P3 || Make backups of data || style="color: red;" | Unknown
|}

===Dataloss===
Users should be able to use Sunbird/Lightning with confidence that their data will be preserved.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|style="background-color: #fdd;"| P1 ||style="background-color: #fdd;"| Subscribing to a calendar with unexpected data should preserve the data || style="color: red;" | Unknown
|-
|style="background-color: #fdd;"| P2 ||style="background-color: #fdd;"| Standards compliant data should be preserved when edited. || style="color: red;" | Unknown
|}

===Misc Regressions===
Users upgrading from past versions should not notice significant loss of functionality/usability.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P1 || "Misc Regressions" is provided to give it visibility during discussions. Individual elements do not exist at this time.
|}

===User pain-points from 0.3===
Wherever possible, we should attempt to address pain-points in 0.3 identified by our users. These were not determined scientifically. They're a "gut feeling" based on IRC, bugmail, and newsgroups.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee;"| '''Bug(s)'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee;"| '''Status'''
|-
|{{bug|349048}}||<strike>Having CalExt installed</strike>||FIXED
|-
|{{bug|349520}}||<strike>24 hour views (and no way to make them smaller)</strike>||FIXED
|-
|{{bug|345643}}||<strike>Date formatting (MM/DD vs DD/MM)</strike>||FIXED
|-
|{{bug|343792}}||<strike>Data import errors - invalid or atypical ICS</strike>||FIXED
|-
|{{bug|354951}}||Data import errors - charset||
|-
|{{bug|310258}}||<strike>Hide completed tasks is missing from Lightning</strike>||FIXED
|}

Calendar:Next Release

2007-03-14T21:45:21Z

Lilmatt:

Calendar:Status

2007-03-14T21:42:47Z

Lilmatt:

#REDIRECT [[Calendar:Status_Meetings:2007-03-21]]

Calendar:Status Meetings:2007-03-21

2007-03-14T21:42:22Z

Lilmatt:

__NOTOC__
<<[[Calendar:Status Meetings:2007-03-14| previous meeting]] | [[Calendar:Status Meetings|index]] | [[Calendar:Status Meetings:2007-03-28| next meeting >>]]

== Meeting Details ==
*[http://www.timeanddate.com/worldclock/meetingtime.html?month=3&day=21&year=2007&pa=16&pa=37&pa=64&pa=179&pa=224 Wednesday, March 21th, 17:00 UTC]
** '''U.S. FOLKS: NOTE THE TIME!'''
* Phone meeting
* Join #calendar-mtg on irc.mozilla.org for attendance

=== Telephone Info ===
* Toll free numbers
** US/Canada: 800 867 8609
** Netherlands: 08002658232
** Germany: 08001014546
** Poland: 008001114706
** Sun: x44444
** More numbers (toll/toll free): [https://g8.cfer.com/g8.jsp?an=8008678609&ac=6064554&login=true Sun Worldwide Ready-Access numbers]
*Access Code
** 3646989
*Conference controls
** *6 mute line
** *7 unmute line
* Each time you say something, please say your name first so people know who's speaking

=== Agenda Items ===
* 0.5 Status Update
** Check out [[Calendar:Roadmap]] and [[Calendar:Next_Release]] for more details.

Calendar:Status Meetings:2007-03-14

2007-03-14T21:39:41Z

Lilmatt: /* Agenda Items */

__NOTOC__
<<[[Calendar:Status Meetings:2007-03-07| previous meeting]] | [[Calendar:Status Meetings|index]] | [[Calendar:Status Meetings:2007-03-21| next meeting >>]]

== Meeting Details ==
*[http://www.timeanddate.com/worldclock/meetingtime.html?month=3&day=14&year=2007&pa=16&pa=37&pa=64&pa=179&pa=224 Wednesday, March 14th, 16:00 UTC]
* Phone meeting
* Join #calendar-mtg on irc.mozilla.org for attendance

=== Telephone Info ===
* Toll free numbers
** US/Canada: 800 867 8609
** Netherlands: 08002658232
** Germany: 08001014546
** Poland: 008001114706
** Sun: x44444
** More numbers (toll/toll free): [https://g8.cfer.com/g8.jsp?an=8008678609&ac=6064554&login=true Sun Worldwide Ready-Access numbers]
*Access Code
** 3646989
*Conference controls
** *6 mute line
** *7 unmute line
* Each time you say something, please say your name first so people know who's speaking

=== Agenda Items ===
* 0.5 Status Update
** Check out [[Calendar:Roadmap]] and [[Calendar:Next_Release]] for more details.

=== Notes ===
* Only lilmatt and mickey were around. mickey will look at the blocking list and see if he can find more items he can pick off.

Calendar:Status Meetings:2007-03-14

2007-03-14T15:49:48Z

Lilmatt: /* Meeting Details */

Calendar:Status

2007-03-14T15:47:49Z

Lilmatt:

#REDIRECT [[Calendar:Status_Meetings:2007-03-14]]

Calendar:Status Meetings:2007-03-14

2007-03-14T15:47:12Z

Lilmatt:

__NOTOC__
<<[[Calendar:Status Meetings:2007-03-07| previous meeting]] | [[Calendar:Status Meetings|index]] | [[Calendar:Status Meetings:2007-03-21| next meeting >>]]

== Meeting Details ==
*[http://www.timeanddate.com/worldclock/meetingtime.html?month=3&day=14&year=2007&pa=16&pa=37&pa=64&pa=179&pa=224 Wednesday, March 14th, 17:00 UTC]
* Phone meeting
* Join #calendar-mtg on irc.mozilla.org for attendance

=== Telephone Info ===
* Toll free numbers
** US/Canada: 800 867 8609
** Netherlands: 08002658232
** Germany: 08001014546
** Poland: 008001114706
** Sun: x44444
** More numbers (toll/toll free): [https://g8.cfer.com/g8.jsp?an=8008678609&ac=6064554&login=true Sun Worldwide Ready-Access numbers]
*Access Code
** 3646989
*Conference controls
** *6 mute line
** *7 unmute line
* Each time you say something, please say your name first so people know who's speaking

=== Agenda Items ===
* 0.5 Status Update
** Check out [[Calendar:Roadmap]] and [[Calendar:Next_Release]] for more details.

Calendar:Next Release

2007-03-14T15:45:11Z

Lilmatt: /* Item Creation/Modification */

<div style="border: thin dotted #aaa; padding: 10px;">
'''Please don't edit this page unless you are a member of the calendar team.''' To join in the discussion regarding the next calendar release, please see [http://groups.google.com/group/mozilla.dev.apps.calendar/browse_thread/thread/5adb513f0ade569e/e057ef42c42cf042#e057ef42c42cf042 this newsgroup thread].</div>

== Overview==
Sunbird and Lightning are aiming for a simultaneous release of their next version (0.5) in early 2007. This page is meant to provide an overview of the status of that release.

Items with a red background were originally targetted for version 0.3

==Key Development Areas==

===Core Architecture===
Develop Sunbird and Lightning's core architecture to be robust enough for new feature support and ease of future development.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P1 || Editing / viewing of events: Complete the move to using a controller to act on the data, instead of having the views do that directly. || style="color: green; white-space: nowrap;"| Complete
|}

===Performance===
Sunbird and Lightning will display all events and tasks with the correct information and in the correct places.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P1 || Improve performance of storage provider (daniel/mvl) || style="color: blue; white-space: nowrap;" | In progress
|-
| P1 || Improve performance of other providers (Sun team) || style="color: blue;" | In queue
|-
| P1 || Improve performance of views (mickey) || style="color: blue;" | In queue
|}

===Zoom/Scroll===
Sunbird and Lightning should allow easy navigation of calendars.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|<strike>P2</strike>||<strike>Investigate zoom scroll</strike> ||style="color: grey; white-space: nowrap;"| Dropped for 0.5
|}

===Navigation===
Sunbird and Lightning should allow users to move to any display they want.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|style="background-color: #fdd;"| P1 ||style="background-color: #fdd;"| A 'Go to Date' functionality should be exposed. (Lightning) || style="color: blue; white-space: nowrap;"| In progress
|}

===Workflow (user experience)===
Sunbird and Lightning should have an easy and intuitive user interface, allowing the user to get things done as effortlessly as possible.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P1 || [[Calendar:Improving_the_Calendar_Views|Determine major pain points]] (christian) || style="color: blue; white-space: nowrap;" | In progress
|-
| P1 || Come up with sketches for solutions (christian) || style="color: blue; white-space: nowrap;" | In progress
|-
| P2 || Implement Agenda View improvements || style="color: red;" | Unknown
|}

===Item Creation/Modification===
Sunbird and Lightning should allow users to create, modify, and interact with tasks and events easily.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|<strike>P1</strike>||<strike>Event vs. Task semantics - Determine what is require for usability and RFC2445 conformance</strike> ||style="color: grey; white-space: nowrap;"| Dropped for 0.5
|-
| P1 || Editting recurring events: "Edit just this" vs. "Edit this and all occurrences after" ||style="color: blue; white-space: nowrap;"| In progress
|-
| P2 || We should be registered to handle .ICS files - Mac||style="color: green; white-space: nowrap;"| Complete
|-
| P2 || We should be registered to handle .ICS files - Windows||style="color: blue; white-space: nowrap;"| In progress
|-
| P2 || We should be registered to handle .ICS files - Unix||style="color: red;"| Unknown
|-
| P2 || We should be registered to handle webcal:// URLs - Mac||style="color: green; white-space: nowrap;"| Complete
|-
| P2 || We should be registered to handle webcal:// URLs - Windows ||style="color: blue; white-space: nowrap;"| In progress
|-
| P2 || We should be registered to handle webcal:// URLs - Unix||style="color: red;"| Unknown
|-
| P2 || Double-clicking an .ICS file should open it (or subscribe, or offer to import it) ||style="color: green; white-space: nowrap;"| Complete
|-
| P2 || Launching a webcal:// URL should add that subscription to the calendar list ||style="color: red;"| Unknown
|-
| P1 || Copying and pasting ICS from the clipboard should create an appropriate new item ||style="color: blue; white-space: no-wrap;"| In progress
|-
| P3 || Copying and pasting hCalendar data from the clipboard should create an appropriate new item ||style="color: red;"| Unknown
|-
| P3 || Copying and pasting events between Lightning and Sunbird should work properly ||style="color: red;"| Unknown
|}

===ICS Export===
Sunbird and Lightning should provide a way for users to export their data in a standards compliant format. This allows users to not need to enter a 'walled garden' when using Sunbird/Lightning

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|style="background-color: #fdd;"| P2 ||style="background-color: #fdd;"| Export of particular items/sets of items should be possible. (Lightning) || style="color: red;"| Unknown
|}

===Conflict Resolution===
Sunbird and Lightning should intelligently handle data conflicts, and present the user with a clear interface for the user to resolve any that it can't do itself.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P2 || Share an .ICS file on the network without dataloss ||style="color: red;"| Unknown
|-
| P2 || Offline storage of remote calendars ||style="color: red;"| Unknown
|-
| P2 || Gracefully handle conflicts between local and network data ||style="color: red;"| Unknown
|}

===Printing===
Sunbird and Lightning should provide an easy to use way for users to get their data in a paper format, through their printer.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|style="background-color: #fdd;"| P1 ||style="background-color: #fdd;"| Printing should be possible. (Lightning) || style="color: green;" | Complete
|-
|style="background-color: #fdd;"| P2 ||style="background-color: #fdd;"| Printing a week's view of items should be possible. || style="color: green;" | Complete
|}

===Publishing===
Sunbird and Lightning should allow users to publish their calendar information to a web server.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|style="background-color: #fdd;"| P2 ||style="background-color: #fdd;"| Publishing a specific set of items should be possible. (Lightning) || style="color: red;" | Unknown
|}

===Get Data In===
Users should be able to get calendar data from multiple sources into the application.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|style="background-color: #fdd;"| P1 ||style="background-color: #fdd;"| Standards compliant data should always be successfully read/preserved. || style="color: red;" | Unknown
|-
|style="background-color: #fdd;"| P1 ||style="background-color: #fdd;"| Errors in standards compliance should be gracefully handled. || style="color: red;" | Unknown
|-
| P2 || Import data from the user's existing calendar applications || style="color: green; white-space: nowrap;" | Complete
|}

===Thunderbird Integration===
Lightning should be integrated as seamlessly as possible into Thunderbird.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P2 || Integrate into Thunderbird's undo/redo queue || style="color: green;" | Complete
|-
| P2 || Integrate into Thunderbird's copy/paste || style="color: green;" | Complete
|-
| P2 || Integrate into Thunderbird's print command || style="color: green;" | Complete
|}

===Calendar Interoperation===
Users should be able to send and receive meeting invitations received via email.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P1 || Allow sending iMIP/iTIP invitations. || style="color: green;" | Complete
|-
| P1 || Allow sending decline/accept iMIP/iTIP responses. || style="color: green;" | Complete
|}

===Backup===
Sunbird and Lightning should provide functionality for users to easily backup and restore their data.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P3 || Make backups of data || style="color: red;" | Unknown
|}

===Dataloss===
Users should be able to use Sunbird/Lightning with confidence that their data will be preserved.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|style="background-color: #fdd;"| P1 ||style="background-color: #fdd;"| Subscribing to a calendar with unexpected data should preserve the data || style="color: red;" | Unknown
|-
|style="background-color: #fdd;"| P2 ||style="background-color: #fdd;"| Standards compliant data should be preserved when edited. || style="color: red;" | Unknown
|}

===Misc Regressions===
Users upgrading from past versions should not notice significant loss of functionality/usability.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P1 || "Misc Regressions" is provided to give it visibility during discussions. Individual elements do not exist at this time.
|}

===User pain-points from 0.3===
Wherever possible, we should attempt to address pain-points in 0.3 identified by our users. These were not determined scientifically. They're a "gut feeling" based on IRC, bugmail, and newsgroups.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee;"| '''Bug(s)'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee;"| '''Status'''
|-
|{{bug|349048}}||<strike>Having CalExt installed</strike>||FIXED
|-
|{{bug|349520}}||<strike>24 hour views (and no way to make them smaller)</strike>||FIXED
|-
|{{bug|345643}}||<strike>Date formatting (MM/DD vs DD/MM)</strike>||FIXED
|-
|{{bug|343792}}||<strike>Data import errors - invalid or atypical ICS</strike>||FIXED
|-
|{{bug|354951}}||Data import errors - charset||
|-
|{{bug|310258}}||<strike>Hide completed tasks is missing from Lightning</strike>||FIXED
|}

Calendar:Next Release

2007-03-14T15:43:31Z

Lilmatt: /* User pain-points from 0.3 */

<div style="border: thin dotted #aaa; padding: 10px;">
'''Please don't edit this page unless you are a member of the calendar team.''' To join in the discussion regarding the next calendar release, please see [http://groups.google.com/group/mozilla.dev.apps.calendar/browse_thread/thread/5adb513f0ade569e/e057ef42c42cf042#e057ef42c42cf042 this newsgroup thread].</div>

== Overview==
Sunbird and Lightning are aiming for a simultaneous release of their next version (0.5) in early 2007. This page is meant to provide an overview of the status of that release.

Items with a red background were originally targetted for version 0.3

==Key Development Areas==

===Core Architecture===
Develop Sunbird and Lightning's core architecture to be robust enough for new feature support and ease of future development.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P1 || Editing / viewing of events: Complete the move to using a controller to act on the data, instead of having the views do that directly. || style="color: green; white-space: nowrap;"| Complete
|}

===Performance===
Sunbird and Lightning will display all events and tasks with the correct information and in the correct places.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P1 || Improve performance of storage provider (daniel/mvl) || style="color: blue; white-space: nowrap;" | In progress
|-
| P1 || Improve performance of other providers (Sun team) || style="color: blue;" | In queue
|-
| P1 || Improve performance of views (mickey) || style="color: blue;" | In queue
|}

===Zoom/Scroll===
Sunbird and Lightning should allow easy navigation of calendars.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|<strike>P2</strike>||<strike>Investigate zoom scroll</strike> ||style="color: grey; white-space: nowrap;"| Dropped for 0.5
|}

===Navigation===
Sunbird and Lightning should allow users to move to any display they want.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|style="background-color: #fdd;"| P1 ||style="background-color: #fdd;"| A 'Go to Date' functionality should be exposed. (Lightning) || style="color: blue; white-space: nowrap;"| In progress
|}

===Workflow (user experience)===
Sunbird and Lightning should have an easy and intuitive user interface, allowing the user to get things done as effortlessly as possible.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P1 || [[Calendar:Improving_the_Calendar_Views|Determine major pain points]] (christian) || style="color: blue; white-space: nowrap;" | In progress
|-
| P1 || Come up with sketches for solutions (christian) || style="color: blue; white-space: nowrap;" | In progress
|-
| P2 || Implement Agenda View improvements || style="color: red;" | Unknown
|}

===Item Creation/Modification===
Sunbird and Lightning should allow users to create, modify, and interact with tasks and events easily.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|<strike>P1</strike>||<strike>Event vs. Task semantics - Determine what is require for usability and RFC2445 conformance</strike> ||style="color: grey; white-space: nowrap;"| Dropped for 0.5
|-
| P1 || Editting recurring events: "Edit just this" vs. "Edit this and all occurrences after" ||style="color: blue; white-space: nowrap;"| In progress
|-
| P2 || We should be registered to handle .ICS files - Mac||style="color: blue; white-space: nowrap;"| In progress
|-
| P2 || We should be registered to handle .ICS files - Windows||style="color: blue; white-space: nowrap;"| In progress
|-
| P2 || We should be registered to handle .ICS files - Unix||style="color: red;"| Unknown
|-
| P2 || We should be registered to handle webcal:// URLs - Mac||style="color: blue; white-space: nowrap;"| In progress
|-
| P2 || We should be registered to handle webcal:// URLs - Windows ||style="color: blue; white-space: nowrap;"| In progress
|-
| P2 || We should be registered to handle webcal:// URLs - Unix||style="color: red;"| Unknown
|-
| P2 || Double-clicking an .ICS file should open it (or subscribe, or offer to import it) ||style="color: blue; white-space: nowrap;"| In progress
|-
| P2 || Launching a webcal:// URL should add that subscription to the calendar list ||style="color: red;"| Unknown
|-
| P1 || Copying and pasting ICS from the clipboard should create an appropriate new item ||style="color: blue; white-space: no-wrap;"| In progress
|-
| P3 || Copying and pasting hCalendar data from the clipboard should create an appropriate new item ||style="color: red;"| Unknown
|-
| P3 || Copying and pasting events between Lightning and Sunbird should work properly ||style="color: red;"| Unknown
|}

===ICS Export===
Sunbird and Lightning should provide a way for users to export their data in a standards compliant format. This allows users to not need to enter a 'walled garden' when using Sunbird/Lightning

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|style="background-color: #fdd;"| P2 ||style="background-color: #fdd;"| Export of particular items/sets of items should be possible. (Lightning) || style="color: red;"| Unknown
|}

===Conflict Resolution===
Sunbird and Lightning should intelligently handle data conflicts, and present the user with a clear interface for the user to resolve any that it can't do itself.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P2 || Share an .ICS file on the network without dataloss ||style="color: red;"| Unknown
|-
| P2 || Offline storage of remote calendars ||style="color: red;"| Unknown
|-
| P2 || Gracefully handle conflicts between local and network data ||style="color: red;"| Unknown
|}

===Printing===
Sunbird and Lightning should provide an easy to use way for users to get their data in a paper format, through their printer.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|style="background-color: #fdd;"| P1 ||style="background-color: #fdd;"| Printing should be possible. (Lightning) || style="color: green;" | Complete
|-
|style="background-color: #fdd;"| P2 ||style="background-color: #fdd;"| Printing a week's view of items should be possible. || style="color: green;" | Complete
|}

===Publishing===
Sunbird and Lightning should allow users to publish their calendar information to a web server.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|style="background-color: #fdd;"| P2 ||style="background-color: #fdd;"| Publishing a specific set of items should be possible. (Lightning) || style="color: red;" | Unknown
|}

===Get Data In===
Users should be able to get calendar data from multiple sources into the application.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|style="background-color: #fdd;"| P1 ||style="background-color: #fdd;"| Standards compliant data should always be successfully read/preserved. || style="color: red;" | Unknown
|-
|style="background-color: #fdd;"| P1 ||style="background-color: #fdd;"| Errors in standards compliance should be gracefully handled. || style="color: red;" | Unknown
|-
| P2 || Import data from the user's existing calendar applications || style="color: green; white-space: nowrap;" | Complete
|}

===Thunderbird Integration===
Lightning should be integrated as seamlessly as possible into Thunderbird.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P2 || Integrate into Thunderbird's undo/redo queue || style="color: green;" | Complete
|-
| P2 || Integrate into Thunderbird's copy/paste || style="color: green;" | Complete
|-
| P2 || Integrate into Thunderbird's print command || style="color: green;" | Complete
|}

===Calendar Interoperation===
Users should be able to send and receive meeting invitations received via email.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P1 || Allow sending iMIP/iTIP invitations. || style="color: green;" | Complete
|-
| P1 || Allow sending decline/accept iMIP/iTIP responses. || style="color: green;" | Complete
|}

===Backup===
Sunbird and Lightning should provide functionality for users to easily backup and restore their data.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P3 || Make backups of data || style="color: red;" | Unknown
|}

===Dataloss===
Users should be able to use Sunbird/Lightning with confidence that their data will be preserved.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|style="background-color: #fdd;"| P1 ||style="background-color: #fdd;"| Subscribing to a calendar with unexpected data should preserve the data || style="color: red;" | Unknown
|-
|style="background-color: #fdd;"| P2 ||style="background-color: #fdd;"| Standards compliant data should be preserved when edited. || style="color: red;" | Unknown
|}

===Misc Regressions===
Users upgrading from past versions should not notice significant loss of functionality/usability.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P1 || "Misc Regressions" is provided to give it visibility during discussions. Individual elements do not exist at this time.
|}

===User pain-points from 0.3===
Wherever possible, we should attempt to address pain-points in 0.3 identified by our users. These were not determined scientifically. They're a "gut feeling" based on IRC, bugmail, and newsgroups.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee;"| '''Bug(s)'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee;"| '''Status'''
|-
|{{bug|349048}}||<strike>Having CalExt installed</strike>||FIXED
|-
|{{bug|349520}}||<strike>24 hour views (and no way to make them smaller)</strike>||FIXED
|-
|{{bug|345643}}||<strike>Date formatting (MM/DD vs DD/MM)</strike>||FIXED
|-
|{{bug|343792}}||<strike>Data import errors - invalid or atypical ICS</strike>||FIXED
|-
|{{bug|354951}}||Data import errors - charset||
|-
|{{bug|310258}}||<strike>Hide completed tasks is missing from Lightning</strike>||FIXED
|}

Calendar:Next Release

2007-03-09T22:07:01Z

Lilmatt: /* Calendar Interoperation */

<div style="border: thin dotted #aaa; padding: 10px;">
'''Please don't edit this page unless you are a member of the calendar team.''' To join in the discussion regarding the next calendar release, please see [http://groups.google.com/group/mozilla.dev.apps.calendar/browse_thread/thread/5adb513f0ade569e/e057ef42c42cf042#e057ef42c42cf042 this newsgroup thread].</div>

== Overview==
Sunbird and Lightning are aiming for a simultaneous release of their next version (0.5) in early 2007. This page is meant to provide an overview of the status of that release.

Items with a red background were originally targetted for version 0.3

==Key Development Areas==

===Core Architecture===
Develop Sunbird and Lightning's core architecture to be robust enough for new feature support and ease of future development.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P1 || Editing / viewing of events: Complete the move to using a controller to act on the data, instead of having the views do that directly. || style="color: green; white-space: nowrap;"| Complete
|}

===Performance===
Sunbird and Lightning will display all events and tasks with the correct information and in the correct places.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P1 || Improve performance of storage provider (daniel/mvl) || style="color: blue; white-space: nowrap;" | In progress
|-
| P1 || Improve performance of other providers (Sun team) || style="color: blue;" | In queue
|-
| P1 || Improve performance of views (mickey) || style="color: blue;" | In queue
|}

===Zoom/Scroll===
Sunbird and Lightning should allow easy navigation of calendars.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|<strike>P2</strike>||<strike>Investigate zoom scroll</strike> ||style="color: grey; white-space: nowrap;"| Dropped for 0.5
|}

===Navigation===
Sunbird and Lightning should allow users to move to any display they want.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|style="background-color: #fdd;"| P1 ||style="background-color: #fdd;"| A 'Go to Date' functionality should be exposed. (Lightning) || style="color: blue; white-space: nowrap;"| In progress
|}

===Workflow (user experience)===
Sunbird and Lightning should have an easy and intuitive user interface, allowing the user to get things done as effortlessly as possible.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P1 || [[Calendar:Improving_the_Calendar_Views|Determine major pain points]] (christian) || style="color: blue; white-space: nowrap;" | In progress
|-
| P1 || Come up with sketches for solutions (christian) || style="color: blue; white-space: nowrap;" | In progress
|-
| P2 || Implement Agenda View improvements || style="color: red;" | Unknown
|}

===Item Creation/Modification===
Sunbird and Lightning should allow users to create, modify, and interact with tasks and events easily.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|<strike>P1</strike>||<strike>Event vs. Task semantics - Determine what is require for usability and RFC2445 conformance</strike> ||style="color: grey; white-space: nowrap;"| Dropped for 0.5
|-
| P1 || Editting recurring events: "Edit just this" vs. "Edit this and all occurrences after" ||style="color: blue; white-space: nowrap;"| In progress
|-
| P2 || We should be registered to handle .ICS files - Mac||style="color: blue; white-space: nowrap;"| In progress
|-
| P2 || We should be registered to handle .ICS files - Windows||style="color: blue; white-space: nowrap;"| In progress
|-
| P2 || We should be registered to handle .ICS files - Unix||style="color: red;"| Unknown
|-
| P2 || We should be registered to handle webcal:// URLs - Mac||style="color: blue; white-space: nowrap;"| In progress
|-
| P2 || We should be registered to handle webcal:// URLs - Windows ||style="color: blue; white-space: nowrap;"| In progress
|-
| P2 || We should be registered to handle webcal:// URLs - Unix||style="color: red;"| Unknown
|-
| P2 || Double-clicking an .ICS file should open it (or subscribe, or offer to import it) ||style="color: blue; white-space: nowrap;"| In progress
|-
| P2 || Launching a webcal:// URL should add that subscription to the calendar list ||style="color: red;"| Unknown
|-
| P1 || Copying and pasting ICS from the clipboard should create an appropriate new item ||style="color: blue; white-space: no-wrap;"| In progress
|-
| P3 || Copying and pasting hCalendar data from the clipboard should create an appropriate new item ||style="color: red;"| Unknown
|-
| P3 || Copying and pasting events between Lightning and Sunbird should work properly ||style="color: red;"| Unknown
|}

===ICS Export===
Sunbird and Lightning should provide a way for users to export their data in a standards compliant format. This allows users to not need to enter a 'walled garden' when using Sunbird/Lightning

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|style="background-color: #fdd;"| P2 ||style="background-color: #fdd;"| Export of particular items/sets of items should be possible. (Lightning) || style="color: red;"| Unknown
|}

===Conflict Resolution===
Sunbird and Lightning should intelligently handle data conflicts, and present the user with a clear interface for the user to resolve any that it can't do itself.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P2 || Share an .ICS file on the network without dataloss ||style="color: red;"| Unknown
|-
| P2 || Offline storage of remote calendars ||style="color: red;"| Unknown
|-
| P2 || Gracefully handle conflicts between local and network data ||style="color: red;"| Unknown
|}

===Printing===
Sunbird and Lightning should provide an easy to use way for users to get their data in a paper format, through their printer.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|style="background-color: #fdd;"| P1 ||style="background-color: #fdd;"| Printing should be possible. (Lightning) || style="color: green;" | Complete
|-
|style="background-color: #fdd;"| P2 ||style="background-color: #fdd;"| Printing a week's view of items should be possible. || style="color: green;" | Complete
|}

===Publishing===
Sunbird and Lightning should allow users to publish their calendar information to a web server.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|style="background-color: #fdd;"| P2 ||style="background-color: #fdd;"| Publishing a specific set of items should be possible. (Lightning) || style="color: red;" | Unknown
|}

===Get Data In===
Users should be able to get calendar data from multiple sources into the application.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|style="background-color: #fdd;"| P1 ||style="background-color: #fdd;"| Standards compliant data should always be successfully read/preserved. || style="color: red;" | Unknown
|-
|style="background-color: #fdd;"| P1 ||style="background-color: #fdd;"| Errors in standards compliance should be gracefully handled. || style="color: red;" | Unknown
|-
| P2 || Import data from the user's existing calendar applications || style="color: green; white-space: nowrap;" | Complete
|}

===Thunderbird Integration===
Lightning should be integrated as seamlessly as possible into Thunderbird.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P2 || Integrate into Thunderbird's undo/redo queue || style="color: green;" | Complete
|-
| P2 || Integrate into Thunderbird's copy/paste || style="color: green;" | Complete
|-
| P2 || Integrate into Thunderbird's print command || style="color: green;" | Complete
|}

===Calendar Interoperation===
Users should be able to send and receive meeting invitations received via email.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P1 || Allow sending iMIP/iTIP invitations. || style="color: green;" | Complete
|-
| P1 || Allow sending decline/accept iMIP/iTIP responses. || style="color: green;" | Complete
|}

===Backup===
Sunbird and Lightning should provide functionality for users to easily backup and restore their data.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P3 || Make backups of data || style="color: red;" | Unknown
|}

===Dataloss===
Users should be able to use Sunbird/Lightning with confidence that their data will be preserved.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|style="background-color: #fdd;"| P1 ||style="background-color: #fdd;"| Subscribing to a calendar with unexpected data should preserve the data || style="color: red;" | Unknown
|-
|style="background-color: #fdd;"| P2 ||style="background-color: #fdd;"| Standards compliant data should be preserved when edited. || style="color: red;" | Unknown
|}

===Misc Regressions===
Users upgrading from past versions should not notice significant loss of functionality/usability.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P1 || "Misc Regressions" is provided to give it visibility during discussions. Individual elements do not exist at this time.
|}

===User pain-points from 0.3===
Wherever possible, we should attempt to address pain-points in 0.3 identified by our users. These were not determined scientifically. They're a "gut feeling" based on IRC, bugmail, and newsgroups.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee;"| '''Bug(s)'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee;"| '''Status'''
|-
|{{bug|349048}}||<strike>Having CalExt installed</strike>||FIXED
|-
|{{bug|349520}}||24 hour views (and no way to make them smaller)||In queue - tbe
|-
|{{bug|345643}}||<strike>Date formatting (MM/DD vs DD/MM)</strike>||FIXED
|-
|{{bug|343792}}||<strike>Data import errors - invalid or atypical ICS</strike>||FIXED
|-
|{{bug|354951}}||Data import errors - charset||
|-
|{{bug|310258}}||<strike>Hide completed tasks is missing from Lightning</strike>||FIXED
|}

Calendar:Next Release

2007-03-09T22:06:23Z

Lilmatt: /* Thunderbird Integration */

<div style="border: thin dotted #aaa; padding: 10px;">
'''Please don't edit this page unless you are a member of the calendar team.''' To join in the discussion regarding the next calendar release, please see [http://groups.google.com/group/mozilla.dev.apps.calendar/browse_thread/thread/5adb513f0ade569e/e057ef42c42cf042#e057ef42c42cf042 this newsgroup thread].</div>

== Overview==
Sunbird and Lightning are aiming for a simultaneous release of their next version (0.5) in early 2007. This page is meant to provide an overview of the status of that release.

Items with a red background were originally targetted for version 0.3

==Key Development Areas==

===Core Architecture===
Develop Sunbird and Lightning's core architecture to be robust enough for new feature support and ease of future development.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P1 || Editing / viewing of events: Complete the move to using a controller to act on the data, instead of having the views do that directly. || style="color: green; white-space: nowrap;"| Complete
|}

===Performance===
Sunbird and Lightning will display all events and tasks with the correct information and in the correct places.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P1 || Improve performance of storage provider (daniel/mvl) || style="color: blue; white-space: nowrap;" | In progress
|-
| P1 || Improve performance of other providers (Sun team) || style="color: blue;" | In queue
|-
| P1 || Improve performance of views (mickey) || style="color: blue;" | In queue
|}

===Zoom/Scroll===
Sunbird and Lightning should allow easy navigation of calendars.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|<strike>P2</strike>||<strike>Investigate zoom scroll</strike> ||style="color: grey; white-space: nowrap;"| Dropped for 0.5
|}

===Navigation===
Sunbird and Lightning should allow users to move to any display they want.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|style="background-color: #fdd;"| P1 ||style="background-color: #fdd;"| A 'Go to Date' functionality should be exposed. (Lightning) || style="color: blue; white-space: nowrap;"| In progress
|}

===Workflow (user experience)===
Sunbird and Lightning should have an easy and intuitive user interface, allowing the user to get things done as effortlessly as possible.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P1 || [[Calendar:Improving_the_Calendar_Views|Determine major pain points]] (christian) || style="color: blue; white-space: nowrap;" | In progress
|-
| P1 || Come up with sketches for solutions (christian) || style="color: blue; white-space: nowrap;" | In progress
|-
| P2 || Implement Agenda View improvements || style="color: red;" | Unknown
|}

===Item Creation/Modification===
Sunbird and Lightning should allow users to create, modify, and interact with tasks and events easily.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|<strike>P1</strike>||<strike>Event vs. Task semantics - Determine what is require for usability and RFC2445 conformance</strike> ||style="color: grey; white-space: nowrap;"| Dropped for 0.5
|-
| P1 || Editting recurring events: "Edit just this" vs. "Edit this and all occurrences after" ||style="color: blue; white-space: nowrap;"| In progress
|-
| P2 || We should be registered to handle .ICS files - Mac||style="color: blue; white-space: nowrap;"| In progress
|-
| P2 || We should be registered to handle .ICS files - Windows||style="color: blue; white-space: nowrap;"| In progress
|-
| P2 || We should be registered to handle .ICS files - Unix||style="color: red;"| Unknown
|-
| P2 || We should be registered to handle webcal:// URLs - Mac||style="color: blue; white-space: nowrap;"| In progress
|-
| P2 || We should be registered to handle webcal:// URLs - Windows ||style="color: blue; white-space: nowrap;"| In progress
|-
| P2 || We should be registered to handle webcal:// URLs - Unix||style="color: red;"| Unknown
|-
| P2 || Double-clicking an .ICS file should open it (or subscribe, or offer to import it) ||style="color: blue; white-space: nowrap;"| In progress
|-
| P2 || Launching a webcal:// URL should add that subscription to the calendar list ||style="color: red;"| Unknown
|-
| P1 || Copying and pasting ICS from the clipboard should create an appropriate new item ||style="color: blue; white-space: no-wrap;"| In progress
|-
| P3 || Copying and pasting hCalendar data from the clipboard should create an appropriate new item ||style="color: red;"| Unknown
|-
| P3 || Copying and pasting events between Lightning and Sunbird should work properly ||style="color: red;"| Unknown
|}

===ICS Export===
Sunbird and Lightning should provide a way for users to export their data in a standards compliant format. This allows users to not need to enter a 'walled garden' when using Sunbird/Lightning

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|style="background-color: #fdd;"| P2 ||style="background-color: #fdd;"| Export of particular items/sets of items should be possible. (Lightning) || style="color: red;"| Unknown
|}

===Conflict Resolution===
Sunbird and Lightning should intelligently handle data conflicts, and present the user with a clear interface for the user to resolve any that it can't do itself.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P2 || Share an .ICS file on the network without dataloss ||style="color: red;"| Unknown
|-
| P2 || Offline storage of remote calendars ||style="color: red;"| Unknown
|-
| P2 || Gracefully handle conflicts between local and network data ||style="color: red;"| Unknown
|}

===Printing===
Sunbird and Lightning should provide an easy to use way for users to get their data in a paper format, through their printer.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|style="background-color: #fdd;"| P1 ||style="background-color: #fdd;"| Printing should be possible. (Lightning) || style="color: green;" | Complete
|-
|style="background-color: #fdd;"| P2 ||style="background-color: #fdd;"| Printing a week's view of items should be possible. || style="color: green;" | Complete
|}

===Publishing===
Sunbird and Lightning should allow users to publish their calendar information to a web server.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|style="background-color: #fdd;"| P2 ||style="background-color: #fdd;"| Publishing a specific set of items should be possible. (Lightning) || style="color: red;" | Unknown
|}

===Get Data In===
Users should be able to get calendar data from multiple sources into the application.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|style="background-color: #fdd;"| P1 ||style="background-color: #fdd;"| Standards compliant data should always be successfully read/preserved. || style="color: red;" | Unknown
|-
|style="background-color: #fdd;"| P1 ||style="background-color: #fdd;"| Errors in standards compliance should be gracefully handled. || style="color: red;" | Unknown
|-
| P2 || Import data from the user's existing calendar applications || style="color: green; white-space: nowrap;" | Complete
|}

===Thunderbird Integration===
Lightning should be integrated as seamlessly as possible into Thunderbird.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P2 || Integrate into Thunderbird's undo/redo queue || style="color: green;" | Complete
|-
| P2 || Integrate into Thunderbird's copy/paste || style="color: green;" | Complete
|-
| P2 || Integrate into Thunderbird's print command || style="color: green;" | Complete
|}

===Calendar Interoperation===
Users should be able to send and receive meeting invitations received via email.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P1 || Allow sending iMIP/iTIP invitations. || style="color: blue; white-space: nowrap;" | In progress
|-
| P1 || Allow sending decline/accept iMIP/iTIP responses. || style="color: green; white-space: nowrap;" | Complete
|}

===Backup===
Sunbird and Lightning should provide functionality for users to easily backup and restore their data.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P3 || Make backups of data || style="color: red;" | Unknown
|}

===Dataloss===
Users should be able to use Sunbird/Lightning with confidence that their data will be preserved.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|style="background-color: #fdd;"| P1 ||style="background-color: #fdd;"| Subscribing to a calendar with unexpected data should preserve the data || style="color: red;" | Unknown
|-
|style="background-color: #fdd;"| P2 ||style="background-color: #fdd;"| Standards compliant data should be preserved when edited. || style="color: red;" | Unknown
|}

===Misc Regressions===
Users upgrading from past versions should not notice significant loss of functionality/usability.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P1 || "Misc Regressions" is provided to give it visibility during discussions. Individual elements do not exist at this time.
|}

===User pain-points from 0.3===
Wherever possible, we should attempt to address pain-points in 0.3 identified by our users. These were not determined scientifically. They're a "gut feeling" based on IRC, bugmail, and newsgroups.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee;"| '''Bug(s)'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee;"| '''Status'''
|-
|{{bug|349048}}||<strike>Having CalExt installed</strike>||FIXED
|-
|{{bug|349520}}||24 hour views (and no way to make them smaller)||In queue - tbe
|-
|{{bug|345643}}||<strike>Date formatting (MM/DD vs DD/MM)</strike>||FIXED
|-
|{{bug|343792}}||<strike>Data import errors - invalid or atypical ICS</strike>||FIXED
|-
|{{bug|354951}}||Data import errors - charset||
|-
|{{bug|310258}}||<strike>Hide completed tasks is missing from Lightning</strike>||FIXED
|}

Calendar:Home Page

2007-03-08T18:03:48Z

Lilmatt: /* Mainly for developers */

__NOTOC__
'''Welcome to the wiki of the Mozilla Calendar Project.'''

This [http://en.wikipedia.org/wiki/Wiki wiki] represents a collection of easily-editable pages providing a variety of information on both the standalone calendar application [http://www.mozilla.org/projects/calendar/sunbird/ Sunbird], and the calendaring extension for [http://www.mozilla.com/thunderbird/ Mozilla Thunderbird], code-named [http://www.mozilla.org/projects/calendar/lightning/ Lightning].

Please keep in mind that while every effort is made to keep these pages up-to-date, sometimes pages do become obsolete.

== Latest Releases ==
*'''[http://www.mozilla.org/projects/calendar/releases/sunbird0.3.1.html Sunbird 0.3.1]''' - Our standalone calendar application for Linux, Mac OS X, and Windows.
*'''[http://www.mozilla.org/projects/calendar/releases/lightning0.3.1.html Lightning 0.3.1]''' - The calendaring extension for [http://www.mozilla.com/thunderbird/ Mozilla Thunderbird]

== For end-users ==
These pages contain information that end-users (that's you!) will hopefully find useful.

*[[Calendar:FAQ | FAQ]] - "Frequently Asked Questions" concerning Sunbird and Lightning
* How to contribute - Looking to get involved? Look here for some good starting points.
*[[Calendar:Charter]] (draft) - The overall mission of the calendar project
*[[Calendar:Target Users|Target Users]] - Who we're writing software for
*[[Calendar:Lightning]] - (jminta-will probably move?) Links to all pages related to Lightning
*[[Calendar:Past_Releases|Past Releases]] - Where we've been.
*[[Calendar:Roadmap|Roadmap]] - Where we're going.
*[[Calendar:For_Everyone:Blocking Flags|Blocking Flags]] - How we choose what makes it into each release.

== For developers ==
These are pages for people interested in contributing in a more formal way to Sunbird and Lightning development, whether through testing (QA), or coding.
*[[Calendar:Next_Release]] - A bunch of stuff for planning the next release.
*[[Calendar:F2F Meeting]] - The July 2006 Toronto face-to-face meeting.
*[[Calendar:Localization]] - Information for translators on how to localize Sunbird and Lightning.
*[[Calendar:Hacking|Beginner's Guide to Hacking Sunbird/Lightning]] (in progress) Information for someone looking to get their feet wet in the mozilla codebase for the first time
*[[Calendar:Dev Guide|New Sunbird/Lightning Developer's Guide]] (draft)- A bird's eye view of the calendar codebase
*[[Calendar:Status Meetings|Meeting notes]] - Notes from past meetings held on IRC. Also includes the schedule and agenda for the next meeting
*[[Calendar: Feature Implementations |Feature Implementations]] - proposals and overviews of past, present, and possible future features in Sunbird and Lightning.
*[[Calendar:QA Home|Calendar QA and Testing]] - Information for those wishing to help test development builds, in an effort to improve quality.
*Administration ([[Calendar: Module Ownership]], [[Calendar:Updating libical]], [[Calendar: Development Strategies]], [[Calendar:Build Team Requests]]) - pages related to administrative tasks in calendar development (reviews, release cycles, etc)
**[[Calendar: UI Ownership]]
**[[Calendar: Review Process]]

[[category:Calendar|*]]

Calendar:Home Page

2007-03-08T18:03:17Z

Lilmatt: /* Mainly for end-users */

__NOTOC__
'''Welcome to the wiki of the Mozilla Calendar Project.'''

This [http://en.wikipedia.org/wiki/Wiki wiki] represents a collection of easily-editable pages providing a variety of information on both the standalone calendar application [http://www.mozilla.org/projects/calendar/sunbird/ Sunbird], and the calendaring extension for [http://www.mozilla.com/thunderbird/ Mozilla Thunderbird], code-named [http://www.mozilla.org/projects/calendar/lightning/ Lightning].

Please keep in mind that while every effort is made to keep these pages up-to-date, sometimes pages do become obsolete.

== Latest Releases ==
*'''[http://www.mozilla.org/projects/calendar/releases/sunbird0.3.1.html Sunbird 0.3.1]''' - Our standalone calendar application for Linux, Mac OS X, and Windows.
*'''[http://www.mozilla.org/projects/calendar/releases/lightning0.3.1.html Lightning 0.3.1]''' - The calendaring extension for [http://www.mozilla.com/thunderbird/ Mozilla Thunderbird]

== For end-users ==
These pages contain information that end-users (that's you!) will hopefully find useful.

*[[Calendar:FAQ | FAQ]] - "Frequently Asked Questions" concerning Sunbird and Lightning
* How to contribute - Looking to get involved? Look here for some good starting points.
*[[Calendar:Charter]] (draft) - The overall mission of the calendar project
*[[Calendar:Target Users|Target Users]] - Who we're writing software for
*[[Calendar:Lightning]] - (jminta-will probably move?) Links to all pages related to Lightning
*[[Calendar:Past_Releases|Past Releases]] - Where we've been.
*[[Calendar:Roadmap|Roadmap]] - Where we're going.
*[[Calendar:For_Everyone:Blocking Flags|Blocking Flags]] - How we choose what makes it into each release.

== Mainly for developers ==
These are pages for people interested in contributing in a more formal way to Sunbird and Lightning development, whether through testing (QA), or coding.
*[[Calendar:Next_Release]] - A bunch of stuff for planning the next release.
*[[Calendar:F2F Meeting]] - The July 2006 Toronto face-to-face meeting.
*[[Calendar:Localization]] - Information for translators on how to localize Sunbird and Lightning.
*[[Calendar:Hacking|Beginner's Guide to Hacking Sunbird/Lightning]] (in progress) Information for someone looking to get their feet wet in the mozilla codebase for the first time
*[[Calendar:Dev Guide|New Sunbird/Lightning Developer's Guide]] (draft)- A bird's eye view of the calendar codebase
*[[Calendar:Status Meetings|Meeting notes]] - Notes from past meetings held on IRC. Also includes the schedule and agenda for the next meeting
*[[Calendar: Feature Implementations |Feature Implementations]] - proposals and overviews of past, present, and possible future features in Sunbird and Lightning.
*[[Calendar:QA Home|Calendar QA and Testing]] - Information for those wishing to help test development builds, in an effort to improve quality.
*Administration ([[Calendar: Module Ownership]], [[Calendar:Updating libical]], [[Calendar: Development Strategies]], [[Calendar:Build Team Requests]]) - pages related to administrative tasks in calendar development (reviews, release cycles, etc)
**[[Calendar: UI Ownership]]
**[[Calendar: Review Process]]

[[category:Calendar|*]]

Calendar:Home Page

2007-03-08T17:48:36Z

Lilmatt: /* Mainly for developers */

__NOTOC__
'''Welcome to the wiki of the Mozilla Calendar Project.'''

This [http://en.wikipedia.org/wiki/Wiki wiki] represents a collection of easily-editable pages providing a variety of information on both the standalone calendar application [http://www.mozilla.org/projects/calendar/sunbird/ Sunbird], and the calendaring extension for [http://www.mozilla.com/thunderbird/ Mozilla Thunderbird], code-named [http://www.mozilla.org/projects/calendar/lightning/ Lightning].

Please keep in mind that while every effort is made to keep these pages up-to-date, sometimes pages do become obsolete.

== Latest Releases ==
*'''[http://www.mozilla.org/projects/calendar/releases/sunbird0.3.1.html Sunbird 0.3.1]''' - Our standalone calendar application for Linux, Mac OS X, and Windows.
*'''[http://www.mozilla.org/projects/calendar/releases/lightning0.3.1.html Lightning 0.3.1]''' - The calendaring extension for [http://www.mozilla.com/thunderbird/ Mozilla Thunderbird]

== Mainly for end-users ==
These pages contain information that end-users (that's you!) will hopefully find useful.

*[[Calendar:FAQ | FAQ]] - "Frequently Asked Questions" concerning Sunbird and Lightning
* How to contribute - Looking to get involved? Look here for some good starting points.
*[[Calendar:Charter]] (draft) - The overall mission of the calendar project
*[[Calendar:Target Users|Target Users]] - Who we're writing software for
*[[Calendar:Lightning]] - (jminta-will probably move?) Links to all pages related to Lightning
*[[Calendar:Past_Releases|Past Releases]] - Where we've been.
*[[Calendar:Roadmap|Roadmap]] - Where we're going.
*[[Calendar:For_Everyone:Blocking Flags|Blocking Flags]] - How we choose what makes it into each release.

== Mainly for developers ==
These are pages for people interested in contributing in a more formal way to Sunbird and Lightning development, whether through testing (QA), or coding.
*[[Calendar:Next_Release]] - A bunch of stuff for planning the next release.
*[[Calendar:F2F Meeting]] - The July 2006 Toronto face-to-face meeting.
*[[Calendar:Localization]] - Information for translators on how to localize Sunbird and Lightning.
*[[Calendar:Hacking|Beginner's Guide to Hacking Sunbird/Lightning]] (in progress) Information for someone looking to get their feet wet in the mozilla codebase for the first time
*[[Calendar:Dev Guide|New Sunbird/Lightning Developer's Guide]] (draft)- A bird's eye view of the calendar codebase
*[[Calendar:Status Meetings|Meeting notes]] - Notes from past meetings held on IRC. Also includes the schedule and agenda for the next meeting
*[[Calendar: Feature Implementations |Feature Implementations]] - proposals and overviews of past, present, and possible future features in Sunbird and Lightning.
*[[Calendar:QA Home|Calendar QA and Testing]] - Information for those wishing to help test development builds, in an effort to improve quality.
*Administration ([[Calendar: Module Ownership]], [[Calendar:Updating libical]], [[Calendar: Development Strategies]], [[Calendar:Build Team Requests]]) - pages related to administrative tasks in calendar development (reviews, release cycles, etc)
**[[Calendar: UI Ownership]]
**[[Calendar: Review Process]]

[[category:Calendar|*]]

Calendar:Past Releases

2007-03-08T17:46:48Z

Lilmatt:

=Disclaimers=
Any "Calendar Extension Roadmap" documents that may continue to be floating around are deprecated and should be treated as such. Long ago, it was determined that in order to improve stability and flexibility, much of the original storage codebase would need to be rewritten. In addition, the standalone calendar app Sunbird gained popularity. However, being one of the first applications based on the then nascent Toolkit API, this also skewed any existing roadmaps somewhat.

=A note or two about version numbers=
Prior to the release of Sunbird 0.3, various alpha, beta, and release candidate (RC) releases were used. It was decided that such formality was inappropriate for a pre-1.0 product, kept us in an almost constant code freeze, and stymied further development. Sunbird 0.3a2 is the last release with such filigree. Until we reach 1.0, future releases of both Lightning and Sunbird will use 0.n version numbers only. No alphas or betas will be released.

In addition, to help alleviate confusion regarding the equivalent feature sets of Lightning and Sunbird, it was decided to skip Lightning version 0.2. Lightning's next release will be 0.3, to coincide with the feature set of Sunbird 0.3.

=Past Releases=
The roadmaps for past releases are provided here for context and historical purposes only.

==Sunbird 0.2==
Sunbird 0.2 still used the original underlying code from OEOne which stored events and tasks as .ics files on the local hard drive (or remote WebDAV server). It relied on libxpical to provide an XPCOM wrapper around the libical library. While much work went in to creating a useable Toolkit-based app, it was clear that future development would require refactoring of the backend storage mechanisms, both for stability and for flexibility in supporting new types of calendar "stores" such as CalDAV.

==Sunbird 0.3a1==
Released 2005-11-04

This was the first release using the refactored backend storage. All data is stored in a SQLite database which is accessed via a unified storage API, and uses custom providers to translate between specific protocols (.ics, CalDAV, etc.) and our unified storage API.

Release Goals:
* Fix regressions from the backend 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 (Sunbird 0.2/non-XBL) views and UI.
* '''Intent 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 Sunbird 0.3a1:'''
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.

==Lightning 0.1==
Released 2006-03-14

This was the first release of Lightning, the integrated calendar extension for Thunderbird. Like Sunbird 0.3a1 before it, Lightning used the new backend storage. Bug fixes for issues found in Sunbird 0.3a1's new backend storage were also included. Lightning also introduced views (Day, Week, Multiweek, Month Views) written in XBL rather than the XUL-based ones used in all previous Sunbird releases, and dating back to OEOne. Since the XBL views can tie more directly to the data, significantly less code is required to keep what is displayed to the user in sync with what is in the database.

Release Goals:
* XBL views
* No known dataloss bugs when editing ICS files exclusively with Lightning
* Basically functionally usable as dogfood with local database & ICS calendars
* Project Page: [[Calendar:Lightning:0.1]]
* Release Notes: [[Calendar:Lightning:0.1:Release Notes]]

==Sunbird 0.3a2==
Released 2006-05-11

This release switched Sunbird from the original (Sunbird 0.2) XUL-based views to the XBL ones originally released in Lightning. Soon after we began to see customizations of views that would have been previously impractical to implement, such as ones that with one button click rotate 90 degrees (day on the x-axis, and hours on the y-axis).

Release Goals:
* Switch to new XBL views.
* 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 (outdated)]]

'''Notes for Sunbird0.3a2:'''
These views are 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.

== Sunbird/Lightning 0.3 ==
Released 2006-10-11

See [[Calendar:0.3_Release_Status | 0.3 Release Status]]

== Sunbird/Lightning 0.3.1 ==
Released 2007-02-19

See [[Calendar:0.3.1_Release_Status | 0.3.1 Release Status]]

Calendar:Home Page

2007-03-08T17:42:58Z

Lilmatt: /* Latest Releases */

__NOTOC__
'''Welcome to the wiki of the Mozilla Calendar Project.'''

This [http://en.wikipedia.org/wiki/Wiki wiki] represents a collection of easily-editable pages providing a variety of information on both the standalone calendar application [http://www.mozilla.org/projects/calendar/sunbird/ Sunbird], and the calendaring extension for [http://www.mozilla.com/thunderbird/ Mozilla Thunderbird], code-named [http://www.mozilla.org/projects/calendar/lightning/ Lightning].

Please keep in mind that while every effort is made to keep these pages up-to-date, sometimes pages do become obsolete.

== Latest Releases ==
*'''[http://www.mozilla.org/projects/calendar/releases/sunbird0.3.1.html Sunbird 0.3.1]''' - Our standalone calendar application for Linux, Mac OS X, and Windows.
*'''[http://www.mozilla.org/projects/calendar/releases/lightning0.3.1.html Lightning 0.3.1]''' - The calendaring extension for [http://www.mozilla.com/thunderbird/ Mozilla Thunderbird]

== Mainly for end-users ==
These pages contain information that end-users (that's you!) will hopefully find useful.

*[[Calendar:FAQ | FAQ]] - "Frequently Asked Questions" concerning Sunbird and Lightning
* How to contribute - Looking to get involved? Look here for some good starting points.
*[[Calendar:Charter]] (draft) - The overall mission of the calendar project
*[[Calendar:Target Users|Target Users]] - Who we're writing software for
*[[Calendar:Lightning]] - (jminta-will probably move?) Links to all pages related to Lightning
*[[Calendar:Past_Releases|Past Releases]] - Where we've been.
*[[Calendar:Roadmap|Roadmap]] - Where we're going.
*[[Calendar:For_Everyone:Blocking Flags|Blocking Flags]] - How we choose what makes it into each release.

== Mainly for developers ==
These are pages for people interested in contributing in a more formal way to Sunbird and Lightning development, whether through testing (QA), or coding.
*[[Calendar:0.3.1 Release Status]] - Overall status of the 0.3.1 release page. For tracking/planning purposes.
*[[Calendar:Next_Release]] - A bunch of stuff for planning the next release.
*[[Calendar:F2F Meeting]] - The July 2006 Toronto face-to-face meeting.
*[[Calendar:Localization]] - Information for translators on how to localize Sunbird and Lightning.
*[[Calendar:Hacking|Beginner's Guide to Hacking Sunbird/Lightning]] (in progress) Information for someone looking to get their feet wet in the mozilla codebase for the first time
*[[Calendar:Dev Guide|New Sunbird/Lightning Developer's Guide]] (draft)- A bird's eye view of the calendar codebase
*[[Calendar:Status Meetings|Meeting notes]] - Notes from past meetings held on IRC. Also includes the schedule and agenda for the next meeting
*[[Calendar: Feature Implementations |Feature Implementations]] - proposals and overviews of past, present, and possible future features in Sunbird and Lightning.
*[[Calendar:QA Home|Calendar QA and Testing]] - Information for those wishing to help test development builds, in an effort to improve quality.
*Administration ([[Calendar: Module Ownership]], [[Calendar:Updating libical]], [[Calendar: Development Strategies]], [[Calendar:Build Team Requests]]) - pages related to administrative tasks in calendar development (reviews, release cycles, etc)
**[[Calendar: UI Ownership]]
**[[Calendar: Review Process]]

[[category:Calendar|*]]

Calendar:Next Release

2007-03-08T01:38:33Z

Lilmatt: /* Calendar Interoperation */

<div style="border: thin dotted #aaa; padding: 10px;">
'''Please don't edit this page unless you are a member of the calendar team.''' To join in the discussion regarding the next calendar release, please see [http://groups.google.com/group/mozilla.dev.apps.calendar/browse_thread/thread/5adb513f0ade569e/e057ef42c42cf042#e057ef42c42cf042 this newsgroup thread].</div>

== Overview==
Sunbird and Lightning are aiming for a simultaneous release of their next version (0.5) in early 2007. This page is meant to provide an overview of the status of that release.

Items with a red background were originally targetted for version 0.3

==Key Development Areas==

===Core Architecture===
Develop Sunbird and Lightning's core architecture to be robust enough for new feature support and ease of future development.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P1 || Editing / viewing of events: Complete the move to using a controller to act on the data, instead of having the views do that directly. || style="color: green; white-space: nowrap;"| Complete
|}

===Performance===
Sunbird and Lightning will display all events and tasks with the correct information and in the correct places.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P1 || Improve performance of storage provider (daniel/mvl) || style="color: blue; white-space: nowrap;" | In progress
|-
| P1 || Improve performance of other providers (Sun team) || style="color: blue;" | In queue
|-
| P1 || Improve performance of views (mickey) || style="color: blue;" | In queue
|}

===Zoom/Scroll===
Sunbird and Lightning should allow easy navigation of calendars.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|<strike>P2</strike>||<strike>Investigate zoom scroll</strike> ||style="color: grey; white-space: nowrap;"| Dropped for 0.5
|}

===Navigation===
Sunbird and Lightning should allow users to move to any display they want.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|style="background-color: #fdd;"| P1 ||style="background-color: #fdd;"| A 'Go to Date' functionality should be exposed. (Lightning) || style="color: blue; white-space: nowrap;"| In progress
|}

===Workflow (user experience)===
Sunbird and Lightning should have an easy and intuitive user interface, allowing the user to get things done as effortlessly as possible.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P1 || [[Calendar:Improving_the_Calendar_Views|Determine major pain points]] (christian) || style="color: blue; white-space: nowrap;" | In progress
|-
| P1 || Come up with sketches for solutions (christian) || style="color: blue; white-space: nowrap;" | In progress
|-
| P2 || Implement Agenda View improvements || style="color: red;" | Unknown
|}

===Item Creation/Modification===
Sunbird and Lightning should allow users to create, modify, and interact with tasks and events easily.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|<strike>P1</strike>||<strike>Event vs. Task semantics - Determine what is require for usability and RFC2445 conformance</strike> ||style="color: grey; white-space: nowrap;"| Dropped for 0.5
|-
| P1 || Editting recurring events: "Edit just this" vs. "Edit this and all occurrences after" ||style="color: blue; white-space: nowrap;"| In progress
|-
| P2 || We should be registered to handle .ICS files - Mac||style="color: blue; white-space: nowrap;"| In progress
|-
| P2 || We should be registered to handle .ICS files - Windows||style="color: blue; white-space: nowrap;"| In progress
|-
| P2 || We should be registered to handle .ICS files - Unix||style="color: red;"| Unknown
|-
| P2 || We should be registered to handle webcal:// URLs - Mac||style="color: blue; white-space: nowrap;"| In progress
|-
| P2 || We should be registered to handle webcal:// URLs - Windows ||style="color: blue; white-space: nowrap;"| In progress
|-
| P2 || We should be registered to handle webcal:// URLs - Unix||style="color: red;"| Unknown
|-
| P2 || Double-clicking an .ICS file should open it (or subscribe, or offer to import it) ||style="color: blue; white-space: nowrap;"| In progress
|-
| P2 || Launching a webcal:// URL should add that subscription to the calendar list ||style="color: red;"| Unknown
|-
| P1 || Copying and pasting ICS from the clipboard should create an appropriate new item ||style="color: blue; white-space: no-wrap;"| In progress
|-
| P3 || Copying and pasting hCalendar data from the clipboard should create an appropriate new item ||style="color: red;"| Unknown
|-
| P3 || Copying and pasting events between Lightning and Sunbird should work properly ||style="color: red;"| Unknown
|}

===ICS Export===
Sunbird and Lightning should provide a way for users to export their data in a standards compliant format. This allows users to not need to enter a 'walled garden' when using Sunbird/Lightning

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|style="background-color: #fdd;"| P2 ||style="background-color: #fdd;"| Export of particular items/sets of items should be possible. (Lightning) || style="color: red;"| Unknown
|}

===Conflict Resolution===
Sunbird and Lightning should intelligently handle data conflicts, and present the user with a clear interface for the user to resolve any that it can't do itself.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P2 || Share an .ICS file on the network without dataloss ||style="color: red;"| Unknown
|-
| P2 || Offline storage of remote calendars ||style="color: red;"| Unknown
|-
| P2 || Gracefully handle conflicts between local and network data ||style="color: red;"| Unknown
|}

===Printing===
Sunbird and Lightning should provide an easy to use way for users to get their data in a paper format, through their printer.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|style="background-color: #fdd;"| P1 ||style="background-color: #fdd;"| Printing should be possible. (Lightning) || style="color: green;" | Complete
|-
|style="background-color: #fdd;"| P2 ||style="background-color: #fdd;"| Printing a week's view of items should be possible. || style="color: green;" | Complete
|}

===Publishing===
Sunbird and Lightning should allow users to publish their calendar information to a web server.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|style="background-color: #fdd;"| P2 ||style="background-color: #fdd;"| Publishing a specific set of items should be possible. (Lightning) || style="color: red;" | Unknown
|}

===Get Data In===
Users should be able to get calendar data from multiple sources into the application.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|style="background-color: #fdd;"| P1 ||style="background-color: #fdd;"| Standards compliant data should always be successfully read/preserved. || style="color: red;" | Unknown
|-
|style="background-color: #fdd;"| P1 ||style="background-color: #fdd;"| Errors in standards compliance should be gracefully handled. || style="color: red;" | Unknown
|-
| P2 || Import data from the user's existing calendar applications || style="color: green; white-space: nowrap;" | Complete
|}

===Thunderbird Integration===
Lightning should be integrated as seamlessly as possible into Thunderbird.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P2 || Integrate into Thunderbird's undo/redo queue || style="color: blue; white-space: nowrap;" | In progress
|-
| P2 || Integrate into Thunderbird's copy/paste || style="color: green;" | Complete
|-
| P2 || Integrate into Thunderbird's print command || style="color: blue; white-space: nowrap;" | In progress
|}

===Calendar Interoperation===
Users should be able to send and receive meeting invitations received via email.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P1 || Allow sending iMIP/iTIP invitations. || style="color: blue; white-space: nowrap;" | In progress
|-
| P1 || Allow sending decline/accept iMIP/iTIP responses. || style="color: green; white-space: nowrap;" | Complete
|}

===Backup===
Sunbird and Lightning should provide functionality for users to easily backup and restore their data.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P3 || Make backups of data || style="color: red;" | Unknown
|}

===Dataloss===
Users should be able to use Sunbird/Lightning with confidence that their data will be preserved.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|style="background-color: #fdd;"| P1 ||style="background-color: #fdd;"| Subscribing to a calendar with unexpected data should preserve the data || style="color: red;" | Unknown
|-
|style="background-color: #fdd;"| P2 ||style="background-color: #fdd;"| Standards compliant data should be preserved when edited. || style="color: red;" | Unknown
|}

===Misc Regressions===
Users upgrading from past versions should not notice significant loss of functionality/usability.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P1 || "Misc Regressions" is provided to give it visibility during discussions. Individual elements do not exist at this time.
|}

===User pain-points from 0.3===
Wherever possible, we should attempt to address pain-points in 0.3 identified by our users. These were not determined scientifically. They're a "gut feeling" based on IRC, bugmail, and newsgroups.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee;"| '''Bug(s)'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee;"| '''Status'''
|-
|{{bug|349048}}||<strike>Having CalExt installed</strike>||FIXED
|-
|{{bug|349520}}||24 hour views (and no way to make them smaller)||In queue - tbe
|-
|{{bug|345643}}||<strike>Date formatting (MM/DD vs DD/MM)</strike>||FIXED
|-
|{{bug|343792}}||<strike>Data import errors - invalid or atypical ICS</strike>||FIXED
|-
|{{bug|354951}}||Data import errors - charset||
|-
|{{bug|310258}}||<strike>Hide completed tasks is missing from Lightning</strike>||FIXED
|}

Calendar:Next Release

2007-03-08T01:37:54Z

Lilmatt: /* Thunderbird Integration */

<div style="border: thin dotted #aaa; padding: 10px;">
'''Please don't edit this page unless you are a member of the calendar team.''' To join in the discussion regarding the next calendar release, please see [http://groups.google.com/group/mozilla.dev.apps.calendar/browse_thread/thread/5adb513f0ade569e/e057ef42c42cf042#e057ef42c42cf042 this newsgroup thread].</div>

== Overview==
Sunbird and Lightning are aiming for a simultaneous release of their next version (0.5) in early 2007. This page is meant to provide an overview of the status of that release.

Items with a red background were originally targetted for version 0.3

==Key Development Areas==

===Core Architecture===
Develop Sunbird and Lightning's core architecture to be robust enough for new feature support and ease of future development.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P1 || Editing / viewing of events: Complete the move to using a controller to act on the data, instead of having the views do that directly. || style="color: green; white-space: nowrap;"| Complete
|}

===Performance===
Sunbird and Lightning will display all events and tasks with the correct information and in the correct places.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P1 || Improve performance of storage provider (daniel/mvl) || style="color: blue; white-space: nowrap;" | In progress
|-
| P1 || Improve performance of other providers (Sun team) || style="color: blue;" | In queue
|-
| P1 || Improve performance of views (mickey) || style="color: blue;" | In queue
|}

===Zoom/Scroll===
Sunbird and Lightning should allow easy navigation of calendars.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|<strike>P2</strike>||<strike>Investigate zoom scroll</strike> ||style="color: grey; white-space: nowrap;"| Dropped for 0.5
|}

===Navigation===
Sunbird and Lightning should allow users to move to any display they want.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|style="background-color: #fdd;"| P1 ||style="background-color: #fdd;"| A 'Go to Date' functionality should be exposed. (Lightning) || style="color: blue; white-space: nowrap;"| In progress
|}

===Workflow (user experience)===
Sunbird and Lightning should have an easy and intuitive user interface, allowing the user to get things done as effortlessly as possible.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P1 || [[Calendar:Improving_the_Calendar_Views|Determine major pain points]] (christian) || style="color: blue; white-space: nowrap;" | In progress
|-
| P1 || Come up with sketches for solutions (christian) || style="color: blue; white-space: nowrap;" | In progress
|-
| P2 || Implement Agenda View improvements || style="color: red;" | Unknown
|}

===Item Creation/Modification===
Sunbird and Lightning should allow users to create, modify, and interact with tasks and events easily.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|<strike>P1</strike>||<strike>Event vs. Task semantics - Determine what is require for usability and RFC2445 conformance</strike> ||style="color: grey; white-space: nowrap;"| Dropped for 0.5
|-
| P1 || Editting recurring events: "Edit just this" vs. "Edit this and all occurrences after" ||style="color: blue; white-space: nowrap;"| In progress
|-
| P2 || We should be registered to handle .ICS files - Mac||style="color: blue; white-space: nowrap;"| In progress
|-
| P2 || We should be registered to handle .ICS files - Windows||style="color: blue; white-space: nowrap;"| In progress
|-
| P2 || We should be registered to handle .ICS files - Unix||style="color: red;"| Unknown
|-
| P2 || We should be registered to handle webcal:// URLs - Mac||style="color: blue; white-space: nowrap;"| In progress
|-
| P2 || We should be registered to handle webcal:// URLs - Windows ||style="color: blue; white-space: nowrap;"| In progress
|-
| P2 || We should be registered to handle webcal:// URLs - Unix||style="color: red;"| Unknown
|-
| P2 || Double-clicking an .ICS file should open it (or subscribe, or offer to import it) ||style="color: blue; white-space: nowrap;"| In progress
|-
| P2 || Launching a webcal:// URL should add that subscription to the calendar list ||style="color: red;"| Unknown
|-
| P1 || Copying and pasting ICS from the clipboard should create an appropriate new item ||style="color: blue; white-space: no-wrap;"| In progress
|-
| P3 || Copying and pasting hCalendar data from the clipboard should create an appropriate new item ||style="color: red;"| Unknown
|-
| P3 || Copying and pasting events between Lightning and Sunbird should work properly ||style="color: red;"| Unknown
|}

===ICS Export===
Sunbird and Lightning should provide a way for users to export their data in a standards compliant format. This allows users to not need to enter a 'walled garden' when using Sunbird/Lightning

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|style="background-color: #fdd;"| P2 ||style="background-color: #fdd;"| Export of particular items/sets of items should be possible. (Lightning) || style="color: red;"| Unknown
|}

===Conflict Resolution===
Sunbird and Lightning should intelligently handle data conflicts, and present the user with a clear interface for the user to resolve any that it can't do itself.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P2 || Share an .ICS file on the network without dataloss ||style="color: red;"| Unknown
|-
| P2 || Offline storage of remote calendars ||style="color: red;"| Unknown
|-
| P2 || Gracefully handle conflicts between local and network data ||style="color: red;"| Unknown
|}

===Printing===
Sunbird and Lightning should provide an easy to use way for users to get their data in a paper format, through their printer.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|style="background-color: #fdd;"| P1 ||style="background-color: #fdd;"| Printing should be possible. (Lightning) || style="color: green;" | Complete
|-
|style="background-color: #fdd;"| P2 ||style="background-color: #fdd;"| Printing a week's view of items should be possible. || style="color: green;" | Complete
|}

===Publishing===
Sunbird and Lightning should allow users to publish their calendar information to a web server.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|style="background-color: #fdd;"| P2 ||style="background-color: #fdd;"| Publishing a specific set of items should be possible. (Lightning) || style="color: red;" | Unknown
|}

===Get Data In===
Users should be able to get calendar data from multiple sources into the application.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|style="background-color: #fdd;"| P1 ||style="background-color: #fdd;"| Standards compliant data should always be successfully read/preserved. || style="color: red;" | Unknown
|-
|style="background-color: #fdd;"| P1 ||style="background-color: #fdd;"| Errors in standards compliance should be gracefully handled. || style="color: red;" | Unknown
|-
| P2 || Import data from the user's existing calendar applications || style="color: green; white-space: nowrap;" | Complete
|}

===Thunderbird Integration===
Lightning should be integrated as seamlessly as possible into Thunderbird.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P2 || Integrate into Thunderbird's undo/redo queue || style="color: blue; white-space: nowrap;" | In progress
|-
| P2 || Integrate into Thunderbird's copy/paste || style="color: green;" | Complete
|-
| P2 || Integrate into Thunderbird's print command || style="color: blue; white-space: nowrap;" | In progress
|}

===Calendar Interoperation===
Users should be able to send and receive meeting invitations received via email.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P1 || Allow sending iMIP/iTIP invitations. || style="color: blue; white-space: nowrap;" | In progress
|-
| P1 || Allow sending decline/accept iMIP/iTIP responses. || style="color: blue; white-space: nowrap;" | In progress
|}

===Backup===
Sunbird and Lightning should provide functionality for users to easily backup and restore their data.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P3 || Make backups of data || style="color: red;" | Unknown
|}

===Dataloss===
Users should be able to use Sunbird/Lightning with confidence that their data will be preserved.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|style="background-color: #fdd;"| P1 ||style="background-color: #fdd;"| Subscribing to a calendar with unexpected data should preserve the data || style="color: red;" | Unknown
|-
|style="background-color: #fdd;"| P2 ||style="background-color: #fdd;"| Standards compliant data should be preserved when edited. || style="color: red;" | Unknown
|}

===Misc Regressions===
Users upgrading from past versions should not notice significant loss of functionality/usability.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P1 || "Misc Regressions" is provided to give it visibility during discussions. Individual elements do not exist at this time.
|}

===User pain-points from 0.3===
Wherever possible, we should attempt to address pain-points in 0.3 identified by our users. These were not determined scientifically. They're a "gut feeling" based on IRC, bugmail, and newsgroups.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee;"| '''Bug(s)'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee;"| '''Status'''
|-
|{{bug|349048}}||<strike>Having CalExt installed</strike>||FIXED
|-
|{{bug|349520}}||24 hour views (and no way to make them smaller)||In queue - tbe
|-
|{{bug|345643}}||<strike>Date formatting (MM/DD vs DD/MM)</strike>||FIXED
|-
|{{bug|343792}}||<strike>Data import errors - invalid or atypical ICS</strike>||FIXED
|-
|{{bug|354951}}||Data import errors - charset||
|-
|{{bug|310258}}||<strike>Hide completed tasks is missing from Lightning</strike>||FIXED
|}

Calendar:GDATA Provider

2007-03-06T12:42:30Z

Lilmatt: /* Disclaimer */

=Disclaimer=
This provider enables write support to Google Calendar. Although unlikely, it is possible that you could lose (parts of) your data here. Neither the author nor Mozilla can be held responsible for that.

=Getting the Provider=
==Downloading==
The provider is not yet available from addons.mozilla.org. It probably will be though.

==Building from CVS==
If you want to build your own copy of the provider from a CVS tree, you currently need to add the gdata directory to <code>/mozilla/calendar/providers/Makefile.in</code>. Once you have compiled, the resulting extension should be at <code>''obj-dir''/dist/xpi-stage/gdata-provider.xpi</code>

=Accessing your Calendar=
To access your calendar data, you need to retrieve your private XML URL from the Google Calendar UI. If you are not sure how, follow these steps:
# Open your [http://calendar.google.com/ Google Calendar]
# Click on the Calendar you would like to use in Sunbird or Lightning
# Select ''Calendar Settings''
# Click on either of the two XML buttons and copy the link that is shown.

Note that the provider does not directly use your private url. The Calendar is still accessible when you [http://www.google.com/support/calendar/bin/answer.py?answer=34576 reset your private url].

You may now use this url as the ''Location'' in the new remote calendar wizard.

=Bugs and Limitations=
Before reporting a bug, carefully check this list to see if the issue you are having is not a known limitation. The list is in FAQ format to make it easier to find your issue. If your question was not answer here, please add it to this page's discussion page. If you believe you have found a bug, please file it in [http://bugzilla.mozilla.org/ bugzilla]

==Can I create or view comments made within the Google Calendar Interface?==
Not currently. Progress on this is being tracked in {{bug|362653}}

==I want to modify an Event but nothing happens. What am I doing wrong?==
Is the event by chance a recurring event? If so, single instances of recurring events cannot be modified yet, they can only be viewed. Progress on this is being tracked in {{bug|362650}}.

The other possibility is that you tried to set the event status to ''Canceled''. Google uses this event status to mark deleted events. If the provider were to allow this, you would be losing your events at least every week.

Next check if you or somebody else is modifying the event from another client (which may also be the Google Calendar UI). The error mentioned below will contain something about ''Status Code: 409 Conflict''. This is a known issue. For now, try switching to a different view (that also contains the event you want to modify) and then retry editing the event. See {{bug|362645}} for details.

You should be getting an error in the error console ''Severe error in internal transaction code! Please report this to the developers''. You can safely ignore this error for now.

==I want to create a recurring event, but after it is created the event dosen't repeat. Why?==
Creating recurring events is not supported yet. You will be able to view recurring events created via the Google Calendar API, but you will not be able to change them or create new ones. Progress on this is being tracked in {{bug|362650}}.

==I tried to set an alarm on an event but the alarm dosen't show==
Alarms have not been implemented yet. Progress is being tracked in {{bug|362648}}.

Also, Google dosen't currently support alarms for non-default calendars. Progress on this issue is being tracked on [http://code.google.com/p/google-gdata/issues/detail?id=20 Google's bug 20].

==I want to invite someone to my event, but he is never notified==
The provider dosen't currently support attendees. See {{bug|355226}} for details.

==Why do all events I create or edit through Sunbird/Lightning have wrong times?==
Is your local timezone set up correctly in Sunbird/Lightning preferences? If not, all events you edit will have the first timezone with the same offset as the original timezone it was set in. Also, created events will use the timezone that was originally set in your timezones preference.

==All events I edit seem to dissappear from the public view of my calendar. How can I make them show for everyone?==
The provider cannot see which is the ''default'' setting for event visibility. It defaults to private, which means that all events are only visible to you.

To change this behavior, set the (string) preference ''<code>calendar.defaultprivacy'' to either ''private'' or ''public''.

==Why can't I create tasks on a Google Calendar?==
Google dosen't support Tasks, so there is no way the provider can support them.

Calendar:Module Ownership

2007-03-05T21:57:16Z

Lilmatt: /* Review Process */

This is a proposal of owners and peers of the calendar modules. '''It is not official yet!'''

Items without any owners at all are generally handled by those under "Default." However, in general, they could benefit from being their own strongly-owned modules at some point.

{| border="1" cellpadding="4"
!Module
!Owner
!Peers (alpha order)
|-
|Default (stuff under /mozilla/calendar not otherwise listed here)
|mvl
|jminta, lilmatt, daniel, mickey
|-
|colspan="3"|'''Applications/Extensions'''
|-
|Sunbird (calendar/sunbird)
|mvl
|jminta, daniel
|-
|Lightning (calendar/lightning)
|mvl
|jminta, daniel
|-
|colspan="3"|'''Components'''
|-
|Accessibility
|?
|?
|-
|Alarms
|jminta
|mvl, daniel
|-
|Art & Branding
|lilmatt
|MarkCarson
|-
|Calendar Manager
|mvl
|jminta, daniel
|-
|Import/Export (calendar/import-export)
|mvl
|mickey
|-
|Installer (calendar/installer)
|lilmatt
|rob_strong
|-
|i18n/l10n (calendar/locales)
|lilmatt
|?
|-
|libical (calendar/libical)
|mvl
|daniel, mickey
|-
|Recurrence
|daniel
|mvl, mickey
|-
|Timezones
|ctalbert
|mvl, lilmatt, daniel
|-
|Views & Dialogs (calendar/{sunbird/}base/content)
|mickey
|jminta, mvl
|-
|iTIP
|ctalbert
|lilmatt
|-
|Printing
|lilmatt
|daniel
|-
|Website
|sipaq
|lilmatt
|-
|colspan="3"|'''Providers'''
|-
|CalDAV
|bbrowning
|jminta
|-
|Composite
|mvl
|daniel, mickey
|-
|ICS
|mvl
|daniel, mickey
|-
|Memory
|mvl
|jminta, daniel
|-
|Storage
|mvl
|jminta, daniel
|-
|WCAP
|daniel
|?
|-
|colspan="3"|'''Tier-1 platform-specific stuff'''
|-
|Linux
|mvl
|jminta, daniel
|-
|Mac OS X
|lilmatt
|jminta
|-
|Windows
|ctalbert
|ssitter, daniel
|}

=== Review Process ===

This is also '''not official'''!

Calendar does not require super-review. The only review is needed is the review of a module owner or peer of the involved module. (If a patch spans multiple modules, you need review from an owner or peer from each module. That sounds problematic, but due to the huge overlap in owners and peers, in most cases it can be done by one person.)

If the module owner and their peers are all busy and don't have time to do a complete review, you can ask someone else to review the code. This must be 'known hacker', somebody who has done calendar work himself, but does not need to be a module owner or peer. If you have code review, you can ask a owner or peer of the module your code touches to give module-owner-approval. Giving this approval only means that the code is good from a high level point of view. Because this is a lot less work, it should be easier to get this approval.

Calendar:Status Meetings:2007-02-28

2007-02-28T06:07:04Z

Lilmatt: /* Agenda Items */

__NOTOC__
<<[[Calendar:Status Meetings:2007-02-21| previous meeting]] | [[Calendar:Status Meetings|index]] | [[Calendar:Status Meetings:2007-03-07| next meeting >>]]

== Meeting Details ==
*[http://www.timeanddate.com/worldclock/meetingtime.html?month=2&day=28&year=2007&pa=16&pa=37&pa=64&pa=179&pa=224 Wednesday, February 28th, 17:00 UTC]
* Phone meeting
* Join #calendar-mtg on irc.mozilla.org for attendance

=== Telephone Info ===
* Toll free numbers
** US/Canada: 800 867 8609
** Netherlands: 08002658232
** Germany: 08001014546
** Poland: 008001114706
** Sun: x44444
** More numbers (toll/toll free): [https://g8.cfer.com/g8.jsp?an=8008678609&ac=6064554&login=true Sun Worldwide Ready-Access numbers]
*Access Code
** 3646989
*Conference controls
** *6 mute line
** *7 unmute line
* Each time you say something, please say your name first so people know who's speaking

=== Agenda Items ===
* We need to go live with a team calendar (ala Google) - it's getting silly to keep track of this stuff without one.
** There were no objections to ctalbert's email
** Here is the calendar, currently ctalbert and Phillip have write access, we can of course change that.
** [http://www.google.com/calendar/embed?src=u7pke58sc91ksbm4h9pf9ofe8c%40group.calendar.google.com HTTP Link to Calendar]

* Need a 0.5 Status post to the blog -- Sipaq can you handle this?

* 0.5 Status Update
** Agree on the 0.5 schedule [http://groups.google.com/group/mozilla.dev.apps.calendar/browse_thread/thread/0e622962bea7c192/f1501e6951d37625#f1501e6951d37625 see lilmatt's post]
** Check out [[Calendar:Roadmap]] and [[Calendar:Next_Release]] for more details.

* Status of review system and module ownership/peers

* Next F2F Meeting?

* Farewell and good luck dmose

WeeklyUpdates/2007-02-26

2007-02-26T20:17:54Z

Lilmatt: /* Other */

[[WeeklyUpdates/2007-02-12| « previous week]] | [[WeeklyUpdates|index]] | [[WeeklyUpdates/2007-03-04|next week »]]

'''Meeting Details'''
* 1:00pm PST (21:00 UTC)
* Mozilla HQ, 1st floor conference table
* +1 866 879 4799 (pin 369) Conf# 8600 (US Toll Free)
* +1 650 903 0800 x91 Conf# 8600 (US/International)
* [Use *1 to mute yourself]
* join irc.mozilla.org #staffmeeting for attendance taking

= In Attendance =

= Development Updates =
== Fx/TB 1.5.0.10 + Fx 2.0.0.2 ==
== TB 2.0 ==

== Gecko 1.9 ==
== Firefox 3 ==
== Other ==
*Sunbird/Lightning 0.3.1 maintenance release to handle US (and elsewhere) Daylight Savings Time changes shipped on 2/19.

== IT ==
== Build ==
== QA ==

= Product Management and Marketing Updates =

== Product Management ==

== Marketing ==

== Community ==

== Developer Relations ==

== Webdev, Add-ons, AMO ==
= Foundation Updates =

= Roundtable =

= Other Business =

Calendar:Next Release

2007-02-26T05:00:20Z

Lilmatt: /* Thunderbird Integration */

<div style="border: thin dotted #aaa; padding: 10px;">
'''Please don't edit this page unless you are a member of the calendar team.''' To join in the discussion regarding the next calendar release, please see [http://groups.google.com/group/mozilla.dev.apps.calendar/browse_thread/thread/5adb513f0ade569e/e057ef42c42cf042#e057ef42c42cf042 this newsgroup thread].</div>

== Overview==
Sunbird and Lightning are aiming for a simultaneous release of their next version (0.5) in early 2007. This page is meant to provide an overview of the status of that release.

Items with a red background were originally targetted for version 0.3

==Key Development Areas==

===Core Architecture===
Develop Sunbird and Lightning's core architecture to be robust enough for new feature support and ease of future development.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P1 || Editing / viewing of events: Complete the move to using a controller to act on the data, instead of having the views do that directly. || style="color: green; white-space: nowrap;"| Complete
|}

===Performance===
Sunbird and Lightning will display all events and tasks with the correct information and in the correct places.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P1 || Improve performance of storage provider (daniel/mvl) || style="color: blue; white-space: nowrap;" | In progress
|-
| P1 || Improve performance of other providers (Sun team) || style="color: blue;" | In queue
|-
| P1 || Improve performance of views (mickey) || style="color: blue;" | In queue
|}

===Zoom/Scroll===
Sunbird and Lightning should allow easy navigation of calendars.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|<strike>P2</strike>||<strike>Investigate zoom scroll</strike> ||style="color: grey; white-space: nowrap;"| Dropped for 0.5
|}

===Navigation===
Sunbird and Lightning should allow users to move to any display they want.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|style="background-color: #fdd;"| P1 ||style="background-color: #fdd;"| A 'Go to Date' functionality should be exposed. (Lightning) || style="color: blue; white-space: nowrap;"| In progress
|}

===Workflow (user experience)===
Sunbird and Lightning should have an easy and intuitive user interface, allowing the user to get things done as effortlessly as possible.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P1 || [[Calendar:Improving_the_Calendar_Views|Determine major pain points]] (christian) || style="color: blue; white-space: nowrap;" | In progress
|-
| P1 || Come up with sketches for solutions (christian) || style="color: blue; white-space: nowrap;" | In progress
|-
| P2 || Implement Agenda View improvements || style="color: red;" | Unknown
|}

===Item Creation/Modification===
Sunbird and Lightning should allow users to create, modify, and interact with tasks and events easily.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|<strike>P1</strike>||<strike>Event vs. Task semantics - Determine what is require for usability and RFC2445 conformance</strike> ||style="color: grey; white-space: nowrap;"| Dropped for 0.5
|-
| P1 || Editting recurring events: "Edit just this" vs. "Edit this and all occurrences after" ||style="color: blue; white-space: nowrap;"| In progress
|-
| P2 || We should be registered to handle .ICS files - Mac||style="color: blue; white-space: nowrap;"| In progress
|-
| P2 || We should be registered to handle .ICS files - Windows||style="color: blue; white-space: nowrap;"| In progress
|-
| P2 || We should be registered to handle .ICS files - Unix||style="color: red;"| Unknown
|-
| P2 || We should be registered to handle webcal:// URLs - Mac||style="color: blue; white-space: nowrap;"| In progress
|-
| P2 || We should be registered to handle webcal:// URLs - Windows ||style="color: blue; white-space: nowrap;"| In progress
|-
| P2 || We should be registered to handle webcal:// URLs - Unix||style="color: red;"| Unknown
|-
| P2 || Double-clicking an .ICS file should open it (or subscribe, or offer to import it) ||style="color: blue; white-space: nowrap;"| In progress
|-
| P2 || Launching a webcal:// URL should add that subscription to the calendar list ||style="color: red;"| Unknown
|-
| P1 || Copying and pasting ICS from the clipboard should create an appropriate new item ||style="color: blue; white-space: no-wrap;"| In progress
|-
| P3 || Copying and pasting hCalendar data from the clipboard should create an appropriate new item ||style="color: red;"| Unknown
|-
| P3 || Copying and pasting events between Lightning and Sunbird should work properly ||style="color: red;"| Unknown
|}

===ICS Export===
Sunbird and Lightning should provide a way for users to export their data in a standards compliant format. This allows users to not need to enter a 'walled garden' when using Sunbird/Lightning

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|style="background-color: #fdd;"| P2 ||style="background-color: #fdd;"| Export of particular items/sets of items should be possible. (Lightning) || style="color: red;"| Unknown
|}

===Conflict Resolution===
Sunbird and Lightning should intelligently handle data conflicts, and present the user with a clear interface for the user to resolve any that it can't do itself.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P2 || Share an .ICS file on the network without dataloss ||style="color: red;"| Unknown
|-
| P2 || Offline storage of remote calendars ||style="color: red;"| Unknown
|-
| P2 || Gracefully handle conflicts between local and network data ||style="color: red;"| Unknown
|}

===Printing===
Sunbird and Lightning should provide an easy to use way for users to get their data in a paper format, through their printer.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|style="background-color: #fdd;"| P1 ||style="background-color: #fdd;"| Printing should be possible. (Lightning) || style="color: green;" | Complete
|-
|style="background-color: #fdd;"| P2 ||style="background-color: #fdd;"| Printing a week's view of items should be possible. || style="color: green;" | Complete
|}

===Publishing===
Sunbird and Lightning should allow users to publish their calendar information to a web server.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|style="background-color: #fdd;"| P2 ||style="background-color: #fdd;"| Publishing a specific set of items should be possible. (Lightning) || style="color: red;" | Unknown
|}

===Get Data In===
Users should be able to get calendar data from multiple sources into the application.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|style="background-color: #fdd;"| P1 ||style="background-color: #fdd;"| Standards compliant data should always be successfully read/preserved. || style="color: red;" | Unknown
|-
|style="background-color: #fdd;"| P1 ||style="background-color: #fdd;"| Errors in standards compliance should be gracefully handled. || style="color: red;" | Unknown
|-
| P2 || Import data from the user's existing calendar applications || style="color: green; white-space: nowrap;" | Complete
|}

===Thunderbird Integration===
Lightning should be integrated as seamlessly as possible into Thunderbird.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P2 || Integrate into Thunderbird's undo/redo queue || style="color: red;" | Unknown
|-
| P2 || Integrate into Thunderbird's copy/paste || style="color: green;" | Complete
|-
| P2 || Integrate into Thunderbird's print command || style="color: red;" | Unknown
|}

===Calendar Interoperation===
Users should be able to send and receive meeting invitations received via email.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P1 || Allow sending iMIP/iTIP invitations. || style="color: blue; white-space: nowrap;" | In progress
|-
| P1 || Allow sending decline/accept iMIP/iTIP responses. || style="color: blue; white-space: nowrap;" | In progress
|}

===Backup===
Sunbird and Lightning should provide functionality for users to easily backup and restore their data.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P3 || Make backups of data || style="color: red;" | Unknown
|}

===Dataloss===
Users should be able to use Sunbird/Lightning with confidence that their data will be preserved.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|style="background-color: #fdd;"| P1 ||style="background-color: #fdd;"| Subscribing to a calendar with unexpected data should preserve the data || style="color: red;" | Unknown
|-
|style="background-color: #fdd;"| P2 ||style="background-color: #fdd;"| Standards compliant data should be preserved when edited. || style="color: red;" | Unknown
|}

===Misc Regressions===
Users upgrading from past versions should not notice significant loss of functionality/usability.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P1 || "Misc Regressions" is provided to give it visibility during discussions. Individual elements do not exist at this time.
|}

===User pain-points from 0.3===
Wherever possible, we should attempt to address pain-points in 0.3 identified by our users. These were not determined scientifically. They're a "gut feeling" based on IRC, bugmail, and newsgroups.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee;"| '''Bug(s)'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee;"| '''Status'''
|-
|{{bug|349048}}||<strike>Having CalExt installed</strike>||FIXED
|-
|{{bug|349520}}||24 hour views (and no way to make them smaller)||In queue - tbe
|-
|{{bug|345643}}||<strike>Date formatting (MM/DD vs DD/MM)</strike>||FIXED
|-
|{{bug|343792}}||<strike>Data import errors - invalid or atypical ICS</strike>||FIXED
|-
|{{bug|354951}}||Data import errors - charset||
|-
|{{bug|310258}}||<strike>Hide completed tasks is missing from Lightning</strike>||FIXED
|}

Calendar:Next Release

2007-02-26T04:59:05Z

Lilmatt: bump release date

<div style="border: thin dotted #aaa; padding: 10px;">
'''Please don't edit this page unless you are a member of the calendar team.''' To join in the discussion regarding the next calendar release, please see [http://groups.google.com/group/mozilla.dev.apps.calendar/browse_thread/thread/5adb513f0ade569e/e057ef42c42cf042#e057ef42c42cf042 this newsgroup thread].</div>

== Overview==
Sunbird and Lightning are aiming for a simultaneous release of their next version (0.5) in early 2007. This page is meant to provide an overview of the status of that release.

Items with a red background were originally targetted for version 0.3

==Key Development Areas==

===Core Architecture===
Develop Sunbird and Lightning's core architecture to be robust enough for new feature support and ease of future development.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P1 || Editing / viewing of events: Complete the move to using a controller to act on the data, instead of having the views do that directly. || style="color: green; white-space: nowrap;"| Complete
|}

===Performance===
Sunbird and Lightning will display all events and tasks with the correct information and in the correct places.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P1 || Improve performance of storage provider (daniel/mvl) || style="color: blue; white-space: nowrap;" | In progress
|-
| P1 || Improve performance of other providers (Sun team) || style="color: blue;" | In queue
|-
| P1 || Improve performance of views (mickey) || style="color: blue;" | In queue
|}

===Zoom/Scroll===
Sunbird and Lightning should allow easy navigation of calendars.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|<strike>P2</strike>||<strike>Investigate zoom scroll</strike> ||style="color: grey; white-space: nowrap;"| Dropped for 0.5
|}

===Navigation===
Sunbird and Lightning should allow users to move to any display they want.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|style="background-color: #fdd;"| P1 ||style="background-color: #fdd;"| A 'Go to Date' functionality should be exposed. (Lightning) || style="color: blue; white-space: nowrap;"| In progress
|}

===Workflow (user experience)===
Sunbird and Lightning should have an easy and intuitive user interface, allowing the user to get things done as effortlessly as possible.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P1 || [[Calendar:Improving_the_Calendar_Views|Determine major pain points]] (christian) || style="color: blue; white-space: nowrap;" | In progress
|-
| P1 || Come up with sketches for solutions (christian) || style="color: blue; white-space: nowrap;" | In progress
|-
| P2 || Implement Agenda View improvements || style="color: red;" | Unknown
|}

===Item Creation/Modification===
Sunbird and Lightning should allow users to create, modify, and interact with tasks and events easily.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|<strike>P1</strike>||<strike>Event vs. Task semantics - Determine what is require for usability and RFC2445 conformance</strike> ||style="color: grey; white-space: nowrap;"| Dropped for 0.5
|-
| P1 || Editting recurring events: "Edit just this" vs. "Edit this and all occurrences after" ||style="color: blue; white-space: nowrap;"| In progress
|-
| P2 || We should be registered to handle .ICS files - Mac||style="color: blue; white-space: nowrap;"| In progress
|-
| P2 || We should be registered to handle .ICS files - Windows||style="color: blue; white-space: nowrap;"| In progress
|-
| P2 || We should be registered to handle .ICS files - Unix||style="color: red;"| Unknown
|-
| P2 || We should be registered to handle webcal:// URLs - Mac||style="color: blue; white-space: nowrap;"| In progress
|-
| P2 || We should be registered to handle webcal:// URLs - Windows ||style="color: blue; white-space: nowrap;"| In progress
|-
| P2 || We should be registered to handle webcal:// URLs - Unix||style="color: red;"| Unknown
|-
| P2 || Double-clicking an .ICS file should open it (or subscribe, or offer to import it) ||style="color: blue; white-space: nowrap;"| In progress
|-
| P2 || Launching a webcal:// URL should add that subscription to the calendar list ||style="color: red;"| Unknown
|-
| P1 || Copying and pasting ICS from the clipboard should create an appropriate new item ||style="color: blue; white-space: no-wrap;"| In progress
|-
| P3 || Copying and pasting hCalendar data from the clipboard should create an appropriate new item ||style="color: red;"| Unknown
|-
| P3 || Copying and pasting events between Lightning and Sunbird should work properly ||style="color: red;"| Unknown
|}

===ICS Export===
Sunbird and Lightning should provide a way for users to export their data in a standards compliant format. This allows users to not need to enter a 'walled garden' when using Sunbird/Lightning

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|style="background-color: #fdd;"| P2 ||style="background-color: #fdd;"| Export of particular items/sets of items should be possible. (Lightning) || style="color: red;"| Unknown
|}

===Conflict Resolution===
Sunbird and Lightning should intelligently handle data conflicts, and present the user with a clear interface for the user to resolve any that it can't do itself.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P2 || Share an .ICS file on the network without dataloss ||style="color: red;"| Unknown
|-
| P2 || Offline storage of remote calendars ||style="color: red;"| Unknown
|-
| P2 || Gracefully handle conflicts between local and network data ||style="color: red;"| Unknown
|}

===Printing===
Sunbird and Lightning should provide an easy to use way for users to get their data in a paper format, through their printer.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|style="background-color: #fdd;"| P1 ||style="background-color: #fdd;"| Printing should be possible. (Lightning) || style="color: green;" | Complete
|-
|style="background-color: #fdd;"| P2 ||style="background-color: #fdd;"| Printing a week's view of items should be possible. || style="color: green;" | Complete
|}

===Publishing===
Sunbird and Lightning should allow users to publish their calendar information to a web server.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|style="background-color: #fdd;"| P2 ||style="background-color: #fdd;"| Publishing a specific set of items should be possible. (Lightning) || style="color: red;" | Unknown
|}

===Get Data In===
Users should be able to get calendar data from multiple sources into the application.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|style="background-color: #fdd;"| P1 ||style="background-color: #fdd;"| Standards compliant data should always be successfully read/preserved. || style="color: red;" | Unknown
|-
|style="background-color: #fdd;"| P1 ||style="background-color: #fdd;"| Errors in standards compliance should be gracefully handled. || style="color: red;" | Unknown
|-
| P2 || Import data from the user's existing calendar applications || style="color: green; white-space: nowrap;" | Complete
|}

===Thunderbird Integration===
Lightning should be integrated as seamlessly as possible into Thunderbird.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P2 || Integrate into Thunderbird's undo/redo queue || style="color: red;" | Unknown
|-
| P2 || Integrate into Thunderbird's copy/paste || style="color: red;" | Unknown
|-
| P2 || Integrate into Thunderbird's print command || style="color: red;" | Unknown
|}

===Calendar Interoperation===
Users should be able to send and receive meeting invitations received via email.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P1 || Allow sending iMIP/iTIP invitations. || style="color: blue; white-space: nowrap;" | In progress
|-
| P1 || Allow sending decline/accept iMIP/iTIP responses. || style="color: blue; white-space: nowrap;" | In progress
|}

===Backup===
Sunbird and Lightning should provide functionality for users to easily backup and restore their data.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P3 || Make backups of data || style="color: red;" | Unknown
|}

===Dataloss===
Users should be able to use Sunbird/Lightning with confidence that their data will be preserved.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|style="background-color: #fdd;"| P1 ||style="background-color: #fdd;"| Subscribing to a calendar with unexpected data should preserve the data || style="color: red;" | Unknown
|-
|style="background-color: #fdd;"| P2 ||style="background-color: #fdd;"| Standards compliant data should be preserved when edited. || style="color: red;" | Unknown
|}

===Misc Regressions===
Users upgrading from past versions should not notice significant loss of functionality/usability.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P1 || "Misc Regressions" is provided to give it visibility during discussions. Individual elements do not exist at this time.
|}

===User pain-points from 0.3===
Wherever possible, we should attempt to address pain-points in 0.3 identified by our users. These were not determined scientifically. They're a "gut feeling" based on IRC, bugmail, and newsgroups.

{| width="100%" cellpadding="3"
|-
| style="background-color: #eee;"| '''Bug(s)'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee;"| '''Status'''
|-
|{{bug|349048}}||<strike>Having CalExt installed</strike>||FIXED
|-
|{{bug|349520}}||24 hour views (and no way to make them smaller)||In queue - tbe
|-
|{{bug|345643}}||<strike>Date formatting (MM/DD vs DD/MM)</strike>||FIXED
|-
|{{bug|343792}}||<strike>Data import errors - invalid or atypical ICS</strike>||FIXED
|-
|{{bug|354951}}||Data import errors - charset||
|-
|{{bug|310258}}||<strike>Hide completed tasks is missing from Lightning</strike>||FIXED
|}

Calendar:QA TestDay:2007-02-09

2007-02-09T07:01:40Z

Lilmatt: updated links

{{Template:Calendar:Testday_Intro|
starthour=13|
startminute=00|
year=2007|
month=February|
startday=9|
endday=10|
startdayEnding=th|
enddayEnding=th|
endhour=01|
endminute=00}}

{{Template:Calendar:Testday_BuildAndTest|
SunbirdBuildLink=http://releases.mozilla.org/pub/mozilla.org/calendar/sunbird/releases/0.3.1rc1/|
LightningBuildLink=http://releases.mozilla.org/pub/mozilla.org/calendar/lightning/releases/0.3.1rc1/|
WhatWillWeTest=We will be testing ONLY 0.3.1 builds. We need to test all localizations as well as the calendaring functionality. We need to ensure that 0.3.1 is ready for release.

You can download these builds from the above links.

We need to test these Localizations:
* Catalan (ca)
* Czech (cs)
* Danish (da)
* German (de)
* Spanish (Spain) (es-ES)
* Basque (eu)
* French (fr)
* <strike>Irish (ga-IE)</strike>
* Hungarian (hu)
* Italian (it)
* Dutch (nl)
* Polish (pl)
* Russian (ru)
* Slovak (sk)
* Slovenian (sl)

On each locale we need to be sure that:
* All dialogs and windows display properly
* Access keys work
* Translations are clear and accurate
* Input with that locale's alphabet is accepted and displayed properly

We need to test the following in both 0.3.1 clean installs and upgrade (from 0.3) installs:
* All recurring appointments
* Changed Timezones
* All Calendar Types
* Drag/Drop
* Copy?Paste
* Navigation|
SbirdLinId=TODO|
LtnLinId=TODO|
SbirdMacId=TODO|
LtnMacId=TODO|
SbirdWinId=TODO|
LtnWinId=TODO|
UnconfirmedBugTotal=TODO}}

== Rewards ==
The reward for this test day will be the pride and comfort in releasing a well tested, quality release for 0.3.1. The tester that runs through the most locales and the most tests will have his or her nickname proudly displayed in our channel topic until the next test day. And of course, should you discover a high priority bug that stops the release, then you will win.

Thank you very much for your help.

Calendar:Updating Timezones

2007-02-09T01:16:22Z

Lilmatt:

(More detail to come later)

We made the choice to provide Outlook 2000 and 2003 compatible timezones in 0.3.1.
Using technically correct timezones output from Olson and vzic (using --pure) would not work with those versions of Outlook. Unfortunately, when instructing vzic to output Outlook-compatible timezones (which it does by default), if a zone's ruleset is too complex to be expressed in an Outlook-compatible way, vzic simply ignores Daylight Savings Time altogether, and only gives includes a BEGIN:STANDARD section in the VTIMEZONE.

As part of {{bug|369543}} and {{bug|367378}}, we had to find which timezones this affected, and attempt to make a VTIMEZONE that was simple enough for Outlook, but that still was as correct as possible.

/Australia/Perth and /America/Tegucigalpa both had DST with a set end date in the future, for example 2009. vzic's interpretation of these timezones were ones with a number of RDATEs, which would bust Outlook. By pretending that DST would go on forever (which it may) we were able to make a VTIMEZONE with two RRULEs. This would work with Outlook.

/Asia/Jerusalem was entirely different. It's DST are so complex that we were unable to both create an "accurate-enough" VTIMEZONE and still keep it Outlook-compatible. As a result, we took the VTIMEZONE created by vzic when run with --pure, and included a release note that .ICS files with events in /Asia/Jerusalem would likely not import cleanly into Outlook <= 2003.

Asia/Jerusalem
The proposed law agreed upon by the Knesset Interior Committee on
2005-02-14 is that, for 2005 and beyond, DST starts at 02:00 the
last Friday before April 2nd (i.e. the last Friday in March or April
1st itself if it falls on a Friday) and ends at 02:00 on the Saturday
night _before_ the fast of Yom Kippur.

Those who can read Hebrew can view the announcement at:
ftp://ftp.cs.huji.ac.il/pub/tz/announcements/2005+beyond.ps

From Paul Eggert (2005-02-22):
I used Ephraim Silverberg's dst-israel.el program
<ftp://ftp.cs.huji.ac.il/pub/tz/software/dst-israel.el> (2005-02-20)
along with Ed Reingold's cal-hebrew in GNU Emacs 21.4,
to generate the transitions in this list.
(I replaced "lastFri" with "Fri>=26" by hand.)
The spring transitions below all correspond to the following Rule:

Rule Zion 2005 max - Mar Fri>=26 2:00 1:00 D

but older zic implementations (e.g., Solaris 8) do not support
"Fri>=26" to mean April 1 in years like 2005, so for now we list the
springtime transitions explicitly.

Calendar:Build Team Requests

2007-02-06T15:12:24Z

Lilmatt: /* Completed */

== High Priority ==

None at this time.

== Med Priority ==

*Update gcc on 'Linux galactica Depend Lt-Release' trunk tinderbox
**{{bug|356663}}

*galactica trunk builds need new pango and cairo switches to be thrown
**{{bug|332900}}

== Completed ==

<strike>
*Upgrade solaria (sunbird trunk tinderbox) to MSVC8
**[https://bugzilla.mozilla.org/show_bug.cgi?id=340192 bug 340192]
**preed said he'd rather set up VMs for Sunbird than to upgrade the cantankerous solaria. Perhaps the VM can be duplicated for the Sunbird branch builds?
</strike>

<strike>
*Windows Lightning builds are uploaded to wrong directory
**[https://bugzilla.mozilla.org/show_bug.cgi?id=341089 bug 341089]
</strike>

<strike>
*Configure Sunbird (trunk) tinderbox to ship MSVC8 runtime libs
**{{bug|342699}}
</strike>

<strike>
*Make Mac Sunbird tinderbox build Univeral Binaries
**[https://bugzilla.mozilla.org/show_bug.cgi?id=340920 bug 340920]
**Current Mac tinderbox (hilo running OSX 10.3.9) can't build Universal Binaries.
</strike>

<strike>
*Perform necessary infrastructure work to allow aus updates for Sunbird (both regular and nightly)
**{{bug|318927}}
**{{bug|341971}}
</strike>

<strike>
*Install UPX on solaria (sunbird mozilla1.8 branch tinderbox)
**{{bug|367108}}
</strike>

<strike>
*Add building Sunbird from MOZILLA_1_8_BRANCH to Sunbird-Mozilla1.8 tree
**{{bug|340406}}
**Current Mac and Windows boxes are slow already. Adding another Sb build will require some thought/work to keep build times and build frequency reasonable. Linux seems snappy™ enough. The Mac needs to be able to build Universal binaries.
</strike>

<strike>
*Add Sunbird to l10n tinderboxen
**{{bug|340845}}
**Sunbird is now using /l10n for locales. Add it to all l10n trunk and branch tinderboxes, and add an iframe for it to the Mozilla-l10n tree page.
**Note that the list of available locales differs between trunk and branch
</strike>

Calendar:Build Team Requests

2007-02-06T15:11:52Z

Lilmatt:

== High Priority ==

None at this time.

== Med Priority ==

*Update gcc on 'Linux galactica Depend Lt-Release' trunk tinderbox
**{{bug|356663}}

*galactica trunk builds need new pango and cairo switches to be thrown
**{{bug|332900}}

== Completed ==

<strike>
*Upgrade solaria (sunbird trunk tinderbox) to MSVC8
**[https://bugzilla.mozilla.org/show_bug.cgi?id=340192 bug 340192]
**preed said he'd rather set up VMs for Sunbird than to upgrade the cantankerous solaria. Perhaps the VM can be duplicated for the Sunbird branch builds?
</strike>

<strike>
*Windows Lightning builds are uploaded to wrong directory
**[https://bugzilla.mozilla.org/show_bug.cgi?id=341089 bug 341089]
</strike>

<strike>
*Configure Sunbird (trunk) tinderbox to ship MSVC8 runtime libs
**{{bug|342699}}
</strike>

<strike>
*Make Mac Sunbird tinderbox build Univeral Binaries
**[https://bugzilla.mozilla.org/show_bug.cgi?id=340920 bug 340920]
**Current Mac tinderbox (hilo running OSX 10.3.9) can't build Universal Binaries.
</strike>

<strike>
*Perform necessary infrastructure work to allow aus updates for Sunbird (both regular and nightly)
**{{bug|318927}}
**{{bug|341971}}
</strike>

<strike>
*Install UPX on solaria (sunbird mozilla1.8 branch tinderbox)</strike>
**{{bug|367108}}
</strike>

<strike>
*Add building Sunbird from MOZILLA_1_8_BRANCH to Sunbird-Mozilla1.8 tree
**{{bug|340406}}
**Current Mac and Windows boxes are slow already. Adding another Sb build will require some thought/work to keep build times and build frequency reasonable. Linux seems snappy™ enough. The Mac needs to be able to build Universal binaries.
</strike>

<strike>
*Add Sunbird to l10n tinderboxen
**{{bug|340845}}
**Sunbird is now using /l10n for locales. Add it to all l10n trunk and branch tinderboxes, and add an iframe for it to the Mozilla-l10n tree page.
**Note that the list of available locales differs between trunk and branch
</strike>