[00:52] <flocculant> probably why things like pareole break for me - I have no cares :p
[00:53] <drc> No, it's becasue apps don't like you..hence perfect QAL.
[00:53] <flocculant> \o/
[00:54] <flocculant> I knew I would WIN
[00:54] <drc> 8 or 10?
[00:54] <knome> 9.
[00:54] <flocculant> 7
[00:54] <flocculant> always 7 
[00:54] <drc> as long as it's not 98ME
[00:55] <flocculant> ha ha 
[00:55] <knome> 6 was my favorite number before but now i don't care
[00:57] <flocculant> always 7 
[00:59] <knome> bluesabre, you should really join #ubuntu-quality 
[00:59] <knome> bluesabre, otherwise me and flocculant start telling you silly things we don't understand, and with our little "manipulation", nor won't you
[01:00] <flocculant> \o/
[01:01] <flocculant> you CAN apparently make ubuntu-bug work with PPAs
[01:01] <flocculant> knome: like that? 
[01:01] <knome> heh, well, maybe...
[01:02] <flocculant> :)
[01:22] <bluesabre> suppose I'll join then
[01:22] <bluesabre> I wonder if I might regret this
[01:22] <bluesabre> :D
[01:25] <flocculant> bluesabre: I promise not to too often link youir quote :D
[01:27] <bluesabre> which one?
[01:28] <bluesabre> the "give us all your bug reports" one
[01:28] <bluesabre> ?
[01:28] <bluesabre> :D
[01:29] <flocculant> nope
[01:30] <flocculant> the "we want all your usabilty issues as bugs one
[01:30] <flocculant> which I make up from 2 ro 3 different quotes
[01:30]  * flocculant should run for office .... 
[01:31] <knome> yes
[01:31] <knome> the bad typing dept.
[01:31] <bluesabre> :)
[01:31] <flocculant> would I win?
[01:32] <flocculant> silly flocculant 
[01:32] <flocculant> ofc you would :P
[01:32] <drc> It's unanimous
[01:32] <bluesabre> +1
[01:33] <flocculant> woot I win then 
 I knew I would WIN
