MozillaWiki - User contributions [en]

Thunderbird/StatusMeetings/2010-02-16

2010-02-16T15:56:29Z

XFallenAngel: /* Lightning Updates */

[[Thunderbird/StatusMeetings/2010-02-09|last meeting]] | [[Thunderbird/StatusMeetings|index]] | [[Thunderbird/StatusMeetings/2010-02-23|next meeting »]]

{|
|+ '''Current Release Schedules'''
!width="50%" | Thunderbird 3.1 Beta 1 !!width="50%" | Thunderbird 3.0.2
|-
| {{:Thunderbird:Thunderbird 3.1b1}}
| {{:Releases/Thunderbird 3.0.2}}
|}

'''Thunderbird Meeting Details''' :

*[http://www.timeanddate.com/worldclock/fixedtime.html?year=2010&month=02&day=16&hour=17&min=30&sec=0 Tuesday, February 16th, 17:30 UTC] (9:30am Pacific, 12:30pm Eastern)
*[[Thunderbird/StatusMeeting/DialInInfo|How to dial-in]]

== Agenda ==

*Who's taking minutes? --> '''davida'''
*[http://ascher.ca/thunderbird/minutes_schedule.html Minute taking Schedule]. Talk to davida for schedule changes/additions.

=== Action Items ===

* '''Open:''' Planning for a dry-run security firedrill build
** Checklist: [[Thunderbird/Release_Driving/Firedrills|draft checklist for firedrill actions]]
** gozer and Standard8 to 'schedule' run through
* '''New:''' Go over [http://docs.google.com/View?id=dcrkwqp5_3dfdfc4hc Lehigh U feedback]
** kathy.f/wayne/clarkbw: to meet re: ue feedback space management/migration assistant
** dan.s/bwinton: to meet re: ispdb
** http://byob.mozilla.com need to explore to have something for Tbird.

=== Friends of the Tree ===

Thanks to our [http://developer.mozilla.org/en/Glossary#FotT Friends of the Tree] When adding someone to this section, please get their T-Shirt size and send it to rebron@mozillamessaging.com so that he can send them a shirt!

* Nathan Tuggy for is good work in bugzilla.

=== [[Thunderbird:Thunderbird3.1|Thunderbird 3.1 (Lanikai)]] ===

* UX/Feature work being driven from [[Thunderbird:UX/Priorities/3.1]]; however, only some things on that page are blockers
* non-versioned wanted-thunderbird flag created
* Bug lists: [[Thunderbird:Thunderbird3.1:Status_Tracking]]
** beta1 slipped; string/code freeze 2 weeks from today
** bug triage in progress; first pass to be completed EOD tomorrow (Weds)
*** high risk that we'll need to add a beta 2 once triage completed
* Discussion about specifics of cutting the 1.9.2 version of comm-central in progress; details soon

==== Lanikai Alpha 1 ====

* [http://weblogs.mozillazine.org/dmose/archives/2010/02/lanikai_alpha_1.html Shipped] (W00t!)

==== Thunderbird 3.1 Beta 1 ====

{{:Thunderbird:Thunderbird 3.1b1}}

=== Thunderbird 3.0.x Developer Update ===

See [http://tinderbox.mozilla.org/showbuilds.cgi?tree=Thunderbird3.0 Tinderbox] for how to get your patches into 3.0.x

==== Thunderbird 3.0.2 ====

* See Schedule above.
* Generally smaller amount of fixes than 3.0.1, but still improving user experience for upgrades and stability.

* [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=ALL%20blocking-thunderbird3.0:needed|blocking-thunderbird3.0:.2+%20-status-thunderbird3.0:fixed&order=map_assigned_to.login_name,bugs.bug_id Blockers (needed and .2)]: 28 (+1)
** Of which [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=ALL%20blocking-thunderbird3.0:.2+%20-status-thunderbird3.0:.2-fixed&order=map_assigned_to.login_name,bugs.bug_id blocking 3.0.2]: 7 (+1)
* [https://bugzilla.mozilla.org/buglist.cgi?field0-0-0=cf_blocking_thunderbird30;query_format=advanced;type0-0-0=equals;value0-0-0=%3F Blocking Nominations]: 10 (+1)
* [https://bugzilla.mozilla.org/buglist.cgi?field0-0-0=cf_status_thunderbird30;query_format=advanced;type0-0-0=equals;value0-0-0=.2-fixed Fixed 3.0.2]: 40 (+4)

=== QA Updates ===
last week :
* Usual event and bug following

This week :
* Normal bugzilla [[Thunderbird:QA_TestDay:2010-02-18|cleaning/maintainance event]].
* Testing for 3.0.2 - announced , litmus run ready.
* Testing for 2.0.24 with the Moco team

Next week :
* [[Thunderbird:QA_TestDay:2010-02-25 | Testday for 3.1b1]] - in progress
* Preparing the 3.1b1 see [https://mail.mozilla.org/pipermail/thunderbird-testers/2010-February/000037.html Full test before release]. We need more man power, please consider joining.

3.0.1 top crashers:
 

{| class="fullwidth-table"
|-
| style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | '''status'''
| style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | '''bug'''
| style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | '''summary'''
| style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | # crash /week
|-
| style="background: red none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | Null signature - no progress
|
|
| 1088 That's 0,011% of our users for the week
|-
| style="background: red none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | Unassigned - no progress
| {{Bug|536308}}
| arena_dalloc_small | arena_dalloc | free | sqlite3_free | pcache1TruncateUnsafe
| 1047
|-
| style="background: Yellow none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | Assigned - no progress
| {{Bug|536960}}
| sqlite3DbMallocRaw
| 1035
|-
| style="background: Green none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | Fixed 
| {{bug|272361}}
| nsMessengerWinIntegration::SetupInbox()
| 933
|-
| style="background: Yellow none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | Needs landing on Branch
| {{Bug|505016}}
| _purecall | nsXPCWrappedJS::QueryInterface(nsID const&, void**)
| 842
|}

=== Marketing Updates ===

=== IT update ===

=== Documentation ===

(last two weeks)

* expand Profiles KB article (TODO - moving and backing up profiles) (bug https://bugzilla.mozilla.org/process_bug.cgi)
* write Gmail KB page; update account setup KB page with gmail examples (http://support.mozillamessaging.com/en-US/kb/Configure+an+Account, bug https://bugzilla.mozilla.org/show_bug.cgi?id=543861)
* copy edits to MDC MailNews automated testing (https://developer.mozilla.org/en/MailNews/MailNews_Automated_Testing)
* copy edits to AsyncTestUtils extended framework https://developer.mozilla.org/en/MailNews/AsyncTestUtils_Extended_Framework
* update ISPdb FAQ with form placeholder info; update autoconfig page to point to new ISPdb page; tweaks to ISPdb page from BWinton's feedback (https://support.mozillamessaging.com/en-US/kb/ISP+Database)
* break upgrade FAQs out to individual pages; create index page for FAQs (https://support.mozillamessaging.com/en-US/kb/FAQ+Upgrading+Thunderbird+2+to+3)

TODO

* Profiles KB article (moving and backing up profiles)
* move info on pref naming conventions to MDC: https://bugzilla.mozilla.org/show_bug.cgi?id=86845#c74 (notify Roland when done)
* make FAQ for Ludo on information he sent in email ("Model the 2 -> 3 upgrade experience")
* review and cross-link MDC and Knowledge Base
* delete Thunderbird-source template? (replaced by tbsource)
* bugs from sid0 (see "from_IRC" file)

Review / Waiting

* blog https://developer.mozilla.org/en/MailNews/AsyncTestUtils_Extended_Framework et al (wait for Standard8's comments)
* follow up with replacement content for gmail help pages - so far no answer from Gmail folks
* port content from http://www.mozilla.org/support/thunderbird/ - ask Roland to redirect
* review / response to http://groups.google.com/group/mozilla.dev.extensions/browse_thread/thread/41113fd2bb4973f7
* when "New in TB 3.0" page is live on sumomo, make redirect from MDC https://developer.mozilla.org/en/Thunderbird_3_for_users (instructions https://developer.mozilla.org/Project:en/External_Redirects)
* Search info from Andrew: http://getsatisfaction.com/mozilla_messaging/topics/what_is_indexing?utm_content=topic_link&utm_medium=email&utm_source=new_topic
* when linting is fixed on MDC, color code sample in https://developer.mozilla.org/en/MailNews/AsyncTestUtils_Extended_Framework

=== Support ===

=== Lightning Updates ===

* Sunbird 1.0b1 build issues probably taken care of, awaiting new build run.
* Blogged about [http://weblogs.mozillazine.org/calendar/2010/02/whats_going_to_happen_in_the_n.html next steps]
* Next for this week: Planning for 1.0 and reviews.

=== Roundtable ===

See the [http://benjamin.smedbergs.us/weekly-updates.fcgi/project/thunderbird Mozilla Status Board] for status updates specific to developers.

==== Highlights ====

=== Attendees ===

__NOTOC__

Calendar:Documentation

2010-02-03T20:09:36Z

XFallenAngel:

This page should be used for planning SUMO documentation for the Calendar Project. If you would like to contribute, please contact a member of [http://www.mozilla.org/projects/calendar/about.html the team].

Here follow some suggestions on which areas of Calendar could be documented. This is by no means all, feel free to add more.

* "Getting Started with Thunderbird, Lightning and your Google Calendar" (i.e. update with permission Jonny's faq at: http://bfish.xaedalus.net/2007/04/stay-in-sync-with-gcal-and-thunderbird/ - a quick and concise summary of getting started and doing the most common tasks for the most popular calendar provider
* Possibly transfer some FAQ items from [[Calendar:GDATA_Provider]]
* How do I access <insert calendar provider here, i.e yahoo, google> ?
* How do I open an ICS file
* How do I subscribe to a remote calendar
** Explain different calendar types (caldav, webdav, ...)

* Main Calendar View
** Sorting Calendars in the Calendar List (DnD, Ctrl+Up/Down)

* Event Dialog
** How to create certain recurring events (custom)
** Custom alarms
*** In which cases Email/SMS alarms are available
** Inviting attendees
** Show time as free / show time as busy

* Setting up Invitations (i.e the email in the calendar properties dialog)
* Using Freebusy

* Explain the Today pane
* Explain Import/Export

* Give an overview of all keyboard shortcuts, with a link to the [http://www.mozilla.org/support/thunderbird/keyboard Thunderbird Keyboard Shortcuts]

* Migrating profile data between Sunbird and Lightning.
** Describe calendar-specific profile files
** Explain how to move Lightning calendars to Sunbird and vice versa
** See also: http://kb.mozillazine.org/Migrating_from_Sunbird_to_Lightning

* [[Calendar:Adding_a_holiday_calendar]]

Thunderbird/StatusMeetings/2010-01-19

2010-01-19T17:44:54Z

XFallenAngel: /* Lightning Updates */

[[Thunderbird/StatusMeetings/2010-01-12|last meeting]] | [[Thunderbird/StatusMeetings|index]] | [[Thunderbird/StatusMeetings/2010-01-26|next meeting »]]

'''Thunderbird Meeting Details''' :

*[http://www.timeanddate.com/worldclock/fixedtime.html?year=2010&month=01&day=19&hour=17&min=30&sec=0 Tuesday, January 19th, 17:30 UTC] (9:30am Pacific, 12:30pm Eastern)
*[[Thunderbird/StatusMeeting/DialInInfo|How to dial-in]]

== Agenda ==

*Who's taking minutes? --> '''bienvenu'''
*[http://ascher.ca/thunderbird/minutes_schedule.html Minute taking Schedule]. Talk to davida for schedule changes/additions.

=== Action Items ===

==== New ====

==== Open ====
* Planning for a dry-run security firedrill build
** Checklist: [[Thunderbird/Release_Driving/Firedrills|draft checklist for firedrill actions]]
** gozer and Standard8 to 'schedule' run through

==== Closed ====

=== Friends of the Tree ===
* [http://boblord.livejournal.com/ Bob Lord] For triaging S/MIME and certificate bugs in the Thunderbird/Security component.

=== [[Thunderbird:Thunderbird3.1|Thunderbird 3.1 (Lanikai)]] ===

==== Lanikai Alpha 1 ====

===== Schedule =====
Not much in 3.1a1, because it hasn't been driven much. I've posted a message proposing that, in the interest of getting in the habit of doing regular releases, we proceed with the following schedule anyway:
{{:Thunderbird:Thunderbird 3.1a1}}
Are there reasons not to go forward with this?

===== Lists of Bugs =====
* Blockers
** [https://bugzilla.mozilla.org/chart.cgi?category=-All-&datefrom=2009-08-19&dateto=&gt=1&label0=TB%20TB%203.1&label1=MC%20TB%203.1&label2=MoMo%20TB%203.1&labelgt=Grand%20Total&line0=1952&line1=1953&line2=1954&name=1183&subcategory=-All-&ctype=png&action=plot&width=400&height=232 3.1 Blocker Chart]
** [https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=blocking-thunderbird3.1%2B&sharer_id=112088 blocking-thunderbird3.1+ (includes tb31needs)]: 62 (+8)
* Proposed Blocking
** [https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=blocking-thunderbird3.1%3F&sharer_id=112088 blocking-thunderbird3.1?]: 87 (+17)

* Fixed Alpha 1
** {{trackinglist|TB 3.1a1 blocking|blocking-thunderbird3.1%2B|FIXED|Thunderbird%203.1a1}}: 5 (+1)

=== Thunderbird 3.0.x Developer Update ===

* [[Thunderbird/Release_Driving/Maintenance_Release_Checklist|3.0.x Release checklist]] updated
* [http://tinderbox.mozilla.org/showbuilds.cgi?tree=Thunderbird3.0 Tinderbox] has links to:
** [[Thunderbird/Thunderbird3_Security_And_Stability_Releases#General_Process_for_landing_bugs_on_Thunderbird_3.0.x|Process for getting bugs into 3.0.x]]
** [[Thunderbird/Thunderbird3_Security_And_Stability_Releases#Status_Tracking|Tracking and Status page]]

==== [[Releases/Thunderbird_3.0.1|3.0.1]] ====

* Builds started.
* Beta Period Starts: January 13
* Estimated Release Date: January 20
* [https://bugzilla.mozilla.org/buglist.cgi?field0-0-0=cf_status_thunderbird30;query_format=advanced;type0-0-0=equals;value0-0-0=.1-fixed Fixed 3.0.1]: 77 (+34)
** 57 actual fixes, the remaining 19 were bugs that landed on the relbranch for 3.0 as well as for 3.0.1.
** [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=ALL%20status-thunderbird3.0:.1-fixed%20-kw:verified-thunderbird3.0&order=bugs.bug_id need verification]: 36 (-4)

==== [[Releases/Thunderbird_3.0.2|3.0.2]] ====

* Schedule TBD.
* May look to sync with Gecko 1.9.1.8 (builds start Feb 1, release Feb 16).
* [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=ALL%20blocking-thunderbird3.0:needed|blocking-thunderbird3.0:.2+%20-status-thunderbird3.0:fixed&order=map_assigned_to.login_name,bugs.bug_id Blockers (needed and .2)]: 30 (+3)
** Of which [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=ALL%20blocking-thunderbird3.0:.2+%20-status-thunderbird3.0:.2-fixed&order=map_assigned_to.login_name,bugs.bug_id blocking 3.0.2]: 2
* [https://bugzilla.mozilla.org/buglist.cgi?field0-0-0=cf_blocking_thunderbird30;query_format=advanced;type0-0-0=equals;value0-0-0=%3F Blocking Nominations]: 6 (+2)

=== QA Updates ===
Last week
* 3.0.1 following
* bug triaging

This week
* 3.1a1 will get our attention
* Thursday event will focus on bugs that might have [[Thunderbird:QA_TestDay:2010-10-21|duplicates]].

Top Crashers for 3.0.1

{| class="fullwidth-table"
|-
| style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | '''status'''
| style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | '''bug'''
| style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | '''summary'''
| style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | # crash /week
|-
| style="background: red none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | Unassigned - no progress
| {{Bug|537822}}
| XPCWrappedNativeScope::TraceJS(JSTracer*, XPCJSRuntime*)
| 30
|-
| style="background: red none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | No signature bug
|
|
| 27
|-
| style="background: red none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | Unassigned - no progress
| {{bug|536308}}
| arena_dalloc_small | arena_dalloc | free | sqlite3_free | pcache1TruncateUnsafe
| 24
|-
| style="background: red none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | Unassigned - no progress
| {{bug|537011}}
| JS_CallTracer
| 22
|-
| style="background: red none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | Unassigned - no progress
| {{Bug|536960}}
| sqlite3DbMallocRaw
| 21
|}

=== Marketing Updates ===
* PR Update:
**Lightning Beta 1 Stories: [http://lifehacker.com/5447181/lightning-beta-brings-calendars-back-to-thunderbird-3 Lifehacker], [http://www.ghacks.net/2010/01/14/mozilla-lighting-1-0-beta-released-mozilla/ Ghacks]
** Operation Aurora in the news [http://www.mcafee.com/us/threat_center/aurora_enterprise.html from McAfee]
* 5.9MM ADUs, peaked 1/13
* [https://preview.addons.mozilla.org/en-US/thunderbird/compatibility Thunderbird Add-on Compatibility Center] is up, 89% of Add-ons are up-to-date with Thunderbird 3

=== IT update ===

* [http://ftp.mozilla.org/pub/mozilla.org/thunderbird/nightly/3.0.1-candidates/build1/ Thunderbird 3.0.1] ready to release
* Thunderbird 3.1a1 ready to build
* [http://tinderbox.mozilla.org/Thunderbird3.1 Thunderbird3.1] builds are temporarly following the 3.1a1 release branch (mozilla-1.9.2)
* New Win32 builders are in production
* [http://build.mozillamessaging.com/tinderboxpushlog/ tinderboxpushlog] updated
* SuMoMo is getting ready for prime-time launch

=== Documentation ===

DONE

* sumomo: testing (feedback to Roland)
* sumomo: migration assistant [https://bugzilla.mozilla.org/show_bug.cgi?id=530135 bug 530135]
* sumomo: manually configuring accounts [https://bugzilla.mozilla.org/show_bug.cgi?id=530122 bug 530122]
* sumomo: sending and receiving messages [https://bugzilla.mozilla.org/show_bug.cgi?id=530122 bug 530122]
* sumomo: re-wrote [https://stage.support.mozillamessaging.com/en-US/kb/Signatures Signatures article]
* sumomo: [https://stage.support.mozillamessaging.com/en-US/kb/Thunderbird+3+for+users Thunderbird 3 for users]
* sumomo: [https://stage.support.mozillamessaging.com/en/kb/FAQ+Upgrading+Thunderbird+2+to+3?bl=n upgrade FAQ]
* MozillaZine proposal - draft to Roland

TODO

* make page for autoconfig security (http://getsatisfaction.com/mozilla_messaging/topics/security_concerns_over_autoconfiguration_probing?utm_content=topic_link&utm_medium=email&utm_source=new_topic) on MDC; link from sumomo page (notify Blake Winton when done)
* write replacement content for gmail help pages - send to Rafael
* move info on pref naming conventions to MDC: https://bugzilla.mozilla.org/show_bug.cgi?id=86845#c74 (notify Roland when done)
* make FAQ for Ludo on information he sent in email ("Model the 2 -> 3 upgrade experience")
* Roland: FAQ on text vs HTML? (http://groups.google.com/group/mozilla.dev.apps.thunderbird/browse_thread/thread/562423bbd2dac0ea)

Review / Waiting

* port content from http://www.mozilla.org/support/thunderbird/ - ask Roland to redirect
* response to http://groups.google.com/group/mozilla.dev.extensions/browse_thread/thread/41113fd2bb4973f7
* when "New in TB 3.0" page is live on sumomo, make redirect from
MDC https://developer.mozilla.org/en/Thunderbird_3_for_users (instructions https://developer.mozilla.org/Project:en/External_Redirects)

=== Support ===
# [[Thunderbird/Support/Workflow|Draft Support Workflow Document]] - ''NEW'' this week - [[Thunderbird/Support/Workflow#Normal_Users.27_Workflow|Updated Normal Workflow section with a tagging convention for duplicate Get Satisfaction Topics]] <-- Again, feedback please! Edit the page, etc.
# [http://getsatisfaction.com/mozilla_messaging/tags/reviewed20100118 The GS topics that were triaged at the January 18, 2010 meeting]
# [http://getsatisfaction.com/mozilla_messaging/tags/review Issues to be reviewed at the next GS Triage meeting scheduled for January 5, 2010] - Please tag topics "review" if you think they need to be reviewed because they cause customer pain
# SUMO for MoMo aka SuMoMo - [[Thunderbird/Support/SUMO_Project_Plan_Thunderbird3|SuMoMo project plan]] - final round of "meta content", config and sysadmin tasks expected to be done Thursday morning after 3.0.1, hoping to launch Thursday or next week
## GS workaround for SSL and satisfaction search widget doesn't work when logged in so will ping GS but probably have to implement workaround which is to not serve up non SSL Satisfaction Search Widgets to IE 6,7 and 8 users, instead serve just a simple link
## content - done except [https://bugzilla.mozilla.org/show_bug.cgi?id=530116 Thunderbird 3 for Windows 7 users]
# Key Support stats from the following graphic:
## approximately 70/ day (494/7 slightly lower than last week), # of visitors 58000 seems like GS has fixed their stats bug although seems high)
## total new topics:494 (down from last week) total replies:1308 from employees and champions: 137 back to normal! (NonMoMo:109 FROM Michael Pasek (thanks!), 53 from Chris Ramsden aka Xenos (thanks!),27 from Wayne (thanks!), 15 from DavRo (thanks and belated welcome!), 15 from Padyx (thanks and belated welcome!), 11 from matt_678579 (thanks and welcome!), 8 from tanstaafl, 6 from from Kent (Thanks!), MoMo: 37 by Bienvenu (thanks), 33 from Roland, 3 from Blake (thanks!), 24 from Ludo (thanks),14 from Mark Banner (thanks) ([http://gist.github.com/196464 Ruby Code] - '''NEW''' improved with automatic sort)
### date:20100112 #new support topics:83 resolved:14
### date:20100113 #new support topics:81 resolved:36
### date:20100114 #new support topics:73 resolved:16
### date:20100115 #new support topics:77 resolved:17
### date:20100116 #new support topics:64 resolved:10
### date:20100117 #new support topics:63 resolved:14
### date:20100118 #new support topics:85 resolved:33

[[File:12-18January_2010-Community_stats_for_Mozilla_Messaging.png|500px]]

=== Lightning Updates ===

* Still waiting for Sunbird 1.0b1 l10n builds
* Philipp mostly swamped with exams, will plan 1.0b2 soon
* Lightning 1.0b1 seems to ve going well, not many complaints.

=== Roundtable ===

Ideas to make the meeting more productive :

* Most people wanting to know dates should find it here and they don't - maybe we could make the planet post from the meeting a bit prettier and easier to read than the half/geeky think that appears on planet.mozilla.org.
* Most people don't know that we have a weekly meeting. Maybe make the meeting more "visible" ?

Description of UCOSP by bwinton.

==== Status Updates ====

===== sid0 =====

===== davida =====

===== dmose =====

===== Standard8 =====

===== asuth =====

===== bienvenu =====
* Reviews and driving
* Helped out on Get Satisfaction issues
* Windows installation was corrupted, still recovering from that.
* Got 4GB offline store limit removal patch through review process

===== gozer =====

===== clarkbw =====

===== wsmwk =====

===== beckley =====

====== Penelope ======

* New beta looks good. Little problems reported.

* Integration of TB 3.0 source code seems to have solved most gloda issues and integration of it in to the Search Messages window is looking likely for our Eudora 8.0 release.

===== KaiRo =====
* Updated SeaMonkey buildbots to mirror Firefox setup even more closely ({{bug|539780}}), hopefully being able to share this with Thunderbird.
* Checked in patch for a CC* release bustage in buildbotcustom ({{bug|537913}}).
* Switched CC* release automation to using ChatZilla from hg ({{bug|537461}}).

===== rkent =====
I've been heads down playing with the old Mozilla SOAP package, evaluating it for possible use with Exchange Server web services. I've got it compilable in a TB 3.0 build as a binary extension using frozen linkage, and just started writing unit tests to take it through its paces.

===== rebron =====
Done
* Partner outreach.
* 3.0.1rc web site work.
* PR team plan/budget.

Next
* 3.0.1 final web site work
* 3.1 alpha relnotes, etc
* Draft plan for Add-on contest.
* sumomo article bug 530116

===== Tsk =====
* gave a try at doing support felt frustrated.
* usual stuff

===== andreasn =====
Done:
* simpler windows icons bug {{bug|539128}}
* smaller info bars {{bug|539416}}
* Mockups for attachments, empty results {{bug|539223}} reciepts {{bug|151244}}

Todo:
* Personas in Thunderbird {{bug|538335}}
* More Lanikai branding
* Look into search box modes more {{bug|540257}}
* More info bars

Misc: My mac died :(

===== bwinton =====
Done:
* Lots of work on the HomeTab extension.
* UCOSP Code Sprint!

Next:
* Lots more work on the HomeTab extension.
* Fly somewhere nice and warm.

===== roland =====

===== sgautherie =====
*Fixed MailNews Core bugs:
**{{bug|538751}} Port | - Failed to build with --enable-dtrace for 64bit library| to comm-central

===== nth10sd =====

* Clearing bugmail..

===== Fallen =====

===== jcranmer =====

===== BenB =====

=== Attendees ===

__NOTOC__

Thunderbird/StatusMeetings/2010-01-12

2010-01-12T17:36:07Z

XFallenAngel: /* Lightning Updates */

[[Thunderbird/StatusMeetings/2010-01-05|last meeting]] | [[Thunderbird/StatusMeetings|index]] | [[Thunderbird/StatusMeetings/2010-01-19|next meeting »]]

'''Thunderbird Meeting Details''' :

*[http://www.timeanddate.com/worldclock/fixedtime.html?year=2010&month=01&day=12&hour=17&min=30&sec=0 Tuesday, January 12th, 17:30 UTC] (9:30am Pacific, 12:30pm Eastern)
*[[Thunderbird/StatusMeeting/DialInInfo|How to dial-in]]

== Agenda ==

*Who's taking minutes? --> '''Standard8'''
*[http://ascher.ca/thunderbird/minutes_schedule.html Minute taking Schedule]. Talk to davida for schedule changes/additions.

=== Action Items ===

==== New ====

==== Open ====
* Planning for a dry-run security firedrill build
** Standard8: Set up [[Thunderbird/Release_Driving/Firedrills|draft checklist for firedrill actions]]

==== Closed ====

=== Friends of the Tree ===

=== [[Thunderbird:Thunderbird3.1|Thunderbird 3.1 (Lanikai)]] ===

* [http://ccgi.standard8.plus.com/blog/archives/322 Lanikai builds] now set up (with new trunk builds).

===== Schedule =====
Not much in 3.1a1, because it hasn't been driven much. I've posted a message proposing that, in the interest of getting in the habit of doing regular releases, we proceed with the following schedule anyway:
{{:Thunderbird:Thunderbird 3.1a1}}
Are there reasons not to go forward with this?

===== Lists of Bugs =====
* Blockers
** [https://bugzilla.mozilla.org/chart.cgi?category=-All-&datefrom=2009-08-19&dateto=&gt=1&label0=TB%20TB%203.1&label1=MC%20TB%203.1&label2=MoMo%20TB%203.1&labelgt=Grand%20Total&line0=1952&line1=1953&line2=1954&name=1183&subcategory=-All-&ctype=png&action=plot&width=400&height=232 3.1 Blocker Chart]
** [https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=blocking-thunderbird3.1%2B&sharer_id=112088 blocking-thunderbird3.1+ (includes tb31needs)]: 54 (+2)
* Proposed Blocking
** [https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=blocking-thunderbird3.1%3F&sharer_id=112088 blocking-thunderbird3.1?]: 70 (+7)

* Fixed Alpha 1
** {{trackinglist|TB 3.1a1 blocking|blocking-thunderbird3.1%2B|FIXED|Thunderbird%203.1a1}}: 5 (+1)

=== [[Thunderbird:Thunderbird3.1a1|Thunderbird 3.1a1]] ===

==== Schedule ====
{{:Thunderbird:Thunderbird 3.1a1}}

=== Thunderbird 3.0.x Developer Update ===

* [[Thunderbird/Release_Driving/Maintenance_Release_Checklist|3.0.x Release checklist]] updated
* [http://tinderbox.mozilla.org/showbuilds.cgi?tree=Thunderbird3.0 Tinderbox] has links to:
** [[Thunderbird/Thunderbird3_Security_And_Stability_Releases#General_Process_for_landing_bugs_on_Thunderbird_3.0.x|Process for getting bugs into 3.0.x]]
** [[Thunderbird/Thunderbird3_Security_And_Stability_Releases#Status_Tracking|Tracking and Status page]]

==== [[Releases/Thunderbird_3.0.1|3.0.1]] ====

* Builds started.
* Beta Period Starts: January 13
* Estimated Release Date: January 20
* [https://bugzilla.mozilla.org/buglist.cgi?field0-0-0=cf_status_thunderbird30;query_format=advanced;type0-0-0=equals;value0-0-0=.1-fixed Fixed 3.0.1]: 77 (+34)
** 57 actual fixes, the remaining 19 were bugs that landed on the relbranch for 3.0 as well as for 3.0.1.
** [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=ALL%20status-thunderbird3.0:.1-fixed%20-kw:verified-thunderbird3.0&order=bugs.bug_id need verification]: 40 (-3)

==== [[Releases/Thunderbird_3.0.2|3.0.2]] ====

* Schedule TBD.
* May look to sync with Gecko 1.9.1.8 (builds start Feb 1, release Feb 16).
* [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=ALL%20blocking-thunderbird3.0:needed|blocking-thunderbird3.0:.2+%20-status-thunderbird3.0:fixed&order=map_assigned_to.login_name,bugs.bug_id Blockers (needed and .2)]: 27
** Of which [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=ALL%20blocking-thunderbird3.0:.2+%20-status-thunderbird3.0:.2-fixed&order=map_assigned_to.login_name,bugs.bug_id blocking 3.0.2]: 2
* [https://bugzilla.mozilla.org/buglist.cgi?field0-0-0=cf_blocking_thunderbird30;query_format=advanced;type0-0-0=equals;value0-0-0=%3F Blocking Nominations]: 4 (-6)

=== QA Updates ===

* Started verifying 3.0.1 Fixed bugs.
** more bugs to verify
** some bugs are difficult to verify pre-release
* smoke testing unsigned builds for 3.0.1 is green on Windows and Mac OS.

Coming up:
* This week we'll host a [[Thunderbird:QA_TestDay:2010-01-14|Triage event ]] - new comers are always welcomed.
* We'll monitor feedback in bugzilla and gs on 3.0.1 during the beta stage.
* and follow release activities
* Next week focus will shift to 3.1a1
* Once 3.0.1 is out The plan is to host a second upgrade from 2.x day - to find and fish out issues not fixed in 3.0.1

 

{| class="fullwidth-table"
|-
| style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | '''status'''
| style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | '''bug'''
| style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | '''summary'''
| style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | # crash /week
|-
| style="background: red none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | Needs verification pending 3.0.1
| {{Bug|505717}}
| EscapeFromSpaceLine(nsIOutputStream*, char*, char const*)
| 1182
|-
| style="background: red none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | Wanted 1.9.1 - some progress
| {{Bug|519962}}
| _purecall | nsPrefBranch::freeObserverList() | nsPrefBranch::Observe(nsISupports*, char const*, unsigned short const*)
| 953
|-
| style="background: red none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | No signature bug 
|
|
| 880
|-
| style="background: yellow none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | Assigned - Not testcase
| {{bug|536960}}
| sqlite3DbMallocRaw
| 834
|-
| style="background: red none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | Unassigned - no progress
| {{Bug|505016}}
| _purecall | nsXPCWrappedJS::QueryInterface(nsID const&, void**)
| 777
|}

=== Marketing Updates ===
* PR Update: [http://www.eweek.com/c/a/Enterprise-Applications/Mozilla-Releases-Firefox-36-Release-Candidate-426899/ Mozilla Rolls Out Firefox 3.6 Release Candidate], [http://lwn.net/SubscriberLink/368768/7e5ce21bedd9cf75/ A look at Thunderbird 3]
* Thunderbird 3 Coverage report Total US Numbers November 4th - December 16th, 2009; Total Articles: 224; Total Original: 156; Total Pick ups: 68
* PR planning for Q1

=== IT update ===

* Lightning [http://releases.mozilla.org/pub/mozilla.org/calendar/lightning/releases/1.0b1/ 1.0b1]

=== Documentation ===

Done

* sumomo: keyboard shortcuts
* sumomo: bug [https://bugzilla.mozilla.org/show_bug.cgi?id=521665 521665] (tweak search KB article)
* sumomo: new in TB 3 [https://bugzilla.mozilla.org/show_bug.cgi?id=530122 bug 530122]
* analysis of Sumomo as a platform; comparison to deki wiki (provided to Roland)
* sumomo: autoconfig KB page
* itemize gmail help pages that need to be updated for TB3 (sent to Rafael)

TODO / In Progress

* sumomo: manually configuring accounts [https://bugzilla.mozilla.org/show_bug.cgi?id=530122 bug 530122]
* sumomo: sending and receiving [https://bugzilla.mozilla.org/show_bug.cgi?id=530122 bug 530122]
* sumomo: migration assistant [https://bugzilla.mozilla.org/show_bug.cgi?id=530135 bug 530135]
* MozillaZine material / cooperation

=== Support ===
# [[Thunderbird/Support/Workflow|Draft Support Workflow Document]] - [[Thunderbird/Support/Workflow#GS_Triage|Updated with GS Triage section]] <-- Again, feedback please! Edit the page, etc.
# [http://getsatisfaction.com/mozilla_messaging/tags/reviewed20100111 The GS topics that were triaged at the January 11, 2010 meeting]
# [http://getsatisfaction.com/mozilla_messaging/tags/reviewed Issues to be reviewed at the next GS Triage meeting scheduled for January 18, 2010] - Please tag topics "review" if you think they need to be reviewed because they cause customer pain
# SUMO for MoMo aka SuMoMo - [[Thunderbird/Support/SUMO_Project_Plan_Thunderbird3|SuMoMo project plan]]
## theming live on [http://getsatisfaction.com/mozilla_messaging/tags/reviewed20100111 stage.support.mozillamessaging.com]
## since SuMoMo uses SSL, waiting for GS to give us GS search widget code that we can put on the sidebar that works with SSL, expected a fix before Christmas (not rocket science since since all the GS widgets except the Satisfaction Search widget that we are using allow SSL, followed up with GS developer January 4) - <strike>still no update</strike> - expected tonight 12jan2010, hopefully won't have to implement workaround which is to not serve up non SSL Satisfaction Search Widgets to IE 6,7 and 8 users, instead serve just a simple link
## content - hoping to get some more of JenZed's time and other contributors to finish this week:
### Priority 1 - if edits and drafts from JenZed are done and contributor start and finishes [https://bugzilla.mozilla.org/show_bug.cgi?id=530116 Thunderbird 3 for Windows 7 users], then we will be done this week!
### Priority 2 - if edits and drafts from JenZed are done and contributor starts and finishes [https://bugzilla.mozilla.org/show_bug.cgi?id=530133 Moving from Thunderbird 2 to 3 - 530133], then we will be done this week!
# Key Support stats from the following graphic:
## approximately 85/ day (601/7 back to normal Thunderbird 3.0 levels after the holidays), # of visitors 333,000 seems a like a bug since it's an order of magnitude higher than 30000, will followup with GS)
## total new topics:601 total replies:1423 from employees and champions: 213 back to normal! (NonMoMo:104 from Chris Ramsden aka Xenos (thanks! and belated Welcome!), 47 FROM Michael Pasek (thanks and belated welcome!) MoMo: 77 from Roland, 57 by Bienvenu (thanks), 9 from Andreas (thanks), 31 from Wayne (thanks!), 5 from Blake (thanks!), 1 from Kent (Thanks!), 2 from ClarkBW (thanks), 2 from Ludo (thanks), 9 from Mark Banner (thanks) ([http://gist.github.com/196464 Ruby Code])
### date:20100105 #new support topics:92 resolved:27
### date:20100106 #new support topics:92 resolved:21
### date:20100107 #new support topics:78 resolved:22
### date:20100108 #new support topics:95 resolved:12
### date:20100109 #new support topics:56 resolved:19
### date:20100110 #new support topics:47 resolved:3
### date:20100111 #new support topics:74 resolved:14

[[File:05-11January_2010_-_Community_stats_for_Mozilla_Messaging.png|500px]]

=== Lightning Updates ===
* lightning was uploaded to AMO
* Google Provider will follow this evening
* Sunbird still waiting for l10n
* Release blog post alsi comming up

=== Roundtable ===

==== Status Updates ====

===== sid0 =====

===== davida =====

===== dmose =====
* Last week
** Got back from vacation
** Found and worked with support folks on email bug in GetSat messages
** Started getting caught up
** Got sick
** Reviewed and landed 3.0.1 extension menu patch
** Fixed 3.0.1 toolbar overflow bug
** Drafted and floated automated testing announcement
** 3.1a1 driving
* This week
** Goals work in Vancouver
** 3.1a1 driving
** Catch up on board minutes

===== Standard8 =====

* 3.0.1 driving, bug fixes, reviews and pushing to being release.
* Updated checklists following comments from drivers.
* Testing Infrastructure component now set up.
* Fixed some l10n issues on trunk & Lanikai branch.

===== asuth =====

===== bienvenu =====
* reviews & driving
* Landed a bunch of fixes for 3.01
* fix {{bug|534835}}, when fetching whole imap message, use the literal size as the message size in case the server gets the rfc822.size wrong consistently, to avoid refetching the same message over and over again.
* try to recover data downloaded to local folders-1 account by 3.0 upgrade from 2.0, {{bug|538414}}.
* Fixed {{bug|382298}} Forwarded icon not shown up in IMAP account
* Fixed {{bug|533865}}, doing quick search in saved search/smart folder clears cached results.
* Fixed imap unread counts with condstore servers, {{bug|517461}}
* Fixed {{bug|534382}}, tb 2 profiles with multiple local folder accounts get one of them turned into smart mailboxes, which messes up pop3 download, remove code that cause problem, and fix deferral to point back to local folders.
* Don't do quick searches or views online unless we have to, {{bug|537820}}

===== gozer =====

''Back from offline vacation''

* Catching up on e-mail
* Thunderbird 3.0.1 build

===== clarkbw =====

===== wsmwk =====

* shepherding #1 crash {{Bug|519962}} - startup crash [@ nsPrefBranch::Observe ... - which is making progress, but far from being fixed.
* shepherding IME crash {{Bug|537828}} - crash [@ nsAString_internal::Assign ... - which seems close to being fixed thanks largely to masayuk and fehe
* continued focus on hang, perf and crashes in bugs, gsfn and fora
* worked part of the verify list for 3.0.1 fixed

===== beckley =====

====== Penelope ======

===== KaiRo =====

===== rkent =====

===== rebron =====

Done:

* GS triage process/weekly meetings started * Mozilla Marketing Community meeting. Notes: http://www.spreadfirefox.com/node/5574 * More PR planning work. * Goals/prelim marketing budget 

Next:

* Tb 3.0.1 pages, finish up. bug 538973 * Snippet localization * Add-on contest spec out. * sumomo article bug 530116 

===== Tsk =====
Done :
* reading bugmail
* bug triage day
* 3.0.1 testing
* started collected software vendors to contact for releases.

todo:
* more 3.0.1 testing
* 3.1a1 preparation.

===== andreasn =====
Done:
* Lanakai branding {{bug|535209}}
* Shredder branding {{bug|433630}}
* Folder pane bug {{bug|535021}}
* Travel booking stuff

Next:
* Personas in Thunderbird {{bug|538335}}
* collapse the toolbar on an ugly manner on OS X {{bug|533342}}
* simpler windows icons {{bug|539128}}
* return receipt should be processed after the message has loaded {{bug|151244}}
* hardcoded colors invisible with some gtk themes {{bug|469300}}

===== bwinton =====
Done:
* Book flights, and a hotel.
* Create {{bug|538568}}.
* Review {{bug|538923}}.
* Check in {{bug|536546}}, {{bug|524045}}, {{bug|516586}}, {{bug|536245}}, and {{bug|538568}} on trunk.
* Check in {{bug|398072}}, {{bug|528039}}, {{bug|516586}}, {{bug|537820}}, {{bug|461152}}, {{bug|531794}}, {{bug|534641}}, {{bug|536245}}, and {{bug|538568}} on comm-1.9.1
* Answer questions in Get Satisfaction.
* More new employee administrivia.

Next:
* Bug DavidA to review some ISPDB patches.
* More work on the netbook and reply-mode-toggle addons.
* Help the students dig into their bugs in the Code Sprint.

===== roland =====

===== sgautherie =====
*Fixed MailNews Core bugs:
**{{bug|536404}} When composing an S/MIME encrypted email, no padlock is shown at bottom right of window
**{{bug|537874}} Port bug 528263 and bug 529441 to comm-central
**{{bug|538745}} Port |Bug 532645 - Upgrade libpng to version 1.4.0| to comm-central

===== nth10sd =====

===== Fallen =====

===== jcranmer =====

===== BenB =====

=== Attendees ===

__NOTOC__

Thunderbird/StatusMeetings/2009-12-15

2009-12-15T17:47:13Z

XFallenAngel: /* Fallen */

[[Thunderbird/StatusMeetings/2009-12-01|last meeting]] | [[Thunderbird/StatusMeetings|index]] | [[Thunderbird/StatusMeetings/2009-12-22|next meeting »]]

'''Thunderbird Meeting Details''' :

*[http://www.timeanddate.com/worldclock/fixedtime.html?year=2009&month=12&day=15&hour=17&min=30&sec=0 Tuesday, December 15th, 17:30 UTC] (9:30am Pacific, 12:30pm Eastern)
*[[Thunderbird/StatusMeeting/DialInInfo|How to dial-in]]

== Agenda ==

*Who's taking minutes? --> '''davida'''
*[http://ascher.ca/thunderbird/minutes_schedule.html Minute taking Schedule]. Talk to davida for schedule changes/additions.

=== Action Items ===

==== New ====

==== Open ====
* Planning for a dry-run security firedrill build

==== Closed ====

=== Friends of the Tree ===

=== Thunderbird 3.0 ===

[http://www.mozillamessaging.com/en-US/about/press/archive/2009-12-08-01 Released last Tuesday]

Some random download stats from the [http://download.mozilla.org/rss/download-counts.php download.m.o counter] (only a part of the downloads, not sure how representative):
* Thunderbird-3.0 --- 1,156,131
* Thunderbird-3.0-Complete --- 912,214
* Thunderbird --- 5,194,344

=== Thunderbird 3.1 Developer Update ===

* [https://wiki.mozilla.org/User:Dmose/Tb_Post-3.0_Scratchpad Post 3.0 Roadmap]
* [https://wiki.mozilla.org/User:Dmose/Tb_Post-3.1_Scratchpad Post 3.1 Roadmap]
* Tb 3.1 cycle specifics
* More branches and work on branches
* Feedback on schedule for 3.next is wanted.

* [https://bugzilla.mozilla.org/chart.cgi?category=-All-&datefrom=2009-08-19&dateto=&gt=1&label0=TB%20TB%203.1&label1=MC%20TB%203.1&label2=MoMo%20TB%203.1&labelgt=Grand%20Total&line0=1952&line1=1953&line2=1954&name=1183&subcategory=-All-&ctype=png&action=plot&width=400&height=232 3.1 Blocker Chart]

* Blockers
** [https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=blocking-thunderbird3.1%2B&sharer_id=112088 blocking-thunderbird3.1+ (includes tb31needs)]: 51
* Proposed Blocking
** [https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=blocking-thunderbird3.1%3F&sharer_id=112088 blocking-thunderbird3.1?]: 48

* Fixed Alpha 1
** {{trackinglist|TB 3.1a1 blocking|blocking-thunderbird3.1%2B|FIXED|Thunderbird%203.1a1}}: 1

=== Thunderbird 3.0.x Developer Update ===

* No concrete plan for 3.0.1 as of yet
* [http://tinderbox.mozilla.org/showbuilds.cgi?tree=Thunderbird3.0 Tinderbox] has links to:
** [[Thunderbird/Thunderbird3_Security_And_Stability_Releases#General_Process_for_landing_bugs_on_Thunderbird_3.0.x|Process for getting bugs into 3.0.x]]
** [[Thunderbird/Thunderbird3_Security_And_Stability_Releases#Status_Tracking|Tracking and Status page]]

* [https://bugzilla.mozilla.org/buglist.cgi?field0-0-0=cf_blocking_thunderbird30;query_format=advanced;type0-0-0=equals;value0-0-0=%3F Blocking Nominations]: 16
* [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=ALL%20blocking-thunderbird3.0:needed%20-status-thunderbird3.0:fixed&order=map_assigned_to.login_name,bugs.bug_id Blockers (needed)]: 1
* [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=ALL%20blocking-thunderbird3.0:.1+%20-status-thunderbird3.0:.1-fixed&order=map_assigned_to.login_name,bugs.bug_id Blocking 3.0.1]: 12
* Of which:
** [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=ALL%20blocking-thunderbird3.0:.1+%20-status-thunderbird3.0:.1-fixed%20-flag:approval-thunderbird3.0.1%2B%20-flag:approval-thunderbird3.0.1%3F&order=map_assigned_to.login_name,bugs.bug_id waiting branch patch] (or approval flag setting): 11

* [https://bugzilla.mozilla.org/buglist.cgi?field0-0-0=cf_status_thunderbird30;query_format=advanced;type0-0-0=equals;value0-0-0=.1-fixed Fixed 3.0.1]: 22
** Of which [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=ALL%20status-thunderbird3.0:.1-fixed%20-kw:verified-thunderbird3.0&order=bugs.bug_id need verification]: 22

=== QA Updates ===

*TB 3.0 released
*Top reported issues :
**Duplicate folder after migrations from 2.x {{bug|505465}}
**Issue with the way we do auth for some SMTP confs, also after migration from 2.x
**Can't open text files {{bug|533462}}

*Bug filled are going up a bit.

*we are going back to our regular Thursday scheduled activities new users are welcome and can easily join. [[Thunderbird:Upcoming QA Testday]]

 

{| class="fullwidth-table"
|-
| style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | '''status'''
| style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | '''bug'''
| style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | '''summary'''
| style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | # of crash
|-
| style="background: red none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | Unassigned [tb30xwants]
| {{Bug|519962}}
| _purecall | nsPrefBranch::freeObserverList() | nsPrefBranch::Observe(nsISupports*, char const*, unsigned short const*)
| 1445
|-
| style="background: lawngreen none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | Assigned Patch in review
| {{Bug|505717}}
| EscapeFromSpaceLine(nsIOutputStream*, char*, char const*)
| 1204
|-
| style="background: red none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | No signature bug 
|
|
| 1100
|-
| style="background: yellow none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | Assigned patch pending review
| {{bug|513543}}
| MimeInlineTextHTML_parse_eof
| 853
|-
| style="background: red none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | Unassigned
| {{Bug|505016}}
| _purecall | nsXPCWrappedJS::QueryInterface(nsID const&, void**)
| 773
|}

concerned by some sqlite related crashers.

=== Marketing Updates ===
* PR update - many articles, mostly positive pick up
** 68 original articles from Dec 8 - 10. 193 total US articles, 135 original since November.
*** [http://blogs.computerworld.com/15221/thunderbird_is_go Computerworld], [http://www.howtogeek.com/howto/7525/our-hands-on-look-at-mozilla-thunderbird-3.0/ HowtoGeek], [http://www.pcworld.com/businesscenter/article/184073/mozillas_thunderbird_email_client_comes_with_tabs.html PCWorld]
** 32 original articles in Germany for Thunderbird 3 release
** 13 original in the UK
** 20 original in Japan
** [http://delicious.com/txt100FF/thunderbird?page=1 over 30 in France]

Next up
* Evaluating press articles.
* Party planning - 3rd/4th week of January for release party.

=== IT update ===

* Post Thunderbird 3.0 fixes and metrics
* Calendar 1.0b1
* TB 3.0 AUS pings yesterday: > 162k
* SuMoMo trunk has all wanted features working

=== Documentation ===

Done

* set up build environment
* edit and link up gloda docs; clean up crufty old stuff
* fix for [https://developer.mozilla.org/en/Extensions/Thunderbird/HowTos/Common_Thunderbird_Extension_Techniques/Get_Thunderbird_version Get Thunderbird version] how-to
* fix for [https://developer.mozilla.org/en/Extensions/Thunderbird/HowTos/Common_Thunderbird_Use_Cases/Compose_New_Message Compose New Message] how-to
* (ongoing) Mission control / autoconfig (also new issue with documenting prefs)

TODO / In Progress

* Doc day on Thursday - announce and set up
* finalize / blog Content Tab docs
* support doc locations ([https://bugzilla.mozilla.org/show_bug.cgi?id=521665 521665])

=== Support ===
# All Hands
## Met everybody in SUMO and AMO and others I wanted to meet except PascalC
## Enabled me to draw up 2010 Support Goals which I will make public later this week
# Top 5 GS Thunderbird 2 Support Topics (code in progress: http://gist.github.com/190923 )
## not collected focused on Thunderbird 3.0
# Thunderbird 3.0 Top Support Issues
## [http://getsatisfaction.com/mozilla_messaging/topics/kaspersky_anti_spam_extension_causing_blank_window_problems_with_thunderbird_3_upgrade Kaspersky DLL and KPT issue causes blank windows after upgrade from TB 2 to 3] - email to Carsten and Mark and Sam sent, not sure who is in charge of Kaspersky, is it Jonathan? awaiting reply to email
## Compact Header
## [http://getsatisfaction.com/mozilla_messaging/topics/thunderbird_2_to_3_0_upgrade_unable_to_authenticate_to_smtp_server_uncheck_use_name_and_password_for_that_server Untick use name and password]
## 4GB Gmail issue - Bienvenu working on fix for Thunderbird 3.1
## opening IMAP text attachments is broken
# SUMO for MoMo
## theming really done this week
## still need people to write kb articles - [http://blogs.mozillamessaging.com/roland/2009/11/30/call-for-sumomo-writers/ sign up to write a SuMoMo article today :-)]
# TB 3.0 Lessons learned for 3.1 Support
## Have a support Day 1 or 2 business days after release
## Test (and notify vendors) all popular anti-virus upgrade scenarios from last major release to new release including Kaspersky
## Have KB articles ready for all new features and GS topics that point to KB articles - start writing KB articles at Beta 1
## Explain how community support works. 1 or 2 brief videos will make it much clearer I think
## Explain how add-ons work and how crucial it is to wait for your add-ons to be ported before upgrading
# Get Satisfaction
## Met with GS team in San Francisco last week and shared our ideas for GS improvements, most critical is split/close, will post wiki page with followup
## GS branding will be done this week, thanks to Gozer for code inspecting
## [[Thunderbird/Support/Workflow|GS Workflow aka How to do support - draft in progress]]
# Key Support stats from the following graphic:
## approximately 105/ day (734/7 new topics 3.6x higher than week of Dec 1, # of visitors 15X higher: 30000 compared to 2000)
## total new topics:734 total replies: 372 ([http://gist.github.com/196464 Ruby Code])
### date:20091208 #new support topics:54 resolved:15
### date:20091209 #new support topics:189 resolved:13
### date:20091210 #new support topics:165 resolved:16
### date:20091211 #new support topics:126 resolved:23
### date:20091212 #new support topics:103 resolved:9
### date:20091213 #new support topics:88 resolved:13
### date:20091214 #new support topics:92 resolved:18
## #replies from non MoMo folks: replies from MoMo folks: not available since JSON GS Replies API is down, email sent to GS folks thanks to Bienvenu, davida, dmosee and new folks for helping
## happiness metric: API doesn't have happiness emotitags, code in progress: http://gist.github.com/190094, JSON replies API is down so no update, Hendrix down to 10 since link replaced with GS link
[[File:8-14Dec2009-Community_stats_for_Mozilla_Messaging.png|500px]]

=== Roundtable ===

* [http://benjamin.smedbergs.us/weekly-updates.fcgi/project/thunderbird bsmedberg's weekly update webapp]

==== Status Updates ====

===== sid0 =====

===== davida =====

===== dmose =====

===== Standard8 =====

* Reviews
* Thunderbird 3 follow-up and bug triage.
* 3.0.x driving
* 1.9.2 branch set up work.

===== asuth =====

===== bienvenu =====
* Reviews and Driving
* MoCo All hands
* 3.1 planning
* Spent time with Get Satisfaction to get an idea of the issues we need to fix for 3.01 and 3.1.
* Added check for null url in NotifySearchHit, potential fix for topcrash {{bug|533249}}
* Attempted to fix dock count issues on mac, {{bug|516477}}
* fix ref counting issue editing drafts, {{bug|532693}}
* Cleaned up some dump statements in unit tests to dump exception caught, not some undefined variable.

===== gozer =====

===== clarkbw =====

===== wsmwk =====

===== beckley =====

====== Penelope ======

* Gloda integration in to Search Messages window not going well, and is backed out for next beta
* Eudora 8.0b8/Penelope 0.5a5 builds made and being tested, with hopes of release later this week

===== KaiRo =====

===== rkent =====

===== rebron =====
* Thunderbird 3 release
* All Hands
* Add-on Conference

This Week
* A few more locales for Thunderbird 3
* PR evaluation.

===== Tsk =====

===== andreasn =====

Done:
* More lightning icons {{bug|494598}}
* Thunderbird 3.0.1 bugs fixes {{bug|526193}}, {{bug|516586}}, {{bug|531140}}
* Fighting hardware issues

Todo:
* Fighting bugs
* Additional lightning polish
* Start adding stuff to netbook meta bug {{bug|533875}}
* Look into {{bug|533342}} and {{bug|534267}}

===== bwinton =====
Last week:
* Review {{bug|518315}}, {{bug|530721}}, {{bug|521173}}, {{bug|522251}}, {{bug|534741}}, and {{bug|530047}}.
* Work on {{bug|525070}}, and post the code to the extension.
* Post a patch for {{bug|533360}}.
* Talk about netbooks.
* Suggest marks for the students working on ISDPB.

Next week:
* More ISPDB driving.
* Start an extension for some of the netbook changes.
* Continue my ReplyMode extension.
* Say hello to next term's students, and help them get started.

===== roland =====

===== sgautherie =====
*Fixed MailNews Core bugs:
**{{bug|520899}} Switch application/x-javascript to application/javascript, MailNews Core part

===== nth10sd =====

===== Fallen =====

* Lightning 1.0b1rc1 is ready, will be released asap.
* Sunbird repacks fail on all platforms, gozer will take a look
* Looking for more channels to make the beta rc1 public

* Next up: check in and have patches reviewed to fix burning on trunk
* Exams in about a month

===== jcranmer =====

===== BenB =====

Working on [https://bugzilla.mozilla.org/show_bug.cgi?id=525238 bug 525238] and automated tests. Implemented AUTH PLAIN and AUTH CRAM-MD5 (for real) in the fake server.

=== Attendees ===

__NOTOC__

Thunderbird/StatusMeetings/2009-12-01

2009-12-01T10:17:31Z

XFallenAngel: /* Fallen */

[[Thunderbird/StatusMeetings/2009-11-24|last meeting]] | [[Thunderbird/StatusMeetings|index]] | [[Thunderbird/StatusMeetings/2009-12-08|next meeting »]]

'''Thunderbird Meeting Details''' :

*[http://www.timeanddate.com/worldclock/fixedtime.html?year=2009&month=12&day=01&hour=17&min=30&sec=0 Tuesday, December 12th, 17:30 UTC] (9:30am Pacific, 12:30pm Eastern)
*[[Thunderbird/StatusMeeting/DialInInfo|How to dial-in]]

== Agenda ==

*Who's taking minutes? --> '''gozer'''
*[http://ascher.ca/thunderbird/minutes_schedule.html Minute taking Schedule]. Talk to davida for schedule changes/additions.

=== Action Items ===

==== New ====

==== Open ====
* Planning for a dry-run security firedrill build

==== Closed ====

=== [[Thunderbird:Thunderbird3:Final|Thunderbird 3]] Developer Update ===

==== RC 1 ====

* Released last Tuesday (24th Nov).

==== Final ====

* Blockers are mainly web site updates.
* Remaining blockers are either trackers, or test-only/build changes to support the security & stability releases.

* [https://wiki.mozilla.org/Thunderbird/Thunderbird3_Security_And_Stability_Releases TB 3 Security and Stability page] updated now that we have flags for 3.0.x tracking.

* Blockers
** [https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=blocking-thunderbird3%2B&sharer_id=1537 blocking-thunderbird3+]: 13 (+1)
** [https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=tb3needs&sharer_id=1537 TB 3 Needs]: 2 (+1)
* Proposed Blocking
** {{trackinglist|Proposed Blockers (all)|blocking-thunderbird3?|---|}}: 14 (+14)

* Fixed RC1
** {{trackinglist|TB 3.0rc1 - blocking|blocking-thunderbird3%2B|FIXED|Thunderbird%203.0rc1}}: 155 (+0)

=== Thunderbird 3.next ===
* [https://wiki.mozilla.org/User:Dmose/Tb_Post-3.0_Scratchpad Post 3.0 Roadmap]
* [https://wiki.mozilla.org/User:Dmose/Tb_Post-3.1_Scratchpad Post 3.1 Roadmap]
* Tb 3.1 cycle specifics
* More branches and work on branches
* Feedback on schedule for 3.next is wanted.

=== QA Updates ===

=== Marketing Updates ===

=== IT update ===

=== Documentation ===

=== Support ===
# Top 5 GS Thunderbird 2 Support Topics (code in progress: http://gist.github.com/190923 ) basically the same as last week
## Cannot send email
## Cannot receive email ([http://getsatisfaction.com/mozilla_messaging/topics/could_not_connect_to_server_pop_att_yahoo_com_the_connection_was_refused AT&T POP server outage on November 20th])
## migration to Vista and Windows 7 from XP including email and address books and from Outlook and Outlook Express
## attachments not working
# Thunderbird 3 RC1 Top Support Issues (starting to monitor to see what we can improve for post 3.0)
## [http://getsatisfaction.com/mozilla_messaging/topics/tb3rc1_hangs_on_close change tls if available on 2.0 to START TLS in tb3, needs to be done manually in rc1, in rc2 will be done automatically]
## which addons for lightning and google calendar sync
# SUMO for MoMo tracker ticket: https://bugzilla.mozilla.org/show_bug.cgi?id=520628
## Goal is to get initial content and theming done at the end of the week - GS branding is done except for last bit of testing and MoMo footer menu tweaks
## [http://blogs.mozillamessaging.com/roland/2009/11/30/call-for-sumomo-writers/SuMoMo call for writers blog post]
# Key Support stats from the following graphic:
## approximately 29/ day (204/7, slightly higher than last week if we subtract the Raindrop topics)
## total new topics:204 total replies: 372 ([http://gist.github.com/196464 Ruby Code])
### date:20091124 #new support topics:18 resolved:30
### date:20091125 #new support topics:33 resolved:15
### date:20091126 #new support topics:36 resolved:14
### date:20091127 #new support topics:26 resolved:5
### date:20091128 #new support topics:19 resolved:7
### date:20091129 #new support topics:20 resolved:2
### date:20091130 #new support topics:21 resolved:3
## #replies from non MoMo folks: 5 from tanstaafl (thanks and welcome!), 108 from pasa (thanks), 1 from TMZ (thanks) MoMo folks: 1 from Wayne Mery (thanks) 79 from Roland, Bienvenu 30 (thanks!), 2 from Tom (thanks!) 6 from Kent James (thanks) 6 from Lightning team (thanks!), 4 from Andreas (thanks!), 8 from Standard8 (thanks), 1 from asuth (thanks!)
## happiness metric: API doesn't have happiness emotitags, , code in progress: http://gist.github.com/190094, manual happiness metric = 123 - 79 = 44 (30 last week), 40 Hendrix messages (generally Hendrix messages are unhappy but this week we had 1 happy messages) - [https://bugzilla.mozilla.org/show_bug.cgi?id=524801 bug to track down Hendrix for Thunderbird 3 and get rid of it as much as possible]
[[File:24-30Nov09-Community_stats_for_Mozilla_Messaging.png|500px]]

=== Roundtable ===

==== Status Updates ====

===== sid0 =====

===== davida =====

===== dmose =====

===== Standard8 =====

===== asuth =====

===== bienvenu =====

===== gozer =====

===== clarkbw =====

===== wsmwk =====

===== beckley =====

====== Penelope ======

===== KaiRo =====

===== rkent =====

===== rebron =====

===== Tsk =====

===== andreasn =====

===== bwinton =====

===== roland =====

===== sgautherie =====
*Fixed MailNews Core bugs:
**{{bug|271841}} Show full newsgroup name as tooltip for abbreviated newsgroup names

===== nth10sd =====

===== Fallen =====
* working on 1.0b1rc1, lots of build related complications
* gozer is doing a great job helping us get the release running.
* future releases will be much easier, working on having buildbot auto-create also localized release lightning builds
* can't make the meeting today, sorry!

=== Attendees ===

__NOTOC__

Calendar:GDATA Provider

2009-11-30T19:46:54Z

XFallenAngel: /* Why can't I create tasks on a Google Calendar? */

=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==
You can obtain the provider from addons.mozilla.org. It is available for [https://addons.mozilla.org/sunbird/addon/4631 Sunbird] and [https://addons.mozilla.org/thunderbird/addon/4631 Lightning].

'''Notes:'''
* It is recommended to use the latest version of Sunbird or Lightning together with the latest Provider for Google Calendar version.
* If you are using the latest nightly versions of Sunbird/Lightning, please use the corresponding version from [ftp://ftp.mozilla.org/pub/calendar/lightning/nightly ftp.mozilla.org] (currently [September 2009] <nowiki>ftp://ftp.mozilla.org/pub/calendar/lightning/nightly/latest-comm-1.9.1/</nowiki> then the xpi subfolder corresponding to your platform).

==Building from Source==
If you want to build your own copy of the provider from the comm-central tree, all you need to do is follow the [https://developer.mozilla.org/en/Comm-central_source_code_(Mercurial)#Sunbird_and_Lightning build instructions] for Sunbird/Lightning. Once you have compiled, the resulting extension should be at <code>''obj-dir''/mozilla/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 ''Settings'' link located in the box at the left of the page.
# Click on the calendar you want to use with Thunderbird Lightning or Sunbird.
# Click on either of the two XML buttons shown at the bottom.

Authentication is always done securely via https. If you would also like to securely transfer your calendar data, then just change the URL to https://.. instead of http://...

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'' when clicking File > New > Calendar > On the Network > Google Calendar in Sunbird/Lightning. There is also a graphical tutorial available at [http://bfish.xaedalus.net/?p=239 bfish.xaedalus.net].

=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 answered here, please discuss it [http://groups.google.com/group/provider-for-google-calendar/topics on the newsgroup]. If you believe you have found a bug, please file it in [https://bugzilla.mozilla.org/enter_bug.cgi?product=Calendar&component=Provider:%20GData bugzilla]

==Enabling calendar.debug.log==
This option is useful for more verbose logging to diagnose problems you are having. It is also a good thing to look at before posting on the discussion group:

* Open your application preferences (Tools or Edit Menu)
* Select the "Advanced" icon at the top.
* Click on the "General" tab, below the icons
* Select "Advanced Configuration"
* Right Click on an empty space in the list of preferences
* Select New > Boolean
* Enter "calendar.debug.log" as the preference name
* Pick "true" as the Boolean value.

Now you have enabled the preference. If you were experiencing a problem, you will get the most debug messages if you restart the application, then do whatever you were doing again until you experience the issue. Then check out the error console ("Tools" menu).

If you are testing CalDAV support, you should do the same steps above for the "calendar.debug.log.verbose" preference.

==I want to stay up to date on all GData Provider bugs!==
Nothing easier than that. In your bugzilla Email preferences, you can set up a list of "users" to watch. Enter the <code>gdata-provider@calendar.bugs</code> email address, and you will receive bugmail on each update to GData Provider bugs and on new bugs.

==Calendar Access==
===I cannot access my calendar at all!===
Now this is very general. First things first: Do you see any error console messages? If not, please enable <code>calendar.debug.log</code> in the advanced config editor. See above for how to do that. You should be getting more debug messages now.

Are you using a calendar nightly? (i.e 1.0pre) If so, you must use a mercurial compiled version of the gdata provider, not the official release. This is also described above in this FAQ.

===I want to be able to pick my calendars from a list, is there a way to do so?===
Not currently. Progress on this is being tracked in {{bug|378873}}.

===I have publicly shared my calendar. I don't want to enter my password each time!===
For public calendars you don't need the Provider for Google Calendar. Just use the standard iCalendar Provider and the ICS feed from Google. If you want to change a public calendar, there is no way around entering your password.

===I want to access a friend's calendar I have access too, but I am asked for a password!===
No problem! As long as you have this calendar added in the Google Calendar web interface, just enter your own credentials.

==Missing Features==
===Why can't I configure any options in the Extension Manager?===
There are currently not enough options to warrant an options window. There are some advanced preferences:

<code>calendar.google.useHTTPMethodOverride = true</code> Instead of using PUT and DELETE methods, use POST and GET with the X-HTTP-Method-Override header. This is good for proxies and since it doesn't harm non-proxies, it defaults to true.

<code>calendar.google.alarmClosest = true</code> Alarm support: Use either the alarm closest (true) or farthest away (false) from the event as the alarm displayed in Sunbird/Lightning.

<code>calendar.google.sendEventNotifications = true</code> When set to true, invitations are sent out to attendees on event modifications.

<code>calendar.google.enableAttendees = false</code> When set to false, attendees are disabled. This might be needed if you experience problems when accepting invitations.

<code>calendar.google.sendEmailNotifications = false</code> Setting this to true allows selecting a Google Calendar when accepting an invitation you received via email. '''WARNING:''' Enabling this option may cause you to unknowingly spam all attendees with an extra invitation! Only enable this option if you know what you are doing.

===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 be able to edit my calendars while offline!===
Version 0.9 of lightning currently allows only read-only access to the calendar events while offline.

You might want to monitor progress of [https://bugzilla.mozilla.org/show_bug.cgi?id=380060 bug 380060] to be informed on any progress on editing during offline mode feature.

==Event Interaction==
===I have set a category, but when changing the event it vanishes===
This could be caused due to {{bug|461995}}. I hope this will be fixed in the next version.

===I want to modify an Event but nothing happens. What am I doing wrong?===
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.

===After creating a recurring event, I am having problems with alarms. Why?===
Aside from the fact that there is no standardized scheme to store dismissing and snoozing alarms, Google doesn't allow setting certain properties on recurring events. This is especially the case for shared calendars. See bug {{bug|424185}} 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.

Also if you are using windows, make sure you have all timezone upgrades installed.

===Why can't I create tasks on a Google Calendar?===
Lately Google has added a Tasks widget to Google Calendar. However, they have not published API that allows extensions and other clients to access those tasks. There are two Google issues open to provide API for this
[http://code.google.com/p/gdata-issues/issues/detail?id=987 gdata issue 987] and
[http://code.google.com/p/google-caldav-issues/issues/detail?id=36 google caldav issue 36]. On the Mozilla side, {{bug|493389}} is filed to fix this as soon as the Google issues are fixed.

Please star the two Google issues to vote for them. DO NOT post "+1" style comments however, this only spams everyone that has voted for the issue.

==Attendees==
===I recieved an invitation from a friend. When trying to accept, my Google Calendars are not in the select calendar dialog, or no dialog is shown===
Accepting an invitation onto your Google Calendar can cause extra invitations being sent out to each attendee. Due to some Google Calendar limitations when adding invitations to your calendar its impossible to allow this in a way that new users will not shoot themselves in the foot.

If you know what you are doing, you can still re-enable this behavior. See the FAQ question regarding options.

===After accepting an invitation, the attendees all get an additional invitation from me===
This is {{bug|400808}}. A workaround is to set <code>calendar.google.sendEventNotifications</code> to false in the advanced config editor, or to not handle event invitations via lightning. Note that setting this preference inhibits all sending of event notifications.

==Alarms==
===What should I keep in mind while using alarms with the provider?===
The provider will only alert alarms of type popup. Depending on the setting of the (boolean) property ''calendar.google.alarmClosest'', it will read either the popup alarm closest to the event (true) or furthest away (false). To avoid confusion, be sure you set only one alarm with type popup. All other alarm types will not be touched by the provider.

===I have set some default reminders in the Google UI, but they don't show up on new events?===
As it might be easy to tell Google to use those default reminders, it requires UI additions to sunbird/lightning. I would like to concentrate on backend functionality before I add such UI extensions. If you would like this functionality, feel free to file an enhancement bug in bugzilla. (Remember to search if such a bug exists first).

===I set an alarm on an event but after looking at the event again, the alarm has a totally different value!===
Since Google supports multiple alarms and sunbird/lightning only supports one alarm, its hard to find a good way to map between the possible alarms. The provider will read the alarm either closest to or furthest away from the event. If you change a popup alarm in sunbird/lightning, and another popup alarm gets closer to (or further away from) the event, then the provider will read the other alarm.

Another possibility is that you have set an alarm value that is not supported by Google. Currently, Google only accepts values between 5 minutes and 4 weeks before the event starts.

===I want to set more than one alarm, but the Event dialog only shows one!===
Since Sunbird/Lightning also does not support multiple alarms, its very hard to do so without massive UI and calendar backend changes. I'd like to fix this in calendar rather than in the provider. See {{bug|353492}} for multiple alarms support.

Thunderbird/StatusMeetings/2009-11-24

2009-11-24T12:41:20Z

XFallenAngel: /* Fallen */

[[Thunderbird/StatusMeetings/2009-11-17|last meeting]] | [[Thunderbird/StatusMeetings|index]] | [[Thunderbird/StatusMeetings/2009-12-01|next meeting »]]

'''Thunderbird Meeting Details''' :

*[http://www.timeanddate.com/worldclock/fixedtime.html?year=2009&month=11&day=24&hour=17&min=30&sec=0 Tuesday, November 24th, 17:30 UTC] (9:30am Pacific, 12:30pm Eastern)
*[[Thunderbird/StatusMeeting/DialInInfo|How to dial-in]]

== Agenda ==

*Who's taking minutes? --> '''Ludovic'''
*[http://ascher.ca/thunderbird/minutes_schedule.html Minute taking Schedule]. Talk to davida for schedule changes/additions.

=== Action Items ===

==== New ====

==== Open ====
* Planning for a dry-run security firedrill build
** Fire drill itself expected to happen after code freeze

==== Closed ====

=== [[Thunderbird:Thunderbird3:Final|Thunderbird 3]] Developer Update ===

==== RC 1 ====

* Build 3 has been produced following a couple of blockers.
* Expecting to publicly release RC 1 on Wednesday.

==== Final ====

* Blockers are mainly web site updates.
* Remaining blockers are either trackers, or test-only/build changes to support the security & stability releases.

* [https://wiki.mozilla.org/Tree_Rules/comm-central#comm-1.9.1 Tree Rules for Thunderbird & 1.9.1 has been updated]

* Blockers
** [https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=blocking-thunderbird3%2B&sharer_id=1537 blocking-thunderbird3+]: 10 (+4)
** [https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=tb3needs&sharer_id=1537 TB 3 Needs]: 1 (0)
* Proposed Blocking
** {{trackinglist|Proposed Blockers (all)|blocking-thunderbird3?|---|}}: 2 (+2)

* Fixed RC1
** {{trackinglist|TB 3.0rc1 - blocking|blocking-thunderbird3%2B|FIXED|Thunderbird%203.0rc1}}: 155 (+1)

=== Thunderbird 3.next ===

=== QA Updates ===

=== Marketing Updates ===

=== IT update ===

=== Documentation ===

=== Support ===
# Top 5 GS Thunderbird 2 Support Topics (code in progress: http://gist.github.com/190923 ) basically the same as last week
## Cannot send email
## Cannot receive email ([http://getsatisfaction.com/mozilla_messaging/topics/could_not_connect_to_server_pop_att_yahoo_com_the_connection_was_refused AT&T POP server outage on November 20th])
## migration to Vista and Windows 7 from XP including email and address books and from Outlook and Outlook Express
## attachments not working
## [http://getsatisfaction.com/mozilla_messaging/topics/f_prot_6_0_9_3_reports_a_virus_in_thunderbird_2_0_0_23?topic_tools=open F-Prot false positive as of November 20] - Carsten is looking at it - [https://bugzilla.mozilla.org/show_bug.cgi?id=530582 bug 530582]
# Thunderbird 3 Beta Top Support Issues (starting to monitor to see what we can improve for post 3.0)
## Lots of folks want Thunderbird 3 RC 1 which is great!
# SUMO for MoMo tracker ticket: https://bugzilla.mozilla.org/show_bug.cgi?id=520628
## Gary Cunningham Lee now has full sftp/scp access so theming work should complete next week. Gary also has access for Get Satisfaction MoMo Branding, should be done this week.
## [[Thunderbird/Support/Initial_SuMoMo_content|Initial SuMoMo content complete with bugs for P1 and P2 - help us out! assign yourself a KB bug and write some KB articles]]
# Key Support stats from the following graphic:
## approximately 25/ day (172/7, slightly lower than last week if we subtract the Raindrop topics)
## total new topics:172 total replies: 64 ([http://gist.github.com/196464 Ruby Code])
### date:20091117 #new support topics:20 resolved:16
### date:20091118 #new support topics:27 resolved:9
### date:20091119 #new support topics:22 resolved:9
### date:20091120 #new support topics:26 resolved:12
### date:20091121 #new support topics:16 resolved:3
### date:20091122 #new support topics:12 resolved:2
### date:20091123 #new support topics:11 resolved:3
## #replies from non MoMo folks: 38 from pasa (thanks), 1 from gyurrika (thanks!) MoMo folks: 1 from Wayne Mery (thanks) 78 from Roland, Bienvenu 23 (thanks!), 1 from Tom (thanks!) 1 from Kent James (thanks) 5 from Lighning team (thanks!)
## happiness metric: API doesn't have happiness emotitags, asked GS staff about that, code in progress: http://gist.github.com/190094, manual happiness metric = 108 - 78 = 30 (26 last week), 49 Hendrix messages (generally Hendrix messages are unhappy but this week we had 1 happy messages) - [https://bugzilla.mozilla.org/show_bug.cgi?id=524801 bug to track down Hendrix for Thunderbird 3 and get rid of it as much as possible]
[[File:17-23November_2009_-_Community_stats_for_Mozilla_Messaging.png|500px]]

=== Roundtable ===

==== Status Updates ====

===== sid0 =====

===== davida =====

===== dmose =====

===== Standard8 =====

===== asuth =====

===== bienvenu =====

===== gozer =====

===== clarkbw =====

===== wsmwk =====

===== beckley =====

====== Penelope ======

===== KaiRo =====

===== rkent =====

===== rebron =====

===== Tsk =====

===== andreasn =====

===== bwinton =====

===== roland =====

===== sgautherie =====
*Fixed (or in-progress) MailNews Core bugs:
**{{bug|459693}} Eliminate nsFileSpec and nsIFileSpec (references) from MailNews
**{{bug|456860}} Improve msgCompSMIMEOverlay.js and msgReadSMIMEOverlay.js
**{{bug|523820}} Remove old MOZILLA_1_9_1_BRANCH ifdefs from comm-central code

===== nth10sd =====

===== Fallen =====
* Lightning 1.0b1rc1 currently planned for Wednesday
* Held beta release for {{bug|529326}} since it drastically improves performance and is an easy fix.
** Patch checked in, will be contained in tomorrow's nightly
** Simon [http://weblogs.mozillazine.org/calendar/2009/11/november_24_2009_lightningsunb.html blogged] about this today.
* Possible regression {{bug|529853}} needs to be debugged, might further hold up release.
** Patch pending review, will hopefully make it into the tree today
** If so, we can continue with the plan to spin rc1 on Wednesday.
** Nightly users with builds after 2009-11-07 might need to do some manual steps to avoid the error message in the mentioned bug. Will blog about this after the patch is checked in and the nightly is ready.

=== Attendees ===

__NOTOC__

Thunderbird/StatusMeetings/2009-11-24

2009-11-23T19:59:38Z

XFallenAngel: /* Fallen */

Calendar:Documentation

2009-11-20T10:23:54Z

XFallenAngel:

This page should be used for planning SUMO documentation for the Calendar Project. If you would like to contribute, please contact a member of [http://www.mozilla.org/projects/calendar/about.html the team].

Here follow some suggestions on which areas of Calendar could be documented. This is by no means all, feel free to add more.

* "Getting Started with Thunderbird, Lightning and your Google Calendar" (i.e. update with permission Jonny's faq at: http://bfish.xaedalus.net/2007/04/stay-in-sync-with-gcal-and-thunderbird/ - a quick and concise summary of getting started and doing the most common tasks for the most popular calendar provider
* Possibly transfer some FAQ items from [[Calendar:GDATA_Provider]]
* How do I access <insert calendar provider here, i.e yahoo, google> ?
* How do I open an ICS file
* How do I subscribe to a remote calendar
** Explain different calendar types (caldav, webdav, ...)

* Event Dialog
** How to create certain recurring events (custom)
** Custom alarms
*** In which cases Email/SMS alarms are available
** Inviting attendees
** Show time as free / show time as busy

* Setting up Invitations (i.e the email in the calendar properties dialog)
* Using Freebusy

* Explain the Today pane
* Explain Import/Export

* Give an overview of all keyboard shortcuts, with a link to the [http://www.mozilla.org/support/thunderbird/keyboard Thunderbird Keyboard Shortcuts]

Thunderbird/StatusMeetings/2009-11-17

2009-11-17T06:39:47Z

XFallenAngel:

[[Thunderbird/StatusMeetings/2009-11-10|last meeting]] | [[Thunderbird/StatusMeetings|index]] | [[Thunderbird/StatusMeetings/2009-11-24|next meeting »]]

'''Thunderbird Meeting Details''' :

*[http://www.timeanddate.com/worldclock/fixedtime.html?year=2009&month=11&day=17&hour=17&min=30&sec=0 Tuesday, November 17th, 17:30 UTC] (9:30am Pacific, 12:30pm Eastern)
*[[Thunderbird/StatusMeeting/DialInInfo|How to dial-in]]

== Agenda ==

*Who's taking minutes? --> '''davida'''
*[http://ascher.ca/thunderbird/minutes_schedule.html Minute taking Schedule]. Talk to davida for schedule changes/additions.

=== Action Items ===

==== New ====

==== Open ====
* Planning for a dry-run security firedrill build
** Fire drill itself expected to happen after code freeze

==== Closed ====

=== [[Thunderbird:Thunderbird3:Final|Thunderbird 3]] Developer Update ===

* Blockers
** [https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=blocking-thunderbird3%2B&sharer_id=1537 blocking-thunderbird3+]: 6 (+3)
** [https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=tb3needs&sharer_id=1537 TB 3 Needs]: 1 (0)
* Proposed Blocking
** {{trackinglist|Proposed Blockers (all)|blocking-thunderbird3?|---|}}: 6 (+6)

* Fixed RC1
** {{trackinglist|TB 3.0rc1 - blocking|blocking-thunderbird3%2B|FIXED|Thunderbird%203.0rc1}}: 154 (+9)

=== QA Updates ===

=== Marketing Updates ===

=== IT update ===

=== Documentation ===

=== Support ===

=== Roundtable ===

==== Status Updates ====

===== sid0 =====

===== davida =====

===== dmose =====

===== Standard8 =====

===== asuth =====

===== bienvenu =====

===== gozer =====

===== clarkbw =====

===== wsmwk =====

===== beckley =====

====== Penelope ======

===== KaiRo =====

===== rkent =====

===== rebron =====

===== Tsk =====

===== andreasn =====

===== bwinton =====

===== roland =====

===== sgautherie =====
*Fixed (or in-progress) MailNews Core bugs:
**{{bug|521618}} Port |Bug 520339 - Remove leftovers from MOZ_COMPONENTLIB| to comm-central
**{{bug|522713}} Port |Bug 448602 - Have a way to enumerate event listeners| to comm-central (apps)
**{{bug|524349}} Port |Bug 517417 - access violation: while compiling xulrunner tries to test for Mercurial repositories above its build dir| to comm-central
**{{bug|459693}} Eliminate nsFileSpec and nsIFileSpec (references) from MailNews
**{{bug|521624}} Port |Bug 517355 - Restore OJI, Liveconnect and the JEP on the 1.9.2 branch on OS X| to comm-central (apps)

===== nth10sd =====

===== Fallen =====
* No Beta blocker bugs left (1 checkin open), waiting for the remaining locales until Nov 21st.
* Will release 1.0b1rc1 shortly after
* Working on buildbot part of making nightlys localized ({{bug|346278}})
* Might need some help with the release engineering part of our beta release.

=== Attendees ===

__NOTOC__

Calendar:Documentation

2009-11-15T13:01:14Z

XFallenAngel:

Calendar:Documentation

2009-11-13T18:47:49Z

XFallenAngel: Created page with 'This page should be used for planning SUMO documentation for the Calendar Project. If you would like to contribute, please contact a member of [http://www.mozilla.org/projects/ca…'

Thunderbird/StatusMeetings/2009-11-03

2009-11-02T22:40:56Z

XFallenAngel: Fallen's progress

[[Thunderbird/StatusMeetings/2009-10-27|last meeting]] | [[Thunderbird/StatusMeetings|index]] | [[Thunderbird/StatusMeetings/2009-11-10|next meeting »]]

'''Thunderbird Meeting Details''' :

*[http://www.timeanddate.com/worldclock/fixedtime.html?year=2009&month=11&day=03&hour=17&min=30&sec=0 Tuesday, November 3rd, 17:30 UTC] (9:30am Pacific, 12:30pm Eastern)
*[[Thunderbird/StatusMeeting/DialInInfo|How to dial-in]]

== Agenda ==

*Who's taking minutes? --> '''clarkbw'''
*[http://ascher.ca/thunderbird/minutes_schedule.html Minute taking Schedule]. Talk to davida for schedule changes/additions.

=== Action Items ===

==== New ====

==== Open ====
* Planning for a dry-run security firedrill build
** Fire drill itself expected to happen after code freeze

==== Closed ====

=== [[Thunderbird:Thunderbird3:Final|Thunderbird 3]] ===

* Now in String freeze
* [http://ccgi.standard8.plus.com/blog/archives/306 Branching completed]
* Schedule:
** Code Freeze for RC1: 2009-10-30 23:59 PST
** L10n deadline: 2009-11-02 23:59 PST
** RC1 builds start on: 2009-11-03
** Subsequent RCs as necessary.

* Blockers
** [https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=blocking-thunderbird3%2B&sharer_id=1537 blocking-thunderbird3+]: 26 (-8)
** [https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=tb3needs&sharer_id=1537 TB 3 Needs]: 1 (0)
** GloDa patch: asuth still working through tests, likely to land today (Tues) or Weds
* Proposed Blocking
** {{trackinglist|Proposed Blockers (all)|blocking-thunderbird3?|---|}}: 7 (+7)

* Fixed RC1
** {{trackinglist|TB 3.0rc1 - blocking|blocking-thunderbird3%2B|FIXED|Thunderbird%203.0rc1}}: 126 (+10)

* Please set bugs to assigned status (as well as owner to you) if you want to do them.
* If you have other bugs assigned to you that you don't want to do, please reassign or discuss with drivers.

=== QA Updates ===

=== Marketing Updates ===

=== IT update ===

=== Documentation ===

=== Support ===

=== Roundtable ===

==== Status Updates ====

===== sid0 =====

===== davida =====

===== dmose =====

===== Standard8 =====

===== asuth =====

===== bienvenu =====

===== gozer =====

===== clarkbw =====

===== wsmwk =====

===== beckley =====

====== Penelope ======

===== KaiRo =====

===== rkent =====

===== rebron =====

===== Tsk =====

===== andreasn =====

===== bwinton =====

===== roland =====

===== sgautherie =====

===== nth10sd =====

===== Fallen =====
* {{bug|470430}} is finally checked in!
* If you have ever used Sunbird, please check if you have an empty folder:
**<code>$HOME\Application Data\Mozilla\Extensions\{718*\calendar-timezones@mozilla.org</code>
**<code>~/.mozilla/extensions/{718*/calendar-timezones@mozilla.org</code>
** If so, please report to {{bug|470430}}

* Now only bug 494140 is separating us from a firm code freeze.
* Waiting for a few locales to finish, will nudge them soon.
* If all this is finished, we are ready for beta 1 candidates.

=== Attendees ===

__NOTOC__

Calendar:GDATA Provider

2009-10-03T11:42:46Z

XFallenAngel: /* Accessing your Calendar */

=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==
You can obtain the provider from addons.mozilla.org. It is available for [https://addons.mozilla.org/sunbird/addon/4631 Sunbird] and [https://addons.mozilla.org/thunderbird/addon/4631 Lightning].

'''Notes:'''
* It is recommended to use the latest version of Sunbird or Lightning together with the latest Provider for Google Calendar version.
* If you are using the latest nightly versions of Sunbird/Lightning, please use the corresponding version from [ftp://ftp.mozilla.org/pub/calendar/lightning/nightly ftp.mozilla.org] (currently [September 2009] <nowiki>ftp://ftp.mozilla.org/pub/calendar/lightning/nightly/latest-comm-1.9.1/</nowiki> then the xpi subfolder corresponding to your platform).

==Building from Source==
If you want to build your own copy of the provider from the comm-central tree, all you need to do is follow the [https://developer.mozilla.org/en/Comm-central_source_code_(Mercurial)#Sunbird_and_Lightning build instructions] for Sunbird/Lightning. Once you have compiled, the resulting extension should be at <code>''obj-dir''/mozilla/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 ''Settings'' link located in the box at the left of the page.
# Click on the calendar you want to use with Thunderbird Lightning or Sunbird.
# Click on either of the two XML buttons shown at the bottom.

Authentication is always done securely via https. If you would also like to securely transfer your calendar data, then just change the URL to https://.. instead of http://...

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'' when clicking File > New > Calendar > On the Network > Google Calendar in Sunbird/Lightning. There is also a graphical tutorial available at [http://bfish.xaedalus.net/?p=239 bfish.xaedalus.net].

=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 answered here, please discuss it [http://groups.google.com/group/provider-for-google-calendar/topics on the newsgroup]. If you believe you have found a bug, please file it in [https://bugzilla.mozilla.org/enter_bug.cgi?product=Calendar&component=Provider:%20GData bugzilla]

==Enabling calendar.debug.log==
This option is useful for more verbose logging to diagnose problems you are having. It is also a good thing to look at before posting on the discussion group:

* Open your application preferences (Tools or Edit Menu)
* Select the "Advanced" icon at the top.
* Click on the "General" tab, below the icons
* Select "Advanced Configuration"
* Right Click on an empty space in the list of preferences
* Select New > Boolean
* Enter "calendar.debug.log" as the preference name
* Pick "true" as the Boolean value.

Now you have enabled the preference. If you were experiencing a problem, you will get the most debug messages if you restart the application, then do whatever you were doing again until you experience the issue. Then check out the error console ("Tools" menu).

If you are testing CalDAV support, you should do the same steps above for the "calendar.debug.log.verbose" preference.

==I want to stay up to date on all GData Provider bugs!==
Nothing easier than that. In your bugzilla Email preferences, you can set up a list of "users" to watch. Enter the <code>gdata-provider@calendar.bugs</code> email address, and you will receive bugmail on each update to GData Provider bugs and on new bugs.

==Calendar Access==
===I cannot access my calendar at all!===
Now this is very general. First things first: Do you see any error console messages? If not, please enable <code>calendar.debug.log</code> in the advanced config editor. See above for how to do that. You should be getting more debug messages now.

Are you using a calendar nightly? (i.e 1.0pre) If so, you must use a mercurial compiled version of the gdata provider, not the official release. This is also described above in this FAQ.

===I want to be able to pick my calendars from a list, is there a way to do so?===
Not currently. Progress on this is being tracked in {{bug|378873}}.

===I have publicly shared my calendar. I don't want to enter my password each time!===
For public calendars you don't need the Provider for Google Calendar. Just use the standard iCalendar Provider and the ICS feed from Google. If you want to change a public calendar, there is no way around entering your password.

===I want to access a friend's calendar I have access too, but I am asked for a password!===
No problem! As long as you have this calendar added in the Google Calendar web interface, just enter your own credentials.

==Missing Features==
===Why can't I configure any options in the Extension Manager?===
There are currently not enough options to warrant an options window. There are some advanced preferences:

<code>calendar.google.useHTTPMethodOverride = true</code> Instead of using PUT and DELETE methods, use POST and GET with the X-HTTP-Method-Override header. This is good for proxies and since it doesn't harm non-proxies, it defaults to true.

<code>calendar.google.alarmClosest = true</code> Alarm support: Use either the alarm closest (true) or farthest away (false) from the event as the alarm displayed in Sunbird/Lightning.

<code>calendar.google.sendEventNotifications = true</code> When set to true, invitations are sent out to attendees on event modifications.

<code>calendar.google.enableAttendees = false</code> When set to false, attendees are disabled. This might be needed if you experience problems when accepting invitations.

<code>calendar.google.sendEmailNotifications = false</code> Setting this to true allows selecting a Google Calendar when accepting an invitation you received via email. '''WARNING:''' Enabling this option may cause you to unknowingly spam all attendees with an extra invitation! Only enable this option if you know what you are doing.

===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 be able to edit my calendars while offline!===
Version 0.9 of lightning currently allows only read-only access to the calendar events while offline.

You might want to monitor progress of [https://bugzilla.mozilla.org/show_bug.cgi?id=380060 bug 380060] to be informed on any progress on editing during offline mode feature.

==Event Interaction==
===I have set a category, but when changing the event it vanishes===
This could be caused due to {{bug|461995}}. I hope this will be fixed in the next version.

===I want to modify an Event but nothing happens. What am I doing wrong?===
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.

===After creating a recurring event, I am having problems with alarms. Why?===
Aside from the fact that there is no standardized scheme to store dismissing and snoozing alarms, Google doesn't allow setting certain properties on recurring events. This is especially the case for shared calendars. See bug {{bug|424185}} 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.

Also if you are using windows, make sure you have all timezone upgrades installed.

===Why can't I create tasks on a Google Calendar?===
Lately Google supports Tasks now, so it is a question of time when Provider will support that too :)

==Attendees==
===I recieved an invitation from a friend. When trying to accept, my Google Calendars are not in the select calendar dialog, or no dialog is shown===
Accepting an invitation onto your Google Calendar can cause extra invitations being sent out to each attendee. Due to some Google Calendar limitations when adding invitations to your calendar its impossible to allow this in a way that new users will not shoot themselves in the foot.

If you know what you are doing, you can still re-enable this behavior. See the FAQ question regarding options.

===After accepting an invitation, the attendees all get an additional invitation from me===
This is {{bug|400808}}. A workaround is to set <code>calendar.google.sendEventNotifications</code> to false in the advanced config editor, or to not handle event invitations via lightning. Note that setting this preference inhibits all sending of event notifications.

==Alarms==
===What should I keep in mind while using alarms with the provider?===
The provider will only alert alarms of type popup. Depending on the setting of the (boolean) property ''calendar.google.alarmClosest'', it will read either the popup alarm closest to the event (true) or furthest away (false). To avoid confusion, be sure you set only one alarm with type popup. All other alarm types will not be touched by the provider.

===I have set some default reminders in the Google UI, but they don't show up on new events?===
As it might be easy to tell Google to use those default reminders, it requires UI additions to sunbird/lightning. I would like to concentrate on backend functionality before I add such UI extensions. If you would like this functionality, feel free to file an enhancement bug in bugzilla. (Remember to search if such a bug exists first).

===I set an alarm on an event but after looking at the event again, the alarm has a totally different value!===
Since Google supports multiple alarms and sunbird/lightning only supports one alarm, its hard to find a good way to map between the possible alarms. The provider will read the alarm either closest to or furthest away from the event. If you change a popup alarm in sunbird/lightning, and another popup alarm gets closer to (or further away from) the event, then the provider will read the other alarm.

Another possibility is that you have set an alarm value that is not supported by Google. Currently, Google only accepts values between 5 minutes and 4 weeks before the event starts.

===I want to set more than one alarm, but the Event dialog only shows one!===
Since Sunbird/Lightning also does not support multiple alarms, its very hard to do so without massive UI and calendar backend changes. I'd like to fix this in calendar rather than in the provider. See {{bug|353492}} for multiple alarms support.

EU MozCamp 2009/Participants

2009-09-03T14:53:52Z

XFallenAngel:

Participants list

{|border="1" cellpadding="5" cellspacing="0"
|-
! Name
! Country
! I work on
|-
|Aizpuru Julen || ||
|-
|Aliiev Rail || ||
|-
|Babych Timothy || ||
|-
|Ballesteros Eva || ||
|-
|Bambas Honza || ||
|-
|Bassetto Thomas || ||
|-
|Beard Chris || ||
|-
|Beddoes Jonathan || ||
|-
|Benes Wim || ||
|-
|Benesperi Iacopo || ||
|-
|Bengoa David || ||
|-
|Biesinger Christian || ||
|-
|Bindernagel Seth || ||
|-
|Blanc William || ||
|-
|Brablc Ondrej || ||
|-
|Braniecki Zbigniew || ||
|-
|Brunschwig Patrick || ||
|-
|Buchner Julia || ||
|-
|Cazenave Fabien || ||
|-
|Châteaux Frédéric || ||
|-
|Chevrel Pascal || ||
|-
|Colmard Bastien || ||
|-
|Corazza Cédric || ||
|-
|Coustenoble Gregoire || ||
|-
|De Voogd Otto || ||
|-
|Dejus Raivis || ||
|-
|Desré Fabrice || ||
|-
|Dessante Philippe || ||
|-
|Dinic Milos || ||
|-
|Dominikowski Tomasz || ||
|-
|Düsterloh Karsten || ||
|-
|Duyck William || ||
|-
|England Steve || ||
|-
|Finch Patrick || ||
|-
|Fiotakis George || ||
|-
|Fraisse Laurent || ||
|-
|Franc Pavel || ||
|-
|Frinolli Carlo || ||
|-
|Fritze Alexander || ||
|-
|Gajewski Hubert || ||
|-
|Gambier Olivier || ||
|-
|Gamonal Edu || ||
|-
|Garcia Gomez Fernando || ||
|-
|Garcia Rodriguez Pedro || ||
|-
|Gautherie Serge || ||
|-
|Gaztelumendi Patxi || ||
|-
|Gemal Henrik || ||
|-
|Gertner Matthew || ||
|-
|Gladkov Alexiej || ||
|-
|Glogowski Grzegorz || ||
|-
|Gozalishvili Irakli || ||
|-
|Greco Luca || ||
|-
|Hassman Martin || ||
|-
|Hecht Axel || ||
|-
|Hermes Stefan || ||
|-
|Hermoso Pulido Toni || ||
|-
|Hirlimann Ludovic || ||
|-
|Hofmann Chris || ||
|-
|Horvat Matjaz || ||
|-
|Hueppe Barbara || ||
|-
|Ian Neal || ||
|-
|Iyer Anusha || ||
|-
|Izquierdo Daniel || ||
|-
|Jouanneau Laurent || ||
|-
|Jovanovski Gorjan || ||
|-
|Kaiser Robert || ||
|-
|Kalamujic Kerim || ||
|-
|Kalla Adrian || ||
|-
|Kemenczy Kalman || ||
|-
|Kewisch Philipp || Germany || Mozilla Calendar Project
|-
|King Brian || ||
|-
|Kirsch Daniel|| ||
|-
|Knous Marcia || ||
|-
|Koehler Michael || ||
|-
|Kristensen Jesper || ||
|-
|Kristoffersen Mike || ||
|-
|Kulev Ognyan || ||
|-
|Lach Kamil || ||
|-
|Lando Simone || ||
|-
|Lau Stephen || ||
|-
|Lebédel Delphine || ||
|-
|Leingruber Tobias|| ||
|-
|Lepikhov Konstantin A. || ||
|-
|Leseul Benoit|| ||
|-
|Lodolo Francesco|| ||
|-
|López Guillermo || ||
|-
|Maças Ricardo || ||
|-
|Małolepszy Stanisław|| ||
|-
|Marcon Jean-Bernard|| ||
|-
|Markham Gervase || ||
|-
|Markus Tobias || ||
|-
|Marteau David || ||
|-
|Martín Rubén || ||
|-
|Mazgaj Joanna || ||
|-
|Menge Cédric || ||
|-
|Mierlus Alina || ||
|-
|Mirra Massimiliano || ||
|-
|Moody Glyn || ||
|-
|Mous Fabrice || ||
|-
|Munk Skrøder Søren || ||
|-
|Narayanan Anant || ||
|-
|Neves Miguel Joao || ||
|-
|Nicolas Vivien || ||
|-
|Ninove Thibaut || ||
|-
|Nitot Tristan || ||
|-
|Novak Chelsea || ||
|-
|Nyman Robert || ||
|-
|Odvarko Jan || ||
|-
|Papadimas Kostas || ||
|-
|Paquet Simon || ||
|-
|Parmenter Stuart || ||
|-
|Pasche Sylvain || ||
|-
|Peev Pavel || ||
|-
|Picolini Francisco || ||
|-
|Piers Sonny || ||
|-
|Plewako Stefan || ||
|-
|Quèze Florian || ||
|-
|Quiviger William || ||
|-
|Raskin Aza || ||
|-
|Rodaro Michele || ||
|-
|Romera Teo || ||
|-
|Rouget Paul || ||
|-
|Rozbora Branislav || ||
|-
|Ruiz Miriam || ||
|-
|Sandu Irina || ||
|-
|Schloegl Florian || ||
|-
|Schroeder Martin || ||
|-
|Schwecherl Thomas || ||
|-
|Seghers Jeroen || ||
|-
|Sell Merike || ||
|-
|Shopov Bogomil || ||
|-
|Skupin Henrik || ||
|-
|Slovesnik Alexander || ||
|-
|Soref Josh || ||
|-
|Stawarz Katarzyna || ||
|-
|Stępień Marek || ||
|-
|Surman Mark || ||
|-
|Szasz Alexandru || ||
|-
|Tenser David || ||
|-
|Timar Andras || ||
|-
|Topal Abdulkadir || ||
|-
|Turbureanu Tiberiu || ||
|-
|Valastiak Vlado || ||
|-
|van der Woude Peter || ||
|-
|Wargers Martin || ||
|-
|Yen Mark || ||
|-
|Younsi Arzhel|| ||
|-
|Zwart Marien || ||
|}

EU MozCamp 2009/DevTrack

2009-09-01T09:01:04Z

XFallenAngel:

List of potential topics:

* Global overview of the labs projects
* firefox.next
* TB3 and future of messaging
* performance
* video/audio element
* Fennec
* Extension 2.0, Jetpack
* XBL2
* multi process
* Semantic Web (web + extensions)
* WebDev
* Prism
* Unit Test mozmill
* Seamonkey 2.0
* Firebug
* l20n status update, bof (Axel etc)
* Calendar Topic (TBD, tentative)

Todo:
* an early draft grid for the schedule: see [https://wiki.mozilla.org/EU_MozCamp_2009/Tentative_Schedule]
* continue working on the list of potential topics
* reach out to potential speakers (focus on Europe)

EU MozCamp 2009/Tentative Schedule

2009-08-28T14:29:05Z

XFallenAngel:

See track view: [https://wiki.mozilla.org/EU_MozCamp_2009/Schedule/Advocacy_Track Advocacy], [https://wiki.mozilla.org/EU_MozCamp_2009/Schedule/Dev_Track Dev], [https://wiki.mozilla.org/EU_MozCamp_2009/Schedule/L10n_Track L10n], [https://wiki.mozilla.org/EU_MozCamp_2009/Schedule/QA_Track QA].

==Saturday 3 October, 2009==

{| border=1 |
|-
{{EUCamp08HeaderRow}}
|-
{{EUCamp08FullRow
|time=08:30 - 09:30
|all=Welcome coffee
}}
|-
{{EUCamp08Row
|time=09:30 - 09:40
|Main=Welcome address - Tristan Nitot
|Opal=
|Topaz=
|Quartz=
|Sapphire=
|Crystal=
}}
|-
{{EUCamp08Row
|time=09:40 - 10:20
|Main= Opening keynote
|Opal=
|Topaz=
|Quartz=
|Sapphire=
|Crystal=
}}
|-
{{EUCamp08Row
|time=10:25 - 11:00
|Main=Keynote speaker 2
|Opal=
|Topaz=
|Quartz=
|Sapphire=
|Crystal=
}}
|-
{{EUCamp08Row
|time=11:00 - 11:45
|Main=Keynote speaker 3
|Opal=
|Topaz=
|Quartz=
|Sapphire=
|Crystal=
}}
|-
{{EUCamp08FullRow
|time=12:00 - 13:00
|all=Lunch
}}
|-
{{EUCamp08Row
|time=13:00 - 13:45
|Main=
|Opal=Firefox.next: performance
|Topaz=Mozilla Calendar Project (tentative)
|Quartz=L10n-drivers Team Presentation
|Sapphire=Promoting Mozilla software
|Crystal=
}}
|-
{{EUCamp08Row
|time=14:00 - 14:45
|Main=
|Opal=TB3 and future of messaging
|Topaz=Fennec, what's next
|Quartz=Testing session with Pike
|Sapphire=Promoting the causes near to our heart: open source, the open web, the use of (open) standards in technology
|Crystal=
}}
|-
{{EUCamp08FullRow
|time=15:00 - 15:45
|all=Coffee break
}}
|-
{{EUCamp08Row
|time=16:00 - 16:45
|Main=
|Opal=Global overview of the labs projects
|Topaz=SUMO - Where we're at and where we're going
|Quartz=QA and l10n roundtable
|Sapphire=influencing organisations to change (e.g. to upgrade from IE6)
|Crystal=
}}
|-
{{EUCamp08Row
|time=17:00 - 17:45
|Main=
|Opal=Seamonkey 2.0
|Topaz=Fennec extensions
|Quartz=Automated Testing
|Sapphire=Organising Communities, best practices
|Crystal=
}}
|-
{{EUCamp08Row
|time=18:00 - 18:45
|Main=
|Opal=multi process
|Topaz=
|Quartz=L10n toolkit - Silme demo/workshop
|Sapphire=
|Crystal=
}}
|-
|}

==Sunday 4 October, 2009==

{| border=1 |
|-
{{EUCamp08HeaderRow}}
|-
{{EUCamp08FullRow
|time=9:00 - 9:45
|all=Welcome coffee
}}
|-
{{EUCamp08Row
|time=10:00 - 10:30
|Main=Keynote speaker 1
|Opal=
|Topaz=
|Quartz=
|Sapphire=
|Crystal=
}}
|-
{{EUCamp08Row
|time=10:30 - 11:00
|Main=Keynote speaker 2
|Opal=
|Topaz=
|Quartz=
|Sapphire=
|Crystal=
}}
|-
{{EUCamp08Row
|time=11:00 - 11:45
|Main=Mozilla 2010 Goals Discussion
|Opal=
|Topaz=
|Quartz=
|Sapphire=
|Crystal=
}}
|-
{{EUCamp08Row
|time=11:45 - 12:30
|Main=
|Opal=
|Topaz=
|Quartz=
|Sapphire= Mozilla Foundation Initiatives
|Crystal=
}}
|-
{{EUCamp08Row
|time=12:45 - 13:30
|Main=
|Opal=Firebug
|Topaz=
|Quartz=Writing a minimized test case
|Sapphire=Experiences in your region
|Crystal=
}}
|-
{{EUCamp08FullRow
|time=13:30 - 14:30
|all=Lunch
}}
|-
{{EUCamp08Row
|time=14:30 - 15:15
|Main=
|Opal=Firefox.next: UI
|Topaz=
|Quartz=
|Sapphire=Promoting the Mozilla Creative Collective in Europe
|Crystal=
}}
|-
{{EUCamp08Row
|time=15:30 - 16:15
|Main=
|Opal=Extension 2.0 (Jetpack ?)
|Topaz=MozMill
|Quartz=
|Sapphire=
|Crystal=
}}
|-
{{EUCamp08Row
|time=16:30 - 17:15
|Main=
|Opal=XBL2
|Topaz=Prism
|Quartz=MCS : How to start a community website and develop it
|Sapphire=
|Crystal=
}}
|-
{{EUCamp08Row
|time=17:30 - 18:15
|Main=
|Opal=
|Topaz=video/audio element
|Quartz=
|Sapphire=
|Crystal=
}}
|-
{{EUCamp08FullRow
|time=18:30 - 19:30
|all=Good bye coffee break
}}
|-
|}

EU MozCamp 2009/Tentative Schedule

2009-08-28T14:27:45Z

XFallenAngel:

See track view: [https://wiki.mozilla.org/EU_MozCamp_2009/Schedule/Advocacy_Track Advocacy], [https://wiki.mozilla.org/EU_MozCamp_2009/Schedule/Dev_Track Dev], [https://wiki.mozilla.org/EU_MozCamp_2009/Schedule/L10n_Track L10n], [https://wiki.mozilla.org/EU_MozCamp_2009/Schedule/QA_Track QA].

==Saturday 3 October, 2009==

{| border=1 |
|-
{{EUCamp08HeaderRow}}
|-
{{EUCamp08FullRow
|time=08:30 - 09:30
|all=Welcome coffee
}}
|-
{{EUCamp08Row
|time=09:30 - 09:40
|Main=Welcome address - Tristan Nitot
|Opal=
|Topaz=
|Quartz=
|Sapphire=
|Crystal=
}}
|-
{{EUCamp08Row
|time=09:40 - 10:20
|Main= Opening keynote
|Opal=
|Topaz=
|Quartz=
|Sapphire=
|Crystal=
}}
|-
{{EUCamp08Row
|time=10:25 - 11:00
|Main=Keynote speaker 2
|Opal=
|Topaz=
|Quartz=
|Sapphire=
|Crystal=
}}
|-
{{EUCamp08Row
|time=11:00 - 11:45
|Main=Keynote speaker 3
|Opal=
|Topaz=
|Quartz=
|Sapphire=
|Crystal=
}}
|-
{{EUCamp08FullRow
|time=12:00 - 13:00
|all=Lunch
}}
|-
{{EUCamp08Row
|time=13:00 - 13:45
|Main=
|Opal=Firefox.next: performance
|Topaz=
|Quartz=L10n-drivers Team Presentation
|Sapphire=Promoting Mozilla software
|Crystal=
}}
|-
{{EUCamp08Row
|time=14:00 - 14:45
|Main=
|Opal=TB3 and future of messaging
|Topaz=Fennec, what's next
|Quartz=Testing session with Pike
|Sapphire=Promoting the causes near to our heart: open source, the open web, the use of (open) standards in technology
|Crystal=
}}
|-
{{EUCamp08FullRow
|time=15:00 - 15:45
|all=Coffee break
}}
|-
{{EUCamp08Row
|time=16:00 - 16:45
|Main=
|Opal=Global overview of the labs projects
|Topaz=SUMO - Where we're at and where we're going
|Quartz=QA and l10n roundtable
|Sapphire=influencing organisations to change (e.g. to upgrade from IE6)
|Crystal=
}}
|-
{{EUCamp08Row
|time=17:00 - 17:45
|Main=
|Opal=Seamonkey 2.0
|Topaz=Fennec extensions
|Quartz=Automated Testing
|Sapphire=Organising Communities, best practices
|Crystal=
}}
|-
{{EUCamp08Row
|time=18:00 - 18:45
|Main=
|Opal=multi process
|Topaz=
|Quartz=L10n toolkit - Silme demo/workshop
|Sapphire=
|Crystal=
}}
|-
|}

==Sunday 4 October, 2009==

{| border=1 |
|-
{{EUCamp08HeaderRow}}
|-
{{EUCamp08FullRow
|time=9:00 - 9:45
|all=Welcome coffee
}}
|-
{{EUCamp08Row
|time=10:00 - 10:30
|Main=Keynote speaker 1
|Opal=
|Topaz=
|Quartz=
|Sapphire=
|Crystal=
}}
|-
{{EUCamp08Row
|time=10:30 - 11:00
|Main=Keynote speaker 2
|Opal=
|Topaz=
|Quartz=
|Sapphire=
|Crystal=
}}
|-
{{EUCamp08Row
|time=11:00 - 11:45
|Main=Mozilla 2010 Goals Discussion
|Opal=
|Topaz=
|Quartz=
|Sapphire=
|Crystal=
}}
|-
{{EUCamp08Row
|time=11:45 - 12:30
|Main=
|Opal=
|Topaz=
|Quartz=
|Sapphire= Mozilla Foundation Initiatives
|Crystal=
}}
|-
{{EUCamp08Row
|time=12:45 - 13:30
|Main=
|Opal=Firebug
|Topaz=
|Quartz=Writing a minimized test case
|Sapphire=Experiences in your region
|Crystal=
}}
|-
{{EUCamp08FullRow
|time=13:30 - 14:30
|all=Lunch
}}
|-
{{EUCamp08Row
|time=14:30 - 15:15
|Main=
|Opal=Firefox.next: UI
|Topaz=Mozilla Calendar Project (tentative)
|Quartz=
|Sapphire=Promoting the Mozilla Creative Collective in Europe
|Crystal=
}}
|-
{{EUCamp08Row
|time=15:30 - 16:15
|Main=
|Opal=Extension 2.0 (Jetpack ?)
|Topaz=MozMill
|Quartz=
|Sapphire=
|Crystal=
}}
|-
{{EUCamp08Row
|time=16:30 - 17:15
|Main=
|Opal=XBL2
|Topaz=Prism
|Quartz=MCS : How to start a community website and develop it
|Sapphire=
|Crystal=
}}
|-
{{EUCamp08Row
|time=17:30 - 18:15
|Main=
|Opal=
|Topaz=video/audio element
|Quartz=
|Sapphire=
|Crystal=
}}
|-
{{EUCamp08FullRow
|time=18:30 - 19:30
|all=Good bye coffee break
}}
|-
|}

User:Dmose:Helping New Lightning Hackers

2009-06-14T20:25:55Z

XFallenAngel: /* Straw-man plan to make above happen */

== Draft strategy for a newly arrived Lightning hacker ==
* set up [[Education/Learning/Irc|IRC]] client to auto-join #education, #calendar, and #maildev
* use #education as a first place to ask for help (especially on stuff not specific to Ltn or Tb)
* pull Thunderbird and Lightning from comm-central, make a build that works
* find a few [http://bit.ly/B6Ei5 [good first bug]]s and do them
* find a bug with a [http://vocamus.net/dave/?p=408 student-project] keyword, discuss with humph/Fallen and do it
* talk to Fallen to find next project

== Straw-man plan to make above happen ==
* find a reasonable set of lightning bugs (10?) to give student-project keyword
* review existing [good first bug]s to ensure that they're still relevant and make sense
* start directing newbies to #education and humph
* draft/publish Lightning near-term roadmap
* draft blog post asking for help, with links to the ramp-up process above and the various buglists
* send version of blog posts to various folks who have expressed interest in the past (dmose has a partial list)
* Make documentation more appealing, provide landing page for new developers

Calendar:Status

2009-03-15T09:49:50Z

XFallenAngel:

'''There will no longer be a separate Calendar phone meeting'''

Due to [http://weblogs.mozillazine.org/calendar/2009/02/calendar_project_at_a_critical.html recent developments], we have decided to fold the Calendar status meeting into the [[Thunderbird/StatusMeetings|Thunderbird status meeting]].

Aside from that, we will be posting updates in the [http://groups.google.com/group/mozilla.dev.apps.calendar/topics newsgroups] and the [http://weblogs.mozillazine.org/calendar/ calendar blog]

The last meeting log can be found [[Calendar:Status_Meetings:2008-12-17|here]].

MAOW:2009:Berlin:en

2009-03-11T17:42:44Z

XFallenAngel:

{| class="messagebox standard-talk" style="text-align:center; border:0px;"
| http://workshop.xulfr.org/pics/robot.png
|-
| '''Mozilla Add-Ons Workshop :: Berlin'''
|-
|Berlin, Saturday 28th of March 2009
|-
|[http://events.mozilla-europe.org/event/?id=4 Online registration required]
|-
| '''In collaboration with the German community'''
|-
|}<noinclude>

== What is the MAOW? ==

Have you always dreamed of going behind the scenes of Firefox ? Are you a Web developer (or not yet!) and have you always wished to make your first Firefox extension ? As an Add-ons developer, you are familiar with XUL, overlays, chrome, but have never dared go further?

This is the opportunity for you to make your wish come true: the next Mozilla Add-ons Workshop is coming to Berlin, on Saturday, 28th of March! In collaboration with the German Xul community, the MAOW will be a day of workshops and presentations (mostly in German, but also English) about Mozilla Technologies, and more particularly about Add-ons.

The schedule includes workshops that will teach you how to make your first extension, many presentations of new Mozilla technologies, conferences on how to hack and contribute to Firefox ... and on top of this, you'll be able to discuss with skillful developers, along with a nice cup of coffee. And not to forget to mention your own demonstrations of Add-ons and of XulRunner applications !

And last but not least, we have the honor to announce the presence of Rey Bango, Community Manager for Mozilla Add-ons, and of Paul Rouget, Mozilla Tech Evangelist, as well as many active members of the Mozilla community.

== Participants ==

Web developers, hackers, C++ developers, XUL developers, or bloggers, journalists and people just plain curious about Firefox Add-ons : '''EVERYONE IS WELCOME and ENTRANCE IS FREE'''

== Goals ==

* Propose a base for discussions and exchange for XUL developers and non developers.
* Encourage and facilitate the creation and diffusion of Add-ons by German developers.
* Promote a local Mozilla ecosystem.

== Schedule ==

If you know the Mozilla platform, we strongly encourage you to help us by giving a talk : feel free to send an email to Paul Rouget <paul at mozilla dot com>. It can be about one these proposed talks, or something from you.

Here is a tentative schedule.

<table cellspacing="4" border="0" cellpadding="3" align="center">
<tr>
<td align="center" bgcolor="#d3d3d3" width="100">Time Slot</td>
<td colspan="3" align="center" bgcolor="#d3d3d3" width="150">Main room</td>
</tr>

<tr>
<td align="center" bgcolor="#d3d3d3">10:00 - 11:00</td>
<td align="center" bgcolor="#d3d3d3" colspan="3">WELCOME COFFEE</td>
</tr>

<tr>
<td align="center" bgcolor="#d3d3d3">11:00 - 11:10</td>
<td valign="top" align="center" bgcolor="#d3d3d3" colspan="3">Welcome introduction - Paul Rouget</td>
</tr>

<tr>
<td align="center" bgcolor="#d3d3d3">11:10 - 12:00</td>
<td valign="top" align="center" bgcolor="#d3d3d3" colspan="3">Keynote - Rey Bango</td>
</tr>

<tr>
<td align="center" bgcolor="#d3d3d3">12:00 - 12:45</td>
<td colspan="3" align="center" bgcolor="#d3d3d3">LUNCH</td>
</tr>

<tr>
<td align="center" bgcolor="#d3d3d3" width="100"> </td>
<td align="center" bgcolor="#d3d3d3" width="150">Main Room</td>
<td align="center" bgcolor="#d3d3d3" width="150">Room A</td>
<td align="center" bgcolor="#d3d3d3" width="150">Room B</td>
</tr>

<tr>
<td align="center" bgcolor="#d3d3d3">12:45 - 13:30</td>
<td align="center" bgcolor="#d3d3d3">The Mozilla Build System: Robert Kaiser</td>
<td align="center" bgcolor="#d3d3d3">How to write your first extension: Robert Nyman</td>
<td align="center" bgcolor="#d3d3d3">TBD</td>
</tr>

<tr>
<td align="center" bgcolor="#d3d3d3">13:30 - 14:15</td>
<td align="center" bgcolor="#d3d3d3">Quality assurance: Carsten Book</td>
<td align="center" bgcolor="#d3d3d3">How to write your first XulRunner application: Daniel Glazman</td>
<td align="center" bgcolor="#d3d3d3">Gecko 1.9.1, what's new?: Yan Minagawa</td>
</tr>

<tr>
<td align="center" bgcolor="#d3d3d3">14:15 - 14:30</td>
<td colspan="3" align="center" bgcolor="#d3d3d3">COFFEE BREAK</td>
</tr>

<tr>
<td align="center" bgcolor="#d3d3d3">14:30 - 15:15</td>
<td align="center" bgcolor="#d3d3d3">Fun and Art: Tobias Leingruber</td>
<td align="center" bgcolor="#d3d3d3">Make money with extensions: Daniel Glazman</td>
<td align="center" bgcolor="#d3d3d3">TBD</td>
</tr>
<tr>
<td align="center" bgcolor="#d3d3d3">15:15 - 16:00</td>
<td align="center" bgcolor="#d3d3d3">Ubiquity: Rey Bango</td>
<td align="center" bgcolor="#d3d3d3">TBD</td>
<td align="center" bgcolor="#d3d3d3">TBD</td>
</tr>
<tr>
<td align="center" bgcolor="#d3d3d3">16:00 - 16:15</td>
<td colspan="3" align="center" bgcolor="#d3d3d3">COFFEE BREAK</td>
</tr>
<tr>
<td align="center" bgcolor="#d3d3d3">16:15 - 17:00</td>
<td align="center" bgcolor="#d3d3d3">How to localize your extension: Jurgen Berg</td>
<td align="center" bgcolor="#d3d3d3">Javascript in add-ons (jsm, XPCOM, 1.7/1.8, and more): Brian King</td>
<td align="center" bgcolor="#d3d3d3">TBD</td>
</tr>
<tr>
<td align="center" bgcolor="#d3d3d3">17:00 - 17:45</td>
<td align="center" bgcolor="#d3d3d3">make extensions work on SeaMonkey 2: Robert Kaiser</td>
<td align="center" bgcolor="#d3d3d3">XBL: Daniel Kirsch</td>
<td align="center" bgcolor="#d3d3d3">Enlightening the Calendar: Writing Calendaring extensions: Philipp Kewisch</td>
</tr>

</table>

== Speakers ==

[[Image:Paul_r.jpg|left|A picture of Paul Rouget]]
* Paul Rouget:
Mozilla Tech Evangelist, organizer.

[[Image:Robert-nyman.jpg|left|A picture of Robert Nyman]]
* Robert Nyman:
Robert has been working with web developing, mostly interface coding, since 1998. His biggest interests lie in HTML, CSS and JavaScript. In his talk he will talk you through your first steps with Firefox extension development to a complete runnable extension.

[[Image:Tbx_avatar.gif|left|A picture of Tobias Leingruber]]
* Tobias Leingruber:
Tobias' background is web development and visual design. In 2007 he fell in love with FF add-ons and remixing the web. The browser is his operating system. He will show a collection of [http://bits.blogs.nytimes.com/2009/02/12/firefox-add-ons-double-as-art-pranks-fun/ fun and experimental add-ons] .

[[Image:Bk_square_64.jpg|left|A picture of Brian King]]
* Brian King:
Long-time Mozilla contributor, Founder of [http://briks.si Briks Software] and President of [http://mozdev.org Mozdev].

[[Image:RobertKaiser.jpg‎|left|A picture of Robert Kaiser]]
* Robert Kaiser ("[[User:KaiRo|KaiRo]]"):
German Mozilla localizer since late 1999, theme designer and code contributor to L10n, build system, UI and SeaMonkey areas, SeaMonkey Council member, serving as project coordinator and build/release engineer.

[[Image:PhilippKewisch.jpg|64px|left|A picture of Philipp Kewisch]]
* Philipp Kewisch:
...has been contributing to the Calendar Project since late 2006. He started out with the Provider for Google Calendar and after many core code contriutions now leads the Project.

== When? ==

Saturday 28th of March, 2009

10:00 to 22:00

== Where? ==

The MAOW Berlin will take place at the C-Base Raumstation (see map [http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&q=c-base+berlin&sll=37.0625,-95.677068&sspn=36.231745,79.101563&ie=UTF8&ll=52.513962,13.419757&spn=0.006803,0.019312&z=16&iwloc=A here]).

For more information on C-Base, please visit http://c-base.org

== Registration ==

All participants are asked to register by filling in the MAOW Berlin registration form [http://events.mozilla-europe.org/event/?id=4 here].

== Speaker Sponsorship ==

All speakers at the MAOW will be fully sponsored. Hotel, food and travel expenses will be fully reimbursed by Mozilla Europe.

To be reimbursed, please send all scanned receipts and the filled-out expense form to William Quiviger (william @ mozilla dot com)

== Information & Contact ==

For any further information, please contact:

* Paul Rouget <paul @ mozilla dot com> (english)
* Wiliam Quiviger <william @ mozilla dot com> (english)

File:PhilippKewisch.jpg

2009-03-11T17:34:26Z

XFallenAngel: Avatar photo of Philipp Kewisch

Avatar photo of Philipp Kewisch

Calendar:Build

2009-03-08T10:12:23Z

XFallenAngel: Linux infos

[[Calendar:Home_Page|<< Back to Calendar Home Page]]

This guide gives you all the information you need to get started with calendar development. While this guide might be quite long, I assume you will need 20-30 minutes ( + time to build the app) to set up everything and have a running development environment.

Note this guide is written for use directly from the console. There is no known documentation to set up a build environment inside IDE's like eclipse or netbeans. If you manage to set up eclipse for calendar, it would be great if you could contribute documentation!

=Setting up prerequisites=
''General documentation [http://developer.mozilla.org/en/docs/Build_Documentation#Build_requirements here]''

The general section on build prerequisites is quite complete and should be used to determine what is needed.

====Additional, Mac-Specific info====
You should install the latest Xcode. This may be available on your MacOS Tiger restore CD (takes about ten minutes), but a later version is probably available at [[http://developer.apple.com/technology/xcode.html developer.apple.com]].

Next you need to install either Fink or MacPorts. I went with MacPorts. You can download it [http://svn.macosforge.org/repository/macports/downloads/ here]. Installing MacPorts is as simple as running the installer found in the mounted .dmg. (five minutes)

Next, use MacPorts to install libIDL (which also installs GLib). You will need to have your administrative password ready; takes around five to ten minutes, depending on your internet connection.
<pre>
sudo port sync
sudo port install libidl
</pre>

====Additional, Linux-Specific info====

You may need to install a few packages to allow building Calendar. The following should install most needed packages. If you happen to have a freshly installed system and a package is please extend this list. The following works on ubuntu, other distributions may have different package names.

<pre>
sudo apt-get install build-essential
sudo apt-get install \
libfishsound1-dev \
libtheora-dev \
libogg-dev \
libxt-dev \
libgconf2-dev \
libgnomeui-dev \
libgnomevfs-dev \
libgnome-dev \
libdbus-glib-1-dev \
pango \
cairo
</pre>

=Getting the source=
There is extensive ''[https://developer.mozilla.org/en/Comm-central_source_code_(Mercurial) documentation]'' on how to get the Calendar source code on [https://developer.mozilla.org developer.mozilla.org].

The source code must be checked out via Mercurial (hg).

In general, you should use a directory for the source code that does not contain spaces or such, i.e on windows "C:\Documents and Settings\MyUsername\My Documents\mozilla" is not a good choice.

Before you start to build, you will need to configure your build environment to build Lightning. Since Lightning is an extension it needs to be built together with its host application Thunderbird.

<pre># Enter the source directory
cd $COMM_CENTRAL (we assume that $COMM_CENTRAL is your source directory here)

# Generate a mozconfig yourself, or use this minimal default one for Thunderbird
echo 'ac_add_options --enable-application=mail' > .mozconfig

# Add calendaring to Thunderbird
echo 'ac_add_options --enable-calendar' >> .mozconfig

# Builds with the object directory the same as the source directory are not
# supported, so set the object directory here. Note: Whether you have the
# object directory within the source directory is up to you. .hgignore includes
# objdir-* and obj-*, making your object directory start with one of them
# will make change finding easier and hg faster, but moving it to outside
# will make things like grep easier and quicker as well.
echo 'mk_add_options MOZ_OBJDIR=@TOPSRCDIR@/../objdir-tb' >> .mozconfig

# configure will be automatically generated using the 'autoconf-2.13'
# command. If autoconf-2.13 isn't the right name for your system, as
# is the case on OS X using MacPorts and on Ubuntu Linux, use the
# real command name as demonstrated below. (Note: it's "autoconf2.13"
# rather than "autoconf213" for Ubuntu 8.04, at least.)
echo 'mk_add_options AUTOCONF=autoconf213' >> .mozconfig

# Now do the build; configure will be run automatically
make -f client.mk build</pre>

=Building the source (first time)=
If you have not previously built the source with the tree you just checked out, you need to do a full compile. Depending on platform and computer specs, this might take a while (Example: MacBook Pro, 2.2Ghz, 2GB ram, ~25-30 Minutes) Go have a beer in between or whatever you prefer :-) This will not be needed as often later on.

If everything went well, the last output won't contain any errors and you are ready to start your development build of Sunbird. If you run into problems, please see the [[Calendar:Build#Troubleshooting|troubleshooting]] section at the bottom of this page.

=Running Lightning=
This section assumes you have a working Thunderbird (3.0 beta2 or later) installed. The best way to add Lightning to Thunderbird is to follow the [http://developer.mozilla.org/en/docs/Building_an_Extension#Test general steps], but for Lightning and Thunderbird. The extension ID for Lightning is <code>{3550f703-e582-4d05-9a08-453d09bdfdc6}</code>. You should use a separate profile for development, to not destroy your normal profile.

The following steps make it easy on Linux, the profile path may be a bit different depending on your system. Remember to replace your profile name. This might also work out in a similar form on Windows and Mac.

<pre>
# Enter the Lightning directory in your object directory
cd $COMM_CENTRAL/../objdir-tb/dist/xpi-stage/lightning

# Create a new profile directory
# This path is only valid for the standard UBUNTU thunderbird
# pwd > ~/.mozilla-thunderbird/<development profile path>/extensions/{3550f703-e582-4d05-9a08-453d09bdfdc6}

# For other distributions, or if you downloaded Thunderbird off ftp.mozilla.org:
pwd > ~/.thunderbird/<development profile path>/extensions/{3550f703-e582-4d05-9a08-453d09bdfdc6}
</pre>

Now you can start thunderbird with your development profile:

<pre>
thunderbird -P <development profile name>
</pre>

This way, when you change code you will always be able to use the latest code, without reinstalling the extension. This profile will automatically contain Lightning.

=Updating Calendar=
If something has changed in calendar code, you will want to get the latest changes. The general documentation suggests you use client.py to get all new changes:

<pre>
# Enter the source directory
cd $COMM_CENTRAL

# Update your local hg repository with the newest changes
python client.py checkout
</pre>

=Building Sunbird and Lightning (after first time)=
After you have done a full build, it is usually not necessary to do the full build again for a while. The only case you might want to do a full build again is if something changed outside of calendar code that seems to affect building calendar (i.e a toolkit change).

==Lightning==
Lightning always needs to be made in one piece, so just issue the following command:

<pre>
# Enter the Lightning directory in your object directory
cd $COMM_CENTRAL/../objdir-tb/calendar/lightning

# Start building
make
</pre>

After this you can start Thunderbird with your development profile, and you should be up to date.

==Sunbird==
Sunbird can be compiled in parts, but its always a good idea to compile the most important parts together:

<pre>
# Enter the object directory
cd $COMM_CENTRAL/../objdir-tb

# Build all general calendar components
make -C calendar

# Build sunbird's components
make -C calendar/sunbird
</pre>

=Debugging and Preferences=
You should set up your debugging environment in the same way you would for extension development. A nice guide can be found [http://developer.mozilla.org/en/docs/Setting_up_extension_development_environment here on developer.mozilla.org].

=Getting started with coding=
This of course depends on what you want to do. Usually, people come to the project since they want something specific fixed. If you are proficient with developing in large projects, you probably know how to get started and can directly start with whatever you wanted to fix. Its always a good idea to see if there is already a bug filed, in case someone else is working on it. If not, go ahead and [https://bugzilla.mozilla.org/enter_bug.cgi?product=Calendar&rep_platform=All&op_sys=All file the bug] and assign it to yourself.

If you don't have much experience with a larger project but do have an idea what you want to fix, then you can take a look at the [[Calendar:Dev_Guide|old dev guide]] or the [[Calendar:Hacking|calendar hacking]] guide. While both are not always up to date, they give some information on the parts of code in calendar.

On the other hand, if you have no idea what to start with but would really like to develop calendar code, you can take a look at the list of [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&product=Calendar&status_whiteboard_type=allwordssubstr&status_whiteboard=good+first+bug&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED good first bugs].

A lot of Calendar code is written in Javascript. This makes it easy to start with development. The user interface consists of XUL, an XML-based user interface language.

Regarding general documentation, you should find everything you need on [http://developer.mozilla.org/ developer.mozilla.org]. Especially interesting are the pages about [http://developer.mozilla.org/en/docs/Extensions Extensions], [http://developer.mozilla.org/en/docs/JavaScript JavaScript] (specifically, the [http://developer.mozilla.org/en/docs/A_re-introduction_to_JavaScript re-introduction to JavaScript]) and [http://developer.mozilla.org/en/docs/XUL XUL] (specifically, the [http://developer.mozilla.org/en/docs/XUL_Tutorial XUL Tutorial]).

If you have calendar-specific questions, you can request help on IRC in #calendar, or in the mozilla.dev.apps.calendar newsgroup. If you have more general Javascript or XUL questions, you can request help on IRC in #developers. Both IRC channels are on irc.mozilla.org

=Creating a Patch=
''General documentation [http://developer.mozilla.org/en/docs/Creating_a_patch here]''.

After you have changed everything you wanted to, you should take a look at the [[Calendar:Style_Guide|Style Guide]], to make sure your code follow the calendar style guidelines we use.

Next, you need to create the patch. The following command can be used to create a patch of all ''changed'' files. Additional commands are needed if you added new files.

<pre>
# Enter the source directory
cd $COMM_CENTRAL

# Create the patch
hg diff > ../my_first_bug.diff
</pre>

If you want to add new files, you will need to add those with the ''hg add'' command. After doing this, you can create the patch as described above.

Now take a final look at the patch if it contains everything you wanted it to contain. You are ready to upload the patch to the bug. If there is no bug for your patch yet, you can [https://bugzilla.mozilla.org/enter_bug.cgi?product=Calendar&rep_platform=All&op_sys=All create one].

You will need to request review from someone specific to make sure your patch is looked at. Take a look at the [[Calendar:Module_Ownership|Module Ownership]] page to find a reviewer. In general you can pick the first reviewer of the module you changed, but to be nice, you should take a look at each reviewer's [https://bugzilla.mozilla.org/request.cgi?action=queue&requester=&product=Calendar&type=review&requestee=&component=&group=requestee Request Queue] to find out who doesn't have too much to do. Note that some reviewers are not active, the module ownership page has the details though.

If you changed UI, its always a good idea to add a screenshot and request ui-review from a ui-reviewer. See also the module ownership page.

The review process usually starts off with a ui-review. It is possible, that the code reviewer will postpone the review until you have ui-review+, in case it is clear that the UI will stay as proposed. In the code review, the reviewer checks if the style fits the [[Calendar:Style_Guide|Style Guide]], and does a general check if the patch works as advertised. To ease review, you should make sure there are no (new) error console warnings or errors, and all tests pass (<code>cd $COMM_CENTRAL/../objdir-tb/calendar; make -C test check</code>).

As soon as you have r+ from all reviewers (r+ means having a positive review, also known as r=''shortname''), you should fix everything that was requested, and upload a new patch. Unless you have Mercurial (hg) access yourself, the reviewer will generally take care of checking in the patch. If that's not the case, or he forgets to do so, you can add the <code>checkin-needed</code> keyword to the bug.

After the patch is checked in and all aspects of the bug are taken care of, the reviewer will resolve the bug as FIXED. The patch will then be available in the next spun nightly. When it is available, it is always a good practice to test the functionality using the original steps to reproduce. If everything works as proposed, you can set the bug as VERIFIED. If any regressions show up, you should file a new bug and set the <code>regression</code> keyword on it.

====Applying a patch====

From time to time, you might need to apply a patch from someone else, or maybe your own patch. This is quite easy, but note that if you plan on applying the patch, making some changes and then want to create a patch that doesn't contain the patch you originally applied, it might be quite a bit harder. This isn't very often the case though. Mercurial (hg) has [[https://developer.mozilla.org/En/Mercurial_Queues an extension called mq]] which is of help in this case.

To apply a patch you need to find out what the path prefix is and match up the -p option. Assuming you or the other person used the process above to create the patch, you can use the following commands to apply the patch

<pre>
cd $MOZILLA/calendar
# --dry-run tests the patching process to ensure that the patch will go
# ahead cleanly. Be sure to run --dry-run at least once before running
# the actual patching process.
patch -p1 -i ~/my_first_bug.diff --dry-run
# Now check if the patch applies cleanly, or you are willing to fix the
# places it went wrong. When you are confident, you can call:
patch -p0 -i ~/my_first_bug.diff

# If the file to patch was not found, take a look at the patch headers. For
# example, if the header contains "+++ themes/winstripe/calendar-views.css",
# then you need to go into the base directory and call again. If the header
# contains "+++ mozilla/calendar/base/Makefile.in", you can use -p2 instead to
# strip the "mozilla/calendar" part.
patch -p2 -i ~/my_first_bug.diff
</pre>

In case you are interested, this is how it would work with mq:
<pre>
cd $COMM_CENTRAL

# Import the diff file into mq. This only needs to be done once.
hg qimport ~/my_first_bug.diff

# Try to load the patch
hg qpush

# If loading fails, then you can remove the patch again:
# hg qpop

# If the patch has rejects, you may resolve them and then refresh the patch:
hg qrefresh
</pre>

If some changes went wrong, patch will create rejects files. To resolve changes, you should open the current file and the rejects file. On large rejects files, you might want to open the rejects file twice so you can see the lines that need to be removed and the lines that need to be added at the same time. Instead you might want to ask the person who created the patch to give you an updated version.

If you want to get rid of all changes at once, you can issue the following command. '''Warning''': This will get rid of all changes to the comm-central tree you have made locally (mail,calendar, ...)

<pre>
# Enter the source directory
cd $COMM_CENTRAL

# Overwrite all local changes
hg update -C
</pre>

=Creating Extensions with the Build System=
If you have gotten this far and want to create an extension for Sunbird or Lightning instead of adding core functionality, it is also easily done. The advantage of this method, is that you don't have to take care of different chrome.manifests for development and deploying and also don't have to take care of zipping together the .xpi file yourself or via a script.

Specifics exceed the scope of this document, but [[Calendar:Creating_an_Extension]] covers this quite well.

=Using directories rather than JARs=
Sometimes it is simpler to develop chrome in a directory. If you choose a JARed structure for releasing, you can still develop with a directory structure by editing your chrome.manifest. For example, calendar.jar in the Lightning extension, rather than having

<pre>
content calendar jar:chrome/calendar.jar!/content/calendar/
</pre>
use
<pre>
content calendar chrome/content/calendar
</pre>

=Troubleshooting=
If you are having trouble, feel free to ask in #calendar on irc.mozilla.org. If you find no help there, try #developers. Do read the [http://developer.mozilla.org/en/docs/Build_Documentation Mozilla documentation] before asking.

==Common Build Errors==
'''Hidden symbols'''
Original Documentation [http://benjamin.smedbergs.us/blog/2005-10-27/gcc-40-workaround/ here]
<pre>
/usr/bin/ld: something.so: hidden symbol `nsSomeClass::SomeFunc(someArg*)' isn't defined
/usr/bin/ld: final link failed: Nonrepresentable section on output
</pre>
This can easily be worked around by adding the following line to your mozconfig

<code>ac_cv_visibility_pragma=no</code>

[[category:calendar|Build]]

Calendar:Build

2009-03-08T08:47:58Z

XFallenAngel: Some updates for the 1.9 tree

[[Calendar:Home_Page|<< Back to Calendar Home Page]]

This guide gives you all the information you need to get started with calendar development. While this guide might be quite long, I assume you will need 20-30 minutes ( + time to build the app) to set up everything and have a running development environment.

Note this guide is written for use directly from the console. There is no known documentation to set up a build environment inside IDE's like eclipse or netbeans. If you manage to set up eclipse for calendar, it would be great if you could contribute documentation!

=Setting up prerequisites=
''General documentation [http://developer.mozilla.org/en/docs/Build_Documentation#Build_requirements here]''

The general section on build prerequisites is quite complete and should be used to determine what is needed.

====Additional, Mac-Specific info====
You should install the latest Xcode. This may be available on your MacOS Tiger restore CD (takes about ten minutes), but a later version is probably available at [[http://developer.apple.com/technology/xcode.html developer.apple.com]].

Next you need to install either Fink or MacPorts. I went with MacPorts. You can download it [http://svn.macosforge.org/repository/macports/downloads/ here]. Installing MacPorts is as simple as running the installer found in the mounted .dmg. (five minutes)

Next, use MacPorts to install libIDL (which also installs GLib). You will need to have your administrative password ready; takes around five to ten minutes, depending on your internet connection.
<pre>
sudo port sync
sudo port install libidl
</pre>

=Getting the source=
There is extensive ''[https://developer.mozilla.org/en/Comm-central_source_code_(Mercurial) documentation]'' on how to get the Calendar source code on [https://developer.mozilla.org developer.mozilla.org].

The source code must be checked out via Mercurial (hg).

In general, you should use a directory for the source code that does not contain spaces or such, i.e on windows "C:\Documents and Settings\MyUsername\My Documents\mozilla" is not a good choice.

Before you start to build, you will need to configure your build environment to build Lightning. Since Lightning is an extension it needs to be built together with its host application Thunderbird.

<pre># Enter the source directory
cd $COMM_CENTRAL (we assume that $COMM_CENTRAL is your source directory here)

# Generate a mozconfig yourself, or use this minimal default one for Thunderbird
echo 'ac_add_options --enable-application=mail' > .mozconfig

# Add calendaring to Thunderbird
echo 'ac_add_options --enable-calendar' >> .mozconfig

# Builds with the object directory the same as the source directory are not
# supported, so set the object directory here. Note: Whether you have the
# object directory within the source directory is up to you. .hgignore includes
# objdir-* and obj-*, making your object directory start with one of them
# will make change finding easier and hg faster, but moving it to outside
# will make things like grep easier and quicker as well.
echo 'mk_add_options MOZ_OBJDIR=@TOPSRCDIR@/../objdir-tb' >> .mozconfig

# configure will be automatically generated using the 'autoconf-2.13'
# command. If autoconf-2.13 isn't the right name for your system, as
# is the case on OS X using MacPorts and on Ubuntu Linux, use the
# real command name as demonstrated below. (Note: it's "autoconf2.13"
# rather than "autoconf213" for Ubuntu 8.04, at least.)
echo 'mk_add_options AUTOCONF=autoconf213' >> .mozconfig

# Now do the build; configure will be run automatically
make -f client.mk build</pre>

=Building the source (first time)=
If you have not previously built the source with the tree you just checked out, you need to do a full compile. Depending on platform and computer specs, this might take a while (Example: MacBook Pro, 2.2Ghz, 2GB ram, ~25-30 Minutes) Go have a beer in between or whatever you prefer :-) This will not be needed as often later on.

If everything went well, the last output won't contain any errors and you are ready to start your development build of Sunbird. If you run into problems, please see the [[Calendar:Build#Troubleshooting|troubleshooting]] section at the bottom of this page.

=Running Lightning=
This section assumes you have a working Thunderbird (3.0 beta2 or later) installed. The best way to add Lightning to Thunderbird is to follow the [http://developer.mozilla.org/en/docs/Building_an_Extension#Test general steps], but for Lightning and Thunderbird. The extension ID for Lightning is <code>{3550f703-e582-4d05-9a08-453d09bdfdc6}</code>. You should use a separate profile for development, to not destroy your normal profile.

The following steps make it easy on Linux, the profile path may be a bit different depending on your system. Remember to replace your profile name. This might also work out in a similar form on Windows and Mac.

<pre>
# Enter the Lightning directory in your object directory
cd $COMM_CENTRAL/../objdir-tb/dist/xpi-stage/lightning

# Create a new profile directory
# This path is only valid for the standard UBUNTU thunderbird
# pwd > ~/.mozilla-thunderbird/<development profile path>/extensions/{3550f703-e582-4d05-9a08-453d09bdfdc6}

# For other distributions, or if you downloaded Thunderbird off ftp.mozilla.org:
pwd > ~/.thunderbird/<development profile path>/extensions/{3550f703-e582-4d05-9a08-453d09bdfdc6}
</pre>

Now you can start thunderbird with your development profile:

<pre>
thunderbird -P <development profile name>
</pre>

This way, when you change code you will always be able to use the latest code, without reinstalling the extension. This profile will automatically contain Lightning.

=Updating Calendar=
If something has changed in calendar code, you will want to get the latest changes. The general documentation suggests you use client.py to get all new changes:

<pre>
# Enter the source directory
cd $COMM_CENTRAL

# Update your local hg repository with the newest changes
python client.py checkout
</pre>

=Building Sunbird and Lightning (after first time)=
After you have done a full build, it is usually not necessary to do the full build again for a while. The only case you might want to do a full build again is if something changed outside of calendar code that seems to affect building calendar (i.e a toolkit change).

==Lightning==
Lightning always needs to be made in one piece, so just issue the following command:

<pre>
# Enter the Lightning directory in your object directory
cd $COMM_CENTRAL/../objdir-tb/calendar/lightning

# Start building
make
</pre>

After this you can start Thunderbird with your development profile, and you should be up to date.

==Sunbird==
Sunbird can be compiled in parts, but its always a good idea to compile the most important parts together:

<pre>
# Enter the object directory
cd $COMM_CENTRAL/../objdir-tb

# Build all general calendar components
make -C calendar

# Build sunbird's components
make -C calendar/sunbird
</pre>

=Debugging and Preferences=
You should set up your debugging environment in the same way you would for extension development. A nice guide can be found [http://developer.mozilla.org/en/docs/Setting_up_extension_development_environment here on developer.mozilla.org].

=Getting started with coding=
This of course depends on what you want to do. Usually, people come to the project since they want something specific fixed. If you are proficient with developing in large projects, you probably know how to get started and can directly start with whatever you wanted to fix. Its always a good idea to see if there is already a bug filed, in case someone else is working on it. If not, go ahead and [https://bugzilla.mozilla.org/enter_bug.cgi?product=Calendar&rep_platform=All&op_sys=All file the bug] and assign it to yourself.

If you don't have much experience with a larger project but do have an idea what you want to fix, then you can take a look at the [[Calendar:Dev_Guide|old dev guide]] or the [[Calendar:Hacking|calendar hacking]] guide. While both are not always up to date, they give some information on the parts of code in calendar.

On the other hand, if you have no idea what to start with but would really like to develop calendar code, you can take a look at the list of [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&product=Calendar&status_whiteboard_type=allwordssubstr&status_whiteboard=good+first+bug&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED good first bugs].

A lot of Calendar code is written in Javascript. This makes it easy to start with development. The user interface consists of XUL, an XML-based user interface language.

Regarding general documentation, you should find everything you need on [http://developer.mozilla.org/ developer.mozilla.org]. Especially interesting are the pages about [http://developer.mozilla.org/en/docs/Extensions Extensions], [http://developer.mozilla.org/en/docs/JavaScript JavaScript] (specifically, the [http://developer.mozilla.org/en/docs/A_re-introduction_to_JavaScript re-introduction to JavaScript]) and [http://developer.mozilla.org/en/docs/XUL XUL] (specifically, the [http://developer.mozilla.org/en/docs/XUL_Tutorial XUL Tutorial]).

If you have calendar-specific questions, you can request help on IRC in #calendar, or in the mozilla.dev.apps.calendar newsgroup. If you have more general Javascript or XUL questions, you can request help on IRC in #developers. Both IRC channels are on irc.mozilla.org

=Creating a Patch=
''General documentation [http://developer.mozilla.org/en/docs/Creating_a_patch here]''.

After you have changed everything you wanted to, you should take a look at the [[Calendar:Style_Guide|Style Guide]], to make sure your code follow the calendar style guidelines we use.

Next, you need to create the patch. The following command can be used to create a patch of all ''changed'' files. Additional commands are needed if you added new files.

<pre>
# Enter the source directory
cd $COMM_CENTRAL

# Create the patch
hg diff > ../my_first_bug.diff
</pre>

If you want to add new files, you will need to add those with the ''hg add'' command. After doing this, you can create the patch as described above.

Now take a final look at the patch if it contains everything you wanted it to contain. You are ready to upload the patch to the bug. If there is no bug for your patch yet, you can [https://bugzilla.mozilla.org/enter_bug.cgi?product=Calendar&rep_platform=All&op_sys=All create one].

You will need to request review from someone specific to make sure your patch is looked at. Take a look at the [[Calendar:Module_Ownership|Module Ownership]] page to find a reviewer. In general you can pick the first reviewer of the module you changed, but to be nice, you should take a look at each reviewer's [https://bugzilla.mozilla.org/request.cgi?action=queue&requester=&product=Calendar&type=review&requestee=&component=&group=requestee Request Queue] to find out who doesn't have too much to do. Note that some reviewers are not active, the module ownership page has the details though.

If you changed UI, its always a good idea to add a screenshot and request ui-review from a ui-reviewer. See also the module ownership page.

The review process usually starts off with a ui-review. It is possible, that the code reviewer will postpone the review until you have ui-review+, in case it is clear that the UI will stay as proposed. In the code review, the reviewer checks if the style fits the [[Calendar:Style_Guide|Style Guide]], and does a general check if the patch works as advertised. To ease review, you should make sure there are no (new) error console warnings or errors, and all tests pass (<code>cd $COMM_CENTRAL/../objdir-tb/calendar; make -C test check</code>).

As soon as you have r+ from all reviewers (r+ means having a positive review, also known as r=''shortname''), you should fix everything that was requested, and upload a new patch. Unless you have Mercurial (hg) access yourself, the reviewer will generally take care of checking in the patch. If that's not the case, or he forgets to do so, you can add the <code>checkin-needed</code> keyword to the bug.

After the patch is checked in and all aspects of the bug are taken care of, the reviewer will resolve the bug as FIXED. The patch will then be available in the next spun nightly. When it is available, it is always a good practice to test the functionality using the original steps to reproduce. If everything works as proposed, you can set the bug as VERIFIED. If any regressions show up, you should file a new bug and set the <code>regression</code> keyword on it.

====Applying a patch====

From time to time, you might need to apply a patch from someone else, or maybe your own patch. This is quite easy, but note that if you plan on applying the patch, making some changes and then want to create a patch that doesn't contain the patch you originally applied, it might be quite a bit harder. This isn't very often the case though. Mercurial (hg) has [[https://developer.mozilla.org/En/Mercurial_Queues an extension called mq]] which is of help in this case.

To apply a patch you need to find out what the path prefix is and match up the -p option. Assuming you or the other person used the process above to create the patch, you can use the following commands to apply the patch

<pre>
cd $MOZILLA/calendar
# --dry-run tests the patching process to ensure that the patch will go
# ahead cleanly. Be sure to run --dry-run at least once before running
# the actual patching process.
patch -p1 -i ~/my_first_bug.diff --dry-run
# Now check if the patch applies cleanly, or you are willing to fix the
# places it went wrong. When you are confident, you can call:
patch -p0 -i ~/my_first_bug.diff

# If the file to patch was not found, take a look at the patch headers. For
# example, if the header contains "+++ themes/winstripe/calendar-views.css",
# then you need to go into the base directory and call again. If the header
# contains "+++ mozilla/calendar/base/Makefile.in", you can use -p2 instead to
# strip the "mozilla/calendar" part.
patch -p2 -i ~/my_first_bug.diff
</pre>

In case you are interested, this is how it would work with mq:
<pre>
cd $COMM_CENTRAL

# Import the diff file into mq. This only needs to be done once.
hg qimport ~/my_first_bug.diff

# Try to load the patch
hg qpush

# If loading fails, then you can remove the patch again:
# hg qpop

# If the patch has rejects, you may resolve them and then refresh the patch:
hg qrefresh
</pre>

If some changes went wrong, patch will create rejects files. To resolve changes, you should open the current file and the rejects file. On large rejects files, you might want to open the rejects file twice so you can see the lines that need to be removed and the lines that need to be added at the same time. Instead you might want to ask the person who created the patch to give you an updated version.

If you want to get rid of all changes at once, you can issue the following command. '''Warning''': This will get rid of all changes to the comm-central tree you have made locally (mail,calendar, ...)

<pre>
# Enter the source directory
cd $COMM_CENTRAL

# Overwrite all local changes
hg update -C
</pre>

=Creating Extensions with the Build System=
If you have gotten this far and want to create an extension for Sunbird or Lightning instead of adding core functionality, it is also easily done. The advantage of this method, is that you don't have to take care of different chrome.manifests for development and deploying and also don't have to take care of zipping together the .xpi file yourself or via a script.

Specifics exceed the scope of this document, but [[Calendar:Creating_an_Extension]] covers this quite well.

=Using directories rather than JARs=
Sometimes it is simpler to develop chrome in a directory. If you choose a JARed structure for releasing, you can still develop with a directory structure by editing your chrome.manifest. For example, calendar.jar in the Lightning extension, rather than having

<pre>
content calendar jar:chrome/calendar.jar!/content/calendar/
</pre>
use
<pre>
content calendar chrome/content/calendar
</pre>

=Troubleshooting=
If you are having trouble, feel free to ask in #calendar on irc.mozilla.org. If you find no help there, try #developers. Do read the [http://developer.mozilla.org/en/docs/Build_Documentation Mozilla documentation] before asking.

==Common Build Errors==
'''Hidden symbols'''
Original Documentation [http://benjamin.smedbergs.us/blog/2005-10-27/gcc-40-workaround/ here]
<pre>
/usr/bin/ld: something.so: hidden symbol `nsSomeClass::SomeFunc(someArg*)' isn't defined
/usr/bin/ld: final link failed: Nonrepresentable section on output
</pre>
This can easily be worked around by adding the following line to your mozconfig

<code>ac_cv_visibility_pragma=no</code>

[[category:calendar|Build]]

Calendar:Build 1.8

2009-03-08T08:28:11Z

XFallenAngel: Restore to 1.8 version

[[Calendar:Home_Page|<< Back to Calendar Home Page]]

{{Warning|This page describes how to build the Calendar Project with the Mozilla 1.8 codebase. This corresponds to Sunbird/Lightning 0.9. Instructions on how to build later versions can be found [[Calendar:Build|here]]}}

This guide gives you all the information you need to get started with calendar development. While this guide might be quite long, I assume you will need 20-30 minutes ( + time to build the app) to set up everything and have a running development environment.

Note this guide is written for use directly from the console. There is no known documentation to set up a build environment inside IDE's like eclipse. If you manage to set up eclipse for calendar, it would be great if you could contribute documentation!

=Setting up prerequisites=
''General documentation [http://developer.mozilla.org/en/docs/Build_Documentation#Build_requirements here]''

The general section on build prerequisites is quite complete and should be used to determine what is needed.

====Additional, Mac-Specific info====
You should install Xcode (i.e 2.4.1). This may be available on your MacOS Tiger restore CD (takes about ten minutes)

Next you need to install either Fink or MacPorts. I went with MacPorts. You can download it [http://svn.macosforge.org/repository/macports/downloads/MacPorts-1.5.0/ here]. Installing MacPorts is as simple as running the installer found in the mounted .dmg. (five minutes)

Next, use MacPorts to install libIDL (which also installs GLib). You will need to have your administrative password ready; takes around five to ten minutes, depending on your internet connection.
<pre>
sudo port sync
sudo port install libidl
</pre>

=Getting the source=
''General documentation [http://developer.mozilla.org/en/docs/Mozilla_Source_Code_(CVS) here]''

Source code should be checked out via CVS. To do so you should first create your mozconfig. This is an example mozconfig for calendar which can be used:

<pre>
mk_add_options MOZ_OBJDIR=@TOPSRCDIR@/obj-@CONFIG_GUESS@
mk_add_options MOZ_CO_PROJECT=calendar # We want to checkout calendar
mk_add_options MOZ_CO_USE_MIRROR=1 # use cvs-mirror
# mk_add_options MOZ_CO_LOCALES=de # Can be used to also checkout a language
# mk_add_options MOZ_MAKE_FLAGS="-j3" # Can be used if you have multiple processors
mk_add_options JS_READLINE=1

# ac_add_options --with-macos-sdk=/Developer/SDKs/MacOSX10.4u.sdk # Needed on MAC
ac_add_options --enable-application=calendar # We want to build calendar
ac_add_options --disable-installer # Installer not needed for development
ac_add_options --disable-airbag # I have had problems with airbag in the past
ac_add_options --disable-crashreporter # (Optional) Disable if you don't want it
ac_add_options --enable-debugger-info-modules=yes # More debug info
# ac_add_options --enable-debug # (Optional) Lots of debugging. Maybe more than you actually want!
ac_add_options --enable-extensions=default,lightning,inspector,venkman # Some extensions in the /extensions directory
ac_add_options --enable-tests # You should enable tests to make sure everything works before posting a patch
# ac_add_options --enable-system-cairo # I needed this on linux

# The following options can be used to reduce/disable debugging.
# ac_add_options --enable-optimize
# ac_add_options --disable-static --enable-shared
# ac_add_options --disable-debug
</pre>
Save this file to your home directory to a file called ".mozconfig".

Now you can start checking out code. Use the following commands for the initial checkout. Do this in a folder where you want to have your tree. In general, you should use a directory that does not contain spaces or such, i.e on windows "C:\Documents and Settings\MyUsername\My Documents\mozilla" is not a good choice.

'''A note about versioning''': While with other projects like Firefox, TRUNK is the latest and greatest, calendar code is commited to both MOZILLA_1_8_BRANCH and TRUNK. This means the only differing factor is the mozilla codebase. We are currently releasing from the more stable MOZILLA_1_8_BRANCH, so you should also develop on this branch.

To clarify, Calendar version 0.8 is MOZILLA_1_8_BRANCH, while Calendar 0.6a1 is TRUNK.

<pre>
cvs -d :pserver:anonymous@cvs-mirror.mozilla.org:/cvsroot co -r MOZILLA_1_8_BRANCH mozilla/client.mk
cd mozilla
make -f client.mk checkout
</pre>

=Building the source (first time)=
If you have not previously built the source with the tree you just checked out, you need to do a full compile. Depending on platform and computer specs, this might take a while (Example: MacBook Pro, 2.2Ghz, 2GB ram, ~25-30 Minutes) Go have a beer in between or whatever you prefer :-) This will not be needed as often later on.

Assuming you are still in the mozilla directory you changed to above, now issue the following command:
<pre>
make -f client.mk build
</pre>
This will build everything needed for calendar. If everything went well, the last output won't contain any errors and you are ready to start your development build of sunbird. If you run into problems, please see the [[Calendar:Build#Troubleshooting|troubleshooting]] section at the bottom of this page.

=Running Sunbird=
You will find the binary to start Sunbird under the following paths. I assume <code>$MOZILLA</code> is the mozilla directory you changed to above. The <code>obj-</code> part may vary depending on platform, build system, and number of bits. The path on Mac also differs (i.e CalendarDebug.app) if you use <code>--enable-debug</code>

<pre>
# Windows
$MOZILLA/obj-i686-pc-cygwin/dist/bin/sunbird.exe
# Linux/Solaris
$MOZILLA/obj-i686-pc-linux-gnu/dist/bin/sunbird
# Mac
$MOZILLA/obj-i386-apple-darwin9.2.2/dist/Calendar.app/Contents/MacOS/sunbird
</pre>

Some interesting command line switches:
<pre>
-g (Mac,Linux) Start using gdb as a debugger
-P <profile> Start using a specific profile.
Leave out <profile> to start the profile manager.
-console (Windows) Open a console for debug messages
</pre>

=Running Lightning=
This section assumes you have a working thunderbird (2.0.0.*) installed. The best way to add Lightning to Thunderbird is to follow the [http://developer.mozilla.org/en/docs/Building_an_Extension#Test general steps], but for Lightning and Thunderbird. The id for Lightning is <code>{3550f703-e582-4d05-9a08-453d09bdfdc6}</code>. You should use a separate profile for development, to not destroy your normal profile.

The following steps make it easy on Linux, the profile path may be a bit different depending on your system. Remember to replace your profile name. This might also work out in a similar form on Windows and Mac.
<pre>
cd $MOZILLA/obj-*/dist/xpi-stage/lightning
pwd > ~/.mozilla-thunderbird/<development profile path>/extensions/{3550f703-e582-4d05-9a08-453d09bdfdc6}
</pre>

Now you can start thunderbird with your development profile.
<pre>
thunderbird -P <development profile name>
</pre>

This way, when you change code you will always be able to use the latest code, without reinstalling the extension.

=Updating Calendar=
If something has changed in calendar code, you will want to get the latest changes. The general documentation suggests you use client.mk to checkout all changes:

<pre>
cd $MOZILLA
cvs up -A -r MOZILLA_1_8_BRANCH client.mk
make -f client.mk checkout
</pre>

Fortunately, this is not needed very often, especially on MOZILLA_1_8_BRANCH. All you need to do is update the calendar directory. This is '''much''' faster than doing a full checkout.

<pre>
cd $MOZILLA/calendar
cvs up
</pre>

Go ahead and do the partial checkouts as long as you are able to compile calendar successfully. If you cannot the program to compile and you think it might have to do with other parts of mozilla (i.e toolkit), you can do a full update and compile.

=Building Sunbird and Lightning (after first time)=
After you have done a full build, it is usually not necessary to do the full build again for a while. The only case you might want to do a full build again is if something changed outside of calendar code that seems to affect building calendar (i.e a toolkit change).

==Sunbird==
Sunbird is usually much faster to compile, since you can selectively build parts of calendar, depending on what changed:

<pre>
cd $MOZILLA/obj-*/calendar

# The following command makes a full sunbird.
make && make -C sunbird

# If you didn't change anything in the calendar/sunbird directory
make

# If you only changed things in base/content or base/themes or prototypes/wcap
make -C base chrome

# If you only changed things in base, but the above doesn't seem to be enough:
make -C base
</pre>

'''Warning''': Especially if you make chrome, be sure that you don't have sunbird running. You may override your .jar files. If this happens, go into the top-level object directory and type make. This will remake all .jar files for the whole product (i.e including toolkit)

==Lightning==
Lightning always needs to be made in one piece, so just issue the following command:

<pre>
cd $MOZILLA/obj-*/calendar/lightning
make
</pre>

After this you can start thunderbird with your development profile, and you should be up to date.

=Debugging and Preferences=
You should set up your debugging environment in the same way you would for extension development. A nice guide can be found [http://developer.mozilla.org/en/docs/Setting_up_extension_development_environment here].

=Getting started with coding=
This of course depends on what you want to do. Usually, people come to the project since they want something specific fixed. If you are proficient with developing in large projects, you probably know how to get started and can directly start with whatever you wanted to fix. Its always a good idea to see if there is already a bug filed, in case someone else is working on it. If not, go ahead and [https://bugzilla.mozilla.org/enter_bug.cgi?product=Calendar&rep_platform=All&op_sys=All file the bug] and assign it to yourself.

If you don't have much experience with a larger project but do have an idea what you want to fix, then you can take a look at the [[Calendar:Dev_Guide|old dev guide]] or the [[Calendar:Hacking|calendar hacking]] guide. While both are not always up to date, they give some information on the parts of code in calendar.

On the other hand, if you have no idea what to start with but would really like to develop calendar code, you can take a look at the list of [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&product=Calendar&status_whiteboard_type=allwordssubstr&status_whiteboard=good+first+bug&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED good first bugs].

A lot of Calendar code is written in Javascript. This makes it easy to start with development. The user interface consists of XUL, an XML-based user interface language.

Regarding general documentation, you should find everything you need on [http://developer.mozilla.org/ developer.mozilla.org]. Especially interesting are the pages about [http://developer.mozilla.org/en/docs/Extensions Extensions], [http://developer.mozilla.org/en/docs/JavaScript JavaScript] (specifically, the [http://developer.mozilla.org/en/docs/A_re-introduction_to_JavaScript re-introduction to JavaScript]) and [http://developer.mozilla.org/en/docs/XUL XUL] (specifically, the [http://developer.mozilla.org/en/docs/XUL_Tutorial XUL Tutorial]).

If you have calendar-specific questions, you can request help on IRC in #calendar, or in the mozilla.dev.apps.calendar newsgroup. If you have more general Javascript or XUL questions, you can request help on IRC in #developers. Both IRC channels are on irc.mozilla.org

=Creating a Patch=
''General documentation [http://developer.mozilla.org/en/docs/Creating_a_patch here]''.

After you have changed everything you wanted to, you should take a look at the [[Calendar:Style_Guide|Style Guide]], to make sure your code follow the calendar style guidelines we use.

Next, you need to create the patch. The following command can be used to create a patch of all ''changed'' files. Additional commands are needed if you added new files. If possible, you should always do the diff inside the <code>$MOZILLA/calendar</code> directory, so its easy to apply the patch.

<pre>
cd $MOZILLA/calendar
cvs diff -u -U8 -p > ~/my_first_bug.diff

# To add a single new file to the patch
diff -upN /dev/null base/content/path/to/file >> ~/my_first_bug.diff

# To add all new files to the patch (advanced)
for i in `cvs -n up 2>/dev/null | grep '^?' | awk '{print $2}'`; do diff -upN /dev/null $i >> ~/my_first_bug.diff; done
</pre>

Now take a final look at the patch if it contains everything you wanted it to contain. You are ready to upload the patch to the bug. If there is no bug for your patch yet, you can [https://bugzilla.mozilla.org/enter_bug.cgi?product=Calendar&rep_platform=All&op_sys=All create one].

You will need to request review from someone specific to make sure your patch is looked at. Take a look at the [[Calendar:Module_Ownership|Module Ownership]] page to find a reviewer. In general you can pick the first reviewer of the module you changed, but to be nice, you should take a look at each reviewer's [https://bugzilla.mozilla.org/request.cgi?action=queue&requester=&product=Calendar&type=review&requestee=&component=&group=requestee Request Queue] to find out who doesn't have too much to do. Note that some reviewers are not active, the module ownership page has the details though.

If you changed UI, its always a good idea to add a screenshot and request ui-review from a ui-reviewer. See also the module ownership page.

The review process usually starts off with a ui-review. It is possible, that the code reviewer will postpone the review until you have ui-review+, in case it is clear that the UI will stay as proposed. In the code review, the reviewer checks if the style fits the [[Calendar:Style_Guide|Style Guide]], and does a general check if the patch works as advertised. To ease review, you should make sure there are no (new) error console warnings or errors, and all tests pass (<code>cd $MOZILLA/obj*/calendar; make -C test check</code>).

As soon as you have r+ from all reviewers (r+ means having a positive review, also known as r=''shortname''), you should fix everything that was requested, and upload a new patch. Unless you have CVS access yourself, the reviewer will generally take care of checking in the patch. If thats not the case, or he forgets to do so, you can add the <code>checkin-needed</code> keyword to the bug.

After the patch is checked in and all aspects of the bug are taken care of, the reviewer will resolve the bug as FIXED. The patch will then be available in the next spun nightly. When it is available, it is always a good practice to test the functionality using the original steps to reproduce. If everything works as proposed, you can set the bug as VERIFIED. If any regressions show up, you should file a new bug and set the <code>regression</code> keyword on it.

====Applying a patch====
From time to time, you might need to apply a patch from someone else, or maybe your own patch. This is quite easy, but note that if you plan on applying the patch, making some changes and then want to create a patch that doesn't contain the patch you originally applied, it might be quite a bit harder. This isn't very often the case though.

To apply a patch you need to find out what the path prefix is and match up the -p option. Assuming you or the other person used the process above to create the patch, you can use the following commands to apply the patch

<pre>
cd $MOZILLA/calendar
# --dry-run tests the patching process to ensure that the patch will go
# ahead cleanly. Be sure to run --dry-run at least once before running
# the actual patching process.
patch -p0 -i ~/my_first_bug.diff --dry-run
# Now check if the patch applies cleanly, or you are willing to fix the
# places it went wrong. When you are confident, you can call:
patch -p0 -i ~/my_first_bug.diff

# If the file to patch was not found, take a look at the patch headers. For
# example, if the header contains "+++ themes/winstripe/calendar-views.css",
# then you need to go into the base directory and call again. If the header
# contains "+++ mozilla/calendar/base/Makefile.in", you can use -p2 instead to
# strip the "mozilla/calendar" part.
patch -p2 -i ~/my_first_bug.diff
</pre>

If some changes went wrong, patch will create rejects files. To resolve changes, you should open the original file and the rejects file. On large rejects files, you might want to open the rejects file twice so you can see the lines that need to be removed and the lines that need to be added at the same time.

If you want to get rid of all changes at once, you can issue the following command. If there are cvs conflicts, you might have to remove the files marked with "C ...", and then issue the command again. '''Warning''': This will get rid of all changes to the calendar tree you have made.

<pre>
cd $MOZILLA/calendar
cvs up -C
</pre>

=Creating Extensions with the Build System=
If you have gotten this far and want to create an extension for Sunbird or Lightning instead of adding core functionality, it is also easily done. The advantage of this method, is that you don't have to take care of different chrome.manifests for development and deploying and also don't have to take care of zipping together the .xpi file yourself or via a script.

Specifics exceed the scope of this document, but [[Calendar:Creating_an_Extension]] covers this quite well.

=Using directories rather than JARs=
Sometimes it is simpler to develop chrome in a directory. If you choose a JARed structure for releasing, you can still develop with a directory structure by editing your chrome.manifest. For example, calendar.jar in the Lightning extension, rather than having

<pre>
content calendar jar:chrome/calendar.jar!/content/calendar/
</pre>
use
<pre>
content calendar chrome/content/calendar
</pre>

=Troubleshooting=
If you are having trouble, feel free to ask in #calendar on irc.mozilla.org. If you find no help there, try #developers. Do read the [http://developer.mozilla.org/en/docs/Build_Documentation Mozilla documentation] before asking.

==Common Build Errors==
'''Hidden symbols'''
Original Documentation [http://benjamin.smedbergs.us/blog/2005-10-27/gcc-40-workaround/ here]
<pre>
/usr/bin/ld: something.so: hidden symbol `nsSomeClass::SomeFunc(someArg*)' isn't defined
/usr/bin/ld: final link failed: Nonrepresentable section on output
</pre>
This can easily be worked around by adding the following line to your mozconfig

<code>ac_cv_visibility_pragma=no</code>

[[category:calendar|Build]]

Calendar:Build 1.8

2009-03-08T08:21:54Z

XFallenAngel: New page: << Back to Calendar Home Page {{Warning|This page describes how to build the Calendar Project with the Mozilla 1.8 codebase. This corresponds to Sunb...

[[Calendar:Home_Page|<< Back to Calendar Home Page]]

{{Warning|This page describes how to build the Calendar Project with the Mozilla 1.8 codebase. This corresponds to Sunbird/Lightning 0.9. Instructions on how to build later versions can be found [[Calendar:Build|here]]}}

This guide gives you all the information you need to get started with calendar development. While this guide might be quite long, I assume you will need 20-30 minutes ( + time to build the app) to set up everything and have a running development environment.

Note this guide is written for use directly from the console. There is no known documentation to set up a build environment inside IDE's like eclipse. If you manage to set up eclipse for calendar, it would be great if you could contribute documentation!

=Setting up prerequisites=
''General documentation [http://developer.mozilla.org/en/docs/Build_Documentation#Build_requirements here]''

The general section on build prerequisites is quite complete and should be used to determine what is needed.

====Additional, Mac-Specific info====
You should install Xcode (i.e 2.4.1). This may be available on your MacOS Tiger restore CD (takes about ten minutes)

Next you need to install either Fink or MacPorts. I went with MacPorts. You can download it [http://svn.macosforge.org/repository/macports/downloads/MacPorts-1.5.0/ here]. Installing MacPorts is as simple as running the installer found in the mounted .dmg. (five minutes)

Next, use MacPorts to install libIDL (which also installs GLib). You will need to have your administrative password ready; takes around five to ten minutes, depending on your internet connection.
<pre>
sudo port sync
sudo port install libidl
</pre>

=Getting the source=
There is extensive ''[https://developer.mozilla.org/en/Comm-central_source_code_(Mercurial) documentation]'' on how to get the Calendar source code on [https://developer.mozilla.org developer.mozilla.org].

The source code must be checked out via Mercurial (hg).

In general, you should use a directory for the source code that does not contain spaces or such, i.e on windows "C:\Documents and Settings\MyUsername\My Documents\mozilla" is not a good choice.

Before you start to build, you will need to configure your build environment to build Lightning. Since Lightning is an extension it needs to be built together with its host application Thunderbird.

<pre># Enter the source directory
cd src (we assume that src/ is your source directory here)

# Generate a mozconfig yourself, or use this minimal default one for Thunderbird
echo 'ac_add_options --enable-application=mail' > .mozconfig

# Add calendaring to Thunderbird
echo 'ac_add_options --enable-calendar' >> .mozconfig

# Builds with the object directory the same as the source directory are not
# supported, so set the object directory here. Note: Whether you have the
# object directory within the source directory is up to you. .hgignore includes
# objdir-* and obj-*, making your object directory start with one of them
# will make change finding easier and hg faster, but moving it to outside
# will make things like grep easier and quicker as well.
echo 'mk_add_options MOZ_OBJDIR=@TOPSRCDIR@/../objdir-tb' >> .mozconfig

# configure will be automatically generated using the 'autoconf-2.13'
# command. If autoconf-2.13 isn't the right name for your system, as
# is the case on OS X using MacPorts and on Ubuntu Linux, use the
# real command name as demonstrated below. (Note: it's "autoconf2.13"
# rather than "autoconf213" for Ubuntu 8.04, at least.)
echo 'mk_add_options AUTOCONF=autoconf213' >> .mozconfig

# Now do the build; configure will be run automatically
make -f client.mk build</pre>

=Building the source (first time)=
If you have not previously built the source with the tree you just checked out, you need to do a full compile. Depending on platform and computer specs, this might take a while (Example: MacBook Pro, 2.2Ghz, 2GB ram, ~25-30 Minutes) Go have a beer in between or whatever you prefer :-) This will not be needed as often later on.

If everything went well, the last output won't contain any errors and you are ready to start your development build of sunbird. If you run into problems, please see the [[Calendar:Build#Troubleshooting|troubleshooting]] section at the bottom of this page.

=Running Lightning=
This section assumes you have a working Thunderbird (3.0 beta2 or later) installed. The best way to add Lightning to Thunderbird is to follow the [http://developer.mozilla.org/en/docs/Building_an_Extension#Test general steps], but for Lightning and Thunderbird. The extension ID for Lightning is <code>{3550f703-e582-4d05-9a08-453d09bdfdc6}</code>. You should use a separate profile for development, to not destroy your normal profile.

The following steps make it easy on Linux, the profile path may be a bit different depending on your system. Remember to replace your profile name. This might also work out in a similar form on Windows and Mac.

<pre>
# Enter the Lightning directory in your object directory
cd @TOPSRCDIR@/../objdir-tb/dist/xpi-stage/lightning

# Create a new profile directory
pwd > ~/.mozilla-thunderbird/<development profile path>/extensions/{3550f703-e582-4d05-9a08-453d09bdfdc6}
</pre>

Now you can start thunderbird with your development profile.

<pre>
thunderbird -P <development profile name>
</pre>

This way, when you change code you will always be able to use the latest code, without reinstalling the extension.

=Updating Calendar=
If something has changed in calendar code, you will want to get the latest changes. The general documentation suggests you use client.py to get all new changes:

<pre>
# Enter the source directory
cd src

# Update your local hg repository with the newest changes
python client.py checkout
</pre>

=Building Sunbird and Lightning (after first time)=
After you have done a full build, it is usually not necessary to do the full build again for a while. The only case you might want to do a full build again is if something changed outside of calendar code that seems to affect building calendar (i.e a toolkit change).

==Lightning==
Lightning always needs to be made in one piece, so just issue the following command:

<pre>
# Enter the Lightning source directory in your object directory
cd @TOPSRCDIR@/../objdir-tb/calendar/lightning

# Start building
make
</pre>

After this you can start thunderbird with your development profile, and you should be up to date.

=Debugging and Preferences=
You should set up your debugging environment in the same way you would for extension development. A nice guide can be found [http://developer.mozilla.org/en/docs/Setting_up_extension_development_environment here on developer.mozilla.org].

=Getting started with coding=
This of course depends on what you want to do. Usually, people come to the project since they want something specific fixed. If you are proficient with developing in large projects, you probably know how to get started and can directly start with whatever you wanted to fix. Its always a good idea to see if there is already a bug filed, in case someone else is working on it. If not, go ahead and [https://bugzilla.mozilla.org/enter_bug.cgi?product=Calendar&rep_platform=All&op_sys=All file the bug] and assign it to yourself.

If you don't have much experience with a larger project but do have an idea what you want to fix, then you can take a look at the [[Calendar:Dev_Guide|old dev guide]] or the [[Calendar:Hacking|calendar hacking]] guide. While both are not always up to date, they give some information on the parts of code in calendar.

On the other hand, if you have no idea what to start with but would really like to develop calendar code, you can take a look at the list of [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&product=Calendar&status_whiteboard_type=allwordssubstr&status_whiteboard=good+first+bug&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED good first bugs].

A lot of Calendar code is written in Javascript. This makes it easy to start with development. The user interface consists of XUL, an XML-based user interface language.

Regarding general documentation, you should find everything you need on [http://developer.mozilla.org/ developer.mozilla.org]. Especially interesting are the pages about [http://developer.mozilla.org/en/docs/Extensions Extensions], [http://developer.mozilla.org/en/docs/JavaScript JavaScript] (specifically, the [http://developer.mozilla.org/en/docs/A_re-introduction_to_JavaScript re-introduction to JavaScript]) and [http://developer.mozilla.org/en/docs/XUL XUL] (specifically, the [http://developer.mozilla.org/en/docs/XUL_Tutorial XUL Tutorial]).

If you have calendar-specific questions, you can request help on IRC in #calendar, or in the mozilla.dev.apps.calendar newsgroup. If you have more general Javascript or XUL questions, you can request help on IRC in #developers. Both IRC channels are on irc.mozilla.org

=Creating a Patch=
''General documentation [http://developer.mozilla.org/en/docs/Creating_a_patch here]''.

After you have changed everything you wanted to, you should take a look at the [[Calendar:Style_Guide|Style Guide]], to make sure your code follow the calendar style guidelines we use.

Next, you need to create the patch. The following command can be used to create a patch of all ''changed'' files. Additional commands are needed if you added new files.

<pre>
# Enter the source directory
cd src

# Create the patch
hg diff >c:\my_first_bug.diff
</pre>

If you want to add new files, you will need to add those with the ''hg add'' command. After doing this, you can create the patch as described above.

Now take a final look at the patch if it contains everything you wanted it to contain. You are ready to upload the patch to the bug. If there is no bug for your patch yet, you can [https://bugzilla.mozilla.org/enter_bug.cgi?product=Calendar&rep_platform=All&op_sys=All create one].

You will need to request review from someone specific to make sure your patch is looked at. Take a look at the [[Calendar:Module_Ownership|Module Ownership]] page to find a reviewer. In general you can pick the first reviewer of the module you changed, but to be nice, you should take a look at each reviewer's [https://bugzilla.mozilla.org/request.cgi?action=queue&requester=&product=Calendar&type=review&requestee=&component=&group=requestee Request Queue] to find out who doesn't have too much to do. Note that some reviewers are not active, the module ownership page has the details though.

If you changed UI, its always a good idea to add a screenshot and request ui-review from a ui-reviewer. See also the module ownership page.

The review process usually starts off with a ui-review. It is possible, that the code reviewer will postpone the review until you have ui-review+, in case it is clear that the UI will stay as proposed. In the code review, the reviewer checks if the style fits the [[Calendar:Style_Guide|Style Guide]], and does a general check if the patch works as advertised. To ease review, you should make sure there are no (new) error console warnings or errors, and all tests pass (<code>cd @TOPSRCDIR@/../objdir-tb/calendar; make -C test check</code>).

As soon as you have r+ from all reviewers (r+ means having a positive review, also known as r=''shortname''), you should fix everything that was requested, and upload a new patch. Unless you have Mercurial (hg) access yourself, the reviewer will generally take care of checking in the patch. If that's not the case, or he forgets to do so, you can add the <code>checkin-needed</code> keyword to the bug.

After the patch is checked in and all aspects of the bug are taken care of, the reviewer will resolve the bug as FIXED. The patch will then be available in the next spun nightly. When it is available, it is always a good practice to test the functionality using the original steps to reproduce. If everything works as proposed, you can set the bug as VERIFIED. If any regressions show up, you should file a new bug and set the <code>regression</code> keyword on it.

====Applying a patch====
''OUTDATED - WE NEED THE APPROPRIATE HG COMMANDS HERE''

From time to time, you might need to apply a patch from someone else, or maybe your own patch. This is quite easy, but note that if you plan on applying the patch, making some changes and then want to create a patch that doesn't contain the patch you originally applied, it might be quite a bit harder. This isn't very often the case though.

To apply a patch you need to find out what the path prefix is and match up the -p option. Assuming you or the other person used the process above to create the patch, you can use the following commands to apply the patch

<pre>
cd $MOZILLA/calendar
# --dry-run tests the patching process to ensure that the patch will go
# ahead cleanly. Be sure to run --dry-run at least once before running
# the actual patching process.
patch -p0 -i ~/my_first_bug.diff --dry-run
# Now check if the patch applies cleanly, or you are willing to fix the
# places it went wrong. When you are confident, you can call:
patch -p0 -i ~/my_first_bug.diff

# If the file to patch was not found, take a look at the patch headers. For
# example, if the header contains "+++ themes/winstripe/calendar-views.css",
# then you need to go into the base directory and call again. If the header
# contains "+++ mozilla/calendar/base/Makefile.in", you can use -p2 instead to
# strip the "mozilla/calendar" part.
patch -p2 -i ~/my_first_bug.diff
</pre>

If some changes went wrong, patch will create rejects files. To resolve changes, you should open the original file and the rejects file. On large rejects files, you might want to open the rejects file twice so you can see the lines that need to be removed and the lines that need to be added at the same time.

If you want to get rid of all changes at once, you can issue the following command. '''Warning''': This will get rid of all changes to the calendar tree you have made.

<pre>
# Enter the source directory
cd src

# Overwrite all local changes
hg update -C
</pre>

=Creating Extensions with the Build System=
If you have gotten this far and want to create an extension for Sunbird or Lightning instead of adding core functionality, it is also easily done. The advantage of this method, is that you don't have to take care of different chrome.manifests for development and deploying and also don't have to take care of zipping together the .xpi file yourself or via a script.

Specifics exceed the scope of this document, but [[Calendar:Creating_an_Extension]] covers this quite well.

=Using directories rather than JARs=
Sometimes it is simpler to develop chrome in a directory. If you choose a JARed structure for releasing, you can still develop with a directory structure by editing your chrome.manifest. For example, calendar.jar in the Lightning extension, rather than having

<pre>
content calendar jar:chrome/calendar.jar!/content/calendar/
</pre>
use
<pre>
content calendar chrome/content/calendar
</pre>

=Troubleshooting=
If you are having trouble, feel free to ask in #calendar on irc.mozilla.org. If you find no help there, try #developers. Do read the [http://developer.mozilla.org/en/docs/Build_Documentation Mozilla documentation] before asking.

==Common Build Errors==
'''Hidden symbols'''
Original Documentation [http://benjamin.smedbergs.us/blog/2005-10-27/gcc-40-workaround/ here]
<pre>
/usr/bin/ld: something.so: hidden symbol `nsSomeClass::SomeFunc(someArg*)' isn't defined
/usr/bin/ld: final link failed: Nonrepresentable section on output
</pre>
This can easily be worked around by adding the following line to your mozconfig

<code>ac_cv_visibility_pragma=no</code>

[[category:calendar|Build]]

Calendar:Who is who

2009-02-01T14:56:47Z

XFallenAngel:

[[Calendar:Home_Page|<< Back to Calendar Home Page]]

== 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
| 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
|
|
|
|-
| Gary Kwong
| Singapore
| QA
| nth10sd
| nth10sd (AT) gmail (DOT) com
| nth10sd (AT) gmail (DOT) com
|
|
|
|-
| Philipp Kewisch
| Germany
| Project Lead and 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
| 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
| ssitter (AT) gmail (DOT) com
| ssitter
| [http://ssitter.googlepages.com/sunbird]
|
|-
| Celina Beach
| USA
| QA
|
|
|
|
|
|
|-
| Sebastian Hengst
| Germany
| QA
| Archaeopteryx
|
|
|
|
|
|-
| Berend Cornelius
| Germany
| UI development
| berend
|
|
|
|
|
|-
| Omar Bajraszewski
| Poland
| QA
| Omar
|
|
|
|
|
|-
| Damian ?
| Poland
| QA and Litmus Administrator
| Damian
|
|
|
|
|
|-
| 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
|
|
|
|
|
|-
| Lars Wohlfahrt
| Germany
| QA
| thetux
| thetux.moz (AT) googlemail (DOT) com
| thetux.moz (AT) googlemail (DOT) com
| thetux
| [http://www.eviltux.de]
|
|-
| Myk Melez
|
|
| myk
| myk (AT) mozilla (DOT) org
|
|
|
|
|-
| Dan Mosedale
| USA
| Calendar Project Lead
| dmose
|
|
|
|
|
|-
| Michael Buettner
| Germany
| Developer
| mickey
| michael.buettner (AT) sun (DOT) com
| michael.buettner (AT) sun (DOT) com
|
|
|
|}

[[category:calendar|Who is who]]

FOSDEM 2009/Schedule

2009-01-22T16:31:34Z

XFallenAngel:

The schedule is still in flux. Please come back again to check for changes before the event.

{| border="1" cellpadding="10" cellspacing="0"
! When
! Title
! Description
! Speaker
|- style="background:#ffffff; color:black"
| Sat 13:15-14:00
| Mozilla Europe
| General Introduction followed by an update on the work of Mozilla in Europe.
| [http://standblog.org/ Tristan Nitot]
|-
| Sat 14:00-14:45
| Mozilla Foundation
| Foundation Update, Programs, Goals etc.
| Gervase Markham
|-
| Sat 14:45-15:15
| Mozilla and Universities
| Lightning talk about MAOW Madrid organized jointly with Madrid University
| Pascal Chevrel, Gregorio Robles
|-
| Sat 15:15-16:00
| Future Firefox
| Firefox 3.2, Extensions 2.0, Labs, and more
| Mike Connor
|-
| Sat 16:00-16:45
| Mozilla Community Sites Project
| ...
| Zbigniew Braniecki
|-
| Sat 16:45-17:30
| Community and Design
| Building Mozilla's visual design community
| John Slater
|-
| Sat 17:30-18:00
| TBD
| ...
| TBD
|-
| Sat 18:00
|
| Room closes at 18:00
|
|-
|
|
|
|
|-
| Sun 09:00-09:45
| SeaMonkey
| SeaMonkey 2 and the vision beyond
| [http://home.kairo.at/blog/ Robert Kaiser]
|-
| Sun 09:45-10:30
| Overview of Mozilla QA
| Who we are, what we do, how to get involved
| Carsten Book (Tomcat)
|-
| Sun 10:30-11:15
| Oni - Structured Concurrency for JavaScript
| In this talk I'll present the JavaScript [http://www.croczilla.com/oni Oni] library, a set of operators for writing composable concurrent code. Oni attempts to restore some modularity to concurrent programs; it offers a 'structured' alternative to conventional 'unstructured' idioms such as asynchronous callbacks.
| [http://www.croczilla.com/blog Alex Fritze]
|-
| Sun 11:15-12:00
| Rising to the Sun(bird) - How to get involved with the Calendar Project and where we are heading
| This presentation is a call to everyone to get involved. No matter if you prefer testing software (QA), designing interfaces or developing extensions or core code: We need you! The goal of this presentation is to show some interesting experiments you might be interested in developing, how you can use [https://addons.mozilla.org/firefox/addon/9018 mozmill] to easily record tests that help improve the software quality or what you can do as a designer if you have ideas on how to improve Calendar's visual appearance.
| [http://kewisch.blogspot.com/ Philipp Kewisch]
|-
| Sun 12:00-13:00
| Thunderbird
| ...
| [http://ascher.ca/blog/ David Ascher] and [http://perso.hirlimann.net/~ludo/blog/ Ludovic Hirlimann]
|-
| Sun 14:00-14:45
| Prism
| Prism is great!
| Matthew Gertner
|-
| Sun 14:45-15:30
| Mobile/Fennec
| General overview, and Fennec 1.0a2 and performance
| [http://www.christiansejersen.com/blog Christian Sejersen], [http://starkravingfinkle.org/blog Mark Finkle]
|-
| Sun 15:30-16:15
| Embedding
| The new embedding API
| [http://starkravingfinkle.org/blog Mark Finkle]
|-
| Sun 16:15-17:00
| Mozilla Headless back-end
| What, why and how it was written, where it's going, and demonstrations
| [http://chrislord.net/ Chris Lord]
|-
| Sun 17:00
|
| Room closes at 17:00 for final keynote
|
|}

FOSDEM 2009/Schedule

2009-01-22T14:31:29Z

XFallenAngel:

The schedule is still in flux. Please come back again to check for changes before the event.

{| border="1" cellpadding="10" cellspacing="0"
! When
! Title
! Description
! Speaker
|- style="background:#ffffff; color:black"
| Sat 13:15-14:00
| Mozilla Europe
| General Introduction followed by an update on the work of Mozilla in Europe.
| [http://standblog.org/ Tristan Nitot]
|-
| Sat 14:00-14:45
| Mozilla Foundation
| Foundation Update, Programs, Goals etc.
| Gervase Markham
|-
| Sat 14:45-15:15
| Mozilla and Universities
| Lightning talk about MAOW Madrid organized jointly with Madrid University
| Pascal Chevrel, Gregorio Robles
|-
| Sat 15:15-16:00
| Future Firefox
| Firefox 3.2, Extensions 2.0, Labs, and more
| Mike Connor
|-
| Sat 16:00-16:45
| Mozilla Community Sites Project
| ...
| Zbigniew Braniecki
|-
| Sat 16:45-17:30
| Community and Design
| Building Mozilla's visual design community
| John Slater
|-
| Sat 17:30-18:00
| TBD
| ...
| TBD
|-
| Sat 18:00
|
| Room closes at 18:00
|
|-
|
|
|
|
|-
| Sun 09:00-09:45
| SeaMonkey
| SeaMonkey 2 and the vision beyond
| [http://home.kairo.at/blog/ Robert Kaiser]
|-
| Sun 09:45-10:30
| Overview of Mozilla QA
| Who we are, what we do, how to get involved
| Carsten Book (Tomcat)
|-
| Sun 10:30-11:15
| Oni
| ...
| Alex Fritze
|-
| Sun 11:15-12:00
| Rising to the Sun - How to get involved with the Calendar Project and where we are heading
| This presentation is a call to everyone to get involved. No matter if you prefer testing software (QA), designing interfaces or developing extensions or core code: We need you! The goal of this presentation is to show some interesting experiments you might be interested in developing, how you can use [https://addons.mozilla.org/firefox/addon/9018 mozmill] to easily record tests that help improve the software quality or what you can do as a designer if you have ideas on how to improve Calendar's visual appearance.
| [http://kewisch.blogspot.com/ Philipp Kewisch]
|-
| Sun 12:00-13:00
| Thunderbird
| ...
| [http://ascher.ca/blog/ David Ascher] and [http://perso.hirlimann.net/~ludo/blog/ Ludovic Hirlimann]
|-
| Sun 14:00-14:45
| Prism
| Prism is great!
| Matthew Gertner
|-
| Sun 14:45-15:30
| Mobile/Fennec
| General overview, and Fennec 1.0a2 and performance
| [http://www.christiansejersen.com/blog Christian Sejersen], [http://starkravingfinkle.org/blog Mark Finkle]
|-
| Sun 15:30-16:15
| Embedding
| The new embedding API
| [http://starkravingfinkle.org/blog Mark Finkle]
|-
| Sun 16:15-17:00
| Mozilla Headless back-end
| What, why and how it was written, where it's going, and demonstrations
| [http://chrislord.net/ Chris Lord]
|-
| Sun 17:00
|
| Room closes at 17:00 for final keynote
|
|}

FOSDEM 2009/Schedule

2009-01-22T14:26:47Z

XFallenAngel:

The schedule is still in flux. Please come back again to check for changes before the event.

{| border="1" cellpadding="10" cellspacing="0"
! When
! Title
! Description
! Speaker
|- style="background:#ffffff; color:black"
| Sat 13:15-14:00
| Mozilla Europe
| General Introduction followed by an update on the work of Mozilla in Europe.
| [http://standblog.org/ Tristan Nitot]
|-
| Sat 14:00-14:45
| Mozilla Foundation
| Foundation Update, Programs, Goals etc.
| Gervase Markham
|-
| Sat 14:45-15:15
| Mozilla and Universities
| Lightning talk about MAOW Madrid organized jointly with Madrid University
| Pascal Chevrel, Gregorio Robles
|-
| Sat 15:15-16:00
| Future Firefox
| Firefox 3.2, Extensions 2.0, Labs, and more
| Mike Connor
|-
| Sat 16:00-16:45
| Mozilla Community Sites Project
| ...
| Zbigniew Braniecki
|-
| Sat 16:45-17:30
| Community and Design
| Building Mozilla's visual design community
| John Slater
|-
| Sat 17:30-18:00
| TBD
| ...
| TBD
|-
| Sat 18:00
|
| Room closes at 18:00
|
|-
|
|
|
|
|-
| Sun 09:00-09:45
| SeaMonkey
| SeaMonkey 2 and the vision beyond
| [http://home.kairo.at/blog/ Robert Kaiser]
|-
| Sun 09:45-10:30
| Overview of Mozilla QA
| Who we are, what we do, how to get involved
| Carsten Book (Tomcat)
|-
| Sun 10:30-11:15
| Oni
| ...
| Alex Fritze
|-
| Sun 11:15-12:00
| Calendar
| Rising to the Sun - How to get involved with the Calendar Project and where we are heading
This presentation is a call to everyone to get involved. No matter if you prefer testing software (QA), designing interfaces or developing extensions or core code: We need you! The goal of this presentation is to show some interesting experiments you might be interested in developing, how you can use [https://addons.mozilla.org/firefox/addon/9018 mozmill] to easily record tests that help improve the software quality or what you can do as a designer if you have ideas on how to improve Calendar's visual appearance.
| [http://kewisch.blogspot.com/ Philipp Kewisch]
|-
| Sun 12:00-13:00
| Thunderbird
| ...
| [http://ascher.ca/blog/ David Ascher] and [http://perso.hirlimann.net/~ludo/blog/ Ludovic Hirlimann]
|-
| Sun 14:00-14:45
| Prism
| Prism is great!
| Matthew Gertner
|-
| Sun 14:45-15:30
| Mobile/Fennec
| General overview, and Fennec 1.0a2 and performance
| [http://www.christiansejersen.com/blog Christian Sejersen], [http://starkravingfinkle.org/blog Mark Finkle]
|-
| Sun 15:30-16:15
| Embedding
| The new embedding API
| [http://starkravingfinkle.org/blog Mark Finkle]
|-
| Sun 16:15-17:00
| Mozilla Headless back-end
| What, why and how it was written, where it's going, and demonstrations
| [http://chrislord.net/ Chris Lord]
|-
| Sun 17:00
|
| Room closes at 17:00 for final keynote
|
|}

FOSDEM 2009/Schedule

2009-01-22T14:16:42Z

XFallenAngel:

The schedule is still in flux. Please come back again to check for changes before the event.

{| border="1" cellpadding="10" cellspacing="0"
! When
! Title
! Description
! Speaker
|- style="background:#ffffff; color:black"
| Sat 13:15-14:00
| Mozilla Europe
| General Introduction followed by an update on the work of Mozilla in Europe.
| [http://standblog.org/ Tristan Nitot]
|-
| Sat 14:00-14:45
| Mozilla Foundation
| Foundation Update, Programs, Goals etc.
| Gervase Markham
|-
| Sat 14:45-15:15
| Mozilla and Universities
| Lightning talk about MAOW Madrid organized jointly with Madrid University
| Pascal Chevrel, Gregorio Robles
|-
| Sat 15:15-16:00
| Future Firefox
| Firefox 3.2, Extensions 2.0, Labs, and more
| Mike Connor
|-
| Sat 16:00-16:45
| Mozilla Community Sites Project
| ...
| Zbigniew Braniecki
|-
| Sat 16:45-17:30
| Community and Design
| Building Mozilla's visual design community
| John Slater
|-
| Sat 17:30-18:00
| TBD
| ...
| TBD
|-
| Sat 18:00
|
| Room closes at 18:00
|
|-
|
|
|
|
|-
| Sun 09:00-09:45
| SeaMonkey
| SeaMonkey 2 and the vision beyond
| [http://home.kairo.at/blog/ Robert Kaiser]
|-
| Sun 09:45-10:30
| Overview of Mozilla QA
| Who we are, what we do, how to get involved
| Carsten Book (Tomcat)
|-
| Sun 10:30-11:15
| Oni
| ...
| Alex Fritze
|-
| Sun 11:15-12:00
| Calendar
| Rising to the Sun - How to get involved with the Calendar Project and where we are heading
| [http://kewisch.blogspot.com/ Philipp Kewisch]
|-
| Sun 12:00-13:00
| Thunderbird
| ...
| [http://ascher.ca/blog/ David Ascher] and [http://perso.hirlimann.net/~ludo/blog/ Ludovic Hirlimann]
|-
| Sun 14:00-14:45
| Prism
| Prism is great!
| Matthew Gertner
|-
| Sun 14:45-15:30
| Mobile/Fennec
| General overview, and Fennec 1.0a2 and performance
| [http://www.christiansejersen.com/blog Christian Sejersen], [http://starkravingfinkle.org/blog Mark Finkle]
|-
| Sun 15:30-16:15
| Embedding
| The new embedding API
| [http://starkravingfinkle.org/blog Mark Finkle]
|-
| Sun 16:15-17:00
| Mozilla Headless back-end
| What, why and how it was written, where it's going, and demonstrations
| [http://chrislord.net/ Chris Lord]
|-
| Sun 17:00
|
| Room closes at 17:00 for final keynote
|
|}

FOSDEM 2009/Schedule

2009-01-20T20:30:30Z

XFallenAngel:

Thunderbird/StatusMeetings/2009-01-20

2009-01-20T08:35:12Z

XFallenAngel: Philipp's status update

[[Thunderbird/StatusMeetings/2009-01-13|last meeting]] | [[Thunderbird/StatusMeetings|index]] | [[Thunderbird/StatusMeetings/2009-01-27|next week »]]

'''Thunderbird Meeting Details'''

* [http://www.timeanddate.com/worldclock/fixedtime.html?year=2009&month=01&day=20&hour=17&min=30&sec=0 Tuesday, Jan 20th, 17:30 UTC] (9:30am Pacific, 12:30pm Eastern)
* [[Thunderbird/StatusMeeting/DialInInfo|How to dial-in]]

== Agenda ==

* Who's taking minutes? --> '''gozer'''
* [http://ascher.ca/thunderbird/minutes_schedule.html Minute taking Schedule]. Talk to davida for schedule changes/additions.

=== Action Items ===

==== New ====

==== Open ====

==== Closed ====

=== [[Thunderbird:Thunderbird_3.0b2|Thunderbird 3 Beta 2]] ===

* For reference, Gecko 1.9.1b3: Jan 13 Code Freeze, Jan 15 QA, Jan 26 Release according to their plan.

* clarkbw is release driver
* gozer is build engineer
* Slushy string freeze from: Thursday 29th January 23:59 PST ('''1.5 weeks''')
* Firm string freeze and slushy Code freeze from: Tuesday 3rd February 23:59 PST
* Firm code/string freeze from: Thursday 5th February 23:59 PST
* l10n-mozilla-1.9.1 freeze from: Sunday 8th February 23:59 PST

(blocker numbers etc updated Monday)

* Blockers/Wanted
** {{trackinglist|TB 3.0b2 - blocking|blocking-thunderbird3%2B|---|Thunderbird%203.0b2&target_milestone{{=}}3.0b1}}: 56 (-4)
** [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=tb3needs&keywords_type=allwords&keywords=&resolution=---&emailassigned_to1=1&emailtype1=exact&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailtype2=exact&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= TB 3 Needs] 5 (0)
** {{trackinglist|TB 3.0b2 - wanted|wanted-thunderbird3%2B|---|Thunderbird%203.0b2}}: 40 (-2)
* Proposed Blocking
** {{trackinglist|Proposed Blockers (b? + milestone)|blocking-thunderbird3?|---|Thunderbird%203.0b2}}: 5 (-1)
* Fixed:
** {{trackinglist|TB 3.0b2 - blocking|blocking-thunderbird3%2B|FIXED|Thunderbird%203.0b2}}: 33 (+11)
** {{trackinglist|TB 3.0b2 - wanted|wanted-thunderbird3%2B|FIXED|Thunderbird%203.0b2}}: 18 (+2)

* We need to drive bugs with large string changes, e.g., archive, auto config, activity manager. Some way of marking bugs needing strings would be useful.
** Archive patch landed.
** Activity Manager is awaiting a new patch from Emre.
** AutoConfig {{bug|422814}}.

=== Thunderbird 3 ===

* [[Thunderbird:Thunderbird3:DevRoadmap]]

* time to truly clamp down and ship sooner rather than later, even at the cost of substantial feature cuts
* we need to get everything tracked in bugzilla
* we will now have component drivers so that people actually own keeping subsets of bugs well-triaged
** dmose to propose component assignments tuesday

* things to file & triage:
** component drivers: blocking+ / blocking? bugs
** davida: development roadmap
** clarkbw: UX bugs from last weeks meeting
** dmose: message reader bugs, tb3needs bugs

* new triage rules
** to stay on blocking+ list, a bug must be owned by someone, even if that's (temporarily) the component driver
** for each triaged bug on the blocking list: owner, target milestone, priority (P1 - P3; will be used to move bugs if milestone added)
** criteria for blocking+: if this were the last blocker, we would make all of our users wait even longer for the existing changes in order to get the fix for this one?

* to think about:
** when do we branch? (i suspect immediately after b2)
** when do we lock down the branch for only blocking+ and approved+ (i suspect a couple of weeks after b2)
** how do we want to handle existing wanted+ bugs? (throw them off the list?)
** when should we target having the first round of filing / triage done? (1 week from Tuesday?)
** There will be a TB 3 beta 3 (milestone created in bugzilla)

=== QA Updates ===

=== Roundtable ===

==== Status Updates ====

===== davida =====

===== dmose =====

===== nth10sd =====

* Triaging more often now since Mozmill in TB is sort-of working now.
* Patches, triage, bugday, etc.
** Patches for {{bug|461317}}, {{bug|473439}}

===== Standard8 =====

Non-goal activities:

* Reviews
* {{Bug|126491}} Drop "Card for:" on address book contact preview panes (part of the Card -> Contact rename).

Two week goals (start of week 2):

* Finish driving in Password Manager
** LANDED!
** Fixed regressions/problems:
*** {{Bug|437635}} (Multiple Master passwords again), {{Bug|473973}} (Calendar gdata issue), {{Bug|474277}} Incorrect use of real versus original usernames (caused at least some imap problems).
** Outstanding regressions/problems:
*** {{Bug|473715}} LDAP fails in autocomplete
*** {{Bug|474115}} Unknown, reporter is unclear (possible failure points are fixed afaict)
* Implement send in background
** Currently fixing/reworking code/interfaces to provide an improved server/listener type format so that we can have one service where everything "send later" related happens, and decent feedback for the UI e.g. activity manager.
** Looking to get at least a turned-off by default version into the code this week.
** {{Bug|473458}} Clean up nsIMsgWindow arguments on some functions so that we don't need a msgWindow for the send later code.
** {{Bug|473740}} Tidied up the service, dropped the intermediate nsIMessenger functions.
* Investigate Weave pop-tart system
** Started to look at, may be difficult for passwords, but could easily do for prompts. Probably worth integrating with the interactive status bar.
* Try and get initial numbers for Ts to see if we can enable jemalloc.

===== asuth =====

===== bienvenu =====

===== gozer =====

===== clarkbw =====

===== wsmwk =====
* triage tab bugs and update meta {{bug|392328}}
* triage tags/labels bugs and update meta {{bug|432710}} (if any are missing, they would probably be in this [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=anywords&short_desc=label+tag+tags+labels+taggegd+labeled+tagging+labeling+&product=MailNews+Core&product=Thunderbird&resolution=---&chfieldto=Now&field0-0-0=short_desc&type0-0-0=nowordssubstr&value0-0-0=html+.label&field0-1-0=component&type0-1-0=notsubstring&value0-1-0=address&negate1=1&field1-0-0=blocked&type1-0-0=substring&value1-0-0=432710 query]
* bugday
* herding crash bugs

===== beckley =====

====== Penelope ======

===== KaiRo =====

===== philipp / Calendar =====
* Calendar is heading towards automated testing with mozmill. First test in {{bug|474322}}. Needs build system integration though ({{bug|457265}}).
* Calendar blocking list needs triaging to cut down needed effort for a 1.0.

* Exams Jan 30th and Feb 2nd.
* I need a definitive answer what features are being cut to find out which areas to focus on.
* Will prepare blog post talking about new leadership.

===== rkent =====

===== rebron =====

Two Week Goal
* Distribution plan.
* Continue work on Support/Help plan.
* Beta 2 work.

=== Attendees ===

__NOTOC__

Philipp Kewisch

2009-01-18T19:45:20Z

XFallenAngel:

Philipp has been a member of the [http://www.mozilla.org/projects/calendar/about.html Mozilla Calendar Team] since 2007. He has contributed to both frontend and backened code and therefore knows his way around the calendar code quite well. To get started with the project, Philipp created the [https://addons.mozilla.org/en-US/sunbird/addon/4631 Provider for Google Calendar] which allows reading and writing data from and to Google Calendar.

In 2008, Philipp mentored a [[Community:SummerOfCode08#Calendar|Google Summer of Code Projects]] connected to the Calendar Project. Specifically, a project for locale-independent natural Language parsing which should cause Sunbird and Lightning to extract events from a plain text. A second project aimed at making Calendar more accessible (i.e via keyboard or also via screenreaders) fell below the line and was not accepted. Unfortuately, the language parser project ended before the mid-term since the project was a bit larger than the student could handle. Philipp fixed about 190 bugs in 2008.

Starting 2009, Philipp [http://weblogs.mozillazine.org/calendar/2009/01/calendar_leadership_changes.html was chosen as Daniel Bölzle's successor] as the Calendar project lead.

To contact Philipp, send email to mozilla at kewis dot ch

Accessibility/JSON ARIA

2009-01-07T12:27:36Z

XFallenAngel:

=Role extensibility=

This is a proposal for how authors could define new ARIA widgets.

=Problem statement=

The basic problem is that every accessibility API today has a predefined set of roles and properties. Historically, because developers are always creating new things, they end up forcing the new semantics into the existing semantics in inappropriate ways, just to get the behavior they want in one or two ATs they test with. This degrades the accessibility API over time as other ATs end up writing special case code for the various semantics on a per-application basis.

For example, an application may make their software work alright with JAWS, by putting additional status information into aria-describedby. However, this will not work well with changes to the status if the widget is later used dynamically, and will not work with alternative input technology.

Another issue is that standards bodies are slow, and that proprietary vendors do not want to spend the resources to painfully push their new ideas through the standards. In addition, it can be a problem to share IP in the new widgets before the release of a new product.

== Use cases ==

No one wants useless bloat, so the plan is to let ARIA 1.0 settle in and prove that it's necessary and usable via prototyping.

Here are some areas we will be developing use cases for:

* Vendor-specific widgets
* New innovations
* Areas that are too detailed and specific for standardization, but useful for accessibility (such as buddylists or scheduling widgets)
* Diagrams, where the visual appearance (color, dashed lines, whatever) often indicates properties

=How does it work?=

A new reusable role is defined by an author or organization via JSON.

The definition includes the following information:
# What other role can it be treated as (inheritance)?
# What properties does it have, and what is the type of each property
# The localization strings necessary to present the object as text
# How to treat property changes
# Which properties can be set by the user

=Status of the discussion=

This is a rough proposal for what the community may decide is not necessary, and even if we do it, we'll be waiting until after ARIA 1.0.

* There is still skepticism of whether this is necessary
* There are proponents of it among the vendor and accessibiltiy communities
* The idea has been run by the leads on Firefox accessibility, as well as the Orca and NVDA screen reader projects, and they believe it is feasible

We will be looking to get as many use cases that we can -- specifically we'll need widgets that ARIA 1.0 does not cover which this technology would help define.

= Authoring new roles =
== Pointing to new roles definitions from within document content==
===HTML===
<pre>
<head>
<link rel="ARIA" href="http://www.myroles.org/buddy.json"/>
<link rel="ARIA" "http://www.myroles.org/buddylist.json"/>

<link rel="ARIA-l10n" href="http://www.myroles.org/buddy-l10n.json"/>
<link rel="ARIA-l10n" href="http://www.myroles.org/buddylist-l10n.json"/>
</head>
</pre>

===XUL, SVG===

XUL and SVG don't define the <link> tag, an open question is how the roles can be included in such documents.

* One suggestion is to create a new processing instruction like: <code> <?xml-aria href="chrome://calendar/content/access/roles.json" type="text/json"?></code>
**Aaron: can we do this on a role by role basis for SVG? We have that advantage in the link solution for HTML
* Also, since XUL has XBL, and this is effectively a new widget, we could require that it be a new element. The nsIAccessibleProvider interface used in XBL could be extended to provide a property that points to the JSON file. Or, in XBL we could actually directly define the properties that would have been in the JSON.
** Fallen: processing instruction has the advantage that its a more general form of inclusion, which could possibly lead to allowing aria extensions for any type of XML document.
** Fallen: In XBL, we could probably use the <resources> block to add something, i.e:
<pre>
<binding id="foobar">
<resources>
<stylesheet src="chrome://calendar/skin/foosheet.css"/>
<aria-roles src="chrome://calendar/content/access/roles.json/>
<aria-roles src="chrome://calendar/locale/access/roles-l10n.json" l10n="true"/>
</resources>
...
</binding>
</pre>
== Authoring content with the new widget ==

<pre>
<div role="buddylist listbox secondary">
<div role="buddy option" aria-away="true" aria-idle="3 hours, 22 minutes" aria-where="mobile" aria-friends="somefriend"/>
</pre>

The author only needs to include the fallback role that we inherit from (in this case listbox or option) if they
need support for browser version that support ARIA but don't support role extensibility. Browsers that support
role extensibility should utilize the "inherits" field from the JSON file.

If you care about validation, you need to write a DTD or schema that handles the new properties.

== Defining the widget ==

Example: buddy widget
The definition is in a [http://en.wikipedia.org/wiki/JavaScript_Object_Notation JSON file], which is easy for any modern browser to parse into an object.

<pre>
{


"role": "buddy",

"inherits": "listbox",




"nameOkFromContents": true,

"activeProperties": [




[ "away", "boolean" ],
[ "activity", "string", "What is this user doing?" ],
],

"editableProperties":





[ "ignored", "boolean" ],

"passiveProperties": [ 

[ "idle", "string" ], 
[ "where", [ "pc", "mobile", "blackberry"] ], 
[ "friends", "IDREF" ], 
]



"localizedRole": "Buddy",

"localizedProperties": [

"friends", "Friends with"
]

"localizedValues": [



[ "ignored", [[ "true", "User blocked" ],
[ "false", "" ],
[ "away", [[ "true", "Currently away"],
[ "false", "Available" ]],
[ "where", [[ "pc", "At desk" ],
[ "mobile", "On phone"],
[ "blackberry", "On blackberry" ]]
]
}
</pre>

= End user experience =

== Screen reader users ==
Screen reader users would be able to hear the role of the new type of object, and associated properties.

Property changes:
* If the object is focused, then any properties in the activeProperties or liveProperties would be spoken
* If the object is not focused, then any properties in the liveProperties would be treated as a polite change

== Alternative input ==

If a property is listed under editableProperties, then it is the author's responsibility to handle mutation events and change the state of the widget based on changes to the ARIA attribute.

An alternative input device (an on screen keyboard, voice input software or even a cell phone browser) may choose to provide alternative methods for data entry that are more suitable for that environment. The web page must watch DOMAttrModified (onpropertychange in IE) and map that to the widget state.

= How to process =

There are 3 ways an AT can handle a new role:
# Basic accessibility: just fall back on the role it inherits from -- this is not wrong, but does not offer large improvements
# Good accessibility: use the provided JSON semantics for the role and its properties. It describes what to present when the object receives focus, and what to present when an attribute changes.
# Enhanced accessibility: via special application code for new role
#* User or vendor-defined AT scripts that operate on a per-webpage or per-role basis
#* If role becomes commonly used across the web, new versions of the core AT can deliver built-in support

== Accessibility API Support (ATK/AT-SPI and IAccessible2) ==

Need to fill this out -- we can either:
# use object attributes and events to indicate changed attributes, or
# develop new interfaces to expose the custom role information

Using a11y API events may be an issue, in terms of specifying which property has changed. We need either event data or a listener/callback mechanism. Need to think about this.

Accessibility/JSON ARIA

2009-01-07T12:26:29Z

XFallenAngel: /* XUL, SVG */

=Role extensibility=

This is a proposal for how authors could define new ARIA widgets.

=Problem statement=

The basic problem is that every accessibility API today has a predefined set of roles and properties. Historically, because developers are always creating new things, they end up forcing the new semantics into the existing semantics in inappropriate ways, just to get the behavior they want in one or two ATs they test with. This degrades the accessibility API over time as other ATs end up writing special case code for the various semantics on a per-application basis.

For example, an application may make their software work alright with JAWS, by putting additional status information into aria-describedby. However, this will not work well with changes to the status if the widget is later used dynamically, and will not work with alternative input technology.

Another issue is that standards bodies are slow, and that proprietary vendors do not want to spend the resources to painfully push their new ideas through the standards. In addition, it can be a problem to share IP in the new widgets before the release of a new product.

== Use cases ==

No one wants useless bloat, so the plan is to let ARIA 1.0 settle in and prove that it's necessary and usable via prototyping.

Here are some areas we will be developing use cases for:

* Vendor-specific widgets
* New innovations
* Areas that are too detailed and specific for standardization, but useful for accessibility (such as buddylists or scheduling widgets)
* Diagrams, where the visual appearance (color, dashed lines, whatever) often indicates properties

=How does it work?=

A new reusable role is defined by an author or organization via JSON.

The definition includes the following information:
# What other role can it be treated as (inheritance)?
# What properties does it have, and what is the type of each property
# The localization strings necessary to present the object as text
# How to treat property changes
# Which properties can be set by the user

=Status of the discussion=

This is a rough proposal for what the community may decide is not necessary, and even if we do it, we'll be waiting until after ARIA 1.0.

* There is still skepticism of whether this is necessary
* There are proponents of it among the vendor and accessibiltiy communities
* The idea has been run by the leads on Firefox accessibility, as well as the Orca and NVDA screen reader projects, and they believe it is feasible

We will be looking to get as many use cases that we can -- specifically we'll need widgets that ARIA 1.0 does not cover which this technology would help define.

= Authoring new roles =
== Pointing to new roles definitions from within document content==
===HTML===
<pre>
<head>
<link rel="ARIA" href="http://www.myroles.org/buddy.json"/>
<link rel="ARIA" "http://www.myroles.org/buddylist.json"/>

<link rel="ARIA-l10n" href="http://www.myroles.org/buddy-l10n.json"/>
<link rel="ARIA-l10n" href="http://www.myroles.org/buddylist-l10n.json"/>
</head>
</pre>

===XUL, SVG===

XUL and SVG don't define the <link> tag, an open question is how the roles can be included in such documents.

* One suggestion is to create a new processing instruction like: <code> <?xml-aria href="chrome://calendar/content/access/roles.json" type="text/json"?></code>
**Aaron: can we do this on a role by role basis for SVG? We have that advantage in the link solution for HTML
* Also, since XUL has XBL, and this is effectively a new widget, we could require that it be a new element. The nsIAccessibleProvider interface used in XBL could be extended to provide a property that points to the JSON file. Or, in XBL we could actually directly define the properties that would have been in the JSON.
** Fallen: processing instruction has the advantage that its a more general form of inclusion, which could possibly lead to allowing aria extensions for any type of XML document.
** Fallen: In XBL, we could probably use the <resources> block to add something, i.e:
<pre>
<binding id="foobar">
<resources>
<stylesheet src="chrome://calendar/skin/foosheet.css"/>
<aria-roles src="chrome://calendar/content/access/roles.json/>
<aria-roles src="chrome://calendar/locale/access/roles-l10n.json" l10n="true"/>
</resources>
...
</binding>

== Authoring content with the new widget ==

<pre>
<div role="buddylist listbox secondary">
<div role="buddy option" aria-away="true" aria-idle="3 hours, 22 minutes" aria-where="mobile" aria-friends="somefriend"/>
</pre>

The author only needs to include the fallback role that we inherit from (in this case listbox or option) if they
need support for browser version that support ARIA but don't support role extensibility. Browsers that support
role extensibility should utilize the "inherits" field from the JSON file.

If you care about validation, you need to write a DTD or schema that handles the new properties.

== Defining the widget ==

Example: buddy widget
The definition is in a [http://en.wikipedia.org/wiki/JavaScript_Object_Notation JSON file], which is easy for any modern browser to parse into an object.

<pre>
{


"role": "buddy",

"inherits": "listbox",




"nameOkFromContents": true,

"activeProperties": [




[ "away", "boolean" ],
[ "activity", "string", "What is this user doing?" ],
],

"editableProperties":





[ "ignored", "boolean" ],

"passiveProperties": [ 

[ "idle", "string" ], 
[ "where", [ "pc", "mobile", "blackberry"] ], 
[ "friends", "IDREF" ], 
]



"localizedRole": "Buddy",

"localizedProperties": [

"friends", "Friends with"
]

"localizedValues": [



[ "ignored", [[ "true", "User blocked" ],
[ "false", "" ],
[ "away", [[ "true", "Currently away"],
[ "false", "Available" ]],
[ "where", [[ "pc", "At desk" ],
[ "mobile", "On phone"],
[ "blackberry", "On blackberry" ]]
]
}
</pre>

= End user experience =

== Screen reader users ==
Screen reader users would be able to hear the role of the new type of object, and associated properties.

Property changes:
* If the object is focused, then any properties in the activeProperties or liveProperties would be spoken
* If the object is not focused, then any properties in the liveProperties would be treated as a polite change

== Alternative input ==

If a property is listed under editableProperties, then it is the author's responsibility to handle mutation events and change the state of the widget based on changes to the ARIA attribute.

An alternative input device (an on screen keyboard, voice input software or even a cell phone browser) may choose to provide alternative methods for data entry that are more suitable for that environment. The web page must watch DOMAttrModified (onpropertychange in IE) and map that to the widget state.

= How to process =

There are 3 ways an AT can handle a new role:
# Basic accessibility: just fall back on the role it inherits from -- this is not wrong, but does not offer large improvements
# Good accessibility: use the provided JSON semantics for the role and its properties. It describes what to present when the object receives focus, and what to present when an attribute changes.
# Enhanced accessibility: via special application code for new role
#* User or vendor-defined AT scripts that operate on a per-webpage or per-role basis
#* If role becomes commonly used across the web, new versions of the core AT can deliver built-in support

== Accessibility API Support (ATK/AT-SPI and IAccessible2) ==

Need to fill this out -- we can either:
# use object attributes and events to indicate changed attributes, or
# develop new interfaces to expose the custom role information

Using a11y API events may be an issue, in terms of specifying which property has changed. We need either event data or a listener/callback mechanism. Need to think about this.

Accessibility/JSON ARIA

2009-01-07T10:37:20Z

XFallenAngel: /* Authoring new roles */

=Role extensibility=

This is a proposal for how authors could define new ARIA widgets.

=Problem statement=

The basic problem is that every accessibility API today has a predefined set of roles and properties. Historically, because developers are always creating new things, they end up forcing the new semantics into the existing semantics in inappropriate ways, just to get the behavior they want in one or two ATs they test with. This degrades the accessibility API over time as other ATs end up writing special case code for the various semantics on a per-application basis.

For example, an application may make their software work alright with JAWS, by putting additional status information into aria-describedby. However, this will not work well with changes to the status if the widget is later used dynamically, and will not work with alternative input technology.

Another issue is that standards bodies are slow, and that proprietary vendors do not want to spend the resources to painfully push their new ideas through the standards. In addition, it can be a problem to share IP in the new widgets before the release of a new product.

== Use cases ==

No one wants useless bloat, so the plan is to let ARIA 1.0 settle in and prove that it's necessary and usable via prototyping.

Here are some areas we will be developing use cases for:

* Vendor-specific widgets
* New innovations
* Areas that are too detailed and specific for standardization, but useful for accessibility (such as buddylists or scheduling widgets)
* Diagrams, where the visual appearance (color, dashed lines, whatever) often indicates properties

=How does it work?=

A new reusable role is defined by an author or organization via JSON.

The definition includes the following information:
# What other role can it be treated as (inheritance)?
# What properties does it have, and what is the type of each property
# The localization strings necessary to present the object as text
# How to treat property changes
# Which properties can be set by the user

=Status of the discussion=

This is a rough proposal for what the community may decide is not necessary, and even if we do it, we'll be waiting until after ARIA 1.0.

* There is still skepticism of whether this is necessary
* There are proponents of it among the vendor and accessibiltiy communities
* The idea has been run by the leads on Firefox accessibility, as well as the Orca and NVDA screen reader projects, and they believe it is feasible

We will be looking to get as many use cases that we can -- specifically we'll need widgets that ARIA 1.0 does not cover which this technology would help define.

= Authoring new roles =
== Pointing to new roles definitions from within document content==
===HTML===
<pre>
<head>
<link rel="ARIA" href="http://www.myroles.org/buddy.json"/>
<link rel="ARIA" "http://www.myroles.org/buddylist.json"/>

<link rel="ARIA-l10n" href="http://www.myroles.org/buddy-l10n.json"/>
<link rel="ARIA-l10n" href="http://www.myroles.org/buddylist-l10n.json"/>
</head>
</pre>

===XUL, SVG===

XUL doesn't define the <link> tag, an open question is how the roles can be included in such documents.

* One suggestion is to create a new processing instruction like: <code> <?xml-aria href="chrome://calendar/content/access/roles.json" type="text/json"?></code>

== Authoring content with the new widget ==

<pre>
<div role="buddylist listbox secondary">
<div role="buddy option" aria-away="true" aria-idle="3 hours, 22 minutes" aria-where="mobile" aria-friends="somefriend"/>
</pre>

The author only needs to include the fallback role that we inherit from (in this case listbox or option) if they
need support for browser version that support ARIA but don't support role extensibility. Browsers that support
role extensibility should utilize the "inherits" field from the JSON file.

If you care about validation, you need to write a DTD or schema that handles the new properties.

== Definining the widget ==

Example: buddy widget
The definition is in a [http://en.wikipedia.org/wiki/JavaScript_Object_Notation JSON file], which is easy for any modern browser to parse into an object.

<pre>
{


"role": "buddy",

"inherits": "listbox",




"nameOkFromContents": true,

"activeProperties": [




[ "away", "boolean" ],
[ "activity", "string", "What is this user doing?" ],
],

"editableProperties":





[ "ignored", "boolean" ],

"passiveProperties": [ 

[ "idle", "string" ], 
[ "where", [ "pc", "mobile", "blackberry"] ], 
[ "friends", "IDREF" ], 
]



"localizedRole": "Buddy",

"localizedProperties": [

"friends", "Friends with"
]

"localizedValues": [



[ "ignored", [[ "true", "User blocked" ],
[ "false", "" ],
[ "away", [[ "true", "Currently away"],
[ "false", "Available" ]],
[ "where", [[ "pc", "At desk" ],
[ "mobile", "On phone"],
[ "blackberry", "On blackberry" ]]
]
}
</pre>

= End user experience =

== Screen reader users ==
Screen reader users would be able to hear the role of the new type of object, and associated properties.

Property changes:
* If the object is focused, then any properties in the activeProperties or liveProperties would be spoken
* If the object is not focused, then any properties in the liveProperties would be treated as a polite change

== Alternative input ==

If a property is listed under editableProperties, then it is the author's responsibility to handle mutation events and change the state of the widget based on changes to the ARIA attribute.

An alternative input device (an on screen keyboard, voice input software or even a cell phone browser) may choose to provide alternative methods for data entry that are more suitable for that environment. The web page must watch DOMAttrModified (onpropertychange in IE) and map that to the widget state.

= How to process =

There are 3 ways an AT can handle a new role:
# Basic accessibility: just fall back on the role it inherits from -- this is not wrong, but does not offer large improvements
# Good accessibility: use the provided JSON semantics for the role and its properties. It describes what to present when the object receives focus, and what to present when an attribute changes.
# Enhanced accessibility: via special application code for new role
#* User or vendor-defined AT scripts that operate on a per-webpage or per-role basis
#* If role becomes commonly used across the web, new versions of the core AT can deliver built-in support

== Accessibility API Support (ATK/AT-SPI and IAccessible2) ==

Need to fill this out -- we can either:
# use object attributes and events to indicate changed attributes, or
# develop new interfaces to expose the custom role information

Using a11y API events may be an issue, in terms of specifying which property has changed. We need either event data or a listener/callback mechanism. Need to think about this.

Fosdem:2009/Session Proposals

2009-01-07T00:02:41Z

XFallenAngel:

<< [[Fosdem:2009|Main FOSDEM 2009 page]]

Add your session proposals to the list here.

{|border="1" cellpadding="5" cellspacing="0"
|-
! Speaker
! Title
|-
| Jane Doe || All about Mozilla
|-
| Gervase Markham || Foundation Update, Programs, Goals etc.
|-
| Pascal Chevrel, Gregorio Robles || Mozilla and universities (lightning talk about MAOW Madrid organized jointly with Madrid University, 20mn)
|-
| || Community building
|-
| || OpenWeb : Where are we ? - HTML5, CSS3, Video/Audio, SVG
|-
| || Mobile (which area ?)
|-
| || Labs (which project ?)
|-
| Ludovic Hirlimann || Thunderbird 3
|-
| Philipp Kewisch || The Future of Calendar (or possibly a technical topic)
|-
| || Tracemonkey - Why is it so cool ? What are the next steps ?
|-
| Robert Kaiser || SeaMonkey 2 and the vision beyond
|-
| Mark Finkle || The new embedding API
|-
| Mark Finkle || XulRunner
|-
| || Firefox 3.2 ? (SVG, SMILE, ACID 3, ...)
|-
| Alex Fritze || [http://www.croczilla.com/zap Zap]
|-
| John Slater || Building Mozilla's visual design community
|-
| Tomcat || Overview over Mozilla QA (who we are, what we do, how to get involved)
|}

Fosdem:2009:Attendees

2008-12-29T12:39:52Z

XFallenAngel: /* Attendees */

===Attendees===

* Gervase Markham (Mozilla Foundation)
* Christopher Blizzard (Mozilla Project)
* Brian King ([http://briks.si Briks Software] and [http://mozdev.org Mozdev])
* Ludovic Hirlimann
* Zbigniew Braniecki (Mozilla Project)
* Alex Fritze ([http://www.8x8.com 8x8 Inc.], [http://www.croczilla.com/zap Zap])
* Dave Townsend (Mozilla Project)
* John Slater (Mozilla)
* Olli Pettay (Mozilla Project)
* Staś Małolepszy (Mozilla)
* Carsten Book "Tomcat" (Mozilla)
* Adrian Kalla (Polish Mozilla L10n)
* Philipp Kewisch (Mozilla Calendar Team)

Fosdem:2009

2008-12-23T23:25:10Z

XFallenAngel: /* Getting Around */

[http://www.fosdem.org/2009/ FOSDEM 2009] will take place in Brussels, Belgium on 7/8 February, 2009.

== What is FOSDEM? ==
FOSDEM is probably the most developer-oriented European Free and Open Source conference. It is taking place in Brussels, Belgium on Saturday 7 and Sunday 8 February 2009. Apart from having many invited speakers, the conference offers developer rooms, stands and lightning talks to projects from the Free and Open Source community.
[http://www.fosdem.org/2009/ More info...]

== Registration ==

A maximum of 75 participants can be sponsored to attend the event. All participants who receive an official invitation email by Mozilla can be sponsored. The invitation email contains a link pointing to an online registration form.

== Attendees ==
If you plan on joining us at FOSDEM 2009, please leave a note at [[Fosdem:2009:Attendees]]. See also the information on [[Fosdem:2009:Directions and travel logistics|travel logistics]] and the [[Fosdem:2009:Reimbursement|reimbursement policy]] if you have been accepted for sponsorship.

== Mozilla DevRoom ==
Every year Mozilla developers and contributors have a dedicated room (ie. Mozilla DevRoom) for the 2 days, in which to hold talks and sessions.

This year, Mozilla will have :

*a room on Sat 7th from 12:00 to 18:00 and on Sun 8th from 10:00 to 17:00,
*a video projector (with VGA cable)
*power (C/E plugs)
*wired (RJ-45) network with Internet access at the speaker's desk,
*best-effort shared wireless Internet access (a and b),
*publication of the schedule on the [http://fosdem.org/2009/ FOSDEM website], including speaker bios and talk abstracts.

== Schedule ==

The program committee this year is Axel Hecht, Brian King, Chris Blizzard and Paul Rouget. If you're interested to give a presentation, please add yourself to the [[FOSDEM 2009/Session Proposals]].

== Mozilla Stand ==
There will be a stand manned by Mozilla volunteers in the main conference building. The goal is two-fold: 
1) to evangelise and answer questions 
2) distribute merchandise.

== Food and Beverages ==

Breakfast will be served for all sponsored Mozilla participants who are staying in one of the two hotels Mozilla has secured for the event.

A dinner for Mozilla participants will be organized on Saturday, 7 February. More details very soon...

Any other food or drink expenses (including room service and in-room minibar charges) are at the expense of the attendee.

== Getting Around ==

A [http://maps.google.com/maps/ms?ie=UTF&msa=0&msid=103018965811080346788.000446969d65cef825f91 google maps overlay] is available with all three hotels and the FOSDEM location marked.

== Traveling by air to Brussels for FOSDEM ==

...the airport is less than 20 minutes from the city centre. From 6am till nearly midnight, the AIRPORT CITY EXPRESS train brings you to Midi, Central and North stations four times per hour. A one-way ticket costs 2,60 € second class and 3,90 € first class. The city express train is located in the basement (level -1) of the terminal building itself.

[[Image:Airport_to_Brussels.gif|frame|none|Map from airport to Brussels town center]]

== Traveling by train to Brussels for FOSDEM ==

If you are traveling by train to Brussels, it is best for you to get off at the Central Station stop.

== Hotels ==

Mozilla guests will be staying at the Novotel Brussels Grand Place, the Novotel Toure Noire or the CHAB : Centre Van Gogh. Please note that we strongly encourage guests sponsored by Mozilla to share rooms so that more Mozillians can be invited to participate at FOSDEM this year.

Here are the hotel details :

Novotel Brussels Grand Place
120, rue du Marché Aux Herbes
1000 BRUSSELS
BELGIUM
Tel: (+32)2/5143333
Fax : (+32)2/5117723
E-mail: H1030@accor.com
[http://www.accorhotels.com/accorhotels/fichehotel/nl/nov/1030/fiche_hotel.shtml See website here]

Novotel Brussels Centre Tour Noire
Rue de la Vierge Noire 32
1000 Bruxelles
Tel: +32.2.5055050
Fax: +32.2.5055000
[http://www.accorhotels.com/accorhotels/fichehotel/gb/nov/2122/fiche_hotel.shtml See website here]

CHAB : Centre Van Gogh
Rue Traversiere, 8
1210 Bruxelles
Tel: +32.2.2170158
Fax: +32.2.2197995
info@chab.be
[http://www.chab.be See website here]

== Getting from the Hotel to FOSDEM ==

From station GARE CENTRALE, take [http://www.stib.be/appl/EN/40000Eng/B/40071E.htm Bus 71] traveling towards DELTA. Get out at the station ULB. From there its a 9 minute footwalk. The total travel takes about 34 minutes.

You can find more local transportation info [http://www.stib.be/index.htm?guest_user=guest_en here].

Also you can find the [http://maps.google.com/ig/directory?synd=mpl&pid=mpl&features=sharedmap%2Cgeofeed&backlink=http%3A%2F%2Fmaps.google.com%2Fmaps%2Fms%3Fie%3DUTF8%26msa%3D0%26ll%3D50.84758%2C4.353772%26spn%3D0.0046%2C0.014334%26z%3D17%26iwloc%3DA&hl=en&num=24&url=http://www.brusselnieuws.be/site/img/geobrussel/mapplet/metrobrussels.xml&output=html metro plan as a google maps overlay].

[[category:Fosdem 2008]]

== Sponsorship for Travel and Accommodation ==

All travel and accommodation costs for participants who have received a personal email invitation by Mozilla Europe will be covered by Mozilla Europe. Please note that if you are sponsored by Mozilla, we strongly encourage you to share your room so that more Mozillians can be invited to participate at FOSDEM this year.

All invited participants will be staying at one of the above-mentionned hotels Mozilla has secured for the event. An email containing detailed information on their hotel will be sent to each participant after they confirm their registration.

Calendar Talk:GDATA Provider

2008-12-14T10:20:16Z

XFallenAngel:

== Offline Access to Google Calendar ==
'''Question'''
It is great to see that you are producing this plug-in and I love the functionality it already has.

I wanted to confirm what your plans were for allowing access to Google calendar appointment when Lightning is offline/the computer has not internet access.

I often need to be able to play with my calendar in this mode on my laptop and it seems that your plugin requires access to the internet currently?

'''Answer'''
This is something that will be supported by lightning/sunbird natively. See {{bug|366923}}.

== Events past 4pm in Google Calendar don't display in Day View ==

'''QUESTION''' When in Day View in Lightning (w/i Thunderbird) I cannot see any appts from Google Calendar that were made after 5pm (i.e. 4:45 and earlier displays correctly). If I switch to Week view or Month view, the appts display correctly, but switch back to Day view and they disappear inside Lightning. When I switch back to Week or Month view and move the appt up to any time from 4:45pm-earlier, then switch back to Day view, it displays correctly. If from Day view, I move that appt that I moved up to 4:45pm back to 7pm (where it originally was), it will move it correctly in Day view and display correctly until I change the view and come back to Day view and it disappears again.

'''Answer'''
Fixed in v0.3

== SMS alerts ==
'''Question'''
do you plan to implement support for sms gcalendar alerts in future releases?
thanks for the great add-on!
'''Answer'''
Yes, bug 389088.

== Categories ==
'''Question'''
Google Calendar doesn't support categories, does it?
'''Answer'''
No, the server doesn't support category entries. We have worked around the issue though, categories should work now.

== Task support ==
'''Question'''
I get it that Google Calendar doesn't support tasks per se, but Google does somewhat support tasks - at least in the Google Deskbar.
Any chance to get to those objects? [[User:Mcicogni|mcicogni]] 05:23, 24 October 2007 (PDT)
'''Answer'''
Unfortunately, since Google doesn't support tasks through the API, there is no easy way to support them. The tasks in google deskbar (?) are probably stored locally.

== Multiple Calendars and Read/Write Access ==
'''Question'''
Is it in the pipeline to support multiple different calendars (i.e ones shared by colleagues) and the read/write privileges?

'''Answer'''
This is already possible. Just add your colleagues XML link, the same as you add your own. When asked for a password, enter your own google calendar data (also username!). Make sure you have added your colleagues calendar via the Google Calendar UI prior to doing so.

== Atendees/Backup Function? ==

'''Question'''
Hi, GDATA Provider it´s an excellent tool, but why doesn´t allow send email invitation to atendees when created in a Google Calendar? Can this tool creates a new calendar in Google and upload the local events? This can be use as a Backup.

Thanks!

'''Answer'''
You can enable the calendar.google.sendEventNotifications pref, but do so on your own risk. you will be sending notifications on every add/update to all attendees.

Calendar:GDATA Provider

2008-12-14T10:18:35Z

XFallenAngel: /* Why can't I configure any options in the Extension Manager? */

=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==
You can obtain the provider from addons.mozilla.org. It is available for [https://addons.mozilla.org/sunbird/addon/4631 Sunbird] and [https://addons.mozilla.org/thunderbird/addon/4631 Lightning].

Note it is recommended to use the latest version of Sunbird or Lightning together with the latest Provider for Google Calendar version.

If you are using the latest nightly versions of Sunbird/Lightning, please use a comm-central version from [ftp://ftp.mozilla.org/pub/calendar/lightning/nightly/latest-comm-central ftp.mozilla.org]

==Building from Source==
If you want to build your own copy of the provider from the comm-central tree, all you need to do is follow the [https://developer.mozilla.org/en/Comm-central_source_code_(Mercurial)#Sunbird_and_Lightning build instructions] for Sunbird/Lightning. Once you have compiled, the resulting extension should be at <code>''obj-dir''/mozilla/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 ''Manage Calendars'' link located at the left of the page.
# Click on the Calendar you want to use with Thunderbird Lightning or Sunbird.
# Click on either of the two XML buttons shown at the bottom.

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'' when clicking File > New > Calendar > On the Network > Google Calendar in Sunbird/Lightning. There is also a graphical tutorial available at [http://bfish.xaedalus.net/?p=239 bfish.xaedalus.net].

=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 answered here, please discuss it [http://groups.google.com/group/provider-for-google-calendar/topics on the newsgroup]. If you believe you have found a bug, please file it in [https://bugzilla.mozilla.org/enter_bug.cgi?product=Calendar&component=Provider:%20GData bugzilla]

==Enabling calendar.debug.log==
This option is useful for more verbose logging to diagnose problems you are having. It is also a good thing to look at before posting on the discussion group:

* Open your application preferences (Tools or Edit Menu)
* Select the "Advanced" icon at the top.
* Click on the "General" tab, below the icons
* Select "Advanced Configuration"
* Right Click on an empty space in the list of preferences
* Select New > Boolean
* Enter "calendar.debug.log" as the preference name
* Pick "true" as the Boolean value.

Now you have enabled the preference. If you were experiencing a problem, you will get the most debug messages if you restart the application, then do whatever you were doing again until you experience the issue. Then check out the error console ("Tools" menu).

If you are testing CalDAV support, you should do the same steps above for the "calendar.debug.log.verbose" preference.

==I want to stay up to date on all GData Provider bugs!==
Nothing easier than that. In your bugzilla Email preferences, you can set up a list of "users" to watch. Enter the <code>gdata-provider@calendar.bugs</code> email address, and you will receive bugmail on each update to GData Provider bugs and on new bugs.

==Calendar Access==
===I cannot access my calendar at all!===
Now this is very general. First things first: Do you see any error console messages? If not, please enable <code>calendar.debug.log</code> in the advanced config editor. See above for how to do that. You should be getting more debug messages now.

Are you using a calendar nightly? (i.e 1.0pre) If so, you must use a mercurial compiled version of the gdata provider, not the official release. This is also described above in this FAQ.

===I want to be able to pick my calendars from a list, is there a way to do so?===
Not currently. Progress on this is being tracked in {{bug|378873}}.

===I have publicly shared my calendar. I don't want to enter my password each time!===
For public calendars you don't need the Provider for Google Calendar. Just use the standard iCalendar Provider and the ICS feed from Google. If you want to change a public calendar, there is no way around entering your password.

===I want to access a friend's calendar I have access too, but I am asked for a password!===
No problem! As long as you have this calendar added in the Google Calendar web interface, just enter your own credentials.

==Missing Features==
===Why can't I configure any options in the Extension Manager?===
There are currently not enough options to warrant an options window. There are some advanced preferences:

<code>calendar.google.useHTTPMethodOverride = true</code> Instead of using PUT and DELETE methods, use POST and GET with the X-HTTP-Method-Override header. This is good for proxies and since it doesn't harm non-proxies, it defaults to true.

<code>calendar.google.alarmClosest = true</code> Alarm support: Use either the alarm closest (true) or farthest away (false) from the event as the alarm displayed in Sunbird/Lightning.

<code>calendar.google.sendEventNotifications = true</code> When set to true, invitations are sent out to attendees on event modifications.

<code>calendar.google.enableAttendees = false</code> When set to false, attendees are disabled. This might be needed if you experience problems when accepting invitations.

<code>calendar.google.sendEmailNotifications = false</code> Setting this to true allows selecting a Google Calendar when accepting an invitation you received via email. '''WARNING:''' Enabling this option may cause you to unknowingly spam all attendees with an extra invitation! Only enable this option if you know what you are doing.

===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 be able to edit my calendars while offline!===
This is only partially possible. If you open the calendar properties dialog by right clicking in your calendar list, you can enable the "Cache". This means you will be able to see your events while in offline mode.

It is not possible to change events while you are offline at current.

==Event Interaction==
===I have set a category, but when changing the event it vanishes===
This could be caused due to {{bug|461995}}. I hope this will be fixed in the next version.

===I want to modify an Event but nothing happens. What am I doing wrong?===
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.

===After creating a recurring event, I am having problems with alarms. Why?===
Aside from the fact that there is no standardized scheme to store dismissing and snoozing alarms, Google doesn't allow setting certain properties on recurring events. This is especially the case for shared calendars. See bug {{bug|424185}} 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.

Also if you are using windows, make sure you have all timezone upgrades installed.

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

==Attendees==
===I recieved an invitation from a friend. When trying to accept, my Google Calendars are not in the select calendar dialog, or no dialog is shown===
Accepting an invitation onto your Google Calendar can cause extra invitations being sent out to each attendee. Due to some Google Calendar limitations when adding invitations to your calendar its impossible to allow this in a way that new users will not shoot themselves in the foot.

If you know what you are doing, you can still re-enable this behavior. See the FAQ question regarding options.

===After accepting an invitation, the attendees all get an additional invitation from me===
This is {{bug|400808}}. A workaround is to set <code>calendar.google.sendEventNotifications</code> to false in the advanced config editor, or to not handle event invitations via lightning. Note that setting this preference inhibits all sending of event notifications.

==Alarms==
===What should I keep in mind while using alarms with the provider?===
The provider will only alert alarms of type popup. Depending on the setting of the (boolean) property ''calendar.google.alarmClosest'', it will read either the popup alarm closest to the event (true) or furthest away (false). To avoid confusion, be sure you set only one alarm with type popup. All other alarm types will not be touched by the provider.

===I have set some default reminders in the Google UI, but they don't show up on new events?===
As it might be easy to tell Google to use those default reminders, it requires UI additions to sunbird/lightning. I would like to concentrate on backend functionality before I add such UI extensions. If you would like this functionality, feel free to file an enhancement bug in bugzilla. (Remember to search if such a bug exists first).

===I set an alarm on an event but after looking at the event again, the alarm has a totally different value!===
Since Google supports multiple alarms and sunbird/lightning only supports one alarm, its hard to find a good way to map between the possible alarms. The provider will read the alarm either closest to or furthest away from the event. If you change a popup alarm in sunbird/lightning, and another popup alarm gets closer to (or further away from) the event, then the provider will read the other alarm.

Another possibility is that you have set an alarm value that is not supported by Google. Currently, Google only accepts values between 5 minutes and 4 weeks before the event starts.

===I want to set more than one alarm, but the Event dialog only shows one!===
Since Sunbird/Lightning also does not support multiple alarms, its very hard to do so without massive UI and calendar backend changes. I'd like to fix this in calendar rather than in the provider. See {{bug|353492}} for multiple alarms support.

Calendar:GDATA Provider

2008-12-14T10:17:06Z

XFallenAngel:

=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==
You can obtain the provider from addons.mozilla.org. It is available for [https://addons.mozilla.org/sunbird/addon/4631 Sunbird] and [https://addons.mozilla.org/thunderbird/addon/4631 Lightning].

Note it is recommended to use the latest version of Sunbird or Lightning together with the latest Provider for Google Calendar version.

If you are using the latest nightly versions of Sunbird/Lightning, please use a comm-central version from [ftp://ftp.mozilla.org/pub/calendar/lightning/nightly/latest-comm-central ftp.mozilla.org]

==Building from Source==
If you want to build your own copy of the provider from the comm-central tree, all you need to do is follow the [https://developer.mozilla.org/en/Comm-central_source_code_(Mercurial)#Sunbird_and_Lightning build instructions] for Sunbird/Lightning. Once you have compiled, the resulting extension should be at <code>''obj-dir''/mozilla/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 ''Manage Calendars'' link located at the left of the page.
# Click on the Calendar you want to use with Thunderbird Lightning or Sunbird.
# Click on either of the two XML buttons shown at the bottom.

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'' when clicking File > New > Calendar > On the Network > Google Calendar in Sunbird/Lightning. There is also a graphical tutorial available at [http://bfish.xaedalus.net/?p=239 bfish.xaedalus.net].

=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 answered here, please discuss it [http://groups.google.com/group/provider-for-google-calendar/topics on the newsgroup]. If you believe you have found a bug, please file it in [https://bugzilla.mozilla.org/enter_bug.cgi?product=Calendar&component=Provider:%20GData bugzilla]

==Enabling calendar.debug.log==
This option is useful for more verbose logging to diagnose problems you are having. It is also a good thing to look at before posting on the discussion group:

* Open your application preferences (Tools or Edit Menu)
* Select the "Advanced" icon at the top.
* Click on the "General" tab, below the icons
* Select "Advanced Configuration"
* Right Click on an empty space in the list of preferences
* Select New > Boolean
* Enter "calendar.debug.log" as the preference name
* Pick "true" as the Boolean value.

Now you have enabled the preference. If you were experiencing a problem, you will get the most debug messages if you restart the application, then do whatever you were doing again until you experience the issue. Then check out the error console ("Tools" menu).

If you are testing CalDAV support, you should do the same steps above for the "calendar.debug.log.verbose" preference.

==I want to stay up to date on all GData Provider bugs!==
Nothing easier than that. In your bugzilla Email preferences, you can set up a list of "users" to watch. Enter the <code>gdata-provider@calendar.bugs</code> email address, and you will receive bugmail on each update to GData Provider bugs and on new bugs.

==Calendar Access==
===I cannot access my calendar at all!===
Now this is very general. First things first: Do you see any error console messages? If not, please enable <code>calendar.debug.log</code> in the advanced config editor. See above for how to do that. You should be getting more debug messages now.

Are you using a calendar nightly? (i.e 1.0pre) If so, you must use a mercurial compiled version of the gdata provider, not the official release. This is also described above in this FAQ.

===I want to be able to pick my calendars from a list, is there a way to do so?===
Not currently. Progress on this is being tracked in {{bug|378873}}.

===I have publicly shared my calendar. I don't want to enter my password each time!===
For public calendars you don't need the Provider for Google Calendar. Just use the standard iCalendar Provider and the ICS feed from Google. If you want to change a public calendar, there is no way around entering your password.

===I want to access a friend's calendar I have access too, but I am asked for a password!===
No problem! As long as you have this calendar added in the Google Calendar web interface, just enter your own credentials.

==Missing Features==
===Why can't I configure any options in the Extension Manager?===
There are currently not enough options to warrant an options window. There are some advanced preferences:

<code>calendar.google.useHTTPMethodOverride = true</code> Instead of using PUT and DELETE methods, use POST and GET with the X-HTTP-Method-Override header. This is good for proxies and since it doesn't harm non-proxies, it defaults to true.

<code>calendar.google.alarmClosest = true</code> Alarm support: Use either the alarm closest (true) or farthest away (false) from the event as the alarm displayed in Sunbird/Lightning.

<code>calendar.google.sendEventNotifications = true</code> When set to true, invitations are sent out to attendees on event modifications.

<code>calendar.google.enableAttendees = false</code> When set to false, attendees are disabled. This might be needed if you experience problems when accepting invitations.

<code>calendar.google.sendEmailNotifications = false</code> Setting this to true allows selecting a Google Calendar when accepting an invitation you received via email. ''WARNING:'' Enabling this option may cause you to unknowingly spam all attendees with an extra invitation! Only enable this option if you know what you are doing.

===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 be able to edit my calendars while offline!===
This is only partially possible. If you open the calendar properties dialog by right clicking in your calendar list, you can enable the "Cache". This means you will be able to see your events while in offline mode.

It is not possible to change events while you are offline at current.

==Event Interaction==
===I have set a category, but when changing the event it vanishes===
This could be caused due to {{bug|461995}}. I hope this will be fixed in the next version.

===I want to modify an Event but nothing happens. What am I doing wrong?===
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.

===After creating a recurring event, I am having problems with alarms. Why?===
Aside from the fact that there is no standardized scheme to store dismissing and snoozing alarms, Google doesn't allow setting certain properties on recurring events. This is especially the case for shared calendars. See bug {{bug|424185}} 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.

Also if you are using windows, make sure you have all timezone upgrades installed.

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

==Attendees==
===I recieved an invitation from a friend. When trying to accept, my Google Calendars are not in the select calendar dialog, or no dialog is shown===
Accepting an invitation onto your Google Calendar can cause extra invitations being sent out to each attendee. Due to some Google Calendar limitations when adding invitations to your calendar its impossible to allow this in a way that new users will not shoot themselves in the foot.

If you know what you are doing, you can still re-enable this behavior. See the FAQ question regarding options.

===After accepting an invitation, the attendees all get an additional invitation from me===
This is {{bug|400808}}. A workaround is to set <code>calendar.google.sendEventNotifications</code> to false in the advanced config editor, or to not handle event invitations via lightning. Note that setting this preference inhibits all sending of event notifications.

==Alarms==
===What should I keep in mind while using alarms with the provider?===
The provider will only alert alarms of type popup. Depending on the setting of the (boolean) property ''calendar.google.alarmClosest'', it will read either the popup alarm closest to the event (true) or furthest away (false). To avoid confusion, be sure you set only one alarm with type popup. All other alarm types will not be touched by the provider.

===I have set some default reminders in the Google UI, but they don't show up on new events?===
As it might be easy to tell Google to use those default reminders, it requires UI additions to sunbird/lightning. I would like to concentrate on backend functionality before I add such UI extensions. If you would like this functionality, feel free to file an enhancement bug in bugzilla. (Remember to search if such a bug exists first).

===I set an alarm on an event but after looking at the event again, the alarm has a totally different value!===
Since Google supports multiple alarms and sunbird/lightning only supports one alarm, its hard to find a good way to map between the possible alarms. The provider will read the alarm either closest to or furthest away from the event. If you change a popup alarm in sunbird/lightning, and another popup alarm gets closer to (or further away from) the event, then the provider will read the other alarm.

Another possibility is that you have set an alarm value that is not supported by Google. Currently, Google only accepts values between 5 minutes and 4 weeks before the event starts.

===I want to set more than one alarm, but the Event dialog only shows one!===
Since Sunbird/Lightning also does not support multiple alarms, its very hard to do so without massive UI and calendar backend changes. I'd like to fix this in calendar rather than in the provider. See {{bug|353492}} for multiple alarms support.

MeteredCheckins

2008-11-27T19:11:35Z

XFallenAngel: /* Checkin Queue */

Checkins are being metered by the active sheriff. If you wish to check in, add the bug number with the checkin to the list below. During this time, in order to land:

* the patch must have approval1.9.1+ or fix a bug marked blocking1.9.1 or blocking-firefox3.1
* the bug must have one of the following attached:
** An mq patch file (straight from .hg/patches)
** A patch created by hg export of a changeset
** An hg bundle (use hg help bundle, [https://developer.mozilla.org/en/Mercurial_FAQ#How_do_I_generate_a_bundle.3f see the FAQ], or ask in #hg if you need help).
* which ever you choose make sure you include a '''commit message''' and an '''username''' in the attachment, otherwise the bug '''won't''' be checked in.

== Checkin Queue ==
Add new items to the bottom of the list, and include your IRC nick in (parentheses).

* {{bug|458924}} activate the DidResizeColumns mechanism when column widths changes in fixed layout (bernd)
* [http://people.mozilla.com/~bturner/workerbundle.hg bent's worker bundle], which includes:
** {{bug|464983}} - Throw exceptions properly from XHR status getters and fake abort events in race conditions.
** {{bug|465108}} - Add navigator object.
** {{bug|465141}} - Implement expression flavor of timeouts, use nsAutoJSValHolder.
** {{bug|465447}} - Implement terminate() for explicitly killing a worker.
** {{bug|466256}} - Prevent cross-site workers and properly resolve relative URIs.
** {{bug|466257}} - Errors in sub workers aren't propagated to top-most parents like they should.
** {{bug|459790}} - Following Error console link causes uncaught exception ( 0x80004002 (NS_NOINTERFACE) [nsISupports.QueryInterface] ).
** {{bug|465006}} - Passing no arguments to the worker constructor throws an NS_ERROR_NOT_INITIALIZED error, incorrectly.
** {{bug|453865}} - Allow JSON-able objects to be passed as messages to worker threads.
* {{bug|395898}} - remove class="plain focusring" for the tree in about:config (mstange)
* [http://people.mozilla.com/~bclary/public/bc-1.bundle bc's js test bundle 1] (bc)
** {{bug|466606}} - JavaScript Tests - Do not force language version upon non-Gecko browsers.
** {{bug|466617}} - JavaScript Tests - default browser tests to non jit.
** {{bug|462939}} - JavaScript Tests - update slow-n.tests, add branch specific slow-1.8.1.tests, slow-1.9.0.tests, slow-1.9.1.tests.
** {{bug|461180}} - Fix test case result comparison function.
** {{bug|466269}} - fall out from getTestCase numeric/NaN comparison bug 461180.
** No bug - JavaScript Tests - sync js/tests/js1_8_1/trace/trace-test.js and js/src/trace-test.js
** {{bug|452786}} - JavaScript Test by Joachim Kuebart.
** {{bug|453915}} - JavaScript Test by Chris Evans.
** {{bug|462470}} - JavaScript Tests - deal with changes in decompilation and behavior from bug 461233.
** {{bug|465272}} - JavaScript Test by Jesse Ruderman.
** {{bug|465276}} - JavaScript Test by Jesse Ruderman.
** {{bug|465308}} - JavaScript Test by Jesse Ruderman.
** {{bug|465337}} - JavaScript Test by Jesse Ruderman.
** {{bug|465347}} - JavaScript Test by Brendan Eich.
** {{bug|465424}} - JavaScript Test by Jesse Ruderman.
** {{bug|465453}} - JavaScript Test by Jesse Ruderman.
** {{bug|465483}} - JavaScript Test by Jesse Ruderman.
** {{bug|465688}} - JavaScript Test by Jesse Ruderman.
** {{bug|466128}} - JavaScript Test by Jesse Ruderman.
** {{bug|466262}} - JavaScript Test by Jesse Ruderman.
** {{bug|466946}} - Sisyphus - JavaScript Tests - use autoconf to build Spidermonkey even if Makefile.ref exists.
** {{bug|466947}} - Sisyphus - retry profile creation on failure.
** {{bug|466951}} - Sisyphus - JavaScript Tests - add option to perform depends builds to bisect.sh.
** {{bug|460569}} - JavaScript Test - fix test so iframe is properly appended to document. Diagnosis by Ben Turner.
** {{bug|466952}} - Sisyphus - JavaScript Tests - update known failures.
* {{bug|463824}} - Introduce GLOBAL_DEPS to build system (Callek)
* [http://www.propagandism.org/peterv-1.bundle peterv's bundle], which includes:
** {{bug|458397}} - Memory leak during TopSite Test on http://www.grono.net.
** {{bug|464067}} - memory leak while running SVG reftests.
** {{bug|461563}} - Allow WrapNative to return a jsval without the wrapper.
** {{bug|461566}} - Don't call FindTearoff when not needed and cache XPCNativeInterfaces in quickstubs.
* {{bug|466756}} - make assertion about needing to call FlushUserFontSet fire under fewer conditiosn (dbaron)
* {{bug|466395}} - fix vertical alignment problems for large inline-blocks (dbaron)
* {{bug|435474}} - Provide a readline function for xpcshell to read a line from stdin (Fallen)

== Did not follow directions ==
'''These patches didn't follow directions, so they will be gotten to if time pending.''' People are welcome to fix and add themselves back to the bottom of the queue.
* {{bug|463687}} "More info" on severity blocklist dialog doesnt do anything (Mossop)

== Backouts ==

'''Landings that got backed out''' (add to the bottom, include reason why):
* from [http://people.mozilla.com/~roc/roc-2.bundle roc's second hg bundle]:
** {{bug|430332}} optimize reconstruction of textruns for text-transform text
* {{bug|453432}} Checking for MaybeGC
*{{bug|414715}} Notify the user if places.sqlite is locked, backed out due to possible Ts regression, needs new patch.

Calendar:Module Ownership

2008-11-19T19:00:32Z

XFallenAngel:

[[Calendar:Home_Page|<< Back to Calendar Home Page]]

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)
|daniel
|philipp, ctalbert, mvl*, lilmatt*
|-
|colspan="3"|'''Applications/Extensions'''
|-
|Sunbird (calendar/sunbird)
|mvl*
|daniel, ctalbert, lilmatt*
|-
|Lightning (calendar/lightning)
|mvl*
|daniel, philipp, ctalbert, lilmatt*
|-
|colspan="3"|'''Components'''
|-
|Accessibility
|philipp
|?
|-
|Alarms
|?
|daniel, philipp
|-
|Art & Branding
|lilmatt*
|MarkCarson
|-
|Calendar Manager
|philipp
|daniel, ctalbert, mvl*
|-
|Import/Export (calendar/import-export)
|mvl*
|
|-
|Installer (calendar/installer)
|lilmatt*
|ssitter, mschroeder, rob_strong, ctalbert
|-
|i18n/l10n (calendar/locales)
|sipaq
|lilmatt*
|-
|libical (calendar/libical)
|mvl*
|daniel
|-
|Recurrence
|daniel
|ctalbert, mvl*
|-
|Timezones
|ctalbert
|daniel, mvl*, lilmatt*
|-
|Views & Dialogs (calendar/{sunbird/}base/content)
|philipp
|berend, mschroeder
|-
|iTIP
|ctalbert
|daniel, lilmatt*
|-
|Printing
|lilmatt*
|daniel
|-
|Website
|sipaq
|lilmatt*
|-
|User Interface (UI)
|christian
|mvl*
|-
|colspan="3"|'''Providers'''
|-
|CalDAV
|bbrowning
|daniel, philipp, lilmatt*
|-
|Composite
|mvl*
|daniel
|-
|ICS
|mvl*
|daniel, sebo
|-
|Memory
|mvl*
|daniel, sebo
|-
|Storage
|mvl*
|daniel, sebo
|-
|WCAP
|daniel
|philipp
|-
|GDATA
|philipp
|daniel
|-
|colspan="3"|'''Tier-1 platform-specific stuff'''
|-
|Linux
|philipp
|daniel
|-
|Mac OS X
|daniel
|ctalbert, lilmatt*
|-
|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
|-
|berend
|berend.cornelius at sun 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
|-
|mschroeder
|mschroeder at mozilla dot x-home dot org
|-
|mvl
|mvl at exedo dot nl
|-
|philipp
|philipp at bugzilla dot kewis dot ch
|-
|rob_strong
|robert.bugzilla at gmail dot com
|-
|sebo
|sebo dot moz at googlemail dot com
|-
|sipaq
|bugzilla at babylonsounds dot com
|-
|ssitter
|ssitter at gmail dot com
|}
|}

=== Request Queue ===
When multiple reviewers come in question, you should check the [https://bugzilla.mozilla.org/request.cgi?action=queue&requester=&product=Calendar&type=review&requestee=&component=&group=requestee Calendar Request Queue] to see which reviewer has the smallest queue.

=== 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.

Use the Bugzilla ID to identify the reviewer in the Requestee field of the Attachment form.

[[category:calendar|Module Ownership]]

Calendar:Module Ownership

2008-11-19T19:00:08Z

XFallenAngel:

[[Calendar:Home_Page|<< Back to Calendar Home Page]]

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)
|daniel,
|philipp, ctalbert, mvl*, lilmatt*
|-
|colspan="3"|'''Applications/Extensions'''
|-
|Sunbird (calendar/sunbird)
|mvl*
|daniel, ctalbert, lilmatt*
|-
|Lightning (calendar/lightning)
|mvl*
|daniel, philipp, ctalbert, lilmatt*
|-
|colspan="3"|'''Components'''
|-
|Accessibility
|philipp
|?
|-
|Alarms
|?
|daniel, philipp
|-
|Art & Branding
|lilmatt*
|MarkCarson
|-
|Calendar Manager
|philipp
|daniel, ctalbert, mvl*
|-
|Import/Export (calendar/import-export)
|mvl*
|
|-
|Installer (calendar/installer)
|lilmatt*
|ssitter, mschroeder, rob_strong, ctalbert
|-
|i18n/l10n (calendar/locales)
|sipaq
|lilmatt*
|-
|libical (calendar/libical)
|mvl*
|daniel
|-
|Recurrence
|daniel
|ctalbert, mvl*
|-
|Timezones
|ctalbert
|daniel, mvl*, lilmatt*
|-
|Views & Dialogs (calendar/{sunbird/}base/content)
|philipp
|berend, mschroeder
|-
|iTIP
|ctalbert
|daniel, lilmatt*
|-
|Printing
|lilmatt*
|daniel
|-
|Website
|sipaq
|lilmatt*
|-
|User Interface (UI)
|christian
|mvl*
|-
|colspan="3"|'''Providers'''
|-
|CalDAV
|bbrowning
|daniel, philipp, lilmatt*
|-
|Composite
|mvl*
|daniel
|-
|ICS
|mvl*
|daniel, sebo
|-
|Memory
|mvl*
|daniel, sebo
|-
|Storage
|mvl*
|daniel, sebo
|-
|WCAP
|daniel
|philipp
|-
|GDATA
|philipp
|daniel
|-
|colspan="3"|'''Tier-1 platform-specific stuff'''
|-
|Linux
|philipp
|daniel
|-
|Mac OS X
|daniel
|ctalbert, lilmatt*
|-
|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
|-
|berend
|berend.cornelius at sun 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
|-
|mschroeder
|mschroeder at mozilla dot x-home dot org
|-
|mvl
|mvl at exedo dot nl
|-
|philipp
|philipp at bugzilla dot kewis dot ch
|-
|rob_strong
|robert.bugzilla at gmail dot com
|-
|sebo
|sebo dot moz at googlemail dot com
|-
|sipaq
|bugzilla at babylonsounds dot com
|-
|ssitter
|ssitter at gmail dot com
|}
|}

