17:00 #startmeeting Xubuntu community meeting 17:00 Meeting started Wed Feb 25 17:00:59 2015 UTC. The chair is knome. Information about MeetBot at http://wiki.ubuntu.com/meetingology. 17:00 17:00 Available commands: action commands idea info link nick 17:01 who's here for the meeting? 17:01 * GridCube is here as a listener today 17:02 be about make a cup of tea time - just got in 17:02 GridCube, non-team members can talk just as well :P 17:02 i know :P but i'll probably have nothing to say 17:02 this is the first meeting i can join in years 17:02 #topic Open action items 17:02 Unit193 to tie up with elfy for xubuntu-core upgrade testing needs 17:02 did that happen? 17:03 no 17:03 #action Unit193 to tie up with elfy for xubuntu-core upgrade testing needs 17:03 * meetingology Unit193 to tie up with elfy for xubuntu-core upgrade testing needs 17:03 rests seems done 17:03 #topic Team updates 17:03 #info The new website theme (with fixes) is live!!! 17:04 I have loads 17:04 just pour them in :) 17:05 right - I'm here now 17:05 though loads is probably 3 or 4 :p 17:06 haha 17:06 #info Trusty testing - once we had a testable image - went well - 94 reported results for that 17:06 \o/ 17:07 knome: Colour scheme of website is good but not sure about the shade of green 17:07 #info First count for QA incentive will be done by Sunday for ochosi to approve 17:07 PaulW2U, we're in the middle of a meeting, can you give the feedback after this, thanks 17:07 #info vivid beta testing is not going too well with the known issue, release team need to make a decision 17:08 elfy, can you summarize where it happens? 17:08 #action xubuntu-release to discuss state of vivid beta and release position 17:08 * meetingology xubuntu-release to discuss state of vivid beta and release position 17:08 knome: yes - any of the install options appear to cause various issues 17:09 ouch.. 17:09 xubuntu-specific only or general? 17:09 I need to check the live session install options - they *appear* ok 17:09 xubuntu-specific it seems 17:09 hmpf 17:10 my opinion, not that i'm in the release team or the team lead, is that it would be important to get beta out for exploratory testing (people are interested in betas) 17:10 of course while that specific info is just one line - it's a big one :p 17:10 if we can only make the system to install more or less cleanly.. 17:10 ftr, ^^^ that's bug 1425047 17:10 bug 1425047 in ubiquity (Ubuntu) "Install (manual partitioning) in Xubuntu Desktop i386 for Vivid Daily doesn't finish installation" [High,Incomplete] https://launchpad.net/bugs/1425047 17:11 slickymasterWork: it's not just that I'm afraid :) 17:11 great, here I was thinking it was just sinply that :P 17:11 kvm - don't even see the screen to install from :) 17:11 apparently there could be a trivial fix to that 17:11 but not landing before the beta 17:12 elfy, or did you test that already? 17:12 not seen anything about fix 17:12 test what? 17:12 aha 17:12 bluesabre sent you a line to turn off tiling 17:12 oh if you mean bluesabre's xfconf-query -c xfwm4 -p /general/tile_on_move -s false 17:12 he also said something about running with utopic ubiquity to debug it 17:12 yes 17:12 that 17:13 my result of that is [13:21] bluesabre: ok - made no difference 17:13 right :( 17:13 well, let's hope we can fix it ASAP 17:13 anything else for the team updates? 17:13 but all is not lost - it IS installable 17:13 yep :) 17:13 just not from all options easily 17:14 yeah.. 17:14 maybe we should send a mail to the ML informing about known working installation options 17:14 hardware testing for all install options from livesession is not something that I can do 17:14 dkessel: they'd be on the release note 17:14 elfy, what can't you? 17:15 all that I CAN do is manual 17:15 oh ok 17:16 well i don't think that makes much difference if the problems are related to window positioning though 17:16 but what do i know... :) 17:16 basically all of the dialogues are off screen 17:16 yep 17:16 since it's likely that's an xfwm bug, it shouldn't stop one from installing 17:16 you can grab them - make sure has focus then alt+space+m then you can select move and grab it 17:16 if you can get the windows to be visible, that is 17:17 yep 17:17 yep - I just need time to work through all the options I can do - vm's and hardware 17:17 let's follow up on this when bluesabre gets back :) 17:17 any other team updates? 17:17 slickymasterWork? 17:18 ups sorry 17:18 no closed from my side 17:18 s/no/nothing 17:18 #done pleia2 published a "Xubuntu at..." blog post 17:18 ok, moving on 17:18 working on a bunch of things, still 17:18 #topic Announcements 17:18 #info Xfce 4.12 is to be released next weekend 17:19 #info Team has got an ACK for a FFe for 4.12 uploads, will be uploaded once everything has settled 17:19 any other announcements? 17:21 #info Next freezes: UIFreeze March 12, DocStringFreeze March 19 17:21 not that I'm aware of 17:22 #topic Discussion 17:22 i believe the core upgrade issue should be solved now 17:22 #subtopic ISO target size 17:22 anybody have comments on this? 17:22 yes 17:22 https://lists.ubuntu.com/archives/xubuntu-devel/2015-February/010606.html 17:23 go ahead :) 17:23 my position is (and isn't likely to change) that we shouldn't constrain ourselves by the 1Gb limit - however that doesn't equate to woohoo - we've got 2 Gb - fill that space up 17:24 yep 17:24 we should bear in mind people that might have bandwidth issues 17:24 this is what i thought when i wrote: 17:24 My suggestion on the meeting was that if we go over 1GB, our new target 17:24 should be "below or as close to 1GB as possible, but 2GB at maximum". 17:24 i think we just need a team vote on this 17:24 yep 17:24 that's also my position, as I already said in the ML 17:25 #action knome to follow up with ochosi on setting up a team vote - or allowing more time for discussion 17:25 * meetingology knome to follow up with ochosi on setting up a team vote - or allowing more time for discussion 17:25 as i said in the ML i think we should not limit to a size, but neither go adding stuff for the sake of it, just try to remain the smaller posible without feeling constrained 17:25 GridCube: that I think is more or less what everyone is saying 17:25 mmhm 17:25 the technical limitation is "required" in order to the trackers to be able to notice when we've gone over a specified limit 17:26 but yeah, i don't think 2GB is really a problem, even if we decided to go ahead with the office stack change 17:26 Unit193's figures for that were like 1.1GB... 17:26 hello, sorry for my delay :-/ 17:26 knome: yea 17:26 #nick Unit193 17:26 (needed that for the action item) 17:27 and on THAT note we need to try tie those other discussion into agenda 17:27 but then again 1.2GB target makes no sense, there is no 1.2GB hardware :D 17:27 you can action me to do both of those 17:27 elfy, the other things that are already on the agenda? :D 17:28 i think it's next to useless to try to discuss them today since we are few-numbered 17:28 knome: yea - so limit should be 2 - that doesn't mean that [team] is going to +1 filling it up 17:28 yep 17:28 knome: there is also the game issue 17:28 right 17:28 #action elfy to add the "game issue" into the meeting agenda 17:28 * meetingology elfy to add the "game issue" into the meeting agenda 17:28 happy? 17:28 :) 17:28 I'd not say that :p 17:28 #undo 17:28 Removing item from minutes: ACTION 17:29 #chair elfy 17:29 Current chairs: elfy knome 17:29 LOL 17:29 * elfy elfy to add the "game issue" into the meeting agenda 17:29 I meant I'd not say I was happy :D 17:29 :D 17:29 lol 17:29 #action elfy to add the "game issue" into the meeting agenda 17:29 * meetingology elfy to add the "game issue" into the meeting agenda 17:29 #subtopic Any other discussion 17:29 oh silly me - forgot the # 17:30 anything else? 17:30 too bad PaulW2U got scared and left... 17:30 nothing from me 17:31 slickymasterWork, want to bring up something? 17:31 nopes, nothing at the moment 17:31 #topic Schedule next meeting 17:31 ochosi for that I think 17:31 #info ochosi schedules the next meeting (XPL duty) 17:32 yep 17:32 #endmeeting