Calendar:Next Release: Difference between revisions
(Bug 343792 was fixed.) |
|||
Line 266: | Line 266: | ||
|{{bug|345643}}||<strike>Date formatting (MM/DD vs DD/MM)</strike>||FIXED | |{{bug|345643}}||<strike>Date formatting (MM/DD vs DD/MM)</strike>||FIXED | ||
|- | |- | ||
|{{bug|343792}}||Data import errors - invalid or atypical ICS|| | |{{bug|343792}}||<strike>Data import errors - invalid or atypical ICS</strike>||FIXED | ||
|- | |- | ||
|{{bug|354951}}||Data import errors - charset|| | |{{bug|354951}}||Data import errors - charset|| |
Revision as of 20:59, 7 January 2007
To join in the discussion regarding the next calendar release, please see this newsgroup thread.
Overview
Sunbird and Lightning are aiming for a simultaneous release of their next version in January 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.
Priority | Item | 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. | Complete |
Performance
Sunbird and Lightning will display all events and tasks with the correct information and in the correct places.
Priority | Item | Status |
P1 | Improve performance of storage provider (daniel/mvl) | In progress |
P1 | Improve performance of other providers (ssa and team) | In queue |
P1 | Improve performance of views (mickey) | In queue |
Zoom/Scroll
Sunbird and Lightning should allow easy navigation of calendars.
Priority | Item | Status |
Dropped |
Sunbird and Lightning should allow users to move to any display they want.
Priority | Item | Status |
P1 | A 'Go to Date' functionality should be exposed. (Lightning) | 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.
Priority | Item | Status |
P1 | Determine major pain points (christian) | In progress |
P1 | Come up with sketches for solutions (christian) | In progress |
P2 | Implement Agenda View improvements | Unknown |
Item Creation/Modification
Sunbird and Lightning should allow users to create, modify, and interact with tasks and events easily.
Priority | Item | Status |
P1 | Event vs. Task semantics - Determine what is require for usability and RFC2445 conformance (ssa) | In progress |
P1 | Editting recurring events: "Edit just this" vs. "Edit this and all occurrences after" | In progress |
P2 | We should be registered to handle .ICS files - Mac | In progress |
P2 | We should be registered to handle .ICS files - Windows | Unknown |
P2 | We should be registered to handle .ICS files - Unix | Unknown |
P2 | We should be registered to handle webcal:// URLs - Mac | In progress |
P2 | We should be registered to handle webcal:// URLs - Windows | Unknown |
P2 | We should be registered to handle webcal:// URLs - Unix | Unknown |
P2 | Double-clicking an .ICS file should open it (or subscribe, or offer to import it) | Unknown |
P2 | Launching a webcal:// URL should add that subscription to the calendar list | Unknown |
P1 | Copying and pasting ICS from the clipboard should create an appropriate new item | In progress |
P3 | Copying and pasting hCalendar data from the clipboard should create an appropriate new item | Unknown |
P3 | Copying and pasting events between Lightning and Sunbird should work properly | 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
Priority | Item | Status |
P2 | Export of particular items/sets of items should be possible. (Lightning) | 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.
Priority | Item | Status |
P2 | Share an .ICS file on the network without dataloss | Unknown |
P2 | Offline storage of remote calendars | Unknown |
P2 | Gracefully handle conflicts between local and network data | 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.
Priority | Item | Status |
P1 | Printing should be possible. (Lightning) | Complete |
P2 | Printing a week's view of items should be possible. | Complete |
Publishing
Sunbird and Lightning should allow users to publish their calendar information to a web server.
Priority | Item | Status |
P2 | Publishing a specific set of items should be possible. (Lightning) | Unknown |
Get Data In
Users should be able to get calendar data from multiple sources into the application.
Priority | Item | Status |
P1 | Standards compliant data should always be successfully read/preserved. | Unknown |
P1 | Errors in standards compliance should be gracefully handled. | Unknown |
P2 | Import data from the user's existing calendar applications | Complete |
Thunderbird Integration
Lightning should be integrated as seamlessly as possible into Thunderbird.
Priority | Item | Status |
P2 | Integrate into Thunderbird's undo/redo queue | Unknown |
P2 | Integrate into Thunderbird's copy/paste | Unknown |
P2 | Integrate into Thunderbird's print command | Unknown |
Calendar Interoperation
Users should be able to send and receive meeting invitations received via email.
Priority | Item | Status |
P1 | Allow sending iMIP/iTIP invitations. | In progress |
P1 | Allow sending decline/accept iMIP/iTIP responses. | In progress |
Backup
Sunbird and Lightning should provide functionality for users to easily backup and restore their data.
Priority | Item | Status |
P3 | Make backups of data | Unknown |
Dataloss
Users should be able to use Sunbird/Lightning with confidence that their data will be preserved.
Priority | Item | Status |
P1 | Subscribing to a calendar with unexpected data should preserve the data | Unknown |
P2 | Standards compliant data should be preserved when edited. | Unknown |
Misc Regressions
Users upgrading from past versions should not notice significant loss of functionality/usability.
Priority | Item | 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.
Bug(s) | Item | Status |
bug 349048 | FIXED | |
bug 349520 | 24 hour views (and no way to make them smaller) | In queue - tbe |
bug 345643 | FIXED | |
bug 343792 | FIXED | |
bug 354951 | Data import errors - charset | |
bug 310258 | FIXED |