#ubuntu-meeting-2 2016-07-19
 * slangasek waves
<mdeslaur> \o
<slangasek> wiki page says infinity or kees is chairing
<slangasek> infinity is at a sprint right now so I'm not sure he'll make it
<bregma> kgunn is at the same sprint (I believe) so I'll be substituting for him today
<mdeslaur> hi bregma
<kees> \o
<kees> so I'm chairing?
<mdeslaur> kees: congrats
<kees> #startmeeting
<meetingology> Meeting started Tue Jul 19 16:04:16 2016 UTC.  The chair is kees. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
<meetingology> Available commands: action commands idea info link nick
<kees> #topic action review
<kees> #meetingtopic action review
<kees> uhm... wtf
<kees> [topic] hello bot
<kees> so, infinity is out, so I guess I'll skip his actions?
<mdeslaur> sure
<kees> "mdeslaur to look into flavour CVE tracking"
<mdeslaur> you can carry mine forward too, I haven't had time to work on that yet
<kees> done!
<kees> #topic unity 8 PPA
<bregma> this is regarding https://bugs.launchpad.net/unity8-desktop-session/+bug/1585362
<bregma> we require either formal TB approval or rejection
<slangasek> [LINK] https://bugs.launchpad.net/unity8-desktop-session/+bug/1585362
<slangasek> right
<slangasek> I would've liked to get the discussion on this one started on the mailing list, given that I'm not sure we'll finish in a live TB meeting, but ENOTIME :/
<slangasek> so this kind of question has come up in various forms over time
<kees> uuhhh... adds a PPA to to sources by default? no. put in -proposed? I don't understand the problem?
<mdeslaur> The list of packages in the PPA is troubling, since it contains more than just unity 8 stuff, like a newer network-manager, etc.
<mdeslaur> I don't think that's appropriate
<slangasek> kees: the problem is that this is the ppa that contains the various packages which have been forked for the phone product and have not been SRUed into the release
<bregma> the over all goal is to make it as simple and easy as possible for people to test the Unity 8 desktop on 16.04 without a two-step (and hence error-prone) process
<kees> the language in this bug doesn't explain anything to me. is this for _testing_, or is this for _default_?
<kees> if it's for testing, why is the TB needed?
<mdeslaur> the issue is that installing that PPA is likely to break people's systems...
<slangasek> this is for opt-in to the unity8 stack, for end users
<slangasek> the current unity8 stack, in the ppa, which is not the same as the one in xenial
<bregma> it's definitely not for default 16.06, not for default 16.10 which should have all the required packages in main by then
<slangasek> because the phone team's process has very good CI to prevent regressions for their stack, but having to regression-test it in Ubuntu for all other use cases would slow down development to a molasses pace - so they generally haven't been SRUing
<kees> I still do not understand the problem: adding a PPA is already trivial for end users to do. what is the issue that needs TB approval?
<slangasek> kees: they wanted auto-ppa enablement on package install
<kees> no.
<kees> :P
<mdeslaur> the approval is for the ppa to be automatically enabled with a xenial update of one of the unity 8 packages
<kees> that's not how Ubuntu does things. :)
<kees> if someone wants to test new unity8, they can run the ppa adding tool. it's a single command line... ?
<kees> it seems like if someone can't do that, they shouldn't be testing things that will break their system.
<mdeslaur> I'm not sure the simple question that gets asked on that package upgrade is enough to inform users of what enabling that ppa entails
<bregma> users, eben the technically inclined, have a history of clicking on shiny things without reading the documentation first, a one-click install is less error-prone
<mdeslaur> for example, will the new network-manager in there break their kde or gnome desktop?
<slangasek> it's not really one commandline, because it's "apt-add-repository <magicstring>; confirm scary commandline prompt; apt-get update; apt-get dist-upgrade"
<kees> and if that's too scary, you want someone to test a system-breaking ppa that can't handle said scariness?
<slangasek> I personally find the apt-add-repository interface much less simple than I think it ought to be :)
<kees> how about adding "update and dist-upgrade" to the apt-add-repository script?
<slangasek> +1 from me on that, but I'm not sure if that addresses kgunn/bregma's issue
<mdeslaur> how about simply adding a "enable-unity8-ppa" tool that prints an appropriate warning?
<kees> mdeslaur: is that any better than apt-add-repository?
<mdeslaur> if the objection is that apt-add-repository is not discoverable and has scary messages, then a more specialized tool would fix that
<mdeslaur> bregma: what testing is performed in that PPA to make sure it doesn't break kde or gnome desktops?
<slangasek> should we discuss the reasons why the packages in question are in this extra ppa in the first place?
<bregma> mdeslaur, at the moment there is mostly informal testing of the PPA on desktop, we're working on mringing that up to par
<slangasek> mdeslaur: the ppa is primarily the phone ppa; so the baseline testing for GNOME/KDE compatibility is 0
<bregma> we are working on MIR for these packages for 16.10, so this should not be a problem going forward
<mdeslaur> right, so that would be my first objection...someone runs gnome, installs the unity 8 desktop to try it out, and it breaks their main gnome desktop
<slangasek> even if bregma's team made that part of their test plan for their updates, there are bound to be other updates landing there to fix phone issues that may not have been tested by them on the desktop
<slangasek> and might get pulled in if the ppa is enabled
<bregma> yes
<slangasek> bregma: sorry, I don't understand how the MIR changes things
<mdeslaur> bregma: how is a MIR going to fix the issue of rapid releases?
<bregma> they're going either have to branch their upstream projects like everyone else does so they can support Ubuntu as well as the phone
<slangasek> fwiw I have been of the view for some time (with my SRU team hat on) that I would like to see more of the packages that land in the overlay ppa SRUed into Ubuntu
<slangasek> the SRU process adds calendar time, and should not block the phone team from getting updates done
<bregma> agreed, and that's part of how I see convergence working
<slangasek> but in general, since these packages also all exist in the main Ubuntu archive and are considered abandonware / not fit for purpose in those versions, I think ideally they would get SRUed and not just published to the overlay
<bregma> our goal is to see Unity 8 in the ISO as an alternative session for 16.10 (hence the MIRs), which would require branching upstream so a rapid cadence contines in the PPA but changes get SRUd into the Ubuntu archives
<slangasek> however I know that getting SRUs done for each package is going to increase the load on the development team; so is that feasible at this stage?
<mdeslaur> +1
<slangasek> bregma: ok.  so you're saying that's the roadmap for 16.10 forward, there would be landings in both the overlay ppa and as SRUs, but that's not on the roadmap for 16.04?
<bregma> well, 16.04 has already been released, so I would see that as being a technical challenge
<slangasek> bregma: from my POV, it seems technically possible to start SRUing packages onto 16.04 today, forking off of the existing packages in the overlay and putting them through the SRU process
<bregma> slangasek, yes, it's possible although they would remain in universe of course
<slangasek> i.e. I don't see any difference, technically, between doing this now for 16.04 vs. doing this for 16.10
<bregma> we have just not considered doing that
<slangasek> ok
<slangasek> if you went that route, you wouldn't need the TB's blessing for anything; you'd be using the standard SRU process
<slangasek> and it means the updates would get verified to ensure they don't regress other stacks in Ubuntu, which is a nice assurance
<slangasek> but it also obviously means more team for your work to prep and validate those SRUs - no shortcuts there
<slangasek> more team for your work? hello brain
<bregma> that work will need to be done for 16.10 and onward, it's a matter of accelerating the plan
<bregma> but given that adding the PPA could possibly break other desktops resulting in increased support workload, it's a worthwhile consideration
<bregma> I will take the suggestion back to the decision makers and defer the question of adding the PPA with the package install until that is resolved
<slangasek> ok
<kees> alrighty. settled for now, it seems...
<slangasek> btw I do remember internal discussion earlier about having a separate ppa for just the converged stack, with different requirements for contents
<slangasek> should I assume the consensus in the TB is that auto-enabling this on package install would also be unacceptable, regardless of the criteria for the ppa?
<mdeslaur> I would vote -1 on auto-enabling it, yes
<slangasek> ok
<slangasek> bregma: you have enough guidance then? :)
<slangasek> (should we have a formal vote on the auto-enable question, for the record?)
<bregma> one question:  would this be a "standing SRU" or separate SRUs required for each update?
<slangasek> bregma: for packages that Canonical is the upstream for within that stack, I would prefer we figure out a standing SRU policy for them that doesn't require writing per-update test cases
<slangasek> when it touches other packages in the archive, those would need to be more ad hoc
<bregma> OK
<bregma> I think I have enough guidance on this, then
<bregma> I would like a formal vote on the matter to take back to my masters
<kees> #topic mailing list
<kees> erf, vote on which piece?
<mdeslaur> auto-enabling of the PPA
<slangasek> I'd posit [VOTE] decline to grant exception for auto-enabling of stable-phone-overlay ppa on unity8 package install; recommend convergence team work with SRU team to include their changes in the main Ubuntu archive"
<kees> so, "should package installs be allowed to auto-enable third-party PPAs?" is that the right language?
<slangasek> maybe with fewer words
<kees> I don't like the inverted question, let's try this...
<kees> #vote grant exception for auto-enabling of stable-phone-overlay ppa on unity8 package install?
<meetingology> Please vote on: grant exception for auto-enabling of stable-phone-overlay ppa on unity8 package install?
<meetingology> Public votes can be registered by saying +1, +0 or -1 in channel, (for private voting, private message me with 'vote +1/-1/+0 #channelname)
<kees> -1
<meetingology> -1 received from kees
<mdeslaur> -1
<meetingology> -1 received from mdeslaur
<slangasek> -1
<meetingology> -1 received from slangasek
<kees> #endvote
<meetingology> Voting ended on: grant exception for auto-enabling of stable-phone-overlay ppa on unity8 package install?
<meetingology> Votes for:0 Votes against:3 Abstentions:0
<meetingology> Motion denied
<bregma> thank you for your time
<slangasek> bregma: thank you!
<kees> and, for the second part, there's not really a vote needed: the recommendation would be to work with the SRU team.
<slangasek> ok
<slangasek> mailing list? :)
<kees> right.
<kees> so, nothing new there (this topic was the only one I saw)
<kees> #topic bugs
<kees> nothing new
<kees> #topic aob
<kees> anything?
<slangasek> not here
<mdeslaur> nope
<kees> #topic chair selection
<kees> looks like mdeslaur with slangasek as backup?
<slangasek> or would it be infinity with mdeslaur backup?
<slangasek> (doesn't matter :)
<kees> hm, yeah
<kees> okay, infinity with mdeslaur
<mdeslaur> ack
<kees> okay, thanks everyone!
<kees> #endmeeting
<meetingology> Meeting ended Tue Jul 19 16:51:05 2016 UTC.
<meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting-2/2016/ubuntu-meeting-2.2016-07-19-16.04.moin.txt
<mdeslaur> thanks bregma!
<mdeslaur> thanks everyone
#ubuntu-meeting-2 2017-07-18
 * slangasek waves
<mdeslaur> \o
<infinity> o/
<slangasek> infinity: hi, not sure stgraber is showing, you may be in charge :)
<infinity> Well poop.
<kees> o/
<mdeslaur> hi kees
 * stgraber waves
