The dozen peeps have shown interest, not registered. I've created a Slack workflow for registering. Before publishing it a date has to be agreed upon.
This year the tickets will be in form of invoices that will be sent out prior to the event. Hopefully well prior. Reason for it being that some of the attendants from previous years haven't paid.
The dozen peeps have shown interest, not registered. I've created a Slack workflow for registering. Before publishing it [a date has to be agreed upon](https://k-space-ee.slack.com/archives/CDL9H8Q9W/p1730461267727519).
This year the tickets will be in form of invoices that will be sent out prior to the event. Hopefully well prior. Reason for it being that some of the attendants from previous years haven't paid.
artur
was assigned by rasmus2024-12-01 16:06:15 +00:00
rasmus
modified the due date from 2024-09-15 to 2024-12-132024-12-01 16:06:23 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
This event needs planning ASAP if you want to get a decent meal.
What would be the date?
combine the dinner with #115 perhaps? or would that be too much?
it'd be pushing it IMHO. hackathon doesn't need to happen in December, which is a hectic time anyway.
12 people registered in the slack poll https://k-space-ee.slack.com/archives/CDL9H8Q9W/p1729157795685999
The dozen peeps have shown interest, not registered. I've created a Slack workflow for registering. Before publishing it a date has to be agreed upon.
This year the tickets will be in form of invoices that will be sent out prior to the event. Hopefully well prior. Reason for it being that some of the attendants from previous years haven't paid.