[00:30] <bluesabre> Gridcube: it's fixed in our release, http://changelogs.ubuntu.com/changelogs/pool/universe/x/xfce4-weather-plugin/xfce4-weather-plugin_0.8.3-2/changelog
[00:31] <GridCube> bluesabre, its on -proposed?
[00:33] <bluesabre> Gridcube: Fixed in -2 in debian and utopic, currently in trusty-proposed.  The issue was the old weather API was deprecated
[00:34] <bluesabre> brainwash_: right, it's a minor UI change... which is why we haven't backported it sooner.
[00:34] <GridCube> ok, so ill enable -proposed and test :)
[00:34] <GridCube> thnks
[00:34] <bluesabre> thanks GridCube
[00:41] <GridCube> :D
[00:41] <GridCube> it works!
[00:41] <GridCube> automatically
[00:41] <bluesabre> woot!
[00:42] <GridCube> :) now to disable -proposed again :P
[00:42] <ochosi> late/brief evening, bluesabre 
[00:42]  * ochosi just installed xubuntu on a 6yr old macbook today
[00:42] <ochosi> worked like a breeze/y badger
[00:43] <ochosi> or in fact. not at all. it really was a breeze
[00:43] <ochosi> breeze badger would've been extremely hard to install on a macbook i guess
[00:46] <bluesabre> maybe
[00:46] <bluesabre> breezy would definitely have been PPC time, not sure how good support was back then
[00:47] <bluesabre> 6yr old might have actually been intel
[00:49] <ochosi> yup, was/is intel
[00:49]  * bluesabre is going to add apport hooks to all his apps for 15.04 to simplify bug reports
[00:50] <ochosi> mm, good ieda
[00:50] <ochosi> idea
[00:50] <ochosi> that also means you'll get loads of bugreports (or not, i hope)
[00:50] <bluesabre> hopefully loads of bug reports with obvious solutions ;)
[00:51] <bluesabre> or "you ran that as sudo... again... congrats!"
[00:51] <ochosi> hehe
[00:51] <ochosi> keeping my fingers crossed
[00:52] <bluesabre> what are you up to ochosi?
[00:53] <ochosi> not too much, it's late, i'm just trying to catch up on some things and finish unfinished mail
[00:54] <bluesabre> cool, I'm torn between being productive and goofing off atm
[00:54] <bluesabre> :)
[00:56] <ObrienDave> goof off being productive ;P
[00:56] <ochosi> bluesabre: what about low-hanging fruit?
[00:56] <ochosi> (i.e. those two xfsettings bugs i mentioned earlier ;))
[00:56] <bluesabre> yeah, that might be the way to go
[00:57] <bluesabre> I'll see if they work in general and then upload, waiting for others to complain :)
[00:57] <bluesabre> baby steps to fix these issues
[00:57] <ochosi> yup, sounds great
[00:57] <ochosi> well they're both rather unproblematic i think
[00:58] <ochosi> mostly exception-catching
[00:58] <ochosi> anyway, mail sent
[00:58] <bluesabre> also, the mythtv one has a fix now too
[00:59] <ochosi> mythtv?
[00:59] <bluesabre> mythbuntu... I'll have to dig up the bug.  I think its vga/tv/etc outputs
[01:00] <ochosi> oh right
[01:00] <ochosi> really?
[01:00] <ochosi> that one where the external tv got its power deactivated?
[01:01] <bluesabre> yeah that one
[01:01] <ochosi> oh cool
[01:01] <ochosi> i thought it was sorta unfixable
[01:01] <bluesabre> somebody came up with a patch that worked for them
[01:01] <ochosi> since i had no idea how to even reproduce it
[01:02] <ochosi> without buying a tv
[01:02] <bluesabre> our goal will be to make sure that patch doesn't break it for other scenarios
[01:02] <ochosi> right
[01:02] <ochosi> yeah, that makes sense
[01:02] <ochosi> gotta head to bed now
[01:02] <ochosi> will be around tomorrow though
[01:03] <bluesabre> I'll try to get some basic testing in and upload tonight... I'll take care of the small fix you messaged me about earlier now
[01:03] <ochosi> for some time at least
[01:03] <ochosi> cool
[01:03] <ochosi> sorry, just too tired for any real work now
[01:03] <ochosi> have a good night and ttyl
[01:03] <bluesabre> np
[01:03] <bluesabre> have a good night
[01:03] <ochosi> ty
[01:04] <ali1234> mythtv problems?
[01:06] <bluesabre> https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1308105
[01:06] <ali1234> bluesabre: would those xfsettings bugs ochosi mentioned happen to include the one i wrote a patch for?
[01:07] <bluesabre> ali1234: I see this one with your name floating around, https://bugzilla.xfce.org/show_bug.cgi?id=11229
[01:07] <ali1234> yeah, that one
[01:08] <bluesabre> anything I should know, or should the final patch be a safe cure-all?
[01:08] <ali1234> it should be perfectly safe
[01:08] <ali1234> cure-all is a bit far
[01:08] <bluesabre> :)
[01:09] <ali1234> i suspect there are many similar problems all over xfce to do with unexpected values in the registry... erm, i mean xfconf
[01:09] <bluesabre> probably
[01:09] <ali1234> but that one key should be bullet proof at least :)
[01:09] <bluesabre> we stole the parole xfconf code from thunar, so if you find issues in thunar, let me know :)
[01:09] <ali1234> i don't like to go near the thunar code
[01:10] <ali1234> essentially though, the problem is that when you ask for the value from xfconf, you get a g_value which can be of any type
[01:11] <bluesabre> right, I've dealt with that a bit recently
[01:11] <ali1234> if you assume it's a string when it isn't, and then ask for the value, you get back NULL
[01:11] <ali1234> if you then attempt to use the string -> segfault
[01:11] <ali1234> and of course user can write any value into any key with any type, at any time
[01:12] <bluesabre> that's fun... I'm guessing it would be a large effort to harden xfconf in general?
[01:12] <ali1234> i would expect so
[01:13] <bluesabre> and then at what point are xfconf and gsettings basically the same :)
[01:14] <ali1234> the other half of the patch is because if you unset a g_value it forgets it's type, and then you can't assign a value to it without reinitializing it
[01:14] <ali1234> i grepped the entire xfce source code for other instances of this type of bug and there were none
[01:15] <bluesabre> oh, that's reassuring at least
[01:17] <ali1234> well, no obvious ones, ie within 5 lines context
[01:18] <ali1234> i doubt there are any subtle versions of this though
[01:26] <bluesabre> Tested, verified, and committed.
[01:26] <ali1234> thanks
[01:26] <bluesabre> ochosi: you're a bug admin, right? Can you mark this one fixed tomorrow? https://bugzilla.xfce.org/show_bug.cgi?id=11229
[01:27]  * bluesabre can only comment on xfce4-settings
[01:27] <bluesabre> despite having full git push to the main branch
[01:27] <bluesabre> and release manager rights :)
[01:30] <bluesabre> ali1234: you're familiar with the forking issues, right?
[01:30] <ali1234> yeah
[01:31] <bluesabre> can you advise whether the first patch here is acceptable, or if I should go with Eric's patch? I'm not sure when the forking issue has occurred https://bugzilla.xfce.org/show_bug.cgi?id=11188
[01:32] <bluesabre> I'm leaning towards the second patch... just ignore --display in general
[01:34] <ali1234> no, eric's is better, as he said, "I was trying to avoid the gtk_get_option_group call because it calls gtk_init"
[01:34] <ali1234> and there are other ways to parse the arguments without invoking gtk init, which is what his patch does, apparently
[01:35] <ali1234> oh wait, that isn;t what it does
[01:35] <ali1234> hmm, i'm not sure
[01:37] <ali1234> no wait, i was pretty much right
[01:37] <ali1234> the first patch is going to call gtk_init before the fork, which should always be avoided, even if it appears to work
[09:00] <ochosi> morning folks
[09:01] <slickymasterWork> hey ochosi, morning
[09:28] <ochosi> bluesabre: taken care of the bugreport in bz and on the critical list
[09:28] <ochosi> i suppose you didn't get to the second one anymore :>
[09:36] <bluesabre> good morning ochosi
[09:36] <bluesabre> getting to the second one now
[09:37] <bluesabre> ali1234: thanks for taking a look
[09:42] <ochosi> cool
[09:44] <bluesabre> for the other bug, I mean that xfsettingsd sometimes crashes when unplugging a monitor, in its current state
[09:46] <ochosi> you mean the one with the --display option?
[09:46] <bluesabre> https://bugzilla.xfce.org/show_bug.cgi?id=11107
[09:47] <ochosi> oh that
[09:48] <ochosi> right, so then there's actually two bugreports
[09:48] <ochosi> that need looking at
[09:48] <ochosi> or pushing their patches actually
[09:48] <ochosi> that one with the tv mode and the other one with the --display option
[09:49] <bluesabre> yeah, probably going to wait for another comment on this one with additional confirmation
[09:54] <ochosi> this == the latter?
[09:55] <bluesabre> the one I just posted
[09:55] <ochosi> oh right
[09:55] <bluesabre> we're having some communication issues this morning :P
[09:56] <ochosi> hehe, seems like it :)
[10:02] <bluesabre> ochosi: committed, https://bugzilla.xfce.org/show_bug.cgi?id=11188
[10:03] <ochosi> great, bz and buglist updated
[10:04] <bluesabre> thanks
[10:05] <ochosi> np, we should probably get you the keys to bz though
[10:05] <ochosi> it's a bit silly you can't do anything there
[10:14] <ochosi> hmpf, successfully pinged xnox, not too sure anything will come of it though
[10:23] <bluesabre> going to get ready for work now, bbl
[10:28] <ochosi> hf bluesabre, ttly
[10:28] <ochosi> ttyl
[11:53] <elfy> ochosi: I see you're missing tonight - got any comments on the 3 discussions points?
[13:11] <ochosi> elfy: i kinda second the xubuntu+1 support proposal
[13:11] <ochosi> we can say we accept that after final beta, makes sense to me
[13:11] <ochosi> better than getting people in the devel channel imo
[13:21] <ochosi> elfy: the QA processes stuff looks a bit bureaucratic to me, considering we're so few people actually following them, but you're the QA lead so I'd think it's up to you to decide how you wanna organise testing
[13:22] <ochosi> i'm fine with getting the team more involved in testing, although i think that it'd be even better to try to get frequent visitors of #xubuntu or new users involved in this
[13:34] <elfy> well ... me asking people in team to test has had really good results ;)
[13:38] <elfy> ochosi: perhaps we should include the ordinary mailing list for testing calls 
[13:38] <ochosi> yeah
[13:39] <ochosi> that's definitely a good idea
[13:39] <ochosi> it's really a pity i can't be there tonight
[13:39] <elfy> that's ok
[13:39] <ochosi> but i would want us to start laying out plans for V asap
[13:39] <ochosi> and we have to settle on either trello or launchapd
[13:39] <ochosi> lp
[13:39] <elfy> ochosi: you know the release note pad is up at http://pad.ubuntu.com/FinalReleaseNotes
[13:39] <ochosi> doing both is exhausting
[13:40] <ochosi> no, thanks, i obviously missed that
[13:40] <elfy> frankly I'd go for LP 
[13:41] <elfy> bluesabre said he was going to get a changelog on the pad 
[13:43] <ochosi> wait, i thought you were on the trello side?
[13:45] <ochosi> what seems most important to me personally is that we only use *one* tool
[13:45] <ochosi> monitoring >1 is just a waste of resources/time/energy
[13:48] <elfy> trello works for me ochosi - and I'll use it again - but I've not got the energy to get people to use it - I don't care now
[13:50] <elfy> I'm certainly not interested enough to set it all up again - though that said I'll not be setting up all the blueprints either - team leads can do that 
[13:53] <ochosi> yeah, every team lead should set his/her blueprint up anyway imo
[13:54] <ochosi> i actually think that this should be a discussion of team leads, since those have the responsibility to keep their stuff up to date (even if others contribute)
[13:56] <elfy> ochosi: do you want me to add trello to the agenda? we can start it if nothing else
[13:56] <ochosi> yeah, i think it'd be good to start the discussion
[13:56] <ochosi> thanks elfy 
[13:57] <ochosi> then we should think of a period we deem appropriate for setting up blueprints and goals for 15.04, i'll try to think about this a bit more on the weekend
[13:57] <elfy> okey doke
[13:59] <elfy> as it stands I'd mark the images ready for release - so that at least is good 
[14:00] <ochosi> sweet
[14:01] <elfy> still got the black bug - but as knome said day or so ago - at least it's black and not a debian background or something 
[14:02] <ali1234> "installer wallpaper replaced by spinal tap album cover"
[14:02] <elfy> ali1234: lol
[14:02] <elfy> as long as we set default volumes to 11 I'd +1 it 
[14:03] <ali1234> are we still going with the pink everywhere?
[14:03] <elfy> yep
[14:03] <elfy> at least I've not heard any different to that
[14:05] <ali1234> next release we should replace it with turquoise because, well, https://www.google.co.uk/search?q=vervet&tbm=isch
[14:05] <elfy> LMAO
[14:32] <ochosi> ali1234: haha, yeah, i'm all for it
[14:33] <knome> >__<
[14:34] <elfy> knome: it is a *blue* sort of :p
[14:38] <knome> hah
[14:38] <knome> when did elfy start teaching me about colors ;)
[14:43] <elfy> lol
[15:12] <Pwnna> https://bugs.launchpad.net/ubuntu/+source/xfce4-settings/+bug/1382888
[15:14] <knome> Pwnna, what is "extend" ?
[15:14] <Pwnna> two monitor
[15:14] <Pwnna> not mirror
[15:14] <knome> it wouldn't hurt if you had examples of commands/gui stuff you do to do that
[15:15] <knome> for the points 1 and 2 at least
[15:16] <knome> and disconnect what power?
[15:16] <knome> it isn't clear to me what you are doing
[15:16] <Pwnna> knome: actually i don't think that part is necessary
[15:17] <Pwnna> just plug another monitor into your computer, xrandr to turn it on, and then turn it off and disconnect
[17:14] <ali1234> Pwnna: i do that all the time and it works fine
[17:14] <ali1234> what we actually need is a backtrace
[18:33] <Pwnna> also: https://bugzilla.xfce.org/show_bug.cgi?id=11188
[18:33] <Pwnna> not sure if this is related
[18:33] <Pwnna> ali1234: where do i get a back trace for that?
[18:46] <Pwnna> xorg.log?
[19:42] <elfy> !team | 20 minute warning
[19:42] <Noskcaj> ok
[19:42] <skellat> I'll be over in #ubuntu-meeting chairing the LoCo Council meeting
[19:43] <knome> elfy, so are we starting 2 minutes past? ;)
[19:43] <elfy> skellat: yea I realise - I'll be trying to keep an eye on it too 
[19:43] <elfy> knome: yep
[19:47]  * slickymaster is starting to have diner
[19:47] <slickymaster> s/diner/dinner
[19:52] <pleia2> neat, I'm in an airport lounge with lousy wifi, but I am here-ish for meeting
[19:54] <elfy> pleia2: I'll make sure that it looks like you've lost signal but actually not be saying anything for long stretches :D
[19:54] <elfy> just to add some confusion to your day :p
[20:00] <elfy> #startmeeting Xubuntu Community Meeting
[20:00] <meetingology> Meeting started Tue Oct 21 20:00:46 2014 UTC.  The chair is elfy. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[20:00] <meetingology> Available commands: action commands idea info link nick
[20:00] <xnox> hi
[20:00] <elfy> ok then, lots to get through - who's here now
[20:00] <elfy> hi xnox 
[20:00] <xnox> ubiquity no desktop background is due to xsettingsd
[20:01] <xnox> not working, that is it's defunct when ubiquity-dm spawns it
[20:01] <pleia2> o/
[20:01] <jjfrv8-work> o/
[20:01] <slickymaster> o/
[20:01] <xnox> xfwm4 is also complaining about the lack of SESSION_MANAGER and i have no clue know is that suppose to be
[20:01]  * xnox looks around and follow the crowd
[20:01] <xnox> o/
[20:02] <pleia2> xnox: it's meeting time :)
[20:02] <dkessel> o/
[20:02] <elfy> #chair pleia2 jjfrv8-work slickymaster 
[20:02] <meetingology> Current chairs: elfy jjfrv8-work pleia2 slickymaster
[20:04] <elfy> xnox: not sure if either ochosi or bluesabre are about tbh - they'd be the ones to deal with it - though it's good to know what it is - we were kind of resigned to the black background this late - it not being something really odd for us like debian background
[20:04]  * slickymaster appreciates that elfy is giving him some time to finish his dineer
[20:04] <slickymaster> * dinner
[20:05] <knome> o/
[20:05] <elfy> xnox: but if that's the reason - that's good to know 
[20:05] <elfy> #chair knome 
[20:05] <meetingology> Current chairs: elfy jjfrv8-work knome pleia2 slickymaster
[20:05] <elfy> and hi
[20:05] <elfy> we'd best march on - bit to get through
[20:05] <knome> ola
[20:05] <elfy> #topic Open action items
[20:05] <slickymaster> olá knome 
[20:06] <elfy> #ACTION: pleia2 to contact unixstickers
[20:06] <meetingology> ACTION: : pleia2 to contact unixstickers
[20:06] <pleia2> I did that
[20:06] <elfy> I knew that too :)
[20:06] <pleia2> they replied :)
[20:06] <elfy> so we just need to ask and then we'll get them? 
[20:07] <pleia2> yep
[20:07] <elfy> cool - so we can mark that one as done :)
[20:07] <pleia2> #DONE pleia2 to contact unixstickers
[20:07] <elfy> like that :p
[20:07] <elfy> #ACTION: knome to write a more formalized proposal about the QA process improvements with elfy after N days of comments/feedback for the pad 
[20:07] <meetingology> ACTION: : knome to write a more formalized proposal about the QA process improvements with elfy after N days of comments/feedback for the pad
[20:07] <knome> hrr, i haven't got to that
[20:08] <elfy> well - I know I've not done much on that
[20:08] <knome> i'll try to get to that ASAP
[20:08] <elfy> and I also know there's been little in the way of comment too
[20:08] <knome> just carry on :)
[20:08] <knome> yeah... sadly
[20:08] <knome> but i guess everybody just agress
[20:08] <knome> *agrees
[20:08] <elfy> well 
[20:09] <elfy> earlier today : <ochosi> elfy: the QA processes stuff looks a bit bureaucratic to me, considering we're so few people actually following them, but you're the QA lead so I'd think it's up to you to decide how you wanna organise testing
[20:09]  * slickymaster agrees
[20:09] <knome> right
[20:09] <elfy> and given that half of it is tied up with making sure that QA and dev get together at cycle start and actually plan things - makes me think we're not going to get far with it
[20:10] <knome> i'll try to make it as little bureaucratic as possible..
[20:10] <knome> though it's  a good thing if qa and dev can get togehter at the beginning of the cycle
[20:10] <elfy> the trouble is - this process issue is tied up with a whole bag of strings
[20:10] <elfy> knome: +1 to that 
[20:11] <mikodo> hey! I just stumbled into this. What is pad ^
[20:11] <knome> the reason why i'd like to have at least something documented is that then we have at least... something documented
[20:11] <elfy> I'm just concerned that time will drag on and I'll end up with less time to plan
[20:11] <elfy> mikodo: http://pad.ubuntu.com/xubuntu-qa-v-cycle
[20:11] <mikodo> elfy, thx and hie
[20:11] <mikodo> *hi
[20:12] <elfy> knome: yep - anyway I think move this to mailing list now to at least try and get *some* comment
[20:13] <elfy> I can get something to the list by the end of the week if that's the case
[20:13] <knome> elfy, let's work with that on the pad then or sth, we have the same goal anyway
[20:14] <elfy> yea - but we really need -team to be in this as well imho
[20:14] <elfy> it does kind of say that they've got to test if asked :)
[20:15] <elfy> #action xubuntu-qa to continue working with v-cycle qa pad
[20:15] <meetingology> ACTION: xubuntu-qa to continue working with v-cycle qa pad
[20:15] <elfy> #action elfy mail the -devel list to garner comment on pad
[20:15] <meetingology> ACTION: elfy mail the -devel list to garner comment on pad
[20:15] <elfy> knome: does that work for you?
[20:15] <knome> yep
[20:16] <elfy> moving on then
[20:16] <elfy> #ACTION: knome to move the "translations important for xubuntu" list to the processes page, discussion can continue when needed 
[20:16] <meetingology> ACTION: : knome to move the "translations important for xubuntu" list to the processes page, discussion can continue when needed
[20:16] <slickymaster> hasn't been done yet
[20:16] <elfy> did you get around to that ?
[20:16]  * slickymaster hides
[20:16] <elfy> slickymaster: were you doing that?
[20:17] <slickymaster> no elfy, it was knome who would do it
[20:17] <slickymaster> at least that's what was decided 
[20:17] <elfy> I thought so - anyway if it's not done - we can move on I guess 
[20:18] <slickymaster> but I can do it, if he doesn't mind
[20:18] <slickymaster> or lacks the time to
[20:18] <elfy> knome: ^^ you can pass the buck if you like :)
[20:19] <knome> i'll do that today.
[20:19] <elfy> ok - thanks knome 
[20:19] <knome> np
[20:19] <slickymaster> thanks knome 
[20:19] <knome> np again ;)
[20:20] <elfy> there were a couple of -quality actions on the logs from last meeting, neither have been started - not had time this week 
[20:20] <elfy> likewise -bugs were going to talk to -qa re a triage plan - even if they'd wanted to I'd not have had time this week :)
[20:21] <elfy> I *think* that's all the open action items
[20:21] <elfy> if anyone thinks differently - speak now or forever hold your peace :)
[20:22] <elfy> moving on then
[20:22] <elfy> # Team updates
[20:22] <elfy> # Topic Team updates
[20:23] <elfy> I mean 
[20:23] <pleia2> no space :)
[20:23] <pleia2> #Topic Team updates
[20:23] <elfy> sigh :D
[20:23] <elfy> anyone got anything ?
[20:23] <elfy> other than me :p
[20:24] <pleia2> #info unixstickers has sold plenty of Xubuntu items, so we just need to let them know what we want for the reward based QA program
[20:24] <elfy> thanks :)
[20:24] <pleia2> #info unixstickers will also be producing t-shirts soon, production info here: http://www.unixstickers.com/tshirts/underground-t-shirts/the-ultimate-pirate-bay-tshirt
[20:24] <slickymaster> nothing from me
[20:25] <knome> nope
[20:25] <knome> quiet week
[20:25] <elfy> ok 
[20:25] <elfy> #info Image testing has been better for the final image
[20:25] <elfy> #info upgrade tests though only have 1 result from me so ... 
[20:26] <pleia2> I did some final iso testing when I was at home, but won't be able to pitch in this week because hotel wifi, etc :\
[20:26] <slickymaster> image testing show a considerable number of test though
[20:26] <elfy> #action Any -team member who can do an Upgrade test of some sort - appreciated - concentrate on the Upgrade rather than Upgrade(image) 
[20:26] <meetingology> ACTION: Any -team member who can do an Upgrade test of some sort - appreciated - concentrate on the Upgrade rather than Upgrade(image)
[20:27] <slickymaster> I can do it tomorroe in a VM
[20:27] <slickymaster> * tomorrow
[20:27] <jjfrv8-work> I can do my laptop tonight
[20:27] <elfy> #Action xubuntu-team to watch tracker for respins - if they appear please test what you can
[20:27] <meetingology> ACTION: xubuntu-team to watch tracker for respins - if they appear please test what you can
[20:28] <elfy> #action #xubuntu-qa to ping team in channel if they see respins appear
[20:28] <meetingology> ACTION: #xubuntu-qa to ping team in channel if they see respins appear
[20:28] <elfy> nothing else from me
[20:28] <knome> xubuntu-qa without # :P
[20:28] <knome> #nick xubuntu-qa
[20:28] <elfy> #undo
[20:28] <meetingology> Removing item from minutes: ACTION
[20:28] <elfy> #action xubuntu-qa to ping team in channel if they see respins appear
[20:28] <meetingology> ACTION: xubuntu-qa to ping team in channel if they see respins appear
[20:29] <elfy> #topic Discussion
[20:29] <pleia2> happy release week :D
[20:29] <elfy> #subtopic Xubuntu+1 support in #xubuntu
[20:29] <elfy> I've got a comment from ochosi earlier re that 
 elfy: i kinda second the xubuntu+1 support proposal
 we can say we accept that after final beta, makes sense to me
