[19:46] godbyk: drive-by increasing sanity level on ayatana list, eh? ;) [19:53] thorwil: My feeble attempt, yes. :-) [19:54] I figured a quick response would generate a bashful reply, 'Oh, well, nevermind then.' Sadly, that's not what happened. [20:00] Hey, rickfosb. How's it going? [20:01] Hey, c7p. [20:01] hi godbyk [20:02] Doing great, godbyk! [20:02] hello all :) [20:02] And you? [20:03] Not too bad. [20:04] Hey! [20:05] Hi c7p. Meeting not for another hour, right? [20:05] another hour yup [20:06] i thought it was now. [20:06] silly british summer time!! [20:06] I thought it was now too. [20:06] But then I realised: 20:00 UTC. [20:06] Gargh. [20:06] Oh well. :-) [20:06] I got here in time as well. :P === godbyk changed the topic of #ubuntu-manual to: Ubuntu Manual Project discussion | Meeting Agenda: http://pad.ubuntu-uk.org/UMP-April-Meeting | Style Guide: http://files.ubuntu-manual.org/style-guide.pdf | Website: http://ubuntu-manual.org | Launchpad: https://launchpad.net/ubuntu-manual | IRC logs: http://irclogs.ubuntu.com [20:37] That wasn't as tricky as I thought it might be. :) [20:43] msg godbyk Question about the use of "\acronym". Not in style guide, but I see it all over the Installation chapter. [20:43] CrustyBarnacle: It's not in the style guide? Hmm.. I'll have to fix that. [20:43] CrustyBarnacle: What's your question? [20:44] msg godbyk Not in Index, and search using find does not bring up any results for it. [20:46] msg godbyk Using this guide: http://files.ubuntu-manual.org/style-guide.pdf [20:46] godbyk, CrustyBarnacle, we probably need to add some verbiage on use (when to and not to use the tag) [20:47] msg godbyk Yes. Should it be used on first occurrence of acronym only? [20:47] sounds reasonable [20:47] CrustyBarnacle: \acronym is a formatting command. It formats the text in small caps. [20:48] CrustyBarnacle: So it should be used each time the acronym is used. [20:48] Hello everyone. I'm new in the whole "ubuntu-manual" think, and as I can see it looks like I'm gonna have to learn about LateX... [20:48] msg godbyk OK [20:49] I thought I could easily help as a chapter author but it's seems that it's gonna be more complicated than that. [20:49] We are supposed to start in a short while, right? [20:49] it seems* [20:49] monfort: Welcome! Don't worry. The parts of LaTeX used by authors and editors is fairly easy to learn. You can find most of the information you'll need in the style guide at . Feel free to ask me any questions you have along the way, too. [20:49] debayan: Yes, we'll start the meeting in 10-15 minutes. [20:49] monfort, its not that bad. [20:49] cool godbyk [20:50] monfort: Also, there are others who are willing to help with the formatting if you just want to focus on writing the content or proofreading. [20:50] monfort, if you supply the typing, the editors can help with the format [20:50] Well actually I thought it was all about using Libreoffice and Scribus ... [20:51] And does learning LateX involves learning HTML ? [20:53] msg monfort http://ubuntu-manual.org/getinvolved/authors [20:53] hei guys [20:53] how are you doing all? [20:53] Hey. [20:53] hai issyl0 [20:53] shrini, really great thanks ! [20:54] monfort: :-) [20:54] happy to see you all again [20:54] CrustyBarnacle : Oh great I never saw that webpage ! :D [20:54] monfort: No, learning LaTeX does not involve learning HTML. LaTeX is great - I'd recommend just looking through the files in the existing bzr branches to get a general idea, and of course the style guide. [20:55] Hey, issyl0. Thanks for your recent editing help on the maverick edition. [20:55] issyl0: I hope this session is being logged. [20:56] Okay I will do it. I won't participate to the meeting today, because I first need to learn on this. I'm gonna start tomorrow and will let you all know about my progress. ( I have to start from the basics ... ). [20:56] godbyk: No worries - always happy to help - seeking to get more involved actually, hence my application for an editor position. [20:56] have in mind i will update the content of get involved pages today or tomorrow, i hope the new content will help you [20:56] Just one question : Who should I keep the email of ? [20:57] I recently started on LaTex. Not as steep a learning curve as it seems to start contributing. [20:57] monfort: you can send mails to mailing list (if i understood the question right) [20:57] Is it the same kind of mailing list that uses dizans of e-mails per day ? [20:58] Seriously sometimes I can't read all of my mails from newsletters and stuff so with a mailing list ... :/ [20:58] monfort; to date, not that many emails from this list. [20:58] monfort: The Ubuntu Manual mailing list is fairly low-traffic at the moment. [20:59] Okay then I'll subscribe ! [20:59] godbyk: I enjoy contributing. :-) [20:59] Hello to all of you [20:59] Hi hannie. [20:59] I have to go now. Really happy to know you all guys and hope to be able to help as soon as I can. [20:59] Thanks for coming, monfort. [20:59] I'm really happy to start contributing and feel part of something great ! [20:59] By ! [21:00] (Ah, the satisfaction of making people happy. :-)) [21:00] hehe yeah, just a motivate to keep contributing [21:00] :-) [21:01] hi guys! [21:01] c7p: Yeah. [21:02] (Hrm. I'll be back in 2 mins. But, o/) [21:02] meeting in 5 mins, raise your hands guys ! [21:02] sounds good [21:02] o/ before I disappear for two minutes... [21:02] ok, 5 min [21:02] ok 5 [21:02] OK 5 [21:04] I hope I can contribute properly. [21:06] Right, hi. [21:06] debayan: don't worry the team will help you to do it [21:09] #startmeeting [21:09] Meeting started at 15:09. The chair is godbyk. [21:09] Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE] [21:10] Hello, everyone. Thanks for coming. Before we get started, can we have a quick roll call? Just a quick 'hello' from anyone who's attending the meeting, please. [21:10] Hello! [21:10] Howdy [21:10] hia [21:10] Hello friends [21:10] hello [21:11] Hello everyone. Great to be here :) [21:11] Thanks! [21:11] [TOPIC] Getting Started with 10.10: What still needs to be done? [21:12] New Topic: Getting Started with 10.10: What still needs to be done? [21:12] I think the Maverick edition of the manual should be nearly ready for publication. [21:12] I know that we still need to take some screenshots. [21:12] What else needs to be done for this edition? [21:13] What's the use of publishing Maverick when Natty is coming so soon? [21:13] I've done a fair bit of editing over the last few days - grammar/spelling/LaTeX/whatever. [21:13] I submitted some screenshots [21:13] do anyone get them? [21:13] are they useful? [21:13] Reviewing Installation [21:13] hannie: Well, since it's practically finished already, there's no harm in it. Also, it will serve as the base for the Natty edition. [21:14] ok [21:14] hannie: On the other side, what's the point of wasting a manual we've written? [21:14] shrini: Ah, I see that most of the screenshots have been submitted. Great! [21:14] It looks like there are just a handful of them missing still. [21:14] godbyk: oh. thanks [21:15] i thought that they were not sent [21:15] to server [21:15] CrustyBarnacle: Would you like to look over the installation chapter of the maverick edition for us? [21:15] It looks like we're just missing one screenshot and one is pending approval. [21:16] godbyk Yes [21:16] there is a problem with that screenshot, quickshot must have a bug [21:16] c7p: The pending screenshot or the missing screenshot? Can we take it manually? [21:16] maybe we can capture it manually and cut the image with gimp to make it proper for the manual [21:17] c7p: Okay. I'll look into that. [21:17] c7p: Shutter works great for taking and editing screenshots :-) [21:17] Are there any other to do items for the maverick edition that anyone can think of? [21:18] CrustyBarnacle: i love gimp :) but maybe i should try Shutter also [21:18] I like shutter too [21:18] quick and easy [21:18] godbyk, when we are ready to 'publish', is it linked to the manual page (simple as that?)? [21:19] rickfosb: When we 'publish' the manual, we upload the PDFs to the website and also publish it to lulu.com (where you can purchase a printed copy). [21:19] thanks [21:19] All right, let's move on to the Natty edition. [21:20] [TOPIC] Natty edition authors and chapter editors [21:20] New Topic: Natty edition authors and chapter editors [21:20] woohoo! [21:20] msg rickfosb what is the publication date for Maverick? What's our deadline to get to translators? [21:20] Cool. [21:20] The GUI is so different in natty [21:20] Earlier this week, we asked for volunteers to write and edit the chapters of the Natty edition of the manual. [21:20] have to write from scratch on the GUI part [21:20] We also contacted the previous authors and editors to see if they'd like to reprise their roles. [21:21] I have some experience with unity. [21:21] https://spreadsheets.google.com/pub?hl=en&key=0Ar0Z6vOO38EydERxaWhGTkU2NTVDU2pxYXNHWWR1MlE&hl=en&gid=0 [21:21] The list of assigned authors and editors is shown here: http://bit.ly/gG59j7 [21:21] CrustyBarnacle, We can probably try to set a date today, [21:21] this is the list of assigned chapters to authors [21:22] c7p: We should ask the new volunteers if they have any preference as to which chapter they're assigned. [21:22] there are like 8 authors and editors that aren't in this list because they haven't a chapter so don't worry [21:22] who assigns them? [21:22] of course [21:22] :-) [21:22] rickfosb will assign you the chapter [21:23] hannie, I'll work with them and assign [21:23] c7p, yes [21:23] Cool. [21:23] great [21:23] If anyone else would like to volunteer to be an author or editor, please feel free. [21:23] but he is new so as most of you so don't make him anxious :) [21:23] We'll take all the help we can get. :) [21:24] I'll reach out via email over the next day or so and start updating the list. [21:24] godbyk: Indeed [21:24] should we advertise for hel at LUGs? [21:24] What's the ratio of editors to authors to chapters to applicants for roles? [21:24] can i volunteer for the prologue? [21:25] CrustyBarnacle: Yes, feel free to advertise and help find some volunteers. [21:25] Who controls that Google Doc? [21:25] piratemurry, -> prologue [21:25] looks good [21:25] issyl0: [21:25] issyl0: i do [21:26] I have sent an email this morning [21:26] c7p, do you have nick to email for all of us? [21:26] c7p: Ah, right. [21:26] Hey I would like to take up the Ubuntu Desktop chapter. [21:27] piratemurry, was the Author, or Editor? [21:27] what do you need? [21:27] author would be first preference but i'm not fussed [21:27] happy to help in any way [21:27] piratemurray; author or editor for prologue? [21:27] who reads jobs@ubuntu-manual.org? [21:28] i like to be author of working with ubuntu [21:28] piratemurray; thanks [21:28] 55 [21:28] Argh. [21:28] hannie: A few of us do: me, c7p, cwoollard, rickfosb. [21:28] rickfosb: so that is author then? [21:28] excellent [21:29] piratemurray: is Author for Prologue [21:29] rickfosb: no i don't know the nicknames, PM me authors and editors [21:29] msg c7p mario@petrielabs.com [21:29] CrustyBarnacle: Be sure to put a / in front of 'msg' otherwise it still sends it to the channel. :) [21:30] Shall I take "Working with Ubuntu" ? [21:30] CrustyBarnacle: You're missing a / before "msg". :-) [21:30] :) [21:30] c7p; thanks. Rest of you, I'll use the 'list' to reach out as needed. [21:30] I see... [21:30] Okay, shall we move on to the next agenda item? [21:31] let's go... [21:31] [TOPIC] Screenshot size for Natty edition [21:31] New Topic: Screenshot size for Natty edition [21:31] c7p: Do you know what this topic is about? [21:32] i didn't write it :) [21:32] In the agenda item, it says that the screenshots in the 10.04 edition of the manual are too large and that it's ahrd to read the text and look at the pictures at the same time. [21:32] my vote is for the higher resolution, but sized down, so we get readable screenshots. [21:33] They suggest using 800×600 resolution screenshots instead of the current 1024×768. [21:33] 800x600 would be nice [21:33] I remember doing some tests early on when we started taking screenshots. [21:33] One of the problems with reducing the screenshot resolution is that the screenshot start to look very pixelated and muddy at lower resolutions. [21:33] Is the quality fo 800x600 good enough? [21:33] I didn't write it either, but if you flip through the manual, some of the shots are full page, some rest within the main column... seems a mis match [21:34] *of [21:34] rickfosb: Here's how the screenshot size in the manual is determined: [21:34] We take all the screenshots at the same resolution (currently 1024×768). [21:35] The widest screenshot (currently we use the full desktop screenshot for this) is scaled to fit in the margins of the manual (across the main text block and the sidenotes area). [21:35] All of the screenshots are scaled using this same scaling factor. [21:36] If the scaled screenshot is narrow enough to fit in the main text block, then it's centered there and the caption appears adjacent in the sidenotes area. [21:36] godbyk; so, menu drop downs, etc., will be a small centered shot.. and desktop or full application will be large; makes sense [21:36] If the scaled screenshot is too wide for the main text block, then it will be centered across the full page (main text block + sidenotes area) and the caption will appear above or below the screenshot. [21:37] what if the max width was only main text block? [21:38] CrustyBarnacle: We could scale all the screenshots so that the max width is only the main text block, but then the text in the screenshots is difficult to read (as it's so small). [21:38] So, back to question, do we have a sample of 800 vs 1024 to compare? [21:38] Screenshots are for reference only, not for providing actual instructions. So... [21:39] rickfosb: In the lucid-e1 repository, there is a lucid-screens/ dir that has samples taken at different resolutions. [21:40] I'll look [21:40] CrustyBarnacle: While the screenshots aren't there to provide instructions themselves, it is frustrating to not be able to read the text in the screenshot. [21:40] godbyk: Absolutely. [21:40] (Re: the frustration.) [21:40] The samples in that directory are taken at 1024×768, 1280×800, and 800×600. [21:40] godbyk: I see... [21:41] Having said all that, we can certainly take another look at the problem and see if we can improve upon the previous (Lucid edition) solution. [21:41] Does anyone else have any questions or comments on this topic? [21:42] can you give us a link to the examples? [21:42] I need to catch up with the instructions at http://ubuntu-manual.org/getinvolved/authors [21:42] is there any weblink available for a quick check on resolutions? [21:42] Can we agree to review the samples and discuss later (next meeting)? [21:43] hannie: http://bazaar.launchpad.net/~ubuntu-manual/ubuntu-manual/main/files/head:/lucid-screens/ [21:43] thank you [21:43] CrustyBarnacle: Sure. [21:43] godbyk, I'll review as well, but unless there is a compelling need to change..., I'm ok with the current process. [21:44] All right. Let's take a look at it and come back to our next meeting with our findings. [21:44] [TOPIC] Do we need to provide screenshots for non-Unity users? [21:44] New Topic: Do we need to provide screenshots for non-Unity users? [21:45] My initial response to this question is, 'Sure, why not?' But I'm not sure what concerns prompted the question. Anyone else? [21:45] what do you mean by non-unity users? [21:45] shrini: GNOME Classic? [21:45] We will need to this because Unity crashes a lot, and many users are likely to go back to Gnome [21:45] I have one of the pc's that doen't support Unity. So, I 'found' my way around the system menus; [21:45] *doesn't [21:45] shrini: I think they're referring to the users who will see the GNOME desktop instead of Unity due to lack of sufficient hardware to run Unity. [21:45] would the screenshots be side-by-side or in a separate section? [21:45] also the hardware support issue. [21:46] If we provide screenshots for non-Unity users, we should provide narritive within the manual about GNOME too - is this feasible/likely? [21:46] s/narritive/narrative/ sorry. [21:46] CrustyBarnacle: I think that the Unity and GNOME sections would be different. [21:46] I'm thinking we just need to cover the 'general' navigation issues. [21:46] well regarding unity, from what i know there will be unity 2d for old pc and unity 3d for new machines -independs to hardware- [21:46] I agree it should be different. Infact lets have separate manuals. [21:46] Does the Gnome desktop comes in default ubuntu 11.04? [21:47] do you not have to do some advanced tweaking to get GNOME back. i thought it was either Unity or Unity 2D (for the older computers) [21:47] or we have to install it separaely? [21:47] debayan_: The problem with having two separate manuals it that you have to know beforehand which manual you need. [21:47] the gnome part can be copied from Maverick I think [21:47] godbyk; agree with one manual [21:47] debayan_: One of the use cases for our manual is that I should be able to hand a copy of the manual along with an Ubuntu CD to a friend and they should be able to install and use Ubuntu without pestering me with incessant questions. :) [21:47] one manual... [21:47] yeah one manual to avoid confusion [21:47] godbyk: hmm, good point. [21:48] godbyk: Totally [21:48] one manual to rule them all [21:48] I suspect that the 2d section would not be 'large' when compared to the changes we'll need to make to 3d [21:48] Is the person who added this agenda item present? If so, can you explain your concerns a bit more? [21:49] godbyk; that was me. So, the concern is, do we need to support non unity users? I have a new netbook, but it doesn't do unity 'as is' [21:49] godbyk: I remember the openSuSE manual. It had Gnome and KDE parts separate. [21:49] MrX [21:49] first of all, we talk hypothetically ? are there tangible differences with unity 2d and unity 3d that will affect the manual ? first we should answer this -if anyone knows- [21:50] rickfosb: Ah, gotcha. [21:50] rickfosb: You are expected to use unity 2d then. [21:50] godbyk; poulsbo drivers aren't ready, yet. [21:50] I think that we should provide at least enough information that they know what they're looking at and provide pointers to further documentation. [21:51] especially, if our graphic shows some nice application icons... and the user doesn't see them [21:51] Yeah. [21:52] Personally, I'm not overly concerned about the size of the manual (as long as it doesn't get too out of hand), and would rather err on the side of including too much information than not enough. [21:52] It's very disconcerting when you're following along in a manual and you've encountered a situation that the manual doesn't cover. [21:52] godbyk: Definitely. [21:52] * issyl0 agrees. [21:53] godbyk: Would an increase change the cost to buy it? [21:53] agree; Since I have a netbook with the 2d issue, I can help out with providing some shots. [21:53] So if we don't include information about GNOME classic (which may be reasonable if it's unlikely that most Natty users will encounter it), then we should at least make mention of it, explain why the reader may have encountered GNOME classic, and where they can go to get more information about it. [21:53] CrustyBarnacle: The price of the printed manuals is based on the page count. So the more pages in the manual, the more expensive it is. [21:54] rickfosb: Did this satisfactorily address your concerns for non-Unity users? [21:54] yes! [21:54] Excellent! [21:54] [TOPIC] Documenting Ubuntu derivatives [21:54] New Topic: Documenting Ubuntu derivatives [21:55] what are they? [21:55] Ubuntu derivatives would be Kubuntu, Xubuntu, Edubuntu, etc. [21:55] kubutu/edubuntu/xubuntu/liubuntu/mint [21:55] Ubuntu derivatives as in [X|K|Edu|...]buntu? [21:55] There are differences in unity 2d and 3d http://www.omgubuntu.co.uk/2011/03/unity-2d-a-quick-look-at-the-latest-updates/ [21:55] oops [21:55] Like edubuntu, kubuntu, xubuntu? [21:56] Right now we mention those derivatives in the introduction, I think, but otherwise we don't talk about them at all. [21:56] yeah i agree [21:56] we make mention of them? not a whole chapter though..... few paragraphs [21:56] The question is, should we include more information about these derivatives in the manual? [21:56] I agree, and we mention links. [21:56] I hope that little content is enough [21:56] Mention + Links [21:57] Yes, keep it short [21:57] because explaining KDE needs a full book [21:57] maybe some reasons why one would want to use the derivite [21:57] Can we link to actual documentation for all derivatives? [21:57] My concern is that I wouldn't talk about them to much in the beginning because you're forcing a choice on the unsuspecting reader. [21:57] such as "use Lubuntu if you want XYZ...." [21:57] godbyk: good point [21:57] How should the reader decide if they'd prefer a different derivative if they're just getting started with Ubuntu proper? [21:57] We shoud mention it at the end. [21:57] Advanced Topics. [21:58] that's how i discovered the derivites when i started using ubuntu [21:58] That would be fine [21:58] I could see adding a section toward the end of the manual that gives a page or two to discuss the pros and cons of each derivative and provides pointers to documentation about them. [21:58] almost as an advanced topic after i was comfortable with Linux/ Ubuntu [21:59] with a screenshot? [21:59] godbyk: yes [21:59] It's also possible to write manuals for each individual derivative at some point in the future, but that's a lot of work. :) [21:59] godbyk: cool, the learning more chapter can host this section [21:59] were gonna need a bigger boat :-) [21:59] c7p: I think that 'Learning More' would be a good place for this info, yeah. [21:59] :-) [21:59] rickfosb: Definitely! [21:59] c7p, agree [21:59] who is updating notes? [21:59] shrini: i wouldn't want to see screenshots of the different *buntus but that's just my opinion [22:00] c7p: Yup. [22:00] Basically, any derivative manuals would warrant their own team of authors and editors. (Though they can share our toolchain, etc.) [22:01] Are there any other thoughts on this or shall we move on to the next agenda item? [22:01] [TOPIC] Useful applications (and how to install them) [22:01] Next :-) [22:01] New Topic: Useful applications (and how to install them) [22:02] Some of the applications listed under this agenda item include Wine, Adobe Acrobat Reader, Inkscape, Chromium, Skype, and XBMC Media Center. [22:02] Cool. [22:02] No acrobat reader [22:02] Hrm. An interesting one... [22:02] The general question is, what applications should we discuss and how much detail should we go into? [22:02] shrini: i agree [22:02] it is huge [22:03] we already have evince. [22:03] evince is great to read a pdf file [22:03] shrini: Agreed [22:03] I like the idea of 'Doing more...' but I would think we keep it simple with links to the source documentation? [22:03] Skype also is not such a must have app. [22:03] rickfosb: i agree [22:03] i don't think we need this chapter [22:03] Not even Wine. People should really be using Windows if they need Wine. [22:03] debayan: i'd disagree. many people migrating to ubuntu would like to see skype [22:04] I use Chromium... but don't want to start a browser feud. [22:04] piratemurray: So they jst need to google. [22:04] Skype hosts deb packages on their website, with instructions. [22:04] arguably they can google everything in the manual [22:04] we can say a like 'skype also available for ubuntu in their site ' [22:04] should we not make light of the fact that skype et al are available in linux? [22:04] shrini: yes [22:05] we have to say about gimp [22:05] piratemurray: I dont know if we should be pointing people towards installing proprieatary stuff on Ubuntu. [22:05] remember that we are working on linux alternative apps table, and i think that's enough http://bit.ly/f0LTRQ [22:05] proprietary * [22:05] what about multimedia codecs? [22:06] ubuntu-restricted-extras [22:06] shrini: Multimedia codecs can be covered in the chapter that covers playing media, because in ubuntu all you have to do is click a few buttons. [22:06] debayan_: thats fine [22:06] shrini: We do mention the restricted drivers and ubuntu-restricted-extras package. [22:06] We mention the Installation option of selecting "third-party software" in Installation [22:07] godbyk: good [22:07] The ubuntu-restricted-extras package is mentioned in the troubleshooting chapter. [22:07] okey [22:07] what about XMBC? [22:07] shrini: That's not mentioned. [22:07] is it available in repository as default? [22:07] XMBC is not desktop use, right? [22:08] Though Mythbuntu and MythTV are. [22:08] it is not there in my 10.10 repos as default [22:09] we can say about cheese [22:09] handbrake [22:09] Do you think that the Linux/Windows app equivalences table will be sufficient? Or do we need to go into more detail? [22:09] gtkpod [22:09] If we need to go into more detail, should that detail be in this manual or in a separate document? [22:09] yup [22:09] that table would be so fine [22:09] godbyk: Table should be sufficient. The instructions for third party apps may change as well. [22:10] Okay. [22:10] Table looks good... [22:10] Mmhmmm. [22:10] [TOPIC] Upload chapters for translation as they are completed [22:10] godbyk; does it format for latex or do we link it? [22:10] New Topic: Upload chapters for translation as they are completed [22:10] hannie: Did you or rickfosb add this item? [22:11] wasn't me [22:11]