[00:00] holy mackeral [00:00] we have 361 fans on facebook... [00:00] cool [00:00] life's tough when you're famous [00:00] 13 days ago we had 169... [00:00] that's nuts [00:01] http://www.facebook.com/pages/The-Ubuntu-Manual/266794861575?ref=ts [00:03] guys check the top of the pad [00:03] i'm making a top 5 list [00:03] have a look, tell me what you think [00:03] and when Ilya comes in, let him know about this pad [00:05] Having trouble thinking of a fifth point? [00:05] humphreybc: any reason why quickshot doesn't use GtkAssistant to set up everything? time constraint? [00:05] Mmm... LaTeX... [00:05] Good choice. [00:06] kklimonda: no idea, i started it with quickly [00:06] because that seemed easiest from what i was told [00:07] humphreybc: re: translators. if they're translating to a new language have them email me to give me a heads-up. [00:07] humphreybc: I was thinking about using GtkAssistant widget to display all pages of the setup phase (i.e. user creation etc.) [00:11] top five list is looking good, benjamin [00:11] semioticrobotic: you're bryan, right? [00:12] yep ... it's me [00:12] kklimonda: okay, sounds good - you'll have to chat to TommyBrunn or Luke Jennings to sort it out. I'll put their email addresses up on the to do list [00:15] okay folks ... gotta get my lectures ready for tomorrow's classes [00:16] I'll check the pad in a day or two for an update on progress [00:17] sweet as [03:01] Okay, I won't be able to get anything done tonight, but I'll dive right into the code tomorrow, at the first chance I get. [03:54] hi guys, i'm back [03:55] had coffee with Tim, Launchad/bzr release manager [03:55] he suggested a pretty cool way to do this quickshot thing and he's going to help with the launchpad side of stuff [03:59] How many Canonical employees did you say there were in .nz again? [03:59] Also, what's his idea? I'm just starting to look at the code now. [03:59] (I got home an hour ago) [04:00] I probably should have line-broken that. [04:07] um i think there are 2 or 3 [04:07] do you have skype? [04:07] (easier to explain over skype) [04:10] I do not. Something about a non-free protocol and me coming from the Debian world. :( [04:11] So the code, at this stage, is basically "display about"? [04:12] okay, that's all good [04:12] basically Tim thinks we should create a new user on Launchpad for Quickshot [04:12] upload an SSH key for that user [04:12] then attach the SSH key to Quickshot [04:13] so everyone who uses Quickshot acts as "that user" [04:13] And then share the private key with the users on all test systems? [04:13] and they'd have full write access to the branch [04:13] no we'd keep it private [04:13] i guess [04:13] How would they push changes, then? [04:13] it's attached to quickshot [04:13] so quickshot *is* the user [04:14] and the "quickshot launchpad user" owns the branch(es) [04:14] so anyone with quickshot can push [04:14] ie, write to the branch [04:14] he then suggests that when someone is pushing we lock the branch until they're done - bzr automatically will wait until the branch becomes available to push - we can just display a message saying that someone else is pushing and it won't take long [04:14] No, I get that... but a private key is needed for the commit, unless I'm missing something about how Launchpad/BZR commits work. [04:15] well i'm not sure of that detail, but he is the release manager for bzr/launchpad so it all comes under his domain [04:15] i can talk to him to clarify stuff like that [04:15] he says he'll do as much as he can to iron out any kinks on the launchpad end to make it easier for us [04:15] It's a pretty trivial detail in any case. If the ey gets compromised, the worst that can happen is that a rollback is needed. [04:15] key* [04:15] yeah, exactly [04:16] as for having multiple branches or not, it really depends how big each image will be [04:16] if each image is >100kb then multiply that by 50 then by 47 [04:16] We could do a quick test with PIL and indexed PNGs. [04:16] yeah [04:16] i suggest that we stay with branches for each language [04:16] (To see if they're usable when indexed) [04:16] because it's already half set up [04:17] and we can just set the quickshot user as the owner for the project - ie, the owner for the branches [04:17] he also mentioned to use bzrlib [04:17] and to talk to lifeless, who is the canonical employee who is the main developer for bzr [04:17] so i'll see if i can grab him [04:19] bzrlib looks pretty well-documented... I could probably have that running in a couple of hours this weekend. [04:20] Though it probably shouldn't be a high priority... I mean, once everything else is done, it's just a matter of running the command fifty times, distributed amongst multiple users, and it's not hard to type it out. [04:21] It would be nice to have it ready in preparation for 10.10, though. [04:21] well, we were aiming for 10.04 .... :) [04:21] (yes our project is crazy) [04:22] I don't think it's unachievable. [04:22] just tough, right? [04:23] I can hack code pretty fast. [04:23] :) [04:23] i'll grab thumper to see if he can come in here and chat to you [04:23] I'll do my best to please you this weekend. [04:27] So is the plan, post-grabbing-of-screenshots, to apply a series of (top, left, width, height) values to each image to extract the relevant rectangles for automatic insertion into a translatable LaTeX document? [04:31] ugh - i think so. Tommy's the one to talk to about that, and Luke - they know more about it than I. [04:32] but they're conveniently asleep now :) [04:32] http://doc.bazaar.canonical.com/bzr.dev/developers/integration.html [04:34] I'll try to catch them earlier tomorrow, then. [04:34] Since I'd probably be able t help most by writing libraries while they focus on design. [04:34] Until I'm fully up to speed. [04:35] awesome [04:35] i'll ask thumper if he can join this channel too [04:35] I'll be going to sleep shortly, unfortunately. [04:36] I need to be up for 4:20 to make it to my place of workage. [04:36] that's okay, i mean just for future [04:36] crap! [05:28] hi [05:28] who is the creator of the ubuntu manual webpage/ [05:28] (report in if present) [05:36] well, if you (creator) read this, email me at wolterh6@gmail.com [07:20] hi Rudi! [07:21] hello humphreybc! [07:21] so what would you say is your biggest skill? [07:21] or what would you most like to do? [07:21] if you take a look at this, it's a list of things that need to be done: http://pad.ubuntu-uk.org/aA6ygCXL9F [07:21] I'm not really sure, I looked at the blue prints and they all seemed to be going pretty well [07:21] I can do the screenshots, once the RC/beta is released [07:22] I can also edit [07:22] well if you're confident in english and know about ubuntu, we really need help on two chapters [07:22] allrighty :) [07:23] which two? [07:23] chapter 4 and 6 are the big ones that are lacking [07:23] you know how to use bzr? [07:23] on the etherpad, take a look under the heading "MANUAL" [07:23] ok... [07:24] godbyk: / humphreybc: what is the background color of the pdf? #000 or off white? [07:24] the part where i can see people writing at the moment? [07:25] i thiink it's plain white but not sure [07:25] actually it should be plain white [07:25] hmm.. [07:25] because it's to be printed, right? [07:26] so we don't want to make them print full page off white [07:26] :) [07:26] ;) yeah , but still the pdf would have a background color , iirc [07:26] where is the pdf located , too many folders in the branch 0.o [07:27] you have to build it :P [07:27] pff.. [07:27] run make [07:27] it's very simple [07:27] oh wait [07:27] do you not have latex? [07:27] i'll make it for you, hold up one se [07:27] sec* [07:27] i dont think so :( [07:28] okay, give me two secs [07:28] ty [07:29] humphreybc, i have bzr installed and i'm ready to go :) [07:30] cool, run "bzr branch lp:ubuntu-manual" [07:30] bzr branch lp:ubuntu-manual [07:30] lol [07:31] my bad [07:32] yup [07:32] then you'll need to run the install script under /pkgs [07:33] which install LaTeX 2009 I think [07:33] it's a fairly big download, 2GB or so (sorry!) [07:33] if you don't want to do that it's not the end of the world [07:33] you can work on the chapters in the .tex files themselves in a program like gedit [07:33] 2GB for latex install! o.0 OMFG [07:34] you just won't be able to compile it into a PDF to see what your work looks like, but you can push your new stuff and one of us can check it if you like. I recommend install latex anyway [07:34] I only have 3GB of bandwidth a month :O [07:34] ah [07:34] bandwidth starved south africa... [07:34] well, in that case, write your chapters in .text files in the correct directory [07:35] oki :) [07:35] and one of us can take what you've written and convert it to tex files with commands and stuff [07:35] :) [07:37] * vish still waiting for pdf from humphreybc ;) [07:37] oh [07:37] oops! [07:37] i forgot for a sec, got distracted [07:37] :P [07:38] ;) [07:42] sry battery ran out [07:42] no probs , just push to bzr? /ubuntu-manual/graphics/ when you are free [07:43] * vish bbl [07:43] yep [07:46] humphreybc, i am now connected to the branch [07:46] kk hold up one sec [07:46] had to add an ssh key to launchpad [07:47] vish, pushing now, revision 383 [07:47] /graphics/main.pdf [07:48] good morning! [07:49] morning! [07:50] Rudi, cool, so you can see the files and stuff? [08:00] Hello, my name is Ronald an active member of the Ubuntu Zimbabwe LoCo team [08:00] hi ronald! [08:00] I am available to invest time in writing chapters and proof reading the manual [08:00] yay! [08:01] have you got experience with bzr or latex? [08:01] unfortunately no, I am prepared to learn [08:01] okay [08:01] so, you'll need to do this: sudo apt-get install bzr [08:02] done [08:02] cool [08:02] now, make a new directory in your home folder called "projects" or something [08:03] then inside that folder, run "bzr branch lp:ubuntu-manual" [08:03] you'll want to set up bzr too, use bzr whoami [08:04] with the quotes?? [08:04] nope [08:05] have a look at https://wiki.ubuntu.com/ubuntu-manual/Help [08:05] also check out https://wiki.ubuntu.com/ubuntu-manual/contributions [08:06] I will, its downloading something [08:11] ubuntujenkins, meet thumper :) [08:11] ubuntujenkins: hi [08:11] heh [08:12] scared off already [08:12] hi thumper [08:12] sorry about that lucid has a very anoying enter key bug for me [08:13] :) [08:13] godbyk: did you talk with Charlene already? [08:14] ubuntujenkins: thumper is the canonical project lead for launchpad/bzr integration [08:14] ooo nice [08:14] i had coffee with him today and he has a cool idea for the quickshot bzr stuff [08:14] I was thinking I should talk to lifeless before we charge down one track [08:14] I have a feeling that the entire picture store could be done with a single branch [08:14] without hitting the users too much [08:14] lifeless is a person right? [08:15] ubuntujenkins: yep [08:15] lifeless is a core bzr developer [08:15] and a very smart guy [08:16] fair eonough, when I spoke to people in #bzr they said we can't do it untill nesting was implimented but it would be easyier if we could do it [08:17] what time zone is liffless in? [08:18] thumper did you have any other suggestions? [08:19] ubuntujenkins: UTC+10 [08:19] I've just been thinking about the branch layout [08:19] cool [08:19] there is nothing to say that a PGP _has_ to be private [08:19] only that it _should_ be private [08:19] or SSH key really [08:20] humphreybc: seems you pushed an empty commit > http://bazaar.launchpad.net/~ubuntu-manual/ubuntu-manual/main/revision/383 , the pdf isnt actually added [08:20] by having a shared private key you open yourself up to potential abuse [08:20] sure I follow so far [08:20] one thing that you'd want to do is to set append only on the branches [08:20] that way if someone did try to remove stuff [08:21] you can just revert their commits [08:21] and you won't lose data [08:21] right i will look at that [08:21] humphreybc: do this `bzr alias commit="commit --strict"` [08:22] humphreybc: that way commit will fail if there are unknown files [08:22] humphreybc: which happens when you forget to add [08:22] i added a file though [08:22] it *is* there [08:22] i'll try again in a minute, hold up folks [08:23] thumper I am utc, I will just nip and have a show I have lectures in 20 mins [08:23] *shower [08:24] ubuntujenkins: ETOOMUCHINFO [08:24] lol [08:30] humphreybc - I have followed your instructions, whats the next step? [08:31] ronald_: sorry :) [08:31] so you've pulled the branch? [08:31] how much bandwidth do you get a month? [08:31] ie, what's your internet plan like [08:32] back thumper [08:32] I am on a fiber network, bandwidth is not a challenge I work for an ISP, I have free Internet from 7 pm to 7 am [08:32] yay! [08:32] godbyk: piong [08:32] ping, well, piong could work too i suppose [08:33] I have never seen the channel so busy [08:33] oh believe me it's been busier than this! [08:33] you should have seen the first meeting.... [08:33] wow. [08:34] I didn't join untill the second or third unfortunatley [08:34] okay, so ronald_ you'll now have to run /pkgs/install-pkgs.sh [08:35] this might take a while, as it will install LaTeX 2009 and a whole heap of fonts and dependencies, which come to about 2GB [08:35] it says bash: /pkgs/install-pkgs.sh: No such file or directory [08:35] ./pkgs/install-pkgs.sh from the ubuntu-manual directory [08:36] include the ./ at the beginning [08:36] thanks [08:36] vish, the reason the branch didn't detect the pdf was because it was in .bzrignore - but i'm just going to rename it and push again. i should have realised in the first place, d'oh! [08:37] vish, revision 384, /graphics/manual.pdf :) [08:38] ah TommyBrunn is here now! [08:39] TommyBrunn, meet thumper - Canonical launchpad/bzr release manager [08:39] Hey there. [08:39] humphreybc: just the release manager for 10.02 of Launchpad [08:39] normally just called launchpad-code team lead [08:39] thumper: okay :) [08:39] *sigh* the software center could be so much better.... [08:40] IlyaHaykinson_: i agree totally [08:40] they certainly have plans to improve it, by v4 [08:40] i.e. 11.04 [08:40] yeah [08:40] seems to be making rather slow progress? [08:40] but, well, that's a while from now. and until then, there's user confusion. [08:41] probably just not a lot of resources dedicated to it. after all, this is actually written by canonical. [08:41] hehe [08:41] what's it written in? [08:41] no idea, actually. [08:42] ah. python + gtk [08:42] that's what i guessed [08:43] so for a python app that's basically just a gui front end to apt, and considering they have synaptic to take stuff from, it's taking them a long time to make any progress. oh well. [08:43] hm, well, there's more to it of course [08:43] what can ya do? haha [08:43] well yes [08:43] the whole app review system is new [08:44] indeed. plus everything simple is always more complex than it seems :) [08:44] take quickshot for example... [08:44] lol [08:44] so i bet just getting the UI to work right, and fast, and reliably, is a big enough challenge [08:44] for a few part-time devs [08:44] or UMP - all we're doing is writing documentation, but it seems to be very hard haha [08:44] :) [08:45] maybe some day when i have a ton of free time, i'll pick a project like the software center and start hacking on it. [08:45] i love python, and would love to learn some gtk+ in the process of working on something [08:46] (but don't try to recruit me for quickly or GC, heh) [08:46] er, quickshot [08:46] heh [08:46] yeah i'm the same [08:47] btw, IlyaHaykinson_ http://pad.ubuntu-uk.org/aA6ygCXL9F [08:47] oh and ubuntujenkins: http://pad.ubuntu-uk.org/aA6ygCXL9F [08:47] and pretty much everyone [08:47] yep got it already thansk [08:47] cool [08:48] wasn't sure if you had or not [08:48] nod; saw it. [08:49] oh btw, i cleaned up the main page of the wiki today [08:50] it should now be easier for new users [08:50] and i decided we're now on 64% completion :P [08:50] * humphreybc loves the completely unscientific progress bar [08:51] :) [08:51] i dispute your finding; 63.9% would have been a lot more appropriate! [08:52] haha [08:52] see i opted for 64% instead of 65% to make it look like we've got some hardout "live" thing [08:52] next time i update it i'll make it something like 68.1% [08:52] hehe [08:53] godbyk: could you please switch the website on test.ubuntu-manual.org to wolter's one now [08:53] thanks :) [08:54] humpreybc, i got bzr to start "fetching revisions, inserting stream data" [08:54] is that correct? [08:57] yep [08:57] just wait for a bit, it's downloading our project files [08:57] IlyaHaykinson_: rudi and ronald_ are going to help with writing and editing [08:58] guys, Ilya is basically in charge of coordinating the authors [08:59] rudi, ronald_: we need most help in chapters 4 (hardware) and 6 (system maintenance) right now. [08:59] noted [09:00] aye captain! [09:00] the harware chapter is about 1/10th finished, at best. [09:00] i think ubuntujenkins was going to take some portions of it [09:00] i believe printing and sound [09:01] so i would prefer if one of you can take CD/DVD burning [09:02] another can take webcams and scanning (these two should be simpler or require less text for now) [09:02] or, one of you can take Chapter 6 on and start thinking about it. [09:02] any takers? [09:02] i'm currently looking at chapter 6 as we speak [09:03] also, IlyaHaykinson_ rudi is on a 3GB bandwidth limit a month [09:03] so he's not going to download latex [09:03] but rather write his chapter in .txt files [09:03] then someone can convert them into .tex and insert commands. thoughts? [09:03] rudi, you can see the completed PDF in /graphics/manual.pdf [09:04] humphreybc,i'll go check quickly [09:04] that's what it looks like when you compile it if you had LaTeX 2009 [09:04] you could probably learn latex commands just by looking at the tex files and then seeing what happens in the pdf. it's not that hard, ie, \textbf{} makes the text inside the braces bold [09:04] eg, \textbf{this text now becomes bold} [09:05] ah, jaminday! [09:05] just the person i wanted to talk to! [09:05] hehe heya [09:05] for chapter 4, see the proposed outline at https://wiki.ubuntu.com/ubuntu-manual/Blueprints/Hardware [09:05] can you sort out your editors and get them to compile a progress report of their assigned chapter? [09:05] so get them to rate it out of 10, 10 being completed, 0 being not even started [09:05] note that this proposed outline is not comprehensive -- it may need to be expanded or contracted as needed [09:05] humphreybc i can see the pdf, it looks awesome [09:05] yep - i just saw that on the to-do list [09:06] i'll use the latex commands that i can see [09:06] and then you'll need to tell them to chase up the authors if their chapter is anything below an 8 [09:06] whereverpossible [09:06] for example, the section on webcams doesn't need to go into detail on ekiga [09:06] we want the editors and the authors working as a team of two people [09:06] what about cheese? [09:06] you want them to post the update on the whiteboard of their blueprint? [09:06] that would be great [09:06] we can mention cheese, but not cover it since it's not installed by default [09:07] e.g. chapter currently at x out of 10 completion etc [09:07] or get them to email the results to you, and you can send a summary to me or Ilya, or the list [09:07] yep. so the idea is that the authors write the chapter, they report to their _editor_ [09:07] yeah ok i'll do that, that way i can collate it better [09:07] rudi: if you send text files to me, i will incorporate them into the chapter. [09:07] the editor and the author work together closely as a _team_ [09:07] for Chapter 6, we don't really have a good chapter outline yet [09:07] i'll reiterate that - the team thing - in the email i'll send out [09:07] when they are both satisfied that the chapter is a 10/10, it gets signed off and that's the end of that [09:07] and what's in the table of contents is just a hint of what could be included, not the actual outline [09:07] awesome [09:08] so someone needs to think through what would make a good chapter [09:08] by team i mean, they should be talking to each other in here, private emails, skype if they must [09:08] given the time constraints [09:08] is the 10/10 completion rating to be used for an overall completion scale for the website as per earlier discussions? [09:08] also, if an editor is lucky enough to have multiple authors - then that's their team :) [09:08] * IlyaHaykinson_ reports his status on chapter 4: chapter is not doing well, no authors, so no editing. [09:09] jamin, not really, we're just manually doing that. check out the main wiki page [09:09] IlyaHaykinson: hmm, that is a problem [09:09] i just made a progress bar myself and we estimated the completion :D [09:09] who *was* writing 4? [09:09] humphreybc: ah cool i like it! [09:09] jaminday: nod. hence i'm recruiting ubuntujenkins, rudi, ronald_, and possibly anyone else [09:09] oh, various people over time. [09:09] jaminday, thanks :) it's also in the sidebar here: http://www.omgubuntu.co.uk/ [09:09] the original author dropped out [09:10] i recruited four more [09:10] okay [09:10] nice work [09:10] of which two submitted a bit of copy [09:10] then disappeared [09:10] IlyaHaykinson: excellent. Good to see we have some new people to help out as well [09:10] what happened to Wendy? [09:10] i think wendy never got ubuntu installed [09:10] darn [09:10] i think anyone with tech writign experience should be put to editing, not writing... [09:10] * humphreybc this room might be busier than offtopic :O [09:10] okay [09:11] well we have some editors [09:11] bryan is editing [09:11] and he's doing a great job [09:11] right. i know. [09:11] well, .... [09:11] yeah [09:11] bryan is doing mainly grammar changes [09:11] that's not editing [09:11] well maybe rudi can you edit? [09:11] since you don't have latex installed [09:11] well, rather, that's minor editing [09:11] okay, well, perhaps ask him to do bigger edits? [09:11] perhaps he doesn't know how much he's actually allowed to change [09:11] right now a lot of the changes we need are for structure, presentation order, completeness, etc. [09:12] well, have him take a cue from me. i [09:12] i'm mercilessly rewriting portions. [09:12] yeah Bryan is probably still getting a feel for the project so making some smaller changes initially [09:12] anyone who has a problem, can easily revert me, i won't get upset. :) [09:12] IlyaHaykinson: yes me too, although i've been somewhat quiet on the editing front for a while now [09:12] so Bryan should feel free to do likewise. [09:12] okay, jamin, how many people are actually *actively* editing? [09:12] jaminday: yes. *glares* :) [09:12] hehe [09:13] i don't mind editing [09:13] i think i'd actually prefer it [09:13] humphreybc: i'd say about 3-4 *actively* editing although not much has happened for a while [09:13] * humphreybc wonders if it's worth asking the docs team if they could spare anyone... [09:13] some have been waiting for more content [09:13] rudi: that might be good [09:13] okay, rudi, you're now an editor :) [09:14] jaminday, what chapters *need* editing? [09:14] although we do need content written pretty urgently so there is something there to edit! [09:14] true [09:14] okay, so, Ilya, how many people do we have actively writing stuff? [09:14] well i can write content too [09:14] well, right now i think we mainly need chapter 4 and 6 written [09:14] i talked to matt griffin tonight and he's going to add in his rhythmbox/music store/ubuntu one stuff soon [09:14] OR we need to decide to cut them completely [09:15] humphreybc: good. though how soon is soon? he didn't reply to a recent mail from me. [09:15] humphreybc: I don't think John Hart stuck around - i think he had too many bzr/LP issues so his assigned chapter probably needs an allocated editor [09:15] well the writing freeze is no the 31st, you guys all know that right? [09:15] IlyaHaykinson_: he knows about the writing freeze and he should have it done by next week [09:15] ok, wonderful. [09:16] he's been busy doing the music store testing since he's in charge of all that for canonical [09:16] understood. [09:16] jaminday: who's john hart? O.o [09:16] just as long as we don't have to cut it at the end. [09:16] nope, he knows it's important [09:16] rudi: i would say pick one of the things that we've mentioned, and go for it. [09:16] where has joe and kelvin gone? [09:16] the chapter 6 authors? [09:17] chapter 6 isn't too long, just by looking at it [09:17] i could probably power through that in a few hours [09:17] humphreybc: I met with John Hart a couple times over chat to get him set up but had some issues, then he stopped replying to my emails [09:17] there's enough work to go around -- writing, editing -- that you would be very helpful in any capacity [09:17] chapter 6 is not too long, but then again i don't think it's been thought out yet [09:17] just has a rough sketch of some must-haves in the TOC [09:17] yeah [09:18] okay, let's decide on a plan for chap 6 [09:18] then i can do that tomorrow [09:18] How about you both take a 'half' each (humphreybc and rudi) [09:18] yeah that could work [09:19] ie one on updating and one on upgrading [09:19] rudi, what do you feel like doing? https://wiki.ubuntu.com/ubuntu-manual/TableOfContents [09:19] there's updating or upgrading [09:19] i'll do updating? [09:19] well, at the very least, to me, "System Maintenance" means app updates; distro upgrades; disk space cleanup; backup [09:19] plus potentially user management [09:19] i think we have those covered except backup [09:20] and user management [09:20] which is pretty easy [09:20] and disk space clean up [09:20] backup: is this using something like rsync? or is it ok to get the end user to install something like grsync? [09:20] http://pad.ubuntu-uk.org/chap6 [09:20] team, GO! [09:20] rudi: we are trying to stick with GUI in the first 6 chapters [09:21] There are a number of GUI backup apps available but not sure what's in the default repos [09:22] Perhaps grsync is the way to go but i've never tried it [09:33] jaminday, thanks for clearing that up [09:34] jamin, you sticking around? [09:35] yep only for a couple of mins [09:55] humphreybc: sorry had to head off for dinner. I'll try and make it back tonight otherwise should be around again in the next day or two. Have allocated another couple of days to work solely on editing so hopefully we will make some more progress. [09:55] humphreybc: Also just email godbyk about our changes to chapter 6. Copied you into the email so you might have read it already. [09:56] *emailed [09:59] hi, i would like to help out with the web development. What do i do? [10:00] ajuliano: You could try to get the countdown-timer-thingy on http://ubuntu-manual.org to work in Internet Explorer. [10:01] It's available in the main branch, in ubuntu-manual/website/countdown/ [10:04] oO and ajuliano if you could insert http://ubuntu-manual.org/progressbar.png into the countdown timer thingy somewhere too that would be cool [10:04] do you know how to use bzr? [10:04] never done it before [10:04] ah [10:04] sudo apt-get install bzr [10:04] bzr branch lp:ubuntu-manual [10:04] website stuff is under /website [10:04] ok thanks [10:05] there are currently two versions of the main website, the stuff in /website and the stuff in /website/wolter-remake [10:05] but the countdown stuff is /website/countdown [10:05] i'm on my mac right now. Is there another way of doing it? otherwise I will try it out later today [10:06] the progressbar looks cool, how does the update work? [10:06] ajuliano: i can send you the files [10:07] i just manually update the .psd for it hehe [10:07] then i put it in the branch [10:07] anything in /website/countdown goes on ubuntu-manual.org [10:07] anything in /website goes on http://test.ubuntu-manual.org [10:07] ok, [10:07] ajuliano: what's your email address? i can zip up the countdown stuff for you [10:08] how good are you at web development? [10:08] till.albert@gmail.com [10:08] groovy [10:09] I do it for a living. [10:09] Working with both Drupal and Wordpress [10:10] Can do a lot of stuffs with php/html/css [10:10] I am a mix of a designer and coder [10:10] Oo [10:10] you're my new favourite person [10:11] :9 [10:11] :) [10:11] this is what i want our site to look like: http://humphreybc.wordpress.com/2010/03/01/more-website-mockups-new-get-involved-page/ [10:11] (i did these mockups last weekend) [10:11] Gotta go now, heading for a meeting [10:11] okay, no probs [10:11] I will check out ur site [10:11] sweet as [10:12] and gonna take a look at the files later today or tomorrow [10:12] btw, i saw the mockups some days ago at OMG!, looks great! [10:12] bye! [10:16] okay well i'm going to watch a movie [10:16] anyone have anything they want me to do before i depart for the evening? [12:17] TommyBrunn1 ping: [12:17] hi [12:17] hi daker [12:20] I'm alive again. [12:21] woo! [12:23] Trying to rejoin my time zone. :) [12:23] isn't it like 6 am for you? [12:28] yeah. [12:28] I went to sleep about 10 pm last night. [12:28] was awesome. [12:29] (I'm naturally a night owl. My schedule was so messed up, I was going to sleep around 4 pm and waking up around 2 am. That's not good.) [12:29] I'm trying to reset it so I'm awake a bit more during the day. [12:29] (Though I'm happy to wake up around 10 a.m.) [12:31] I am so tired at the moment fell asleep in a law lecture [12:33] oops. :) [12:33] I'm reading irc backlogs, so I'll be posting responses to ancient questions for a couple minutes. Feel free to ignore me. [12:33] vish: There is no background, it's just white/transparent (#fff). [12:34] vish: You can grab some compiled version of the manual from here, if you like: http://ubuntu-manual.org/builds/ [12:35] thorwil: No, I haven't written back to Charlene yet. I was AFK yesterday. [12:35] humphreybc: poing? [12:35] bens in bed [12:44] okay, I'm caught up now. [12:44] ubuntujenkins: who let him go to sleep?! [12:44] I don't know :P why would he ahve to sleep? [12:45] sleep is a complete waste of time, imo. [12:45] :o [12:46] godbyk: what's the state of the internal layout? [12:46] thorwil: abysmal? [12:46] I'm going to be attacking it today -- just as soon as I'm done switching the test website around to point at wolter's. [12:47] asciidoc? whatever happened to good old-fashioned html? [12:47] godbyk: ok. slowly getting time to at least be sure about the margins [12:47] thorwil: if you have specific complaints or suggestions, feel free to lay 'em on me and I'll add 'em to my list. [12:47] yeah, margins are a big one. [12:48] now that we have the fonts selected (well, for the Latin alphabet, at least), we can get the line-spacing set and figure out a good block size and whatnot. [12:50] pdftex: define anchor at line 82: page.52 [12:51] [52] [12:51] ! Misplaced alignment tab character &. [12:51] l.89 ...uch as ``Office'', ``Games'', or ``Sound & [12:51] thorwil: Error: I am only a bot, please don't think I'm intelligent :) [12:51] manualbot: i know you are stupid an talking to you makes no sense [12:51] thorwil: Error: "i" is not a valid command. [12:51] thorwil: Error: I am only a bot, please don't think I'm intelligent :) [12:51] silly bot did that to me yesterday [12:52] thorwil: put a backslash in front of the ampersand: \& [12:53] Also, if we're using American-style grammar and typography, the commas go inside the closing quotation marks: [12:53] ``Office,'' ``Games,'' or ``Sound \& ... [12:54] godbyk: avoid quotation marks by using italic? [12:54] thorwil: Possibly, depending on the context. [12:55] it may not need to be set off at all, for that matter. [12:59] pushed [12:59] and make is happy now [13:00] good. :) [13:00] the directory structure for wolter's site is weird. [13:01] godbyk: he's using asciidoc to define content and structure? [13:01] yeah. [13:02] I have no idea if I uploaded all the right stuff. [13:02] http://test.ubuntu-manual.org/ [13:02] clicking on pages/ shows the index page [13:02] (it looks like I need to clean my glasses. :-)) [13:02] ARG! [13:03] I'm trying to figure out if I did something wrong or if it's meant to look that way. [13:05] aha! [13:05] it doesn't look that way when I load the local copy. [13:06] I didn't upload the etc dir. [13:06] so the html pages will be an extra dir deeper, even. [13:06] uploading now. [13:08] http://test.ubuntu-manual.org/share/pages/ [13:12] copyright notice is broken [13:13] on the web page? [13:13] yep [13:13] http://test.ubuntu-manual.org/share/pages/downloads.html [13:13] see the footer [13:14] daker: yeah, looks like the image is pushing it all down. [13:14] the background box isn't expanding to encompass the image and footer text. [13:14] oh, well, that's officially Someone Else's Problem (SEP). :) [13:16] some fun (but super ugly) stats: http://ubuntu-manual.org/stats/ [13:17] I'll get a real stats program installed sometime. [13:17] Top 5 traffic sources: [13:17] omgubuntu.co.uk (referral) 763 25.85% [13:17] (direct) ((none)) 648 21.95% [13:17] planet.ubuntu.com (referral) 271 9.18% [13:17] google.com (referral) 225 7.62% [13:17] ubuntizandoelplaneta.com (referral) 131 4.44% [13:18] okay, so back to latex stuff. :) [13:21] godbyk: could you minimize the ......... in the toc? [13:21] as in making the whole thing as narrow as the longest heading permits? [13:21] hey, thorwil: is your cover page in bzr? can I swap that in to the PDFs? (I know it's unfinished.) [13:21] thorwil: you mean the table of contents? [13:21] godbyj: What's the username and password for the statistics area? [13:21] yes [13:22] I'm going to remove the leaders entirely, I think. [13:22] we'll have the numbers appear right after the chapter/section title. [13:22] (i.e., ragged right) [13:22] TommyBrunn1: ooh, good point. sorry. it may not be public. [13:22] I did'nt think about that. oops! [13:23] that's the crappy stats that my hosting company provides. [13:23] when I get a real stats program installed, I'll make it public. [13:23] Alright [13:24] godbyk: just wanted to say that ragged is an option, too. if someone complains we can say Bringhurst does it, too ;) [13:24] TommyBrunn1: When the site was first set up, we had 0 hits. The next day (1 March), we had 122 hits. On 2 March, we had 2830 hits. [13:24] thorwil: Yeah, I prefer ragged. I made it the default in the document class I use in LaTeX. [13:24] * thorwil 's record is something 22000 hits [13:25] thorwil: I mean, it's not like you're trying to add up the page numbers in a column or something! [13:25] thorwil: nice! [13:25] I don't think my site comes close to that. I never write in my blog. [13:25] godbyk: it was an exception, got myself on digg [13:25] cool [13:26] for what? [13:26] godbyk: http://thorwil.wordpress.com/2008/05/09/popup-scrollbar-concept-demo/ [13:26] somewhat outdated, as i tweaked the demo script later on [13:30] thorwil: cool! [13:30] godbyk: line spacing could be larger, but not much [13:31] godbyk, there is an other bugg [13:31] http://test.ubuntu-manual.org/share/pages/ [13:31] the Download button is getting 100% of the content page [13:32] yeah, I noticed that, too. [13:32] ah oki [13:32] daker: Can you file bugs for these? [13:32] Wolter's the one working on the site right now. [13:32] I'm just hosting it. [13:32] where ? [13:33] godbyk: i see " " and “ ” in use on page ix [13:33] daker: The button should be replaced with a prettier one. I set it all up in a previous version, but it seems Wolter broke it, took it out, or something. [13:34] oki [13:34] thorwil: *sigh* yeah, that's lots of little things like that we'll need to fix. [13:34] we should compile a list for when the copyeditors get to it. [13:35] godbyk: you really want to have the preliminary title page pdf in the repo? [13:35] normally, I'd run a sed script through all the .tex files to fix a bunch of that stuff in one go, but that's cause lots of conflicts for people when they go to commit stuff they've been working on. [13:36] thorwil: sure! I like it better than the lynx page (especially how it looks right now). [13:36] godbyk: what path/name? [13:37] thorwil: you can throw it in the titlepage/ dir. [13:37] name it whatever you'd like. [13:37] do you have just the A4 size or a letter size one too? [13:37] just a4 [13:38] k [13:41] titlepage/title_a4.pdf pushed [13:41] I'm famished. I'm going to find something to eat. Will be back soon. [13:41] thorwil: awesome, thanks! [13:42] np [13:48] TommyBrunn1 last time I spoke to you about quickshot you said you were looking into how to take screenshots with python how is that going? [13:49] ubuntujenkins: I haven't worked on Quickshot at all lately, as I haven't been feeling well (still isn't). However, I have found some information regarding taking screenshots. http://faq.pygtk.org/index.py?file=faq23.039.htp&req=edit & http://ubuntuforums.org/showthread.php?p=2681009#post2681009 [13:50] ok thats cool I hope you feel better soon I will have a look at that stuff. thanks [13:53] okay, I'm back. Tasty cereal. [14:21] godbyk: text figures for section header numbers don't do it for me. i think those should capital style figures or however you call them [14:21] thorwil: in the chapter headings, you mean? (the section headings are unnumbered) [14:22] for example the 9 in front of Troubleshooting looks like it doesn't share the same baseline rather than being a text figure [14:22] I was thinking about doing something more fun with the chapter numbers.. make them more prominent.. but I'm waiting to hear back on the chapter icons situation. [14:22] oh right [14:23] do you know what the status is of the chapter icons? [14:23] are they a go or no-go? [14:23] godbyk: still unsure [14:23] fair enough. [14:25] all the section titles are fairly short until you get to the troubleshooting chapter. [14:26] thorwil: godbyk: where are the chapter icons supposed to be placed? [14:26] i see place holders for screenshots , but nothing for icons [14:26] vish: that hasn't been specified yet. [14:26] depends on the icon design and stuff. [14:26] hmm , well , we need to decide on where before the icon design ;) [14:27] one thought I had was to have the icons be large watermarks that are placed in the top right of the chapter opening pages. [14:27] vish: i think Ben once mentioned as watermarks. i think he really likes watermarks. and dropshadows [14:27] vish: Are you doing the icon design? [14:27] ;p [14:27] godbyk: well , anything that thorwil has still left undone ;p [14:27] thorwil: ? [14:27] :) [14:27] he hasnt done the icons :) [14:28] okay. [14:28] so you're it, then, vish! (you lucky guy!) [14:28] ;) [14:28] vish: have you seen thorwil's title page and the line art icons there? [14:28] I was thinking just simple flat icons that we could watermark and put in the top right cover of the chapter opening page. [14:29] they'd only be partially on the page and bleed to the edge. [14:29] then I can superimpose large chapter numbers over them. [14:29] godbyk: yup , i'v modified a bit too , we[ thorwil and i ] have been doing it off the ML [14:29] lemme see if I can do a mockup or something real quick. [14:29] (inkscape hates how many fonts I have installed and takes forever to load.) [14:29] tell me more about that [14:30] thorwil: more about what? [14:30] godbyk: i meant, yeah, here too, stupid inkscape [14:30] thorwil: ah! gotcha. [14:31] it should at least show a splash screen if it's gonna take 5 minutes and let me know what it's doing. [14:31] godbyk: we need not too silly concepts for the icons to make further thinking about them even worthwhile [14:31] if humphreybc ever let's us finish the visual design (instead of waiting on ubuntu/canonical's phantom announcement), we can break up the title page into its graphical and text components and piece it back together again in latex. [14:31] godbyk: what the heck to do for Troubleshooting, for example [14:31] that way the translations happen automatically. [14:32] coffee time, bbl [14:32] thorwil: I hear ya. Hmm.. [14:32] k [14:32] maybe troubleshooting is just the same as the 'help!'-style icons. [14:32] question marks and the like. [14:35] If it's worth anything, I associate "help" with "help me solve this" more than I associate "help" with "walk me through this". [14:36] TommyBrunn1, ubuntujenkins, I should have time to whip up a take-picture-of-window library today and commit it to the tree. Any specific subdirectory in which you want it to be placed? [14:37] the correct one as per python terms I personaly don't mind [14:37] what does this libary do ? [14:38] Just something to take screencaps, since that's what you were talking about earlier. [14:38] Like a module with a couple of public functions. [14:38] fair enough you know what you are on about [15:07] Red_Hamster and kklimonda we have a problem with ssh keys and bzr branches, we were going to use a shortcut and call on the configuration functionality in goundcontrol, but this is currently broken due to launchpad. any thoughs on how we can do it? A major shortcut is to copy the users .ssh folder into the quickshot user. [15:07] kklimonda: ty tu? [15:10] BlessJah: that's why I hate offtopic on the #ubuntu-pl - too many channels too keep track of if people don't stay on topic. [15:11] ubuntujenkins: hmm.. we have to push ssh key to the launchpad so users can pull quickshot and then push changes? what exactly is broken right now? do you have a bug number? [15:12] kklimonda: that's why we've created -offtopic [15:12] we need the user to be able to push stuff into the ubuntu-manaul-screenshots branches [15:12] looking for the bug now [15:13] ubuntujenkins, humphreybc was working on that last night. [15:13] Do you have access to logs? [15:13] I will look them up [15:14] I noticed a potential snag in the strategy he proposed, but it didn't seem too hard to work around. [15:14] kklimonda: make ops to kick for offtop, they'll learn to use -offtopic channel [15:14] I can paste the relevant lines if you need them. [15:14] Via e-mail or something. [15:14] Bug #527978 is what I was refering to kklimonda [15:14] Launchpad bug 527978 in groundcontrol "Launchpad now using openid breaks login" [Critical,Confirmed] https://launchpad.net/bugs/527978 [15:15] My last night, not yours. [15:15] ~10-11 hours ago. [15:16] BlessJah: you should know that it doesn't work like that on #-pl [15:19] ok Red_HamsterX I am now up to date, what was the snag in bens stratergy? [15:21] I'm pretty sure we'd need to share the private key with all committers, which isn't really much of a problem. [15:21] Since we'd be trusting them to commit useful data anyway. [15:21] and storing the password is insecure then [15:21] Not necessarily the password... It could be a throwaway cert or other key. [15:22] If it gets compromised, it could be fixed with a revoke, rollback, and broadcast to all legitimate contributers. [15:23] from a chat nin #launchpad on how to add ssh keys to launchpad " if it's not in the api you'll either have to script a web browser "or do screen-scraping [15:24] can we not assume the user has a launchpad account and ssh key and when the log back into their normal user get them to do the upload? [15:25] Would that be easier or harder than, perhaps, setting up a public Subversion server and just letting them commit data at that, then export its state and commit it to bzr ourselves? [15:28] mmm thats an idea godbyk you deal with server stuff any thoughts ^^^^^? [15:29] ubuntujenkins: for the whole screenshot stuff: [15:29] Setting up public svn is pretty easy, if we've got a server to handle it. I've got two, but I'd prefer to prove my worth before offering to host something like that. [15:29] I think it'd be easier to just have a script on the server and the quickshot program uploads images to the server. [15:29] Just 'cause trusting someone new to do something crucial always worries me. [15:29] skip the bzr repositories and all that mess. [15:29] A script on which server? [15:30] Or something like scp? [15:30] Red_HamsterX: Why not just use a php (python or whatever) script that runs on the ubuntu-manual.org web server? [15:30] quickshot uploads the screenshots via http. [15:30] Also, what about version control, in case someone tries to upload false images over real data? [15:30] Oh, that could work... [15:31] Red_HamsterX: the script could deal with that, I s'pose. But they shouldn't be taking a screenshot if it's already been taken, right? [15:31] POST -> if file exists, copy old file to backup location; save new file? [15:31] Red_HamsterX: exactly. [15:31] Yeah, that would be pretty easy. [15:31] then some moderator could choose the best screenshot to move to our bzr repository. [15:31] we currently have no means of telling which screenshots are taken [15:31] Actually, that's not true, ubuntujenkins. [15:31] ubuntujenkins: well, quickshot can ask ubuntu-manual.org [15:32] If we use a REST-based system like that, it can just query directory contents. [15:32] it can download a small text file/database. [15:32] Kinda like AJAX. [15:32] Red_HamsterX: precisely. [15:32] really wow this is way over my head now I didn't think this was possible [15:32] Quickshot starts, user chooses language/language is inferred, quickshot sends query string, server responds with directory listing. [15:32] so instead of quickshot messing with launchpad, bzr, etc., etc., just use the web server. [15:33] makes more sense can we make the server so that users can't remove images? [15:33] Quickshot takes screenshot -> data is POSTed to server -> filesystem-based database is updated [15:33] Yeah. [15:33] Write-only logic. [15:33] If a duplicate is uploaded, the old one gets moved to somebackup location. [15:33] this saves us a tun of hassel [15:33] Maybe its filename with mtime appended. [15:34] Red_HamsterX: and the server-side script would handle naming the file with a unique name. [15:34] quickshot just submits a form to the server with the screenshot, language, and whatever metadata. [15:34] That makes more sense, actually. [15:35] Always write something like program_name-timestamp.png [15:35] I have a list of language codes that ubuntu its self uses [15:35] and when you start the program, it asks the web server what screenshots are still needed for whatever language. [15:35] And put them in directories based on language code. [15:35] Or prefix all of that with language code. [15:35] Red_HamsterX: or it could just give it a random garbage name and keep the metadata in a database. [15:36] That would also make thumbnail-based filtering a quick process, to avoid having questionable material get past early scrutiny. [15:36] when someone wants to move that png to the bzr repository, the web server can give it an appropriate filename on the fly. [15:36] It'd probably be easiest to just rely on the filesystem and avoid complicating things with a database. [15:36] Unless we need more meta-data than we can store in a filename. [15:36] we need to have a way of creating 'hey, here's a new screenshot we need for the manual' stuff. [15:37] language code chapter number [15:37] all we need in each and maybe order which it occurs in [15:37] ubuntujenkins: nah, we don't need that. [15:37] Or do an scp/rsync from a committer's system and let them run a script that transforms their local copy into bzr-friendly filenames/directories. [15:37] from the latex side, I'd do something like: [15:38] \includegraphics{screenshots/LANG/short-description} [15:38] I am happy to do the commits as quickshot is geting beond me [15:38] and LANG will be filled in automatically so the translators never have to worry about that. [15:38] right sounds good to me what ever works [15:39] basically each screenshot should be independent of every other screenshot. [15:39] Actually, ubuntujenkins, all you'd need to know to work with this system is a simple function like 'commit_screenshot(data)'. [15:39] so no sequence numbers or any of that. [15:39] 'cause we'll end up inserting a new screenshot at the last minute or something and then everything goes out the window. [15:39] You shouldn't need to know anything about the webserver to script the Python stuff. [15:39] from the quickshot end, it'll be just like submitting a web form. [15:39] I can write that function pretty quickly as soon as godbyk creates the submit form, if we go with this. [15:40] I can create the ui if someone tells me what boxes it needs to have [15:40] asuming the ui is in quickshot windows [15:40] shouldn't need any UI. [15:41] well, if we're using quickshot for multiple projects, it'll need to know, say, a project url. [15:41] this does seam the best option [15:41] Nope. The webserver should just be an I/O box. [15:41] where it can download the metadata for the project. [15:41] With more I than O from Quickshot's persoective. [15:41] the metadata would contain the upload script URL [15:41] Data goes in, return code comes out. [15:41] Red_HamsterX's got it. [15:42] cool [15:42] I do web development, Python development, and sysadmin stuff for something approximating a living, godbyk. :) [15:43] nice :-) if we might get this finished [15:44] godbyk does /menu work now? [15:44] in laytex [15:44] ubuntujenkins: \menu works, yeah. [15:45] Thanks [15:47] thorwil, vish: I emailed you guys some examples of what I was thinking for the icons thing. [15:58] godbyk and Red_HamsterX can you please explain your thoughts to huphreybc when he is on next. [15:59] Sure. It's pretty simple from an architectural point of view, though. [15:59] Very easy to diagram. [15:59] And simple means doable. [15:59] cool thats what we like [16:58] godbyk: kinda the wrong side of things for the numbers. icons could work, though i suspect some would be very susceptible to such treatment [16:59] thorwil: fair enough. [16:59] I figured since we reference the chapters by number, the numbers should perhaps be a bit more prominent. [17:00] but I'm definitely open to ideas. [17:00] (I don't know how best to incorporate the icons into the design, I guess.) [17:15] hmm, why is the side wrong? [17:15] vish: side? [17:15] for the numbers [17:15] ? [17:16] * godbyk is confused. [17:16] godbyk: what thorwil said above [17:16] ah [17:16] i dont think it is wrong [17:17] vish: chapter numbers tend to be in the front, not following the title [17:18] thorwil: not necessarily , there are several books which keep the numbers on the right/left margin and the title on top [17:18] vish: Maybe you could mock up a better sketch to illustrate? [17:18] I fear my sketch sucked so bad that it's worthless. [17:19] godbyk: yeah , i was just doing that Now :) but just throwing in random variations ;) thorwil would kick my ass if he sees it ;p [17:58] Wow. quickly is not 2008-netbook-friendly, dependency-wise. [17:59] ...cvs as a dependency? Weird. [18:01] /dev/sda1 3.7G 3.5G 50M 99% / [18:01] Nice. [18:03] ouch [18:05] Hey, vish.. forgot the attachments? [18:05] aw crap! [18:05] :) [18:05] I'm glad I'm not the only one who does that! === ubuntu is now known as danyR [18:07] I can reposition some stuff under /home or on the always-present SD card if I get any lower. But, still, that thing has a lot of dependencies. [18:08] godbyk: hehe , i usually have a word attached in the mail ,and evolution reminds me to attach , this time i forgot even the word attach ;p [18:08] word "attached" [18:21] vish, godbyk: i think the number shouldn't have more weight than the title [18:21] so if it's larger, it should be toned down [18:21] hold on, lemme open the svg. [18:21] (it'll only be 20 minutes before inkscape loads. :)) [18:21] * thorwil opened it in eog [18:22] thorwil: ah , right , the size of the text/number is just there , i didnt know what the actual font size was [18:23] if the number is larger, then yeah, it shouldn't be full black.. it'll be a dark grey. [18:23] thorwil: we can just have the same size or slightly bigger title number [18:23] that way the number and the text appears to be the same color. [18:23] thorwil: Is that what you mean? [18:23] yes [18:23] 'kay. I agree with that bit, then. [18:26] * godbyk finally got it open in inkscape. [18:26] We should probably avoid the rules and background colors for the chapter titles because we can't guarantee they'll fit on one line with all the translations. [18:29] i'm all for keeping it simple, so we won't shoot our own feet [18:29] vish: we will also have to face that canadian guy ;) [18:30] ') [18:30] ^thats me closing one eye ;p [18:31] on irc, most people have no nose!! [18:31] thorwil: safer to keep it tucked that to stick it out ;) [18:31] than* [18:39] thorwil: godbyk: we already draw a line under the title , right? thats why i tried the third variant , and just went on ;p [18:40] my fail. just lost almost a page of ubuntu-manual's first strings translated into pt. === ubuntu is now known as danyR [18:40] :| [18:43] vish: there aren't any lines being drawn anywhere yet, I don't think. [18:46] godbyk: oh.. i think i got it mixed with the other pdf you sent [18:46] ah, gotcha. [18:51] Okay, I'm gonna head to a friend's house to hang out for a few hours. [18:51] I'll holler when I return. [19:06] did I miss anything important? [19:07] Maybe. [19:08] We've got a new plan for automatically collecting screenshots from Quickshot clients. [19:09] It only affects the transfer process, though. [19:12] * dutchie is not as involved in QS as he should be [19:15] I just got here yesterday. [19:16] I've been here a while :) [20:15] godbyk: https://wiki.ubuntu.com/Brand [20:15] * dutchie suspects this may annoy godbyk somewhat [20:20] From earth to light? Quite a shift. [20:25] Hi [20:34] Hi. [20:44] Red_HamsterX: Hi [21:40] Hello! Just sign up to give you hand. I can help with the editing. If someone could give some direction as to what needs to be done, that would be great!! Thanks! [21:41] jaminday: ^^ [21:43] dutchie: How's the manual coming along? [21:56] I'm back now. [22:03] evening all [22:05] sebsebseb: well-ish I think [22:05] lots still to do though [22:18] dutchie: do you know if vish and thorwil saw the new brand stuff? [22:18] er, thorwil did, I see. :) [22:19] looks soo good can't wait to see it tomorrow [22:21] godbyk: no idea [22:21] looks cool though :) [22:21] dutchie: is there a way I tell po4a or whatever to just not even add it to the list of things to be translated? [22:21] dutchie: ok [22:22] The PyGTK reference TommyBrunn linked to works fine, with a few minor catches. I'll start functionizing and optimizing it now. [22:22] godbyk: possibly [22:22] (For the actual screencapping) [22:22] not something I'm going to start looking into at 22:22 though [22:22] I've started adding "% TRANSLATORS: leave this line alone!" to a few things [22:22] where they keep translating, say, \coverpage or \tableofcontents. [22:22] sounds good Red_HamsterX [22:22] dutchie: fair enough! :) [22:22] You mean they're translating the LaTeX functions? [22:23] which branch is it going in? [22:23] Red_HamsterX: Occasionally, yeah. [22:23] ubuntujenkins, I'm not sure how the branches are currently set up. My experience has, unfortunately, been with centralized VCSes. (Subversion, CVS) [22:24] I need to break the highlight habit. [22:24] This is a slow channel. [22:25] I suggest it goes into main https://code.launchpad.net/~quickshotdevs/quickshot/quickshot don't worry about highlighting it draws my attention [22:25] I was just going to merge things into the main branch, when stable, since I'm adding new modules, rather than reworking existing ones. [22:26] I don't actually mind I am going to netten my stuff up when we finish the timer bit for it [22:26] My typical approach is to always commit to main, unless working on something experimental or possibly damaging stable code. [22:26] (From an SVN standpoint) [22:27] fair enough my branch was only made when I started tinkering and as I don't knwo much python I didn't want to mess up main [22:29] Red_HamsterX: tbh, we don't really use it in a very DVCS way [22:31] dutchie, that suits me just fine. :) [22:50] Well, it looks like the new Ubuntu font isn't ready for use yet. [22:50] According to popey: "The new logo at the top of this article has a new typeface called ‘Ubuntu’ and whilst it’s nowhere near finished (last count I think they had about 15 characters done) it will eventually replace the old Ubuntu Title font." [22:51] thats usefull what letters are there? [22:51] He continues: "Canonical are looking to get community involvement in helping develop this font – which looks like it will become the default at some point. Clearly the first characters to be done were “ubnt” for Ubuntu and “CANOIL” for the Canonical logo – which borrows a person from the Ubuntu circle of friends and sticks her in the “O”." [22:51] :) [22:51] Hey, popey's here! :-) [22:51] hullo [22:52] popey: Is there a dev project for the font? [22:52] there's a guy working on it [22:52] heh.. I take it that's a 'no'? :) [22:52] i believe they are going to get people in to help [22:52] given there's a lot of characters yet to do [22:53] gotcha