#ubuntu-meeting-2 2016-04-26
<infinity> Agenda says I'm the chair, but it also says the meeting is two weeks ago.  Did I forget to update the wiki, or did I forget to attend?
<slangasek> I don't think two weeks ago counted as a meeting
<slangasek> you can have a mulligan
<infinity> Having a quick "break" before we start.
<mdeslaur> \o
<mdeslaur> hi kees
<kees> hola!
<infinity> #startmeeting Tech Booooooooard!
<meetingology> Meeting started Tue Apr 26 16:00:53 2016 UTC.  The chair is infinity. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
<meetingology> Available commands: action commands idea info link nick
<infinity> #topic Action (action, ACTION, this Sunday only!) review
<infinity> We'll start with mine.  maas stuff still not done.  docker is in progress, discussion about TB size is completed and Mark's response was "do what you think is best", so I think we're down to 5.  I'll inform dholbach so he doesn't announce 6 winners.
<infinity> slangasek: juju SRU?
<slangasek> that's juju SRU exception documentation, yes? carry over
<infinity> Carried.
<slangasek> on the subject of maas sru, we have https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1509147 now
<infinity> #topic mailing list review
<infinity> slangasek: Yup.  With release behind me, I'll tackle MAAS stuff and make some sense of it.
<infinity> Mailing list seems full of resolved issues and election things, nothing interesting.
<infinity> #topic community bugs
<infinity> Nein.
<infinity> Nada.
<infinity> Zip.
<infinity> #topic next chair
<infinity> Next chair is a mystery, as the election should be done by then, but assuming we get reelected, it's kees.
<slangasek> fwiw the "resolution" of the request for php7.0 mre was to punt it to the sru team, who have no formal meetings or clear process for getting these things done
<stgraber> infinity: election is over, we are all re-elected
<slangasek> so while the TB has delegated that back to the SRU team, I'm not sure it hasn't left Nish in limbo
<infinity> stgraber: Oh.  Did I miss the mail?
<stgraber> infinity: so new TB is same as old TB, minus pitti
<slangasek> infinity: apparently :)
<stgraber> our membership has been renewed on LP till May 2018
 * infinity wonders where that email went.
