Thanks to the wonderful folks at Linagora, I was able to spend the last three days at the Calconnect XXXI meeting in Bedford, England. The goal of this meeting is to get server and client vendors together in a room both for ad-hoc testing and discussions on calendaring standards.
Before arriving, I’ve set myself the goal to go through a big list of bugs that have been sitting around in our CalDAV component to see if they can be resolved. It turns out that I was able to close 48 of the 76 bugs I had picked out:
A good amount of the bugs I’ve resolved were sitting and waiting for any one of our contributors to reproduce with a specific server. This is often a problem because the time it takes to set up and configure the servers is time consuming. The great thing about being here at Calconnect is having a testing instance most of the reported servers readily set up. Not only that, but engineers from the respective servers are sitting together at a table and can answer any questions that may arise, or comment on potential bugs that have been fixed in later versions.
The other category of bugs are support issues, duplicates and bugs that haven’t received an answer from the reporter. These could have been found outside of Calconnect, but its still a good opportunity to take the time to handle these.
Eight of the remaining bugs already have a patch attached, four of them were created while I was here. There is also a new feature coming up that makes it easy to share calendars with other users directly from Lightning. This requires the server to support caldav-sharing, for example the Apple Calendar and Contacts Server and fruux.com.
In the next few days we will be going on to the standards discussions. I am actively involved as the chair to TC-API, a technical committee dedicated to producing an abstract calendaring model that ensures that vendors integrating calendaring into their products are aware of the implications of calendaring and scheduling, hopefully resulting in better interoperability in the future. Another goal we have is to find a common understanding for a REST API that is geared towards webpages, which may become a standards document some day.
Over the years I’ve organized or tried to organize pgp key signing parties every time I go somewhere. I the last year I’ve organized 3 that were successful (eg with more then 10 attendees).1. Have a venue
I’ve tried a bunch of times to have people show up at the hotel I was staying in the morning - that doesn’t work. Having catering at the venues is even better, it will encourage people to come from far away (or long distance commute). Try to show the path in the venues with signs (paper with PGP key signing party and arrows help).2. Date and time
Meeting in the evening after work works better ( after 18 or 18:30 works better).
Let people know how long it will take (count 1 hour/per 30 participants).3. Make people sign up
That makes people think twice before saying they will attend. It’s also an easy way for you to know how much beer/cola/ etc.. you’ll need to provide if you cater food.
I’ve been using eventbrite to manage attendance at my last three meeting it let’s me :
- know who is coming
- Mass mail participants
- have them have a calendar reminder
For such a party you need people to attend so you need to reach out.
I always start by a search on biglumber.com to find who are the people using gpg registered on that site for the area I’m visiting (see below on what I send).
Then I look for local linux users groups / *BSD groups and send an announcement to them with :
- link to eventbrite and why I use it
- ask them to forward (they know the area better than you)
- I also use lanyrd and twitter but I’m not convinced that it works.
for my last announcement it looked like this :Subject: GnuPG / PGP key signing party September 26 2014 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="t01Mpe56TgLc7mgHKVMajjwkqQdw8XvI4" This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --t01Mpe56TgLc7mgHKVMajjwkqQdw8XvI4 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hello my name is ludovic, I'm a sysadmins at mozilla working remote from europe. I've been involved with Thunderbird a lot (and still am). I'm organizing a pgp Key signing party in the Mozilla san francisco office on September the 26th 2014 from 6PM to 8PM. For security and assurances reasons I need to count how many people will attend. I'v setup a eventbrite for that at https://www.eventbrite.com/e/gnupg-pgp-key-signing-party-making-the-web-o= f-trust-stronger-tickets-12867542165 (please take one ticket if you think about attending - If you change you mind cancel so more people can come). I will use the eventbrite tool to send reminders and I will try to make a list with keys and fingerprint before the event to make things more manageable (but I don't promise). for those using lanyrd you will be able to use http://lanyrd.com/ccckzw. Ludovic ps sent to buug.org,nblug.org end penlug.org - please feel free to post where appropriate ( the more the meerier, the stronger the web of trust).= ps2 I have contacted people listed on biglumber to have more gpg related people show up. --=20 [:Usul] MOC Team at Mozilla QA Lead fof Thunderbird http://sietch-tabr.tumblr.com/ - http://weusepgp.info/ 5. Make it easy to attend
As noted above making a list of participants to hand out helps a lot (I’ve used http://www.phildev.net/pius/ and my own stuff to make a list). It make it easier for you, for attendees. Tell people what they need to bring (IDs, pen, printed fingerprints if you don’t provide a list).6. Send reminders
Send people reminder and let them know how many people intend to show up. It boosts audience.
Common (excluding Website bugs)-specific: (19)
- Fixed: 501689 – Investigate making storage asynchronous
- Fixed: 577461 – Status of date invitation in response emails is not shown
- Fixed: 673089 – Automate Lightning Beta Releases
- Fixed: 881285 – Remove obsolete nightly builds from nightly/latest-comm-central and nightly/latest-comm-aurora
- Fixed: 1022120 – Week-view: labels in the day headers don’t change from long to short format
- Fixed: 1041299 – Sending invitations with configured cc/bcc is broken
- Fixed: 1045223 – Creating events per drag doesn’t take default status values into account
- Fixed: 1045417 – Event attendee with a comma in display name gets splitted in two attendees
- Fixed: 1047227 – Lightning 3.3 no event cancellation button
- Fixed: 1048878 – Events’ order In the Unifinder doesn’t persist across Thunderbird’s sessions
- Fixed: 1049341 – Cannot edit meeting attendee list once invite created
- Fixed: 1054679 – Make the CalDAV provider async safe
- Fixed: 1055111 – Make calCachedCalendar async safe
- Fixed: 1059474 – update certificate exception handling in lightning to deal with bug 940506
- Fixed: 1063085 – Get rid of calIDateTime::jsDate
- Fixed: 1064552 – Fix postflight_all after the objdir move
- Fixed: 1067007 – [mozmill] tests do not work after TB build changes
- Fixed: 1068075 – Fix failure caused by [TypeError: redeclaration of variable ...]
- Fixed: 1068853 – TEST-UNEXPECTED-FAIL | /builds/slave/test/build/mozmill/testLocalICS.js | testLocalICS.js::testLocalICS
Sunbird will no longer be actively developed by the Calendar team.
- Fixed: 934874 – Thunderbird: Header labels in message reader have last letter of aria-label truncated
- Fixed: 950335 – “Force encryption” changed by “Use encryption if available” after XMPP wizard
- Fixed: 966655 – Scrollbar shown for recipient list when empty (involving screen dpi scaling): slightly insufficient default height of msgHeadersToolbar cripples visibility of recipients rows (see Bug 1056404)
- Fixed: 994655 – Allow ESC key to hide automatical attachment reminder notification bar when focus is in message subject
- Fixed: 1022209 – msgButton is null error when get new messages button not found on toolbar
- Fixed: 1024578 – attachment notification no longer collapses duplicate keywords
- Fixed: 1039452 – Near-perma orange: TEST-UNEXPECTED-FAIL | test-attachment-reminder.js | test-attachment-reminder.js::test_manual_attachment_reminder
- Fixed: 1039453 – TEST-UNEXPECTED-FAIL | test-charset-edit.js | test-charset-edit.js::test_wrong_reply_charset + test-charset-edit.js::test_no_mojibake
- Fixed: 1040009 – .mozconfig configure options are ignored if objdir path is absolute
- Fixed: 1041211 – Toolbox border still visible when all toolbars collapsed
- Fixed: 1044439 – No rule to make target `/home/josiah/comm-central/mozilla/intl/locale/src/props2arrays.py’, needed by `charsetalias.properties.h’ Build regression due to bug 1038537
- Fixed: 1046318 – glodaFacetView.css references non-existing attachment-col.png
- Fixed: 1046328 – update certificate exception handling in thunderbird to deal with bug 940506
- Fixed: 1046563 – tab bar UI broken on windows classic theme, TB31
- Fixed: 1052071 – Style of quota indicator not as nice as it used to
- Fixed: 1054260 – Can not drag main window by title bar
- Fixed: 1054738 – toolkit/library/target fails to link on Thunderbird MacOSX 10.8 Opt builds
- Fixed: 1055926 – Mozmill tests don’t run due to no mozinfo
- Fixed: 1056285 – Titlebar broken in fullscreen on OS X Yosemite
- Fixed: 1056404 – In addressing widget, only 2 recipient rows shown (including empty line) in spite of mail.compose.addresswidget.numRowsShownDefault=3; (caused by bug 966655)
- Fixed: 1057708 – Fix bustage caused by ‘Bug 1055281 – Make it an error to add a non-existent directory to LOCAL_INCLUDES’
- Fixed: 1057759 – Port bug 803812 to TB – “Restart to Update” button label in about dialog is vague
- Fixed: 1058873 – Permanent Orange: TEST-UNEXPECTED-FAIL | test-account-tree.js::test_account_open_state (Test Failure: a != b: ‘true’ != ‘false’)
- Fixed: 1059192 – Permanent orange: TEST-UNEXPECTED-FAIL | test_searchSuggest.js | contains an error
- Fixed: 1060281 – Mac universal build error: “autoconf.mk:3: /config/emptyvars.mk: No such file or directory”
- Fixed: 1060890 – Static-link the CRT into Thunderbird executable (/mail/app/moz.build). Port Bug 1023941 Part 1
- Fixed: 1062750 – Double border on main toolbar on Aero
- Fixed: 1062833 – tooltipUsernames is not defined
- Fixed: 1063919 – windows bustage: calbasecomps.dll : fatal error LNK1120: 13 unresolved externals
- Fixed: 1064698 – TEST-UNEXPECTED-FAIL | C:\slave\test\build\tests\xpcshell\tests\mail\base\test\unit\test_windows_font_migration.js | test failed (with xpcshell return code: 0)
- Fixed: 1065885 – Remove jschar from mail and mailnews
MailNews Core-specific: (35)
- Fixed: 66763 – Deleting a folder fails when there is already a folder with the same name in Trash
- Fixed: 324467 – TBird 1.5 fails to automatically filter on message body, if Anti-Virus quarentining is ON(mailnews.downloadToTempFile=true). POP3 not IMAP.
- Fixed: 332639 – force display of Sender header if S/MIME sender is the signer
- Fixed: 681632 – crash [@ nsMsgWindow::GetOpenFolder(nsIMsgFolder**)] beginning in version 6 [fixed by bug 679626]
- Fixed: 799821 – Folders misbehave when LSUB does not return mailbox flags
- Fixed: 858337 – Implement header parsing in JSMime
- Fixed: 859269 – upgrading to 20.0b1 hangs on “looking for folders” on uw-imap server (Bad configuration of an UW-IMAP server was unfortunately exposed by unplesant change to ‘LIST “” “*” use again’ by bug 799821)
- Fixed: 882968 – Clean up and move DEFINES and friends to moz.build in comm-central
- Fixed: 944526 – Include account name in status bar messages when sending/receiving/getting/downloading/fetching new News messages
- Fixed: 1005336 – startup or shutdown crash in nsObserverService::RemoveObserver(nsIObserver*, char const*) via nsMsgIncomingServer. reference to nsImapIncomingServer released off the main thread in destructors, due to preferences no longer use threadsafe refcounting
- Fixed: 1008718 – sending to wrong email (list) if “name” is in address book twice and one of them is a mailing list
- Fixed: 1020696 – Improve composition tests
- Fixed: 1037505 – test_pop3MoveFilter.js failure matching messages
- Fixed: 1046998 – Modify test_copyThenMoveManual.js to use Promises
- Fixed: 1047981 – Port |Bug 1047924 – When building with ac_add_options –enable-extensions extensions are put expanded into the wrong location in dist/bin| to comm-central
- Fixed: 1052327 – crash [@ PL_strnchr | nsParseMailMessageState::ParseHeaders() ]
- Fixed: 1052943 – Move additions to C*FLAGS into moz.build and do not link against the static RTL
- Fixed: 1053444 – Remove MOZ_APP_COMPONENT_MODULES from comm-central
- Fixed: 1054357 – Update c-c to address non-backward compatible changes to JS let semantics
- Fixed: 1054526 – Move LDFLAGS / WIN32_EXE_LDFLAGS out of Makefiles for c-c
- Fixed: 1054536 – Port *FLAG and related changes to config.mk
- Fixed: 1054727 – TEST-UNEXPECTED-FAIL | check-sync-dirs.py | build file copies are not in sync, port mozconfig.cache and client.mk changes from m-c to c-c
- Fixed: 1055867 – Move RCFLAGS and RCINCLUDE to moz.build and hardcode manifest name
- Fixed: 1056948 – Port bug 559505 to c-c (need to package xulstore)
- Fixed: 1057478 – Port bug 899585 modifying nsIAlertsService to mailnews
- Fixed: 1057537 – nsImapMailFolder::OnStartRequest generating error because it is not an nsIRequestObserver
- Fixed: 1057847 – Fix some more xpcshell-test failures due to warnings in the system logs
- Fixed: 1059551 – Bayesian spam filter won’t compile since bug 1057912
- Fixed: 1060258 – Permanent Orange: TEST-UNEXPECTED-FAIL | test_cleanup_msf_databases.js (and some other gloda tests)
- Fixed: 1060715 – TEST-UNEXPECTED-FAIL | /builds/slave/test/build/tests/xpcshell/tests/mailnews/news/test/unit/test_biff.js | 8 == 9 – See following stack: and other failures
- Fixed: 1060901 – [tb31.1 only] expand mail list broken for lists whose description is quoted
- Fixed: 1060959 – comm-central/configure: line 544: test: : integer expression expected
- Fixed: 1061338 – Port DELAYLOAD_LDFLAGS from bug 944800
- Fixed: 1062630 – Port bug 1041941 to c-c
- Fixed: 1063469 – some trivial “assignment to undeclared variable” in TB core.
Thunderbird meeting notes 2014-09-11
Today’s minutes taker, please don’t forget to :
– save etherpad before clearing for this meeting, if etherpad wasn’t previously cleared (but copy “Action items” to the top before clearing)
– after end of meeting, copy entire etherpad contents to a new dated wiki page on http://mzl.la/tbstatus so that they will go public in the meeting notes blog.
– save etherpad, copy “Action items” to “Action items from last meetings”, and clear the rest of etherpad comments
- rkent, florian queze, irving, rolandtanglao, magnus
- rkent and wsmwk to unblock / deal with bienvenu bugs
- no progress on “bienvenu” bugs
- comm-central changes on hold pending mercurial changes and signoff by smedberg
- discussion about kent’s modification to Thunderbird governance proposal is positive
- much work on summit and video from mconley and rkent
- summit agenda planning, rkent to ask in tb-planning
- Likely won’t be at meeting today, one of my meetings changed time slots to start 30m before this one
- according to gps, hg partial checkouts are targetted to land 3.2, more likely to land in 3.3 (release dates of Nov 1/Feb 1, respectively)
- bsmedberg has said this is his blocker for letting c-c merge into m-c
- gps plans to make it a high priority to update to newer hg quickly, and now has a new role to make that more possible
- Played with putting OpenLDAP server in a Docker container
- I have some prototype tests that use this server to test LDAP functionality
- Have done reviews and have been giving feedback in bugs, but personal development time has slowed. My development machine has to have a part replaced on Saturday plus I have papers and college applications to finish this month, so availability will be limited until around the time of the Summit.
- OS X Codesign V2 status is coming along, I’m mostly just waiting for a finished version of the Fx implementation.
- Summit: we really need a group of people to work on the agenda. Volunteers?
- Discussion of reorg plan?
- Now acting as interface between TB community and ProTravel Inc
- The attendees list has been garnered from the wiki, along with 2 extras from Fallen and Florian for Calendar / Chat. Waiting to hear from a few more.
- Re-connected with Aaron Mandel about a fundraising video. Quote is approximately $600 (+tax), since he likes Mozilla and wants to give us a deal
- We need to find a good variety (accents, countries of origin, languages) members of the TB community who are comfortable / articulate in front of the camera (about 5-7 people), and come up with “our story”. I suggested our audience be current TB users who don’t actually know what’s happening with Thunderbird.
- Quickly talk about where Thunderbird came from, the transition to community development, and where we are now – and why we need help. Instead of just talking heads, these interviews will be interspersed with shots of people checking their email, doing calendaring, chatting, etc.
- We need the quick and punchy stuff: “Put users in control of their email”, “Your email is yours, even when you’re offline”, “Lots of tweaks and add-ons for power users”
- We also need to send Aaron TB art / assets for graphical work.
- Once we have our story, we’ll put together a really basic script, so we know who to put in front of the camera, and what questions to ask.
- Then, I’ll meet with Aaron face-to-face 2 weeks before we shoot to make sure we have everything we need
- During the summit (probably the Friday), we’ll pull our 5-7 people aside, ask them the questions we’ve scripted (maybe several times to get the sound bites we want), and then Aaron will cut together the video.
- Been in contact with some of the DarkMail developers, have been trying to get them to ask questions in #maildev, but they seem to like to ask through me.
- They’ve said things like “Random people don’t get answers there”
- More likely they’re working during times when “we’re” not online.
- Roland transitioning. Last Day is April 30, 2015. Organizing weekly support meetings to get bugs/papercuts done as part of the transition.
- mconley: Come up with a short-list of volunteers to go on camera, send out emails with questions on them to get responses, find the responses that resonate, and from that, assemble our script.