public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: IPFire Developer Summit 2019
Date: Sun, 28 Apr 2019 11:31:58 +0100	[thread overview]
Message-ID: <894150E5-E38D-44B0-A31B-C8181E44F740@ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 814 bytes --]

Good morning,

I would like to officially announce our this year’s IPFire Developer Summit.

This year’s date is June 20-25th and we are going to be in London.

We have settled on this date, because the Core Developers have little availability this year and this is the only date that would work, but we are hoping that many of you will join us then and there.

We do not have a venue, yet, but as soon as we have a number of attendees I will start planning this.

With this email, I would like to invite everyone to attend. This year, we are not planning to have any talks, but rather organise the event as a hackathon and planning meeting.

If you would like to attend, or if you would like to sponsor us and help us with paying for this important event, please get on touch!

Best,
-Michael

                 reply	other threads:[~2019-04-28 10:31 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=894150E5-E38D-44B0-A31B-C8181E44F740@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox