16:00:46 #startmeeting Debian Publicity Team January2025 agenda: https://deb.li/5N8c 16:00:46 Meeting started Wed Jan 8 16:00:46 2025 UTC. The chair is DonaldNorwood[m]. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:46 Useful Commands: #action #agreed #help #info #idea #link #topic. 16:00:58 #topic Roll Call 16:01:06 Hello o/ 16:01:08 Hi 16:01:24 Hi (phew, made it) 16:01:28 hi o/ 16:01:31 Hi! 16:02:00 o/ 16:02:30 Hi 16:02:38 ok 16:02:46 #topic timing 16:02:58 I have a timer sitting next to me so we can try to keep within 5 to 10 minutes per topic. I'll send a reminder ping at 3 and at 7 minutes. If no topic gets a response in 1 minute we close it and move to the next topic. 16:03:12 Lets start. 16:03:20 #topic Do we want a meeting every month or every 2 months? 16:03:36 every month 16:03:39 +1 for every month. 16:03:43 a meeting every month? 16:03:44 +1 16:03:51 I think if we can close a lot of points here we can do a monthly. 16:03:53 yeah I think more frequent meetings are better 16:04:34 next topic? :) 16:04:43 That is 6 for monthly. 16:04:52 7 :-) 16:04:59 #action We will have a monthly meeting 16:05:03 We beat the timer! 16:05:07 lol 16:05:10 #topic Review of the tasks assigned to team members 16:05:25 matrix: https://salsa.debian.org/publicity-team/todo/-/blob/main/tasklist.md 16:05:37 I think everyone is okay with their areas? Any changes wanted? 16:06:15 Moving on. 16:06:18 #topic Continue updating our publishing and procedures 16:06:26 Style guide is happening. 16:06:30 everything under my name seems alright (though I should get back to interviews) 16:06:39 oo style guide! 16:06:41 I'm missing the entry "Delegated tasks" for Anupa. 16:06:42 Sorry, holding the topic. Go on. 16:06:43 No change, just another point of view could be usefull wath are we doing togetehr ? 16:06:56 I should have given a minute read. 16:07:01 not each of us , 16:07:29 AndreasTille[m]: I will update after the meeting 16:07:49 Delegated task for Anupa +1 16:08:02 collective responsibilites at the top would be nice 16:08:06 jipege1: What do you mean? 16:08:08 Ah ok. 16:08:11 +1 16:08:41 disaster2life: +1 for collective responsibilities at the top 16:08:46 I normally just put (team) next to something but I agree a different style of showcasing would be ideal. 16:08:50 I tink it's just the meaning of team 16:09:06 Anyone care to volunteer to update it? 16:09:35 I can 16:09:47 then I can learn better the team's tasks 16:09:53 #action Charles to update the team matrix 16:09:55 it is not only an addition of individual tasks 16:10:03 charles: applause! 16:10:06 Next topic? 16:10:26 #topic Continue updating our publishing and procedures 16:10:41 I mentioned the Style Guide is still coming along. 16:10:53 jbr: Anything to add there? 16:11:06 not really 16:11:13 Perfect 16:11:36 I have a question, where can we journal? We don't do bits from the team or anything. 16:11:52 As in where can we keep a log of team work? I tend to use the todo repo for stuff. 16:12:05 I can start another 'housekeeping' directory in it. 16:12:06 Thoughts? 16:12:40 that would be nice I think, a place to write down stuff more persistent than here 16:13:14 Ok, with no further discussion I can action it to myself. 16:13:32 Perhaps a place for internal work (public of course) in the main reposit 16:13:51 #action Start team journal donald 16:14:27 It can stand in the main repo but I've been moving things around a bit there, so maybe not so much.... we can talk more on it later. 16:14:30 I think we could use more our mailing list to discussion 16:14:55 (3 min) 16:14:59 oh actually yeah the mailing list 16:15:24 +1 for ML 16:15:27 I think that would be easy enough to have everything updated here and would give a space for everyone to be updated 16:15:28 What I would really welcome if any new member would write some short intro. 16:15:42 Any team I know is requesting this. 16:15:48 it's the thing I can keep more up to date 16:15:59 +1 16:16:03 yeah mailing list is really efficient for this I believe 16:16:10 AndreasTille[m] short intro for what? 16:16:15 Just showing up on some task list without intro is a bit strange for other team members 16:16:43 depends if they would want to stay for longer or just quickly fix sth 16:16:45 oh for all the tasks? yeah that would be much more accessible 16:16:58 If someone is joining a team than write some short text who the new member is, what skills and what plans to do. 16:17:38 oh, not what I thought, but yeah, I think that would depend on whether they are here for the long term or a quick fix 16:17:48 gsz: If someone is listed on the tasks list that seems more than a quick fix. 16:17:57 (1 min) 16:18:02 sure 16:18:16 I think someone popping in would like to see whom to contact, is the way that I viewed it. 16:18:38 So they were not shouting into the wind and hoping for an echo back. 16:18:48 We can come back to this one, next topic. 16:18:54 yeah that makes sense to me 16:19:05 #topic Create a schedule to note our important deadlines. 16:19:35 This lines up with the prior topic, we can send out an email each start of the month with dates. 16:19:50 Or use event.d.n when it is mature. 16:20:32 dates for important stuff within the month to write up posts / stuff for? 16:20:52 Yes and anniversaries, etc ... 16:20:57 what are the things that have an important deadline to us? 16:21:23 Point releases and upcoming events mainly. 16:21:28 I think Just a simple file will be enought 16:21:37 We miss things sometimes because it is not on everyones radar. 16:21:46 I can think of point releases, anviersaries, debconf, minidebconf dates 16:22:04 I remember AndreasTille[m] mentioning some terminal calendar utility from a previous meeting, that seemed neat 16:22:13 jipege1 (IRC): I tried that with the todo file but not many read/use it. So I think another method would be better to use. 16:22:32 charles (IRC): exactly! 16:22:35 since it's mainly "stable"-ish, I think a every 3 months or every 6 months easier on us 16:22:41 Une simple lime plate suffira 16:22:57 Just a simple flate file will be enought 16:23:11 or a simple file too 16:23:25 We put it on salsa and place the link in this channel topic? Good solution? 16:23:25 and we could send it or a reminder in the ML 16:23:33 DonaldNorwood[m]: yes! 16:23:44 Ok. 16:23:46 yes 16:23:50 Who wants it? :) 16:23:51 +1 16:24:00 +1 16:24:08 +1 16:24:43 (closing in 1) 16:24:44 I can do that. 16:24:54 perfect! Thank you AnupaAnnJoseph[m] 16:25:09 #action AnupaAnnJoseph[m] Flat file calendar 16:25:27 #topic How much lead time do we really need for items that are not going out immediately? 16:25:54 How much time do we need for edit, review, and translation of items? 16:26:07 As in what is a realistic lead point for us to get something out? 16:26:44 is between 1 and 2 weeks a realistic from experience? 16:26:44 I mean, when I am translated my last article to Hindi, on and off it took me 2 days to finish up I believe 16:27:01 I think translation is not really publicity job there are other teams dedicated to translation 16:27:39 4 days avg from charles and disaster seem reasonable. 16:27:51 This is just to give us an idea not a forced deadline. 16:27:54 translation isn't our work but we should still know how much time to give the translation teams (should we ask them a mail and ask them?) 16:27:55 jipege1: agree, but having a few days to translate and publish together would be nice 16:28:26 so I would like 1 week for editing and then1 week for review and trasnlations, then we publish 16:28:27 Our job is to mobilize the translation teams and warn them 16:28:29 Yes, we are on the same page. Translation is still a part of the process because we wait for that team a day or so then publish regardless. 16:29:13 2 days for (initial) translating is ok 16:29:28 For example for each release with have just 2-3 day left to translate 16:29:45 Could we say including the translation wait will be 7 days? 16:30:13 (5 minutes mark) 16:30:31 DonaldNorwood[m]: yeah 16:30:31 no sometime we msut be more reactive 16:30:49 I mean this is for non essential articles yes? 16:31:03 Non critical stuff, correct. 16:31:04 well "essential" is a bad word, time sensitive 16:31:52 Some time, It's not dramatic to publish the translations with a few days of delay 16:32:16 Lets hold at it takes us 7 days to turn something around fully with translations. Any objection? 16:32:26 (3 minutes mark) 16:32:52 I'd say (for this non-time sensitive), we could announce it's ready for review and give 4/5 days for reviews and translations 16:32:53 I think thats reasonable jipege1 but I think thats more a case by case situation, whereas I think I would prefer most articles going out with translations even if it delays the process a bit 16:32:54 Yeah, articles with strict deadline needs to be published without further delay. 16:33:10 AnupaAnnJoseph[m]: +1 16:33:45 hmmmm 16:33:56 and l10n teams workwork at their own pace... 16:34:09 But for others I say we can publish the articles if we have 2-3 translations and add others later as they come. 16:34:13 Should we really wait for 7 days to get all the translations? 16:34:46 Ganneff (IRC): We arent waiting, we tend to be 3 -4 days, but it seems it takes a day or some from them. 16:34:59 opps, AnupaAnnJoseph[m] 16:35:08 Yeah, OK. 16:35:18 This one is going over the limit, 2 extra minutes. 16:35:45 I mean, I would take the osm article for example since thats in recent memory, I think that going out even a week after it did, it would have still been as relevant and a week earlier 16:36:09 True. 16:36:12 sorry, I don't think we strictly need to wait for translations to arrive. We just announce that the item is ready for review (from ourselves) and then wait 4 days for these reviews 16:36:37 then l10n teams can have the same time as reviewers to translate 16:36:38 2 days and you have a yes from me. 16:36:53 (again non critical items not included) 16:36:55 charles yeah sure thats reasonable I guess 16:36:59 (since it's supposed to have only small-ish after is ready for review) 16:37:23 Out of time on this one. Lets just call it at a 4 day standard. 16:37:25 can be 2 days too 16:37:38 forget, 4 is awesome! 16:37:41 :-) 16:37:46 haha 16:37:56 cool enough Id say 16:38:07 #topic Reminder: Next point release of Debian 12.9 is 2025-01-11 16:38:17 For the official nnounce we can't wait??? 16:38:25 wait... 16:38:32 Just a reminder. 16:38:42 oh release in 4 days 16:39:03 #topic Set up authors and deadline date for the DPN/DPB 16:39:04 that fell between the memory couch cushion 16:39:07 The announce is on the repo since this morning 16:39:16 disaster2life: yeah! The announcement is already in the repo 16:39:31 The SUA went out yesterday I think as well. 16:39:48 On this topic, I suggest we table it until the next meeting after this DPN goes out. 16:39:51 yeah I remember the email 16:40:26 (closing in 1) 16:40:52 May I know what was the topic for that mail? 16:41:10 I meant Subject line. 16:41:15 let me check- 16:41:24 [SUA 262-1] Upcoming Debian 12 Update (12.9) 16:41:47 Ok, Thank you! 16:41:50 https://lists.debian.org/debian-stable-announce/2025/01/msg00000.html 16:42:07 Next topic. 16:42:15 Thank you jbr and DonaldNorwood[m] 16:42:24 #topic Review procedures for monitoring point/release announcements 16:42:38 Do we need a review here? The process seems to work well. 16:42:45 We are kind of already on that topic. :) 16:43:29 Yes : I'll do the job assisted by anupa for this relaese 16:43:46 \o/ 16:44:05 I guess I can ask since we were talking about the translation teams, do they start when the repo is updated or when we send it to them? 16:44:25 jipege1 (IRC): action is please. :) 16:44:29 *it 16:44:51 (closing in 1) 16:44:59 I think when they see the email to d-stable-announce 16:45:17 sorry I meant DonaldNorwood[m]: ^ 16:45:25 (test) 16:45:34 I know. Makes sense. 16:45:42 Maybe we should reach out to ask them? 16:45:58 seems reasonable 16:46:18 I can take that task 16:46:27 #action Ask translation teams when they start translations for announcements @charles 16:46:34 Next topic 16:46:48 #topic Increase cooperation with the which teams? 16:47:04 Good timing on this one. 16:47:35 So we have a reach out to the translation team, any other teams we can focus on expanding a relationship with? 16:47:59 In this same topic, I skipped a point which was: Clarify our relationship with webwml/release teams. Ask where exactly we are needed; do we need to be at the forefront of releases at this point? 16:48:30 Planning for 12.10 started and we have been asked for our availability. 16:49:29 The release team is very good about reaching out to us and the multiple teams involved. 16:49:40 Yes it"s our job to publish the announcement on web and on mail list 16:50:26 Does anyone recall the conversation that was started in this channel about us not doing the announcement? I think the topic was around the timing between the email, website update, and other postings. 16:51:24 (closing in 1) 16:51:50 DonaldNorwood[m]: was it about waiting for the cd-images being updated before publishing the announcemens? 16:52:06 Yes if I recall correctly. 16:52:26 no perfect outcome for that one :-( 16:52:52 Might be a larger discussion perhaps better had with team cc'd emails. 16:53:02 I think we have to do our job WITH the web team especially because we don't have to act deirectly on the web server 16:53:41 DonaldNorwood[m]: we can't delay to much because people we see the archive update, but if it's too early people won't be able to get CD-images to install it 16:54:17 jipege1 (IRC): We work on the web server when we stop the cron jobs and update. 16:54:52 charles: Yes, it was around that timing. The release goes out in stages. 16:55:10 Is iIs it really difficult for you to work with an t really difficult to work with anothe team ??? 16:55:17 I don't recall the exact discussion, but thought to bring it up in case we needed to discuss it. 16:56:01 Pardon? 16:56:24 Is it really difficult to work with another team ??? 16:56:37 (1 minute) 16:57:10 I think we work well with other teams. I may not be understanding. 16:58:03 I don't think the CD-images is that important for now, so let's just move it to the next meeting 16:58:11 (closing for further discussion) 16:58:18 #topic Reporting back to the project about our email, web, and social media reach. 16:58:19 In the relaese process, it' release team that sets the pace 16:58:53 jipege1: if I understand correctly the problem is the interaction about Webmaster and us? 16:58:58 +1 jipege1 17:00:05 I think that now there no more problem to work together. 17:00:21 I think we can work together with the Webmasters team for release announcements. 17:00:39 Do we need to release reach or stats? Is there interest in compiling that data? 17:01:20 DonaldNorwood[m]: Do you have that data? 17:01:20 I think I would be interested but thats personal curiosity, don't really think the numbers really matter *that* much 17:01:21 ( 1 minute) 17:01:32 I have collected some. But not monthly update. 17:01:54 AnupaAnnJoseph[m]: That data needs to be pulled to share. 17:02:02 (you typed as I was) 17:02:16 This is our subscriber status as of now. 17:02:16 Mastodon (bot): 13K followers 17:02:29 LinkedIn: Debian group (private listed): 1,385 members 17:02:29 Debian Administrator group: 9,985 Total members 17:02:44 We are almost 10K members in Debian Administrator group now. 17:02:58 Twitter/X (bot): 287.2K Followers 17:02:59 Very nice. 17:03:51 Fedi should be bigger I think- weird it is not honestly 17:04:05 I think we can pull every 4 months or so, I do not think we need a tight metric. 17:04:05 Apropos Twitter/X: It might be worth discussing whether Debian wants to stay on X or not. 17:04:22 Perhaps we will have to ask ourselves questions about our presence on 17:04:43 We relay Micronews to Fediverse and Twitter/X. 17:05:12 Twitter/X and LinkedIn are the largest audiences we reach and where most of the IT readers consume information. 17:05:14 AndreasTille[m]: you are too fast (or I'm too slow) 17:05:20 There was a discussion about a Discord group, not aware of it's status now. 17:05:33 its* 17:05:51 Discord is there, but separate for later as an update 17:05:54 yeah I personally am not that strong on the Twitter presence, but also given its status as the biggest platform, its good that it is there? 17:06:10 Donald Norwood I know the role of X - but I also know our ethical principles and I'm sensing a conflict 17:06:25 honestly, I feel like this is a discussion for the mailing list because it's complex and has a broader scope than only publicity team 17:06:39 This is a much much larger discussion than we can have here. 17:06:58 but I acknowledge the concern of publishing to twitter, linked in and the likes 17:07:04 charles: Yes! Definitely. I just said "might be worth discussing" 17:07:08 (1 minutes mark) 17:07:27 AndreasTille[m]: fair, I missed that 17:07:30 starting on the mailing list might be good then 17:07:52 It would need be a project email I think.... next topic. 17:07:55 ​ 17:07:55 #topic Our new markdownlint procedures and how it can assist the team 17:08:04 charles (IRC): ? :) 17:08:21 so I guess it's on me 17:08:31 I did send a very long email the other day 17:08:33 The floor is yours. 17:08:44 Want to close on that? 17:08:45 explaining the hows and whys 17:09:04 and I have a pending email to respond on the ML 17:09:08 https://lists.debian.org/debian-publicity/2025/01/msg00002.html 17:09:45 from jipege1 17:10:02 though my main idea is to make it easier on us and newcomers 17:10:30 I have to say I have had way less time than I would like though 17:10:36 I like the new tools very much. 17:10:55 now, did you guys have the time to read and/or have questions or feedback? 17:11:05 if not, we can move on to the next topic 17:11:11 #topic Information about rally.d.n. and cryptpad.d.n (testing/not announced) 17:11:37 I intend to make a detailed response after the next point release. 17:11:43 rally.d.n was moved from one VM to another and is up and running. phls_ (IRC) did the install of it. 17:11:49 jipege1: ack and thanks 17:11:49 oh theres a debian instance for cryptpad now? 17:12:11 There is some feedback on it so we can update it to work easier and make sense for everyone. 17:12:31 phls \o/ 17:12:40 The cryptpad.d.n. was also moved from one VM to another. It is not up and running. Probably later this week if I have more time. 17:13:12 (1 minute) 17:14:15 #topic The idea to create a place where Teams/DDs/contributors can upload propositions to spread a information, news, or updates. 17:14:38 This item has been on 2 different agendas. Any ideas? 17:15:09 Maybe learn to send emails to pulbicity ??? 17:15:57 Can you expand? 17:16:20 (1 minute) 17:16:51 debian-publicity@d.o is a good place to propoose any subject/micronew/ideas to the publicity team 17:17:16 Agreed. 17:17:21 (next topic) 17:17:27 I think its more about a place that people can just put stuff up and read about stuff happening without our intenvention? 17:17:45 ItIt's quite simple and requires little technical skill. 17:17:49 but ah yeah more emails from other teams on what they are upto should be good 17:17:56 That is what I thought it was about, but I'm not sure. Its just been on the agenda for some time now and I thought someone wanted to discuss it. 17:18:30 disaster2life: I did send a year end request to several teams on that topic recently. 17:18:45 (1 minute) 17:18:46 I don't exactly have anything to propose other than just like a "wall" everyone can write and read off of 17:19:19 Kind of like bringing back Dents and the Ideas file? 17:19:22 maybe we can do a bits post on how to contribute to publicity team (with micronews/bits/etc) 17:19:25 DonaldNorwood[m]: ah, hopefully we will be getting more stuff to public about then! 17:19:41 or have a page with that content 17:19:42 charles: I like that idea. 17:19:51 "Dents and the Ideas file"? 17:20:06 bits is cool because has a good internal reach and it goes to planet.d.o (right?) 17:20:27 disaster2life (IRC): Dents where when anyone could pop into the channel with a micronews suggestion, the would prepend the suggestion with the word "Dent:" 17:20:29 I believe it does go to planet debian 17:20:50 The ideas file was just an open flat file that anyone could also add suggestions for articles and the such. 17:21:22 DonaldNorwood[m] ooh thats cool, I think that would be cool but I assume it went away for a reason? 17:21:30 hmmm I don't think that bits goes to planet. I can check. 17:21:44 #action does bits go to planet? donald 17:22:06 disaster2life (IRC): Just under-used and then I think forgotten about. 17:22:26 (next topic?) 17:22:37 ah I see, well if we could push that more but yeah maybe put this for later 17:22:47 #topic Where can we fit in DevNews? 17:23:15 We have devnews under our repo, its last use was 9 years ago. 17:23:33 It tends to be great news but I think overly technical for casual readers. 17:23:54 So where can we fit this in or do we leave it on its own list? 17:24:18 I mean, I think we actually do not have anything that does cater actively to very technical stuff? 17:24:45 Not too much I believe. 17:25:07 (1 minute) 17:25:28 I mean if there are people who would be interested in that, we could keep that to offer more technical topics 17:26:14 I honestly don't know the interest level. 17:26:53 We could test it by pushing a post to the Debian Administrators list on LinkedIn, that would let us track the interest. 17:27:34 I think people would be interested, at least would want to read about the technical stuff not happening in their team 17:28:06 hmmm 17:28:23 Lets read some of the last issues and then make a decision on it. 17:28:30 I tha the role of Debian Weekly news the ancestro of DPN 17:28:46 (also side note, I am pretty sure bits doesn't go to planet.d.o, I read through and didn't see so) 17:29:07 #action read devnews and discuss at next meeting. 17:29:11 DonaldNorwood[m] that would be smart, I have no clue what I am talking about :P 17:29:16 (next topic) 17:29:17 haha 17:29:26 ​ 17:29:26 #topic Renaming Master to Main 17:29:30 charles (IRC): 17:29:39 ack 17:30:23 I've seen that all our repos use master as the default branch and it makes sense because until a few years ago this was the default in git 17:30:44 nowadays it changed to main when you create a new repo in git 17:31:16 so I'd like to know opinions and how much work it would be to change the default branch name on our repos? 17:32:09 I think there is no real loss from changing it to main, I would prefer if we did, though I speak from a completely non technical point of view 17:32:28 I don't think it is a lot of work to change. All of the new project are indeed main. todo style and something else. 17:33:25 (I'm thinking also about cronjobs we might have around doing a git pull master or something) 17:33:36 master is being phased our in lot of other projects. I always associated master with masterwork, but I can still see the desire to no longer use the word. 17:33:50 charles (IRC): There is a script turning an old gbp packaging repository into a DEP14 compliant one. I have *not* tested it but there is a chance for automation. 17:33:51 *out 17:34:07 I'm personally not sure whether its worth the effort - just mentioning it. 17:34:41 hmmmm 17:34:45 AndreasTille[m]: ack. For packaging is more difficult, for us it'd be simpler I think (famous last words) 17:35:12 I will not stop any volunteer who wants to do that work ... 17:35:22 Our new repos will automatically be named main so the change is more historical at this point I would imagine. 17:35:50 the thing is, if no one has strong opinions against the change, I'd like to tackle that after I finish with bits/micronews CI/CD and contributing guide 17:36:12 Someone mentioned we could also name head levels whatever we wanted to, I suggest 'genius'. :) 17:36:20 No objection here. 17:36:48 charles unsure how much help I would be but yes, I feel a strong enough urge to lend a hand 17:37:23 disaster2life: cool! I'll send a message before starting 17:37:23 #action looking into changing master to main charles 17:37:37 #topic In Progress 17:37:43 These are pretty quick. 17:37:46 (before starting: think a few months from now) 17:38:10 ah thats a reasonable timeline 17:38:19 bits.d.o tag audit is very slow. That is the entire update. I do have a large batch hitting later this week. 17:39:10 DPN is being done as an archive issue for things you may have missed in 2024. We have reached out to 20? teams asking for updates. Web, Med, and a few others have expressed interest. 17:39:32 Both are open for any help anyone wishes to give. :) 17:39:56 DNS records for both of our VMs were recently updated. 17:40:08 I'll topic the next one 17:40:31 Unless anyone has another item to add here? I think most are under the action tag in the meeting so far. 17:40:43 oh wait. 17:41:07 I am doing the repository cleanup. 8 of 18 projects are active/semi-active. 17:41:39 cool! 17:41:46 woo! 17:42:02 There are a few that we should take a look at and a few outstanding merge requests. I'll email the authors to see if the merges are still valid or not so I do not break anything with an update/merge. 17:42:49 I've stopped the emails out for a few of the projects, it is a waste of resources, also has the benefit of stopping outside parties from publishing before we can. KGB in channel notifications are not touched. 17:42:52 I think we haven't done an official announcement about Lenovo sponsoring hardware to Debian. Have we? 17:43:08 AnupaAnnJoseph[m]: Not yet. 17:43:58 2 projects stand out in our repo: refcard which is a fork of Documentation/refcard. It is active, though not sure why it is under us. I will reach out to the DD writing to it. 17:44:10 re 17:44:26 the mails project has 2 commits to it and is redundant, it will be archived. 17:44:53 This is just minor stuff, I'll commit to a housekeeping file and then send to the list. 17:45:15 (next topic) 17:45:34 did we go through everything? We are already on 1:45 mark 17:45:41 About Lonovo, I will ask for a rereading of what had already been prepared to the persons concerned 17:45:53 Yes, was going to open for discussion. 17:45:59 charles: on the agenda I think we are finished 17:46:11 I think the only things is a few social media updates, but it is just outreach stuff. 17:46:32 #topic open discussion 17:47:33 nothing on my side (I think) 17:47:45 I don't think I have anything to add 17:48:18 (1 minute) 17:48:34 What is the status of Vorlon's obituary? 17:48:48 i hope the meeting was productive, i'll read logs later 17:49:16 AnupaAnnJoseph[m]: I have received only 1 reply to my ask. I will most likely run through the emails and do a quote style. 17:49:35 Ok, Thank you. 17:49:43 (1 minute) 17:50:19 afk, bbl 17:50:22 #endmeeting