[14:00]  * micahg waves
[14:00] <Laney> greetings
[14:00]  * bdrung waves
[14:02] <micahg> stgraber: DMB meeting?
[14:02] <stgraber> :/me waves
[14:03]  * stgraber waves
[14:03] <micahg> ok, we have quorom, let
[14:03] <Laney> s go
[14:03] <micahg> 's get started...
[14:03] <Laney> :-)
[14:03] <micahg> #startmeeting DMB
[14:03] <meetingology> Meeting started Mon Sep 26 14:03:32 2011 UTC.  The chair is micahg. Information about MeetBot at http://wiki.ubuntu.com/AlanBell/mootbot.
[14:03] <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
[14:03] <micahg> #topic Review of previous action items
[14:04] <micahg> #subtopic Laney to start thread on ubuntu-devel about renaming UCD
[14:04] <Laney> O_O
[14:04] <Laney> clearly not done, sorry
[14:04] <Laney> do people care much about this?
[14:06] <Laney> ahem.
[14:06] <bdrung> Laney: it would be nice to have a better name, but there was no better one proposed yet
[14:06] <micahg> I don't think it's so bad, but I'd have to go back and look at the reason why we decided to change this in the first place
[14:07] <Laney> I don't want a tiresome bikeshedding thread for choosing a new name
[14:07] <bdrung> because it can be misinterpreted
[14:07] <Laney> I said we should use Ubuntu Development Members as that's in line with other stuff but some people didn't like that (I don't remember why)
[14:07] <bdrung> Laney: we should collect name suggestions and then discuss it here.
[14:08] <Laney> ok i'll start it soon then
[14:08] <micahg> Laney: thanks, carried forward then
[14:08] <micahg> #subtopic geser to e-mail the TB with the result of the poll
[14:09] <micahg> I believe this was done
[14:09] <Laney> yeah
[14:09] <micahg> #subtopic stgraber to add micahg to the mailing-list once TB has added him to the team
[14:09] <micahg> this was done as well
[14:09] <micahg> #subtopic jono to ask Daniel to update https://wiki.ubuntu.com/UbuntuDevelopers to be easier to read
[14:10] <micahg> I think that the main membership page was updated, but not the Developers page yet
[14:10] <micahg> dholbach: is the above on your list?
[14:11] <micahg> well, carried forward until we can find out...
[14:12] <micahg> #subtopic cody-somerville to write some documentation on how to endorse someone
[14:12] <micahg> carried forward as Cody's not here
[14:12] <micahg> #subtopic stgraber to get the list of all package sets and their content somewhere online
[14:13] <stgraber> http://people.canonical.com/~stgraber/package_sets/
[14:13] <micahg> \o/
[14:13] <micahg> thanks stgraber
[14:13] <Laney> WOO!
[14:13] <dholbach> micahg, add to which mailing list?
[14:13] <micahg> dholbach: sorry, I meant on your to do list :)
[14:13] <dholbach> I didn't have time to look into https://wiki.ubuntu.com/UbuntuDevelopers yet, but I'll bump the priority
[14:14] <micahg> dholbach: were you at least asked :)
[14:14] <Laney> can we have the team and packageset name in the reports?
[14:14] <dholbach> Jono indeed mentioned it to me
[14:14] <micahg> dholbach: excellent, thank you
[14:14] <Laney> team → LP ID of uploader(s)
[14:16] <stgraber> Laney: package set name is the filename but I'm happy to add it to the report as well
[14:16] <Laney> cheers
[14:16] <micahg> stgraber: I think Laney is referring to the uploaders team
[14:16] <Laney> both
[14:16] <micahg> ah, heh, missed the first line :)
[14:16] <stgraber> Laney: I can expand the teams though probably won't do it recursively as it may take a while in some cases
[14:17] <Laney> I don't care about recursively, just the top-level entries
[14:17] <Laney> although I hope there will only be one of those ... :-)
[14:18] <bdrung> stgraber: can you put the generation script into a bzr branch under our hood?
[14:18] <micahg> well, top level of the teams should have multiple people hopefully
[14:18] <stgraber> bdrung: sure, I'll do that. What project should I use?
[14:18] <bdrung> good question. +junk?
[14:19] <stgraber> I guess that'd be a start :)
[14:20] <micahg> #action stgraber to publish packageset generation script so the rest of the DMB can help maintain it
[14:20] <meetingology> ACTION: stgraber to publish packageset generation script so the rest of the DMB can help maintain it
[14:20] <Laney> and get it auto deployed ;-)
[14:20] <Laney> bzr pull && ...
[14:20] <stgraber> yep
[14:20] <micahg> does that need a second action?
[14:21] <Laney> nah, I'm sure he can remember
[14:21] <micahg> ok, anythiing else about this script?
[14:21] <stgraber> indeed :)
[14:21] <bdrung> rule the world ;)
[14:21] <stgraber> updated script is running at the moment :)
[14:22] <Laney> we should link it from somewhere
[14:22] <stgraber> yeah, the developer membership wikipage would be a good candidate
[14:22] <Laney> https://wiki.ubuntu.com/UbuntuDevelopers#Ubuntu_Developers_.28from_delegated_teams.29
[14:23] <bdrung> stgraber: Launchpad.login_with('testcase') -> better app name than testcase, please
[14:23] <Laney> can we do code review some other time?
[14:23] <stgraber> bdrung: looks like some copy/paste, will fix that :)
[14:23] <stgraber> Laney: sure
[14:23] <Laney> ty
[14:23] <micahg> ok, yes, let's debug the script later
[14:23] <micahg> moving on
[14:24] <micahg> #topic Administrative Matters
[14:24] <micahg> #subtopic Continue discussion on Ubuntu Developer Survey Report with jono
[14:25] <Laney> I guess we should have some TB involvement?
[14:25] <micahg> well, did we exhaust the subject ourselves or do we want a joint meeting before that?
[14:26] <micahg> or did you have something else in mind?
[14:26] <Laney> dunno, I just thought the idea was to have them involved
[14:27] <Laney> didn't see any reaction on the email from them though
[14:29] <micahg> well, perhaps we can discuss this further once the wiki gets updated to clarify the membership guidelines
[14:29] <Laney> i suppose the main issues were dealt with
[14:29] <micahg> right, it seems so
[14:30] <micahg> I'll leave this on the agenda and we can discuss with jono at the next meeting
[14:30] <micahg> #subtopic Continue discussion about our package set management workflows
[14:31] <micahg> I think we should wait to discuss this until the end as we can easily run out the clock with it
[14:31] <micahg> any objections?
[14:32] <bdrung> no
[14:32] <Laney> nah, go ahead
[14:32] <stgraber> sounds good
[14:32] <micahg> #topic PerPackageUploader Applications
[14:32] <Laney> as long as we do, because I know how I think it should work :-)
[14:32] <micahg> #subtopic cyphermox applying for PPU for usb-modeswitch*
[14:33] <micahg> cyphermox: are you around?
[14:33] <cyphermox> yup
[14:33] <micahg> #link https://wiki.ubuntu.com/Mtrudel/PPU-usbmodeswitch
[14:33]  * micahg wonders if that worked...
[14:33] <cyphermox> IIRC you don't get ack for #link :)
[14:34] <micahg> cyphermox: can you please introduce yourself?
[14:34] <cyphermox> sure
[14:34] <cyphermox> I'm a developer working for Canonical on the Ubuntu Desktop team. My "official" task is to maintain NetworkManager, but I also usually touch other things such as evolution and generally interested in the networking stack
[14:35] <cyphermox> as such, usb-modeswitch is a clear dependency/important point, when you want to use 3G devices
[14:36] <cyphermox> at UDS-O we discussed porting the usb-modeswitch dispatcher script from Tcl to C which is what I've done, and a big part of why I'd like to be able to upload it directly
[14:36] <cyphermox> (just keeping up maintenance and porting changes to the upstream script to the C version)
[14:36] <Laney> do you anticipate having to maintain this patch in Ubuntu for long?
[14:37] <cyphermox> Laney: no. I've already spoken to the Debian maintainer and upstream author, the plan is to have both versions available from upstream
[14:38] <bdrung> cyphermox: why both? what drawbacks does the C version have?
[14:38] <cyphermox> bdrung: mainly the one of not being as editable by users directly; which is something upstream sees as important.
[14:39] <bdrung> sounds plausible
[14:39] <cyphermox> bdrung: my feeling is that it's mostly a matter of keeping it in a scripted language, I haven't really had other responses from upstream
[14:39] <Laney> can't you close bug 679256 now? :-)
[14:40] <cyphermox> yes, I can ;)
[14:40]  * Laney has no real questions
[14:40] <Laney> thanks for getting the endorsers
[14:40] <Laney> oh, and please subscribe to bugs for -data
[14:40] <cyphermox> oh, indeed, good point
[14:41] <tumbleweed> cyphermox was very helpful when I ran into issues related to those packages, thiscycle
[14:41] <tumbleweed> (drive by endorsement)
[14:41]  * bdrung has no questions.
[14:41] <micahg> cyphermox: I'm just curious about your response to what slangasek said on your app under Areas of Improvement
[14:42]  * bdrung has only 30 mins left.
[14:43] <cyphermox> micahg: well, it's right, it was a dumb move, not sure what else to add :)
[14:44] <micahg> cyphermox: ok
[14:44] <stgraber> cyphermox: wasn't that related to the PATH from within udev being broken at some point (just remembered you mentioning something like that, so thought it could be related)
[14:44] <cyphermox> stgraber: well, it was based on the fact that it *could* be missing, but testing it proved it was available from udev when the script was called
[14:45] <stgraber> ok
[14:45]  * stgraber is ready to vote
[14:45] <micahg> #vote cyphermox to gain PPU for usb-modeswitch and usb-modeswitch-data
[14:45] <meetingology> Please vote on: cyphermox to gain PPU for usb-modeswitch and usb-modeswitch-data
[14:45] <meetingology> Public votes can be registered by saying +1, +0 or -1 in channel, (private votes don't work yet, but when they do it will be by messaging the channel followed by +1/-1/+0 to me)
[14:45] <Laney> +1
[14:45] <meetingology> +1 received from Laney
[14:46] <bdrung> +1
[14:46] <meetingology> +1 received from bdrung
[14:46] <stgraber> +1
[14:46] <meetingology> +1 received from stgraber
[14:46] <micahg> +1
[14:46] <meetingology> +1 received from micahg
[14:46] <micahg> cody-somerville: ?
[14:47] <Laney> brb
[14:47] <micahg> #endvote
[14:47] <meetingology> Voting ended on: cyphermox to gain PPU for usb-modeswitch and usb-modeswitch-data
[14:47] <meetingology> Votes for:4 Votes against:0 Abstentions:0
[14:47] <meetingology> Motion carried
[14:47] <micahg> cyphermox: congratulations
[14:47] <bdrung> congrats
[14:47] <stgraber> cyphermox: congrats
[14:47] <cyphermox> thanks
[14:47] <micahg> jamespage: are you around?
[14:48] <jamespage> yep!
[14:48] <micahg> #topic Ubuntu Core Developer Applications
[14:48] <micahg> #subtopic James Page
[14:48] <micahg> #link https://wiki.ubuntu.com/JamesPage/CoreDevApplication
[14:49] <micahg> jamespage: unfortunately, we only have 12 minutes before the next meeting, but we can see how far we get here
[14:49] <micahg> jamespage: please introduce yourself
[14:49] <jamespage> OK
[14:50] <jamespage> So my name is James Page and I work for Canonical as a member of the Ubuntu Server Platform team
[14:50] <jamespage> I have been contributing as a developer to Ubuntu for the last year; my contributions  have mainly been server related with a particular focus on Java.
[14:51] <jamespage> I already have upload permissions for the ubuntu-server packageset (June this year)
[14:52] <bdrung> jamespage: why do you want to become MOTU too?
[14:52] <jamespage> having a broader set of upload permissions would really help me work more effectively - and reduce the sponsorship burden I place on others at the moment
[14:52] <jamespage> bdrung: I would like to be recognised as MOTU as well I have a keen interest in helping ensure the quality of packages in universe
[14:53] <jamespage> most of the Java packages I have worked on are in universe
[14:53] <bdrung> jamespage: motu != universe. what have you done in the motu team?
[14:53] <jamespage> and I think having MOTU membership as well as core-dev recognises this contribtuion
[14:53] <micahg> jamespage: were you aware that core-dev membership includes membership in the MOTU team?
[14:54] <jamespage> micahg: yes I was
[14:54] <jamespage> bdrung: I have helped a few people on IRC (mainly pointing them in the right direction)
[14:55] <jamespage> note sure whether its directly related to MOTU but I also ran a UDW session - helping raise awareness of the Java packaging toolset
[14:56] <micahg> jamespage: your direct uploads appear to have ceased at the end of July, is there any reason for this?
[14:58] <jamespage> micahg: I think that reflects that I work outside of the server packageset that I have upload access to
[14:58] <jamespage> and the fact that eucalyptus moved out of the packageset; taking alot of java dep's with it
[14:59] <micahg> right, but what about the stuff in the package set, what happens to it, are you still keeping an eye on those packages?
[15:00] <micahg> or were the java packages your main focus in that packageset?
[15:00] <jamespage> I definately have more focus on the java packages in that packageset - but its not exclusive
[15:01] <micahg> ok, any more questions?
[15:01] <jamespage> I have a few contributions to the packaging of openstack (nova) - but we do that through a packaging branch
[15:01] <bdrung> micahg: no
[15:01] <jamespage> so it not always relected in my personal upload history
[15:02] <stgraber> I'm ready to vote
[15:02] <micahg> Laney: anything else?
[15:03] <Laney> got pulled away, sorry
[15:03] <micahg> we have 2 minutes....
[15:04] <micahg> Laney: any questions for jamespage or can we vote?
[15:04] <Laney> my only question is social and is in regard to the MOTU application
[15:04] <Laney> do you feel you are as involved with the MOTU community as you should be?
[15:05] <Laney> s/you/a MOTU/ :-)
[15:05] <jamespage> Laney: honestly - I feel I could be more involved
[15:06] <micahg> time's up...I guess we'll take this to the mailing list
[15:06] <Laney> thought so
[15:06]  * Daviey raises pompom's for JamesPage.
[15:06] <Laney> I am ready to vote
[15:06] <Laney> if you still want to do it now
[15:06] <micahg> #vote jamespage to become core-dev (with social MOTU membership)
[15:06] <Daviey> micahg: If the others are ready to vote, couldn't it be achieved in meeting?
[15:06] <meetingology> Please vote on: jamespage to become core-dev (with social MOTU membership)
[15:06] <meetingology> Public votes can be registered by saying +1, +0 or -1 in channel, (private votes don't work yet, but when they do it will be by messaging the channel followed by +1/-1/+0 to me)
[15:06] <Laney> argh
[15:07] <Laney> you should hav edone that separately!
[15:07] <micahg> #endvote
[15:07] <meetingology> Voting ended on: jamespage to become core-dev (with social MOTU membership)
[15:07] <meetingology> Votes for:0 Votes against:0 Abstentions:0
[15:07] <meetingology> Deadlock, casting vote may be used
[15:07] <micahg> #vote jamespage to become core-dev
[15:07] <meetingology> Please vote on: jamespage to become core-dev
[15:07] <meetingology> Public votes can be registered by saying +1, +0 or -1 in channel, (private votes don't work yet, but when they do it will be by messaging the channel followed by +1/-1/+0 to me)
[15:07] <bdrung> +1
[15:07] <meetingology> +1 received from bdrung
[15:07] <stgraber> +1
[15:07] <meetingology> +1 received from stgraber
[15:08] <Laney> +1
[15:08] <meetingology> +1 received from Laney
[15:08] <Laney> no qualms about quality of work, good testimonials
[15:08] <Laney> good observations of your interactions with the release team :-)
[15:09] <micahg> +0, I don't have any technical reservations, but just a question if there have been enough main uploads that belong outside the packageset of server (which I think is broken), I"ll have to discuss this later as I still need to do a review (tentative +1)
[15:09] <meetingology> +0, I don't have any technical reservations, but just a question if there have been enough main uploads that belong outside the packageset of server (which I think is broken), I"ll have to discuss this later as I still need to do a review (tentative +1) received from micahg
[15:09] <micahg> #endvote
[15:09] <meetingology> Voting ended on: jamespage to become core-dev
[15:09] <meetingology> Votes for:3 Votes against:0 Abstentions:1
[15:09] <meetingology> Motion carried
[15:09] <micahg> jamespage: so core-dev tentative
[15:09] <micahg> #vote jamespage to be MOTU
[15:09] <meetingology> Please vote on: jamespage to be MOTU
[15:09] <meetingology> Public votes can be registered by saying +1, +0 or -1 in channel, (private votes don't work yet, but when they do it will be by messaging the channel followed by +1/-1/+0 to me)
[15:09] <micahg> +1
[15:09] <meetingology> +1 received from micahg
[15:10] <micahg> bdrung: Laney: stgraber ? ara is waiting :)
[15:10] <stgraber> +1
[15:10] <meetingology> +1 received from stgraber
[15:11] <Laney> -1 Sorry, but I would really like to see more social involvement with the MOTU team before giving people upload rights which they technically already have. I'd really like to see you back here in a few weeks though.
[15:11] <meetingology> -1 Sorry, but I would really like to see more social involvement with the MOTU team before giving people upload rights which they technically already have. I'd really like to see you back here in a few weeks though. received from Laney
[15:11] <micahg> Laney: would that be a +1 w/out core-dev?
[15:12] <micahg> bdrung: ?
[15:12] <bdrung> +0 core-dev gives you indirect motu membership. direct motu membership has a social component. (+1 without core-dev)
[15:12] <meetingology> +0 core-dev gives you indirect motu membership. direct motu membership has a social component. (+1 without core-dev) received from bdrung
[15:12] <Laney> erm, probably. I'd need to think about it.
[15:12] <micahg> #endvote
[15:12] <meetingology> Voting ended on: jamespage to be MOTU
[15:12] <meetingology> Votes for:2 Votes against:1 Abstentions:1
[15:12] <meetingology> Motion carried
[15:12] <micahg> ok, we'll take that to the ML
[15:12] <micahg> we'll decide a chair offline
[15:12] <micahg> #endmeeting
[15:12] <meetingology> Meeting ended Mon Sep 26 15:12:42 2011 UTC.
[15:12] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2011/ubuntu-meeting.2011-09-26-14.03.moin.txt
[15:13] <micahg> my apologies to ara and the Ubuntu Friendly team
[15:13] <ara> micahg, no worries :)
[15:14] <ara> Turn for the UF meeting
[15:14] <ara> hello!
[15:14] <brendand> hi!
[15:14] <roadmr> hey! o/ o\
[15:14] <jedimike> heyhey!
[15:14] <ara> #startmeeting
[15:14] <meetingology> Meeting started Mon Sep 26 15:14:59 2011 UTC.  The chair is ara. Information about MeetBot at http://wiki.ubuntu.com/AlanBell/mootbot.
[15:14] <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
[15:15] <ara> Getting started, we only have 45 minutes this time
[15:15] <ara> #topic AGENDA
[15:15] <ara> * I want my 3 stars!!
[15:15] <ara> * AOB
[15:16] <ara> #topic I want my 3 stars!!
[15:16] <ara> As you guys know (or if not you know now), a system that reports all its core components as working gets a minimum of three stars.
[15:16] <ara> #link https://wiki.ubuntu.com/UbuntuFriendly/Process
[15:16] <ara> If one or more core components are reported as not working, the system gets the minimum rating (1 star). What happens at this point:
[15:16] <ara> #link http://<IP_ADDRESS>/
[15:16] <ara> It is clear that some tests that are associated with core components are still failing.
[15:16] <ara> This meeting is an attempt to coordiante between the people working on the client side and the people working on the server side to know exactly what needs to be done in order for this to work correctly.
[15:16] <ara> Anyone has an idea where to look?
[15:17] <roadmr> o/
[15:17] <ara> ..
[15:17] <brendand> o/
[15:17] <ara> roadmr, go ahead
[15:17] <roadmr> I guess everyone has something to say on this :)
[15:17] <jedimike> o/
[15:17] <ara> :)
[15:18] <roadmr> We should look at submissions from systems we know from experience are mostly working, see which tests are marked as failing, and either improve the tests so they don't fail, or have the calculation script not consider them as fail-worthy
[15:18] <roadmr> I know for instance a lot of systems fail the cpu_frequency_governors test by a small percentage, but they still work fine
[15:18] <roadmr> since this test is in the cpu category it is considered core
[15:19] <roadmr> it's just an example though, I'd still say to review the submissions and make any tweaks necessary is a possible way to go
[15:19] <roadmr> ..
[15:19] <ara> thanks roadmr
[15:19] <ara> brendand, ?
[15:19] <brendand> hi
[15:19] <brendand> first of all, roadmr - frequency_governor isn't in the whitelist ;)
[15:20] <brendand> i'll just clear that up
[15:20] <brendand> but what i was going to say is, take the example of this Samsung N310 i have
[15:20] <brendand> i have two bugs:
[15:20] <brendand> https://bugs.launchpad.net/checkbox/+bug/855382
[15:21] <brendand> the wireless on this system works perfectly but because of this bug the tests don't run
[15:21] <brendand> second, and this is a question as well:
[15:21] <brendand> https://bugs.launchpad.net/checkbox/+bug/855538
[15:22] <brendand> the question being does that impact the stars (i didn't think camera was a core component)?
[15:22] <brendand> also that one is easily workaroundable (by installing xawtv)
[15:22] <brendand> ...
[15:22] <ara> jedimike, ?
[15:23] <jedimike> at the moment, in UF I just store if a certain category of test has passed or failed. What I'd like to do is store the names of the tests that caused a category to fail, so we can see what we need to do for specific systems to get the 3 stars and above.
[15:24] <jedimike> I feel like that's starting to duplicate the results tracker's functionality though, so I'd like cr3 to feedback on that before i do anything
[15:24] <jedimike> ...
[15:24] <ara> cr3, around?
[15:25] <ara> it looks like he's not around
[15:25] <cr3> ara: I'm there, thinking
[15:26] <jedimike> cr3: it's not something i'd display on the site, just something i'd record so we can get a breakdown of failures easily based on the definitions of systems that UF has
[15:26] <cr3> jedimike: I'm not sure about the implications of what you propose, does this need to be solved here?
[15:27] <ara> in the mean time I have a question about brendan's wireless. If his wifi card is not recognize as wireless, it shouldn't count as core component, shouldn't it?
[15:27] <ara> it is like it is not there
[15:27] <jedimike> cr3: it doesn't need to be solved on the UF side if you already know which tests are the troublesome ones, or have an easy way of finding that out
[15:28] <cr3> jedimike: I meant "here" as in "within the 30 minutes of this meeting". this is the first time I hear about this request, so I'd like to better understand it and having to raise hand to talk is going to make that rather long
[15:28] <jedimike> cr3: ok, it's an idea i came up with in the last 5 mins, which is why this is the first mention of it :)
[15:28] <cr3> jedimike: no problem, lets talk about the implementation details after the meeting
[15:29] <brendand> o/
[15:29] <cr3> ..
[15:29] <ara> #action jedimike and cr3 to talk about how to get a list of failing tests
[15:29] <meetingology> ACTION: jedimike and cr3 to talk about how to get a list of failing tests
[15:29] <ara> brendand, ?
[15:30] <brendand> i think it would be better if wireless was a seperate category so we can make the distinction between it not working on a laptop and it not working on a desktop
[15:30] <brendand> but
[15:30] <brendand> wouldn't it be the case that *all* tests in a category would need to pass to say the component is working?
[15:31] <ara> yes, that's the case
[15:31] <brendand> so as long as we test each of the network interfaces, having them all bundled under NETWORKING would be okay
[15:31] <brendand> since both the wifi and ethernet would have to work
[15:31] <ara> brendand, but wifi is not core in a desktop
[15:32] <brendand> yeah, see it's a tricky one. well as i said in the bug, the only way may be to relax the requires on the wireless test. if a system doesn't have wireless then the user will just have to say that, since there doesn't seem to be a perfectly reliable way to detect it
[15:32] <brendand> ...
[15:33] <roadmr> o/
[15:33] <ara> roadmr, go ahead
[15:33] <roadmr> as far as I could see, looking at the output of iwconfig is pretty reliable to identify wireless. Just a thought.
[15:33] <roadmr> ..
[15:34] <ara> o/
[15:34] <ara> I think that it is clear that we need a better solution for the atheros wifi, but I am afraid that it is too late for that :(
[15:34] <ara> do you think a fix is feasible for Oneiric?
[15:34] <ara> ..
[15:34] <brendand> o/
[15:35] <ara> brendand, go ahead
[15:35] <brendand> roadmr, that's true - i meant using the info in udev_resource. we'd have to write a new resource script. as ara said, feasible in the next couple of days?
[15:36] <brendand> may be better to relax the requirement and put whatever better fix there is in the PPA version
[15:36] <brendand> ...
[15:36] <ara> I was voting for not even relax the requirement ;-)
[15:37] <ara> atheros will have 1 star
[15:37] <ara> known issue
[15:37] <ara> (we will be in Beta, anyway)
[15:37] <ara> ..
[15:37] <brendand> fair enough, i don't agree - but your call ;)
[15:37] <ara> no, let's vote
[15:38] <ara> #vote defer the problem with the atheros wifi cards to 12.04 LTS
[15:38] <meetingology> Please vote on: defer the problem with the atheros wifi cards to 12.04 LTS
[15:38] <meetingology> Public votes can be registered by saying +1, +0 or -1 in channel, (private votes don't work yet, but when they do it will be by messaging the channel followed by +1/-1/+0 to me)
[15:39] <ara> nobody votes?
[15:39] <roadmr> +1
[15:39] <meetingology> +1 received from roadmr
[15:39] <brendand> ara - i don't think the question is well worded
[15:39] <cr3> ara: I'm still trying to understand how significant the changes really are
[15:40] <ara> #endvote
[15:40] <meetingology> Voting ended on: defer the problem with the atheros wifi cards to 12.04 LTS
[15:40] <meetingology> Votes for:1 Votes against:0 Abstentions:0
[15:40] <meetingology> Motion carried
[15:40] <brendand> -1
[15:40] <ara> OK, let's discuss it a bit further before voting
[15:40] <ara> and brendand, you do the wording ;)
[15:40] <brendand> ara - sure
[15:40] <roadmr> o/
[15:40] <ara> roadmr, go ahead
[15:40] <cr3> o/
[15:40] <roadmr> there are many tweaks to be done, I think if we scram to fix this particular one when there are so many to handle is not good
[15:41] <roadmr> so I'd say working on those tweaks for the P cycle (and maybe making progress available in a checkbox-stable ppa) would be better than rushing to meet O release
[15:41] <roadmr> ..
[15:41] <ara> cr3, your turn
[15:41] <cr3> is there a bug open about atheros wireless cards?
[15:41] <cr3> ..
[15:41] <ara> https://bugs.launchpad.net/checkbox/+bug/855382
[15:41] <cr3> o/
[15:42] <ara> cr3, go ahead :)
[15:42] <jedimike> o/
[15:42] <cr3> should systems with these cards be reported with one star or, if the card is detected as NETWORKING instead of WIRELESS, could the device be ignored and reported as 3 stars?
[15:43] <ara> cr3, I thought that it would be 3 stars, as UF thinks that there is no wireless card
[15:43] <cr3> ..
[15:44] <ara> jedimike, go
[15:44] <jedimike> cr3: if there's no wireless card, and no wireless tests run, it would still be possible to get 3 stars, yes
[15:44] <jedimike> also
[15:44] <jedimike> I'm wondering what cards this bug affects
[15:45] <jedimike> because http://<IP_ADDRESS>/11.10/ASUSTeK%20Computer%20Inc./U36SD/p:E4:I8g:B4w:BFJp:h:B5G:Cw9:BkT/ reports an atheros wireless card, and one unit has the tests passing for it too
[15:45] <jedimike> so perhaps it's only a certain model of atheros card?
[15:45] <jedimike> ...
[15:46] <cr3> o/
[15:46] <ara> cr3, go ahead :)
[15:46] <cr3> after looking at the bug, I personally don't have enough information to determine the scope of the change necessary to make this work. so, if we vote, I'm: 0
[15:46] <cr3> ..
[15:47] <brendand> o/
[15:47] <ara> brendand, go ahead
[15:48] <brendand> to answer jedimikes question, i have two netbooks though i'm not sure if they have the same card or a different one - and they are both affected by this
[15:48] <brendand> the exact model is shown in the bug
[15:48] <brendand> but for the purpose of voting people should assume only one model of atheros card is affected
[15:49] <brendand> ...
[15:49] <ara> OK, let's vote, this is taking too much time
[15:49] <ara> brendand, what should be the wording?
[15:50] <brendand> ara - now that i'm trying to think of one it's quite difficult!
[15:51] <ara> shall I give a try?
[15:52] <brendand> ara - i'll go with your wording now that we all understand the issue better
[15:52] <ara> #vote Postpone the investigation and fix or workaround for bug 855382 for P
[15:52] <meetingology> Please vote on: Postpone the investigation and fix or workaround for bug 855382 for P
[15:52] <meetingology> Public votes can be registered by saying +1, +0 or -1 in channel, (private votes don't work yet, but when they do it will be by messaging the channel followed by +1/-1/+0 to me)
[15:53] <roadmr> +1 we need more data to decide on this, tweaking for specific systems piecemeal is going to be too much work
[15:53] <meetingology> +1 we need more data to decide on this, tweaking for specific systems piecemeal is going to be too much work received from roadmr
[15:53] <jedimike> 0, because i'm not sure if we have enough information to prove the fix or not
[15:53] <meetingology> 0, because i'm not sure if we have enough information to prove the fix or not received from jedimike
[15:53] <ara> +1, we don't even know if this issue is causing those systems to have one star
[15:53] <meetingology> +1, we don't even know if this issue is causing those systems to have one star received from ara
[15:53] <cr3> 0
[15:53] <meetingology> 0 received from cr3
[15:53] <brendand> 0
[15:53] <meetingology> 0 received from brendand
[15:54] <ara> #endvote
[15:54] <meetingology> Voting ended on: Postpone the investigation and fix or workaround for bug 855382 for P
[15:54] <meetingology> Votes for:2 Votes against:0 Abstentions:3
[15:54] <meetingology> Motion carried
[15:54] <ara> OK,  moved to P
[15:54] <ara> o/
[15:55] <ara> Before we end the meeting I would like to know if it would be easy to cr3 to get a list of tests in the RT that are failing, and jedimike a list of core categories that are failing
[15:55] <ara> so we can concentrate if fixing those
[15:55] <ara> ..
[15:55] <jedimike> o/
[15:56] <ara> jedimike, go ahead
[15:56] <cr3> o/
[15:56] <jedimike> it would be relatively easy for me to record the failing tests against the failing categories in UF, and that's what our action is about discussing
[15:56] <jedimike> ...
[15:57] <ara> cr3, ?
[15:57] <cr3> ara: could what jedimike is proposing meet both requirements, ie absolving me of that action item? :)
[15:57] <cr3> ..
[15:58] <ara> cr3, jedimike: I would prefer if you guys could talk about it, so we make sure that we are not putting stuff in UF that should be in LR
[15:59] <ara> but we need it, urgently :)
[15:59] <ara> OK, anything else on this topic?
[15:59] <cr3> ara: ok, feel free to add another action item for both of us to coordinate
[15:59] <ara> it was about that :)
[16:00] <ara> moving on to the next topic?
[16:00] <ara> #topic Any Other Business?
[16:00] <roadmr> o/
[16:00] <ara> roadmr, go ahead
[16:01] <roadmr> Just a last call for testing, if you get a minute to add the checkbox ppa to your oneiric system and run it, to make sure we don't have any nasty showstoppers at this point. Thanks!
[16:01] <roadmr> ..
[16:02] <ara> thanks roadmr :)
[16:02] <ara> Anything else?
[16:03] <ara> #endmeeting
[16:03] <meetingology> Meeting ended Mon Sep 26 16:03:09 2011 UTC.
[16:03] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2011/ubuntu-meeting.2011-09-26-15.14.moin.txt
[16:03] <ara> thanks brendand, roadmr, jedimike and cr3 for participating!
[16:03] <roadmr> awesome, thanks!
[16:03] <jedimike> :)
[16:03] <brendand> bye!
[16:03] <roadmr> ready for the 'freeze?
[17:00] <mdeslaur> hello
[17:00] <jdstrand> hi
[17:01] <dlm_> hi
[17:01] <tyhicks> hello
[17:01] <jjohansen> \o
[17:01] <jdstrand> so, let's get started
[17:01] <jdstrand> #startmeeting
[17:01] <meetingology> Meeting started Mon Sep 26 17:01:51 2011 UTC.  The chair is jdstrand. Information about MeetBot at http://wiki.ubuntu.com/AlanBell/mootbot.
[17:01] <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
[17:01] <jdstrand> The meeting agenda can be found at:
[17:01] <jdstrand> [LINK] https://wiki.ubuntu.com/SecurityTeam/Meeting
[17:02] <jdstrand> [TOPIC] Announcements
[17:02] <jdstrand> Ubuntu 11.10 is scheduled to release in a few weeks. If you are interested, it would be great if people helped make sure that the [[https://launchpad.net/ubuntu-cve-tracker|Ubuntu CVE Tracker]] is up to date for the devel release (particularly for universe/multiverse packages.
[17:02] <jdstrand> [TOPIC] Review of any previous action items
[17:03] <jdstrand> jdstrand to update highlighted packages to also mention UCT in general: this was completed, but not in HighlightedPackages, because it is included by GettingInvolved, and that didn't quite make sense
[17:03] <jdstrand> I updated the wiki docs to mention it and made it part of our release cycle checklist
[17:03] <jdstrand> [TOPIC] Weekly stand-up report
[17:03] <jdstrand> I'm on community this week
[17:04] <jdstrand> I've got some more MIRs to audit, some pending updates, a couple work items and some last minute oneiric bugs
[17:04] <jdstrand> I hope to actually squeeze apparmor testing in this week as well
[17:04] <jdstrand> that's it from me
[17:04] <jdstrand> mdeslaur: you're up
[17:05] <mdeslaur> I've just rebuilt my tomcat6 packages because of a new CVE that popped up this morning
[17:05] <mdeslaur> so I'll be testing those this week
[17:05] <mdeslaur> also, there are some CVEs mismatches in oneiric still, so I'll be working on those
[17:05] <mdeslaur> this week, we need to brainstorm our UDS blueprints
[17:06] <mdeslaur> so we can start creating them at the end of the week
[17:06] <mdeslaur> and that's it from me
[17:06] <mdeslaur> sbeattie: you're up
[17:07] <sbeattie> I'm still working on php (*sigh*), apache and openssl
[17:07] <mdeslaur> sbeattie: need any help/moral support?
[17:07] <jdstrand> mdeslaur: ah, yes, meant to add UDS prep to my list as well
[17:07] <sbeattie> I'm also hoping to do some qart testing this week, to ensure that things are in a good shape for oneiric
[17:08] <sbeattie> mdeslaur: send booze.
[17:08]  * kees hugs sbeattie
[17:08] <sbeattie> And I guess UDS prep as well.
[17:08] <mdeslaur> sbeattie: heh
[17:08] <sbeattie> I think that's it for me. micahg, you're up.
[17:09] <micahg> tomorrow's Mozilla release day, so Firefox/Thunderbird to go out
[17:09] <micahg> I still have chromium that needs to go out
[17:09] <micahg> NSS should be updated for oneiric final, I'm going to try to get that done as well
[17:09] <micahg> UDS/blueprint/qrt next week for me
[17:10] <micahg> oh, and it's a short week for me, off Thu/Fri
[17:10] <micahg> tyhicks: your turn
[17:10] <tyhicks> I've got the triage role this week.
[17:10] <tyhicks> I will finish up mutt testing (some other items preempted me last week), finish backporting and testing a few eCryptfs patches for a libreoffice-on-ecryptfs bug, and take a closer look at an upstream eCryptfs oops report.
[17:11] <tyhicks> jdstrand: that's it for me
[17:12] <jdstrand> cool
[17:12] <jdstrand> [TOPIC] Highlighted packages
[17:12] <jdstrand> The 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. See 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/Securi
[17:13] <jdstrand> http://people.canonical.com/~ubuntu-security/cve/pkg/tangerine.html
[17:13] <jdstrand> http://people.canonical.com/~ubuntu-security/cve/pkg/cakephp.html
[17:13] <jdstrand> http://people.canonical.com/~ubuntu-security/cve/pkg/xymon.html
[17:13] <jdstrand> http://people.canonical.com/~ubuntu-security/cve/pkg/libglpng.html
[17:13] <jdstrand> http://people.canonical.com/~ubuntu-security/cve/pkg/libcgroup.html
[17:13] <jdstrand> [TOPIC] Miscellaneous and Questions
[17:13] <jdstrand> Does anyone have any other questions or items to discuss?
[17:16] <jdstrand> thanks everyone!
[17:16] <jdstrand> #endmeeting
[17:16] <meetingology> Meeting ended Mon Sep 26 17:16:59 2011 UTC.
[17:16] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2011/ubuntu-meeting.2011-09-26-17.01.moin.txt
[17:19] <mdeslaur> hanks jdstrand!
[17:19] <mdeslaur> euh, thanks
[17:19] <micahg> thanks jdstrand
[18:00] <akgraner> ok it's time for the Ubuntu Leadership team meeting
[18:00] <akgraner> #startmeeting
[18:00] <meetingology> Meeting started Mon Sep 26 18:00:33 2011 UTC.  The chair is akgraner. Information about MeetBot at http://wiki.ubuntu.com/AlanBell/mootbot.
[18:00] <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
[18:01] <akgraner> here's the agenda for the meeting - https://wiki.ubuntu.com/UbuntuLeadership/Meetings
[18:01] <akgraner> [link] - https://wiki.ubuntu.com/UbuntuLeadership/Meetings
[18:01] <akgraner> #link https://wiki.ubuntu.com/UbuntuLeadership/Meetings
[18:01] <AlanBell> it got it, just doesn't echo it back to you :)
[18:01] <akgraner> ok clearly I need a lesson on how to use this new bot
[18:01] <valorie> o/
[18:02] <akgraner> thanks AlanBell I didn't realize that
[18:02] <akgraner> :-)
[18:02] <akgraner> ok I'll give it just another minute then we'll get started
[18:02] <AlanBell> it is a bit inconsistent at the moment, but it should be less echoey in principal
[18:02] <cjohnston> o/
[18:02] <Joeb454> o/
[18:02]  * charlie-tca waves
[18:03] <Cheesehead> o/
[18:03] <AlanBell> the other one is like Sigourney Weaver in Galaxy Quest
[18:04] <akgraner> #topic - Welcome
[18:04] <AlanBell> o/
[18:04] <topyli> aww
[18:04] <topyli> o/
[18:04]  * pleia2 waves
[18:04] <IdleOne> o/
[18:04] <akgraner> Since this is the first of our meetings I wanted to take a moment and welcome everyone and say thank you to those who have already joined the team
[18:05] <akgraner> and are working toward the goals of better leadership resources and skills
[18:06] <akgraner> The main wiki landing page that gives a little more description about the team can be found at https://wiki.ubuntu.com/UbuntuLeadership
[18:06] <valorie> I'd like to thank Amber and David for getting us up and running
[18:06] <valorie> and everybody who has already contributed!
[18:07] <valorie> every day there is new cool stuff!
[18:07] <akgraner> Thanks valorie! and thanks to head_victim for working on the wiki pages over the weekend
[18:07] <topyli> indeed, the infrastructure is pretty much there
[18:07] <akgraner> #topic Ubuntu Leadership document -
[18:07] <akgraner> valorie, this is your item  - ready to discuss it?
[18:08] <valorie> your item and my item are pretty much the same
[18:08] <akgraner> oh and if you have comments on a topic please use o/ and wait to be recognized
[18:08] <valorie> I would like to know what plans/thoughts are about the docs
[18:08] <akgraner> ahh ok
[18:09] <akgraner> then let me go through what we've got and go from there then
[18:09] <valorie> I see that we are planning to get the manual into version control
[18:09] <valorie> cool
[18:09] <akgraner> sound ok?
[18:09] <valorie> yep
[18:10] <topyli> o/
[18:10] <akgraner> right now we have a couple active documents we are working on  - LoCo Leadership handbook, Leadership skills list and the welcome letter
[18:11] <akgraner> topyli, go ahead
[18:11] <topyli> about the handbook. it sounds like it could easily become an actual book on leadership and not very ubuntu specific. i see this as a danger, how can we handle producing it?
[18:12] <akgraner> great question
[18:12] <akgraner> Leadership is universal
[18:12] <akgraner> no matter what the project - but we can add items that tailor it to the specific needs of the Ubuntu Community
[18:13] <akgraner> in the case of the LoCo leadership handbook the target audience is LoCo leadership
[18:14] <akgraner> I am not sure I see a danger in a general book on leadership skills and styles as there will always be some overlap needed
[18:14] <topyli> sure, but there already are books like that
[18:14] <akgraner> yes but not tailored to Ubuntu community
[18:14] <valorie> so this is seen as about Loco leadership, and not about all the leadership roles in the ubuntu community?
[18:14] <akgraner> which is what we are wanting to do
[18:14] <topyli> maybe we should steal jono's disposition and tailor it
[18:15] <akgraner> we can take elements from Art of community - but the goal is to give leaders the skills they don't have
[18:15] <akgraner> and teach the leadership styles and how it fits with an all volunteer community
[18:16] <akgraner> we had to start somewhere  - so we started with LoCo teams b/c over the past few years I have had several people ask me about leading loco teams
[18:16] <akgraner> valorie, no it will be for all leadership positions - but again we just picked a place to start
[18:17] <akgraner> this will not be a requirement but a set or resources for the community
[18:17] <charlie-tca> LoCo Handbook would seem like it should be very loco oriented. That doesn't mean limiting this group to loco's, though.
[18:17] <akgraner> charlie-tca, right
[18:17] <akgraner> people can take and tailor it to any group
[18:18] <akgraner> we aren't here to force people to use these skills but to lead by example and be here to help and provide training etc when people ask for it
[18:18] <akgraner> back to valorie's point
[18:18] <jussi> Is it planned then to actually be part of the process that that happens? or just a lets do this and hope others pick it up and taylor it?
[18:19] <akgraner> yes we want to get it into bzr by module/chapter for proper version control
[18:19] <topyli> i can imagine it being versioned for forums/irc/technical...
[18:19] <akgraner> jussi, the hope is that we get this first resource written and promoted
[18:19] <akgraner> them encourage and help tailor it to other projects and teams
[18:20] <akgraner> topyli, exactly
[18:21] <akgraner> here are the links to the documents in case someone doesn't have them already - Leadership Handbook - https://docs.google.com/document/d/1_5CJYkBSaoN4l7L8mIPKoZNxzPrr16NOZP12Ln_8EXg/edit?hl=en_US
[18:21] <akgraner> skills list - https://docs.google.com/document/d/13VOmTgEqCzIW8oITV2d5fIRD3xsiKRVMd39OUlpx6xQ/edit?hl=en_US
[18:21] <valorie> cool
[18:21] <akgraner> welcome letter - https://docs.google.com/document/d/1da8Moj340VcvzIQuX8XUm3OXDZpb9l6bfxz8vkvIZM4/edit?hl=en_US
[18:22] <akgraner> any other questions or comments about the documents we've started so far?
[18:22] <akgraner> Also I plan on blogging weekly about various leadership skills and styles each Monday
[18:23] <akgraner> so if you want more information on something let me know and I'll add it to the list
[18:23] <akgraner> and the wiki page will contain links to all blog posts about or from the leadership team stuff
[18:24] <akgraner> https://wiki.ubuntu.com/UbuntuLeadership/Links
[18:24] <valorie> that is very useful
[18:24] <akgraner> Anyone opposed to sending the welcome letter to members who join the mailing list?
[18:24] <akgraner> I can set it up to send it automatically when someone joins
[18:25] <akgraner> Just means we'll have to be careful to make sure it's always up to date :-)
[18:25] <valorie> sounds great!
[18:25] <topyli> go ahead, it's a good idea
[18:26] <charlie-tca> +1
[18:26] <akgraner> #action akgraner to add automatic welcome letter to those joining the mailing list
[18:26] <meetingology> ACTION: akgraner to add automatic welcome letter to those joining the mailing list
[18:26] <akgraner> ok any other comments about documentation before I move on?
[18:27] <akgraner> #needs
[18:27] <akgraner> #topic needs
[18:27] <akgraner> Logo
[18:27] <akgraner> Getting the documentation into BZR by module
[18:27] <akgraner> Recruiting more members
[18:28] <akgraner> these are just a few of the needs I listed - I am sure there are more but for this meeting I didn't want to go over an hour
[18:28] <akgraner> can someone work on getting a logo designed?
[18:28] <akgraner> that meets the branding guidelines
[18:28] <akgraner> anyone?
[18:29] <topyli> i could talk to knome, he's good but i don't know if he's interested
[18:29] <akgraner> cool - could someone contact the Canonical design team and see if someone there would be interested in helping
[18:30] <akgraner> I know they are busy right now - but at least we can get it on their radar
[18:30] <akgraner> Basically let's all explore the contacts we have with various design people and see what we can come back with
[18:30] <akgraner> how does that sound?
[18:31] <akgraner> Let's see what we can do between now and UDS
[18:31] <jussi> ++ knome being good.
[18:32] <valorie> +1
[18:32] <charlie-tca> +1
[18:32] <akgraner> #action topyli to talk to knome - other team members to talk to other sources as well and see what we come up with
[18:32] <meetingology> ACTION: topyli to talk to knome - other team members to talk to other sources as well and see what we come up with
[18:32] <akgraner> topyli, is that ok with you?
[18:32] <topyli> sounds good to me
[18:32] <akgraner> thank you!
[18:33] <akgraner> next  - we need someone who can add the chapters into BZR
[18:33] <akgraner> I'm not a documentation person, but I am willing to learn
[18:33] <akgraner> if someone can take the lead on this that would be great
[18:34] <akgraner> Any documentation guru's in the group
[18:34] <valorie> DarkwingDuck is a natural
[18:34] <akgraner> I know DarkwingDuck said he would help with this as well - I know he's been a little busy
[18:34] <valorie> he just pushed the kubuntu docs for 11.10
[18:34] <akgraner> but can some folks contact him and give him a hand
[18:35] <valorie> I will gladly do so
[18:35] <akgraner> #action DarkwingDuck to get documentation into BZR
[18:35] <meetingology> ACTION: DarkwingDuck to get documentation into BZR
[18:35] <akgraner> I just volun-told him :-)
[18:35] <valorie> I'm on the Kub. docs team
[18:35] <charlie-tca> I guess I will have to learn BZR yet, then.
[18:36] <valorie> the beginner bits weren't hard
[18:36] <akgraner> valorie, awesome - can you talk to DarkwingDuck and you all come up with plan
[18:36] <valorie> will do
[18:36] <akgraner> thanks
[18:36] <valorie> I think the big bit is the docbook-ification
[18:36] <akgraner> #action valorie collaborate with DarkwingDuck on documentation efforts
[18:36] <meetingology> ACTION: valorie collaborate with DarkwingDuck on documentation efforts
[18:36] <valorie> we might need some group help with that
[18:37] <charlie-tca> Maybe mallard would help with it?
[18:37] <akgraner> I'm getting a class at UDS on how to do this
[18:37] <valorie> mallard and DarkwingDuck sound like a match made in Heaven!
[18:37] <valorie> :-)
[18:37] <akgraner> haha
[18:37] <akgraner> ok recruitment
[18:37] <charlie-tca> akgraner: subscribe me to it?
[18:38] <akgraner> charlie-tca, ok will do  (the class you mean)
[18:38] <charlie-tca> right, the class
[18:38] <akgraner> will do
[18:39] <akgraner> we've had a lot of people show interest in this group - we need to make sure everyone knows this is a place for resources and training and learning about leadership
[18:39] <akgraner> it's nothing that leaders will be forced to go through
[18:39] <akgraner> but we want to know what people need from this group.
[18:40] <akgraner> I'll email all the leadership councils and boards and loco-contacts but if you all could forward that email once I send it to the list that would be great
[18:40] <akgraner> any thoughts on what else we can do at this moment to gain more interest in the group?
[18:41] <akgraner> there will be  many things we can do once we are more organized and have more resources in place
[18:41] <akgraner> but for now - any suggestions?
[18:41] <Cheesehead> o/
[18:41] <akgraner> Cheesehead, go ahead
[18:42] <Cheesehead> I'm interested in providing...
[18:42] <Cheesehead> small-group sessions on IRC of specific skills.
[18:42] <Cheesehead> So if anyone looks at that skill list...
[18:42] <Cheesehead> and sees something they want to learn or teach , please let me know
[18:42] <akgraner> +1 one for that - we would like to have a series of leadership based classes
[18:42] <Cheesehead> ..
[18:43] <topyli> oh yes, small sessions on specific topics
[18:43] <akgraner> #action Cheesehead to manage online leadership tutorial sessions
[18:43] <meetingology> ACTION: Cheesehead to manage online leadership tutorial sessions
[18:43] <Cheesehead> rgr
[18:44] <akgraner> Cheesehead, that sound good to you - you can clear the dates with the classroom team and start rolling them out
[18:44] <akgraner> I am sure there are many people on the team already who are ready to go forth and share various skills
[18:45] <valorie> I hope that we'll be advertising to *all* leaders in the community
[18:45] <valorie> not just loco leaders
[18:45] <akgraner> so if you are interested in teaching leadership skills online talk to Cheesehead
[18:45] <akgraner> valorie, we are
[18:45] <valorie> because really, aren't we interested in growing the group as well as providing a good skillset?
[18:45] <topyli> especially aspiring ones, i would assume
[18:45] <valorie> cool
[18:45] <akgraner> all councils, boards, and team contacts are getting emails
[18:46] <valorie> \o/
[18:46] <akgraner> valorie, yes - much like UW is a springboard to the community  - this is a springboard to leaderhip mentoring and better leaders
[18:46] <akgraner> make sense
[18:47] <topyli> akgraner's blog (and hopefully all our blogs!) works to getting new blood inspired i hope
[18:47] <akgraner> we want current, new and aspiring leaders to all be part of this team and learn from each other
[18:47] <akgraner> topyli, yes exactly
[18:47] <akgraner> just make sure when you blog about leadership and the team you add the link to the wiki page
[18:47] <akgraner> :-)
[18:47] <valorie> akgraner: that's a great crystalization of the team mission, right there
[18:48] <akgraner> yep :-)
[18:48] <topyli> yeah put it at the top of the wiki page :)
[18:48] <akgraner> #topic acknowledgements
[18:48] <akgraner> Again thank you to everyone who has helped so far in everything that you have been doing!
[18:48] <akgraner> Great work!
[18:49] <akgraner> #topic next meeting
[18:49] <akgraner> do we want to have monthly meetings or bi-monthly meetings?
[18:49] <topyli> thanks all
[18:49] <Cheesehead> Monthly
[18:50] <akgraner> +1 for monthly from me
[18:50] <valorie> +1 here
[18:50] <topyli> +1, we change if it doesn't feel right
[18:50] <akgraner> I'll check the calendar and see what is going on the last week of October
[18:50] <akgraner> people will be getting ready for UDS but...
[18:51] <topyli> oh dear, it's last week of the month again. where did my time go?
[18:51] <akgraner> Oct 24th at 1800 UTC is open
[18:52] <akgraner> so let's set it for 24 Oct 1800 UTC and see how it works out...
[18:52] <akgraner> any volunteers to chair the next meeting
[18:52] <valorie> o/
[18:53] <akgraner> valorie, are you voluteering or do you have a comment
[18:53] <valorie> I've never done it, but can pick AlanBell's brain
[18:53] <valorie> volunteering
[18:53] <akgraner> valorie, it's easy  :-)
[18:53]  * AlanBell reads back
[18:53] <AlanBell> oh yeah, help yourself to my brain
[18:53] <valorie> I'm not going to UDS, so it's perfect
[18:54] <akgraner> #action valorie to chair next leadership meeting on 24 OCT 2011 @1800 UTC in -meeting
[18:54] <meetingology> ACTION: valorie to chair next leadership meeting on 24 OCT 2011 @1800 UTC in -meeting
[18:54] <akgraner> anything else before I end the meeting?
[18:54] <topyli> how did you think about distributing the minutes?
[18:54] <topyli> it could be advertising too if you distribute them widely
[18:54] <akgraner> mailing list, wiki page
[18:54] <akgraner> as well as social media :-) and blogs
[18:55] <topyli> ok good enough :)
[18:55] <akgraner> Thanks everyone!
[18:55] <akgraner> #endmeeting
[18:55] <meetingology> Meeting ended Mon Sep 26 18:55:43 2011 UTC.
[18:55] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2011/ubuntu-meeting.2011-09-26-18.00.moin.txt
[18:56] <valorie> thank you akgraner -- good meeting!
[18:56] <charlie-tca> akgraner: thank you for chairing
[18:56] <Cheesehead> akgraner: Good meeting. Thanks.
[18:56] <akgraner> thanks! :-)
[18:56]  * akgraner blushes and heads back to -leadership
[19:01] <AlanBell> valorie: grab me any time with questions or to try a practice meeting with the bot
[19:01] <AlanBell> https://wiki.ubuntu.com/meetingology <- reasonable documentation
[19:23] <valorie> AlanBell: I'll make a doc with stuff I can copy/paste for the meeting, and get your feedback on it, if you are willing


