Information regarding the 3rd Mozilla Calendar Developers Face-to-Face Meeting

Americans should read 20 things to keep in mind when visiting Germany first :-)

Who

When

Where

Meeting

Sun Microsystems GmbH
Nagelsweg 55
20097 Hamburg
Germany

Map

Lodging Proposals

• Junges Hotel
• Hanse Clipper Haus Boardinghouse nice location
• Wedina nice location
• SAS Radisson (Favorite, good public transportation)
• Dorint Novotel Hamburg Alster

Public Transportation

• take the S31 (direction: Harburg Rathaus) or S3 (direction: Stade)
• get out at Hammerbrook (City Süd)

.

Agenda

	THIS PAGE IS A WORKING DRAFT
	The page may be difficult to navigate, and some information on its subject might be incomplete and/or evolving rapidly. If you have any questions or ideas, please add them as a new topic on the discussion page.

tbd, add your name, pick a slot!

• Find ways to recruit more people for the Calendar Project. Your help is needed!
• If a lot of first-time vistors join, we may even offer a hands-on workshop!

Day 1 (Saturday)

Day 2 (Sunday)

Day 3 (Monday)

Day 4 (Tuesday)

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.

Results

Day 1 (Saturday)

Task mode in Sunbird

• Can be implemented by community
• Should be implemented as a mode, technically.
• This will mean more code consolidation, and easier addition of further modes (i.e journal mode) by only moving UI and some extra code.
• Implement as a view button for the user

Unifinder

• How does mac ical do it?
• Some like it, others hate it
• Could be changed to only be shown with search results when searching
  • Search bar integration with thunderbird, create similar bar for sunbird.

Leaks and Performance

• Roadmap spreadsheet: Split point 90 into finding, fighting, fixing.
• Leaks not strictly blocking, but storage provider should be improved.

High level goals for 0.9 These goals were brainstormed. It might be a good idea to define high level goals and then in a second pass try to define specific features, and in a third pass define specific bugs.

• 80% of daily use UI should be "usable"
• Being interoperable
• Improve performance: Make a standard manager calendar be usable

Versioning ideas

• Next release is the last branch release
• If quality isn't "good enough", then calling the release 1.0 might hurt the Mozilla Brand, since round versions have always meant quality.
• If quality is sufficient, the next release will be called 1.0, otherwise 0.9
• Afterwards, we should switch to trunk
• If Thunderbird 3 is delayed, possibly add another release on branch.

Day 3 (Monday)

Accessibility

• MarcoZ held an interesting talk about accessibility
• In thunderbird, the list of email addresses (i.e To, CC) is not very accessible
• In calendar, the calendar grid is not very accessible
• MarcoZ is happy to test builds for accessibility, if someone provides them
• MacOSX is not very accessible, Windows has had screen readers for 13 years, linux is a bit younger
• Gnome has a pre-installed, integrated screen reader called orca
• Common windows screen reader is called NVDA.
• In order to make a binding accessible, nsIAccessibleProvider has to be implemented, possibly also nsIAccessible if common objects cannot be used.
• There should be keybindings for every possible command.
• Every user-accessible element should be in the taborder