/srv/irclogs.ubuntu.com/2019/01/28/#ubuntu-meeting.txt

rbasako/19:00
rbasakWho's here?19:00
rharpero/19:00
tsimonq2Heya.19:01
slashdo/19:01
cyphermoxo/19:02
rbasakWe have quorum!19:02
rbasakAny chair volunteers?19:02
tsimonq2Sure.19:02
tsimonq2#startmeeting Ubuntu Developer Membership Board19:02
meetingologyMeeting started Mon Jan 28 19:02:59 2019 UTC.  The chair is tsimonq2. Information about MeetBot at http://wiki.ubuntu.com/meetingology.19:02
meetingologyAvailable commands: action commands idea info link nick19:02
=== 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 | Ubuntu Developer Membership Board Meeting | Current topic:
blackboxsw\019:03
slashdI'll chair the next one19:03
tsimonq2#topic Review of previous action items19:03
=== 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 | Ubuntu Developer Membership Board Meeting | Current topic: Review of previous action items
tsimonq2#subtopic cyphermox to handle the recent three packageset requests19:03
cyphermox*not* all done, sorry.19:03
tsimonq2Alright, we'll carry the agenda item.19:03
cyphermoxsome of this is dependent on seed changes that the requesters should do beforehand, I need to get back to them19:03
cyphermox(and making sense of all the changes, there's a fair amount)19:04
tsimonq2Sure, thanks.19:04
tsimonq2#topic Package Set/Per Package Uploader Applications19:04
=== 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 | Ubuntu Developer Membership Board Meeting | Current topic: Package Set/Per Package Uploader Applications
tsimonq2#subtopic Ryan Harper application for PPU19:04
tsimonq2rharper: Hello!19:05
rharpertsimonq2: Hi!19:05
tsimonq2Could you introduce yourself?19:05
rharpersure,  I'm Ryan Harper;  I work for Canonical, on the Ubuntu Server team, since Oct 2013;  I've been using Ubuntu since oh, say, Breezy19:06
tsimonq2Cool :)19:06
tsimonq2For reference: https://wiki.ubuntu.com/RyanHarper/DeveloperApplicationPPU19:06
tsimonq2Does anyone have any questions for rharper?19:06
rharpercd installs to make my ThinkPad actually work well.  I've been in Open Source for about 20 years or so;  I've lots of experience with kernel, virtualization, servers, embedded systems, and at Canonical mostly focused on storage, networking, and cloud-init as well19:07
jbichao/19:07
rbasakI guess we should ask the usual questions then?19:09
slashdrharper, I didn't look in lp do you have any upload right atm ?19:09
rharperslashd: no, I do not have any upload rights at this time19:09
rharperPPAs don't count, I think for your question19:09
slashdrharper, right was talking about the ubuntu archive19:10
rharperyes, no upload rights to the archive19:10
slashdrharper, where would you look if a package you have uploaded get stuck in -proposed to find the reason why it is stuck ?19:11
tsimonq2rharper: Let's say either of these two packages are stuck in the -proposed pocket of the development release. What would you look at to see why that is the case?19:11
tsimonq2slashd: Jinx.19:11
tsimonq2(It's the same question.)19:11
slashdtsimonq2, lol19:11
sarnoldlol19:12
rharperI would look in the queue for the various releases, (upload queue)19:12
slashdbut let's say the package has been approve and build in -proposed (the package at this point is no longer in the upload queue)19:12
slashdbut didn't get release in -updates after a while19:12
slashdwhere would you look to see what's going on with that package and see why it is not release yet19:13
rharperfor SRUs, I track a release in a bug which has links to the various bugs that all need verified before it can be released19:14
rharper This page tracks which packages have pending srus; http://people.canonical.com/~ubuntu-archive/pending-sru.html19:15
slashdrharper, yep that's the answer I was looking for tks19:15
rharperok, for our projects, cloud-init/curtin we have an exception which has us track all of the bugs our upload will fix, and run verification on all of those; so we're the ones doing most of the testing19:16
rbasakrharper: what about for the development release?19:17
rharperrbasak: well, SRU's aren't for the development release;19:17
rbasakNo, I mean non-SRUs19:18
rbasakWhen you upload to the development release.19:18
rbasakSay for example you upload a new cloud-init to Disco, and you see something like this (but for cloud-init): https://launchpad.net/ubuntu/+source/libphp%2Dphpmailer19:18
jbicharharper: cloud-init was uploaded to disco on Saturday. Where would you check to find out why it isn't in disco yet (but only in disco-proposed)?19:19
rbasakIn this example you'll have just uploaded 6.0.6-0.1.19:19
rbasakWhat would you do next?19:19
rharperrbasak: for devel uploads, i'd check to see if the package failed to build, http://qa.ubuntuwire.org/ftbfs/19:21
rbasakrharper: let's say it doesn't appear there. What next?19:22
rharperthere may be a dependency that hasn't landed yet,19:23
rharperthat is, something else may be holding up other packages from going into the archive;  In the absense of information, I'd likely head to #ubuntu-release and ask for some help19:26
tsimonq2That could be correct, but how do you confirm that?19:26
cyphermoxrharper: do you know where the migration report lives?19:28
cyphermoxtsimonq2: rbasak: I think we would do well to be clearer with our questions so that what we're looking for isn't ambiguous19:28
rharpercyphermox: no, I've not seen that URL19:28
cyphermoxack19:29
slashdrharper, one last question for me ... talking about devel release ... when should you stop introducing new features for let's say 'cloud-init' (for the current devel cycle) ?19:29
cyphermoxrharper: see https://wiki.ubuntu.com/ProposedMigration19:29
rharperslashd: each ubuntu cycle has a FeatureFreeze date set by the release schedule;  ideally we'll need to have landed all of those features before that date;  otherwise we need FeatureFreeze Exceptions19:30
slashdrharper, tks19:31
jbicharharper: are you familiar with the term NBS?19:31
rharpercyphermox: thx19:31
rharperjbicha: no, I've not seen that19:31
jbicharharper: the term comes from Debian and means "no longer built from source". See https://people.canonical.com/~ubuntu-archive/nbs.html19:32
jbichain this case, netplan.io has stopped building its nplan transitional package but cloud-init still depends on that package name19:32
rharperjbicha: interesting; yes we'll need disco to use the new name in the disco archive, we'll maintain the older deps in a our per-release branches ;19:34
jbichaI don't think you're going to need that page very often; it's very specific to a particular kind of archive maintenance work19:34
jbichait's not required for this application at all, I was just mentioning it as something your team can follow up on later19:34
cyphermoxit's also something that shows up elsewhere19:34
cyphermox(in other reports)19:34
rharperjbicha: indeed19:35
jbichaI don't have any other questions today 😊19:35
blackboxswrharper: from my end, both cloud-init and curtin projects have a number of tools and scripts to streamline our release process. What do you feel could use more improvement to ensure quality or ease of release for the SRU verification process?19:35
rharperblackboxsw: I think our biggest challenge is regression detection;  cloud-init runs in so many places, and we have to deal with upgrades and new instances; it's quite hard to ensure we've got as much coverage as possible;  We've got on our list (with partners) to enable more CI on target platforms; which will help raise confidence that releasing things won't break customers19:37
tsimonq2Any other questions or are we ready to vote?19:38
jbichacloud-init is one of my favorite things made by Canonical :)19:38
tsimonq2^19:39
cyphermoxready to vote.19:39
slashdtsimonq2, I'm good to vote19:39
tsimonq2#vote rharper PPU for cloud-init, curtin19:40
meetingologyPlease vote on: rharper PPU for cloud-init, curtin19:40
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:40
jbicha+119:40
meetingology+1 received from jbicha19:40
tsimonq2+119:40
meetingology+1 received from tsimonq219:40
slashd+119:41
meetingology+1 received from slashd19:41
cyphermox+119:41
meetingology+1 received from cyphermox19:41
tsimonq2rbasak?19:42
rbasak+0 rharper is on my team at Canonical, so my usual (personal) policy applies: I abstain unless everyone else present is unanimously +1 and my vote is required for quorum or some other procedural issue.19:42
meetingology+0 rharper is on my team at Canonical, so my usual (personal) policy applies: I abstain unless everyone else present is unanimously +1 and my vote is required for quorum or some other procedural issue. received from rbasak19:42
tsimonq2ah19:42
tsimonq2#endvote19:42
meetingologyVoting ended on: rharper PPU for cloud-init, curtin19:42
meetingologyVotes for:4 Votes against:0 Abstentions:119:42
meetingologyMotion carried19:42
rbasakrharper: congratulations!19:42
tsimonq2rharper: Congratulations. :)19:42
slashdCongrats rharper19:42
blackboxswwoot!19:42
rharper\o/19:42
tsimonq2Anyone want to volunteer to handle ACLs?19:43
slashdtsimonq2, I'll do it19:43
* blackboxsw is greatful for the help rharper can now provide19:43
tsimonq2Alright, cool.19:43
sarnoldrharper: congratulations :)19:43
tsimonq2#topic AOB19:43
=== 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 | Ubuntu Developer Membership Board Meeting | Current topic: AOB
blackboxsw*grateful19:43
tsimonq2Anything else, folks?19:43
rharpersarnold: thanks!19:43
rbasaktsimonq2: could you assign actions for slashd please, so we can track it?19:43
rbasakhttps://wiki.ubuntu.com/DeveloperMembershipBoard/KnowledgeBase#Actions_after_a_successful_applications19:43
rbasakcalls for two actions19:44
rbasakslashd: and that link has instructions for you too19:44
slashdrbasak, I appreciate it19:44
tsimonq2rbasak: Oh, sure.19:45
tsimonq2#action slashd to handle ACLs for rharper's PPU application19:45
meetingologyACTION: slashd to handle ACLs for rharper's PPU application19:45
tsimonq2#action slashd to announce rharper's successful application19:45
meetingologyACTION: slashd to announce rharper's successful application19:45
tsimonq2Alright, anything else?19:46
rbasakThanks!19:46
rbasakThere was a suggestion to better document what we expect applicants to know.19:46
tsimonq2#action tsimonq2 to better document what we expect applicants to know19:47
meetingologyACTION: tsimonq2 to better document what we expect applicants to know19:47
rbasakThanks :)19:47
tsimonq2So we have it for the record. :)19:47
tsimonq2#endmeeting19:47
=== 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 Jan 28 19:47:23 2019 UTC.19:47
meetingologyMinutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2019/ubuntu-meeting.2019-01-28-19.02.moin.txt19:47
rbasaktsimonq2: thank you for chairing!19:47
tsimonq2Thanks everyone!19:47
cyphermoxta tsimonq219:48

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