Hi all! [cross-post to make sure everyone knows about it, please follow-up-to the osmodev...@lists.osmocom.org mailing list for further discussion]
As I mentioned several times at different occasions, I really think we should put together a OsmoDevCon again. In case you don't know what that is, please see https://osmocom.org/projects/osmo-dev-con/wiki/OsmoDevCon We should have restarted already in 2023, but I really was too busy and it was a somewhat difficult year for me at times, sorry. Date ---- In terms of timing, I am thinking about "after April but before the main summer holiday season (June-August)". That leaves May. Given that May has the whitsunday weekend as well as GPN (Gulaschprogrammiernacht, a CCC event that will likely conflict of interest with some people interested at attending OsmoDevCon), I'm currently considering the following candidate dates: * May 3 to 6 * May 24 to 27 This is as usual a friday-to-monday timeframe, allowing people who don't work professionally on osmocom to attend just the two weekendd days, while others can attend the full 4 days. Venue ----- In terms of venue, I'm hoping we can move to a slightly different arrangement where the whole group stays together for the whole duration of the event - as opposed to everyone staying at different hotels and having to commute from hotel to venue and back every day. So something like a hotel with a sufficiently large meeting room, hotels and catering all day. And all of that ideally at a nice venue with some kind of park / outdoor area, not downtown at the city center. Yes, that will obviously come at a higher price tag than we're used to - but I'm confident we can get that covered between sponsors and sysmocom. Do you guys think this is a good idea? Or would you prefer the traditional ad-hoc approach at IN-Berlin? Regards, Harald -- - Harald Welte <lafo...@gnumonks.org> https://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)
