NaN

Geek stuff from a french geek and photographer
Recent Tweets @lhirlimann
www.flickr.com

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

4 Reach out

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 :

  • date
  • venue
  • 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.

I’m organizing a pgp Keysigning 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’ve setup a eventbrite for that at https://www.eventbrite.com/e/gnupg-pgp-key-signing-party-making-the-web-of-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.(Please tweet the event to get more people in).

We just released the second beta of Thunderbird 31. Please help us improve Thunderbird quality by uncovering bugs now in Thunderbird 31 beta so that developers have time to fix them.

There are two ways you can help

- Use Thunderbird 31 beta in your daily activities. For problems that you find, file a bug report that blocks our tracking bug 1008543.

- Use Thunderbird 31 beta to do formal testing.  Use the moztrap testing system to tests : choose run test - find the Thunderbird product and choose 31 test run.

Visit https://etherpad.mozilla.org/tbird31testing for additional information, and to post your testing questions and results.

Thanks for contributing and helping!

Ludo for the QA team

Updated links

We just released the first beta of Thunderbird 30. There will be two betas for 30 and probably 2 or more for 31. We need to start uncovering bugs nows so that developers have time to fix things.

Now is the time to get the betas and use them as you do with the current release  and file bugs. Makes these bugs block our tracking bug : 1008543.

For the next beta we will need more people to do formal testing - we will use moztrap and eventbrite to track this. The more participants to this (and other during the 31 beta period), the higher the quality. Follow this blog or subscribe to the Thunderbird-tester mailing list if you wish to make 31 a great release.

Ludo for the QA team

We’ve just released another beta of Thunderbird. We are now in the middle of the release cycle until the next major version is released to our millions of daily users. (we’ve fixed 200+ bugs since the last major release (version 24)). We currently have less than 1% of our users - using the beta and that’s not enough to catch regressions - because Thunderbird offers mail, newsgroups and rss feeds we can’t cover the usage of our user base. Also many companies out there sell extensions for spam filtering, for virus protection and so forth. The QA community just doesn’t have the time to try all these and run these with Thunderbird betas to find issues.

And that’s where you dear reader can help. How you might ask well here is a list of examples of how you can help :

  • Use the beta yourself it’s downloadable at http://www.mozilla.org/en-US/thunderbird/all-beta.html
  • spread the word by sharing this with your friends
  • you are a reps ? make this post available in your language ….
  • You help on a support forum - link to the beta download page explaining why it’s important to have more users on beta
  • You work for a vendor that sell a product that integrates in Thunderbird ? Qualify your product with the beta so when we ship final we both won’t get surprises.
  • Your company uses Thunderbird ? Setup a small group of beta users and gather the bugs, issues and let us know.

If you find issues let us know either thru bugzilla or thru the support forums, so we can try to address them.

ps the current download page says English only because of a bug in our build infrastructure for windows. Linux and Mac builds are available localized.

A recent twitter thread annoyed me about innovation in email :

That got me annoyed, because I always here we need to innovate with email and gmail is always taken as a reference in terms of email innovation.

But if you look at it gmail brought the following things to the world :

  1. unlimited “brokenish imap”
  2. Dkim/spf to fight spammers
  3. Good/very good spam filters (using the sender trust level)
  4. new nice UI to webmail

And that’s it. I’ve been involved with a MUA long enough now that I think email can’t be fixed by ‘just’ UI work or client work. Some things need to happen at the spec level and be implemented on both client and servers.

Unfortunately email has been around for 30ish years now and working for all that time - so fixing and simplifying can’t happen over night.

Let’s make a list of what needs to be fixed client side first :

  • The way headers are parsed and handled - way too complicated. Whilst this might have been a necessity 30 years ago I think , that with the email usage we have today it can be simplified. http://tools.ietf.org/html/rfc5322 Needs to be simplified for headers.
  • The way mime is handled - the RFC is 18 years old and needs revisiting, we can probably simplify it too, I don’t believe we need so many ways to send attachments in an email. One should be enough.
  • Threading - discard reference-to headers if the subject doesn’t keep any words from the initial subject for instance.
  • Make it very easy to unsubscribe from a mailing list.

On the server side there are way more things that need to be fixed

  1. smtp needs to be replaced with something that would reduce spam and try to keep the identify of the sender (things done today with things like dkim/spf/openpgp).
  2. mailing list need to be rethought in the way you interact with them - eg digest mode / subscribe / unsubscribe / vacation / cross-posting
  3. Rich Format email

Of course the last thing to fix is users, why ho why on earth do I get a Microsoft word has an attachment - while I could have directly got the content in the email itself.

On march 25th 2014 I’m organizing a pgp key signing party in the Mozilla London office after working hours.

If you value privacy and email you should probably attend. In order to organize the meeting I need to know the number of participants , for that I’m requesting that people register using eventbrite.

For thos who don’t know how pgp key signing party work you should read this http://sietch-tabr.tumblr.com/post/61392468398/pgp-key-signing-party-at-mozilla-summit-2013-details.