[01:33] <drc> egotist
[01:34] <drc> and with that, I concede and "goodbye"
[01:34] <flocculant> I would like to take this opportunityy to win things for drc - we are all equal, or old or stuff
[01:34] <flocculant> o 
[01:35]  * bluesabre forgets that his youth escapes a bit more each day
[01:35] <flocculant> he missed winning :(
[01:35] <flocculant> bluesabre shouldn't do that 
[01:36] <Unit193> bluesabre: Soon you'll be a cranky old man like the rest of us.
[01:36] <knome> or, with some exact surgery, cranky old lady
[01:36] <bluesabre> :D
[01:37] <flocculant> ha ha
[09:04] <akxwi_dave> flocculant, I retried the window snapping last night on real hardware (fresh install) and its working as is.. On my old vm it isnt, however, i have just built a fresh Xneial VM from the 1st iso release and snapping is working fine.  So I'll assume that there is something wrong with my original VM.
[09:05] <akxwi_dave> oh and Morning by the way..  :-)
[09:11] <Unit193> Howdy.
[10:52] <bluesabre> morning all
[11:06] <akxwi_dave> Morning
[11:46] <drc> OK, Before I dive back into flocculant's "Xfce4 Power Manager Settings" Testcase, I'd like to clear up a little confusion I'm having re: Power Manager plugins.
[11:47] <drc> It appears that there is a Power Manager plugin that is installed in the panel by default and is independent of either the Notification Area or Indicator Plugin.
[11:49] <drc> It also appears that there is a Notification Area Power Manager Indicator/plugin that is activated via the XFCE Power Manager Settings/General Tab (System tray icon)
[11:50] <drc> Both these do the same thing, abeit is slightly different fashions.  Am I correct so far?
[11:53] <drc> And that the Power Manager plugin is now monochromatic while the "System Tray icon (maybe not the best working, not sure we have a system tray now) is colorized.
[11:54] <drc> SO my question is:  Is this by design, we really want both of these?
[11:55] <drc> After thinking for a bit, I wonder if this results from folks wanting the old "Indicator Plugin" battery indicator?
[11:59] <Unit193> Right, so one is an xfce4-panel plugin, one is a tray icon, for say tint2.  The panel plugin should have more features, or generally be slightly better than the plain tray icon.
[12:00] <drc> Unit193: From what I see, they do the same thing, except one uses a right click and one uses a left click.
[12:38] <drc> Hey flocculant, quick question on "Xfce4 Power Manager Settings" Testcase.  Why was Display-> Brightness reduction not tested?
[12:40] <drc> Other than some (still) wording on the testcase itself, everything work as advertised.
[12:41] <drc> Submitted a "Pass". But what do you want in the Hardware profile?  I <can> use a inxi -F :)
[12:58] <slickymasterWork> or you can go to https://wiki.ubuntu.com/QATeam/Hardware drc
[12:59] <slickymasterWork> and then just add the gist github link
[13:01] <drc> reading now
[13:04] <Unit193> ...That is a horrible page.
[13:04] <slickymasterWork> that's what I use whenever I need to add my hardware profile either on the tracker or LP
[13:04] <slickymasterWork> yes, it is
[13:06] <akxwi_dave> thats one o fthe reasons i typr mine in the comments.. :-)
[13:10] <drc> OK, pretty straight forward until it comes time to "edit the top table only"  How would one go about doing this? I see nothing that would let me edit it.
[13:14]  * drc wonders if he'd get away with just saying "Apple ][" ? 
[13:16] <akxwi_dave> dare you... :-)
[13:17] <drc> To misquote Red Skelton "He don't know me very well, do he?"
[13:29] <flocculant> good day everyone 
[13:30] <flocculant> installs are still fubar with the mtab thing I see :)
[13:30] <flocculant> off shortly and will be back Sunday :)
[13:35] <akxwi_dave> going anywhere nice?
[13:44] <flocculant> god-daughter and her family - Brighton 
[13:52] <flocculant> have a good weekend 
[14:07] <akxwi_dave> enjoy flocculant, have a good time..
[14:30] <slickymasterWork> drc, you're not obliged to add yourself to that table
[14:31] <drc> I know, I was just wondering if I was missing something obvious.
[14:31] <slickymasterWork> all you need is the gist github link itself, since it's where your hardware specs are listed
[14:32] <slickymasterWork> did you login successfully in the wiki? 
[14:32] <drc> My guess is no.
[14:33] <slickymasterWork> so that's probably why you weren't able to edit it :P
[14:33] <slickymasterWork> tbh the wiki is a pain, anyhow 
[14:33] <drc> Like I said, something obvious :)
[14:34] <slickymasterWork> :)
[14:34] <drc> All I really care about is "what do they want me to put in the "hardware profile" of the test cases"  If Dell 1420n is enough, I'm good.
[14:36]  * slickymasterWork doesn't have a clear answer to that
[14:36] <slickymasterWork> ballons would be the one
[14:36] <slickymasterWork> * balloons
[14:37] <drc> I may just go with that Apple ][ ... see how long it takes someone to ask "Really?"
[14:38] <slickymasterWork> lol
[14:39] <drc> Silly Ubuntu One/wiki/whatever logins...running in circles
[14:39] <drc> That's why I gave it up years ago :(
[14:40] <drc> It seems like it's more about the infrastructure itself than what you do with it
[14:40] <slickymasterWork> yeah it's really annoying 
[14:41] <drc> BAH!  Apple ][ it is :)
[14:47] <akxwi_dave> ;-)
[14:48] <drc> hey akxwi_dave ... and congrats on becoming a "made man" :)
[14:50] <akxwi_dave> drc, cheers mate
[16:49] <knome> slickymasterWork, at least you around?
[16:49] <slickymasterWork> yes, I am
[16:49] <slickymasterWork> why
[16:49] <slickymasterWork> ?
[16:49] <knome> hah
[16:49] <knome> "whyyyyy"
[16:50] <knome> i was thinking setting up the contributor docs
[16:50] <knome> what's your take on this:
[16:50] <slickymasterWork> I saw you add it to the blueprint
[16:50] <knome> should we add it to the same repository or create a new one?
[16:50] <slickymasterWork> I'd go with a new one
[16:50] <knome> right
[16:51] <slickymasterWork> just a matter of organization, keeping things tidy 
[16:51] <knome> i'll register a new project in lp for that then as well
[16:51] <knome> xubuntu-contributor-docs ?
[16:51] <knome> (obviously we can always change that..)
[16:51] <slickymasterWork> yes, that's about what I'd call it
[16:51] <knome> ok
[16:51] <knome> i'll make some room on the kitchen table and start working on it next then
[16:51] <slickymasterWork> btw knome, the "HowTo build docs locally"
[16:52] <knome> the what? :)
[16:52] <slickymasterWork> can I draft it right on the website or do you want me to do it in a pad?
[16:52] <knome> sudo apt-get build-dep && make
[16:52] <knome> works in wily...
[16:52] <slickymasterWork> not that you silly you
[16:52] <knome> :D
[16:52] <knome> that's building docs... locally
[16:53] <slickymasterWork> the tutorial I'm writting on how to do it
[16:53] <slickymasterWork> it's an item in the blueprint
[16:53] <knome> i'm wondering if we need a tutorial
[16:53] <slickymasterWork> silly nilly
[16:53] <knome> :D
[16:53] <knome> am i missing something here?
[16:53] <knome> the tutorial is this:
[16:53] <knome> 1) sudo apt-get install bzr
[16:53] <slickymasterWork> well flocculant mentioned it, the need for it, and I do see that there's a need
[16:54] <knome> 2) bzr branch lp:xubuntu-docs
[16:54] <slickymasterWork> I know that knome 
[16:54] <knome> 3) sudo apt-get build-dep xubuntu-docs
[16:54] <slickymasterWork> lol
[16:54] <slickymasterWork> stop
[16:54] <knome> :D
[16:54] <knome> let's just add that to the contributor docs :P
[16:54] <slickymasterWork> chances are that we may have a lot of potential contributors that just don't know
[16:54] <knome> yes
[16:55] <slickymasterWork> either way works for me
[16:55] <knome> well i'm not opposed to a blog article either
[16:55] <knome> i guess just write it up in the blog
[16:55] <knome> unless you decide to go deeper in the docbook land
[16:55] <slickymasterWork> oki doke
[16:56] <slickymasterWork> one thing I remembered that afterwards will have to go on the contributor-docs is this https://smdavis.us/doku/doku.php?id=playground:sceenshot-stds
[16:56] <slickymasterWork> jjfrv8, ochosi and I kind of settle that'd be the standard 
[16:58] <knome> slickymasterWork, i guess that's debatable, but at least we can link to it :)
[16:58] <slickymasterWork> of course it is, bit it's one standard at least
[16:58] <knome> one con to the seprate repositories is that then it isn't as easy to share the same stylesheet
[16:58] <knome> or at least we need to update both repositories with that when doing updates
[16:59] <slickymasterWork> well, that focus mainly in the wiki-type of documentation
[16:59] <knome> still
[16:59] <knome> we want it to look the same as the end-user docs
[16:59] <knome> with some changes, sure
[16:59] <slickymasterWork> no argues there
[16:59] <knome> but mostly the same
[17:00] <slickymasterWork> but we have to take in consideration the weight of xfce in that particular solution/standard 
[17:00] <knome> hmm?
[17:01] <slickymasterWork> and sean adopt it to his appps
[17:01] <slickymasterWork> hey so many 'ppp'
[17:01] <knome> oh, you're talking about something else than me
[17:01] <slickymasterWork> what are you talking about, then?
[17:02] <knome> 18:58  knome: one con to the seprate repositories is that then it isn't as easy to share the same stylesheet
[17:02] <knome> so basically, we have an established stylesheet (and a somewhat matching PDF style layer)
[17:02] <knome> if we do a separate repository, it isn't as easy to use the exact same files for this
[17:03] <slickymasterWork> oh, yes
[17:03] <knome> or at least it means that if we make changes, we need to push them to two repositories
[17:03] <slickymasterWork> yes, I agree with that reasoning 
[17:03] <knome> also, if we want to mention the contributor docs from the docs startpage, the easiest way is that they exist in the same repository/package
[17:03] <knome> of course, it would have its own subdirectory
[17:04] <slickymasterWork> I wasn't at all go against it
[17:04] <knome> and all of it would be separated fromt he main docs
[17:04] <knome> so i guess i'll do that - at least for now
[17:04] <knome> it's relatively easily splittable too
[17:04] <slickymasterWork> I was just merely considering that we should somehow reference that standard in there some way
[17:05] <knome> yeah, that's a totally different discussion :P
[17:05] <slickymasterWork> yeaps
[17:05] <slickymasterWork> the goal is to also try to catch some contributors to the xfce documentation
[17:05] <knome> can be
[17:06] <slickymasterWork> on a different topic, I've been going through flocculant's -docs MP and I must say that other than a few minor wording changes it seems great
[17:07] <knome> :)
[17:07] <slickymasterWork> he has done a great, and thorough, work on it
[17:18] <knome> mhm
[17:29] <ochosi> my two cents are that we don't necessarily have to follow the style of the xfce docs
[17:29] <knome> ochosi, no, i'm about to follow the style of xubuntu docs
[17:29] <ochosi> the faenza icon theme is not an ideal choic there since its not maintained for yeras
[17:30] <ochosi> (just as an example)
[17:30] <knome> ssh, i need silence for working
[17:30] <knome> i'm just breaking all the docs and i want to do it well
[17:30] <slickymasterWork> hey ochosi 
[17:31]  * ochosi sneaksout
[17:31] <ochosi> hehe
[17:32] <slickymasterWork> I wasn't implying we should follow that style ochosi, just saying that we should somehow link some sort of reference to yet another side/aspect of -docs contribution
[17:33] <ochosi> hey slickymasterWork 
[17:33] <ochosi> sorry very slow internet on this train...
[17:33] <slickymasterWork> :)
[17:33] <ochosi> and yeah, to that i agree
[18:20] <knome> bbl
[20:44] <knome> ooookay, https://code.launchpad.net/~ubuntu-core-doc/xubuntu-docs/xenial
[20:58] <dkessel> bluesabre: i need some translator hints for catfish :p
[20:59] <dkessel> strings 25 and 27: in which context are "other" and "any" used?
[21:00] <dkessel> only those two string to do in german now :p
[21:13] <ochosi> dkessel: checking...
[21:14] <ochosi> dkessel: "other" is part of the file type filters
[21:15] <knome> ochosi, now you can start writing documentation for contributors :P
[21:15] <ochosi> as in: documents, folders, images, music, videos,..., other
[21:15] <ochosi> knome: doc for contributors in what sense?
[21:16] <knome> ochosi, like developer docs
[21:16] <ochosi> dkessel: so "any" is the same in terms of the date range
[21:16] <knome> ochosi, "how to contribute with artwork"
[21:16] <dkessel> File filters... where do i have to click? :?
[21:16] <ochosi> dkessel: those are in the sidebar
[21:17] <dkessel> ah. strange enough, those are both translated in my version here... although on launchpad they aren't
[21:17] <ochosi> dkessel: here's the context for "other" http://i.imgur.com/FGg6NhX.png
[21:17] <dkessel> thanks ochosi
[21:17] <ochosi> no worries
[21:17] <ochosi> grep is your friend ;)
[21:17] <ochosi> (in case you run into such a problem again)
[21:18] <ochosi> or you can also check the "Located in.." hint on the launchpad translation site :D
[21:19] <ochosi> knome: yeah, i  guess that'd be a nice effort, but why the "now"?
[21:20] <knome> ochosi, i just set up the infrastructure for that, we now have a new docbook book in the -docs branch
[21:20] <ochosi> oh ok
[21:20] <ochosi> cool
[21:20] <ochosi> well that would be a nice target for 16.04
[21:20] <knome> ochosi, ultimately, we can ship that with all releases and have it in docs.xubuntu.org
[21:20] <ochosi> then again, are you sure ppl will read docs like that?
[21:21] <knome> no, but then again, i'm not going to put a huge effort on them
[21:21] <knome> i mean, we should document our processes as we have done now
[21:21] <knome> and if we can extend that to some of the technical issues, that's good
[21:21] <knome> it's as much a guide to us as to new contributors
[21:22] <knome> at least that's how i imagine it...
[21:25] <ochosi> yeah, that makes sense
[22:04] <knome> slickymaster, see above
[22:05] <slickymaster> doing it already
[22:05] <slickymaster> :)
[22:07] <slickymaster> knome, "The Xubuntu status tracker is where the development progress for the current development cycle is tracked and is located at."
[22:08] <slickymaster> isn't there an extra 'is' between 'tracked and' 'located'
[22:08] <slickymaster> what about "The Xubuntu status tracker is where the development progress for the current development cycle is tracked and located at
[22:09] <knome> no, the link tag was faulty and the link didn't show up
[22:09] <knome> i pushed a new revision now
[22:10] <knome> happy that you are happy that we can actually work on this now ;P
[22:10] <slickymaster> lol
[22:10] <slickymaster> are you referring to rev. 465
[22:11] <knome> ^
[22:11] <slickymaster> yeah, lag
[22:11] <slickymaster> the sentence remains the same knome 
[22:12] <knome> well, you can fix it yourself...
[22:12] <slickymaster> lol
[22:13] <slickymaster> don't want to do it if you do not agree with it
[22:13] <knome> no, i just wanted to set some initial content up
[22:13] <slickymaster> branching it anyway
[22:13] <knome> this is by no means final, or well-thought
[22:13] <slickymaster> ok
[22:14] <slickymaster> it will also serves the purpose of seeing it in the browser
[22:14] <slickymaster> * serve
[22:21] <slickymaster> knome, the license file is a clone from the one in the -docs?
[22:22] <knome> slickymaster, yes
[22:23] <slickymaster> thanks, it saves the effort of reading it
[22:23] <knome> heh
[22:24] <slickymaster> another quetsion knome, are you thinking in having the common-infrastructure bzr centric?
[22:25] <knome> no, but for anything that is common for several subtopics
[22:26] <slickymaster> yes, agree