/srv/irclogs.ubuntu.com/2005/10/26/#ubuntu-meeting.txt

=== didascalos [n=Hagen@p54A88B53.dip0.t-ipconnect.de] has joined #ubuntu-meeting
=== didascalos [n=Hagen@p54A88B53.dip0.t-ipconnect.de] has left #ubuntu-meeting []
=== didascalos [n=Hagen@p54A88B53.dip0.t-ipconnect.de] has joined #ubuntu-meeting
=== didascalos [n=Hagen@p54A88B53.dip0.t-ipconnect.de] has left #ubuntu-meeting []
=== doko_ [n=doko@dslb-084-059-072-019.pools.arcor-ip.net] has joined #ubuntu-meeting
=== slomo_ [n=slomo@p5487FBEF.dip.t-dialin.net] has joined #ubuntu-meeting
=== crimsun [i=crimsun@pdpc/supporter/silver/crimsun] has left #ubuntu-meeting []
=== FLeiXiuS [n=fleixius@pcp0010489211pcs.essex01.md.comcast.net] has joined #ubuntu-meeting
=== highvoltage [n=Jono@196.36.161.235] has joined #ubuntu-meeting
=== ogra [n=ogra@p5089E05B.dip.t-dialin.net] has joined #ubuntu-meeting
=== Lathiat [i=lathiat@gasp.bur.st] has left #ubuntu-meeting []
=== Seveas [n=seveas@seveas.demon.nl] has joined #ubuntu-meeting
=== JaneW [n=JaneW@196.36.161.235] has joined #ubuntu-meeting
=== Ubugtu` [n=bugbot@81.171.100.21] has joined #ubuntu-meeting
=== DapperDr1ke [n=seveas@nuts.okkernoot.net] has joined #ubuntu-meeting
=== slomo_ [n=slomo@p5487FBEF.dip.t-dialin.net] has joined #ubuntu-meeting
=== Treenaks_ [n=martijn@messy.foodfight.org] has joined #ubuntu-meeting
=== ealden [n=ealden@219.90.91.16] has joined #ubuntu-meeting
=== siretart [i=siretart@tauware.de] has joined #ubuntu-meeting
=== lordk4rf [n=me@c-24-130-96-156.hsd1.ca.comcast.net] has joined #ubuntu-meeting
=== phlaegel [n=phlaegel@atdot.ca] has joined #ubuntu-meeting
=== Kamion [n=cjwatson@83-216-156-196.colinw664.adsl.metronet.co.uk] has joined #ubuntu-meeting
=== ajmitch [n=ajmitch@port163-86.ubs.maxnet.co.nz] has joined #ubuntu-meeting
=== JanC [n=janc@lugwv/member/JanC] has joined #ubuntu-meeting
=== sivang [n=sivang@box79162.elkhouse.de] has joined #ubuntu-meeting
=== fabbione [i=fabbione@gordian.fabbione.net] has joined #ubuntu-meeting
=== uniq [n=frode@213.184.199.55] has joined #ubuntu-meeting
=== Mithrandir [n=tfheen@c5100BC63.inet.catch.no] has joined #ubuntu-meeting
=== sladen [i=paul@starsky.19inch.net] has joined #ubuntu-meeting
=== Riddell [i=jr@kde/jriddell] has joined #ubuntu-meeting
=== whiprush [n=jorge@64.62.190.212] has joined #ubuntu-meeting
=== DapperDrake [n=seveas@nuts.okkernoot.net] has joined #ubuntu-meeting
=== JaneW [n=JaneW@196.36.161.235] has joined #ubuntu-meeting
=== Ubugtu [n=bugbot@81.171.100.21] has joined #ubuntu-meeting
=== BenC [n=bcollins@debian/developer/bcollins] has joined #ubuntu-meeting
=== Topslakr [n=Topslakr@24-54-42-180.lndnnh.adelphia.net] has joined #ubuntu-meeting
=== Sepheebear [n=SepheeBe@cpe-68-175-57-11.nyc.res.rr.com] has joined #ubuntu-meeting
=== \sh_away [n=sh@server3.servereyes.de] has joined #ubuntu-meeting
=== Mortas [n=kris@ams.xsguard.com] has joined #ubuntu-meeting
=== rejden [n=rejden@147.175.55.175] has joined #ubuntu-meeting
=== jbailey [n=jbailey@testhaus.cns.utoronto.ca] has joined #ubuntu-meeting
=== Sepheebear [n=SepheeBe@cpe-68-175-57-11.nyc.res.rr.com] has joined #ubuntu-meeting
=== BenC [n=bcollins@www.swissdisk.com] has joined #ubuntu-meeting
=== whiprush [n=jorge@64.62.190.212] has joined #ubuntu-meeting
=== Riddell [i=jr@kde/jriddell] has joined #ubuntu-meeting
=== sladen [i=paul@starsky.19inch.net] has joined #ubuntu-meeting
=== Mithrandir [n=tfheen@c5100BC63.inet.catch.no] has joined #ubuntu-meeting
=== uniq [n=frode@213.184.199.55] has joined #ubuntu-meeting
=== fabbione [i=fabbione@gordian.fabbione.net] has joined #ubuntu-meeting
=== sivang [n=sivang@box79162.elkhouse.de] has joined #ubuntu-meeting
=== JanC [n=janc@lugwv/member/JanC] has joined #ubuntu-meeting
=== ajmitch [n=ajmitch@port163-86.ubs.maxnet.co.nz] has joined #ubuntu-meeting
=== Kamion [n=cjwatson@83-216-156-196.colinw664.adsl.metronet.co.uk] has joined #ubuntu-meeting
=== phlaegel [n=phlaegel@atdot.ca] has joined #ubuntu-meeting
=== lordk4rf [n=me@c-24-130-96-156.hsd1.ca.comcast.net] has joined #ubuntu-meeting
=== siretart [i=siretart@tauware.de] has joined #ubuntu-meeting
=== ealden [n=ealden@219.90.91.16] has joined #ubuntu-meeting
=== Treenaks_ [n=martijn@messy.foodfight.org] has joined #ubuntu-meeting
=== slomo_ [n=slomo@p5487FBEF.dip.t-dialin.net] has joined #ubuntu-meeting
=== Sepheebear [n=SepheeBe@cpe-68-175-57-11.nyc.res.rr.com] has joined #ubuntu-meeting
=== DapperDrake [n=seveas@nuts.okkernoot.net] has joined #ubuntu-meeting
=== Topslakr [n=Topslakr@24-54-42-180.lndnnh.adelphia.net] has joined #ubuntu-meeting
=== \sh_away [n=sh@server3.servereyes.de] has joined #ubuntu-meeting
=== terrex [n=terrex@84-122-90-162.onocable.ono.com] has joined #ubuntu-meeting
=== phlaegel [n=phlaegel@atdot.ca] has joined #ubuntu-meeting
=== doko_ [n=doko@dslb-084-059-081-172.pools.arcor-ip.net] has joined #ubuntu-meeting
=== robitaille [n=robitail@d154-5-117-228.bchsia.telus.net] has joined #ubuntu-meeting
=== mvo [n=egon@ip181.135.1511I-CUD12K-01.ish.de] has joined #ubuntu-meeting
=== nsomniac [n=nsomniac@ppp-70-249-149-182.dsl.rcsntx.swbell.net] has joined #ubuntu-meeting
=== Kamion [n=cjwatson@83-216-156-196.colinw664.adsl.metronet.co.uk] has joined #ubuntu-meeting
=== triceratops [n=tricerat@dyndsl-085-016-013-065.ewe-ip-backbone.de] has joined #ubuntu-meeting
=== triceratops [n=tricerat@dyndsl-085-016-013-065.ewe-ip-backbone.de] has left #ubuntu-meeting ["Leaving"]
=== Ubugtu [n=bugbot@81.171.100.21] has joined #ubuntu-meeting
=== terrex [n=terrex@84-122-90-162.onocable.ono.com] has joined #ubuntu-meeting
=== Seveas [n=seveas@seveas.demon.nl] has joined #ubuntu-meeting
=== terrex [n=terrex@84-122-90-162.onocable.ono.com] has joined #ubuntu-meeting
=== terrex [n=terrex@84-122-90-162.onocable.ono.com] has joined #ubuntu-meeting
=== Hirion [n=Hirion@p5487FBEF.dip.t-dialin.net] has joined #ubuntu-meeting
=== Kamping_Kaiser [n=Karl@ppp209-139.lns1.adl2.internode.on.net] has joined #ubuntu-meeting
=== Kamion [n=cjwatson@83-216-156-196.colinw664.adsl.metronet.co.uk] has joined #ubuntu-meeting
=== slomo [n=slomo@p5487FBEF.dip.t-dialin.net] has joined #ubuntu-meeting
=== Treenaks [n=martijn@messy.foodfight.org] has joined #ubuntu-meeting
=== ealden [n=ealden@219.90.91.16] has joined #ubuntu-meeting
=== siretart [i=siretart@tauware.de] has joined #ubuntu-meeting
=== lordk4rf [n=me@c-24-130-96-156.hsd1.ca.comcast.net] has joined #ubuntu-meeting
=== ajmitch [n=ajmitch@port163-86.ubs.maxnet.co.nz] has joined #ubuntu-meeting
=== JanC [n=janc@lugwv/member/JanC] has joined #ubuntu-meeting
=== sivang [n=sivang@box79162.elkhouse.de] has joined #ubuntu-meeting
=== fabbione [i=fabbione@gordian.fabbione.net] has joined #ubuntu-meeting
=== uniq [n=frode@213.184.199.55] has joined #ubuntu-meeting
=== Mithrandir [n=tfheen@c5100BC63.inet.catch.no] has joined #ubuntu-meeting
=== sladen [i=paul@starsky.19inch.net] has joined #ubuntu-meeting
=== Riddell [i=jr@kde/jriddell] has joined #ubuntu-meeting
=== whiprush [n=jorge@64.62.190.212] has joined #ubuntu-meeting
=== manveru_ [n=manveru@micht2-132-141.utaonline.at] has joined #ubuntu-meeting
=== manveru_ [n=manveru@micht2-132-141.utaonline.at] has left #ubuntu-meeting ["Konversation]
=== judax [n=troy@adsl-70-240-14-115.dsl.austtx.swbell.net] has joined #ubuntu-meeting
=== rob^ [n=rob@pdpc/supporter/student/rob-ubuntu] has joined #ubuntu-meeting
=== lamont [n=lamont@15.238.5.68] has joined #ubuntu-meeting
=== hno73 [n=henrik@henrik.gotadsl.co.uk] has joined #ubuntu-meeting
judax<- Troy Williams04:03
mdkehello04:03
judaxhiya04:03
Kamping_Kaiserhi :)04:03
hno73<- Henrik Nilsen Omma04:03
mdkeMatthew East04:04
Kamping_KaiserKarl Goetz04:04
Kamping_Kaiser(not on wiki)04:04
rob^Robert Stoffers04:04
mdkei will just be in and out, as per my email today04:05
=== apokryphos [n=apokryph@70.85.216.98] has joined #ubuntu-meeting
rob^hmm, looks like I'll have to forward a lot of the agenda to the mailing list04:05
mdkeis jbailey coming?04:05
rob^not sure04:05
mdkeyeah i was just hilighting him04:06
mdke:)04:06
rob^heh04:06
jbaileyNick highlights in irssi suck.04:06
jbaileyfabbione: Thanks.04:06
=== jeffsch [n=jeffsch@fatwire-204-157.uniserve.ca] has joined #ubuntu-meeting
=== Treenaks [n=martijn@messy.foodfight.org] has joined #ubuntu-meeting
Kamping_Kaiserlol04:06
mdke:)04:06
mdkehey jeff04:06
jbaileyFor some reason they only seem to highlight at the beginning of a sentence.04:06
=== jbailey needs to switch back to x-chat soon.
mdkejbailey, mine go a different colour if it is in the middle04:06
Mithrandirjbailey: it does that by default.  Nice feature.04:06
rob^mmm xchat04:06
mdkejbailey,  [15:06:53]  hilightwin      /home/matt/.irssi/scripts/autorun/hilightwin.pl04:07
jbaileyMithrandir: Suck feature.  I miss pings all the time.04:07
mdkeoh no, that's something else04:07
mdkejbailey, i guess you can set it to hilight in the middle04:07
Mithrandirjbailey: define your own highlight thingy, then04:07
jbaileyMithrandir: What I really want is my graphical x-chat do be able to work in a screen session.04:07
jbaileyMithrandir: But I think I've mentioned this wish to you and you suggested NX04:08
mdkeme too04:08
mdkeanyhow are we go?04:08
Mithrandirjbailey: yes, true.  Be aware of the crack levels therein.04:08
rob^yes, I gotta go to work soon04:08
mdkemerging back to trunk: kubuntu has been done already, who is going to do ubuntu stuff?04:08
=== jbailey grabs the agenda.
rob^what does it intail? just copy/paste?04:09
mdkei don't know04:09
mdkethere is some clever svn merge thing04:09
jbaileyWhat it needs is the layout of the repo thought about first.04:09
=== mdke nods
jbaileyI wound up in the end just hacking things so that they'd work.04:09
jbaileySo it's not just a clean merge back.04:09
mdkeok04:09
jbaileyCan you move this to after the repo layout item?04:09
jbaileys/you/we/04:09
mdkegood idea04:09
rob^can we do that?04:10
mdkesure, why not?04:10
jbaileyUp to whoever is running the meeting, really. =)04:10
rob^ie can we merge back to a new layout automagically?04:10
jbaileyOh. =)04:10
mdkeoh04:10
judaxwhy not merge back, then chop up?04:10
jbaileyNo, it'll be a series of copies, but that won't be hard I don't think.04:10
rob^oh ok, I thought so04:11
jbaileyThe other thought is that if all the work went onto the trunk and the branch, we don't really need to merge anything back.04:11
hno73why not just import to baz while we are moving stuff around anyway04:11
mdkejbailey, what about judax's idea there04:11
mdkehno73, we'd have to take the decision to use baz04:11
hno73that's meant to have better merging right?04:11
jbaileyRight, but what I'm wondering is if all the data is already on the trunk, what's to merge back except my changes for the packaging which have to be rethought anyway.04:12
hno73mdke: it seems to be on the agenda04:12
mdkejbailey, changes made since the branch04:12
mdkehno73, yeah :)04:12
jbaileymdke: I thought everyone had been trunking those as well?04:12
mdkejbailey, nope04:12
jbaileyAh, okay.04:12
jbaileyUmm.  I guess I'm the most familiar with the stuff, so I should do it.04:13
mdkei like judax's idea04:13
mdkemerge back and then rearrange directory structure accordingly04:13
rob^i like jbailey's idea04:13
jbaileyRight, but merging back means what?04:13
judaxI think that would make life easier04:13
jbaileyRearranging the repo should happen on the trunk, yes.04:13
jbaileyThe branch needs to be pretty much considered locked at the point.04:14
mdkeok, so it's the same idea04:14
rob^yep04:14
jbaileyChanging it would make doing occasional snapshots quite hard.04:14
=== jbailey ^5's judax
=== rob^ brb
mdkeok so what does the merge entail04:15
=== rob^ back
mdkecopying anything in the branch that has changed since it was branched right?04:15
jbaileymdke: Right, except in cases where people have contributed stuff on the trunk.04:15
=== mdke nods
mdkewhen are we gonna do it?04:16
jbaileyCan do this afternoon or maybe Monday.04:17
jbaileyI'll try this afternoon so it doesn't block people.04:17
judaxyou can examine the changes in the working copy (trunk) and the branch04:17
judaxby doing a --dry-run04:17
rob^nice one04:18
jbaileyYeah.04:18
jbaileydiff is my friend, too. =)04:18
jbaileyI don't think svn has much of a concept of merging changesets from branches to the trunk (like bzr would)04:18
mdkeok cool04:19
mdkeshall we move on04:19
rob^ok04:20
rob^gonna be hard seeing as hes not here..04:20
mdkeUBZ is a bit of a red herring afaics because only corey will be there, there might not be much docs discussion04:20
jbaileyI will be as well, but I'm not sure how my time will be spread out.04:20
mdkeyeah04:21
mdkeperhaps the best thing is to play it by ear and comment on any relevant BOFs on the mailing list?04:21
judaxthere is a nice chapter in the svnbook (svnbook.red-bean.com) about Branching and Merging, just FYI04:21
jbaileyjudax: Thanks, I'll reread it.04:21
rob^mdke, sounds like a good idea04:21
rob^the only thing I'm concerned about is some of the stuff mentioned in the BOFs04:22
jbaileyjudax: I have the page bookmarked for how to do .cvsignore equivalents. =)04:22
jbaileyrob^: Like what?04:22
mdkerob^, don't forget bof's are just ideas04:22
judaxjbailey: ah :)04:22
rob^things like in line help are a little pie-in-the-sky04:22
rob^ms has been doing it for years anyway with their question mark thing, and no body cares about that either04:23
rob^in the end I expect pretty much the status quo to happen anyway04:23
jbaileyrob^: It would be interesting to get a commitment from mdz and sabdfl that all specs must have a documentation component to them in order to be complete.04:24
jbaileyI don't know if it's doable or not.04:24
rob^jbailey, thats a lot of work04:24
jbaileyrob^: It's far more work for the docteam to do it after the fact.04:24
Kamionsome specs are just "fix <deep thing>"04:24
jbaileyKamion: Sure, but should that fix not be documented so that it's understood after?04:25
KamionI think we'd want a little more selectivity than a blanket requirement04:25
jbaileyKamion: Mmm.  When I think of the specs that I went to at UDU, most of them could've used at least some basic documentation.  It would be nicer if it were an "apply for exception".04:25
Kamiondepends on how much the person who scheduled the BOF knew about the code - I've had specs that were utterly obvious04:25
rob^I'm thinking that such a change would mean we would be forking everything from upstream, ie adding lots of code to each program04:26
Kamionas long as there's an exception process, no problem04:26
rob^ubuntu already gets accused of being a Debian fork, this would only serve to make it worse I think04:27
Kamping_Kaiserjbailey: what do you mean by 'doc component' in a spec?04:28
jbaileyrob^: I see less of those accusations now that the random nay-sayers are getting ignored =)04:28
rob^heh04:28
rob^I'm not saying it is, but why give them more ammunition?04:28
mdkei think you two are talking at cross purposes, jbailey's proposal was not to add code to every program04:29
mdkeas i understand it04:29
mdkehe is just saying, specs should be documented04:29
rob^how else would you implement in line help?04:29
jbaileyKamping_Kaiser: What I'd like to see is that we build up a documentation set for Ubuntu.  But the problem is that the docteam is just a small group of people not involved in the development.  I would like to see the coders responsible for creating the needed documentation as part of completeing the spec (So before payment of the bounty, or whatnot)04:29
mdkerob^, he is not talking about in line help at all afaics04:29
jbaileySorry, I was still mention things for UBZ04:30
rob^mdke, thats what I was on about04:30
Kamping_Kaiserjbailey: so the programers write all/some help, and what does the docteam do? make it usefull? other?04:30
mdkerob^, true but that doesn't stop the subject from being changed04:31
rob^mdke, heh yeah04:31
jeffschthe docteam can edit it and de-geekify it so users can understand it04:31
Kamping_Kaiserlol. i see. well put jeffsch :)04:31
mdkethe problem is really that the docteam only has a handful of contributors04:31
apokryphosif you don't mind me saying, the job of the coder is to code; we don't wanna waste their time with documentation (hence a docteam), but of course it's good to have coordination between these04:31
mdkeat least at the moment04:31
mdkeapokryphos, that is quite a controversial statement04:31
apokryphosI stand by it04:32
mdkelots of people accept that part of writing programs is documenting them04:32
jbaileyI don't think I know any programmer who has the task of just coding.  There's always meetings, documentation, end-user troubleshooting, etc.04:32
=== mdke nods
apokryphossmall things like those; but, for example, it shouldn't be a coders job (per se) to write a handbook for a given app04:32
Kamping_Kaisernot a handbook, a basic help to help the doc team, surely?04:33
apokryphosin my ideal, you have a given docteam, who tries/uses the given application, and coordinates with the programmer on questions; the doccer takes note of these, then documents them04:33
judaxnot full-on documentation, but at least 'spec-form' documentation04:33
apokryphosthe way I've always done things in the past, is just arrange to have a chat with the person in question online; have a quick talk asking questions etc, then go away and write it up04:34
apokryphos(quite like a reporter, in some ways)04:34
rob^whos going to have the time to round all these up and de-geekify them anyway?04:34
jbaileyrob^: Well, it's best-effort. =)04:34
rob^heh04:35
jbaileyI tend to think that if we ship geeky documentation, that it will still be an improvement on shipping just three documents like we did now.04:35
rob^I wonder if we can wiki-ify them to allow anyone to help us04:35
jbaileyMy thought is that the people implementing the specs should have some interest in seeing the documentation written.04:35
apokryphosbasic user documentation is probably paramount, but more geeky documentation is necessary for giving other users the better user-experience04:36
apokryphosjbailey: definitely04:36
Kamionapokryphos: handbook-style documentation definitely isn't appropriate for every development task. In many cases (non-end-user-facing ones), comments or a simple document for developers is sufficient and the developer should write those04:36
apokryphosdefinitely; things like "What's This" help are of course the job of the coder04:37
=== fabbione [n=fabbione@port49.ds1-van.adsl.cybercity.dk] has joined #ubuntu-meeting
=== fabbione [n=fabbione@port49.ds1-van.adsl.cybercity.dk] has joined #ubuntu-meeting
rob^apokryphos, thats what I was touching on before04:37
rob^shall we move on?04:40
Kamping_Kaisergoing back to jbaileys comment on 'geeky doc is better then nothing', im not sure thats always right. rob^ and the ohter auther of the faq have a great intro text, but i cant see a user wanting to go deeper into geeky help untill they feel comfortable. that faq and similar help is requiered04:40
=== jjesse [n=jjesse@mail.ftpb.com] has joined #ubuntu-meeting
jjessetoo late?04:40
mdkeno, hi04:40
Kamping_Kaiserhi  :)04:40
jjessesorry had to solve an emergency at work04:40
mdkeshall we progress to the next agenda item?04:41
mdkeor do people have more points about docs at UBZ04:41
KamionKamping_Kaiser: that's "not optimal" certainly but doesn't refute "better than nothing", I think04:41
=== ealden [n=ealden@219.90.91.16] has joined #ubuntu-meeting
rob^it would be nice to get something for each program, but unless someone wants to stand up and do all the work it will probably just mostly go to waste04:42
Kamping_KaiserKamion: sure. and i dont mind about next item fwiw04:42
rob^any more for any more?04:43
mdkeok translations - does anyone want more information than I've set out in my email to the list today?04:43
rob^no, it all sounds good mdke 04:43
rob^any idea of time frame?04:44
judaxthat covers it, imho04:44
Kamping_Kaiseri didnt realy follow, but i havent seen it in action :|04:44
rob^Kamping_Kaiser, http://article.gmane.org/gmane.linux.ubuntu.doc/352104:44
mdkei had originally said about a month04:44
rob^ok04:44
mdkebecause that is about time of language-packs04:44
rob^oh ok cool04:44
mdkebut i don't think that is a major thing04:45
jbaileyYay, langpacks.04:45
Kamping_Kaiserta rob^04:45
rob^np04:45
mdkejbailey, got any issues about translation updates?04:46
=== jsgotangco [i=jsgotang@info1-190.info.com.ph] has joined #ubuntu-meeting
jbaileymdke: Nope.  Just need to figure out the langpack thing with Martin.04:46
jsgotangcobloody hell04:46
=== jsgotangco is in a cafe in a hotel
Kamping_Kaiserlol04:47
jsgotangcomirc has the lousiest interface ever04:47
=== jsgotangco lurks
rob^heh04:47
mdkejbailey, well that is for dapper. We're on breezy04:47
jbaileymdke: Right, sorry.04:47
jbaileyNone for breezy. =)04:47
mdkecool04:48
rob^next04:48
rob^sorry, I have to get up in ~4 hours for work04:48
jbaileyBig picture stuff for dapper - for me is just langpacks and nightly snapshots.04:49
jsgotangcosnapshots +104:49
jjessesnapshots of ?04:49
jbaileyjjesse: The trunk of the repository04:49
jbaileyUploaded weekly to dapper for wider review.04:49
jjessejbailey: which will then include the kubuntu-docs?04:50
rob^snapshots is good04:50
jbaileyjjesse: I'm not clear on what we should do for that.  I'm a bit concerned that the docteam is reponsible for Ubuntu, Kubuntu, Edubuntu and Xubuntu (per the agenda)04:50
jsgotangcowell we can ask Ridell for that....04:50
jbaileyjjesse: I'm not really clear how much there is in common between them and if they should really be done out of the same repository.04:51
jbaileyIn terms of producing snapshots, though, no skin off my teeth. =)04:51
jjessedid i miss the discussion of the infrastructure?04:51
judaxjjesse: no04:51
jbaileyIt'll be largely automated.04:51
jjessei can talk to Riddell about the daily snapshots of kubuntu dapper including the docs04:51
jbaileyjjesse: Cool.  I just don't want to see all of those treated as second-class citizens.04:52
jbaileyjjesse: But I'm not sure the best way to do that.04:52
jjessejbailey: don't worry i'll keep bugging Riddell for any help i need we have worked together for the breezy docs04:53
mdkejbailey, why are you concerned about the docteam doing ubuntu, kubuntu etc? there is only one docteam, not more than one.04:53
jbaileymdke: I'm wondering how the docteam decides whether it cares about a derivative or not.04:53
mdkejbailey, it's a question of having willing contributors04:53
=== Riddell turns up
rob^I hope this bloody thunderstorm goes away or I'm gonna have to go04:53
jbaileymdke: Like, someone decides to do Xubuntu.  Does it suddenly become the docteams responsibility?04:53
judaxit seems that way04:54
mdkejbailey, i think that would be a question for the team, but certainly it has decided to include kubuntu04:54
mdkeand jerome has done work on edubuntu04:54
apokryphosjbailey: it cares about them if they're official projects, I'd imagine (i.e. being in MAIN etc)04:55
rob^if its *ubuntu and someone wants to write docs sure04:55
jjessewhat you would get is teams that only have 1 member04:56
jsgotangcoi don't want to do work on some other svn for sure04:56
jjesseagreed jsgotangco 04:56
jbaileyRight.04:56
jsgotangcoi'd say we remove the upstream stuff though...04:56
jsgotangcothe current trunk is like 250MB04:56
jbaileyI just don't want suddenly it to become "do your own derivative, have the docteam take care of it"04:56
judaxthat is where you have a problem though, you need to do what is right for the distro04:57
mdkejbailey, yeah, the team can decide what to work on04:57
jbaileyHalf of the model of Ubuntu is to make it easy to do derivatives.  So making it easy to derive the docs should be part of that.04:57
rob^maybe, but that doesn't mean we have to accept them04:57
jbaileyI wonder if having it all in one source package works towards that.  I don't have the thoughts all clear in my head.04:57
mdkeobviously we need to build contributors for ubuntu and kubuntu, but if people want to work on other ubuntu-related, that is cool04:57
jsgotangcoi'd like to focus on Partner Projects04:58
mdkejbailey, we can have separate source packages, and one repository with a number of separate directories, as suggested by rob^ 04:58
jsgotangcoso that's 3 projects04:58
jjesseshouldn't we have a "head" of ubuntu-docs a 04:58
Kamping_Kaiserif somone has comit on svn, can they commit to an project corrently? or can it be restricted?04:58
rob^jbailey, https://wiki.ubuntu.com/DocteamRepositoryLayout04:58
jsgotangcoKamping_Kaiser: its an open svn :)04:59
rob^Kamping_Kaiser, no all04:59
jjesse"head" of kubuntu-docs and "head" of edubuntu-docs, etc04:59
jbaileyrob^: Cool.  I save comments until the right part of the agenda.04:59
Kamping_Kaiserok :| thats not helpfull ;O04:59
jbailey(Lagging a bit, conference call)04:59
mdkeit is true that we need to encourage contribution to partner projects before we can have the manpower to contribute on things like xubuntu04:59
jsgotangcoyes05:00
=== jsgotangco will focus on kubuntu and edubuntu
mdkeanyhow, what other big pictures for dapper?05:00
jjessei will focus on kubuntu05:00
mdkewe need to think about what docs to write05:00
jsgotangcolet's make the specs again from DocteamProjects05:01
jjessefor dapper i have started wiki.ubuntu.com/KubuntuDocs05:01
rob^mdke, as a side thing I would like to get some of the upstream xubuntu docs and have them available maybe with modification in xubuntu05:01
jsgotangcoupstream xubuntu?05:01
rob^I mean xfce05:01
rob^they have an svn repo05:01
jsgotangcoplease make efforts as much as possible to look at upstream work just in case :)05:01
jsgotangcoor fix our upstream as well :) (scrollkeeper borkage)05:02
rob^thats what I have been/am going to do05:02
jsgotangcofor gnome, there's current upstream 2.12 on the works, but not optimistic about it :)05:02
rob^xfce have a nice user guide05:03
mdkeare we going to try and complete the ubuntu userguide?05:03
mdkeit has a distinct aim from the faqguide, but overlaps in many respects05:03
rob^yes, I did a lot of work during breezy to not overlap as much as possible05:04
mdkei would favour trying to get it back up and running05:04
jjessemdke: for kubuntu docs that i have started to focus on for dapper please see http://wiki.ubuntu.com/KubuntuDocs05:04
mdkejjesse, ok, you need to mark things in DocteamProjects if you can05:04
jsgotangcojjesse: we have to update the KQuickGuide though...05:05
jsgotangcoeven halfway...05:05
jsgotangcoat least there won't be that much changes for Dapper unless we actually see KDE 3.5 :)05:05
jjessejsgotangco: yes we do, update it all the way, quickguide release notes, userguide are the ones05:05
rob^jjesse, do we still want to use kudos for a kubuntu faq guide?05:05
jjesserob^: yes i have seen some requests in #kubuntu for faq guide05:05
jsgotangcoyes05:06
jjesserob^: maybe we can work together on that one05:06
judaxkudos would be a good start05:06
rob^jjesse, I'd like to have it done for dapper05:06
rob^jjesse, sure05:06
jjesserob^: ok05:06
=== jsgotangco is still getting used to KDE...but doing good atm
rob^jjesse, does kudos have an xml version by any chance?05:07
jsgotangconone05:07
jsgotangcowe can grep it though05:08
jjessesorry kudus is?05:08
judaxit is like ubuntuguide.org05:08
jjesseah05:08
rob^jjesse, the kubuntu unofficial faq guide05:08
jsgotangcothat's the kubuntu faqguide...05:08
rob^yeah05:08
rob^I'd like to use that to save work05:08
jjessedo i need to get permission to create a docbook file of that from someone?05:08
rob^we need to check the licences05:08
jsgotangcoif its licensed accordingly, you can use it05:08
rob^I think sean said we have premission to use it under our current licences though05:09
jsgotangcobut dig the list archive for details05:09
jsgotangcoyes05:09
jsgotangcoi asked the author about it05:09
judaxdidn't sean talk to the author?05:09
jsgotangcome and sean05:09
rob^apparently05:09
jsgotangcowe have permission05:09
judaxjsgotangco: ok05:09
rob^ok05:09
jsgotangcowe'll just see if its updated05:09
jsgotangcoits in berlios05:09
rob^an xml?05:09
jjessei heard on #kubuntu that it's not updated05:10
jsgotangco(actually its a good ton of work)05:10
jsgotangcorob^: we wish05:10
jjessebut haven't checked myself05:10
rob^jsgotangco, yes we do :)05:10
jsgotangcoits quite good....very visual for an faqguide05:10
rob^do we have premission to use the site as is?05:10
rob^ie can I copy it from there tomorrow?05:10
jsgotangcowell that's another story05:10
judaxdoes not look updated to me atm05:11
jsgotangcowe asked the author to work in svn before, but he declined05:11
rob^I'd like to start some work on that in about 6 hours if I could05:11
jsgotangcorob^: no rush, focus on your xubuntu :)05:11
rob^heh05:11
jsgotangcowe can take kde from here :)05:11
jjessejsgotangco: do you want to create the file or should i?05:11
rob^ok05:12
rob^I'll just follow your lead05:12
jsgotangcoi'll fix the kquickguide first05:13
rob^ok can we move on?05:13
jsgotangcoi'll grep the kudos site later when i get home05:13
mdkehelp.ubuntu.com and doc.ubuntu.com on the new server are now available for all to see05:14
rob^holy heck its pouring outside05:14
mdkecomments to the mailing list i would say, otherwise we'll be here for hours05:14
jsgotangcomdke: both are in server pronto already?05:14
mdkeyes05:14
mdkerefresh your caches05:14
jsgotangcogood good05:14
=== mdke points at hno73 's funky artwork
rob^no css on doc.u.c?05:15
hno73:)05:15
mdkerob^, eh?05:15
apokryphosre: kudos. They guy seems generally pretty understanding, but has very big plans05:15
Kamping_Kaiserrob^: got none here05:15
rob^hmm no there we go mdke 05:15
apokryphos(said he wanted to make most of the steps into shell scripts, so users could just run them)05:15
rob^apokryphos, ouch05:15
judaxyikes05:16
Kamping_Kaiserhm.05:16
apokryphosin some ways suffers some of the same blunders as ubuntuguide guy, but kudos-guy said he did plan to add more explanations (which would be cool). The whole idea, he says, is a proof of concept (Linux being user-friendly etc)05:16
rob^each to their own I guess05:16
mdkek, back to help.ubuntu.com, some things to discuss as per my email05:17
apokryphosthere's some really useful stuff (I incorporated some stuff into kde docs), like the given Linux application with win/mac equivalent -- very handy for newbies05:17
mdke1. whether to include translations05:17
judaxyes, that matrix is nice05:17
mdke2. whether and how to include the bar and side panel to all docs05:17
mdke3. please fix the kde docs so I can add them05:18
rob^1 - yes I think we should05:18
rob^2 - Yes, I think we should05:19
mdkei think we shouldn't, because I think that locoteams will want to host their own05:19
mdke-fr and -it are already in that process05:19
mdkeand they will no doubt change things like appearance to make the guides in tune with their websites05:19
rob^:)05:19
mdkealso, it will get messy if we host 30 translations05:19
rob^can we alter the html on help.u.c at all?05:19
rob^mdke, maybe we can have an additional translations page05:19
mdkerob^, comments about the page itself are probably best postponed to the list imo05:19
rob^yep05:19
mdkebut sure, we can change anything05:19
mdkeit's our server05:20
rob^hmm nice05:20
mdkei had thought, a link to a list of the various locoteam webpages05:20
=== rob^ thinks about using his l33t html/php coding skillz
rob^oh crap05:20
rob^I gotta go, the thunderstorm outside is getting pretty bad05:21
Kamping_Kaiserlater rob^ :) 05:21
mdkebye05:21
rob^cyas05:21
Kamping_Kaiserlater05:21
whiprushdid I miss the meeting?05:21
mdkeso does anyone else have any thoughts about translations? perhaps we can ask the locoteams themselves? they would be well placed to offer advice05:21
jsgotangcowhiprush: not much :)05:21
whiprushwhew05:21
Kamping_Kaisermdke: ask locos on the list? i dont hav any ideas about it05:22
jsgotangcomdke: add them to d.u.c.? nice idea although we'll have to get their work or they upload it themselves (bit of work)05:22
jeffschmdke: link to all translations; some will be hosted locally, others on translation team sites05:22
mdkejeffsch, that will take quite a bit of maintaining05:22
mdkejsgotangco, no, not their work, translations of the docteam stuff05:22
Kamping_Kaiserthis would be hard, but on a help page offer links to the same page translated by the doco teams?05:23
hno73mdke: not if it's a wiki page :)05:23
jsgotangcoit'd be nice if we can just link 'em but if we got a nice server why not...05:23
Riddellmdke: what's the status of translations at the moment?05:23
hno73then teams can update the links themselves05:23
jsgotangcoaye, like the one in edubuntu....05:23
mdkeRiddell, for ubuntu-docs the status is at http://launchpad.net/products/ubuntu-docs05:23
mdkehno73, nice idea05:23
mdkeRiddell, kubuntu stuff isn't translated05:24
mdkehno73, have you got moin up on there already?05:25
hno73mdke: no, but I expect it to be up later today05:25
mdkecool05:25
hno73I have a side menu thing working in moin now05:25
jsgotangcowow05:25
hno73so we can have the same side menu as the rest of the site05:26
mdkeexcellent05:26
jsgotangcohno73: is the frontpage of the edubuntu.org site in moin too? it has a side menu thing05:26
jjessei have to split have another work meeting :(05:26
jsgotangcolater jjesse05:26
Kamping_Kaiser:( later jjesse05:27
mdkebye05:27
judaxbye jjesse 05:27
hno73jsgotangco: no, that's plain html05:27
judaxmdke: concerning #3, I just built kak (About Kubuntu), what problem are you experiencing05:27
hno73but it would be nice to make it moin based05:27
=== jeffsch goes off to work :(
Kamping_Kaiserlater mate05:28
jbaileyI think we've lost a pile of people.  Should we punt the other items to next time?05:28
mdkejudax, i'm experiencing this: http://help.ubuntu.com/kde/about-kubuntu/C/05:28
=== jeffsch [n=jeffsch@fatwire-204-157.uniserve.ca] has left #ubuntu-meeting ["gone]
mdkejbailey, yes we can, or pursue them on the mailing list05:29
Riddellmdke: that's using the KDE non-web stylesheet05:29
judaxmdke: the style05:29
mdkeyes05:29
mdkeif that can be sorted out, I'll put em up and link em05:30
Riddellyou want to use the KDE web stylesheet, which is in a top secret place.  or just a normal stylesheet05:30
=== jsgotangco will have to learn more KDE steylesheets
judaxwhat stylesheet do you want05:31
mdkeRiddell, either way, if you fix it, I'll build it and put it up on that site05:31
Riddellmdke: what do I need to fix?  what's the command used to generate that?05:32
judaxmake kak05:32
=== ian_brasil [n=vern@pintada.proamazon.com.br] has joined #ubuntu-meeting
RiddellWe probably need a make kak-web05:32
mdkeok05:34
mdkealso for whatever other documents to be hosted online05:34
jsgotangcoahhh Riddell you seem to have svn access now?05:34
Kamping_Kaiserare we still meeting?05:35
jsgotangcowell i can't stay long, i'm still outside, its almost midnight here, need to catch a cab05:36
=== jsgotangco will just check the log later
Kamping_Kaiserdoestn seem like ther will be mucht o check05:37
mdkeok we're done i think05:37
Kamping_Kaiserok. fair enough05:37
mdkewe need to chase up this directory structure, use of gnome-doc-utils build stuff at a later date05:37
judaxok05:38
jsgotangcoah so we're stalemate on the structure?05:38
jsgotangcois it merged already?05:38
mdkewe didn't get that far05:38
judaxmerge first05:38
jsgotangcook sounds good05:39
mdkeshall I prepare an announcement for help.ubuntu.com?05:39
mdkehno73?05:39
hno73mdke: sure, thanks05:39
mdkegreat05:39
judaxtake care all05:40
Kamping_Kaiser:) 05:40
=== judax [n=troy@adsl-70-240-14-115.dsl.austtx.swbell.net] has left #ubuntu-meeting ["Konversation]
jsgotangcook gotta go too05:40
mdkehno73, will you link it in www.u.c/support?05:40
Kamping_Kaisersounds like it done then :)05:40
jsgotangcook guys later05:41
=== jsgotangco [i=jsgotang@info1-190.info.com.ph] has left #ubuntu-meeting []
Kamping_Kaiserlater mate05:41
hno73mdke: yepp. Shall we launch now or on monday?05:42
mdkeup to you05:42
hno73the wiki stuff isn't ready05:42
mdketrue05:42
mdkethat will take a while05:42
hno73but that can come later I guess05:42
mdkeand things can be added gradually05:42
hno73cool, ok05:42
mdkeRiddell, ping me if you manage to sort that kak-web thing out :)05:47
Riddellok05:49
=== hno73 [n=henrik@henrik.gotadsl.co.uk] has left #ubuntu-meeting []
=== cyphase [n=cyphase@adsl-68-127-26-37.dsl.pltn13.pacbell.net] has joined #ubuntu-meeting
cyphasehey everyone05:56
Kamping_Kaiserhi05:57
whiprushmdke: if you need something announced on the fridge let me know.06:05
whiprushI'd like to showcase more docteam stuff on it.06:05
mdkecool06:07
mdkeif I ever get onto planet I'll do it there too06:07
mdkewhiprush, i'll copy you the announcement? are you jorge@u.c?06:07
whiprushI'm always on irc so ping me when you want something done.06:08
whiprushI don't have a u.c address yet.06:08
whiprushfridge-devel@ works though06:08
mdkeok06:08
whiprushjdub can run stuff also, but he's on tour. :p06:08
mdkeyup06:09
=== jjesse [n=jjesse@mail.ftpb.com] has left #ubuntu-meeting ["Konversation]
=== ogra [n=ogra@p5089E05B.dip.t-dialin.net] has joined #ubuntu-meeting
=== mdke [n=matt@unaffiliated/mdke] has left #ubuntu-meeting []
=== Hirion [n=Hirion@p5487FBEF.dip.t-dialin.net] has joined #ubuntu-meeting
=== ogra [n=ogra@p5089E05B.dip.t-dialin.net] has joined #ubuntu-meeting
=== Hirion [n=Hirion@p5487FBEF.dip.t-dialin.net] has joined #ubuntu-meeting
=== lamont__ [n=lamont@mib.fc.hp.com] has joined #ubuntu-meeting
=== sivang [n=sivang@box79162.elkhouse.de] has left #ubuntu-meeting []
=== ajmitch_ [n=ajmitch@port161-102.ubs.maxnet.co.nz] has joined #ubuntu-meeting
Treenakshttp://foodfight.org/movies/2005-10%20Ubuntu%20Fanpeople/10:14
mvoTreenaks: nice!10:20
Treenaksmvo: thanks :)10:20
Treenaksmvo: I'll take my cam to UBZ, so you can try it too :)10:20
ajmitchheh10:21
mvohaha, jeff is the best!10:21
=== ajmitch is trying to load it..
ajmitchhaha10:23
Treenaksmvo: try Jono Bacon too10:23
RiddellI've never seen any of the films Jono has taken10:24
Riddellwrong channel for this but10:25
mvoTreenaks: hahaha10:26
=== mvo shouldn't see this stuff while drinking tea
ajmitch:)10:26
=== Treenaks tries to imagine one of sabdfl :)
mvothat's going to be fun10:27
=== senecastudent [n=shanks@69.158.2.94] has joined #ubuntu-meeting
senecastudentHello everyone11:21
senecastudentanyone in here?11:22
=== senecastudent [n=shanks@69.158.2.94] has left #ubuntu-meeting []
=== doko [n=doko@dslb-084-059-081-172.pools.arcor-ip.net] has joined #ubuntu-meeting

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