350
edits
(moving roadmap bugs) |
|||
| (18 intermediate revisions by 3 users not shown) | |||
| Line 2: | Line 2: | ||
Americans should read [http://www.tobsy.de/?p=22 20 things to keep in mind when visiting Germany] first :-) | Americans should read [http://www.tobsy.de/?p=22 20 things to keep in mind when visiting Germany] first :-) | ||
__TOC__ | |||
=Who= | =Who= | ||
| Line 78: | Line 78: | ||
</table> | </table> | ||
== Agenda | == Agenda == | ||
=== Day 1 (Saturday) === | === Day 1 (Saturday) === | ||
{| border="1" cellpadding="3" width="100%" valign="top" | {| border="1" cellpadding="3" width="100%" valign="top" | ||
| Line 214: | Line 214: | ||
* 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 [http://developer.mozilla.org/en/docs/Mochitest_FAQ MochiTest] 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. | * 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 [http://developer.mozilla.org/en/docs/Mochitest_FAQ MochiTest] 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 ({{bug|365212}}). 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. | * We also decided that until the new UI lands, we should begin writing API tests that use XPCShell ({{bug|365212}}). 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. | ||
* Matt outlined the build-system, release process, and Tinderbox setup process to one of the release engineers at Sun. | * Matt outlined the build-system, release process, and Tinderbox setup process to ause, one of the release engineers at Sun. | ||
* We also talked at great length about how to perform invitations in the new UI that we decided on to better integrate Lightning into Thunderbird. We decided that there will be an invitation management UI that will be part of the "calendar" mode. We will indicate the number of invitations (both email and server based invitations) by bumping a number next to the "calendar mode" icon. (This is similiar to the way that a number for new emails are shown as an icon next to the thunderbird icon). Once you click the calendar mode button the calendar view shows up wnad you have an invitation dialog available. YOu will be able to accept/tentatively accept/decline the invitations from this UI. You will also be able to drag the invitations from this UI into some other calendar (which generates an "Accept"). If you double click on a invitation from this UI you will see the invitation displayed in a "read only" version of the event dialog. Default behavior will be to accept, and as far as sending notifications back, it will default to bring up the compose window to allow the user to edit the response. | * We also talked at great length about how to perform invitations in the new UI that we decided on to better integrate Lightning into Thunderbird. We decided that there will be an invitation management UI that will be part of the "calendar" mode. We will indicate the number of invitations (both email and server based invitations) by bumping a number next to the "calendar mode" icon. (This is similiar to the way that a number for new emails are shown as an icon next to the thunderbird icon). Once you click the calendar mode button the calendar view shows up wnad you have an invitation dialog available. YOu will be able to accept/tentatively accept/decline the invitations from this UI. You will also be able to drag the invitations from this UI into some other calendar (which generates an "Accept"). If you double click on a invitation from this UI you will see the invitation displayed in a "read only" version of the event dialog. Default behavior will be to accept, and as far as sending notifications back, it will default to bring up the compose window to allow the user to edit the response. | ||
** We also discovered that by using a Filter, you can filter messages based on the "Content-Type" setting, and if you do that, it seems that the filtering code pre-screens the message in order to determine information about the attachments. This means that we might be able to do the same thing in order to "under the covers" load emailed invitations into the invitation management system. | ** We also discovered that by using a Filter, you can filter messages based on the "Content-Type" setting, and if you do that, it seems that the filtering code pre-screens the message in order to determine information about the attachments. This means that we might be able to do the same thing in order to "under the covers" load emailed invitations into the invitation management system. | ||
| Line 277: | Line 277: | ||
* By storing the provider's timezone version (a value that is changed when the provider's timezone definitions change), and by always storing the provider timezone definition we may be able to mitigate the timezone destruction caused by having two versions of Calendar access the same ICS file. | * By storing the provider's timezone version (a value that is changed when the provider's timezone definitions change), and by always storing the provider timezone definition we may be able to mitigate the timezone destruction caused by having two versions of Calendar access the same ICS file. | ||
'''Possible Items to store in a central timezone mapping database''' | '''Possible Items to store in a central timezone mapping database, or in the storage provider so that it can be used as an offline storage cache for providers''' | ||
* Provider UID ( this would include UID for Mozilla providers i.e. local storage etc) | * Provider UID ( this would include UID for Mozilla providers i.e. local storage etc) | ||
* Provider timezone version | * Provider timezone version | ||
| Line 286: | Line 286: | ||
* Mozilla Tzid value | * Mozilla Tzid value | ||
* Mozilla zone definition | * Mozilla zone definition | ||
=== Resulting Bugs === | |||
These bugs were either filed as a result of the meeting or were spoken of during the meeting. | |||
'''TODO: File them, add them.''' | |||
* {{bug|373330}} (Can't Browse Sunbird Addons} | |||
* {{bug|327783}} (Offer more ways to switch between mail/calendar views) | |||
* {{bug|379005}} (Create Stub Extension that allows <em:requires> tags in Sunbird/Lightning Extensions) | |||
* {{bug|378872}} (Make providers easily pluggable) | |||
* {{bug|306692}} (Simplify file menu (New calendar vs. Subscribe to calendar)) | |||
* {{bug|314594}} (No error message if invalid URL used for new calendar, creates invalid calendars) | |||
* {{bug|379029}} (Add provider capabilities to calICalendarProvider interface) | |||
* {{bug|365212}} (Use xpcshell based unit test framework) | |||
* {{bug|313822}} (Make lightning work on SeaMonkey) | |||
* {{bug|366923}} (implement changelog-based offline support) | |||
* {{bug|196942}} (Ability to replicate server events to local for offline viewing) | |||
* {{bug|360799}} ([RFE] Lightning - Email Alerts) | |||
* {{bug|379200}} (Thunderbird should show an invitation icon next to the messages that contain invitations) | |||
* {{bug|378270}} (Remove 'Rotate' button and move the rotate option to the views menu) | |||
A list of these bugs as a bugzilla search can be found [https://bugzilla.mozilla.org/buglist.cgi?bug_id=196942%2C306692%2C313822%2C314594%2C327783%2C360799%2C365212%2C366923%2C373330%2C378872%2C379005%2C379029%2C379200%2C378270 here] | |||
'''Roadmap Bugs''' have been moved to [[Calendar:Roadmap#Roadmap_Bugs|Roadmap Page]]. | |||
edits