17:00:19 #startmeeting 17:00:19 Meeting started Sun Aug 10 17:00:19 2025 UTC. The chair is joostvb. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:19 Useful Commands: #action #agreed #help #info #idea #link #topic. 17:00:31 #topic rollcall 17:00:36 o/ 17:00:52 Hello o/ 17:00:55 please say hi if you'd like to participate in this debian publicity team meeting 17:00:57 \o 17:01:03 hi 17:01:08 agenda is @ https://pad.debian.net/p/PublicityMeeting202508-keep 17:01:22 hi 17:01:39 hi 17:02:33 #topic welcome charles 17:02:45 o/ 17:02:45 recently Charles[mds] joined us as a new delegate 17:02:51 Charles[mds]: welcome aboard! 17:03:03 +1 17:03:11 thanks, glad to be here and help however I can 17:03:17 * AnupaAnnJoseph[m] claps 17:03:38 charles: as you've already been doing for quite a while! 17:03:57 👏 👏 👏 17:04:58 jipege1: you mentioned "Pub Team Sprint" : would you like to say something about that? 17:06:10 Yes I think we could organize a sprint between the delegates to share ou skils ont the publicity tasks 17:06:24 +1 17:06:30 We have to be versatile 17:07:07 I think it's a very good idea 17:07:12 good idea; guess next step would be to agree upon a date / setup a date planner? 17:07:31 and and know how to do all the basic tasks 17:07:50 Not yet 17:08:01 yes of course 17:08:02 jipege1: +1 so we can all do everything and cover for each other 17:08:12 exactly 17:09:19 #agreed Pub Team Sprint for skillsharing is useful for the team 17:09:21 and to know some tricks useful 17:09:44 given the the geographic distance, I assume we would do it online? Maybe one weekend? 17:10:49 Yes online 17:11:01 jitsi could work i guess 17:11:19 +1 17:12:12 The best could be to build a program + schedule and adjust the duration 17:13:47 ok. i could setup this date chooser website? 17:13:56 framadate iirc 17:16:10 #action joostvb setup a framadate to choose a date for Pub Team Sprint 17:16:20 you have framadate in storm.debian.net (if you prefer that one than framadate.org or other particular instance) 17:16:30 larjona: a yes, thanks 17:16:38 jipege1: could you take care of the schedule? 17:18:39 Yes . I will also prepare or revise some how-tos and we will see together if they are good and sufficient. 17:19:07 jipege1: merci! excellent 17:19:43 #action jipege1 prepare schedule, revise how-to's for Pub Team Sprint 17:20:07 if nobody objects, i'd like to start next item on agenda 17:20:17 no date too close please 17:20:32 jipege1: i'll offer a wide range 17:21:06 And please avoid point release dates. 17:21:12 Between DebConf and trixie release some of us are tired :-) 17:21:23 +1 17:21:44 sure sure, and of course everybody is always free to block some dates which don't suite them 17:21:48 After next point release then? 17:21:56 eventually we'll find a date we all can live with 17:22:10 :-) 17:22:53 #topic review on Publicity Team BOF at DebConf 17:23:16 jipege1: thank you for the extra slides, i'll commit them to git so these don't get lost 17:23:33 if i may say, i was pretty happy with our BoF 17:23:49 I'm really sorry I was absent 17:23:56 you were online 17:24:02 And sorry for the problems with audio during the BoF 17:24:13 and i believe you had a good excuse to not be physically there 17:24:53 Charles[mds]: iirc on the final video audio was pretty ok? hrm, maybe apart from the jipege1 videocall audio? 17:25:33 we had to change rooms last minute iirc, that made things a bit complicated 17:25:52 it was very choppy in my side 17:26:02 a ok... 17:26:15 I was referring to the audio return so jipege could hear us 17:27:45 AnupaAnnJoseph[m]: i was very happy about your statement on why debian people would want to make use of publicity team services, and what's in it for them 17:28:42 #link https://meetings-archive.debian.net/pub/debian-meetings/2025/DebConf25/debconf25-779-publicity-team-bof.av1.webm 17:29:17 anybody would like to share anything else on this debconf25 BoF? 17:29:50 Well, on the old News there was a good development and they are back online 17:30:10 Charles[mds]: a yes, let's discuss this later on the agenda, ok? 17:30:26 Mostly thanks to Jonathan Downland (hopefully I got it right) 17:30:30 Yeap 17:31:40 #topic review Debian 13 "trixie" release process 17:32:05 so, that was yesterday. there was cooperation with release-team, webteam 17:32:27 anybody would like to share thoughts on that? 17:33:38 For the website parts, I cannot build the site with the updated tags (12->13) until the News is published, because you need it published for the script for the mail 17:34:11 so I hope the news was committed a bit before, also because the images team finished the tests very quickly this time (many people testing) 17:34:22 and some mistakes on cloud and live images were found in the news item 17:35:21 as you reported here 6 and a half hours ago 17:35:52 I think we would benefit from a checklist like the release team has but only with our tasks 17:35:56 we were waiting for an explicit signal from the release team to publish the News 17:36:06 jipege1: I say commit, no publish 17:36:28 ok 17:36:34 so it's ready to build+publish quicker when it's the time for publishing 17:37:06 (and I am not sure that the release team needs to say green light, I guess that's something you decide, maybe in coordination with image media testing team) 17:37:08 larjona: you're talking about debian/webwml/english/News/2025/20250809.wml ? 17:37:15 yes 17:37:55 larjona: and you're waiting for a _final_ commit? 17:38:04 what do you mean? 17:38:44 larjona: you're waiting for the 20250809.wml to get published, right? 17:38:49 I have to wait until the News is shown in www.d.o 17:39:31 it _is_ now, at https://www.debian.org/News/2025/20250809 17:39:35 joostvb: This is about yesterday, there was a delay between release team saying go and the commit for News file. 17:39:35 then I commit my stuff, build and publish the change in all the tags (12->13, oldstable, etc) 17:39:47 AnupaAnnJoseph[m]: aha, tnx 17:40:05 larjona: you're saying it took too long this time? 17:40:43 What Laura said is that we can commit it to the repo when it is ready and not to wait for the release team. 17:40:44 not exactly, but as the images were ready very soon, there was a bit of breakage in the web, for 1h or so 17:41:23 so what Charles[mds] said: publicity team should get/make a checklist for us 17:41:33 +1 17:41:52 with clear indications who's waiting when on whom 17:42:49 I confess I didn't follow closely enough the time of the web breakage 17:44:27 #agreed there is a need for a checklist for the publicity teams tasks, for the debian 14 release 17:45:39 I can help with that, but will need Anupa's and jipege's help to fill the gaps 17:46:07 Ok, we can work on that. 17:46:16 jipege1: I can provide details later in private to clarify the timing 17:46:32 but overall I think it was quite good 17:46:46 #action charles AnupaAnnJoseph[m] work on a checklist for the publicity teams tasks, for the debian 14 release 17:47:55 larjona: about the cloud and live image errors in 20250809.wml : i can collect info & produce a patch 17:48:06 tnx for spotting that! 17:48:54 thanks 17:49:01 #action joostvb produce a patch for webwml 20250809.wml about errors in news on cloud and live image, as mentioned by laura 17:49:34 anybody would like to share anything else on the release process? 17:50:33 #topic Trixie Release Parties and Debian Day 17:50:47 we did some coverage on those 17:51:37 most release parties were yesterday, debian day is next weekend 17:51:38 We can do another for Debian Day this week, more parties on the way! 17:51:53 +1 17:52:27 +1 17:52:51 Usually we prepare a post on Bits for the Debian Day + link to the wiki page which brings together the events 17:53:13 +1 17:55:19 ok, next topic? 17:55:52 Is there a logo for Debian Day this time or an artwork? 17:55:52 #topic mastodon relay script and debian.net VM 17:56:00 AnupaAnnJoseph[m]: woops, sorry 17:56:15 AnupaAnnJoseph[m]: i'm not aware of anything, tbh 17:56:22 Ok 17:56:24 Anupa: I don't think so 17:56:33 Just the regular debian day logo 17:56:59 for 30th day we had some nice stuff, and i guess people worked hard to ask the right people for that 17:58:10 anyway... 17:58:22 phls: want to chime in on the VM and relay script? 17:59:13 Hey 17:59:18 phls[mds]: hi! 17:59:26 o/ 18:00:24 phls[mds]: anything to share on mastodon relay script and debian.net VM ? 18:00:45 The script running to send from micronews to mastodon is on a VM kept by me and Donald 18:01:31 I can keep the script there, or i can copy the files to you run in another vm 18:02:26 another vm would be preferable i guess; ideally it'd be a dsa managed vm 18:02:50 it seems more than useful to me 18:03:20 having the files in our repo on salsa would be good too 18:03:27 The vm is running pad.d.n, I also think would be better to split things 18:03:52 joostvb: +1 on salsa 18:04:03 I can copy to salsa, but there is a password 18:04:18 I will copy without the password :-) 18:04:20 we generally keep those on master.d.o, right? 18:04:44 AnupaAnnJoseph[m]: ^ ? 18:04:59 Passwords, yes. 18:05:01 We can also run from gitlab CI in the micronews repo 18:05:08 There is a package to be installed 18:05:22 I dont remember the name now 18:06:40 phls[mds]: anyway, thanks a lot for bringing this up, this is an important task to be done by us 18:07:53 sure 18:08:12 #agreed infrastructure for sending from micronews to mastodon should be moved to another vm, administered by publicity team (or dsa) 18:09:05 #agreed needed files for this mastodon service ideally on salsa, passwords kept on master.d.o 18:10:06 #agreed another option for sending-to-mastodon service: use gitlab ci 18:12:35 more thoughts on this, now? or better come back to this issue later? 18:12:49 All good 18:13:36 #topic Page listing DDs available for talks, interviews and the likes 18:13:49 Charles[mds]: ^ 18:14:29 This came up in this year Brazilian minidc. One person said they couldn't find a listing of DDs (and regular contributors) who would be willing to give talks about Debian 18:15:06 Ah, there was also a request for a podcast interview. 18:15:21 We said we would do it for the brazilian community, but seeing press@d.o, maybe www.d.o could also benefit from it 18:15:30 I believe there is or was a page listing DDs available 18:16:13 I know this one https://wiki.debian.org/CategoryDebianSpeaker 18:16:13 but people (Debian wiki users) should tag themselves, maybe you want to encourage them to use the tag in the wiki 18:16:27 there is https://wiki.debian.org/Presentations (but that seems old-ish) 18:17:57 one could always search the schedule for previous debconf's and related events, of course 18:18:02 Would be ok to add a link to the wiki in www.d.o? And do a roll call on debian-devel@? 18:18:42 Charles[mds] what do you mean a link to the wiki in www.d.o? 18:19:25 people looking for speakers generally are the ones organising an event. these generally do a public Call for Presentations / Papers 18:20:18 A paragraph in a page like "about us" or "contact us" saying there is a list of DDs available to give talks at the wiki 18:21:08 about interviews: formally that's part of the DPL's task list, fwiw 18:22:38 Charles[mds]: I am with joostvb, people in need of speakers know where to look at (www.d.o/events, https://wiki.debian.org/DebianEvents/ etc. Maybe link from https://wiki.debian.org/DebianEvents/ to CategorySpeaker) 18:23:05 that would be a useful link indeed 18:23:28 That would do it 18:23:32 cool 18:23:38 but that is not a decent list (yet)... maybe encourage people to use it with a micronews or a bits post 18:24:09 +1 18:24:28 +1 18:25:16 Charles[mds]: this works for you, right? then i'll continue with next topic 18:25:34 #topic www.d.o/News cleanup fallout 18:25:54 people are removing obsolete content from www.d.o 18:26:04 to make the website more maintainable 18:26:32 old news items have been removed, but are now hosted by a machine built by Jonathan Dowland at chronicles.debian.org 18:26:41 which is _truely_ _awesome_ imnsho :) 18:27:03 jmtd ftw 18:27:39 joostvb: it does 18:28:47 Charles[mds]: cool. would you like to add something about www.d.o/News maybe? anybody else? 18:28:52 And there are redirects to make old links keep working 18:28:58 yes there are! 18:29:57 #topic closing 18:30:04 anybody has anything else to share maybe? 18:30:26 There are still things to be done in there, so anyone wanting to help should check out https://salsa.debian.org/chronicles-team/chronicles.debian.org/-/issues 18:30:30 Forgot to add something during release process review. 18:31:00 But that's beyond the scope of publicity team (re:chronicles) 18:31:41 We are planning to post another Bits post about trixie with some statistics shared by https://fulda.social/@Ganneff 18:32:06 AnupaAnnJoseph[m]: nice! 18:32:39 Thanks to Aurélien for suggesting. 18:32:51 +1 18:32:54 (and i'm sorry i could do only so very very little during release) 18:33:46 we have the plan for the skill sharing; when do we want a next team meeting? or decide about that later? 18:36:03 ok let's first plan the skill sharing session 18:36:28 i guess we're done 18:36:36 \o/ 18:37:00 \o/ 18:37:16 #endmeeting