17:00:02 <pwaring> #startmeeting DC26 orga team meeting. https://deb.li/dc26meet
17:00:02 <MeetBot> Meeting started Tue Jan 13 17:00:02 2026 UTC.  The chair is pwaring. Information about MeetBot at https://wiki.debian.org/MeetBot.
17:00:02 <MeetBot> Useful Commands: #action #agreed #help #info #idea #link #topic.
17:00:04 <pwaring> #topic Roll call
17:00:07 <pwaring> as always, say hi if you're here
17:00:24 <DLange> say hi if you're here :)
17:00:30 <lenharo[m]> Hi! i'm here!
17:01:01 <billchenchina[m]> o/
17:01:40 <EnkelenaH[mds]> hi
17:01:52 <gwolf> o/
17:02:02 <tumbleweed> Hi
17:02:21 <martinbayo[mds]> Hello
17:03:00 <pwaring> #topic DC25: Videos
17:05:13 <pwaring> do we need to say anything on videos from DC25?
17:05:22 <tumbleweed> No news I'm afraid :(
17:05:36 <pwaring> ok we can carry it forward, no problem
17:05:38 <gwolf> Any expectation on action?
17:05:57 <gwolf> (of course, being us all volunteers and stuff... but we have pushed the point over several meetings)
17:06:16 <tumbleweed> at some point it has to happen
17:06:20 <tumbleweed> I'll shake the tree again
17:06:21 <santiago> o/
17:06:56 <gwolf> tumbleweed: not meaning to press you into anything, much to the contrary — maybe the item should be taken off the persistent questioning...
17:08:09 <pwaring> #topic DC25: Academic track
17:08:32 <gwolf> I just checked, from our last meeting to this one, we went from 6 to 7 published papers
17:08:35 <gwolf> (still missing 3)
17:08:48 <pwaring> ok, do we want to keep this on the agenda as well?
17:08:56 <gwolf> however, as rouca told us — we are just unfreezing from Winter vacations
17:09:10 <gwolf> well, it's easy to report, and at some point we want to say "it's done!" 😉
17:09:26 <pwaring> heh, ok
17:09:30 <gwolf> I'll want to talk with the (still not instated?) DC26 content team as to whether we want to repeat the stint
17:09:32 <tumbleweed> sorry, lost connectivity for a moment. I'll be back in a few mins
17:09:35 <gwolf> (I'm for it FWIW)
17:09:45 <pwaring> #topic DC26: Sponsors
17:10:07 <pwaring> we have five sponsors on the site so far: https://debconf26.debconf.org/
17:10:25 <EnkelenaH[mds]> and a gold one as of today
17:10:40 <santiago> dc26 website says CFP will be open on January 26th
17:10:55 <EnkelenaH[mds]> we'll update that soon
17:10:55 <DLange> optimistic website :)
17:10:58 * gwolf jumps with a small rush of joy 🙂
17:11:09 <gwolf> (due to the sponsor, not due to the CfP 😉)
17:12:15 <santiago> and sorry, that comment was about the "(still not instated?) DC26 content team", that needs to handle the CFP
17:13:16 <pwaring> #topic DC26: Bursaries and visas
17:13:19 <gwolf> santiago: I'll mail about kicking the Content Team back to life.
17:13:32 <pwaring> a few people have been asking about visas in between meetings
17:14:19 <gwolf> pwaring: we have advanced with the necessary information; yesterday I committed an updated page to dc26.dc.o/about/visas
17:14:29 <gwolf> (still not generated, but there is no real rush for it)
17:14:44 <gwolf> sorry, /pages/about/visas
17:15:04 <pwaring> ok sounds good
17:15:14 <pwaring> anything else we need to say on bursaries / visas?
17:15:16 <gwolf> (right now we are still showing information about Schengen)
17:15:24 <pwaring> (there is some bursary info on dc26)
17:16:12 <EnkelenaH[mds]> the info from martinbayo about the timing from university was useful
17:16:18 <EnkelenaH[mds]> if we could set a deadline to follow on that
17:17:27 <pwaring> by the next meeting? (27 Jan)
17:18:20 <EnkelenaH[mds]> their uni is on vacation until Feb, so maybe sometime in Feb
17:19:07 <martinbayo[mds]> The university resumes work in February; for more details on the invitation letters, we'll have to wait.
17:19:27 <pwaring> ok let's wait until the university is back then, we can keep the item on the agenda
17:19:40 <martinbayo[mds]> yep , may be mid frebruary
17:19:59 <pwaring> #topic Health policy
17:20:14 <pwaring> last time a health policy was being drafted
17:20:23 <gwolf> Right, we have to re-ignite work on that front!
17:20:47 <gwolf> We had an interesting work session in December; dc-committee members were invited
17:21:18 <gwolf> We are in the process of writing it (mostly, we came up with lots of points, and tumbleweed was combing it into coherent text)
17:21:20 * tumbleweed is back
17:21:30 <gwolf> but AFAICT it's still not ready to be widely circulated.
17:21:53 * santiago would like to point out that we need it for opening registration
17:22:15 <tumbleweed> I think it's basically ready, but the committee needs to sign-off on it
17:22:26 <gwolf> santiago: not necessarily IMO. But yes, would be good to have it ready.
17:24:25 <pwaring> #topic Meeting schedule
17:24:39 <pwaring> next meeting will be 27th January as we are still on fortnightly meetings
17:24:45 <pwaring> #topic AOB
17:24:48 <pwaring> anything else before we finish?
17:26:10 <santiago> the website also says "Opening attendee registration" happens January 26th
17:26:44 <tumbleweed> OK, so if we want to do that, we have lots of hoops to jump through
17:26:50 <santiago> there are different action items for that
17:27:21 <tumbleweed> Or we commit now to redesigning the registration to allow opening an initial registration now (to start visa & bursary processes) and come back to the rest in time
17:28:42 <tumbleweed> with the current registration process, we need to know t-shirt sizes, paid registration food and accommodation prices to open registration
17:29:01 <tumbleweed> typically you need to have a budget, to know those prices
17:29:38 <gwolf> we have several points where we have dependency circles...
17:29:39 <tumbleweed> we *should* also have: CfP, travel directions, and important-dates locked down, when we open registration
17:31:03 <DLange> people have been buying flights, so the dates are locked down
17:31:16 <gwolf> the conference dates are set, yes
17:31:17 <tumbleweed> I meant all the other important dates
17:31:26 <gwolf> but there are some "important dates" that are still somewhat in the air
17:31:36 <gwolf> or at least, in a best-effort-wish...
17:31:47 <gwolf> (such as January 26)
17:31:49 <tumbleweed> yeah, which is good enough
17:32:46 * tumbleweed -> phone
17:34:37 <pwaring> which path do we want to take then: 1. getting everythign ready using the existing flow. 2. redesigning registration flow (which requires time + volunteers)
17:35:19 <gwolf> who would be doing either 1. or 2.? :-]
17:35:35 <tumblingweed> Probably me
17:35:50 * gwolf sends a pack of spoons towards tumblingweed
17:36:11 <gwolf> hoping not to get an EUNROUTABLE...
17:36:15 <tumblingweed> I'm keen to do it
17:36:20 <DLange> so tumblew* should be choosing between 1 and 2, too
17:40:05 <DLange> tumblingweed is still discussing with himself :)
17:40:33 <gwolf> well, it's probably not a decision we need to have _now_
17:40:53 <tumblingweed> As I said, I'm keen
17:41:02 <gwolf> I think it is important for tumblingweed to push the work and have something _soon_, but which way... I'd let him decide off-meeting
17:41:37 <santiago> should we try to have volunteers to help you, tumblingweed? (I cannot commit myself)
17:41:46 <tumblingweed> I'll see if I can get the first bits done before the next meeting, and unblock registration
17:42:01 <tumblingweed> Review help would be good
17:42:04 <terceiro> tumblingweed: let me help you with it
17:42:18 <tumblingweed> Thanks!
17:44:27 <santiago> if reviewing is what you need, *maybe* I could help too
17:44:28 <gwolf> Any other other business for this meeeting?
17:45:15 <pwaring> ok, thanks everyone for coming and see you in two weeks!
17:45:20 <pwaring> #endmeeting