/srv/irclogs.ubuntu.com/2005/03/12/#ubuntu-meeting.txt

Simira*waiting impatiently for Tollef to come home*12:14
=== OddAbe19 [~OddAbe19@pcp02542642pcs.lncstr01.pa.comcast.net] has joined #ubuntu-meeting
=== pitti [~martin@box79162.elkhouse.de] has joined #ubuntu-meeting
=== pitti [~martin@box79162.elkhouse.de] has left #ubuntu-meeting []
=== ..[topic/#ubuntu-meeting:smurfix] : Tuesday 8 March 2005 16:00 UTC Community Council meeting -- https://www.ubuntulinux.org/wiki/CommunityCouncilAgenda || Tuesday 1 March 2005 20:00 UTC: Technical Board -- http://www.ubuntulinux.org/Hwiki/TechnicalBoardAgenda. || This is NOT #ubuntu, nor #ubuntu-devel
smurfixCan somebody clear the topics from the CC agenda page which were processed last time?09:30
=== smurfix could do it, but he wasn't there, so ...
=== ..[topic/#ubuntu-meeting:smurfix] : Tuesday 8 March 2005 16:00 UTC Community Council meeting -- https://www.ubuntulinux.org/wiki/CommunityCouncilAgenda || Tuesday 1 March 2005 20:00 UTC: Technical Board -- http://www.ubuntulinux.org/wiki/TechnicalBoardAgenda. || This is NOT #ubuntu, nor #ubuntu-devel
=== jani [~jani@iv.ro] has joined #ubuntu-meeting
=== jani [~jani@iv.ro] has left #ubuntu-meeting ["Leaving"]
=== mjg59 [mjg59@cavan.codon.org.uk] has joined #ubuntu-meeting
=== mjg59 [mjg59@cavan.codon.org.uk] has joined #ubuntu-meeting
=== mjg59 [mjg59@cavan.codon.org.uk] has joined #ubuntu-meeting
=== pitti [~martin@box79162.elkhouse.de] has joined #ubuntu-meeting
=== opi [~emil@195.69.82.35] has joined #ubuntu-meeting
=== zul [~chuck@CPE0006258ec6c2-CM000a73655d0e.cpe.net.cable.rogers.com] has joined #ubuntu-meeting
=== sabdfl [~mark@host217-37-231-28.in-addr.btopenworld.com] has joined #ubuntu-meeting
sabdflhi all05:00
=== mako [mako@micha.hampshire.edu] has joined #ubuntu-meeting
sabdflis the tech board meeting today also at 20h00?05:00
=== Mithrandir points sabdfl to the topic
=== mako nods
sabdflerk05:02
sabdfldidn't think mdz meant to move ALL tb meetings, just the one week05:02
KamionI think I'd got the impression that it was a permanent change, although I don't know from where05:11
smurfixHeh, whether he meant to or not, it happened. ;)05:16
=== sivang [~sivang@box79162.elkhouse.de] has joined #ubuntu-meeting
=== doko [~doko___@dsl-082-082-205-117.arcor-ip.net] has joined #ubuntu-meeting
=== jani [~pet@Home03207.cluj.astral.ro] has joined #ubuntu-meeting
=== tseng [~tseng@thegrebs.com] has joined #ubuntu-meeting
=== jani [~pet@Home03207.cluj.astral.ro] has left #ubuntu-meeting []
=== pitti [~martin@box79162.elkhouse.de] has joined #ubuntu-meeting
=== jbailey [~jbailey@CPE000ded9d787c-CM014260028338.cpe.net.cable.rogers.com] has joined #ubuntu-meeting
=== Nafallo [~nafallo@h62n4c2o1027.bredband.skanova.com] has joined #ubuntu-meeting
=== Nafallo [~nafallo@h62n4c2o1027.bredband.skanova.com] has left #ubuntu-meeting ["Lmnar"]
=== jdz [~jdz@chpau.oxfordnetworks.net] has joined #ubuntu-meeting
=== ogra [~ogra@p508EB7D9.dip.t-dialin.net] has joined #ubuntu-meeting
=== dholbach [~daniel@pD9E64BCC.dip.t-dialin.net] has joined #ubuntu-meeting
=== jani [~pet@Home03207.cluj.astral.ro] has joined #ubuntu-meeting
=== silbs [~sbsm0084@host81-154-101-223.range81-154.btcentralplus.com] has joined #ubuntu-meeting
Simirahi silbs08:53
zulhye ogra08:54
ograhi zul08:54
=== Keybuk [~scott@descent.netsplit.com] has joined #ubuntu-meeting
silbshi Simira08:56
sivanghi silbs 08:59
Simirasilbs: I'm working on some "package solution" on merchandice-stuff for lan-parties and conferences. I was on a lan-party last week, and did some recognozation. :)08:59
sivanghey Simira , everybody else09:01
sabdfl-hi all09:01
zulhey sabdfl 09:01
pittiHi sabdfl09:01
sivanghi again sabdfl 09:01
Simirahi sivang09:01
=== Mithrandir waves
ograhi sabdfl09:02
=== Simira waves back
=== sivang high fives Mithrandir
sabdfltech board here?09:02
sivangright09:02
zulhey everyone else09:02
sabdflwell that's the greets taken care of - and nicely too :-)09:02
ogralooks like TB ...in the topic....09:02
=== T-Bone [varenet@T-Bone.developer.debian] has joined #ubuntu-meeting
zulhey T-Bone 09:03
T-Bonehi09:03
sivangsome interesting stuff there wrt "WinningTheDesktop" and "WhatWindowsUsersWant" on the wiki09:03
Keybukjust waiting for mdz ... :p09:03
pittisivang: indeed, this was pretty good09:03
sabdfleveryone read the agenda?09:03
ograpitti: did you recognize my mail ?09:04
Simiraah, right... the meeting09:04
=== mdz [~mdz@ca-studio-bsr1o-251.vnnyca.adelphia.net] has joined #ubuntu-meeting
mdzmorning09:04
sabdflhiya09:05
sabdflis tim morris here?09:05
dokoevening all09:05
Keybukevening09:05
mdzI do not think he is here09:05
sabdflok, let's get going09:06
mdzI have skimmed his documents, and they are very interesting, but I do not think it is tech board material09:06
mdzwould make a great BOF I think09:06
pittiindeed09:06
ograyup09:06
pittimdz: fits nicely into the Hoary+1 goals09:06
sivangmdz: yeah09:06
sabdflhis work is excellent09:06
ogralooks like he did a lot of work for that09:06
sabdflsome of the issues are tb, i think, in terms of signing off on specs and goals09:06
sivangwe could take some of the features there and actually make action items out of them for hoary+109:07
mdzwe're not doing that for hoary+1 yet09:07
sivangso maybe for hoary+2 :-09:07
KeybukI think mdz means we're not planning the hoary+1 goals yet09:07
mdzright09:07
sivanguh right , sorry09:07
mdzwe'll be doing that in Sydney09:07
mdzwhere we have a huge list to discuss09:08
sabdflyes, the timing of sydney is great for feature goal plans09:08
Keybukthose two pages would be a fantastic basis for a BOF or two in Sydney09:08
mdzyes, I'll add it to my BOF list09:08
sabdflbof or nine, i think09:08
sivanghehe09:08
mdzwho added this item about sending patches to Debian?09:08
Keybuksabdfl: someone only gave us a week this time ... :p09:08
Keybukmdz: me09:08
sabdflremember - the output of sydney has to be hard specs09:08
sabdflin the past we've had great discussions, but never crystallised them into specs09:09
sabdflalright, MaintainerCandidates!09:09
ograKeybuk: we will have a MOTU meeting on thursday, probably it fits better there09:09
mdzlamont has been reviewing the patches spit out by MOM for quite some time now, in order to submit things upstream which have fallen through the cracks09:09
sabdflMOM?09:09
mdzmerge-o-matic09:09
ograKeybuk: since thats the majority of packages...09:09
sabdflright09:09
mdzlamont: ?09:09
lamontmdz: and that fell through the cracks last week with the kernel stuff, it's back on top of my list09:10
mdzlamont: ok, please start submitting bugs this week09:10
Keybukogra: yeah, if you could bring it up in MOTU meeting as well, that'd be good; as a few of those I've been pointed at have been universe packages09:10
mdzwhen we last spoke, you already had a stack of things that seemed ready to submit09:10
ograKeybuk: yup, and if we dont have a policy in place before the masses run in we are lost :)09:11
lamontI had a stack of known differences, then went looking at them and came up with one that was clearly a debian bug fix and not an ubuntu-ism.  That one got filed09:11
sabdflwe should definitely be continuing to publish the patches, as we did for warty09:11
lamontand questioned09:11
sabdflmalone will allow us to automate a lot of this09:11
lamontsabdfl: that'll be great09:11
sabdflwhere we fix a bug that malone knows is in debian, it could automatically file a note in the debian bts09:12
sabdflsaying: "baz get ...."09:12
sivangwow, that'd be so cool09:12
=== mdz waves his hands frantically
Keybuklamont: I think part of the problem is the line between ubuntu-ism and bugs; some maintainers (Marco) want to see everything and be able to decide themselves whether it's a bug or ubuntuism09:12
mdzKeybuk: perhaps we should more widely publish the MOM output09:13
=== dredg [niall@malkovich.office.blacknight.ie] has joined #ubuntu-meeting
mdzand invite Debian maintainers to review it09:13
sabdflhold on - we have a responsibility to publish source, which we do, and where we can help notify someone of a fix to a known bug, we should, but we can't take repsonsibility for getting it all accepted09:13
lamontKeybuk: one cop-out solution is to just file bugs against every package in hoary that has 'ubuntu' in the version, telling the maintainer that there's a diff.  But that's the wrong end of the spectrum, I believe09:13
sabdflif the debian maintainer wants to be tightly in the loop, let them become ubuntu maintainers and collaborate09:13
Keybukmdz: yeah, I could mail debian-devel with the URL of the m-o-m output09:13
lamontKeybuk: that'd be a big step forward I think.09:13
sabdflthat would be spam-o-matic09:13
mdzsabdfl: we've made a statement that we'll go the extra step, and not require them to come to us in order to see what we've done09:13
lamontespecially given the subjective nature of what the maintainer(s) want to know about09:14
sabdflmdz: where we fix debian bugs, yes09:14
sabdflwe can't do the work on both sides09:14
=== mvo [~egon@ip181.135.1511I-CUD12K-01.ish.de] has joined #ubuntu-meeting
haggaiwhat about making a way for DDs to opt in to notifications of changes for just the packages they are interested in09:14
haggaii.e. their own packages09:15
sabdflwe could build that into malone, yes09:15
mdz"Ubuntu contributes patches directly to Debian as bugs are fixed during the Ubuntu release process, not just when the release is actually made"09:15
Keybukdoes malone/launchpad provide the functionality to subscribe to a package?09:15
Keybukala. the Debian QA system09:15
mdzhypothetically09:15
sabdflmdz: we were publishing them in /patches/ which is plenty09:15
sabdflKeybuk: no, we've not spec'd that, it would be a good bof in UDU09:15
mdzsabdfl: there seems to be some question about what subset of what we do, we publish09:15
pittibut eventually they should be filed in the Debian BTS to track them there, too. /patches/ is too invisible and untrackable09:16
sabdflin theory we should be publishing everything09:16
mdzlaunchpad can't be the answer to this stuff; this level of functionality is a very long way off09:16
dholbachper-package RSS feeds with links to /patches/ would be cool09:16
mdzsabdfl: I mean, what we push-publish09:16
dokopublishing the patches is /patches is a lot of work, for some packages I created an attachment in the bug report and pointed the maintainer to the bug report.09:16
dokos/is/in09:16
sabdflmdz: we should *definitely* push-publish any fix for a known debian bug09:16
pittiI think as soon as we do everyting in arch, we already have the corresponding changelogs for a patch, then we can publish these somewher09:17
=== mjw [~mark@ext-gw01.feelslikefriday.com] has joined #ubuntu-meeting
haggaidoko is right, to do it manually is certainly quite time consuming09:17
mdzpitti: yes, but again, this is a very long way off09:17
sabdflthat's why it's most important to do it for the places we fix a known bug in debbugs09:17
pittiuntil then I think we just need to take the time to fill bugs09:17
mdzKeybuk: do you have a pointer to something which describes actual complaints from Debian, if any?09:17
mdzKeybuk: is it about our enhancements, bugfixes, methods of publishing, what?09:17
pittihowever, I very often file bugs to the Debian BTS, but many of them (derooting, cups, etc.) tend to be ignored09:17
Keybukmdz: nothing concrete, is mostly just /msg when I'm active in #debian-devel from one or two people09:18
pittiso far _none_ of my derooting patches has been adopted09:18
mdzpitti: I don't think it's necessary to push those09:18
Kamionthere was a fair bit of disgruntled blog activity a couple of weeks back09:18
KeybukI think most of the changes fall into our enhancements that people feel should be in Debian09:18
lamontpitti: this isn't about whether or not they accept them09:18
Keybukhotplug, etc.09:18
pittilamont: right, but if you don't see any reply, my motivation decreases to publish further patches09:18
dokopitti: yes, same experience here, 50% are ignored, and the rest applied with, or without any notice.09:18
sabdflif we've slacked off since the warty release i can understand it, it's a lot of work to push every patch, but we should try to tighten up again now we are in pure-fix-bugs mode09:18
Keybukor where a bug is filed in our Bugzilla, fixed by us -- but never filed in debbugs, even though it affects them09:19
sivangwe should be probably working close with the packages respective debian maintainers like pitti does with sjored on hal and dbus09:19
pittiOTOH, my security patches are really leeched09:19
lamontpitti: except that we happen to be paid to publish them... 09:19
pittiright, cooperation with sjoerd works perfectly09:19
sivangso maintainers have an idea what's going on and if they want to adopt patches they do.09:19
lamontsabdfl: definitely09:19
mdzsabdfl: we have slacked a bit on bugfixes, but we do a lot more on our own now (and not in response to known debian bug reports) as well09:19
mdzwe're not working out of debbugs anymore09:20
mdzthe vast majority of our work is directly with Ubuntu users09:20
Kamionmy impression is that it's not that there's a general lack of communication, there's just enough things that fall through the cracks that people notice them09:20
lamontmdz: and that's certainly a component of the problem09:20
sabdflso let's leave it to the judgement call of the person making the fix09:20
Keybukmdz: and we're not using Debian ourselves anymore, so don't notice the bugs09:20
mdztherefore, the policy that we would submit things to Debian where it was known/reported in Debian already, has led to a drop in patch submission09:20
sabdflif it's in debbugs, and we found it there and fixed it, then we should definitely notify upstream / maintainer about the fix09:20
mdzto do otherwise would be prohibitively expensive in terms of developer time, in order to investigate/test/reproduce the bug on Debian09:20
sabdflwe're not using debbugs any longer?09:21
sabdfli don't know that09:21
=== maskie [~maskie@196-30-109-242.uudial.uunet.co.za] has joined #ubuntu-meeting
sabdfldidn't09:21
mdzsabdfl: not exclusively09:21
lamontusers are filing bugs at bugzilla.ubuntu.colm09:21
mdzwe still import RC bugs from Debian09:21
sabdflbut we're still syncing in from debbugs to bugzilla?09:21
mdzmy point was that most of the bugs are from Ubuntu users now, and not from debbugs09:21
lamontand those bugs aren't necessarily in debbugs09:21
sabdflright09:21
sabdflwell, let's start with this:09:21
Kamionsince we get all the trivial stuff through bugzilla and only get the serious stuff through debbugs09:21
sabdfl - if it's in debbugs, and we fix it, definitely try to publish the fix in debbugs09:22
mdzKamion: right09:22
Kamionand the volume of the former is much greater :)09:22
mdzsabdfl: searching debbugs to find out of the bug is filed there is a great deal of work for non-trivial packages09:22
=== trulux [~lorenzo@trulux.user] has joined #ubuntu-meeting
truluxhi09:22
sabdfl - otherwise use your judgement09:22
mdzs/out of/out if/09:22
sivangmdz: imported RC bugs get always published-pushed right?09:22
sabdflmdz: i meant, if we LEARNED about it from debbugs, so we already know its there09:23
mdzsabdfl: ok09:23
mdzsivang: that is the idea, yes09:23
Kamionsivang: not automatically, though09:23
sivangmdz: at least for those is should be 09:23
sivangKamion: eh09:23
sabdfldo we have an idea of the patch acceptance rate for that class of patches?09:23
mdzthat's become a very small amount of our work, though09:23
lamontsivang: and at least a few people missed a few such...09:23
sabdfl - in debbugs, we fix it, we ppublish the patch?09:23
sivanglamont: I see09:23
mdzs/in debbugs/came from debbugs/09:23
Kamionsivang: because sometimes we need to say "this doesn't affect us" for one reason or another, and that would just be noise in debbugs09:23
sabdflyes, sorry, came from debbugs09:24
sivangKamion: ok09:24
Kamionsivang: so our automatic gateway is only unidirectional, very deliberately09:24
=== lamont expects that some of the debian mindset is because they s/came from debbugs/in debbugs/
=== elmo [~james@83-216-141-215.jamest298.adsl.metronet.co.uk] has joined #ubuntu-meeting
sabdflKamion: i like the idea of allowing the debian maintainer to turn on bidirectionality09:24
pittiis that possible with bz?09:24
Kamionsabdfl: it's not a per-maintainer thing really though, it's a per-bug thing09:25
sabdflthat would be harder :-09:25
sabdfl)09:25
Kamionand the Debian maintainer can subscribe to a particular bug if they want09:25
sabdfl"flag this bug as "HELP ME PLEASE""09:25
haggaiKamion: but debian users wouldn't see the bug like that09:25
T-Bonejust a 2cents, but what about adding a knob to bz "send this comment back to BTS", for bugs that were imported?09:25
Kamionsabdfl: I could probably gather statistics on how many bugs containing our patch URLs are closed and how many open, which might be close enough09:25
sivangbz?09:25
Kamionsivang: bugzilla09:26
sivangKamion: k09:26
sabdflKamion: ok, would be interesting09:26
mdzis there any TB decision to be made on this issue?09:27
sabdflbig picture - my sense is that we are fixing a lot of bugs, and while we should tighten up again to be like pre-warty where we were religious about pushing the bugfixes, we should not also assume responsibility to file a bug upstream for every patch we make09:27
Keybukmdz: don't think so; just seemed like a good time to broach the subject given bug fix frenzy starting and most parties being here09:27
mdzunlike Warty, the bug fixing spree we're about to do is going to be dominated by Ubuntu bug reports, not Debian ones09:28
sabdflmdz: perhaps just a mail to the team from you reminding folks of the procedure particularly for bugs which came to us from debbugs and which we fix?09:28
T-Bonesabdfl: i thought we made a religion of pushing back fixes?09:28
pittisabdfl: indeed, filing bugs upstream is a PITA09:28
sabdflT-Bone: we publish everything, immediately, and where we know it is going to be immediately useful we make it extra easy for upstream09:29
pittisabdfl: pushing them to Debian is easy, but for upstream you have to look for gazillions of different email and bts systems, some of them don't even have a bts09:29
mdzwe could build some tools to simplify the process, but it would be throwaway work09:29
T-Bonesabdfl: ok got it09:29
sabdflmalone is coming along09:29
pittiwhen, BTW?09:29
sabdflit will take time to get it right, but it gives us the ability to automate a LOT of this09:30
sabdflwe'll be using it heavily for bendy, and it will be rocking for bendy+109:30
Keybuks/bendy/hoary+1/09:30
Keybuk:p09:30
sivanghehehe09:30
sabdflKeybuk: you STARTED it09:30
mdzshould we start a flam^Wdiscussion with Debian about what we do in this area?09:30
haggaican the m-o-m output URL be placed next to the statement on the Debian and Ubuntu page about pushing patches back09:30
Keybuksabdfl: I was JOKING :p09:31
ograbtw, we will discuss this topic too in the MOTU meeting on thursday: https://www.ubuntulinux.org/wiki/MOTUMeeting09:31
sabdflhaggai: good idea09:31
mdzagreed09:32
sabdflok, let's move on09:32
sivangwould be interesting to look at it regardless of pushing stuff upstream, I never saw a MOM output :)09:32
Keybukhttp://people.ubuntu.com/~scott/ongoing-merge/09:32
Keybukor09:32
Keybukhttp://people.ubuntu.com/~scott/patches/09:32
sivangKeybuk: hehe, cool 09:33
=== haggai adds that URL to DeveloperResources
haggaiah, it was already here :)09:33
Keybukthe latter just provides the current ubuntu/debian changes09:34
Keybukwith added humour09:34
sabdflKeybuk: very nice!09:34
sabdflready for MaintainerCandidates?09:34
KamionKeybuk: last I looked, it only provided the changes when a subsequent Debian change (and thus m-o-m run) had happened09:34
KamionKeybuk: has that been fixed?09:34
sivangKeybuk: http://people.ubuntu.com/~scott/patches/blam/blam_1.6.0-1ubuntu1_unknown.patch :-)09:34
KeybukKamion: that's still true09:34
mdz(added link to /patches/ to the Ubuntu and Debian page)09:35
Keybukit's a side-effect of the merge-o-matic output rather than a separate process in its own right09:35
KeybukI could make it a separate process easy enough though09:35
mdzready for MaintainerCandidates09:35
sabdflKeybuk: go ahead and do that09:35
Keybukon MaintainerCandidates, the current list is huge -- could it be separated out into lists of people at each stage so we know who is actually up this time?09:36
ograsabdfl: we have four MOTU candidates that could get apprved if they had a review from a second approver and have already workes on packages that were upoaded on behalf...09:36
mdzit has been cleaned up since the last time09:36
ogras/workes/worked09:37
mdzthe people who are already maintainers/members have been processed09:37
ograyup, these are all current candidates09:37
mdzIs there anyone here who is seeking technical board approval to upload packages to Ubuntu?09:37
dholbachdredg, jani, wasabi and metalikop are on the list, right ogra?09:38
ograwasabi, dredg ,  jani, metallikop anyone around ?09:38
dredg?09:38
=== wasabi [~wasabi@207.55.180.100] has joined #ubuntu-meeting
=== dredg wakes up
Keybukmdz: is the current list /all/ awaiting TB approval then?09:38
sabdflhi dredg, wasabi09:38
dokomdz: not exactly, but pushing zope packages from universe to supported.09:38
dredglo sabdfl 09:38
wasabiHello.09:38
mdzKeybuk: no09:38
dholbachmetalikop seems to be idle for 03:34:4109:39
sabdflyou guys are up for maintainership candidacy, right?09:39
mdzdoko: we're talking about confirming new Ubuntu maintainers09:39
=== dredg nods
wasabiYes.09:40
dholbachjani, metalikop and dredg have been very active in the UniversePythonTransition09:40
mdzfor universe, or unrestricted?09:40
janiI'm here 09:40
janiwas gone for 5 minutes09:40
dholbachmdz: universe09:40
ogramdz: MOTU09:40
mdzdo all of you already have approval from an MOTU leader?09:41
mdzand so only need one more ack?09:41
ograyup09:41
ograwe did a lot of cross review....09:41
mdzhave you already sent signed CoC to mako?09:41
dredgi have not.09:41
janinot me yet09:41
ogragah09:41
janino keyowners in the area09:41
janihave to do it via snailmail09:42
jani:(09:42
dredgunsigned key. i can fax it09:42
dredg(well, selfsigned)09:42
wasabiI am hopeing to maintain some java-related things... most notably Eclipse.09:42
mdzcan each of you state your real name?  your nicks are not familiar09:42
dredgmdz: Niall Sheridan09:42
janiJani Monoses09:42
wasabiJerry Haltom09:42
mdzthanks09:43
janinor are our real names ;)09:43
ogrametalikop would be: AaronLake09:43
KeybukI don't see JerryHaltom on MaintainerCandidates ?09:43
mdzit would be preferable to allow MOTU itself to approve new members; that was the original intent.  are we still seeking a second MOTU leader?09:43
Kamionwe appointed Treenaks09:44
mdzit is much more effective for MOTU to be self-supporting, since you are working as a group and are familiar with one another's activities09:44
Kamionwith somebody as backup, who temporarily escapes me09:44
ogranope... but both additional approvers were on fosdem last weekend..09:44
Kamionoh, was it Mithrandir as backup?09:44
ograyup09:44
Mithrandiryes09:44
wasabiKeybuk, it's not. I came to this meeting unprepared. My shoes are untied and I had to have the secretary put on my tie. =/09:45
sabdflmdz: we'll need to bootstrap it a little, though09:45
ograKamion: but you are welcome as well ;)09:45
Kamionogra: you don't want to see the length of my to-do list already09:45
mdzsabdfl: MOTU has a healthy base already, in fact09:45
sabdflmaybe it would help to say something like "when you've had 5 packages reviewed and uploaded"?09:45
mdzwasabi: we're still getting into the rhythm of the process09:45
ograsabdfl: since we are working in a group and do cross reviews this would probably be a better way09:46
dholbachsabdfl++09:46
ograsabdfl: wouldnt invole relying on a singl (or two) persons09:46
mdzthe wiki only mentions haggai09:46
sabdfli like what's written on all the guys' wiki pages, so we are on the right track09:46
mdzwho, as I recall, had to step down09:46
sabdfli'm just concerned that asking someone who hasn't reviewed real code to approve someone else as a maintainer is not going to get the result we want09:47
mdzwe all agree that it doesn't make much sense for the technical board to try to make a judgement on candidates without any information to go on09:47
sabdflogra: who's been most active in the MOTU team?09:47
Kamionmdz: I think the wiki is obsolete; we discussed this in the CC meeting last week09:47
ograsabdfl: dholbach and me i think.....09:47
dokodholbach seemed to be quite ctive09:47
KamionI was under the impression some MOTU would update their pages09:48
tsengyep, id agree with dholbach and ogra as most active09:48
ograsabdfl: dholbach recently lots more then me, since i'm busy with hwdb09:48
wasabiI added myself to the wiki in case it matters.09:48
sabdflare there any of the candidates that you can both recommend without reservation, confident they will do high quality work and that they'll be able to identify risky moves in advance of making them?09:48
sabdfl*both* recommend?09:48
ograsabdfl: i think we could both be happy with dredg, jani and wasabi ...metalikop could need a bit more training09:49
ogradholbach ?09:49
dholbachi can definitely recommend dredg, jani09:49
sabdfldholbach: ?09:49
dholbachi didnt work with wasabi that much09:49
dholbachbut he seems quite active on the java front09:50
dholbachdredg and jani communicate nicely with the team09:50
mdzwasabi: you've been working with jbailey on the java stuff, or on your own?09:50
wasabiWith jbailey.09:50
mdzjbailey: are you here?09:50
ograjbailey ?09:50
jbaileyI've been working with him.09:50
jbaileyI'm happy with wasabi's packaging, and I'm confident that he thinks things through before giving them to me to sponsor.09:51
sabdflok, i'm happy to take ogra and dholbach's endorsement of dredg and jani09:51
mdzjbailey: do you have enough information to make a recommendation about whether he is ready to upload packages to universe/09:51
mdzbetween ogra and jbailey, I'm happy with wasabi09:52
jbaileymdz: I've reviewed 3 of his packages to far for packaging, and I've worked with him on this and seen him around #gnome-debian before.09:52
sabdflok09:52
ograi think if someone has already fixed 7 packages (wasabi) that got uploaded on behalf he must have at least understood the basics ;)09:52
wasabi7?09:52
sabdfli guess metalikop needs to work with the MOTU team a little longer09:52
dholbachwow... 7 already09:52
sabdflguys, there will be a LOT of movement in universe these next few weeks, with a lot of work on KDE09:53
mdzwho will take responsibility for guiding them through the rest of the process (keys, CoC, etc.)?09:53
mdzsabdfl: most of KDE moved into main today09:53
ogramdz: dholbach and me09:53
wasabiogra, where did that 7 come from?09:53
dholbachyes09:53
sabdflok09:53
dholbachhoary-changes?09:54
mdzogra: ok, thank you09:54
ograwasabi: i did a search for your name in hoary-changes....09:54
wasabiOh I see! Probably my few gnome packages which seb never change the maintainer line on.09:54
sabdflok, are we done with MaintainerCandidates?09:54
mdzI think so09:54
dholbachcool09:54
=== dholbach gives high fives to both jani and dredg.
mdzI'd like to say that I think MOTU is coming together very nicely, you're doing excellent work as a team09:55
mdzthanks for your efforts09:55
=== jani is honored
dredgcheers guys09:55
sabdflwelcome aboard guys09:55
janithanks09:55
dholbachthanks :-)09:55
wasabiNo hi five for me? :)09:55
sabdflwasabi: respek09:56
=== pitti high-fives wasabi
sabdflnext?09:56
=== ogra gives high fives to wasabi
wasabiyay. =)09:56
mdzthanks especially to ogra and dholbach for helping organize the team and encourage people to join09:56
mdzthat's it for the agenda09:56
mdzany other business?09:56
sabdflany other business?09:56
janimdz, right they're both very motivating and helpful09:56
haggaiyup thanks from me too to ogra/dholbach09:56
sivangapparently another nice short and relazing tb meeting :-)09:56
=== dholbach high-fives ogra as well
sivangs/relazing/relaxing/09:57
sabdflsoo... about that bootsplash on the live cd...09:57
sabdflkidding09:57
sivanghehehe09:57
=== mdz snarls
T-Boneheh09:57
sabdflthanks mdz, thanks everyone09:57
ograeverybody is invited on thursday to joinr our first meeting : https://www.ubuntulinux.org/wiki/MOTUMeeting09:57
sabdflogra: is that a weekly?09:57
=== ogra makes some advertizing
sabdfli'll be there if i can, but will be quiet if possible :-)09:57
ograsabdfl: lets see how often its needed :)09:57
sabdflmdz: do you want the tb to be at 20h00 every time?09:58
mdzsabdfl: yes09:58
sabdflok09:58
sivangsabdfl: it's pretty good like that09:58
T-Bonethat's cool09:58
dholbachthanks mdz and sabdfl, thanks everyone else :-)09:58
mdzsabdfl: is it a problem?09:58
sivangsabdfl: wops, that was for mdz09:59
sabdflnot at all, i was just under the impression it was a one-off change09:59
mdzit's nice to be awake for at least half of the weekly meetings09:59
sabdflrock09:59
sabdflcheers all09:59
dholbachbye sabdfl 09:59
mdzthanks, everyone09:59
sabdflhey, who's going DOWN UNDER?09:59
ograbye sabdfl 09:59
zuli wish09:59
T-Bonei'd have loved to ;}09:59
sivangsabdfl: btw, how was down under chosen as a name?10:00
MithrandirI am (:10:00
=== mvo raises his hand
dredgoh me, if enough people contribute to the 'dredg-goes-down-under' fund10:00
pittisivang: given where it takes place...10:00
ograsabdfl : not sure yet (i resigned from my job last week, dunno if i have the money)10:00
Keybuksivang: "Down Under" is UK slang for Australia10:00
sabdflsivang: Australia10:00
sivangKeybuk: ah!10:00
jbaileyKeybuk: Isn't it common slang elsewhere too?10:00
Keybukjbailey: one assumes it isn't common south of the Equator :p10:00
janinot in australia :)10:00
dholbachjbailey: i only learned it in english classes :-)10:00
Kamionjbailey: originated in the UK though, since Australia is pretty much antipodeal to here10:01
pittiUbuntuRightHere for .au :-)10:01
dredgand by 'contribute to' i mean pay wads of cash into :) and by fund i mean bank account10:01
dredg(details available on request)10:01
wasabiso what are the procedures for this post-meeting? key added to upload keyring?10:01
jbaileyAh.  Well Canadians wind up absorbing UK slang alot of the time anyway.10:01
dholbachwasabi: you'll have to send the signed CoC to mako10:01
wasabialready done10:01
wasabifor Membership.10:01
dholbachwasabi: and send a signed mail to *looking it up on the wiki*10:01
mdz(wiki updated)10:02
janilink please?10:02
dholbachwasabi: upload@ubuntulinux.org for being on the whitelist and keyring@ubuntulinux.org for being able to upload10:02
=== sabdfl [~mark@host217-37-231-28.in-addr.btopenworld.com] has left #ubuntu-meeting []
=== Keybuk [~scott@descent.netsplit.com] has left #ubuntu-meeting ["Leaving"]
=== pitti [~martin@box79162.elkhouse.de] has left #ubuntu-meeting []
dholbachwasabi: someone already signed your key?10:03
wasabigood point10:03
=== T-Bone [varenet@T-Bone.developer.debian] has left #ubuntu-meeting ["Leaving"]
wasabioh that's going to be a difficult one10:03
dholbachdamn :-/10:03
janiso  for those with unsigned keys what is to be mailed exactly?10:03
dholbachtseng had to organize it too10:04
dholbachbut managed else10:04
janiprinted signed CoC, along with a copy of the  ID?10:04
dholbachyour gpg key id10:04
dholbachand some notarization10:04
janiand the CoC goes normally via e-mail?10:05
dholbachyes10:05
dholbachsigned, sent to mako10:05
dholbachsabdfl offered to sign the key of tseng, when he sent him all that by snailmail10:05
janiso a text something like this gpg id belongs to Jani Monoses?10:05
wasabithere a page describing this?10:05
dholbachnot yet10:05
dholbachdamn10:05
dholbachtseng just left10:06
wasabiwell somebody set up a fax machine once you get a page. ;)10:06
janitseng said he'll solve it by getting signed at a asecurity conf he'll attend soon10:06
wasabior is this all email? heh10:06
janiso no papers in his case10:06
=== sivang [~sivang@box79162.elkhouse.de] has left #ubuntu-meeting []
dholbachi guess you ask in #u-d explicitly or get in touch with mako(?)10:07
dholbachi thought he was another keysigning guru :-)10:07
=== metalikop [i@pcp0011431183pcs.sothfd01.mi.comcast.net] has joined #ubuntu-meeting
metalikopMeeting still on?10:19
metalikopI'm a bit late :)10:19
ogrametalikop: meeting is over10:20
metalikopi figured as much10:20
metalikopanyone have a log up somewhere?10:20
ograhttp://people.ubuntu.com/~fabbione/irclogs/ubuntu-meeting-current.html10:20
=== jani [~pet@Home03207.cluj.astral.ro] has left #ubuntu-meeting []
metalikopthanks10:22
haggaiogra/metalikop: http://irclog.workaround.org is quicker at updating10:24
ograah, thanks10:25
=== mdz [~mdz@ca-studio-bsr1o-251.vnnyca.adelphia.net] has left #ubuntu-meeting ["Client]
=== amu [amu@amu.developer.debian] has joined #ubuntu-meeting
=== amu [amu@amu.developer.debian] has left #ubuntu-meeting []
=== BlackHussar [~chatzilla@corp.stamps.com] has joined #ubuntu-meeting
=== silbs [~sbsm0084@host81-154-101-223.range81-154.btcentralplus.com] has left #ubuntu-meeting []
=== metalikop [i@pcp0011431183pcs.sothfd01.mi.comcast.net] has left #ubuntu-meeting []
=== BlackHussar [~chatzilla@corp.stamps.com] has left #ubuntu-meeting []

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