[12:18] <somerville32> mdke: Can we discuss someway to reduce launchpad spam? lol
[12:19] <mdke> somerville32: you could setup a filter?
[12:20] <somerville32> There is nothing I could filter it on
[12:20] <mdke> filter launchpad bugmail
[12:20] <somerville32> I want launchpad bugmail
[12:20] <somerville32> I just don't want get launchpad bugmail on ubuntu documentation
[12:20] <mdke> I mean, filter it into a separate directory
[12:21] <somerville32> I tag it already
[12:21] <mdke> can't you filter?
[12:21] <somerville32> It has tagging
[12:21] <mdke> sounds like it sucks to me. Well, what solution do you propose?
[12:21] <somerville32> Maybe creating sub-teams and changing the bug contacts to these sub-teams?
[12:22] <mdke> and the subteam would be "everyone-except-somerville32"?
[12:22] <mdke> (the whole point of having bugmail is so members of the team can fix the bugs)
[12:23] <somerville32> Right but I'm wouldn't fix Ubuntu, Edubuntu, or Kubuntu documentation bugs - I'd fear stepping on people's toes.
[12:24] <mdke> generally lots of bugs appear in all derivatives. Potentially xubuntu is an exception, because it doesn't have much documentation, but you're here to change that!
[12:24] <somerville32> lol
[12:24] <somerville32> True
[12:24] <mdke> let's think it over, you may be right
[12:24] <somerville32> But then they should do proper triage
[12:24] <somerville32> And apply it to the Xubuntu documentation product
[12:24] <mdke> we do great triage!
[12:24] <somerville32> :D
[12:24] <somerville32> Awesome.
[12:24] <mdke> is there a separate product?
[12:25] <somerville32> I have no idea but I'm sure I could create one if there isn't already
[12:25] <mdke> I'm not convinced its a good idea
[12:25] <dsas> but I'm sure everyone can give input on most things, no matter which -docs package they care about the most.
[12:25] <mdke> part of the reason we keep the code together is to encourage this collaboration
[12:25] <mdke> the best solution may well for you to read the bugmail!
[12:25] <mdke> :p
[12:26] <somerville32> mdke: TBH, I really don't have time for that, lol
[12:27] <somerville32> And I don't think that changing the team layout would change how we collaborate. Xubuntu people are still expected to the Documentation and I'm still going to ask questions if I need help :)
[12:27] <somerville32> *to do the Documentation for Xubuntu
[12:28] <mdke> do you think it would have a confusing effect for people looking to file bugs?
[12:28] <somerville32> I think that it is more confusing for people now
[12:29] <somerville32> If Xubuntu user xyz wants to file a bug, I think they might hesitate before assigning it to the ubuntu documentation product
[12:29] <mdke> you may be right
[12:29] <somerville32> It would most likely get assigned to the Xubuntu meta package
[12:29] <somerville32> and then all of us would get spammed
[12:29] <somerville32> lol
[12:29] <somerville32> I see what you mean though
[12:29] <somerville32> About it being one big team
[12:30] <somerville32> And we should stress that we are STILL one big team
[12:30] <mdke> let's have a think. I still think the best solution may be to stay where we are, but you have some valid points
[12:46] <manicka> howdy mdke
[12:47] <LaserJock> well, my solution is that LP should have something that tells you why the heck you're getting the email
[12:48] <mdke> LaserJock: somerville32's complaint is about getting it in the first place
[12:48] <LaserJock> but I think it's fine to get it in the first place if you can at least sort it out
[12:48] <somerville32> Right
[12:48] <mdke> well, you can sort it out already
[12:49] <somerville32> Not in gmail
[12:49] <dsas> Some people don't realise and get angry though. Particularly when they file ubiquity bugs.
[12:49] <mdke> filter in the launchpad-bug header and content for ubuntu-docs
[12:49] <mdke> somerville32: that's gmail's fault though
[12:49] <somerville32> mdke: I want Xubuntu bugs
[12:49] <mdke> somerville32: "content for ubuntu-docs"
[12:49] <LaserJock> mdke: I don't think that'll work
[12:49] <LaserJock> it'll catch quite a few
[12:50] <LaserJock> my most of the bugemail I get doesn't really let me know why I'm getting it, which is annoying
[12:50] <mdke> oh, they use the short url for the bug link
[12:50] <mdke> sucks
[12:50] <LaserJock> somerville32: we don't have enough bugs to really worry about, IMO
[12:50] <LaserJock> and it's important to see what bugs are going on elsewhere in the repo
[12:50] <dsas> mdke: it makes sense, otherwise the package might have changed by the time you read it and it's then confusing
[12:50] <mdke> dsas: wouldn't prevent a reference to the task in the footer though
[12:51] <somerville32> LaserJock, I have a screen full of bugs for stuff I don't need to have
[12:51] <mdke> yeah, you're lucky you aren't subscribed to ubuntu-website, somerville32. I did the same amount of bugs on that this evening
[12:51] <LaserJock> the only thing I can see is the "it's confusing for users to know what to file a bug against"
[12:51] <dsas> mdke: Oh no, I think LaserJock is right it should say why you're getting mail about it,
[12:51] <LaserJock> somerville32: but I'm saying that rarely happens and I'll submit that you may need to have them
[12:52] <dsas> I get mail all the time from bug commentors, "here's the debug log you asked for", and I haven't a clue what package it is.
[12:52] <somerville32> LaserJock, It is mostly typos
[12:52] <LaserJock> there have been many occasions when an Ubuntu doc bug was also a Kubuntu doc bug, etc.
[12:52] <mdke> dsas: nod
[12:52] <somerville32> Right
[12:52] <somerville32> And in that case, the traiger should an apply to the xubuntu-docs product
[12:52] <LaserJock> dsas: mhm, I almost mentioned that when sabdfl asked about the Malone wishlist
[12:52] <dsas> LaserJock: Heh, my mind went blank at the time.
[12:53] <somerville32> Most cases where that would occur, I'm sure it is evident enough that someone would atleast mention it to us
[12:54] <LaserJock> somerville32: anyway, ubuntu-doc bugs are still important to at least filter through to see if anything applies to you
[12:54] <LaserJock> and doc bugs are a pretty small drop in the bucket ;-)
[12:55] <mdke> yeap
[12:55] <LaserJock> you could always filter against Matthew East ;-)
[12:55] <somerville32> lol
[12:56] <mdke> you'd miss all the wisdom though
[12:56] <somerville32> Do you really think I read them now? :P
[12:57] <LaserJock> I at least browse them
[12:57] <LaserJock> it's hard to tell what applies and what doesn't
[12:57] <LaserJock> and it's cool to see what's going on anyway
[12:57] <dsas> I read them and I haven't done anything in months
[12:58] <LaserJock> man, there are some real email junkies out there
[12:58] <LaserJock> the people that are subscribed to all of wiki.u.c
[12:59] <LaserJock> and to the bug mailing lists
[12:59] <LaserJock> I can't handle that much info flying at my face :-)
[03:54] <LaserJock> hi theCore_
[03:54] <theCore_> hi LaserJock
[03:55] <LaserJock> been thinking about some major Packaging Guide reworking lately
[03:55] <theCore_> oh?
[03:55] <theCore_> what kind of reworking?
[03:59] <LaserJock> well, more content, of course
[04:00] <LaserJock> reordering of examples
[04:04] <theCore> hmm... maybe I could help
[04:05] <LaserJock> I'll try to put up an outline on the wiki page tonight
[04:06] <theCore> ok then, I look at it and see what I can o
[04:06] <theCore> s/o/do/
[04:16] <somerville32> For the packaging guide and the packaging from scratch section, I don't think you should pull stuff from an already existing package.
[04:16] <somerville32> Kind of defies the premise of packaging from scratch
[04:31] <LaserJock> somerville32: it's also kinda hard to write documentation for packaging from scratch
[04:32] <LaserJock> without having an example
[04:32] <LaserJock> I'm think of putting debhelper first
[04:33] <LaserJock> but I know what you mean
[04:33] <LaserJock> I never really liked how that worked out
[04:34] <somerville32> Since I just recently learnt how to package, maybe I could help out?
[04:36] <LaserJock> yeah, once I get my thoughts down on paper, etc. I'm going to blog and email for people wanting to write
[04:36] <LaserJock> I don't have time to do it all myself
[07:02] <somerville32> Ok, so I lie :) I'm actually using my whiteboard.
[08:33] <somerville32> mdke: I thought that the documentation was built nightly and placed on doc.ubuntu.com
[09:36] <mdke> somerville32: that's broken atm
[09:36] <mdke> xubuntu probably still works, actually
[09:36] <somerville32> Unfortunately I don't see my changes
[09:37] <mdke> does "make all" in the xubuntu directory work?
[09:38] <mdke> yeah it does. Hmm, should be working
[09:41] <mdke> somerville32: oh, it is stuck on updated the repository due to a bug. I'll fix it
[09:42] <somerville32> Awesome :] 
[09:47] <mdke> ah, two bugs
[09:48] <mdke> all better now
[09:49] <somerville32> Is it rebuilding now?
[09:50] <mdke> it's done
[10:06] <somerville32> mdke: Did you get my e-mail?
[10:07] <mdke> somerville32: I don'y know
[10:07] <somerville32> I just sent it
[10:07] <somerville32> Regarding fesity documentation spec
[10:07] <mdke> email normally arrives ok, assume it got it
[10:07] <somerville32> mdke: I don't see the updates to the Xubuntu documentation yet
[10:08] <somerville32> oh sorry
[10:08] <somerville32> Cached
[10:08] <somerville32> :)
[10:08] <somerville32> I see it now
[07:12] <FactTech> mdke Are you online at the moment? Seveas pointed me to you.
[07:14] <FactTech> Is anyone online at the moment? I can't tell if I'm being block for not having registered my nick yet.
[09:22] <mdke> jenda: can you dispose of that nonsense in -locoteams pls?
[09:22] <jenda> mdke: working on it.
[09:22] <jenda> I don't have the power myself.
[09:22] <mdke> ok
[09:22] <jenda> mdke: which name are for kickin'?
[09:22] <mdke> those ones
[09:23] <mdke> also, maybe get ops for a few more people?
[09:23] <mdke> Seveas, myself, yourself, elkubuntu spring to mind
[09:48] <mdke> nixternal: if you wanna follow my example for Kubuntu maybe?
[09:49] <LaserJock> preview server?
[09:49] <mdke> LaserJock: you've forgotten all about the docteam :(
[09:50] <LaserJock> no, I just don't know what you are refering to :-)
[09:50] <LaserJock> doc.ubuntu.com ?
[09:50] <mdke> you remember we have that server at doc.u.c which hosts our documentation in development.
[09:51] <mdke> it's been broken since we rearranged the whole of our tree
[09:51] <LaserJock> yeah, I just don't think of it as a preview server, that's all :-)
[09:51] <mdke> aha
[09:51] <LaserJock> I think of it as doc development server, or something
[09:51] <LaserJock> anyway, I'm with you know
[09:52] <LaserJock> *now
[09:52] <mdke> http://doc.ubuntu.com/ubuntu/C/index.html
[09:59] <mdke> so why aren't there any translations in kubuntu-docs?
[10:01] <mdke> they are missing from debian/rules
[10:02] <dsas> mdke: I get a 404 at http://doc.ubuntu.com/ubuntu/C/newtoubuntu/windows.xml
[10:03] <mdke> dsas: yeah. it's not easy enough to fix right now
[10:04] <mdke> you'll see a fair few more too, sadly
[10:15] <mdke> jenda: !! are mailing list/forum deltas that easy?
[10:16] <jenda> mdke: it seems they are.
[10:16] <mdke> this is a chance of making significant progress in forum integration
[10:16] <mdke> jenda: I've replied excitedly
[10:16] <jenda> mdke: has me wondering, why we only have one so far.
[10:16] <jenda> :)
[10:17] <mdke> this has so much potential
[10:17] <jenda> 
[10:17] <mdke> damn, my screen has gone funny and I can't read what you just said
[10:17] <Seveas> mdke, yeah, I'll ask jono about more ops when he signs on
[10:17] <mdke> say it again?
[10:18] <mdke> Seveas: thanks
[10:19] <mdke> jenda: sorry, I missed your last comment. Can you repeat/
[10:19] <jenda> Seveas: I msg'd Yann about it.
[10:19] <jenda> mdke: it was just a smiley ;)
[10:19] <dsas> mdke: "" :)
[10:19] <mdke> damn you dsas, you made my screen go funny again
[10:19] <mdke> is this some hippy character that breaks irssi/screen?
[10:19] <dsas> mdke: Heh, you have a non UTF8 client.
[10:20] <bdmurray> mdke: works for me
[10:20] <willvdl> looks good in xchat
[10:20] <mdke> i think it's a gnome-terminal thing, it's been doing weird things to me recently
[10:20] <bdmurray> I'm using konsole, irssi, screen so maybe
[10:21] <mdke> I have irssi+screen on dapper and gnome-terminal on feisty
[10:21] <jenda> mdke: Confirmed - it's possible.
[10:21] <jenda> mdke: Ryan will get to it tonight.
[10:22] <mdke> jenda: I think one for devel-discuss should be the priority then. We should consult with whoever the admin of that is
[10:22] <jenda> shweet
[10:22] <mdke> admins
[10:22] <jenda> now... who is?
[10:22] <mdke> lists@admin.canonical.com
[10:22] <jenda> hehe :)
[10:23] <jenda> mdke: will you or should I?
[10:23] <mdke> I will
[10:23] <mdke> I'm *too* excited about this
[10:23] <mdke> hopefully it can be put in a good place in the forum heirarchy
[10:26] <jenda> mdke: have a look at teh current layout - I'd see the cleanest implementation as 'Community team mailing lists' below loco team forums.
[10:27] <nixternal> mdke: i will get the kubuntu side up tonight
[10:27] <LaserJock> mdke: what are you excited about?
[10:27] <mdke> nixternal: rock
[10:28] <mdke> jenda: i don't think it should be at the bottom at all
[10:29] <jenda> mdke: neither do I, but tech support takes the first spot.
[10:29] <jenda> make that below or above the loco forums ;)
[10:30] <mdke> jenda: it would certainly be in "Community Discussions" yeah, and thus under tech support. But I think it should be the first item in there
[10:32] <jenda> mdke: we probably won't push it ahead of the forum community.
[10:32] <jenda> (BTW, I didn't realise what I said first was at the bottom :))
[10:32] <mdke> well, I think the structure could be played around a bit there, but tbh, I'll be glad to see mailing lists there
[10:33] <jenda> Yeah - if it looks like it works fine, we can try negotiating a restructuring.
[10:34] <mdke> i'll cc you on the email
[10:35] <jenda> great, thanks.
[10:35] <mdke> sent
[11:04] <mpt> mdke, common/C/contributors.xml is missing according to doc.ubuntu.com
[11:05] <mpt> oh, and bravo for adding "Keeping your computer safe" :-)
[11:08] <mdke> mpt: there are quite a lot of broken links, I'm afraid