=== Request Queue ===
When multiple reviewers come in question, you should check the [https://bugzilla.mozilla.org/request.cgi?action=queue&requester=&product=Calendar&type=review&requestee=&component=&group=requestee Calendar Request Queue] to see which reviewer has the smallest queue.

=== 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.

Use the Bugzilla ID to identify the reviewer in the Requestee field of the Attachment form.

[[category:calendar|Module Ownership]]

Calendar:Module Ownership

2008-11-17T21:49:33Z

XFallenAngel:

[[Calendar:Home_Page|<< Back to Calendar Home Page]]

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*
|daniel, philipp, ctalbert, lilmatt*
|-
|colspan="3"|'''Applications/Extensions'''
|-
|Sunbird (calendar/sunbird)
|mvl*
|daniel, ctalbert, lilmatt*
|-
|Lightning (calendar/lightning)
|mvl*
|daniel, philipp, ctalbert, lilmatt*
|-
|colspan="3"|'''Components'''
|-
|Accessibility
|philipp
|?
|-
|Alarms
|?
|daniel, philipp
|-
|Art & Branding
|lilmatt*
|MarkCarson
|-
|Calendar Manager
|mvl*
|daniel, philipp, ctalbert
|-
|Import/Export (calendar/import-export)
|mvl*
|
|-
|Installer (calendar/installer)
|lilmatt*
|ssitter, mschroeder, rob_strong, ctalbert
|-
|i18n/l10n (calendar/locales)
|lilmatt*
|sipaq
|-
|libical (calendar/libical)
|mvl*
|daniel
|-
|Recurrence
|daniel
|mvl*, ctalbert
|-
|Timezones
|ctalbert
|daniel, mvl*, lilmatt*
|-
|Views & Dialogs (calendar/{sunbird/}base/content)
|philipp
|berend, mschroeder
|-
|iTIP
|ctalbert
|daniel, lilmatt*
|-
|Printing
|lilmatt*
|daniel
|-
|Website
|sipaq
|lilmatt*
|-
|User Interface (UI)
|christian
|mvl*
|-
|colspan="3"|'''Providers'''
|-
|CalDAV
|bbrowning
|daniel, philipp, lilmatt*
|-
|Composite
|mvl*
|daniel
|-
|ICS
|mvl*
|daniel, sebo
|-
|Memory
|mvl*
|daniel, sebo
|-
|Storage
|mvl*
|daniel, sebo
|-
|WCAP
|daniel
|philipp
|-
|GDATA
|philipp
|daniel
|-
|colspan="3"|'''Tier-1 platform-specific stuff'''
|-
|Linux
|philipp
|daniel
|-
|Mac OS X
|daniel
|ctalbert, lilmatt*
|-
|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
|-
|berend
|berend.cornelius at sun 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
|-
|mschroeder
|mschroeder at mozilla dot x-home dot org
|-
|mvl
|mvl at exedo dot nl
|-
|philipp
|philipp at bugzilla dot kewis dot ch
|-
|rob_strong
|robert.bugzilla at gmail dot com
|-
|sebo
|sebo dot moz at googlemail dot com
|-
|sipaq
|bugzilla at babylonsounds dot com
|-
|ssitter
|ssitter at gmail dot com
|}
|}

