[12:10] mdke, how are those minutes coming ^^? lol [12:11] Oh, up, cool. [12:12] squinn: On the mainling list, or online? [12:12] *mailing [12:12] Online, JonA. [12:13] squinn: Thanks. [12:14] https://wiki.ubuntu.com/DocumentationTeamMeetingSummary5 [12:14] https://wiki.ubuntu.com/DocumentationTeamMeeting20050616 as well === Seveas [~seveas@seveas.demon.nl] has joined #ubuntu-doc [12:18] Welcome back, Seveas. [12:18] ty [12:30] ooh is the list back? [12:30] on [12:30] damn, still nothing [12:31] was just gonna say it ;) [12:31] what's up with the lists anyway? [12:31] how are ya Seveas [12:31] not too bad [12:32] been manually compiling C code today (and that means manually writing assembly crap) [12:32] so i'm kinda cooked :) [12:32] *grins* === Burgundavia [~corey@S0106000000cc07fc.gv.shawcable.net] has joined #ubuntu-doc [12:34] mdke, sorry I had to leave meeting. I can volunteer for some projects..if I'm neeed. [12:34] needed.* [12:35] squinn, that is cool. Check out the docteam wiki pages and the archive see what interests you [12:35] hi burgs [12:35] salut [12:36] anyone else got got by NMs cute little bug? [12:36] sup? [12:38] mdke: In general, I'd be looking at a GNOME Project. Right now, ' [12:38] I'm over-abundant on time, so I'm not in a crunch* [12:43] squinn, great [12:44] mdke, I also just added Install Guide to DocTeam Projects. [12:44] Tenatively, I put No Info Page, No Status Page, and No Preview. [12:45] ok i see it [12:45] cool thanks [12:45] Not a problem. [12:49] mdke, question [12:50] wait, maybe nevermind [12:53] mdke, is there a way i can subscribe to all bugs assigned to ubuntu-doc? === JonA [~jonathan@alxpc1jaa2.alx.aber.ac.uk] has joined #ubuntu-doc [01:24] squinn, to be honest we don't tend to use bugs much [01:27] mdke: Are you free for me to ask some questions about the GNOME docs? [01:30] gimme a bit [01:30] JonA, just need to tidy something up [01:30] JonA, gonna be around in 15? [01:30] No rush :-) [01:30] mdke: Yeah. [01:30] what time zone is wales in? [01:30] :p [01:36] GMT, so it's 12:36 am here :-) [01:43] here I am! [01:44] JonA, i'll try and answer your questions, but I am no expert [01:46] JonA? [01:46] mdke: They're not really technical questions :-) I was just wondering what would be the best way to go about tackling the GNOME guide. Are there any sections which are flagged for revision, or is there a general consensus (which I've missed) of how it needs to be updated? [01:46] squinn: Yo? [01:46] JonA, the userguide or quickguide? [01:48] for the userguide, essentially the thing is pretty disorganised, there are lots of sections that haven't been written, and others that need revision [01:48] The userguide. [01:48] for the quickguide, since it was shipped for hoary, its a question of updating, and no plan has yet been done (to my knowledge) about that [01:48] aha [01:48] Should I just grep around for authorblurb sections and see what I find? [01:49] JonA, if you feel up to starting to write sections that are not yet done at all, that would be awesome [01:50] JonA, ideally sections get marked with "done/to revise" etc but the problem is that different authors have different ideas about when that stage is reached ;) [01:50] the userguide is so young right now that i don't think we need to worry too much [01:50] it ALL needs revision ;) [01:50] in general, the earlier sections are better done than the later ones [01:51] mdke: Right, I guess I'll have a stab at some of the sections which haven't been started. [01:51] that would be awesome [01:51] JonA, couple of things to bear in mind are that there is plenty of info to draw on in the wiki/forums, and that the user target of the guide is beginner [01:52] otherwise, run amok [01:52] JonA, you can open the xml files in yelp to read through what is already there [01:52] Okay, well, I'll try to write a couple of sections tomorrow and get a patch up. If I'm doing anything terribly wrong, I'll find out early. [01:52] yep [01:53] if you follow the basic procedure you won't go wrong [01:53] mdke: Yeah, I've checked it all out and I've been playing about, seems simple enough. [01:53] https://wiki.ubuntu.com/DocteamStepByStepRepository is good [01:54] if you validate and check your work visually as described there, you are good to go [01:54] mdke, I think I'll work [lead if needed] on the About Ubuntu page [01:55] squinn, cool [01:55] hopefully not a lot will change for breezy so that document will just need updating === gepatino [~gabriel@200.68.127.46] has joined #ubuntu-doc [01:58] when the mailing list is sorted we can start organising that stuff [01:59] hi gepatino [01:59] hi [01:59] just looking [01:59] welcome :D [02:00] i'd like to help somehow in the ubuntu project [02:00] cool! [02:00] right now i dont have much time [02:01] but i'd like to know what options do i have to help [02:02] ooh lots of things [02:02] you can contribute to the documentation writing project in our archive or on the wiki, or help people on the forums, or help people here in irc in #ubuntu [02:03] or on the mailing list [02:03] i've been helping with translations into spanish (my primary language) [02:03] thats another great way [02:03] but it's almost anything already translated :) [02:04] do you work with the spanish locoteam to get translations done? [02:05] no, i've just entered in the rosetta site and translate when i have some free time [02:05] before breezy there will be lots of documentation to be translated :) [02:05] ah good idea [02:05] mmm sounds good [02:05] gepatino, some of our existing documentation is in rosetta [02:07] but hopefully lots more will be for Breezy [02:08] should i belong to the spanish translation group to make my stranslations effective? [02:09] i've applied to that group, by haven't got any answer yet [02:09] no no [02:09] all translations in rosetta are effective [02:10] ok, i'll take a look again in rosseta [02:11] thanks for your time [02:11] any time [02:11] see you [02:11] yeah [02:11] bye! === gepatino [~gabriel@200.68.127.46] has left #ubuntu-doc [] [02:23] night all === FLeiXiuS [~fleixius@pcp0011790326pcs.essex01.md.comcast.net] has joined #ubuntu-doc === jsgotangco [jerome5@dialup-222-126-74-185.infocom.ph] has joined #ubuntu-doc === ealden [~ealden@219.90.91.99] has joined #ubuntu-doc === _jeff [~jeffsch@fatwire-201-201.uniserve.ca] has joined #ubuntu-doc === gtaylor [~gtaylor@24-158-66-230.dhcp.spbg.sc.charter.com] has joined #ubuntu-doc [08:22] howdy === froud [~sean@ndn-165-146-74.telkomadsl.co.za] has joined #ubuntu-doc [08:34] African greetings [08:44] Canadian Greetings [08:46] a lot of interesting discussions on the channel in the last 24 hours. I finally went throught the backlogs earlier today [08:46] Ah yes [08:46] very interesting [08:46] how do you feel about them? [08:47] Its ok if you think I am totally out of wack, honest [08:47] morn gtaylor [08:48] morn JonA [08:48] Burgundavia: [08:48] personally I think it makes sense to do everytnig in xml, and from that source produce in whatever format is needed for packaging. [08:49] Hmm is lists.u.c is still not working [08:49] robitaille: OK [08:49] still down. It's getting a bit annoying. They filled up a hard drive many hours ago; I wonder why it hasn't been cleared yet [08:50] I guess it takes time [08:50] Maybe they will rush in the transition to the new lists.ubuntu.com that was supposed to be done shortly anyway. [08:50] maybe [08:50] system problems often occurs on Friday nights :) [08:51] I see the logs are also stuck [08:51] yeah, typical [08:51] robitaille: are you now setup and ready for work? I cant remember [08:53] yes. I just haven't found the time yet. But I have been pulling in updated stuff from the repo from time to time to look at them. So I'm all setup; I just need to get myself in gear to do something :) [08:53] :-) yeah [08:53] sometimes that can take time [08:53] we need you to do a few god patches [08:53] good [08:54] then we can get you a commit account [08:54] And I still want to sit down to read that Docbook Guide you sent earlier. [08:54] Which Bob Staytons book? [08:54] yes [08:54] Oh most excellent [08:55] I think everybody on the team should read it [08:55] but its a big book, lots to undersatnd [08:55] Bokker tov sivang [08:56] robitaille: but that should notstop you from writing [08:56] if you know what it is you want to write that is:-) [08:57] I know. The guide is for my personal learning enjoyment. I had no idea about all these documentation things only a few weeks ago; and I have been working with computers for years. [08:57] JonA: if you have time I can help you get setup [08:58] Once I have a good knowledge base, I want to push a more organized way of doing docs at my workplace. [08:58] yeah, docbook is a blessing and a curse all the same [08:59] robitaille: workplace [09:02] I'm back (one of my kid got up). Yes; I work for a research group of the Canadian government, and ours docs are a bit disorganized; some done in text, some done with latex, some with framemaker [09:02] and some in html [09:03] Ah yes I remember now :-) === _froud [~sean@ndn-165-146-74.telkomadsl.co.za] has joined #ubuntu-doc [09:04] <_froud> argh split [09:04] we're small enough (~25 staff) that it should be easy to steer the few of us who need to write things in a certain direction..thus the docbook reading [09:05] yeah, It can work well for the technical docs === FLeiXiuS [~fleixius@pcp0011790326pcs.essex01.md.comcast.net] has joined #ubuntu-doc [01:36] froud: Morning. I've pretty much got myself set up, I think. I've checked out the tree, and I've been playing with making some edits and patches. === ealden [~ealden@219.90.92.252] has joined #ubuntu-doc [02:38] email is now trickling in slowly [03:58] squinn, around? [05:07] yep, mdke [05:07] or..i wasn't lol === robitaille [~robitaill@d154-5-117-228.bchsia.telus.net] has joined #ubuntu-doc [06:10] squinn, np i replied on the list [06:23] mdke, to answer your question in your email about the minutes to the last doc meeting and where they should be sent, you should just ask mako to give you access to -news. He did that semi-recently with dholbach for the MOTO reports. [06:23] robitaille, i mentioned it to him yesterday, i'm not sure if he is gonna post it himself [06:25] maybe this time...but in the future you probably want to do it yourself. He is so busy, it's probably the best way for the emails to be sent in a timely manner [06:25] yes [06:25] I would have thought he would say that [06:25] we'll see what he thinks [06:26] and of course all these reports will one day be available on "The Fridge" :) [06:27] hmm [06:27] i need to check that out [06:27] is there a testing project? or just the spec [06:33] it's still mostly a spec. jdub has a live site going on his own server, but it's still pretty basic, and a work in progress. [06:33] it's nice to finally have e-mails back from the lists :) [06:34] have you got a url for it? [06:34] if you post to -news, mako or i will moderate it through [06:34] mdke: it's not public yet [06:34] jdub, ok cool [06:35] jdub, is -news the appropriate list? [06:35] sure [06:36] ok [06:36] thanks :) === froud [~sean@ndn-165-146-74.telkomadsl.co.za] has joined #ubuntu-doc === squinn [chaos@68.205.198.0] has joined #ubuntu-doc === Seveaz [~seveas@seveas.demon.nl] has joined #ubuntu-doc === squinn [~squinn@68.205.198.0] has joined #ubuntu-doc [07:54] mdke, I'm here. [07:55] squinn, hi [07:55] hey [08:08] mdke, you were looking for me earlier/ [08:09] squinn, yes, I replied on the list :) [08:11] ah, ok, lemme take a look === buzzle [~adsfase@pcp04528012pcs.valenc01.az.comcast.net] has joined #ubuntu-doc [08:17] hey everyone [08:18] Hey buzzle [08:18] im having trouble connecting to my lan in ubuntu [08:19] suggestions? [08:19] using wireless [08:22] hm [08:22] i'd suggest #ubuntu [08:22] but h/o a sec [08:22] just found it [08:22] thank you [08:23] oh ok [08:23] enjoy buzzle [08:23] thank you :] [08:24] yeah, be specific' [08:24] what card..what drivers..that kinda stuff [08:24] i see [08:24] buzzle, because some one who has no idea of the card can't give help [08:25] i guess i was looking for basic set up info to start with [08:25] its not so much that my card is being an issue yet, as i cant figure out a basic set up to even see [08:25] ah ok [08:25] mdke, i don't see it? [08:25] i did get two messages from ubuntu-doc thouhg [08:26] ubuntu-doc-bounces ?! [08:33] Hmmm, where can I post a document on the xml or html debate? === JonA [~jonathan@alxpc1jaa2.alx.aber.ac.uk] has joined #ubuntu-doc [08:34] froud, mailing list [08:35] squinn, are you subscribed to the mailing list? [08:35] is it working [08:35] yes [08:36] squinn, its definitely there (http://lists.ubuntu.com/archives/ubuntu-doc/2005-June/002583.html). perhaps you are not subscribed [08:37] froud, it is definitely working [08:37] yes I just tested, thanks === gtaylor [~gtaylor@24-158-66-230.dhcp.spbg.sc.charter.com] has joined #ubuntu-doc === gtaylor [~gtaylor@24-158-66-230.dhcp.spbg.sc.charter.com] has left #ubuntu-doc [] === gtaylor [~gtaylor@24-158-66-230.dhcp.spbg.sc.charter.com] has joined #ubuntu-doc [08:43] aroo [08:44] I saw it finally, mdke. [08:45] On web..thanks. [08:45] Here comes my confirmation email from mailing list. [08:45] I was subscribed, but not approved yet, I believe. [08:47] mdke, thanks i'm fixing patch now [08:47] Looks like things have been busy this weekend [08:50] gtaylor, yeah. yesterday, seemed like lists were off or i just didn't get them [08:50] so i'm extra busy now [08:50] lists were down yesterday [08:51] hey gtaylor [08:51] mdke, question [08:52] is it possible to have all mail previously [for example: all conversations in the month of june] sent to list sent to my inbox? [08:53] not as emails, but you can get them in a news reader [08:53] http://news.gmane.org/gmane.linux.ubuntu.doc/ [08:53] ah okay [08:54] or can you just view them in a browser from that link [08:54] right ok [08:54] like how i read your mail [09:02] mdke, proofread the patch, sending now [09:02] cool [09:04] sent === Njal [~chatzilla@dsl-80-46-140-184.access.as9105.com] has joined #ubuntu-doc [09:04] Lo [09:07] hey Njal [09:07] I was on here yesterday seeing how i might be able to try to help with the documentation project [09:08] Well, I' [09:08] I'm not in charge, but I think I am [hehe] [09:09] What would you want to work with? [09:09] hey Njal [09:09] Again, I'm not in charge..I'm just curious. [09:09] froud told me that i would need setting up with the cvs system you use [09:09] svn [09:09] subversion, yes. [09:09] yup [09:09] I don't even think I've set mine up. [09:09] i presume i apt-get it? [09:09] Unless that's StepByStep thing was setting it up [09:09] apt-get install subversion does the binaries yes [09:10] Njal: read this https://wiki.ubuntu.com/DocteamStepByStepRepository [09:11] Oh, I did set it up then. :D [09:11] hey, froud, can you do me a favor? [09:12] yep [09:12] proofread the patch i just sent out on list [09:12] Njal: you should install xsltproc [09:12] will do, was it applied [09:12] no [09:12] mdke said it was pretty much there, just had to change a few things [09:12] Ok [09:13] I'm with Njal as well, in the n00b boat. === sivang [~sivang@box79162.elkhouse.de] has joined #ubuntu-doc [09:13] Ok will look at it [09:14] Thanks froud [09:14] squinn: Njal: hav eyou both installed xsltproc [09:14] you also need to ensure docbook is installed [09:15] as well as docbook-xsl [09:15] yes, all three installed here [09:15] install also poxml from kdesdk [09:15] ironically, just installed docbook-xsl..and okay [09:16] see also http://wiki.ubuntu.com/ForTheHasty [09:18] there, froud [09:18] yes [09:18] just about to read your patch === Njal [~chatzilla@dsl-80-45-186-84.access.as9105.com] has joined #ubuntu-doc [09:20] ok [09:20] welcome back Njal [09:20] thanks net just died for some reason [09:21] ok subvesion is now installed [09:22] subversion [09:23] how do i use it? Never had to use a versioning system before [09:23] the instructions on the wiki page froud posted should help a lot [09:23] kk [09:36] squinn: patch applied [09:36] thanks [09:37] squinn: did you ask questions about LearnLinux? [09:38] No. [09:38] That's another Sean [09:38] I'm Sean D. Quinn [09:38] There's some Sean C. something [09:38] sorry we now have three Seans, me included [09:38] Yep. [09:42] froud, I don't understand the second message I was supposed to /ignore [09:42] yes I fix the things in the first patch [09:42] and applied &kubuntu-download; and refer to main [09:47] ah ok works better [09:47] thanks [09:48] np [09:48] squinn: what are you going to work on? === Njal [~chatzilla@dsl-80-43-165-70.access.as9105.com] has joined #ubuntu-doc [09:50] Njal: how's it going [09:50] finally back [09:51] good [09:51] how far did you get [09:51] I got subversion installed [09:51] ok [09:51] di you get a checkout [09:51] I was also pointed to the wiki for further instruction [09:52] ok [09:52] you want to go through it [09:53] yes as im still not quite sure how to use a versioning system [09:53] ok in your home dir do svn checkout https://docteam.ubuntu.com/repos ubuntu-doc [09:54] hold [09:54] in your home dir do svn checkout https://docteam.ubuntu.com/repos/trunk ubuntu-doc [09:54] this will create a directory called ubuntu-doc/ [09:54] it didn't [09:55] it will add a working copy of the files in trunk to this folder [09:55] oh wait [09:55] give it time [09:55] the first checkout is big [09:55] it was asking me to accept something like a cookie that's why i didn't see it doing anything [09:55] it wasn't a cookie [09:55] are you in a shell session [09:55] yes [09:56] bash [09:56] ok select to permanently add it [09:56] I did do, it was a case of not reading something carefully [09:56] ok [09:56] give it a minute and you will see may lines starting with A [09:57] MMMMMMMMMMMAAAAAAAAAAAAAAAAANNNNNNNNNNNNNNNNNNNYYYYYYYYYYYYYYYYYYYY is right [09:57] OK that is the working copy downloading to the ubuntu-doc folder [09:57] lotsa .pngs though [09:57] yes [09:58] So lemmie just get my heard around this [09:58] head [09:58] ok [09:59] what you are copying to your disk is a copy of the code we all collaborate on [09:59] I am downloading everything that has ever been done on the documentation project, and like all other versioning systems only one person can work on one file at any one time? [09:59] not quite [09:59] ok [09:59] you are copying the HEAD version [09:59] Whats that then? [09:59] that is the current revision [10:00] ok [10:00] each of us has a copy [10:00] we hack our local copies [10:00] then we upload to the repository [10:00] if you have a commit account then you do this directly using the svn commit command [10:01] if you dont then you create a patch [10:01] Ok am lost now [10:01] and send it to our mailing list [10:01] Ok where did I lose your [10:01] you [10:01] the commit account bit [10:01] OK you dont have one at present [10:01] no [10:02] but if you are serious and give us a few patches we will arrange an account for you [10:02] until then you will be expected to create patches [10:02] I will lead you through this procedure [10:02] when the checkout is complete [10:03] I will also show you how to update your working copy or sync it with the repos [10:03] Ok so if i submit enough work to make it worthwhile giving me an account i get one, until then i just submit, the hacked local copies via email? [10:03] yes [10:03] ok it's starting to make sense [10:03] how's that checkout doing, is it finished [10:04] not yet [10:04] onto the gnome stuff now [10:04] OK [10:04] How do i edit these local copies? [10:04] I will explain it [10:04] ... in good time :P [10:04] Ok best way really [10:05] I take it you are new to this and have also never used docbook [10:05] but dont worry [10:05] its easier than it sounds [10:05] just takes the will from you to learn it [10:05] yes, this is all very new to me, to be honest i think i am trying to find my place in the community [10:05] what is your background [10:06] i have just finished a Diploma in IT practitoners (software dev), and am going on to learn networking/networked programing (software dev and deployment accross networks) [10:07] But [10:07] anyone can contribute to the docs, but knowing their background can help us in pointing you to work [10:07] I'm not that good at programming yet [10:07] Ok so you have technical knowledge [10:07] hows your knowledge of Linux [10:08] Historically i think it's reasonably good, but the working of it, getting there, still trying to learn how to recompile a kernel, just for the experience [10:08] I think you will do just fine [10:09] thanks [10:09] doing docs is a great way to learn [10:09] I think we are all learning in one way or another [10:09] I can see how it would be [10:09] The more i learn the more i realise i know nothing [10:10] :-) yeah [10:10] Checked out revision 1184. [10:10] beautiful [10:10] ok just gimme a sec b 4 we go on [10:10] sure thing [10:12] Ok have you subscribed to the commit list? [10:12] http://lists.ubuntu.com/mailman/listinfo/ubuntu-doc-commits [10:13] Njal: ? [10:13] not yet am going there now [10:14] Ok let me know when you have confirmed your subscription [10:15] is this a mailing list... of sorts? [10:15] yes [10:16] each time one of the members with a commit account adds something to the repos it will send out an email message [10:16] you never post to this list, only get stuff from it [10:16] you will see what I mean once you have subscribed [10:16] have you? [10:17] let me know when done, I need to know so I can demo for you [10:18] i am now subscribed [10:18] you confirmed your subscription? [10:18] yup [10:19] ok I am now going to make a commit [10:19] I am just commenting out a peice of code that is not critical [10:20] OK I did the commit. Refresh your mail client [10:20] Modified: [10:20] trunk/kde/kquickguide/C/kquickguide.xml [10:20] OK that message shows you what ws changed [10:21] this list is useful because it lets you know when things change in the repos [10:21] when someting changes in the repos you must update your working copy [10:21] so [10:21] are you in your home dir? [10:21] if not do cd ~ [10:21] then do cd ubuntu-doc [10:22] now issue the command svn up [10:23] yup sync'd [10:23] Ok now you know how to get updates from the repos [10:23] just svn up? [10:23] when i get an email? [10:23] yep [10:23] yep [10:23] easy [10:23] ok i think i can manage that [10:23] right next [10:24] yes? [10:24] areyou using gnome or kde? [10:24] gnome [10:24] OK I want you to now edit a file [10:24] to do this [10:24] yes? [10:25] cd kde/kquickguide/C [10:25] ls [10:25] kquickguide.xml [10:26] you see the file I updated [10:26] do gedit kquickguide.xml [10:26] This will open the file in gedit [10:27] at the top of the file you will see this [10:27] yup i know that [10:27] [10:27] yes i see the bits you mean? [10:27] mean [10:28] I want you to delete the at the end [10:28] then save [10:28] done [10:28] svn commit by chance? [10:28] Ok close gedit [10:29] no [10:29] ok [10:29] you dont have a commit account yet ;-) [10:29] when you do then yes [10:29] svn diff kquickguide.xml > kquickguide.xml.diff [10:29] then ls [10:29] ls [10:29] kquickguide.xml kquickguide.xml.diff [10:30] yup its created a diff(erences?) file? [10:30] exactly send me that to sean@inwords.co.za [10:30] in future however you will send it to the docteam user list [10:31] did you send it [10:31] Yes [10:31] Just this second [10:32] OK now when Iget it I will apply it [10:32] and you will svn up again [10:32] are all the doc's in .xml? [10:32] yes [10:32] docbook [10:32] Coz i don't know xml [10:32] :( [10:33] that's also OK [10:33] you will learn [10:33] follow the markup around you [10:33] I will track your patches and make fixes to the sematic [10:33] That's the thing i don't understand much of the markup languages [10:33] over time you will get to know it [10:34] OK so you can do reading at http;//www.docbook.org [10:34] and we will help you [10:34] really it is not that hard [10:34] ;-) [10:35] you just edited a file and sent it to me [10:35] now if I had applied the patch, you would get an email from the commit list [10:35] Yes i understand the transfer of files etc, it's xml i don't understand, i will have a look at this site though [10:35] and you just cd to ubuntu-doc/ and do svn up [10:36] dont worry about the xml [10:36] you just worry about writing and do your best with the xml [10:36] we will fix it [10:36] well... [10:36] its a good idea to learn as you go [10:36] Im sorry i miss the writing principle here, let me look at that edited file [10:37] sure, take a look at the markup, it will make sense [10:37] Njal, but its easy, you'll pick it up by playing with the files, and checking them after you edit with the validate script and visually, as described in the wiki document [10:37] most of the tags are natural [10:37] Ok so we have content, i presume that it's meant to be viewed in a webbrowser? [10:37] Njal: mdke is right [10:37] no [10:38] ok [10:38] Njal: XML is presentation neutral [10:38] however, I think you will find that Yelp is a good help for you at this point [10:38] it can be made into many things, html, pdf, or stay as it is to be viewed by certain clients [10:38] so I would like you to do yelp kquickguide.xml [10:38] So [10:39] Xml is umm.. clay [10:39] that can be moulded into whatever [10:39] :) [10:39] ;-) one way to see it [10:40] Njal: did you yelp the file? [10:40] Yeah i really need to grasp what happening before i try anything, so we write an xml file that gets turned into a usefull file [10:40] no [10:40] working on it [10:40] Ok tak eyour time [10:40] you cant break anything [10:40] so dont be afraid of it [10:41] and i you edit a file and think you have really botched it [10:41] So yelp presents the xml file in a human readable way? [10:41] what can you do [10:41] yes [10:42] if you both a file then just use the revert command 'svn revert file.xml' [10:42] Right, i think the next few days are going te be hello world xml things [10:42] ah, i didn't even know that about reverting..thanks froud [10:42] that will return your working copy file back to the copy in svn [10:42] squinn: np [10:43] froud, now that i'm back from yard work, here's my question [10:43] Njal: but you will lose any change you made in that file [10:43] what can one do to find patchable things? [10:43] i mean, sure, i was already working on the about ubuntu guide [10:43] Hmm, Idont understand? [10:43] yeah but if it's botched... [10:43] Njal, it goes back to the one from the web [10:43] Njal: yes exactly === _jeff is now known as jeffsch [10:44] froud, how can I find things to patch?* [10:44] squinn: yu mean what can you work on? [10:44] squinn, everything needs work [10:44] yeah. [10:44] well we have breezy targets [10:44] i mean, that kubuntu thing came upon me while i read and was working on the About Ubuntu guide. [10:44] keep reading and you'll find more [10:44] froud, true, but those can't be svn commited until breezy's almost ready for release [10:44] user guide user guide user guide user guide :) [10:45] yeah, i noticed some OLD screenshots of user-guide [10:45] warty screenshots [10:45] ;-) jeffsch [10:45] yuck, i must update [10:45] jeffsch, + [10:45] howdy folks [10:45] Ok another analergy time [10:45] squinn: we are working towards breezy [10:45] squinn, screenshots its probably better to leave until later, so we can get breezy shots [10:45] squinn: [10:45] one problem [10:45] Im learning C, and you need the #include deal [10:46] i've got another question, i'll ask in a minute [10:46] is this the xml equal [10:46] squinn: you are most likely working with hoary [10:46] Njal: no [10:46] Njal: see the doc type decl [10:46] right [10:46] "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [ [10:47] squinn: you have hoary on your computer [10:47] froud, that is correct. i'm using hoary. [10:47] squinn: the problem with that is that you can only see what is in hoary [10:47] so, what to do [10:48] well if you have another computer you can install hoary and then just change the sources.list to breezy repos [10:48] and then you us ethat machine to document [10:48] Ok well i am going to go for tonight, i've got a fair bit to digest here [10:48] but [10:48] Njal: np c ya [10:48] bye, and thanks [10:48] froud, only one usable computer atm [10:48] squinn: you can also download the prerelease ISO files [10:49] then you use something like qemu [10:49] ah, good idea [10:49] with qemu [10:49] do i just... [10:49] to emulate linux under linux [10:49] qemu "livecdorwhateversmartguysatcanonicaldecidetocalltheiso.iso"? [10:49] Hmm cant remember the commands but see the qemu docs [10:49] okay, thanks [10:50] man qemu after install? [10:50] if you get stuck I will type up a tutorial [10:50] okay, thanks [10:50] with the emulator.. [10:50] i can't save or download anything though, right? [10:50] squinn: the problem with that is that you must wait for prereleases [10:50] but at least you can do your work [10:50] what if [10:51] i created some partitions for breezyt [10:51] for the most part I think you will find that your hoary system is good enough to doucment against [10:51] squinn: that is up to you [10:51] yeah, that user guide for hoary still needs work [10:51] yes [10:51] so you just write abook [10:51] have fun [10:52] use hoary if you must and as we get closer to breezy we will check it and realign it if needed [10:52] well, breezy's what, not until 5.10 [10:52] yes [10:52] it's 5.06 still right now right? [10:53] using ubuntu's system of numbers [10:53] that is why I say that you can use hoary [10:53] right [10:53] many things will be the same [10:53] but later to release it will be a good idea to use the breezy development version [10:53] so you can see any changes [10:53] yes [10:53] mdke: yes [10:53] at about 5.08, i think i'll upgrade [10:54] and right now, all cvs can take is hoary right [10:54] er, svn* [10:55] ? [10:56] what do you mean by "can take"? [10:56] um [10:56] all that can be handled by svn is hoary documents [10:56] meaning a document written for breezy could not be in svn right now, correct? [10:59] not correct. anything we work on now is for breezy release [11:00] okay [11:00] i think i'm starting to understand [11:00] but i could still write up say..the user guide..based on hoary..and will update for warty [11:00] going back in time [11:00] breezy* [11:01] yes. when we know better what breezy looks like, then we can make any updates/changes [11:02] it's better to have something to fix, rather than nothing at all [11:02] right. [11:02] okay, well i'm looking at the quickguide now, i see some errors already [11:02] this is quickguide that comes with hoary [11:02] not in svn [11:03] you have to work in svn [11:03] things may have already been changed [11:03] i know, i'm doublechecking [11:03] squinn, best thing is to ignore the old version [11:05] i am lol [11:05] svn much better version [11:05] yet something i don't like [11:05] [possible flood warning] [11:05] The top panel contains the [11:05] Applications Menu [11:05] , [11:05] System Menu [11:05] , and [11:05] Places Menu [11:05] and those three titles are huge and brown [11:05] squinn, you are free to edit [11:05] and it just looks very..off and unprofessional [11:05] that's yelp's fault [11:05] squinn, best thing is to work on it [11:06] ah, ok, jeffsch [11:06] and alright mdke [11:06] if there's a workaround, jeffsch..i'd like to at least try to find one [11:08] squinn, that is the least of our worries!! there is much content to sort out [11:08] the workaround is to not use xrefs with the endterm attribute [11:08] for example: user guide [11:08] ok [11:11] hello jeffsch long time no speak [11:11] froud: howdy dude [11:11] what you been doing [11:12] nuthin. honest. i didn't do it. or at least, it's not my fault. [11:12] :-) [11:12] :) [11:13] I was looking at style guide. good stuff dude [11:13] still a lotta blanks need filling though [11:13] yep, but I am sure it will be no problem for ppl here [11:13] just needs some time [11:14] getting them to follow it once it's done... [11:14] Hmm, .... [11:14] maybe the doc leads, or primary contacts can be responsible for implementation [11:15] doc leads? [11:15] leaders on certain doc projects [11:16] from the meeting https://wiki.ubuntu.com/DocumentationTeamMeetingSummary5 [11:16] I dont think there are any yet. [11:16] I intend to lead on About Ubuntu in GNOME [11:16] mdke: " The install guide is not in the list of projects, this oversight should be corrected ASAP." [11:16] mdke: the install guide is on th elist [11:17] froud, yes, because it was corrected ASAP [11:17] doh! [11:17] Oh OK [11:17] mdke: are there doc leads? [11:18] not yet [11:18] some have expressed interest [11:18] it needs to be decided via the ML [11:18] yes saw that [11:18] listen I will be back later, am in a -it meeting right now [11:18] ML? [11:18] ok [11:18] ML = mailing list [11:18] ah [11:18] k [11:19] Ok I am off for the night, c ya around [11:19] later === froud [~sean@ndn-165-146-74.telkomadsl.co.za] has left #ubuntu-doc ["Konversation] [11:21] well i have to get some air... === jeffsch is now known as jeff-away [11:25] heh, i fixed the little style errors [11:25] took away the color, they are hyperlinks now..look a lot more professional [11:26] squinn, have you read the styleguide? [11:26] its important to have consistency throughout our documentation === JonA [~jonathan@alxpc1jaa2.alx.aber.ac.uk] has joined #ubuntu-doc [11:42] yes, mdke i have [11:42] cool [11:44] I'm going to submit what I just worked on as a patch. [11:45] how was your italian meeting? [11:45] still going [11:45] ah [11:45] I'm going to try and become a member. [11:46] Probably not now..in a little bit. [11:46] I think about a month. [11:47] So, mdke do you live in Italy or just speak the language? [11:47] just the language [11:48] Ah. [11:48] That's awesome. [11:48] I know a little here and there. [11:48] I actually, just gotta send out this patch and head downstairs and help the mom make meatballs. [11:49] enjoy :) === ealden [~ealden@219.90.91.86] has joined #ubuntu-doc