[01:51] <poningru> mdke: dude which laptop do you have?
[01:52] <poningru> presario 2100?
[01:52] <poningru> which one exactly though?
[02:36] <Burgundavia> salut all
[02:37] <LaserJock> hi Burgundavia 
[02:41] <Madpilot> hi Burgundavia 
[02:54] <LaserJock> hi bustacap 
[02:54] <Burgundavia> hmm, interesting thread on the wiki
[02:55] <bustacap> gday LJ
[02:57] <LaserJock> Burgundavia: how so?
[03:00] <Burgundavia> LaserJock: lots of good ideas
[03:08] <LaserJock> Burgundavia: do you think better use of Categories on a help.ubuntu.com wiki would be helpful?
[03:08] <LaserJock> like a category for each major area of documentation?
[03:10] <Madpilot> LaserJock, I was thinking about that too - not quite sure how to structure it, though
[03:14] <crimsun> LaserJock: you guys are in string freeze, correct? What will you do about changes to the packaging guide that potentially rearrange sentences to eliminate awkwardness and/or correct grammatical mistakes?
[03:15] <poningru> I thought minor changes didnt fall under string freeze,  just like minor bugfixes for software
[03:15] <poningru> but /me is not part of the doc team
[03:15] <crimsun> well, these potentially (definitely in most of the cases I see) affect strings.
[03:16] <LaserJock> crimsun: well, I'm going to do small changes. The pot files haven't been uploaded yet
[03:16] <crimsun> ok, good. I'm looking at it now.
[03:16] <LaserJock> crimsun: if you email me a list of changes I'll do what I can, ok?
[03:16] <crimsun> sorry I haven't been able to look earlier; ALSA work has been really ...forceful... lately.
[03:21] <crimsun> is "website" standardized in the documentation? The last place I worked used "Web site".
[03:21] <Burgundavia> LaserJock: yes, but sadly we cannot use better categories, due to having non-docs there
[03:21] <Madpilot> afaik it's one word in all our stuff, crimsun 
[03:21] <crimsun> ok, consistency it is.
[03:22] <LaserJock> Burgundavia: that is why I was saying in combination with BetterWikiDocs
[03:23] <Burgundavia> LaserJock: once we migrate to our own wiki, then yes
[03:23] <Madpilot> in combination with actually, finally moving the docs to help.u.c, you mean?
[03:23] <Burgundavia> yes
[03:23] <LaserJock> yes, that is what I was trying to say
[03:23] <Burgundavia> ah
[03:23] <Burgundavia> sorry, am currently cooking now
[03:24] <LaserJock> np
[03:42] <robotgeek> Burgundavia: blue is good :P
[03:49] <crimsun> LaserJock: do you prefer packaging guide diffs sent to you or to the list?
[03:49] <crimsun> (apologies if you've already answered, different proxy, multitasking, yadda yadda)
[03:49] <LaserJock> crimsun: me is fine
[03:49] <Burgundavia> robotgeek: blue is a not an Ubuntu colour
[03:50] <robotgeek> Burgundavia: heh, we see what we want. muhahaha
[03:53] <crimsun> LaserJock: patch 1 of ? sent.
[03:53] <LaserJock> crimsun: k, thanks
[03:55] <LaserJock> crimsun: wow, through. You must teach ;-)
[03:55] <crimsun> I actually missed a place: It should read "files are installed to the right places."
[03:57] <LaserJock> crimsun: k
[04:55] <Burgundavia> anybody awake?
[04:55] <Madpilot> hmm?
[04:56] <Burgundavia> can you take a peek at /Website/Desktop?
[04:56] <Burgundavia> I want to do the screenshots tonight and then move it to the website
[04:56] <LaserJock> I'm awake and getting close to panic mode
[04:56] <Burgundavia> LaserJock: why so?
[04:58] <Madpilot> Burgundavia, that Firefox screenshot that someone else put in there is not done w/ the stock desktop theme - you'll need to re-take it
[04:58] <Burgundavia> I realize that
[04:58] <LaserJock> Burgundavia: umm, something came up and I need to do some real tweaking on a section in the Packaging Guide
[04:58] <Burgundavia> ah
[04:59] <Burgundavia> the packaging guide is not critical, so it can release a bit later
[04:59] <Madpilot> in the OOo section, does Base really need it's own line? I'd just add, "and databases with Base" to the first line there
[04:59] <Burgundavia> Madpilot: make edits as you see fit
[05:03] <Madpilot> done, just a small edit
[06:00] <LaserJock> hi mpt 
[06:00] <mpt> hello LaserJock 
[06:04] <LaserJock> thanks for the email about Dive into Python. I had kinda forgotten about it
[06:05] <LaserJock> I used it a fair amount when I started learning Python
[06:06] <LaserJock> mpt: do you think the second part of my idea (community cookbook) was plausible?
[09:08] <mpt_> LaserJock_away, let us share in commiserations that the second parts of our respective e-mail messages weren't noticed :-)
[09:12] <mpt_> LaserJock_away, it looks very much like you're describing http://www.python.org/doc/
[09:13] <mpt_> particularly http://www.python.org/doc/topics/
[09:15] <Burgundavia> mpt_: what was the second part of your email?
[10:20] <mpt__> Burgundavia, the three things I'd love to see, and the three things I'd be disappointed to see, in Dapper+1
[10:23] <Burgundavia> mpt__: ah
[12:08] <mdke_> mpt__, I don't think that wasn't noticed
[12:14] <mdke_> i read it, anyhow
[12:16] <keith> Morning !
[07:55] <theCore> mdke: ping
[07:56] <mdke> theCore, pong
[08:15] <mdke> theCore, pong
[08:16] <theCore> mdke: sorry, I been disconnected
[08:16] <mdke> np
[08:16] <theCore> so?
[08:16] <mdke> theCore, I haven't seen your question yet
[08:17] <theCore> hmm
 mdke: what do you think about adding a CodingStyle for DocBook to the Style Guide?
 mdke: I really want to clean those files for Dapper+1