<mdeslaur> hi stgraber
<kees> hola
<mdeslaur> infinity: lucky :)
<infinity> I jabbed him in his tiny ribs.
<stgraber> #startmeeting TB meeting
<meetingology> Meeting started Tue Jul 18 16:05:27 2017 UTC.  The chair is stgraber. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
<meetingology> Available commands: action commands idea info link nick
<mdeslaur> hehe
<stgraber> #topic Actions
<stgraber> infinity: made any progress on yours?
<stgraber> ACTION: infinity to ask maas team to prepare SRU exception policy Ã  la CurtinUpdates
<stgraber> ACTION: infinity to play with seed/maint-check changes on dogfood to build a new xenial release pocket for support length auditing (ETA: 16.04.3 release)
<infinity> https://wiki.ubuntu.com/MAASUpdates is a thing now.  Last roaksoax said, it "wasn't done yet", I'll have to catch up with him to see if it's ready for review.
<infinity> And no movement on the maint-check thing.
<slangasek> agreed wrt it not being done, but fwiw it was useful to me when processing the most recent SRU, so that's progress
<slangasek> (wrt https://wiki.ubuntu.com/MAASUpdates)
<infinity> Maybe I should I make a card for it, since that's the hip new thing to do.
<stgraber> being agile now? :)
<infinity> As little as I can manage.
<stgraber> ACTION: slangasek to investigate getting tagged ubuntu-community bugs automatically forwarded to technical-board, and if not feasible, fall back to DMB sending signed emails to list for ACL requests
<stgraber> ACTION: slangasek to follow up to snapd-glib SRU exception request
<stgraber> slangasek: how about those two?
<slangasek> the first is carry-over
<slangasek> the second was done on the mailing list
<stgraber> ok, updated the wiki
<stgraber> #topic Mailing-list stuff
<stgraber> not seeing anything relevant for this meeting, other than the aforementioned snapd-glib thread
<stgraber> #topic LP bugs
<stgraber> https://bugs.launchpad.net/ubuntu-community/+bugs?field.assignee=techboard is empty
<stgraber> #topic Next chair
<stgraber> infinity, kees as backup
<stgraber> #topic AOB
<stgraber> anyone got anything?
<mdeslaur> I don't
<infinity> I'm OBless.
<slangasek> I'm good
<stgraber> #endmeeting
<meetingology> Meeting ended Tue Jul 18 16:13:12 2017 UTC.
<meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting-2/2017/ubuntu-meeting-2.2017-07-18-16.05.moin.txt
<stgraber> thank you very much for attending :)
<slangasek> thanks!
<mdeslaur> thanks stgraber, thanks everyone
<kees> thanks!
#ubuntu-meeting-2 2019-07-16
 * vorlon waves
