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

=== OddAbe19 [~OddAbe19@pcp02542642pcs.lncstr01.pa.comcast.net] has joined #ubuntu-meeting
=== ogra [~ogra@p508EB0BD.dip.t-dialin.net] has joined #ubuntu-meeting
=== ..[topic/#ubuntu-meeting:ogra] : 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. || Thursday 03 March 2005 http://www.ubuntulinux.org/wiki/MOTUMeeting || This is NOT #ubuntu, nor #ubuntu-devel
=== ..[topic/#ubuntu-meeting:ogra] : 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. || Thursday 03 March 2005 16:30 UTC http://www.ubuntulinux.org/wiki/MOTUMeeting || This is NOT #ubuntu, nor #ubuntu-devel
=== Riddell [jr@muse.19inch.net] has joined #ubuntu-meeting
=== haggai [~halls@i-83-67-20-196.freedom2surf.net] has joined #ubuntu-meeting
=== ogra [~ogra@p508EB0BD.dip.t-dialin.net] has joined #ubuntu-meeting
=== dholbach [~daniel@pD9E64BD5.dip.t-dialin.net] has joined #ubuntu-meeting
=== mvo [~egon@ip181.135.1511I-CUD12K-01.ish.de] has joined #ubuntu-meeting
=== pitti [~martin@box79162.elkhouse.de] has joined #ubuntu-meeting
=== pitti [~martin@box79162.elkhouse.de] has left #ubuntu-meeting []
=== Simira [rpGirl@m146i.studby.ntnu.no] has joined #ubuntu-meeting
=== zul [~chuck@198.62.158.205] has joined #ubuntu-meeting
=== jbailey [~jbailey@CPE000ded9d787c-CM014260028338.cpe.net.cable.rogers.com] has joined #ubuntu-meeting
=== wasabi [~wasabi@207.55.180.100] has joined #ubuntu-meeting
=== zul [~chuck@198.62.158.205] has joined #ubuntu-meeting
=== bradb [~bradb@modemcable206.155-81-70.mc.videotron.ca] has joined #ubuntu-meeting
=== koke [~koke@rm-001-26.serve.com] has joined #ubuntu-meeting
=== ggi [~ggi@ggi.base.supporter.pdpc] has joined #ubuntu-meeting
=== pitti [~martin@box79162.elkhouse.de] has joined #ubuntu-meeting
=== jani [~jani@iv.ro] has joined #ubuntu-meeting
dholbachhi everyone05:30
ograhi everybody, lets start the meeting then05:30
zulhey05:30
=== pitti waves
ograi would first like to do some administrativa before we come to the agenda05:31
dholbachwhich you can read here http://www.ubuntulinux.org/wiki/MOTUMeeting05:31
=== mvo waves too
=== herve [~herve@mutualite-3-82-67-67-10.fbx.proxad.net] has joined #ubuntu-meeting
ograhow often do we want to do this meeting05:31
ajmitchat this hour? not too often 05:31
=== dredg [niall@malkovich.office.blacknight.ie] has joined #ubuntu-meeting
ograwe can have a rotating timeschedule, but i meant how frequently05:32
pittijust see how it goes, how much of the agenda will still be left, and decide that afterwards05:32
ograweekly, 2 weekly, monthly05:32
ograok05:32
ograso lets go to the agenda...05:33
ograhow do we handle packages in universe that are newer than in Sid or will never enter debian but ubuntu etc05:33
hervewe can still append ubuntu1 to the revision 05:33
ograthere was something on the wiki a while back, cant look t up right now..05:33
hervein case thy enter Debian some day05:33
pittiyou should start with ubuntu005:33
ogra...it said something like upstream must be actively maintained05:34
pittiso that the first Debian version will be never05:34
ajmitchpitti: we've been doing -0ubuntu105:34
pitti-> then you can sync05:34
dholbachnot -0ubuntu1?05:34
pittiajmitch: argh, right05:34
pittiI meant this05:34
pittisorry05:34
dholbachok05:34
dholbachbut the problem is the interaction with debian people05:34
pitti^ a technical or a social one?05:35
ograi think its up to the DD to choose that for his pkg05:35
dholbachatm i can't say anything positive about it05:35
dholbachyeah... i had no reaction until this point05:35
hervewhy Debian wouldn't do the opposite of what we do?05:35
hervesync Ubuntu packages into Debian05:36
herveour definition of free software is close enough05:36
dholbachherve: because they don't have the syncing mechanism05:36
ajmitchherve: they might, if people upload into debian by their procedures05:36
Kamionit's a matter for individual maintainers05:36
herveI meant manually :)05:36
ograherve, that up to them05:36
dholbachit's each DD's decision05:36
ogratahts even05:36
ograargl05:36
herveso we would need some mentor like new packagers :-)05:37
pittithe problem is, if you have a NEW package, then there is no default DD for it05:37
dholbachif people used cdbs-tarball-dpatch/simple-patchsys (ok, only in the cases where it's possible), giving back would be a lot easier05:37
pittiif you want it in Debian, you have to file an RFP05:37
pittidholbach: ++05:38
ajmitchdholbach: not everything fits well with cdbs :)05:38
ajmitchor an ITP if you intend to maintain it05:38
dholbachajmitch: that's what i just said :-)05:38
pittiajmitch: no, but most packages do05:38
hervedholbach, got the message ;)05:38
dholbachbut that doesnt apply to NEW packages05:38
pittiajmitch: right, if you want to maintain it in Debian yourself, there is no problem, right?05:38
ajmitchpitti: yep05:38
pittiI thought the problem were if you don't want/can't maintain it in Debian05:39
ograbut we will have a lot MOTUs that are no DD in the future i guess05:39
dholbachcan't any of you ubuntu-DDs be the sync-NEW-from-ubuntu--guy? :-)05:39
pittibtw, Debian can't sync pacakges because they don't want ubuntu version numbers05:39
ograthey would have to take maintainership05:39
pittidholbach: no, that would be a PITA05:39
ajmitchogra: sure, you don't have to be a DD to maintain debian packages, just to upload05:39
dholbachpitti: yes... i can see that05:39
pittidholbach: we can certainly sponsor uploads, though05:40
pittibut not maintain05:40
ograbut lets not discuss the debian part here, its up to them05:40
pittifor the record, I'm fine with sponsoring Debian package uploads05:40
haggaias long as it is easy for debian to use them05:40
pittias long as I don't have to review them every time05:40
=== ajmitch can also help with that if needed
dholbachpitti: i'll get back to you :-)05:40
ograour part shold be maintainig a list of such packages05:40
dholbachogra: which ones?05:41
hervepitti, you could trust a package that was trusted to enter Ubuntu?05:41
haggaigood idea.  Time for a new wiki page listing new packages not in Debian?05:41
ograso if debian is interested they can request a sync05:41
pittiherve: "trust" in which sense?05:41
ogradholbach: NEW05:41
dholbachok05:41
dholbachubuntu-NEW :-)05:41
hervepitti, uploading without reviewing05:41
pittiherve: I don't speak about NEW packages05:41
pittiherve: just updates05:41
ogradholbach: yeah05:41
ajmitchherve: I wouldn't expect ubuntu packaging to always be perfect05:41
pittiherve: I can't process NEW packages any way05:41
haggaihaving such a wiki page would also be a reference for people wondering what additional stuff ubuntu has05:41
ograajmitch: i would...(after some time)05:42
hervepitti, ok you would prefer to review each update, ideally05:42
pittiherve: I mean, the actual maintainer has to care for his bugs, I only would sponsor the upload05:42
ajmitchogra: only when someone has time to review the packages :)05:42
Mithrandirsorry, was off for food.05:42
pittihowever, I don't think that we should automatically upload all new Ubuntu packages to Debian05:42
ograajmitch: i hope we dont drop the crossreviewing05:42
ograpitti: never ever05:43
hervecould some ubuntu platform or mailing list be set as the maintainer email of such packages?05:43
pittifiling RFPs with a link to the Ubuntu package is more than enough IMHO05:43
ajmitchogra: yes, but when people are MOTUs they can upload without getting reviews05:43
=== tritium [~tritium@12-202-90-180.client.insightBB.com] has joined #ubuntu-meeting
pittithen the Debian community can decide 05:43
ograajmitch: we will have a poicy for NEW packages....05:43
pitti++ for the wiki page with new stuff05:43
ograok..05:44
ogranoted05:44
ograok, next point ? 05:44
dholbachubuntu-NEW packages05:44
dholbachand their process05:44
ograyup05:44
ograi find the suggestion of dholbach very tempting05:45
dholbachthe idea is quite clear: we need to have a thorough review of those packages05:45
dholbach3 MOTUs is ok in my eyes05:45
pittiwhat about mandating, or at least urging a sane pacakging format?05:45
Mithrandirogra: to have a couple of MOTUs reviewing packages before they are uploaded?05:45
ajmitchpitti: later in the agenda :)05:45
pittiI mean for new ubuntu packages05:45
pittiok05:45
=== ogra remembers metalikops first package (an gnome applet with suid binary)
ograMithrandir: yup05:46
=== koke [~koke@rm-001-26.serve.com] has left #ubuntu-meeting ["Abandonando"]
pittiajmitch: "urge Debian people..." -> that's not my point, but nevermind05:46
=== koke [~koke@rm-001-26.serve.com] has joined #ubuntu-meeting
ajmitchpitti: ah, sorry, misread it05:46
ajmitchMithrandir: yes, any of the MOTU team, not just the leads I think05:46
dholbachany other ideas, proposals?05:47
pittiI'd mandate cdbs+tarball and a proper patch system (simple-patchsys, quilt, whatever); this comes close to the future dpkg format and is really good05:47
ograjust to make sure 6 or more eyes have seen it05:47
pittiogra: we should collect a list of more folks who are willing to do review05:47
Mithrandirpitti: I find making cdbs packages really icky when you have a bit of complexity.  It has no docs.05:47
pittii. e. I'd be willing to review packaging05:47
janipitti, so cdbs preferred over plain debhelper?05:48
pittifor _some_ pacakges05:48
ograpitti: we do a lot of cross reviewing in #ubuntu-motu05:48
pittiMithrandir: right, the docs should be improved, but it rocks; however, dbs is fine, too05:48
pittijani: it's only a proposal, but cdbs really rocks and avoids many errors (and makes packaging easy, btw)05:48
ajmitchperhaps jbailey or someone could actually document cdbs one day :)05:48
pittimy point is, if we have one common packaging format, review is easy05:49
Mithrandirpitti: we don't want to get people to use dbs.05:49
ograpitti, but we always have packages nobody feels smart enough to review, like hula05:49
dholbachno other opinions on the ubuntu-NEW thing?05:49
pitti:-)05:49
haggaidholbach: might be worth noting it only applies to MOTUs, not maintainers?05:49
pittiogra: during my security work, I've seen so many braindead packaging formats, it really hurts05:49
pittiogra: we must not make this error again05:49
ograheh05:49
ograok05:49
dholbachhaggai: this is MOTUMeeting :-)05:49
pittiso enforcing a strong packaging policy would really rock05:49
dholbachpitti: ++05:50
haggaidholbach: I know but you're talking about documenting a process05:50
MithrandirI think that having patches in arch can also be fine, if the arch repo is mirrorer publically05:50
pittiMithrandir: you mean patches which are directly in the debian diff.gz?05:50
dholbachcan we please get to the patch-thing later?05:50
pittiok05:51
Mithrandiryes, and {arch} directories in there too05:51
pittiargh05:51
dholbachhaggai: you're right... there should be exceptions to it05:51
pittiMithrandir: arch dirs in diff.gz? that sucks05:51
dholbachhaggai: i wouldn't tell seb128 to let me review his packages :-)05:51
Mithrandirt would be interesting to have a MOTU review some of my packages. :)05:52
ajmitchMithrandir: if we're up to the task :)05:52
ograhaggai, i think forcing a policy that NEW packages must get reviewed is a good first set in a process05:52
pitti++05:52
ogras/reviewed/crossreviewed05:52
herveby at least 3 persons?05:53
pittiogra: the lintian output should be published somewhere05:53
ograadditionally i would like to have the "must actively be maintained upstream or you take it yourself" in05:53
mvoyes, I think this review is good because we have much less "ownership" on packages than e.g. debian05:53
ajmitchherve: yes, we've often had reviews from 2-3 people already05:53
ogras/take it/take it over05:53
dholbachogra: ++05:54
herveok so you can conclude 3 is enough?05:54
Mithrandiryes, more seems a bit excessive05:54
ajmitchyes, we don't want too many05:54
crimsun3's sufficient to me05:54
ografor a initila review, its ok05:54
herveapproved!05:54
ajmitchit'd get too slow to do 4 or more reviews for each new package05:54
dholbachand keeping a list of those who "signed off" is good, those 4 guys have to fix the bugs then :-)05:54
pittiogra: special exception for suid/sgid binaries05:54
pittiogra: I'd like to be notified about them05:54
ajmitchpitti: we can pass those on to you05:55
pittiso that I can do a more insight review05:55
ograhehe, piti, i assume one of the three will raise a hand then05:55
dholbachpitti: yeah05:55
pittiogra: can we please formalize this?05:55
ajmitchogra: well it only took a couple of minutes to spot the suid applet :)05:55
ograpitti: you will get them all ;)05:55
pittiogra: no suid/sgid without approval from security@ubuntu.com05:55
pittiokay, thanks05:55
ograok, all suid binary packages go to the security team first05:55
dholbachMithrandir: about the public mirror05:55
dholbachpitti: about the lintian warnings05:56
=== ajmitch will have logs of the meeting once we're finished, btw
dholbachwe have no mechanisms at all for doing that05:56
pittidholbach: I'm more concerned about certain errors05:56
crimsunajmitch: (it's also logged concurrently by fabbione)05:56
pittidholbach: okay, forget the publishing05:56
ajmitchcrimsun: great05:56
dholbachand doing it manually is a pain in the ass05:56
pittidholbach: but lintian finds a lot of errors, at least the packager/the reviewers should pay attention to it05:56
pittidholbach: oh, not manually05:56
ograpitti: i normally dont approove packages with linian errors/warnings....05:57
pittidholbach: I thought about integrating it into the buildd process05:57
Mithrandirdholbach: public mirror and ask jblack to mirror it on the supermirror (sourcecontrol.net)05:57
dholbachpitti: we will set up docs of common "pitfalls"05:57
pittiokay05:57
pittidholbach: debian automatically publishes the lintian errors, we can certainly set this up, too05:57
dholbachyeah... we need some architectural changes05:57
dholbachbecause the motu crowd will grow05:57
janiwhat about lintian warnings when sweeping across universe (i.e. python transition)05:57
dholbachwere what? 10 now?05:57
pittijani: in particular?05:58
janishould we stop for them or postpone for separate task05:58
dholbachbut we'll 50-100 soon, i guess05:58
janiand do just the focused changes05:58
ajmitchdholbach: trying to coordinate that many will be fun05:58
ograso are we done with NEW Packages ?05:58
dholbachajmitch: that's why we have to make proper decisions now05:58
janipython transition or the new .desktop file missing05:58
ajmitchogra: I think so05:58
dholbachogra: yeah05:58
crimsunpitti: something equivalent to Debian's packages.qa would be wonderful, but that seems to be quite some infrastructure.05:58
ograok, next is Teams05:59
pittijani: oh, lintian complains about old pythong versions? neat05:59
ajmitchcurrently there are 2 teams listed05:59
Mithrandircrimsun: we'll have that, it's called launchpad05:59
ajmitchpitti: I don't think it does05:59
pitticrimsun: no worries, that's already being worked on05:59
janipitti, no for instance unrelated warings05:59
crimsunMithrandir: / pitti: ah, excellent.05:59
janipitti, for each transitioned package say 5 warnings05:59
dholbachogra: write in CAPITAL letters05:59
ograTEAMS NOW05:59
pittijani: well, common sense applies :-)05:59
janipitti, stop and solve them or go on with transitioning packages (the current goal)05:59
dholbachjani, pitti: that's something we'll discuss in "patches"06:00
=== ogra whistles....
pittijani: I don't care about speling errrors, I care about broken libraries and suid files and such06:00
janidholbach,ok :)06:00
janipitti, ok then06:00
ograwe currently have two active teams and a bunch of proposals06:00
dholbachnamely java and mono?06:01
ajmitchogra: well the zope/plone page was just put up yesterday, we've got 3 people willing to do zope stuff for now 06:01
dholbachoh cool06:01
ograi personally would like to see the packaging efforts shared in a team then having individual maintainers06:01
dholbachyeah06:01
janicrimsun, xfce4 team?06:01
herveno Python team or merged with Zope?06:01
ograbut we need teamleaders.... to care for them06:01
crimsunjani: sure, something of that ilk06:02
ajmitchherve: separate06:02
ajmitchsee MOTUTeams06:02
ograherve: propse one :)06:02
ajmitchnoone has created the wiki page, so there's no team :)06:02
dholbachwe'll have more overview over the packages (with a chance of weeding out)06:02
ogracrimsun: could you make a page below desktop teams...06:02
ografor xfce06:02
crimsunogra: absolutely06:02
ogragreat :)06:02
dholbachbut how do we get people in teams? you have any ideas?06:03
ograas i wrote on the agenda, i think its up to the teamleaders.....06:03
ajmitchpitti: you want people in the MOTUSecurity team?06:03
=== herve would like a Python teamn (he recently gained valuable experience ;o))
ograbut we need these first06:03
pittiajmitch: in any case, right now we only have one person caring for universe security updates06:03
pitti(Gerardo di Giacomo, Astarot)06:03
ajmitchogra: how will team leaders be elected/appointed/volunteered?06:03
ograbtw: http://www.ubuntulinux.org/wiki/MOTUTeams06:03
ajmitchpitti: alright06:04
pittibut he's no MOTU06:04
ajmitcha few more would be good then06:04
pittiin any case06:04
dholbachajmitch: activity, that's what i'd say06:04
ograajmitch: who comes first....06:04
ograajmitch: later the team should sort it themselves06:04
pittiI will coordinate vulnerabilities and I have tools to support me06:04
pittibut I would appreciate a MOTU to do the uploads06:04
ograpitti: the plan was that the team is lead by a MOTU, but the members dont need to be...06:05
pittifine for me06:05
ograpitti: as a team will need at least one uploader06:05
ajmitchogra: ok, so the zope team lead would currently be doko (although he's a full maintainer, not a MOTU)06:05
herveok so I can be member of a Python team06:05
ajmitchherve: you can 06:05
crimsunherve: indeed06:05
ajmitchI'll also be in a python team, I think06:05
herveso I'll create the MotuPyton page and I myself to the members06:06
ograi'll join pygtk :)06:06
ograherve: go on06:06
dholbachwe need ideas what those teams have on their goal list06:06
ajmitchherve: just copy the text from the other team page :)06:06
dholbachso people have a clearer meaning of why joining the team06:06
ajmitchdholbach: agreed06:06
herveajmitch, you read my mind :-)06:06
ogradholbach: that schould be written on every team page06:06
dholbachyeah... but we have to move :-)06:07
ajmitchherve: well I just copied the appropriate text from the mono team page :)06:07
crimsundholbach: true. I've forwarded jani a brief (by no means conclusive) list of goals for xfce; that will be on the wiki page for the xfce team.06:07
dholbachcool06:07
dholbachwhat should the group separation be based on? skill? "package section"? ...?06:08
dholbachor whatever 2-3 people agree on? ;-)06:08
ograseparation ?06:08
ogralet the groups sort it themselves....06:08
dholbachok06:08
janifocus on a specific software?06:08
ajmitchthere are going to be people in more than one group anyway06:09
dholbachwas just an idea to help new guys to get into it06:09
ogralets just see that we get one MTU as lead for every group06:09
crimsunthere's an implicit separation based on packages if you're referring to overarching themes - or do you mean within a team?06:09
crimsuns/themes/teams/06:09
dholbachno... not within a team06:09
hervewhat about a team able to help and solve on porting problems06:09
herve?06:09
ograthe teams should have a package list ....06:09
=== koke [~koke@rm-001-26.serve.com] has joined #ubuntu-meeting
dholbachjust as proposal... i could imagine there's someone who wants to get involved and doesnt know where to start06:10
ograso every othe team can see what they are working on06:10
hervePython team officialy created!06:10
janiwell teams should not be exhaustive06:10
ajmitchherve: renaming your page, sorry :)06:10
janijust specialized groups06:10
ogradholbach: he asks and gets pointed to the teamleader06:10
dholbachif (s)he says: "i know a bit of perl", (s)he could get into a PerlGroup *shrug*06:10
herveajmitch, ?06:10
janiother MOTU activities might go on outside of specific teams06:10
dholbachi was just wondering if this was any good06:10
ogradholbach, yup, so you poing him/her to the perl team06:11
ajmitchherve: hmm, I think we should probably keep the MOTU pages with the MOTU prefix consistent?06:11
dholbachyeah06:11
crimsundholbach: yes, that sounds fine06:11
crimsunajmitch: agreed06:11
ajmitchalthough the zope & mono team pages aren't..06:11
jania METAMOTUTeam06:11
janito coordinate where new people go :)06:11
dholbachso a division of groups based on skill and "interest"/"package section"?06:11
herveajmitch, ok I retitle the Zope page too then06:11
ograinterest and package selection06:12
dholbachjani: MOTUTeams :-)06:12
crimsundholbach: moreso the latter06:12
ajmitchherve: ok06:12
ograanybdy else who wants to lead/join a tema ?06:12
dholbachi'd say perl/mono/java is a "skill" :-)06:12
ograman...my typing is crap06:12
ajmitchogra: I just joined python team06:12
janiogra, we got used to it, no problem :)06:12
herveas a beginner, I prefer not giving myself too much burden06:13
ajmitchherve: we'll soon thrash you into shape ;)06:13
ograhehe06:13
dholbachok... what did we agree on?06:13
ograwe have teams06:13
crimsunherve: the mentoring process is a vital part; the more experienced among us are helping each other and the less experienced; the less experienced will then become more experience and are expected to assist newer, etc.06:13
janiI'd join xfce06:13
ograled by a motu06:13
hervecrimsun, sounds like a mailing-list and a plain wiki section for MOTUs...06:14
ajmitchherve: and irc, of course :)06:14
herveI can't but agree on the sharing of knowledge06:15
dholbachyeah06:15
herveajmitch, yes but it's getting harder with more and more people06:15
dholbachand we should have sexy RSS feeds06:15
dredgdamn work (specifically tomcat being on crack) has wiped out any chance of me paying attention to what's going on. where can i get logs of this for later reading?06:16
crimsunogra: teams led by a MOTU(s) with possibly major contributions from members and non-members, correct?06:16
dholbachdredg: people.u.c/~fabbione/irclogs06:16
ajmitchcrimsun: yep06:16
crimsunajmitch: ok06:16
ajmitchherve: are you a MOTU yet, or going through the process?06:17
dholbachok, is the MOTUTeam thing settled?06:17
Mithrandirdredg: http://err.no/tmp/foo.txt is just today's log, very up-to-date.06:17
dholbachi dont think we have to form the teams right now :-)06:17
dholbachogra: alright?06:18
crimsunI'm clear wrt MOTUTeam06:18
dredgcheers06:18
dholbachok06:18
=== jdz_ [~jdz@66-231-199-135.oxfordnetworks.net] has joined #ubuntu-meeting
dholbachthe next point will be the most-eagerly discussed one: patches going back to debian06:19
ajmitchah yes06:19
=== ogra [~ogra@p508EA7EC.dip.t-dialin.net] has joined #ubuntu-meeting
ograsorry, got disconnected06:19
dholbachas i proposed on MOTUMeeting: we need some form of easy-to-apply patches (publically, maybe with mail/rss notification), where changes are absolutely obvious06:19
ogramy summary of the last topic:06:20
pitti... or documented in the changelog06:20
ogra<ogra> teams are led by a motu06:20
ogra<ogra> the teams are separated by interests/package selection06:20
ogra<ogra> eery team needs a short description on the teams page06:20
ogra<ogra> and a packagelist06:20
ogra<ogra> team members dont need to be MOTU06:20
ajmitchdholbach: we can't expect debian packagers to change their packaging ways, either :)06:20
dholbachno we can't06:21
herveajmitch, maintaing is enough for now but being trusted a MOTU some day would be an honor06:21
dholbachbut we can urge them to, whenever we touch packages and submit out patches to    *.u.c/patches06:21
crimsunogra: great, agreed.06:21
ograk06:21
ajmitchthey're a notoriously stubborn lot, the debian maintainers ;)06:21
dholbachbut it's the best we can do... as i see it06:21
ajmitchyes06:21
dholbachany other plans? ideas?06:22
ograyou wont get them doing that i suspect06:22
ajmitchand sometimes they'll reject patches because they don't fit well 06:22
Mithrandirwe really want to get our patches back into debian, since we then don't have to maintain them ourselves.06:22
hervehu... sorry I'm catching up...06:22
ograi would like (as i wrote) just make a list of changes we made06:22
dholbachMithrandir: what about the syncing aspect?06:22
ajmitchMithrandir: agreed, the less work we have to do to keep packages in sync, the better06:22
hervewhat's the difference with patches for Ubuntu main packages from Debian?06:22
ograits the up to the DD to pick is particular ones06:22
pittias a general rule of thumb, debdiffs are the most universal form of patch submission06:22
pittithey will fit everytime06:23
pittiand include changelogs and such06:23
Mithrandirdholbach: MOM helps a lot, but it's still a bit of manual work.06:23
dholbachMithrandir: ok... will have to learn about that at some stage06:23
crimsunogra: that should be listed in the changelog - for instance, I enumerate in debian/changelog what each thing I've added to debian/patches/ does, so one can search the hoary-changes archive06:23
ogramalone should help there as well06:23
dholbachpitti: yeah... but easy to "select" patches would be rocking even more06:23
pittidholbach: one debdiff per change06:24
pittidholbach: unless you changed several things in one upload06:24
crimsunpitti: ah, excellent idea06:24
pittidholbach: then of course this needs to be split06:24
ogracrimsun: i thougth about a more viewable thing...like a list/websearch etc06:24
crimsunogra: oh ok06:24
hervecrimsun, is there a policy or procedure on modifying Debian packages yet?06:24
=== tseng [~tseng@thegrebs.com] has joined #ubuntu-meeting
dholbachherve: it's happening now :-)06:24
ograherve: dont break it to much06:25
herveyes but some draft somewhere on the wiki or the wild internet06:25
herveI don't ask for the approved one :)06:25
ajmitchherve: it mainly depends on the changes needed & the package, I guess06:25
ajmitchthere are policies for versioning & the like06:26
pittiyes, you should follow the versioning policy in all cases06:26
Mithrandirwe also want to decide whether we should fix minor bugs or not.06:26
herveok nothing for more advanced cases06:26
pittiotherwise this will become a mess06:26
Mithrandirlike spelling errors and such06:26
pittiwhy not?06:26
pittiif somebody wants to?06:26
ograsure06:26
Mithrandirpitti: more work to maintain.06:26
Mithrandirbasically06:26
=== herve is picky on spelling mistakes
dholbachi guess this is something which would be better to decide we had a cooler architecture06:26
pittiMithrandir: MOM?06:27
Mithrandirpitti: mergeomatic06:27
herveI think those can wait another revision with more important patches?06:27
pittiMithrandir: if it's _only_ a speling mstake, then it might not be worth the trouble, agreed06:27
ograif i pick a package to maintain. i want it to be as clean as i can get it06:27
pittiMithrandir: but fixing it in addition is fine imho06:27
Mithrandirit's just a matter of policy -- I can live with either.06:28
dholbachogra: there's nothing wrong with fixing stuff and with being nitpicking ,but how do we have to change the architecture to make it as easy as possible for debian and us?06:28
crimsunMithrandir: I think minor errors are game; in that case one dpatch in debian/patches/ fixing the like would suffice, no? (easily sent back to Debian)06:28
pittiit is easiest if you don't change the architecture :-)06:28
Mithrandir(but forcing them to be _clean_ would make my work easier, since I can just continue being really stict when reviewing packages)06:28
dholbachpitti: <b>I</b> wouldnt dare it06:29
ogradholbach: as i said before, a list/webinterface where a DD can look for changes on his/her pkg06:29
ograand decide which to adopt06:29
pittidholbach: in some cases I successfully bitched the Debian maintainer to do it :-)06:29
ograso they dont feel we steal their work06:29
ograbut rather feel we helped....06:30
dholbachi think before hoary is released we should focus on getting things done, after that we need to *magically* get that architecture06:30
dholbachso we can do everything as nicely as we can06:30
ograas i said before, i think malone is much of that tool06:31
dholbachi heard much about keeping patches in baz06:31
dholbachwhat do you think?06:31
ajmitchdholbach: we haven't got much time to get stuff done for hoary :)06:31
Kamiondholbach: won't really work until we have imports of all the packages06:32
ograthat would require additional baz knowledge for new MOTUs06:32
Kamiondholbach: when we do, that'll be great, but it's a dead loss until then06:32
dholbachKamion: ok06:32
ograwhich is an additional hurdle06:32
KamionCanonical has an employee working on a next-generation baz, which should be much less painful to use06:32
dholbachogra: right... but if it makes things <ever> most easy, that's the way to go06:32
ogradholbach: but that would lower the rate of new MOTUs a lot i guess....06:33
dholbachogra: depends on the tool :-)06:33
janiogra, if done right using it will be easier than learning debian packaging 06:33
dholbachogra: maybe there'll be some automatism06:34
ograguys, baz isnt even fully documented 06:34
janiogra,  true06:34
ograhow should one that has never used a versioning tool step in there easily06:34
pittihct06:35
pitti:-)06:35
ograi think the learning curve is already quite high if you never did packaging....06:35
janiwhat I'm saying is that if the tool has a nice interface it should be less of a hurdle than dpkg :)06:35
janitla/baz is far from that :(06:35
pittiogra: cdbs is great to make the learnign curve less steep :-)06:36
herveogra, when I started, I inspected other packages and copied some stuff06:36
ajmitchpitti: as long as it's documented06:36
herveis cdbs documented enough? 06:36
ajmitchpitti: I've had to read through the cdbs source a number of times :)06:36
pittiwell, enough to understand it06:36
pittibut not very detailled06:36
pittiajmitch: me too :-)06:36
ajmitchand I've had great success harassing jbailey on irc ;)06:36
ograpitti: i have cdbs as suggestion for NEW packages in my notes already ;)06:37
Mithrandirpitti: I disagree, I think cdbs is terrible and dh_make-generated stuff is a lot easier to read and understand,.06:37
ajmitchbut he was also my sponsor for some debian packages06:37
tritiumPerhaps canonical could set up a bounty for cdbs documentation.06:37
Mithrandirthat is, it's terrible because you have to read through the source to figure out how it works.06:37
pittiMithrandir: I've seen too many poorly written debian/rules files which weren't more than the dh_make output :-(06:37
=== Kamion agrees with Mithrandir
pittiokay, but then this is a documentation problem06:38
tsengdh_make makes a pretty nasty package06:38
herveI lost the topic we're talking about :o06:38
pittiMithrandir: and cdbs has tarball.mk :-)06:38
dholbachherve: ++06:38
pittiwhich rocks06:38
ograherve,  The right way to handle upstream bugfixes06:38
ajmitchpitti: agreed, I like using that06:38
=== pitti cries for dpkg next generation
ograbut its a bit offtopic indeed06:38
herveogra, rather sounds like "packaging made easy"06:38
ograheh06:38
janipitti , any link to dpkg-ng talks?06:38
ajmitchherve: it is :)06:38
ograok, did we have any consensus on the topic ?06:39
MithrandirI don't think a rules file with:06:39
Mithrandir #! /usr/bin/make -f06:39
Mithrandirinclude /usr/share/cdbs/1/class/makefile.mk06:39
Mithrandirinclude /usr/share/cdbs/1/rules/debhelper.mk06:39
Mithrandiris very understandable either.  Unless you happen to understand cdbs.06:39
pittijani: hmm, ask Keybuk, he has a nice page about it06:39
dholbachogra: not yet06:39
janipitti, ok thanks06:39
Mithrandirjani: possibly on dpkg.org06:40
hervecan we sum up the decisions or proposals about handling upstream bugfixes?06:40
tritiumBut for a new packager, it's less intimidating.06:40
pittiMithrandir: but you have to understand debhelper, too06:40
Mithrandirpitti: it has man pages and sensible names. :)06:40
ograi think its easier to understand the basics of packaging without cdbs....06:40
pitti(okay, off-topic, agreed)06:40
dholbachogra: we won't sort it out today06:40
Mithrandiryeah, off-topic. :)06:40
ograeven it may be easier to maintain06:40
ograOK06:40
ajmitchogra: yes, but currently we don't have the equivalent of NM06:41
tsengherve: in bugzilla, or packages?06:41
ograNEXT POINT !06:41
=== Treenaks reads backlog
hervetseng, I lost it long ago06:41
Mithrandircan we get a summary first?06:41
ograhmm, did we have any consensus?06:41
ograi didnt see one06:41
ajmitchon bugfixes/patches?06:41
ograyup06:42
dholbachwe want to have cool web-based/mail/rss/baz-architecture06:42
dholbachi think that was all06:42
Mithrandirdholbach: at some point in the future.06:42
ograwhich malone might do already06:42
Mithrandirand we want to push as many changes back to debian as humanly possible06:42
ogra(list with ubuntu changes)06:42
ajmitchbut for now, use debdiff to get patches to submit to debian maintainers06:42
=== tseng takes the "get to know your debian maintainer" approach
Mithrandirwe'll do minor changes as well as larger and infrastructural stuff, but try not to rip apart the debian packages completely06:43
tsengwhich I think everyone should strive to do, where possible06:43
ajmitchtseng: either that or be the debian maintainer :)06:43
Mithrandir(larger and infrastructural is like the python transition)06:43
tsenghm that will be a whore to get back into debian06:44
ograok, noted for the summary06:44
Kamionlike the conventions for people doing non-maintainer uploads in Debian06:44
Kamionit's considered polite not to totally change the packaging in an NMU06:44
pitti++06:44
Kamionin our case, it's just silly to totally change the packaging - you're making a lot of merge work for yourself in the future06:44
Kamionunless you're sure that change will go back to Debian06:45
TreenaksHow about submitting all (useful) patches from universe to the debian bts?06:45
MithrandirKamion: true, but we want to do stuff like correct spelling and such, which you wouldn't do in an NMU06:45
ograok, are we done with the topic ?06:45
KamionTreenaks: it's a matter of filtering06:45
ograoh06:45
KamionMithrandir: that's true06:45
TreenaksKamion: true, but MOTUs need to do coordinate with the debian maintainers, imho06:45
KamionTreenaks++06:45
Kamionbut, in the event that you simply can't, you shouldn't let that stop you06:46
=== ogra thinks its up to the DD himself....we can just offer stuff
=== mdz [~mdz@ca-studio-bsr1o-251.vnnyca.adelphia.net] has joined #ubuntu-meeting
ajmitchmorning mdz 06:46
mdzmorning06:46
ajmitchogra: yes, that's all we can do really06:46
mdzI had a reminder set to attend this meeting, but was distracted by kubuntu pressures06:46
Treenaksogra: yes, but talking to the d-d is not a bad thing.. knowing who he/she is, knowing a bit about the packages06:47
mdzhave you talked about Malone yet?06:47
ogramdz: next 06:47
ajmitchno, that's next on the list I think06:47
dholbachmdz: briefly in hoping it'd make patch-offers-for-debian easier06:47
=== bradb is eagerly waiting for that discussion to begin :)
ograTreenaks: sure, but what i propose is just having a list, and let them pick themselves...06:47
ogra...and notify if iwe made changes06:48
ograwhich i would expect to be possible with malone....so lets move on now :)06:48
ograok for everyone ?06:48
ajmitchok06:49
dholbachok for me06:49
ograBug tracking using Malone06:49
bradbyeah06:49
ograbradb, tell us about it :)06:49
bradbso:06:49
bradbi need to get a feel for what you guys need to get rolling with malone06:49
bradbhere's the goal:06:49
ograbtw, thanks for coming06:49
mdzyou are now bradb's most important customer :-)06:49
bradbget universe using Malone ASAP. it's good for you; it's good for me.06:49
=== sabdfl [~mark@host217-37-231-28.in-addr.btopenworld.com] has joined #ubuntu-meeting
ajmitchit'll be great for us..06:50
dholbachhi sabdfl 06:50
ajmitchhi sabdfl 06:50
sabdflhi all06:50
ograyeah06:50
bradbso, we have to figure out what needs to happen to get universe on malone06:50
ograhi sabdfl 06:50
bradbhi sabdfl 06:50
=== Nafallo [~nafallo@h101n1c1o1027.bredband.skanova.com] has joined #ubuntu-meeting
bradbso, first: how many malone users are there for universe?06:50
Mithrandiras submitters or packagers?06:50
pittiusers in the sense of packagers?06:50
bradband from there, what kind of activity could we expect on the system?06:50
ogracurrently about ten, but we expect to grow a lot soon06:50
dholbachbradb: 10 MOTUs + 10 not-yet-MOTUs + developers06:51
ogra(MOTU)06:51
bradbok06:51
bradbhow many bug reports do you think we'd see per day in the system?06:51
bradbballpark06:51
bradblike, way ballpark06:51
Riddellis malone intended to replace bugzilla.ubuntu.com?06:51
ograyup06:52
dholbachthere should be some kind of a changelog-extraction to know who worked on the package06:52
ograbut universe is the test iirc06:52
Treenaksbradb: universe only? 20-ish?06:52
bradbRiddell: for universe first, yes. it's intended to be the BTS for the MOTU.06:52
dholbachthat'd make things most easy06:52
bradbTreenaks: ok06:52
bradbnext: when do you really need to get started?06:52
bradbhow urgent is this?06:52
Mithrandirbradb: bugs.d.o seems to have about 5k bugs/month.06:53
ograas soon as we can06:53
dholbachbradb: i wouldnt want to be a pain in the neck, but the current system is a bit chaotic06:53
ograbradb: its a PITA to use ubuntu-users for that06:53
dholbach:-)06:53
Mithrandirdholbach: what system? ;)06:53
ajmitchogra: or the wiki06:53
dholbachMithrandir: the *pointing wildly around* system06:53
ograheh06:53
Mithrandirbasically, we don't have any BTS atm.  It sucks, wildly.06:53
ograyup06:53
bradbi ask because one of our guys told me it would take about another week to get universe packages imported into Malone.06:53
Mithrandirbradb: so three months ago would be nice.06:53
tsenga few bugs go through bugzilla anyway06:54
dholbachbradb: what will the bug assignment be based on?06:54
tsengive done what I could with them in-place but resolved them UNIVERSE06:54
bradbMithrandir: cool, that makes it easier for you to drink the koolaid06:54
bradb:P06:54
ograbradb: if next week is as soon as possible, thats ok ;)06:54
bradbdholbach: distro + sourcepackagename06:54
dholbachbradb: but we dont own packages in ubuntu06:55
Mithrandirbradb: you know this, but running something as big as universe (heck, even just main) without a BTS is madness.  If next week is what we get, then next week is fine.06:55
bradbnext: how do we verify that malone is suitable for your purposes, for a first go? remember, we're not trying to knock you out in round 1.06:55
dholbachbradb: so everyone who worked on a package should be possible bug fixer06:55
ogracros bug fixer06:55
bradbdholbach: that's how it is right now. wiki-mode task editing.06:55
ogracross even06:55
bradb(for distro side, anyway)06:56
tsengre that, do we have a policy for bugs which are "upstream"06:56
ajmitchbradb: universe maintainership is fairly loose, thankfully06:56
tsengand there isnt an obvious fix/patch06:56
Mithrandirtseng: somebody adopts the bug and talks to upstream?06:56
tsengthe one im refereing to isnt even reproducable afaict06:56
bradbogra: would it be you that would look at malone to see if it's sane for basic universe usage? mdz? sabdfl? all of the above?06:56
Treenakstseng: fix bug, send patch to upstream. or tell upstream there's a bug, hope they fix it06:56
tsengi asked the user to work on an already open bug upstream06:57
tsengin the case im refering to06:57
ograbradb: i don like to be responsible alone as long as i can have more eyes helping out....laets make it a small group ....06:57
dholbachbradb: does the MOTU crew get a preview? :-)06:57
bradbi just need a single point of contact between me and universe.06:58
ograok, that would be me or dholbach, since we do the administrativa06:58
MithrandirI would be happy with ogra06:58
ajmitchogra: lucky vic^Wvolunteers :)06:58
bradbdholbach: can you all access dogfood? we might need to sort out. i'd be more than happy to schedule something like that in the next day or two.06:58
MithrandirI guess we'll whine if stuff passes them but needs fixing still06:58
bradbogra: then it's you! :P06:59
ograok06:59
ajmitchgreat06:59
dredgsorry i've missed the past er.. while.. day job got in the way ;)06:59
dredgwhere are we?06:59
ajmitchdredg: malone06:59
bradbok, so, to recap, here's what we've figured out so far:06:59
dredg(i'll catch up on the older stuff in a bit)06:59
bradb1. the universe traffic should be easily manageble by malone07:00
bradb2. we have stuff to do, but we can hopefully get universe imported within a week (depending on what the gina guys can do for me)07:00
dredgajmitch: cheers07:00
bradb3. we need a session to demo malone, and ensure it's usable for a first go, for your guys' purposes.07:00
dholbachcool07:01
bradb4. ogra is my point of contact for universe; dholbach is my backup contact for universe.07:01
tsengcan I ask a stupid question? probably already been addressed even07:01
=== dholbach is just a bit confused by gina and dogfood
=== jani too
ogratseng: no07:01
ogratseng: ask a wise one ;-P07:01
tsengwell, im wondering what malone does over bugzilla.07:01
dholbachi didnt follow the development cycle of malone07:01
Treenaksgina sounds like one of the ftp-admin tools07:01
Treenaksdogfood is 07:01
Treenaksuh07:01
bradbdholbach: gina is the thing that does package imports. dogfood is app we use for internal usage only of the apps.07:01
tsengim sure it does something crazy cool, its just not apperant from the web interface that I can see07:02
ogratseng: the power is under the hod ;)07:02
ograhood even07:02
dholbachbradb: ok, nice to know you're working on it07:02
dholbachbradb: with the gina and dogfood guys :-)07:03
bradbheh07:03
hervetseng, piloting a BTS-like platform from e-mails cannot be seen from a Web interface :-)07:03
ograif i understood correctly, malone will care for the flwback of bugfixes to debian07:03
bradbhow should we schedule the demo session then? when should it be scheduled for? who absolutely must attend?07:03
ajmitchogra: that will rock07:03
dholbachbradb: we could meet on irc or mail the concrete date and time07:04
ograbradb: 1. i'm free all the time, just tell me a date 2. aks the others that want to attend then 3. as many MOTUs we can get07:04
bradbI'm thinking a little lead time would be useful, so maybe we should aim for Mondayish.07:05
ograbard: ok... i'll sort it out with the others then07:06
crimsunMonday, 14 March 2005?07:06
bradbwe need to ensure you guys can access dogfood too07:06
ograoops s/bard/bradb07:06
ajmitchbradb: that would be good07:06
Treenakssounds ok07:06
dredgok, we know what to do... we can work out the finer points after the meeting07:06
dredg(imo)07:06
ogracrimsun: 7th ?07:06
bradbcrimsun: march 7th :)07:06
crimsunbradb: ah, ok.07:06
sabdfljust reading scrollback, i didn't see an explanation for you guys about why malone is worth doing over bugzilla07:06
sabdflshould i run through that now, and bradb can correct me if i take a wrong turn?07:07
tsengplease.07:07
ograyay07:07
dredgsabdfl: bugzilla is heinous ;)07:07
bradbsabdfl: please do :)07:07
sabdflok07:07
mdzI think the problems with bugzilla are widely acknowledged, but sure :-)07:07
sabdflfirst off, malone is brand new, minimalist, and likely to have bugs. yay07:07
sabdflyou guys are the distro guinnea pigs, but i hope you will love the vision07:08
sabdflso that's what i'll pitch07:08
pittiwill it ease propagating patches to Debian?07:08
sabdflpitti: yes, explicitly07:08
pittithat was the main concern IIRC07:08
sabdflmalone is a BTS for the whole open source world, if they want it07:08
sabdflyou can use it for an upstream project07:08
sabdflyou can use it for ubuntu, and derivatives07:08
sabdfland you can easily keep track of the state of a bug anywhere in that system07:08
sabdflso07:08
sabdfla user files a bug on a source package in universe07:09
pittisure, I mean, does that help for the MOTUs right now? I. e. is all of this already implemented?07:09
herveI guess Malone is supposed to be user-friendly too?07:09
pittiif so, then it is certainly worth a try07:09
sabdflsomeone here looks at that and says "hey, that's upstream", so they mark it as upstream07:09
sabdflthis much works already07:09
hervewhich bugzilla hardly is with the default interface07:09
pitticool07:09
=== pitti wants it too
ograherve, https://launchpad.ubuntu.com/malone07:09
sabdflupstream can see their bugs, and we can see bugs on source packages07:09
sabdflcomments are shared between everyone who sees the bug07:09
pittisabdfl: don't you think a bunch of "real" users would be good to develop Malone further?07:09
dredgsabdfl: right. the main thing here is that currently it's recommended to report bugs to ubuntu-users. that ml is already *very* high volume, and bug reporting to a mailing list is imo a bad idea07:10
herveogra, thanks07:10
sabdflthere are some real users already - bazaar, and lp internal07:10
ograpitti: thats what we are starting right now07:10
sabdfldredg: once the basics are working in malone we will direct users to malone07:10
sabdflpeople can mark a bug fixed in *their* part of the open source world07:10
sabdflso at a glance you can see "ah, upstream have fixed this bug"07:10
sabdflsimilarly, if we fix a bug, and it's also been flagged as upstream, then upstream will see that we fixed it07:11
pittisabdfl: does it interact with debbugs?07:11
sabdflpitti: steady on07:11
dredgsabdfl: ok, this sounds very promising07:11
sabdflthe idea is to encourage people to collaborate07:11
sabdflwe will sync all debbugs bugs into malone07:11
sabdfland we will keep track of them07:11
sabdflso, when debian fixes a bug, we see that it is fixed, and will show that in malone07:12
Treenakscool07:12
sabdfland we will also spec a feature to tell debian when we fix it 07:12
sabdflautomatically07:12
dredgnice07:12
sabdflas long as the maintainer wants that07:12
pitti^ that's what I meant07:12
pittifor pushing back patches07:12
ajmitchsounds useful07:12
pittithat would rock07:12
sabdflyes07:12
dredgok, currently how usable is malone?07:12
sabdflfurther down the line, this will integrate with baz07:12
sabdflso when you make a patch, it can propagate and be tracked at a code level07:12
sabdfldredg: the basic structure is there, but there is a LOT of work to be done07:13
sabdflthere's been no heavy usage, and so lots of things will irritate you07:13
dredgfair enough07:13
sabdfli am confident it will be pretty polished by the time we get to hoary+107:13
ograsince we are the testers ;)07:13
bradbdredg: we've just doubled the size of the development team though (2 people! :), and indeed, Real Users (TM) is the best way i've found to do the things most useful for users as early as possible.07:14
ograit has to be :)07:14
dholbachi'm already excited about it07:14
dredgok. but it seems to me that having active testers doing real things would be a good thing07:14
pittibut at some point real guinea^testers are just required to see how it behaves in practice07:14
pittidredg: :-)07:14
ograim excited about it since mataro....but still wait.....07:14
dredgprovided that it's not so young that it can kill work07:14
=== Nafallo seconds ogra :-) *
dredgie there's not much point using it at all even for real-world tests if it eats the bugs/kills my cat/whatever07:15
=== ogra wanted to take part in MOTUGuineapigs anyway (http://www.ubuntulinux.org/wiki/MOTUTeams)
dholbachdredg: look at the current situation, how could it kill work? :-)07:15
sabdfldredg: it wont eat your bugs07:15
bradbdredg: it's stable. you won't lose data. there will be some things that will annoy you though, like sabdfl said.07:15
dredgdholbach: point taken :)07:15
sabdflit might just require more clicking than you'd like07:15
dredgsabdfl: i can live with that07:15
sabdfls/might/will/ :-)07:15
ajmitchdholbach: it leaves us stunned & amazed in awe? :)07:15
ajmitchsabdfl: any BTS will be better than what we have :)07:16
sabdflajmitch: stunned like a brick between the eyes?07:16
dholbach:-)07:16
ograthe current situation can only improve....07:16
ajmitchthere is that..07:16
sabdflok, that's enough smileys to win any battle with07:16
dredgsabdfl: the idea of tracking bugs via a ml gives me The Fear07:16
Treenaksmore clicking... that's not bad, as long as there's a way of reporing it :)07:16
Treenakswhich is probably there :)07:16
Mithrandiremail interface?07:16
sabdfldude, luurrve debbugs - it's a mlmgr!07:16
sabdflMithrandir: not yet, but in the works07:17
bradbMithrandir: notifications yes, but no reporting interface yet07:17
hervewas there some discussion already done about not developing a user-friendly interface over BTS?07:17
dredgsabdfl: the idea of tracking bugs via a ml as high volume as ubuntu-users makes me die inside07:17
Mithrandirit would be _very_ useful to be able to bug manipulation through email07:17
sabdfltrue07:17
dholbachajmitch: we'll be rocking universe even harder... 07:17
sabdflMithrandir: you'll have that by bendy, promise07:17
Mithrandirsabdfl: yay. :)07:17
ajmitchand an emacs interface as well.. 07:18
ograbendy ? is it official now ?07:18
sabdflogra: oops. no.07:18
ograhe07:18
ograh07:18
sabdflworking title07:18
pittiajmitch: rather a command line tool like "bts"07:18
Mithrandirpitti: both07:18
pitti"bts tag 12345 pending" is really cool07:18
ajmitchpitti: yes, but I like to be able to view the list of bugs in emacs when working on the changelog07:18
hervepitti, rather a graphical tool for end users?07:18
ajmitchthat is useful, I agree07:18
dredgajmitch: bah. emacs. no matter what the users say about it i maintain that, like sendmail, lacks a decent editor and mta07:18
sabdflfor example, here are the bugs in bazaar (the distributed rcs)07:19
sabdflhttps://launchpad.ubuntu.com/malone/products/bazaar/07:19
Treenaksajmitch: bts query 1234507:19
ograok, there are still three topics left 07:19
ograare we done with malone ?07:19
ajmitchTreenaks: I know, but I like emacs still :)07:19
ajmitchogra: three topics left & the sun is rising here07:20
dredgok, i'm happy enough with malone07:20
bradbi think so. i'll get the demo sorted with you guys by later today. (i.e. a firm date/time)07:20
Treenaksogra: I think we're done with malone07:20
dholbachbradb: cooool07:20
dredgyes it may require more clicking but if it benefits us long term (and everyone else) then it can't be a bad thing07:20
ajmitchbradb: thanks07:20
ograok, next is: questions regarding ChanServ? and the like ??07:20
hervewe don't need to be so many ops07:21
dredgogra: simple. add a bunch of trusted users (5-10) to the access list who can op when needed07:21
Treenaksogra: nobody ops, MOTUs voice, MOTU Masters can get ops to get rid of abuse?07:21
dredgthat many ops are unneeded07:21
dredgthe current access policies are on crack07:21
ograTreenaks, ++07:21
dholbachdredg: ++07:21
ajmitchdredg: agreed07:21
herveTreenaks, agree07:21
Treenaks(voice is for the "visual distinction" Mithrandir asked for)07:21
dholbachi dont think we need that07:22
ograhow is it handled in -devel currently07:22
ogra?07:22
dholbachand i dont like it, to be honest07:22
Mithrandirnot07:22
dredgTreenaks: yeah. the key here is "can get ops"07:22
dredgi'm not sure we need voice07:22
ajmitchogra: topic isn't locked in devel07:22
=== moquist_ [~moquist@pool-64-222-173-229.man.east.verizon.net] has joined #ubuntu-meeting
Treenaksajmitch: I'm for unlocking it in -motu07:22
ograis it locked in -motu ?07:22
dredgmotu should be a collaborative channel by MOTUs, contributers and j.random stranger07:22
ajmitchif only a couple of people can get ops, then unlock topic07:22
Treenaksogra: mode -t07:22
ograah07:22
sabdflquick question - are the MOTU the full set of people who can upload to universe? or the people who approve people to upload?07:23
sabdflare they the MMOTU?07:23
ograsabdfl: i confused that in the beginning07:23
ograsabdfl: so vurrently MOTU is every uploader to universe07:23
ogras/v/c07:23
sabdflok07:23
sabdfllet's leave it that way07:24
dredgsabdfl: for the most part everone in -motu is a contributer on some level07:24
ograand we have some motu masters07:24
sabdfland MOTUM are the people who can approve new MOTU07:24
sabdflgotcha07:24
dredgah, you mean MOTU as opposed to the channel...07:24
ografor approval and administrativa07:24
dholbachi don't think we need voices, you can always look up or ask who's a MOTU07:25
ograsabdfl: it just sounds cooler to your friends to say "i became a MOTU today" 07:25
tsengthere need not be a distiction between members and non members07:25
dredgogra: meh07:25
dholbachit's like dredg said: " everone in -motu is a contributer on some level"07:25
tsengI felt none when i worked on mono stuff for hoary07:25
ograso we agree on unlocking the topic, no ops and a list off administartive ops ppl07:25
ajmitchogra: agreed, we've got to get those tshirts printed for conferences  ;)07:25
tsengI was treated the same as everyone else working on ubuntu07:25
ograajmitch: YAY !!! +++07:26
dredgi don't see the need for separation or 'classes' of users in the channel07:26
Mithrandirajmitch: "I am your MASTER"?07:26
dholbachyeah, dredg ++07:26
ograMithrandir: yeah07:26
ajmitchMithrandir: sounds good07:26
dredgit's pointless. anyone who contributes is doing their job07:26
hervetseng, I would even think you were already a MOTU at the beginning! 07:26
ograMithrandir: dont punish to much ;)07:26
dholbachcould we decide on the chanserv thing now? :-)07:27
dholbachplease :-)07:27
ograso we agree on unlocking the topic, no ops and a list off administartive ops ppl07:27
ogra??07:27
dredgogra: yes07:27
herveagree07:27
ograok, noted for the summary07:27
tsengsame as #-devel07:27
Mithrandirogra: ok07:27
ogranext:  what can we do that our approval process doesnt slow down as much as debians NM process if the masses start rushing in07:27
dholbachwe need more reviewers07:28
ajmitchreviewers of packages?07:28
ogrado we want a policy that a new MOTU has to review a certain amount of pkgs ?07:28
dholbachthe system sabdfl appointed in last tb meeting is sufficient in my eyes07:28
ajmitchdholbach: summary of that?07:28
ogra5 packages sponsored07:28
ograits not enough in my eyes07:29
ograbut fine in the fast approval process we're currently in07:29
tsengI would disagree with any sort of policy forcing work on volunteers07:29
Mithrandirtseng: ack07:29
dredgi don't think you can gauge it on number of packages..07:29
Mithrandirsome packages are big and hard and evil, while others are small and trivial07:30
sabdflnew folks should focus on small, then grow, though07:30
ogratseng: if its a premise 07:30
dholbachwe should make sure, people communicate nicely, people minding only their own stuff, it's a matter of trusting07:30
dholbachs/, people minding only their own stuff/07:30
tsengogra: would it make more sense to have people specifically allocated to reviewing packages?07:30
dholbachtseng: anyone who finds the time07:30
ogratseng: sure, but we dont have them yet07:31
dholbachyou won't find anyone who is "just the review guy"07:31
ogratseng: so forcing newbies will probably help both sides07:31
ogratseng: i learned a lot more about packaging by reviewing others packages07:31
Treenaksogra: newbies will learn a lot from that, especially if they review together with some other people07:32
ograyup07:32
ograthats my point07:32
dholbachfurthermore we should find a way of tracking the things people do, not a documentation overhead, but something to get an impression of what people do/work on07:32
dholbachthen it'll be a lot easier to approve people07:32
ajmitchdholbach: you've done a good start on that with the wiki07:32
ograthat should be sorted in the groups stuff07:32
dredgdholbach: so what you're saying is that there should be a better way of communicating with other contributers?07:32
hervedholbach, their wiki homepage?07:32
dholbachtake wasabi for example: if you saw his plan on wiki/JavaProgress, you knew he was up for the job07:32
dholbachthat added to some nice packages he did should make the decision easy07:33
ogradholbach: i think currently your list is enough...07:33
ograif everybody cares to update regulary07:34
dholbachyeah, but we should have an agreement for every MOTU to subscribe to it :-)07:34
ograyup07:34
ograbut it will get a mess in the future07:34
dholbachand an agreement to do reviews :-)07:34
ograwe should keep a better system in mind07:34
dholbachyeah... maybe team-based07:34
ajmitchdholbach: I think most of the current MOTUs do reviews anyway07:34
ograsince you dont want a wiki page with a list of 1000s of packages07:35
tritiumpersonally, I'm a private person.  I don't blog, and don't keep a homepage or wiki page.07:35
ajmitchtritium: so am I, but it does make it easier to track work07:35
dholbachi think we should collect ideas on this issue and the provide-patches-for-debian issue and discuss it in the next meeting07:36
ogragreat idea07:36
dholbachthese 2 points are really a lot of work07:36
ogradholbach ++07:36
tritiumajmitch, yes...07:36
tsengagreed07:36
dholbachthanks07:36
dholbachnext item would be " Opportunity of a MOTU dedicated mailing-list. " :-)07:36
=== dredg waves the 'i like mailing lists' flag
ajmitchah, that's another topic, next meeting time :)07:36
ograargl07:36
dholbachi like the idea too07:37
tsengim pondering what the usefulness is at present time07:37
dholbachsince the current mailing lists really are a bit crowded07:37
tsengwe get devel topics on -devel list07:37
dholbachwe already have 3-4 people not showing up in IRC often07:37
tsengand we really want packages to be reviewed to go to the wiki07:37
ograi dont like it07:37
dholbachwell... atm it is only package reviewing07:38
ograeverything can be done through -devel currently....07:38
hervethe idea is also to lower the traffic on -users07:38
dholbachbut the organisation of teams will be another issue soon07:38
tsengpackage review should go to our wiki07:38
dholbachherve: yeah07:38
ograit would fragmet the stuff07:38
tsengwe can make a better document on the proceedure07:38
dholbachogra: there's nothing wrong with separating things from each other07:38
dholbachi think07:39
tsengif it doesnt already exist in the "how to be an motu" docs07:39
ograit is, if they arerelated to the same task07:39
tsengindeed07:39
dholbachbut we'll grow07:39
ograand MOTU is simply -devel07:39
tsenghm im not sure what "simple" part you work on :P07:39
ograadministrative things can be done through -users or on irc07:39
ajmitchI don't think we need to separate universe development from main development07:40
dholbachi think it's no problem subscribing to 2 lists07:40
ograi dont see the need for a ML yet....probably later07:40
dredger ok.07:40
dredg1. irc is not convenient for everyone07:40
tsengdholbach: the problem is, everyone subscribes to 2 lists, which isnt always convenient07:40
tritiumdholbach, once I return to my job, IRC will not be an option for me.07:40
dredg2. users is very high volume. very very very07:40
tsengand those who are unaware miss out07:40
herveas for now, MOTU mails must to -devel?07:40
tsengherve: thats the question.. what are MOTU mails?07:40
ogradredg: since users is dedicated to universe, we should read it anyway (at least i do that)07:41
ograherve: devel mails must to devel, yes07:41
dholbachwell.. ok... atm we dont seem to have the need for it... we collect pros and cons on the wiki and discuss it in two months, ok? :-)07:41
dredgogra: right. i get 500+ mails/day for mailing lists associated with my job. i killed my sub to users cos i'd end up with thousands of unread mails07:41
janidredg, consider reading though gmane07:41
janiso you don;'t get you inbox flooded07:42
ograin my definition motu mails are devel mails or administartive motu stuff...07:42
Mithrandirjani: the problem is the volume.07:42
Mithrandirjani: and gmane doesn't solve that07:42
=== herve_ [~herve@mutualite-3-82-67-67-10.fbx.proxad.net] has joined #ubuntu-meeting
dredgjani: oh, and i hate web interfaces :)07:42
tsengI admit that ive also unsubbed from -users07:42
janimithrandir: you only pick the subjects you care about ;)07:42
tsengit wasnt useful for me to have it pile up unread07:42
dredgjani: especially for something that is not web based07:42
janigmane through thunderbird ;)07:43
ajmitchdredg: use nntp then07:43
janiof course not the web07:43
janinntp that's what I implied but not said actually07:43
herve_I do read lists over gmane.org07:43
ajmitchthat's how I read it07:43
ografor me -users is a big pool of things that are needed....there are te suggestions what is missing, and we are the guys to solve the missing bit, since we are more free then the main crew07:44
janisince I switched to nntp I can follow a lot more lists07:44
herve_it's far better than regular mail or Web forums (*sigh*)07:44
dholbachok... shall we re-discuss it in 2 months?07:44
=== herve_ is now known as herve
Mithrandirjani: my news reader and mail reader is the same, so it doesn't matter.  -users is too high-volume for a lot of MOTU to follow it.07:44
hervedholbach, in 2 month, Malone will have changed things, moreover07:45
dholbachok07:45
ograherve: and currently we are about 10 motus...so i still see no need for a own ML07:45
ograsince amloe will change a lot07:46
dholbachok07:46
ogramalone even07:46
ogralets reschedule the task for times we are 50 MOTUs or more 07:46
herveogra, it's also for all packagers, not just the reviewers07:46
dholbachok07:47
dholbachconclusion is: there are an awful LOT of things to decide now, because we will grow... i will set up wikipages soon to collect ideas and to re-discuss things. i'd appreciate it, if you'd add your ideas, too.07:47
hervewhat topic are left? (I must go soon)07:47
ogranone, 07:47
ajmitchherve: that was the last on the page07:47
ogra...07:47
hervegood!07:47
herve:-)07:47
ajmitchI think we just need to argue about the next meeting time :)07:47
ograso about the next meeting07:47
herveI can't leave you then07:48
ograas i asked in the beginning, how often should we hold this07:48
herveI'm not very productive with my cough anyway07:48
ogramonthly ? 07:48
tsengmonthly.07:48
dholbachyeah07:48
janiok07:48
ogranext time an hour later ?07:48
dholbachnice :-)07:48
ogra(for Treenaks )07:48
ajmitchmonthly07:48
dholbachand poor ajmitch 07:48
Treenaksogra: uh that's OK07:48
=== herve [~herve@mutualite-3-82-67-67-10.fbx.proxad.net] has left #ubuntu-meeting ["Leaving"]
ajmitchheh07:49
ograagain on Thursday ?07:49
ajmitchok07:49
ograok, next meeting will be on march 31 2005 17:30 utc07:49
ografour weeks from now...07:50
dredgcool07:50
dholbachvery nice07:50
ajmitchjust before hoary release?07:50
Treenaksajmitch: why not :)07:50
ograi'll write a summary and send it to -devel and -users07:50
dholbachthanks ogra, thank you very much07:50
dredgOT: does anyone know of who is in the list of 'strongly signed' keys?07:50
ograexpect it in half an hour07:50
ajmitchTreenaks: as long as we can have a release party as well ;)07:50
ogradredg: everyone you find on the keyservers07:51
dredgi need to arrange to get my key signed, even if i have to fax my passport and drivers licence to another country07:51
ajmitchdredg: most people with a GPG key who are involved in debian or ubuntu :)07:51
ogradredg: (signed that is)07:51
ajmitcheg any DD07:51
ajmitchnearly any07:51
ogradredg, http://keyserver.mine.nu/07:51
dredgajmitch: right. i note the lack of any strongly signed keyholders in ireland :)07:51
=== ajmitch takes a look
dredgthough hmmm07:51
Treenaksogra: not subkeys.pgp.net?07:51
ograTreenaks: works too :)07:52
ajmitchdredg: I see 5 DDs in ireland07:52
dredgajmitch: eh?07:52
ograso thank you for everybody attending here...meeting is closed07:52
ajmitchdredg: see db.debian.org07:52
ajmitchogra: thanks07:52
dholbachthanks ogra, again :-)07:53
tritiumthanks :)07:53
=== tritium [~tritium@12-202-90-180.client.insightBB.com] has left #ubuntu-meeting ["Leaving"]
=== Nafallo [~nafallo@h101n1c1o1027.bredband.skanova.com] has left #ubuntu-meeting ["Lmnar"]
Kamiondredg: the strong set's pretty trivial to get into07:55
Treenaksyeah, ask #ubuntu-nl :P07:55
janikamion, not in romania apparently ;(07:56
janiby all07:58
=== jani [~jani@iv.ro] has left #ubuntu-meeting []
=== dredg [niall@malkovich.office.blacknight.ie] has left #ubuntu-meeting ["Leaving"]
=== pitti [~martin@box79162.elkhouse.de] has left #ubuntu-meeting []
=== maskie [~maskie@196-30-108-208.uudial.uunet.co.za] has joined #ubuntu-meeting
=== ..[topic/#ubuntu-meeting:ogra] : 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. || Thursday 31 March 2005 17:30 UTC http://www.ubuntulinux.org/wiki/MOTUMeeting || This is NOT #ubuntu, nor #ubuntu-devel
=== sabdfl [~mark@host217-37-231-28.in-addr.btopenworld.com] has left #ubuntu-meeting []
=== zul [~chuck@198.62.158.205] has left #ubuntu-meeting ["Leaving"]
=== dholbach [~daniel@pD9E64BD5.dip.t-dialin.net] has left #ubuntu-meeting ["Verlassend"]
=== Mithrand1r [~tfheen@vawad.err.no] has joined #ubuntu-meeting
=== bradb [~bradb@modemcable206.155-81-70.mc.videotron.ca] has left #ubuntu-meeting ["Leaving"]
=== pitti [~martin@box79162.elkhouse.de] has joined #ubuntu-meeting

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