=== Request Queue ===
When multiple reviewers come in question, you should check the [https://bugzilla.mozilla.org/request.cgi?action=queue&requester=&product=Calendar&type=review&requestee=&component=&group=requestee Calendar Request Queue] to see which reviewer has the smallest queue.

=== 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.

Use the Bugzilla ID to identify the reviewer in the Requestee field of the Attachment form.

[[category:calendar|Module Ownership]]

Calendar:Status Meetings:2008-08-27

2008-08-20T17:21:06Z

XFallenAngel: New page: __NOTOC__ << previous meeting | index | next meeting >> == Mee...

__NOTOC__
<<[[Calendar:Status Meetings:2008-08-20| previous meeting]] | [[Calendar:Status Meetings|index]] | [[Calendar:Status Meetings:2008-09-03| next meeting >>]]

== Meeting Details ==
*[http://www.timeanddate.com/worldclock/fixedtime.html?month=8&day=27&year=2008&hour=18&min=0&sec=0&p1=37&sort=2, Wednesday, August 27th, 18:00 CET]
* Phone meeting

=== Telephone Info ===
* Toll free numbers
** US/Canada: 866-692-3163
** Netherlands: 0800-020-1392
** Germany: 0800-000-3441
** Switzerland: 0800-001-523
* 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 ===
* [[Calendar:Next_Release#Tracking_0.9|Tracking 0.9]]
** l10n Status
* TB Integration Status

=== Meeting Log ===
* Participants:

Calendar:Status Meetings:2008-08-20

2008-08-20T17:19:27Z

XFallenAngel: /* Meeting Log */

__NOTOC__
<<[[Calendar:Status Meetings:2008-08-13| previous meeting]] | [[Calendar:Status Meetings|index]] | [[Calendar:Status Meetings:2008-08-27| next meeting >>]]

== Meeting Details ==
*[http://www.timeanddate.com/worldclock/fixedtime.html?month=8&day=20&year=2008&hour=18&min=0&sec=0&p1=37&sort=2, Wednesday, August 20th, 18:00 CET]
* Phone meeting

=== Telephone Info ===
* Toll free numbers
** US/Canada: 866-692-3163
** Netherlands: 0800-020-1392
** Germany: 0800-000-3441
** Switzerland: 0800-001-523
* 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 ===
* [[Calendar:Next_Release#Tracking_0.9|Tracking 0.9]]
** l10n Status
* TB Integration Status

=== Meeting Log ===
* Meeting over irc today since Fallen's alarm didn't fire and it took a while to find out how to open the conference.
* Participants: davida, clarkbw, lilmatt, nth11sd, mvl, ctalbert, sipaq, Fallen, the rest of #calendar

'''Status'''
* 11 Blocker bugs, 3-4 are release bugs
* Berend is taking care of philipp's bugs and vice versa
* SSL hang bug has stacks, hopes are up that kaie will know how to fix things.
* Other bugs should soon be taken care of

'''Tb-integration'''
* davida wanted to know if everyone has enough clarity on the tb-integration flag.
* philipp doesn't want tb-integration to be a neverending quest
* davida agrees we should set a bar, he is confident that 90% of integration is "just XUL".
* Fallen was missing menus in the mockups, clarkbw will post something soon.

'''l10n status'''
* Not much to say, last Fallen heard all tinderboxen are green and there are some minor usage problems with some locales.