[04:13] <kotux> good evening
[06:07] <bkerensa> mmm
[06:13] <godbyk> bkerensa: I spent some time this evening chatting with kotux and getting him to the point that he's downloaded the ubuntu-docs bzr repository.
[06:13] <bkerensa> excellent
[06:13] <godbyk> bkerensa: I suggested that starting points (since he was eager to get started) would be to review the existing documentation to find typos, grammatical errors, and bits that are out of date or incorrect.
[06:13] <bkerensa> great mentoring :)
[06:14] <bkerensa> godbyk: So I am staging wiki.ubuntu.com/DocumentationTeam/GettingStarted
[06:14] <bkerensa> when that has a solid outline we can add it to the menu
[06:14] <godbyk> bkerensa: I also suggested he could take a look at the slew of existing bug reports and pick away are some of the smaller ones he finds or to start a discussion thread on the mailing list if he wants to tackle something larger.
[06:14] <bkerensa> I also want to keep a list of our processes inside the ubuntu-docs repo somewhere in a text file
[06:15] <godbyk> Ah, great!
[06:15] <bkerensa> and also create a master todo list which we can update each cycle
[06:15] <bkerensa> so people have a list of work that needs doing
[06:15] <godbyk> That's a good idea, too.
[06:15] <bkerensa> yeah if he wants to triage bugs that would be helpful too
[06:15] <bkerensa> Im sure lots are invalid
[06:15] <godbyk> As I explained to kotux, we're pretty new to this game, so we need to try to get everything sorted out ourselves before we can be of help to others.
[06:15] <bkerensa> once that link gets updated the invalid bugs should be reduced
[06:15] <bkerensa> yeah
[06:17] <godbyk> Our documentation and processes aren't perfect in the manual project, but they might give you some ideas, too: http://ubuntu-manual.org/getinvolved
[06:18] <godbyk> For the manual project, we organized the processes based on various roles one might want to assume.
[06:18] <godbyk> So translators can find instructions and information relevant to their work.
[06:18] <godbyk> Editors, authors, etc. similarly.
[06:19] <godbyk> (Some of our information is in a style guide PDF <http://files.ubuntu-manual.org/style-guide.pdf>. It's not all listed on the website.)
[06:20] <bkerensa> cool
[06:21] <bkerensa> godbyk: you didnt send that e-mail yet right? If not lets wait till tomorrow or this weekend and include a doodle.com scheduler so we can setup a first meeting too
[06:21]  * bkerensa is going to go off to bed but will start working on his work items tomorrow I think
[06:21] <godbyk> Which email was that?
[06:22] <bkerensa> godbyk: the uds summary one?
[06:22] <godbyk> Yep. I already sent that one.
[06:22] <bkerensa> ah ok :)
[06:23] <godbyk> https://lists.ubuntu.com/archives/ubuntu-doc/2013-May/017299.html
[06:23] <bkerensa> well I will send a meeting one this weekend then
[06:23] <godbyk> I mentioned that we'd schedule a health-check meeting within the next month or so.
[06:23] <bkerensa> odd it didnt go to my Ubuntu label in Gmail
[06:23] <bkerensa> hehe
[06:23] <godbyk> Oh, sure, blame gmail! ;-)
[06:24] <bkerensa> that looks great
[06:24] <bkerensa> good work on that
[06:24] <godbyk> Thanks.
[06:24] <bkerensa> godbyk: so I checked and committters cant add committers so mdke cant add you
[06:24] <bkerensa> I would just ping pleia2 tomorrow since there has been no objections
[06:24] <godbyk> As I feared, though, our UDS session attracted a bit of attention (i.e., potential contributors wanting to help) that we're not quite yet ready for.  :)
[06:25] <bkerensa> and perhaps she or someone else on the CC can add you
[06:25] <bkerensa> godbyk: indeed
[06:25] <godbyk> Ah, okay. I'll check into tomorrow.
[06:25] <bkerensa> it means perhaps we need to work to get the getting started done sooner
[06:25] <bkerensa> :D
[06:25] <godbyk> Yes.
[06:25] <godbyk> I think our getting started docs need to get finished ASAP.
[06:26] <godbyk> Then we can distract our new contributors with fixing bugs and improving documentation while we sort out all the other background details. ;-)
[06:26] <godbyk> Matt said he wouldn't mind answering questions if we get stuck or whatnot, but that he's otherwise going to be quite busy with other work.
[06:27] <godbyk> So we do still have him as a source if we get completely stuck on something.
[11:44] <knome> is somebody who is taking care of the server guide administration side here?
[20:28] <ahoneybun> mhall119:
[20:34] <mhall119> ahoneybun: ?
[20:34] <ahoneybun> can you help me make a docbook?
[20:45] <ahoneybun> make the package I mean
[22:58] <godbyk> jbicha: Would you suggest that I fix typos in the raring branch or should that be frozen now?
[23:08] <bkerensa> woah jbicha returns
[23:08] <bkerensa> :D
[23:10] <godbyk> jbicha: I just fixed a bug and set the status to 'fix committed'. Should I attach the bug to a particular milestone so it's easy to find later when we release the 13.10 docs and want to mark the bug as 'fix released'?