[02:07] flocculant, I guess you'll see the panel testcase bug and merge proposal for revision. [02:08] ochosi, xfpm 1.4.4 docs update ready for your review when you have a chance. [07:45] jjfrv8: thanks :) I'll sort it out later today [08:11] knome: is there are way to rename a wiki page? or just copy [08:11] https://wiki.ubuntu.com/WilyWerewolf/FinalRelease/Xubuntu to /ReleaseNotes/Xubuntu [08:16] flocculant: It's in the menu, under "More Actions" [08:17] You won't see it while editing. [08:18] zequence: I see that now [08:19] however it tells me the page already exists - but it doesn't :( [08:20] Renaming usually works. Not sure why you are having problems [08:22] * flocculant neither [08:22] thanks for telling me though [08:23] did it the other way for the moment [08:42] 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] 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] knome: ack - didn't know the why - dealt with it that way [13:36] 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] ochosi, and of course it looks different. How do you want to handle that? Skip 1.4.4 altogether? [15:39] 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] 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] (unless there's a 1.6 release in time) [15:42] 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] jjfrv8: thanks - all merged now [19:12] pleia2: I got a mail in the newsletter queue re the IRC test session [19:13] flocculant: cool, approved [19:15] thanks :) [19:16] don't really want to run it for 3 people :D [19:22] I'd show up for support, but airplanes, as usual [19:22] :) [19:24] i can join and ask stupid questions [19:24] :Ð [19:24] :D [19:25] I retweeted with comment too just now [19:25] thanks pleia2 :) [19:25] twitter web ui has gone all sideways [19:25] 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] wouldn't know [19:26] drc: that would be a pretty accurate guess [19:26] pleia2, retweeted your retweet with a comment [19:26] but didn't comment on it... [19:26] how meta [19:26] (i'm sorry failing to be that silly) [19:29] 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] hence getting it on UWN etc [19:37] 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] And with that I'll leave. [19:39] hit and run, the usual strategy here. [23:11] 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] (Other than that, and updating the translation templates, my MP is ready to go.) [23:14] - the [23:14] krytarik, the / in the "Mainly built ..." is intentional [23:14] the long version should read: [23:14] Mainly built for Xubuntu or almost only used by Xubuntu [23:15] 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] I'd expand it to: "Mainly built for and [mainly] used by Xubuntu". [23:16] Yeah, some note would be nice. [23:16] "top directory" ? [23:16] Yes. [23:16] not "branch root directory" [23:16] or sth [23:17] Well, didn't want to duplicate "branch" there - had though. [23:17] 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] Alright. [23:17] "Translation Guidelines ..." -> "Translation guidelines ..." [23:17] but [23:18] "Working with testcases" -> "Working with Testcases" [23:18] wut? :P [23:18] Well, those are different parts of the docs. :P [23:18] :P [23:18] Didn't want to make all the same there, that is. :D [23:18] aha.. [23:19] Basically, for one chapter it should be the same. [23:19] in XSD, if "Xubuntu Community" -> "Community", then i think we should go further and change it to "Community Organization" or sth [23:20] organization is bad, but maybe that gives you an idea what i'm thinking about [23:20] krytarik, why the extra line between the titles and the paragraphs? [23:20] knome: "Structure" maybe? [23:21] slickymaster: It's common for the docs, it seems. [23:21] something like that [23:21] slickymaster, that's what we've been doing [23:22] haven't noticed that yet, tbh [23:22] krytarik, maybe, though the section isn't really talking much about the structure [23:22] knome: "do the following in the branch root" - I think that can stay as is. [23:22] one other thing krytarik "...the QA team should keep watch on testing reports on the trackers..." [23:23] knome: Yep, and I'm not convinced we should add anything there. [23:23] slickymaster, always a blank line after , , , etc. unless the next line is , , [23:23] shouldn't be "...the QA team should keep a watch on testing reports on the trackers..." [23:23] krytarik, no, definitely not add (but i should look at the wording on the users section, it's silly now [23:23] it gives the impression that the xubuntu users only "organize" via the LP team [23:24] which is far from the reality [23:24] slickymaster: Yeah, wasn't particularly sure whether that's acceptable as is, or what else flocculant would prefer. :P [23:24] it's probably the last thing our users use for organizing [23:25] add it before pushing your MP knome [23:25] sorry krytarik [23:25] :P [23:25] damn autocompletion [23:25] pebkac [23:25] knome: Otoh, I only dropped "Xubuntu" there. :P [23:26] krytarik, i know, but it felt better... [23:26] :P [23:26] or maybe the title was bad to begin with [23:26] Hah, everything is always better with Xubuntu! :D [23:26] except...nevermind [23:27] slickymaster: Yeah, maybe just add an "a" there. [23:28] hmm why do you capitalized Testcases and went the other way around in guidelines, krytarik? [23:28] distraction? [23:28] slickymaster, ffs, read the backlog? [23:29] slickymaster, i literally JUST asked him about that [23:29] too tired [23:29] 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] krytarik, yeah, maybe :) [23:29] Didn't notice it then, that is. [23:30] i haven't been putting *too* much thought into any of it yet, tbh [23:30] 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] * read [23:31] slickymaster: In short, different chapters, different consistency. :P [23:31] Didn't want to change unnecessarily much, that is. [23:31] krytarik, ultimately, shouldn't all chapters have the same rules/consistency? [23:32] Yeah, but ↑. :P [23:32] also krytarik, "...about required testing, Testers..." [23:32] i know, but it has to be done at some point :P [23:32] I mean, it also looks rather weird with some headers. [23:32] is that intentional? I mean the capitalized T in testers [23:32] Particularly the longer ones. [23:33] yeah... [23:33] slickymaster: Yes, referring to a group there. [23:34] mmeh. [23:34] we have "Xubuntu Developers" group too, but we aren't talking about Developers [23:35] (if we're going this nitpicky road) [23:35] 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] NO! [23:35] lol [23:36] 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] hi [23:36] hello bluesabre [23:36] :D [23:36] whats up knome, krytarik ? [23:36] north [23:37] Yep, similar thought. :D [23:37] on my end I don't object to krytarik's wording [23:37] hey bluesabre [23:37] ooh and slickymaster [23:38] that is to mean that I'm fine with his chnages [23:38] "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] 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] 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] proper nouns [23:39] Xubuntu Testers != Xubuntu testers [23:39] krytarik, in the case you mentioned, it might be better to open it up [23:39] bluesabre, did you see my comment about Developers/developers before? [23:39] I see the one just above, yes [23:40] :P [23:47] slickymaster: Well, I've just gone with "should keep an eye on testing reports" - between the two. :P [23:47] + now