<infinity> Hrm.
<infinity> I realised I forgot to update the wiki last time.
<infinity> So I went looking through irc logs, and... There aren't any logs for ubuntu-meeting-2 in the last two months?
 * vorlon dunnos
<infinity> Irksome.
<infinity> Try the last year, even.
<vorlon> blink
<infinity> https://irclogs.ubuntu.com/latest/
<infinity> Last log for u-m-2 is 2018-08-22
<infinity> WHat bot is responsible, and how do we get it reinvited?
<vorlon> you ran a meeting in June, meetingology acknowledged your commands
<vorlon> http://wiki.ubuntu.com/meetingology ?
<infinity> Oh, meetingology might have its own logs?
<infinity> Though, if so, not sure where.
<vorlon> 04-06-2019 12:47:49 < meetingology!~meetingol@ubuntu/bot/meetingology: Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting-2/2019/ubuntu-meeting-2.2019-06-04-19.04.moin.txt
<infinity> Have we not had quorum since then?  Or has no one else updated the wiki either? :P
<vorlon> that's the last time anyone gaveled us in according to my logs
<mdeslaur> \o
<infinity> Alright, saved the new action to the wiki.
<infinity> And updated chair to kees/mdeslaur, who seems to now be here. :P
<mdeslaur> awww
<mdeslaur> so I'm chair?
<vorlon> :)
<mdeslaur> #startmeeting
<meetingology> Meeting started Tue Jul 16 19:15:35 2019 UTC.  The chair is mdeslaur. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
<meetingology> Available commands: action commands idea info link nick
<mdeslaur> [topic] Apologies
<mdeslaur> no apologies from the usual slackers
<mdeslaur> [topic] Action review
<mdeslaur> ACTION: vorlon to ask DMB to require flavor developer teams in LP to have a 6-month expiry policy, thus requiring developers to reaffirm their committment each release cycle
<vorlon> carry over
<mdeslaur> ACTION: Wimpress To follow-up on-list with design review to address MATE Boutique security/consent concerns.
 * mdeslaur looks at Wimpress 
