[03:45] mimico: I'm thinking about stubbing the booklet pages from Ubuntu's help for this release [03:46] because LO doesn't need it [03:49] jbicha, you mean take them out completely? [03:50] I think they mainly pertain to Evince anyways. [03:51] hello [03:52] mimico: basically, maybe they could be cleaned up for a later release [03:53] interested in getting involved with the doc. team [03:53] reading up on it [03:55] Captainkrtek: have you used bzr before? [03:55] jbicha, it was written initially with only Evince in mind, so taking it out is okay by me. [03:56] jbicha, I'm afraid I have not [03:56] mimico: ok, thank you [03:56] but I have experience in MediaWiki, technical writing, and open source documentation and development [03:56] mostly for Android [03:59] unfortunately we don't use MediaWiki [03:59] yeah [03:59] but I have the writing experience [03:59] I have also written for a portal with over 3-4 Million views a month [03:59] there's 2 parts to docs, the wiki & the user help [03:59] on technical topics [03:59] yeah [03:59] I'd be interested more in the wiki [04:00] spent lots of time in wikis [04:01] what about the documentation onboard the OS? [04:01] or do you have to first prove yourself [04:02] no, for the system docs, you'll just need to learn bzr :-) [04:03] ive used GIT before [04:03] and gerrit [04:03] and the docs are written in mallard (older docs are written in docbook) [04:03] so i've used revision control before [04:03] gotcha [04:03] lots to learn :-) [04:04] yeah, bzr is similar to git but different [04:04] https://wiki.ubuntu.com/UbuntuDevelopment/GettingSetUp [04:05] you need a GPG key and do the stuff in setting up your dev environment [04:05] trying to setup my key right now [04:06] is it a huge learning curve from GIT? [04:09] I've used bzr more so I couldn't tell you [04:09] I think newer bzr users don't like git because it's more complex, git users don't like bzr [04:09] because it's slower & doesn't do everything git can [04:10] hmm [04:10] ill have to check it out [04:10] I'd love to give back through this community :) [04:13] generating the key [04:13] this is taking a bit :P [04:18] so what do you work on jbicha ? [04:20] I've been getting the user guide into shape for Natty, basically changing the Gnome 3 [04:20] stuff to describe Unity instead [04:20] cool :-) [04:20] I have not upgraded to natty yet [04:21] probably should do that [04:32] k gpg and ssh keys setup [04:39] jbicha, K I went through that whole guide [04:40] ok, the pbuilder part isn't needed for documentation [04:40] oh okay [04:40] still did it hehe [04:40] so where can I get started? [04:41] looking at some pages... [04:41] https://code.launchpad.net/~ubuntu-branches/ubuntu/natty/gnome-user-docs/natty [04:41] oops, that's not it [04:42] hehe [04:42] my launchpad id is steven.richards btw [04:42] https://code.launchpad.net/~ubuntu-core-doc/gnome-user-docs/natty [04:43] so as you can see on that page, you'll need to run [04:43] bzr branch lp:~ubuntu-core-doc/gnome-user-docs/natty [04:43] yeah [04:43] running :) [04:43] let me know when it's done downloading [04:43] okay! [04:44] thanks for getting me set up I appreciate it :) [04:52] jbicha, it's done [04:53] ok, conveniently the help doesn't require compilation to be viewed [04:53] k [04:53] so you can just cd into gnome-help/C/ [04:53] and then run yelp . [04:53] to view the help as of right now [04:54] very cool [04:55] but it won't look quite right if you're not using yelp 3 which is in natty [04:55] gotcha [04:55] m running 10.10 [04:55] im* [04:55] so go through the files [04:55] edit them [04:55] save em [04:55] how would I submit the change using bzr? [04:56] https://wiki.ubuntu.com/DocumentationTeam/SystemDocumentation/Submitting [04:56] either bzr bundle and email the mailing list [04:56] and then for [04:56] bzr push lp:~yourusername/ubuntu-docs/branchname [04:56] Id to [04:57] bzr push lp:~krtek/natty/gnome-help/C [04:57] s/to/do [04:58] I do it more like bzr push lp:~jbicha/gnome-user-docs/display-typos [04:59] oh [05:00] what's the difference? [05:00] if im working in /C [05:00] because the final part is your branch name and you can pick whatever you like [05:00] ahh [05:00] so no difference really [05:00] might as well make it easy to recognize what that branch does [05:01] yeah [05:01] and then the files tagged .stub [05:01] arent done yet [05:01] right, so not visible to users, but you can do yelp --editor-mode . [05:02] if you really want to see them or read comments [05:02] Unknown option --editor-mode [05:03] that only in yelp 3? [05:03] I guess, you can check yelp --help [05:04] it doesn't actually edit, it just shows some extra stuff [05:09] hey jbicha sorry about that [05:09] wifi cut out [05:09] np [05:09] what editor do you use [05:11] gedit actually [05:11] me too :) [05:12] and what is the syntax called we are writing in? [05:12] need to find a guide [05:12] http://projectmallard.org/ [05:13] bookmarked [05:13] time to get to work [05:13] thanks again for the help! [05:20] I pushed an update, so you can do bzr pull to get the latest [05:20] very cool, updating now :) [05:20] Im going to try to make a change [05:22] quick question if you don't mind [06:42] hello mimico [06:43] do you have a minute to help answer a question? [06:46] or anyone [06:47] jbicha, you still around? [06:47] Captainkrtek: yes, for a bit longer [06:47] okay great [06:47] so I just edited display-2monitors.page.stub [06:48] ran the check_validation.sh [06:48] ./check_status.sh is useful [06:48] said it validates [06:48] no return on check_status [06:48] I can't yelp display-2monitors.page.stub either. [06:49] any idea? [06:50] bzr mv display-2monitors.page.stub display-2monitors.page [06:50] and then yelp . will show it [06:51] he requested URI "display-2monitors.page" is invalid [06:51] The* [06:51] um, are you sure it validates then? [06:52] krtek@krtek:~/natty/gnome-help/C$ ./check_validation.sh display-2monitors.page [06:52] --Validating display-2monitors.page ... [06:52] display-2monitors.page validates [06:52] :/ [06:52] just do yelp . don't try specifying the specific page [06:53] then search for it? [06:53] yes, there's a trick to do a specific page in yelp 2.32 but I'd have to google it [06:53] everything I own is running Natty at the moment [06:53] hmm [06:54] can I pastebin the file? [06:54] see if it looks right to you? [06:54] did you get it to open yet? [06:54] nope :/ [06:54] http://pastebin.com/M9FpmjD6 [06:54] couldn't find it [06:54] oh wait [06:55] hmmm [06:55] can't find it... [06:56] oh [06:56] found it :) [06:57] good [06:57] wasn't easy [06:57] is there a way to submit an update but not a final one? [06:57] like I will make changes to this one [06:57] it would be better to get it mostly final before submitting [06:57] yeah [06:57] did the pastebin look okay? [06:58] need to read the style guide... [06:58] well it needs more work, you'd probably find it easier to read or edit existing pages instead of creating a stub [06:58] okay [06:59] I just found that one [06:59] that was an existing stub [06:59] you picked an important topic but it's ok if it doesn't get done in time for 11.04 [06:59] I can get it done tomorrow hopefully [06:59] yes, the stub is from Gnome [06:59] how long will it take to get approved? [07:00] review shouldn't take more than a couple days at most, maybe much faster [07:00] approval depends on quality :-) [07:01] okay [07:01] any tips for me [07:01] we appreciate the help [07:01] based on that pastebin? [07:01] don't use tabs, use spaces [07:02] spellcheck, compare to already existing pages for tricks like guiseq [07:02] okay [07:02] so like download an old branch? [07:02] no, compare to other pages in the guide [07:02] what about detail? is that long enough [07:02] okay [07:02] to learn how to use the syntax [07:02] yeah [07:02] is there a way to include images? [07:02] like screenshots [07:03] yes, but space is limited so I'm not sure if we actually need one [07:03] okay [07:03] the gnome-user-guide is shipped on the CD [07:03] ahh [07:03] wow [07:03] :) [07:04] maybe I can get something on there before release :) [07:04] 11.04's CD is basically done though [07:04] oh [07:04] no, they'll only rebuild the CD image for urgent bugfixes [07:04] darn [07:04] but there are updates [07:05] yes [07:05] :) [07:05] very cool [07:06] yes, it's neat to see your name in the changelog [07:07] yeah [07:07] it's a cool project [07:07] how long have you been doing this? [07:08] also, is this, http://pastebin.com/4Z9XgnaR , what should be in the guide? [07:09] about 3 weeks for the user guide, I had a bunch of free time [07:11] comments aren't visible to end users, it was just notes from Gnome about what they thought should be on the page [07:12] a significant amount of Gnome's guide was only written in March [07:12] http://j1m.net/2011/03/19/gnome-3-documentation-hackfest/ [07:14] but I was interested in Gnome help for a year, I should have jumped in sooner [07:18] hey [07:18] sorry had to reconnect [07:19] but I was interested in Gnome help for a year, I should have jumped in sooner [07:19] cool [07:19] I have a friend who does some gnome work [07:19] think he does design [07:19] it's a bit easier to write & edit the new help once more of it is written [07:19] back then, Mallard was quite new [07:19] yeah [07:20] how do you edit the sub title text on yelp for an item? [07:20] like this [07:20] http://i.imgur.com/ax6Qu.png [07:21] see there is no text below second monitor [07:21] that's the desc field [07:22] got it :) [07:22] thanks [07:27] shouldn't dual displays go under hardware? [07:27] oh nvm [07:29] if you're still here just have one final thing [07:30] ok [07:30] the comment section [07:31] is that a request, like "please include details on blah blah blah" [07:34] if you're able to include the important stuff then you don't need to write comments [07:34] k [07:34] might be able to get this one close to done tonight [07:34] it is a note to other writers and editors [07:34] gotcha [07:44] Think I have this one done :) [07:46] I'm done for tonight, talk to you later! [07:46] okay me as well, goodnight! [08:13] hey dpm [08:17] well, that was a short conversation === czajkows1i is now known as czajkowski [22:37] mdke: howdy [22:37] jbicha: heya [22:38] I thought it would simpler to link to an app than telling users to search for one or [22:39] I think the instructions should be app independent really [22:39] telling them to click through Get Software, down arrow, Canonical Partners [22:39] ideally there would be a check box in software sources for the partner repo, as there was in previous releases, but I didn't see one when I tested so I used the apt line [22:40] oh, there's a check box [22:40] perhaps it was added after the version I have got [22:40] I'm a week or two out of date [22:41] it could be because you've been upgrading for a while [22:42] I haven't upgraded at all, I have a daily live usb from the daily snapshot a week or two ago [22:42] but I haven't kept it up to date as that takes up a lot of disk space [22:42] interestingly, if you delete the "Canonical Partners" repo from Software Sources, the "Use This Source" button can add it back for you [22:43] * mdke nods [22:43] jbicha: to change the subject briefly, have you by any chance gone over the topics which you reviewed prior to getting commit access and marked them as final? If not that would be useful. [22:43] You've made amazing progress over the last few days [22:44] == SUMMARY == [22:44] None: 0 [22:44] Stub: 6 [22:44] Incomplete: 1 [22:44] Draft: 3 [22:44] Review: 23 [22:44] Candidate: 10 [22:44] Final: 92 [22:44] Outdated: 92 [22:44] pretty awesome :) [22:44] bbl [23:44] hello [23:44] jbicha, you here? [23:44] Captainkrtek: hi [23:44] hello [23:45] so last night I finished a doc [23:45] committed locally [23:45] and emailed the mailing list [23:45] but I dont think anyone has seen it [23:46] no, we saw it [23:46] oh okay :) [23:46] you should upgrade to 11.04 [23:46] yeah [23:46] I was going to last night [23:47] I will in about 20 minutes, is it good though? [23:47] the user guide is written based on the Unity desktop, so System>Preferences>Monitors isn't how we do it now [23:47] oh.... [23:47] whoops [23:48] so I'll rewrite it [23:48] once I upgrade [23:49] other than that issue, how is it style wise? I tried using some syntax from the mallard docs [23:52] use status="review" instead of making up a status [23:53] oh [23:53] I didn't make that up [23:53] I saw it somewhere in the editing guide [23:54] the wiki? the wiki talks about docbook so it's out of date [23:54] https://wiki.ubuntu.com/DocumentationTeam/SystemDocumentation/Checking [23:55] on the bottom [23:55] I used "writing" if I remember right [23:55] that page was last edited 2 years ago :-) [23:56] whoops [23:56] hehe [23:56] didn't know where else to look [23:56] basically projectmallard and already existing docs are where you should look [23:57] okay gotcha [23:57] thanks for all the help [23:57] sorry for bothering [23:57] we're going to update the wiki but because we're trying to finish up natty's docs it might not get done this week [23:57] okay [23:57] no, you're not a bother at all [23:58] well thanks for your patience in helping a nuub :-)