<kees> yay chairing
<slangasek> technical-board@lists.ubuntu.com
<infinity> Not to u-d-a or tb...
<infinity> Oh.
<infinity> Attached to an old thread.
<infinity> Naughty.
<infinity> Well, congrats us!
<infinity> Next chair is kees, then. :P
<mdeslaur> hehe
<kees> woo!
<infinity> With Marc backup.
<mdeslaur> ack
<slangasek> yes, it was a surprising result from a dark horse candidate
<infinity> #topic AOB
<slangasek> yes AOB
<slangasek> I think I suggested last time that we should double-check post-election that this meeting time is still good for the board
<infinity> So, since we have a renewed term, anyone have AOAOB to discuss?  Plans?
<mdeslaur> not sure if this is tech board worthy, but I'd like to discuss what the output of ubuntu-support-status should be
<infinity> It's the same board, minus pitti, though I think pitti was the reason we had this specific time.
<infinity> FWIW, I'm used to this time now, and changing will confuse me. :P
<kees> stgraber: what's your TZ?
<stgraber> this time works fine for me, but I'd be happy to move it later if it helps some folks
<infinity> kees: He's eastern, except when not.
<stgraber> kees: eastern
<stgraber> eastern but working pacific-ish hours usually
<kees> i'm ok keeping this, but ok to move too
<slangasek> infinity: yes, and we have not had perfect attendance at this time slot
<infinity> The entire board is between pacific and eastern now.
<infinity> So we could certainly move it a bit.
<mdeslaur> this meeting is during my usual lunch hour, but I don't mind keeping it or moving it
<infinity> Well, we all sound pretty wishy-washy. :)
<slangasek> I'm fine either way; just wanted to raise the question because I wasn't sure the time was working for everyone else
<infinity> Would we prefer easten afternoon to make it later for Pacific/Mountain?
<kees> deadlocked already!
<slangasek> does anyone care about the time enough to run a doodle poll?
<stgraber> we could push it by a couple of hours
<infinity> I prefer morning meetings so they don't break up my day, but then I run the risk of missing them when I've had an insomniac night.  *shrug*
<infinity> Basically, I can't win. :P
<infinity> So, I leave it to the PST/EST people to fight out, if they care enough to do so.
<slangasek> does anyone care about the time enough to run a doodle poll?
<slangasek> if not then the meeting can stay where it is
<mdeslaur> it can stay
<stgraber> I don't :)
<infinity> #vote does anyone care?
<meetingology> Please vote on: does anyone care?
<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)
<slangasek> though if we moved the meeting, we might manage to get rid of that -2 suffix on the channel ;)
<infinity> -1
<meetingology> -1 received from infinity
<slangasek> +0
<meetingology> +0 received from slangasek
<stgraber> -1
<meetingology> -1 received from stgraber
<mdeslaur> +0
<meetingology> +0 received from mdeslaur
<infinity> kees: Register carefactor? :P
<kees> -1
<meetingology> -1 received from kees
<infinity> #endvote
<meetingology> Voting ended on: does anyone care?
<meetingology> Votes for:0 Votes against:3 Abstentions:2
<meetingology> Motion denied
<infinity> The motion to not care carries.
<mdeslaur> laziness prevails
<mdeslaur> :)
<infinity> mdeslaur: So, support-status....
<infinity> mdeslaur: Retroactively fixing this is hard and potentially harmful (requires careful diffing of the archive when we ever do anything stupid like republish the release pocket).
<infinity> But we could, if there was enough pressure to do so.
<infinity> We could also band-aid it by making the tool just do an "if in main == status == same_as_base-files" or something. :P
<infinity> If the tool is deemed the "correct" way for people to determine status.
<mdeslaur> I was thinking of just doing main/universe for < xenial, and for xenial doing if main == same_as_base-files
<slangasek> I certainly don't consider it deprecated, in spite of the unfortunate bit-rotting that had happening
<slangasek> happened
<kees> (i thought my delegates would handle that that vote)
<mdeslaur> I don't think the seeds were accurate for precise to trusty
<mdeslaur> sorry, precise to wily
<infinity> mdeslaur: So, it's called UBUNTU-support-status, not CANONICAL-support-status, thus yor main/universe split isn't correct.
<infinity> Maybe we should determine what the tool's actually supposed to tell people.
<kees> didn't we just create a manual file back in dapper time?
<mdeslaur> infinity: right, but do you want to republish the stable releases?
<mdeslaur> or, alternatively, we could bundle a manual file with the tool for the stable releases
<infinity> mdeslaur: My point was that lots of stuff in universe for precise/trusty (correctly) lists itself as supported due to flavour LTSes.
<slangasek> infinity: per my comment on thread, I don't think letting flavors claim LTS "support" without any sort of CVE tracking is particularly honest
<mdeslaur> infinity: yes, but I don't think the seeds are right
<infinity> Sure they are.
<infinity> The seeds are correct, it's how we're interpreting them in LP that isn't what you expect.
<mdeslaur> yes, that's what I meant
<mdeslaur> you're nitpicking :)
<mdeslaur> ok, let me investigate and I'll come up with a proposal
<infinity> FWIW, this is the current logic: http://bazaar.launchpad.net/~ubuntu-archive/ubuntu-archive-publishing/trunk/view/head:/scripts/maintenance-check.py
<mdeslaur> slangasek: we did have a web page that tracked cves for flavour supported packages...I don't know if it's still alive though
<infinity> So, you can see we pick up desktop, server, and some supported seeds.  The bug is that we don't take *all* supported seeds (hence, we don't get all of main).
<mdeslaur> which we should
<infinity> The universe bits are accurate, it's just main that isn't, due to some confusion about the desktop/server split meaning that !desktop and !server got short times.
<infinity> mdeslaur: Anyhow, I'm not against republishing xenial-release if we have to.  It just requires great care.  I will flat out refuse to republish precise or trusty, though, so those would need some tool hackery to be "good enough".
<mdeslaur> infinity: let's say we fix that, is it worth republishing the release pocket, or should we just bundle a static list with the tool
<mdeslaur> so you'd be ok with xenial-release, but for earlier we hack the tools, that's fine by me
<slangasek> infinity: let's ignore precise+trusty for now; I'm not sure the tool *runs* in all of those releases
<slangasek> (that's how bad the bit rot was)
<mdeslaur> the nginx thread was trusty
<infinity> slangasek: The original archive reorg plan had a way to designate *who* support came from, which would (somewhat) mitigate your concern, as people can adjust expectations based on "community" versus "canonical", but with the current setup, we can't do much be keep it muddy.
<infinity> s/be keep/but keep/
<infinity> It may be slightly dishonest to claim lxde has 3y support when it's not the same support we provide for glibc, but it's equally dishonest to claim it's not supported when they committed to supporting it, so it's rock meets hard place.
<slangasek> infinity: well, as the TB what we can do is insist that flavors actually provide support in the way we mean it before granting them LTS status
<infinity> slangasek: Sure, that's not unreasonable.
<slangasek> which we have not done up to this point, at least for the meaning of support that I consider relevant
<mdeslaur> when we say "9m" support for everything in universe that nobody has commited to supporting, isn't that a lie?
<slangasek> I'm not asking to readjudicate all of that for 16.04, but I think we should put out a clearer standard for future LTS
<infinity> mdeslaur: I know the CVE tracker needs a lot of manual garndening.  Is there a way to run it in a "good enough" mode for !canonical-supported stuff that just does an okay job of importing things, ish? :P
<infinity> mdeslaur: So it's not extra workload for you, but the community people have a place to look?
<slangasek> mdeslaur: sure, maybe unseeded should be 0 instead of 9?
<mdeslaur> infinity: we did have a web page for flavours, let me figure out what happened to it
<infinity> unseeded is 0.
<mdeslaur> slangasek: that's kind of what I'm thinking
<infinity> mdeslaur: It would be a lie if that were the case, but it's not.
<slangasek> infinity: ah, ok
<stgraber> well, it's not 0, it's just not set (no Supported field), maybe we should actually set it to 0 too
<infinity> (xenial-amd64)root@nosferatu:/home/adconrad# apt-cache show libc6 | grep ^Sup
<infinity> Supported: 5y
<slangasek> in that case, 9m for flavor-seeded-but-no-track-record-of-doing-security-support is probably an ok compromise
<infinity> (xenial-amd64)root@nosferatu:/home/adconrad# apt-cache show thunar | grep ^Sup
<infinity> Supported: 3y
<infinity> (xenial-amd64)root@nosferatu:/home/adconrad# apt-cache show lazarus | grep ^Sup
<infinity> (xenial-amd64)root@nosferatu:/home/adconrad#
<stgraber> or "Supported: not"
<infinity> We could fill in the field, sure.  Empty == 0 historically, but meh.
<mdeslaur> are flavours that didn't apply for lts actually supporting stuff for 9m?
<infinity> That's more bikeshedding than fixing any real problem, I think.
<slangasek> agreed, -1 to bikeshedding
<infinity> mdeslaur: There are no non-lts flavours.
<infinity> mdeslaur: Anything you see with "9m" is due to the misfeature we're discussing, not flavours.
<infinity> mdeslaur: Basically, it's listed in a supported seed that we don't consider for LTS length.
<infinity> http://bazaar.launchpad.net/~ubuntu-archive/ubuntu-archive-publishing/trunk/view/head:/scripts/maintenance-check.py#L36
<infinity> Those lists there are the ones that get LTS length.
<infinity> Any other supported seeds are 9m.
<infinity> That's the bit we'd fix if we were to republish.
<infinity> It's a two-line change or so to get all of main in.
<mdeslaur> SUPPORTED_SEEDS = ["all"]
<infinity> Yeah, SUPPORTED_SEEDS ends up being 9m.
<mdeslaur> who supports the supported seeds that aren't flavours, and aren't main
<slangasek> mdeslaur: there's no such thing?
<slangasek> seeds are in main, or they're flavors
<slangasek> more precisely: seeds are the definition of the products, including the community flavors; and some of those seeds are also defined as main
<mdeslaur> but xenial universe is chock full of 9m
<infinity> So, I can whip up a change on dogfood for people to see what this would look like if I pull all the ubuntu/main seeds in.
<slangasek> curious
<mdeslaur> who's supporting those packages in xenial universe for 9m
<slangasek> infinity: does maintenance-check follow build-deps?
<slangasek> this could be fallout from archive reorg
<infinity> slangasek: Oh, hrm.  It might.
<infinity> Though it shouldn't.
<infinity> Oh.
<infinity> Balls.
<infinity> No.
<infinity> following build-deps is a seed property.
<infinity> And we only turned it off in *our* seeds.
<infinity> So flavours will get *their* build-deps recursed.
<infinity> Derpy McDerpface.
<mdeslaur> hehe
<infinity> Okay, I think we might need to fiddle with this a bit on dogfood.
<infinity> Twiddle seeds to stop doing recursion, twiddle maint-check to include the rest of ubuntu/platform supported, and regen and see how scary the diff is.
<slangasek> infinity: well, the first few 9m hits I find in universe are Task: ubunutstudio-audio, plus a -dbg package.  Those seem like a different issue from build-deps
<infinity> slangasek: The studio ones seem entirely reasonable to be 9m.  They'd be in a studio seed that isn't desktop.
<slangasek> infinity: why is that reasonable?
<infinity> And almost everyone has bugs where they don't include a supported: ALL MY TASKS bit in STRUCTURE.
<mdeslaur> Supported: 9m
<mdeslaur> Task: edubuntu-desktop-gnome
<infinity> slangasek: Reasonable given the code, not reasonable as in "that's the desired output".
<slangasek> infinity: yes, so my question is what's the right way to fix those, given that no-follows-build-dep doesn't change it
<slangasek> do we expect anything seeded by an LTS flavor to get the LTS support length, the same as we expect for main?
<infinity> slangasek: Oh, the way to fix those studio ones is to include all their seeds in supported in STRUCTURE (and same for all flavours... Indeed, that's our correct fix too)
<infinity> slangasek: Yeah, I think that's what we want.
<slangasek> ok; I agree
<slangasek> does mdeslaur ?
<mdeslaur> yes
<infinity> Okay, this'll take some grinding on dogfood to work out a set of changes to maint-check and seeds and see if it turns out more correct.
<infinity> But I can take an action to play with that.
<slangasek> sounds good
<infinity> And then we can revisit if we want to republish or mangle tools.
<mdeslaur> infinity: let me know when you have something to look at
<infinity> But I think republishing will be the right answer.
<mdeslaur> and I can take care of the tools, whatever we ultimately decide
<infinity> mdeslaur: I think fudging the tools for precise/trusty will be fine.  There are no LTS precise flavours left, and only a couple of LTS trusty flavours soon, so meh.
<infinity> #action infinity to play with seed/maint-check changes on dogfood to build a new xenial release pocket for support length auditing
<meetingology> ACTION: infinity to play with seed/maint-check changes on dogfood to build a new xenial release pocket for support length auditing
<mdeslaur> infinity: ok, so the main/universe tool fudge I suggested earlier for precise and trusty would be ok?
<infinity> mdeslaur: Well, either that, or "if main, same_as_base_files" ... Then you're not demoting universe things that do claim 3/5.
<slangasek> now, what's the action re: making sure flavors are accountable for security updates before we declare them LTS, which I believe today they are not?
<infinity> mdeslaur: Since this bug/misfeature doesn't mean anything is listed as too long, only too short.
<mdeslaur> assuming the supported tags in precise/trusty universe actually make sense, I'll have to look first
<infinity> slangasek: We ask them to be accountable, enforcing that is harder.  But feel free to take an action to follow up on tooling available and educating them about their responsibilities.
<slangasek> infinity: "ask them to be accountable"> nack
<slangasek> there needs to be a burden of evidence here
<infinity> slangasek: Some things (like security having to go through the security team) make the process suck.  We might be able to do better there, with a community security PPA or something.
<mdeslaur> I'll take an action to look into the web page we had that listed open CVEs by flavour
<slangasek> o
<slangasek> k
<slangasek> I'm fine with the Ubuntu Security team driving that reporting
<infinity> #action mdeslaur to look into flavour CVE tracking
<meetingology> ACTION: mdeslaur to look into flavour CVE tracking
<infinity> Yeah, I'm fine with them driving it, as long as they don't also spend time gardening it.
<infinity> So, it should be mostly automagic (even if that means it has a ton of false positives)
<slangasek> if the Security Team doesn't have the time for that, though, I would say that we would need to put it to the flavors that they need to do this themselves
<infinity> Sadly, the way it's built, there's no way to give someone, say, SSO access to NACK an invalid CVE or something.
<infinity> But oh well.
<infinity> One step at a time.
<mdeslaur> a merge proposal works fine for now
<infinity> Check.
<infinity> mdeslaur: So, once we nail down the exact correct logic for maint-check, the same seed sets should be used to divvy up the flavours.
<infinity> mdeslaur: But we're diving into implementation here, so we can talk about that sort of thing later.
<mdeslaur> yes, perfect
<infinity> I don't disagree that the flavours have done a poor job of being "as good as Canonical's security team", but we can probably meet in the middle.  I hope.
<slangasek> I am not asking that the flavors be "as good as Canonical's security team"
<slangasek> I am saying we should not be rubber-stamping a 5-year LTS for a flavor when there is no committment whatsoever to provide security support
<stgraber> infinity: once the seeds are updated, http://people.canonical.com/~stgraber/supported-packages/lists/ should show the list of packages we expect each flavor to look at
<infinity> slangasek: Right, I know.
<infinity> stgraber: Oh, right.  That magic thing.  That's what Marc should be looking at.
<infinity> stgraber: The way that's built, can you pin shared responsibility on some things (like, studio/xu both owning xfce?)
<stgraber> that link above shows the list of packages that are unique to a given flavor (it knows what flavor depends on what other flavor)
<stgraber> infinity: we could change the logic to show that, though it'd then basically be straight germinate output
<mdeslaur> oh! nice
<infinity> stgraber: Cause studio's LTS application said they intended to help with xubuntu, rather than just rely on xubuntu fixing it all for them.
<infinity> stgraber: Well, not all flavours should report that way.  xu/studio are special. :)
<stgraber> infinity: ah, then we could change their config to say that it's not based on xubuntu, which would then include the xubuntu bits in their own list of packages too
<infinity> stgraber: Most flavours should report in the way you do already, just the stuff they're uniquely responsible for.
<stgraber> infinity: changed the studio config, next run will have them maintain anything that's not supported by ubuntu, so that will mean the xubuntu bits they use will show up in their list
<infinity> Perfect.
<infinity> Okay.  I think we've exhausted this topic from the POV of the TB meeting.
<infinity> And have given ourselves more work.  So, go us.
<slangasek> :)
<mdeslaur> hehe
<infinity> I think we should definitely reopen the flavour conversation with all of the flavour leads, but perhaps we should hold off until we've checked our own tooling to see if we can offer them an olive branch while also chastising them.
<infinity> Compliment sandwich style, as it were.
<slangasek> infinity: reopen for 16.04?
<slangasek> I think 16.04 is done; TB has approved these and we have to own that now
<infinity> slangasek: Well, yes, I think we want to make sure they're accountable for 16.04 updates.
<slangasek> but.. - yes, that
<infinity> slangasek: We approved it, but what we approved is them actually taking responsibility.
<slangasek> ack ;)
<infinity> slangasek: So, we need to make sure that's meaningful.
<infinity> To be fair, some do alright just by virtue of pushing new upstream point releases (ie: KDE).
<stgraber> also note that most of them only took 3y LTS this time around which is a bit more reasonable than the 5y a bunch of them had last time around
<infinity> Others could use a bit more of a shove.
<stgraber> the exception being Kylin IIRC
<infinity> And some only ship like 20 unique packages, so their burden is low.
<infinity> Yeah, kylin is the only 5y, and 99% of kylin is Ubuntu.
<infinity> Which is the only reason I didn't shoot them down.
<slangasek> fair
<stgraber> well, they apparently will be suppporting chromium for 5 years
<slangasek> even 3 years needs to mean something, though
<stgraber> but yeah besides that one, their delta seems fine
<infinity> slangasek: Absolutely.  My 5y/3y criteria was about overlap commitment and staffing.
<infinity> slangasek: The responsibility within the time period is obviously the same.
<infinity> (We talked a few flavours into dropping to 3 due to staffing)
<infinity> Anyhow.
<infinity> We're about to hit meeting end time for the first time in months.
<infinity> Which is scary.
<infinity> But potentially productive?  Yay.  We did a thing.
<stgraber> it'd have been nice to do the LTS review for flavors before release week as I expect a bunch of them would have been tweaking their seeds to reduce the number of packages they end up being responsible for
<infinity> Well, we planned to do a thing.
<stgraber> but that's something we'll have to do better for 18.04...
<slangasek> yes
<stgraber> I'd recommend we do the flavor approval before we hit feature freeze next time, leaves them time to shuffle bits around to reduce their package list
<mdeslaur> stgraber: +1
<slangasek> when all is said and done let's write that down somewhere so we remember to do it in 1.5y time ;)
<infinity> stgraber: Yeah.  Though, for most of them, the stuff they're supporting is "their DE", and not much to drop there.
<infinity> studio being a whacky outlier, but they love shipping every multimedia thing ever.
<stgraber> infinity: well, I'd have expected kylin to ditch evolution and chromium-browser, lubuntu to notice they were supporting ltsp and some other random bits, ... we fixed a bunch of those last minute in London, would have been nice not to have to do it so late :)
<infinity> stgraber: Oh, yes, the ltsp thing was lolz.
<infinity> And I fixed a bunch of kylin stuff due to their forked seeds.
 * mdeslaur spits coffee at mention of chromium-browser
