[02:12] <bluesabre> Unit193, look good to you? https://bugs.launchpad.net/ubuntu/+source/xfce4-notifyd/+bug/1668821
[02:23] <Unit193> Sure, perhaps get someone from studio to ACK.
[02:28] <bluesabre> Seemingly lubuntu as well
[02:28] <Unit193> Eh..
[02:28] -SwissBot:#xubuntu-devel- ::xubuntu-artwork:: [shimmer-themes-debian] r18 Update packaging for Numix theme (by Sean Davis)
[02:29] <bluesabre> Who are our normal contacts for those now?
[02:29] <Unit193> wxl, krytarik, sakrecoer: ↑
[02:31] <bluesabre> thanks
[02:31] <bluesabre> going to wander off for a bit now
[02:31] <Unit193> Cool, have fun.
[08:07] <flocculant> ochosi: built gtk3 panel in vm - using default panel location I *do* see the panel flicker you talk of - but I need to be almost out of the top of the panel to trigger it - also confirm there not being able to move plugins
[08:09]  * flocculant normally has panel in bottom left corner - shrunk down to 1 pixel auto resize
[08:26] <flocculant> you must have wondered how I wasn't see something so pronounced ;)
[09:22] <ochosi> flocculant: ok, it's just one more (minor) thing i have to fix
[10:12] <Unit193> cyphermox: I don't suppose you'll be doing a late devscripts merge? :>  Some delta has been fixed upstream.
[12:20] <bluesabre> flocculant, akxwi-dave, wxl, sakrecoer, if you would like to review https://bugs.launchpad.net/ubuntu/+source/xfce4-notifyd/+bug/1668821 and potentially ack it for zesty :)
[12:22] <flocculant> bluesabre: done by me
[12:23] <bluesabre> suppose I'll go ahead and sub -release
[12:23] <flocculant> best to I guess :)
[12:24] <bluesabre> oh
[12:24] <bluesabre> Unit193 already did
[12:24] <flocculant> sneaky :p
[12:24] <flocculant> you only look a bit silly :)
[12:24]  * bluesabre is happy with his dev team
[12:24] <flocculant> :D
[12:29]  * flocculant thinks he should install any gtk3 stuffs in the vm 
[14:47] <Perigee> Hi everyone, I would like to help out with Xubuntu development. I'm thinking QA testing to start. Could someone help get me setup to do so?
[14:49] <slickymasterWork> hello Perigee, the best place for you to start is to have a read at the QA section of the Xubuntu contributors documentation: http://docs.xubuntu.org/contributors/qa-tester.html
[14:49] <flocculant> hi Perigee - quick first question 
[14:49] <Perigee> flocculant: Shoot
[14:50] <flocculant> Perigee: can you test on hardware - running the dev version (which is pretty much completely stable now) or do you intend to test thing in a vm? 
[14:51] <flocculant> this late in the cycle - I'd prefer people who are brave enough to do some real world testing :)
[14:51] <Perigee> I can do either. I have a few different laptops I can test on, and at least one desktop, maybe two 
[14:51] <flocculant> awesome
[14:52] <flocculant> so best way to start is grab the daily and install that - we have a few official ppa's we use to
[14:53] <Perigee> ok, what do I need to do about the ppa's?
[14:53] <flocculant> for a bit more detail - you can look at the dev docs which slickymasterWork posted (there are actually 3 'tester' chapters - first one deals with setting up 
[14:53] <Perigee> Ok will do
[14:53] <flocculant> http://docs.xubuntu.org/contributors/ chapters - 4 to 6
[14:54] <flocculant> I'm pretty much around for a few hours now - akxwi-dave is the other qa lead - so either of us will be able to help with specifics - anyone is likely to help with less specific stuff
[14:55] <Perigee> Great, I'll read through that and get the basics setup.
[14:55] <flocculant> okey doke
[14:58] <flocculant> Perigee: dual booting is a useful half-way - I kind of do that - if dual booting can be used to describe having 6 options :D
[15:00] <Perigee> flocculant: Been there myself with the hexabooting at times. :) I remember back in my Gentoo days (2004 era or so) I had a huge list... just trying to get things to work
[15:01] <flocculant> :)
[15:01] <flocculant> good choice of word there too :D
[15:09] <cyphermox> Unit193: what would it bring us? I'm not sure it's that big of a deal...
[15:11] <cyphermox> Unit193: tbf, before looking at the merge, we should fix that issue with the autopkgtests not passing on some architectures
[15:11] <cyphermox> (because otherwise it wouldn't transition anyway)
[16:27] <flocculant> knome akxwi-dave - updating of http://xubuntu.org/contribute/qa at https://xubuntu.org/?p=4279&preview=true
[16:28] <flocculant> knome: 5 attempts to login today before I had more than my profile - really must talk to IS about that :p
[16:33] <knome> hmmh
[16:33] <knome> right
[16:34] <knome> that's weirdish
[16:34] <knome> i'll try to debug it with you later today to see if $something helps
[16:34] <flocculant> aah ok 
[16:34] <knome> but it's not "much" i can do
[16:35] <knome> and i believe there's not much more IS can do...
[16:35] <flocculant> well
[16:35] <flocculant> it worked first time before 
[16:35] <flocculant> so 'something' has changed :D
[16:36] <knome> heh
[16:36] <knome> maybe
[16:36] <knome> anyway, coffee time, bbl
[16:36] <flocculant> :)
[16:54] <Perigee> flocculant: I've gone through the doc chapters, signed up for the various resources. I just got a VM running the daily ISO + PPA's. Is there a rigid testing regimen that needs to happen each day/week and be reported somewhere as success/failure? I understand the bug reporting aspect.
[16:54] <genii> mmm coffee
[16:59] <flocculant> Perigee: http://iso.qa.ubuntu.com/qatracker/milestones/369/builds alphabetical - right at the bottom
[17:00] <flocculant> the only thing we do specifically is iso testing this cycle
[17:00] <flocculant> sometimes we do package testing - mostly when dev wants something testing or it's lts cycle
[17:01] <flocculant> hi genii :)
[17:03] <Perigee> flocculant: Ok I see now. Is that what I should focus on then? Running those test procedures for the various ISO's and reporting via the tracker there? (On various hardware of course)
[17:03] <genii> flocculant: Salutations
[17:04] <flocculant> Perigee: to be honest - the greatest value for 'me' is people that run the dev version daily in use 
[17:04] <flocculant> much of the iso stuff is common - so if there's an issue - it would be *buntu not just us
[17:05] <flocculant> particular things like lock breaking are issues we keep seeing - but that's not likely to break again this cycle
[17:05] <Perigee> flocculant: Got it, and doing that throughout my day would be reported just with bug reports if any are found, right?
[17:05] <flocculant> yup - though check for dupes first 
[17:05] <Perigee> flocculant: Ok then, makes sense.
[17:05] <flocculant> Perigee: and check upstream https://bugzilla.xfce.org/ too
[17:06] <flocculant> could be it's reported there and not on lp 
[17:07] <flocculant> I tend to find issues just doing what I do normally ... 'mmm that didn't do that last week' 
[17:07] <Perigee> Ok, I'll certainly get my main laptop running the daily
[17:08] <flocculant> Perigee: that would be great :)
[17:11] <flocculant> Perigee: this late in the cycle little is going to change - and oops moments are unlikely
[17:11] <Perigee> flocculant: Ok, you should see me on the Launchpad team and elsewhere in Ubuntu-land as "crouthamela / Andrew Crouthamel".
[17:12] <flocculant> if you stick around (which I hope) starting using the dev cycle on release+ 1 day like I do can see a few hiccups - hence the multi-boot scenario but rarely am I more than a short while outside
[17:12] <flocculant> ok cool - nice to meet you :)
[17:13] <Perigee> :)
[17:14] <flocculant> but to be honest - the times that packages landing completely breaking are few now - changes in the way packages land and testing by canonical are different than they were I believe
[17:14] <Perigee> So they're more careful now?
[17:14] <flocculant> seems so
[17:15] <knome> there have been several instances where uploading after freezes have been made much "harder" (for justified reasons), and i think this has started paying off
[17:15] <flocculant> well - not perhaps careful, but proposed is usually disabled - you could break your system more often by using that repo if you wanted too
[17:15] <flocculant> knome: ack
[17:15] <knome> so developers aren't maybe any more careful, but the archive admins and release team are more cautious about late uploads ;)
[17:16] <Perigee> ahh
[17:16] <flocculant> I think in the last couple of cycles - lock has been problematic - but not unusable
[17:16] <flocculant> more likely to see issues actually during install than anything else
[19:29] <knome> flocculant, around?
[19:33] <knome> slickymaster, around?
[19:36] <flocculant> knome: yea
[19:36] <flocculant> for a while - then bbl
[19:36] <knome> oh
[19:36] <knome> give me 5 mins
[19:37] <flocculant> actually - bbl later noq, was waiting for M to return :)
[19:37] <chatter29> hey guys
[19:37] <knome> heh
[19:37] <knome> hello chatter29 
[19:38] <chatter29> allah is doing
[19:38] <knome> flocculant, ok, so look at https://temp.knome.fi/xubuntu/contributor-docs/contributor/C/
[19:38] <knome> flocculant, does the QA ToC structure make sense like this?
[19:39] <knome> flocculant, and: would you rather see even more subsection titles there (under testing infra etc.) or is this good enough?
[19:45] <akxwi-dave> :-) that looks good knome
[19:46] <knome> oh obviously akxwi-dave needs to ack too
[19:46] <knome> ok, i'll look into getting things sorted so that the different subsections can still have their own pages but appear as subitems like this
[19:46] <akxwi-dave> actually it 
[19:46] <knome> it what? :)
[19:47] <akxwi-dave> looks really good
[19:47] <knome> heh, ok, good good
[19:47] <knome> i'm planning to land some more stuff on documentation, likely also subsections, so need to do this in order to keep things clean
[19:47] <akxwi-dave> and evenin
[19:47] <knome> hullo hullo!
[19:51] <knome> ahh great, incremental config for contributors <3
[21:24] <flocculant> knome: yea - as akxwi-dave says looks good 
[21:31] <knome> now to beat docbook as long as it does what i want...
[21:31]  * flocculant hands knome the beating stick
[21:31] <knome> i have my hammer out...
[21:31] <flocculant> possibbly too much :p
[21:32] <knome> nah
[21:32] <knome> i might need bigger tools
[21:36] <Unit193> cyphermox: And ah fun.  Didn't see anything that'd fix the gpg2 fun.
[21:38] <flocculant> knome: as far as subsections goes - the fewer the better imo
[21:40] <knome> mhm
[21:40] <knome> i've almost got what i want...
[21:40] <knome> but not quite
[21:41] <flocculant> :)
[21:43] <knome> hmph.
[21:43] <knome> now i'm at least getting the subsections i want printed
[21:44] <knome> (and nothing more)
[21:47] <knome> how important do you think it is to be able to get the subsections into separate pages?
[21:47] <flocculant> to print?
[21:48] <knome> like, http://docs.xubuntu.org/contributors/qa-testing.html
[21:48] <flocculant> oh you mean like when dev finishes and docs starts? I'd ay quite
[21:48] <knome> nope, the subsections of *qa*
[21:49] <knome> i understand this will be quite a long page if they are all in one...
[21:49] <knome> basically, whole qa stuff would appear on one html page
[21:49] <flocculant> mmm - better if they do - but *I* would be more likely to print the whole of it - others maybe not
[21:49] <knome> i'll look into it then
[21:55] <slickymaster> am now, knome :)
[21:55] <slickymaster> evening all
[21:55] <knome> oki
[21:55] <knome> so basically see the discussion with flocculant aboce
[21:55] <knome> above too
[21:55] <slickymaster> already saw
[21:56] <slickymaster> and I do agree with flocculant 
[21:56] <knome> above too
[21:56] <knome> hmm, oops
[21:56] <slickymaster> regarding avoiding large html pages
[21:57] <slickymaster> and do +1 your subsections idea, knome 
[21:59] <knome> hmm, so every sect1 should be a chunk...
[22:00] <slickymaster> not sure I understand what you mean, knome 
[22:01] <slickymaster> to what do you refer by sect1?
[22:01] <knome> you don't have to
[22:01] <knome> i'm just saying it aloud for my personal reference later :P
[22:01] <slickymaster> lol
[22:02] <flocculant> knome: not sure how the sub-sectioning is working but Dispute Resolution on strategy should be a section - not sub-section of development
[22:02] <flocculant> unless we think dev cause all the issues :p
[22:02] <knome> well that's a content issue, not a technical one
[22:03] <knome> i'm mostly poking the technical stuff today
[22:03] <flocculant> assumed as much - just making sure now rather than in 6 months :D
[22:04] <knome> actually i think the issue is just that "Development" is a clumsy section title; it should be more like "contributing" or sth
[22:04] <knome> because if you look at the content/context, it all is general for everything, not just code contributions
[22:06] <flocculant> or communication - cos that's what the majority is about - then sub-section comms would need another name
[22:07] <flocculant> bluesabre: did I say that seek in parole was a bit broken? 
[22:10] <flocculant> knome: next time I'm trying to login to x.org I'll grab utc time too - then I'll go see IS and report it - having an actual time should help
[22:10] <flocculant> in the meantime - I'm off - night all 
[22:10] <slickymaster> night flocculant 
[22:24] <cyphermox> Unit193: if there's something you need though, it's a different story
[22:34] <knome> because if you look at the content/context, it all is general for everything, not just code contributions
[22:34] <Unit193> cyphermox: Better handling of buildinfo files (for when one is building Debian packages) and git-deborig looked interesting, but not enough for you to drop everything else for 'em.
[22:35] <knome> oops again
[22:35] <knome> i'll move the irc window elsewhere...