/srv/irclogs.ubuntu.com/2005/08/09/#ubuntu-meeting.txt

dholbachthat's why i'd like to introduce another idea for solving this: in my opinion what makes a transition a good one, is a good plan12:08
dholbachso having somebody responsible for a task who keeps an eye on it, is more important12:09
\shwhen there are more work then in normal times (breezy is not really normal)12:09
dholbacha aalib transition manager or something12:09
dholbachfor example12:09
\shs/are/is/12:09
siretartdholbach: this would my my suggestion/expectations from the teams12:09
dholbachthe c++ transition was a good example for this - our beloved doko did an awesome job in planning this12:09
bddebiandholbach: That's mor along the lines of what I was thinking12:09
\shthen we should split up our strength, and say ok, 5 members here, 5 members there and 5 members are doing something else also important12:09
siretartdholbach: having a lead and interested people for a specific topic which need to get done12:09
siretartthe lead should have an overview and be able to explain what is going on12:10
dholbachabsolutely12:10
dholbachwrite a nice wiki page, with notes about the transition and a list to tick things off - and pushes people into it, creates some party atmosphere behind it all :)12:11
Seveasthis sounds just like the way tasks are planned already in ubuntu: One lead, perhaps a second and a bunch of worker drones12:11
ajmitchdholbach: sounds good, just like what you did for hoary ;)12:11
bddebianSeveas: Where is this happening?12:11
dholbachajmitch: thanks for the flowers :-p12:11
Seveasbddebian, http://udu.wiki.ubuntu.com/UbuntuDownUnder/BreezyGoals12:12
ajmitchbddebian: breezy goals, lead & seconds were assigned at the kickoff meeting12:12
\shactually, I don't like the lead stuff for those works12:12
bddebianSeveas: Ah, nice12:12
dholbach\sh: they're not supposed to do the work all themselves12:12
\shdholbach: right..but this I don't mean...12:13
dholbachah ok... maybe i got you wrong12:13
ogra\sh, you need a point of contact... someone who is responsible and trys to coordinate a bit12:13
ajmitchyou want more of a coordinator12:13
\shok, we have some good members working on sources..the others are working as good reviewers..so everybody has their own field, right?12:13
dholbachi'm not quite sure, if all the stuff doesnt really go hand in hand12:14
dholbachi mean reviewing and fixing is all about fixing source packages :)12:14
\shso if there is a lot of "source" work to do, those members will help in the transitions, while the others are doing review or new motu trainings etc.12:14
ograyes, both teaches you a lot... you shouldnt do one without the other12:15
\shthe rest of the time, it will stay like normal work...merges, new uploads, sourcework, review, training at the same time and everybody is helping12:15
siretart\sh: hm. so you want to make people concentrating on one specific topic?12:15
siretartI just try to understand you12:15
\shsiretart: yes...in busy times like these days e.g.12:15
ograsiretart, that would be desirable, but happens anyway imho12:15
bddebianPlease don't take this the wrong way but are there people concentrating on training new MOTU's?12:16
\shogra: but u have to see, like those merges now, if we would have this work in our eyes, we wouldn't be in a hurry and we wouldn't be in this situation far away from the timetable12:16
crimsunbddebian: we should all be assisting each other.12:17
siretartbddebian: let's discuss this later, ok?12:17
ograbddebian, depending on your questions, yes12:17
=== tseng [~tseng@tseng2.ath.cx] has joined #ubuntu-meeting
bddebiansiretart: ok12:17
ograhey tseng 12:17
tsenghi12:17
\shtseng: welcome12:17
bddebianwelcome tseng 12:17
dholbachhey tseng :)12:17
siretarthey tseng, how are you?12:17
ajmitchmorning tseng 12:17
tsengi will be just watching I think12:17
dholbachtseng: https://wiki.ubuntu.com/MOTUMeeting - first point12:17
ogra\hif everybody had looked at the merge stuff first, we wouldnt have had 250 pkgs there12:17
dholbachbddebian: i hope i'll be able to do more on this front in 4 weeks12:18
ogra\sh, even12:18
dholbachogra: yes, that's why i suggest some leads organizing the different motu actions12:18
bddebianLike I said, don't take that the wrong way.  Everyone has been very helpful, I just don't see a specific "direction" so to speak.12:18
\shogra: that's what I meant...we had our eyes on something else as prio 1, and forget about those merges12:18
ogradholbach, nope, its a process we must establish... 12:18
ajmitchogra: yeah, I started doing some merges right at the beginning of the breezy cycle with my list12:18
ajmitchogra: but quickly ran out of spare time12:19
dholbachogra: a process like what?12:19
\shajmitch: so did I during the cxx trans12:19
ograif you touch a package with -ubuntuX version you should always look for mergers first12:19
comadrejawhat about this as a middle point. Somebody dispatching tasks on a "do-it-if-you-can" way ?12:19
siretart\sh: the problem I have with this suggestion is, that I have different interests for breezy, and I try to accomplish them all. So focusing on one topic would mean choosing one topic I'd like to accomplish12:19
ajmitchogra: that will reduce forking from debian12:19
dholbachogra: ah ok yes12:19
comadrejalike writing a wiki page 12:19
ogradholbach, if we do the merges constantly, we dont have this many12:19
dholbachogra: absolutely12:19
dholbachcomadreja: you mean as in assigning jobs?12:20
\shsiretart: actually we all have "different" interessts ... I'm far from being finished with my projects I wanted to accomplish12:20
ograajmitch, yes, exactly... it will still be a fork, but the changes are smaller12:20
crimsunTo be fair, though, several MOTUs have been busy otherwise (tritium, dholbach, and myself at least). As I see it, the problem isn't so much one of "we spent too much time doing non-merge stuff" but "we didn't have time at all".12:20
comadrejadholbach : like in writing in a wiki page a priority list12:20
dholbachcomadreja: ah ok, i see12:20
ajmitchogra: well we have to try & keep as close to debian as possible to avoid work for us12:20
ajmitchwe have to be naturally lazy! ;)12:20
\shcrimsun: this is something u will always have for volunteer work12:20
ogracrimsun, did you look for every -ubuntuX package you touched at MOM first ? 12:21
comadrejathat way, every single motu can use their time on that...12:21
tsengi dont like MOM12:21
\shcrimsun: even ogra is too busy to deal with motu stuff right now...12:21
dholbach\sh: do you think planning will be easier, if somebody signs up for such a task force?12:21
crimsunogra: yep, that's how I've been getting back into the MOTU swing of things.12:21
\shdholbach: I think it could help...some things are really showstopping us, right, and other things are just slipped out of our hands12:21
ogracrimsun, ah, great ten... i didnt and was hit by it...12:21
ogras/ten/then12:22
ograand many others of us too...12:22
dholbachwho else thinks that a recruited taskforce will make planning easier?12:22
bddebiantseng: Agreed, it does have it's limitations12:22
ograsome packages from MOM were already touched in the Cxx transition for example12:22
comadrejadholbach : we first need a scheduler :)12:22
dholbachcomadreja: of course, we need the plan first12:23
comadrejaI'll join \sh12:23
\shdholbach: if we have a fighting plan (for breezy+1), we know what transitions have to be done, on what we have to have a closer look (MoMs) etc. then we don't need a taskforce for those things12:23
dholbachto cap it up a bit: we agreed that we need more planning and maybe guys responsible for that, we too agreed, that we rely on volunteers work12:23
=== sistpoty2 is now known as sistpoty
dholbach\sh: some things just happend and you can't foresee them, because you're not involved with libxyz's upstream12:24
ogra\sh, note, there will be no X and no Cxx transition...12:24
siretart\sh: Can you describe what you expect a taskforce to look like? what would be expected from ppl joining a taskforce? give an example12:24
\shdholbach: things like Xorg yes..but this is ok..this will halt everything12:24
ograbreezy+1 will be an awesome development cycle12:24
dholbachyeah... let's get back to the TASK FORCE concept planning12:24
\shogra: we will have many bugs for breezy+112:24
ajmitchbreezy+1 is going to be different, in that main will be supported by the ubuntu foundation for *5* years12:24
ajmitchwe need to try & get quality up12:25
ogra\sh, yes, but a lot less mass transitions and thus a lot more time to play and develop12:25
ajmitchogra: more recruiting! :)12:25
ograyay !12:25
\shogra: breezy+1 will be polishing our work now...breezy will  be a desert safari ,-)12:26
\shok...long story short...12:26
dholbachok, who wants to make a suggestion that goes  beyond  "more organization"12:26
bddebianThen you need to either recruit folks that are familiar with hacking/Debian packaging or get some better direction for the NewMOTU process12:26
=== bddebian ducks
ajmitchbddebian: fine, put your suggestions down somewhere :)12:26
siretartajmitch: I think I have an suggestion for NewMOTU process, more on this later..12:27
dholbachok, as i see it there are 2 options12:27
ajmitchsiretart: great12:27
dholbach1) just try it out, whatever happens12:27
\shogra: u r involved in all that main stuff...I would like to take u as a "gateway" with main...to plan some important stuff to accomplish for breezy+1 so we can create something like a  "MOTU project plan"12:27
dholbach2) flesh out the process for such a task forces with all it's implications and go from there again12:27
crimsunWe could try each having a primary and a secondary "role", if you will. For instance, my primary role would be Mentoring new MOTUs, and my secondary would be Review work (aside from that done as part of mentoring). We could put this on our wiki pages.12:27
\shogra: just because u guys have a better overview what will come...and even 5 mins before it happens ,-)12:28
ogra\sh, sure, lets d that12:28
=== siretart likes that role concept
ogrado even12:28
dholbachok... shall we put up wiki pages up for those ideas and decide over them again?12:29
dholbachthis to me sounds like the best plan, since it is more detailed and more goal focused12:29
siretartdholbach: I second this suggestion. let's move on12:29
ajmitchyep12:29
\shlet's do it like that...12:29
dholbach\sh: thanks for bringing the point up - as you see - there are lot of opinions on that12:29
dholbachpoint two12:30
siretartbut may I suggest some procedure for new MOTU's?12:30
\shdholbach: yes...likley :) 12:30
siretartit is somehow related to that Team concept12:30
dholbachsiretart: fire away12:30
siretartI propose a mentoring concept for newMOTU's12:30
ogradholbach, why do we need to feed them, they give a grown up impression... they can gra it themselves12:30
ogragrab even12:31
siretarta bit similar to debian, but not quite. Each new candidate is assigned to one specific motu he uses as mentor12:31
dholbachogra: siretart wanted to add a new team idea in between12:31
tsengeh12:31
ograah,oh, ok12:31
tsengpeople move really fast in motu right now12:31
tsengbecause they can get help from everyone12:31
siretartthe apprentice and the motu aggree on a workflow how to get packages from the apprentice into universe12:31
\shsiretart: gentoo has this concept12:31
=== CarlFK [~CarlK@c-67-163-43-70.hsd1.il.comcast.net] has joined #ubuntu-meeting
siretartthis may or may not be using revu12:32
ajmitchtseng: they wouldn't be limited to this one person, but they'd be their primary contact12:32
=== ogra doesnt like the mentor concept at all
ajmitchogra: what's wrong with it?12:32
siretart\sh: I don't know how gentoo works, can you elaborate?12:32
ajmitchtoo much workload on existing motus?12:32
dholbachsiretart: what i like about the current process is it's openness12:33
ograit drags people more away into a secret corner... i see this with my google students, they arenot very active in the motu world, even if there are often people that could help them better then me12:33
\shsiretart: as u explained...when u want to get the dev status quo for gentoo, u need to have a mentor, which guides u through the whole infra structure and things like that, explains what is important in building ebuilds (in our case debian/*) etc.12:33
dholbachsiretart: so more people have a good image of how a motu hopeful proceeds12:33
tsengogra: right.12:33
ograit tears down the amount of work done with the whole tem12:33
ograteam12:33
siretartok. I see the point raised by dholbach and ogra.12:33
=== tseng still thinks gentoo is broken
dholbachsiretart: but this is a point we will have to discuss soon12:34
dholbachsiretart: you were right in bringing this up12:34
\shsiretart: but the other devs don't know the "apprentice" at this time...and most of the times, the new devs will do whatever they want...12:34
ajmitchright, you don't want the big happy family to be dysfunctional12:34
siretartI don't want to take the newbees into secret corners. they should work with the community12:34
siretartthe problem I want to solve is another one:12:34
=== ogra guesses after breezy+1, when we have lots and lots more people to manage
ajmitchas the team grows, we don't want new MOTUs to get lost in the cracks12:34
\shtseng: it's broken yes12:34
siretarthaving a mentor, an apprentice has a an advocate, which really know about the packaging skills of his apprentice12:35
\shtseng: but it's not against gentoo..it's against their governance :(12:35
dholbachwhat do you think about this: shall a motu-process2 team sit together and throw some ideas together and form a "spec"?12:35
siretartso this mentoring concept is rather a more formal process of having packages sponsored12:35
dholbachover which we can decide more formally?12:35
siretartdholbach: perhaps this would be an idea.12:35
=== kinjoo [~kinjoo@p54AA677A.dip.t-dialin.net] has left #ubuntu-meeting ["Verlassend"]
dholbachany other opinions?12:36
ajmitchdholbach: we might need to schedule another meeting soon then 12:36
dholbachyes12:36
siretartI'll try to write up my ideas on a wiki page and present them the next meeting12:36
ajmitchunless we do our debating on the wiki12:36
dholbachsuper, thanks siretart 12:36
dholbachit think it's better to have ideas more fleshed out, before we decide12:36
siretartthis won't be before next week ;)12:36
dholbachmay we get to point 2 now?12:37
\shyes12:37
ograsiretart, we meet once a month ;)12:37
ajmitchplease do..12:37
ogratake your time12:37
dholbachi proposed this one: "Proceedings of feeding UniverseNewPackages (and Andrew's RFP list) to utnubu-discuss."12:37
dholbachbecause i found that most of our NEW packages are not announced anywhere and just "end up in the archive"12:37
dholbachdon't you think we should push them more into the debian direction?12:37
ajmitchdholbach: agreed, very important12:37
ograwhy do we need to feed them, they give a grown up impression... they can grab it themselves lets just point them there12:37
ajmitchat the last meeting we resolved to file these RFPS12:38
dholbachthere were only SOME reactions RFP/ITP-wise from our side12:38
dholbachogra: yeah, but *nearly* nobody does it at the moment12:38
ograajmitch, now there is an active group in debian....12:38
dholbachso i think this should be more of a policy12:38
ogradholbach, what ? 12:38
ajmitchogra: I know, I see you're in the group12:38
siretartwell, I don't think that it would be very much efford announcing new addition to universe to the utnubu mailing list12:38
dholbachthat the package needs to be announced12:38
\shogra: u r involved in that utnubu thing12:38
dholbachsiretart: ++12:38
ajmitchI've got to get involved there too12:39
siretartand I think nometa and other debian developers would really appreciate it12:39
dholbach\sh, ogra: yes?12:39
=== ajmitch has been saying that for awhile though
\shogra: how is the mood towards ubuntu patches and new packages at all?12:39
ogradholbach, they have browsers eyes and are able to read... lets point them to the page and they can care themselves12:39
luis_could you create an rss feed from your current tools, and ask them to subscribe to that for timely/reliable info?12:39
ogra\sh, its ok... the tone is rougher...12:39
ograluis_, sure12:39
\shogra: rougher? 12:39
Seveasluis_, there are RSS feeds for Ubuntu uploads12:40
\shogra: in what way?12:40
siretart\sh: I think it is generally very mixed and depends whom you ask. the utnubu guys seem to be very colaborative.12:40
ograbut my opinion is that we have enough work to do here... putting this stuff on a wiki page for them is already nice and makes their job easier12:40
dholbachi think it's no problem for anybody to write a mail: "hey, this is my package, it's in the archive, if you have questions, feel free to ask me"12:40
ograbut in the end its *their* job12:40
dholbachogra: nobody does that either12:40
\shactually, I can tell only about my experiences with some maintainers...12:41
dholbachan RSS feed in my opinion is not much of a "relationship", although it's convenient12:41
\shand these exp. are really mixed12:41
ogradholbach, i dont know since when youre subscribed to -utnubu-devel, but they already have tools to produce theur lists12:41
siretartdholbach: this could be the last step of work of the reviewing team, if a package is accepted into universe, write a small mail for that. I think I could hack something up like that for revu2..12:41
dholbachogra: i read all the threads12:41
dholbachwho is opposed to add "announce it on utnubu" to our MOTUNewPackagesPolicy?12:42
ogradholbach, its their job as import team... its nice of us to offer them something, but i refuse to do their job12:42
dholbachogra: we're not going to make them debian compliant or uploading or do whatever to the debian archive12:42
comadrejadholbach : I also think it's their job12:43
dholbachok... any other opinions?12:43
ogradholbach, if there are problems with a particular package i'm happy to help if they ask... but still they want to be the ubuntu import team...12:43
dholbachi never thought we'd have that response to writing a mail12:43
\shogra: can u give me the subscription address for this utnubu-devel ML? i only see -discuss and -maintainers12:43
comadrejadholbach : that mail could be automated12:43
ogra\sh, its on alioth.debian.org12:44
ogra\sh, search for utnubu12:44
ogra\sh, i meant -discuss above, sorry12:44
\shogra: ah ok :)12:44
seb128dholbach: don't annonce stuff on utnubu 12:45
ajmitchogra: perhaps I should try & make it more part of my MOTU responsibilites then?12:45
dholbachok... we seem to cannot agree here and will rely on volunteer action12:45
dholbachseb128: it think it's ok to announce a new package there - do you think that's a problem or might make us run into problems?12:45
seb128it's not ok12:45
CarlFKI didn't see anyone opposed to the rss feed idea12:45
ograajmitch, i dont see it as a motu responsibility... i see itas a responsibility to make the info public available, but thats all12:45
seb128this project is not fine12:45
\shdholbach: I think with new packages not in debian they will come with RFP/ITP process...12:46
dholbachi think we can just offer12:46
siretartseb128: what are your objections to utnubu?12:46
dholbachogra: i was talking about making info public available, nothing else :)12:46
seb128ie: I don't want somebody to just take GNOME stuff from Ubuntu, to put them on the utnubu SVN and non maintain them from here12:46
seb128Debian expects some quality12:46
dholbachbut it might be a start of working together on stuff12:47
seb128if somebody wants to maintain a GNOME stuff with Debian he should rather work with pkg-gnome12:47
ogradholbach, you were talking about announcing it to utnubu, which may end in endless discussions... i dont like to waste my time with that12:47
siretartseb128: I think that was not nometa's intention12:47
seb128ie: with people interesting on that12:47
dholbachogra: announcing, not discussing details :)12:47
seb128s/interesting/interested/12:47
ogradholbach, you end up with this... see gparted... i dont see the last word spoken there12:47
seb128dholbach: that's not the place to announce, stuff12:48
seb128they will grab them12:48
dholbachogra: that's one case - you can't judge a project after 3-4 weeks12:48
seb128upload them here rather than at the right place12:48
ogradholbach, nope, i know...12:48
seb128and non-maintain them12:48
dholbachok, we had quite some interesting points here... :)12:49
dholbachok, looking at the time, we might hop over to point 3 - is that ok for you?  12:49
siretartplease12:49
seb128if somebody is interested to do the job for Debian he can do it correctly and join the appropriate team and working with thel12:49
seb128them12:49
seb128dholbach: go :)12:49
dholbachTrashing of MOTUNewPackages and MOTUToReview in favour of REVU12:49
dholbachthe pages are momentarily just lying around12:49
\shdholbach: when it's in the proper place on an own linode12:50
dholbachand nobody cares after them, some packages already got uploaded to REVU12:50
dholbach\sh: i'm solely talking about the wiki pages mentioned12:50
\shI will clean them up...on sunday12:50
\shdholbach: yes...12:50
dholbach\sh: we are discussing the point now :)12:51
dholbachdoes anybody feel we should keep them for a bit of time?12:51
siretart\sh: have you heard any news about the linode server?12:51
\shsiretart: no ... I will poke mdz or mako 12:51
\shor jane?12:51
dholbachor elmo?12:51
ogra\sh, rather elmo12:51
\shsomeone :)12:51
\shor elmo12:51
siretart\sh: great. I haven't had time the last weeks. next week I think I will have more time to work on revu12:51
dholbachok? anybody who wants to keep them to not annoy people who mentioned their package there?12:52
siretartI think I read that the common lisp team has packages for review there..12:52
siretartwhat about packages which are on the package, but not uploaded yet to revu?12:52
\shwhat about this: <h1>THESE PAGES WILL BE REMOVED IN THE NEAR FUTURE</h1> <h2>Please upload your packages to REVU</h2> on the first two lines?12:52
ograyep, thats there since a month12:53
tsengand email -devel12:53
\shyep12:53
dholbachyeah, we maybe should do that12:53
dholbachkeep them for a brief period of time12:53
dholbachand announce their disposal12:53
dholbachagreed12:53
dholbachrobitaille: are you there? point 4 is your point :)12:53
robitailleyes I'm here.  12:53
ajmitchbug squashing!12:54
dholbachintroduce us into the delights of malone assigning :)12:54
robitailleShould Malone bugs on Universe packages be assigned to MOTU members, or leave them unassigned?12:54
=== Treenaks [~martijn@messy.foodfight.org] has joined #ubuntu-meeting
ajmitchas an aside, we should have a bug squashing party ;)12:54
ajmitchrobitaille: assign them12:54
robitailleI have seen 2 positive feedback and one negative to the few I did recently12:54
ajmitchotherwise we don't see them12:55
siretart++12:55
tsengi have no attention in even looking at bugs that are mass assigned to me12:55
tsengjust one opinion12:55
ograajmitch, we have bugday every wednesday, since 2 months12:55
dholbachrobitaille: i'm for it as well12:55
tsengi have my own bugs12:55
ajmitchtseng: you're different, in that you mainly focus on mono12:55
tsengyes.12:55
ograajmitch, tseng is on the teamlist12:55
ajmitchogra: sure, but how often do people hear about that?12:55
ograso he gets the bugmails12:55
ajmitchogra: I know12:55
\shwell...we can assign them to the team and then can somebody pick up his favorite12:56
ograajmitch, you dont need to tell me that i suck as bugmaster ;)12:56
dholbachok, how shall we deal with this?12:56
robitailleand there are maybe 250-300 bugs on universe packages.  THat's could be a lot of traffic12:56
ajmitchogra: haha, I didn't mean that ;)12:56
ograajmitch, but i... i'd love to get rid of that job :)12:56
ajmitchogra: search for willing victims :)12:56
dholbachogra: can we add a mailing list for assigned bugs?12:56
dholbachogra: so we don't annoy people with millions of bug mails12:57
=== ajmitch spots luis_ hiding in the crowd
dholbachogra: i don't remember the last state12:57
ogradholbach, why dilys is posting every new bug in #ubuntu-bugs12:57
ograajmitch, yes, i saw him too :)12:57
dholbachogra: but i'm not on irc 24h12:57
ajmitchogra: irc isn't the best place for bug notification12:57
dholbachajmitch: ++12:57
ajmitchit's useful, for sure12:57
ograajmitch, dholbach dilys can be easily modified to feed to rss i guess12:57
ajmitchI've spotted bugs there & started on the fixing because of dilys12:58
robitailleI like the dilys announcements...a good way to do quick bug triage on the spot12:58
dholbachok, how can we have MOTUs in the MOTU team (for visibility), but not annoy them with sometimes useless bug mails12:58
ograsince she already entertains us with her prose :)12:58
dholbachok, don't we have a solution for that yet?12:59
ogradholbach, thats a question  to the launchpad team12:59
dholbacha mailing list for motu bug mails would be cool12:59
\shogra: how fast can dilys be changed for feeding rss?12:59
dholbachogra: i recall to already have asked the question - or maybe you did it12:59
ogra\sh, no idea... its not my baby12:59
=== ajmitch will have to find a decent rss reader then
\shajmitch: akregator ;)12:59
ogradholbach, i think kiko said its trivial iirc12:59
dholbachok12:59
ajmitch\sh: I said *decent* :)01:00
dholbachso we defer this question until we have a launchpad answer01:00
\shajmitch: ffox ;)01:00
siretartsistpoty: we need rss feeds for revu2 ;)01:00
ajmitch\sh: besides, I do a fair bit of work remotely01:00
dholbachis that ok with you?01:00
\shsistpoty: rss2 please with full comments ;)01:00
sistpotysiretart: ack ;)01:00
ogradholbach, yep... o with me...01:00
ograok01:00
dholbachok01:00
dholbachcommon REVU practices - there are two topics I can think of, which got discussed on REVU - maybe we should have a bit of bendable policy and an agreement here01:00
dholbach1)  config.{guess,sub} in the diff (relying on build hosts' build system vs. clean diff)01:00
dholbach2)  changing .ORIG.tar.gz (sorry, I'm a bit biased)01:01
dholbach:)01:01
\shaehm01:01
dholbachopinions on how to deal with that kind of stuff :)01:01
\sh1) i don't like copies of config.{guess,sub} in the clean targets of the rules...01:01
ograi thinkwe should hear a very experienced package for 1)01:01
ograpackager even01:01
siretartajmitch: how do you think about this topic, with your DD hat on ;)01:02
=== ajmitch hates having a messy diff
\shthey're messing sometimes the who diff.gz so I put them in the configure target before ./configure01:02
bddebianheh01:02
Riddell\sh: you mean removing copies in the clear targets?01:02
ajmitchsiretart: I've been a MOTU longer than a DD ;)01:02
\shRiddell: yep01:02
siretarthehe01:02
\shor the build management is so intelligent to remove those diffs from diff.gz01:03
ajmitchbut I don't like having a diff with that mess01:03
\shRiddell: and putting them in the configure target or config.sub01:03
dholbachi think there is clearly clearability of the diff  versus  relying on build systems' config.{guess,sub}01:03
dholbach(and we're talking about two files)01:04
Riddell\sh: what's wrong with removing it in debian/rules clean?01:04
siretartI see general agreement leaving config.{guess,sub} out for nicer .diff.gz (and therefore, better reviewability)01:04
ograRiddell, its about *adding* it there01:04
tsengthats a pet peeve of mine01:04
tsengi cant stand that stuff in the diff01:04
\shRiddell: dh_make templates is not removing them in debian/rules clean, they're copying it from build system01:05
\shRiddell: so the diff.gz or debdiffs are getting messy with this crap01:05
=== mdz [~mdz@ca-studio-bsr1o-251.vnnyca.adelphia.net] has joined #ubuntu-meeting
tsenghi mdz :)01:05
\shRiddell: it you move it from clean target to configure target u won't see them in the diff.gz or debdiff01:05
mdzI can't be fully attentive but if you have specific questions I can try to answer01:06
dholbachwe're trying to arrange a bendable agreement on point 5 of https://wiki.ubuntu.com/MOTUMeeting01:06
dholbach config.{guess,sub} in the diff (relying on build hosts' build system vs. clean diff)     and      changing .ORIG.tar.gz01:06
siretartmdz: the current topic is if config.{guess,sub} should be deleted in debian/rules clean target01:06
dholbachbecause the reviewers suggested different "solutions"01:07
mdzI am not a fan of updating those files during the build in the first place01:07
ograby default dh_make places the copying of these files in the clean target, that means i clutter my diff.gz totally... whats the rationale for that01:07
dholbachbe back in a minute01:07
Riddell\sh: so move the  rm -f config.{guess,sub} from debian/rules clean to debian/rules configure?  how it that more elegant?01:07
\shRiddell: it's not about rm -f config.{guess,sub} it's about cp -f /usr/share/misc/config.{guess,sub} $(CURDIR) in clean target01:08
ograRiddell, its the cp that puts them into your sourcetree, not the rm....01:08
seb128just use cdbs :p01:09
ajmitchseb128: sadly we can't convert the world to cdbs :)01:09
bddebianWhy not? ;-)01:09
mdzdoing a build and then cleaning the tree should give you back the same tree you started with01:09
ograit is done in the clean target by default, while it could be done with a build-dep on autotools-dev which makes sure the fils are the most recent and saves space in the diff01:10
ajmitchmdz: isn't that part of the automated testing spec?01:10
dholbachthe readability isnt such a big point when you're talking about two files, is it?01:10
mdzajmitch: possibly?01:10
mdzso if 1) you are updating config.* during the build, and 2) the build is being done in-tree, then you need to restore the files, not delete them01:11
ogradholbach, if you make only a dependency change the difference is *huge*01:11
ajmitchI think pitti was talking about that, but that's another matter01:11
mdzthat is what cdbs does, I believe01:11
dholbachogra: and you rely on the build system's config.{sub,guess}, which is the whole point of copying them in before, NOT relying on the build system, but on your patch01:12
siretartso the approach dh_make uses is broken?01:12
mdzdh_make is broken in all sorts of ways01:12
sistpotysiretart: i think so... at least the templates that come from it (iirc)01:12
\shok...01:12
\shthis is an example01:13
ogradholbach, but since they carry the descriptions of supported arches etc, i dont see the point not to take them from the build system... they'll match the build system... and in my eyes they are part of the tools, not of the source01:13
\sh        -test -r /usr/share/misc/config.sub && \01:13
\sh          cp -f /usr/share/misc/config.sub config.sub01:13
\sh        -test -r /usr/share/misc/config.guess && \01:13
\sh          cp -f /usr/share/misc/config.guess config.guess01:13
\shin clean target before dh_clean01:13
dholbachshall we take this question to the mailing list and proceed to the next one? :)01:14
\shso debuild is calling debian/rules clean first, copies the build systems config.{guess,sub} to the $(CURDIR) and messes the diff..this is what dh_make gives u as template...and many packages are using it01:14
dholbachoh sorry, \sh wanted to say something01:14
\shexample: atlas-cpp01:15
dholbach\sh: it doesnt "mess" for the sake of it01:15
siretartfrom the discussions we had, I'd consider that pattern in debian/rules broken01:15
ajmitch\sh: right, cdbs has a fair bit of stuff in /usr/share/cdbs/1/rules/buildcore.mk & other files for handling this01:15
ograme too01:15
dholbach\sh: it's there for a good reason - even lintian complains about too old config.{guess,sub} for a reason01:15
siretartit fails to restore the package state01:15
=== Treenaks [~martijn@messy.foodfight.org] has joined #ubuntu-meeting
ogradholbach, but it describes the capabilitys of the build tools, so why not use the ones from the actual build system01:16
\shdholbach: i don't mind to copy that stuff..but not in the clean target, cause the diff is generated after debian/rules clean 01:16
dholbach\sh: if you copy it in, it will always be in the diff01:16
ogradholbach, it will be always new in every diff...01:17
\shdholbach: not if the tree is cleaned correctly...it copies the stuff only, when config.{guess,sub} is not in place01:17
ogradholbach, which is a total waste01:17
seb128these file are updated because that's required to build on some archs01:17
\shbut it's build time..not cleaning time...01:17
dholbach(especially for all those packages in debian that weren't touched for like two decades.... :))01:18
\shso it should be in those parts where the build is done..and not where the build stuff is cleaned up01:18
dholbachbut then you don't have control over what you upload, you rely on the build hosts config.{sub,guess}01:18
ograseb128, yes, but why not updating them on the actual build system they use... i.e. at buildtime...01:18
seb128that's what cdbs does01:19
seb128dholbach: you don't want to use your version, autotools-dev has the reference versions known to work01:19
\shseb128: that's what I said...put this piece of code in debian/rules configure target before the ./configure call...01:19
ograah, so my doing isnt wrong then :)01:19
ajmitchogra: no, that's what we're arguing about ;)01:20
mdzthe best solution would be to modify autoconf, upstream, to use the newer of the installed file and the one shipped with the package01:20
dholbachseb128: i want to use the version, i have locally on my disk, which procudes my diff :)01:20
mdzthen this problem goes away entirely01:20
seb128dholbach: why? 01:20
mdzit's the way it should have worked in the first place01:20
ogradholbach, that might be outdated at buildtime...01:20
mdzI suggest proposing that to the upstream maintainer with a description of our situation01:21
ograok...01:21
dholbachmdz: which upstream?01:21
dholbachmdz: every single one of each package?01:21
ograany objections when we go on to use the ones on the buildd until thats fixed ?01:21
mdzdholbach: autoconf upstream, as I said01:22
dholbachmdz: ah ok01:22
dholbachmdz: thanks01:22
dholbachok, seems like we should proceed to the next time :)01:23
bddebianAre we making any decisions? ;-)01:23
dholbachwhat do you all think about chaging orig.tar.gz?01:23
ograbddebian, thats rare in motu meetings... 01:23
ajmitchdholbach: I don't like it01:23
ogra;)01:23
ograme neither01:23
\shbddebian: yes we're contacting the autotools (god) upstream maintainer ;)01:24
ajmitchdholbach: and it should only be done where really really necessary01:24
seb128don't touch the orig.tar.gz01:24
dholbachi know cases of packaging cvs exported stuff, where a ./autogen.sh && make dist is in order01:24
ajmitchexceptions are license issues, where you have to cut out undistributable source01:24
dholbachbut that's all i'd allow policy-wise01:24
ograseb128, what do you do with cvs checked out stuff... dont you remove the CVS dirs ?01:25
\shdholbach: why don't u call ./autogen during build time? ,-)01:25
dholbachogra: cvs export01:25
ajmitchogra: do that in debian/rules01:25
dholbach\sh: you don't do that :)01:25
seb128ogra: I use "make dist" which makes a proper tarball01:25
Riddellchanging .orig.tar.gz is fine for removing upstream debian/ directories01:25
seb128no01:25
\shdholbach: for cvs stuff of course...cause the original tarball is cvs exported...01:25
siretartdebian policy suggests the target get-orig-source01:26
siretartThis target fetches the most recent version of the original source package from a canonical archive site (via FTP or WWW, for example), does any necessary rearrangement to turn it into the original source tar file format described below, and leaves it in the current directory.01:26
seb128replacing the debian/ dir can go to the diff.gz01:26
dholbachseb128: ++ even if it looks ugly01:26
seb128it's not ugly01:26
dholbachseb128: in the diff - and i don't care about that :)01:26
dholbachseb128: i'm not opposing01:27
seb128k :)01:27
seb128-- other way :p01:27
dholbachbut it's very hard to check hwo the source was altered01:27
dholbachand i ALWAYS do that when reviewing packages01:27
dholbachand you should imho do that too01:27
ajmitchmy debian sponsor told me off for repacking the orig tarball :)01:27
=== siretart would rather prefer the wig and pen format, I how this will be allowed soon in the archive
ogradholbach, please... indeed everybody does that :)01:27
dholbachin that perspective chainging orig.tar.gz is not very nice01:27
dholbachogra: yes?01:28
ogradholbach, sure... at least every reviewer i know around here01:28
RiddellI've also had tar files which are badly made upstream and arn't distcleaned, that should be tidied for .orig.tar.gz in my opinion01:28
dholbachogra: i never did see such a comment on REVU expept my own :)01:28
ogradholbach, you need to be more around on IRC ;-p01:29
ajmitchthere is the other exception - cdbs & tarball.mk01:29
seb128if upstream tarball is not nice speak with upstream to get that fixed01:29
dholbachRiddell: i think it's more important to lart upstream and get it fixed in the diff :)01:29
\shthe question is, when you generate a CVS/SVN snapshot..is it a real orig.tar.gz or should we handle it in some other way01:29
tseng\sh: look at evolution-sharp01:29
seb128dholbach: exactly :)01:29
tsengevolution-sharp_0.6.99+0.7.orig.tar.gz01:29
\shtseng: u made a diff from 0.699 to 0.7...01:30
dholbachsiretart: i never heard of that target before - i'll have a look into it, thanks for the pointer01:30
\sh?01:30
tsengno, i made a snapshot of the 0.7 branch01:30
siretartdholbach: it is an optinal target, though. But mentioned in debian policy, so I'd consider that as semi official target01:31
\shtseng: and u called autogen.sh and created your own tarball?01:31
dholbachsiretart: i'll look into it :)01:31
tsengautogen and make dist01:31
ajmitch\sh: that's a standard way to do it01:31
ajmitch\sh: since there is no existing tarball01:31
siretartdholbach: section 4.801:31
dholbachcvs exports are an exceptional case i think01:31
ogradholbach, isnt that what the debian/watch file is for ?01:31
RiddellI also change .orig from tar when using unsermake but upstream has made the tar for automake01:31
seb128all the changes can go to the diff.gz01:32
Riddellseb128: that makes for a muckle .diff.gz01:32
ograseb128, s/can/should01:32
dholbachwho took notes for PackagingTips?01:33
ajmitchok, so do we have any agreement here?01:33
Riddelland some changes can't go in .diff e.g. removing files01:33
ograRiddell, sure they can01:33
=== ajmitch wants to get this meeting wrapped up :)
\shtoo many ways are leading to mekkah01:33
Riddellogra: removing files can't, means you need to add explicit rm -f  lines to debian/rules01:34
bddebianheh01:34
ograajmitch, bah, youre just volunteering for a review day master job and cant wait... be patient !01:34
dholbachi think it's crucial, to encourage new motus to work tidily, to just grab upstream's tarball, apply their changes to it and not let them rip out what they want to make something "easier"01:34
ograRiddell, and ? 01:34
Riddelltidier and less error prone to just fix the upstream tar for the .orig01:35
siretartsorry folks, I need to leave now. See you tomorrow01:35
\shcu siretart 01:35
bddebianLater siretart 01:35
sistpotygn8 siretart01:36
ajmitchogra: oh sure, it's my wildest dream ;)01:36
ogra;)01:36
dholbachthe problem as i see it, is: it's harder to track what people did to the code, people from other distributions/other developers have no clue, what they did to upstreams code, in my eyes it might even lead to security - imagine a new motu uploading a "modified" upstream source - you'd just read .diff.gz and not recognize what happened01:37
ograRiddell, but breaking a holy rule :)01:37
\shdholbach: changing upstreams code only via patch in debian/rules patch 01:37
dholbachbye siretart 01:37
seb128dholbach: md5sum should match upstream one01:37
ajmitchdholbach: I agree, someone reviewing should ideally be able to grab the tarball off upstream's site, confirm md5sum is what you have, and use it01:37
dholbach\sh: that's what we're talking about01:37
tsengim not sure why we even need to talk about this :)01:38
dholbachseb128: that's what i'm saying: never change the upstream orig.tar.gz :)01:38
tsengit seems obvious.01:38
dholbachajmitch: that's what i do01:38
ajmitchtseng: it is obvious, but not everyone does it01:38
\shdholbach: but this is the rule ;) 01:38
dholbachok, then we can all agree on pushing people to lart upstream, if the code/buildsystem is buggy and fix it in .diff.gz, right?01:38
seb128yep01:38
dholbachsuper01:39
tseng++01:39
dholbachi love you guys01:39
dholbachlast point on the agenda01:39
=== seb128 hugs dholbach
dholbachajmitch: do it! :)01:39
dholbachseb128: :))))01:39
\shdholbach: this is what we're doing all the time..fixing stuff from upstream via patch/dpatc01:39
\shh01:39
ajmitchdholbach: why me? ;)01:39
ograyeah, ajmitch for REVIEW MASTER !!01:39
dholbachajmitch: it's your point01:39
bddebian++01:40
ajmitchok, I'm not applying for ReviewMaster, but we need to review *more*! :)01:40
Riddelldholbach: I trust you'll inform debian's ftpmasters of that policy then01:40
\shajmitch: come on...push us ,-) 01:40
ograajmitch, to late... you got the job now :)01:40
ajmitchdholbach's enthusiasm for review days is great01:40
ajmitchso I think they need to be a regular part of our calendar01:40
ajmitchand we need to keep the list as short as possible01:40
ajmitchof course, feel free to do reviewing at anytime you can01:41
ograajmitch, dholbach will soon have a new job that draws his time.... dont expect him to be much more active then me01:41
ogra(in motu land)01:41
dholbachRiddell: i think we established reasons for doing it that way01:41
ajmitchogra: yeah, don't expect anyone here to have lots of free time01:41
ograajmitch, and since you brought it up .... :)01:41
ograajmitch, i dont ...01:41
ajmitchlooks like I've got another cap then?01:41
dholbachogra: you seem to know more than i do01:42
ajmitchdholbach: sure, you'll probably find out about your job responsibilities the day you start (or later) :)01:42
dholbachi always had review days in mind like a measure to catch up on the always growing lists01:42
\shok...last point now...last cigarette01:42
ogradholbach, just guessing from experience01:42
ogra;)01:42
dholbach\sh: i have no papers left01:42
ogradholbach, next meeting date and time01:42
ajmitchreview days are a good time to make sure that the new guys are around to talk to01:43
dholbachi hope we'll find a way to get them sorted soon01:43
dholbachajmitch: yeah that's true01:43
ajmitchogra: 2 weeks or 4?01:43
dholbachok... when will be next 1) review day 2) motu meeting?01:43
ograwe had said 4 once01:43
\shogra: between the last one and now were only 2 ;)01:43
ograbut if itsrewuired, we should change it01:43
ajmitchdholbach: next review day in 2 weeks01:43
\shas I remember01:43
ogra\sh, the last one was postponed 2 weeks01:44
ograso it were actually 601:44
ajmitchby 'day' we mean a 48-hour period or more :)01:44
dholbachajmitch: ok, i'll do an announce - august 18th?01:44
\shogra: oh yes01:44
ajmitchdholbach: sounds good01:44
dholbachok, next review day august 18th01:44
\sh2.9 + 14 days?01:44
ogradholbach, calendar ? 01:44
dholbachnext motu meeting when?01:44
\sh1601:44
\shfits01:44
dholbachogra: i'll do it01:44
ogragreat...01:44
dholbachso when will it be?01:45
dholbachwhich time?01:45
dholbachthe motu meeting01:45
ograthis current meeting isnt mentioned... we are lost without your care dholbach 01:45
ajmitchdholbach: 3 weeks? :)01:45
ajmitchdoes this time of day suit people?01:45
dholbacha bit earlier :)01:45
ajmitchok01:46
dholbachogra: it is01:46
ograiwouldnt say it suits, but better then 6:00 UTC 01:46
ajmitch20:00 UTC?01:46
bddebianAye01:46
bddebianajmitch: 20:00 is good01:46
dholbachyeah01:46
ajmitchgreat01:46
comadreja++01:46
dholbachwhich date?01:46
ajmitch8am for me, not too hard :)01:46
ogradholbach, since when, i imported the calendar yesterday 01:46
=== \sh is not available from 29th august to 12th septembre
ajmitchdholbach: 3 weeks from now is the 24th01:46
ajmitchif you want it that soon01:46
ajmitchwe've got a few things for the agenda already01:47
dholbachok01:47
ogradholbach, haha... 4th 00:00 *g* its there since ~2h it seems, sorry for the noise01:47
dholbachogra: 3rd 22:00 utc01:47
ogradholbach, my evo translates the TZ to localtime :)01:48
dholbachah ok01:48
dholbachok01:48
ograso it shows up for the 4th01:48
dholbachone last thing: who will do a quick wrap up for the mailing lists?01:48
dholbacha quick one01:48
ograi already missed the last one...01:48
dholbachi won't have the time this time01:48
=== bddebian needs to check out some mailing lists apparently
ograme neither 11th is feature freeze01:49
\shbddebian will do it ,-)01:49
=== ajmitch won't have time until saturday for summaries
dholbachi'll do the announces of the next meetings/review days - thanks everybody - you guys rock! :)01:49
ajmitchdholbach: great, thanks01:49
bddebian\sh: Sure pretty easy.  "No decisions were made"01:49
=== bddebian hides
ograbddebian, volunteering to write a wrap up ? 01:49
ajmitchso who will summarise? bddebian, or shall I volunteer? :)01:49
=== dholbach hugs bddebian
\shbddebian: ;) http://people.ubuntu.com/~fabbione/irclogs/01:49
ograbddebian, thanks :)01:49
dholbachjust describe the points on the agenda and 2 sentences on what we decided/discussed :)01:50
ajmitchlooks like it's been decided for poor bddebian 01:50
bddebianAye, wtf? :-)01:50
ajmitchbddebian: I can do it if you prefer01:50
ajmitchbut it will take a couple of days for me to get to01:50
\shbddebian: actually u r a native speaker...so when I will write all this...damn my english teacher will kill me ,-)01:50
dholbachgood night :)01:50
ajmitchnight dholbach 01:51
\shajmitch: let bddebian do it ;)01:51
bddebianajmitch: I wouldn't mind but between not being an MOTU nor being on the ML, maybe you should?01:51
bddebiangnight dholbach 01:51
sistpotynight dholbach01:51
\shbddebian: u will write...and I will post01:51
comadrejanite01:51
\shcu guys...01:51
ograciao dholbach 01:51
\shgood night even :)01:51
mbreitgood night...01:51
\shbddebian: deal?01:51
bddebian\sh: deal01:52
=== macgyver2 [~eric@macgyver2.user] has left #ubuntu-meeting ["Leaving"]
\shbddebian: ok :)01:52
ajmitchalright..01:52
ograbddebian, http://lists.ubuntu.com/archives/ubuntu-devel/2005-March/005093.html01:52
bddebianCan I hit it tomorrow morning, my time?01:53
\shbddebian: and u'll find the logs of this meeting on http://people.ubuntu.com/~fabbione/irclogs/ so u know what to summarize01:53
=== sistpoty is bigger than bed now
\shbddebian: yes01:53
ograbddebian, you can hit it every time you like...01:53
bddebianheh01:53
sistpotygn8 everybody01:53
bddebiangnight sistpoty 01:53
ajmitchnight sistpoty 01:53
=== \sh has only 4 hours left to sleep :(
bddebianGo to bed :-)01:53
\shwill do right now :)01:54
=== ajmitch still has an afternoon & more of work to get through
bddebianI gotta go play with the kids, catch you all later01:54
bddebianajmitch: Have fun :-)01:54
ograciao bddebian and thanks :)01:54
\shbddebian: play soccer ;)01:54
bddebianogra: np01:54
\shok...good night gentlemen :) cu later this morning ;)01:54
bddebian\sh: Aye :)01:54
bddebiangnight \sh01:54
ogra\sh, sleep well01:54
\shtrying to :)01:54
ajmitchsomeone can put the next meeting & review days on the calendar?01:54
=== ajmitch does it..
janimonosesgood night all01:55
=== janimonoses [~pet@Home03207.cluj.astral.ro] has left #ubuntu-meeting []
ajmitchhmm, will do after lunch, someone remind me then :)01:56
robitailleajmitch: I can do it a bit later when I update my ics file01:56
ograajmitch, dholbach said he would 01:56
ajmitchrobitaille: dholbach has it open for editing01:56
ajmitchso I'll leave that to him01:56
robitaillethese daniels are so good at updates... :)01:57
ograheh01:57
ograwhat would we dou without you :)01:57
ogras/dou/so01:57
ogrado01:57
ogragrrrr01:57
=== cyphase [~cyphase@ppp-69-233-164-189.dsl.pltn13.pacbell.net] has joined #ubuntu-meeting
cyphasehey everyon01:58
cyphaseeveryone*01:59
ajmitchhello01:59
ajmitchbye all02:00
robitaillecyphase:  looking for a meeting?02:01
Seveasrobitaille, this isn't a dating channel ;)02:05
tsengits not?02:08
=== ..[topic/#ubuntu-meeting:Seveas] : Calendar - https://wiki.ubuntu.com/Calendar | Logs: http://people.ubuntu.com/~fabbione/irclogs/ | 5 Aug 20:00 UTC: NUN http://wiki.ubuntu.com/NUNAgenda | 9 Aug 20:00 UTC: Tech Board http://wiki.ubuntu.com/TechnicalBoardAgenda | 11 Aug 22:00 UTC: Doc Team http://wiki.ubuntu.com/DocteamMeetingAgenda | 16 Aug 12:00 UTC: CC http://wiki.ubuntu.com/CommunityCouncilAgenda | 24 Aug 20:00 UTC: MOTU http://wiki.ubuntu.com/MOTUMeeting
=== azeem [~mbanck@proxy-out.lrz-muenchen.de] has joined #ubuntu-meeting
=== mako [~mako@bork.hampshire.edu] has left #ubuntu-meeting []
=== Seveas [~seveas@seveas.demon.nl] has joined #ubuntu-meeting
=== flint [~flint@209.246.42.100] has joined #ubuntu-meeting
=== joz [~mak@h66-201-246-249.gtcust.grouptelecom.net] has joined #ubuntu-meeting
=== Razor-X [~user@user-11fa9ie.dsl.mindspring.com] has joined #ubuntu-meeting
=== mdz [~mdz@ca-studio-bsr1o-251.vnnyca.adelphia.net] has joined #ubuntu-meeting
=== crimsun [~crimsun@sh.nu] has joined #ubuntu-meeting
=== robitaille [~daniel@d154-5-117-228.bchsia.telus.net] has joined #ubuntu-meeting
=== jiyuu0 [~jiyuu0@219.95.146.166] has joined #ubuntu-meeting
=== knuty [~knuty@182.84-48-114.nextgentel.com] has joined #ubuntu-meeting
=== mdz [~mdz@ca-studio-bsr1o-251.vnnyca.adelphia.net] has joined #ubuntu-meeting
=== direwolf [~direwolf@pcp0010121770pcs.crosky01.pa.comcast.net] has joined #ubuntu-meeting
=== direwolf [~direwolf@pcp0010121770pcs.crosky01.pa.comcast.net] has left #ubuntu-meeting ["Leaving"]
=== highvoltage [~Jono@196.36.161.235] has joined #ubuntu-meeting
=== highvolt1ge [~Jono@196.36.161.235] has joined #ubuntu-meeting
=== rob^ [~rob@rob-ubuntu.student.supporter.pdpc] has joined #ubuntu-meeting
=== highvolt1ge [~Jono@196.36.161.235] has joined #ubuntu-meeting
=== JaneW [~JaneW@wbs-146-169-90.telkomadsl.co.za] has joined #ubuntu-meeting
=== highvoltage [~Jono@196.36.161.235] has joined #ubuntu-meeting
=== mvo [~egon@ip181.135.1511I-CUD12K-01.ish.de] has joined #ubuntu-meeting
=== Unfrgiven [~ankur@202.76.176.94] has joined #ubuntu-meeting
=== mvo [~egon@ip181.135.1511I-CUD12K-01.ish.de] has joined #ubuntu-meeting
=== Mez [~Mez@cpc2-lich4-3-0-cust115.brhm.cable.ntl.com] has joined #ubuntu-meeting
=== highvolt1ge [~Jono@196.36.161.235] has joined #ubuntu-meeting
=== JaneW [~JaneW@wbs-146-169-90.telkomadsl.co.za] has left #ubuntu-meeting ["Bye"]
=== highvoltage [~Jono@196.36.161.235] has joined #ubuntu-meeting
=== terrex [~terrex@84-122-73-155.onocable.ono.com] has joined #ubuntu-meeting
=== highvolt1ge [~Jono@196.36.161.235] has joined #ubuntu-meeting
=== Mez [~Mez@cpc2-lich4-3-0-cust115.brhm.cable.ntl.com] has joined #ubuntu-meeting
=== highvoltage [~Jono@196.36.161.235] has joined #ubuntu-meeting
=== jdthood [~jdthood@x084.decis.nl] has joined #ubuntu-meeting
=== rob^ [~rob@rob-ubuntu.student.supporter.pdpc] has joined #ubuntu-meeting
=== rob^ [~rob@rob-ubuntu.student.supporter.pdpc] has joined #ubuntu-meeting
=== knuty [~knuty@182.84-48-114.nextgentel.com] has joined #ubuntu-meeting
=== kinjoo [~kinjoo@p54AA60E3.dip.t-dialin.net] has joined #ubuntu-meeting
=== Mez [~Mez@cpc2-lich4-3-0-cust115.brhm.cable.ntl.com] has joined #ubuntu-meeting
=== tseng [~tseng@tseng2.ath.cx] has left #ubuntu-meeting []
=== Mez [~Mez@cpc2-lich4-3-0-cust115.brhm.cable.ntl.com] has joined #ubuntu-meeting
=== mvo [~egon@ip181.135.1511I-CUD12K-01.ish.de] has joined #ubuntu-meeting
=== Mez [~Mez@cpc2-lich4-3-0-cust115.brhm.cable.ntl.com] has joined #ubuntu-meeting
=== Mez [~Mez@cpc2-lich4-3-0-cust115.brhm.cable.ntl.com] has joined #ubuntu-meeting
=== kinjoo [~kinjoo@p54AA60E3.dip.t-dialin.net] has joined #ubuntu-meeting
=== highvoltage [~Jono@196.25.192.240] has joined #ubuntu-meeting
=== lamont [~lamont@15.238.5.30] has joined #ubuntu-meeting
=== terrex [~terrex@84-122-73-155.onocable.ono.com] has joined #ubuntu-meeting
=== ogra [~ogra@p5089DC89.dip.t-dialin.net] has joined #ubuntu-meeting
=== JaneW [~JaneW@wbs-146-184-247.telkomadsl.co.za] has joined #ubuntu-meeting
=== JaneW [~JaneW@wbs-146-184-247.telkomadsl.co.za] has left #ubuntu-meeting ["Bye"]
=== bddebian [~bddebian@user216-178-65-218.netcarrier.net] has joined #ubuntu-meeting
=== JaneW [~JaneW@wbs-146-184-247.telkomadsl.co.za] has joined #ubuntu-meeting
=== ..[topic/#ubuntu-meeting:JaneW] : Calendar - https://wiki.ubuntu.com/Calendar | Logs: http://people.ubuntu.com/~fabbione/irclogs/ |5 Aug 19:00 UTC BreezyGoals Update | 5 Aug 20:00 UTC: NUN http://wiki.ubuntu.com/NUNAgenda | 9 Aug 20:00 UTC: Tech Board http://wiki.ubuntu.com/TechnicalBoardAgenda | 11 Aug 22:00 UTC: Doc Team http://wiki.ubuntu.com/DocteamMeetingAgenda | 16 Aug 12:00 UTC: CC http://wiki.ubuntu.com/CommunityCouncilAgenda | 24 Aug 20:00 UTC: MOTU http://wiki
=== bddebian [~bddebian@user216-178-65-218.netcarrier.net] has left #ubuntu-meeting ["Leaving"]
=== ..[topic/#ubuntu-meeting:JaneW] : Calendar - https://wiki.ubuntu.com/Calendar | Logs: http://people.ubuntu.com/~fabbione/irclogs/ |5 Aug 15:00 UTC BreezyGoals Update | 5 Aug 20:00 UTC: NUN http://wiki.ubuntu.com/NUNAgenda | 9 Aug 20:00 UTC: Tech Board http://wiki.ubuntu.com/TechnicalBoardAgenda | 11 Aug 22:00 UTC: Doc Team http://wiki.ubuntu.com/DocteamMeetingAgenda | 16 Aug 12:00 UTC: CC http://wiki.ubuntu.com/CommunityCouncilAgenda | 24 Aug 20:00 UTC: MOTU http://wiki
=== crimsun [~crimsun@sh.nu] has joined #ubuntu-meeting
=== terrex [~terrex@84-122-73-155.onocable.ono.com] has joined #ubuntu-meeting
=== doko_ [~doko___@dsl-084-059-071-048.arcor-ip.net] has joined #ubuntu-meeting
=== Seveaz [~seveas@seveas.demon.nl] has joined #ubuntu-meeting
=== robitaille [~daniel@d154-5-117-228.bchsia.telus.net] has joined #ubuntu-meeting
=== knuty [~knuty@182.84-48-114.nextgentel.com] has joined #ubuntu-meeting
=== mvo [~egon@ip181.135.1511I-CUD12K-01.ish.de] has joined #ubuntu-meeting
=== terrex [~terrex@84-122-73-155.onocable.ono.com] has joined #ubuntu-meeting

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