[00:22] hi. i'm looking to double-check that the content of my chapter fits the ui changes in lucid. i'm trying to install beta1 in virtualbox, but i can't get past the first screen 'try ubuntu...install ubuntu...memtest...etc.' [00:23] anyone got a pointer? [01:37] alright time to roll out the new logo [01:54] godbyk: ping [02:19] humphreybc: I'm back now. [02:19] godbyk cool [02:20] I started to read through the manual earlier. [02:20] You use 'simply' way too often. :) [02:21] could you update the website with the new logo? [02:21] including the favicon [02:21] :) [02:21] I can try. [02:21] Is it the same size as the old one? [02:21] no [02:21] you'll have to change things a bit [02:21] the new logo files are under team-images/logo [02:21] and team-images/banner [02:23] also can you add the following as options to the form [02:23] Inconsistencies in wording [02:23] Missing references [02:25] what's missing references mean? [02:25] like links to community docs and things [02:27] how will people know when a ref is missing? [02:27] no idea [02:27] lol [02:27] okay maybe don't add that option in, they can just specify it if they need to [02:28] some people might know of a good guide to setting up ATI drivers or something that they think should be linked [02:28] They can categorize it under 'missing information' or use the 'other' option. [02:28] kk [02:29] As I started proofreading the manual (I've only got halfway through the installation chapter), I've been making a list of common errors I'm encountering. [02:30] that way we can send that list out to give hints on what to look for, too. [02:30] awesome [02:30] i'm just typing up the OMG post now [02:30] won't post it for another couple of hours [02:32] http://ubuntu-manual.org/ [02:32] I think I'm gonna have to play with the graphic a bit. :( [02:32] yeah, we should figure out a couple details before you post it. [02:33] ubuntujenkins brought up a point earlier as to who should have access to edit the spreadsheet so we know what's been fixed and what hasn't. [02:33] also, who's allowed to make edits? we don't want everyone in the universe editing at the same time, or bzr will murder us. [02:34] hmm\ [02:34] just me, you, Jamin, Josh and Bryan [02:34] When we're ready to push out the article, I'll add a para on the website about helping us find bugs. [02:34] cool [02:35] is the svg for the logo and stuff in the repository? [02:35] perhaps you and dutchie can triage the bugs from the spreadsheet to launchpad and assign them to either myself, Jamin or Bryan [02:35] yep [02:35] all under team-images [02:35] and is there a way in the spreadsheet to mark something as triaged? just delete the row? [02:38] just delete a row. maybe we can add a column.. I don't know if the added column will show up in the form or not. we'll have to try it. [02:45] kk [02:50] humphreybc: okay, inkscape hates me. when I copy the logo and paste to a new svg, it is invisible. [02:50] Here's what I want: [02:50] the original graphic on the site was 344x100 [02:51] can you make the logo the same size as the original logo (roughly) and then put the text "Ubuntu Manual Project" in two lines, left-aligned next to the logo? [02:51] the font is Linux Biolinum O [02:51] or we can wait for thorwil to make an appearance. :) [02:52] bollocks. I suck at Inkscape too. I can't even select the logos for some reason [02:52] i can probably do it in photoshop. [02:52] :) [02:53] 344 x 100 you say [02:53] well, x100, really. [02:53] the width can be up to 364. [02:53] k [02:53] er 344 [02:55] why does the text have to be on two lines [02:55] ? [02:57] godbyk http://humphreybc.homeip.net/files/websiteimage.png [02:57] humphreybc: because one line looks crappy? http://ubuntu-manual.org/ [02:58] I just see the old one [02:58] oh [02:58] no i dont' [02:58] ew [02:58] okay [02:58] does that one there work for you? [02:59] we could just do a heap of spacing above it [02:59] to push it down [03:00] like this: http://humphreybc.homeip.net/files/websiteimage2.png [03:01] can you try them both on the site please? [03:01] humphreybc: first one is up now. [03:01] open the site in a new tab and I'll try the second [03:02] k [03:02] second is up now [03:02] hrm [03:02] what do you think? [03:03] maybe just make the second one bigger? [03:03] can I make it longer? [03:03] about 50% larger? [03:03] we can try. :) [03:03] k [03:05] http://humphreybc.homeip.net/files/websiteimage3.png [03:05] try that [03:05] I moved it up a bit to try and line it up with the language combo box [03:06] 'kay, it's up [03:06] that looks okay [03:06] i might move it up a tad higher [03:06] I s'pose we could even make it a bit bigger, even. [03:06] kk [03:08] k [03:08] http://humphreybc.homeip.net/files/websiteimage3.png [03:08] same link again [03:09] look good enough for me right now. we can have thorwil fix anything he finds wrong with it. :) [03:09] cool [03:10] now it's not going to get overwritten by the branch auto update? [03:10] it will in 20 minutes if I don't commit it now. [03:11] haha [03:11] okay, pushed. [03:11] so did the healthcare reform work [03:11] ? [03:12] I don't know that they've actually done it yet. [03:12] the republicans were dragging it out last I heard. [03:12] ah ok [03:12] what's the plan? [03:13] the blog post is all ready to go [03:13] looks like it passed. 216 to 203. [03:13] woohoo [03:13] so what does it mean? [03:13] are they publicising healthcare? [03:13] no clue. most of it doesn't really take effect until 2014. [03:13] oh ok [03:13] haha [03:13] when's the next election? [03:13] I've lost track of what's in there and what isn't. It's probably not nearly as cool as I'd hope. [03:14] btw, http://builds.ubuntu-manual.org/builds/ubuntu-manual-en.pdf better work because that's what i'm linking to for the post [03:14] the next presidential election is 2012. [03:14] ah okay. will Obama be re-elected? [03:14] humphreybc: well it does now, but may break sometime. [03:14] surely if W could reelected three times Barack has a chance... [03:14] let me copy that pdf over to the real site [03:14] that way everyone's using the same revision. [03:14] cool [03:15] try this link [03:15] http://ubuntu-manual.org/ubuntu-manual-draft.pdf [03:15] yeah that works [03:16] do you want to leave megan fox in there? [03:16] is that what we should have as the download link on the wiki and the post? [03:16] oO almost forgot haha [03:16] we should probably take her out [03:16] in case we get into trouble with some feminist OMG! readers [03:17] it might be best to just direct them to the website and use the download link there. [03:17] that way we can change it on the fly if needed. [03:18] nah, people are lazy [03:18] they won't want to click more than once to downloa it [03:18] i can update the link on OMG if need be [03:18] i'll remove megan and push [03:19] decide on a URL to use for the download link [03:19] use the link I gave you then. [03:19] draft? [03:20] that's a good idea to include "draft" in the PDF namne [03:21] yeah. [03:21] all clear for me to push? [03:21] that's what I figured too. will make it obvious it's a draft copy. [03:21] hold off one sec. [03:21] k [03:21] I wonder if it's worth adding some red text on the top of the license page saying it's a draft [03:21] pull then push. I just pushed [03:21] kj [03:22] k* [03:25] man it takes ages to make now [03:25] a good 20 seconds [03:25] yeah, I know. [03:26] okay, i removed Megan and replaced the PDF in daker with the new one without Megan [03:26] pushing it now [03:28] k [03:28] that's weird [03:29] ? [03:29] whenever i try to make the link on the OMG! post [03:29] it changes it to a google docs viewer link [03:29] that's lame. [03:29] blogger is owned by google right? [03:31] yep [03:31] * sunson referer: http://kanchilug.wordpress.com/ [03:31] okay it might have fixed it [03:32] i might post it now godbyk [03:32] check everything is alright [03:32] it's 3:30am in the UK [03:33] hold on a bit. let's triple-check everything first. :) [03:33] k [03:33] I'm still waiting for bzr to pull down the updates [03:33] hi sunson [03:34] godbyk you better triple check everything fast [03:34] http://www.omgubuntu.co.uk/2010/03/ubuntu-manual-project-needs-you.html [03:34] i don't think there's a way to un-do the publish :P [03:34] well, first, the pdf hasn't been updated on the site yet. [03:34] and someone has already commented haha [03:34] oh bollocks [03:35] did you actually push? [03:35] yeah [03:35] 'kay. just checking [03:36] * humphreybc thinks so [03:36] yup [03:36] rev 555 [03:36] 9 minutes ago [03:37] still waiting on it. [03:37] odd [03:38] I just filed a test bug [03:38] the thanks thing on the form looks crap [03:38] and it says "Your response will now appear in my spreadsheet" [03:39] how do I get to the spreadsheet? [03:39] they should report if they think there should be a screenshot and there isn't. [03:40] still no bzr update. :-( [03:40] crud [03:40] i'll push again [03:40] I saw the email message that said you pushed. [03:40] not sure why it's not pulling [03:40] hrm [03:41] it's not pulling on any of the 3 machiens I've tried. [03:41] did it pull already? [03:41] check the pdf on the site and see if it's the new one [03:41] what rev have you gt? [03:42] build it and check in the license [03:42] it's quite slow to download off your server [03:44] 3.4KB/s [03:44] could just be our shitty internet [03:44] how do I get into the spreadsheet? [03:45] the pdf on the site is rev 554 [03:45] crud [03:45] I downloaded it at about 400 kbps [03:45] can you manually stick the new one there? [03:45] sure, if I had a copy of it. :) [03:46] my home computers aren't pulling the update yet either. [03:46] rev 555: humphreybc.homeip.net/files/ubuntu-manual-draft.pdf [03:46] http://humphreybc.homeip.net/files/ubuntu-manual-draft.pdf [03:47] downloading at 15 kbps from you. :) [03:47] haha [03:49] the one you gave me is 554, too. [03:49] wtf [03:49] it looks like megan is gone. [03:49] oh yea [03:49] so maybe you're just off by a rev? [03:49] no [03:49] i copied it before i pushed [03:49] so i removed megan, compiled the manual, copied it into daker's folder, make clean and the pushed [03:50] gotcha [03:50] so it would have been 555 after because I made it on rev 554 [03:50] so that's okay [03:50] so the pdf would lag behind by one rev #. [03:50] right. [03:50] yup [03:50] now how do I get into the spreadsheet? [03:50] to change the thank you text [03:52] what's the thank you text say? [03:52] "Your response will now appear in my spreadsheet" [03:52] and it looks all screwed up [03:52] (when it's embedded inside the website) [03:53] I don't think we can edit that. [03:53] that sucks [03:53] at least, I never typed anything like that. [03:53] http://spreadsheets.google.com/a/ubuntu-manual.org/ccc?key=0AiussLy2MfjjdHRrYlR0Q0RMRXRTaXJuR2w0QjFUcXc&hl=en [03:53] feel free to look around. [03:54] don't break it, though. people are already using it. [03:54] that's quite the link [03:54] oh god people alreay are using it [03:55] HA [03:55] I found it [03:55] what do we want to say? [03:56] How about: "Thanks for your bug report. We'll get it fixed soon." or somesuch. [03:57] "Thanks for helping us make "Getting Started with Ubuntu 10.04" the best it can be." [03:57] yup i changed it to what you suggested [03:57] 'kay. [03:57] cool [03:57] and now we wait? [03:57] or start triaging... [03:58] we just wait. [03:58] lol [04:04] Any idea what Bryan Behrenshausen's LP name is? [04:05] dw [04:05] found it [04:18] godbyk could you de-capitilize "Edit" on the front page, in "Help Edit the Manual" [04:18] please :) [04:19] You get to choose between "Help edit the manual" and "Help Edit the Manual" [04:19] the former [04:19] do that with all the links [04:19] headings sorry [04:19] Wouldn't "in-built" make more sense to be "built-in"? [04:19] Takyoji: where is that? [04:19] First page of Proluge [04:20] page 7 [04:20] sure, can you report it as a bug? [04:20] http://ubuntu-manual.org/?bugs [04:20] :) [04:20] "What this guide is not" 2nd paragraph [04:20] Alrighty [04:20] http://ubuntu-manual.org/ better? [04:20] Is that a frontend to Launchpad by the way? [04:20] Takyoji, nope [04:21] it goes to a spreadsheet where we can look at the bugs and then report them to launchpad, assign them to the right people [04:21] ahh [04:21] thanks for using the form, it means we can keep track of stuff easier. Otherwise i'll just forget xP [04:21] godbyk much better [04:22] godbyk, could you put this underneath the countdown? http://linuxhub.net/wp-content/uploads/2010/01/alarm-clock.png [04:22] maybe make it a bit smaller [04:22] bout 70% [04:22] :P [04:23] if you resize it, I can put it there. [04:23] k [04:23] don't make it too big or the rest of the text will get pushed down and people may not read it [04:23] you should run this command... [04:23] sudo apt-get install gthumb [04:23] xP [04:23] I'm busy editing the manual. :) [04:24] I leave the graphics work to those who are better at it than me.. Mr. Photoshop. ;-) [04:24] Bug submitted. [04:24] http://humphreybc.homeip.net/files/alarm-clock.png [04:24] thanks Takyoji [04:24] * Takyoji continues reading [04:24] if you find more errors, just submit them in the form :D [04:25] hi [04:25] hi Guest39530 [04:26] By the way, when is the day that screenshot capture starts? [04:27] 1st April [04:27] humphreybc: http://ubuntu-manual.org/ [04:27] Alright [04:27] :) [04:28] godbyk beautiful [04:29] hi humphreybc [04:35] hi [04:36] godbyk, not sure if you can fix this or wait for Daker, but when you click on "Get Involved" on the site, both the Get Invovled and Report a Bug links are dark and bold [04:36] whereas it should just be the "Get Involved" link that's dark and bold [04:36] and the bugs start pouring in [04:40] humphreybc: should be fixed now [04:41] yay [04:41] four bugs are "pouring in"? :) [04:41] well [04:41] yes [04:41] hah [04:42] bear in mind that it's 5am in the UK [04:42] and I have at least one person who's going to post it on Planet Ubuntu Monday morning US time [04:48] Well, thorwil's blog is syndicated on ubuntu planet. [04:48] true [04:48] Martin is going to post it, maybe Elizabeth [04:48] I could ask Jono and Alan [04:48] heh [04:48] * humphreybc imagines the entire Planet Ubuntu filled with Ubuntu Manual Project [04:50] for bugs that I've found while proofreading, should I submit them to the spreadsheet, submit them to launchpad, or just fix them immediately? [04:50] um [04:51] fix the immediately [04:51] no point wasting time if you can fix them straight away cos you have the source etc [04:51] lucid didn't wake up on my laptop after the lid was closed. that's a bummer. [04:51] true [04:51] oh no! it fixed my suspend/resume but broke yours? [04:51] apparently. [04:51] that sucks [04:52] did you do a completely clean install or upgrade? [04:52] when I lifted the lid, the hard drive ground away for a bit, the screen was showing garbage. [04:52] I waited for the hard drive to stop and it did, but the screen was still garbled. [04:52] what graphics card? [04:52] I hit ctrl+alt+f1 (to get a text terminal) and nothing happened. [04:52] finally had to hold down the power button to power off. [04:52] when you hit caps lock, does the caps lock light go on? [04:52] clean install. nvidia [04:52] using the nvidia binary driver [04:53] nope, it didn't. [04:53] ah [04:53] same problem i had in Karmic [04:53] well, trade back then! :) [04:53] seems that everything starts up fine but the keyboard and monitor don't wake up properly [04:53] ahaha [04:53] I love that the spreadsheet auto-updates as new bugs are filed. [04:53] me too [04:54] also, telepathy-haze crashes all the time. [04:55] I'd file a bug, but there are already bugs with the same summary line and I'm too lazy to read through them and see if mine's the same bug. [04:55] lol [04:55] use Pidgin [04:55] telepathy is empathy stuff right? [04:55] I'm going to turn on some music and proofread more of the manual. [04:55] awesome [04:55] if you need more, just invoke my name. :) [04:55] sure [04:55] yeah. [04:56] I usually use pidgin, but I figured I'd give empathy another shot. [04:56] hey [04:56] Robert Ancell is testing our manual [04:56] (Ubuntu core dev, wrote Simple Scan among other things) [04:56] well, at least the scanning bits. [04:56] yeah [04:57] neat that he knows about us though [04:57] I think everyone knows about us to some degree [04:57] which means we're doing pretty well for a 3 month young project :P [04:58] you should tell the omg readers to pick a random chapter to start with. that way we don't have all the bugs in the prologue and installation found, but none in chapter 9 or whatever. [04:59] good idea [04:59] I'm going to go read some more of the manual. [04:59] ping me if you need anything. [04:59] kk [04:59] So does Quickshot need any testing yet, or? [05:00] Takyoji: not sure. You'll have to talk to Red_HamsterX, TommyBrunn or ubuntujenkins - they're some of the developers [05:00] I think they're mainly doing in house testing at the moment until they get the UI finished [05:01] ahh [05:02] yup [05:02] you can download the branch if you like [05:02] lp:quickshot [05:02] I might, out of curiosity. [05:03] sweet :) [05:11] okay who the hell used the word "Snooping" in the manual [05:29] where? [06:23] godbyk, see the spreadsheet [06:23] One sec. [06:23] #10 [06:26] hey godbyk, howcome spanish isn't listed here? http://builds.ubuntu-manual.org/ [06:26] (that's looking really pretty btw) [06:27] I think I had both those marked in my edits already too. [06:27] humphreybc: blog post forthcoming, I'll let you know once it's up [06:27] It is there. [06:27] pleia2: awesome, thankyou! [06:28] godbyk oh so it is [06:28] I was looking under S for the name [06:28] Alphabetical by language code. [06:28] yup [06:29] hey jamin [06:29] everything is under way [06:29] hey humphreybc [06:29] excellent [06:29] excellent *does the finger thing* [06:29] http://www.omgubuntu.co.uk/2010/03/ubuntu-manual-project-needs-you.html [06:30] yeah i just read that post [06:30] did you get the email i just sent you? [06:30] it's going to be reposted on the planet too [06:30] nope i'll check just now [06:30] the draft is updated whenever we want to update it [06:31] it's just the one under website/daker [06:31] ok [06:31] (anything in daker is hosted at ubuntu-manual.org) [06:31] we could quite easily have the draft be updated for each revision if we wanted to [06:32] ah ok. What about just once a day at a set time? [06:32] yeah maybe, we could do it manually [06:32] or godbyk could set a cron job to run at the same time every day that copies main.pdf from the latest build to daker and renames it [06:33] yeah thats what i was thinking [06:33] the PPA is a good idea, but I think it might be a bit too difficult to do right now [06:33] I don't know anything about PPAs or packaging [06:33] yeah ok - like i said i've got no idea about setting up ppa's [06:33] nah thats cool - could be useful for next release maybe? [06:33] yup [06:33] I can just have the build script copy the latest to the website too. [06:33] we'll definitely do that for 10.10 [06:34] godbyk-android, yeah we could do that, can you rename it to ubuntu-manual-draft.pdf ? [06:34] oh ok - godbyk-android how often does the build script run [06:34] I've thought about making a ppa, but don't want to have people complain that it gets updated too often right now. [06:35] Maybe after the writing freeze [06:35] yeah that's why i thought calling it ubuntu-manual-daily or something [06:35] and just updating it once a day [06:36] Right now the build script gets run manually by me, but I can automate it pretty easily. [06:36] godbyk-android: maybe just have it run at a set time every day [06:36] 0000 UTC? [06:37] ok. Yeah that way people can see the changes that are made if they are interested, and might save us getting the same bug reported multiple times [06:37] Sure. [06:37] neat [06:38] anyway i just got home from work so am gonna go eat some food etc then i'll be back in an hour or so to do some editing [06:38] awesome :) [06:38] jaminday, I'll start too [06:38] I'm thinking we should just make changes ourselves [06:38] instead of reporting them to the form [06:38] I hate proofreading [06:38] hehe [06:39] humphreybc: you mean if we find bugs we just fix them and not worry about reporting? [06:39] haha [06:39] jaminday: yep [06:39] yeah that's what i was gonna do [06:39] we may as well not waste time, since we have the source and are on the team as editors :) [06:39] doesn't seem like much point reporting the bugs to ourselves [06:39] haha nope [06:40] When I was in school and had to proofread mt neighbor's paper I always felt bad because I'd scribble all over it and they wouldn't find many steroids in mine [06:40] haha [06:40] Gash [06:40] gah. [06:40] steriods huh, android keyboard is fun :P [06:40] hehe steroids [06:41] Damn android keyboard. [06:41] godbyk-android: it certainly has room for improvement [06:41] Errors. [06:41] At first glance i thought it said hemorrhoids for some strange reason [06:41] i have no idea why [06:41] I wouldn't put it past this keyboard! [06:42] hehe [06:42] anyway, i'll be back [06:42] Also maybe we should add on the website that the draft is updated once per day at 0000 UTC so people know to come back and re-download if it's been a couple of days [06:43] God idea. [06:43] Good idea, rather. [06:43] sweet [06:43] * godbyk-android goes back to his book for a bit. [06:46] jaminday: if you log in to the spreadsheet, it gets updated live as people report things [06:46] it's awesome [06:47] we're up to 20 reports already [07:05] http://planet.ubuntu.com/ [07:05] :) [07:06] I love how our new logo stands out on a page [07:07] :) [07:16] humphreybc: when did that[new logo] happen? [07:16] last couple of days [07:16] thorwil designed it [07:16] ah.. neat [07:17] you like it? [07:18] yup , looks good [07:18] neat :) [07:18] hey so vish, what happened with chapter icons? [07:18] we were going to do watermarked ones rightr? [07:18] humphreybc: i thought we dropped them.. thorwil didnt want them [07:19] * vish doesnt like it either :s [07:19] lol [07:20] righto then [07:20] but i went to all the trouble of mocking up a series of different icon implementations :P [07:20] http://humphreybc.homeip.net/files/chaptericon4.png [07:21] * vish saw that , wasnt a fan ;p [07:21] haha [07:21] okay then Vish [07:24] http://milocasagrande.wordpress.com/2010/03/21/what-you-shouldnt-do/ [07:27] heh [07:43] damn the website looks kickass [07:43] hey nisshh :) [07:43] hey [07:43] daker did the website yea? [07:44] yup, i designed it tho :{ [07:44] :P* [07:45] cool [07:45] have a look at planet ubuntu [07:46] and omgubuntu.co.uk [07:49] godbyk interesting list. I think we're pretty good and adhere to most of those. I don't agree with the first one, my mum for example wouldn't make the connection that a button that says "open" opens a document [07:49] for people who have never ever used computers before, even the most obvious things can be overwhelming when you are sat in front of a screen for the first time [07:49] many bugs been reported yet? [07:50] nisshh: yeah just over 20 [07:50] :) [07:50] ah nice [07:50] nisshh: do you have a login to the spreadsheet? [07:50] nope i think it requires a @ubuntu-manual.org email [07:51] we need to start reporting these on launchpad and assigning them to people [07:51] if i had a login i would help lol [07:51] cool [07:51] godbyk can we get Ryan a ubuntu-manual.org email address? [07:53] Sure. Email me his address and I'll set it up in a few minutes. [07:53] nisshh: ^^ [07:53] what's your email? [07:53] nisshh@hotmail.com [07:53] cool [07:53] and we'll go with ryan@ubuntu-manual.org ? [07:53] cool [07:53] or do you want nisshh ? [07:54] we've all got our first names [07:54] it's friendlier :) [07:54] yea go with first name [07:54] cool, so godbyk-android: nisshh@hotmail.com and if you could do ryan@ubuntu-manual.org [07:54] :) [07:55] godbyk: so i presume anything sent to ryan@ubuntu-manual.org will be forwarded to my actaul email? [07:55] so nisshh, basically, there's a spreadsheet with the form results. You'll need to take the stuff from the spreadsheet and manually report each one as a bug under our project in launchpad, then assign it to me, Jamin or Bryan to fix. [07:55] nisshh: nah you'll have to log in to @ubuntu-manual.org and set up email forwarding [07:56] ok easy to do [07:56] sweet [07:56] when assigning bugs, bear in mind that Jamin is doing chapters prologue - 3, i'm doing 4,5,6 and Bryan is doing 7,8,9 [07:56] is there some way of knowing which ones have already been manually reported on launchpad [07:57] none of them have yet [07:57] ok cool [07:57] we have to work out a way [07:57] a column in the spreadsheet [07:57] maybe [07:57] ah nope i found a way [07:57] a strike through [07:57] saying "reported on launchpad" [07:57] i did the first one as an example [07:57] ah cool [07:57] a column would be better but it might show up on the form... i'll check [07:58] okay no it doesn't, column is good [07:58] you will have to bear with me since i havent used google docs or whatever before [07:58] do we need to even use launchpad then [07:59] we could have an "assigned to" column [07:59] that would be far quicker [07:59] and then once the bug has been fixed, strike through or have a "fixed" column [07:59] okay let's do that [07:59] ok sounds good [07:59] also, what are the mugshots of team members going to be used for? [08:00] it's a surprise! [08:01] nothing evil i promise [08:01] hehe [08:02] i bet your going to compile a list of team members and post them somewhere arent you? [08:02] ok ill send you my mugshot later today [08:04] close, but no cigar [08:04] * humphreybc added in a "Which chapter is the error in" field in the form [08:04] hehe oh well worth a shot [08:05] godbyk: ping me on here when you have my email setup, thanks. [08:08] nisshh: what's your full name? [08:08] Ryan Macnish [08:10] godbyk, I added in a chapter question [08:10] but i don't think it's working properly [08:11] no it's not [08:11] damn [08:12] nisshh: I've sent the info to your email address [08:12] cool thanks [08:13] humphreybc: isn't the page number enough to locate the error? [08:13] probably but i wanted to make it easier to assign errors to people based on chapters [08:13] Make it easier for the bug reporter [08:13] doesn't look like it's going to work properly [08:14] yeha [08:14] i removed it [08:14] We can glance at the pdf and see what chapter it's in pretty easily [08:15] true [08:15] The more questions we ask, the fewer responses we'll get. [08:15] kk [08:16] humphreybc: ok im logged in and setup, what is the link to the spreadsheet [08:16] http://spreadsheets.google.com/a/ubuntu-manual.org/ccc?key=0AiussLy2MfjjdHRrYlR0Q0RMRXRTaXJuR2w0QjFUcXc&hl=en [08:17] ok got it [08:17] so i just need to assing each report to one of you three? [08:18] basically [08:18] and if you come across duplicates, mark them as duplicates [08:18] somehow [08:18] hehe ok [08:18] and as they are fixed, we'll mark them as fixed [08:18] in theory [08:18] fun times! [08:19] the spreadsheet auto updates when new entries are submitted [08:19] so you don't need to refresh [08:19] you can just stare at the screen waiting for one to come in and then assign it real quick :P [08:19] ok cool, i already found aduplicate [08:19] neat [08:19] we should probably get to fixing them asap and then update the manual so we don't get a crapload of duplicates all week [08:20] hey it's thorwil! [08:20] yea [08:20] hi! [08:20] how should i mark the duplicate? [08:20] your new logo is all over the net :P [08:20] nisshh, switch to the chat in the spreadsheet [08:21] thorwil: really like the logo! [08:23] humphreybc: cool, but why did i create specific sizes if you go and just scale it? [08:24] I tried to export the big size one [08:24] but it had this problem, i'll show you [08:25] http://humphreybc.homeip.net/files/logo.png [08:26] see the green bar at the bottom left, is out of place [08:26] I couldn't work out how to fix it in Inkscape :P [08:26] thorwil: if you can whip up one to fit the header area of the website, I'll get it uploaded. [08:26] oh yeah thorwil, we had to do a quick and nasty fix for the website :P [08:27] Inkscape was being cantankerous. [08:27] ok [08:27] * humphreybc doesn't know how to work inkscape [08:27] * humphreybc used photoshop [08:28] if a hammer is the only tool you know, every problem looks like a nail [08:28] :P [08:28] thorwil, you're so clever [08:29] godbyk-android: the first likely stumbling block would be that i have a locked layer in that file [08:29] ah [08:29] there's the problem [08:30] no wonder I couldn't select it [08:30] there's a "main" and a "targets" layer [08:31] main contains all artwork. targets contains rectangles with IDs such as "ump_logo_192px" [08:31] ohhh [08:31] so you can lock the main layer, do a select all in the targets layer, -> export and enable batch export there [08:32] you end up with one PNG per rectangle with the IDs as filenames [08:32] When I copied the logo to a new svg file, it was invisible. I gave up. [08:32] very good [08:32] godbyk, you probably only copied the target area [08:32] same as what I tried to do... [08:33] * humphreybc spent ages furiously clicking the icon to see if he could select that bar to move it one pixel up [08:33] hit ctrl-shift-L for the layers panel [08:34] * humphreybc hits ctrl+alt+L and locks his screen [08:34] humphreybc: there is a report on the spreadsheet that says "multiple pages" under which page [08:34] that the XSane one? [08:35] its a "multi-chapter bug [08:35] no its number 22 on the spreadsheet [08:35] Should i assign it to all three of you? [08:36] nah [08:36] assign it to Kevin [08:36] it's a LaTeX thing [08:36] yep [08:36] give him pink :) [08:36] heh nice, one step ahead of me! [08:36] hehe [08:37] might make it a bit lighter [08:37] google docs is easy to use [08:37] that other pink was killing my eyes [08:37] hehe [08:37] it's google, what do you expect? :P [08:37] meh yea true! [08:38] I added in a "Notes" column [08:38] yep, see it [08:39] thorwil: there's a bug about the title page there [08:41] awesome [08:41] humphreybc: whats with number 30 in the spreadsheet? [08:44] ok, they are all assigned at the moment, i will keep checking over the rest of today and update the spreadsheet as needed [08:45] awesome [08:45] # 30 was me testing something [08:45] but i deleted the row [08:46] wow this spreadsheet is gonna save us heaps of time catching bugs [08:46] * humphreybc thinks the form/spreadsheet thing will work quite good in future for surveys [08:46] humphreybc: what bug? [08:47] "The chat icon's edges are cut" [08:47] * nisshh agrees with benjamin [08:47] http://www.ubuntu-pics.de/bild/48269/screenshot_013_xb86tF.png [08:48] dropping your game thorwil, *shakes head* :P [08:48] hehe [08:49] humphreybc: not at all. this issue does not exist in the svg [08:49] humphreybc: you have it easy, chapter 4, 5 and 6 only have a couple of bugs [08:49] it would take effort to produce something like that [08:49] :P [08:50] so far they do, nisshh, so far :) [08:50] thorwil: hmm. well it's cut in the PDF, so somewhere along the line that's happening. It's not particularly noticeable [08:50] humphreybc: it's alos not cut in a direct export to pdf [08:50] weird [08:51] godbyk-android: http://www.ubuntu-pics.de/bild/48269/screenshot_013_xb86tF.png ? [08:52] thorwil: not sure. I just selected the icon and saved as pdf using the selection as the bounds. [08:53] godbyk-android: we were going to use exports of the whole svg, anyway, right? [08:54] if inkscape can handle the typesetting correctly, sure [08:54] Otherwise we'll have latex do the typesetting and compose they page from within latex. [09:00] * jaminday has his icecream and finally ready to sit down for an hour or two of editing [09:01] jaminday: yay! [09:01] * humphreybc is watching The Cleveland Show [09:02] * nisshh has just finished cleaning out his entire room [09:13] just finished my book. [09:16] new bug reports rolling in [09:16] big one for you benjamin [09:16] I like it how at the top next to the 'Form" menu it has in brackets how many responses we've received. [09:17] jaminday: yes i saw that too [09:18] I think both the bugs assigned to me are NOTABUGs. [09:18] The PDF is set up to be duplex and the chapters open on the right (recto) side of the spread. [09:19] jaminday: I was trying to figure out what that meant when it was (3). [09:19] I was thinking, 'did I screw up and make 3 forms?!' [09:19] hehe [09:20] meh [09:20] nope just google being kick-ass again [09:20] apparently. :) [09:21] google is part kick-ass and part privacy-encroaching [09:22] hehe yes true [09:22] but it's the way of the new digital age [09:22] good point there [09:23] no one under 15 seems to give a sh*t about privacy anymore! [09:23] nope [09:23] yeah, I'm torn on the privacy thing. [09:24] I like the idea of privacy, but I'm also a pretty open person. I just don't want to be *forced* to be public. [09:24] yeah that's true [09:24] seems like society is headed that way anyway, though. [09:24] godbyk: exactly [09:24] but google does give you the option of making things public or not [09:25] it just wasn't too obvious when buzz first launched so they copped a lot of flack [09:25] criticism comes first these day [09:25] s [09:25] yes it does [09:26] I just freaked out at how many bug reports i'm getting, but then i realised that most of them are from pages i haven't even looked at yet. Phew! [09:26] hehe [09:27] benjamins got alot of bugs coming in for him [09:28] er [09:28] someone broke the bug reporting page [09:28] "Parse error: syntax error, unexpected T_STRING, expecting ',' or ';' in /home/godbyk/bzr/ubuntu-manual/website/daker/includes/structure.php on line 139" [09:28] godbyk: you better take a look [09:28] oh noes! [09:28] it's back [09:28] sorry [09:28] lol [09:28] hehe [09:29] trying to re-add the google analytics code and mucked up the copy/paste. [09:29] smooth [09:29] real smooth [09:29] heh. [09:29] hey jamin, nice, you're burning through the bugs [09:29] bryan has alot of bugs to fix [09:29] popey: thanks for letting us know it was gebrocht [09:29] np [09:30] popey, was going to get you to look over the manual later in the week, along with a few other ubuntu community folk [09:30] yeah my first ones were pretty simple, but got a few bigger ones to look at [09:31] looks like we've got a fun week ahead of us [09:32] meh [09:32] definitely! I've got thursday + friday off from work this week so I'll do most of mine then [09:32] neat [09:32] okay, google analytics code should be back in there now. [09:32] i'm pretty busy tomorrow but should have free evenings [09:33] I'll be reading the manual through this week and editing as I go. [09:33] i have college middle of the week but will assign people after i get home at night [09:33] Lots of little bugs so far. I'm only halfway through the installation chapter. [09:34] * popey has filed a few bugs humphreybc [09:34] popey, just reading through them now. Very good work, helpful suggestions :) [09:34] we'll get them fixed asap [09:34] feel free to do some more bug checking as you have free time in the rest of the week [09:35] godbyk: installation chapter has a few bugs around the partitioning section, as i haven't really fixed that bit up yet [09:35] but there are probably others [09:35] whoever wrote the prologue and installation chapters really likes the word 'simply'. :) [09:36] godbyk... that may have been me :P [09:36] simply is a good word [09:36] haha [09:36] I've also been marking down where I think we should add glossary entries. [09:36] hehe i probably added a few as well [09:36] simply is usually not a good word to use in a manual, though. [09:36] this is true [09:36] if you tell me I can 'simply' do something, and it's not simple for me, then I feel bad. [09:37] That's good feedback cos when you only write bits at a time you don't realise how often you use particular words [09:37] failing that, it sounds like bragging. :) [09:37] yeah absolutely [09:37] and everyone has their own pet phrases and words when they're writing. [09:37] actually i put a few 'simply' in there too [09:37] humphreybc: why aren't you using launchpad for bug tracking? [09:37] 'as well as' is a phrase that jumps out at me, too. usually 'and' will suffice. [09:38] popey: too high a barrier of entry [09:38] popey: what he said [09:38] with this form we get to control the format and questions [09:38] as opposed to the free-form stuff we'd get via launchpad [09:38] we can make it specific to our project [09:38] how will i know if my bugs are fixed? [09:38] and the form doesn't require anyone to log in. [09:38] so my mom can glance at the pdf and easily file bugs. [09:38] popey: you won't. [09:38] unless you track them yourself. [09:39] thats unfortunate [09:39] Do you really want the three emails per bug when we add a comma? [09:39] unfortunate, but worth the trade-off [09:40] i would like to track my bugs [09:40] as I do with every other part of ubuntu [09:40] but you're not reporting small bugs like commas and things [09:40] you're welcome to file them via launchpad if you really want to. [09:40] just provide the same type of info. [09:40] 44 bugs reported now [09:40] there's nothing that prevents anyone from filing a bug via launchpad. this form is just for collecting a bunch of small bugs in a short period of time. [09:40] for people who are just doing tiny bugs like spelling mistakes and whatnot, a form/spreadsheet type thing is more optimal than launchpad [09:41] ok [09:41] i can just see a few of mine generating discussion [09:41] and that wont be captured [09:41] popey: if you think they'll generate discussion or you want to track them more closely, you can submit them via launchpad. [09:42] and besides, we honestly don't have time to discuss every bug - we're pressed for time as it is [09:42] the idea of this is to fix quality issues like spelling, grammar, formatting errors, inconsistencies and whatnot - small bugs [09:42] bugs that anyone who knows anything about english can find [09:42] it will be interesting to see how effective this means of bug reporting and tracking is [09:43] depends how you measure 'effectiveness' [09:43] if we get all of the bugs fixed before the writing freeze, then it's worked well. [09:44] I'm hoping that this method will have reduced the barriers to entry so that we get more bug reports than we would have via launchpad. [09:45] it's also working out quite well at the back end too, the spreadsheet is updated live and we have a couple of people assigning bugs to people with colour-coding [09:45] the fixers, three of us, can go through and see the ones assigned to us very quickly, all the information we need is in one row [09:45] then we can just cross it off and mark it as fixed, move onto the next [09:46] meanwhile the whole thing is working live like etherpad, and we can chat to each other while it's working [09:46] for our project, it's a far more efficient and faster bug reporting and assigning tool than launchpad. That's not to say Launchpad isn't good, it is good for other projects that don't have to get hundreds of tiny bugs from hundreds of people and fix them in 9 days. [09:47] At least we're hoping that's the case. [09:48] Ask us how it worked next week. :) [09:48] ;P [09:49] I think that icon bug you have assigned to thorwil is on me. But I may need thorwil's help to resolve it. [09:49] this is what it looks like: http://humphreybc.homeip.net/files/spreadsheet.png [09:49] kk [09:49] (I probably just checked the wrong box when I exported from inkscape.) [09:50] the cover page that's in the pdf is one that I coded in latex. it's not the one thorwil created. [09:50] in other words, it's not per thorwil's spec. :) [09:50] kk [09:51] Do you think we need a side note explaining what a 'window' is? [09:51] I prettied up our twitter account btw [09:51] http://twitter.com/TheUbuntuManual [09:51] jaminday: hmm [09:51] it's kinda just introduced without any introduction to what it actually is [09:51] yep [09:51] okay let's do that [09:51] is there an api for submitting bugs to launchpad? [09:52] godbyk apparently there is one, but I'm not sure where the info is on it [09:52] that may be handy in the future. [09:52] indeed [09:52] so we could design a nice web form that's specific to our project and submit the bug to launchpad in whatever form we prefer. [09:53] that would be good [09:55] * humphreybc might head to bed [09:55] long day at uni tomorrow [09:56] humphreybc: no worries, have a good one [09:56] i'll do a bit more then join you [09:56] not literally of course [09:56] lol [09:56] i hope not! [09:56] hehe [09:56] hehe [09:56] someone might need to contact Bryan btw [09:56] did i miss something?? [09:56] has anyone heard from him recently? [09:56] no [09:56] humphreybc: no not since the meeting [09:57] okay, jamin if you could flick him an email before you hit the sack [09:57] he needs to be contacted, he has alot of bugs to fix [09:57] just make sure he knows what's going on [09:57] he seemed keen to help out though so hopefully it's still ok [09:57] cool [09:57] yeah no worroes [09:57] worries [09:57] godbyk can you make sure Bryan has an email to log in to the spreadsheet please [09:57] who what huh? [09:57] hehe [09:57] gimme his full name and current email address and I can set up an account for him. [09:58] k [09:58] godbyk: Bryan Behrenshausen [09:58] bryan@stillnotcool.com [09:58] or behrenshausen@gmail.com1 [09:58] without the 1 [09:58] behrenshausen@gmail.com [09:58] either of those [09:58] or this one bryanb@gmail.com [09:58] send it to all three :) [09:58] gah.. pick one. :) [09:58] set him up with bryan@ubuntu-manual.org [09:58] humphreybc: expect there to be alot of bugs reported tomorrow, since everyone will check their feed readers in the morning [09:59] nisshh: yeah, well omgubuntu is on UK time [09:59] but there are a couple of posts going up on Planet Ubuntu [09:59] (to sync with US time) [09:59] popey: if you want to post on the planet too I'll buy you a cookie at UDS :) [09:59] yep [09:59] I sent the info to behrenshausen@gmail.com. [09:59] you coming to UDS humphreybc ? [10:00] popey: not confirmed no, but i remain hopeful haha [10:00] i applied for sponsorship [10:00] "Power of positive thought" right? [10:00] :) [10:01] Elizabeth has already posted an article about our testing, but if you want to do one as well then that would be awesome :) [10:01] where is UDS this time around? [10:01] any extra pair of eyes we can get on the manual won't go to waste [10:01] nisshh: Brussels, Belgium [10:01] right cool [10:01] just hit 50 bugs too [10:01] * humphreybc wonders if there are any UMP members in Brussels [10:02] not that i know of [10:02] Wow they are coming in thick and fast [10:02] jaminday: heh [10:02] well Joey does have 8000+ subscribers on omg! [10:02] and planet ubuntu is huge [10:03] 8000+ ! [10:03] and if we've made it as simple as it ought to be, there should be 8000 people clicking that download button and submitting bugs. besides, OMG! readers are total grammar nazis. [10:03] that works well for us [10:03] indeed [10:03] Also i set the Fixed? column to autoformat to green whenever a 'yes' or 'y' is typed in [10:03] hehe [10:04] jaminday: nice! [10:04] we can remove it if distracting but thought it might make it easier to glance [10:04] makes it easy [10:04] jaminday: could you set up the Assignee one to default to yellow if "Jamin" is typed in, green if "Benjamin" is typed in etc? [10:04] definitely [10:04] awesome [10:04] cool\ [10:05] its only 6pm here so ill keep assigning bugs [10:05] done [10:05] cool [10:06] It should work for Kevin, Benjamin, Bryan and Jamin now [10:06] Ooh.. I'm aubergine! :) [10:06] aahhhh, not aubergine! [10:06] hahaa [10:07] reminds me of the lucid theme too much [10:07] Kevin now you're WHITE TEXT on aubergine... [10:07] *shudders* [10:07] oooh [10:07] ah, that's better. [10:07] Note that my name is left-aligned, too. Take that, Luddites! [10:08] I'm saving the space to the right of my name for something special. [10:08] hehe [10:08] like? [10:08] You'll have to wait 'til October to find out. [10:09] hahahaa [10:09] argh i'm not good at waiting [10:10] the bugs marked 'fixed'.. have those been committed or are they just fixed locally on someone's hard drive? [10:10] At the moment mine are just on my hard drive till i do a push [10:10] if not, they should be committed and pushed [10:10] no point pushing after every bug or i'll be here all night [10:10] so i'll just do it when i go to bed [10:11] right. was just curious. [10:12] though we'll have to orchestrate it well or it'll be hell resolving all the conflicts. [10:12] yeah i was thinking that [10:12] yea [10:12] I suppose it everyone sticks to specific chapters, it should be okay. [10:12] So all the chapter 1 bugs get fixed by A, ch 2 by B, etc. [10:12] yeah hopefully our system will work that way [10:12] if we stick to it! [10:13] meh [10:13] Must not deviate from the plan! [10:13] hehe [10:13] I think I'll test out the form myself with some of the bugs I've found. [10:13] We'll see how fast/slow the form us. [10:13] form is. [10:13] (Can't blame that one on the android keyboard!) [10:13] hehe [10:14] godbyk: which android phone do you have? [10:14] nisshh: I have a Nexus One. [10:14] cool! is it any good? [10:15] I love it. [10:15] nice, i would get one if they would lower the price a bit [10:19] I think I may have to add a 'style / voice' entry to the list of bug types as I have more of those. [10:20] yeah good idea [10:24] wow, i just worked out that if you right click on maximise, it maximises the window horizontally but keeps the vertical height as is [10:24] jaminday: cool! [10:25] I've never seen that before! [10:25] Maybe it's a compiz thing [10:25] obviously they moved that out of compiz and actaully made it a feature [10:25] nah, theres a shortcut for it in compiz [10:26] Well, there's six bugs for page 7 alone. [10:26] On to page 8! [10:26] but, if you cant run compiz(like me) then its better [10:26] hehe good work godbyk [10:26] * nisshh thinks that godbyk just opened a can of woop-ass [10:26] hehe [10:27] * jaminday wishes godbyk started on someone elses chapters first [10:27] ? [10:27] this is why I hate proofreading. takes so long to do a thorough job. [10:27] heh [10:28] humphreybc: are you sleep-typing? [10:28] almost [10:29] hehe [10:29] hahah [10:29] * humphreybc just read back through the channel [10:29] meh [10:29] i've been trying to feature our bug checking marathon all over the web [10:30] like where? [10:30] Does that involve typing a lot of question marks? :) [10:30] *"Help the Ubuntu Manual Project!" appears on google.com* [10:31] facebook.com login screen: "Think. Do you REALLY need to perve at your hot friends' photos today, or should you come and help the Ubuntu Manual Project?" [10:31] :P [10:31] nah but seriously, Planet Ubuntu, Ubuntu Forums, various blogs [10:31] cool [10:31] and that right click on maximise thing is cool [10:32] yeah but it's definitely compiz [10:32] doesn't work in default lucid [10:32] awh [10:32] no your right [10:32] i just googled ubuntu manual and saw this https://help.ubuntu.com/6.06/pdf/ubuntu/C/desktopguide.pdf [10:33] it's from 6.06! [10:33] page 8 -- done [10:33] yeah i know [10:33] nothing like a bit of outdated documentation to throw newbies off xP [10:33] yea [10:33] that always pops up when i do a search for docs i need [10:33] that's right. Still, someone put a lot of effort into it back in the day [10:34] yea looks like it [10:34] anything worth stealing? [10:35] most of its waaaaaaaaaaaaaayyyyyyyyyyyy out of date... [10:35] jaminday: Canonical stuff [10:35] The 'conventions' page is a good idea [10:35] jaminday: we have been meaning to put that in [10:35] ah ok [10:35] I believe godbyk was going to do that... :P [10:35] oh, yeah. totally forgot about that. [10:36] remind me again in 12 hours. :) [10:36] lol [10:36] Ours is much more newbie focused - ie we explain a lot of jargon and lingo [10:37] but at the price of a lot more words on the page [10:37] indeed [10:37] and alot more work for us [10:37] there's a good summary of directories/file systems [10:37] ie stuff we were talking about the other day humphreybc [10:37] yup [10:37] did you see the image martin made? [10:37] nope [10:38] it's in the manual [10:38] end of the installation chapter i believe [10:38] it's just chilling [10:38] ah - i'll take a look [10:38] oh crap, that reminds me should i explain the different parts of the file system in my chapter for 10.10? [10:38] we need to a) find somewhere to put it and b) write some text to go wit hit [10:38] with it* [10:38] ah cool [10:39] would it work if the home folder was a different colour to represent it's own partition [10:39] by default it's not on it's own partition thoug [10:39] though* [10:40] yeah i know but as an example of how partitions are mounted [10:40] hm [10:40] maybes [10:40] that they fit into the existing directory structure [10:40] you need to say its not default to have home on a seperate partitiion though [10:40] humphreybc, godbyk: shall i add a "logo" dir to the manual branch? [10:40] rather than a separate 'e drive' or something [10:40] nisshh: yeah definitely [10:41] thorwil, team-images/logo [10:41] already one there [10:41] check out /banner too [10:41] k [10:41] godbyk have you got that build script automized to make the manual and copy it across to /website/daker each day at 0000 UTC? [10:42] nope [10:42] oooh, 78 bugs reported now [10:42] could you do that asap so that it's ready for tomorrow? [10:42] I'll do it when I wake up, though. [10:42] kk thanks [10:42] bets on how many bugs we'll get to by next Monday? [10:42] 280+ [10:43] pfft [10:43] we'll get way more than that! [10:43] that's a safe bet :P [10:43] if godbyk keeps going, ALOT more! [10:43] lol [10:43] hehe [10:43] haha [10:43] I'm almost finished with page 9. [10:43] well, we've almost got 80 and it's only been available to the public for 8 hours [10:43] pushed updated logo files [10:43] Another downside to using this form is I don't get mad karma points. :( [10:44] yea good point [10:44] godbyk, true, you don't! [10:44] godbyk: lol [10:44] godbyk if you want mad karma, go through and update some blueprints :P [10:44] godbyk, we will just say you have heaps of imagniary ones [10:45] nisshh: I'll take it! [10:45] hehe [10:45] so, I reckon we'll easily get about 600 bug reports by next Monday [10:45] potentially a lot more [10:45] should we have had more than the three of you on fixing? [10:46] we'll see how we go [10:46] nisshh: possibly, but then you potentially sacrifice consistency [10:46] if we need more then yeah we'll have to get some more [10:46] page 9 -- done [10:46] yay [10:46] a lot of bugs will be simple, quick fixes like a spelling mistake or something [10:46] godbyk: want a logo-title image flattened on that grey for the website? [10:47] thorwil: sure! if that is transparent. [10:47] yea i guess [10:47] (not sure if the transparency would blend well or not) [10:48] godbyk: huh? current one seems to have alpha channel, but is on a flat grey ground, afaics [10:48] nice. blame humphreybc. :) [10:48] huh? [10:49] humphreybc: the website background will stay flat grey? [10:49] thorwil: yep [10:49] for the foreseeable future [10:50] * humphreybc is expecting to wake up tomorrow to see 200 bug reports [10:50] We're at 87 now [10:50] anyone else notice that we've had about 4 or 5 people join the team since this started? [10:51] could prove to be quite the publicity stunt as well [10:51] page 10 -- done [10:51] godbyk: nice work on the bug reporting. I've been mainly focussed on bigger changes like rewriting paragraphs that needed it, so there's lots of little stuff I've missed along the way. [10:51] It will save me so much time just going through your bugs to find them. [10:51] yeah, it's not difficult to find the errors, just time-consuming. [10:52] who's assigned the installation chapter? [10:52] that would be me [10:52] oh, man. you're gonna hate me today! [10:52] i still need to finish partitioning and some stuff at the end i think [10:52] hehe [10:52] i'm sure i will! [10:53] don't hold back though [10:56] godbyk: just a thought - you might want to skip chaps 2 and 3 for now and come back to them later. [10:57] I am still doing my first edit (major edit) on these chapters so there will be a lot of stuff that gets fixed [10:57] okay [10:57] I've only done the first couple pages of chapter 2 [10:57] so I'll leave off that and come back to it later then [10:58] I'm going to try to finish entering the bugs I've got so far and then get some sleep. [10:58] ok. I'm up to 'managing windows' in ch 2. [10:58] 91 bugs now [10:58] lol [10:58] btw - that bug you just reported on heading styles, page 11 [10:59] hey, i wrote the installation chapter, it shouldn't have that many bugs :P [10:59] jaminday: yeah? that applies to all the headings. just assign the bug to me. [10:59] are you talking about formatting? [10:59] ah ok [10:59] also assign the lining figures bug to me. [10:59] nisshh: can you reassign bug 90 to kevin [11:00] sure [11:00] and bug 88 [11:00] to kevin? [11:00] yep [11:00] they are latex issues [11:00] ok done [11:04] ok all, ive gotta work tomorrow so heading to bed. I'll try and do a bit more tomorrow night. [11:04] jaminday: awesome [11:04] thanks for your help [11:04] chow! [11:05] no probs, talk later! [11:05] i'll head off now too [11:05] night all [11:05] keep it up :) [11:05] cheers [11:05] 102 bugs now [11:05] =| [11:05] how many are ones I've entered? [11:05] am I artificially inflating the bug count? :) [11:06] about 20? [11:06] a bug's a bug, regardless of who entered it :) [11:06] page 11 -- done [11:06] and with that [11:06] ok who broke the colors when i assign people? [11:06] i'm out! [11:07] weird [11:07] the rule just stopped working [11:07] yea [11:08] weird [11:08] i made them again but it doesn't want to work [11:08] maybe it'll come back... [11:09] k night! [11:09] night [11:09] night [11:16] page 12 -- done [11:16] ok, cya godbyk. [11:21] page 13 -- done [11:24] page 14 -- done [11:28] page 15 -- done [11:28] page 16 -- nothing to report [11:32] page 17 -- done [11:35] page 18 -- done [11:37] page 19 -- done [11:37] page 20 -- nothing to report [11:37] page 21 -- nothing to report [11:38] okay. I think I'll stop there. [11:39] 152 bugs so far. I think humpreybc will get his wish and wake up to over 200 bugs. :) [11:41] we are going to need more people to fix them [11:41] most of them are pretty easy fixes, I think. [11:41] at least the ones I reported were. [11:43] godbyk yesterday i commented out 3 lines in /prefs-hardware/sound so that the manual would compile again. there is an image missing I don't suppose you happen to know who added it? [11:44] I added the few example screenshots. (Unless someone else has added more since then.) [11:45] That might be the case see if you have the file in the /pref-hardwar/images folder [11:48] there's a folder, but it's empty. [11:48] the screenshots should go in ubuntu-manual/screenshots/LANGCODE/ [11:48] someone else must have added them then [11:49] there are images folders in each subfolder now [11:53] Interesting. [11:53] Guess we'll have to look into that. [11:54] Well, I'm gonna head to bed. I'll be back in some number of hours. [11:54] I trust you'll hold down the fort in my absence? :) [12:57] godbyk: I will do my best but i am in and out all day [13:17] hi there, I wonder where to download the source code and compile it myself? [13:28] wyh have you used bzr before ? [13:34] wyh I have to go but have a look at https://wiki.ubuntu.com/ubuntu-manual/authors follow that through and you should be fine [14:01] ubuntujenkins: sorry, I was away for other things. thank you. [14:01] ubuntujenkins: actually I didn't know much about Launchpad... [14:03] I'll look it over. [17:36] Hello [17:37] I need help about Ubuntu manual [17:37] I am searching for a different language Bengali (India, Bangladesh) is that available yet, or if not I would love to help Ubuntu manual to translate in that language [17:38] Any help I can get? [17:38] (note: this channel may be a bit dead; as I think a handful are in a different timezone or something) [17:39] xfact: I will just find the link [17:40] ubuntujenkins, Ok, But can yo utell me where to apply (or what to do) for translating Ubuntu manual in my own language? [17:40] I want to start the work ASAP, cause we have only one month time and the manual is long.... [17:41] xfact https://translations.edge.launchpad.net/ubuntu-manual/main/+lang/bn should be your language [17:42] ubuntujenkins, Thank you very much.... :0 [17:42] :) [17:42] no problem [17:44] If anyone has any questions feel free to ask them, if we are not always here we wil answer them when we get back [17:44] One more question, do we have to end this job before 29th? [17:44] 29th of march? [17:45] 29th April the day of Lucid stable release [17:46] I am waiting for the answer... [17:46] that would be ideal, sorry just checking the wiki [17:47] ok no problem.... [17:48] yea 29th would be great [17:49] @all ask any questions, I will answer them when i get back from getting my dinner === MenZa_ is now known as MenZa === titeuf_87_ is now known as titeuf_87 [18:19] o/ [18:29] wow, planet ubuntu's picked up our testing [18:30] thats good [19:15] hey ubuntujenkins, do you still have the list of languages with short code? [19:15] I can't remember where I saved it anymore [19:16] have I have an in comlpete one I will look it up but also look at builds.ubuntu-manual.org [19:17] titeuf_87: http://paste.ubuntu.com/399472/ [19:17] aha, this is helpful, thanks! [19:17] and thanks for that second link too [19:17] no problem [19:17] I am going to do some wiki work next week for quickshot [19:19] I'm going to finish the basic functionality of quickshot, will try to get it done asap [19:19] cool it would be good to get a alpha/beta out before the 1st [19:19] yeah that should be certainly possible :) [19:20] not a lot missing anymore really [19:20] cool [19:21] I will do the sample screenshots tomorrow, I am having problems changeing the live cd username I found one post that implied it worked but it doesn't work that way any more [19:21] does it have to be changed? [19:22] well it would be easyier if it could be ,c an you create a new user whilst in the live cd? [19:22] if so we can do a preinstall of quickshot and the languages needed [19:23] no idea, but the live cd runs a default setup anyway, so we can just use quickshot as the default user [19:23] yes but thats called ubuntu in the top right. I have a few things to add on release, detection if the user is using lucid [19:24] I can't remember the other one [19:25] How do you plan to distribute the iso? Just as a big file everyone can download? [19:26] Big file on the wiki was my thought, I will try and build one regulary so that it is up to date [19:31] Need anything from me, titeuf_87? I not, I'll write a basic index page for the server to make exporting a little more intuitive. [19:32] If not* [19:32] Red_HamsterX, not right now, but if I'll have a question I'll be sure to let you know [19:33] MUSIC STORE HAS ARRIVED [19:33] Okay. I'll be around for a while, working on some other stuff. [19:33] Just highlight me and I should notice in a few minutes. [19:34] ok [19:34] dutchie: its a bit slow [19:36] it's basically a website embedded into RB aiui [19:36] i know but the other stores are quiker [19:37] hasn't been a problem for me [19:38] hadn't really noticed speed one way or the other [19:38] strange i should probably do an update [20:07] hi @all [20:09] hi Daker [20:09] Hey Daker. will you be around for a bit? [20:09] I'm going to shower then be back. [20:10] ye [20:10] p [20:10] hello Daker [20:11] I want to make sure I haven't screwed up your website code too much. :-) [20:11] hi ubuntujenkins [20:11] oki godbyk-android [20:11] be back [20:23] titeuf_87: how do i set up a flag for quickshot like the "quickshot run -r" [20:23] near the bottom of bin/quickshot add something like: parser.add_option("-r", "--remove", action="store_true", dest="remove", help="Remove quickshot user") [20:24] then you can access that from anywhere with options.remove (or the name you've chosen) [20:24] ok thanks i will have a play [20:50] titeuf_87 how can you call windows form options i have added http://paste.ubuntu.com/399527/ but i get an error shown at the bottom. [20:52] That's because you're not calling this from the window class. You should move this over to the finish_initializing function [20:53] also, is this to show a different message when you're logged in as the quickshot user? [20:53] yes [20:53] also trying to under stand more [20:54] Okay, I'm back now. [20:54] when quickshot is run it detects the username of the user running it, and if it's the quickshot user then the loggedIn function is called [20:55] but that is called on the click of the first next button. [20:55] hello godbyk [20:55] Hey, ubuntujenkins. How's it going? [20:55] right [20:56] I am good, its been quite in here we have over 217 bugs last time i checked [20:56] you could check again at the end of finish_initializing: if os.environ["USER"] == "quickshot": ...set label text... [20:56] titeuf_87: I would like the first screen to be a congrats you will soon be ready to take screenshots message [20:57] are that sounds good i will have aplay again [20:57] thnaks [20:57] no problem, let me know if it doesn't work or you have more problems :) [20:58] back [20:59] titeuf_87: it works :-) [20:59] nice! [20:59] ubuntujenkins: We're up to 254 bugs now. [21:00] ouch thats a lot good though [21:00] How's quickshot coming along? Any major snags? [21:00] erm not as far as I know [21:01] godbyk, it should be able to launch an application now, maximize it, take a screenshot and upload it [21:02] titeuf_87: sweet! [21:02] if you guys need me to set up stuff at screenshots.ubuntu-manual.org, let me know. [21:03] So far I'm still using Red_HamsterX's test server, may want to ask him about what needs to be done server-side to make it work [21:04] It's just a simple symlink right now. [21:04] I've symlinked the working capy from bzr into a web-acessible location. [21:04] copy* [21:04] And that's all. [21:05] 'bzr pull' updates everything. [21:05] Sounds easy enough. [21:05] which dir is symlinked? [21:05] this apears bland what can i add to it http://imagebin.org/89943 [21:06] server/screencaps -> ~/public_html/screencaps [21:06] You could symlink the contents under a virtual vost without issue. [21:06] Can we just skip that screen if it's not doing anything? [21:06] The only catch will be adding authentication, since we'd want that outside of bzr for obvious reasons. [21:07] Unless we use mcrypt or something. [21:07] Or maybe sha. [21:08] Red_HamsterX: like this? http://screenshots.ubuntu-manual.org/ [21:09] what's the auth talk about? [21:09] Just to prevent someone from flooding the server. [21:10] Or from uploading questionable content. [21:10] Ah, I see. [21:10] A simple key (or set of keys) we could give out to anyone helping. [21:10] What OS are you running? [21:11] Do you mean a key that quickshot and the server share? [21:11] Everything seems to be working fine, except for the bzr query. [21:11] It's running Linux (Debian, I think). [21:11] Yeah. A simple key like that. [21:11] as long as the user doesn't have to deal with the key -- i.e., it's in the config file or something. [21:12] Key goes into a file in config/ and the user puts it in Quickshot somehow. [21:12] Or that. [21:12] I dunno how it'll work. [21:12] It's not necessary right now anyway. [21:12] right. [21:12] we can deal with that later. [21:13] Is it a VPS or a more restrictive environment? [21:13] If it's a vps, just install bzr with apt and everything should be good. [21:13] I'll work on writing a more intuitive export proces this evening. [21:13] Red_HamsterX: the screenshots.ubuntu-manual.org site should auto-update every 30 minutes. [21:14] though the way it's set now, it'll wipe anything uploaded to that dir [21:14] if screenshots get uploaded under a subdir there, then I'll have to recode the cronjob a bit. [21:14] It's a shared server. [21:14] I have bzr installed. [21:14] Ah... Yeah, they go into data/. [21:14] the screenshots end up in the data directory [21:14] I don't get to use apt (no root access). [21:15] ok [21:15] let me see if I can fix something then. [21:15] If bzr's installed, then it's not working right... [21:15] it's not in the path, I don't think. [21:15] where is it calling bzr? [21:16] ah, it is in the path.. [21:16] /usr/bin/env bzr, called in get_status.php [21:16] but the php file may not inherit the environment variables I set in .bashrc or _profile or whatever. [21:16] Can you see if the webserver's user can see bzr from env? [21:17] If not, I can just hardcode the path. [21:17] It's in /usr/bin under Ubuntu. [21:17] Probably the same under Debian. [21:17] Can you tell me what error msg you're getting? [21:17] (Though I haven't had cause to install it on my Debian systems) [21:17] No, I cannot. [21:18] It's installed in my ~/local/bin dir. [21:18] To simplify parsing, I just have the PHP script drop the bzr-query from its output if the command fails for any reason. [21:18] Your error log should tell you, though. [21:18] Hmm... [21:19] I could do an exists() check on the system location, then use ~/local/bin before aborting... [21:19] 256 BUG REPORTS.!?!?!? [21:19] Is that bad? [21:19] I KNOW ITS LOADS [21:20] SWFKL2NRIUP2P=F}"s [21:20] WE HAVE LIKE 8 DAYS TO FIX THESE [21:20] I can help if you like [21:20] Red_HamsterX: call the file again. [21:20] I'm tailing the http error log [21:20] Done. [21:21] I'm going to implement the workaround, though. [21:22] nothing in the http error log [21:24] the only error I see in the http error log (aside from the missing favicon) is: "client denied by server configuration: /home/godbyk/screenshots.ubuntu-manual.org/config/" [21:26] So the bzr binary is in /home/godbyk/local/bin/? [21:26] config/ is protected by .htaccess. [21:26] That's probably what caused the error. [21:27] Red_HamsterX: yes. [21:27] $ which bzr [21:27] /home/godbyk/local/bin/bzr [21:27] gotcha [21:28] I just tried loading it twice to make sure. [21:29] Pushing a workaround... [21:29] Done. [21:30] Red_HamsterX: pulled [21:34] Still doesn't seem to be working... [21:34] does it auto-pull? [21:35] Can you put the following in get_status.php, on line 25, just before the exec() call? [21:35] echo $bzr_path.' ls -qR '.$_BZR_SCREENCAP_BASE.escapeshellarg($_REQUEST['language']); [21:35] I want to see exactly what it's trying to call. [21:36] Red_HamsterX: It's set to auto-pull every 30 minutes at the top and bottom of the hour [21:37] Red_HamsterX: done [21:37] Okay. I can work with that timeframe pretty easily. [21:37] I can disable the auto-pull for now, too. [21:37] In fact, I'll do that. [21:38] since it was killing me the other day when I was fiddling with the website. :) [21:38] okay, disabled auto-pull for now [21:42] /home/godbyk/local/bin/bzr ls -qR lp:~ubuntu-manual/ubuntu-manual-screenshots/'fr' [21:42] That's what it says it's running... [21:42] If you put that into a shell, does it work? [21:42] You should see, after a few seconds, a list of chapter directories. [21:43] I'm expecting some sort of error to be reported almost immediately, though. [21:43] Red_HamsterX: $ /home/godbyk/local/bin/bzr ls -qR lp:~ubuntu-manual/ubuntu-manual-screenshots/'en' [21:43] bzr: ERROR: Not a branch: "bzr+ssh://bazaar.launchpad.net/~ubuntu-manual/ubuntu-manual-screenshots/". [21:44] We don't have an 'en' branch. [21:45] (Which is why I chose fr) [21:46] Red_HamsterX: $ /home/godbyk/local/bin/bzr ls -qR lp:~ubuntu-manual/ubuntu-manual-screenshots/'fr' [21:46] lp:~ubuntu-manual/ubuntu-manual-screenshots/fr/chapter-1/ [21:46] lp:~ubuntu-manual/ubuntu-manual-screenshots/fr/chapter-10/ [21:46] lp:~ubuntu-manual/ubuntu-manual-screenshots/fr/chapter-2/ [21:46] lp:~ubuntu-manual/ubuntu-manual-screenshots/fr/chapter-3/ [21:46] lp:~ubuntu-manual/ubuntu-manual-screenshots/fr/chapter-4/ [21:46] lp:~ubuntu-manual/ubuntu-manual-screenshots/fr/chapter-5/ [21:46] lp:~ubuntu-manual/ubuntu-manual-screenshots/fr/chapter-6/ [21:46] Bleh. [21:46] lp:~ubuntu-manual/ubuntu-manual-screenshots/fr/chapter-7/ [21:46] lp:~ubuntu-manual/ubuntu-manual-screenshots/fr/chapter-8/ [21:46] lp:~ubuntu-manual/ubuntu-manual-screenshots/fr/chapter-9/ [21:46] So it's working fine... [21:46] http://stellvia.uguu.ca/~flan/screencaps/get_status.php?language=fr [21:46] That's what it should generate. [21:46] The --END FINAL signifies that bzr found data. [21:47] (It's one entry per line. I just didn't bother setting it to text/plain) [21:48] hmm.. [21:48] I'm trying to see if php will tell us the output to STDERR [21:48] The single quotes are just a bash-escape, to prevent arbitrary execution of additional commands or stuff like that. [21:49] Well, we could change the comamnd to redirect STDERR to STDOUT and then echo $output... [21:49] lemme do that [21:49] 2>&1 [21:49] It should work in PHP. [21:50] Since I think the entire command is processed by the shell before pipes are set up. [21:51] wiatt whtf [21:51] why am I now on rev 530 of the manual? [21:51] have we gone backwards? [21:52] Aha! [21:52] [0] => bzr: ERROR: Couldn't import bzrlib and dependencies. [21:52] [1] => Please check the directory containing bzrlib is on your PYTHONPATH. [21:52] [2] => [21:52] [3] => Traceback (most recent call last): [21:52] [4] => File "/home/godbyk/local/bin/bzr", line 107, in ? [21:52] [5] => import bzrlib [21:52] [6] => ImportError: No module named bzrlib [21:52] Ah. [21:52] Yes, that could definitely do it. [21:52] what's happened to the branch?? [21:52] humphreybc: ? [21:52] http://bazaar.launchpad.net/~ubuntu-manual/ubuntu-manual/main/changes [21:52] latest revision is 530 [21:52] last night it was 554 [21:52] remember? [21:53] Maybe someone merged the newer changed with one of their commits. [21:53] check the spreadsheet, everyone is checking bugs on 554/555 [21:53] changes( [21:53] Reducing them all to one node. [21:53] I am looking it doesn't build which i can fix i think it has been merged [21:53] That is odd. [21:53] bzr frightens and confuses me! [21:53] we've lost 50 commits? [21:53] ;-) [21:53] godbyk: you know i was telling you about the line calling screenshots it has been uncommented again [21:54] it was dutchie who broke it! [21:54] is sayantandas here? [21:54] there are no commits on record between the 18th and the 21st March [21:54] bzr fightens and confuses me, too. [21:54] does that mean we lost three days worth of commits? [21:54] DVCS in general does that. [21:54] It means the merge superseded everything. [21:55] It may include all of those changes. [21:55] crap [21:55] so now all the testers are testing something that's older than our branch, but 24 revisions ahead?! [21:55] I merged over someone's changes in Quickshot a few days ago, but I think I was able to patch everything back in. [21:55] ubuntujenkins: great. [21:55] I am fixing with a note not to uncomment [21:55] humphreybc: do you want to skim through the bzr logs and see what's been changed and if we're still okay or if things are borked? [21:56] what? [21:56] that was mine Red_HamsterX ;-) you did it fine [21:56] what did I break? [21:56] Does anyone have a 555 working copy? [21:56] http://bazaar.launchpad.net/~ubuntu-manual/ubuntu-manual/main/changes [21:56] dutchie, the branch had gone back about 20 revisions [21:56] since when? [21:56] yesterday it was up to about 560 odd [21:56] If so, you can probably diff it and apply a patch. [21:56] hmm [21:56] we released rev 554 to the testers [21:56] Sorry, ubuntujenkins. D: [21:56] and that's what everyone is testing on [21:56] I've got a copy of this: $ bzr revision-info [21:56] 555 humphreybc@gmail.com-20100322032628-x7u14y55m6ap1uib [21:57] Red_HamsterX: no problem it still works [21:57] but now we're back to 530 somehow [21:57] humphreybc, hi :) [21:57] * dutchie hasn't done anything bzr related for a while [21:57] $ bzr revno [21:57] 535 [21:57] if you check the dates, it looks like there has been a gap for 2 days, nothing committed on the 19th or 20th [21:57] wtf [21:57] dutchie: you have 535? [21:58] yep [21:58] okay i'm confused [21:58] does this mean we lost two days of work somehow? [21:58] we were at 565 and then Sayantan pushed 528-530. [21:58] :\ [21:58] I had a felling Ayantan caused it [21:58] humphreybc: are you subscribed to the bzr log emails? [21:58] godbyk, yea [21:59] hang on, I've got a subscription to the RSS feed [21:59] looks like 529 was the big merge. [21:59] yeah so we got up to 565 [21:59] where jamin pushed all his changes [21:59] it lists 561-565, then goes back to 506 [21:59] fixed a tonne of bugs from the spreadsheet [21:59] crap [21:59] ask the folks in #bzr what's going on? [22:00] humphreybc, it's possible that the bugs are still fixed. The number-change may not reflect a progress-change. [22:00] Don't panic just yet. [22:00] okay [22:00] can someone please check [22:00] take a look at the spreadsheet [22:00] find a bug that's marked fixed by jamin [22:00] see if it's actually fixed [22:00] bzr push has been done the manual will compile again [22:00] * ubuntujenkins looks [22:01] uh oh, looks like the errors are still there [22:02] Looks like my cron pulled a post-merge update... [22:02] ...so I can't provide a diff. :( [22:03] crap [22:03] can we revert to jamin's last push. 565? [22:04] run bzr log -n0 [22:04] row 62 is fixed [22:05] 529 mentions some commits by jaminday... [22:05] wait [22:05] run bzr log -n0 [22:05] have a look at rev 525 [22:06] there are a shitload of *sub* revisions [22:06] * godbyk is scared to touch anything now. :) [22:06] For 525? No, there aren't. [22:06] wow, this is a *big* pull [22:06] wait [22:06] For 529, yes... [22:06] eyah [22:06] but if you look at [22:06] revno: 525.4.25 [22:06] jamin's last push [22:06] was rev 565 [22:07] Oh, actually, there are a lot of 525-subs in 527. [22:07] Many by jaminday. [22:07] * dutchie prefers git ;) [22:07] So maybe a lot of the fixes were preserved. [22:07] * Red_HamsterX prefers Subversion. [22:07] branch and tag. =P [22:07] http://paste.ubuntu.com/399564/ [22:08] cjohnston: what revison is you version of the manual on? [22:08] * godbyk at least groks svn. DVCSs seem a lot more complicated. [22:08] bzr confuses me [22:09] git took a while to get my head around properly, but it seems founded on a much sounder model than bzr [22:09] huh? [22:09] I suppose all we can do is ask jaminday to quickly check the status of 530... [22:09] * dutchie is now on rev 531 [22:09] git makes sense. [22:09] http://bazaar.launchpad.net/~ubuntu-manual/ubuntu-manual/main/revision/529 [22:09] cjohnston what bzr revison are you on? [22:09] look at the files removed/modified [22:09] don't update it yet [22:10] * cjohnston isnt doing anything with manual yety [22:10] yet [22:10] What version have you pulled? [22:10] http://bazaar.launchpad.net/~ubuntu-manual/ubuntu-manual/main/changes/525.4.25 [22:10] cjohnston: no problem we just could do with an older version if someone has one [22:10] you can get it all from LP [22:11] I have to head off to my ubuntu hour... ill be back online when I get there [22:11] cjohnston: we've had a bit of a scare, with a load of revisions apparently disappearing [22:11] cjohnston, there was a branch merge and we're trying to make sure everything is accounted for. [22:11] If you have a pull from the past couple of days, please on't update it yet. [22:12] i think we might be okay [22:12] someone check if megan fox is still in the prologue? [22:12] http://bazaar.launchpad.net/~ubuntu-manual/ubuntu-manual/main/changes/525.4.25 [22:12] * dutchie wonders if there is a way to make it not have to compile the manual 15000 times every time [22:12] I think so, too, based on the sub-commits. [22:12] Comppiling postscript is fun, though~ [22:12] humphreybc: she is in my 535 version [22:12] really? [22:13] megan isn't in my 530 one [22:13] so your 535 one is older than my 530 one [22:13] not in mine either [22:13] which means that the testers have an older version, but a newer revision number. [22:13] so i think our changes are fine [22:13] http://media.joshh.co.uk/megan.png [22:13] dutchie: probably, but we have run it at least 3-4 times with makeglossaries and makeindex interspersed to get everything to come out right. [22:13] just the rev count was fucked when there was a big merge [22:13] um okay [22:13] why was she ever there? [22:13] for times like this :P [22:14] haha [22:14] godbyk: another thing for your todo list ;) [22:14] are we sorted then? [22:14] so when we update the testers PDF, they'll all be like WTF cos the rev number has gone down [22:14] (and it wasn't my fault :P) [22:14] but we'll have to somehow tell them that they now have a newer version... [22:14] sigh [22:14] I think we should wait for this to die down before worrying about PYTHONPATH, godbyk. =P [22:14] Red_HamsterX: apparently. :) [22:15] I'll eat lunch in the meantime. [22:15] either that, or we could push 40 times in the next few hours before we update the translations stuff [22:15] * dutchie returns to maths [22:15] (good excuse to take a break) [22:15] * Red_HamsterX returns to Python issue-tracker stuff. [22:15] and whoever Sayantan is needs to be banned from bzr [22:16] That seems a bit harsh. :( [22:16] lol [22:16] I still fail at bzr. [22:16] he needs a talking to [22:16] all you ahev to do is a pull before a commit [22:16] Pull beore you commit? [22:16] Yeah. [22:17] It's a hard habit to break when coming from centralised VCS, though. [22:17] Pull before developing anything new... [22:17] I messed up bzr on my first use, I e-mailed the person whos commit I wrote over in a right panik [22:17] :-P [22:17] I think I have four such offenses in Quickshot. [22:18] Red_HamsterX: if you only commit when you upload and always do a pull before you will be fine [22:18] Yeah, that's what I'm doing now. [22:18] cool [22:19] But I'm so used to svn complaining during the commit process that I've learned to use it as a crutch for speed's sake. [22:19] is my name showing in the spread sheet any one? if not how do i make it show? [22:19] Red_HamsterX: fair enough [22:19] Update before writing code, write code, commit, walk away. [22:20] hope nobody else does the same while code is being written... [22:20] Well, yes, but if they do, it'll get caught during the commit. [22:20] Instead of branches diverging. [22:21] "Merging that Just Works truly can change how developers work together." [22:21] * humphreybc wonders if we need to make our team/branch restricted [22:21] from the bzr docs page [22:21] right, maths time [22:22] stop distracting me [22:22] humphreybc, +1 [22:22] humphreybc: do you know if jamin wants any help fixing bugs? [22:22] hey so daker, you all good with the website? did josh pass the message on? [22:23] josh =? dutchie [22:23] ubuntujenkins: not sure, you could probably go through and help him fix small ones like spelling mistakes/missing commas and what not [22:23] josh = dutchie [22:23] yeah [22:23] ubuntujenkins: perhaps it would be better if you assign all the new bugs to people [22:23] from 111 onwards they're not assigned [22:23] humphreybc: I don't mind what i do but can't write to the spreedsheet [22:24] oh can you not? [22:24] last time i checked you needed a @ubuntu-manual.org e-mail [22:24] godbyk, can you set up Luke with an @ubuntu-manual.org email please [22:24] thanks [22:25] humphreybc: Give me his full name and email address. [22:25] ubuntujenkins: ^^ [22:25] Luke Jennings ubuntujenkins@googlemail.com [22:26] * daker wants a @ubuntu-manual.org e-mail to :) [22:27] godbyk, while you're at it, give daker one as well :) [22:27] gimme his details [22:27] daker ^^ [22:27] Adnane Belmadiaf adnane002@gmail.com [22:28] hey daker did you see the new contributions mockup I did? [22:28] (presuming it wasn't overwritten [22:28] not yet :s [22:28] yay it's still there [22:29] in the branch, website/source/contributors.png [22:29] oki [22:29] oh and daker, all the text is now finalized, I've changed some of it [22:29] I just changed it in the mockups [22:29] oki humphreybc [22:29] both accounts are created now [22:29] humphreybc: if the bug is just grammer does it matter who i assign the bugs to just do it evenly? [22:30] thanks godbyk [22:30] also, i was just thinking, when you see the contributors page you'll see the top section with the key people like me, Kevin, Jamin etc. Could you make each name a hyperlink with their email address, so like Jamin's name would be a hyperlink "mailto:jamin@ubuntu-manual.org" [22:30] thanks godbyk :) [22:30] etc [22:30] assign all the bugs for one chapter to one person. that way it reduces the potential conflicts we'll have. [22:30] makes sense [22:30] yeah, so basically jamin is doing prologue - 3 [22:31] i'm doing 4,5 and 6 [22:31] Bryan is doing 7, 8 and 9 [22:31] I think that's how it is [22:32] cool on it now [22:32] sweet [22:33] there is meant to be a rule that automatically colour codes the boxes [22:33] but it's not happening for some reason [22:33] no idea why [22:34] so you'll just have to do it manually [22:34] is bzr sorted now? [22:34] i think so [22:34] cool [22:34] godbyk, did you set up the auto update thing? [22:34] humphreybc: not yet. [22:35] have any edits been committed yet? [22:35] can someone link me the docs login page please [22:37] ubuntujenkins: docs.ubuntu-manual.org [22:37] its not showing in the list [22:38] http://spreadsheets.google.com/a/ubuntu-manual.org/ccc?key=0AiussLy2MfjjdHRrYlR0Q0RMRXRTaXJuR2w0QjFUcXc&hl=en [22:38] thanks [22:39] why isn't it showing in the list? [22:39] it's set to allow all ubuntu-manual.org users to edit it [22:39] no idea [22:39] it does now must be a accout set up thing [22:40] there should be no excuse for not pulling before pushing now, i've emailed the list, facebook, twitter and contacted that user directly [22:41] humphreybc, the website works very well in Chrome, Opera, FF, IE6,7 and 8, Safari [22:41] daker, yeah i saw that, awesome work [22:41] it's looking great :) [22:49] shouldn't it be 'pull before commit'? [22:53] huh? [22:53] did i cock it up? [22:54] oh right [22:54] yeah it should be [22:54] but whatever [22:54] * humphreybc has too much stuff on to worry about details [22:54] :P [22:55] pff.. it's *all* about the details. :) [22:55] i know i know [23:01] Red_HamsterX: I've added "PYTHONPATH=my_pythonpath" to the beginning of the exec line. we should add that as a var to the config file along with the bzr path location. [23:06] are well night all o/ [23:08] hey godbyk, can you give us some fun statistics on how many people have downloaded ubuntu-manual-draft.pdf? [23:08] and how many hits we've had at ubuntu-manual.org ? [23:08] one sec. [23:10] won't have any real stats until tomorrow after the stats programs run. [23:10] ah okay [23:10] that's all good then [23:10] any numbers I gave you now would be useless. [23:10] sweet [23:10] looking forward to seeing some numbers [23:10] :P [23:11] i'm going to stick my neck out here and say that UMP brings a whole new level of epicness to Ubuntu projects [23:11] everything we seem to do is highly ambitious and completed in an incredibly short time frame [23:11] like fixing potentially thousands of bugs in 7 days [23:11] wow, that maths paper was fun [23:12] now for more maths [23:12] lol [23:13] * daker will release a beta version of the website the 31 march [23:13] daker = awesome [23:13] godbyk, daker, can we still keep using test.ubuntu-manual.org while we have the other website running like it is at the moment? [23:14] humphreybc: they're pulling from the same place right now. [23:14] so unless someone reorganizes stuff, no [23:14] so we'd have our final website, which is being tested at test.ubuntu-manual and then we have our temporary countdown/bug reporting website for this bug reporting stuff [23:14] (and if you do go about reorganizing things you have to talk to me first, or you'll break the live site) [23:14] either that or daker integrates the bug reporting form into his final website [23:14] i can [23:14] the live site is the final site. [23:15] perhaps daker copies everything in daker to daker-test and works on his site from there [23:15] I just hid the nav options for pages that aren't complete yet. [23:15] okay cool [23:15] kk [23:15] All i'm trying to avoid is testers seeing our website change all the time as daker changes stuff [23:15] you can still access the pages directly. [23:15] okay that's cool [23:15] likt http://screenshots.ubuntu-manual.org/get_status.php?language=fr [23:15] i'll copie daker to daker-test ? [23:15] er [23:15] http://ubuntu-manual.org/?contributors [23:16] if you know where to look [23:16] so daker can work on the home page with the fancy javascript transition thing and no one will see it [23:16] uh [23:16] sure. [23:16] lol [23:16] stop confusing me! :) [23:16] all i want to do is make sure that a) the current site that people are using for reporting forms stays that way and is stable, and b) daker gets a place to test his website, where no one else can see [23:17] so in theory we want ubuntu-manual.org to stay how it is, but test.ubuntu-manual.org to be pointing at a different folder in the branch, ie, daker-test, where he can test out the new home page/contributors pages and stuff with the links intact [23:17] does that make sense? [23:17] godbyk, one minute [23:18] * humphreybc thinks that our manual might be more popular and highly anticipated than lucid itself [23:18] "Enrique Raimundo I just can't wait!!! 60% Ubuntu manual progress!!!" [23:18] that'd be pushing it I think humphreybc [23:19] lol [23:19] the music store is ludicrously cool [23:19] true [23:19] as is the deep integration of mail/microblogging/chat [23:19] would be kinda funny if ubuntu-manual.org got more hits on the 29th than ubuntu.com [23:19] not going to happen but [23:19] dreams are free [23:21] * daker is doing a hundreds things at the same time [23:21] if you want test.ubuntu-manual.org to differ from ubuntu-manual.org, then they should be pointing to two separate directories, yes. [23:21] okay, so let's copy what's in daker to daker-test [23:21] leave daker as it is [23:21] humphreybc, +1 [23:21] point test.ubuntu-manual.org at daker-test [23:22] daker can work on his beta release of the final website in daker-test, with the nav buttons restored, no countdown timer and what not [23:22] daker, because we're going to be using the bug form after this week anyway, you could build support for it into your final website [23:23] and daker, if you could fix the integration of the form confirmation dialog, that would be cool [23:23] (fill out the bug form and hit submit, you'll see what I mean) [23:23] one sec [23:24] what integration? [23:25] the confirmation box where it says "Thanks for reporting the bug, we'll fix it as soon as we can." [23:25] what about it? [23:25] you can see how it's just sort of floating in the content area of the website [23:25] (maybe it's just in chrome) [23:25] floating? [23:26] the whole form is in an