/srv/irclogs.ubuntu.com/2018/03/13/#ubuntu-meeting-2.txt

=== tdaitx_ is now known as tdaitx
tsimonq2o/19:59
kees\o19:59
* slangasek waves20:00
slangasekkees: https://wiki.ubuntu.com/TechnicalBoardAgenda suggests that you are chairing today :)20:03
slangasekotoh, mdeslaur sent regrets and I see no infinity or stgraber20:03
keesyeah, sorry, got caught up in the xchat bug-reading20:03
keesdo we have enough folks?20:03
keesslangasek: infinity idle 11 hours.20:05
keesso... there's only 2 TB members here, we don't have quorum.20:06
slangasekack20:06
keesslangasek: would it be valueable for us to discuss the xchat issue anyway, even though we can't have a binding decision?20:06
slangasekkees: well, I failed to follow up on that before meeting because I was instead focused on the ubuntu-seeded-snaps topic which I considered more urgent20:07
* kees nods20:07
slangasekkees: but IMHO there's no reason for xchat to be escalated to the TB at all at this point, it's squarely in the domain of the archive admins20:07
keesthat was my first reaction, yes. :P20:07
rbasako/20:08
rbasakIt wasn't obvious to me that it is within the domain of the archive admins, because it's at least in part a social decision.20:08
rbasakBut without a reply to my post on ubuntu-release@, nobody seemed to be making a decision.20:08
rbasakThis is why I added to the agenda.20:09
slangasekit is clear to me that the archive admins have the authority, and escalating to the TB is not going to get a decision *faster* than letting the archive admins think it through and respond20:09
slangasekany decision by the AA team can of course be reviewed by the TB20:09
rbasakHow long should we wait for an AA decision before re-escalating to the TB if we don't get one?20:10
rbasak(since a lack of a decision before final freeze -ish is effectively a decision by default)20:11
slangasekI would say a week should be the minimum20:11
keesI would say just leave it on the agenda for the next TB meeting. if you get a resolution before then, remove it. :)20:11
slangasek(and certainly longer than the time between the Thursday of an engineering sprint, and the Monday when a lot of people are swapped on travel)20:11
rbasakI think (but it's not clear) that ~ubuntu-archive was subscribed when the bug was submitted which is over a week ago - but yeah, the engineering sprint didn't help.20:12
jbicha(I filed lots of ubuntu-archive removal bugs that are still open)20:13
rbasakBut as I say I'm asking the TB because it (to me) wasn't clear it's an AA thing, and nobody said otherwise on the list. So I didn't want to wait weeks before being told that the AAs were ignoring it because they didn't see it as an AA decision.20:13
jbicha(killing libgnome stuff, old webkitgtk, gksu, etc.)20:13
rbasakkees: sure. Easy enough, thanks.20:14
slangasekjbicha: yes, and I would spend some time on these if not for launchpad timing out on the bug list for ~ubuntu-archive20:15
rbasakTo be clear, I'm only trying to drive this because I think we owe it to the community as a project to be able to decide on this without letting it languish.20:15
slangasekanyway, since we don't have quorum, we also don't really have a meeting20:16
keesrbasak: yeah, I agree about avoiding a problem with a package living in LTS.20:16
slangasekso I'm going to wander off from this discussion, and follow up to the mailing list threads as appropriate20:17
rbasakkees: well, I'm not necessarily in favour of removal :)20:17
rbasakI just think the project should have a very clear line to a decision, and I don't feel that it has right now.20:17
keesrbasak: right, I mean "evaluating it" in case we have a solid concern to avoid it20:17
rbasakAh. Yes, I agree then :)20:18
jbichaslangasek: for webkitgtk, the tricky one is still gnucash which I guess you're sort of following20:21
jbichalooking at the links from https://bugs.debian.org/892177 there is supposed to be a 2.7.6 release any time now20:22
rbasakThanks for looking anyway.20:24
* rbasak EODs20:24

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