<infinity> But I think that takes us to notice, not them. :(
<infinity> kylin's seeds have been broken for 1.5y.
<stgraber> mdeslaur: http://people.canonical.com/~stgraber/supported-packages/lists/ubuntukylin.xenial
<infinity> The part where no Kylin people even seemed to notice when I fixed their seeds implies that they never would have noticed they were broken either. :P
<mdeslaur> ok, can we wrap up?
<stgraber> infinity: well, we should absolutely point them at those package lists before granting them LTS status and have them confirm that they will do x years maintenance on all of those, I guess at that point they'll go "wth is package XYZ in our list?" and start fixing stuff to have a more reasonable list :)
<infinity> Yes!
<mdeslaur> not that I don't enjoy talking with you guys :)
<stgraber> but anyway, that's 18.04 talks at this point
<infinity> stgraber: Agreed.
<stgraber> mdeslaur: getting a bit hungry? :)
<infinity> stgraber: We probably need to document community LTS processes in general somehow, but let's leave that for another meeting.
<mdeslaur> stgraber: and dizzy :)
<infinity> #topic AOAOB
<infinity> Going once.
<infinity> Going twice.
<infinity> #endmeeting
<meetingology> Meeting ended Tue Apr 26 17:00:19 2016 UTC.
<meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting-2/2016/ubuntu-meeting-2.2016-04-26-16.00.moin.txt
<slangasek> thanks!
<mdeslaur> thanks everyone!
<stgraber> thanks!
#ubuntu-meeting-2 2017-04-25
<kees> \o
 * mdeslaur waves
