All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Christian T. Steigies" <cts@debian.org>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: Debian m68k <debian-68k@lists.debian.org>,
	Linux/m68k <linux-m68k@vger.kernel.org>
Subject: Re: Debian 68k meeting in 2018
Date: Wed, 8 Nov 2017 13:08:44 +0100	[thread overview]
Message-ID: <20171108120844.GA21585@nunzio.venus.sol> (raw)
In-Reply-To: <80eb7c16-6016-55f7-089a-8ea2511c6f00@physik.fu-berlin.de>

Moin,
On Sat, Nov 04, 2017 at 12:51:53PM +0100, John Paul Adrian Glaubitz wrote:
> Hi list!
> 
> I was wondering whether anyone would be interested in having another
> Debian/m68k meeting in 2018 after the last one in 2015 was quite a
> success :).
> 
> We could work on resurrecting various kernel drivers for Amiga hardware
> as I have now enough hardware available for testing which I could bring.
> 
> Another area to work on would be the debian-installer which has made
> some process in the past months but there are certainly still some
> things that can be improved.
> 
> Maybe we can gather more people this time since the overall visibility
> of Debian/m68k seems to have increased.
> 
> Any suggestions for a venue?

2015 was a good year for meetings, Debconf was in Heidelberg and I proposed
a debian-science sprint there for the following year. On the weekends and
during the semester break, it should be easy to book a room for us. We have
eduroam and with a little bit of work we can probably use wired network as
well. Some (outdated) info on the venue is here:
http://www.ieap.uni-kiel.de/et/people/steigies/summerschool/localinfo.html

We did already have a m68k meeting in Kiel, not so long(?) ago:
https://lwn.net/Articles/297777/

However, the sleeping arrangements from those days are not possible anymore. 
I have a bit more space than those days (nobody has to sleep in the bathtub
anymore), but we have lots of hostels/hotels in town as well.  And as long
as you don't want to visit during Kieler Woche (you should!), rooms should
be available.

But with the overwhelming response to Adrians request, I am not sure if
the rooms at the institute are large enough for all the participants...

Christian
 

  reply	other threads:[~2017-11-08 12:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-04 11:51 Debian 68k meeting in 2018 John Paul Adrian Glaubitz
2017-11-08 12:08 ` Christian T. Steigies [this message]
2017-11-08 12:23   ` ALeX Kazik
2017-11-08 13:11   ` John Paul Adrian Glaubitz
2017-11-09  9:57     ` Christian T. Steigies
2017-11-09 10:03       ` John Paul Adrian Glaubitz
2017-11-09 11:17         ` Carsten Strotmann
2017-11-13 19:05           ` Ingo Jürgensmann
2017-11-09 10:07       ` Ingo Jürgensmann

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=20171108120844.GA21585@nunzio.venus.sol \
    --to=cts@debian.org \
    --cc=debian-68k@lists.debian.org \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=linux-m68k@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.