=== 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 [04:03] <- Troy Williams [04:03] hello [04:03] hiya [04:03] hi :) [04:03] <- Henrik Nilsen Omma [04:04] Matthew East [04:04] Karl Goetz [04:04] (not on wiki) [04:04] Robert Stoffers [04:05] i will just be in and out, as per my email today === apokryphos [n=apokryph@70.85.216.98] has joined #ubuntu-meeting [04:05] hmm, looks like I'll have to forward a lot of the agenda to the mailing list [04:05] is jbailey coming? [04:05] not sure [04:06] yeah i was just hilighting him [04:06] :) [04:06] heh [04:06] Nick highlights in irssi suck. [04:06] fabbione: Thanks. === jeffsch [n=jeffsch@fatwire-204-157.uniserve.ca] has joined #ubuntu-meeting === Treenaks [n=martijn@messy.foodfight.org] has joined #ubuntu-meeting [04:06] lol [04:06] :) [04:06] hey jeff [04:06] For some reason they only seem to highlight at the beginning of a sentence. === jbailey needs to switch back to x-chat soon. [04:06] jbailey, mine go a different colour if it is in the middle [04:06] jbailey: it does that by default. Nice feature. [04:06] mmm xchat [04:07] jbailey, [15:06:53] hilightwin /home/matt/.irssi/scripts/autorun/hilightwin.pl [04:07] Mithrandir: Suck feature. I miss pings all the time. [04:07] oh no, that's something else [04:07] jbailey, i guess you can set it to hilight in the middle [04:07] jbailey: define your own highlight thingy, then [04:07] Mithrandir: What I really want is my graphical x-chat do be able to work in a screen session. [04:08] Mithrandir: But I think I've mentioned this wish to you and you suggested NX [04:08] me too [04:08] anyhow are we go? [04:08] jbailey: yes, true. Be aware of the crack levels therein. [04:08] yes, I gotta go to work soon [04:08] merging back to trunk: kubuntu has been done already, who is going to do ubuntu stuff? === jbailey grabs the agenda. [04:09] what does it intail? just copy/paste? [04:09] i don't know [04:09] there is some clever svn merge thing [04:09] What it needs is the layout of the repo thought about first. === mdke nods [04:09] I wound up in the end just hacking things so that they'd work. [04:09] So it's not just a clean merge back. [04:09] ok [04:09] Can you move this to after the repo layout item? [04:09] s/you/we/ [04:09] good idea [04:10] can we do that? [04:10] sure, why not? [04:10] Up to whoever is running the meeting, really. =) [04:10] ie can we merge back to a new layout automagically? [04:10] Oh. =) [04:10] oh [04:10] why not merge back, then chop up? [04:10] No, it'll be a series of copies, but that won't be hard I don't think. [04:11] oh ok, I thought so [04:11] The 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] why not just import to baz while we are moving stuff around anyway [04:11] jbailey, what about judax's idea there [04:11] hno73, we'd have to take the decision to use baz [04:11] that's meant to have better merging right? [04:12] Right, 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] mdke: it seems to be on the agenda [04:12] jbailey, changes made since the branch [04:12] hno73, yeah :) [04:12] mdke: I thought everyone had been trunking those as well? [04:12] jbailey, nope [04:12] Ah, okay. [04:13] Umm. I guess I'm the most familiar with the stuff, so I should do it. [04:13] i like judax's idea [04:13] merge back and then rearrange directory structure accordingly [04:13] i like jbailey's idea [04:13] Right, but merging back means what? [04:13] I think that would make life easier [04:13] Rearranging the repo should happen on the trunk, yes. [04:14] The branch needs to be pretty much considered locked at the point. [04:14] ok, so it's the same idea [04:14] yep [04:14] Changing it would make doing occasional snapshots quite hard. === jbailey ^5's judax === rob^ brb [04:15] ok so what does the merge entail === rob^ back [04:15] copying anything in the branch that has changed since it was branched right? [04:15] mdke: Right, except in cases where people have contributed stuff on the trunk. === mdke nods [04:16] when are we gonna do it? [04:17] Can do this afternoon or maybe Monday. [04:17] I'll try this afternoon so it doesn't block people. [04:17] you can examine the changes in the working copy (trunk) and the branch [04:17] by doing a --dry-run [04:18] nice one [04:18] Yeah. [04:18] diff is my friend, too. =) [04:18] I don't think svn has much of a concept of merging changesets from branches to the trunk (like bzr would) [04:19] ok cool [04:19] shall we move on [04:20] ok [04:20] gonna be hard seeing as hes not here.. [04:20] UBZ is a bit of a red herring afaics because only corey will be there, there might not be much docs discussion [04:20] I will be as well, but I'm not sure how my time will be spread out. [04:21] yeah [04:21] perhaps the best thing is to play it by ear and comment on any relevant BOFs on the mailing list? [04:21] there is a nice chapter in the svnbook (svnbook.red-bean.com) about Branching and Merging, just FYI [04:21] judax: Thanks, I'll reread it. [04:21] mdke, sounds like a good idea [04:22] the only thing I'm concerned about is some of the stuff mentioned in the BOFs [04:22] judax: I have the page bookmarked for how to do .cvsignore equivalents. =) [04:22] rob^: Like what? [04:22] rob^, don't forget bof's are just ideas [04:22] jbailey: ah :) [04:22] things like in line help are a little pie-in-the-sky [04:23] ms has been doing it for years anyway with their question mark thing, and no body cares about that either [04:23] in the end I expect pretty much the status quo to happen anyway [04:24] rob^: 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] I don't know if it's doable or not. [04:24] jbailey, thats a lot of work [04:24] rob^: It's far more work for the docteam to do it after the fact. [04:24] some specs are just "fix " [04:25] Kamion: Sure, but should that fix not be documented so that it's understood after? [04:25] I think we'd want a little more selectivity than a blanket requirement [04:25] Kamion: 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] depends on how much the person who scheduled the BOF knew about the code - I've had specs that were utterly obvious [04:26] I'm thinking that such a change would mean we would be forking everything from upstream, ie adding lots of code to each program [04:26] as long as there's an exception process, no problem [04:27] ubuntu already gets accused of being a Debian fork, this would only serve to make it worse I think [04:28] jbailey: what do you mean by 'doc component' in a spec? [04:28] rob^: I see less of those accusations now that the random nay-sayers are getting ignored =) [04:28] heh [04:28] I'm not saying it is, but why give them more ammunition? [04:29] i think you two are talking at cross purposes, jbailey's proposal was not to add code to every program [04:29] as i understand it [04:29] he is just saying, specs should be documented [04:29] how else would you implement in line help? [04:29] Kamping_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] rob^, he is not talking about in line help at all afaics [04:30] Sorry, I was still mention things for UBZ [04:30] mdke, thats what I was on about [04:30] jbailey: so the programers write all/some help, and what does the docteam do? make it usefull? other? [04:31] rob^, true but that doesn't stop the subject from being changed [04:31] mdke, heh yeah [04:31] the docteam can edit it and de-geekify it so users can understand it [04:31] lol. i see. well put jeffsch :) [04:31] the problem is really that the docteam only has a handful of contributors [04:31] if 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 these [04:31] at least at the moment [04:31] apokryphos, that is quite a controversial statement [04:32] I stand by it [04:32] lots of people accept that part of writing programs is documenting them [04:32] I don't think I know any programmer who has the task of just coding. There's always meetings, documentation, end-user troubleshooting, etc. === mdke nods [04:32] small things like those; but, for example, it shouldn't be a coders job (per se) to write a handbook for a given app [04:33] not a handbook, a basic help to help the doc team, surely? [04:33] in 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 them [04:33] not full-on documentation, but at least 'spec-form' documentation [04:34] the 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 up [04:34] (quite like a reporter, in some ways) [04:34] whos going to have the time to round all these up and de-geekify them anyway? [04:34] rob^: Well, it's best-effort. =) [04:35] heh [04:35] I 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] I wonder if we can wiki-ify them to allow anyone to help us [04:35] My thought is that the people implementing the specs should have some interest in seeing the documentation written. [04:36] basic user documentation is probably paramount, but more geeky documentation is necessary for giving other users the better user-experience [04:36] jbailey: definitely [04:36] apokryphos: 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 those [04:37] definitely; things like "What's This" help are of course the job of the coder === 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 [04:37] apokryphos, thats what I was touching on before [04:40] shall we move on? [04:40] going 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 requiered === jjesse [n=jjesse@mail.ftpb.com] has joined #ubuntu-meeting [04:40] too late? [04:40] no, hi [04:40] hi :) [04:40] sorry had to solve an emergency at work [04:41] shall we progress to the next agenda item? [04:41] or do people have more points about docs at UBZ [04:41] Kamping_Kaiser: that's "not optimal" certainly but doesn't refute "better than nothing", I think === ealden [n=ealden@219.90.91.16] has joined #ubuntu-meeting [04:42] 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 waste [04:42] Kamion: sure. and i dont mind about next item fwiw [04:43] any more for any more? [04:43] ok translations - does anyone want more information than I've set out in my email to the list today? [04:43] no, it all sounds good mdke [04:44] any idea of time frame? [04:44] that covers it, imho [04:44] i didnt realy follow, but i havent seen it in action :| [04:44] Kamping_Kaiser, http://article.gmane.org/gmane.linux.ubuntu.doc/3521 [04:44] i had originally said about a month [04:44] ok [04:44] because that is about time of language-packs [04:44] oh ok cool [04:45] but i don't think that is a major thing [04:45] Yay, langpacks. [04:45] ta rob^ [04:45] np [04:46] jbailey, got any issues about translation updates? === jsgotangco [i=jsgotang@info1-190.info.com.ph] has joined #ubuntu-meeting [04:46] mdke: Nope. Just need to figure out the langpack thing with Martin. [04:46] bloody hell === jsgotangco is in a cafe in a hotel [04:47] lol [04:47] mirc has the lousiest interface ever === jsgotangco lurks [04:47] heh [04:47] jbailey, well that is for dapper. We're on breezy [04:47] mdke: Right, sorry. [04:47] None for breezy. =) [04:48] cool [04:48] next [04:48] sorry, I have to get up in ~4 hours for work [04:49] Big picture stuff for dapper - for me is just langpacks and nightly snapshots. [04:49] snapshots +1 [04:49] snapshots of ? [04:49] jjesse: The trunk of the repository [04:49] Uploaded weekly to dapper for wider review. [04:50] jbailey: which will then include the kubuntu-docs? [04:50] snapshots is good [04:50] jjesse: 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] well we can ask Ridell for that.... [04:51] jjesse: 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] In terms of producing snapshots, though, no skin off my teeth. =) [04:51] did i miss the discussion of the infrastructure? [04:51] jjesse: no [04:51] It'll be largely automated. [04:51] i can talk to Riddell about the daily snapshots of kubuntu dapper including the docs [04:52] jjesse: Cool. I just don't want to see all of those treated as second-class citizens. [04:52] jjesse: But I'm not sure the best way to do that. [04:53] jbailey: don't worry i'll keep bugging Riddell for any help i need we have worked together for the breezy docs [04:53] jbailey, why are you concerned about the docteam doing ubuntu, kubuntu etc? there is only one docteam, not more than one. [04:53] mdke: I'm wondering how the docteam decides whether it cares about a derivative or not. [04:53] jbailey, it's a question of having willing contributors === Riddell turns up [04:53] I hope this bloody thunderstorm goes away or I'm gonna have to go [04:53] mdke: Like, someone decides to do Xubuntu. Does it suddenly become the docteams responsibility? [04:54] it seems that way [04:54] jbailey, i think that would be a question for the team, but certainly it has decided to include kubuntu [04:54] and jerome has done work on edubuntu [04:55] jbailey: it cares about them if they're official projects, I'd imagine (i.e. being in MAIN etc) [04:55] if its *ubuntu and someone wants to write docs sure [04:56] what you would get is teams that only have 1 member [04:56] i don't want to do work on some other svn for sure [04:56] agreed jsgotangco [04:56] Right. [04:56] i'd say we remove the upstream stuff though... [04:56] the current trunk is like 250MB [04:56] I just don't want suddenly it to become "do your own derivative, have the docteam take care of it" [04:57] that is where you have a problem though, you need to do what is right for the distro [04:57] jbailey, yeah, the team can decide what to work on [04:57] Half 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] maybe, but that doesn't mean we have to accept them [04:57] I 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] obviously we need to build contributors for ubuntu and kubuntu, but if people want to work on other ubuntu-related, that is cool [04:58] i'd like to focus on Partner Projects [04:58] jbailey, we can have separate source packages, and one repository with a number of separate directories, as suggested by rob^ [04:58] so that's 3 projects [04:58] shouldn't we have a "head" of ubuntu-docs a [04:58] if somone has comit on svn, can they commit to an project corrently? or can it be restricted? [04:58] jbailey, https://wiki.ubuntu.com/DocteamRepositoryLayout [04:59] Kamping_Kaiser: its an open svn :) [04:59] Kamping_Kaiser, no all [04:59] "head" of kubuntu-docs and "head" of edubuntu-docs, etc [04:59] rob^: Cool. I save comments until the right part of the agenda. [04:59] ok :| thats not helpfull ;O [04:59] (Lagging a bit, conference call) [04:59] it is true that we need to encourage contribution to partner projects before we can have the manpower to contribute on things like xubuntu [05:00] yes === jsgotangco will focus on kubuntu and edubuntu [05:00] anyhow, what other big pictures for dapper? [05:00] i will focus on kubuntu [05:00] we need to think about what docs to write [05:01] let's make the specs again from DocteamProjects [05:01] for dapper i have started wiki.ubuntu.com/KubuntuDocs [05:01] mdke, as a side thing I would like to get some of the upstream xubuntu docs and have them available maybe with modification in xubuntu [05:01] upstream xubuntu? [05:01] I mean xfce [05:01] they have an svn repo [05:01] please make efforts as much as possible to look at upstream work just in case :) [05:02] or fix our upstream as well :) (scrollkeeper borkage) [05:02] thats what I have been/am going to do [05:02] for gnome, there's current upstream 2.12 on the works, but not optimistic about it :) [05:03] xfce have a nice user guide [05:03] are we going to try and complete the ubuntu userguide? [05:03] it has a distinct aim from the faqguide, but overlaps in many respects [05:04] yes, I did a lot of work during breezy to not overlap as much as possible [05:04] i would favour trying to get it back up and running [05:04] mdke: for kubuntu docs that i have started to focus on for dapper please see http://wiki.ubuntu.com/KubuntuDocs [05:04] jjesse, ok, you need to mark things in DocteamProjects if you can [05:05] jjesse: we have to update the KQuickGuide though... [05:05] even halfway... [05:05] at least there won't be that much changes for Dapper unless we actually see KDE 3.5 :) [05:05] jsgotangco: yes we do, update it all the way, quickguide release notes, userguide are the ones [05:05] jjesse, do we still want to use kudos for a kubuntu faq guide? [05:05] rob^: yes i have seen some requests in #kubuntu for faq guide [05:06] yes [05:06] rob^: maybe we can work together on that one [05:06] kudos would be a good start [05:06] jjesse, I'd like to have it done for dapper [05:06] jjesse, sure [05:06] rob^: ok === jsgotangco is still getting used to KDE...but doing good atm [05:07] jjesse, does kudos have an xml version by any chance? [05:07] none [05:08] we can grep it though [05:08] sorry kudus is? [05:08] it is like ubuntuguide.org [05:08] ah [05:08] jjesse, the kubuntu unofficial faq guide [05:08] that's the kubuntu faqguide... [05:08] yeah [05:08] I'd like to use that to save work [05:08] do i need to get permission to create a docbook file of that from someone? [05:08] we need to check the licences [05:08] if its licensed accordingly, you can use it [05:09] I think sean said we have premission to use it under our current licences though [05:09] but dig the list archive for details [05:09] yes [05:09] i asked the author about it [05:09] didn't sean talk to the author? [05:09] me and sean [05:09] apparently [05:09] we have permission [05:09] jsgotangco: ok [05:09] ok [05:09] we'll just see if its updated [05:09] its in berlios [05:09] an xml? [05:10] i heard on #kubuntu that it's not updated [05:10] (actually its a good ton of work) [05:10] rob^: we wish [05:10] but haven't checked myself [05:10] jsgotangco, yes we do :) [05:10] its quite good....very visual for an faqguide [05:10] do we have premission to use the site as is? [05:10] ie can I copy it from there tomorrow? [05:10] well that's another story [05:11] does not look updated to me atm [05:11] we asked the author to work in svn before, but he declined [05:11] I'd like to start some work on that in about 6 hours if I could [05:11] rob^: no rush, focus on your xubuntu :) [05:11] heh [05:11] we can take kde from here :) [05:11] jsgotangco: do you want to create the file or should i? [05:12] ok [05:12] I'll just follow your lead [05:13] i'll fix the kquickguide first [05:13] ok can we move on? [05:13] i'll grep the kudos site later when i get home [05:14] help.ubuntu.com and doc.ubuntu.com on the new server are now available for all to see [05:14] holy heck its pouring outside [05:14] comments to the mailing list i would say, otherwise we'll be here for hours [05:14] mdke: both are in server pronto already? [05:14] yes [05:14] refresh your caches [05:14] good good === mdke points at hno73 's funky artwork [05:15] no css on doc.u.c? [05:15] :) [05:15] rob^, eh? [05:15] re: kudos. They guy seems generally pretty understanding, but has very big plans [05:15] rob^: got none here [05:15] hmm no there we go mdke [05:15] (said he wanted to make most of the steps into shell scripts, so users could just run them) [05:15] apokryphos, ouch [05:16] yikes [05:16] hm. [05:16] in 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] each to their own I guess [05:17] k, back to help.ubuntu.com, some things to discuss as per my email [05:17] there's some really useful stuff (I incorporated some stuff into kde docs), like the given Linux application with win/mac equivalent -- very handy for newbies [05:17] 1. whether to include translations [05:17] yes, that matrix is nice [05:17] 2. whether and how to include the bar and side panel to all docs [05:18] 3. please fix the kde docs so I can add them [05:18] 1 - yes I think we should [05:19] 2 - Yes, I think we should [05:19] i think we shouldn't, because I think that locoteams will want to host their own [05:19] -fr and -it are already in that process [05:19] and they will no doubt change things like appearance to make the guides in tune with their websites [05:19] :) [05:19] also, it will get messy if we host 30 translations [05:19] can we alter the html on help.u.c at all? [05:19] mdke, maybe we can have an additional translations page [05:19] rob^, comments about the page itself are probably best postponed to the list imo [05:19] yep [05:19] but sure, we can change anything [05:20] it's our server [05:20] hmm nice [05:20] i had thought, a link to a list of the various locoteam webpages === rob^ thinks about using his l33t html/php coding skillz [05:20] oh crap [05:21] I gotta go, the thunderstorm outside is getting pretty bad [05:21] later rob^ :) [05:21] bye [05:21] cyas [05:21] later [05:21] did I miss the meeting? [05:21] so does anyone else have any thoughts about translations? perhaps we can ask the locoteams themselves? they would be well placed to offer advice [05:21] whiprush: not much :) [05:21] whew [05:22] mdke: ask locos on the list? i dont hav any ideas about it [05:22] mdke: 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] mdke: link to all translations; some will be hosted locally, others on translation team sites [05:22] jeffsch, that will take quite a bit of maintaining [05:22] jsgotangco, no, not their work, translations of the docteam stuff [05:23] this would be hard, but on a help page offer links to the same page translated by the doco teams? [05:23] mdke: not if it's a wiki page :) [05:23] it'd be nice if we can just link 'em but if we got a nice server why not... [05:23] mdke: what's the status of translations at the moment? [05:23] then teams can update the links themselves [05:23] aye, like the one in edubuntu.... [05:23] Riddell, for ubuntu-docs the status is at http://launchpad.net/products/ubuntu-docs [05:23] hno73, nice idea [05:24] Riddell, kubuntu stuff isn't translated [05:25] hno73, have you got moin up on there already? [05:25] mdke: no, but I expect it to be up later today [05:25] cool [05:25] I have a side menu thing working in moin now [05:25] wow [05:26] so we can have the same side menu as the rest of the site [05:26] excellent [05:26] hno73: is the frontpage of the edubuntu.org site in moin too? it has a side menu thing [05:26] i have to split have another work meeting :( [05:26] later jjesse [05:27] :( later jjesse [05:27] bye [05:27] bye jjesse [05:27] jsgotangco: no, that's plain html [05:27] mdke: concerning #3, I just built kak (About Kubuntu), what problem are you experiencing [05:27] but it would be nice to make it moin based === jeffsch goes off to work :( [05:28] later mate [05:28] I think we've lost a pile of people. Should we punt the other items to next time? [05:28] judax, i'm experiencing this: http://help.ubuntu.com/kde/about-kubuntu/C/ === jeffsch [n=jeffsch@fatwire-204-157.uniserve.ca] has left #ubuntu-meeting ["gone] [05:29] jbailey, yes we can, or pursue them on the mailing list [05:29] mdke: that's using the KDE non-web stylesheet [05:29] mdke: the style [05:29] yes [05:30] if that can be sorted out, I'll put em up and link em [05:30] you want to use the KDE web stylesheet, which is in a top secret place. or just a normal stylesheet === jsgotangco will have to learn more KDE steylesheets [05:31] what stylesheet do you want [05:31] Riddell, either way, if you fix it, I'll build it and put it up on that site [05:32] mdke: what do I need to fix? what's the command used to generate that? [05:32] make kak === ian_brasil [n=vern@pintada.proamazon.com.br] has joined #ubuntu-meeting [05:32] We probably need a make kak-web [05:34] ok [05:34] also for whatever other documents to be hosted online [05:34] ahhh Riddell you seem to have svn access now? [05:35] are we still meeting? [05:36] well i can't stay long, i'm still outside, its almost midnight here, need to catch a cab === jsgotangco will just check the log later [05:37] doestn seem like ther will be mucht o check [05:37] ok we're done i think [05:37] ok. fair enough [05:37] we need to chase up this directory structure, use of gnome-doc-utils build stuff at a later date [05:38] ok [05:38] ah so we're stalemate on the structure? [05:38] is it merged already? [05:38] we didn't get that far [05:38] merge first [05:39] ok sounds good [05:39] shall I prepare an announcement for help.ubuntu.com? [05:39] hno73? [05:39] mdke: sure, thanks [05:39] great [05:40] take care all [05:40] :) === judax [n=troy@adsl-70-240-14-115.dsl.austtx.swbell.net] has left #ubuntu-meeting ["Konversation] [05:40] ok gotta go too [05:40] hno73, will you link it in www.u.c/support? [05:40] sounds like it done then :) [05:41] ok guys later === jsgotangco [i=jsgotang@info1-190.info.com.ph] has left #ubuntu-meeting [] [05:41] later mate [05:42] mdke: yepp. Shall we launch now or on monday? [05:42] up to you [05:42] the wiki stuff isn't ready [05:42] true [05:42] that will take a while [05:42] but that can come later I guess [05:42] and things can be added gradually [05:42] cool, ok [05:47] Riddell, ping me if you manage to sort that kak-web thing out :) [05:49] ok === 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 [05:56] hey everyone [05:57] hi [06:05] mdke: if you need something announced on the fridge let me know. [06:05] I'd like to showcase more docteam stuff on it. [06:07] cool [06:07] if I ever get onto planet I'll do it there too [06:07] whiprush, i'll copy you the announcement? are you jorge@u.c? [06:08] I'm always on irc so ping me when you want something done. [06:08] I don't have a u.c address yet. [06:08] fridge-devel@ works though [06:08] ok [06:08] jdub can run stuff also, but he's on tour. :p [06:09] yup === 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 [10:14] http://foodfight.org/movies/2005-10%20Ubuntu%20Fanpeople/ [10:20] Treenaks: nice! [10:20] mvo: thanks :) [10:20] mvo: I'll take my cam to UBZ, so you can try it too :) [10:21] heh [10:21] haha, jeff is the best! === ajmitch is trying to load it.. [10:23] haha [10:23] mvo: try Jono Bacon too [10:24] I've never seen any of the films Jono has taken [10:25] wrong channel for this but [10:26] Treenaks: hahaha === mvo shouldn't see this stuff while drinking tea [10:26] :) === Treenaks tries to imagine one of sabdfl :) [10:27] that's going to be fun === senecastudent [n=shanks@69.158.2.94] has joined #ubuntu-meeting [11:21] Hello everyone [11:22] anyone in here? === 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