[00:01] <brainwash> bluesabre: any plans for lls and trusty? could a new version or single patches be backported?
[00:15] <bluesabre> brainwash: does trusty need a new LLS?
[00:17] <Unit193> bluesabre: See anything upstream that might have broken that?
[00:18] <bluesabre> Unit193: broken what? (on phone)
[00:18] <Unit193> bluesabre: Ah, not really important, but: xfpm and stuff fail to build, xdt-autogen tries to copy stuff into m4/ before creating the directory...
[00:19] <bluesabre> Oh right. Haven't had a chance to look yet.
[00:20] <bluesabre> Should be able to resolve easily though
[00:23] <Unit193> Yes, but what caused it and shouldn't that be fixed?  In the latest xfce4-screenshooter I just did a mkdir m4 :P
[00:23] <Unit193> Anywho, figured I'd share. :P
[02:46] <pleia2> bzr: ERROR: Connection error: while sending POST /bazaar/: [Errno 110] Connection timed out
[02:46] <pleia2> nice
[02:47] <pleia2> from a canonical server to the code on lp
[02:48] <Unit193> Hah, even better than normal.
[02:48] <pleia2> works ok at home o_o
[02:55] <pleia2> knome: it's a bit hokey becuase the server doesn't want to talk to bazaar.launchpad.net, but static and docs are updated
[09:44] <ochosi> morning everyone
[09:55] <ochosi> hey slickyma1ter 
[09:55] <ochosi> or slickymasterWork 
[09:55] <slickymasterWork> hey ochosi 
[09:56] <slickymasterWork> ochosi -> http://irclogs.ubuntu.com/2015/01/15/%23xubuntu-devel.html#t15:23
[09:56] <ochosi> oh good
[09:57] <ochosi> thanks for that, i overlooked it
[09:57] <slickymasterWork> np
[10:03] <elfy> morning 
[10:04] <elfy> ochosi: thanks for mailing laney - I scrubbed us off the wiki - no idea why amijawad thought he could add us :|
[10:04] <ochosi> ah thanks, hadn't noticed that :)
[10:11]  * Unit193 scratches head.
[10:16] <ochosi> Unit193: right, so i guess we're stuck with pushing new versions of xdg-utils to ubuntu then
[10:33] <ochosi> brainwash: i suggest you file a merge-request against xdg-utils in ubuntu to get your blanking patch in (or i can do it on top of my other MR for it if you don't wanna)
[10:58] <jarnos> Could someone fix that Ctrl-Esc would launch applications menu in 14.04?
[11:00] <jarnos> Currently it tries to launch xfce4-popup-menu that does not exist and I can not override the setting.
[11:01] <jarnos> Actually, I am using mythbuntu, but isn't it the same?
[11:16] <elfy> no it's not - if mythbuntu don't install something, try #ubuntu-mythtv
[11:24] <brainwash> bluesabre: trusty does not need a new lls, but it's always nice to push a bug fix release -> long term support. maybe it's not worth the effort though
[11:27] <brainwash> ochosi: but my patch is not that important (unless we want to backport it to 14.04/14.10)
[11:29] <brainwash> ochosi: you patch xdg-screensaver to make it compatible with ll, and the new ll already inhibits screen blanking
[11:29] <brainwash> in 15.04
[11:30] <bluesabre> brainwash: https://bazaar.launchpad.net/~light-locker-settings-team/light-locker-settings/trunk/view/head:/NEWS
[11:32] <bluesabre> not many bugfixes happening other than supporting libraries post trusty
[11:33] <brainwash> localizations not being used and some startup crash fix
[11:33] <brainwash> so yeah, probably not worth the effort
[11:34] <brainwash> bluesabre: any thoughts on the compton shadow workaround/fix?
[11:35] <brainwash> basically adding a new shadow rule to the xubu default settings compton config
[11:35] <bluesabre> shouldn't hurt to add it to trunk
[11:35] <brainwash> which disables shadows for windows with CSD
[11:36] <brainwash> because these windows draw their own shadows now
[11:36] <jarnos> I don't like that you reserve keyboard shortcuts Super+number. I have used to use these for setting certain video modes, some for multi display configuration.
[11:37] <jarnos> They are very handy, if you loose access to display for some reason.
[11:38] <brainwash> bluesabre: want to add it or should i create a branch? it basically just "shadow-exclude = [ "_GTK_FRAME_EXTENTS@:c" ]"
[11:38] <brainwash> bluesabre: https://github.com/chjj/compton/issues/189
[11:38] <brainwash> I've tested it and it works fine so far
[11:38] <bluesabre> create a branch and I'll merge for you
[11:38] <brainwash> ok
[11:39] <ochosi> brainwash: not sure i get what you're saying. either way, your patch is ready, the ll patch isn't is the point. and until we have ll support in xdg-screensaver, yours will work just fine
[11:39] <brainwash> jarnos: that's our default keyboard shortcuts configuration, you can easily reassign keybinds
[11:42] <brainwash> ochosi: I mean that with your planned changes to xdg-screensaver and the new ll in 15.04, my patch won't be crucial anymore to fix reported bug on launchpad
[11:42] <brainwash> the reported
[11:42] <ochosi> i know
[11:43] <ochosi> getting it merged in is the first step in getting it SRUd to trusty (if we decide to go through with that)
[11:45] <brainwash> sadly, it's not sru worthy
[11:49] <jarnos> brainwash, oh, for some reason I can not do that for Ctrl-Escape in Mythbuntu, where it is bind for nonexisting xfce4-popup-menu.
[11:50] <jarnos> brainwash, I mean the keybinding I set will be added to the list, but the original one is kept and used anyway..
[11:50] <brainwash> jarnos: try to clear the existing keybind more than once
[11:51] <brainwash> and the reassign your new one
[11:51] <brainwash> then
[11:52] <jarnos> brainwash, no matter how many times I remove it, it stays in the list.
[11:52] <jarnos> brainwash, maybe because it is default binding.
[11:54] <brainwash> jarnos: look at bug 1410760
[11:55] <brainwash> please read the comments
[11:59] <ochosi> brainwash: who told you it's not sru worthy?
[12:00] <ochosi> also, we can always throw the patched version in a PPA
[12:01] <ochosi> since it'll work with older versions of light-locker too
[12:02] <brainwash> ochosi: according to launchpad it's just a small bug and there is no major uproar which usually forces the devs to do something
[12:03] <brainwash> PPA sounds ok
[12:04] <brainwash> Unit193 will gladly do the packaging, right? :)
[12:06] <jarnos> brainwash, I don't see how it is relevant.
[12:07] <brainwash> jarnos: you have problems with a Ctrl keybind
[12:09] <brainwash> jarnos: I suggest that you look at your xfce4-keyboard-shortcuts-xml
[12:10] <brainwash> also, if this is a mythbuntu specific issue, then you should contact the mythbuntu devs and/or file a bug against mythbuntu
[12:11] <elfy> brainwash: the ctrl+esc is myth specific - it calls something that's not installled 
[12:11] <elfy> I checked ;)
[12:11] <brainwash> still, the user should be able to reassign the keybind without problems
[12:12] <jarnos> brainwash, I have three of them.
[12:12] <brainwash> jarnos: three of what?
[12:12] <elfy> but the default of reserving ctrl+f1 - f9 is in us too - seems rather overkill for workspaces especially when we don't do anymore than give people 1 workspace now
[12:13] <bluesabre> Settings Manager -> Keyboard, find what is using Ctrl+Esc, click Edit, change the application being called
[12:13] <jarnos> brainwash, xfce4-keyboard-shortcuts-xml
[12:13] <elfy> bluesabre: yea - that's not anything for us to worry about 
[12:13] <elfy> and it's f1- f12 reserved for workspaces 
[12:14] <bluesabre> I kmow, just trying to help reduce the amount of walking around the actual steps here :)
[12:14] <elfy> :)
[12:14] <bluesabre> other place is Settings Manager > Window Manager > Keyboard
[12:15] <knome> pleia2, ough. well, at least it's easier for me to tell you what i want changed :)
[12:15] <ochosi> bluesabre: is the bluetooth icon issue fixed for you?
[12:15] <bluesabre> ochosi: haven't tried yet
[12:16] <bluesabre> fix was in e-xfce or something else?
[12:17] <brainwash> jarnos: there should be only one in your .config directory
[12:18] <bluesabre> brainwash: why edit the xml instead of using settings manager?
[12:18] <ochosi> bluesabre: yeah, should work for both e-xfce and e-xfce-dark*
[12:18] <brainwash>  don't want to edit it, we want to check if the file is broken
[12:18] <bluesabre> ok
[12:19] <brainwash> broken = contains invalid entries :)
[12:19] <bluesabre> check permissions if it is stuck... sometimes people run things with sudo and give up ownership of their own files
[12:19] <ochosi> bluesabre: i'd say if it works, we could do an update of xubuntu-artwork with pulling in the icons from git and get that to the archive. i think the icons should be more or less gtk3.14-ready now
[12:19] <bluesabre> sudo menulibre = x.x
[12:19] <bluesabre> oh yeah
[12:20] <bluesabre> you marked numix and greybird done.... ready to package for release with git tags and all?
[12:20] <ochosi> knome: do you think you can get that dev-wallpaper ready soonish? i'd like to update xubuntu-artwork soonish with the icons, so that could go in too
[12:20] <ochosi> bluesabre: i need to mark greybird 1.5.1 actually since more fixes came along after 1.5
[12:20] <ochosi> but in git it's all done
[12:21] <ochosi> wanted to give it a few days to see whether more theming issues show up
[12:21] <ochosi> and to see what you think of the catfish-sidebar and popovers now
[12:21] <bluesabre> k, tag me some releases and let me know when to package ;)
[12:21] <bluesabre> also, new tag for ali1234
[12:21] <bluesabre> 's orion?
[12:21] <ochosi> well that depends, it isn't actually finished
[12:22] <bluesabre> k
[12:22] <ochosi> he said there were some padding issues
[12:22] <ochosi> so no MR yet
[12:22] <bluesabre> that can come in later then
[12:22] <ochosi> yup
[12:22] <ochosi> priority is greybird+numix for now
[12:23] <bluesabre> agreed
[12:24] <ochosi> one more thing that'll have to be fixed in the theme/s is the spinner
[12:24] <ochosi> not sure why that's not working
[12:24] <ochosi> larsu said he had it on his todo-list, so i'm waiting for him to figure it out
[12:24] <ochosi> (not even sure whether it's strictly a theme issue or some problem with gtk3 itself)
[12:24] <bluesabre> ubuntu-gtk issue?
[12:25] <ochosi> i'd rather wait than invest time in such an issue
[12:25] <bluesabre> i'd poke satya to test with fedora/ozon
[12:26] <bluesabre> also, does it work with adwaita?
[12:27] <ochosi> larsu claimed it does, but i couldn't confirm that tbh
[12:27] <ochosi> with adwaita there's just no spinner at al
[12:27] <ochosi> l
[12:27] <ochosi> you can test it easily with the printer-dialog or catfish
[12:28] <bluesabre> k, I'll have a look tonight
[12:28] <bluesabre> need to get ready for work now, bbl
[12:28] <ochosi> sure thing, ttyl
[12:28] <bluesabre> I'll be around tomorrow morning btw, don't know the rest of my schedule
[12:29] <ochosi> morning would be like now?
[12:30] <ochosi> or later cause it's a saturday?
[12:38] <knome> ochosi, i guess so :)
[12:43] <bluesabre> probably like now
[13:26] <jarnos> brainwash, it has only type="empty" lines for property name="&lt;Control&gt;Escape"
[13:45] <brainwash> jarnos: which ubuntu release? the notation has been changed (Control -> Primary) in 14.04
[13:46] <jarnos> brainwash, 14.04
[13:46] <brainwash> so, the linked launchpad report is relevant
[13:47] <brainwash> I assume that mythbuntu installs a custom keyboard shortcuts xml in /etc/xdg/..
[13:47] <brainwash> and it has not been updated yet
[13:59] <brainwash> jarnos: got any more question? if yes please query me instead of using this channel
[14:14] <slickymasterWork> ok knome, we can then put a stone on the docs conversion, at least for the moment
[14:24] <knome> ? :)
[14:28]  * slickymasterWork wonders to what does knome question refers 
[14:28]  * ochosi wonders what slickymasterWork's reference to "stones" refers to
[14:28] <ochosi> ;)
[14:28] <ochosi> aren't stones usually rolling?
[14:29] <knome> slickymasterWork, i was wondering what you were referring to? :P
[14:29] <slickymasterWork> your cahnges to the whiteboard of the docs blueprint´
[14:29] <slickymasterWork> * changes
[14:30] <knome> re: PDF export?
[14:30] <slickymasterWork> yes
[14:31] <slickymasterWork> ochosi, is a portuguese expression, when you put a stone on a subject you intend to mean that it's a dead subject
[14:32] <knome> yeah, i think it's not really worth it
[14:33]  * slickymasterWork won't question knome's assessment on the subject  
[14:34] <ochosi> yeah, i think we don't really need it
[14:37] <knome> if it was only a trivial change/task to get it right, then maybe
[14:37] <knome> but since it means dragging in relatively large build deps and then the output is less than sub-ideal...
[14:49] <elfy> we're a great community :) dholbach says so 
[14:50] <knome> :)
[14:50] <knome> good to hear that from somebody outside
[14:52] <elfy> https://daniel.holba.ch/blog/2015/01/building-a-great-community/
[14:53] <knome> ooh
[14:53] <slickymasterWork> you could also have mentioned the lack of translators elfy 
[14:54] <knome> we should tweet
[14:55] <knome> tweeted; pleia2, if you want to social mediaze it more: https://twitter.com/Xubuntu/status/556102390202761217
[14:57] <elfy> slickymasterWork: I tend to forget those 
[14:58] <elfy> sorry - I did you see you join the channel - you could have ;)
[15:10] <silviu> anybody help me to creat a ppa?
[15:10] <silviu> :((
[15:11] <silviu> my linux its xubuntu
[15:11] <slickymasterWork> yeah, I joined but something come up here and I was unable to participate
[15:12] <knome> slickymasterWork, see https://help.launchpad.net/Packaging/PPA for information
[15:12] <elfy> slickymasterWork: such is life 
[15:12] <knome> silviu, see https://help.launchpad.net/Packaging/PPA for information
[15:12] <slickymasterWork> lol knome 
[15:12] <knome> silviu, or you can ask #launchpad
[15:13] <elfy> slickymasterWork: that said, it's entirely likely that any translation comment would have got a "yea - others say the same thing" 
[15:14] <knome> i think we've got more interest with the calls
[15:14] <knome> at least one finnish guy asked about helping out
[15:14] <elfy> good 
[15:15] <elfy> at least that's positive - no idea what to do about testing 
[15:15] <knome> mh
[15:15] <slickymasterWork> most probably elfy 
[15:15] <knome> elfy, if only we would know *why* people don't test :/
[15:15] <silviu> thenks
[15:16] <elfy> rather - why they don't report - because I would have to  hope are testing 
[15:16] <slickymasterWork> I think people 'do test' knome, thing is why don't they report it
[15:16] <knome> maybe
[15:16] <knome> but as you implied, their testing could be put in parenthesis...
[15:17] <slickymasterWork> put in parenthesis ?!
[15:17] <slickymasterWork> what do you mean knome ?
[15:18] <knome> what i'm referring to is that many people "test" xubutnu
[15:18] <knome> *xubuntu
[15:18] <knome> maybe it can be called exploratory testing
[15:18] <elfy> I'll ask - see if people respond
[15:18] <knome> elfy, ++
[15:19] <elfy> late posting that - should read I've asked :p
[15:19] <knome> haha
[15:19] <knome> :)
[15:19] <slickymasterWork> :)
[15:19] <knome> yeah...
[15:19] <elfy> if it really is something like PaulW2U said -= then I'll say what we said in here 
[15:20] <elfy> rather you reported bug against xubuntu-foo than not at all 
[15:20] <knome> yep
[15:20] <slickymasterWork> what did he say?
[15:20] <knome> elfy, maybe we can try to improve http://xubuntu.org/contribute/qa/
[15:21] <elfy> hard to know what to report issues against - which I can understand
[15:21] <elfy> knome: possibly - lets see what sort of responses we get 
[15:21] <slickymasterWork> yes, I can see that elfy, but that doesn't explaing why aren't people reporting test in the tracker
[15:22] <elfy> knome: I for one go all cross-eyed when I look at that triage page
[15:22] <ali1234> you already know my feelings about the qa trackers
[15:22] <knome> if you do exploratory testing, then you basically can't; because you aren't following the testcases
[15:22] <elfy> slickymasterWork: because if you tested and there's a bug and you don't know what to report it against - you can hardly mark it passed 
[15:22] <ali1234> exactly
[15:22] <knome> elfy, triage page on the website or the wiki one? :)
[15:22] <elfy> knome: the wiki 
[15:23] <knome> yeah...
[15:23] <knome> "In a hospital, triage happens the instant a patient arrives through the emergency room doors. His vital signs are checked, his status assessed, and he gets sorted in amongst all the other patients waiting for treatment."
[15:23] <knome> that's a good way to start..
[15:23] <elfy> that's just like "We'd love you to help - but we're going to make it as hard as we possibly can for to you make any sense of the next 5000 words"
[15:23] <elfy> ^^ the wiki
[15:24] <ali1234> the other day i "tested" the iso and found two bugs
[15:24] <ali1234> i reported them both on launchpad
[15:24] <slickymasterWork> well there's always the possibility of marking a test, whether is a failed one, or not, and then just write some sort of a brief explanation in the commentary section
[15:24] <knome> it might sound duplicating, but what if we set up our own contributor documentation (as discussed before)
[15:24] <knome> we could explain things in an easy to understand way there
[15:24] <knome> and once we get things done, copy that back over to the wiki
[15:25] <ali1234> bug 1408495 and bug 1409015
[15:25] <ali1234> what i don't understand, is what am i supposed to do with the qa tracker?
[15:26] <knome> ali1234, we've gone through this discussion before...
[15:26] <ali1234> yeah, i never got a good answer
[15:26] <knome> ali1234, you don't have to understand it, testing and reporting bugs is enough
[15:26] <knome> ali1234, or you never wanted to accept the answer
[15:26] <ali1234> no answer was given
[15:27] <knome> but please let's not waste time again listening how you think the trackers suck
[15:27] <elfy> slickymasterWork: you can't fail and not give a bug
[15:27] <ali1234> just hand waving
[15:27] <knome> ali1234, reporting bugs in the trackers is the only way to measure how many people ran the pre-determined tests
[15:27] <ali1234> i don't know how to report bugs in the trackers
[15:27] <elfy> for better or worse - the trackers is the only thing we have to gauge that 
[15:27] <ali1234> expecially the ISO tracker
[15:28] <knome> ali1234, it also helps us know which bugs were experienced with which flavors/dailies
[15:28] <elfy> ali1234: you don't report bugs IN the tracker - you report bugs ON the tracker - you have to have the number first 
[15:28] <knome> ali1234, you are supposed to file the bugs just like you do now, and then list their numbers on the tracker
[15:28] <ali1234> knome: you're justifying the existence of the tracker, you're not saying what it is you want me to do with it
[15:28] <slickymasterWork> I know elfy, I was referring to situations where you go all the way through the test, you face a bug and don't no against package to file it, but the test itself isn't a fail
[15:28] <knome> ali1234, i want you to report that you tested a certain ISO with a certain testcase to 1) know you did that 2) know which bugs are present with specific dailies
[15:29] <ali1234> i didn't follow any part of the test case
[15:29] <knome> ali1234, then you shouldn't report a test in the tracker
[15:29] <slickymasterWork> in those cases, one could just write a brief description of what happened in the commentary section elfy 
[15:29] <elfy> ali1234: but the install testcases cover what you did I would suspect 
[15:29] <elfy> slickymasterWork: yes - but you still then have to pass it 
[15:29] <ali1234> well then, the reason i don't report tests in the tracker is because i shouldn't report tests in the tracker.
[15:30] <knome> ali1234, no, you should, but only if you follow the testcase instructions.
[15:30] <knome> ali1234, which is, like elfy said, pretty much what you did anyway
[15:30] <ali1234> except i didn't
[15:30] <knome> ali1234, but to make sure, you should know what the testcase says
[15:30] <ali1234> i didn't even read them
[15:30] <elfy> ali1234: so what did you actually do with the iso when you 'tested' it ?
[15:30] <knome> ali1234, then read them,.
[15:30] <ali1234> elfy: i installed it
[15:31] <ali1234> elfy: actually i should say i attempted to install it
[15:31] <ali1234> it didn't work
[15:31] <elfy> ok - something else, clean, auto-resize - os some other variable that we don't bother to report 
[15:32] <ali1234> all of the above
[15:32] <knome> ali1234, next time you are running "tests", please read the testcases to confirm you are going through all the steps mentioned in them
[15:32] <elfy> then you don't actually need to read them - the testcases are just a list of the things that you have to do to install 
[15:32] <knome> ali1234, and then report a tracker report with any bugs you found
[15:33] <elfy> if you're doing an install - you really don't need to read it - you can't install the wrong way 
[15:34] <ali1234> there's three different test cases for installing
[15:34] <knome> ali1234, you just said you did all of what elfy mentioned
[15:34] <knome> ali1234, eg. each of the test case once
[15:34] <ali1234> so you want three reports?
[15:34] <knome> yes.
[15:34] <knome> if you installed three times.
[15:34] <ali1234> i failed to install three times, yes
[15:35] <knome> that counts.
[15:35] <elfy> and if you failed to install - then they are critical bugs 
[15:35] <knome> ^ and the test status is failed
[15:35] <ali1234> so just to be clear this is the list of things i need to do when i find a bug:
[15:36] <ali1234> 1. generate hardware profile for my computer
[15:36] <elfy> ali1234: nope
[15:36] <knome> ali1234, you can omit 1, but if you do it, you only have to do it once and then relink to the same URL
[15:36] <ali1234> 2. format computer and attempt to install xubuntu
[15:36] <elfy> I don't do that
[15:36] <ali1234> 3. confirm bug still exists
[15:36] <ali1234> 4. report on iso tracker
[15:36] <ali1234> 5. repeat another 2x
[15:36] <knome> yes, or you can only try installing one way
[15:36] <knome> unless you want to use more time installing
[15:37] <knome> just doing one test is *fine*
[15:37] <knome> and 3) file a bug if one doesn't exist
[15:38] <ali1234> as i said, i already filed a bug (it's on the way to being fixed actually)
[15:38] <elfy> ali1234: all that you're really doing in effect is reporting the bug in one extra place - that is easy for all to see 
[15:38] <knome> ali1234, yes, just to clarify
[15:38] <ali1234> yeah i would be fine with just reporting that i found this one bug on the tracker
[15:39] <elfy> that's really all we are asking
[15:39] <ali1234> no, it isn't
[15:39] <knome> how come?
[15:39] <elfy> it's all I'm asking 
[15:40] <ali1234> well i can't report it now because the iso i used to install from is like 4 days old
[15:40] <knome> then zsync a newer ISO and retest
[15:41] <knome> and next time, report on the same day
[15:41] <ali1234> right, you're asking me to retest the installation every time i find a bug if it has been more than a day since the last one
[15:41] <ali1234> reinstalling is a two hour process
[15:41] <ali1234> reporting a bug takes 5 minutes
[15:41] <knome> ali1234, that's the only way to measure accurately if the bug still exists
[15:42] <knome> but really, we aren't asking you to retest every day
[15:42] <knome> you reinstall/-test as often as you feel like
[15:42] <ali1234> unless i find a bug every day
[15:42] <ali1234> which isn;t unusual at all
[15:42] <knome> in installation?
[15:42] <knome> or in the installed system?
[15:42] <ali1234> in the installed system
[15:42] <knome> that's what the package tracker is for.
[15:42] <ali1234> where is that?
[15:43] <ali1234> and how do i use it?
[15:43] <knome> packages.qa.ubuntu.com
[15:43] <knome> the same way
[15:43] <ali1234> if it's the same way then i do have to reinstall every day
[15:43] <knome> no
[15:43] <knome> the same way except the testcases are different
[15:43] <knome> they describe a process to test the applicaiton
[15:43] <knome> which is why you should READ what the test cases say
[15:44] <ali1234> i'm just going to start filing reports with comment "did not read the testcase but this thing is broken so fail anyway"
[15:44] <knome> please don't
[15:44] <knome> then rather just don't file the testcase reports
[15:45] <knome> filing the bugs for the applications is good enough
[15:45] <ali1234> for example, the firefox testcase doesn't even test for the bug i found
[15:45] <ali1234> so i should pass it on that basis?
[15:45] <knome> of course, test cases can't cover everything
[15:45] <knome> yes.
[15:45] <knome> here's the thing
[15:45] <elfy> no idea - the firefox test is not listed in the xubuntu packages 
[15:46] <knome> i don't mind if bugs that aren't mentioned on the testcase are reported on the tracker, BUT
[15:46] <knome> if you aren't reading the testcase, then you really shouldn't report in the tracker
[15:47] <ali1234> the point is i'm not going to follow the testcase anyway
[15:47] <knome> then don't report on the tracker
[15:47] <knome> but please also don't come telling us how you don't understand the trackers
[15:47] <knome> if you aren't going to use them as they are intended
[15:47] <ali1234> okay, but please don't act like you can't understand why nobody is using the trackers
[15:47] <ali1234> when you just told me not to use the tracker
[15:48] <knome> ali1234, i told you not to because you said you aren't going to use them in the intended way anyway
[15:48] <knome> ali1234, i'd love you to use them if you were to use them in the intended way
[15:49] <knome> ali1234, i wouldn't want you to file bugs either if you were not going to file them the way they are supposed to, either
[16:03] <knome> elfy, ochosi: http://temp.knome.fi/xubuntu/tester-of-the.png
[16:04] <ochosi> having my real name there and elfy's elf-name is just weird
[16:04] <knome> heh
[16:04] <ochosi> other than that, not bad ;)
[16:04] <knome> i wondered about that, but also, first draft
[16:04] <ochosi> it does look very formal
[16:04] <ochosi> i guess that is intended
[16:04] <knome> it's following the ubuntu certificate style
[16:05] <ochosi> ah
[16:05] <knome> http://fridge.ubuntu.com/2013/06/14/certificates-for-ubuntu-members/
[16:05] <ochosi> wasn't aware of that at all
[16:05] <ochosi> "has contributed ... contributions"
[16:05] <ochosi> who writes like that ^ ?
[16:05] <knome> lawyers?
[16:07] <knome> http://temp.knome.fi/xubuntu/certificate-blank.png
[16:11] <ochosi> 404
[16:12] <ochosi> ah, now it works
[16:12] <ochosi> weird
[16:12] <knome> :)
[16:14] <elfy> saw them - the look ok with only the one contribut(ed/ion) 
[16:37] <knome> bbl
[16:38] <brainwash> who will be our first TotW? :)
[16:39] <drc> ???   TOTW: Taste of the Wild: TotW: Tales of the World (game) TOTW: Topic of the Week: TOTW: Top of the World: TOTW: Temple of Three Winds ???
[16:55] <ochosi> tester of the week
[16:56] <drc> ah...thanks.  Didn't think it referred to dog food (much).
[17:09] <brainwash> heh :D
[17:09] <brainwash> ah, so that's the reason why ali1234 is interested in iso testing
[17:14] <drc> pleia2: http://www.everydaylinuxuser.com/2015/01/an-everyday-linux-user-review-of.html
[17:23] <pleia2> drc: cool, thanks
[17:23] <drc> You still want them here rather than -ot, right?
[17:30] <pleia2> yep
[17:30] <pleia2> it's on topic :)
[17:30] <drc> Only if it's a good review :)
[18:54] <pleia2> oh, I did some drafting of QA+stickers blog post: http://pad.ubuntu.com/QAIncentive
[18:54] <pleia2> given the timetable, we can publish whenever and then re-promote each time the beginning of a milestone/month begins
[19:17] <elfy> pleia2: which bit of it? 
[19:18] <elfy> oh nvm - assume the bit right at the bottom :)
[19:18] <pleia2> bottom of the pad, if that's what you're asking :)
[19:18] <elfy> it was - then I woke up :p
[19:18] <pleia2> I never know what to put in the testing instructions section
[19:18] <elfy> ohhh - I see that 
[19:27] <davmor2> pleia2: pretend you have a new user, walk them through 1 step at a time on how to use the thing you are testing.  Mkaing sure you are using it the correct way, that then sets the test step that should in theory always give the same results.  If you are not sure on how to use something then you might not be the person to write the test, but you can follow someone else to ensure you get the same result and confirm
[19:28] <davmor2>  the steps as good
[19:29] <davmor2> I hope that made sense
[19:29] <elfy> it did to me - but not really what's needed for this 
[19:30] <davmor2> elfy: I hope it would to you ;)
[19:30] <elfy> lol
[19:33] <elfy> pleia2: added some stuff 
[19:35] <pleia2> ta
[19:37] <elfy> and moved it to the beginning of the page
[19:42] <pleia2> davmor2: I meant to include in a simple blog post about testing :) there are lots of docs (and a video or two) that walk folks through how to use the trackers, but I often don't know what to point people to
[19:46] <elfy> https://wiki.ubuntu.com/QATeam/Roles/Tester 
[19:46] <elfy> is a basic one pleia2 
[19:47] <elfy> but at some point a Xubuntu specific thing will be useful
[19:48]  * pleia2 nods
[19:48] <pleia2> thanks
[19:48] <elfy> certainly not going to look this cycle - but maybe next cycle I will 
[19:49] <pleia2> suppose I should figure out if testdrive still works
[19:49] <pleia2> since all the docs still talk about it
[19:49] <elfy> ochosi: and we need to make a decision about who's going to get stickers 
[19:50] <pleia2> I figure you give me a list and I run a random script against it
[19:50] <elfy> wut? 
[19:50] <pleia2> a list of names of all the testers for each timeframe
[19:50] <elfy> oh 
[19:50] <elfy> that's not at all what I envisaged 
[19:51] <pleia2> oh, what did you have in mind?
[19:51] <elfy> and something I'll have nothing to do with :|
[19:51] <pleia2> top tester?
[19:51] <elfy> yea 
[19:51] <pleia2> ah
[19:51] <elfy> that's what the discussion has hinged around for months and months :)
[19:51] <pleia2> sorry, I misunderstood
[19:52] <pleia2> I'll reword the blog post
[19:52] <pleia2> probably "top tester who isn't part of -team and hasn't already received stickers"
[19:52] <elfy> imagine in a period - we have 10 people, 9 do 1 test, the 10th does 20 :)
[19:52] <elfy> well - that's what we need to make a final decision on 
[19:52] <pleia2> well, I figure we recognise them specifically with a pack at the end of the cycle if that happens :)
[19:53] <pleia2> but I doubt it would
[19:54] <elfy> left out specifying -devel deliberately - I call on users towards the cycle end as well 
[19:54] <pleia2> hm, so which list should we link to?
[19:55] <pleia2> they need to know how to get on the list :)
[19:55] <elfy> mmm
[19:57] <brainwash> ali1234: bug 1307657 is now fixed in trusty, hooray
[19:58] <pleia2> :)
[19:59] <elfy> pleia2: got both in :)
[19:59] <pleia2> wfm
[20:01] <elfy> Maybe we could add that we'll be looking at t-shirts too during this LTS cycle, books too - no reason why we can't apply to the fund for that stuff 
[20:03] <pleia2> good idea
[20:05] <elfy> pleia2: knome was playing with  certs too - did you see those ^^ 
[20:06] <pleia2> nope
[20:06] <elfy> http://temp.knome.fi/xubuntu/tester-of-the.png and http://temp.knome.fi/xubuntu/certificate-blank.png
[20:07] <pleia2> cool
[20:07] <pleia2> I should get a color printer :)
[20:08]  * pleia2 practices forging ochosi and elfy's sigs
[20:08] <elfy> mine's really easy 
[20:08] <pleia2> X
[20:08] <elfy> X ... 
[20:08] <pleia2> haha
[20:08] <elfy> ha ha ha
[20:09] <drc> Is that printing or cursive?
[20:09] <Unit193> Just like in Hitchhikers Guide to the Galaxy.
[20:10] <elfy> drc: cursive is hard with a blunt 6" nail
[20:10] <drc> Then use a Nine Inch Nail.
[20:14] <elfy> too loud for me
[20:46] <ochosi> pleia2: mine is just my name in Comic Sans 14
[20:46] <Unit193> :D
[20:47] <Unit193> ochosi: Set your terminal to comic sans, see how long you last (and see how seriously you take everyone too. :P )
[20:48] <ochosi> hehe
[20:48] <ochosi> yeah, good idea for people starting flamewars
[20:48] <ochosi> calm them down with Comic Sans ;)
[20:48] <elfy> ha ha 
[21:02] <knome> pleia2, was thinking we can just send those out as PDF's with fake sigs :)
[21:03] <knome> or copies of real, if signign people want that
[21:14] <elfy> I guess it would be *nicer* if one of the two signing actually sent them if we did pdf's
[21:19] <knome> yeaah, but is that really logistically possible (or sane)?
[21:19] <knome> that same person should be the one sending the stickers then as well to save in shipping
[21:20] <elfy> mmm
[21:20] <elfy> you were talking about pdf's :)
[21:20] <elfy> I've never received a pdf through the post ... 
[21:24] <knome> heh, right
[21:24] <knome> yeah
[21:24] <knome> sorry, am a bit unfocused
[21:24] <elfy> that's ok :)
[23:48] <brainwash> bluesabre: will you take a look at the xfpm bug which I've already linked several times? I want to create a branch which inverts the logind-handle-lid-switch value, but as of now I don't know if it's needed or not
[23:50] <brainwash> mmh, if I create it and request it to be merged, then you will have to check the report to understand the reasoning behind it :>