/srv/irclogs.ubuntu.com/2008/07/25/#ubuntu-meeting.txt

=== |Aryn| is now known as aRyn
=== nhandler is now known as nhandler_AFK
=== asac_ is now known as asac
=== fdd-01 is now known as fdd
jussi01!test > me08:27
ubottujussi01, please see my private message08:27
=== nhandler_AFK is now known as nhandler
=== nhandler is now known as nhandler_AFK
=== RainCT_ is now known as RainCT
=== ember_ is now known as ember
=== RainCT is now known as RainCT_
=== bazhang is now known as tv7498
=== tv7498 is now known as bazhang
=== stdin_ is now known as stdin
=== nhandler_AFK is now known as nhandler
=== gnomefre1k is now known as gnomefreak
=== mc44_ is now known as mc44
=== Tweenaks is now known as Treenaks
=== ubottu changed the topic of #ubuntu-meeting to: Current meeting: MOTU | Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 28 Jul 14:00 UTC: Maintainer scripts | 31 Jul 14:00 UTC: Mentoring Reception | 31 Jul 16:00 UTC: Ubuntu Mobile | 02 Aug 13:00 UTC: Xubuntu Community | 03 Aug 18:00 UTC: Mozilla Team
sistpotyhi folks20:59
* persia waves21:00
sistpotyok, let's get started, shall we?21:01
persiaWho wants to chair today?21:02
cody-somervilleHi folks21:02
sistpotypersia: if noone volunteers, I'd go for it21:03
* cody-somerville voluntells sistpoty :)21:03
persiaOK.  Who does minutes?21:03
cody-somervilleI suppose I could21:03
sistpoty#startmeeting21:03
MootBotMeeting started at 15:06. The chair is sistpoty.21:03
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]21:03
persiaI'll do announcements then.21:03
sistpotyaction cody-somerville to do minutes21:04
sistpoty#action cody-somerville to do minutes21:04
sistpotyarg...21:04
sistpoty[action] cody-somerville to do minutes21:04
MootBotACTION received:  cody-somerville to do minutes21:04
sistpotyheh21:04
sistpoty[action] persia to do announcements21:04
MootBotACTION received:  persia to do announcements21:04
sistpotyso welcome everyone to the motu meeting :)21:04
sistpotylooking at the agenda, it's pretty much empty. so anyone with a point right now?21:05
norsetto.21:05
persiaNot that kind :)21:05
sistpotynorsetto: should I put the "." as an idea? :P21:05
* norsetto take the point back21:05
cody-somerville:]21:05
* cody-somerville raises his hand.21:06
sistpotyok, how about the motu key teams thingy? seems like the discussion has stalled21:06
* cody-somerville lowers his hand.21:06
sistpotyanyone a good idea how to unstall it?21:06
sistpotyor how to proceed?21:06
cody-somervillesistpoty, I think we need to have a concrete proposal.21:07
cody-somervilleAnd then tell everyone "vote on it or be unhappy forever more"21:07
sistpoty*nod*21:07
sistpotycody-somerville: would you like to take this into your hands?21:07
cody-somervilleWell, not exactly. I think I've really carried this conversation thus far and I don't want to my idea of how things to be to be adopted just because I'm the only one interested enough21:08
cody-somerville*to have21:08
sistpotyok, "." taken ;)21:09
sistpotyanyone else who'd like to volunteer?21:09
persiacody-somerville: It doesn't have to be your idea.21:09
persiaWe just need a proposal to move forward.  Currently, we don't have anything on which to debate.21:09
cody-somervilleI think we do21:09
cody-somervilleI divided it up,21:09
sistpotypersia: if we wouldn't, we'd have consensus already and could move on, couldn't we?`21:09
cody-somervilleOne person voiced that they didn't feel persia's idea would work for us21:10
cody-somervillebut no one else stepped up to say anything more21:10
persiaRight.  I phrased that badly.21:11
sistpotywell, I also think that this idea doesn't work too well (for various reasons), but iirc noone really was in favor of that idea... correct?21:11
persiaThere are issues outstanding.  There is contention.  I just have mostly seen different viewpoints, rather than anything on which we could agree or disagree.21:11
sistpotywell, we could e.g. come to a vote about the voting system used21:12
persiaCertainly.21:12
sistpoty(though I still don't know about the subtle differences to be honest *g*)21:12
persiaMy feeling was more that a change in voting system wouldn't address the perceived issue: specifically that there are questions about the teams.21:12
norsettoseems to me that the voting system should be the least of our worries21:13
sistpotypersia: can you elaborate on these?21:13
sistpotynorsetto: but iirc it got the most attention ;)21:13
norsettosistpoty: perhpas because people feel more confortable to talk about "technical"issues instead of "political" ones :-)21:13
persiasistpoty: My impression was that there was dissatisfaction with the composition and activity of the teams.21:14
sistpotypersia: hm... I seem to have failed to see this, any hints why you come to this conclusion?21:14
sistpotyor let's better phrase, anything in particular people are worried about?21:15
sistpotyhey LaserJock21:15
LaserJockhi!21:16
LaserJockis there a MOTU Meeting?21:16
NCommanderhola Laney21:16
NCommanderer LaserJock21:16
nhandlerYes LaserJock21:16
persiasistpoty: That was the impression I had from the initial mails on the subject.  Since then there's been discussion of voting methods.  If it's only about voting methods, maybe I misunderstood.21:16
sistpotyLaserJock: yep, you came right into it, we're just discussing motu key teams membership policy (and how to unstall it)21:16
sistpotypersia: imo there was dissatisfaction that there was no clear policy, but I may be wrong (and biased due to being on a key team as well)21:17
LaserJocksistpoty: ah thanks, I've been thinking a tad about that21:17
sistpotyLaserJock: maybe you have a good idea how to unstall the discussion and how to proceed?21:17
LaserJocksistpoty: sure21:17
LaserJock;-)21:17
sistpotythen go ahead ;)21:18
NCommandersistpoty, what stalled the discussion in the first place?21:18
LaserJockdon't vote unless you need to, communicate as often as possible, and favor working teams over beuracratically-laden hirearchies21:19
sistpotyNCommander: not too sure, I'd say that noone really felt responsible to lead the discussion into reaching a consensus, but YMMV21:19
NCommandersistpoty, well, what specifically is the issue then? (I'm sorry for arriving late)21:19
sistpotyNCommander: membership policy in motu key teams (motu-sru, motu-release)... (/me looks for the initial thread)21:20
LaserJockI think the voting method discussion, while interesting and useful, is really distracting from the intial goal21:20
NCommanderI assume this was brought up due to the fact we just lost two motu-sru's?21:20
sistpotyNCommander: yep... it started with this: https://lists.ubuntu.com/archives/ubuntu-motu/2008-May/003919.html21:20
NCommanderWell, I dunno what the existing policy is, but I'd recommend voting with just a signed email to a publically available list21:21
sistpotyLaserJock: *nod*21:21
NCommanderWhat was decided thus far?21:22
sistpotywell, as written prior, we imho need someone to take response for the discussion and care to reach the initial goal... however would anyone volunteer?21:22
NCommanderOk21:22
* NCommander steps up21:22
NCommanderLets simply go right down the list, and start with motu-sru21:23
NCommanderBeyond being an MOTU, are there any specific requirements you MUST have to hold this position?21:23
LaserJockone of the key sticking points so far has been whether team membership requires a MOTU-wide refurendum or not21:23
LaserJocki.e. can we just take people who offer or do we need to vote every time a member is added21:23
NCommanderI think it can be take people who offer UNLESS there is a reason to cap the number of available motu-sru seats21:24
NCommanderAny arguements for or against?21:24
sistpotyNCommander: cody-somerville posted a pretty good summary of the discussion on ubuntu-motu, but I can't find the link right now21:24
=== RoAk is now known as RoAkSoAx
LaserJockNCommander: there are good arguments for both :-)21:24
persiaWell, when TB asked for the creation of MOTU SRU, it was intended to be a core group that had a high level of technical expertise for reviewing the impact of patches.21:24
NCommanderIf its already been discussed, maybe its time for a vote.21:24
LaserJockNCommander: is a vote needed?21:25
NCommanderOn deciding if motu-sru should be open to all, or capped to specific number that you have to be elected to21:25
sistpotyalso the question is what exactly to vote upon? voting policy is one point that comes to my mind21:25
persiasistpoty: "voting policy" meaning to take a vote on policy, or to policy on how votes are taken?21:26
NCommandersistpoty, do I dare ask the current voting policy?21:26
sistpotypersia: what voting system should be used21:26
LaserJockdo we need a vote on how to take a vote on voting on policy? :-)21:26
NCommanderrofl21:26
sistpotyNCommander: there is no current policy, that's what started it all21:26
NCommanderMay I purpose then a voting system which is simple, clear, and accountable?21:26
persiaLaserJock: If we are to adopt any given system, it only seems appropriate to select that system using that system as demonstration of how well the system works.21:27
sistpotyLaserJock: what other points do you see worth to discuss, that have been raised on the mailing list already?21:27
* NCommander personally would recommend setting up devotee, and using MOTU/core-dev key rings for votes21:27
sistpotypersia: argh... you create bootstrapping problems :P21:27
LaserJockwell, I personally would like to back the discussion up21:27
persiasistpoty: Well, perhaps, but then I've never been a fan of voting.21:27
* NCommander nominates the Debian devotee system21:27
LaserJockI think perhaps the issues are more fundamental and we're gonna get stalled each time21:28
NCommanderLaserJock, well, then someone needs to step up, and decide the matter21:28
LaserJockI'm fairly convinced that we should only be voting in rare cases21:28
NCommanderI agree with LaserJock on this one21:28
NCommanderI figure though if we keep getting stalled, then forcing a vote to get things moving probably the best option21:29
LaserJock*how* we vote is not so much the issue for me as *when* we vote21:29
cody-somervilleThat adds in a whole heck load of complexity.21:29
persiaLaserJock: Can you describe "the issue"?  I'm also not feeling that the manner in which we vote is the core problem, but I'm not sure how to articluate it.21:29
NCommanderLaserJock, when someone calls, and its seconded21:29
LaserJockwell, it goes back to what I said earlier21:29
sistpotyNCommander: ah, found the summary FYI: https://lists.ubuntu.com/archives/ubuntu-motu/2008-July/004227.html21:30
LaserJockthe question seems to me to be how we hold teams to be validated21:30
LaserJockdo we *have* to vote on members for them to be valid?21:31
NCommandershit, someone just totalled my car21:31
NCommanderBbl21:31
LaserJockI think in the past ScottK has indicated that he believes they do21:31
cody-somervilleI think voting is the simplest way to do that21:32
LaserJockso it seems to me that we need to figure out more clearly what our view of teams really is21:32
sistpotyLaserJock: given the last motu-sru probs, I think the focus should be to have working teams in the first place (but OTOH I got flamed quite hard for stating that voting is not necessary back then *g*)21:32
persiaI think the simplest way is to just use the any-MOTU-can-veto model.21:32
LaserJockpersia: I think that kind of hits at the heart of the matter21:33
geserpersons for key positions (like ~motu-sru or ~motu-release) should somehow be "confirmed" by MOTU21:33
* cody-somerville nods with geser.21:33
cody-somervilleWe have a hard enough time getting people to voice issues with approving new motus21:33
LaserJockdo we say "you can only do what the MOTU tell you" or "you just can't do what the MOTU tell you you cant" :-)21:33
sistpotypersia: sounds like a plan... maybe combined with: "if veto then vote"21:33
cody-somervilleHow are we going to get people to "veto"21:33
LaserJockcody-somerville: "if there aren't any objections within 2 days I'm moving forward"21:34
LaserJockcody-somerville: if somebody has a problem they'll rais it21:34
cody-somervilleLaserJock, but people won't do it21:34
LaserJockif they care they will21:34
persiasistpoty: Unless there's strong discussion to override a veto, or no other candidate, I'd rather not have someone voted who would have been rejected by any-MOTU-can-veto.21:34
cody-somervilleand then we'll have silently grudging21:34
cody-somervilleLaserJock, no, they won't21:34
cody-somervilleWe see that already21:34
LaserJockcody-somerville: why not?21:34
cody-somervilleLaserJock, Because people don't like to cause drama or speak their mind21:34
persiaMaybe that's the problem.  Why don't people complain in public?21:34
cody-somervillepeople don't complain like they used to21:35
geserif there is no veto does that mean that everybody is happy with the decision or just that nobody cared?21:35
cody-somervillewe can't trust people to voice their real opinion anymore21:35
cody-somervillegeser, the later21:35
LaserJockcody-somerville: probably because they feel like they'll just be out voted21:35
LaserJock:-)21:35
cody-somerville*latter21:35
persiageser: I'd like to believe that everybody is happy.  If nobody cares, the voting system really doesn't matter.21:35
cody-somervilleLaserJock, we don't use the voting model now21:35
LaserJockcody-somerville: yes we do21:35
LaserJockfor quite a few things21:36
LaserJockbut it should be even more accentuated if a veto actually meant something21:36
sistpotygeser: either way, we need functional teams21:36
persiaLet's focus on functional teams.21:36
LaserJock+121:36
persiaWithout that, the rest doesn't matter.21:36
* cody-somerville has to run.21:36
persiaWhat do we need for functional teams?21:36
norsettopersia: I think the possibility to remove people that do not perform is essential21:37
cody-somervilleBefore I go, I'd like to note that none of the times these meetings occur are good for me.21:37
* cody-somerville waves.21:37
persianorsetto: We have the mechanism to hear complaints now.  Could we just use that?21:37
sistpotywell, speaking as a member of motu-release, I guess we need a policy to confirm (or reject) current members... currently we have an unclear status, which is hindering to move on imho21:37
sistpotycya cody-somerville21:38
norsettopersia: we could, it will be a good step in the right direction anyway21:38
gesercody-somerville: what meeting times do you prefer?21:38
cody-somervillegeser, an hour later would be good21:38
* cody-somerville thinks this topic will be a good UDS session :P21:38
persiacody-somerville: That's December though :(21:39
sistpotynorsetto: I think it's hard to find out if s.o. doesn't perform... or at least takes some guts (the motu-release post complaining about team colleagues wasn't one I did from the bottom of my heart)21:39
* norsetto notes we never discuss MOTU stuff at UDS21:39
cody-somervillenorsetto, we did quite a bit at the last one21:39
norsettocody-somerville: off doors21:39
geserpersia: I prefer to know when nobody cares instead of assuming everybody is happy21:39
persiaLet's defer MOTU stuff at UDS for now: we can organise some sessions later, but it's well off topic for team issues.21:40
LaserJockok, so can we look more at fundamentals?21:40
sistpotyLaserJock: +21:40
sistpoty121:40
LaserJockthe way I look at it21:40
cody-somervilleLaserJock, It seems to me we're always going back to "fundamental"? Why aren't we ever clearing that up?21:40
LaserJockif people are focused on doing the work of the team21:40
persiageser: I can understand that.  On the other hand, I've not seen any indication of anything else for a while, and would rather focus on working teams than everyone.21:40
LaserJockthen we shouldn't get in the way21:40
LaserJockisn't it pretty much a fundamental MOTU philosophy to let people do as they please as long as they aren't violating some policy?21:41
LaserJockso if a person becomes keenly interested in SRUs21:41
persiaWell, there's also the idea that we try to respect others goals and not interfere, but basically.21:41
LaserJockunless there is some obvious objection why should we get in their way?21:41
* cody-somerville thinks maybe we need a fundamental MOTU philosophy wiki page or something.21:42
LaserJockif it's on a wiki page I'd venture to say it's no long fundamental ;-)21:42
persiaTB has asked for a team of 5-7 members, so we ought limit the size to around that much.  As long as we don't have too many interested parties, we ought be fine.21:42
LaserJockor rather "if it  *has* to be on a wiki page"21:42
cody-somervilleLaserJock, or maybe the barrier to MOTU has become too low21:43
LaserJockhmm, not sure on that one21:43
LaserJockagain, if somebody I didn't think should be in MOTU SRU and I could back it up, I think I should be able to veto21:43
persiacody-somerville: There are others who complain the barrier is higher than it has ever been.21:44
LaserJockto me, the question with the leadership teams is not primarily about barriers, but about interests and activities21:44
cody-somervilleIMHO, I think any MOTU should be qualified to fill the roles of those teams21:45
LaserJockwe've had several "leadership teams" composed of very skilled people but the team basically didn't do anything21:45
cody-somervilleAnd it is just a matter of selecting the highest preferred subset21:45
persiacody-somerville: TB has asked for MOTU to organise those best at those tasks to perform review.21:45
sistpotypersia: just OOI, when did TB do all that?21:45
* cody-somerville nods.21:46
sistpoty(as in any links to logs/mails/discussions)? I recall there was a topic set once, but not the outcome21:46
LaserJockI just don't think all the voting and "selecting" get's us much of anywhere21:46
persiasistpoty: For MOTU SRU, it was around the end of gutsy / beginning of hardy I think.21:46
persiaFor MOTU Release, it was much earlier (I forget when).  Actually, MOTU Release may not be a TB mandate, but MOTU SRU was created specifically after a request by pitti to the TB.21:47
sistpotyah, good to know21:47
* persia doesn't have a working mouse right now, and hopes someone else can hunt the logs21:47
sistpotyok, we've discussed this for quite a while now, let's try to come to some conclusions, shall we?21:49
persiaFor MOTU Release (then MOTU FFe or something) it might have been for Dapper?21:49
* NCommander is back21:50
cody-somervilleI'm in favour of confirmation via vote.21:50
LaserJock1 of my conclusions is to unstall we need to get away from the voting method discussion21:50
sistpotypersia: not too sure, I recall that it was there for a very long time, but not when it was introduced ;)21:50
* persia seconds LaserJock21:50
* sistpoty agrees21:50
cody-somervilleI'm in favour of confirmation via vote.... and I veto anyone who opposes :P21:51
LaserJocklol21:51
persiaI really like the idea of accepting interested parties unless 1) there is disagreement or 2) the team is overfull (in which case we vote for who is the best)21:51
LaserJockI'm in favor of a simple guideline about how people can object to tings21:51
LaserJock*things21:51
LaserJock+1 to persia21:52
sistpotyok, let me try to put this into actions... how about:21:52
NCommander+1 persia21:52
cody-somervilleLets just vote and there is no question about if there is disagrement or not21:52
cody-somervilleThe STV requires a quota to be met21:52
LaserJockcody-somerville: voting sucks, lets not do it unless we have to :-)21:52
cody-somervilleLaserJock, We have to in this case21:53
sistpoty1st: "agreed" that we should get away from the voting discussion (to focus on the real issue instead)21:53
cody-somervilleWe do it for CC and TB21:53
LaserJockcody-somerville: why?21:53
cody-somervilleLaserJock, why not? :P21:53
LaserJockno, you are affirming we have to, it is your case to make21:53
cody-somervilleIsn't the proof of burden on the opposition?21:53
LaserJockyes21:53
LaserJockand you are opposing doing nothing (the default)21:54
cody-somerville*burden of proof21:54
cody-somervilleWe already vote21:54
cody-somervilleso not voting is the opposition, no?21:54
sistpoty2nd: "action" persia to write proposal to motu list that interested parties should get accepted until disagreement or team is overfull21:54
LaserJockcody-somerville: no, we have no system currently21:54
LaserJockso I don't think voting is the default21:54
persiasistpoty: accepted21:54
persiacody-somerville: CC and TB and MC must be voted by their creation.  The other teams don't currently have policy.21:55
LaserJockdo we have a "how to object" document anywhere?21:55
sistpoty3rd: "action" LaserJock and cody-somerville to continue the discussion on the motu-list? *g*21:55
LaserJockperhaps that might be an interesting thing to have written up, in general21:55
persiaLaserJock: We only have the document of how to complain about someone repeatedly behaving inappropriately.  Something with guidance for lighter cases would be good.21:55
cody-somervilleI don't like this system.21:56
persiacody-somerville: What don't you like about it?21:56
sistpoty(where 3rd would unstall the discussion I hope)21:56
cody-somervilleI rather speak up to show support then speak up to show opposition.21:56
gesercody-somerville: you can object :)21:56
cody-somervilleI rather speak up to show support then speak up to show opposition.21:56
LaserJockcody-somerville: well, that becomes kinda sticky21:56
persiacody-somerville: If you only say things in support, shall we assume you object the rest of the time?21:56
persiaIs this true for others?  Need we get all of us to commit to each action?21:57
sistpotyand maybe 4th: "action" that geser will play shephard and make sure the discussion stays on pace21:57
* persia notes that no election in Ubuntu since Dapper has ever included a majority of those eligible voting21:57
sistpotyno, seriously everyone... the discussion right here is taking almost an hour, with different opinions voiced while nothing happened on the ml for quite some time.21:58
sistpotythat makes me a little bit sad actually21:58
LaserJockI think it's fundamentally more in line with Ubuntu/MOTU philosophy to let people have freedom to do what they want as long as there aren't objections21:58
sistpotyseems like s.th. is going fundamentally wrong outside of motu-key teams21:58
norsettopersia: thats a bit of an understatement21:59
LaserJockas oppposed to only letting people to do what is explicitly allowed21:59
cody-somervilleOkay, lets get rid of -sru and -release21:59
LaserJockcody-somerville: why?21:59
cody-somervillePeople obviously don't care enough to have it.22:00
gesersistpoty: the problem is how to get an opinion from the majority of MOTU22:00
cody-somervilleLets just go pure-motu style and let everyone be in -sru and -release22:00
persiacody-somerville: We at least can't get rid of -sru.  It's mandated by TB.  I suspect the same is true of -release, but don't remember precisely.22:00
sistpotygeser: kind of, I'd even say the problem is that everyone wants to state her/his opinion but doesn't care too much in the end22:00
cody-somervillepersia, I22:00
* NCommander feels that has bad idea written all over it22:00
LaserJockcody-somerville: that seems a bit like a pendulum swing :-)22:00
NCommanderIt's a bootstrapping problem because this is the first serious issue that can't be cleaner resolved22:00
persiasistpoty: That seems like a good summation.  Any ideas as to how to address it?22:01
NCommanderpersia, I think we need to boil everything down to the basic choices, and then open voting up to every MOTU22:01
sistpotypersia: actually my action points weren't all kidding... if s.o. takes over the issue on the mailing list and really cares that an outcome will be reached, I think we'll come to a conclusion22:02
sistpotyit's just a bit to force people into stating their opinions, take on what there are different opinions and have some means (that's where a poll served quite well in the past) about these last bit of differences22:03
persiasistpoty: I think you're right, and given the time the other issue can be for another meeting.  I still think both the key teams issue and the who cares issue are worth addressing somehow.22:03
sistpotyok, so who'd like to take over final responsibility over the motu-key team issue?`22:04
LaserJockwell, is there really a separate issue?22:04
LaserJockI personally don't see one22:04
NCommandersistpoty, what does that entail specifically?22:04
sistpotyto make it more rewarding, I'd say he/she should get all the duties of a shephard and is able to call for a vote if needed22:04
sistpotyNCommander: it boils down to reading the summary from cody-somerville, see the follow up posts, look at what was discussed today, summarize it again call for other opinions and as soon as no objection or no agreemant can be reached to take action22:05
sistpotyso not too much of an issue :P22:05
* NCommander steps forward if a non-MOTU is allowed to do so22:06
LaserJockI'd say we can call the motu-key team thing as a non-issue22:06
persiaLaserJock: I disagree.22:06
LaserJockand move on to better things22:06
persiaThere seems sufficient interest in discussion that we ought resolve it.22:06
LaserJockpersia: why? we have current teams, we don't need new members?22:06
persiaLaserJock: Because it's an open item that should be closed.22:06
LaserJockthe fundamental issue makes sense22:06
sistpotyNCommander: sure, maybe that would even help, since you're outside of motu and hence will server as someone unbiased?22:06
LaserJockbut I don't see anything specific to motu-key teams22:07
persiaLaserJock: Your recommendation which I'll write up based on interested parties.22:07
LaserJockso I think we're going around talking about the wrong thigns22:07
geserLaserJock: do you want to have this discussion when new members are needed again? I don't believe we have the time then to discuss first how new members are selected.22:07
* NCommander pulls out a giant gong22:07
* persia agrees with geser22:07
LaserJockgeser: that's not what I'm saying!22:08
LaserJockI'm saying that if we take care of the root problem, then the key-team issue fixes itself22:08
LaserJockif we can figure out how to deal with decisions then the key-team thing is a non-issue22:08
sistpotyLaserJock: actually, what geser wrote is why I bring it up now: the motu-release discussion I started stalled, and I'd like to have a clear policy for membership rather sooner than later22:08
LaserJocksure22:08
persiaLaserJock: Let's not stop working on this just because there are other things as well.22:09
geserLaserJock: then I misunderstood you22:09
LaserJockbut key-teams is *not* the problem22:09
LaserJockour inability to make decisions *is* the problem22:09
persiaLaserJock: Even if just a symptom, having some guidelines will reduce confusion in the future.22:09
sistpotyLaserJock: that's why I'm forcing you to come to s.th. right now... timer ticking :P22:09
LaserJockpersia: I'm just worried about making decisions too quickly about regarding key-teams that we have to redo later22:10
LaserJockbut whatever, if we can come up with something soon I'm all for it22:10
LaserJockI'll take something over nothing ;-)22:10
persiaLaserJock: While I see your point, I also believe that taking a decision on this will be a step towards taking other decisions.22:10
sistpotyLaserJock: how about you write your conclusions to the motu mailing list (remember, motu-meeting doesn't make decisions any longer, otherwise I might have called for a vote already :P)22:10
sistpoty(LaserJock: and I'm quite happy to follow up if you do ;))22:11
* persia misses the old efficient process22:11
NCommandersistpoty, is there a specific reason we can't simply have voting in the meeting?22:11
* LaserJock misses the older more efficient process ;-)22:11
sistpotyheh, persia, seems like the old process did include votes :P22:11
sistpotyNCommander: we're trying out the new process atm.22:12
LaserJockok, so let's wrap up with action points22:12
* NCommander comes back in a week22:12
sistpotyok, now I forgot my old points... let's start with22:12
persiasistpoty: Yes, but of the quick uncomplicated sort :)22:12
LaserJockNCommander: are you going to shepard our key-teams discussion?22:12
sistpoty[action]22:12
MootBotACTION received:22:13
NCommanderI'll do it22:13
sistpotyheh22:13
sistpotynot that22:13
NCommanderAre we simply going to vote here on IRC< or are we going to do something formal?22:13
persiaNCommander: Neither.22:13
geseris there a wiki page with current policies/guidelines? I never know what's current22:13
sistpoty"action" eveveryone to state her/his opinion again on the mailing list22:13
persiageser: ScottK was going to update MOTU Meetings, but hasn't yet.22:13
sistpoty"action" NCommander to play shephard with the motu-key teams discussion and makes sure it reaches a conclusion22:14
NCommander"accept" I take this responsibility22:14
sistpotyanything else or any objections?22:14
sistpoty322:14
sistpoty222:14
LaserJockwait22:14
sistpoty122:14
sistpotyhrmpf *g*22:15
LaserJockwasn't persia going to do something?22:15
sistpotypersia?22:15
sistpotyLaserJock: but any objections to the other points from you?22:15
sistpoty(so we could at least agree on a subset already *g*)22:15
persiaI was going to write up the mail to propose accepting volunteers unless there was an objection or it would push the team oversize.  In the former case, we seek other volunteers.  In the latter case, we vote.22:15
LaserJocksistpoty: no, no objections from me22:16
sistpoty:)22:16
sistpoty[action] eveveryone to state her/his opinion again on the mailing list22:16
MootBotACTION received:  eveveryone to state her/his opinion again on the mailing list22:16
sistpoty[action] NCommander to play shephard with the motu-key teams discussion and makes sure it reaches a conclusion22:16
MootBotACTION received:  NCommander to play shephard with the motu-key teams discussion and makes sure it reaches a conclusion22:16
sistpoty[action] persia to write up the mail to propose accepting volunteers unless there was an objection or it would push the team oversize22:17
MootBotACTION received:  persia to write up the mail to propose accepting volunteers unless there was an objection or it would push the team oversize22:17
sistpotywoohoo!22:17
sistpotyso I guess we can move on now?22:17
* NCommander uses this opporunity to make sure I'm subscribed to ubuntu-motu22:18
sistpotyok, anyone else got a point? if not, I'd like to raise another one, but this time hope it won't be that long22:18
LaserJock:-)22:18
sistpotyok, then I just go ahead: ubuntu-universe-sponsors queue has grown again, today it was 118 bugs22:19
sistpotyplease everybody go sponsoring :)22:19
sistpotyanyone got some details from the REVU front?22:19
sistpotyor any other tasks we also should be pursuing right now?22:20
sistpotydo we have the critical debian bugs script running atm?22:20
NCommanderI've got one22:20
sistpotyNCommander: then go ahead22:21
NCommanderA reminder about freeze policy; there was an issue with evince breaking freeze and then indirectly breaking xubuntu's livecd build22:21
sistpotyNCommander: freeze doesn't apply for universe, or let's rather say most parts of universe22:22
LaserJockNCommander: that generally doesn't affect Universe though22:22
persiasistpoty: most parts22:22
NCommanderwell, if I just didn't stick my foot in my mouth22:22
* NCommander runs away22:22
LaserJockNCommander: np22:22
sistpotyheh22:22
NCommanderstill, its worth a reminder since some core-devs are here22:22
LaserJockI could just mention that the Ubuntu QA team is off to a pretty good start22:22
sistpotyNCommander: /me hides *g*22:22
persiaNCommander: The upload didn't break the build: something else did a couple days previously (and silently).  The upload that broke it was outside the freeze period.22:22
gesersistpoty: NCommander doesn't get far with a broken car :)22:23
LaserJockand hopefully some of that work will definately be helping MOTU22:23
sistpotyheh22:23
* NCommander drops his broken car on geser 22:23
NCommanderdon't get me started on my broken car22:23
NCommanderor else you'll be victim to drive by insults22:23
LaserJockDktrKranz has been working on a transition tracker22:23
sistpotyLaserJock: does qa also take over running e.g. the rcbugs script (or later running archive rebuilds/piuparts test), or can you talk about plans?22:23
sistpotyLaserJock: cool22:24
LaserJockwell, not sure about "take over"22:24
LaserJockbut we're working on trying to get more unified/helpful scripts22:24
LaserJockwgrant has been awesome enough to put some of his ubuntuwire code in our bzr22:25
LaserJockwe're collecting good QA code22:25
LaserJockand people ;-)22:25
LaserJockso one thing would be to give the rcbugs data a bit of a face lift22:25
sistpotyah, and I can see right now, that rcbugs is working atm :)22:26
LaserJockand promote it more22:26
LaserJockalso some work on rcbugs <-> LP interaction may be in the works22:26
NCommanderLaserJock, I've done some work in getting data out of LP, I'd be glad to share what I learned22:26
sistpotythat's great new altogether :)22:27
* NCommander actually has a second bit of news22:27
sistpotythen shoot ahead, NCommander22:27
NCommanderREVU is currently in the process of having updates written, and pending the will of the revu-hackers, hopefully hit trunk somewhat soon. There is a blueprint against REVU (revu2) which lists purposed features.22:28
NCommanderCurrently on the list is single signon with LP (already coded), PPA import, apt-get'ble source archives, and perpahs as far as a buildd network22:28
NCommanderIf you have a feature suggestion, nows the time :-)22:29
sistpotyoh, just to confirm, I haven't seen so many updates to revu for quite a while that NCommander did this week... and I still hope that RainCT will review and merge them all *g*22:29
NCommandersistpoty, he deferred that to you and siretart22:29
* RainCT hides :P22:29
sistpotyhrmpf... I haven't read revu code since ages *g*22:30
LaserJockwell, perhaps I'm getting into deep water again22:30
RainCTsistpoty: but you still know it better than me ;)22:30
LaserJockbut could the whole thing be a frontend to PPA?22:30
NCommanderIf anyone here feels like skinning things, please address the "REVU is ugly as hell" bug that I filed ;-)22:30
sistpotyRainCT: that's a rumor22:30
=== ubottu changed the topic of #ubuntu-meeting to: Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 28 Jul 14:00 UTC: Maintainer scripts | 31 Jul 14:00 UTC: Mentoring Reception | 31 Jul 16:00 UTC: Ubuntu Mobile | 02 Aug 13:00 UTC: Xubuntu Community | 03 Aug 18:00 UTC: Mozilla Team | 05 Aug 22:00 UTC: Community Council
LaserJockseems like disk space is often an issue, and iff you want apt-get'ble source archives, and a buildd network ...22:30
NCommanderLaserJock, we looked at it, but Soyuz doesn't give the necessary control, so rolling our own infrastructure is easier22:30
LaserJockwhat kind of control do you need?22:30
NCommanderWell, apt-get source archives are easily22:31
LaserJockbandwidth and disk space isn't22:31
NCommanderIts just generating valid source packages with a version number that isn't going to break things to high heaven22:31
NCommanderMaybe its time we get a REVU mirror :-)22:31
sistpotyLaserJock, NCommander: actually disk space is an issue (bandwith not too much)... as we've got only 72Gb raid (and half of it is used atm by current data)22:32
NCommandersistpoty, ouch22:32
sistpotyNCommander: well, these are old scsi disks for sun, which aren't needed anywhere else in the university, so we could grab them *g*22:32
NCommandersistpoty, probably time to find mirrors, or run a Donate-Hardware drive22:32
LaserJockwhy do we need any more checks than what Soyuz does?22:32
LaserJockif it's good enough for a PPA shouldn't it be good enough for REVU?22:32
NCommanderLaserJock, hence the PPA importer, however, PPAs don't build on all architectures, and they have other limitations w.r.t to superseeding and versioning22:33
* RainCT agrees with LaserJock as in that we shouldn't need buildds for revu22:33
* NCommander has heard arguements for and against22:33
persiaWhat was the argument for?22:34
* persia has never heard a good one22:34
LaserJockpersia: for PPAs or for having REVU do it all?22:34
sistpotywell, if s.o. volunteers to write the code and maybe even has some server to run such a buildd on, I'd be the least to object *g*22:34
NCommandersistpoty, once we have an apt-get source repo going, getting buildds going is pretty trival22:34
persiaLaserJock: For autobuilding REVU submissions.22:35
NCommandersistpoty, care to merge the openid code ;-)22:35
RainCTNCommander: btw, how far did you get with the e-mail verification?22:36
LaserJockpersia: #1 for me is  because it tells you whether it even builds22:36
sistpotypersia: to run lintian on the .debs and to check if it builds in the first place?22:36
NCommanderRainCT, you need to login with the username and password, and I folded lostpw.py into merge_accounts.py22:36
RainCTNCommander: and for people who don't have an old account or who get a new e-mail address?22:36
NCommanderRainCT, not yet, but until we actually DO something with email addresses, I don't really see it as a priority22:37
persiaWell, the submitter should have done both those things.  I'd rather discover the problem and instruct the submitter on best practices before upload than have an automated build that might build the expectation that an uploader shouldn't check locally.22:37
sistpotyerm... maybe we should continue the discussion about revu-development in #ubuntuwire?22:37
persiaHeh.22:37
sistpoty(we're still in a motu-meeting, mind you *g*)22:37
NCommander(having the ability to have comments go to personal emails will go in later)22:37
persiaMaybe just announce the next meeting time and end the meeting?22:37
NCommanderwoo, I completely derailed #u-meeting!22:37
sistpotypersia: that's what I wanted to propose right now... ;)22:38
sistpotyso when's the next meeting?22:38
NCommanderanyone want to change their vote on making me shepard?22:38
sistpotytwo weeks from now, +8 hours, right?22:38
sistpotyNCommander: no, that was already agreed on :O22:38
sistpoty:P even22:38
NCommanderlol22:38
persiasistpoty: -16 hours I thought.22:39
sistpotypersia: heh, thinking in modulo 24 that should be the same? (but not thinking in calendar days of course *g*)22:39
persiasistpoty: Precisely :)22:40
* persia fears a strict 334 hour rule would end up stomping other meetings after only a few months22:40
sistpotyso it would be Friday the 8th, 4utc, correct?22:40
persiaI think so.22:40
persias/334/344/22:40
sistpoty[ACTION] next motu meeting at Friday, 8th, 4 UTC22:41
MootBotACTION received:  next motu meeting at Friday, 8th, 4 UTC22:41
sistpotyany last words from anyone?22:41
LaserJockno, please no!22:42
* persia is glad to see more non-MOTU taking actions in the MOTU meeting again22:42
NCommanderI'd like to close this meeting by beginnign with the opening sections of War and Peace22:42
persia(well, some actions)22:42
sistpotyNCommander: you're out :P22:42
NCommanderpersia, do I really count? I just don't know the meeting of "Shut up and watch" :-P22:42
norsettoI guess that was meaning22:43
persiaNCommander: Yep.  For the past 3-4 months, we've not had so much non-MOTU contribution.  I think it's important to remember we are part of a larger development community.22:43
sistpotyok, I propose to close the meeting, and since we haven't had a vote yet so far, vote with +1 to close the meeting *g*22:43
sistpoty[vote] close the meeting?22:43
MootBotPlease vote on:  close the meeting?.22:43
MootBotPublic votes can be registered by saying +1/-1/+0 in the channel, private votes by messaging the channel followed by +1/-1/+0  to MootBot22:43
MootBotE.g. /msg MootBot +1 #ubuntu-meeting22:43
sistpoty+122:43
MootBot+1 received from sistpoty. 1 for, 0 against. 0 have abstained. Count is now 122:43
geser+122:43
MootBot+1 received from geser. 2 for, 0 against. 0 have abstained. Count is now 222:43
RainCT+122:43
MootBot+1 received from RainCT. 3 for, 0 against. 0 have abstained. Count is now 322:43
norsetto+122:43
MootBot+1 received from norsetto. 4 for, 0 against. 0 have abstained. Count is now 422:43
NCommander+1 sistpoty22:43
MootBot+1 received from NCommander. 5 for, 0 against. 0 have abstained. Count is now 522:43
NCommanderwoo22:44
sistpoty[endvote]22:44
MootBotFinal result is 5 for, 0 against. 0 abstained. Total: 522:44
sistpotywith a result of 5 in favor: meeting adjourned :)22:44
sistpotythanks for coming, and thanks for the patience :)22:44
* persia considers always volunteering to chair when sistpoty is around to avoid the obligatory close-the-meeting-vote22:44
* NCommander falls over22:45
sistpoty[endmeeting]22:45
sistpotystopmeeting22:45
sistpotypersia: heh22:45
persia#endmeeting22:45
NCommander</meeting>22:45
RainCTkillall meeting22:45
sistpotydamn, we're doomed! *g*22:45
NCommandertelint 022:45
sistpoty#endmeeting22:45
persiaNo, really, Mootbot wants the # from sistpoty22:45
MootBotMeeting finished at 16:48.22:45
NCommanderBTW, if you want to try something fun22:45
NCommandertry: /join 022:45

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