<mdeslaur> CTION: infinity to ask maas team to prepare SRU exception policy Ã  la CurtinUpdates (see https://wiki.ubuntu.com/MAASUpdates) (awaiting response from rbasak)
<infinity> Carry, but that might come up in the meeting we have in 13 minutes.
<mdeslaur> ACTION: vorlon to circle around with store, snapcraft, et all, and revise the snap source revision policy to be more clear with regards to rebuildability and GPL compliance.
<vorlon> carry
<mdeslaur> CTION: vorlon to reply to seeded snap upload permissions question on list
<vorlon> carry :/
<mdeslaur> [vorlon] discuss how to ensure flavors are continuing to meet certification requirements
<infinity> Refresh, I deleted that.
<infinity> We discussed it last time.
<mdeslaur> whoopsie
<mdeslaur> [topic] Mailing list archive
<mdeslaur> I don't see anything recent
<mdeslaur> [topic] Community bugs
<infinity> Literally nothing, indeed.
<mdeslaur> no bugs
<mdeslaur> does anyone have anything else they would like to discuss?
<infinity> Does anyone in a near-director-ish position (stares at vorlon) want to take the bullet for bugging Mark about an election again?
<infinity> We're only a year or so overdue.
<vorlon> I mean
<vorlon> I have that as an undeclared action as well
<vorlon> so yes
<mdeslaur> cool
<mdeslaur> anything else?
<infinity> Our quorum issues might resolve if some people who don't have time (kees) and people who've already checked out (stgraber) weren't re-elected. :)
<infinity> I don't have anything else.
<mdeslaur> [topic] Next chair
<mdeslaur> kees, with slangasek as backup
<mdeslaur> err, sorry
<mdeslaur> kees, with vorlon as backup
<infinity> Thus proving that you don't tab complete nicks?
<vorlon> heh
<mdeslaur> well, it explained why that one wouldn't tab complete :)
<infinity> Hah.
<vorlon> you managed to highlight me with both, so
<vorlon> job done
<mdeslaur> #endmeeting
<meetingology> Meeting ended Tue Jul 16 19:23:45 2019 UTC.
<meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting-2/2019/ubuntu-meeting-2.2019-07-16-19.15.moin.txt
<mdeslaur> thanks everyone
<vorlon> mdeslaur, infinity: thanks
<infinity> Oh, does anyone know who runs the public logging bot and how to make it log this place again?
<infinity> I guess I could ask in a more populous channel.
#ubuntu-meeting-2 2020-07-14
 * vorlon waves
