[02:07] <jjfrv8> flocculant, I guess you'll see the panel testcase bug and merge proposal for revision.
[02:08] <jjfrv8> ochosi, xfpm 1.4.4 docs update ready for your review when you have a chance.
[07:45] <flocculant> jjfrv8: thanks :) I'll sort it out later today
[08:11] <flocculant> knome: is there are way to rename a wiki page? or just copy 
[08:11] <flocculant> https://wiki.ubuntu.com/WilyWerewolf/FinalRelease/Xubuntu to /ReleaseNotes/Xubuntu
[08:16] <zequence> flocculant: It's in the menu, under "More Actions"
[08:17] <zequence> You won't see it while editing.
[08:18] <flocculant> zequence: I see that now
[08:19] <flocculant> however it tells me the page already exists - but it doesn't :(
[08:20] <zequence> Renaming usually works. Not sure why you are having problems
[08:22]  * flocculant neither
[08:22] <flocculant> thanks for telling me though
[08:23] <flocculant> did it the other way for the moment 
[08:42] <zequence> I was thinking maybe it had something to do with there not existing a page called /ReleaseNotes, but haven't tried that before. You were able to create a new page though?
[12:12] <knome> flocculant, as zequence said, renaming doesn't work when the target page has existed before; just copy-paste the page contents in the edit window over
[12:39] <flocculant> knome: ack - didn't know the why - dealt with it that way
[13:36] <jjfrv8> ochosi, re xfpm, thanks to the link on the Developer Area page of the website, I see that 1.5.2 is already upstream.
[13:38] <jjfrv8> ochosi, and of course it looks different. How do you want to handle that? Skip 1.4.4 altogether?
[15:39] <ochosi> jjfrv8: it does look a bit different, but it shouldn't be all-too different. since docs are versioned, we can leave 1.4 and 1.5 alongside each other in docs.xfce.org
[15:39] <ochosi> jjfrv8: also, 1.5 is a development release (stable releases are evenly numbered), so i guess we won't have it in 16.04
[15:39] <ochosi> (unless there's a 1.6 release in time)
[15:42] <jjfrv8> ochosi, ok, thanks. So if it looks like a new one will make it into 16.04, we can address it then. Not much would have to change with the text, just the screenshots.
[16:18] <flocculant> jjfrv8: thanks - all merged now
[19:12] <flocculant> pleia2: I got a mail in the newsletter queue re the IRC test session
[19:13] <pleia2> flocculant: cool, approved
[19:15] <flocculant> thanks :)
[19:16] <flocculant> don't really want to run it for 3 people :D
[19:22] <pleia2> I'd show up for support, but airplanes, as usual
[19:22] <flocculant> :)
[19:24] <knome> i can join and ask stupid questions
[19:24] <knome> :Ð
[19:24] <flocculant> :D
[19:25] <pleia2> I retweeted with comment too just now
[19:25] <flocculant> thanks pleia2 :)
[19:25] <pleia2> twitter web ui has gone all sideways
[19:25] <drc> flocculant: How many "confirmed and active" testers do you have now.  My guess would be that 3 more folks willing to at least show up would be a 33%-50% improvement,
[19:25] <flocculant> wouldn't know 
[19:26] <flocculant> drc: that would be a pretty accurate guess 
[19:26] <knome> pleia2, retweeted your retweet with a comment
[19:26] <knome> but didn't comment on it...
[19:26] <pleia2> how meta
[19:26] <knome> (i'm sorry failing to be that silly)
[19:29] <flocculant> drc: the thing in this case being have 2 people hang about for maybe 3 people to show up - we could just as easily answer 3 mails to the list 
[19:29] <flocculant> hence getting it on UWN etc 
[19:37] <drc> OK...I was just wondering why, after cycles of QAL's complaining about not having enough testers, one would say "Sorry, we don't have enough people present for us to train".
[19:37] <drc> And with that I'll leave.
[19:39] <knome> hit and run, the usual strategy here.
[23:11] <krytarik> flocculant, knome, slickymaster: Please check and tell me if you're fine with the some additional changes I did to the contributor docs, particularly the QA Team page - alongside and incl. fixing DocBook syntax, reducing duplication of "Xubuntu", increasing consistency, and fixing typos: http://paste.openstack.org/show/cblQfn6zn9PQbmIIoAJp/
[23:12] <krytarik> (Other than that, and updating the translation templates, my MP is ready to go.)
[23:14] <krytarik> - the
[23:14] <knome> krytarik, the / in the "Mainly built ..." is intentional
[23:14] <knome> the long version should read:
[23:14] <knome> Mainly built for Xubuntu or almost only used by Xubuntu
[23:15] <knome> if we spell Bazaar in the title, then i'd like a note that we will be referring to it with Bzr (or make the title "Bazaar (Bzr)"
[23:15] <krytarik> I'd expand it to: "Mainly built for and [mainly] used by Xubuntu".
[23:16] <krytarik> Yeah, some note would be nice.
[23:16] <knome> "top directory" ?
[23:16] <krytarik> Yes.
[23:16] <knome> not "branch root directory"
[23:16] <knome> or sth
[23:17] <krytarik> Well, didn't want to duplicate "branch" there - had though.
[23:17] <knome> if you want to use top, make sure "root" isn't used anywhere else - i'm pretty sure i'm using that at least in one place
[23:17] <krytarik> Alright.
[23:17] <knome> "Translation Guidelines ..." -> "Translation guidelines ..."
[23:17] <knome> but
[23:18] <knome> "Working with testcases" -> "Working with Testcases"
[23:18] <knome> wut? :P
[23:18] <krytarik> Well, those are different parts of the docs. :P
[23:18] <knome> :P
[23:18] <krytarik> Didn't want to make all the same there, that is. :D
[23:18] <knome> aha..
[23:19] <krytarik> Basically, for one chapter it should be the same.
[23:19] <knome> in XSD, if "Xubuntu Community" -> "Community", then i think we should go further and change it to "Community Organization" or sth
[23:20] <knome> organization is bad, but maybe that gives you an idea what i'm thinking about
[23:20] <slickymaster> krytarik, why the extra line between the titles and the paragraphs?
[23:20] <krytarik> knome: "Structure" maybe?
[23:21] <krytarik> slickymaster: It's common for the docs, it seems.
[23:21] <knome> something like that
[23:21] <knome> slickymaster, that's what we've been doing
[23:22] <slickymaster> haven't noticed that yet, tbh
[23:22] <knome> krytarik, maybe, though the section isn't really talking much about the structure
[23:22] <krytarik> knome: "do the following in the branch root" - I think that can stay as is.
[23:22] <slickymaster> one other thing krytarik "...the QA team should keep watch on testing reports on the trackers..." 
[23:23] <krytarik> knome: Yep, and I'm not convinced we should add anything there.
[23:23] <knome> slickymaster, always a blank line after </title>, </para>, </itemizedlist>, </note> etc. unless the next line is </section>, </chapter>, </appendix>
[23:23] <slickymaster> shouldn't be "...the QA team should keep a watch on testing reports on the trackers..."
[23:23] <knome> krytarik, no, definitely not add (but i should look at the wording on the users section, it's silly now
[23:23] <knome> it gives the impression that the xubuntu users only "organize" via the LP team
[23:24] <knome> which is far from the reality
[23:24] <krytarik> slickymaster: Yeah, wasn't particularly sure whether that's acceptable as is, or what else flocculant would prefer. :P
[23:24] <knome> it's probably the last thing our users use for organizing
[23:25] <slickymaster> add it before pushing your MP knome 
[23:25] <slickymaster> sorry krytarik 
[23:25] <knome> :P
[23:25] <slickymaster> damn autocompletion
[23:25] <knome> pebkac
[23:25] <krytarik> knome: Otoh, I only dropped "Xubuntu" there. :P
[23:26] <knome> krytarik, i know, but it felt better...
[23:26] <knome> :P
[23:26] <knome> or maybe the title was bad to begin with
[23:26] <krytarik> Hah, everything is always better with Xubuntu! :D
[23:26] <knome> except...nevermind
[23:27] <krytarik> slickymaster: Yeah, maybe just add an "a" there.
[23:28] <slickymaster> hmm why do you capitalized Testcases and went the other way around in guidelines, krytarik?
[23:28] <slickymaster> distraction?
[23:28] <knome> slickymaster, ffs, read the backlog?
[23:29] <knome> slickymaster, i literally JUST asked him about that
[23:29] <slickymaster> too tired
[23:29] <krytarik> knome: Oh, since you're referring to the branch root with what I just posted, and it's the intro to that list, we could as well not mention it again for the 'add' command.
[23:29]  * knome slaps slickymaster 
[23:29] <knome> krytarik, yeah, maybe :)
[23:29] <krytarik> Didn't notice it then, that is.
[23:30] <knome> i haven't been putting *too* much thought into any of it yet, tbh
[23:30] <knome> my intention has just been to increase the amount of content (well, with useful subjects)
[23:30]  * slickymaster is way to tired to reab the backlog and is simpler if krytarik just answers
[23:30] <slickymaster> * read
[23:31] <krytarik> slickymaster: In short, different chapters, different consistency. :P
[23:31] <krytarik> Didn't want to change unnecessarily much, that is.
[23:31] <knome> krytarik, ultimately, shouldn't all chapters have the same rules/consistency?
[23:32] <krytarik> Yeah, but ↑. :P
[23:32] <slickymaster> also krytarik, "...about required testing, Testers..."
[23:32] <knome> i know, but it has to be done at some point :P
[23:32] <krytarik> I mean, it also looks rather weird with some headers.
[23:32] <slickymaster> is that intentional? I mean the capitalized T in testers
[23:32] <krytarik> Particularly the longer ones.
[23:33] <knome> yeah...
[23:33] <krytarik> slickymaster: Yes, referring to a group there.
[23:34] <knome> mmeh.
[23:34] <knome> we have "Xubuntu Developers" group too, but we aren't talking about Developers
[23:35] <knome> (if we're going this nitpicky road)
[23:35] <krytarik> knome: "When you have worked on a branch and want to push your changes to a branch, do the following in the branch root:" - heh, there is no "branch" duplication *at all* there! :P
[23:35] <knome> NO!
[23:35] <krytarik> lol
[23:36] <knome> When you have worked on your changes and want push them to a remote branch, do the following on the local branch root:
[23:36] <bluesabre> hi
[23:36] <knome> hello bluesabre 
[23:36] <bluesabre> :D
[23:36] <bluesabre> whats up knome, krytarik ?
[23:36] <knome> north
[23:37] <krytarik> Yep, similar thought. :D
[23:37] <slickymaster> on my end I don't object to krytarik's wording
[23:37] <slickymaster> hey bluesabre 
[23:37] <bluesabre> ooh and slickymaster 
[23:38] <slickymaster> that is to mean that I'm fine with his chnages
[23:38] <krytarik> "Testers will get regular contact from us, but we should only, in general, call on Users at later stages." - particularly, it's also used to differentiate there.
[23:38] <knome> i would personally lowercase all mentions of Testers, Developers or whatever, even if they are referring to a group, as long as they make sense in lowercase
[23:38] <knome> eg. if we had a group called "Xubuntu Bulldozers", saying "bulldozers" would not make sense because it wouldn't be obvious if we were referring to the group or the machine :P
[23:39] <bluesabre> proper nouns
[23:39] <bluesabre> Xubuntu Testers != Xubuntu testers
[23:39] <knome> krytarik, in the case you mentioned, it might be better to open it up
[23:39] <knome> bluesabre, did you see my comment about Developers/developers before?
[23:39] <bluesabre> I see the one just above, yes
[23:40] <knome> :P
[23:47] <krytarik> slickymaster: Well, I've just gone with "should keep an eye on testing reports" - between the two. :P
[23:47] <krytarik> + now