16:06 #startmeeting Ubuntu Developer Membership Board 16:06 Meeting started at 16:06:06 UTC. The chair is rbasak. Information about MeetBot at https://wiki.ubuntu.com/meetingology 16:06 Available commands: action, commands, idea, info, link, nick 16:06 Let's go straight to applications 16:06 #topic Package Set/Per Package Uploader Applications 16:06 #subtopic Paolo Pisati (2023-04-03) 16:06 ppisati: welcome! Would you like to introduce yourself? 16:06 #link https://wiki.ubuntu.com/PaoloPisati/DKMSUploadApplication 16:06 yep 16:07 Hi there, my name is Paolo and I've been a member of the Ubuntu kernel team since 2011 16:07 my main focus is devel kernel / kernel packaging, and i mantain the kernel dev series 16:08 I'm applying for dkms upload rights so i can (hopefully) speedup release of new kernels 16:08 since often new kernels are blocked on DKMS FTBFS or various other DKMS failures 16:09 Does anyone have questions for ppisati? 16:09 I can start :) 16:09 ppisati: do you know what the SRU team's opinion is of "Regression Potential: None" or similar? 16:10 rbasak: yes, they don't like it! :) 16:10 i think you picked that from one of my previous DKMS upload 16:10 I looked for recent SRUs, and see bug 2002527 and bug 2002329 :) 16:11 that is actually part of the SRU template and should show where the update you are working on 'could go wrong' 16:11 Bug 2002636 too. 16:11 Those are your most recent SRUs I think? 16:12 rbasak: yep, somehow that list doesn't show all the SRUs i did in the past 16:12 I'm looking at https://udd.debian.org/cgi-bin/ubuntu-sponsorships.cgi?render=html&sponsor=&sponsor_search=name&sponsoree=Paolo+Pisati&sponsoree_search=name - is that more representative? 16:12 https://launchpad.net/~p-pisati/+uploaded-packages only shows each package once I think. 16:13 Maybe per package or per release or something like that. Anyway I find the sponsorship miner to be more comprehensive. Or do you think there are more yet that are missing? 16:13 rbasak: yes, that looks more complete 16:13 rbasak: the last url you posted looks good (please dont' ask me what i did in 2011...) 16:14 Looking at your past few SRUs (most recent) from there, I feel that you're missing something in your communications with the SRU team. They keep needing to clarify things, and I don't think they generally include much of a regression analysis at all. 16:15 rbasak: yes, i should improve that 16:15 eg. https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/2002320/comments/2 and https://bugs.launchpad.net/ubuntu/+source/openafs/+bug/2002527/comments/3 16:15 OK, let's move on 16:16 ppisati: are there times when it might be inappropriate to upload DKMS fixes to the development release? 16:16 rbasak: when we are in beta freeze or finale freeze, for example 16:17 rbasak: but even feature freeze, upload should slow down, and only hot fixes for specific bugs are admitted 16:17 Great. 16:17 ppisati: what freeze applies to Lunar at the moment, and where can you find that information? 16:18 rbasak: ATM we just left beta freeze and we are back to feature freeze, final freeze should be... 16:18 https://discourse.ubuntu.com/t/lunar-lobster-release-schedule/27284 16:18 April 13 ^ 16:18 Great, thanks! 16:19 the release schedule tells you the state of the archive wrt uploads 16:19 ppisati: to fix packages in the stable release, where is the process and policy documentation? 16:20 rbasak: it's the SRU process -> https://wiki.ubuntu.com/StableReleaseUpdates 16:22 Thanks! I have no more questions. 16:22 Does anyone else have any questions for ppisati? 16:24 ppisati: what could block your upload in proposed? What would you do to investigate that? 16:25 kanashiro[m]: autopkgtests, i useually check the excuse page and then take it from there 16:25 e.g. https://ubuntu-archive-team.ubuntu.com/proposed-migration/update_excuses.html 16:26 is autopkgtest the only reason to get a package blocked? 16:27 kanashiro[m]: uhm, no, it could depend on another package that is not installable 16:28 it could be that the archive is frozen 16:28 or the package violates one of the SRU rules 16:29 ppisati: thanks for the answer! It could also be a installability issue in the package itself or a FTBFS 16:30 kanashiro[m]: sure 16:31 no more questions from me 16:31 Anyone else? 16:31 (thanks kanashiro[m]!) 16:33 OK, let's vote. 16:33 #vote Grant ppisati membership of the kernel-dkms packageset uploading team 16:33 Please vote on: Grant ppisati membership of the kernel-dkms packageset uploading team 16:33 Public votes can be registered by saying +1, -1 or +0 in channel (for private voting, private message me with 'vote +1|-1|+0 #channelname') 16:33 +1 you have an extensive track record of fixes to DKMS packages, sufficient Ubuntu development knowledge (likely a lot more!) and endorsements from relevant developers. I'd like to see more comprehensive regression analysis and test plans for your SRUs, but on balance I think Ubuntu would benefit more if you could upload these directly today. 16:33 +1 you have an extensive track record of fixes to DKMS packages, sufficient Ubuntu development knowledge (likely a lot more!) and endorsements from relevant developers. I'd like to see more comprehensive regression analysis and test plans for your SRUs, but on balance I think Ubuntu would benefit more if you could upload these directly today. received from rbasak 16:33 But please consider what you could do to reduce questions review iterations on your SRU uploads. I welcome conversations with the SRU team about that - especially discussions around anything you think we should change. 16:34 +1 seems a solid application for the requested packages, I would also like to see improvements on the SRU front as mentioned by Robie 16:34 +1 seems a solid application for the requested packages, I would also like to see improvements on the SRU front as mentioned by Robie received from seb128 16:35 +1 I would like to see improvements on the SRU front as Robie mentioned, but otherwise a solid application for the packages requested. 16:35 +1 I would like to see improvements on the SRU front as Robie mentioned, but otherwise a solid application for the packages requested. received from teward 16:35 *sips coffee* 16:36 +1. I see all the amount of work done during those several years and I do believe more people taking care of DKMS packages would benefit the project. I'd say you still need to improve your SRUs to avoid more work on the overloaded SRU team. Thanks for all your work and keep it up! 16:36 +1. I see all the amount of work done during those several years and I do believe more people taking care of DKMS packages would benefit the project. I'd say you still need to improve your SRUs to avoid more work on the overloaded SRU team. Thanks for all your work and keep it up! received from kanashiro[m] 16:36 #endvote 16:36 Voting ended on: Grant ppisati membership of the kernel-dkms packageset uploading team 16:36 Votes for: 4, Votes against: 0, Abstentions: 0 16:36 Motion carried 16:36 Congratulations ppisati! 16:36 congrats! 16:36 Any volunteers for the ACL change and/or the announcement please? 16:36 congrats ppisati ! 16:37 thanks guys, i'll be more careful wrt SRUs / regression potential 16:37 rbasak: I can take it 16:37 Thanks! 16:37 Checklist reminder: https://wiki.ubuntu.com/DeveloperMembershipBoard/KnowledgeBase#Actions_after_a_successful_application 16:37 #action kanashiro[m] to announce ppisati's successful application 16:37 * meetingology kanashiro[m] to announce ppisati's successful application 16:37 ack 16:37 ack 16:37 #action kanashiro[m] to make ACL changes for ppisati's approved application 16:37 * meetingology kanashiro[m] to make ACL changes for ppisati's approved application 16:38 ppisati: please do ask if it's not clear about the SRUs. Often it's just about mismatched expectations and talking is the easiest way to fix that :) 16:38 rbasak: i promise i'll do 16:38 Thanks! 16:38 #topic Review of previous action items 16:39 teward follow up to get all application process wiki/docs to explain the process to be able to edit wiki pages, for applicants who don't yet have wiki edit access (carried over) 16:39 rbased to document the decision on Keeping IRC meetings moving 16:39 Mine needs carrying over 16:39 same on mine 16:39 never enough cycles >.< 16:39 #action rbasak to document the decision on Keeping IRC meetings moving 16:39 * meetingology rbasak to document the decision on Keeping IRC meetings moving 16:39 #action teward follow up to get all application process wiki/docs to explain the process to be 16:39 * meetingology teward follow up to get all application process wiki/docs to explain the process to be 16:39 able to edit wiki pages, for applicants who don't yet have wiki edit access (carried 16:39 over) 16:39 Sorry for the bad paste 16:39 #undo 16:39 Removing item from minutes: ACTION 16:39 #action teward to follow up to get all application process wiki/docs to explain the process to be able to edit wiki pages, for applicants who don't yet have wiki edit access (carried over) 16:39 * meetingology teward to follow up to get all application process wiki/docs to explain the process to be able to edit wiki pages, for applicants who don't yet have wiki edit access (carried over) 16:40 #topic Outstanding mailing list requests to assign 16:40 I don't see any 16:40 #info No outstanding mailing list requests to assign 16:40 #topic Open TB bugs 16:41 #info 16:41 There are currently no open bugs. 16:41 #info There are currently no open bugs. 16:41 #topic AOB 16:41 AOB? 16:43 none 16:43 #endmeeting