19:06 #startmeeting Technical Board 19:06 Meeting started at 19:06:48 UTC. The chair is rbasak. Information about MeetBot at https://wiki.ubuntu.com/meetingology 19:06 Available commands: action, commands, idea, info, link, nick 19:07 #topic Action review 19:07 * rbasak seb128 to contact release team about official status of riscv64 19:07 I guess we carry that over 19:07 #action seb128 to contact release team about official status of riscv64 19:07 * meetingology seb128 to contact release team about official status of riscv64 19:07 * rbasak rbasak to draft a response to merlijn's email thread about the OSAID for review 19:07 This is done 19:07 * rbasak rbasak to reply to the release team and clarify the LTS flavor delegation process 19:07 Done, though the release team hasn't yet replied on my process/documentation question 19:07 * rbasak seb128 to continue working with AA and Release teams to document their membership process and link to it from https://wiki.ubuntu.com/TechnicalBoard#Team_Delegations 19:07 Carry over I guess? 19:07 #action seb128 to continue working with AA and Release teams to document their membership process and link to it from https://wiki.ubuntu.com/TechnicalBoard#Team_Delegations 19:07 * meetingology seb128 to continue working with AA and Release teams to document their membership process and link to it from https://wiki.ubuntu.com/TechnicalBoard#Team_Delegations 19:08 * rbasak teward to follow up with "who can vote" and documentation at https://ubuntu.com/community/governance/technical-board with the CC 19:08 teward: any progress on this, please? 19:08 * rbasak teward to write up a proposal for how the move away from the wiki will work 19:08 teward: ^ also this 19:08 * rbasak rbasak to proposed https://paste.ubuntu.com/p/ZrTXdHhM3P/ or a lightly edited version as the policy on DMB staffing 19:08 This is done and documented 19:08 Carry over both. 19:08 #action teward to follow up with "who can vote" and documentation at https://ubuntu.com/community/governance/technical-board with the CC 19:08 * meetingology teward to follow up with "who can vote" and documentation at https://ubuntu.com/community/governance/technical-board with the CC 19:08 #action teward to write up a proposal for how the move away from the wiki will work 19:08 * meetingology teward to write up a proposal for how the move away from the wiki will work 19:09 #topic Scan the mailing list archive for anything we missed (standing item) 19:09 i don't think there is anything 19:09 My larger task at the MOMENT has been the meetingology replacement. The chaos from Earlier(TM) has left us without the matrix meetingology that someone I will not mention had created. 19:09 I don't see anything either 19:09 Oh i have an FYI for us btw 19:09 #info No recent ML activity that requires follow-up 19:10 #topic Check up on community bugs and techboard bugs (standing item) 19:10 #info No open community bugs 19:10 i think we are actually progressing on https://bugs.launchpad.net/techboard/+bug/2015921 in some ways? 19:11 #info No new techboard bugs 19:11 I'm not sure we have a good answer yet, but it isn't a problem currently. 19:11 agreed 19:11 We appointed new DMB members and have a process for that now 19:11 Agreed 19:11 That bug is more about what to do when there are absentee DMB members. 19:12 Some of the bugs could do with catching up with current status and recent discussion, if someone would like to do that? 19:13 But apart from documentation in the bugs I don't think there's any action needed from the TB righ tnow 19:13 #topic Select a chair for the next meeting (next from https://launchpad.net/~techboard/+members) 19:13 100% me 19:13 there is also the 'Consider marking riscv64 architecture "official"' topic that we ran out of time discussing at some point, i don't know if we wnat to talk about it now 19:13 For next 19:13 i can be back up 19:14 #info The next chair will be teward with mwhudson as back up 19:14 Thanks! 19:15 i have a couple of topics, more for information than discussion (he says optimistically) 19:15 mwhudson: given the issues with builders slowness and such, etc. And the massive massive backlog of builds, I dont think we can move forward on that effectively at the moment? (RE: riscv official status) 19:15 IIRC the last time we discussed riscv64, we agreed that the release team should set a quality bar but then leave it to them to make a recommendation, or something like that? I'm not sure if I have the details right. 19:15 #topic AOB 19:16 rbasak: i seem to remember thats where we left off 19:16 maybe i should try to summarize where we were and raise this properly in the next meeting 19:17 i don't want to just rehash things 19:17 Sounds good - thanks! 19:17 mwhudson: i think that would work. Make that a specific action item 19:17 #action mwhudson to catch up on the previous riscv64 "official status" discussion and then drive it forward as needed 19:17 * meetingology mwhudson to catch up on the previous riscv64 "official status" discussion and then drive it forward as needed 19:18 mwhudson: you said you had a couple of other AOB items? 19:18 teward: you too? 19:18 for this meeting, topic 1: there has been some discussion about hardware specific kernels only being in specific LTS releases and such. one of the relevant teams at canonical has made a document to try to explore this topic and maybe propose a way forward 19:19 i only got the document a few hours ago though and i've been asleep for 90% of that time so nothing really to talk about, just that there is some stuff going on 19:19 Good to know they're driving this - thanks! I'll wait to see the document then I guess? 19:19 the other topic is about the ubuntu project documentation and moving the techboard documentation into that 19:20 the plan is to limit change to the techboard docs via CODEOWNERS (as was doing for AA documentation) 19:20 e.g. https://github.com/ubuntu/ubuntu-project-docs/blob/main/.github/CODEOWNERS 19:20 I'd like to see some kind of agreed sign-off system 19:20 Maybe signed tags or something? 19:21 Since otherwise _who_ signed off on a change will become lost to time (or the next migration to somewhere else) 19:22 i think robert should email the list about this. i'll send that comment back to him for now 19:22 Thanks! 19:22 just an fyi about things, there are known issues with the email systems and ubuntu email aliases - things are being looked at but the hiccup seems to be at Canonical. They know about it but its been several weeks without a fix. Just so everyone knows if they use their ubuntu aliases and arent getting messages. 19:22 Thats just a general notice for awareness. Nothing actionable by TB 19:23 But its having massive impact on bug notices, lists, etc. Going to people 19:23 OK thanks 19:23 Anything further to discuss? 19:24 I dont have anythjng, nope. 19:24 anything* 19:24 nothing from me 19:24 #endmeeting