[20:30] <elfy> the thinking here from me at least is that - we're trying to improve testing and #ubuntu+1 is a bit xubuntu light
[20:31] <elfy> and if we are pushing we ought to at least give people the chance to get some help
[20:32] <dkessel> Sounds food. Better than sending people to #ubuntu+1 and having them get no support there
[20:33] <elfy> yea 
[20:33] <knome> dkessel, FOOD?
[20:33] <knome> is the traffic too high in -devel to send the people here?
[20:33] <elfy> freudian slip - or it would be if I said it 
[20:33] <slickymaster> and I'm the one eating :)
[20:33] <dkessel> good I meant. Boo, autocomplete...
[20:34] <pleia2> hehe
[20:34] <elfy> knome: <ochosi> better than getting people in the devel channel imo
[20:34] <knome> oh ;)
[20:34] <knome> dkessel, you have "food" in autocomplete?
[20:34] <slickymaster> lmao
[20:35] <elfy> but tbh I'm quite relaxed about where - just so long as it's a #xubuntu channel 
[20:35] <knome> #xubuntu+1 works, but then we should know how's going to op that channel
[20:35] <dkessel> knome: Ask the Android dictionary makers...
[20:35] <elfy> knome: oh 
[20:36] <slickymaster> I propose knome and elfy to op it
[20:36] <elfy> didn't know we had that 
[20:36] <slickymaster> and Unit193, also
[20:36] <elfy> unless we didn't ... 
[20:36] <knome> elfy, we don't, but if we set that up...
[20:36] <elfy> oh right :)
[20:37] <knome> and we'll have to see if the irc team wants to take the maintaining responsibility for that
[20:37] <elfy> mmm 
[20:37] <knome> or if it's just like -devel (more probable)
[20:37] <knome> i can take care of that with Unit193 if we decide to go ahead with that
[20:37] <elfy> so how about going with #xubuntu towards the end of the V cycle 
[20:38] <elfy> trouble with having a new channel is it's likely not to see many people who can actually help
[20:38] <elfy> probably
[20:38] <knome> well,
[20:38] <knome> that's my argument for -devel or the general ubuntu+1 channel
[20:38] <elfy> the only reason the likes of *most of us* don't in #xubuntu is because it's nto channel policy
[20:39] <elfy> which I ignore if it's something simple or quick ;)
[20:39] <knome> people who'd be helping in #xubuntu+1 is probably the same people as here or #ubuntu+1
[20:39] <elfy> holstein for instance commented 
[20:39] <knome> (and it's one more channel)
[20:39] <elfy> knome: yea possibly - but I'm more likely to notice someone saying something in #xubuntufoo
[20:40] <knome> that's true
[20:40] <knome> but -devel
[20:40] <knome> i understand it's not the ideal solution either
[20:40] <knome> maybe we should simply vote?
[20:40] <elfy> on which :)
[20:40] <elfy> or both?
[20:41] <knome> well, all options
[20:41] <knome> can be even a non-technical vote
[20:41] <knome> just say what you think is the best option
[20:41] <slickymaster> you mean vote on the ML?
[20:41] <knome> no, in irc, right now
[20:41] <elfy> I'd start here 
[20:41] <knome> let's not make it too bureaucratic
[20:41] <knome> just shout out which channel you'd like
[20:42] <knome> (no need to start a #vote even)
[20:42] <elfy> ok - I'll start then 
[20:42] <knome> sure
[20:42] <knome> i'm still thinking
[20:42]  * slickymaster waits his turn
[20:43] <elfy> vote for support in #xubuntu channel for dev version once Beta 1 is testing
[20:44] <pleia2> +1
[20:44] <jjfrv8-work> +0
[20:44]  * slickymaster votes for support in a yet to be created #xubuntu+1 channel
[20:44] <knome> #xubuntu-devel for x+1 support after beta1 is out; second favorite #x+1
[20:45] <pleia2> more channels make me meh, and people end up lurking in -devel and asking support questions once we open that up
[20:45] <knome> pleia2, that's fair, but mixing people who whine about each small feature breaking and very clueless people in #x...
[20:45] <pleia2> sounds perfect :D
[20:46] <knome> sounds like more frustration for both the supporters and people seeking help
[20:46] <knome> i can live with that
[20:46] <elfy> awesome 
[20:46] <pleia2> I worry that we'll just spend half our time redirecting people to the right channel
[20:46] <knome> but i'll tell you it'll be hard to police that "after beta 1 is out" rule
[20:46] <pleia2> apparently even -devel vs support is hard for a lot of folks ;P
[20:46] <knome> pleia2, that hasn't been a problem so far
[20:47] <elfy> so we've got half a dozen different ideas and still no further forward
[20:47] <pleia2> elfy: yeah, how's that beer?
[20:47] <elfy> cold :)
[20:47] <knome> i'd just go with elfy's suggestion if ochosi wasn't +1 on +1
[20:48] <elfy> ok - so it's now 21:47 here - executive decision is now that 
[20:48] <pleia2> we could just try out one suggestion and see how it goes
[20:48] <pleia2> thanks elfy 
[20:49] <elfy> #action Elfy to mail -devel re where we support testers
[20:49] <meetingology> ACTION: Elfy to mail -devel re where we support testers
[20:49] <knome> let's go with +1 support on #xubuntu agter beta then
[20:49] <knome> elfy, well that's different
[20:49] <knome> testers should be supported in -devel
[20:49] <elfy> good lord 
[20:49] <knome> people who just install +1 and ask a support question not :P
[20:49] <elfy> mmmm
[20:49] <knome> i'm sorry for nitpicking :P
[20:49] <elfy> that's a matter of semantics 
[20:50] <knome> but the difference is that testers are useful for us
[20:50] <elfy> someone running +1 IS testing ;)
[20:50] <ali1234> how can you tell the difference?
[20:50] <knome> then we should support them here and make them report tests.
[20:50] <knome> ali1234, see if they've submitted iso/package testing results.
[20:50] <elfy> ali1234: I guess we can see if reports are being made
[20:50] <elfy> yea 
[20:50] <ali1234> i never do that
[20:50] <knome> ali1234, shame on you.
[20:50] <knome> ali1234, you should.
[20:50] <ali1234> i don't even understand how it is useful
[20:51] <ali1234> reports go there to die
[20:51] <knome> ali1234, i'll PM you
[20:51]  * elfy will still mail the list
[20:51] <elfy> #subtopic Decide on Trello or Launchpad 
[20:51] <elfy> so
[20:52] <elfy> I've not got the energy to even go here tbh - I really don't care what we do
[20:52] <knome> i still don't mind which one we use, as long as we only use one
[20:52] <knome> i'm leaning towards launchpad because it has the real-time bug status synergy.
[20:52] <pleia2> I don't look at trello much, it's just not in my workflow :(
[20:52] <pleia2> launchpad emails me <3
[20:53] <elfy> both mail me pleia2 ;)
[20:53] <pleia2> and launchpad is open source :D
[20:53] <elfy> anyway - I'm happy to do whatever  we decide as a team
[20:54] <elfy> last cycle website was on a blueprint - from what I can see , that's not made it to anything this cycle
[20:55] <elfy> any point in doing anything like a vote with this?
[20:55] <pleia2> oops :(
[20:56] <knome> i think that and the situation with testing just reflects how much away people have been this cycle
[20:56] <elfy> I'm quite happy to just go back to using launchpad 
[20:57] <knome> anybody disagrees?
[20:57] <jjfrv8-work> nah
[20:57] <pleia2> I've been away more than normal
[20:57] <knome> same here; in comparison to the trusty cycle, much more
[20:58] <elfy> I do know that ochosi will be wanting team leads to do their own blueprints 
[20:59] <elfy> which is fair enough
[20:59] <knome> absolutely.
[20:59] <knome> they are the only ones who know what the goals for the cycle are anyway
[20:59] <elfy> yep
[20:59] <knome> and/or are laying them out
[21:00] <knome> if nobody disagrees to returning to LP, let's move on
[21:00] <knome> somebody wants to send an email to the list, or just 3info it?
[21:00] <elfy> the other 2 discussion items we've dealt with afaik
[21:00] <knome> . #info too..
[21:01] <elfy> #info return to using launchpad, team leads to set out their blueprints
[21:01] <knome> #info Trello can be used by subteams if they feel it's useful for them, but all general cooperation should go through LP
[21:01] <knome> ok, let's move on
[21:01] <elfy> #announcements
[21:02] <elfy> Release in 2 days \o/ 
[21:02] <knome> yep, and no critical bugs :)
[21:02] <elfy> anyone got any others
[21:02] <elfy> indeed :)
[21:02] <knome> good work everybody who did even a small bit
[21:02] <slickymaster> ^^^
[21:03] <elfy> #Schedule next meeting
[21:03] <elfy> ochosi is up next for that 
[21:03] <elfy> #endmeeting
[21:03] <meetingology> Meeting ended Tue Oct 21 21:03:46 2014 UTC.  
[21:03] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/xubuntu-devel/2014/xubuntu-devel.2014-10-21-20.00.moin.txt
[21:03] <elfy> I didn't want to do this in meeting 
[21:03] <pleia2> thanks elfy 
[21:04] <slickymaster> thanks elfy 
[21:04] <knome> $this ?
[21:04] <knome> and thanks :)
[21:04] <elfy> but if I feel the same way during the next cycle as I have during this one - I'll not be QA lead in the WW cycle and team can look for someone else to do it 
[21:04] <elfy> knome: that ;)
[21:05] <knome> i'll do anything to not let that happen, as much as my own schedule allows
[21:05] <elfy> well - everyone says that but I still felt that the whole cycle was a complete and utter waste of my time
[21:06] <knome> well that's probably right
[21:07] <elfy> anyway - I'll see in January or February - what I will not do though is just walk away :)
[21:07] <knome> that's appreciated :)
[21:08] <elfy> I'm not *quite* as bad as I pretend ;
[21:08] <elfy> )
[21:08] <knome> lol
[21:10] <elfy> mmm 
[21:10] <elfy> looks like everyone is getting a respin ... 
[21:10] <knome> mhm
[21:13] <elfy> sigh
[21:14] <knome> well it's not too bad, we have many tests already
[21:14] <elfy> so I did the team report etc for pleia2 last week - now I can't find where I started from 
[21:14] <knome> hm? :D
[21:14] <pleia2> oh! thanks elfy, that was on my todo list :)
[21:14] <pleia2> now I just have California to do
[21:15] <elfy> knome: yea - tbh as long as I can boot on hardware and vm and install to both I'd happily mark as release
[21:15] <knome> yep
[21:15] <elfy> pleia2: no - you have to do this week for xubuntu for me :D
[21:15] <pleia2> :)
[21:15] <elfy> knome: where did I manage to get the summary from last week :(
[21:16] <elfy> oh 
[21:16] <knome> :D
[21:16] <elfy> nvm ... 
[21:16] <knome> yeah
[21:16] <elfy> mmm 
[21:17] <elfy> no - I thought there was a template for the meeting page somewhere 
[21:20] <knome> elfy, there is, it's in the meeting logs :P
[21:20] <knome> i mean, the meeting minutes
[21:20] <knome> it should be a copy-paste
[21:21] <elfy> mmm
[21:22] <elfy> possibly done something wrong - meetings has the whole irc log
[21:22] <elfy> oic
[21:23] <elfy> silly me 
[21:23] <knome> :)
[21:24] <elfy> think that's done lol - have a look please knome :)
[21:25] <knome> yep, looks good tome
[21:25] <knome> to me too
[21:25] <elfy> coolio
[21:32] <mikodo> looks good! :)
[22:51] <gridcube_> elfy, can i have the link to the testcase?
[22:52] <elfy> gridcube_: 32 bit upgrade?
[22:52] <gridcube_> Linux gridcube-Intel-powered-classmate-PC 3.13.0-37-generic #64-Ubuntu SMP Mon Sep 22 21:30:01 UTC 2014 i686 i686 i686 GNU/Linux
[22:52] <gridcube_> thats 64bit right?
[22:52] <knome> i686 is 42-bit
[22:52] <elfy> i686 is 32 bit afaik
[22:52] <elfy> http://iso.qa.ubuntu.com/qatracker/milestones/325/builds/82112/testcases/1310/results
[22:52] <gridcube_> k, then yes, 32b
[22:52] <gridcube_> thanks
[22:53] <elfy> knome: lol 
[22:53] <knome> err, yeah, 32-bit..
[22:53] <elfy> anyway - bed for me while it's still Tuesday :)
[22:53] <elfy> night all 
[22:53] <knome> nighty elfy 
[22:54] <gridcube_> :) bye
[23:07] <gridcube_> update-manager -d -c first says that im updated and there is a 14.10 release to upgrade, but if i choose to do so the terminal show "searching for upgrades" and tehn "no upgrades found" and closes
[23:08] <gridcube_> maybe i need to change my sources to the main server
[23:09] <gridcube_> well its already there
[23:09] <gridcube_> sorry i dont know what else to do
[23:29] <gridcube_> well, that was sad :(
[23:30] <gridcube_> https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1383943
[23:31] <Unit193> knome: FWIW, I'd also vote for not yet another channel, and keeping it in #xubuntu.  Of course, #ubuntu+1 can be handy for core issues, but Xubuntu users can benefit from the help in #xubuntu even if it's not the development release.
[23:32] <gridcube_> ^ +1
[23:34] <gridcube_> should i try to do do-release-upgrade -p ?
[23:35] <gridcube_> its not the test case instruction
[23:35] <gridcube_> welp nevermind -p fails too
[23:35] <gridcube_> :/
[23:35] <gridcube_> guess thats that then
[23:36] <knome> Unit193, yeah, another channel is meh, and #ubuntu+1 is kind of another channel too..
[23:37] <knome> going to bed, nighty ->
[23:47] <mikodo> Hi. I want to try testing, "updating" tonight. Is this the procedure?  http://iso.qa.ubuntu.com/qatracker/testcases/1310/info  I will need to download "Trusty" and install it first. I think I read, we are doing the update testing on xubuntu 32-bit, right?
[23:51] <mikodo> Well, I am going to download "Trusty 32-bit" while I wait for answers. :)
[23:55] <mikodo> ... and I need to change around partitioning to make room for it.