From: Gilou via pve-devel <pve-devel@lists.proxmox.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>,
Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Cc: Gilou <contact+dev@gilouweb.com>
Subject: [pve-devel] FOSDEM 2025
Date: Wed, 8 Jan 2025 04:13:20 +0100 [thread overview]
Message-ID: <mailman.93.1736306011.441.pve-devel@lists.proxmox.com> (raw)
[-- Attachment #1: Type: message/rfc822, Size: 4859 bytes --]
From: Gilou <contact+dev@gilouweb.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>, Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: FOSDEM 2025
Date: Wed, 8 Jan 2025 04:13:20 +0100
Message-ID: <28f3a30f-18b5-4531-a990-96afde6460c5@gilouweb.com>
Hello Proxmox community!
I hope everyone is having an amazing start in this new year... and this
year again, Proxmox will be represented @ FOSDEM in Brussels, on
February 1st & 2nd at ULB, stand will be in H-10.
Alexandre Derumier, FX Guidet and myself will be there for the week-end.
It would be awesome if one or two more Proxmox passionate persons could
join, as based on our previous experience: it's quite eventful, and we
almost get no rest at the stand.
Well, people do love Proxmox, what do you expect??
We will have a bit of merch provided by Proxmox, and also have a demo
cluster running on displays, so that fans and curious people can play
around with Proxmox live. And we do love beer.
So who is willing to give us a hand at anytime during the week-end? Even
if it's for one or 2 hours, it helps, and makes it easier for us to take
breaks!
We hope to see a lot of users there, make sure you pass by our stand if
you're there anyway!
Cheers,
Gilou
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
reply other threads:[~2025-01-08 3:13 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=mailman.93.1736306011.441.pve-devel@lists.proxmox.com \
--to=pve-devel@lists.proxmox.com \
--cc=contact+dev@gilouweb.com \
--cc=pve-user@lists.proxmox.com \
/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