| rbasak | o/ | 16:00 |
|---|---|---|
| vicamo | o/ | 16:00 |
| bandali | o/ | 16:00 |
| ivanhu | o/ | 16:00 |
| seb128 | o/ | 16:01 |
| seb128 | is it quiet or is my IRC not working? | 16:03 |
| bandali | seems pretty quiet so far | 16:04 |
| seb128 | so what do we need to get started? | 16:05 |
| rbasak | We aren't quorate currently. | 16:05 |
| rbasak | We need a couple more DMB members to appear | 16:05 |
| seb128 | Lukasz and Brian denied the meeting so I guess we should count them out | 16:06 |
| rbasak | This used to be a regular problem. At that time, the DMB concluded that: | 16:06 |
| rbasak | "Quorum votes are required, however if quorum is not reached at first meeting, at the next meeting majority present votes are required" | 16:06 |
| rbasak | I think that suggests that if we don't get quorum today, we will need to postpone, but when the same applicants are considered again, only the board members present at that meeting will be needed. | 16:07 |
| rbasak | Usually I wait ten minutes and then go. I am interrupting my leave to be here. | 16:08 |
| bandali | is it perhaps worth trying pinging the other members? | 16:09 |
| seb128 | bandali, it was done on #ubuntu-devel | 16:09 |
| seb128 | it feels like we will need to postpone again... | 16:09 |
| rbasak | Sorry, it seems unlikely that hanging around longer will help, so let's postpone. | 16:10 |
| seb128 | yes :-( | 16:10 |
| rbasak | ivanhu: please reschedule yourself in the next available slot | 16:11 |
| ivanhu | rbasak, OK | 16:12 |
| utkarsh210243 | \o | 16:12 |
| utkarsh210243 | \o | 16:12 |
| utkarsh210243 | this is utkarsh2102 here | 16:12 |
| rbasak | bandali: I suppose you can use the same replacement slot as an exception, following the previous exception. | 16:12 |
| utkarsh210243 | can't you read my texts from the Matrix side? | 16:12 |
| rbasak | Nope. | 16:12 |
| utkarsh210243 | rbasak, seb128: I said we're 4 of us here | 16:12 |
| utkarsh210243 | I've been saying that for too long :P | 16:12 |
| rbasak | I only see three? | 16:13 |
| utkarsh210243 | Robie, Seb, Utkarsh, Lucas | 16:13 |
| rbasak | Lucas doesn't appear to be here either. | 16:13 |
| utkarsh210243 | whaaaaaaat | 16:13 |
| utkarsh210243 | the bridge seems to be down | 16:13 |
| rbasak | Fix your bridge please, or just use IRC directly? We've wasted a quarter of our time already :-( | 16:13 |
| utkarsh210243 | because I can see him here | 16:13 |
| utkarsh210243 | I mean, Matrix generally works. It's rare that it doesn't. | 16:14 |
| utkarsh210243 | kanashiro: hi! \o | 16:14 |
| teward | *appears* | 16:14 |
| utkarsh210243 | hehe | 16:14 |
| utkarsh210243 | 5 of us now | 16:14 |
| kanashiro | I am out of matrix now | 16:14 |
| rbasak | ivanhu: still here? | 16:14 |
| teward | so both matrix and irccloud decided to tell me to go screw myself and didn't send me notifications oops | 16:14 |
| ivanhu | rbasak, yes | 16:14 |
| rbasak | Can someone else chair please? | 16:15 |
| kanashiro | I think this is the first time I have an issue with the matrix to IRC bridge :/ | 16:15 |
| utkarsh210243 | same | 16:15 |
| kanashiro | I am in a concurrent meeting FWIW | 16:15 |
| === utkarsh210243 is now known as utkarsh | ||
| teward | been a while since i chaired i'll do it but let me grab the agenda first | 16:16 |
| rbasak | AIUI, we're considering ivanhu's application first. | 16:16 |
| bandali | and i'm still around as well (if there's time for me) | 16:16 |
| teward | #startmeeting Developer Membership Board Meeting - March 6, 2023 | 16:17 |
| meetingology | Meeting started at 16:17:14 UTC. The chair is teward. Information about MeetBot at https://wiki.ubuntu.com/meetingology | 16:17 |
| meetingology | Available commands: action, commands, idea, info, link, nick | 16:17 |
| teward | Hello, everyone, and welcome to the DMB meeting for March 6th, 2023. | 16:17 |
| rbasak | bandali: right, but we set a cut-off at 1630 UTC, so I'm not sure there'll be time now, sorry :-( | 16:17 |
| teward | As we're short on time I'm going to move some things to "later" (review of previous items, etc.) | 16:18 |
| bandali | -_- | 16:18 |
| teward | and we're going to jump right in to the meeting here. I see that there's some missing links in the agenda page to application pages | 16:18 |
| rbasak | vicamo: you seem to have picked a full meeting date, so I'm not expecting that your application would have been considered today anyway. Please see the email thread, find a free slot, and adjust your agenda item. | 16:18 |
| teward | #topic Packageset / PPU Uploader Applications | 16:18 |
| teward | #subtopic Ivan Hu | 16:19 |
| * vicamo so sad | 16:19 | |
| teward | #link https://wiki.ubuntu.com/IvanHu/PPU | 16:19 |
| rbasak | vicamo: the agenda page says this at the top: "The Developer Membership Board will consider a maximum of one applicant per meeting." | 16:19 |
| teward | ivanhu: greetings, how about you start by introducing yourself to the DMB and why you're here, while we review your applicaiton page. | 16:19 |
| ivanhu | sure | 16:20 |
| teward | vicamo: pick a meeting date that isn't full already (we only process one application per meeting at the moment because of the lengths we go to in vetting someoen for their applications) | 16:20 |
| === utkarsh16 is now known as utkarsh | ||
| ivanhu | hi there, I am IvanHu, I am currently in kernel - HWE team, focus on the firmware related issues and functions. I have been the developer and maintainer of FWTS(firmware test suite) since I joined Canonical. | 16:21 |
| vicamo | teward, rbasak: I saw two fall on today, therefore I thought it's allowed for 3. | 16:21 |
| teward | vicamo: assuming things does not help, the text on the page itself is the most important part, and we've already sent emails in the past to peopel who are double-scheduling to choose another day. some haven't gotten to it yet. But we can discuss this later, right now the DMB needs to pay attention to the applicant who has the floor, ivanhu | 16:22 |
| rbasak | ivanhu: welcome! | 16:23 |
| rbasak | ivanhu: do you have any need or plans to change a package in a stable release, such as to fix bugs, or update the package after release? Or are you only interested in uploading to the development release? | 16:23 |
| ivanhu | rbasak, fwts use stable ppa for getting the latest version and also will create a live image for using every release, so uploading to the development release should be fine. | 16:27 |
| rbasak | ivanhu: if you find that you do need to update a stable release, do you know where to find the documentation on how to request that, or who to ask? | 16:29 |
| ivanhu | rbasak, yes | 16:30 |
| rbasak | Where do you find the documentation, or who/how/where would you ask? | 16:31 |
| ivanhu | rbasak, the SRU process document https://wiki.ubuntu.com/StableReleaseUpdates#regressions, and I can ask me colleague Timo who is in SRU team. | 16:33 |
| rbasak | OK great, thanks. Next question: do you have any experience in making packaging changes? | 16:34 |
| rbasak | I see very little in the history of fwts. | 16:34 |
| rbasak | What would you do if you had to make a packaging change in fwts? | 16:34 |
| ivanhu | rbasak, I might modify the debian configures, such as control or rule... | 16:38 |
| rbasak | I'm not sure if you are still answering. Please let me know when you are finished with an answer. | 16:39 |
| ivanhu | rbasak, I actually add the efi_runtime DKMS for the fwts package. | 16:39 |
| ivanhu | that's my answer. | 16:41 |
| rbasak | Ah, in 0.26.01-1, back in 2012? Is that your most recent experience of packaging changes? | 16:41 |
| ivanhu | rbasak, no, that's my ex-colleague | 16:43 |
| rbasak | [Ivan Hu] | 16:43 |
| rbasak | * efi_runtime: add efi_runtime kernel driver module into fwts | 16:43 |
| rbasak | That's against: | 16:44 |
| rbasak | fwts (0.26.01-1) raring; urgency=low | 16:44 |
| rbasak | Do you have a more recent example? | 16:44 |
| utkarsh | TIL: raring :) | 16:44 |
| ivanhu | rbasak, I am afraid no. | 16:45 |
| rbasak | OK | 16:46 |
| rbasak | I have one more question about the release schedule, and then a suggestion. | 16:46 |
| rbasak | Question: is there a time when it is inappropriate to upload feature changes? If so, how do you find out when that is? | 16:46 |
| utkarsh | oh, also, Colin (your top sponsorer and endorser) said: "His packaging work has been flawless and I am very confident [...]" - what packaging work are they talking about? | 16:48 |
| utkarsh | please answer rbasak first! | 16:48 |
| ivanhu | when the featurefreeze | 16:48 |
| ivanhu | you can fine in the shedule wiki | 16:49 |
| ivanhu | s/fine/find | 16:49 |
| rbasak | Can you find a link to the appropriate page please? | 16:49 |
| ivanhu | rbasak, https://discourse.ubuntu.com/t/lunar-lobster-release-schedule/27284 | 16:50 |
| rbasak | Great, thanks! | 16:51 |
| rbasak | My suggestion: it looks like you're doing a great job upload fwts to stay up to date with the latest upstream versions! | 16:51 |
| ivanhu | utkarsh, actually I have a wiki to the fwts release process | 16:52 |
| ivanhu | https://wiki.canonical.com/IvanHu/fwtsReleaseProc | 16:52 |
| rbasak | However, there's no track record here of you working on stable release updates, or any recent track record that demonstrates your understanding of packaging changes | 16:52 |
| ivanhu | utkarsh, and also a script to release fwts https://github.com/Ivanhu5866/script-fwts/blob/master/release_fwts.sh | 16:52 |
| rbasak | I don't want to block on your ability to upload non-packaging-impacting new upstream releases to this package. | 16:53 |
| rbasak | So I suggest we grant you PPU, but with some limitations, which would be enforced by trust only. Specifically, that you do not upload packaging changes or SRUs without a public code review from a core dev first (but with a public core dev +1, you could then sign and upload yourself). | 16:54 |
| rbasak | If this were to be agreed by the DMB, would this work for you? | 16:55 |
| ivanhu | rbasak, works for me | 16:57 |
| rbasak | Great! Other DMB members: would that be acceptable to you? | 16:57 |
| kanashiro | +1 | 16:58 |
| utkarsh | +1 | 16:58 |
| seb128 | +1 | 16:59 |
| rbasak | Shall we consider that the voting done then? :) | 17:00 |
| rbasak | Unless teward has a different opinion and would like us to reconsider? | 17:01 |
| teward | +1 no objection | 17:01 |
| rbasak | ivanhu: it might be the case that you have no need for SRUs or packaging changes for a long time, which would be absolutely fine. | 17:02 |
| rbasak | If you do need to start doing those, then feel free to come back to the DMB to ask for the limitation to be removed once you have a track record of having done some with core dev review. We don't want to obstruct people doing valuable work - it's just that it's difficult for us to approve something when there isn't much of a track record. | 17:03 |
| ivanhu | rbasak, understand. thanks! | 17:04 |
| utkarsh | cool, I can announce the application then! :) | 17:05 |
| rbasak | It'll need a TB member to make the PPU change. I can do that. | 17:05 |
| utkarsh | s.w.e.e.t. | 17:06 |
| utkarsh | congratulations, ivanhu! \o | 17:07 |
| ivanhu | thanks. \o/ | 17:08 |
| utkarsh | and with that, teward can you conclude the team meeting? | 17:08 |
| teward | congrats! | 17:08 |
| teward | yes I can | 17:08 |
| teward | i'm going to carry over my taskl though | 17:08 |
| teward | but 1 quick question: | 17:08 |
| teward | #topic Vote on Keeping IRC meetings moving | 17:08 |
| teward | We did this right? | 17:08 |
| teward | rbasak: do you also want to take the announce of the application and the conditions? | 17:09 |
| vicamo | is it my network connection or IRC meeting is not moving? | 17:18 |
| teward | #end meeting | 17:36 |
| teward | #endmeeting | 17:36 |
| meetingology | Meeting ended at 17:36:44 UTC. Minutes at https://ubottu.com/meetingology/logs/ubuntu-meeting/2023/ubuntu-meeting.2023-03-06-16.17.moin.txt | 17:36 |
| teward | nah you're not wrong i lagged hard and IRCCloud told me to shove it | 17:36 |
| teward | i'll just arbitrarily assign some tasks | 17:37 |
| teward | (read: my internet went down for a short while) | 17:40 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!