[12:15] <JoseStefan> ok, done
[12:19] <FireRabbit> well, edgy is currently for people who want to help find bugs... update-manager is no exception...
[12:20] <crimsun> LaserJock: 10-4
[12:21] <LaserJock> crimsun: ubuntu-docs is a product for doc team bugs
[12:21] <crimsun> the issue at hand was the editing of /community
[12:22] <crimsun> not being current on doc policy, I didn't know that anyone could add/edit that hierarchy
[12:22] <JoseStefan> me neither, that's why i came here first ;)
[12:23] <FireRabbit> hense the name 'community' :)
[12:23] <crimsun> there's way too much going on. Two of my seniors are defending theses tomorrow morning; I have a sponsor meeting; tomorrow's REVU day ... it just never ends.
[12:25] <LaserJock> mhm
[12:30] <crimsun> what's the status of the "contributing" doc that andreas is working on?
[12:30] <JoseStefan> thanks for everything...
[12:38] <LaserJock> crimsun: I think it's in the svn repo
[12:39] <LaserJock> crimsun: but I'm not sure if it's in the help system yet or not
[02:31] <JoseStefan> Is there any wiki or other doc, that describes EOL of ubuntu releases?
[02:31] <LaserJock> hmm, I'm not sure
[02:32] <JoseStefan> i don't know if i'm using the wrong search terms, but i can't seem to find any
[02:32] <LaserJock> what specifically are you looking for?
[02:32] <JoseStefan> for example: what is official EOL of hoary?
[02:33] <LaserJock> 18 months from release I believe for normal releases
[02:34] <JoseStefan> well, i know about the 18 months, but is there such thing as a known deadline? since it's common for ubuntu dates to wrap to Thursdays
[02:34] <JoseStefan> by that i mean exact known date
[02:34] <LaserJock> oh, no
[02:34] <LaserJock> I think it's determined by the releases
[02:35] <LaserJock> so I think warty was EOL when Dapper was released
[02:36] <JoseStefan> So hoary would be expected to EOL on the same day Edgy is released?
[02:36] <LaserJock> I would think so
[03:37] <JoseStefan> I have updated the Releases wiki to include brief description of LTS and EOL
[08:37] <DBO> the ubuntu wiki on compiz is horribly out of date (though still technically working), I would like to overhaul the whole thing if thats ok with you people
[08:38] <Madpilot> DBO, go nuts. It can't possibly break more machines than XGl/compiz already do ;)
[08:39] <mpt> Sure, DBO, go ahead
[09:05] <FireRabbit> DBO: hey speaking of that, I just overhauled the AIGLX page.
[09:05] <FireRabbit> id be happy to help with compiz too, i was just looking at how bad that is
[09:07] <DBO> FireRabbit, I am holding out just a little bit for the release of beryl
[09:07] <FireRabbit> beryl?
[09:07] <DBO> which is going to screw aiglx and compiz sections up anyhow
[09:07] <DBO> oh you dont know, compiz is forking
[09:07] <FireRabbit> oh great, all the guides are going to break again!
[09:08] <DBO> exactly
[09:08] <FireRabbit> beryl = quinnstorm's branch, with csm, etc. ?
[09:08] <DBO> yes
[09:08] <DBO> I talk with the devs on a daily basis
[09:08] <FireRabbit> and "compiz" will continue to use gconf?
[09:08] <DBO> so we will make sure everything is working right
[09:08] <DBO> compiz-vanilla will become compiz
[09:08] <DBO> and will of course use gconf
[09:08] <FireRabbit> okay
[09:08] <DBO> compiz is becoming beryl, and will use csm
[09:09] <DBO> amoung its many other enhancements
[09:09] <FireRabbit> gotcha
[09:09] <DBO> I'll be writing a switch to beryl guide as soon as package names and release dates are finalized
[09:09] <FireRabbit> okay
[09:09] <DBO> and be overhauling the ubuntu wiki the same day
[09:09] <FireRabbit> great, great
[09:09] <DBO> if you want to help with the aiglx section that would be fantastic
[09:09] <DBO> are you an aiglx user?
[09:10] <FireRabbit> sure, although i didnt mention any compiz-related stuff on the AIGLX wiki, just 'go here for the next step'
[09:10] <DBO> thats fine
[09:10] <DBO> I am going to write a full guide for the wiki once beryl is released
[09:10] <DBO> most ubuntu users think of compiz-quinn when they think compiz
[09:10] <DBO> and thats what I am going to suggest users use
[09:10] <FireRabbit> nod
[09:11] <DBO> but we are going to need guides for both compiz and compiz vanilla since there will now actually be two composite managers available
[09:11] <DBO> which is going to be a total nightmare
[09:11] <FireRabbit> i am using xgl on here (nvidia card), a friend of mine installed AIGLX so he helped me update the wiki.
[09:11] <FireRabbit> heh
[09:11] <FireRabbit> well as long as they dont both have "compiz" in the name, i think we can sort the docs out.
[09:11] <FireRabbit> so i am happy to hear about the name change.
[09:12] <DBO> well they both still going in composite manager
[09:12] <DBO> just different sub-pages
[09:12] <DBO> since the xgl/aiglx setup portion is the same for both of them
[09:12] <FireRabbit> right
[09:12] <FireRabbit> Beryl and Compiz. 
[09:12] <DBO> and the repos arent changing (minus possible domain changes)
[09:13] <DBO> also ubuntu needs to settle on a standardized way to start Xgl
[09:13] <FireRabbit> no kidding
[09:13] <DBO> I am thinking we should drop the session method
[09:13] <FireRabbit> the compiz installation page is horrible
[09:13] <FireRabbit> i agree
[09:13] <DBO> good
[09:13] <FireRabbit> doesnt make sense for GDM to use a different X server than your session
[09:13] <DBO> so the guides will only modify either kdmrc or gdm.conf-custom
[09:14] <DBO> exactly
[09:14] <FireRabbit> that is something that will need to be updated on the AIGLX page, i dont know anything about KDM.
[09:14] <DBO> oh its easy
[09:14] <FireRabbit> https://help.ubuntu.com/community/CompositeManager/AIGLX
[09:14] <DBO> oh wow you did overhaul it
[09:15] <DBO> can you add a table of contents to that and proper headers?
[09:15] <DBO> (look at another page for hints)
[09:15] <FireRabbit> yeah alright
[09:15] <DBO> then I will add the kdmrc method
[09:15] <FireRabbit> cool.
[09:18] <FireRabbit> do you know if anyone has spoen with the gdm/kdm/xorg package maintainers to try to come up with some way for packages to set the X server, so users dont need to do it by hand?
[09:19] <DBO> i dont think thats a good idea
[09:19] <DBO> its alpha software
[09:19] <DBO> it shouldnt be touching core config files
[09:19] <FireRabbit> true
[09:20] <DBO> perhaps later on when its stable and all the memory leaks have been plugged
[09:20] <FireRabbit> nod, sounds good
[09:21] <FireRabbit> i added a TOC to that page.
[09:21] <DBO> ok I will add the aiglx method
[09:22] <DBO> erm
[09:22] <FireRabbit> s/aiglx/kdm/ ?
[09:22] <DBO> kdm
[09:22] <DBO> yes
[09:22] <FireRabbit> ok, thanks.
[09:22] <DBO> eeek
[09:23] <DBO> I wouldnt suggest aiglx to voodoo users... its just not pretty
[09:23] <FireRabbit> haha
[09:23] <DBO> Im going to remove that till I get better confirmation from users that its working better
[09:23] <FireRabbit> i copied that from the official page
[09:23] <FireRabbit> go head.
[09:23] <FireRabbit> maybe make "extremely slow" italic in the line above it? :)
[09:23] <DBO> naw...
[09:24] <DBO> i just dont think its a good idea right now
[09:24] <FireRabbit> i mean, under ATI
[09:24] <DBO> that information was not intended to be used in that manner
[09:24] <DBO> we will get so many broken xorgs it will be redonkulous
[09:24] <FireRabbit> heh
[09:25] <DBO> blutkind is broke
[09:25] <DBO> removing
[09:25] <FireRabbit> oh ok.
[09:25] <FireRabbit> its still on xgl.compiz.info
[09:26] <DBO> yes I know
[09:26] <DBO> sudo ln -s /usr/lib/xorg/modules/input/ /usr/lib/xorg-air/apt-cmodules/   =P
[09:26] <DBO> typo =P
[09:26] <FireRabbit> whoops
[09:26] <FireRabbit> good eye
[09:27] <DBO> gdm.conf-custom already exists, you dont need to create it =)
[09:27] <FireRabbit> oh, okay.
[09:27] <FireRabbit> its been a while. :)
[09:27] <DBO> =)
[09:27] <DBO> just letting you know
[09:27] <FireRabbit> i appreciate it
[09:28] <FireRabbit> might as well make sure all this stuff is accurate 
[09:29] <DBO> gonna add a section for filed to backup
[09:30] <FireRabbit> for what exactly?
[09:33] <DBO> erm
[09:33] <DBO> files that need to be backed up
[09:33] <DBO> as a safety measure
[09:34] <FireRabbit> ah okay
[09:34] <DBO> ok updated
[09:34] <DBO> check it out
[09:35] <DBO> Edgy users with the right hardware only need to add the repos and install compiz
[09:35] <DBO> aiglx is ready to go for them
[09:35] <FireRabbit> so its part of the xserver-xorg-* packages?
[09:35] <DBO> aiglx?
[09:35] <DBO> no
[09:35] <DBO> its PART of xserver-xorg
[09:35] <DBO> it is included in Xorg 7.1 to be more exact
[09:36] <FireRabbit> right, okay.. that's what i was getting at. gotcha. cool.
[09:36] <DBO> and in edgy its on by default
[09:36] <FireRabbit> -nods-
[09:36] <FireRabbit> it just dawned on me that my laptop has a GMA 950, so ill have to install edgy on there
[09:36] <FireRabbit> and give it a try
[09:37] <DBO> also adding sudo depmod -a after sudo lrm-manager
[09:37] <FireRabbit> i think lrm-manager runs depmod -a
[09:37] <FireRabbit> maybe not though, *shrug*
[09:37] <DBO> something weird goes on
[09:37] <FireRabbit> it certainly cant hurt
[09:37] <DBO> some users have reported the new modules dont work until they depmod -a
[09:38] <FireRabbit> gotcha
[09:38] <FireRabbit> let me know when you're doing with the edits and ill change the blurb about edgy
[09:39] <DBO> done
[09:41] <FireRabbit> you had a mistake, 4a and 4b both said "GDM", fixing :)
[09:41] <FireRabbit> will edgy users still need to modify their Xorg.conf?
[09:42] <FireRabbit> to enable composite, etc?
[09:42] <DBO> they shouldnt have to
[09:43] <DBO> but that might change
[09:43] <DBO> so I wouldnt get too over-zealous
[09:43] <FireRabbit> okay, well for now ill assume that they dont.
[09:43] <FireRabbit> THIS GUIDE IS FOR THE DAPPER RELEASE ONLY! EDGY USERS DO NOT NEED TO FOLLOW ANY OF THIS, AND CAN SKIP RIGHT TO CompositeManager/InstallingCompiz
[09:43] <FireRabbit> so dont put that?
[09:44] <DBO> well no they cant
[09:44] <DBO> InstallingCompiz doesnt cover edgy users anyhow
[09:44] <FireRabbit> right
[09:44] <FireRabbit> but it will soon..
[09:44] <Burgundavia> are you two cleaning up those pages?
[09:44] <Burgundavia> that would be awesome
[09:44] <DBO> Burgundavia, actually after the fork I am going to re-write them
[09:44] <FireRabbit> well, i am happy to, once all those changes you mentioned happen.
[09:45] <DBO> they work, but they are messy
[09:45] <FireRabbit> ill just put it back to saying that info for edgy people is coming soon, and ill change that once we get the compiz pages fixed.
[09:45] <DBO> there is no point in fixing the pages until I can get more solid info about beryl out of the devs
[09:46] <DBO> but like I said I talk to them daily so thats not a big deal, but fixing their current versions will be a pointless waste of effort since the whole thing will be broken in a couple weeks anyhow
[09:46] <FireRabbit> okay, so im just going to stop messing with the AIGLX page for now, and go over it again once beryl surfaces.
[09:47] <DBO> We are also going to need a BerylSwitch page
[09:47] <FireRabbit> -nod-
[09:47] <DBO> since more or less users with the compiz package are going to be left in the "no updates" limbo
[09:47] <DBO> and eventually they will get reverted to vanilla
[09:47] <DBO> which they wont want
[09:47] <DBO> they want beryl
[09:47] <FireRabbit> at least thats better than the "what the hell is going on" limbo that has happened a few times in the past, heheh
[09:47] <FireRabbit> communication from the devs. to the community has been less than perfect
[09:47] <DBO> hahaha
[09:48] <DBO> the beryl folks are very accessable
[09:48] <DBO> they dont hide from us at all =)
[09:48] <FireRabbit> oh you renamed all the packages? you dumped gconf? thanks for announcing it!
[09:48] <DBO> oh that bit
[09:48] <DBO> it WAS announced...
[09:49] <DBO> and I did put an announcement in the #ubuntu-xgl topic when it happened
[09:49] <DBO> but the overall effect has actually been good
[09:49] <DBO> people understand csm better
[09:49] <FireRabbit> yeah
[09:49] <DBO> we have a standard method for starting beryl
[09:49] <FireRabbit> csm is cool
[09:49] <DBO> oh that reminds me
[09:49] <DBO> csm is becoming beryl settings managerr btw, but the configuring compiz page, I added a quick note that it no longer applies to compiz-quinn
[09:50] <DBO> but it needs a SERIOUS overhaul
[09:50] <DBO> like I mean scrap the whole thing as it all no longer applies
[09:50] <DBO> we will need two pages
[09:50] <FireRabbit> yep
[09:50] <DBO> one for gconf, and one for csm
[09:50] <FireRabbit> its bad
[09:50] <FireRabbit> yeah
[09:51] <FireRabbit> http://orion.extremeboredom.net/~eric/CompizGuide.txt FYI, this is the guide i wrote for my friends so they would stop bugging me, the AIGLX page is based off of this.
[09:51] <FireRabbit> i tried to actually explain whateverything is, so once this overhaul happens, id like to make sure that all gets onto the wiki
[09:53] <DBO> ehhhh you should be using glxgears to test, not ppracer =P
[09:53] <FireRabbit> that's ridiculous!
[09:53] <DBO> haha
[09:53] <FireRabbit> tuxracer is the *perfect* test to see if 3d acceleration is working, *nods*
[09:54] <DBO> also adding compiz to the gnome-session
[09:54] <DBO> bad idea
[09:54] <DBO> lets not do that huh? =)
[09:54] <FireRabbit> uh, whats the alternative?
[09:54] <DBO> just run it at startup
[09:54] <DBO> its alpha software
[09:54] <FireRabbit> by hand?
[09:54] <DBO> and when it breaks, those people are hosed
[09:54] <DBO> yes by hand
[09:54] <DBO> its a safety measure
[09:55] <FireRabbit> that's ridiculous, the compiz-start script should just be changed to fall back to metacity.
[09:55] <FireRabbit> or kwin or whatever
[09:56] <DBO> thats fine for xgl users
[09:56] <DBO> but AIGLX users might experience all sorts of badness
[09:56] <DBO> ranging from blank screens to crashing xservers
[09:56] <DBO> and since there is no fallback server...
[09:56] <DBO> well you get the idea
[09:57] <FireRabbit> ok ok, so when we write the guide, we'll tell people to first test it by hand, then then OPTIONALLY make it auto-start, if it worked.
[09:57] <DBO> ehhhh...
[09:57] <DBO> updates break aiglx sometimes too
[09:57] <DBO> (the devs use xgl mostly)
[09:57] <FireRabbit> right
[09:57] <FireRabbit> we're beating a dead horse, none of this matters until theres a new compiz page on the wiki, we can worry about it later.
[09:58] <DBO> right, we can start drafting it now
[09:58] <DBO> hey anyone on the doc team present?  Burgundavia?
[10:05] <Burgundavia> DBO: about to crash
[10:05] <DBO> quick question
[10:05] <DBO> is using the wiki to draft up a new howto, but marking it as under construction ok?
[10:05] <Burgundavia> yep
[10:05] <DBO> it might be a week or more before its actually usefull, but when the switch happens we need it in place
[10:06] <Burgundavia> create a draft page, then move it over to the existing page and place a redirect from the draft page
[10:06] <DBO> uhhh...
[10:07] <DBO> oh you mean make something like BeryleHowtoDraft
[10:07] <DBO> then when its ready move it to BerylHowto and redirect the berylHowtoDraft?
[10:08] <Burgundavia> yep
[10:08] <DBO> ok thanks
[10:08] <Burgundavia> but avoid the` word howto
[10:08] <Burgundavia> in page names, that is
[10:09] <DBO> yeah I know, its just going into the CompositeManager stuff
[10:09] <DBO> I helped make those pages in the first place
[10:09] <Madpilot> DBO, what is Beryl, aside from a girl's name? A more descriptive page name might be a good thing, too
[10:09] <DBO> its also a gem Madpilot =P
[10:09] <Madpilot> that too
[10:09] <DBO> its a fork of compiz
[10:09] <DBO> so it will go in with its howto right next to compiz in the composite manager wiki page
[10:11] <DBO> most people are actually using the beryl mods right now
[10:11] <DBO> thats what the standard walkthrough installs
[08:04] <halfhaggis> Hello. I'm keen to proof-read the documentation, but I don't want to duplicate work. Is there a systematic way in which proof reading is being carried out, or should I just dive in randomly?
[08:04] <LaserJock> there really isn't a very systematic way I'd guess
[08:04] <LaserJock> I'd pick a doc that is ready for proof-reading and dive in
[08:05] <LaserJock> do you have a checkout of the svn repo?
[08:05] <halfhaggis> yes
[08:05] <nixternal> i would recommend grabbing them from trunk though, as everything that is on the help.ubuntu.com website has been fixed im sure for the edgy docs ;)
[08:05] <LaserJock> haha
[08:05] <nixternal> nm then, you are one step ahead of me ;)
[08:06] <halfhaggis> Systematic would be better, me thinks
[08:07] <LaserJock> halfhaggis: sure, we just need a system ;-)
[08:13] <trappist> halfhaggis: proofreading is about 90% of what I do on the team.  I've done all of the xubuntu directory and bits and pieces of others.  I was thinking I'd hit kubuntu next.
[08:16] <LaserJock> yeah just don't do the packaging guide just yet ;-)
[08:18] <halfhaggis> Yeah, okay. By next time, hopefully I'll be more involved in helping out, and we can get something more organised started
[08:20] <LaserJock> what do you mean by organized?
[08:21] <jjesse> like a group of eople that are assigned to proofreading certain docs?
[08:21] <jjesse> is that waht u mean?
[08:40] <halfhaggis> that's sort of what I mean. been tried before? didn't work?
[08:41] <LaserJock> well, so far the authors proofread their stuff and then get somebody else to do it as well
[08:41] <halfhaggis> I just think that avoiding duplication is a good thing(tm)
[08:41] <LaserJock> trappist did a large amount of that for dapper
[08:42] <jjesse> i don't think we have tried to have a schedule of proofreaders, because most proofreaders befcome authors :)
[08:42] <LaserJock> right
[08:42] <halfhaggis> Ok. Here's the scenario. I want to volunteer to do some proof-reading. I don't particularly want to proof read something that's already been proof-read
[08:42] <halfhaggis> What should I look at?
[08:43] <halfhaggis> Does every author make sure that another author checks his/her work?
[08:43] <LaserJock> well, if our status pages were up-to-date I'd say you could go with that
[08:43] <jjesse> start w/ the kubuntu docs 
[08:43] <jjesse> i think that would be good
[08:43] <LaserJock> but I'm not sure they are
[08:44] <halfhaggis> i checked the status pages last week - so unless something has changed since then...
[08:44] <LaserJock> where did you look?
[08:44] <jjesse> is the stats page getting updated?
[08:46] <LaserJock> uggg, doesn't look like it
[08:47] <jjesse> is that an mdke thing?
[08:47] <LaserJock> http://doc.ubuntu.com/ubuntu/status/pg-report.html looks like the dapper version
[08:47] <LaserJock> I'm not sure
[08:47] <LaserJock> perhaps since I believe it is run from doc.ubuntu.com
[08:48] <halfhaggis> Ah, now that's just confusing. What's the point of this page then: https://wiki.ubuntu.com/DocumentationTeam/Projects
[08:49] <LaserJock> to list projects and give info from people
[08:49] <LaserJock> :-)
[08:49] <LaserJock> but when it's not updated very often it's a bit of a bummer
[08:49] <jjesse> and i don't know if that is up to date or current
[08:50] <jjesse> o tjp
[08:50] <halfhaggis> Hmm. Yes. because I've been checking out the wiki mostly. Guess I'll wander around doc.ubunut.com for a bit then
[08:50] <jjesse> doh
[08:50] <jjesse> i thought that should be building automatically?
[08:53] <LaserJock> well, I don't see a cron job for it
[08:55] <LaserJock> good grief, the status reports are from June 2nd
[08:59] <LaserJock> lloydinho: ping?
[08:59] <jjesse> hmmm
[09:00] <LaserJock> anybody know if mdke is checking email?
[09:52] <FireRabbit> is it me, or does help.ubuntu.com often stop working for a few minutes?
[09:52] <jjesse> it might be slow sometimes?
[09:52] <nixternal> sometimes...seems like all the time for me
[09:52] <FireRabbit> it doesnt appear to just be slow, right now its not accepting my connection
[09:53] <FireRabbit> at all
[09:53] <nixternal> looks like it is down
[09:53] <FireRabbit> yeah.
[09:53] <nixternal> which isn't new at all for the doco servers around here
[09:53] <nixternal> hrmm..it just popped up
[09:53] <FireRabbit> is anyone from canonical around?
[09:54] <nixternal> i just messaged the web guy 
[09:54] <nixternal> see if he is around
[09:54] <FireRabbit> thanks.
[09:55] <FireRabbit> wiki.ubuntu.com isnt coming up either.
[09:57] <nixternal> they came up for me, just took 53 seconds for h.u.c and 71 seconds for w.u.c
[10:09] <nixternal> jjesse: https://wiki.ubuntu.com/KubuntuDocs/Edgy
[10:09] <nixternal> you have a status?  should we be working on that?
[10:43] <lloydinho> LaserJock, pong.
[10:43] <LaserJock> lloydinho: hi
[10:43] <LaserJock> I haven't talked to you for a few while
[10:43] <LaserJock> lloydinho: did you see that I got the doc freeze moved to the 21st?
[10:45] <lloydinho> LaserJock, I did see that. 
[10:45] <lloydinho> I've been away for the weekend though, and haven't been able to touch it at all.
[10:45] <LaserJock> lloydinho: did you get any instructions from mdke before he left?
[10:45] <LaserJock> I apparently wasn't paying attention enough or something
[10:46] <lloydinho> Not really. Just "have a look at the Desktop guide and flesh out the Internet section" 
[10:46] <lloydinho> So I went through it and removed placeholders and added a bit of new.
[10:46] <LaserJock> ok
[10:46] <lloydinho> Coordinated the frontpage with Don Scorgie and had the desktop team repackage it in Yelp
[10:47] <lloydinho> But that was all that we talked about at the DocTeam meeting.
[10:47] <LaserJock> ok, then I think we just need final draft and proofread
[10:47] <LaserJock> and we'll be set for the 21st
[10:47] <lloydinho> yeah. I think we're all final draft at the moment.
[10:48] <lloydinho> So we need to proofread.
[10:49] <lloydinho> But reading back, I can see that the review system hasn't been updated at all since Dapper?
[10:49] <LaserJock> yeah, I thought the status pages were being built same as with the rest of doc.ubuntu.com
[10:49] <LaserJock> but it appears not
[10:50] <lloydinho> no, we might have to setup some cron job or some such.
[10:51] <LaserJock> yeah, I looked at the cron jobs for doc.ubuntu.com and I didn't see anything related to docs :/
[10:51] <lloydinho> But even so, all the chapters are still set to "complete" or "awaiting review" or some such from back in dapper.
[10:51] <LaserJock> and I don't know how they are triggered
[10:51] <lloydinho> Do we need to reset all of those manually as well?
[10:51] <LaserJock> yep
[10:51] <LaserJock> I did it for the packaging guide
[10:52] <lloydinho> Since we are so few, wouldn't it be easier to have a few people divide up the guides between them?
[10:52] <LaserJock> well, unfortunately I have my hands full with the packaging guide
[10:53] <LaserJock> I think the Kubuntu guys are taking care of their docs pretty well
[10:53] <LaserJock> I wonder if the server guide has had really any changes since dapper
[10:53] <LaserJock> trappist is willing to help ;-)
[10:54] <lloydinho> I don't think Bhuwan has really updated it that much.
[10:55] <lloydinho> well, if trappist can get in touch with the Bhu^Wthe current maintainer, I'm sure they can work something out.
[10:55] <LaserJock> ok, so what is the status of ubuntu docs? did mdke's cool front page get reverted?
[10:56] <lloydinho> Don did pretty cool stuff with the front page.
[10:56] <lloydinho> Apparently, it should be in Edgy now, though I haven't seen it.
[10:57] <lloydinho> So that leaves the "About Ubuntu", the "Contribute to Ubuntu" and the "Desktop Guide"
[10:57] <nixternal> LaserJock: in the Kubuntu release notes, there is the ShipIt portion...i think this should be removed because for Edgy, there will not be the ShipIt for everyone..ShipIt will continue to be Dapper until further notice
[10:58] <nixternal> the only Edgy ShipIts will go to the LoCo's
[10:58] <LaserJock> oh wow, I just looked at yelp for the first time in a while
[10:58] <LaserJock> it's waaay cool
[10:58] <nixternal> i wish kde had a parser like that...you can use khelpcenter, but you have to build the docs first
[10:58] <nixternal> then do
[10:59] <lloydinho> LaserJock, it works?
[10:59] <nixternal> khelpcenter /kubuntu/blah/C/index.html
[10:59] <LaserJock> lloydinho: well, I'm not sure what it is *supposed* to look like
[10:59] <LaserJock> and I'm running Edubuntu
[10:59] <LaserJock> but it shows up as "Ubuntu Help Center"
[11:00] <LaserJock> with a nice front page
[11:00] <lloydinho> That sounds right. Let me just dig up Don's mockups.
[11:00] <LaserJock> and the sidpar has the other docs
[11:00] <lloydinho> Yeah, something like this: http://donscorgie.pwp.blueyonder.co.uk/UHC.png
[11:01] <LaserJock> kinda, but mine is different
[11:02] <lloydinho> Yeah, I asked him to change the order and the titles of some of them.
[11:02] <lloydinho> But he didn't send me a new screenshot of that.
[11:02] <LaserJock> yeah
[11:04] <lloydinho> Well, if it works, it's cool. I see that Daniel also uploaded the docs as-was on Friday..
[11:05] <LaserJock> lloydinho: http://chem.unr.edu/~mantha/ubuntu/Screenshot.png
[11:06] <lloydinho> LaserJock, looks good. Though I'll have to change the desktop guide's omf file.
[11:07] <lloydinho> (anyone know how to make clean line breaks in an .omf scrollkeeper entry?)
[11:07] <lloydinho> The description isn't quite right.
[11:08] <lloydinho> LaserJock, how do you like the article descriptions, otherwise?
[11:08] <LaserJock> on the contributing one
[11:08] <LaserJock> I'd take out the last "here"
[11:09] <lloydinho> noted.
[11:09] <lloydinho> I'll whip up a patch right away.
[11:10] <LaserJock> do you change the individual .omf files
[11:10] <LaserJock> or is there one specifically for the front page
[11:11] <lloydinho> yeah. We don't really have a better system in place.
[11:11] <LaserJock> I think the packaging guide description should be changed
[11:12] <lloydinho> LaserJock, it's your show. Change like you want to... :-)
[11:12] <lloydinho> (though, what, if I may ask, is the trouble?)
[11:13] <LaserJock> "easily be installed on Ubuntu..." -> "easily be included in Ubuntu..."
[11:13] <LaserJock> I don't really touch on personal packaging in the guide
[11:13] <LaserJock> it's more about creating packages that you could include in the distro
[11:14] <lloydinho> Of course. That is what I meant to say, as well. I guess I didn't think to thoroughly about it though.
[11:14] <lloydinho> Do you want me to change that in my patch as well?
[11:16] <LaserJock> yes, please ;-)
[11:18] <lloydinho> It is done.. :-) I'll hopefully have a patch for you in a bit.
[11:30] <nixternal> Kubuntu Release Notes are getting a big time work-over by me right now...anyone going to be available later to proof them?
[11:39] <crimsun> yes
[11:40] <nixternal> awesome, my favorite proofer at that ;)
[11:41] <nixternal> let me sling this moron off of my dcc chat so I can get back to work on it
[11:45] <LaserJock> Burgwork: "I've been begged not to make this Final Offer!"? you guys need to get some better email subject lines ;-)
[11:46] <lloydinho> LaserJock, the patch is on the mailing list. Feel free.
[11:47] <lloydinho> What's this Final Offer business about?
[11:47] <LaserJock> lloydinho: Burgwork's company sends me stuff
[11:48] <lloydinho> LaserJock, heh. They sound like a funny lot.
[11:51] <Burgwork> LaserJock, have you gotten the cd thing?
[11:52] <LaserJock> hmm, don't know
[11:52] <Burgwork> that must be what it is
[11:52] <LaserJock> it's just the DiscoverStation Trial kit
[11:52] <LaserJock> I have no idea what it is
[11:52] <Burgwork> yep, that is what it is
[11:53] <LaserJock> but apparently Brian is going pull the plug soon so I need to hurry ;-)
[11:53] <Burgwork> not reallyl
[11:53] <Burgwork> it is a marketing ploy
[11:54] <LaserJock> but kind of a cheesy one
[11:55] <Burgwork> hey, I don't write this stuff
[11:55] <LaserJock> thank goodness
[11:59] <LaserJock> lloydinho: done
[12:00] <lloydinho> LaserJock, awesome.
[12:00] <lloydinho> Have we decided what else we need to do?
[12:02] <LaserJock> proofread
[12:06] <lloydinho> well. Yeah. I'll have a look at some of it tomorrow, I guess. Night all.