/srv/irclogs.ubuntu.com/2020/03/09/#ubuntu-meeting.txt

rbasako/15:00
sil2100o/15:00
slashdo/15:00
rafaeldtinocoo/15:01
ddstreeto/15:02
sil2100Do we have a selected chair for today?15:02
rafaeldtinocodont think so15:03
* gaughen watches15:03
sil2100Should I start then? Or are there any other volunteers?15:03
* rcj watches15:03
* rbasak is in a concurrent meeting, so would prefer not to chair15:04
* rafaeldtinoco in the same meeting15:04
ddstreetI'm on vacation on my phone so I will mostly watch/listen15:04
sil2100Let me start then15:05
sil2100#startmeeting DMB meeting15:05
meetingologyMeeting started Mon Mar  9 15:05:50 2020 UTC.  The chair is sil2100. Information about MeetBot at http://wiki.ubuntu.com/meetingology.15:05
meetingologyAvailable commands: action commands idea info link nick15:05
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds: Please leave swords by the door | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendars | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | <wxl> be nice | DMB meeting | Current topic:
tewardo/15:05
tewardsorry network issues15:06
teward(just fixed them heh)15:06
sil2100#topic Review of previous action items15:06
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds: Please leave swords by the door | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendars | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | <wxl> be nice | DMB meeting | Current topic: Review of previous action items
sil2100I think the only sensible action item from previous meetings is the fact that the vote announcement has finished and we have new DMB members o/15:07
rbasakWe need to ratify/select our ongoing meeting schedule15:07
tewardindeed we do (thank you to all who gave me a vote of confidence!)15:07
rbasakAnd welcome to the new DMB members :)15:07
sil2100Welcome o/15:07
rafaeldtinocothank you!15:07
rafaeldtinoco=)15:08
ddstreetThnx o/15:08
sil2100Let's get to the meeting schedule during AOB15:08
tewardagreed15:08
sil2100Anyway, I'll clean up the agenda page to clean up those items that make no longer sense (from Review of previous action items)15:08
sil2100Let's move on for now15:08
sil2100#topic Package Set/Per Package Uploader Applications15:09
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds: Please leave swords by the door | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendars | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | <wxl> be nice | DMB meeting | Current topic: Package Set/Per Package Uploader Applications
sil2100We have two applicants today15:09
sil2100I see rcj is here already, cascardo are you also here?15:09
cascardoI am around for any questions15:09
sil2100Ok, so let's proceed in order per the agenda page then15:10
sil2100#subtopic Thadeu Lima de Souza Cascardo for makedumpfile, kexec-tools, crash PPU15:10
sil2100#link https://wiki.ubuntu.com/ThadeuCascardo/KdumpUploadApplication15:10
sil2100cascardo: hello! Could you briefly introduce yourself?15:10
cascardohello, I work on the kernel team, have been a DD for a while, and have been maintaining kdump-tools/makedumpfile for a couple of years, IIRC15:11
rbasakcascardo: do you have upload access to anything in Ubuntu right now, or would this be the first time you can upload to Ubuntu without sponsorship?15:13
cascardorbasak: I can upload the linux set of packages15:13
rbasakAh - granted by the kernel team DMB delegation presumably? When were you given access to that?15:14
rbasakAnd do you have any other upload access apart from the linux set?15:14
sil2100DMB members: please proceed with questions, if you have any15:14
* rafaeldtinoco looks at https://launchpad.net/ubuntu/+source/kexec-tools/1:2.0.16-1ubuntu115:14
cascardoaround early 201815:14
cascardorbasak: only the linux set15:15
rbasakOK, thanks15:15
slashdI don't have questions, I've worked closely with cascardo in a couple of occasions.15:17
* rbasak is still looking15:17
* teward is still looking as well15:18
tewardcascardo: this may sound like an obvious question since you're on the server team, but I notice in your application you indicate that you need to be more concervative on uploads to stable releases.  You also indicate more testing should be done.  ...15:18
bdmurrayteward: he said he's on the kernel team15:19
teward... do you have any intention of spearheading the 'additional testing' you indicate should be done?  And how would PPU rights faciliate that testing compared to what you currently have access to?15:19
tewardbdmurray: the ... indicated a truncation, please permit me to finish my sentences ;)15:19
tewards/server team/kernel team/15:20
tewardE:NeedThirdCoffee :)15:20
teward(sorry for the mistype_15:20
cascardoteward: yeah, I would like to spearhead that, add additional testing to those packages so we can find out when they stop working for new kernels, and be more active in backporting new versions15:20
rbasakcascardo: at the moment, would any regular upload to Ubuntu for your requested PPU packages be acceptable, or are there any restrictions?15:20
cascardothe PPU rights would not facilitate working on that additional testing, but would allow me to more quickly get those fixes in Ubuntu15:20
cascardorbasak: sorry, I didn't understand the question, what do you mean by regular uploads? sponsored uploads?15:21
rafaeldtinococascardo: he means today I suppose .. would exist any blocker if you wanted to upload it today ?15:24
rafaeldtinoco(he is talking in a meeting I'm listening to, trying to help)15:24
cascardoI am supposing you mean someone else doing the uploads, I haven't had issues with that, so, in principle, no restrictions15:26
rafaeldtinococascardo: let's say you want to do a upload to kdump-tools in focal today15:26
rafaeldtinocowhat are the things you would not be able to do ? are you aware ?15:26
cascardowell, since we are at feature freeze, I would need to get it past the SRU queue to get it into focal-proposed15:27
rafaeldtinocoyep =)15:28
rafaeldtinocoi dont have any questions, i was just finishing rbasak's question15:28
ddstreetcascardo are you subscribed, directly or indirectly, to all new bugs for these packages?  If not, are you willing to subscribe yourself and triage and/or own new bugs?15:28
cascardoand by feature freeze, it means I should not introduce new features, but mostly fixes, closing bugs15:28
cascardoddstreet: I am currently subscribed to makedumpfile, and I have no problems being subscribed to the other two (if I am not already)15:28
ddstreetThanks, no more q from me15:29
sil2100Any other questions?15:29
rbasako/15:29
rbasakcascardo: I was asking about Focal, which isn't a stable release yet.15:29
rbasakSo no SRU queue involvement?15:29
tewardi was about to ask that myself heh15:30
cascardorbasak: there is SRU queue involvement right now because of Feature Freeze, if I understand correctly15:30
rbasakcascardo: my question is about making sure you understand Ubuntu development process15:30
cascardobefore feature freeze, I could just upload to focal-proposed15:30
cascardothat is my understanding15:30
rbasakcascardo: do you know where to go if you need a feature freeze exception, and where that process is documented?15:30
tewardbut that's not the SRU queue15:30
sil2100cascardo: yeah, so it's just a naming thing, the SRU queue is how we specifically call the queue for stable series - there is a focal queue but we don't name it like that15:32
cascardoit's an upload queue15:32
sil2100cascardo: exactly15:32
cascardoand are they reviewed by a different team?15:33
sil2100cascardo: and for Feature Freeze it's just a 'soft lock', so things do not go to the upload queue just yet15:33
cascardofrom what I can read, the feature freeze exception would involve an ACK on a bug by the release team, by CCing ubuntu-release15:34
cascardoand I would follow that for minor version releases that include only bug fixes just to be on the safe side15:35
cascardoat least until I build enough confidence that my judgement on those is aligned with the release team15:36
rbasakI think it might be better for you to continue checking with your current sponsors for these kinds of exceptional cases, whether your application today is approved or not.15:39
rbasakWaiting for the release team will take a much longer time I expect.15:39
cascardothat makes sense15:39
sil2100Any other questions?15:39
rbasakcascardo: let's move on from feature freeze. Can you tell me about proposed migration? If you do an upload and you see that it is stuck in the proposed pocket and not moving to the release pocket, what would you do?15:40
cascardoI would go through the excuses update page, find out what is the problem for migration15:40
cascardosometimes it happens because bugs are not verified, so I would request for verification once more, or do them by myself15:40
rbasakTo be clear, my question is about the development release again, not the stable release.15:41
cascardosometimes it happens because of test failures on ADT, so I would investigate those, and try to fix them15:41
rbasakOK, thanks. No more questions.15:41
tewardi have one question following rbasak's.15:41
tewardand your response.15:42
tewardother than the excuses page, where else can you get information about what may be holding up a package or might be affecting proposed migration?15:42
=== genii_ is now known as genii
cascardoI am not familiar with other tools, though I looked it up and just found out about the proposed-migration script, though I don't know where to find it15:44
tewardno more questions on my end.15:45
rafaeldtinococascardo: https://launchpad.net/ubuntu/+source/kexec-tools/+publishinghistory15:45
rafaeldtinocojust 1 example15:45
rafaeldtinocoon where to get current migration status15:45
rafaeldtinocoand publishing history15:45
sil2100Ok, I think we're done with questions then?15:46
cascardookay, I used it before to get hold of older versions not in the archive anymore15:46
sil2100Let's vote in this case o/15:47
rafaeldtinocoyep15:47
sil2100#vote Granting cascardo PPU rights for makedumpfile, kexec-tools and crash15:47
meetingologyPlease vote on: Granting cascardo PPU rights for makedumpfile, kexec-tools and crash15:47
meetingologyPublic votes can be registered by saying +1, +0 or -1 in channel, (for private voting, private message me with 'vote +1/-1/+0 #channelname)15:47
rafaeldtinoco+115:48
meetingology+1 received from rafaeldtinoco15:48
slashd+115:50
meetingology+1 received from slashd15:50
sil2100+0 (I am confident in cascardo's packaging skills, but the answers to archive/release related questions made me feel a bit worried, so for now my vote will be abstaining)15:51
meetingology+0 (I am confident in cascardo's packaging skills, but the answers to archive/release related questions made me feel a bit worried, so for now my vote will be abstaining) received from sil210015:51
rbasak-1 reasons to follow15:51
meetingology-1 reasons to follow received from rbasak15:51
teward-1 also reasons to folow15:51
meetingology-1 also reasons to folow received from teward15:51
rbasakI have no concerns about the quality of your work in itself, but do think your understanding of processes in the Ubuntu development release is quite muddled. I think you'd benefit from the continued supervision of a sponsor for the time being. Some of my questions covered more exceptional circumstances that you might not have encountered yet, so this might seem a little unfair, but it seems to me15:52
rbasakthat with a muddled understanding you are likely to unwittingly walk into a conflict with expectations from others when they will inevitably arise, and so remaining under the guidance of a sponsor makes sense. I hope that with some more experience or reading through various bits of documentation you will be ready to reapply soon.15:52
sil2100ddstreet: are you still around to vote?15:53
ddstreet+0 as I'm traveling and my vote would not change the outcome15:53
meetingology+0 as I'm traveling and my vote would not change the outcome received from ddstreet15:53
tewardI do not question your work quality, however like rbasak says, I think your understanding of the processes in the current dev release are incomplete or confused.  I also believe that some of your statements and understanding of the tools is concerning, and additional guidance in those tools is warranted.  To that end, the confused understanding of the tools and the processes are likely to make you run into provlems as they arise...15:54
sil2100Ok, I think we will need tsimonq2's vote in this case15:54
sil2100Who does not seem to be present today15:55
teward... especially with the expectations of others or the Release/dev teams, and continued ongoing guidance from a sponsor is warranted.  I also encourage you to inquire with your sponsors about things that you may or may not be sure about even if you are almost certain you are correct, to act as a sounding board to point out any mistakes in processes, etc. you have.15:55
sil2100#endvote15:55
meetingologyVoting ended on: Granting cascardo PPU rights for makedumpfile, kexec-tools and crash15:55
meetingologyVotes for:2 Votes against:2 Abstentions:215:55
meetingologyDeadlock, casting vote may be used15:55
sil2100Cliffhanger! Guess we'll have to contact tsimonq2 somehow and make him vote, or carry this over to the next meeting15:56
tewardsil2100: i propose we bring that vote to email and ask the non-present DMB members (tsimonq2 specifically) to cast their vote.15:56
tewardsince it can be... difficult... to get hold of tsimonq2 sometimes15:56
RikMillssil2100: I will ping him on telegram15:57
bdmurrayCould ddstreet vote after his travels?15:57
RikMillsyes, circumstances mean tsimonq2 is not always instantly available at the moment15:57
teward(he's available in talking to me right now on telegram, as an aside)15:58
sil2100cascardo: sorry that we couldn't get your application resolved today - we'll try to do that ASAP and let you know the outcome15:58
sil2100This shouldn't take longer than till the next meeting15:59
cascardosil2100: no problems, thanks everyone for reviewing the application15:59
tewardsil2100: given info in the other channel, and tsimonq2's statement to me, we will have SImon's vote within the hour, but for now I say we move this one along in the "follow up" items to check up with next meeting.15:59
tsimonq2Hi.15:59
tewardoh wait there's the SImon :P15:59
sil2100\o/15:59
cascardoI find out that the questions were fairly raised, and, in the meantime, I hope I can get better graps of the exceptional processes15:59
tsimonq2I will have my vote within the hour.15:59
tsimonq2I hate DST.16:00
sil2100Ok, let's move on in the meantime so that rcj doesn't have to wait16:00
sil2100#subtopic Robert Jennings applying for livecd-rootfs PPU16:00
sil2100#link https://wiki.ubuntu.com/rcj/PerPackageUploadLivecdRootfs16:00
sil2100rcj: o/16:00
rcjHi, I work on a team developing and delivering Ubuntu images to public clouds.16:00
rcjThese Ubuntu images are built using livecd-rootfs (ubuntu-cpc project) and I have been contributing to the package through sponsored uploads for several years.  This would be my first upload access in Ubuntu.16:00
sil2100Questions please o/16:01
rbasakbdmurray: as you're here and you have previously sponsored livecd-rootfs for rcj, any comment please?16:02
rbasakrcj: similar questions to you then I guess. What would you do if you want to make a feature change to livecd-rootfs in Focal at this point in the cycle?16:03
bdmurrayI didn't get a chance to write an endorsement with travel, sprints and stuff like that. But I do endorse rcj's application. livecd-rootfs is kind of special as it isn't really used like a normal package but the cpc team does extensive testing of it.16:04
tsimonq2Alright, my vote on cascardo is -1 because I agree with rbasak that more thorough process knowledge would be beneficial.16:04
tsimonq2Apologies for being so brief.16:04
rbasakbdmurray: thanks!16:04
tsimonq2Thanks for attending cascardo, I'd love to see you apply again soon.16:04
sil2100tsimonq2: thanks for the vote!16:04
tsimonq2Now on to the current topic...16:05
tewardrcj: I have one question, and this is probably a stupid one, but to confirm: this application is for *you yourself* and not your team, correct?16:05
tewardthere were a couple times you referenced "me and my team" so I want to clarify this point16:05
sil2100cascardo: be sure to re-apply soon though!16:05
rcjrbasak: If I needed to make a feature change in livecd-rootfs at this stage I would create a bug with MP outlining rationale for the change and risk subscribing ubuntu-release per FFE16:05
rcjteward: this is just for me.16:06
rbasakrcj: OK, thanks. What about if you wanted to make that change for Bionic?16:06
tsimonq2rcj: What's your favorite part about working with livecd-rootfs?16:06
tsimonq2I'm going somewhere with this. :P16:07
rcjrbasak: I'd SRU with the bug template to highlight testing requirements, impact, and regression potentials16:07
tsimonq2(after rbasak of course)16:07
rcjrbasak: that was a bit of a mess of an answer as I was reading the next question.  ...16:07
tsimonq2Apologies.16:07
tewardrcj: thank you for clarifying, that was the first question and I wanted to make sure that we were on the same page (I had assumed it was just for you, but I needed that confirmed thanks!)16:08
rcjOnce I had the SRU template in the bug and the MP I'd upload and get subscribe the sru team for r3eview16:08
rcjteward: np16:08
rbasakrcj: anything special for it being a feature change in the SRU, which is normally not permitted?16:08
rcjrbasak: yeah, so livecd-rootfs is an outlier here in that feature changes do get SRU'd back frequently unlike other packages in the archive which is documented on the SRU wiki for this package16:10
rbasakrcj: thanks. Do you have a link to that page please? I just looked and can't find one!16:10
rcjrbasak: https://wiki.ubuntu.com/StableReleaseUpdates#livecd-rootfs16:10
rbasakAh, gotcha, thanks.16:11
sil2100Ok, any other questions?16:11
tsimonq2See my above question.16:12
sil2100Ah, there is one indeed!16:12
tsimonq2rcj: What's your favorite part about working with livecd-rootfs?16:12
sil2100rcj: did you see tsimonq2's earlier question?16:12
tsimonq2That :)16:12
tewardsorry i got a call for work, reading back and then seeing if I have any other questions.16:13
tsimonq2I have to make a small commute quickly.16:14
rcjtsimonq2: Favorite part of working on livecd-rootfs?  Well, it's fundamental to the work I do so anything I can do to make it better is a win.  The support for parallel, consistent LP image builds is fantastic.16:14
tsimonq2Thanks.16:14
* rbasak has no more questions16:15
tsimonq2I'm ready to vote.16:15
tewardno more questions from me, also ready to vote16:15
rafaeldtinocoim ready as well16:15
sil2100o/16:15
sil2100ddstreet: any questions? I guess you're travelling now, so maybe we'll just proceed if you don't mind16:16
sil2100Ok, let's vote16:17
sil2100#vote Granting rcj PPU rights for livecd-rootfs16:17
meetingologyPlease vote on: Granting rcj PPU rights for livecd-rootfs16:17
meetingologyPublic votes can be registered by saying +1, +0 or -1 in channel, (for private voting, private message me with 'vote +1/-1/+0 #channelname)16:17
tsimonq2+116:17
meetingology+1 received from tsimonq216:17
teward+116:17
meetingology+1 received from teward16:17
sil2100+116:17
meetingology+1 received from sil210016:17
gaughenquery rcj16:18
gaughenbah16:18
sil2100HAH16:18
sil2100;)16:18
rbasak+116:18
meetingology+1 received from rbasak16:18
rafaeldtinoco+1 for being a ppu application and a *special* pkg - sru wise - that rcj is already familiar with based on merges pointed in his application wiki page. I see he seeks coredev in the future, but he also says "Make time for general distro work". I would encourage rcj to start doing this distro work sooner than later.16:18
meetingology+1 for being a ppu application and a *special* pkg - sru wise - that rcj is already familiar with based on merges pointed in his application wiki page. I see he seeks coredev in the future, but he also says "Make time for general distro work". I would encourage rcj to start doing this distro work sooner than later. received from rafaeldtinoco16:18
gaughenshush16:18
tewardgaughen: i guess your / key is broken :P16:18
tsimonq2Agreed rafaeldtinoco.16:18
sil2100rafaeldtinoco: agreed!16:18
tewardalso agree with rafaeldtinoco16:18
gaughen:-)16:18
sil2100#endvote16:18
meetingologyVoting ended on: Granting rcj PPU rights for livecd-rootfs16:18
meetingologyVotes for:5 Votes against:0 Abstentions:016:18
meetingologyMotion carried16:18
tsimonq2gaughen: I assume it's to give rcj a congrats. ;)16:19
sil2100(ended vote already since +5 can not be overriden)16:19
gaughenyou know it!16:19
rcjthank you everyone16:19
sil2100rcj: congratulations!16:19
gaughenand to tell him I was impressed with his answer on "favorite part"16:19
tsimonq2Congrats!16:19
sil2100Yeah, I guess my answer to the 'favorite part' would be "nothing"16:19
rbasakSo the next steps are https://wiki.ubuntu.com/DeveloperMembershipBoard/KnowledgeBase#Actions_after_a_successful_application16:19
sil2100j/k of course, I love livecd-rootfs myself16:19
gaughensil2100, lol16:19
sil2100rbasak: maybe someone16:20
sil2100uh16:20
sil2100rbasak: maybe someone from the new members could sign up for that?16:20
sil2100As a learning exercise?16:20
rbasakSure. Any volunteers?16:20
tsimonq2sil2100: I wasn't looking for a valid answer as much as I was looking for an answer from someone who has thought about it. :P16:20
rbasakWe'll then give that person two meeting actions (as per the docs)16:20
tewardi'll be happy to announce the successful applicants16:20
* tsimonq2 voluntells teward.16:20
sil2100#action teward to e-mail the relevant ML after the successful application16:21
meetingologyACTION: teward to e-mail the relevant ML after the successful application16:21
rbasakWe still need to discuss the meeting schedule going forwards16:21
sil2100teward: will you also deal with granting the PPU?16:21
tewardsil2100: not without guidance from an incumbent on what to send to whom, because I'm new to the board (the announcement email is the easy part)16:22
rbasakteward: it's all documented I hope!16:22
rbasakteward: where it isn't, feel free to ask me.16:22
tewardack16:22
tewardrbasak: prepare for inbound question stream16:23
rbasakThe announcement email also needs to go to a list of prescribed places16:23
sil2100Ok, assigning to teward then! Remember: feel free to ask whenever in doubt16:23
sil2100#action teward to adjust the ACLs for rcj's new PPU16:23
meetingologyACTION: teward to adjust the ACLs for rcj's new PPU16:23
sil2100Ok, moving on!16:23
tewardyep, that's the plan.  gotta fix a switch that just died though here at work first, so 30-min break then lunch :P16:23
sil2100#topic AOB16:23
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds: Please leave swords by the door | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendars | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | <wxl> be nice | DMB meeting | Current topic: AOB
sil2100rbasak: can you lead the meeting schedule discussion?16:24
rbasakSure16:24
rbasakSo we've had problems with DMB member attendence in the past.16:24
rbasakIt might be different with the new DMB.16:24
rbasakOne suggestion is to ask all DMB members immediately after an election if they are happy with the current schedule, or if they'd like to change the schedule so they can attend.16:25
rbasakWe do also have to consider the needs of applicants, of course, but if DMB members cannot attend then that clearly cannot work.16:25
rbasakSo I'd like to have a vote to ratify the current schedule, which is every two weeks on a Monday, alternating between 1500 UTC and 1900 UTC, phasing set by today's meeting.16:26
rbasakIf you expect to be able to make these meetings, please vote yes. Otherwise, please vote no, and we'll then discuss what we can do about changing the schedule.16:26
rbasakUltimately it's down to us as a group. We can change our own schedule as we wish. Under the current rules, that means that if four of us vote +1 to change the schedule, it will change.16:27
rbasakDoes this approach sound OK to everyone? Any questions?16:27
rafaeldtinocosgtm16:27
tewardyes for teh most part - there's a meeting in a month and a half I will be out that time for, details to folow because it could get canceled due to 'concerns' in the world.16:27
sil2100All good here, should I start the vote then?16:27
tewardotherwise sounds good to me16:27
rbasakI think it's fine to miss the occasional meeting. We all have lives.16:28
rbasakBut the expectation IMHO should be that we all expect to attend the majority of meetings.16:28
rbasaksil2100: please do16:28
tsimonq2+116:28
rafaeldtinoco+116:29
teward+116:29
sil2100#vote Current DMB schedule to remain as-is16:29
meetingologyPlease vote on: Current DMB schedule to remain as-is16:29
meetingologyPublic votes can be registered by saying +1, +0 or -1 in channel, (for private voting, private message me with 'vote +1/-1/+0 #channelname)16:29
rbasak+116:29
meetingology+1 received from rbasak16:29
teward+116:29
meetingology+1 received from teward16:29
tsimonq2+116:29
sil2100(please vote now ;) had issues with WORDS)16:29
meetingology+1 received from tsimonq216:29
sil2100+116:29
meetingology+1 received from sil210016:29
rafaeldtinoco+116:29
meetingology+1 received from rafaeldtinoco16:29
slashd+116:30
meetingology+1 received from slashd16:30
rbasakOK so the current schedule is staying, but for the record it's probably useful to get everyone's votes.16:30
sil2100ddstreet: are you still aroundish to cast your vote? I guess we can query you for it later16:30
rbasakI guess we'll have to wait.16:31
rbasakBut that's already helpful. Thanks everyone!16:31
sil2100Let's get in touch with him later, but yes, the timing will stay it seems16:31
sil2100#endvote16:31
meetingologyVoting ended on: Current DMB schedule to remain as-is16:31
meetingologyVotes for:6 Votes against:0 Abstentions:016:31
meetingologyMotion carried16:31
sil2100Do we have anything else for today?16:32
rbasakIf ddstreet can't make the current schedule, or if anyone's circumstances change, we can still the schedule.16:32
rbasakstill *change* the schedule16:32
rbasakNobody should feel that the current schedule is set in stone16:32
sil2100rbasak: exactly16:32
sil2100+1 to that16:32
rbasakAnd even if I can make the current schedule, if someone cannot, I'm still in favour of exploring changing it.16:32
rbasakThat's all from me. Thanks!16:32
sil2100I think we're good then16:33
sil2100Since this meeting already took longer than expected, let's finish16:33
sil2100#endmeeting16:34
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds: Please leave swords by the door | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendars | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | <wxl> be nice
meetingologyMeeting ended Mon Mar  9 16:34:02 2020 UTC.16:34
meetingologyMinutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2020/ubuntu-meeting.2020-03-09-15.05.moin.txt16:34
rbasaksil2100: thank you for chairing!16:34
sil2100Thanks everyone! This was a very productive meeting16:34
sil2100I'll clean up the agenda page16:34

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!