kim0 | Hi, is there some markup language that generates moinmoin wiki (for w.u.c), html, and pdf easily ? | 00:22 |
---|---|---|
jbicha | kim0: not sure, what do you need all of that for? | 00:36 |
Captainkrtek | jbicha, any pages you need focused on tonight? | 00:43 |
Captainkrtek | or just do whatever | 00:43 |
jbicha | nothing in particular, did you see my email this morning? | 00:43 |
Captainkrtek | umm | 00:43 |
Captainkrtek | let me look | 00:43 |
Captainkrtek | what was it titled | 00:44 |
jbicha | Driver doc page | 00:44 |
Captainkrtek | gotcha | 00:45 |
Captainkrtek | I can fix that | 00:45 |
jbicha | personally I'm mostly done with the Natty docs and we're not ready to mess with Oneiric yet | 00:46 |
Captainkrtek | k | 00:46 |
Captainkrtek | Im also starting with with ubuntu-manual | 00:46 |
jbicha | so I'm working with gnome 3 packaging stuff for fun, and I'll also work with Gnome upstream docs if I make time for it | 00:47 |
Captainkrtek | yeah I'll try to figure out the gnome stuff | 00:47 |
Captainkrtek | any idea when oneiric work will start? | 00:47 |
jbicha | Natty has 2 printing pages that need done, install a printer and set as default but it may take me a few days to get to it | 00:47 |
Captainkrtek | I can do that today maybe | 00:48 |
Captainkrtek | Ill put natty on a live cd and run it on my downstairs PC | 00:48 |
jbicha | oneiric can start once we get natty finalized, starting before that means we have to merge any natty changes | 00:50 |
jbicha | and you can make your own branches for stuff if you want to try something different | 00:51 |
jbicha | or have changes that aren't ready for our main branch or something | 00:51 |
jbicha | a bzr shared repo would probably be handy for working with multiple branches but I haven't learned how to effectively use one yet | 00:52 |
Captainkrtek | was talking to j1mc yesterday | 00:56 |
Captainkrtek | about setting deadlines more specifically | 00:56 |
jbicha | the way I understand the freeze we're in now for Natty is we can still make necessary changes and we can still add content but we shouldn't make other changes | 00:58 |
jbicha | so as not to annoy our translators | 00:58 |
Captainkrtek | true | 00:58 |
Captainkrtek | so now just work on stuff like stubs | 00:58 |
jbicha | not exactly, a lot of those stubs were just for brainstorming and we don't necessarily need them now | 00:59 |
Captainkrtek | k | 00:59 |
jbicha | I was confused on that myself, the first thing I did was spend a bunch of time on the cheese stub which worked and is useful | 01:00 |
Captainkrtek | how long have you been working on ubuntu-docs ? | 01:00 |
jbicha | but we don't necessarily need the other app- stubs now, I think Gnome's idea was it was supposed to be a quick advertisement | 01:01 |
jbicha | with an install link or documentation link | 01:01 |
jbicha | a few weeks but I was interested for a year | 01:01 |
Captainkrtek | ahh cool | 01:01 |
Captainkrtek | I'm trying to pick this up quickly, appreciate the tips and pointers | 01:02 |
jbicha | yeah, no problem, we have to keep new contributors happy or they'll find something else to do :-) | 01:02 |
Captainkrtek | hehe | 01:03 |
Captainkrtek | feed us more hot pockets ;-) | 01:03 |
Captainkrtek | jbicha, one Q for you, how often do our commits get pushed to updates? | 01:07 |
jbicha | well, all SRUs have to get approval from the SRU team and first go to -proposed | 01:08 |
Captainkrtek | gotcha | 01:08 |
jbicha | then if enough good feedback is received on the SRU bug, it is then pushed to -updates | 01:08 |
Captainkrtek | how long does that usually take? | 01:09 |
jbicha | it could be a few days, if there's no feedback then it can even get removed from -proposed without going to -updates | 01:09 |
Captainkrtek | oh interesting | 01:10 |
Captainkrtek | still learning the ropes around here hehe | 01:10 |
Captainkrtek | there's a process for everything :-) | 01:10 |
jbicha | SRUs and backports are a bit of a hassle, it's a lot easier to get stuff fixed before release freeze | 01:13 |
Captainkrtek | yeah | 01:13 |
Captainkrtek | also, what about editing the official wiki? | 01:13 |
jbicha | anyone can do that, do enough good stuff and you can get wiki admin prilileges to edit restricted page or delete pages | 01:15 |
Captainkrtek | ahh cool :) | 01:15 |
Captainkrtek | was referring to: http://help.ubuntu.com/ | 01:16 |
Captainkrtek | like the official documentation wik | 01:16 |
Captainkrtek | that just our .pages ? | 01:16 |
jbicha | https://code.launchpad.net/~ubuntu-core-doc/ubuntu-docs/help.ubuntu.com | 01:18 |
Captainkrtek | oh cool | 01:18 |
jbicha | and help.ubuntu.com pulls from there overnight or something | 01:18 |
Captainkrtek | ahh nice :) | 01:18 |
jbicha | that doesn't need SRU or anything | 01:18 |
Captainkrtek | very cool | 01:18 |
Captainkrtek | going to pull that branch | 01:19 |
jbicha | mdke syncs our branch with that one as needed | 01:19 |
Captainkrtek | gotcha | 01:19 |
Captainkrtek | do you work much with that branch? | 01:19 |
jbicha | no, it's just snapshots of the other branches | 01:20 |
Captainkrtek | okay | 01:20 |
Captainkrtek | jbicha, any projects you can reccomend to work on besides ubuntu-doc and ubuntu-manual? | 01:28 |
jbicha | there's the server guide, kubuntu-docs, etc. | 01:30 |
Captainkrtek | okay :) | 01:30 |
jbicha | you can find some app that needs better docs, like this one for instance: | 01:30 |
jbicha | https://live.gnome.org/Evolution/DocRewrite | 01:30 |
Captainkrtek | thanks :) | 01:31 |
jbicha | there are apps that no one is working on yet, so you can write the whole thing if you want | 01:31 |
jbicha | but you probably should work with somebody at first to help you with syntax & writing style | 01:31 |
Captainkrtek | just requested permissions to the gitorious | 01:38 |
Captainkrtek | on that app | 01:38 |
Captainkrtek | thanks for all the help jbicha :-) | 01:39 |
jbicha | I'd expect you should introduce yourself too | 01:41 |
Captainkrtek | in the mailing list? | 02:07 |
jbicha | if you're asking for commit access, the people controlling that want to know you are | 02:15 |
Captainkrtek | good point | 02:15 |
Captainkrtek | just list my experience? | 02:15 |
jbicha | yeah, just say who you're are, what you've done, and why you need it | 02:15 |
jbicha | some people like to see patches first, I don't know about this group | 02:16 |
Captainkrtek | "why you need it" Should I ask up front then? like "im requesting..." | 02:17 |
jbicha | not sure I understand you, but you should say something about why you requested commit privileges | 02:29 |
Captainkrtek | oh | 02:29 |
Captainkrtek | already sent :/ | 02:29 |
jbicha | I meant "introduce yourself to the guys using gitorious" but it's good anyway | 02:56 |
Captainkrtek | ohhhhh | 02:56 |
Captainkrtek | whoooooops | 02:56 |
jbicha | because I'm not part of the Evolution docs rewrite, just mentioned it as an example | 02:58 |
Captainkrtek | thought you meant for the Ubuntu-docs team | 02:58 |
Captainkrtek | whoopsie... | 02:58 |
Captainkrtek | jbicha, you online? | 07:43 |
Captainkrtek | jbicha, if so: http://bazaar.launchpad.net/~steven.richards/+junk/gnome-help/revision/1562 | 07:44 |
Captainkrtek | fixed that drivers page, or just check your email | 07:44 |
=== Pendulum_ is now known as Pendulum | ||
Captainkrtek | jbicha, you here? | 22:32 |
=== Captainkrtek is now known as feeyoisthebest | ||
=== feeyoisthebest is now known as Captainkrtek | ||
Captainkrtek | hey Rocket2DMn you have commit rights ? | 23:42 |
Rocket2DMn | hi Captainkrtek , yes i do | 23:44 |
Captainkrtek | could you look at this patch: http://bazaar.launchpad.net/~steven.richards/+junk/gnome-help/revision/1562 | 23:45 |
Rocket2DMn | i'm seeing some spelling mistakes | 23:46 |
Captainkrtek | oh | 23:46 |
Captainkrtek | let me fix those | 23:46 |
Rocket2DMn | "that beings with" "for thee word"... | 23:46 |
Captainkrtek | whoops | 23:47 |
Rocket2DMn | Hardward section | 23:47 |
Captainkrtek | ill fix all those, one sec | 23:48 |
Rocket2DMn | <item><p>1. Run the command - you dont need to number the list manualy | 23:49 |
Captainkrtek | Rocket2DMn, I ported this document from the official wiki | 23:49 |
Captainkrtek | I know, I had some issues with getting sub-lists | 23:49 |
Rocket2DMn | i expect you should be able to embed lists in mallard | 23:50 |
Captainkrtek | I tried using <tree> | 23:50 |
Rocket2DMn | tbh i'm not a big fan of porting much wiki documentation to the system docs, so much of it is very specific and difficult to maintain | 23:50 |
Captainkrtek | it was a syntax nightmare to embed it | 23:50 |
Captainkrtek | yeah | 23:50 |
Rocket2DMn | anyway, you could probably do <list><item><p><list>... | 23:51 |
Rocket2DMn | may not need the <p> | 23:51 |
Captainkrtek | tried | 23:51 |
Captainkrtek | didn't work | 23:51 |
Captainkrtek | :/ | 23:51 |
Rocket2DMn | hmm documentation seems to indicate that you can | 23:52 |
Captainkrtek | I did follow the documentation | 23:52 |
Captainkrtek | let me try again | 23:52 |
Rocket2DMn | looks like there is a "type" attribute so you can number the list with "numbered" value if that's what oy uwant | 23:53 |
Captainkrtek | yeah | 23:53 |
Captainkrtek | <list type="numbered"> | 23:54 |
Captainkrtek | im trying it again | 23:54 |
Rocket2DMn | i would take out all the links to the wiki anchors | 23:55 |
Captainkrtek | all the other wiki docs online? | 23:55 |
Rocket2DMn | not saying dont link to the wiki where appropriate, but were you have something like: Run the command <link href="https://help.ubuntu.com/community/WifiDocs/Wireless | 23:55 |
Rocket2DMn | 23:55 | |
Rocket2DMn | 122 | 23:55 |
Rocket2DMn | TroubleShootingGuide/Commands#iwlist">sudo iwlist</link> | 23:55 |
Captainkrtek | yeah | 23:56 |
Captainkrtek | true | 23:56 |
Rocket2DMn | not sure if that's just the diff causing problems, but i wouldnt break up a link across lines either | 23:56 |
Rocket2DMn | that's a rather large diff, i dont really have time to review it all right now, i literally just walked in from work when i logged in, gotta go make some dinner here shortly | 23:57 |
Captainkrtek | okay no problem | 23:57 |
Captainkrtek | ill keep working on it | 23:57 |
Rocket2DMn | in any case, i wouldnt let the directions get too technical, there is no need to maintain complex directions in the system docs ,you can always link to the wiki for additional support | 23:58 |
Rocket2DMn | common troubleshooting steps are good to have though | 23:59 |
Captainkrtek | yeah | 23:59 |
Captainkrtek | true | 23:59 |
Captainkrtek | ill remove some of the steps | 23:59 |
Rocket2DMn | like i said, i havent reviewed it all, there could be some great directions in there, it's difficult to see from the diff how complex or difficult they are to follow | 23:59 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!