<kees> hola
 * kees looks for infinity
<kees> mdeslaur: hm, should we skip?
<mdeslaur> he's coming
<infinity> o/
<mdeslaur> hi infinity
<kees> \o
<infinity> Oh look, I'm the chair.
<infinity> How did that happen?
<slangasek> musically?
<infinity> :P
<infinity> #startmeeting Ubuntu Technical Board Meeting
<meetingology> Meeting started Tue Apr 25 16:06:13 2017 UTC.  The chair is infinity. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
<meetingology> Available commands: action commands idea info link nick
<infinity> #topic apologies
<infinity> I see none.  So, clearly, we're all here.
<infinity> stgraber seems to not be here.
<infinity> #topic Action Review
<infinity> infinity: How are you doing on your actions?
<infinity> infinity: I've been pretty busy, and also, apparently, a slacker.
 * stgraber waves
<infinity> infinity: Well, sort that.
<infinity> infinity: Yes dear.
<infinity> slangasek: How about your two?  ubuntu-community bugs thing, and snapd-glib thing?
<slangasek> infinity: both carry-over
<infinity> Right, all sorts of deferrals all-round, then.
<infinity> #topic Mailing List
<slangasek> snapd-glib I need to jfdi via email due to poor timezone syncage
<infinity> Looks pretty dead to me since the last meeting?
<slangasek> there were some DMB requests
<infinity> Right, but both actioned.
 * slangasek nods