[00:01] <vorlon> LocutusOfBorg, tjaalton: accepted
[00:01] -queuebot:#ubuntu-release- New: accepted xxhash [amd64] (bionic-proposed) [0.7.3-1~ubuntu18.04.2]
[00:01] -queuebot:#ubuntu-release- New: accepted xxhash [armhf] (bionic-proposed) [0.7.3-1~ubuntu18.04.2]
[00:01] -queuebot:#ubuntu-release- New: accepted xxhash [ppc64el] (bionic-proposed) [0.7.3-1~ubuntu18.04.2]
[00:01] -queuebot:#ubuntu-release- New: accepted xxhash [arm64] (bionic-proposed) [0.7.3-1~ubuntu18.04.2]
[00:01] -queuebot:#ubuntu-release- New: accepted xxhash [s390x] (bionic-proposed) [0.7.3-1~ubuntu18.04.2]
[00:01] -queuebot:#ubuntu-release- New: accepted xxhash [i386] (bionic-proposed) [0.7.3-1~ubuntu18.04.2]
[00:02] -queuebot:#ubuntu-release- New: accepted rust-globwalk [riscv64] (hirsute-proposed) [0.8.1-1]
[00:02] -queuebot:#ubuntu-release- New: accepted rust-rustc-std-workspace-std [riscv64] (hirsute-proposed) [1.0.1-1]
[00:02] <LocutusOfBorg> thanks
[00:02] <LocutusOfBorg> vorlon, LocutusOfBorg> oSoMoN, golang-gopkg-libgit2-git2go.v28 should be removed?
[00:02] <LocutusOfBorg> for this one?
[00:02] <LocutusOfBorg> we would like to progress on transitions
[00:03] <LocutusOfBorg> superseeded by golang-gopkg-libgit2-git2go.v30 and golang-gopkg-libgit2-git2go.v31
[00:03] <LocutusOfBorg> no reverse-deps, removed in debian
[00:03] <LocutusOfBorg> Updating golang-gopkg-libgit2-git2go.v28 introduces new bugs: #976522.
[00:04] -queuebot:#ubuntu-release- New binary: vlc-plugin-bittorrent [riscv64] (hirsute-proposed/universe) [2.12-2] (no packageset)
[00:06] <vorlon> LocutusOfBorg: what transition does this impact?
[00:06] <LocutusOfBorg> libgit2
[00:06] <LocutusOfBorg> not being shown as candidate
[00:06] <vorlon> ok
[00:06] <LocutusOfBorg> autopkgtest fails
[00:06] <vorlon> removed
[00:06] <LocutusOfBorg> <3
[00:07]  * LocutusOfBorg goes to sleep
[00:07] <LocutusOfBorg> cheers!
[00:09] -queuebot:#ubuntu-release- New binary: rust-rustc-std-workspace-std [arm64] (hirsute-proposed/universe) [1.0.1-1] (no packageset)
[00:09] -queuebot:#ubuntu-release- New binary: wordpress [amd64] (hirsute-proposed/universe) [5.6+dfsg1-2ubuntu1] (no packageset)
[00:11] -queuebot:#ubuntu-release- New: accepted wordpress [amd64] (hirsute-proposed) [5.6+dfsg1-2ubuntu1]
[00:11] -queuebot:#ubuntu-release- New: accepted rust-rustc-std-workspace-std [arm64] (hirsute-proposed) [1.0.1-1]
[00:11] -queuebot:#ubuntu-release- New: accepted vlc-plugin-bittorrent [riscv64] (hirsute-proposed) [2.12-2]
[00:12] -queuebot:#ubuntu-release- New binary: rust-ref-cast-impl [arm64] (hirsute-proposed/universe) [1.0.3-1] (no packageset)
[00:13] -queuebot:#ubuntu-release- New binary: rust-ref-cast-impl [armhf] (hirsute-proposed/universe) [1.0.3-1] (no packageset)
[00:13] -queuebot:#ubuntu-release- New binary: rust-rustc-std-workspace-std [armhf] (hirsute-proposed/universe) [1.0.1-1] (no packageset)
[00:14] -queuebot:#ubuntu-release- New: accepted rust-ref-cast-impl [arm64] (hirsute-proposed) [1.0.3-1]
[00:14] -queuebot:#ubuntu-release- New: accepted rust-rustc-std-workspace-std [armhf] (hirsute-proposed) [1.0.1-1]
[00:14] -queuebot:#ubuntu-release- New: accepted rust-ref-cast-impl [armhf] (hirsute-proposed) [1.0.3-1]
[00:16] -queuebot:#ubuntu-release- New binary: vlc-plugin-bittorrent [armhf] (hirsute-proposed/universe) [2.12-2] (no packageset)
[00:19] -queuebot:#ubuntu-release- New binary: vlc-plugin-bittorrent [arm64] (hirsute-proposed/universe) [2.12-2] (no packageset)
[00:23] -queuebot:#ubuntu-release- New binary: rust-globwalk [arm64] (hirsute-proposed/universe) [0.8.1-1] (no packageset)
[00:23] -queuebot:#ubuntu-release- New binary: rust-globwalk [armhf] (hirsute-proposed/universe) [0.8.1-1] (no packageset)
[01:05] <Eickmeyer[m]> I rebuilt ubuntustudio-meta and am going to need any builds for risc64 removed. Can anybody do that for me?
[02:37] <OldManWinter> Hello!  LP 1910744 was filed, thanks.
[02:38] -queuebot:#ubuntu-release- Unapproved: s390-tools (hirsute-proposed/main) [2.15.1-0ubuntu4 => 2.15.1-0ubuntu5] (core)
[05:18] -queuebot:#ubuntu-release- New binary: rust-docmatic [amd64] (hirsute-proposed/universe) [0.1.2-1] (no packageset)
[05:18] -queuebot:#ubuntu-release- New binary: rust-docmatic [ppc64el] (hirsute-proposed/universe) [0.1.2-1] (no packageset)
[05:20] -queuebot:#ubuntu-release- New binary: mkautodoc [amd64] (hirsute-proposed/universe) [0.1.0-1] (no packageset)
[05:20] -queuebot:#ubuntu-release- New binary: rust-docmatic [s390x] (hirsute-proposed/universe) [0.1.2-1] (no packageset)
[05:20] -queuebot:#ubuntu-release- New binary: pytest-datadir [amd64] (hirsute-proposed/universe) [1.3.1+ds-1] (no packageset)
[05:21] -queuebot:#ubuntu-release- New binary: trac [amd64] (hirsute-proposed/universe) [1.5.2+dfsg-1] (no packageset)
[05:21] -queuebot:#ubuntu-release- New binary: meep [s390x] (hirsute-proposed/universe) [1.17.0-2] (no packageset)
[05:23] -queuebot:#ubuntu-release- New binary: meep [amd64] (hirsute-proposed/universe) [1.17.0-2] (no packageset)
[05:25] -queuebot:#ubuntu-release- New binary: meep [ppc64el] (hirsute-proposed/universe) [1.17.0-2] (no packageset)
[05:33] -queuebot:#ubuntu-release- New binary: rust-docmatic [riscv64] (hirsute-proposed/universe) [0.1.2-1] (no packageset)
[05:42] -queuebot:#ubuntu-release- New binary: vast [amd64] (hirsute-proposed/universe) [2020.12.16-1] (no packageset)
[05:53] -queuebot:#ubuntu-release- New binary: rust-docmatic [arm64] (hirsute-proposed/universe) [0.1.2-1] (no packageset)
[05:53] -queuebot:#ubuntu-release- New binary: rust-docmatic [armhf] (hirsute-proposed/universe) [0.1.2-1] (no packageset)
[06:02] -queuebot:#ubuntu-release- New binary: meep [armhf] (hirsute-proposed/universe) [1.17.0-2] (no packageset)
[06:03] -queuebot:#ubuntu-release- New binary: meep [arm64] (hirsute-proposed/universe) [1.17.0-2] (no packageset)
[07:33] <tjaalton> vorlon: thanks!
[07:55] -queuebot:#ubuntu-release- New binary: meep [riscv64] (hirsute-proposed/universe) [1.17.0-2] (no packageset)
[08:23] -queuebot:#ubuntu-release- Unapproved: borgbackup (bionic-proposed/universe) [1.1.15-1~ubuntu<IP_ADDRESS> => 1.1.15-1~ubuntu<IP_ADDRESS>] (no packageset)
[08:24] <LocutusOfBorg> tjaalton, ^^ sorryyyyyyyyyyy damn ppa wrongly configured
[08:24] <LocutusOfBorg> I did lower from 12 to 11
[08:29] <tjaalton>  bah
[08:30] -queuebot:#ubuntu-release- Unapproved: accepted borgbackup [source] (bionic-proposed) [1.1.15-1~ubuntu<IP_ADDRESS>]
[08:31] <LocutusOfBorg> thanks
[09:07] -queuebot:#ubuntu-release- New binary: freedict-wikdict [amd64] (hirsute-proposed/universe) [2020.12.28-1] (no packageset)
[11:22] -queuebot:#ubuntu-release- New: accepted freedict-wikdict [amd64] (hirsute-proposed) [2020.12.28-1]
[11:22] -queuebot:#ubuntu-release- New: accepted meep [arm64] (hirsute-proposed) [1.17.0-2]
[11:22] -queuebot:#ubuntu-release- New: accepted meep [ppc64el] (hirsute-proposed) [1.17.0-2]
[11:22] -queuebot:#ubuntu-release- New: accepted meep [s390x] (hirsute-proposed) [1.17.0-2]
[11:22] -queuebot:#ubuntu-release- New: accepted trac [amd64] (hirsute-proposed) [1.5.2+dfsg-1]
[11:22] -queuebot:#ubuntu-release- New: accepted meep [amd64] (hirsute-proposed) [1.17.0-2]
[11:22] -queuebot:#ubuntu-release- New: accepted meep [riscv64] (hirsute-proposed) [1.17.0-2]
[11:22] -queuebot:#ubuntu-release- New: accepted vast [amd64] (hirsute-proposed) [2020.12.16-1]
[11:22] -queuebot:#ubuntu-release- New: accepted meep [armhf] (hirsute-proposed) [1.17.0-2]
[11:22] -queuebot:#ubuntu-release- New: accepted mkautodoc [amd64] (hirsute-proposed) [0.1.0-1]
[11:23] -queuebot:#ubuntu-release- New: accepted pytest-datadir [amd64] (hirsute-proposed) [1.3.1+ds-1]
[11:23] -queuebot:#ubuntu-release- New: accepted rust-docmatic [arm64] (hirsute-proposed) [0.1.2-1]
[11:23] -queuebot:#ubuntu-release- New: accepted rust-docmatic [ppc64el] (hirsute-proposed) [0.1.2-1]
[11:23] -queuebot:#ubuntu-release- New: accepted rust-docmatic [s390x] (hirsute-proposed) [0.1.2-1]
[11:23] -queuebot:#ubuntu-release- New: accepted rust-docmatic [amd64] (hirsute-proposed) [0.1.2-1]
[11:23] -queuebot:#ubuntu-release- New: accepted rust-docmatic [riscv64] (hirsute-proposed) [0.1.2-1]
[11:23] -queuebot:#ubuntu-release- New: accepted rust-docmatic [armhf] (hirsute-proposed) [0.1.2-1]
[11:23] -queuebot:#ubuntu-release- New: accepted rust-globwalk [arm64] (hirsute-proposed) [0.8.1-1]
[11:23] -queuebot:#ubuntu-release- New: accepted vlc-plugin-bittorrent [arm64] (hirsute-proposed) [2.12-2]
[11:23] -queuebot:#ubuntu-release- New: accepted rust-globwalk [armhf] (hirsute-proposed) [0.8.1-1]
[11:23] -queuebot:#ubuntu-release- New: accepted vlc-plugin-bittorrent [armhf] (hirsute-proposed) [2.12-2]
[13:17] -queuebot:#ubuntu-release- New binary: pytest-regressions [amd64] (hirsute-proposed/universe) [2.1.1+ds-1] (no packageset)
[18:35] -queuebot:#ubuntu-release- New binary: dart [ppc64el] (hirsute-proposed/universe) [6.9.5-3] (no packageset)
[18:43] -queuebot:#ubuntu-release- New binary: dart [amd64] (hirsute-proposed/universe) [6.9.5-3] (no packageset)
[18:56] -queuebot:#ubuntu-release- New: accepted dart [amd64] (hirsute-proposed) [6.9.5-3]
[18:56] -queuebot:#ubuntu-release- New: accepted pytest-regressions [amd64] (hirsute-proposed) [2.1.1+ds-1]
[18:56] -queuebot:#ubuntu-release- New: accepted dart [ppc64el] (hirsute-proposed) [6.9.5-3]
[23:44] -queuebot:#ubuntu-release- New binary: libcoro-twiggy-perl [amd64] (hirsute-proposed/universe) [0.03-1.1] (no packageset)


