[cabfpub] Fwd: Last Call: Certificate Transparency - Second Hack Day: May 7th, 2014

[Ben Laurie]

---------- Forwarded message ----------
From: Eran Messeri <eranm at google.com>
Date: 23 April 2014 13:20
Subject: Last Call: Certificate Transparency - Second Hack Day: May 7th, 2014
To: certificate-transparency at googlegroups.com, "trans at ietf.org" <trans at ietf.org>


Gentlefolk,
If you intend to attend the second CT hack day, please sign up here by
Friday, May 2nd.

One of the issues that came up repeatedly recently was logs'
infrastructure and using the open-source log implementation in
production environments. If that's an interesting topic for you, the
hack day would be a very suitable forum to discuss it.

Regards,
Eran

---------- Forwarded message ----------
From: Eran Messeri <eranm at google.com>
Date: Thu, Mar 27, 2014 at 10:55 AM
Subject: Re: Certificate Transparency - Second Hack Day: May 7th, 2014
To: certificate-transparency at googlegroups.com, "trans at ietf.org" <trans at ietf.org>


The Certificate Transparency team at Google invites interested parties
to the second CT hack day at Google's London office on Wednesday, May
7th, 2014.

The agenda is open, though we have some suggestions:

Improving open-source C++ and Python monitors.
Draft (I-D) editing for RFC6962-bis.
Updates on Chrome support and Google's production logs.
Gossip: brainstorming communication channels and implementation.

Members of the trans WG are welcome to attend and collaborate (but
it's not a trans WG meeting).
We'll break into coding/discussion streams, like last time.

Register your interest and propose agenda items here (by May 2nd).

Eran, on behalf of the Certificate Transparency team at Google


On Thu, Mar 27, 2014 at 10:30 AM, Eran Messeri <eranm at google.com> wrote:
>
> The Certificate Transparency team at Google invites interested parties to the second CT hack day at Google's London office on Wednesday, May 7th, 2014.
> The agenda is open, though we have some suggestions:* Improving open-source C++ and Python monitors.* Draft (I-D) editing for RFC6962-bis.* Updates on Chrome support and Google's production logs.* Gossip: brainstorming communication channels and implementation.Members of the trans WG are welcome to attend and collaborate (but it's not a trans WG meeting).We'll break into coding/discussion streams, like last time.
> Register your interest and propose agenda items here (by May 2nd). If you can't attend in-person, let us know so we may set up a video conference for remote participants.
> Eran, on behalf of the Certificate Transparency team at Google





-- 
Certificate Transparency is hiring! Let me know if you're interested.