<infinity> #topic Community Bugs
<infinity> Nada.
<infinity> #topic Tech Board Pizza and Pyjama Party
<infinity> Who's coming?
<kees> \o/
<mdeslaur> yay!
<infinity> My only request is that in the inevitable pillow fight, you don't mistake stgraber for a pillow and hit me with him.
<mdeslaur> lol
<infinity> #topic AOB
<infinity> And, uhm.  Do we have anything interesting?  Anyone?
<slangasek> nothing here
<kees> goo.gl/epkCTZï¿¼content_copyCopy short URL
<mdeslaur> remember when there used to be controversial stuff that required a tech board?
<kees> gah
<kees> goo.gl/epkCTZcontent_copyCopy short URL
<mdeslaur> kees: go somewhere else with your exploits
<infinity> I think kees is trying to exploit our IRC clients.
<kees> GAH
<kees> goo.gl/epkCTZ <- me ready for party
<kees> (but clearly not ready for cut/paste)
<mdeslaur> hehe
<infinity> Did you just make me request a buzzfeed URL?
<infinity> That *is* quite the exploit.
<infinity> #topic Next Chair
<infinity> Looketh like kees, mit mdeslaur fur backup.
<mdeslaur> ack
<kees> yawp
<infinity> On May 9th.
<infinity> So.  If that's all anyone's got.
<infinity> 3
<infinity> 2
<infinity> 1
<infinity> #endmeeting
<meetingology> Meeting ended Tue Apr 25 16:16:50 2017 UTC.
<meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting-2/2017/ubuntu-meeting-2.2017-04-25-16.06.moin.txt
<kees> sold!
<mdeslaur> thanks infinity
<kees> thanks!
<slangasek> thanks, all
<stgraber> thanks!
#ubuntu-meeting-2 2018-04-24
 * slangasek waves