[14:26]  * cpaelzer is lighting the MIR campfire
[14:26] <cpaelzer> pre-ping sarnold didrocks slyon doko_ ddstreet jamespage
[14:30] <ddstreet> o/
[14:30] <cpaelzer> hi
[14:30] <cpaelzer> #startmeeting Weekly Main Inclusion Requests status
[14:30] <meetingology> Meeting started at 14:30:09 UTC.  The chair is cpaelzer.  Information about MeetBot at https://wiki.ubuntu.com/meetingology
[14:30] <meetingology> Available commands: action, commands, idea, info, link, nick
[14:30] <slyon> o/
[14:30] <cpaelzer> given that it is release week, we'd hope to not have any urgent MIR acticity
[14:30] <cpaelzer> but the one for next cycle might start :-)
[14:30] <cpaelzer> #topic Review of previous action items
[14:31] <cpaelzer> As promised I have started the unification of rules/templates on our wiki
[14:31] <cpaelzer> a first suggestion is available for your review at https://github.com/cpaelzer/ubuntu-mir/pull/2
[14:31] <cpaelzer> #topic current component mismatches
[14:31] <cpaelzer> #link https://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.svg
[14:31] <cpaelzer> #link https://people.canonical.com/~ubuntu-archive/component-mismatches.svg
[14:32] <didrocks> (hey)
[14:32] <cpaelzer> jamespage: with cherrypy3->python-cheroot and python-oslo.metrics not being ready they wont make it in 21.10 as it seems
[14:32] <cpaelzer> is that a problem?
[14:33] <cpaelzer> Not sure is jamespage is around to see this, as backup pinging coreycb
[14:34] <cpaelzer> we will go on with our agenda, but if there are answers to the above please chime in and let us knows
[14:34] <cpaelzer> the rest of the mismatches looks as-usual no new entries AFAICS
[14:34] <cpaelzer> #topic New MIRs
[14:34] <cpaelzer> #link https://bugs.launchpad.net/ubuntu/?field.searchtext=&orderby=-date_last_updated&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&assignee_option=none&field.assignee=&field.subscriber=ubuntu-mir
[14:34] <cpaelzer> There is one new entry
[14:34] <cpaelzer> https://bugs.launchpad.net/ubuntu/+source/vulkan-tools/+bug/1946359
[14:35] <cpaelzer> anyone having the cycles to work on that (I'm on PTO soon, then planning sprint; so not me this time :-/ )
[14:35] <coreycb> cpaelzer: we need oslo.metrics but we could probably back out to an old oslo.messaging as a last resort. the security team made it through one of the two packages I think.
[14:35] <slyon> I can take on that.
[14:35] <cpaelzer> thanks slyon
[14:36] <cpaelzer> slyon: assigned
[14:36] <cpaelzer> coreycb: yes .messaging is done
[14:36] <cpaelzer> coreycb: do you know if secruity aware that the deadline for this is essentially days/hours now?
[14:36] <cpaelzer> sarnold isn't here today
[14:36] <cpaelzer> I'd ask you coreycb and jamespage to get in touch with security Team to make sure this is resolved by Impish release
[14:37] <coreycb> cpaelzer: yes, I chatted with him last week - I don't think there was a guarantee
[14:37] <coreycb> cpaelzer: ok I'll touch base over there
[14:37] <cpaelzer> because even if you would "back out to an old oslo.messaging" that would still be uploads and migration - and we are in final freeze
[14:37] <cpaelzer> thank you coreycb
[14:37] <cpaelzer> this isn't anything the MIR team can help, but we can push you to help youself :-)
[14:38] <cpaelzer> #topic Incomplete bugs / questions
[14:38] <cpaelzer> #link https://bugs.launchpad.net/ubuntu/?field.searchtext=&orderby=-date_last_updated&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.subscriber=ubuntu-mir
[14:38] <cpaelzer> Two recent updates
[14:38] <cpaelzer> https://bugs.launchpad.net/ubuntu/+source/opensc/+bug/1892559 seems to be re-started but not yet for us to review
[14:39] <cpaelzer> And https://bugs.launchpad.net/ubuntu/+source/lua5.4/+bug/1909665 also might be 22.04 or later material (to switch to a newer lua verion some day)
[14:39] <cpaelzer> but it doesn't need MIR team attention so far
[14:39] <cpaelzer> #topic Any other business?
[14:39] <cpaelzer> nothing from me except asking again for review of the PR that updates the rules in the wiki
[14:39] <didrocks> yeah, will do :)
[14:40] <sarnold> good morning, sorry I'm late
[14:40] <slyon> I will have a look at your PR as well!
[14:40] <slyon> Nothing else from my side.
[14:40] <cpaelzer> hi sarnold
[14:41] <cpaelzer> np to be late, but please see the above question on https://bugs.launchpad.net/ubuntu/+source/python-prometheus-client/+bug/1943143
[14:41] <cpaelzer> slyon: AFAICS that needs to happen more or less "now" since the fallback by the OS team also would take some time
[14:41] <sarnold> cpaelzer: can you repaste the question?
[14:41] <cpaelzer> sarnold: sure
[14:41] <sarnold> (it'll be half an hour or something before the logbot gets to it)
[14:42] <cpaelzer> the package python-prometheus-client still awaits security review
[14:42] <cpaelzer> for the MIR in https://bugs.launchpad.net/ubuntu/+source/python-prometheus-client/+bug/1943143
[14:42] <cpaelzer> This is 21.10 material
[14:42] <cpaelzer> And release is in two days
[14:42] <cpaelzer> So the openstack team (jamespage / coreycb) will need to know asap if this will be reviewed (and be ok)
[14:43] <cpaelzer> or if they need to do last minute changes to fall back to an alternative
[14:43] <cpaelzer> I guess that summarizes the question
[14:44] <sarnold> cpaelzer: thanks; prometheus_client looks short enough that I can get through it asap...
[14:44] <sarnold> I suggest we continue under the assumption it'll be fine
[14:44] <cpaelzer> coreycb: ^^
[14:44] <cpaelzer> awesome
[14:45] <cpaelzer> if the two of you sarnold + coreycb (jamespage) could sort that out today it could then be promoted tonight/tomorrow
[14:45] <coreycb> sarnold: thanks for looking!
[14:45] <cpaelzer> ok, I guess that covers the "other topics"
[14:45] <cpaelzer> I'd close unless there is anything else ???
[14:45] <sarnold> nothing from me
[14:46] <slyon> thank you o/
[14:46] <didrocks> thanks cpaelzer
[14:46] <cpaelzer> Final FYI next week I'd be on PTO, if someone else could drive this then that would be great.
[14:46] <sarnold> nice, enjoy :)
[14:47] <cpaelzer> Or you can all let the archive reopening ruin -proposed and idle a week until things look reasonable :-)
[14:47] <cpaelzer> #endmeeting
[14:47] <meetingology> Meeting ended at 14:47:13 UTC.  Minutes at https://new.ubottu.com/meetingology/logs/ubuntu-meeting/2021/ubuntu-meeting.2021-10-12-14.30.moin.txt
[14:47] <sarnold> thanks cpaelzer, all :)
[14:47] <didrocks> yeah, I don’t think there is a need for a meeting next week
[14:47] <didrocks> other opinions?
[14:50] <cpaelzer> That is the one week I won't care since I'm off :-)
[18:57] <cyphermox> o/
[18:58] <sarnold> hey cyphermox :)
[18:58]  * vorlon waves
[18:59] <cyphermox> hey sarnold
[18:59] <cyphermox> I'm here, but actually currently doing maintenance in a DC, I might be slow to respond
[19:01] <vorlon> I may have failed to update the agenda after last meeting?  Checking chairs
[19:01] <rbasak> o/
[19:03] <vorlon> so sil2100 is primary chair, and he may be buried under the release; mdeslaur is backup but sent regrets
[19:04] <rbasak> I can chair
[19:04] <rbasak> #startmeeting Technical Board
[19:04] <meetingology> Meeting started at 19:04:53 UTC.  The chair is rbasak.  Information about MeetBot at https://wiki.ubuntu.com/meetingology
[19:04] <meetingology> Available commands: action, commands, idea, info, link, nick
[19:05] <rbasak> #topic Apologies
[19:05] <rbasak> #info mdeslaur sends his apologies
[19:05] <rbasak> #info sil2100 may be unavailable due to the imminent Ubuntu release
[19:05] <rbasak> #topic Action review
[19:05] <rbasak> ACTION: rbasak to communicate the TB's MATE resolution to the MATE flavour leads.
[19:06] <rbasak> I just did this, and Wimpy said to expect a response in a couple of weeks. Thanks Wimpy!
[19:06] <rbasak> ACTION: formal ratification of third party seeded snap security policy, depends on:
[19:06] <rbasak> 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.
[19:06] <vorlon> carry-over
[19:06] <rbasak> #action formal ratification of third party seeded snap security policy, depends on:
[19:06] <meetingology> ACTION: formal ratification of third party seeded snap security policy, depends on:
[19:06] <rbasak> #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.
[19:06] <meetingology> 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.
[19:06] <rbasak> #action vorlon to reply to seeded snap upload permissions question on list
[19:06] <meetingology> ACTION: vorlon to reply to seeded snap upload permissions question on list
[19:07] <vorlon> carry-over
[19:07] <rbasak> #action vorlon to reply to seeded snap upload permissions question on list
[19:07] <meetingology> ACTION: vorlon to reply to seeded snap upload permissions question on list
[19:07] <rbasak> FWIW, I'm not sure what that item is referring to exactly
[19:07] <rbasak> ACTION: sil2100 to start a draft summarizing the OEM archive portion of the meeting which xnox and TB will review, edit, and ratify before we move on to figuring out the next step
[19:08] <rbasak> I assume we will carry this as sil2100 isn't here.
[19:08] <rbasak> #action sil2100 to start a draft summarizing the OEM archive portion of the meeting which xnox and TB will review, edit, and ratify before we move on to figuring out the next step
[19:08] <meetingology> ACTION: sil2100 to start a draft summarizing the OEM archive portion of the meeting which xnox and TB will review, edit, and ratify before we move on to figuring out the next step
[19:08] <rbasak> ACTION: all TB members to "vote" or explain what they do not like of a proposal on https://pad.ubuntu.com/third-party-repository-requirements
[19:09] <rbasak> Does everyone consider their input on this complete?
[19:10] <vorlon> I see there's an ongoing discussion at the bottom of the document
[19:10] <vorlon> I've given feedback on everything up to that point
[19:10] <rbasak> I have an answer for the next related action item, so let's carry this I guess.
[19:11] <rbasak> #action all members to continue discussion at https://pad.ubuntu.com/third-party-repository-requirements
[19:11] <meetingology> ACTION: all members to continue discussion at https://pad.ubuntu.com/third-party-repository-requirements
[19:11] <rbasak> ACTION: rbasak to draft refined rules for the proposed "stability" requirement for third-party software repositories
[19:11] <sil2100> o/
[19:11] <rbasak> I just drafted this
[19:11] <rbasak> o/
[19:11] <rbasak> Let me paste it into the pad
[19:11] <sil2100> Sorry everyone, got distracted
[19:12]  * vorlon finds it, look for --BEGIN---
[19:13] <vorlon> rbasak: thanks.  I think we should take some time to digest this rather than trying to decide on it this meeting (at least, I need time to digest :)
[19:14] <rbasak> Sure.
[19:15] <rbasak> I think the next agenda item will suffice to track the general goal of sorting this out.
[19:15] <rbasak> #topic Erich Eickmeyer via the mailing list: DisplayCAL in the archive as a deb that pulls in a Flatpak, and its inclusion in Ubuntu Studio by default. See https://lists.ubuntu.com/archives/technical-board/2021-July/002562.html and https://pad.ubuntu.com/third-party-repository-requirements
[19:15] <rbasak> Any specific next steps here? Is everyone happy to continue digesting/feedbacking?
[19:17] <Eickmeyer> I don't want to crash the meeting, but can I say something about this (got a ping)?
[19:18] <rbasak> Sure, please do
[19:18] <Eickmeyer> Ok, well, considering the feedback I got from vorlon, I'm willing to drop this and have been working on a snap.
[19:18] <Eickmeyer> Unfortunately, that has been quite the struggle, so I'm going to be enlisting some help on this.
[19:19] <Eickmeyer> At the appropriate time, I hope to make it a seeded snap
[19:19] <sil2100> \o/
[19:20] <Eickmeyer> However, I agree that the technicality of being able to include a flatpak of *something* has merit, but I'm no longer pursuing it for this particular application.
[19:20] <rbasak> OK. Thank you for the update!
[19:20] <Eickmeyer> No problem. I hope that helps. :)
[19:20] <rbasak> Where do we want to go from here then?
[19:20] <sil2100> I think it's still good to work out an official policy for such cases
[19:21] <cyphermox> +1
[19:21] <rbasak> Should we archive the current discussion until/unless it's raised again by someone else with a similarly credible request? Or as sil2100 says, should we carry on anyway?
[19:21] <cyphermox> well, aren't we with the third party repo requirements pad?
[19:22] <vorlon> I think archiving it carries the risk of retread the next time it comes up :)
[19:22] <rbasak> Personally I'm in favour of solidifying this anyway, as we are continuing with seeded snaps which would I think be expected to comply with these generic requirements anyway
[19:22] <rbasak> OK, so I think we're agreed that we carry on?
[19:22] <sil2100> My apologies for not finishing my comments for that one, but I think we should be continuuing, especially that I feel it's 'close' to being all properly defined
[19:24] <rbasak> #agreed We will continue working on defining the third party repo requirements even though Eickmeyer has withdrawn his request for the DisplayCAL case, as we think it'd be useful to have anyway
[19:24] <meetingology> AGREED: We will continue working on defining the third party repo requirements even though Eickmeyer has withdrawn his request for the DisplayCAL case, as we think it'd be useful to have anyway
[19:25] <rbasak> So there remains an action item for everyone to continue working on the pad, so I'll leave that there, and I'll adjust the agenda item to make this request generic
[19:25] <sil2100> +1
[19:25] <rbasak> Anything else for this topic for now?
[19:25] <rbasak> #topic Scan the mailing list archive for anything we missed (standing item)
[19:26] <rbasak> #info No recent communication on the public mailing list
[19:26] <rbasak> However there was a private communication that needs a response I think, but should probably remain private for now.
[19:26] <rbasak> Is there somewhere private the TB can go to discuss this now? Or do we need to use private email or something?
[19:26] <vorlon> private email is pretty much it
[19:27] <rbasak> OK. I'll start that thread after the meeting.
[19:27] <rbasak> #topic Check up on community bugs (standing item)
[19:27] <rbasak> #info No open community bugs
[19:27] <rbasak> #topic Select a chair for the next meeting (next from https://launchpad.net/~techboard/+members)
[19:27] <sil2100> Me o/
[19:28] <sil2100> Since I was supposed to be chairing today, right?
[19:28] <rbasak> #info Next chair will be sil2100 with mdeslaur as backup
[19:28] <rbasak> Yup, makes sense.
[19:28] <rbasak> #endmeeting
[19:28] <meetingology> Meeting ended at 19:28:23 UTC.  Minutes at https://new.ubottu.com/meetingology/logs/ubuntu-meeting/2021/ubuntu-meeting.2021-10-12-19.04.moin.txt
[19:28] <vorlon> thanks, all!
[19:28] <sil2100> Thank you rbasak for chairing!
[19:28] <sil2100> And thanks for the meeting o/