[08:17] <mdke> I'm not too bothered by that, to be honest.
[08:18] <mdke> in fact I think it might cause inconvenience, not sure
[08:19] <mdke> but we should definitely talk about it as a team
[08:20] <theCore> well, keeping the files like would cause inconviences too
[08:21] <theCore> it just a distraction
[08:22] <mdke> yeah, well, I'm not against the idea
[08:23] <mdke> personally, I always use the tab button to make a tree of tags
[08:23] <mdke> and don't bother breaking lines within paragraphs
[08:25] <theCore> this could bother peoples doesn't use line wrapping in their editor
[08:25] <mdke> it could do, but I just assume they will get over it, and concentrate on writing
[08:25] <mdke> anyway, everyone should use gedit ;)
[08:26] <theCore> :)
[08:27] <theCore> we can't force peoples to use a certain editor, it would be even more bothering
[08:27] <dsas> we could have a fun 'debate' about the worthiness of said editors though 
[08:27] <mdke> it's no contest, gedit is the best
[08:28] <dsas> vim > * tbh, everyone should know vim. It's the universal editor.
[08:28] <theCore> M-x praise-emacs
[08:29] <mdke> vim is just silly
[08:29] <mdke> what's going on with having to press a button before you can type
[08:29] <mdke> *shakes head*
[08:30] <theCore> so you can use hjkl for navigation
[08:31] <dsas> How many times do you edit an existing document versus writing a complete new one? Having command mode be the default means you can quickly get to the bit you want to edit.
[08:31] <mdke> theCore, i have arrow keys for navigation
[08:31] <mdke> and pgup/down
[08:32] <dsas> mdke: arrow keys are slooow
[08:32] <mdke> pgup/down
[08:33] <dsas> pgup/pgdn are also slow, you have to move your fingers away from the home row
[08:34] <mdke> pah
[08:36] <theCore> it's all about efficiency, which includes economy of motion
[08:36] <dsas> tbh I use gedit at home for most tasks, editing config files and docbook is vims job though.
[08:36] <theCore> less you move, faster you edit
[08:38] <mdke> theCore, i like to give my fingers a work out :)
[08:48] <theCore> mdke: did you ever tried to write a plugin for gedit?
[08:50] <mdke_> theCore, nope
[08:50] <mdke_> it can be made even better?
[08:50] <mdke_> surely not
[08:58] <theCore> mdke_: to write one, you must know to use GObject from C, not an easy thing
[09:01] <theCore> mdke_: with vi or emacs, writing one is trivial
[09:04] <theCore> ok, I think that I done enough editor advocacy today ;)
[09:07] <mdke_> heh
[09:07] <mdke_> gedit doesn't need plugins, it's too good
[09:10] <theCore> well, it could be better with an SVN plugin
[09:12] <theCore> you could make Gedit read your mail too ;P
[09:12] <mdke_> and make my dinner
[09:14] <theCore> you could make Gedit publish your recipes to the rest of the world
[09:16] <theCore> I think I'm corrupted by the `Emacs does everything' philosophy
[09:25] <dsas> theCore: You can write gedit plugins in python too
[09:26] <theCore> dsas: you still have to deal with GObject
[09:34] <mach> hi, I'd like to know if is it possible to translate the WIP documentation projects through Rosetta?
[09:47] <dsas> mach: the dapper docs to be translated are here: https://launchpad.net/distros/ubuntu/dapper/+source/ubuntu-docs/+translations
[09:48] <mach> dsas, hey, thank you very much
[09:51] <dsas> Splitting hairs probably, but shouldn't our docs to be translated be translated as an upstream project, rather than just as the Dapper thing?
[09:51] <dsas> I may just be going through my usual launchpad confusion.
[09:54] <mdke> there are some things to be cleared up there, so we haven't announced translation yet
[09:55] <dsas> Oh, sorry. What have we got left to do?
[09:56] <mdke> we need to remove a few templates from rosetta
[11:52] <LaserJock> theCore: heh, you still trying to get everybody to use emacs? ;-)
[11:55] <theCore> LaserJock: lol
[11:57] <LaserJock> the only thing that I'd really be worried about is tabs vs. spaces
[11:57] <LaserJock> anybody know what gedit does with tabs by default?
[12:00] <LaserJock> the main reason I don't use gedit is I'm usually writing over ssh or on OSX