9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Martin Schmitz <marden@db8ms.org>
To: 9front@9front.org
Subject: Re: [9front] mini hackathon
Date: Thu, 18 Jan 2024 23:06:28 +0100	[thread overview]
Message-ID: <78F67E53-F791-43BE-BB23-AD014264EBEE@db8ms.org> (raw)
In-Reply-To: <3AA3CB7F-553A-4ABE-9238-7C5961FA8839@web.de>

Hi, 

I’m currently not very active in using 9front or I never really appeared on the mailing list but I would join the hackathon. My knowledge became a bit rusty and coding C was ages ago.
Maybe I can be helpful in reviewing some docs, manpages, FQA or whatever.  
I also live in Cologne.
It’s also possible to provide some hardware if needed. Some small desktop switches, cables, a raspberry pi zero and 3B, some sensors (I2C, SPI) including wire-wrap stuff to avoid soldering on site, a Thinkpad R500 and X220 Tablet, a small intel Atom board which failes to run 9front, also on FreeBSD bhyve.

Greetings 

Marden


> Am 18.01.2024 um 17:17 schrieb Alexander Shendi (Web.DE) <Alexander.Shendi@web.de>:
> 
> Hi all, 
> 
> I'm sorry, I can't make it to the mini hackathon the weekend before FOSDEM anymore. 
> 
> I hope you have a lot of fun.
> 
> All the best,
> 
> Alexander
> 
> On January 18, 2024 3:28:53 PM GMT+01:00, hiro <23hiro@gmail.com> wrote:
>> ehmry added to the list.
>> 
>> i will continue sharing location data/timestamps as they become available to me.
>> it seems there will be something for everybody: uncomputing,
>> socializing, street computing and serious mortgage-driven
>> software-development. here's the schedule so far:
>> 
>> FRI afternoon/evening
>> on arrival:
>> Brauhaus FRÜH am Dom, Am Hof 12-18, 50667 Köln
>> This is across the station and then on the other side of the cathedral.
>> since the train station is cold, i suggest that if you are the first,
>> or while figuring out where everybody else has gone, or lost, first
>> head to frueh brauhaus.
>> train arrival times of attendees a) 15:40 b) 19:04
>> later we'll find some bar or music venue for the night.
>> 
>> SAT
>> 12:00-18:00
>> lunch at Limani, Agrippinawerft 6, 50678 Köln
>> 
>> SUN
>> 11:00-21:00
>> Bürgerhaus Stollwerck, Dreikönigenstr. 23, 50678 Köln
>> Meetingroom with Desk and 10 chairs for concentrated serious
>> programming business.
>> 
>> hiro


  reply	other threads:[~2024-01-18 22:08 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-08 11:47 hiro
2024-01-08 12:28 ` qwx
2024-01-08 13:53 ` Martin Riese
2024-01-08 15:15 ` [9front] " hiro
2024-01-09  2:08   ` hiro
2024-01-12 17:58     ` Arne Meyer
2024-01-13 18:35       ` qwx
2024-01-13 19:08         ` sirjofri
2024-01-13 19:35           ` hiro
2024-01-13 15:10     ` hiro
2024-01-13 19:30       ` hiro
2024-01-15 14:35         ` Emery Hemingway
2024-01-18 14:28           ` hiro
2024-01-18 16:17             ` Alexander Shendi (Web.DE)
2024-01-18 22:06               ` Martin Schmitz [this message]
2024-01-18 22:49             ` hiro
2024-01-25 18:33               ` [9front] " Martin Schmitz
2024-01-26  3:59               ` [9front] " hiro

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=78F67E53-F791-43BE-BB23-AD014264EBEE@db8ms.org \
    --to=marden@db8ms.org \
    --cc=9front@9front.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;
as well as URLs for NNTP newsgroup(s).