/srv/irclogs.ubuntu.com/2017/02/27/#ubuntu-meeting.txt

=== hggdh_ is now known as hggdh
=== maclin1 is now known as maclin
=== maclin1 is now known as maclin
=== fabo_ is now known as fabo
=== maclin1 is now known as maclin
=== lan3y is now known as Laney
=== tinwood is now known as tinwood_swap
=== yofel_ is now known as yofel
tyhickshello16:42
tyhicks#startmeeting16:42
meetingologyMeeting started Mon Feb 27 16:42:07 2017 UTC.  The chair is tyhicks. Information about MeetBot at http://wiki.ubuntu.com/meetingology.16:42
meetingologyAvailable commands: action commands idea info link nick16:42
tyhicksThe meeting agenda can be found at:16:42
tyhicks[LINK] https://wiki.ubuntu.com/SecurityTeam/Meeting16:42
tyhicks[TOPIC] Announcements16:42
=== meetingology changed the topic of #ubuntu-meeting to: Announcements
tyhicksAndreas Cadhalpun provided debdiffs for xenial and yakkety for ffmpeg (LP: #1664402 #1664403)16:42
ubottuLaunchpad bug 1664402 in ffmpeg (Ubuntu) "FFmpeg security fixes February 2017 (yakkety)" [Medium,Fix released] https://launchpad.net/bugs/166440216:42
tyhicksPaul Gevers (elbrus) provided debdiffs for trusty and xenial for cacti (LP: #1663891)16:42
ubottuLaunchpad bug 1663891 in cacti (Ubuntu Trusty) "Security uploads for cacti (trusty and xenial)" [High,Fix released] https://launchpad.net/bugs/166389116:42
tyhicksBrian Morton (rokclimb15) provided debdiffs for precise-yakkety for libssh2 (LP: #1664812)16:42
ubottuLaunchpad bug 1664812 in libssh2 (Ubuntu) "CVE-2016-0787" [Medium,Fix released] https://launchpad.net/bugs/166481216:42
tyhicksGianfranco Costamagna (LocutusOfBorg) provided debdiffs for trusty-yakkety for tcpdump (LP: #1662177)16:42
ubottuLaunchpad bug 1662177 in tcpdump (Ubuntu) "tcpdump multiple CVEs" [Medium,Fix released] https://launchpad.net/bugs/166217716:42
tyhicksThank you for your assistance in keeping Ubuntu users secure! :)16:42
tyhicks[TOPIC] Weekly stand-up report16:42
=== meetingology changed the topic of #ubuntu-meeting to: Weekly stand-up report
tyhicksjdstrand: you're up16:42
jdstrandhi!16:42
jdstrandthis week I plan to work on:16:43
jdstrandvarious snappy PR reviews (snap-confine, Personal, et al interfaces) and store reviews16:43
jdstrandreview gsettings patches16:43
jdstrandvarious policy updates for 2.2316:43
jdstrandthat's it for me16:43
jdstrandcontinue seccomp arg filtering policy16:43
jdstrandmdeslaur: you're up16:43
mdeslaurI'm on community this week16:44
mdeslaurand I'm about to release tiff updates16:44
mdeslaurand I'll be going down the list16:44
mdeslaurthat's about it, sbeattie, you're up16:44
sbeattieI'm on bug triage this week16:46
sbeattieI also have kernel signoffs to do.16:46
sbeattieafter that, I'll also be focusing on updates16:46
sbeattiethat's pretty much it for me. tyhicks, you're up16:47
tyhicksI'm on cve triage this week16:47
tyhicksI need to propose a bit of a design change for the seccomp kernel patches and send out revision 5 of the set16:48
tyhicksneed to circle back to the apparmor utils patch set to fix something that cboltz requested and then send out revision 2 of the set16:48
tyhicksI have a design review to do16:49
tyhicksand right now I'm fighting with configuration issues on my new laptop so I need to spend a little time smoothing those out16:49
tyhicksthat's it for me16:49
tyhicksjjohansen: you're up16:49
jjohansenI need to revise the gsetting patches based on review feedback, and send out the notification patchset so it can be reviewed16:49
jjohansenand I need to get back to upstreaming work, I am hoping to get an RFC out this week so I can do another pull request in a few weeks16:49
jjohansenoh and there some bugs, I need to follow up on.16:49
jjohansenthat is it for me, sarnold16:51
sarnoldI'm in the happy place this week; I'm going to release the shadow update, finish the lasso mir, AA patch reviews, and then move down the list of MIRs16:51
sarnoldthat's it for me, chrisccoulson?16:51
chrisccoulsonI plan to get our firefox packages building with rust by the end of the week16:52
chrisccoulsonI've also got to start preparing the next update, which is next week16:52
chrisccoulsonBefore I do that, I need to fix our menubar patch which currently makes it crash thanks to a late change in firefox16:52
chrisccoulsonI also need to unbreak ubufox (bug 1648649)16:53
ubottubug 1648649 in ubufox (Ubuntu) "Ubufox is broken in Firefox Nightly, due to using no-longer-supported "for each" syntax. Error console now shows "SyntaxError: missing ( after for UpdateNotifier.js:217:8"" [High,Triaged] https://launchpad.net/bugs/164864916:53
chrisccoulsonOther than that, I've got 2 large code reviews to do for oxide16:53
chrisccoulsonI suspect I might not get much else done this week16:53
chrisccoulsonthat's me done16:53
ratliffI'm in the happy place this week16:53
ratliffI'm still working on vivid updates for Core and Touch16:53
ratliffback to you, tyhicks16:54
tyhicksthanks!16:54
tyhicks[TOPIC] Highlighted packages16:54
=== meetingology changed the topic of #ubuntu-meeting to: Highlighted packages
tyhicksThe Ubuntu Security team will highlight some community-supported packages that might be good candidates for updating and or triaging. If you would like to help Ubuntu and not sure where to start, this is a great way to do so.16:54
tyhicksSee https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures for details and if you have any questions, feel free to ask in #ubuntu-security. To find out other ways of helping out, please see https://wiki.ubuntu.com/SecurityTeam/GettingInvolved.16:54
tyhickshttp://people.canonical.com/~ubuntu-security/cve/pkg/php-openid.html16:54
tyhickshttp://people.canonical.com/~ubuntu-security/cve/pkg/sleekxmpp.html16:54
tyhickshttp://people.canonical.com/~ubuntu-security/cve/pkg/collectd.html16:54
tyhickshttp://people.canonical.com/~ubuntu-security/cve/pkg/vxl.html16:54
tyhickshttp://people.canonical.com/~ubuntu-security/cve/pkg/libpdfbox-java.html16:54
tyhicks[TOPIC] Miscellaneous and Questions16:54
=== meetingology changed the topic of #ubuntu-meeting to: Miscellaneous and Questions
tyhicksDoes anyone have any other questions or items to discuss?16:54
chrisccoulsonoh, I need to sponsor chromium too :)16:54
tyhicksack16:56
tyhicksjdstrand, mdeslaur, sbeattie, jjohansen, sarnold, ChrisCoulson, ratliff: Thanks!16:56
tyhicks#endmeeting16:56
=== 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
meetingologyMeeting ended Mon Feb 27 16:56:22 2017 UTC.16:56
meetingologyMinutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2017/ubuntu-meeting.2017-02-27-16.42.moin.txt16:56
ratliffthank you, tyhicks!16:56
mdeslaurthanks tyhicks16:56
jjohansenthanks tyhicks16:56
sarnoldthanks tyhicks :)16:57
sbeattietyhicks: thanks117:01
rbasako/19:00
rbasakWho's here?19:00
bdmurrayme19:00
brookswarnerrbasak: i'm here but dont count19:01
slashdrbasak, few SEG fols are here today for the sru-uploader vote19:01
slashdfolks19:01
tinocoo/19:01
* Mmike is here19:05
* ddstreet here too19:05
=== micah_mobile is now known as micahg_mobile
rbasakI know micahg_mobile might be having connectivity issues.19:06
rbasakBut we still need one more additional DMB member for quorum.19:06
slashdrbasak, can we ping them on the channel to see if someone answer ?19:09
bdmurrayThey were pinded in #ubuntu-devel.19:10
slashdbdmurray, ack19:10
slashdtks19:10
cyphermoxo/19:13
rbasakOK we might have four if micahg_mobile manages to participate.19:14
rbasakHe said he might be more able at 1930.19:14
rbasakWho's chairing?19:14
micahg_mobileWell, we can try19:14
rbasak#startmeeting DMB19:15
meetingologyMeeting started Mon Feb 27 19:15:02 2017 UTC.  The chair is rbasak. Information about MeetBot at http://wiki.ubuntu.com/meetingology.19:15
meetingologyAvailable commands: action commands idea info link nick19:15
=== 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 | DMB Meeting | Current topic:
rbasak#topic Review of previous action items19:15
=== 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 | DMB Meeting | Current topic: Review of previous action items
chiluko/19:15
rbasakcyphermox to handle Sean Davis' xfdashboard packageset request19:15
rbasakcyphermox to refresh Kubuntu packageset19:15
rbasakcyphermox: I think both of those are done?19:15
cyphermoxboth still todo, hopefully I can get to them later19:15
rbasakOh, OK.19:15
cyphermoxfor now I'm fighting maas here.19:16
rbasak#action cyphermox to handle Sean Davis' xfdashboard packageset request (carried over)19:16
meetingologyACTION: cyphermox to handle Sean Davis' xfdashboard packageset request (carried over)19:16
rbasak#action cyphermox to refresh Kubuntu packageset (carried over)19:16
meetingologyACTION: cyphermox to refresh Kubuntu packageset (carried over)19:16
rbasak#topic Ubuntu Contributing Developer Applications19:16
=== 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 | DMB Meeting | Current topic: Ubuntu Contributing Developer Applications
rbasak#subtopic Ross Gammon (rosco2)19:16
rbasakRosco2: hello!19:16
Rosco2Hi All19:16
rbasak#link https://wiki.ubuntu.com/RossGammon/ContributingDeveloperApplication19:17
rbasakI reviewed Ross' previous application earlier.19:17
rbasakLooking for the link19:17
rbasak#link https://irclogs.ubuntu.com/2016/08/01/%23ubuntu-meeting.html#t15:2119:18
rbasakDoes anyone have any further questions for Rosco2?19:19
micahg_mobileI'm wondering what has changed19:19
micahg_mobileI see comments now, but I don't see any uploads past October19:20
cyphermoxwell, his last meeting was in august.19:20
bdmurrayokay, but 3 uploads since august doesn't seem like enough to show significance.19:21
micahg_mobile3 uploads in 6 months isn't significant and sustained contribution IMHO19:21
Rosco2No uploads recently - but some waiting for sponsorship19:21
cyphermoxI'm not saying it necessarily meets the guidelines, just that there exists uploads since last review.19:22
micahg_mobileRosco2: you're also already an Ubuntu member, so this status won't confer any additional rights19:23
rbasakRosco2: have you had any other development activity you can call out apart from uploads and uploads pending sponsorship?19:23
Rosco2Well this year so far in Ubuntu has mainly been about releases19:24
micahg_mobileNot that Contributing dev isn't a nice badge of honor as well, but just wanted to point that out19:24
Rosco2I have been ISO testing for point releases & Zesty Beta 119:24
rbasakI see 15 uploads in all and two in the sponsorship queue.19:25
rbasakLatest thing in the sponsorship queue is dated 21 Feb19:25
Rosco2There are also a few backports that have gone stale that I need to get back to19:25
rbasakAny other questions for Rosco2?19:27
rbasak#vote Grant Rosco2 Contributing Developer19:28
meetingologyPlease vote on: Grant Rosco2 Contributing Developer19:28
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)19:28
rbasak+119:28
meetingology+1 received from rbasak19:28
micahg_mobile+119:28
meetingology+1 received from micahg_mobile19:28
rbasakI think the number of uploads, even if over a long period of time and not very dense currently, adds up to significant enough. I appreciate your contributions.19:29
rbasakEspecially as Set, Timo and Daniel all appear happy with your work.19:29
micahg_mobileDitto19:29
Rosco2thanks19:29
cyphermox+1219:30
meetingology+12 received from cyphermox19:30
cyphermoxugh19:30
cyphermox+1, obviously.19:30
meetingology+1, obviously. received from cyphermox19:30
bdmurrayI guess I don't need to vote then19:30
bdmurraybut I will anyway19:30
bdmurray+119:30
meetingology+1 received from bdmurray19:30
rbasak#endvote19:30
meetingologyVoting ended on: Grant Rosco2 Contributing Developer19:30
meetingologyVotes for:4 Votes against:0 Abstentions:019:30
meetingologyMotion carried19:30
rbasakCongratulations Rosco2 and thank you for your contributions.19:31
rbasakCan someone volunteer to sort that and announce it please?19:31
Rosco2Your'e welcome. Tanks for your time everyone19:31
rbasak#action rbasak to add Rosco2 to the contributing developer team19:32
meetingologyACTION: rbasak to add Rosco2 to the contributing developer team19:32
rbasak#action rbasak to announce Rosco2's new contributing developer team membership19:32
meetingologyACTION: rbasak to announce Rosco2's new contributing developer team membership19:32
rbasak#topic SRU uploader proposal19:32
=== 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 | DMB Meeting | Current topic: SRU uploader proposal
rbasak#link https://lists.ubuntu.com/archives/ubuntu-devel/2017-February/039690.html19:32
rbasakMy position is a +1 already obviously.19:32
bdmurrayrbasak: Do you expect people to already have some upload rights before applying to this new team? If so what kind?19:33
rbasakTo the other board members: opinions? Objections? Anything I can address before a vote?19:33
rbasakbdmurray: no, I expect new members of this team to be uploading directly for the first time by joining it.19:33
chilukrbasak that's why it's a great idea ^^19:34
rbasakRight, as a stepping stone.19:34
bdmurrayrbasak: directly uploading for the first time to main / restricted?19:34
rbasakbdmurry: yes. But in stable releases only, for things that meet SRU policy only.19:34
sarnoldrbasak: as a member of the security team but not core-dev I've got similar privileges; it's a bit strange to have privileges to push updates to ~25M machines but not to check in changes to -devel. But it'd be far more annoying to have to go through patch piloting for every change..19:34
rbasakbdmurray sorry :)19:34
micahg_mobileSarnold, that was a loophole I meant to address several years ago :)19:35
sarnoldmicahg_mobile :)19:35
bdmurrayI guess I have concerns as an SRU team member about keeping up with the volume of reviews. Its some what challenging as it is.19:35
rbasakbdmurray: I do expect the DMB to grant this only to applicants who have shown that they understand SRU policy and procedure by having a good track record of doing these things. And there would be a second sanity check through the SRU team anyway. But if there's any concern that an applicant will bother the SRU team, I'd expect that application to be refused.19:36
chilukbdmurray.. .ubuntu-sru team would still have to approve the upload.19:36
tinocobdmurray: it would be the same amount since our case load wouldn't change19:36
bdmurraytinoco: its not just a team for you though, anybody could apply to join it.19:36
rbasakbdmurray: it might also be reasonable to expect endorsements for the SRU team and refuse an application if there aren't any. I hadn't considered that before.19:36
micahg_mobileBdmurray: I brought that up at the last meeting and was told the load would be the same19:36
rbasakmicahg_mobile: yeah that's MHO.19:37
tinocoyou can control the load with the amount of people you approve. controlling bottleneck in the sru team if needed.19:37
rbasakI don't see any reason why this would open the floodgates to the SRU team.19:37
micahg_mobileI can forsee such a case :)19:38
rbasakCurrently the demand comes from Canonical STS who are getting their SRU requests sponsosred anyway19:38
rbasakUploads under this scheme would either be acceptable to the SRU team, or not.19:39
rbasakIf they're acceptable, then we should be taking them and growing the SRU team even if it does increase workload. Why should we be turning down good SRU contributions?19:39
bdmurrayI don't think saying "we can't have more people in the team because the SRU team is overloaded" is fair19:39
rbasakIf they're not acceptable, then I'm proposing that we don't grant membership of this team to such applicants.19:39
micahg_mobileYeah, but once we compress the feedback window by eliminating sponsorship, there's the potential to start throwing more fixes in19:39
rbasakmicahg_mobile: that's true, but that's a good thing surely?19:40
bdmurrayWill there be a way for an SRU team member to request removal of somebody from the team?19:40
rbasakbdmurray: who do you think is saying that?19:40
rbasakrequest removal> I'm not sure the DMB has ever had to do that before, but if it came up, it would presumably be the DMB who would handle it.19:41
rbasak(and I think we have the remit)19:41
bdmurraytinoco said "you can control the load with the amount of people you approve"19:41
rbasakAh, OK.19:41
tinocobdmurray: totally agree on what you are saying19:41
rbasakI'd take a request to have someone removed from any uploading team quite seriously.19:42
bdmurrayIf there is a way for the SRU team to get people removed I'd feel better. Although the SRU team would need a way to keep track of rejections I guess.19:42
rbasakAnd perhaps the DMB should deal with that in private or something.19:42
rbasakBut given the SRU team have to review everything anyway, it would make no sense for the DMB to refuse to remove someone the SRU team want removed.19:43
rbasakSo how about:19:43
rbasak1) We expect SRU team endorsement on any application.19:44
rbasak2) The SRU team can ask for any SRU uploader to be removed.19:44
rbasaks/expect/require/ if you prefer.19:44
rbasakWhether the SRU team think any single SRU team member should be able to request removal, or it needs a majority, or what, could perhaps be entirely up to them.19:45
rbasakBy "can ask for" I mean "the DMB will do it".19:46
micahg_mobileIt should be either a majority of the SRU team or DMB votes (or both)19:46
bdmurrayThe SRU team is rather large so majority seems like a lot to me.19:47
micahg_mobileOk, I just want some checks here19:47
rbasakTaking off my SRU team hat for a moment, I was thinking of leaving how they want to resolve their decision as up to them.19:47
micahg_mobileDMB vote is fine even if 1 person requests the DMB to review19:48
rbasakLet me write this down: http://pad.ubuntu.com/m9xRiL8pyP19:49
rbasakHow does that look? Does that cover all options that have been proposed?19:52
bdmurrayI don't think "requires" SRU team member endorsement is necessary.  SRU sponsor would be fine.  Its harder to find the SRU accepter than it is the SRU sponsor.19:53
bdmurrayAs an SRU team member I don't recall good uploads rather its the rejects I remember more.19:54
bdmurrayI'd also like to see members of this ubuntu-sru-uploaders team not leave stuff languishing in -proposed.19:55
bdmurrayThe pending-sru report is full of sadness.19:55
slashdbdmurray, most of our work in STS requires to SRU to be Fix Release before we close the support ticket with customer19:56
slashdso it won't be a problem for us19:56
chilukbdmurray, so that's an additional permission bit... promotion from -proposed -> -updates... are you proposing that ubuntu-sru-uploader have those rights?19:57
bdmurraychiluk: No, I'm saying verify your uploads if nobody else does.19:57
tinocochiluk: i believe he said for us to verify things more quickly.19:57
slashdchiluk, I think he is talking about the verification-done step19:58
micahg_mobileI agree with bdmurray on the endoresements piece19:58
micahg_mobileAnd rbasak on how a member should be removed19:58
slashdbdmurray,rbasak, Does this potential sru-uploader team would be able to nominate bugs for release without approval ?19:59
rbasakslashd: I think that's a separate issue.19:59
slashdrbasak, ack19:59
rbasakAnd doesn't really fall under the DMB.19:59
rbasakIt's a bug squad/bug control thing.20:00
slashdok, disregard my last comment then20:00
rbasakWe should still address that, but not at the DMB.20:00
bdmurrayrbasak: it might just work with the acl20:00
rbasakI'm hoping so :)20:00
rbasakcyphermox: opinions?20:01
chilukrbasak, i'm part of both bug control and bug squad teams, and don't have permission to approve nominated releases...20:01
rbasakchiluk: I'm aware :)20:01
chilukrbasak do you know what team I'm missing?20:01
rbasakchiluk: I believe you get it if you can upload the package.20:01
rbasakBut let's talk about that another time.20:01
rbasakBack to the pad20:02
rbasakFor joining, I'm happy to not require 2 either.20:02
bdmurrayupload the package or member of a special ubuntu-release-nominators team20:02
micahg_mobileUploader rights for the package or there are two other teams I think, ubuntu-release and I thought we made one team that didn't have other rights attached to it20:03
micahg_mobileThat's it20:03
rbasakbdmurray, micahg_mobile: how does the pad look for you now? Are you comfortable with what we have now?20:04
bdmurrayCan we resolve line 1?20:04
rbasakGood point.20:04
rbasakI'm happy either way.20:05
micahg_mobileYeah, I think it is fine20:05
rbasakI guess that means I say "expected".20:05
rbasakBut if someone wants to tighten it to "requires" I'm fine with that.20:06
bdmurrayThat's what I expect20:06
rbasakNow that's a confusing statement :-)20:06
rbasakYou expect someone to tigthen it to "requires"? :-P20:06
bdmurrayI expect it to say excpet not requires20:06
rbasakOK I'll change it.20:07
rbasakAnd let me take out 2, since we seem to have some consensus it isn't required.20:07
rbasakcyphermox: ?20:09
cyphermoxsorry, I'm busy20:10
rbasakOK20:11
rbasakmicahg_mobile, bdmurray: are you +1 on the current pad?20:12
bdmurrayyes20:12
micahg_mobileYes20:13
rbasakGreat, thanks! I guess there's no need for a formal meetingology vote for the sake of it.20:13
rbasakWe'll need one more +1.20:13
rbasakShall we move on and let the others vote offline?20:13
rbasakI will copy the pad, clean up and post it to the thread.20:14
micahg_mobileRbasak: Shows up in the meeting logs as a vote :)20:14
rbasak#topic Expiring DMB members20:14
=== 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 | DMB Meeting | Current topic: Expiring DMB members
micahg_mobileCan we change members to membership please?20:15
rbasakmicahg_mobile: you mean line 1120:15
rbasak?20:15
micahg_mobileCurrent topic :)20:15
rbasak#topic Expiring DMB membership20:16
=== 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 | DMB Meeting | Current topic: Expiring DMB membership
rbasakcyphermox pointed out that his membership expires soon20:16
rbasak2015-03-0220:16
cyphermoxyep, in 4 days20:16
cyphermoxFWIW, +1 on the SRU proposal from me20:16
rbasakOh great, thanks. Then it's done :)20:16
rbasak\o/20:16
rbasaks/2015-03-02/2017-03-01/20:17
cyphermox... or less than four days20:17
rbasakYeah, so we need to organise nominations and a vote for cyphermox's seat, right?20:17
rbasakcyphermox: are you intending to stand again?20:17
micahg_mobileI think the first thing would be to ask the TB to extend cyphermox's membership 4 weeks so we can hold an election20:17
cyphermoxrbasak: I'm not sure.20:17
rbasakmicahg_mobile: that sounds reasonable. Everyone happy with that?20:18
bdmurray+1 for the extension20:18
bdmurrayDoesn't Adam expire this year too?20:18
rbasak#agreed The DMB will ask the TB to extend cyphermox's membership 4 weeks so we can hold an election20:19
rbasakYes, 2017-08-0320:19
rbasakShould we hold an election early for that seat too, or wait?20:19
cyphermoxask infinity?20:19
bdmurrayI guess it is 5 months20:19
micahg_mobileHis membership expires in August, we could seek 2 now and have the second one's term start in August20:19
rbasakI'm fine either way20:20
rbasakAlso, would it be an idea to adjust term lengths to get those two seats lined up?20:20
bdmurrayAre we excluding anybody by holding the election early?20:20
rbasakJust to save admin in the future. I don't think anyone will care about the length adjustments, will they?20:20
micahg_mobile18 months or so for the second one I guess20:21
rbasakYeah that sounds right20:22
rbasakOK so two things20:22
rbasak1) Hold an election for infinity's seat now, together with cyphermox's seat.20:23
rbasak2) Shorten infinity's seat's next term to coincide expiry with cyphermox's seat's next term.20:23
rbasakPresumably we'd hold the usual ranked CIVS thing and give the top result the longer immediate seat, and the second result the shorter delayed seat?20:24
rbasakEveryone happy with that?20:24
bdmurray0) ask for extension for cyphermox20:24
rbasakYep20:25
* rbasak minuted that already :)20:25
rbasakI thought that was uncontroversial :)20:25
bdmurrayokay20:26
rbasakcyphermox? micahg_mobile?20:26
cyphermoxheh, either way is fine by me20:27
slashdrbasak, with regard to the sru-uploader team ... what are the next steps ? Do you guys need more votes or we can already say it is officially approved ?20:29
slashdand when do you think ppl can start applying for this new team ?20:32
rbasakslashd: I'll sort it on the mailing list afterwards.20:33
slashdrbasak perfect, tks20:33
slashdtks all for your time about this subject20:33
micahg_mobileRbasak, I'm good with that20:35
rbasakGreat, thanks!20:36
rbasakAny volunteers to sort it out?20:36
bdmurraywhich thing?20:38
bdmurrayIf its the SRU team thing could we break up the tasks?20:38
rbasakThe three things - extending cyphermox's term, organising the vote, announcing the adjustment of terms, etc.20:38
rbasakI'm happy to take sorting out the SRU team thing.20:39
bdmurrayI guess we can't make cyphermox do it20:39
bdmurraySo I'll do it20:39
rbasakThank you!20:40
rbasak#action bdmurray to sort out votes and related items in respect of the two upcoming expiring DMB memberships20:41
rbasak#action rbasak to sort out the SRU uploaders team20:41
meetingologyACTION: bdmurray to sort out votes and related items in respect of the two upcoming expiring DMB memberships20:41
meetingologyACTION: rbasak to sort out the SRU uploaders team20:41
rbasak#topic Any other business20:41
=== 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 | DMB Meeting | Current topic: Any other business
rbasakAnything else to raise?20:41
chilukrbasak.. my core dev application status?20:41
rbasakLet me check.20:41
chilukthanks.20:42
bdmurrayI may have replied privately not publicly.20:42
rbasakSo there was no vote from anyone at the IRC meeting, correct?20:43
chilukrbasak not that I recall ...20:44
micahg_mobileI'm sorry, I thought that was addressed in the last meeting, but I don't remember the conclusion20:44
rbasakI count +1s from sil2100, BenC and cyphermox.20:45
rbasakbdmurray: I don't see a private or public vote from you, nor from Adam.20:46
bdmurrayrbasak: looking20:46
rbasakAnd I had deferred for the ~ubuntu-sru-uploader topic. Now that is resolved, I need to look again, but I suspect the reason I did that was because I felt that would be more appropriate.20:46
rbasakBut I'll give myself an action to look again properly.20:46
bdmurrayI see a sent mail about it20:47
rbasak#action rbasak to vote on chiluk's core dev application20:49
meetingologyACTION: rbasak to vote on chiluk's core dev application20:49
bdmurrayresent it20:49
rbasakAh20:50
rbasakI see it.20:50
rbasakIn that case, I don't need to do anything :)20:50
rbasak#undo20:50
meetingologyRemoving item from minutes: ACTION20:50
rbasakchiluk: congratulations :)20:50
chilukWOOHOO!20:50
chilukthanks guys.20:50
rbasakNow this one we _can_ give to cyphermox :-)20:51
rbasak#action cyphermox to add chiluk's core dev membership20:51
meetingologyACTION: cyphermox to add chiluk's core dev membership20:51
rbasak#action cyphermox to announce chiluk's core dev membership20:51
meetingologyACTION: cyphermox to announce chiluk's core dev membership20:51
rbasakcyphermox: seems only fair as bdmurray is handling your seat :-)20:51
rbasakOK. AOAOB?20:51
rbasakI guess we're done then!20:52
rbasakThank you all for your patience. Long meeting!20:52
rbasak#endmeeting20:52
=== 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
meetingologyMeeting ended Mon Feb 27 20:52:29 2017 UTC.20:52
meetingologyMinutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2017/ubuntu-meeting.2017-02-27-19.15.moin.txt20:52
=== inaddy is now known as tinoco

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