public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: g6094199@freenet.de
To: development@lists.ipfire.org
Subject: Re: IPFire Developer Summit 2016
Date: Wed, 29 Jun 2016 19:45:16 +0200	[thread overview]
Message-ID: <ba1007f7-f01f-90bf-17f9-f9091d01c2cb@chefmail.de> (raw)
In-Reply-To: <1467208729.2710.88.camel@ipfire.org>

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

Hi Michael,

just a sidenote: i dont know where the main contributors from the
community come from,  statisticly, but London might be out of the
question for most Germans for a quick stop by. ;-)


Sash


 

Am 29.06.2016 um 15:58 schrieb Michael Tremer:
> Hi,
>
> so I haven't received a single reply to this message which I find really
> upsetting. It is difficult to host this event and it is becoming more and more
> difficult over the years. I can only interpret the silence as a lack of interest
> and hopefully I am proven wrong.
>
> So before I sent out this email the entire Core team has already signed up for
> this summit and about a hand full more people will be joining. This isn't as
> many people as we had in the past years, but that doesn't necessarily say that
> this won't be an interesting summit.
>
> So in case someone was still considering coming, I would like to keep
> registration open for two more weeks until July 15th.
>
> After then we need to book accommodation and play any remaining things.
>
> Looking forward to hearing from you!
>
> Best,
> -Michael
>
> On Mon, 2016-04-18 at 00:12 +0100, Michael Tremer wrote:
>> Hello,
>>
>> as usual, I would like to invite for this year's IPFire Developer Summit. This
>> is our annual event where we meet up, discuss, plan and socialise.
>>
>> In contrast to the other years, we won't have talks and do more hands-on
>> things
>> instead. Think of it more of a hackaton than anything else. Feel free to bring
>> your own ideas.
>>
>> As everyone's schedule is very tight, we have agreed on the following dates
>> already:
>>
>>   Sept 1st-5th 2016
>>
>> It will be held in London as usual. I have not reached out to arrange a
>> location
>> like the Mozilla office we had last year as I would like to await
>> registrations
>> first.
>>
>> So here is the registration process:
>>
>>   Mailing list: http://lists.ipfire.org/mailman/listinfo/ids2016
>>
>> * Please drop me an email if you are going to attend so that we can estimate
>>   the number of people and start searching for a location.
>> * Also drop me an email if you are part of the active development team and not
>>   planning to attend. That will help me to know when to close the registration
>>   process.
>> * The mailing list is also the place to ask any questions, etc.
>> * I do not have a fixed date yet when I will close the registration process,
>>   but I would like to do this sooner than later. So please subscribe and
>>   mail soon.
>>
>> There is also the usual wiki page:
>>   http://wiki.ipfire.org/ids/2016/start
>>
>> Best,
>> -Michael



  reply	other threads:[~2016-06-29 17:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-17 23:12 Michael Tremer
2016-06-29 13:58 ` Michael Tremer
2016-06-29 17:45   ` g6094199 [this message]
2016-07-01 16:30   ` 5p9
2016-07-02 12:42     ` Michael Tremer
     [not found] <257a6b2b-5450-8ef5-e6db-87cfc9d7801e@ipfire.org>
2016-07-01 12:57 ` ummeegge

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=ba1007f7-f01f-90bf-17f9-f9091d01c2cb@chefmail.de \
    --to=g6094199@freenet.de \
    --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