[16:02]  * pleia2 waves
[16:02] <pleia2> hello everyone :) bright and early here in California
[16:03] <pleia2> (actually, not so bright, it's raining)
[16:03] <pleia2> welcome to Ubuntu Documentation Day! We'll have 6.5 hours of sessions here in the Classroom about Ubuntu Documentation
[16:04] <pleia2> if you're not already, you may join #ubuntu-classroom-chat as well to ask questions and chat with other attendees
[16:04] <pleia2> questions should be in the form of:
[16:04] <pleia2> QUESTION: Do you like Ubuntu?
[16:04] <pleia2> so the ClassBot can pick them up :)
[16:04] <pleia2> anyone want to give it a try?
[16:04] <ClassBot> knome asked: Is Xubuntu the best flavor?
[16:05] <pleia2> haha, it depends on who you ask :)
[16:05] <ClassBot> belkinsa asked: What favor of Ubuntu is the best?
[16:05] <pleia2> they're all wonderful!
[16:05] <pleia2> alright, so that's questions
[16:05] <pleia2> the schedule today is as follows:
[16:06] <pleia2> 17:00 UTC Getting started contributing to Desktop docs with godbyk
[16:06] <pleia2> 18:00 UTC Getting started contributing to Server docs with dsmythies
[16:06] <pleia2> 19:00 UTC Getting started contributing to the Wiki docs with belkinsa
[16:06] <pleia2> 20:00 UTC Getting started contributing to Manual with godbyk (again! busy guy)
[16:07] <pleia2> 21:00 UTC Ubuntu Manual versions explained with tacorwin and patrickdickey
[16:07] <pleia2> the full schedule is here, along with time zone conversions from UTC: https://wiki.ubuntu.com/DocumentationTeam/Classroom
[16:08] <pleia2> now, this session is an introduction to docs, which shall serve as sort of a quick start to everything else that folks will be exploring today
[16:08] <pleia2> I'll go through each of them quickly, syncing up with where they land on the schedule
[16:08] <pleia2> feel free to ask questions, but anything complicated is probably best left for the person giving the session about that particular topic, since they're the experts :)
[16:09] <pleia2> first up, Desktop docs!
[16:09] <pleia2> the Desktop docs are shipped on every Ubuntu Desktop install
[16:10] <pleia2> they're also published to help.ubuntu.com, so the latest official desktop docs can be found here: https://help.ubuntu.com/13.10/ubuntu-help/index.html
[16:10] <pleia2> this makes them pretty important to get right, and since everyone who works on documentation in Ubuntu is an unpaid volunteer, we could always use the help with all aspects
[16:11] <pleia2> the team commits to updating this documentation every cycle
[16:12] <pleia2> on the technical side, the documentation is written in a markup language called "Mallard" (the same as what GNOME uses) and it lives at lp:ubuntu-docs which can be accessed via the revision control system bazaar (bzr)
[16:12] <pleia2> godbyk will be giving the full tour in about 38 minutes
[16:13] <pleia2> next up we have server documentation
[16:13] <pleia2> this documentation is specific to servers running Ubuntu and is separate from the desktop documentation
[16:14] <pleia2> just like desktop docs, the team is committed to releasing this every cycle
[16:14] <ClassBot> knome asked: Do flavors ship documentation, are they published online and do they also use Mallard and BZR?
[16:14] <pleia2> many flavors do ship documentation, but they select the tools they use to write and publish, I'll get to that toward the end :)
[16:15] <pleia2> unlike desktop docs, server docs are not shipped with installed versions of Ubuntu server and instead are just published on help.ubuntu.com
[16:15] <pleia2> they're available there as html and pdf as you can see in the latest release here: https://help.ubuntu.com/13.10/index.html
[16:16] <pleia2> these docs are written in DocBook, and are also available via bzr at lp:serverguide
[16:16] <pleia2> DocBook is a pretty standard tool for writing documentation in open source projects, so many folks are already familiar with it
[16:18] <pleia2> now, beyond these "official" documentation types in the core Docuemtation team, we also have docuementation that's maintained on the wiki
[16:18] <pleia2> everything under /community at help.ubuntu.com is actually a wiki
[16:18] <pleia2> starting here: https://help.ubuntu.com/community
[16:18] <pleia2> this can be edited by anyone in the community, at any time, and there are no set deadlines or freezes for when it should be completed
[16:19] <pleia2> as such, it's a much more "living" document that the community maintains, and while there is a team to keep an eye on things, it's not strictly updated every cycle
[16:20] <pleia2> it's also not shipped with Ubuntu or anything, so it's more of an online reference
[16:20] <pleia2> to get started working with this, all you need is a web browser and a launchpad account :) see here for getting started: https://wiki.ubuntu.com/DocumentationTeam/Wiki
[16:21] <pleia2> wiki syntax is easier to learn than DocBook or Mallard, so a lot of folks enjoy starting here
[16:22] <pleia2> ah, should clarify, a launchpad account linked to Ubuntu One account (if you sign up for launchpad today it's automatic, but if you have an older account it might not be), see: https://help.ubuntu.com/community/WikiGuide/Registration
[16:23] <pleia2> the wiki also allows you to create new articles for things that aren't documented, and improve existing documents when you find errors, so it's a low barrier way to get involved
[16:23] <pleia2> there's also the Ubuntu Manual project
[16:23] <pleia2> the work the Ubuntu Manual does is to present a low-cost (or free pdf) printable Ubuntu book for users, their site is at http://ubuntu-manual.org/
[16:24] <pleia2> it's structured differently than the official desktop documentation because it's in book form, but the manual covers similar topics
[16:24] <pleia2> the manual team has also been committed to releasing every cycle
[16:25] <pleia2> the Manual is written in LaTeX and then exported to pdf and to online book print shops in whatever format they require
[16:26] <pleia2> they also use bzr to track revisions
[16:26] <pleia2> one of the things this team did early on was work to make it as easy as possible for contributors can help out, as you can see from their nice, clean get involved page: http://ubuntu-manual.org/getinvolved
[16:27] <pleia2> so that's all the documentation that's focused on Ubuntu specifically - it's a lot! and we have a pretty small team for all of these
[16:28] <pleia2> beyond that, some of the flavors of Ubuntu maintain their own documentation too
[16:29] <pleia2> Xubuntu, for instance, has documentation that's written in DocBook and also lives on launchpad
[16:29] <ClassBot> ahoneybun asked: are other flavors of ubuntu going to talk?
[16:30] <pleia2> unfortunately not! but from my experience xubuntu and kubuntu (the two that maintain docs) are friendly folks and can point you in the right direction
[16:31] <pleia2> we'll work to get some flavor representatives in for our next Doc day :)
[16:31] <pleia2> these documentation teams run pretty independently from Ubuntu, so they can choose their tools and publishing mechanisms
[16:32] <pleia2> for Xubuntu the documentation is published on http://docs.xubuntu.org/ and shipped with each release
[16:35] <pleia2> oh and xubuntu docs live on lp at lp:xubuntu-docs
[16:36] <pleia2> and since we don't have a specific session for flavors, ahoneybun is here to give us some info about kubuntu documentation :)
[16:36] <ahoneybun> Hello all I am here for the Kubuntu Docs Team
[16:36] <ahoneybun> 'Docs" = Documentation
[16:37] <ahoneybun> Currently we have moved out docs over to http://userbase.kde.org/Kubuntu where you would need to log in here https://userbase.kde.org/index.php?title=Special:OpenIDLogin&returnto=Kubuntu
[16:38] <ahoneybun> It is based on MediaWiki vs MoinMoin that wiki.ubuntu.com uses
[16:39] <ahoneybun> Once we get the docs nice, perfect for release we export it into HTML then to DocBook for the khelpcenter to import
[16:40] <ahoneybun> we do use launchpad for a few things but not as much as say xubuntu at lp:kubuntu-docs
[16:41] <ahoneybun> and we have a docs website at http://docs.kubuntu.org/Kubuntu/KubuntuDocs.html but we are working on getting a way to create a snapshot at each release to push to that site
[16:42] <ahoneybun> Right now at http://userbase.kde.org/Kubuntu we need translators to make the docs the best and most available to everyone :)
[16:43] <pleia2> thanks ahoneybun
[16:43] <ahoneybun> no problem :)
[16:44] <pleia2> other flavors tend to either rely upon upstream, or have minimal documentation for specific tasks either on the wiki or on their website, like Edubuntu: https://edubuntu.org/documentation
[16:44] <pleia2> so participating in upstream documentation is highly recommended as well :)
[16:45] <pleia2> upstream == from projects that the distribution uses, like lxde or gnome
[16:46] <pleia2> they also rely heavily (or exclusvely) on volunteers, so documentation everywhere always needs help from the community
[16:47] <pleia2> finally, I also want to mention that the Ubuntu community also has wiki.ubuntu.com - which is not for user documentation, this tends to be confusing for a lot of people, it's actually a teams wiki that should be used by community members for project coordination and how-tos related to getting involved with their projects
[16:49] <pleia2> and that's all I have for this whirlwind tour of documentation :) in 10 minutes or so we'll have godbyk give you a more in depth tour of the desktop docs, and again the full schedule is here: https://wiki.ubuntu.com/DocumentationTeam/Classroom
[16:49] <pleia2> I was asked by dsmythies that if you are attending the server session later, that you install some packages with:
[16:50] <pleia2> sudo apt-get install bzr docbook docbook-xsl xsltproc libxml2-utils yelp-tools yelp-xsl fop gnome-doc-utils make
[16:50] <ClassBot> There are 10 minutes remaining in the current session.
[16:51] <pleia2> this will pull in what you need to contribute to server docs, and pulls in a bunch of dependencies so it'll take a few minutes
[16:55] <ClassBot> There are 5 minutes remaining in the current session.
[16:57] <ClassBot> gulundin asked: is some deadline set on the official documentation for the Trusty Tahr release?
[16:58] <pleia2> great question, and there is!
[16:58] <pleia2> grabbing the link for our release schedule
[16:59] <pleia2> https://wiki.ubuntu.com/DocumentationTeam/ReleaseSchedule
[16:59] <pleia2> DocumentationStringFreeze is coming up quick, on March 20th, so it needs to be done by then
[17:00] <ClassBot> Logs for this session will be available at http://irclogs.ubuntu.com/2014/03/02/%23ubuntu-classroom.html following the conclusion of the session.
[17:00] <godbyk> Hello, everyone, and welcome to the classroom session for Ubuntu desktop documentation.
[17:01] <godbyk> If you have any questions during this session, please ask in #ubuntu-classroom-chat. Don't forget to prefix your question with "QUESTION:"
[17:01] <godbyk> The upcoming sessions are:
[17:01] <godbyk> 18:00 UTC Getting started contributing to Server docs with dsmythies
[17:01] <godbyk> 19:00 UTC Getting started contributing to the Wiki docs with belkinsa
[17:01] <godbyk> 20:00 UTC Getting started contributing to Manual with godbyk
[17:01] <godbyk> 21:00 UTC Ubuntu Manual versions explained with tacorwin and patrickdickey
[17:02] <godbyk> As pleia2 mentioned in the previous session, the Ubuntu desktop docs are published each cycle along with Ubuntu.
[17:02] <godbyk> They are present in two places:
[17:02] <godbyk> 1. On your desktop (just search for 'help' in the Dash), and
[17:02] <godbyk> 2. Online at https://help.ubuntu.com/13.10/ubuntu-help/index.html.
[17:03] <godbyk> In this session, I'll give you a brief overview of how you can help contribute to the desktop documentation.
[17:04] <godbyk> For those of you who are eager to dive right in (and not wait on my slow typing!), you can follow our getting started guide at https://wiki.ubuntu.com/DocumentationTeam/SystemDocumentation/UbuntuDesktopGuide.
[17:05] <godbyk> To start working with the desktop documentation, you should first join our contributors team: https://launchpad.net/~ubuntu-doc-contributors
[17:05] <godbyk> And subscribe to our mailing list.
[17:05] <godbyk> You can help us by reviewing the current documentation online at https://help.ubuntu.com/13.10/ubuntu-help/index.html.
[17:06] <godbyk> If you find an error—incorrect information or typos—there are a few ways of correcting it:
[17:07] <godbyk> 1. Email the list. This is probably the easiest way as others will do most of the work. Just notifying us of these errors helps us enormously!
[17:07] <godbyk> 2. File a bug on Launchpad. You can file a bug against the ubuntu-docs project at https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+filebug.
[17:08] <godbyk> Be sure to include a link to the page you found the bug in and be specific about what the error is.
[17:08] <godbyk> 3. Create a patch and file a merge proposal.
[17:08] <godbyk> If you're feeling adventurous (and we hope you are!), you can download the documentation code yourself, fix the error, and submit a patch.
[17:09] <godbyk> After you've contributed to the project for a while, you can apply to become a "committer".
[17:09] <godbyk> Committers can commit code directly to the main bzr repository without having to create a merge proposal.
[17:09] <godbyk> They also help review and approve merge proposals from contributors.
[17:10] <godbyk> The Ubuntu desktop documentation is written in a markup language called Mallard.
[17:10] <godbyk> Mallard is designed specifically for topic-based documentation (as opposed to say, books or lengthier publications).
[17:11] <godbyk> En example Mallard document looks like this: http://bazaar.launchpad.net/~ubuntu-core-doc/ubuntu-docs/trusty/view/head:/ubuntu-help/C/unity-launcher-intro.page
[17:11] <godbyk> When we convert this Mallard document to HTML, it looks like this: https://help.ubuntu.com/13.10/ubuntu-help/unity-launcher-intro.html
[17:11] <godbyk> If you search the Dash for 'help', it will bring up an offline viewer known as Yelp.
[17:11] <godbyk> Yelp can read and display Mallard pages directly without converting them to HTML first.
[17:13] <godbyk> Next, I'd like to walk you through the process of downloading our documentation source code. This process will also give you a head start on any server guide work you'd like to do.
[17:13] <godbyk> But first, are there any questions so far?
[17:15] <godbyk> Okay, let's dive in!  If you have questions along the way, feel free to ask them in #ubuntu-classroom-chat. Don't forget to prefix your question with "QUESTION:".
[17:15] <godbyk> We've written a short guide to getting started with the desktop docs at <https://wiki.ubuntu.com/DocumentationTeam/SystemDocumentation/UbuntuDesktopGuide>.
[17:15] <godbyk> I'll be walking you through this process.
[17:16] <godbyk> !q
[17:16] <godbyk> jose: You can find out all about Mallard at http://projectmallard.org/.
[17:17] <ClassBot> jose asked: where can I learn Mallard?
[17:17] <godbyk> jose: We may not have time to cover much of Mallard in this sessions, but if there's interest, we could hold a future classroom session about it.
[17:19] <godbyk> Okay, for the first step, you'll need to install a few packages:
[17:19] <godbyk> $ sudo apt-get install bzr xsltproc libxml2-utils yelp-tools yelp-xsl
[17:19] <ClassBot> ahoneybun asked: how well does mallard handles translations?
[17:20] <godbyk> ahoneybun: Mallard handles translations pretty well. When we're finished updating the docs, we generate a translation template file and upload it to Launchpad.
[17:21] <godbyk> ahoneybun: Translators can then translate the documentation. The docs team will periodically upload the translations to the help.ubuntu.com website.
[17:21] <godbyk> Next, we'll need to generate an SSH key.
[17:21] <godbyk> First, check to see if you already have an SSH key:
[17:22] <godbyk> Open a terminal, and type:
[17:22] <godbyk> $ ls ~/.ssh/id_rsa.pub
[17:22] <godbyk> If it lists the file, then you already have an ssh key and can skip the next step.
[17:23] <godbyk> If you don't already have a key (it says "No such file or directory"), then we'll create one with the following command:
[17:23] <godbyk> $ ssh-keygen -t rsa
[17:23] <godbyk> It's easiest to just press Enter to accept the defaults to all of the questions.
[17:23] <godbyk> You may enter a password for additional security if you like, but it's not required.
[17:24] <ClassBot> jose asked: how do I open a terminal?
[17:24] <godbyk> jose: You can open a terminal by searching the Dash for 'Terminal' or by pressing Ctrl+Alt+T on your keyboard.
[17:24] <ClassBot> belkinsa asked: Is there a way to copy and paste those commands in the terminal for the ese?
[17:25] <godbyk> belkinsa: You can copy and paste these commands from the chat window or from our web page at https://wiki.ubuntu.com/DocumentationTeam/SystemDocumentation/UbuntuDesktopGuide.
[17:25] <godbyk> belkinsa: In your terminal, press Ctrl+Shift+V to paste the text.
[17:25] <godbyk> belkinsa: Be sure to leave out the initial $. That's just showing the prompt.
[17:26] <godbyk> Next, we'll need to upload the SSH key to Launchpad.
[17:26] <godbyk> Open your favorite web browser and head to https://launchpad.net/~/+editsshkeys
[17:27] <godbyk> If you don't yet have a Launchpad account, create one and then revisit the URL.
[17:28] <godbyk> If you already have a Launchpad account, log in.
[17:28] <godbyk> Scroll down to the bottom of the page and you'll see a large text box below the "Add an SSH key" heading.
[17:29] <godbyk> We'll need to paste the SSH key we just created into this box.
[17:29] <godbyk> In your terminal, run:
[17:29] <godbyk> $ gedit ~/.ssh/id_rsa.pub
[17:30] <godbyk> Copy the entire contents of this file and paste them into the textbox on the Launchpad page. Click the Import Public Key button.
[17:30] <godbyk> This SSH key allows us to communicate securely with Launchpad.
[17:30] <godbyk> Next, we'll set up bzr.
[17:31] <godbyk> bzr (Bazaar) is the version control system that Ubuntu uses for its projects.
[17:31] <godbyk> bzr maintains a history of all the changes we make to the documentation.
[17:31] <godbyk> This allows us to roll back any accidental changes and to see our progress as we update the documentation.
[17:32] <godbyk> First, we'll need to tell bzr who we are.
[17:32] <godbyk> We'll tell bzr which name and email address we'd like it to show when we submit code to Launchpad.
[17:33] <godbyk> Run the following command:
[17:33] <godbyk> $ bzr whoami "Kevin Godby<EMAIL_ADDRESS>[17:33] <godbyk> Replace 'Kevin Godby' with your full name and<EMAIL_ADDRESS>with your own email address.
[17:33] <godbyk> Don't forget the quotation marks.
[17:33] <godbyk> And don't forget to put your email address in < and > (like I failed to).
[17:33] <godbyk> $ bzr whoami "Kevin Godby<EMAIL_ADDRESS>[17:34] <godbyk> Next, we'll need to tell bzr what our Launchpad username is:
[17:34] <godbyk> $ bzr launchpad-login godbyk
[17:34] <godbyk> If you've forgotten your Launchpad username, you can find it by visiting https://launchpad.net/~ in your web browser.
[17:35] <godbyk> Launchpad will redirect you to your Launchpad account page. The part of the address after the tilde (~) is your username.
[17:35] <godbyk> Finally, we can download a copy of the documentation using bzr.
[17:35] <godbyk> This step can take a little bit of time because we're downloading the entire history of all of the changes made to the documentation over the years.
[17:36] <godbyk> In your terminal, run the following command:
[17:36] <godbyk> $ bzr branch lp:ubuntu-docs
[17:37] <godbyk> Are there any questions so far?
[17:39] <godbyk> Since it will take a little while to download the documentation, we'll explore the files online.
[17:39] <godbyk> If you visit http://bazaar.launchpad.net/~ubuntu-core-doc/ubuntu-docs/trusty/files with your web browser, you can see a list of all of the files and directories in the bzr repository.
[17:39] <godbyk> These are the files that are being downloaded by bzr.
[17:40] <godbyk> The Mallard files that we write for the desktop documentation live in the ubuntu-help/C/ subdirectory.
[17:40] <godbyk> Click on ubuntu-help and then C to find .page files.
[17:41] <godbyk> The .page files contain the Mallard markup for the documentation.
[17:42] <godbyk> Let's take another look at the example Mallard file I showed you earlier: http://bazaar.launchpad.net/~ubuntu-core-doc/ubuntu-docs/trusty/view/head:/ubuntu-help/C/unity-launcher-intro.page
[17:42] <godbyk> Once bzr has finished downloading all the files, you can open this file on your computer by running the following command in your terminal:
[17:43] <godbyk> $ gedit ubuntu-docs/ubuntu-help/C/unity-launcher-intro.page
[17:43] <godbyk> If you spot an error in this file, you have a few options for correcting it:
[17:44] <godbyk> 1. Email the ubuntu-docs mailing list about it and someone there will fix it.
[17:44] <godbyk> 2. File a bug report at https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+filebug and someone there will fix it.
[17:45] <godbyk> 3. Make the changes yourself.
[17:45] <godbyk> The first two options are fairly self-explanatory, so let's explore the third option.
[17:45] <godbyk> You can open the offending .page file in gedit, make the desired changes, and save the file.
[17:45] <godbyk> Now you have the corrected .page file on your own computer.
[17:46] <godbyk> The next step is to get your changes back to Launchpad so they can be incorporated into the main documentation repository.
[17:47] <godbyk> First, you'll need to commit your changes to the bzr repository.
[17:47] <godbyk> Run the following command:
[17:47] <godbyk> $ cd ~/ubuntu-docs
[17:47] <godbyk> $ bzr commit -m 'A brief description of your changes goes here'
[17:48] <godbyk> The 'bzr commit' command will commit your changes. The text between the apostrophes should be a short description of the changes you've made.
[17:48] <godbyk> Next, you'll need to upload your changes to Launchpad.
[17:48] <godbyk> Run the following command:
[17:49] <godbyk> $ bzr push lp:~username/ubuntu/trusty/ubuntu-doc/my-first-change
[17:49] <godbyk> where you've replaced 'username' with your own username and 'my-first-change' with a couple words describing your change (no spaces allowed).
[17:50] <ClassBot> There are 10 minutes remaining in the current session.
[17:50] <godbyk> Finally, you'll need to create a 'merge proposal' to alert the ubuntu-docs team of your proposed changes so they can be reviewed.
[17:50] <godbyk> Run:
[17:50] <godbyk> $ bzr lp-propose
[17:51] <godbyk> This command will open your web browser to the merge proposal page on Launchpad. Provide a brief description of your proposed changes and submit the merge proposal.
[17:51] <godbyk> The ubuntu-docs team will be notified of your merge proposal.
[17:51] <godbyk> They will review your proposed changes and either accept them or discuss them with you.
[17:52] <godbyk> We've only had a short time to get an overview of the Ubuntu desktop documentation and how you can join the team.
[17:53] <godbyk> If you'd like more information, feel free to email us on our mailing list at<EMAIL_ADDRESS>or chat with us in our IRC channel at #ubuntu-doc.
[17:53] <godbyk> We hope to hear from you soon!
[17:53] <godbyk> We have a few minutes for some questions.
[17:54] <godbyk> In our next session, dsmythies will discuss the server documentation.
[17:55] <ClassBot> There are 5 minutes remaining in the current session.
[17:58] <dsmythies> to help save time in the sererguide session please do this (if you didn't already), as it might take over 15 minutes:
[17:58] <dsmythies> $ sudo apt-get install bzr docbook docbook-xsl xsltproc libxml2-utils yelp-tools yelp-xsl fop gnome-doc-utils make
[18:00] <ClassBot> Logs for this session will be available at http://irclogs.ubuntu.com/2014/03/02/%23ubuntu-classroom.html following the conclusion of the session.
[18:00] <dsmythies> Hello everyone, my name is Doug Smythies and this is the "Getting Started Contributing to the Serverguide" session.
[18:00] <dsmythies> Over the next hour, and for the Ubuntu Serverguide, we will learn: How to setup a working environment; How to build and verify the HTML and PDF versions; How to create and submit a merge proposal.
[18:00] <dsmythies> Note that I am IRC challenged, and have asked for help from invisbile to you classroom volunteers, whom I would like to thank now, because I will forget at the end.
[18:01] <dsmythies> Could everybody participating please comment in #ubuntu-classroom-chat. And please say if you intend to "participate" or just follow along but not actually "do", as the numbers will dictate how I deliever the material.
[18:02] <dsmythies> Questions are O.K. during this session, but I might not see them right away. Please ask in #ubuntu-classroom-chat. Be sure to prefix it with 'QUESTION:' to ensure that it gets noticed by the classroom robot.
[18:03] <dsmythies> Prerequisites: You should already have a launchpad account, with an uploaded ssh key for the computer you will be using. You should already have bzr installed and setup. Is this O.K or is it a problem for anyone?
[18:04] <dsmythies> Hmmm....
[18:05] <dsmythies> I guess I'll move along then...
[18:06] <dsmythies> We will work on 3 real bug reports, but don't worry they are simple typo bug reports. At this stage we are here to learn about the process and not get lost in some detailed overhaul of a chapter or section.
[18:06] <dsmythies> While what we are covering shouldn't take too long, there might be download delays and such which could result in time pressures for the hour.
[18:07] <dsmythies> First and foremost, we should always have the serverguide "quick how to" page open somewhere on our desktop and as our main reference.
[18:07] <dsmythies> Please open: https://wiki.ubuntu.com/DocumentationTeam/SystemDocumentation/UbuntuServerGuide
[18:07] <dsmythies> and go to the kickstart section.
[18:07] <dsmythies> Second, things are done via the command line, so we always need some sort of terminal window or session open. Go ahead and make a terminal window or open an ssh session now.
[18:08] <dsmythies> Cut and paste the install the software line (even if you think you already have everything installed, there is no harm in checking):
[18:09] <dsmythies> Note: Lyz asked you to do this earlier and I asked awhile ago also.
[18:09] <dsmythies> $ sudo apt-get install bzr docbook docbook-xsl xsltproc libxml2-utils yelp-tools yelp-xsl fop gnome-doc-utils make
[18:10] <dsmythies> This step might take 15 minutes or more, if you do not already have anything installed.
[18:10] <dsmythies> (I am hoping you have done this already, as pleia2 mentioned the command at the end of her session. Although I know some of you might not have been here then.)
[18:10] <dsmythies> O.K.? comment on #ubuntu-classroom-chat as to progress. And note that even if you took Kevin's session just prior to this one, there are an extra couple of packages needed for Serverguide.
[18:13] <dsmythies> Now we are ready to get a local copy of the master files for the Ubuntu Servverguide:
[18:13] <dsmythies> 1.) make a working directory and change to it:
[18:13] <dsmythies> $ mkdir sguide-1404
[18:13] <dsmythies> $ cd squide-1404
[18:14] <dsmythies> 2.) make a local copy (branch) of the master Serverguide files: (put it in the subdirectory called "classroom")(this will take at least 4 minutes.)
[18:14] <dsmythies> $ bzr branch lp:serverguide classroom
[18:15] <dsmythies> If it is your first bzr/launchpad interaction, you will see:
[18:15] <dsmythies> The authenticity of host 'bazaar.launchpad.net (<IP_ADDRESS>)' can't be established.
[18:15] <dsmythies> RSA key fingerprint is bla bla bla.
[18:15] <dsmythies> Are you sure you want to continue connecting (yes/no)?
[18:15] <dsmythies> enter "yes"
[18:15] <dsmythies> This step might take 4 minutes or more.
[18:16] <dsmythies> O.K.? comment on #ubuntu-classroom-chat as to progress.
[18:17] <dsmythies> 3.) Now, before we make any changes, check to make sure everything is O.K..That the code builds and that the code validates:
[18:18] <dsmythies> $ cd classroom
[18:18] <dsmythies> $ scripts/validate.sh serverguide/C/serverguide.xml
[18:18] <dsmythies> $ make serverguide-html
[18:18] <dsmythies> $ make serverguide-pdf
[18:20] <dsmythies> While we have worked hard to get rid of exranious messages during compile, there are still a few.
[18:20] <dsmythies> Now have a look at the compiled serverguide. How you actually do this will depend on your setup. I do things on a server and have the drive shared with my Laptop via Samba. If you are using a desktop computer you can use it directly.
[18:21] <dsmythies> The built serverguide will be in the build/serverguide/C sub-directory. Navegate there and open the index.html file. Similarly for the serverguide.pdf file. In both the HTML and the PDF, browse to the Zyntal section.
[18:21] <dsmythies> Note: in the new (Red) theme, sometimes it is not obvious where stuff is in the HTML. With the old (Brown) theme it was easier. (It is under "Remote administration")
[18:22] <dsmythies> If you are just following along and not actually building on your local machine, then go to https://help.ubuntu.com/13.10/index.html and proceed from there.
[18:22] <dsmythies> TIP: Sometimes it is easier to find stuff in the .PDF because you can search the whole document, and then you know where to look in the HTML.
[18:23] <dsmythies> Once we have determined that the unaltered code validates and compiles, we are ready to start making changes.
[18:23] <dsmythies> Let's look at the first bug report we intend to tackle: Please all open a new broswer page and go to bug 1278146
[18:24] <dsmythies> https://bugs.launchpad.net/serverguide/+bug/1278146
[18:24] <dsmythies> O.K.? comment on #ubuntu-classroom-chat that you have opened and read the bug report.
[18:25] <dsmythies> I'll set the bug report status to "In progress". I already assigned myself so as to hold the bug report for this class, but typically you would assign yourself, or maybe you were previously assigned.
[18:25] <dsmythies> I want everybody to click and add themselves to get every e-mail about this bug report (over on the right about 4 or 5 groups down).
[18:26] <dsmythies> First we check our compiled HTML and PDF, so we can verify before and after we fix it. Search for "a serie of"
[18:28] <dsmythies> Now, we have the context of the bug report. This will be useful later.
[18:28] <dsmythies> Close the PDF Serverguide, because (at least on my computer) we can not rebuild it while it is open. Keep the HTML open.
[18:28] <dsmythies> Now we have to figure out where the referenced error is in the source code. (ignoring for the moment, that I already did that and made an entry in the bug report.):
[18:29] <dsmythies> $ cd serverguide
[18:29] <dsmythies> $ cd C
[18:29] <dsmythies> $ grep -n "a serie of" *.xml
[18:29] <dsmythies> you should get this:
[18:29] <dsmythies> remote-administration.xml:451:      <application>Zentyal</application> consists of a serie of packages
[18:29] <dsmythies> So you know line 451 of remote-administration.xml is the line to fix.
[18:30] <dsmythies> O.K.? Was everyone able to identify the issue in the source code?
[18:30] <dsmythies> TIP: Sometimes our grep search fails. Why? Because sometimes there are line breaks in the source code that interfere with the search pattern. If that happens, just move the search pattern a little.
[18:30] <dsmythies> TIP: Notice that in the HTML "Zyntal" is in italics. That likley means that it is surrounded by docbook tags in the source code, and we should not include it in the grep search pattern.
[18:31] <dsmythies> We are ready to make a change to the source code. Use your preferred editor to open remote-administration.xml and go to line 451, make the required change and save the file. I use nano.
[18:33] <dsmythies> O.K.? We'll wait for everybody. (I'm dropping the "comment on #ubuntu-classroom-chat" from here on, assuming you know to. (nobody seems to be doing this anyhow))
[18:34] <dsmythies> moving on...
[18:34] <dsmythies> Always, always validate:
[18:34] <dsmythies> $ cd ..
[18:34] <dsmythies> $ cd ..
[18:34] <dsmythies> $ scripts/validate.sh serverguide/C/serverguide.xml
[18:34] <dsmythies> $ make serverguide-html
[18:35] <dsmythies> $ make serverguide-pdf
[18:35] <dsmythies> And refresh your browser and observe the fixed code. Open the serverguide.pdf file, and observe there also.
[18:35] <dsmythies> Let's do some bzr checks:
[18:35] <dsmythies> $ bzr status
[18:35] <dsmythies> $ bzr diff
[18:36] <dsmythies> aghhh... I see that someone did add themselves to the bug report. Great.
[18:37] <dsmythies> So onto the second bug, one submitted by a translator. bug 1272984 . Flaipe always submits very nice typo bugs with a reference to the source file and line. However, often reports from translators only contain the string reference, and you'll have to figure it out for yourself.
[18:37] <dsmythies> https://bugs.launchpad.net/serverguide/+bug/1272984
[18:39] <dsmythies> The process is the same as the last one. Add your names to be notified about changes to this bug report.
[18:39] <dsmythies> Find the typo in the HTML and PDF documents.
[18:39] <dsmythies> (Hint try the TIP from earlier and find it in the PDF first.)
[18:40] <dsmythies> Ugh Oh.... I have a confusing note in my script. What on earth was I thinking? ....
[18:41] <dsmythies> $ grep -n repostory serverguide/C/*.xml
[18:41] <dsmythies> $ serverguide/C/vcs.xml:199:            <para>Or add the server's project as a remote for an existing git repostory:</para>
[18:41] <dsmythies> $ nano serverguide/C/vcs.xml   (you use whatever editor you prefer)
[18:43] <dsmythies> Always, always validate:
[18:43] <dsmythies> $ scripts/validate.sh serverguide/C/serverguide.xml
[18:43] <dsmythies> $ make serverguide-html
[18:43] <dsmythies> $ make serverguide-pdf
[18:44] <dsmythies> And refresh your browser and observe the fixed code. Open the serverguide.pdf file, and observe there also.
[18:44] <dsmythies> Again, let's do some bzr checks:
[18:44] <dsmythies> $ bzr status
[18:44] <dsmythies> $ bzr diff
[18:45] <dsmythies> One more, another one from Flaipe: bug 1272064
[18:45] <dsmythies> https://bugs.launchpad.net/serverguide/+bug/1272064
[18:46] <dsmythies> Go ahead and do this one yoursleves, without any input from me. (However note that when I sreached the PDF for "the the", I found some other occurances. Normally we would stop and fix those also, but we don't have time right now.)
[18:48] <dsmythies> ... I am doing it also ...
[18:49] <dsmythies> O.K.? Is everybody done?
[18:49] <dsmythies> Did everyone do the bzr checks as the last step? and does everyone get this: http://paste.ubuntu.com/7023049/
[18:50] <dsmythies> Now it is time to wrap this up and put our branch into launchpad. Starting with a commit line. Use the wiki page as a reference. (and use your name and your launchpad account name):
[18:50] <ClassBot> There are 10 minutes remaining in the current session.
[18:50] <dsmythies> $ bzr commit --fixes lp:1278146 --fixes lp:1272984 --fixes lp:1272064 -m 'simple typos; LP: #1278146; LP: #1272984; LP: #1272064; by Doug Smythies'
[18:52] <dsmythies> $ bzr push lp:~dsmythies/serverguide/classroom
[18:53] <dsmythies> this is taking ahile and I might run out of time...
[18:53] <dsmythies> You should also be getting e-mails from the bug reports saying that branches are linked to them.
[18:53] <dsmythies> Now go to your launchpad account under the "code tab" and you should see your code there. Click on it to go there.
[18:53] <dsmythies> You should see the bug reports under "Related bugs" with links to them.
[18:53] <dsmythies> Under recent revisions you should see your just uploaded revision. Click on the revision number, 188.
[18:55] <dsmythies> ... my upload is taking awhile... I'll add my remaining notes here and we'll come back to this is there is time.
[18:55] <ClassBot> There are 5 minutes remaining in the current session.
[18:55] <dsmythies> Click on each of the modified files listed to expand the color differences. Do they make sense? (they should).
[18:55] <dsmythies> Go back to branch summary, either via the link in the top left corner or via the browser back button.
[18:55] <dsmythies> Under "Branch merges" clcik on "Propose for merging"
[18:56] <dsmythies> Enter a description. "Simple typos" will do in this case
[18:56] <dsmythies> Leave blank the spots where it says "optional", they will autofill with the correct information.
[18:56] <dsmythies> Click on the "Propose Merge" radio button at the bottom of the page.
[18:56] <dsmythies> After a short delay you should see a Merge Proposal page with a MP number.
[18:57] <dsmythies> I'll add a comment and "approve" and then also set the status to "approve"
[18:57] <dsmythies> I go to my up to date working branch, and merge in the MP:
[18:57] <dsmythies> $ bzr merge lp:~jdoe/serverguide/classroom
[18:57] <dsmythies> $ bzr commit --fixes lp:1278146 --fixes lp:1272984 --fixes lp:1272064 -m 'simple typos per MP: #XXXXXX; LP: #1278146; LP: #1272984; LP: #1272064; by Jane Doe'
[18:57] <dsmythies> $ bzr push lp:serverguide
[18:57] <dsmythies> Notice the MP automatically got set to a status of "merged"
[18:58] <dsmythies> ( or woul dhave if we actually did this part)
[18:58] <dsmythies> We should also now set the bug reports status' to "fix committed". (which I will complete after the class.)
[18:59] <dsmythies> ... my upload continues... I shdould have done one before and had it ready. Sorry.
[19:00] <belkinsa> Thank you, dsmythies, for your session.  I hope that helps everyone who wants to help out.
[19:00] <dsmythies> The class will switch over in a moment. Thanks.
[19:00] <ClassBot> Logs for this session will be available at http://irclogs.ubuntu.com/2014/03/02/%23ubuntu-classroom.html following the conclusion of the session.
[19:00] <belkinsa> Hey all from snowy Southwest Ohio, welcome to the, "Getting started contributing to the Wiki docs", session.  My name is Svetlana Belkin (A.K.A. belkinsa) and I'm your instructor.
[19:01] <belkinsa> If you have any questions during this session, please ask in #ubuntu-classroom-chat. Don't forget to prefix your question with "QUESTION:"
[19:01] <belkinsa> The upcoming sessions are:
[19:01] <belkinsa> 20:00 UTC Getting started contributing to Manual with godbyk
[19:01] <belkinsa> 21:00 UTC Ubuntu Manual versions explained with tacorwin and patrickdickey
[19:01] <belkinsa> Before I start with my lesson: If you'd like more information, feel free to email us on our mailing list at<EMAIL_ADDRESS>or chat with us in our IRC channel at #ubuntu-doc.  Please use the prefixes: [Desktop],[Server], and [Wiki] when you mail the list.  Each of them are for the three types of docs that we have.
[19:03] <belkinsa> Like what pleia2 said about the Wiki.  We have two types of wikis: the wiki.ubuntu.com where our teams hold pages, and for you the ones who are active and wish to seek the Ubuntu Membership.  The Community Help Wiki contains all of the support pages that don't go into our guides that we have.
[19:03] <belkinsa> The link to the Community Help Wiki is: https://help.ubuntu.com/community
[19:05] <belkinsa> The great thing about the Community Help Wiki is that anyone with a LaunchPad account can edit pages and there is no fear of doing anything wrong since we have wiki admins that approve the changes and the rollback feature.
[19:05] <belkinsa> How to get a Launchpad Account?  Here is how:  https://help.ubuntu.com/community/WikiGuide/Registration
[19:05] <belkinsa> Any questions?
[19:07] <belkinsa> Okay, our example that will be used is that you all (those who wants to learn how to wiki edit) will be creating your every own Userpage that you can use to show when you apply to the Ubuntu Membership.
[19:08] <belkinsa> To do this, first you need to log into the wiki by going to wiki.ubuntu.com.
[19:09] <belkinsa> You should see a Ubuntu logo banner and below it, a menu bar that says "Log in" or "edit", if you are logged in.
[19:09] <belkinsa> If you are not logged in, please click that "Log in" and proceeded to log in with your LaunchPad account.
[19:09] <ClassBot> jose asked: Do both wikis use moinmoin?
[19:10] <belkinsa> Yes, both do.
[19:10] <belkinsa> MoinMoin is a wiki syntax that both wikis use and it's easy to learn.
[19:11] <belkinsa> This link has the syntaxes: https://help.ubuntu.com/community/WikiGuide/Formatting
[19:12] <belkinsa> Okay, once you are logged in.  Go to this page: https://wiki.ubuntu.com/MembershipTemplate
[19:12] <belkinsa> This page contains the template that we will use.
[19:12] <belkinsa> There are two ways to copy and paste this template into a new page.
[19:13] <belkinsa> The first one is to "Edit" the page.  You do this by hitting "edit" on the menu bar under the Ubuntu banner and it should take you to a text editor with the text for the template.  Copy that.
[19:14] <belkinsa> Or you can go to the drop down menu and select "copy".  This should take you a page that says where to copy the page.
[19:14] <belkinsa> I think the first method is the easiest.
[19:15] <belkinsa> Because you need to know where to copy the page.
[19:15] <belkinsa> In the address bar: type in https://wiki.ubuntu.com/<username>.  <useraname> is your username that you use in LaunchPad.
[19:16] <belkinsa> Thanks, jose. Don't use edit to view the source, use the drop down and select 'view raw'
[19:16] <belkinsa> This is for the first method.  ^^^
[19:17] <belkinsa> Once you are at your page, you should see a dialogue telling you that it is not created yet.  Click "create a new page".  This should take you to the editor.
[19:19] <belkinsa> At the editor, paste the template.  There is a menu above the editor.  Select "preview" and it will show you what you have done or you can select "Save" and the page will be saved and you should see a normal looking page without the editor.
[19:19] <belkinsa> Any questions?
[19:20] <belkinsa> Oh, as an example: https://wiki.ubuntu.com/belkinsa This is my page, please use "view raw" to see what I have done.
[19:21] <belkinsa> You can write anything about yourself.  ;)
[19:21] <belkinsa> Okay, now you have the basics of the syntax and how to edit a page.
[19:22] <belkinsa> Now, when you find a page to work on, you can do it right on that page or you can use a page called a "sandbox" page.
[19:23] <belkinsa> These sandboxes are used to play around with pages with out effecting the main one.
[19:24] <belkinsa> To create one, the easiest way to https://wiki.ubuntu.com/<username>/sandbox ( <useraname> is your username that you use in LaunchPad).  Follow the directions as for your userpage to create a blank page to fill.
[19:25] <belkinsa> You can add more pages after the first one by https://wiki.ubuntu.com/<username>/sandbox/<newpage>.
[19:26] <belkinsa> As with all pages, don't forget to save when you are done and preview to extend the lock period.
[19:26] <belkinsa> Any questions so far?
[19:28] <belkinsa> There is a way to see what other users did to the pages and these are called "revisions".
[19:29] <belkinsa> These allow rollbacking to older versions of pages.
[19:29] <belkinsa> Log in which is under the “Ubuntu Wiki” banner. Under the “Ubuntu Wiki”, you should see a menu bar that starts with “Edit”
[19:29] <belkinsa> Next to the 'Edit”, you should see a “Info” button- this will take you to a page called Revision History
[19:29] <belkinsa> Here you can see:
[19:30] <belkinsa> Revision Number (#) - which shows how many revisions the page gone through
[19:30] <belkinsa> Date – which shows when the revision was made
[19:30] <belkinsa> Size – which shows how large the page and/or if there is attachments to the page
[19:30] <belkinsa> Duff - which allows to compare two versions of the same page
[19:30] <belkinsa> Editor – which allows to see who done the last edit
[19:30] <belkinsa> Comment – which allows to see what the editor did, if there is a comment
[19:30] <belkinsa> Action – which allows to view the page without the diff
[19:30] <belkinsa> Clicking on “View” will allow to enter the revision.
[19:31] <belkinsa> If you want to rollback:
[19:31] <belkinsa> Go back to the menu bar under the Ubuntu Wiki banner and find the drop down that is labeled, “More Actions:”.
[19:31] <belkinsa> Scroll down to “Revert to this revision”.
[19:31] <belkinsa> Another page will pop up after section
[19:31] <belkinsa> You can comment on why you doing this
[19:31] <belkinsa> And select “Revert” if you are sure on the choice
[19:31] <belkinsa> Any questions on revisions?
[19:33] <belkinsa> Before I forget about creating new pages: https://help.ubuntu.com/community/WikiGuide/PageCreation.  This page contains a temple if you want to create a new page: https://help.ubuntu.com/community/DocumentationTemplate
[19:34] <belkinsa> If you don't have any expertise on any subject, the Doc team has small tasks for people to do.  These range from proofreading to tagging pages.
[19:35] <belkinsa> https://wiki.ubuntu.com/DocumentationTeam/Wiki/Tasks
[19:35] <belkinsa> Has the tasks.
[19:36] <belkinsa> We also have a tagging system to tag pages: , https://help.ubuntu.com/community/Tag These tags help us to figure out what needs to be deleted or needs fixing.
[19:37] <belkinsa> We might have a Global Jam session(s) for this this year, if we have people wanting to help to clean up the wiki.
[19:37] <belkinsa> Any questions before I move on?
[19:39] <belkinsa> Okay.
[19:40] <belkinsa> The wiki has a way to categorize pages in order for the pages of the same subject mater to stay together.
[19:40] <belkinsa> he format is CategoryCategory where the second is the name of the category
[19:40] <belkinsa> The*
[19:41] <belkinsa> This must be placed on the bottom of the page with “----” before it in one line.
[19:41] <belkinsa>  iii. https://help.ubuntu.com/community/CategoryCategory has more information
[19:41] <belkinsa> minus iii.
[19:42] <belkinsa> This could be a focus for someone who has expertise on a subject matter so they can review many pages in one place.
[19:43] <belkinsa> Any questions?
[19:45] <belkinsa> My final topic for my lesson is the other projects that people can do with us.
[19:45] <belkinsa> The first is the importing "How To Do" guides from the Ubuntu Forums: https://wiki.ubuntu.com/DocumentationTeam/Wiki/Tasks/Forum
[19:46] <belkinsa> The Ubuntu Forums have a wealth of information available. It is important to ensure that the wiki documentation (and ultimately the documentation which is included in the Ubuntu system) benefits from that information.
[19:46] <belkinsa> Same rules for these pages created apply.
[19:47] <belkinsa> The other project is the PopularDocs project.
[19:47] <belkinsa> https://launchpad.net/~newdocs
[19:47] <belkinsa> This project is now under the Doc Team and we aim to index the most used pages in order for users to find what they need faster.
[19:48] <belkinsa> We == as in the team.  I'm a part of it.
[19:49] <belkinsa> Any questions for my final section?
[19:50] <ClassBot> There are 10 minutes remaining in the current session.
[19:50] <belkinsa> As I said before, the wiki is a great place to start with the Doc team since it has less of a barrier and it's easier to understand.
[19:51] <belkinsa> As always:
[19:51] <belkinsa> If you'd like more information, feel free to email us on our mailing list at<EMAIL_ADDRESS>or chat with us in our IRC channel at #ubuntu-doc.  Please use the prefixes: [Desktop],[Server], and [Wiki] when you mail the list.  Each of them are for the three types of docs that we have.
[19:52] <belkinsa> I would like to thank everyone who came and did the example as I was teaching it.  Hopefully this can help you leap into wiki editing and hopefully get you to help us to have a useful wiki for all.
[19:53] <belkinsa> I would like to also thank pleia2 and the rest for planning this Classroom session/Doc Day event.
[19:53] <belkinsa> It was fun teaching this session.
[19:53] <pleia2> thanks belkinsa!
[19:55] <belkinsa> In five (5) minutes, godbyk will be teaching his "Getting started contributing to Manual" lesson.
[19:55] <ClassBot> There are 5 minutes remaining in the current session.
[19:58] <ClassBot> knome asked: Should I be worried about messing something up in the wiki?
[19:59] <belkinsa> knome, no, because of the rollback feature and the wiki admins are aways there.
[19:59] <belkinsa> The wiki admins are users with more power than the normal user.
[19:59] <belkinsa> They can delete and rename pages.
[20:00] <ClassBot> Logs for this session will be available at http://irclogs.ubuntu.com/2014/03/02/%23ubuntu-classroom.html following the conclusion of the session.
[20:00] <godbyk> Welcome to the Ubuntu Manual classroom session.
[20:01] <godbyk> The Ubuntu Manual Project publishes "Getting Started with Ubuntu" every six months.
[20:01] <godbyk> "Getting Started with Ubuntu" is a beginner's guide for Ubuntu. It's aimed at helping those who are new to Ubuntu become familiar with it.
[20:02] <godbyk> You can download a free PDF of the book from our website at http://ubuntu-manual.org/.
[20:02] <godbyk> You can also purchase a printed and bound copy through CreateSpace.com or Amazon.com.
[20:03] <godbyk> If you have any questions during this session, feel free to ask them in #ubuntu-classroom-chat. Don't forget to prefix your question with "QUESTION:".
[20:03] <godbyk> The Ubuntu manual covers a lot of material that's helpful for new users.
[20:04] <godbyk> It walks the reader through installing Ubuntu, introduces the Ubuntu desktop, instructs on how to install software, explains how to set up common applications, and provides some troubleshooting information.
[20:05] <godbyk> The manual is written and edited by a team of volunteers.
[20:05] <godbyk> We're always looking for more authors and editors to help us out.
[20:05] <godbyk> This session will explain how you can start contributing to the Ubuntu manual.
[20:06] <godbyk> There are a number of ways you can help create the next Ubuntu manual:
[20:06] <godbyk> * You can become an author.
[20:06] <godbyk> Authors help write new material to cover new Ubuntu applications and features.
[20:07] <godbyk> They also update the existing text when Ubuntu changes with each release.
[20:07] <godbyk> * You can become an editor.
[20:07] <godbyk> Editors review what the authors have written.
[20:07] <godbyk> The editors proofread the text for grammatical and spelling errors. They also ensure the information is accurate and up to date.
[20:08] <godbyk> * You can become a translator.
[20:08] <godbyk> We would like to publish the manual in as many languages as we can.
[20:09] <godbyk> The manual is currently available in English, Spanish, German, Dutch, Greek, Lithuanian, and Slovenian.
[20:11] <godbyk> If you'd like to get involved in the Ubuntu Manual Project, you can find more information on our website at http://ubuntu-manual.org/getinvolved.
[20:12] <godbyk> In this session, I'll briefly walk you through part of the process of becoming and author/editor and a translator.
[20:12] <godbyk> 1. Becoming an author or editor
[20:12] <godbyk> The complete instructions and process for becoming an author or editor are outlined online at http://ubuntu-manual.org/getinvolved/authors
[20:13] <godbyk> The first step is to create a Launchpad account and join our team.
[20:13] <godbyk> If you don't already have a Launchpad account, you can create one for free at https://launchpad.net/
[20:13] <godbyk> Once you've registered an account, you can join our team by visiting https://launchpad.net/~ubuntu-manual/ and clicking "Join this team".
[20:14] <godbyk> While you're there, subscribe to our mailing list.
[20:15] <godbyk> As an author or editor, you'll be working directly with our documentation files.
[20:15] <godbyk> We write our documentation using a markup language called LaTeX.
[20:15] <godbyk> We'll explore the LaTeX markup language a bit later in this session.
[20:16] <godbyk> Now that you have a Launchpad account and you've joined our team, you can download our documentation files.
[20:16] <godbyk> If you haven't already done so, you'll need to generate an SSH key and share it with Launchpad before you can download the files.
[20:17] <godbyk> To create an SSH key, open a terminal (by searching for 'Terminal' in the Dash or pressing Ctrl+Alt+T on your keyboard), and type the following commands (ignoring the $):
[20:17] <godbyk> $ sudo apt-get install openssh-client
[20:17] <godbyk> $ ssh-keygen -t rsa
[20:18] <godbyk> You can just press Enter to accept the default answers to all of the questions that ssh-keygen asks you.
[20:18] <godbyk> You may specify a password if you like, but it's not necessary.
[20:18] <godbyk> ssh-keygen will create a file named id_rsa.pub in the .ssh/ subdirectory of your home directory.
[20:19] <godbyk> We'll need to upload the the contents of this file to Launchpad.
[20:19] <godbyk> Visit your SSH keys page at https://launchpad.net/people/+me/+editsshkeys
[20:19] <godbyk> Open your key file by running the following command in a terminal:
[20:19] <godbyk> $ gedit ~/.ssh/id_rsa.pub
[20:20] <godbyk> Copy the contents of that file to your clipboard and paste it into the text box at the bottom of the Launchpad page. Click the "Import public key" button to continue.
[20:20] <godbyk> Now we can start downloading the documentation files.
[20:20] <godbyk> Install Bazaar by running the following command:
[20:21] <godbyk> $ sudo apt-get install bzr
[20:21] <godbyk> Tell bzr who you are:
[20:21] <godbyk> $ bzr whoami "Your name<EMAIL_ADDRESS>[20:21] <godbyk> Change 'Your name' to your own full name and<EMAIL_ADDRESS>to your email address. Don't forget to include the quotation marks and the angle brackets.
[20:22] <godbyk> Give bzr your Launchpad username:
[20:22] <godbyk> $ bzr launchpad-login myusername
[20:22] <godbyk> You can find your username by visiting http://launchpad.net/~
[20:22] <godbyk> Launchpad will display your username after the tilde (~) in the address bar.
[20:23] <godbyk> Finally, we can start downloading the documentation files:
[20:23] <godbyk> $ bzr branch lp:ubuntu-manual
[20:23] <godbyk> This may take a few minutes depending on the speed of your Internet connection.
[20:24] <godbyk> Once you've finished downloading the documentation files, you can start taking a look at them.
[20:24] <godbyk> For this session, we'll explore the files online.
[20:25] <godbyk> Due to time constraints, I've omitted some of the steps required for you to build the manual PDF yourself. For full instructions, please visit http://ubuntu-manual.org/getinvolved/authors
[20:26] <godbyk> Inside the ubuntu-manual directory, you'll see a number of subdirectories and files. You can view these online at http://bazaar.launchpad.net/~ubuntu-manual/ubuntu-manual/trusty/files
[20:26] <godbyk> Each chapter of the manual is stored in its own subdirectory (e.g., installation, ubuntu-desktop, learning-more).
[20:26] <godbyk> Let's take a look at the installation chapter.
[20:27] <godbyk> Inside the installation/ subdirectory, you'll find an installation.tex file.
[20:27] <godbyk> The .tex files are the LaTeX source files for our manual.
[20:27] <godbyk> You can view the installation.tex file online at http://bazaar.launchpad.net/~ubuntu-manual/ubuntu-manual/trusty/view/head:/installation/installation.tex
[20:28] <godbyk> While the LaTeX markup may appear daunting at first, it's fairly simple to read and use once you get accustomed to it.
[20:28] <godbyk> We won't have time in this session to explore the LaTeX markup language, but you can find more information about how we use LaTeX in our style guide.
[20:28] <godbyk> Our style guide is available online at http://files.ubuntu-manual.org/style-guide.pdf
[20:29] <godbyk> The style guide covers most of what you'll need to know to participate in the Ubuntu Manual Project:
[20:29] <godbyk> * how to become a member of the project
[20:29] <godbyk> * the setup instructions we're coving in this session (and more)
[20:29] <godbyk> * how we use bzr
[20:30] <godbyk> * how we use the LaTeX markup language
[20:30] <godbyk> * information for translators
[20:30] <godbyk> * usage notes on terminology used in the manual
[20:30] <godbyk> Back to the installation.tex file (http://bazaar.launchpad.net/~ubuntu-manual/ubuntu-manual/trusty/view/head:/installation/installation.tex)
[20:31] <godbyk> If you compare the contents of that file to the contents of the Installation chapter in the PDF of our manual (available at http://ubuntu-manual.org//download/13.10/en_US/screen),
[20:31] <godbyk> you'll see how the markup language handles all of the formatting for us.
[20:32] <godbyk> For example, we just specify a section heading and LaTeX will decide how to style it (font size, bold, etc.).
[20:32] <godbyk> Are there any questions about anything we've covered so far?
[20:33] <godbyk> If you decide you'd like to become an author or editor, please send an email to our mailing list at<EMAIL_ADDRESS>and we'll help you get started.
[20:33] <godbyk> You'll be able to choose which section of the manual you'd like to work on.
[20:34] <godbyk> Okay, next, we'll see how our manual is translated into various languages.
[20:34] <godbyk> As I mentioned before, our manual is translated into a number of languages.
[20:35] <godbyk> If you'd like to help with one of the existing languages or translate the manual into a new language, just let us know!
[20:35] <godbyk> Instructions for translators are available online at http://ubuntu-manual.org/getinvolved/translators and in our style guide (available at http://files.ubuntu-manual.org/style-guide.pdf).
[20:36] <godbyk> Becoming a translator is pretty easy.
[20:36] <godbyk> The first step is to create a Launchpad account if you don't already have one.
[20:36] <godbyk> We covered that in detail earlier.
[20:36] <godbyk> Once you've created an account, go to your page: launchpad.net/~
[20:37] <godbyk> Click on the yellow 'edit' icon next to the Languages header and add all the language you speak.
[20:37] <godbyk> Some translation teams require you join their team before you can translate text into that language.
[20:38] <godbyk> For those teams, you'll need to visit their team page on Launchpad and sign up to join their team. Each team may have its own requirements for joining.
[20:38] <godbyk> Finally, you can visit our translations page at http://translations.launchpad.net/ubuntu-manual.
[20:38] <godbyk> You should see your preferred languages listed. Click on the language you'd like to translate to and start translating the text.
[20:39] <godbyk> As a translator, you will need to learn a bit about the LaTeX markup language to know what parts of the text you should and shouldn't translate.
[20:39] <godbyk> You can find all the details of this in chapter 7 of our style (again, available at http://files.ubuntu-manual.org/style-guide.pdf).
[20:40] <godbyk> If you have any questions about translating that aren't answered by our style guide, feel free to ask on the ubuntu-manual mailing list or in the #ubuntu-manual channel here on IRC.
[20:40] <godbyk> Are there any questions about translating the Ubuntu manual?
[20:45] <godbyk> All right, if there are any other questions about the Ubuntu Manual project or any of the other Ubuntu docs projects, feel free to ask them in #ubuntu-classroom-chat.
[20:45] <godbyk> Don't forget to prefix your question with "QUESTION:".
[20:46] <ClassBot> benonsoftware asked: Is the Ubuntu Manual in the Ubuntu archive?
[20:46] <godbyk> benonsoftware: The manual isn't currently available in the Ubuntu archive or the Software Center.
[20:47] <godbyk> You can download a PDF of the manual for free from our website at http://ubuntu-manual.org/downloads
[20:47] <godbyk> Or you can purchase printed-and-bound copies of the book online at http://ubuntu-manual.org/buy/gswu1310/en_US or through Amazon.com.
[20:47] <ClassBot> belkinsa asked: Wouldn't be better to use the content from Ubuntu Desktop guide in the Ubuntu Manual?
[20:48] <godbyk> belkinsa: The manual covers many of the same topics as the desktop docs do, but it's in a different form.
[20:48] <godbyk> The desktop docs are written in a topic-based way. They're designed to answer an immediate 'how do I...?' question.
[20:49] <godbyk> The manual is designed to be something that you could sit down and read through as you learn Ubuntu.
[20:49] <godbyk> The manual is also useful if you don't have access to the Internet or haven't yet installed Ubuntu to be able to access the desktop docs.
[20:50] <ClassBot> There are 10 minutes remaining in the current session.
[20:51] <godbyk> By the way, if you don't want to commit to becoming an author, editor, or translator, you can still help improve the Ubuntu manual by emailing<EMAIL_ADDRESS>with suggestions for how we can improve the manual.
[20:51] <godbyk> If you found a typo, incorrect or outdated information, or have a suggestion for a topic we should write about, feel free to email us.
[20:51] <ClassBot> jsjgruber-l101-p asked: Does the printed manual come with an Ubuntu CD?
[20:52] <godbyk> jsjgruber-l101-p: The printed manual doesn't come with an Ubuntu CD at this time.
[20:52] <godbyk> It's a good idea, though, and something we'd love to be able to do in the future!
[20:52] <godbyk> Are there any other questions about the Ubuntu manual or any of the other Ubuntu docs projects?
[20:55] <godbyk> In a few minutes, the next session will start: Ubuntu Manual versions explained by tacorwin.
[20:55] <ClassBot> There are 5 minutes remaining in the current session.
[21:00] <ClassBot> Logs for this session will be available at http://irclogs.ubuntu.com/2014/03/02/%23ubuntu-classroom.html following the conclusion of the session.
[21:00] <tacorwin> Hello everyone! Before we start, I'd like to mention that there will be three sections in this session: The Ubuntu Manual, the Lubuntu Manual, and a proposed project, the Wine on Ubuntu Manual project.
[21:01] <tacorwin> Please save all questions until the end of each section, respectively.
[21:01] <tacorwin> Since godbyk has explained the Ubuntu Manual, I won't go in depth, but rather skim the topic.
[21:02] <tacorwin> The Ubuntu Manual project was created in 2009 by Benjamin Humphrey to provide up-to-date information for new users of the Ubuntu OS.
[21:03] <tacorwin> We try to make every ounce of information educational an simple to understand to lower the Linux barrier for new users.
[21:04] <tacorwin> There are many ways to contribute to the manual: Becoming an author, editor, translator, designer, etc.
[21:04] <tacorwin> I will be skipping the "how to contribute" portion, as it was previously explained.
[21:05] <tacorwin> As I said, this was brief.
[21:05] <tacorwin> Any questions pertaining to the Ubuntu Manual?
[21:06] <tacorwin> Okay. The next topic is the Lubuntu Manual Project.
[21:07] <tacorwin> The Lubuntu Manual was just created last year to provide the same form of documentation for the Lubuntu variant.
[21:08] <tacorwin> The contribution types are the same (Author, Editor, etc.), but things are a bit shaky at the moment, as they are trying to start the actual work of the first manual release.
[21:09] <tacorwin> To contribute, follow this link. https://wiki.ubuntu.com/Lubuntu/DocumentationTeam/Manual
[21:09] <tacorwin> There is a Launchpad project for the Lubuntu Manual as well, that you should add to become part of the team.
[21:10] <tacorwin> You can simply join Lubuntu Wiki and Docs Team and after the administrator of the team approve your request, please send an introduction email to the list and make yourself known.
[21:10] <tacorwin> This will ensure that your efforts are known to all members.
[21:11] <tacorwin> You should also add your name to the list on the page (referring to the last link).
[21:12] <tacorwin> There really aren't a whole lot of details I can give at this point about the LMP, because they have recently started up, and haven't entirely started releasing a manual.
[21:13] <tacorwin> If there are any specific questions about this manual, you can ask now.
[21:15] <tacorwin> We have one more topic to cover, the Wine on Ubuntu Manual Project.
[21:16] <tacorwin> I can give more information on this manual, unlike the others because I have proposed it and have (slowly) started the production of it.
[21:18] <tacorwin> In a nutshell, the WOUMP (abbr.) is an attempt to lower the Linux barrier even more by explaining how to run a lot of Windows programs on a Linux OS (Ubuntu) using WINE (Wine Is Not an Emulator)
[21:19] <tacorwin> This manual was proposed about 6 months ago, by myself, and will hopefully be adapted as an official Ubuntu Manual Project affiliate.
[21:20] <ClassBot> There are 10 minutes remaining in the current session.
[21:20] <tacorwin> Right now, contributors are needed to start the project in the right direction, but I will explain what will be contained.
[21:21] <tacorwin> Installation, configuration, usage, and uninstallation are just a few of the topics planned to be in the manual.
[21:23] <tacorwin> For a list of plausible sections, go to: https://docs.google.com/spreadsheet/ccc?key=0ApexI9z0UYtGdERqWHpEZmpXVUgwZV9CeExFdlNBT0E&usp=docslist_api
[21:23] <tacorwin> This is a spreadsheet containing the old authors and editors list I was going to uses
[21:23] <tacorwin> I will use the last few minutes to answer specific questions about this manual, as well as any others mentioned previously.
[21:25] <ClassBot> There are 5 minutes remaining in the current session.
[21:25] <ClassBot> belkinsa asked: How many are in the WINE Manual team at the moment?
[21:26] <tacorwin> One, unfortunately.
[21:26] <tacorwin> I'm currently trying to find other contributors.
[21:27] <tacorwin> belkinsa: forgot to put your name.  I wanted to further organize it before I began a full-scale team.
[21:28] <tacorwin> Any other questions? :)
[21:30] <ClassBot> Logs for this session will be available at http://irclogs.ubuntu.com/2014/03/02/%23ubuntu-classroom.html
[21:30] <pleia2> thanks tacorwin!
[21:30] <tacorwin> This was the last session for today's Documentation Day. Thank you all for attending.
[21:30] <tacorwin> :) anytime pleia2


 @tsimonq2, Done. https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3291/+sourcepub/9257332/+listing-archive-extra
 @mitya57, Thank you!


[12:09] <gnomefreak> this sucks
[12:12] <gnomefreak> i think ill see if i can backport libflashsupport to gutsy since its not there and flash 10 needs it
[12:17] <wgrant> asac: Ping - your plugin finder service (nppapt.py:77) is causing quite a few sources.lists to break.
[12:18] <wgrant> asac: If one tries to install totem-mozilla through ubufox, it will try to add the 'web' component to sources.list, so will kill everything.
[12:18] <wgrant> (I presume this wasn't found to occur frequently because totem-mozilla is installed by default)
[12:19] <wgrant> Checking for the emptiness of tail and setting real_section to 'main' should fix it...
[12:20] <asac> wgrant: whats the apturl ccommand line you see while installing totem-mozilla?
[12:20] <wgrant> asac: I've checked the XML returned by your script. It's bogus.

[12:20] <asac> hmm
[12:21] <wgrant> You're not checking for the emptiness of tail, so anything in main (ie. only totem-mozilla will return the real section, not component.
[12:21] <asac> wgrant: have a patch?
[12:21] <asac> feel free to submit
[12:21] <asac> :)
[12:22] <wgrant> asac: It's all of two lines, but sure.
[12:26] <wgrant> asac: http://pastebin.com/f6951091c should do it, but I can't really test.
[12:27] <asac> wgrant: will tail be "" or None?
[12:28] <wgrant> asac: Meant to be an empty string IIRC, but I'll check help(str.partition)....
[12:28] <wgrant>     Searches for the separator sep in S, and returns the part before it,
[12:28] <wgrant>     the separator itself, and the part after it.  If the separator is not
[12:28] <wgrant>     found, returns S and two empty strings.
[12:28] <asac> k
[12:30] <gnomefreak> damnit
[12:31] <asac> hu?
[12:32] <gnomefreak> ha it worked
[12:32] <gnomefreak> or not
[12:32] <asac> wgrant: ok thanks. committed and currently recreating the db
[12:33] <gnomefreak> ha
[12:33] <gnomefreak> damn script isnt working
[12:36] <wgrant> asac: Thanks!
[12:46] <wgrant> asac: How long does it take? It's still broken.
[12:47] <asac> wgrant: did some tests first
[12:49] <asac> wgrant: ok please test
[12:49] <wgrant> asac: Perfect, thanks.
[12:54] <wgrant> Would this have affected Gutsy systems as well?
[12:54] <wgrant> Or do we only have a month of broken Xubuntu machines?
[12:55] <asac> wgrant: i think gutsy is not affected
[12:55] <asac> the section feature was somewhat broken at that point iirc
[12:56]  * gnomefreak just found out gutsy doesnt have libflashsuppot so i have to talk to jdong to see what he thinks about backporting it
[12:57] <wgrant> asac: Thanks.
[12:58] <gnomefreak> see you later
[12:58] <asac> wgrant: ask someone with gutsy to post sources.list to be sure
[13:00] <asac> let me know. thanks!
[13:07] <wgrant> asac: Hm, bug #228264 looks like it might.
[13:07] <asac> no bot
[13:08] <wgrant> https://bugs.edge.launchpad.net/ubuntu/+source/update-manager/+bug/228264
[13:09] <wgrant> asac: Another case of that :(
[13:09] <wgrant> And another.
[13:09] <wgrant> So it does affect gutsy.
[13:11] <asac> wgrant: reassigned that bug
[13:12] <asac> wgrant: ok i retitled the bug and made it a master
[13:12] <asac> if you find dupes, please merge them in that bug
[13:14] <wgrant> asac: I was going to take 202170 as the master, and already marked it as fixed, but will do.
[13:14] <asac> wgrant: its not fixed ;)
[13:15] <wgrant> Right, your interpretation of the real bug is more correct than mine.
[13:16] <asac> bug 202170
[13:16] <wgrant> ENOBOT
[13:16] <wgrant> I tracked this down and fixed it this evening. See bug #202170 for details.
[13:16] <wgrant> Gah.
[13:16] <wgrant> Oops.
[13:16] <wgrant> https://bugs.edge.launchpad.net/ubuntu/+bug/202170
[13:17] <asac> ok ill mark it as dupe anyway to give this bug more weight ;)
[13:17] <wgrant> Yep.
[13:37] <gnomefreak> bug 230016
[13:37] <asac> ENOBOT still gnomefreak
[13:37] <gnomefreak> shit
[13:39] <gnomefreak> thanks asac they are working on a different bot since we have 4 or so bots just none are really set up
[14:06] <gnomefreak> why the hell would add deps to a package if the deps have NEVER been in Ubuntu, most likely set deps from upstream but than you wouldnt respin it until those packages have been added if we add them :(
[14:06]  * gnomefreak wonders who did this
[14:14] <gnomefreak> asac: does sid get updated as lemmy gets updated or is it outdated?
[14:33] <asac> gnomefreak: if we have packages without build-deps thats an archive but
[14:34] <asac> unless they are scheduled for removal
[14:35] <gnomefreak> well irssi newest build is still borked
[14:51] <Jazzva> gnomefreak: I took a look at firegpg, but I wasn't able to get it working. I think that when I tried to install the xpi file, made by build script, it also didn't work.
[14:52] <gnomefreak> Jazzva: ok ioll look at it this week again sometime right now perl issues are pissing me off
[14:53] <Jazzva> Ok... Good luck with perl.
[14:53] <asac> Jazzva: does upstream .xpi work?
[14:54] <Jazzva> asac: Didn't try to download the version from their site
[14:54] <gnomefreak> asac: yes it does
[14:54] <asac> then our xpi should work too
[14:54] <asac> you most likely unzipped it in a not-so-nice fashion :)
[14:54] <gnomefreak> i have changes to make to it like package version and stuff that i forgot but nothing that would cause it to fail to install
[14:55] <Jazzva> asac: I think it was checked out from svn
[14:55] <gnomefreak> it was
[14:55] <gnomefreak> asac: its nothing that i did since it builds fine
[14:55] <gnomefreak> it just doesnt install
[14:55] <Jazzva> gnomefreak: I'm not sure if I mentioned before, you forgot to remove the .svn dirs
[14:55] <gnomefreak> Jazzva: yeah that too
[14:56] <gnomefreak> still wouldnt cause this issue though and im not gonna go around fixing things until i find out what is wrong (other than changelog version)
[14:56] <Jazzva> it should be easy with "for SVNDIR in `find . -name .svn` ; do rm -rf $SVNDIR ; done
[14:57] <Jazzva> running from build directory
[14:58] <gnomefreak> without the first "
[14:58] <gnomefreak> or is that a *
[14:59] <Jazzva> right :). I forgot to close it (just to separate it from text)
[14:59] <Jazzva> but without the "
[14:59] <Jazzva> :)
[15:10] <gnomefre1k> ok time to try new irssi now that i fixed it
[15:10] <gnomefre1k> be back
[16:38] <gnomefreak> asac: since gutsy doeasnt have libflashsupport should we bother backporting it to gutsy from hardy or intrepid or should i just do that from PPA?
[18:44] <fta> asac, your bz394103_dont_scale_images.patch diverged in rc2
[18:44] <fta> asac, http://bonsai.mozilla.org/cvslog.cgi?file=/mozilla/gfx/src/thebes/nsThebesDeviceContext.cpp&rev=HEAD&mark=1.79  (last 2 commits)
[18:45] <fta> i prefer to let you fix that
[18:50] <asac> fta: how does the reject hunk look like?
[18:51] <fta> full reject
[18:51] <asac> k
[18:51] <fta> http://paste.ubuntu.com/16231/
[18:58] <asac> done
[18:58] <asac> 273
[18:58] <fta> thanks
[19:52] <fta> hm, we can no longer work on 2 branches at the same time with the new bzr
[19:53] <fta> there's a global lock per user
[19:53] <fta> s/per user/per repo/
[22:30] <asac> he?
[22:32] <asac> fta: is the lock gone?
[22:32] <fta> i mean locally
[22:32] <asac> dont understand that
[22:32] <asac> but maybe because I dont see it yet :/
[22:33] <asac> fta: ah ... maybe the default is now lightweight checkout
[22:35] <fta> i was in ~/bzr/xul1.9.head doing a commit (editing changes), and i wanted to pull another branch in ~/bzr/xxx, bzr said:
[22:35] <fta> Unable to obtain lock file:///src/bzr/.bzr/repository/lock
[22:35] <fta> held by<EMAIL_ADDRESS>on host ix [process #15691]
[22:35] <fta> locked 1 second ago
[22:35] <fta> Will continue to try until 20:56:03
[22:36] <fta> well, it was not a pull but another commit
[22:38] <asac> ah ok ... well then its a lightweight checkout indeed
[22:38] <asac> ~/bzr/ is a repo most likely
[22:38] <asac> or maybe repo has just been fixed
[22:38] <asac> just use ~/bzr2/
[22:38] <asac> : )


[01:54] <ColdRush> Does anyone ever talk here?
[10:30] <leszek> hi
[14:37] <Riccardone> hi all
[14:38] <dyd> i want to run a script when any usb device is plugged in. I added a file in /etc/udev/rules.d/ named 90-local.rules that contains SUBSYSTEM=="usb", RUN+="/usr/local/bin/usbhook". I restarted udev, but if i plug any usb pen nothing happens. Why?
[14:46] <Riccardone> prova
[14:47] <ColdRush> I feel so leet using linux :D
[15:58] <ColdRush> Can someone upload their openbox lubuntu-rc.xml?  I'm trying to figure out the proper way to write the commands for my back, forward, and refresh keys
[16:00] <Jef91> Does Lubuntu 12.10 support non-PAE systems?
[16:01] <econdudeawesome> howdy all. I'm having trouble getting my laptop (12.04 I think) to use multiple monitors. The monitors are detected, but I am unable to have each screen be independent
[16:02] <holstein> Jef91: http://askubuntu.com/questions/182048/will-it-be-possible-to-use-a-non-pae-kernel-in-12-10
[16:02] <holstein> econdudeawesome: i would try arandr ..i found with my ndivia card on my main audio production machine i needed the proprietary driver
[16:03] <econdudeawesome> holstein: arandr? I'm familiar with xrandr but arandr i've not heard of before?
[16:03] <Jef91> So that is a no then holstein?
[16:04] <holstein> Jef91: AFAIK, that is a guide on how to get a non pae kernel in 12.10
[16:04] <econdudeawesome> holstein: reading up on it now--thanks for the tip
[16:04] <holstein> Jef91: i havnet needed to do that first-hand yet, though i was told it worked, and i know its possible
[16:04] <Jef91> Alrighty, I was miss informed. Someone told me 12.10 provides non-PAE kernels
[16:04] <Jef91> (Lubuntu 12.10 that is)
[16:04] <holstein> Jef91: lubuntu is ubuntu
[16:05] <holstein> Jef91: there might be a non-pae kernel in the repos, but i dont think so.
[16:05] <Jef91> I'm aware, as I said I was miss informed. Someone told me they built their own kernel to support non-PAE systems
[16:05] <tsimpson> there's probably a PPA with non-PAE kernels, but not part of the default install
[16:06] <holstein> http://www.webupd8.org/2012/05/how-to-install-ubuntu-1204-on-non-pae.html is for 12.04
[16:06] <holstein> for a system like that, i would want to stick on 12.04 anyways...
[19:23] <tweakster> hi. I just installed firefox as the default browser in Lubuntu, including "gecko-mediaplayer" plugin. This plugin states that it is a Video Player plugin for Quicktime, Realplayer and Windows Media Player streams using MPlayer. To me this statement suggests that I can remove the other default plugins (namely, Quicktime, RealPlayer and Windows Media Player), which also installed with Firefox. I mean, there would seem little
[19:32] <holstein> tweakster: they might depend on each other
[19:32] <holstein> tweakster: is there a space concern?... with proprietary stuff like that, you might want to just leave it be if its working as you need it to
[19:40] <tsimpson> tweakster: I doubt you have any of those other plugins, if you look they should all be provided by that one plugin
[19:51] <elsie> hi there
[19:51] <lyyyy> hi there, quick question. I want to work in the terminal (tty) but the blink rate is annoyingly fast
[19:52] <lyyyy> how do I reduce the terminal blink rate?
[19:56] <holstein> http://unix.stackexchange.com/questions/3759/how-to-stop-cursor-from-blinking
[19:56] <holstein> http://forums.debian.net/viewtopic.php?f=5&t=55798
[19:58] <lyyyy> holstein the debian form one is unheklpful - mostly just someone complaining that it's hard to do!
[19:59] <holstein> lyyyy: ignore it then
[19:59] <lyyyy> holstein I'm just pointing out that I did look into it before I posted
[19:59] <lyyyy> looking at the stackexchange forum now
[20:00] <holstein> lyyyy: i thought it was relevant since it references the echo -e '\033[?17;0;127c' from the stackexchange link
[20:00] <holstein> its its not relevant to you.. its not
[20:01] <lyyyy> holstein unfortunately that just stops it blinking entirely
[20:01] <lyyyy> what I want is to reduce the rate
[20:01] <holstein> lyyyy: it says that
[20:01] <holstein> stopping is slower, plus i thought that might be "better", or "preffered"
[20:01] <lyyyy> I'm honestly amazed that there isn't some simply setting in .bashrc or something
[20:02] <lyyyy> haha
[20:02] <lyyyy> stopping is slower, true
[20:40] <jarnos> 12.04 is terrible, everything crashes now and then, even Abiword.
[20:45] <holstein> jarnos: maybe its hardware support related.. 12.04 is quite stable for me
[20:49] <phiscribe> 12.04 work pretty good for me, im on 12.10 now
[20:58] <jarnos> Well, crashes of Abiword should not be hardware related.
[20:59] <holstein> jarnos: its not crashing here
[20:59] <holstein> jarnos: open a terminal, and launch it.. see if there is some helpful output
[21:00] <holstein> jarnos: system crashes and instability could be due to some hardware driver support issue with the kernel and your specific harware
[21:00] <holstein> OR, you have bad hardware.... or some corrupt files. or a bad install
[21:38] <dreambox> hey folks! I'm running Ubuntu (unity) and would like to get rid of it and install Lubuntu through apt-gets (no reinstalls etc..)
[21:38] <dreambox> any idea how?
[21:39] <dreambox> wouldn't like to keep unused packages.. hdd economy..
[21:39] <holstein> sudo apt-get install lubuntu-desktop
[21:39] <bioterror> !purelxde | dreambox
[21:39] <dreambox> thanks :)
[21:40] <dreambox> damn the complicated desktops...
[21:40] <dreambox> Unity is a bugfest
[21:42] <holstein> works fine for me.. you can use and prefer what you like though
[21:46] <TheLordOfTime> mind if i give you some advice dreambox?
[21:46] <TheLordOfTime> stop whining about unity in #ubuntu if you're going to be using lubuntu as a solution?
[21:48] <dreambox> TheLordOfTime, democracy.. I'll express my concerns... either you like it or not.
[21:48] <dreambox> good night
[21:48] <holstein> yeah... a lot of volunteers work hard to develop unity..
[21:48] <TheLordOfTime> this isnt a democracy dude.
[21:48] <TheLordOfTime> !whining
[21:48] <TheLordOfTime> what?  there's no factoids for this?
[21:48]  * TheLordOfTime walks over to the IRCC
[21:49] <TheLordOfTime> there are limits to how much we allow you to whine and complain
[21:50] <dreambox> TheLordOfTime, man, I stopped chatting with you like 10' ago ..
[21:50] <dreambox> give it a rest please.
[22:45] <jarnos> holstein, Well, I have upgraded to 12.04 from older release in two different hardware and they both have various crashes. Fortunately 12.04 has feature that is supposed to report crashes easily to developers.
[23:10] <holstein> jarnos: i have fresh installs that dont crash.. maybe try making a new user and testing there, taking your configuration out of the equation


[07:13] <dholbach> good morning
[09:52] <nhaines> dholbach: good morning!
[09:53] <nhaines> I'm just about to go to sleep.  But I'm pleased because I finished my work on the Ubuntu member business cards finally.  :D
[10:02] <dholbach> hi nhaines
[10:02] <dholbach> great :)
[10:04] <nhaines> dholbach: yup, the name badges from yesterday was only the first step!
[10:04] <dholbach> :-D
[10:04] <nhaines> Of course, I only have two steps.  But it's a start anyway.  :D
[10:04] <nhaines> I'll have to take a look at the UAK....  I'm giving a presentation for an installfest in May and they'll need fliers so there should be some stuff to add.  :)
[10:10] <dholbach> cool :)
[10:13] <nhaines> Okay, bedtime now... maybe the Phone landing team will surprise me with a promoted image when I wake up.  :)
[10:13]  * nhaines dreams of an image where he doesn't have to enable sound on an N5 manually.
[10:30] <dholbach> sleep tight :)


[00:15] -queuebot:#ubuntu-ci-eng- RikMills, https://bileto.ubuntu.com/#/ticket/4454 Currently building (hirsute/ktp-common-internals, hirsute/signon-keyring-extension). Diff missing (hirsute/kaccounts-integration, hirsute/kaccounts-providers, hirsute/ktp-accounts-kcm, hirsute/ktp-approver, hirsute/ktp-auth-handler, hirsute/signon-kwallet-extension, hirsute/signon-plugin-oauth2, hirsute/signond). Failed to build (hirsute/accounts-qml-module, hirsute/signon-plugin-sasl, hirsute/
[00:35] -queuebot:#ubuntu-ci-eng- RikMills, https://bileto.ubuntu.com/#/ticket/4454 Dependency wait (hirsute/signon-keyring-extension). Diff missing (hirsute/kaccounts-integration, hirsute/kaccounts-providers, hirsute/ktp-accounts-kcm, hirsute/ktp-approver, hirsute/ktp-auth-handler, hirsute/signon-kwallet-extension, hirsute/signon-plugin-oauth2, hirsute/signond). Failed to build (hirsute/accounts-qml-module, hirsute/signon-plugin-sasl, hirsute/signon-ui). Uploading build (hirs
[00:55] -queuebot:#ubuntu-ci-eng- RikMills, https://bileto.ubuntu.com/#/ticket/4454 Dependency wait (hirsute/signon-keyring-extension). Diff missing (hirsute/kaccounts-integration, hirsute/kaccounts-providers, hirsute/ktp-accounts-kcm, hirsute/ktp-approver, hirsute/ktp-auth-handler, hirsute/ktp-common-internals, hirsute/signon-kwallet-extension, hirsute/signon-plugin-oauth2, hirsute/signond). Failed to build (hirsute/accounts-qml-module, hirsute/signon-plugin-sasl, hirsute/sig
[01:15] -queuebot:#ubuntu-ci-eng- RikMills, https://bileto.ubuntu.com/#/ticket/4454 Dependency wait (hirsute/signon-keyring-extension). Diff missing (hirsute/kaccounts-integration, hirsute/kaccounts-providers, hirsute/ktp-accounts-kcm, hirsute/ktp-approver, hirsute/ktp-auth-handler, hirsute/signon-kwallet-extension, hirsute/signon-plugin-oauth2, hirsute/signond). Failed to build (hirsute/accounts-qml-module, hirsute/signon-plugin-sasl, hirsute/signon-ui). Pending binary packag
[01:35] -queuebot:#ubuntu-ci-eng- RikMills, https://bileto.ubuntu.com/#/ticket/4454 Dependency wait (hirsute/signon-keyring-extension). Diff missing (hirsute/kaccounts-integration, hirsute/kaccounts-providers, hirsute/ktp-accounts-kcm, hirsute/ktp-approver, hirsute/ktp-auth-handler, hirsute/ktp-common-internals, hirsute/signon-kwallet-extension, hirsute/signon-plugin-oauth2, hirsute/signond). Failed to build (hirsute/accounts-qml-module, hirsute/signon-plugin-sasl, hirsute/sig
[08:15] -queuebot:#ubuntu-ci-eng- cpaelzer, https://bileto.ubuntu.com/#/ticket/4475 No packages are being considered! If you are preparing sources manually, please upload them to the PPA now
[08:55] -queuebot:#ubuntu-ci-eng- cpaelzer, https://bileto.ubuntu.com/#/ticket/4475 Failed to build (hirsute/tgt). Pending binary packages (hirsute/python-rtslib-fb)
[09:15] -queuebot:#ubuntu-ci-eng- cpaelzer, https://bileto.ubuntu.com/#/ticket/4475 Diff missing (hirsute/python-rtslib-fb). Failed to build (hirsute/tgt)
[10:40] -queuebot:#ubuntu-ci-eng- slyon, https://bileto.ubuntu.com/#/ticket/4439 Needs rebuild due to higher version at destination (bionic/linux). Proposed pocket (bionic/binutils)
[11:00] -queuebot:#ubuntu-ci-eng- slyon, https://bileto.ubuntu.com/#/ticket/4439 Proposed pocket (bionic/binutils). Security pocket (bionic/linux)
[12:36] -queuebot:#ubuntu-ci-eng- cpaelzer, https://bileto.ubuntu.com/#/ticket/4475 Diff missing (hirsute/python-rtslib-fb). Pending binary packages (hirsute/tgt)
[12:56] -queuebot:#ubuntu-ci-eng- cpaelzer, https://bileto.ubuntu.com/#/ticket/4475 Diff missing
[13:16] -queuebot:#ubuntu-ci-eng- cpaelzer, https://bileto.ubuntu.com/#/ticket/4475 Diff missing (hirsute/tgt). Needs rebuild due to higher version at destination (hirsute/python-rtslib-fb)
[18:15] -queuebot:#ubuntu-ci-eng- RikMills, https://bileto.ubuntu.com/#/ticket/4454 Currently building (hirsute/signon-keyring-extension). Diff missing (hirsute/kaccounts-integration, hirsute/kaccounts-providers, hirsute/ktp-accounts-kcm, hirsute/ktp-approver, hirsute/ktp-auth-handler, hirsute/ktp-common-internals, hirsute/signon-kwallet-extension, hirsute/signon-plugin-oauth2, hirsute/signond). Failed to build (hirsute/accounts-qml-module, hirsute/signon-plugin-sasl, hirsute/
[18:35] -queuebot:#ubuntu-ci-eng- RikMills, https://bileto.ubuntu.com/#/ticket/4454 Dependency wait (hirsute/signon-keyring-extension). Diff missing (hirsute/kaccounts-integration, hirsute/kaccounts-providers, hirsute/ktp-accounts-kcm, hirsute/ktp-approver, hirsute/ktp-auth-handler, hirsute/ktp-common-internals, hirsute/signon-kwallet-extension, hirsute/signon-plugin-oauth2, hirsute/signond). Failed to build (hirsute/accounts-qml-module, hirsute/signon-plugin-sasl, hirsute/sig
[21:34] -queuebot:#ubuntu-ci-eng- RikMills, https://bileto.ubuntu.com/#/ticket/4474 Needs rebuild due to higher version at destination