[00:01] yeah we probably could [00:10] have you all gone here and marked the bug as affecting you? [00:10] https://bugs.edge.launchpad.net/ubuntu/+source/example-content/+bug/505873 [00:10] Launchpad bug 505873 in example-content "Ubuntu Manual for example content in Lucid" [Wishlist,New] [00:43] humphreybc, wouldn't you prefer the manual to be in the desktop? [00:47] i would [00:47] this is just the first step [00:48] if we get it as example content then it will be easy to ask them to add a link on the desktop [00:48] ok [00:49] yeah I thought that was your intention :) just making sure [00:49] i also want a big fat link here: http://www.ubuntu.com/getubuntu/download [00:50] right beside the big green "download ubuntu" button I want another button that says "download the official manual" [00:54] That'd be so nice [00:54] humphreybc, I have a couple of questions [00:55] #1 requires you to read a piece of my chapter blueprint [00:55] 1. Do I need to meticulously describe how to get the basic operations done in applications such as Software Sources, Ubuntu Software Center and Synaptic Package Manager, or rather just explain the purpose of each? [00:57] the other one i don't remember [00:57] but I would like to suggest a section in the advanced part of the manual to explain how to build packages [00:57] and how simple it can be [01:07] wolter: um software center is pretty easy, you could probably just say something like "search for the application you require or find it under the categories and then click install to let Ubuntu do the rest" - I think they're working on the software center in Lucid to make it even easier [01:08] Software Sources and Synaptic you will have to go into a bit more detail [01:08] but not a lot of detail [01:08] and as for building packages, that's too advanced even for the advanced section I'm afraid [01:08] oh ok [01:09] yeah sorry [01:15] how big do we think the PDF will be? [01:15] well, i think about 40 pages? [01:15] don't you think? [01:15] the last time i built the manual it was 21 pages long, but not at all finished as we all know [01:16] no i mean size [01:16] it's about 150kb at the moment [01:16] but with images [01:16] and another 20 pages or so [01:16] it'll be what, 2mb? [01:18] * humphreybc is talking to Jorge Castro who packages the example content for the releases [01:20] * humphreybc he says we need to squeeze every kilobyte out of it [01:21] * humphreybc "me: And you personally, think it's a good project?" [01:22] * humphreybc "Jorge: yeah of course!we definately need it!" [01:25] * humphreybc has registered a new blueprint: https://blueprints.edge.launchpad.net/ubuntu-manual/+spec/optimization [01:37] nice work humphreybc :) [01:39] we're on our way! [01:46] i will send an article that may seem interesting to all the manual writers to the mailing lists [01:48] ok [01:52] humphreybc, do you think I should write always with a semi-paranoic point of view? [01:52] what do you mean? [01:52] like, in deb packages i should warn people to not install every deb package they see [01:52] because anybody could make one [01:52] right? [01:53] yeah that would be a good idea [02:06] nice link [02:22] thanks [02:24] i wonder if we should do some research [02:26] i might start a thread on UF with 5 questions [02:26] for content [02:27] something like "If you could definitely have one topic in the manual, what would it be?" and "Would you prefer lots of screenshots to show you how to do things, or would you prefer step by step guides?" etc [02:27] but i'd need help from the team to formulate five good useful questions [02:28] and of course we will have to aim it at Ubuntu newcomers - so we'll have something like "Remember to back when you first started using Ubuntu, and answer these questions as if you were that person back then:" or something [02:28] as well as putting it in the absolute beginners forum [02:28] so, guys, ideas for questions please [02:30] what do we NEED to know? [02:31] perhaps we could give them the list of default apps and ask them to put them in order of which should be highest priority/include the most detail [02:31] ok, I think we should open a page for this in the wiki [02:31] will you do it? [02:31] There we can draft questions [02:31] okay cool [02:31] i'll start a new apge [02:32] hold up one sec [02:32] and separate from that, anybody can either roam the #ubuntu channel for frequent questions, the forums, or even make threads like the one you suggested [02:32] good [02:35] https://wiki.ubuntu.com/ubuntu-manual/survey [02:35] tell me your ideas in here and i'll add them to the wiki (so we don't have two people editing the same page) [02:38] refresh the page, i've just added some questions [02:38] ok [02:38] oops screwed up the headers, refresh again now [02:39] well, I have heard of tons of people having problems with their ATI video cards and with pulseaudio [02:39] so we could have a section for hardware problems [02:39] i was sort of meaning for this questionnaire to just be a general thing [02:39] with only a few questions [02:39] oh sorry [02:39] yes [02:39] you know, like it covers the whole concept of the manual [02:39] hm.. so, these questions will be part of some poll to get feedback from the community? [02:39] okay well let's start with what we need to know [02:40] wolter, yeah kind of [02:40] it's also a bit of a promo for the manual, and to get some more feedback from the community [02:40] what do we need to know from users that we don't know already? [02:40] we need to know how highly they value say, getting online, compared to learning about Ubuntu One? [02:40] Well, what i just said may be a topic in the manual [02:41] like a hardware support [02:41] section [02:41] and well, the stuff about pulseaudio could be covered in the troubleshooting section [02:42] that's chapter 4 [02:42] in fact (sorry for taking the topic temporarily elsewhere) i think we should have also a troubleshooting wiki page where we all suggest troubles to shoot described in the final troubleshooting chapter of the manual [02:43] because it wouldn't be intelligent to have problem-solving spread all around the manual [02:43] instead we should have like, "if you have problems with this and that, look for a solution in chapter 8: troubleshooting. Anyway, lets get back to your topci [02:43] let me think of other questions [02:43] about how many questions would you like to have? [02:45] yeah i'll create a troubleshooting page soon [02:46] well 5 - 8 questions [02:46] refresh the page [02:46] tell me what you think [02:47] I think the questions you have there are very useful [02:47] cool [02:47] can you think of anything else? [02:47] hm, but I would include, in the first question, that the topic has to be ubuntu specific [02:47] for example, to avoid stuff like "a how-to-use-audacity tutorial" [02:47] okay [02:47] because there are people in the forums that don't know where they are standing [02:48] let me think of a question myself [02:48] What do you dislike about ubuntu/ [02:48] ? [02:48] maybe? [02:49] Or, if you were to stop using ubuntu, why would it be [02:49] ? [02:50] (also, how about a section in the wiki where we the team suggest potential content?) [02:51] I don't think that question is specific to us [02:51] it's more a general Ubuntu thing, rather than something to do with the manual [02:51] or [02:51] I suppose if we ask that [02:52] and get an overwhelming response like "lack of hardware documentation" then we know we need to make chapter 4 awesome [02:52] is that what you mean? [02:57] refresh the page again, added another couple of questions. I think that's almost all we need, really. Unless you can think of some more, I might go ahead and create the UF thread. [03:10] http://ubuntuforums.org/showthread.php?p=8650191 [03:11] now we wait .... [03:43] look how many people we have actively working on the project: https://edge.launchpad.net/ubuntu-manual/+topcontributors [04:05] yes humphreybc that is what i meant :) [04:05] we could get some important info [04:05] such as, "ubuntu doesn't have an application for ______" [04:06] so if there actually is one, but it is buried deep, we can point that out [04:06] that is, if it is general purpose [04:06] humphreybc, sorry for my unanounced afk-ness [04:06] I had a break from writing chap 5 [04:06] but i am now more oriented than i ever was [04:07] no probs [04:07] I will push something later, like in a couple of hourse or more [04:07] lol, I wish I saw myself on that list [04:08] All i need to do is push my changes to get karma? [04:08] yeah you get branch stuff [04:13] humphreybc, its getting damn good feedback the thread [04:13] nice work [04:13] I am working on 1) of post #5 :) [04:15] i'm going afk right now, see you in an hour or such [04:15] yeah but wolter an admin moved our thread to the community cafe [04:15] I've emailed the forum council to find out why [05:15] hmm.. how about that.. the ubuntu pocket guide uses the corner strip to declare the version of ubuntu it is for [05:18] humphreybc, have you thought about contacting the ubuntu pocket guide author? === brishu is now known as angelus [05:34] Oh hi brishu, I read your post in the forums [05:35] Did you find out about the manual this way [05:35] o angelus sorry [05:35] wolter, yup ... [05:35] Good [05:35] are you going to help out? [05:35] i hope so ... [05:36] im looking at it and seeing if there is anything i can tackle .. [05:36] angelus, i am working in a big chapter.. chapter 5 [05:36] you know where to find the table of contents? [05:37] gimme a second to get there [05:38] i'm at the chapter 5 page right now ... you are doing software packaging in Ubuntu am i correct ? [05:38] yes [05:39] a lot of people have suggested us to go big on that section [05:39] and the good thing is, its something really easy [05:40] yup i would say so ... especially since you can do thhe software management center ... [05:41] err ... ignore that [05:42] i meant ... i can help out with the Software Center ... as well as little bit on How to add repositories the GUI way on to the software sources .. , [05:43] id say go the vi /etc/apt/sources.list ... but i think there was an agreement to not get into too much of the terminal/CLI stuff till later in the book am i correct ?? [05:53] yes well [05:53] I am writing for both methods sometimes [05:53] but without getting into detail [05:54] however, if the team wants me to wipe those parts off I will [05:54] * humphreybc is talking to the Ubuntu Community Learning Project on how we can get their support for the manual [05:56] https://wiki.ubuntu.com/Learning [05:59] oh nice [06:01] * humphreybc the Learning project is officially backed by Canonical [06:04] hmm.. why can I not use uline? [06:05] what's uline? [06:06] underline, according to the wikibook [06:06] hmm [06:06] I may have to review the writing format guidelines [06:06] maybe it's deprecated [06:06] Is underline not used? [06:06] oh [06:06] i just use bold [06:06] I am using underline for addresses [06:06] where abouts/ [06:06] like Applications > Administration > Software Sources [06:06] what should I use? [06:06] and for file addresses [06:06] as in /etc/apt/sources.list [06:07] not sure [06:08] wolter, i would italicize the addresses, or put them in a monospace [06:08] yeah, i will italize while I test [06:08] I think this things should be defined, if not already [06:09] they might be [06:09] talk to joe? [06:10] wolter, i have the Ubuntu Pocket Guide in front of me and they are italicizing the Menu Addresses(i.e. Applications->Games->Tertis) [06:11] and monospace w/ dotted underline for folder addresses (/home) [06:11] i recommend doing Parent → Child → etc [06:11] well, rather, the latex equivalent of these [06:12] also, since Software Sources already lets ppl edit the sources list, i don't think there's a strong need to tell ppl to edit a file manually... [06:14] IlyaHaykinson, but the easiest way to edit the sources normally is sudo nano /etc/apt/sources.list, which we will need the terminal for ... [06:16] IlyaHaykinson, yeah, but I am just letting them know that software sources edits that file, in case they want to do anything with it... do you think I should not mention that? [06:16] id say a blurb on how to do it on the GUI, then a Link to the editing sources.list section(if we have one), for those interested [06:17] s/blurb/section [06:17] hm, i wouldn't mention it. every tool in the GUI edits some file or another. [06:17] brishu, well, we are not basing our manual on the ubuntu pocket guide [06:17] sorry ... [06:17] haha, no problem [06:17] i would avoid discussing manual editing of things unless that's really the only way to do something [06:17] or unless it's vital for troubleshooting [06:17] I also think that whoever is making the style definitions should make a single \thing{} for command lines [06:18] it's like a beginner's manual for Windows trying to direct people (even optionally) into the Registry [06:19] talk to jmburgess about style guide [06:19] ok [06:20] or dutchie [06:20] there should probably be two different code commands -- one for inline filenames etc, and one for actual snippets (i.e. standalone code sections or the like) [06:20] lol, the last times i have tried to install something through software center I have not been able to do it without the authetification thing bothering me === \vish is now known as vish [06:23] what latex editors do you use? [06:24] so IlyaHaykinson you would say to not touch the details much when writting the manual? [06:26] hm. my preference is for a medium level of detail -- not just tell people to use an application, but point them to a particular screen; explain the contents of the screen, but not go into telling people about every single button. [06:27] ok [06:27] basically, tell them how to do the most common things so that it's possible to follow along. and then hint or make a cursory mention of the other, slightly more advanced things. [06:27] and what latex editor do you use? [06:27] at least that's how i would approach it. [06:27] oh. i use emacs. [06:27] i guess i could as well use gedit here. i treat it as pure text, basically. [07:17] what can I do when there is a "text conflict" in a file? [07:20] nvm [07:20] bzr resolve FILE (for the record) [07:53] everyone check Planet Ubuntu in about 10 minutes [07:54] wow nice [07:55] I think you will be very pleased :) [07:58] is it in the fridge? [07:58] or some other blog? [08:00] I saw a bullet in the fridge in the Ubuntu Weekly Newsletter #175 that says Ubuntu Manual Project [08:08] http://planet.ubuntu.com/ [08:08] scroll down a wee bit [08:15] the picture (is it the proposed-cover?) looks awesome. :) [08:17] yes it's a proposed cover [08:17] one of many proposed ones! [08:19] kool :) ... [08:21] add your feedback if you like [08:22] https://wiki.ubuntu.com/ubuntu-manual/Screenshots [08:27] humphreybc, nice!! [08:27] my lynx :) [08:27] indeed! [08:29] humphreybc, this feels so nice.. the project coming out so well [08:31] yep we're doing good [08:32] although I can't help but feel we're not getting the content done.... maybe it's just me because I haven't written in about a week [08:32] I hope it's not "all talk but no action" kind of thing [08:55] might pay to have a look at this: https://wiki.ubuntu.com/Training/PDFs [08:57] well, I have done a big portion on chap 5 [08:57] its already on the branch [08:57] for good :) [08:57] this bzr tool is amazing [09:05] man wolter, nice work! [09:06] do you think so? [09:06] :) [09:06] yeah i will have a read soon! [09:07] do have a look at that link i posted up above [09:08] we can't copy it tho [09:09] oh haha, i thought you had read it and that was why you said "nice work!" [09:09] lol [09:10] should I get student? [09:13] wow that document is big [09:20] hm.. i could even help translate that book to spanish [09:20] that'd give me karma too :) [09:21] you could [09:21] student english yea [09:21] 60mb i know [09:21] 357 pages [09:21] it's a paid-for manual written about Ubuntu 8.04 [09:21] we can't copy it, it would be illegal [09:22] and we don't want to either [09:26] yeah [09:41] okay wolter i'm going to have a read now [09:41] good [09:41] cant wait for your feedback [09:41] I don't know if I'm making it too long or if its just nice [09:42] I'll add comments as I go in the tex file and then push it through for you [09:44] nice :) [09:50] i might assign myself as the editor for chapter 5 :) [09:51] good :) [10:01] I have written a testimonial for you .. hope it helps you get into the members board whenever you want to [10:02] awesome I just saw that, i'll read it in a sec - almost done adding comments to chapter 5 :) [10:08] * humphreybc just pushed up a new revision with changes [10:09] good [10:10] have a look :) [10:11] nice testimonial wolter, much appreciated :) [10:11] if you ever go for membership then i'll gladly write you one and support you [10:13] yeah well, I would like one membership, but my efforts in the community are not even near to getting me a membership [10:13] maybe someday, I say [10:13] I have read logs of meetings.. those guys are cruel [10:15] they can be yes [10:15] although [10:15] if you're nice to them then they're nice back [10:16] I got declined at my one last year, but they were very nice about it and offered to help me work on my stuff to get my membership sorted. popey was actually one of the guys on the council [10:18] hah [10:18] we're not cruel [10:18] some people apply for membership without even reading the guidelines [10:18] effectively wasting our time [10:19] oh yeah i know [10:19] a lot of people have an ill-informed idea of what membership is and means [10:19] indeed [10:19] so apply without really any experience :S [10:19] I might apply around june or something [10:19] I've even had people message me asking what is the absolute minimum they need to do to get membership [10:19] depends how this manual pans out [10:20] because all they want is the @ubuntu.com email address [10:20] which fails to see the whole point of membership [10:20] indeed. I read the article in this weeks' newsletter about membership which might clear some stuff up [10:21] when do you think i should be ready to apply popey? [10:21] thats impossible to answer [10:21] heh [10:22] haha, the @ubuntu.com email address was one big reason why I wanted the membership [10:22] impossible? so it's actually harder than time travel? [10:22] and because it is not what it is all about is basically why I have not wasted your time ;) [10:22] wolter: nice [10:22] the whole point of membership is to reward significant and sustained contribution to the project [10:22] humphreybc, I would read the log of the meeting when they rejected you [10:22] it's not a badge [10:23] and actually try to think how would they act now with all your work [10:23] so the goal should be to contribute [10:23] the goal should not be membership [10:23] popey, indeed [10:23] heh well that's what i'm doing, i just need to do more xD [10:23] i didnt apply until a couple of years after I started contributing [10:23] I can't lie saying I did not want an @ubuntu.com email address, which is my point haha [10:24] wolter: what do you think of the feedback? [10:24] (just getting on topic again) [10:25] humphreybc, I agree with 95% of it [10:25] I will start working on the implementation tomorrow [10:26] humphreybc, I disagree in that we should not show terminals until the second part of the manual [10:26] I think we should provide a slight description on how to do certain things [10:26] and then link to chap8, in case the reader does not understand [10:26] but of course, the manual is yours and I will honor your desicion [10:27] decision* [10:27] I mean, its ours, but I still do [10:27] Hm so, I will go to sleep now [10:28] It is very late. Perhaps the day I have stayed up the longest time. Its 4:30 AM here and I am starting to feel like a miscarriaged person [10:28] So, good-bye. Sorry for my ranting and, if you have anything to say, make good use of the memoserv [10:28] you know.. /msg memoserv help [10:28] bye all. [10:32] so brishu, who are you? [10:35] dutchie, ping [10:41] * humphreybc can't believe that the software center idea was started over 4 years ago! [10:41] https://wiki.ubuntu.com/SoftwareCenter?action=show&redirect=SoftwareStore [11:10] dutchie: ping [11:26] right i'm off to bed now fellas [11:26] night [15:26] 99 unread messages.. guys?? [16:08] Chapter 5 -> "Synaptic Package Manager" This is removed from lucid. [16:09] !ping [16:09] Here I am, brain the size of a planet and you expect me to respond to a ping? How depressing. [17:58] pererik87: What's the problem? [18:54] Hi all [18:54] check out the main forums page [18:54] http://ubuntuforums.org/ [18:57] nice :) [18:57] hmmm [18:57] I am concerned about the amount of focus and drive you're putting on getting the manual on the cd [18:58] oh? [18:58] how so [18:58] considering no other application or data gets _considered_ for inclusion on the cd until it at least _exists_! [18:58] :) [18:58] fact is right now the manual doesn't exist (in terms of completeness) [18:58] true [18:58] It also puts pressure on the ubuntu project [18:59] because you're going round asking people a question to which the answer will almost certainly be "yes" [18:59] what do you mean? [18:59] well, what I'm saying is get it written first and foremost [18:59] then packaged [18:59] tested [18:59] then request inclusion on the cd [19:00] Right but by then it will be too late for Lucid [19:00] or rather, inclusion into the "main" section of the repo [19:00] Sure I understand what you mean, that would be fine if the project was started maybe 6 months ago [19:00] but the problem with the way you're doing it now (and this is my opinion) is that you are putting pressure on the project [19:01] but thats not necessarily a bad thing [19:01] by going round getting people to "me too" a bug , and +1 a forum post [19:01] it is if the manual doesnt get finished in time [19:01] how so? I would think that I'm putting pressure on our project, more than Ubuntu itself. [19:01] And the manual will be finished in time, I can guarantee it. [19:01] you cant [19:01] I know that's a bold thing to say [19:01] you absolutely cant [19:01] what if you're hit by a bus tomorrow? [19:02] Have you been following the branch? [19:02] yes [19:02] its not about that [19:02] enthusiasm counts for a lot! [19:02] as does the amount of work you've done [19:02] but just hear me out a moment [19:02] Well I'd like to think i'm safer than that, and besides, we've got people who could quite easily take over from where I left off if something did go wrong. [19:02] Sure i'll listen [19:02] ok [19:03] lets suppose you don't get one of the steps complete, whether that is completing the manual itself (which may happen), packaging it, or more importantly getting it into main. [19:03] if you get it into main then someone needs to be responsible for its maintenance [19:03] and _then_ and only then, there's the option of getting it on the CD [19:03] right - it's a long shot, I know [19:04] sure, and I'm not saying it wont happen [19:04] my concern is the amount of focus on getting it on the cd puts pressure on ubuntu because... [19:04] even _if_ you did all those things, what if the project said "no" [19:04] for whatever reason [19:04] the project would look like prize assholes because you've rounded up a posse of people who say it should be on the cd [19:04] and thats not the way ubuntu works [19:04] we dont vote for what goes on the cd [19:05] I realize that. Being on the CD isn't the be all and end all of our project [19:05] exactly [19:05] but it's the 2nd question on your forum post [19:05]