[04:28] Fresh builds are up at http://builds.ubuntu-manual.org/. [05:11] http://twitpic.com/1w0ni3/full [05:16] nice [05:16] maybe offer some common destinations, too. (in addition to your search box note) [05:17] I was going to, but then I realised there are big fat links up above, and below [05:17] I'll keep thinking about it [05:17] yeah, I considered that, too. [05:18] ideally, I'd like it to analyze the url you're trying to get to and figure out where you're trying to go and link you there. [05:18] (easier said than done.) [05:18] haha === \vish is now known as vish [09:05] morning [09:09] morning! [09:09] hey thorwil o/ [09:11] hmm, i will have only a few minutes at the start of today's meeting [09:13] I will be busy revising and not pay loads of attention [10:33] c7p: how is the release of your translation going? [10:35] ubuntujenkins: godbyk is working on the tex files, checking that everything is fine in there. In the same time he is making a list of everything that needs to be done before the release of a translated edition. [10:36] I'm waiting today's meeting to learn the actual date :) [10:37] yea i have the link to the list of stuff. I am hoping to give godbyk a hand with some of the next ones as I think we will have 4 at once soon [10:38] ubuntujenkins: are you working going to work on this link: http://typewith.me/rE4pCABOXs or another ? [10:40] I do have that link I am going to try and speak with godby-k about what needs doing etc. [10:41] ok if you need another hand I can always help ;) [10:41] cool I will let you know [10:41] nice [11:30] is there a server edition of the manual being worked on? [11:30] no there is not I am afraid [11:31] dns53: this might be of interest https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/497834 [11:31] Launchpad bug 497834 in ubuntu-docs "Ubuntu Server Guide isn't aesthetically appealing." [Wishlist,Confirmed] [11:31] also the current server guide is https://help.ubuntu.com/10.04/serverguide/C/index.html [11:34] thx [11:35] no problem :) === ubuntujenkins_ is now known as ubuntujenkins [16:01] godbyk / godbyk-sagan ping [18:26] ubuntujenkins: I just got back home. Let me fix something for lunch and then I'll be right with you. [18:27] godbyk-sagan: cool no rush [18:29] godbyk-sagan: btw, you going down in RSA [18:29] :P [18:29] ras? [18:29] Republic of South Africa ;) [18:29] o yea your going down godbyk-sagan :P [18:30] \join #england [18:38] Uh-oh, what'd I do to the South Africans now? [18:38] usa vs england in the world cup [18:38] Aha [18:39] So you're talking about soccer? [18:39] no, real football [18:39] where you actually use your foot [18:39] no we are talking about football :P [18:40] they are talking about watching silly people run around a grass field kicking a ball around =P [18:47] godbyk I would like to discuss the process that the manual goes through after the translations are complete and what i can do to help. [18:48] when you have finished eating :) [19:29] Hey, ubuntujenkins. I'm back now. [19:31] hey godbyk [19:32] So I don't have a formal checklist yet. It's something that c7p and I have been taking notes on as we go along. [19:32] But we should create an actual checklist so we don't forget things. [19:32] cool I have the check list book marked. [19:33] is \ldots with a lower case l or i becasue in launchpad they look the same [19:33] l for line [19:33] It's a lowercase L. [19:33] thats what i thought allot of people are putting i [19:33] Yeah, they're wrong. :) [19:34] right [19:34] i'm watching the football [19:34] hmm the pad link i have does not work [19:34] bye [19:34] bye dutchie [19:34] See ya, dutchie. [19:34] 1-0 england \o/ [19:34] within 4 mins [19:34] ubuntujenkins: Let me find my link to it again. [19:35] also the first {} in \newglossaryentry is often translated [19:35] Yeah, it shouldn't be. [19:35] Nor should the \gls and \glspl commands be translated. [19:36] I think those are the most commom mistakes that are not on the list already [19:36] Nor should the \label, \ref, pageref, \chaplink, \seclink, etc. commands be translated. [19:36] can we add it to the pad? [19:36] Sure, if you like. [19:36] Do you have the pad link? [19:37] I do but it doesn't work [19:37] http://www.typewith.me/rE4pCABOXs [19:38] acording to http://downorisitjustme.com/ the site is down [19:38] nice. [19:38] I thought I had one on Etherpad, but perhaps not. [19:39] do you have a local copy? [19:39] Nope. [19:39] Let's just create a new one. [19:39] We can update it with typewith.me comes back online. [19:40] yea cool , so apart from that list what else gets done. [19:40] http://pad.ubuntu-uk.org/translationtodo [19:53] that list looks good [19:53] That covers a lot of it. [19:53] I'm sure I'll add more things as I encounter them. [19:54] It'd be nice if we have a web page where the translator editors could go to see where they're at on the checklist or something. [19:54] So we can see how far along things are. [19:54] good idea we need to respond to surst's e-mail about the german on [19:56] I'll email him right now. [19:56] cool, I am just looking for stuff I don't know how to do in latex [19:57] how do you change the paper size? [19:57] I will be back in 5 to 10 mins [19:57] ubuntujenkins: the paper size gets changed automatically based on the language. [19:58] (if it doesn't, then I need to edit the .cls file to set it properly.) [20:02] Okay, email sent. [20:07] cool as far as the small caps formating where would that be changed? [20:08] Well, it depends. [20:08] So with the German translation, for instance, he wanted the running heads to be different. [20:09] With other translations, we have to use fonts that don't have small-caps. [20:09] So it depends on the situation. [20:09] running heads being .... [20:09] to ask a silly question :) [20:09] Running heads are the bits at the top of the page with the page number and the book title and chapter title. [20:09] Nope, it's not a silly question at all. I'm guessing the vast majority of the people in the world have absolutely no idea what a running head is. :) [20:09] ok cool [20:10] whilst i don't forget shrini asked me to ask you about the japanise caracters on the side of evince they should be tamil [20:11] Uh... [20:11] No clue on that one. [20:11] I had no clue where to look at all [20:11] o we will have to look into it [20:11] I'll have to ask him when I see him next. [20:12] I'm not sure where Japanese characters would be coming from. [20:12] if you look at it its really obvious that they are not tamil [20:12] So previously, I was building 2 PDFs at a time when I built all the translations. [20:12] When my new computer I'm doing 8 at a time. It's a lot faster. :) [20:12] eight what are your specs? [20:13] way more people have an idea of a running nose than of a running head [20:13] Where am I looking for the Japanese characters, ubuntujenkins? [20:13] thorwil: I bet! [20:14] thorwil: It looks like we may have to whip up a Tamil title page soon. [20:14] godbyk: on the index pain of evince [20:14] thorwil: After I find a font that isn't horrible. [20:14] (Not many Tamil fonts out there, it seems.) [20:15] I just grabbed the Tamil PDF from the builds page. And the index pane on mine (which shows the chapters, etc.) has Tamil and English text there. [20:15] godbyk: oh, Tamil has been very low of my list based on a snapshot of translations status way back [20:15] thorwil: I know. They spiked up this past week. A lot! [20:16] ok then its an issue with ones built on my computer, the tamil text works but not the index appantly [20:16] They're in 7th place right now. [20:16] ubuntujenkins: Oh, that could be. I'm not building the index right now. [20:17] godbyk: I need to redo the index rules they work but they way I did it is not 100% the correct way. I need to get my exam on tuesday out the way first [20:17] No worries. [20:18] We should write up instructions for ourselves on how to do the indexing, too. [20:18] We'll also need to take a look at hyphenation patterns. [20:18] they are really easy once you know how. I will do instructions. A lot depends on the language. [20:18] hyphenation patterns in what sense? [20:18] If they're not in LaTeX already, I think we can steal them from OpenOffice.org. [20:19] Hyphenation patterns tell LaTeX where it's okay to break a word at the end of the line (hyphenate it). [20:19] http://ubuntuone.com/p/6kf/ is tamil built on my computer . [20:19] Without being able to hyphenate words, the spacing isn't nearly as good (lines run too long or too short). [20:19] ok that make sense [20:20] ubuntujenkins: weird. yeah, something barfed there. we'll have to look into it. [20:20] once i get the index correct then we know its not that [20:20] right [20:20] also there is a two page gap before the index [20:21] Yeah, I recall having to fix that manually with the English edition, too. [20:21] Let's add that to the checklist. [20:21] godbyk: regarding hyphenation, seen http://code.google.com/p/hyphenator/ ? [20:22] thorwil: Cool! [20:22] I think browsers should have built-in hyphenation (and CSS should support H&J rules) [20:23] godbyk: that's what i have been thinking, too. but what can you expect from people who think it's alright to draw underlines right through descenders? ;) [20:24] godbyk: seeing how adding lots of ­ the hard way is not practical at all, this script is the best available solution [20:25] I s'pose. It just seems like they're coming at it from the wrong direction. [20:25] Hyphenation shouldn't be some post-hoc decoration, y'know? [20:29] no doubt browsers doing it themselves would beat this [20:29] but it is a relief to see this in action. text on the web starts to suck less quite a bit :) [20:29] Hey, thorwil, you have a nice, large collection of typefaces, right? [20:29] Definitely. [20:30] ok thanks godbyk I think i can help translators with most of the list [20:30] godbyk: not here on my lucid install [20:30] ubuntujenkins: cool. If there are things you can't help with let me know and I'll try to teach you. [20:30] It's always best if multiple people know how something works. [20:30] thorwil: Ah, bummer. I wrote a script that scans the fonts on your system and lists all of the fonts that support a particular script. [20:30] Was hoping you had a nice Tamil font that I didn't have. [20:31] I'm not terribly thrilled with the one we're using right now. [20:31] godbyk: I would like to learn as well :) . with item 10 where do the translated items go in the .tex file? [20:31] I find tamil looks better if you increase the font size [20:31] ubuntujenkins: They go in the um-LANGUAGE.clo file. [20:31] godbyk: if the "on your system" can be stretched a bit, i could check the font dir on my other partition [20:31] I have to in gedit when working with it for the index [20:31] (I need to update the um-template.clo file to be more comprehensive.) [20:31] thanks godbyk [20:32] thorwil: Sure. You just edit the file and change the list of paths it searches. [20:32] thorwil: I'll email it to you. [20:33] I ment to send a meeting reminder to the list and sent it to ben! [20:34] lol [20:34] he probably needs one, too! :) [20:35] godbyk the list that we are working on is http://pad.ubuntu-uk.org/translationtodo ? [20:35] c7p: At the moment. Your site was down, so we started recreating the list. [20:35] I wondered why the mail wasn't on the list sent it now [20:37] who is chairing the meeting ? [20:37] ben i guess [20:37] If he shows up. :) [20:37] :) [20:39] * ubuntujenkins learns more about three phase generators [20:52] team: do we have any meeting now? [20:52] in 8 mins shrini [20:52] ubuntujenkins: thanks [20:52] oh no [20:52] can we delay it half an hour or so? [20:52] what dutchie ? [20:53] the football is not that important [20:53] i can't watch the match and do a meeting at the same time [20:53] ubuntujenkins: USA equalised :( [20:53] nearly took the lead just then [20:53] put it on head phones I am listening as i have no tv licence [20:53] raido 5 :) [20:54] probably better than the ITV coverage [20:54] their HD channel went to adverts for the first goal [20:54] what that sucks [20:54] Look, you know we're going to win, so you probably don't really want to watch anyway. [20:55] you stick to playing sports that nobody else bothers with [20:55] lol [20:55] You couldn't handle real football. :) [20:55] i have actually played american football [20:56] so :P [20:56] yes we could a real footbal os round [20:56] *is [20:56] dutchie: Just once, eh? I rest my case. [20:56] godbyk: i have played it many times actually [20:56] i am actually not bad [20:57] (by the standards of my friends) [20:57] I pretty much suck at all sports. So I don't pay any attention to them. [20:57] I have only really palyed rugby which is much better as there is no padding [20:57] not a massive fan of playing rugby [20:58] I don't play it much [20:58] aren't you obligated to play sport at loughborough anyway? ;) [20:58] no, only if you do a course that is sport [20:59] loughbrough is good at engineering as well [21:00] * dutchie wonders what godbyk's attempt at pronouncing "loughborough" is like [21:00] minutes for people to read whilst we wait https://wiki.ubuntu.com/ubuntu-manual/Meetings [21:01] I ment agenda [21:01] I saw your previous discussions on the 'proper' pronunciation. [21:01] Hi. [21:01] greetings [21:01] Hey, guys. [21:01] * flan needs to stop getting distracted. [21:01] hi [21:02] godbyk: bet you can't pronounce my city [21:02] hello everyone [21:02] hmm no ben yet [21:02] Well, shall we get started or wait for more stragglers? [21:02] I'm gonna start beinging my Eee with me on the train. [21:03] godbyk: Are we missing anyone you'r expecting (besides benjamin)? [21:04] godbyk: i'm about to disappear, actually [21:04] semioticrobotic: also ilya [21:04] I'm not sure if Ilya was planning to be here or not. [21:04] We'll get started then. [21:04] ubuntujenkins: Ah! Yes, of course. [21:04] I may go through the agenda in a different order in case Ilya or Ben pops in late. [21:04] yea we should get started [21:05] good plan [21:05] Okay, so first up, let's talk about the Lucid first edition translations. [21:05] don't for get the meeting bot [21:05] As you can see from here: https://translations.launchpad.net/ubuntu-manual [21:05] a number of translations have been completed. [21:05] Many of them are currently in the editing/proofreading phase. [21:06] I think the German and Greek translations have progressed just beyond that. [21:06] godbyk: not going to do a #startmeeting? [21:06] well done to the translators [21:06] #startmeeting [21:06] Meeting started at 15:06. The chair is godbyk. [21:06] Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE] [21:06] just for dutchie [21:06] \o/ [21:06] agreed. well done translation teams! [21:06] [TOPIC] Lucid first-edition translations [21:06] New Topic: Lucid first-edition translations [21:07] So with the help of c7p and ubuntujenkins, we have a rough check-list of items that need to be completed for each translation: http://pad.ubuntu-uk.org/translationtodo [21:07] We will probably continue adding to this as we encounter new issues. [21:08] Each translation team has an assigned translation editor: http://wiki.ubuntu.com/ubuntu-manual/TranslationEditors [21:08] The translation editor is in charge of communicating with the rest of the Ubuntu Manual team to ensure that each of the steps on that checklist is completed [21:08] godbyk: maybe mention the lulu cover, too? [21:09] and will have the final say on when we publish that translation. [21:09] thorwil: Good idea. Add that in there someplace. [21:09] gotcha [21:09] can people add irc nicks in another column to https://wiki.ubuntu.com/ubuntu-manual/TranslationEditors [21:09] ubuntujenkins: sure. [21:09] Hello All, Sorry I am late. [21:09] Does anyone have any questions about the general process for releasing the first edition translations? [21:10] Hey, ChrisWoollard. No worries. We're just getting started. [21:10] :) [21:10] Okay, if there's nothing else to add, we'll move on to the next topic. [21:11] [TOPIC] Lucid second edition release schedule [21:11] New Topic: Lucid second edition release schedule [21:11] Currently, the release date for the second edition of the Lucid manual is 29 July. [21:11] (5 days after my birthday \o/) [21:11] aha [21:11] We don't have any particular alpha/beta/etc. release dates scheduled, but we can add them in if we feel the need. [21:12] ok [21:12] hi [21:12] The second edition will contain all the bug fixes and last minute material that we didn't have time to clean up for the first edition. [21:12] Hey, humphreybc-mini. [21:12] hi humphreybc-mini [21:12] I think we've fixed a pretty large number of bugs in the second edition already. [21:12] But we should continue doing read-throughs to find more bugs. [21:13] It sure seems like it [21:13] The second edition will be the manual that hangs around with the LTS release, so it may be used for some years yet. [21:13] humphreybc-mini: has the winner of the competion be told that they won? [21:13] good point [21:13] bug comp^ [21:13] ubuntujenkins: Well, I have to actually figure out who won [21:13] I've only had one person tell me they have done 10 buigs [21:13] bugs* [21:13] Just out of interest. Are specifica people responsible for checking different chapters or anything like that [21:13] Are they supposed to notify you, or do they expect you to tally up the results? [21:14] I think about 3-4 people at a guess i have not actually looked . [21:14] hi [21:14] godbyk: I didn' [21:14] hey daker [21:14] ChrisWoollard: Nope. It's a free-for-all. [21:14] I didnt say, but I expect the latter [21:14] There was one guy that logged a good hundred bugs [21:14] I need to tally em up [21:14] Is there an end date to the competition? [21:14] nope [21:15] oh [21:15] well [21:15] 2nd edition release I guess [21:15] humphreybc-mini: We should set an end date so we have time to get the contributor names in the second edition of the manual. [21:15] true [21:15] I'll get onto all that at the end of next week [21:15] Okay. [21:15] Any other questions about the release of the second edition? [21:15] I think this guy logged a lot of bugs [21:15] what about the bug tracking of the translated edition? [21:15] https://edge.launchpad.net/~marc.stewart [21:16] when is it? or did i miss that? [21:16] I have a quick question [21:16] found it 29th july [21:16] ubuntujenkins: The second edition will be released 29 July. [21:16] (5 days after my birthday \o/) [21:16] semioticrobotic: ask away [21:17] Could someone clarify the syntax for linking specific fixed bugs in bzr commit anotations? [21:17] I see people have been doing that; it's very cool, and I want to do it [21:17] bzr commit --fixes lp: [21:17] does that automatically mark the bug as fixed? [21:17] don't think so [21:17] * humphreybc-mini confesses that he hasn't looked at the branch in two months [21:18] ok [21:18] i think it will do if the branch ends up in the main line [21:18] semioticrobotic: Running 'bzr help bugs' will show you some examples, too. [21:18] so after committing and pushing, manually mark the bug [21:18] thanks, godbyk [21:18] semioticrobotic: Yeah, that's what I've been doing: fix, push, mark the bug manually. [21:18] I thought the procedure was to mark the bug as fix commited until the release. [21:19] ChrisWoollard: It is. [21:19] :) [21:19] ... but I didn't know if that had to happen manually [21:19] Once the bug has been fixed and commit, mark it as 'Fix Committed' [21:19] yes [21:19] gotcha [21:19] thanks for the clarification [21:19] 'Fix released' will be what we set those bugs to after the final PDF and book have been released. [21:19] ok [21:19] Which basically means it's in the branch, ready for a release [21:19] Right. [21:20] Okay, any other questions about the second edition release? [21:20] question: What about the bug tracking of the translated editions? The http://bugs.ubuntu-manual.org/ isn't working. [21:20] Of course, since this is a book, our releases aren't super defined because we're always releasing things... it's really a rolling release [21:20] c7p: You can file them in Launchpad, if you like. [21:20] c7p: tell me asap about bugs.u-m.o outages [21:20] i'll sort in a moment [21:20] c7p: Yeah, Launchpad is the best until we get the new site design up with new bug form [21:20] c7p: Also, you can pester dutchie about the bugs page. [21:21] Any other questions? [21:21] are we winning? [21:21] Okay, since humphreybc-mini's here, we'll move on to some of his agenda items. [21:21] [TOPIC] Ubuntu Manual Project Philosophy [21:21] New Topic: Ubuntu Manual Project Philosophy [21:21] ah [21:21] yes [21:21] I have been working on this [21:21] sort of [21:22] So basically, here's more or less the near final version of this thing [21:22] http://pad.ubuntu-uk.org/axMP6X6TIq [21:22] LINK received: http://pad.ubuntu-uk.org/axMP6X6TIq [21:23] how embarrassing [21:23] (the football) [21:23] lol [21:23] Why [21:23] 1-1 draw [21:23] which game [21:24] england v usa [21:24] shocking game [21:24] haha [21:24] Oh dear [21:24] I should know that [21:24] dutchie: We'll take that as a win, then. [21:24] * ChrisWoollard pretends he cares [21:24] haha :P [21:24] That is tragic [21:24] godbyk: your lack of understanding of the game is obvious [21:24] Hilarious [21:24] but tragic [21:24] straneg [21:25] humphreybc-mini: Do we have anything we need to discuss about the mission statement / philosophy, or are we just reading through it? [21:25] i don't see NZ at the world cup [21:25] godbyk Just reading through. If you have any suggestions, make some comments on the pad [21:25] dutchie: Amusingly, despite our obvious lack of understand, we've managed to keep you at bay. Oh, superiority! [21:25] Okay. [21:26] let's get through the meeting, then godbyk can gloat [21:26] yep [21:26] Does anyone have any questions, comments, suggestions, criticisms, etc. about the philosophy/mission statement stuff? (It'll take a bit of time to read through, so you can pester us on the list or in here later if you like.) [21:26] Stephen Fry didn't predict a draw: http://twitter.com/stephenfry/status/15995140379 [21:26] Okay, moving along then. :) [21:27] [TOPIC] Ubuntu Support and Learning Center [21:27] New Topic: Ubuntu Support and Learning Center [21:27] humphreybc-mini: Do you want to take this topic, too? [21:27] ah [21:27] well [21:27] this is fairly broad [21:27] https://wiki.ubuntu.com/ubuntu-support-and-learning-center [21:27] What should we write it in? Python? Okay, settled. [21:28] just finished reading, humphreybc-mini. it's come a long way! I like the new mission statement [21:28] I'm not sure that humphreybc-mini knows enough Python yet. :-P [21:28] lol [21:28] well, if it's an online jobbie, it'll end up being HTML/Javascript... [21:28] I was looking at things like Zope [21:28] Doesn't change the fact that Python's the best language in use today. [21:28] * ubuntujenkins is not sure he knows enough python either [21:28] dutchie: Looks like your bug report got filed okay. [21:28] I think the majority of the thing should be python [21:28] godbyk: from the bugs page? [21:28] dutchie: yeah. [21:29] Launchpad uses python, everyone uses python [21:29] what to do with python for support center? [21:29] humphreybc-mini: I think we need to establish another meeting with the docs team and learning team to get some details out of the way. [21:29] It seems to offer the most flexibility when it comes to doing stuff like this, I was talking to thump er about it a couple of weeks ago [21:29] I am new to this concept [21:29] godbyk, yeah [21:30] but we need to make some decisions soon [21:30] Is everyone here familiar with this Ubuntu Support and Learning Center concept that we've started working on? [21:30] humphreybc-mini, could you perhaps summarize the current state of our collaboration wth those teams? [21:30] That would be good [21:30] coz after my exams I'm going to market it like crazy to get some developers... and we need to know who we're trying to entice :)O [21:30] semioticrobotic: Well, the learning team love us, the docs team love us except for Matthew East. [21:31] am i correct in thinking that we have not had the colaberation meeting yet or did i miss it? [21:31] He hates us :) [21:31] why [21:31] And I need to be smacked on weekdays so I'll actually focus on Quickshot so I can hel you get started on USLC. [21:31] hahaa [21:31] if you need some python code, count me in [21:31] I think it was called off coz no one showed up from their side [21:31] So the short version is that we'd like to merge our work with the work of the doc team and learning team so that we're sharing a huge pool of documentation. Any team can pull docs from the pool and organize them however they'd like. [21:31] ubuntujenkins, it was canceled but is being rescheduled [21:31] * flan is strangely unmotivated right now. [21:31] So we can pull our docs from the pool to create PDFs and online manuals. [21:31] semioticrobotic: thats what i thought [21:31] The learning team can produce handouts, textbooks, lesson plans, etc. [21:31] flan: i am starting on quickshot this tueday after my exam [21:32] have we got around to working out how all this will work yet? [21:32] We're going to integrate translations and editing via the website. [21:32] great [21:32] That'll probably help, ubuntujenkins. [21:32] The original plan was to get the infrastructure in place using our content as a proof of concept first [21:32] You won't have to use LaTeX directly anymore as we'll have a web-based editor. [21:32] There is also the developer manual. Were we going to have anything to do with that as well? [21:32] okay [21:32] so I remember humphreybc-mini's clusterfl0ck of a flow chart [21:32] ChrisWoollard: We're working with that team a bit, too. [21:32] ChrisWoollard: Sort of. Rick and Didier and a couple of other guys are making that, we're just offering advice and letting them use our channel [21:33] how exactly does that translate into concrete work on the ground? Which groups will be responsible for what kinds of production/action? [21:33] flan: cool, I will need some help with understanding some stuff you wrote [21:33] So, pretty much if they ask for help..... then maybe [21:33] ChrisWoollard: oh no, sure we'll help them [21:33] :) [21:33] Mainly with technical stuff though [21:34] The idea is that they get the projects to write their own code, or grab shit from existing project help [21:34] own code/text [21:34] Our next steps are to reschedule the collaboration meeting when folks from the other two teams can attend so we can hash out a few technical details. [21:34] Then we'll be busy designing and coding. [21:35] But for the Maverick release, along with the usual PDF and printed manuals, we'll have an online version of the manual. [21:35] yarp [21:35] ok [21:35] the online version will be our text in USLC as a proof of concept [21:35] With the online version of the manual, people can report bugs right from the page as they're reading the manual. [21:35] They'll be able to link directly to a paragraph or section of the manual (handy for providing pointers in emails, forums, and IRC channels). [21:35] godbyk: we better get started on the site we need more coders [21:35] ubuntujenkins: Agreed. [21:36] But the whole awesome edited backend, paragraph at a time, suggestion based moderated wiki and online editor magical content pool etc might not be in place till next year ;) [21:36] and the giant content pool will be ... a repository? a code branch? [21:36] semioticrobotic: A bit of a hybrid. [21:36] semioticrobotic: Not sure [21:36] ok [21:36] just trying to envision it all :) [21:36] How will the translation of that online manual stuff be done? Through launchpad ? [21:36] semioticrobotic: Right now, we're thinking it'll be stored in a database with regular (nightly? hourly?) exports to a bzr branch. [21:36] ok [21:36] semioticrobotic: We're pushing off any bzr import stuff until much, much later, though. [21:37] godbyk, ahh, that would work [21:37] so contributing won't even require knowledge of bzr, launchpad, or anything like that [21:37] ok [21:37] c7p: We'll probably have our own translation system if Launchpad's doesn't improve sufficiently. [21:37] semioticrobotic: correct [21:37] it will be awesome [21:37] ok [21:37] everything's starting to come together for me now [21:37] So as you can see, we're fairly ambitious and have a lot of work ahead of us. [21:37] yes, I can see that! [21:37] ok it sound pretty good, I'm looking forward to it [21:37] yar [21:37] godbyk: that makes a change [21:37] It will take a lot of effort [21:38] We're going to try to meet with the other teams in the next week or two to work out a few of the underlying technical details and then we'll start designing and coding. [21:38] dutchie: What makes a change? [21:38] godbyk, a lot of work :) [21:38] So if we can get some more details hammered out in the next couple of weeks, I'll start working on the specification and marketing for it so we can get some people to help us [21:38] You've all probably seen some traffic on the Ubuntu Manual mailing list a few weeks ago about this. You'll probably see some more traffic soon. [21:38] okay, sounds goos [21:38] good* [21:39] we're going to need lots of help :) [21:39] Okay, any other questions, comments, etc. on this topic? [21:39] What lanaguages were we talking about again? [21:39] I missed that bit. I think. [21:40] for the development [21:40] python (django) or PHP [21:40] ChrisWoollard: We haven't pinned that down yet. [21:40] django \o/ [21:40] all of the cool languages [21:40] Shame I don't know Python. [21:40] But i know Perl [21:40] you'd better learn quick :P [21:40] that is cool :P [21:40] I've kinda been sold on Pylons. It didn't take much effort to set up and it seems quite scalable and flexible. [21:41] [TOPIC] Research on manual usability [21:41] New Topic: Research on manual usability [21:41] https://lists.launchpad.net/ubuntu-manual/msg01941.html [21:41] yeah ... when it comes to programming languages, I'm of no help. But when you're generating content ... well, THAT I can edit [21:41] So Ilya's worked up a plan for running some studies on how people use our manual and what problems they encounter. [21:41] he's not here though, bummer [21:42] If you have any feedback or questions about his study designs, you can respond to the thread on the mailing list. [21:42] I think it is really good :) [21:42] the information will certainly be useful, that's for sure [21:43] I agree. [21:43] Okay, next up: [21:43] [TOPIC] Cleaning up the instructions on the website [21:43] New Topic: Cleaning up the instructions on the website [21:43] godbyk: I have submitted one but I am still waiting an answer [21:43] plus, it'll be cool to say I was involved in something that required a Kickstarter campaign :) [21:43] Some of the instructions on our website are a bit short. [21:43] and others are way too long [21:43] the latex ppa should go on [21:43] For example, http://ubuntu-manual.org/getinvolved/editors stops just short of explaining how to edit the .tex files, commit them back, etc. [21:43] i think so [21:43] I was thinking we could fix these up for the site redesign [21:44] the ppa is useful [21:44] ubuntujenkins: Absolutely. If the PPA is working, then that will simplify the TeX stuff, I think. [21:44] What do you guys think about having help overlays pop up more often on our site, like on launchpad? [21:44] humphreybc-mini: Can you give me an example of where that would be useful? [21:44] * humphreybc-mini thinks [21:45] Well I'm just trying to figure out whether the approach we have now (giving instructions based on roles) is the best [21:45] * godbyk takes that as a 'nope'. [21:45] :) [21:45] godbyk: It works and i can update it now i know how to make the packages my self [21:45] I think it is [21:45] but [21:45] ubuntujenkins: awesome. [21:45] still open to other options [21:45] I want to make the instructions as coooooooooooooool as possible [21:46] So we need to update the instructions to ensure they're still accurate and reflect our current development efforts (make sure people are using the right branch, etc.). [21:46] (also, helpful) [21:46] that cool, huh? [21:46] We need to extend the instructions to include how to edit files, provide a link to the style guide, and so forth. [21:46] simplicity [21:46] godbyk, for example, where we tell people to set up an SSH key for Launchpad. We could just have that stuff in an overlay [21:46] Would anyone like to volunteer to work on the instructions? [21:47] Well I think I was going to do some [21:47] You won't have to do all of them yourself. If you only know the translation side, that's great. Ditto for authors/editors. [21:47] godbyk: I think I can help with the instructions [21:47] humphreybc-mini: Okay. [21:47] c7p: Great! [21:47] I'll let c7p and humphreybc-mini work together on the instructions then. [21:48] yarp [21:48] sounds groovy [21:48] You guys should be able to cover all the bases there, I think. [21:48] Last item on the agenda: [21:48] [TOPIC] Goals for Maverick [21:48] New Topic: Goals for Maverick [21:48] humphreybc-mini: Do you want to field this topic, too? [21:48] ah [21:48] okay [21:48] well [21:49] Major things are of course, new edition of the manual, quickstart booklet(s), first release of USLC and a new look for the team [21:49] Let's take those one at a time, then. [21:49] What did USLC stand for? [21:49] [TOPIC] Maverick edition of the manual [21:49] New Topic: Maverick edition of the manual [21:50] ChrisWoollard: USLC: Ubuntu Support and Learning Center. [21:50] is it possible to have different layout? [21:50] ChrisWoollard: (the new website we were talking about before) [21:50] for the book? [21:50] ?mppa > humphreybc-mini [21:50] so ... will the Maverick edition be comprised of material from the giant content pool? [21:50] ubuntujenkins: Error: "mppa" is not a valid command. [21:50] humphreybc-mini, please see my private message [21:50] shrini: Possibly. What're you thinking? [21:50] Godbyk: Thanks. I just didn't link it to the learning centre [21:50] godbyk: the paper a4 is not good for a book to read [21:51] shrini: True, but it's good for printing the book yourself. [21:51] check out other normal books [21:51] godbyk: you are right [21:51] :-) [21:51] ok. agree [21:51] So we're kind of compromising a bit there. [21:51] Normally the problem with larger format books is that the lines are too long and the book is too heavy. [21:51] thats fine [21:52] In our case, the lines are shorter since we leave plenty of room for sidenotes, and the book isn't too heavy as we're too lazy to write so much material. [21:52] (Okay, the real reason is because we're trying to keep it fairly short.) [21:52] :-) [21:52] so maverick will get a lot of stuff cut out [21:52] shrini: But we can look into different paper formats down the road. Remind me again in a couple months! :) [21:52] we're going even shorter? [21:52] and some more stuff added in that's more applicable to our target audience [21:52] Having bucket loads of text doesn't make easy reading [21:53] semioticrobotic: yep [21:53] ok [21:53] No terminal stuff in Maverick [21:53] so the maverick edition's text won't be composed from the start, right? [21:53] godbyk: sure. will remind you [21:53] It will truly become a "Getting Started" guide, and readers will be directed to USLC for further learning [21:53] c7p: We'll be reusing whatever we can from the Lucid editions. [21:53] now ... will the giant content pool be generated BEFORE the Maverick release, or after? [21:53] semioticrobotic: after most likely [21:53] ok [21:54] When is the Maverick manual planned for release? [21:54] so Maverick writing will be our springboard into the pool [21:54] semioticrobotic: ya [21:54] ChrisWoollard: Not sure, it will be a day before Maverick is released. Which will October 9th. [21:55] ChrisWoollard: We had a nice release schedule, but then they moved the date on is and we haven't revised our schedule yet. [21:55] Ok. So not much time to write it then [21:55] nope [21:55] humphreybc-mini: In that case, the docs team and the manual team will most likely be collaborating during the writing and editing process? [21:55] semioticrobotic: I bloody well hope so :) [21:55] Here's what our original release schedule looked like: http://pad.ubuntu-uk.org/MaiZTb4Fjd [21:55] * semioticrobotic laughs [21:55] yes, me too [21:56] oh, and the persona [21:56] forgot about that [21:56] not doing it? [21:56] hopefully we are [21:56] The persona will be kind of a big deal, I think. [21:56] we'll just see [21:57] but not the persona touted in the first (and, er, only) episode of Ubuntuesday? [21:57] priorities are something like manual > USLC > quickshot > persona > our website > quickstart booklets [21:57] Shall we move on to the booklets real quick? [21:57] semioticrobotic: Ubuntuesday is going to make a stellar return soon [21:57] Whatever the case, I am happy to help write if required. [21:57] [TOPIC] Quick-start booklet(s) [21:57] New Topic: Quick-start booklet(s) [21:58] humphreybc-mini: Gotcha. That's actually a very helpful, seeing a hierarchical list of items [21:58] so we can test the water with one for installation I think [21:58] I think we should also do an about ubuntu one [21:58] ubuntujenkins: ah, that could be good too [21:58] and leave it at two. They are like the first two in a series [21:59] thorwil and I will be working on the design at some point [21:59] Ubuntu One (inc. music store). [21:59] The quick-start bookets will be really short guides (how-to's) that focus on just one task, procedure, or small application. [21:59] Then we just need to make it a latex template or something, and shove the text in [21:59] I think a Quick Start guide that has Ubuntu equivalents of popular Winows programs (for switchers) would be good [21:59] i think there will be a set eventully [21:59] yeah, think about the size of an Ubuntu CD sleeve, although slightly taller [21:59] what about a three fold leaflet? [21:59] a4 [22:00] I was just thinking about that [22:00] that'd certainly be nice for LoCos [22:00] * ubuntujenkins thinks great minds think a like :P [22:00] A4 would be good for locos to print off themselves [22:00] ;) [22:00] really i need to go, i'll read the log ASAP [22:00] daker: no worries, chow! [22:00] se ya daker [22:00] daker: No problem. Thanks for coming! [22:00] * semioticrobotic thinks these are all great minds [22:00] thanks [22:00] [TOPIC] First release of Ubuntu Support and Learning Center (USLC) [22:00] New Topic: First release of Ubuntu Support and Learning Center (USLC) [22:01] I think we've already discussed this item, but if there's anything anyone wants to add... [22:01] pyyyyyyyyyyyython [22:01] lol [22:01] Okay, then. :) [22:01] Anyway [22:01] Php ? [22:01] And finally: [22:01] [TOPIC] New look for the team [22:01] New Topic: New look for the team [22:01] So this new look will be [22:01] o do i get new clothes? [22:01] haha [22:01] Makeovers for everyone! [22:01] hair style? [22:01] I need some shirts [22:01] is this like another reboot of Power Rangers or something? [22:01] new website, new slogan, new philosophy, new marketing materials, new website instructions, new collaboration with other teams [22:01] Do i have to wear a bowtie [22:02] LOL [22:02] good idea [22:02] okay [22:02] My last exam is this friday [22:02] that's ... quite a makeover! [22:02] after that I have two weeks holiday where I will be working 9 - 5 on Ubuntu :P [22:02] on the new philosophy/colaberation it would be nice if we hung out in #ubuntu-doc as well as here [22:02] So I'll get a mega shit tonne of designs and specs out [22:03] ubuntujenkins: Yeah, good point [22:03] humphreybc-mini, i need perfection for the website [22:03] * ubuntujenkins hints everyone to join [22:03] haha [22:03] daker: I know :P [22:03] daker: It's coming along good [22:03] we will see [22:03] daker: http://twitpic.com/1w0ni3 [22:04] good [22:04] http://bobbo.me.uk/index.php/planet-ubuntu/operation-cleansweep-day-four-update [22:04] LINK received: http://bobbo.me.uk/index.php/planet-ubuntu/operation-cleansweep-day-four-update [22:04] GOOD [22:04] nice daker! [22:05] That progress bar is nice [22:05] good stuff [22:05] hi [22:05] [TOPIC] Miscellaneous/other business and open questions [22:05] operation cleansweep seems like a huge undertaking [22:05] New Topic: Miscellaneous/other business and open questions [22:05] hi zleap [22:05] Okay, does anyone have any other topics we should discuss? [22:05] Any questions? [22:06] good night [22:06] just downloaded the UK english manual, according to the properties its in US letter [22:06] G'night, daker [22:06] this is properties of the file, so the properties dialog says US letter [22:06] godbyk: this is your area [22:06] zleap: It says A4 here. [22:06] hrmmmmm [22:06] humphreybc-mini: I'll be moving soon ... a pretty significant relocation so I can start my doctoral studies [22:07] zleap: I just downloaded it from http://builds.ubuntu-manual.org/builds/ubuntu-manual-en_GB.pdf [22:07] semioticrobotic: where are you off to? [22:07] unfortunately, during that time, I'll be MIA [22:07] semioticrobotic: Awesome! What're you studying? [22:07] Moving to another state, North Carolina [22:07] team: alpha version of ubuntu manual is released in the ubuntu release party http://kanchilug.wordpress.com/2010/06/07/ubuntu-10-04-release-party-at-kanchipuram/ [22:07] * humphreybc-mini though semioticrobotic lived in Germany [22:07] http://kanchilug.wordpress.com/2010/06/11/alpha-version-of-ubuntu-manual-in-tamil-released/ [22:07] LINK received: http://kanchilug.wordpress.com/2010/06/11/alpha-version-of-ubuntu-manual-in-tamil-released/ [22:07] ha! [22:07] humphreybc-mini: that's thorwil [22:07] thanks a lot your help [22:07] humphreybc-mini: Most people assume this, because of my last name [22:08] screwed godby and ubuntujenkins a lot [22:08] shrini: Congratulations! Awesome job on the translation. [22:08] lots of people assume i come from the netherlands, due to my nick [22:08] thanks godbyk. [22:08] * godbyk doesn't know what people make of him. [22:08] godbyk: I'll be studying in the Department of Communication Studies [22:08] working on cultural studies, critical theory, and media studies [22:08] my UK PDf from that link reckons it's A4 [22:09] on builds.ubuntu-manual.org. Why are the two English (American) entries? [22:09] thanks [22:09] ChrisWoollard, maybe one is print the other is screen [22:09] ChrisWoollard: I think I started the script, then stopped it and restarted it (without wiping out the half-written html file). [22:09] Ok. Thanks [22:10] ChrisWoollard: Or: Because American English is so incredibly awesome, it's worthy of two entries. [22:10] Take your pick. :) [22:10] I am really pleased the UK edition only has 2 warnings/ [22:10] godbyk: Whatever. [22:10] shrini: that release party looked awesome [22:10] humphreybc-mini: :-) [22:11] * humphreybc-mini is tempted to do an OMG! Ubuntu! post on release parties now [22:11] ChrisWoollard: I think that those warnings can be ignored, too. I'll look into them. [22:11] OMG post is a good idea [22:11] Okay, does anyone have anything else for the meeting, or shall I release MootBot from his duties? [22:11] hey so godbyk, what's the story on translations? [22:12] When can I announce that we have some more released? [22:12] humphreybc-mini: You should've been here about 10 minutes earlier. :) [22:12] I am sure that one was a image. which is fine because the US english cover is good for UK [22:12] humphreybc-mini: Short answer: When I tell you. :) [22:12] boo [22:12] humphreybc-mini: http://pad.ubuntu-uk.org/translationtodo [22:12] ubuntujenkins and c7p and I have been working on a checklist. [22:13] #endmeeting [22:13] Meeting finished at 16:13. [22:13] Thanks, MootBot! [22:13] very informative meeting :D. Godbyk what else remains for the greek edition? [22:13] Good ol' MootBot [22:14] good meeting everyone [22:14] so what am i supposed to do? [22:14] godbyk how awfully complicated [22:14] I'm off [22:14] dutchie: start working on USLC :P [22:14] humphreybc-mini: tell me about it! [22:14] c7p: I'm not sure yet. Do you have everything on that checklist done already? [22:14] bye everyone [22:15] semioticrobotic: bye [22:15] team: thanks all [22:15] I think yes, but I'm not 100% sure. Let me check the list [22:15] c7p: Okay. [22:16] shrini: we will have to work on the final version of tamil when the translations are finished [22:16] humphreybc-mini: I have 5 more exams, and nobody has told me anything about the backend infrastructure :P [22:16] dutchie: When is your last exam? [22:16] ubuntujenkins: yes. will finish it up as soon as possible [22:16] humphreybc-mini: ages [22:16] .... [22:16] shrini: no rush I look forward to seeing it finished [22:16] 28th of June [22:16] Seems everyone busy with exams these days. [22:16] no worries [22:16] you concentrate on exams [22:17] when you're finished I guarantee you there will be work :) [22:17] yay [22:17] ubuntujenkins: sure. [22:17] thanks [22:17] okey friens [22:17] leaving now [22:17] * ubuntujenkins shouts at gwibber [22:17] * humphreybc-mini is hoping that once USLC work commences, Canonical might hire a dev or two to work on it [22:18] Like they did with Zeitgeist and a few other things [22:18] catch you later [22:18] humphreybc-mini: keep dreaming [22:18] see ya shrini [22:18] bye [22:18] maybe they could pay me to work on it [22:18] maybe dutchie [22:18] ubuntujenkins: Did you run through http://pad.ubuntu-uk.org/translationtodo on en_GB? [22:19] ChrisWoollard: no I just checked it for build errors [22:19] Ok. I'll try to do that this week. [22:20] i did about 5 langauges and recorded the common mistakes. I will have a look if i have time after my exams [22:21] * humphreybc-mini has to get out of bed and start studying [22:22] I have two big exams this week so don't expect to see me around till next weekend [22:22] humphreybc-mini: have you finally got OOP/Python? [22:22] ya I think so [22:22] godbyk Is it possible to make a simple program/script checking that everything is fine on the tex file? (e.g Idots ans so on) [22:22] Had an exam on that on friday [22:23] went fairly well [22:23] wish i could have an exam on python [22:23] I wish i could have an exam on ubuntu. [22:23] actually, most I wish that my eyes/nose would learn how to deal with pollen [22:23] lol [22:24] c7p: Well, it's really hard to parse LaTeX code properly, but I would like to have a script that checks a lot of the simple/common errors. [22:24] i did put that on my todo list once [22:24] it didn't get very far [22:25] I could write up a whole list of simple checks to make, if someone wants to take a shot at coding it up. [22:25] I think i got as far as "#!/usr/bin/perl; use strict; use warnings;" [22:25] I wrote a script before that checked for common English errors. [22:25] That needs to be updated/expanded, too. [22:25] And Ilya wrote a script that runs spellcheck against the .tex files. [22:25] We should probably wrap all those functions into once place. Maybe with a simple GUI frontend, too. [22:26] don't mention a gui :P [22:26] dutchie: Ilya's and my scripts were in Python. [22:26] GUI isn't required by any means. [22:26] just glade [22:26] hack it all together :P [22:27] But yeah, I think we should have an Ubuntu Manual lint program. :) [22:27] "lint" ? [22:27] If anyone gets some free time (or feels like procrastinating) and wants to take it on, give me a holler. [22:27] * ubuntujenkins hides at the mention of glade [22:28] ubuntujenkins: yeah. there are lots of *lint programs that check the format of code or other nit-picky details. [22:28] ubuntujenkins: see "apt-get search lint" for examples. [22:28] (including lots of 'em for python.. like pyflakes.) [22:28] I see [22:28] many things to be done, we have still long way [22:28] why will facebook not add in gwibber [22:29] c7p: For the project in general, or for the Greek translation in particular? [22:29] ubuntujenkins: check your username. [22:29] the project in general :) [22:29] RTL stands for ? [22:29] c7p: definitely true [22:29] godbyk: it authorises it jsut will not do anything after clicking all [22:30] c7p: right to left [22:30] ubuntujenkins: thank you :) [22:30] *add not all [22:30] c7p: I did not know untill daker told me :) [22:30] yey giwbber works! [22:32] right [22:32] im off [22:32] catchya later [22:32] seya humphreybc-mini [22:34] godbyk: At http://builds.ubuntu-manual.org/ I see that the greek pdf has 4 warnings, and 2 errors [22:35] godbyk: the last time I checked it had 4 warnings 0 errors :/ [22:35] c7p: Yeah, the errors are my bad. [22:36] c7p: I rewrote the code for the revision info translation stuff and screwed up the Greek version. [22:36] c7p: I just committed a fix. [22:36] godbyk: ok, no worries :) [22:36] godbyk: I there any way I can find and "fix" those 4 warnings [22:36] I'm going to update all of the builds again soon. [22:37] c7p: Hm.. let me see what they are. [22:41] c7p: It looks like they're fontspec warnings. It's complaining that there's no Greek language for the Greek script. [22:41] I'm not quite sure what it's on about there. I'll have to look into it. [22:41] c7p: Can you check the page number references in the glossary and see if they're correct? [22:41] The English ones weren't. [22:41] If I continue to have problems with them, I will just disable them. [22:42] I'll be back in just a bit. [22:43] night all [22:43] night [22:43] godbyk: sure [22:43] night ubuntujenkins [22:46] godbyk: hm, by "page number references: you mean the (translated) word(s) that it should have? [23:01] c7p: At the end of each glossary entry, there are page numbers that link to the page(s) that the word appears on. [23:01] In the English version, the page numbers were off by one, sometimes. [23:02] For example, it may say the word appeared on page 47 when it was actually on page 48. [23:02] godbyk: ok I'll check the number references [23:08] godbyk: On ISP entry the page 168 isn't correct, I've also other bugs should I mail them to you or report them one by one on channel ? [23:11] Probably best to email them to me. [23:11] That way if I don't get them fixed immediately, they can stay in my inbox and visually harass me until I do fix them. :) [23:15] godbyk: lol :p ok [23:45] godbyk: message send, 7 bugged glossary entries tracked