Bug 1070

this likely needs to be moved out a few months, potentially jan/feb or
even as a sub-conference / workshop at FOSDEM2024?

(In reply to Luke Kenneth Casson Leighton from comment #1)
> this likely needs to be moved out a few months, potentially jan/feb or
> even as a sub-conference / workshop at FOSDEM2024?

I'll note that i likely have conflicting plans in december (cousin getting married), so I think FOSDEM would probably work best.

Good idea, Luke and I talking about what might be possible for FOSDEM on Monday.  Can we have inputs please.

I suggest a stand, where we showcase some FPGA boards running a libre-soc core. Last time there was a ton of hardware related stands, all in one place. I even volunteer myself to be at the stand...

(In reply to Cesar Strauss from comment #4)
> I suggest a stand, where we showcase some FPGA boards running a libre-soc
> core. Last time there was a ton of hardware related stands, all in one
> place. I even volunteer myself to be at the stand...

That would be amazing, can we have something ready by then?
Hell even if it's only MicroWatt if libre-soc proper is not possible yet.

(In reply to Sadoon Albader from comment #5)

> That would be amazing, can we have something ready by then?
> Hell even if it's only MicroWatt if libre-soc proper is not possible yet.

it is.

do bear in mind the stands are a *lot* of work, 2 people, an entire
day, you get 400-500 people asking questions, there is almost no
sitting down! so we have to arrange a strict rota ok?

l.

Last night I booked train and hotels for James, Luke, Andrey Shriya and myself  to attend FOSDEM24 in Brussels.

This is our annual chance to meet up and the Friday will be available for communal activities.

We will travel out by Eurostar on the 1st Feb 2024 on the 11:04 train arriving 14:05 and return on the 5th Feb on the 14:52 train arriving back at 15:57 (all local times)

We all have individual rooms at the  ibis Hotel Brussels Centre Gare du Midi with showers and breakfast, and we will cover other food and subsistence.

Each room has two single beds so if we have additional attendees, assuming some of us are prepared to share, there would be accommodation available. (Nicholas etc.)

I have all the links to print tickets and I will distribute these nearer the time.

There is already a buzz of thinking about what we can do over the two show days and Luke is going to address whether we can get a stand, a development room, or speaking slots.  Thoughts to Luke please.

Luke and I are also addressing receiving a grant to cover out costs, which have been paid in advance.

David

i've submitted the stand request, thank you cesar and david.
used the one from last year.
https://git.libre-soc.org/?p=fosdem-stand.git;a=summary

tobias the 2go4.be hostels are pretty good and low cost when doing shared rooms.
they have two, i was at the one "City Center", they have a great shared
kitchen and breakfast room, with fridge cooker i stayed almost 3 weeks
once and loved it. just remember you are sharing with 4-6 other people
and friday night is pretty rowdy despite it "not being permitted to shout
when drunk and wake the entire floor up"...

https://pretalx.fosdem.org/fosdem-2024-call-for-devrooms/cfp

regardless of whether we have a devroom some talks would be a good idea.

(In reply to Luke Kenneth Casson Leighton from comment #8)
> i've submitted the stand request, thank you cesar and david.
> used the one from last year.
> https://git.libre-soc.org/?p=fosdem-stand.git;a=summary

May I suggest changing the Project Theme of the stand, as submitted, from "Multimedia and graphics" to "Hardware", or even "IoT"?

This way, we are more likely to end up being near potential users/contributors/sponsors, like Pine64, OpenEmbedded, Automotive Grade Linux, openHAB (smart home), etc.

Besides, I'm kind of a hardware/embedded guy, and enjoyed being around so many nice projects when I visited the AW Building on FOSDEM this year...

(In reply to Cesar Strauss from comment #11)

> May I suggest changing the Project Theme of the stand, as submitted, from
> "Multimedia and graphics" to "Hardware", or even "IoT"?

ah that was 2 years ago. i think this year i put in "hardware".

> This way, we are more likely to end up being near potential
> users/contributors/sponsors, like Pine64, OpenEmbedded, Automotive Grade
> Linux, openHAB (smart home), etc.

good call.

I was inspired by cesar's comment that we should have a demo, so, being somewhat bored in my spare time, I wrote a 3D game where you can place/remove blocks in a 3D world. it uses ray-casting through a 3D voxel lattice, and is entirely fixed-point-only. it runs at a few fps on microwatt on my orangecrab.

I pushed it to: https://git.libre-soc.org/?p=microwatt.git;a=shortlog;h=refs/heads/voxels_game
and: https://github.com/programmerjake/microwatt/tree/voxels_game

it doesn't use the fpga's usb connection since last time that was kinda glitchy, instead it uses a separate usb-serial dongle at 1MBaud.

Maybe we could change it to start out with "Libre-SoC" spelled out in blocks.

screenshot:
https://ftp.libre-soc.org/voxels_game_orangecrab/screenshot.png

.dfu file:
https://ftp.libre-soc.org/voxels_game_orangecrab/microwatt.dfu

readme:
https://git.libre-soc.org/?p=microwatt.git;a=blob;f=rust_voxels_game/README.md;h=9298383931171a3a2af5e9f9261954db7344e5cc;hb=96ea1a53696d78b4990f14ea708da48bbcbb81cb

(In reply to djac from comment #7)
> Each room has two single beds so if we have additional attendees, assuming
> some of us are prepared to share, there would be accommodation available.
> (Nicholas etc.)

I mean to attend, and am prepared to share, if someone would have me. Otherwise, I will just book another room at the same hotel, no problem.

I'm keeping my second bed in case Nicholas can join us and Shriya cannot share.

the others are James (unlikely), Luke and Andrey.

(In reply to Cesar Strauss from comment #14)
> I mean to attend, and am prepared to share, if someone would have me.

(In reply to djac from comment #15)
> the others are James (unlikely), Luke and Andrey.

I'm happy to share if you want to save on costs Cesar.


Also, sent the talk idea notes on the devlist after this evening's meeting:
https://lists.libre-soc.org/pipermail/libre-soc-dev/2023-October/005717.html

As an example, I created bug #1178 for the talk I'm planning to do.

(In reply to Andrey Miroshnikov from comment #16)
> I'm happy to share if you want to save on costs Cesar.

Thanks for having me, Andrey!

David, how can I pay you for my share? Can you inform the Hotel, so they will be expecting me? Can I get a breakfast option as well (I assume there is an extra charge)?

Thanks,
Cesar

It is a nominal additional amount and I (RED) will pay for it when we arrive.

cesar thank you for this, it is a good suggestion. especially because
talks can be in the wiki and a Makefile added.

https://lists.libre-soc.org/pipermail/libre-soc-dev/2023-October/005744.html

i did fosdem2021 in latex but forgot the Makefile, and also i realise
now, of course it is not in markdown so does not go in the wiki as
a page, it had to be a PDF link.

https://git.libre-soc.org/?p=libreriscv.git;a=tree;f=conferences/fosdem2021;hb=HEAD

idea: do small 5 min talks.
also do lightning on SV as precursor to bigger topics

we need to plan and action some announcements, a "call for papers",
and put both out on social media and appropriate mailing lists.
can i recommend this be discussed at the next meetings?

meeting TONIGHT at usual jitsi location 17:00 UTC.
https://pretalx.fosdem.org/fosdem-2024/cfp

writing and promoting the CFP is URGENT, there are only THREE WEEKS until
proposals close.

(In reply to Luke Kenneth Casson Leighton from comment #22)
> meeting TONIGHT at usual jitsi location 17:00 UTC.
> https://pretalx.fosdem.org/fosdem-2024/cfp
> 
> writing and promoting the CFP is URGENT, there are only THREE WEEKS until
> proposals close.

First draft CfP is on the wiki:
https://libre-soc.org/conferences/fosdem2024/fosdem2024_cfp/

Will be discussed and fixed up during the meeting before further dissemination.

(In reply to Andrey Miroshnikov from comment #23)
> First draft CfP is on the wiki:
> https://libre-soc.org/conferences/fosdem2024/fosdem2024_cfp/
> 
> Will be discussed and fixed up during the meeting before further
> dissemination.
Thank you to all the attendees, the CfP has been fixed up and updated.

Now waiting for a final review, and in about 4 hours should be ready to be distributed.



My plan is to send the CfP as an email to the LibreSoC dev mailing list.
Should I include the "libre-soc-devroom-manager@fosdem.org" email in CC for this?

(In reply to Andrey Miroshnikov from comment #24)
> 
> My plan is to send the CfP as an email to the LibreSoC dev mailing list.

Thank you all for the final checks and finishing touches.
I have submitted the CfP and should start thinking about proposals.
https://lists.libre-soc.org/pipermail/libre-soc-dev/2023-November/005790.html

On a recent email I was sent via the devroom-managers mailing list, I found out that we'll only get the first half of Saturday.

Also, the proposal submission site:
https://pretalx.fosdem.org/fosdem-2024/cfp
Only allows a 30 min time slot (no more, no less), so think about fitting your talks within 20-25 min (+5 min Q&A).


Those developing LibreSOC talks, once you've come up with material which is good to share, we can put it under the fosdem2024 directory on the wiki:
https://libre-soc.org/conferences/fosdem2024/

Updated comment #0, and looked at the Luke's corrections in the CfP.

I've made a bunch fixes based on your review Luke.

Order dates:
https://git.libre-soc.org/?p=libreriscv.git;a=commitdiff;h=19f2b9ff94a82c17b651d91981953c34d3d91dc6
https://git.libre-soc.org/?p=libreriscv.git;a=commitdiff;h=9cccb0dcaef7473b3df7073c2ebf5a9a86432e58
https://git.libre-soc.org/?p=libreriscv.git;a=commitdiff;h=9396c23215c59ef44d1a440b54197c8ee1d4aeb5

Add different time slots for talks back:
https://git.libre-soc.org/?p=libreriscv.git;a=commitdiff;h=cbba3e58a6619614f6280bed8e2df5805c8b1da8

Update submission section by making sure the right devroom is chosen.
Copied section on recording licensing from open hardware CfP (with attribution):
https://git.libre-soc.org/?p=libreriscv.git;a=commitdiff;h=4ac94b73227ce931edbc6bc3faccc0262c9cecf6
https://git.libre-soc.org/?p=libreriscv.git;a=commitdiff;h=acf5e5bc237b22252ffd5e0689c6d4eef9206680
https://git.libre-soc.org/?p=libreriscv.git;a=commitdiff;h=5a745c02672d31cc53ec271bc41b81aa4fbca106
https://git.libre-soc.org/?p=libreriscv.git;a=commitdiff;h=3fdfe4410faa05b4f7444b6b66274e146958acc8
https://git.libre-soc.org/?p=libreriscv.git;a=commitdiff;h=bb84c6fe83378f8e7b20d64e2fc287ac0214f49d

Change heading levels:
https://git.libre-soc.org/?p=libreriscv.git;a=commitdiff;h=5e8c6f694045b260e0ce139d09c4b7d3412c53c1
https://git.libre-soc.org/?p=libreriscv.git;a=commitdiff;h=186059dcabbb2403ae1f7bd338a3e0ad0f62c549

Move links section to the top:
https://git.libre-soc.org/?p=libreriscv.git;a=commitdiff;h=8a360c41d0541ee8dc80e276b8d1710c2522c099

Luke, you've also made a point of making the CfP shorter:
https://lists.libre-soc.org/pipermail/libre-soc-dev/2023-November/005791.html

Sections that might be worth cutting to reduce size:
- 1.2.1 "What is FOSDEM?" (Already have a link to the FOSDEM homepage and FAQ)
- 1.3.2 "Optional" (optional information regarding submission)
- First three bullet points in section 1.4 "Things to be aware of" (although probably better to leave this)
- Merge 1.5 "Important Dates" with the "key dates" at the top of the CfP

I don't know if we want to cut down the "Desirable Topics section", as that is what those interested will be looking at as guidance.


Please all have a look and make sure the formatting and content of CfP still looks good.
And let me know if you agree with cutting down and/or editing the above mentioned sections.
If you think there's a better way to word a section to reduce duplication, please let me know.


I will wait until Luke has had sufficient time to review before re-submitting (and apologising to the FOSDEM organisers for the confusion).

(In reply to Luke Kenneth Casson Leighton from comment #0)

> * DONE: plan and action call for papers
>   *(Luke has found errors in submitted CfP, needs to be corrected)*

(and did not say, "spam everyone with a 2nd copy of the CFP".
correcting the web version where the URL should have been at the top
is enough)

> * IN PROGRESS: Review corrected CfP, re-submit before 2023-DEC-01 DEADLINE
>   - TODO:
> https://git.libre-soc.org/?p=libreriscv.git;a=commitdiff;h=0a53d4274

more minor corrections needed.
See other CFPs. the URL web version of each is right at the top

(In reply to Luke Kenneth Casson Leighton from comment #27)
> (and did not say, "spam everyone with a 2nd copy of the CFP".
> correcting the web version where the URL should have been at the top
> is enough)
Ok, I won't send it out on the fosdem list again then.

> more minor corrections needed.
> See other CFPs. the URL web version of each is right at the top
Fixed:
https://git.libre-soc.org/?p=libreriscv.git;a=commitdiff;h=ee13d1134ace03a2824dfab06c9331b754faaa91


If this CfP is good to go Luke, can we make further posts about it?
I can make a post on Linkedin (as a LibreSOC member).

(In reply to Andrey Miroshnikov from comment #25)

> 
> On a recent email I was sent via the devroom-managers mailing list, I found
> out that we'll only get the first half of Saturday.

ah. ok. well that is still great.

> Also, the proposal submission site:
> https://pretalx.fosdem.org/fosdem-2024/cfp
> Only allows a 30 min time slot (no more, no less), so think about fitting
> your talks within 20-25 min (+5 min Q&A).

hmmm hmmm we can potentially do a pair of short libresoc talks.

20 mins. 5 mins QA. 5 mins *changing to the next person*.



> Move links section to the top:
> https://git.libre-soc.org/?p=libreriscv.git;a=commitdiff;
> h=8a360c41d0541ee8dc80e276b8d1710c2522c099
> 
> Luke, you've also made a point of making the CfP shorter:

looking at the others i thi k it's fine.

i'll mention that dec 1st isn't the deadline:
https://lists.fosdem.org/private/devroom-managers/2023-November/003204.html
>> Is it mandatory the CfP end in 2023-12-01? Or can we go until 10?
>> As said here before, the CfP page has this date.
> 
> I've attempted to remove that, as the requirements for each track vary, and in
> practice we don't stop people making late submissions.

created: https://discourse.llvm.org/t/fosdem-cfp-call-for-participation-libre-soc-fpga-and-vlsi-at-fosdem-2024/74839?u=programmerjake

sent: https://list.libresilicon.com/hyperkitty/list/libresilicon-developers@list.libresilicon.com/thread/L636DCWEL35AW7MQURTTQBGSQFUGFGCS/

reminder to everyone (including myself) we have 10 days to the submission
deadline.

please raise bugreports and put them into comment #0 replacing "bug #TODO".
also i have modified "leave it up to eople to decide" to "we WILL use
latex beamer, see examples already in the wiki". anything too "complex"
take screenshots convert to images and commit those as well, but keep them
LOW RESOLUTION (no 100mbyte RAW images), absolute maximum resolution 1280x720.

ASSUME A 1280x720 PROJECTOR RESOLUTION but 800x600 is better.

I want to do a talk about gram and my FPGA work. Mostly my work on ls2 using the OrangeCrab. At the end I want to introduce a small hobby project of me which uses the ICE40 for Lighthouse Tracking in Virtual Reality. I few years I did the following talk: https://media.libreplanet.org/u/libreplanet/m/the-librevr-project/

(In reply to Tobias Platen from comment #34)
> I want to do a talk about gram and my FPGA work. 

great, please raise a new bugreport and then also submit
on the new fosdem pretalx, we only have 8 days left.

I have submitted a talk for demoing how to write SVP64 code using the pypowercim C glue code that I developed. I will demo the chacha20 and other SVP64 code that I wrote.
I will not go into detail of the SVP64 code and features much, just how integrating normal C and pypowersim can work to reduce runtime by orders of magnitude.

https://pretalx.fosdem.org/fosdem-2024/talk/review/7XKH3XHNHWBQ3H78CFX8GB9WRCTMMXLJ

Konstantinos Margaritis

https://lists.libre-soc.org/pipermail/libre-soc-dev/2023-November/005799.html

(In reply to Luke Kenneth Casson Leighton from comment #0)

> Proposed talks. The numbers I assigned to the talks were done in the order I
> wrote them, actual order will likely change (except for the overview and
> round-off talks).
> 
> Live talks:1
> 1. bug #TODO  Overview of LibreSOC - Andrey?

> Pre-recorded:
> 2. bug #TODO    Introduction to PowerISA and SVP64 (with ISACaller demo?) -
> Andrey

andrey which two bugs have you raised and when will you be editing comment #0
to make note of them so that everyone can keep track of what is happening?

External submission:
"Cologne Chip GateMate FPGA -- filling a gap between hardware and software (with a presentation of the GMM-7550 module)" by Anton Kuzmin
https://pretalx.fosdem.org/orga/event/fosdem-2024/submissions/XGM7SV/

(In reply to Luke Kenneth Casson Leighton from comment #37)
>
> andrey which two bugs have you raised and when will you be editing comment #0
> to make note of them so that everyone can keep track of what is happening?

andrey thnk you o much for doing that during today's meeting
https://libre-soc.org/meetings/sync_up/sync_up_2023-11-29/

reminder, comment #0 basically is our "canonical communications point",
so can contain *private* links that make *our* job as devroom managers
easier ok?

(In reply to Luke Kenneth Casson Leighton from comment #0)

> 6. bug #TODO      Advanced features of Data-Dependent Fail-First - Luke:
>    + How can be used with link list tracking
>    + strncpy example

https://pretalx.fosdem.org/orga/event/fosdem-2024/submissions/SEJUPE/#

Draft schedule link, needs some thinking:
https://libre-soc.org/conferences/fosdem2024/fosdem2024_schedule/

Email:
https://lists.libre-soc.org/pipermail/libre-soc-dev/2023-December/005804.html

https://github.com/marcusmueller/fosdem-submissions-getter/blob/main/getsubmissions.py

let's use this to manage submissions and autogeneratw
the schedule

(In reply to Andrey Miroshnikov from comment #41)
> Draft schedule link, needs some thinking:
> https://libre-soc.org/conferences/fosdem2024/fosdem2024_schedule/
> 
> Email:
> https://lists.libre-soc.org/pipermail/libre-soc-dev/2023-December/005804.html

QN: how *on the proposed schedule* do you get to this page
and to the mailing list?

https://pretalx.fosdem.org/orga/event/fosdem-2024/schedule/export/

full export capability.


Start
When the talk starts, if it is currently scheduled
 

End
When the talk ends, if it is currently scheduled
 

no more hand-writing of schedule markdown tables please.
write a program that *generates* the markdown and edit
the schedule *in pretalx* and re-run the autogenerator

(In reply to Luke Kenneth Casson Leighton from comment #36)

> https://pretalx.fosdem.org/fosdem-2024/talk/review/
> 7XKH3XHNHWBQ3H78CFX8GB9WRCTMMXLJ
> 
> Konstantinos Margaritis
> 
> https://lists.libre-soc.org/pipermail/libre-soc-dev/2023-November/005799.html

konstantinos this is a great talk (just read the abstract) however as the
abstract will be public can you please update it to be factually representative?
thanks in advance.

i totally get the advantages of the approach, however it is complementary
to existing techniques (DMI+JTAG interface i developed and used to test the
FPGA and verilator), as well as the qemu VM technique developed by
Lauri Kasanen, so the abstract should be representative and recognise that
this is a complex extremely comprehensive project to which you have
contributed.

(In reply to Luke Kenneth Casson Leighton from comment #45)
> (In reply to Luke Kenneth Casson Leighton from comment #36)
> 
> > https://pretalx.fosdem.org/fosdem-2024/talk/review/
> > 7XKH3XHNHWBQ3H78CFX8GB9WRCTMMXLJ
> > 
> > Konstantinos Margaritis
> > 
> > https://lists.libre-soc.org/pipermail/libre-soc-dev/2023-November/005799.html
> 
> konstantinos this is a great talk (just read the abstract) however as the
> abstract will be public can you please update it to be factually
> representative?
> thanks in advance.
> 
> i totally get the advantages of the approach, however it is complementary
> to existing techniques (DMI+JTAG interface i developed and used to test the
> FPGA and verilator), as well as the qemu VM technique developed by
> Lauri Kasanen, so the abstract should be representative and recognise that
> this is a complex extremely comprehensive project to which you have
> contributed.

It is factually representative, I claim nothing which is untrue. It is impossible at the moment to test SVP64 instructions on FPGA, so I'm not even touching that topic. And before you can even start testing user-space software you would have to enable kernel support for SVP64, the actual CPU, the board, fix the bootloader, before you can even start testing stuff like DCT or crypto. So, in the case of finding potential problems with instructions, or even other possible optimization opportunities, it might mean lost time in board upbringing. I'm not demeaning the project, I'm just mentioning hard facts.

I could actually rephrase that it *will* actually be complementary to JTAG on FPGA, when an FPGA implementation is available, but until that happens, my method is *currently* the only usable method to test SVP64 integration with user-space software.

Rephrased:

"LibreSOC's SVP64 is an interesting concept, with many novel ideas but it's an experimental ISA. There is no hardware yet and current Microwatt FPGA support does not include the new SVP64 instructions. There exists a full heavily developed Python simulator that defines and implements SVP64, but how does one actually test user-space code like DCT, Crypto algorithms like Chacha20 or C Library String functions? Running the unit tests can take quite a long time."

final rephrase:

"LibreSOC's SVP64 is an interesting concept, with many novel ideas but it's an experimental ISA. There is no hardware yet and existing FPGA support does not include the new SVP64 instructions. There exists a full heavily developed Python simulator that defines and implements SVP64, but how does one actually test user-space code like DCT, Crypto algorithms like Chacha20 or C Library String functions? Running the unit tests can take quite a long time."

(In reply to Konstantinos Margaritis (markos) from comment #46)

> It is factually representative, I claim nothing which is untrue. 

yes, you do.

> It is
> impossible at the moment to test SVP64 instructions on FPGA,

false.

you're not taking the time to understand and correctly represent the facts.
given this and the lack of empathy shown on the mailing list plus the statement
that you do not intend to spend the time to make proper representation of the
facts i am not approving your talk as your aggressive attitude will cause
more harm than good.

that is therefore a violation of the Libre-SOC Charter that has to be taken
seriously. if you recognise that and can apologise then your talk, which
otherwise technically i know will be absolutely superb, can go back on the
list.

Saturday schedule:
https://fosdem.org/2024/schedule/day/saturday/

(Comment #0 also updated.)

i've asked everyone to make certain that their PDF is ABSOLUTE MAXIMUM
1280x800 and preferably 800x600. larger images and resources can be
*referred* to and uploaded to either the FOSDEM system (or to the
libre-soc FTP site if absolutely necessary).

https://lists.libre-soc.org/pipermail/libre-soc-dev/2023-December/005892.html

direct messages have gone out to the two non-libresoc contributors,
this is one example:
https://pretalx.fosdem.org/orga/event/fosdem-2024/mails/6479/

i've just heard back from seth hilbrand, the talk that was considering
moving to our room has confirmed they're happy to do so, so out of
courtesy we need to... how-to-say... "make that happen"? :)

my talk is 12:50 to 13:20 which is... 30 minutes. i don't need 30
minutes, it can be cut down to... 20 possibly even 15 total (10 talk
5 questions).

https://pretalx.fosdem.org/orga/event/fosdem-2024/submissions/CSNVEU/reviews/?

apologies i looked at the abstract (and your review, andrey)
and it is just not the case that there are very few FOSS
companies.

this talk would be viewed with... puzzlement and we need the
space for 3 other non-Libre-SOC plus my talk which i just
cut from 30 to 15 minutes in order to bring in another one
that we were waiting to move rooms (done, comment #52)

an extra 5 mins to each of the verilog, ddffirst, openVLSI and
FPGA Cologne board would be very sensible, although i can likely
do with just 15 mins if necessary.

ok i just completed some minor shuffling,
https://fosdem.org/2024/schedule/track/libre-soc-fpga-and-vlsi/

i put james' talk at 15 mins back-to-back with the 2nd one
rather than shorten it, and extended 3 by 5 mins but still
leaving a 5 min gap between all.

unless a really good reason this needs freezing to give
people time to do their talks at a known length.
i have however no idea how to do that!

bug #1244 - Data Dependent Fail First, Luke & Shriya
-strncpy

(In reply to shriya.sharma from comment #56)
> bug #1244 - Data Dependent Fail First, Luke & Shriya
> -strncpy

thank you shriya, i justt edited comment #0 to add it.

I'll arrive on Brussels Midi train station by Eurostar coming from Schiphol Airport on the 1st Feb 2024 at 17:08, going directly to the ibis Hotel Brussels Centre Gare du Midi. I'll send a message on arrival. Hoping we can meet somewhere and have diner together. 

My return is on 5th Feb on the 16:52 train to Amsterdam Centraal.

(In reply to Cesar Strauss from comment #58)
> I'll arrive on Brussels Midi train station by Eurostar coming from Schiphol
> Airport on the 1st Feb 2024 at 17:08, going directly to the ibis Hotel
> Brussels Centre Gare du Midi. I'll send a message on arrival. Hoping we can
> meet somewhere and have diner together. 
> 
> My return is on 5th Feb on the 16:52 train to Amsterdam Centraal.

ok Cesar - Rita Madsen would be interested to meet people, she
is doing a PhD on the social interactions of FOSS projects.
https://lists.libre-soc.org/pipermail/libre-soc-dev/2024-January/005987.html

what fun, we inadvertently triggered a bug in the toml parser, which I just now reported:
https://github.com/uiri/toml/issues/438

as a workaround, don't put spaces between the date and the `}`

(In reply to Jacob Lifshay from comment #60)
> what fun, we inadvertently triggered a bug in the toml parser, which I just
> now reported:
> https://github.com/uiri/toml/issues/438
> 
> as a workaround, don't put spaces between the date and the `}`

turns out spaces are ok, as long as you also have spaces around the `=` before the date.