<mdeslaur> hi!
<slangasek> so the agenda wiki says kees was chair but he chaired last week
<slangasek> I think it's my turn; updating that quickly
<slangasek> #startmeeting
<meetingology> slangasek: Error: Can't start another meeting, one is in progress.
 * slangasek squint
<slangasek> #endmeeting
<mdeslaur> longestmeetingever
<slangasek> who is Rewer43 and why did they break our bot?
<sarnold> it looked like usual drive-by trolling at the time
<slangasek> >_<
<slangasek> [TOPIC] Apologies
<slangasek> no apologies sent to the list
<slangasek> infinity is at the release sprint so possibly indisposed
<slangasek> stgraber, kees: here?
<slangasek> may have been wishful thinking to try for quorum on release week
<slangasek> jbicha: would it be useful to talk informally about the DMB voting question?
<slangasek> I've already replied on the list with my opinion
<mdeslaur> I share slangasek's opinion
<jbicha> yes
<jbicha> and yes I think the TB does have power over voting procedures
<slangasek> ok, so, 2 for and 0 against
<slangasek> do you need one of us to start the vote?
<jbicha> you're saying option 2 from my email is what we should go with then?
<slangasek> if option 2 is the "have a NOTA option, only empanel those who clear the bar", yes
<mdeslaur> yes, option 2
<slangasek> if that means we don't have all the seats filled after the vote, we can have a second call for candidates at that point
<jbicha> ok, I think the DMB can start the vote. We'll let you know if we need more help
<slangasek> ok
<slangasek> jbicha: thanks
<slangasek> beyond that, since we're not at quorum and someone has sabotaged the bot...
<slangasek> #endmeeting
<jbicha> mdeslaur: do you want to reply to my TB email then?
<slangasek> anyone know who the meetingology admins are?
<mdeslaur> sure, I'll do it now
<Strangerdanger8> #endmeeting
#ubuntu-meeting-2 2018-04-25
<DalekSec> #endmeeting
<meetingology> Meeting ended Wed Apr 25 00:02:36 2018 UTC.
<meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting-2/2018/ubuntu-meeting-2.2018-04-22-01.19.moin.txt
<strangerdanger6> !ops end the meeting started by the troll
<strangerdanger6> !ops
<strangerdanger6> end the meeting started by the troll
#ubuntu-meeting-2 2018-04-29
<specialtr4> TESTING TESTING
<tsimonq2> Testing 1 2
<tsimonq2> :P
<specialtr4> You cannot be in here. This channel is under maintenance
<specialtr4> Sorry about that.
<tsimonq2> uhm?
<tsimonq2> !ops
<tsimonq2> Oh, no bot.
<tsimonq2> That's just /great/
<specialtr4> This channel is closed.
<specialtr4> Sorry for the inconvenience
<specialtr4> but you have to leave
<tsimonq2> specialtr4: No, you.
<specialtr4> I am doing my job
<tsimonq2> Do you have proof of who you work for?
<specialtr4> I work for Supertex
<specialtr4> Please leave the channel
<specialtr4> I have to have the job done by tomorrow morning
<tsimonq2> I don't know how to tell you this, but you literally can't have channels be "under maintenance" unless you're a freenode admin. You don't have the cloak, which makes me think you're just trolling.
<specialtr4> Think what you want, but you must leave
<specialtr4> I was hired by Ubuntu to do this job
<tsimonq2> Â¯\_(ã)_/Â¯
#ubuntu-meeting-2 2020-04-21
 * vorlon waves
<mdeslaur> hi vorlon
<vorlon> this does not look like quorum
<mdeslaur> vorlon: what do we need for xnox's proposal on the list...can I just +1 it?
<vorlon> well I haven't read it yet
<vorlon> so maybe? :)
