[01:12] <nixternal> jjesse: can you give me that patch in txt format?
[01:12] <nixternal> it is in html format on lp
[01:13] <nixternal> actually, I can just edit manually
[01:41] <ryanakca> nixternal: well, since you don't know about Qt and C++, I'm sure you know about KDE documentation
[01:41] <nixternal> what is that?
[01:41] <ryanakca> does anybody with 'gobby' installed feel like "mentoring" me in rewriting my KMail + gpg-agent article?
[01:42] <nixternal> ryanakca: you want to know the easiest way to do what you want?
[01:42] <nixternal> download and use Desktop MoinMoin
[01:42] <ryanakca> Desktop MoinMoin? okies
[01:42] <nixternal> you can do it in wiki, and then export to docbook with the new version
[01:42] <ryanakca> And... what do I want?
[01:42] <ryanakca> ah
[01:42] <nixternal> ya, I have been messing with it here lately
[01:43] <nixternal> it is actually working fairly well
[01:45] <ryanakca> nixternal: hmmm. If I'm exporting it to docbook... where is it going? I was thinking it would go into Community Documentation on help.u.c...
[01:46] <nixternal> ahh, then no need to export it to docbook..I thought that is why you asked for mentoring
[01:46] <nixternal> gotcha
[01:46] <nixternal> you can always post it to the wiki and work from there..much easier than asking me to fireup gobby ;)
[01:47] <ryanakca> hmmm... but I'm more than willing to convert it to docbook, and you can stick it somewheres
[01:47] <nixternal> I am afraid of where you might want me to stick it ;p
[01:47] <ryanakca> I dunno
[01:48] <nixternal> ryanakca: I would love to put it into KDE documentation for one, and if it doesn't fit there well do to it being distro dependant, then I would love to have it in Kubuntu docs
[01:48] <ryanakca> It would have to be distro dependant...
[01:49] <nixternal> speaking of manpages, I actually have to create one in order to be considered for a debian developer
[01:49] <nixternal> that one through me for a loop
[01:49] <ryanakca> hehe
[01:49] <ryanakca> get a KDE app and run kdemangen.pl on it :P
[01:49] <nixternal> hehe
[01:50] <nixternal> isn't there a xml or docbook 2 man?
[01:50] <ryanakca> You created it... kindof...
[01:50] <nixternal> I have used help2man before
[01:52] <ryanakca> hmmm
[02:04] <jjesse> nixternal: did you get that patch correctly?
[02:04] <nixternal> I just did it by hand...it was spitting it out as html on lp..did you select the patch button?
[02:04] <jjesse> hmm don't remember what i did, i thought i just attached a file
[02:05] <nixternal> ya, if it is a patch you need to select the patch checkbox just under the folder icon when you attach
[02:05] <jjesse> ok, will do in the future
[02:12] <ryanakca> nixternal: Any idea what the gentoo documentation is released under?
[02:12] <jjesse> license wise?
[02:13] <nixternal> gfdl I thought
[02:13] <nixternal> cc-by-sa for us
[02:13] <ryanakca> but.. if someone is going to be installing gpg-agent with kmail, they know what gpg, -agent and kmail are.
[02:14] <nixternal> http://gentoo-wiki.com/Gentoo_Linux_Wiki:Copyrights
[02:14] <nixternal> Unless otherwise stated, the content of this wiki is in public domain.
[02:15] <ryanakca> ah, so, safe to include the What is gpg-agent blurb?
[02:34] <ryanakca> nixternal: how do you include boxes like those in http://gentoo-wiki.com/HOWTO_KMail_gpg-agent_kde#Setup for moinmoin? I know I could use tables, but anything more elegant?
[02:34] <nixternal> not in our version unfortunately
[02:34] <jjesse> nixternal: email message sent, please add in your .02
[02:35] <nixternal> will do
[03:12] <ryanakca> nixternal: done.
[03:12] <ryanakca> I just have do figure out how to place a paragraph in a table though... it seems to be ignoring [[BR] ] 
[03:14] <ryanakca> nixternal: https://help.ubuntu.com/community/KMailGPGAgent#preview
[04:32] <LaserJock> hmm, bzr again
[04:34] <LaserJock> nixternal: have you been doing any docs in bzr?
[04:34] <nixternal> no buntu docs no
[04:35] <nixternal> messing with jjesse docs, and kubuntu-system-settings, and a couple of websites..and the list goes on
[04:35] <LaserJock> I'm pretty hesitant still
[04:35] <LaserJock> I want to see LP with the smartserver stuff
[04:35] <LaserJock> and time that and see how fast it is
[04:36] <nixternal> it is a tad bit faster now..hell, I can commit faster with bzr than I can doc svn right now
[04:38] <LaserJock> yeah, but commit speed hasn't really ever been an issue I don't think
[04:38] <nixternal> nah, just the initial checkout is slow
[04:38] <crimsun> the initial commit, too.
[04:38] <nixternal> and remember you are pulling in the entire history as well
[04:38] <crimsun> and quadruply so on a 33.6kbps
[04:38] <crimsun> remember not all of us are on broadband.
[04:38] <nixternal> and we need to see if there was an issue with the export from svn to the import of bzr as well
[04:38] <nixternal> crimsun: then I suggest they get broadband ;)
[04:39] <crimsun> nixternal: tell that to the providers.
[04:39] <nixternal> there are only 8 contribs at most to docs anyways right now :)
[04:39] <nixternal> point me to them, I will gettum
[04:39] <crimsun> I'll suffer for a few more weeks. After I move, I'll just get fiber.
[04:40] <nixternal> oooh
[04:40] <nixternal> living in DC, there is fiber everywhere
[04:40] <LaserJock> jjesse usually uses dialup
[04:40] <crimsun> yes, and I won't be paying for it. :)
[04:40] <nixternal> LaserJock: but that is understandable with jjesse seeing most of his neighbors just purchased AOL accounts. I know where he lives...remember Deliverance? :)
[04:41] <nixternal> SQUEEL!!!
[04:44] <LaserJock> I think we can handle dialup users by providing weekly/monthly tarballs
[04:45] <nixternal> that isn't to bad of an idea..but only if we get them asking
[04:46] <crimsun> weekly could be managed. I'd rsync, much as I do now.
[04:47] <nixternal> also with bzr you can do the lightweight checkouts
[04:48] <LaserJock> yeah, but then ...
[04:48] <LaserJock> why not just keep using svn
[04:49] <LaserJock> the thing is, with our current workflow I really don't see any real advantage with bzr
[04:49] <nixternal> just trying to be like everyone else ;)
[04:49] <nixternal> lets switch to git
[04:49] <nixternal> ;p
[04:50] <LaserJock> well, switch RCS just 'cause is pretty stupid, IMO
[04:59] <LaserJock> I think we need to sort of rework workflow/repo structure if we want to use bzr
[05:00] <nixternal> oh most definitely
[05:00] <nixternal> I think having xubuntu-docs, kubuntu-docs, edubuntu-docs, and ubuntu-docs all within the Ubuntu Documentation Project would be good
[05:01] <nixternal> or could be good rather
[05:01] <LaserJock> yeah, but that means reworking things
[05:01] <nixternal> well, I can easily separate kubuntu docs from svn w/o any issues
[05:01] <nixternal> I would need trunk/libs and thats about it
[05:05] <LaserJock> the svn structure is specificly designed to minimize redundancy
[05:05] <LaserJock> and to enourage collaboration, team spirit
[05:06] <jjesse> sorry was afk playing madden and now heading to bed
[05:06] <jjesse> i'm on dsl now
[05:06] <jjesse> and thanks nixternal
[05:07] <jjesse> svn just seems more cumbersome to maintain
[05:07] <jjesse> anyways email the list as  i'm off to bed
[05:09] <LaserJock> it's only cumbersome because he keeps forgetting his svn password ;-)
[05:12] <nixternal> hahahahahahahaha
[05:12] <nixternal> you know what we should do if we keep svn
[05:12] <nixternal> svn+ssh
[05:12] <nixternal> that way there you can't lose your key
[05:12] <nixternal> debian is svn+ssh, kde is svn+ssh
[05:22] <LaserJock> yeah, seems like that would help
[11:52] <mdke> morning all
[06:35] <ubotu> New bug: #117382 in ubuntu-docs (main) "Usability of 'Manually Mounting and Unmounting File Systems'" [Undecided,Unconfirmed]  https://launchpad.net/bugs/117382
[06:40] <ubotu> New bug: #48852 in ubuntu-docs (main) "relogin isn't sufficient for xserver config changes [desktopguide - config-system] " [Low,Confirmed]  https://launchpad.net/bugs/48852
[06:41] <nixternal> hrmm
[08:59] <mdke> nixternal: outrageous... encouraging people to post howtos on their blogs
[09:05] <LaserJock> heh
[09:10] <nixternal> lol
[09:10] <nixternal> I knew you would say something about that :)
[09:12] <mdke> I've actually been planning a plea for bloggers to contribute their howtos to the wiki
[09:13] <mdke> there is a lot of good material out there which doesn't get near the wiki :(
[09:14] <LaserJock> I suppose
[09:14] <nixternal> I am getting ready to do a Howto on Howto post a Howto :)
[09:14] <nixternal> hahaha
[09:14] <LaserJock> I do find a lot of good stuff on blogs
[09:15] <mdke> especially the more technical stuff
[09:16] <LaserJock> yeah
[09:29] <mdke> so LaserJock, what about this bzr business
[09:29] <LaserJock> heh
[09:29] <LaserJock> if LP gets the bzr smartserver then the speed should be quite a bit improved
[09:29] <mdke> I don't think the "waiting on RT" issue is a big one
[09:29] <mdke> it's speed vs convenience of using LP
[09:30] <LaserJock> and if it doesn't have smartserver right now I think it's going to be real soon now
[09:30] <mdke> is the speed poor even if you use it without downloading the whole history?
[09:31] <LaserJock> it's still a bit slower than svn, but not nearly as much as a full branching
[09:31] <LaserJock> each release of bzr gets faster and faster
[09:31] <LaserJock> the biggest reason I can see
[09:31] <mdke> right
[09:31] <LaserJock> would be the ability to check out just kubuntu docs, or edubuntu docs, etc.
[09:31] <mdke> I'm not really sure about that
[09:32] <LaserJock> I see quite a few people that one to contribute to a specific area
[09:32] <mdke> there is common stuff for all of them
[09:32] <LaserJock> but they get overwhelmed with having the whole repo
[09:32] <LaserJock> I agree
[09:32] <LaserJock> that's why I'm hesitant about
[09:32] <LaserJock> *what
[09:32] <mdke> let's think this through
[09:32] <mdke> what would be the consequence of keeping all the packages separately?
[09:33] <LaserJock> well, I think it could depend on how we do it
[09:33] <mdke> theoretically, not much; I guess. A small amount of effort to keep the common stuff updated across them all. In practice, I suspect that it would be problematic in terms of each sub-group following what the others are doing
[09:34] <LaserJock> I *think* we could split it up into something like common, ubuntu, edubuntu, kubuntu, xubuntu, teamstuff
[09:34] <LaserJock> so if you want to work on kubuntu you could get a branch of common and kubuntu
[09:35] <mdke> hmm
[09:35] <mdke> I don't like that much
[09:35] <LaserJock> for technical reasons?
[09:35] <mdke> no :)
[09:35] <LaserJock> right
[09:36] <mdke> just a feeling
[09:36] <LaserJock> me too
[09:36] <mdke> I don't have a problem with nuking common and simply putting the relevant docs into each branch
[09:36] <mdke> I'm just concerned that the benefits of having us all working together would be lost
[09:37] <mdke> fragmentation etc
[09:37] <LaserJock> yeah, I can certainly understand that
[09:38] <LaserJock> although I'm not sure if I like the idea of having a technical constraint in order to keep the team together
[09:38] <mdke> but then again, do any other packages which appear in kubuntu, edubuntu and ubuntu share the same branch or source package?
[09:39] <LaserJock> not that I know of
[09:39] <mdke> maybe *ubuntu-desktop
[09:39] <nixternal> there we go...howto post a howto
[09:39] <LaserJock> those are done from separate source
[09:39] <LaserJock> the -desktops are separate source built from seed files that are in bzr in ~ubuntu-core-dev
[09:40] <nixternal> svn co https://docteam.ubuntu.com/repos/trunk/kubuntu
[09:40] <LaserJock> ideally that's the situation I'd like to see with the docs
[09:40] <nixternal> ya, so that doesn't work out well
[09:40] <mdke> LaserJock: can you explain how that works?
[09:40] <nixternal> only thing though, that won't pull in the trunk/libs or trunk/common
[09:41] <LaserJock> mdke: well, the seed files are stored in bzr in ~ubuntu-core-dev
[09:41] <nixternal> I think another reason was hit on my LaserJock last night, and that was the "forgetting of passwords"...which could be curbed by using svn+ssh
[09:41] <LaserJock> each derive and release is a separate branch
[09:42] <mdke> nixternal: or the writing down of passwords
[09:42] <LaserJock> so edubuntu-feisty, ubuntu-gutsy, etc.
[09:42] <nixternal> mdke: that makes to much sense thoug ;)
[09:42] <nixternal> s/thoug/though
[09:43] <mdke> nixternal: jjesse's problem is that he keeping forgetting his gnupg password, which is *quite odd*. I have no confidence that he will remember his ssh key password better :)
[09:43] <nixternal> and using svn+ssh would also prevent us from having to go to RT everytime to add a user...we would just add their key to a script file in svn
[09:43] <nixternal> but ssh doesn't use your gpg password
[09:43] <mdke> no, it uses your ssh password/phrase
[09:43] <nixternal> it uses a plain text password
[09:44] <nixternal> our svn uses some silly password..it don't use my ssh password either...I have the password in a txt file in ~/.ssh
[09:44] <mdke> no, you've missed the point
[09:44] <nixternal> I shouldn't say silly, but it uses plain text when it is just ssh
[09:44] <mdke> he can't remember his GNUPG key password in order to decrypt the email with his svn password
[09:44] <nixternal> are we talking bzr or ssh with the ssh password/phrase
[09:45] <nixternal> mdke: oh..hahahaGHAHAH@H#@
[09:45] <mdke> if he can't remember that, then why will he be able to remember his ssh password?
[09:45] <nixternal> holy smokes I did not catch that
[09:45] <mdke> :)
[09:45] <mdke> anyway, RT is quite quick with svn requests nowadays
[09:46] <mdke> still, if there are reasons to use bzr over svn, then we should consider it anyway
[09:46] <nixternal> only thing I don't like about using svn is if I lose my laptop, someone can commit quite easily...svn+ssh curbs that as well...a little more security really
[09:46] <LaserJock> yeah, I think it's minimally more convenient to do authentication via LP team
[09:46] <nixternal> well I think waiting for the module that LaserJock was referring to may be best
[09:46] <mdke> LaserJock: nod
[09:47] <LaserJock> I think the strongest point is that bzr would open up new workflows
[09:47] <nixternal> and we can give it a shot in a bit
[09:47] <LaserJock> not that it makes our current workflow better
[09:47] <mdke> potentially we could move to bzr and keep a single repo, and then consider split repos later
[09:47] <nixternal> well, people can create their own personal bzr branch if needed, and we would still be able to pull from it and merge it into svn quite easily
[09:47] <nixternal> and vice-versa
[09:48] <LaserJock> mdke: I think really we perhaps need a spec/wiki page
[09:48] <LaserJock> we need to get the bzr guys (like lifeless) to help us out
[09:49] <mdke> ok. are you volunteering?
[09:49] <nixternal> another thing I could possibly take a little flak over is licensing...it seems there may be some unhappy people coming down the tubes since Kubuntu docs are CC-by-SA and not GFDL anymore. I am guessing the KDE and Debian guys that have used some of our docs and vice-versa in the past
[09:49] <nixternal> Riddell pinged me earlier but has yet to respond
[09:50] <nixternal> I will keep you abreast of the situation though
[09:50] <mdke> debian has used our docs?
[09:50] <nixternal> ya..I didn't know that until I got emailed today by one
[09:50] <LaserJock> well
[09:50] <mdke> oh well; they are still free to do so :)
[09:50] <mdke> it's not like we've closed anything up
[09:50] <nixternal> cc-by-sa == non-free to Debian Policy though
[09:50] <LaserJock> the email said they think the docs should be done more in collaboration
[09:51] <mdke> nixternal: so is gfdl
[09:51] <nixternal> the list email did
[09:51] <LaserJock> for debian it has to be GPL
[09:51] <nixternal> yup
[09:51] <nixternal> or MIT/BSD and such
[09:51] <LaserJock> well, it has to be compatible with GPL
[09:51] <mdke> I haven't seen these emails
[09:52] <LaserJock> i.e. not GFDL or CC
[09:52] <LaserJock> mdke: nixternal when and made a mistake by emailing the debian documentation mailing list
[09:52] <nixternal> I am guessing with the new release of the GFDL that is due out about the same time as the GPL v3
[09:52] <nixternal> haha LaserJock
[09:52] <mdke> spontaneously?
[09:53] <mdke> or prompted by something else?
[09:53] <nixternal> I had helped with one of their documents prior...not spontaneously
[09:53] <nixternal> prompted by a KDE/Debian talk last night
[09:53] <mdke> so they have used some of our documentation, and can no longer do so?
[09:54] <nixternal> well from the talk in #kde-docs yesterday that would be a yes...on the Kubuntu side of things
[09:54] <nixternal> Debian doesn't have much KDE help it seems
[09:54] <mdke> what did they use?
[09:54] <nixternal> I couldn't tell you
[09:54] <nixternal> I haven't even seen a KDE based doc out of them truthfully
[09:55] <mdke> It seems really strange the idea that *our* upstream is complaining about our licensing
[09:55] <nixternal> I wonder how they use KDE documentation then seeing it is GFDL
[09:55] <mdke> anyone, bbl
[09:55] <mdke> anyway*
[09:55] <nixternal> hehe
[09:55] <nixternal> later
[09:55] <LaserJock> GFDL is ok as long as it doesn't have invariant sections
[09:55] <LaserJock> I think
[09:56] <nixternal> LaserJock: you are correct...I tend to forget about the invariance
[09:56] <LaserJock> which is not cool, in some instances
[09:57] <LaserJock> Debian had to basically strip out the TeX documentation
[09:57] <LaserJock> and RMS isn't so happy :-)
[09:57] <nixternal> RMS should know better though
[09:57] <LaserJock> yeah, but he made some really good sense
[09:58] <nixternal> I was told by Peter Brown that they are supposedly removing the "invariant sections" part(s)
[09:58] <LaserJock> like he set the license in the doc as a invariant section
[09:58] <LaserJock> *an
[09:58] <LaserJock> because you should be changing the license, right?
[09:59] <ryanakca> nixternal: fixed a few typos, etc in https://help.ubuntu.com/community/KMailGPGAgent ... how do I export to docbook with Moin Moin desktop?
[10:00] <nixternal> in the drop down menu there is the option
[10:00] <ryanakca> hmmm. Okies
[10:00] <nixternal> LaserJock: I should be changing it?
[10:04] <LaserJock> nixternal: changing what/
[10:04] <LaserJock> ?
[10:04] <nixternal> [ LaserJock]  because you should be changing the license, right?
[10:04] <nixternal> which license? and why me?
[10:04] <LaserJock> bah
[10:05] <LaserJock> let me rewrite my sentence
[10:05] <nixternal> lol
[10:05] <LaserJock> RMS set the licensing section of documentation as invariant
[10:05] <LaserJock> since people deriving from the work shouldn't be changing the text of the license
[10:05] <nixternal> ahh, got it
[10:06] <nixternal> yes you are correct
[10:06] <LaserJock> like if I working from a doc that was GFDL I shouldn't be able to reword the GFDL
[10:06] <LaserJock> so that really did make sense to me
[10:06] <nixternal> correct...at least what I could gather from the Debian lists from 2004 when that all started
[10:07] <nixternal> I also noticed that while watching the GPL v3 highlights where people could leave messages, I swore I seen the "invariant" section in there as well
[10:07] <nixternal> and someone commented on it
[10:07] <LaserJock> so according to the GFDL you can only make "secondary" material as invariant
[10:07] <LaserJock> which is another reason I don't mind it
[10:08] <nixternal> right
[10:08] <nixternal> there is a "Secondary" and "Invariant" section
[10:08] <LaserJock> so I really don't have a problem with GFDL
[10:08] <LaserJock> but I can sort of see where it'd be DFSG non-free
[10:08] <LaserJock> but I think it's an area where DFSG is a big pain in the butt and not realistic
[10:08] <nixternal> OK, so the invariant applies to the secondary
[10:09] <LaserJock> you can *only* mak invariant a secondary section
[10:09] <LaserJock> "Secondary Section" is a named appendix or a front-matter section of
[10:09] <LaserJock> the Document that deals exclusively with the relationship of the
[10:09] <LaserJock> publishers or authors of the Document to the Document's overall subject
[10:09] <LaserJock> (or to related matters) and contains nothing that could fall directly
[10:09] <LaserJock> within that overall subject.
[10:09] <LaserJock> oops didn't mean to paste that much
[10:10] <nixternal> hehe, I have it open reading it as well
[10:10] <LaserJock> so I really don't see why those invariant sections restricte anything meaningful
[10:10] <nixternal> ya, me either
[10:11] <nixternal> I need to re-read that debian list again to see their reasoning
[10:11] <LaserJock> but definition it doesn't effect the real contents of the doc
[10:11] <LaserJock> well, they don't care how significant it is, I think
[10:11] <LaserJock> if it restricts modification in anyway I think it's non-DFSG
[10:12] <nixternal> that legal mumbu jumbo is enough to drive someone to drink
[10:12] <nixternal> s/mumbu/mumbo
[10:13] <LaserJock> yeah
[10:13] <LaserJock> I really dislike licensing, especially doc licensing
[10:13] <nixternal> hehe, it should just say "You are free to do whatever"
[10:14] <LaserJock> but then ... do I want people to do "whatever"?
[10:14] <LaserJock> I go between wanting to MIT everything I do
[10:14] <LaserJock> to wanting to make everything proprietary evilness ;-)
[10:14] <nixternal> the MIT license from what I can understand isn't to shabby, nor is the BSD license
[10:15] <nixternal> the BSD license will allow you to make it proprietary evilness
[10:15] <nixternal> what exactly is a "front-matter section"
[10:16] <nixternal> never mind, that same sentence tries to explain it
[10:16] <LaserJock> like I was thinking the other day what it'd be like to find out code I'd written as used by hackers/terrorists/bad guys to do harm
[10:16] <ryanakca> nixternal: where would you like the docbook for the KMail thing? ubuntu-doc ML?
[10:17] <nixternal> you can put it there or fire it off to me
[10:17] <nixternal> make sure you dual license that bad boy though so I can use it with Kubuntu docs as well as KDE docs
[10:17] <nixternal> ;D
[10:18] <ryanakca> dual license...
[10:19] <ryanakca> send me the legal blurb/tell me how to do that, and sure
[10:20] <nixternal> in order for me to be able to use your work, you need to license it either GFDL for KDE or CC-by-SA for Kubuntu, or both :)
[10:20] <nixternal> you can explicitly state that in a signed email as well
[10:21] <nixternal> if you do, at least link me to the GFDL and the CC-by-SA 2.5 license
[10:21] <ryanakca> Kubuntu won't take GFDL?
[10:21] <nixternal> instead of attaching the huge things there
[10:21] <ryanakca> ox
[10:21] <ryanakca> ok
[10:21] <nixternal> nope, only CC-by-SA unless Riddell pushes for GFDL/GPL
[10:21] <LaserJock> ohhh for goodness sakes :/
[10:21] <nixternal> hehe
[10:22] <LaserJock> sorry, just reading planet :(
[10:22] <nixternal> lol
[10:22] <nixternal> which one?
[10:22] <nixternal> ryanakca: something tells me that his ping earlier was going to get into that
[10:23] <LaserJock> nixternal: \sh leaving Ubuntu ... again
[10:23] <nixternal> I just noticed he is back online
[10:23] <nixternal> LaserJock: hahahaha
[10:23] <nixternal> you are just now reading about it?
[10:23] <nixternal> you didn't see them arguing in motu earlier?
[10:24] <nixternal> I am upset with the fact they a) argued it out in a public channel, and b) it got posted tot he planet afterwards
[10:24] <nixternal> that is the stuff the FUD/anti-Ubuntu people love to see
[10:24] <nixternal> you know, and Dell enjoys seeing it as well
[10:25] <LaserJock> darn it
[10:45] <nixternal> holy smokes, I just read the 2006 vote for the GFDL and the DFSG...talk about mind boggling
[10:45] <nixternal> so now I totally understand the "secondary section"
[10:46] <nixternal> it is the a section created with the beliefs and/or opinions of the author...therefor the author makes that section invariant
[10:46] <ryanakca> nixternal: hmmm. Do I need to add the licenses as a comment in the docbook file?
[10:47] <nixternal> which is commendable, as you wouldn't want anyone editing and changing your beliefs/opinions and still calling them yours
[10:47] <nixternal> it makes sense, and I agree with option 3, it would be considered unethical to do so
[10:47] <nixternal> ryanakca: you probably should
[10:47] <nixternal> bbiaf..need to check up on the weather outside
[10:47] <ryanakca> comments... <!-- comment -->
[10:47] <ryanakca> ok
[10:54] <nixternal> sure
[10:58] <ryanakca> nixternal: hmmm. And, saving the file messes up the structure... *points to #docbook*
[11:01] <ryanakca> any idea?
[11:03] <ryanakca> weee! I fixed it with `tidy`
[11:05] <nixternal> <!-- Dual License under GFDL and CC-by-SA -->
[11:05] <nixternal> haha
[11:08] <ryanakca> ah, that's all I need?
[11:09] <nixternal> and link to the licenses I guess
[11:09] <nixternal> but ifyou got it, don't worry about it then
[11:09] <ryanakca> hmmm.
[11:09] <nixternal> you are good to go then
[11:09] <ryanakca> How do I "visualize"/read the docbook. I can see the xml stuff, but reading it?
[11:10] <ryanakca> rendering is probably a better term
[11:10] <nixternal> meinproc *.xml
[11:19] <ryanakca> nixternal: Error: CALS tables must specify the number of columns.
[11:19] <nixternal> hrmm
[11:20] <nixternal> send me the xml file, let me take a quick look at it
[11:20] <ryanakca> ok
[11:22] <nixternal> brb..I need to eat some food
[11:22] <ryanakca> sent
[11:22] <ryanakca> ok
[11:37] <ryanakca> when you come back, I've cleaned up a bit of it, and fixed that error. It still doesn't properly generate the .html... it creates two files, one with intro and TOC, and another with conclusion.
[11:37] <ryanakca> http://blog.ryanak.ca/KMailGPGAgent.xml
[11:51] <nixternal> oh wow, the moin2docbook doesn't make a pretty output does it
[11:51] <nixternal> it actually creates invalid xml
[11:56] <ryanakca> hmmm
[11:57] <ryanakca> that's what it looks like after running tidy -m -i -xml KMailGPGAgent.xml on it, btw
[11:57] <ryanakca> feel free to mess around with the formatting...
[11:58] <nixternal> hrmm, from into to conclusion
[12:00] <nixternal> did you already post to the wiki this document?
[12:00] <nixternal> ya, that made sense
[12:00] <ryanakca> I have an old copy on the ubuntu wiki, just a sec
[12:00] <nixternal> where is your new copy wikified?
[12:00] <nixternal> wtf is up with me
[12:01] <nixternal> where is your new WIKIFIED copy
[12:01] <mdke> nixternal: what moin2docbook are you using?
[12:01] <nixternal> the latest in MoinMoin Personal Desktop
[12:01] <ryanakca> nixternal: https://help.ubuntu.com/community/KMailGPGAgent
[12:02] <mdke> nixternal: ah, that is rubbish
[12:02] <ryanakca> nixternal: I had fixed it up on my desktop wiki, just had to update the help.ubuntu.com
[12:02] <nixternal> cool ryanakca
[12:02] <nixternal> is there another version mdke?
[12:03] <mdke> nixternal: there is a test wiki with the latest code, but it appears to be broken
[12:03] <nixternal> hrmm...maybe I can find the latest code and create a new plugin with it
[12:03] <mdke> that would be very helpful
[12:04] <mdke> http://moinmoin.wikiwikiweb.de/DocBook
[12:04] <mdke> Burgwork: damn; we have communication issues
[12:09] <nixternal> g'nite