[08:02] <flocculant> knome: so we build early in the morning now 
[09:20] <knome> :)
[12:39] <bluesabre> ochosi: indeed, clutter seems to be on its way out the door
[12:40] <bluesabre> flocculant, I'll try to look at it (thunar) tonight, on my phone, and only my desktop password manager knows my password :D
[12:50] <flocculant> bluesabre: ok :)
[12:50] <flocculant> I thought it was 1password! 
[12:54] <ochosi> password1234
[12:55] <flocculant> \o/
[12:55] <flocculant> now I know yours too :p
[12:55] <ochosi> bluesabre: i wonder what we should do in the meantime with parole... disable clutter?
[12:55] <ochosi> flocculant: ooops :)
[12:55] <flocculant> and you know mine as well :D
[14:32] <knome> flocculant, around?
[15:16] <flocculant> knome: yup
[15:18] <knome> flocculant, so... http://dev.xubuntu.org/#tab-qa
[15:18] <knome> flocculant, that's some test data, but you can see how it looks
[15:18] <knome> flocculant, also see the item in the menu
[15:19] <knome> flocculant, anything else you need there? :)
[15:25] <flocculant> knome: that's more or less what I had in mind - thanks :)
[15:25] <knome> great!
[15:25] <knome> btw...
[15:26] <knome> if you want any links to trackers or whatever to the qa status page... just poke me and i'll add them
[15:26] <flocculant> mmm
[15:26] <flocculant> have to think about that 
[15:26] <knome> sure, no hurry
[15:35] <flocculant> knome: actually - see no reason why that status page shouldn't link to iso tracker 
[15:35] <knome> yep
[15:35] <knome> let me find the right mousepad window again...
[15:35] <flocculant> lol
[15:37] <knome> done
[15:38] <flocculant> ta :)
[15:40] <flocculant> once this is dusted and mail list knows - I will disable the image test on the tracker
[15:40] <flocculant> biab
[16:21] <Unit193> LP #1576576, looking less likely.
[16:21] <Unit193> ochosi: ↑ GTK .20 looking less likely.
[16:22] <Unit193> (This is not based on my own idea of likely, read it in #u-devel.)
[16:40] <dkessel> nice, so that is the autopilot boot result on the dev tracker?
[16:41] <knome> dkessel, no
[16:42] <knome> dkessel, it's manual by the QA team
[16:44] <dkessel> oh :(
[16:45] <knome> flocculant said the autopilot boot result is useless
[16:45] <knome> :P
[17:07] <flocculant> dkessel: the autopilot thing seems to have died again 
[17:07] <flocculant> and even when it's up - most fails seem to be in the test - not the image
[17:08] <flocculant> wasn't interested in waiting for another cycle to pass by
[17:13] <flocculant> actually seems to be up 
[17:13] <flocculant> reporting fails still
[17:23] <dkessel> sure, i understand
[17:25] <flocculant> knome: possible to have update date/time on the admin page?
[17:26] <knome> maybe
[17:27] <flocculant> just thinking - fine while it's just 1 person doing it
[17:27] <knome> okay
[17:27] <flocculant> but no way for anyone to check it's updated 
[17:27] <knome> be assured, once i've figured this one thing out, things will be much nicer for everybody
[17:28] <flocculant> :)
[17:28] <knome> flocculant, there is, just see the qa status page and see if anything is "unconfirmed"
[17:28] <knome> ...but yeah, not on the admin
[17:29] <flocculant> knome: aah - so at 2am it switches to unconfirmed? 
[17:29] <knome> yep
[17:29] <flocculant> mmm - ok then I think update time would be superfluous 
[17:29] <knome> :)
[17:29] <flocculant> obviously didn't read that 2am thing properly earlier :)
[17:30] <knome> that happens
[17:31] <flocculant> what happens? 
[17:31] <flocculant> :p
[17:31] <knome> not reading properly
[17:31] <knome> and not reading at all
[17:31] <knome> and trolling
[17:31] <flocculant> :)
[17:31] <knome> (:
[19:24] <knome> !team | meeting in 5ish
[19:30] <knome> #startmeeting Xubuntu community meeting
[19:30] <meetingology> Meeting started Mon May  2 19:30:08 2016 UTC.  The chair is knome. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[19:30] <meetingology> Available commands: action commands idea info link nick
[19:30] <knome> who's around today?
[19:30] <akxwi-dave> aye
[19:30] <knome> hello akxwi-dave :)
[19:30] <flocculant> I'm around 
[19:30] <flocculant> tuit
[19:31] <dkessel> hey there o/
[19:31] <knome> Unit193 is not around, i take it
[19:31] <Unit193> Certainly not, nope.
[19:31] <flocculant> phew
[19:31] <knome> what about ochosi?
[19:31]  * knome shrugs
[19:31] <knome> #topic Open action items
[19:31] <knome> none
[19:31] <knome> #topic Updates and Announcements
[19:31] <knome> #subtopic Milestone participation (flocculant)
[19:32] <flocculant> we're only participating in Final Beta this cycle
[19:32] <knome> ack
[19:32] <knome> #info Xubuntu will only do Final Beta for 16.10
[19:32] <knome> anybody have anything on that?
[19:32] <knome> no?
[19:32] <knome> moving on.
[19:32] <knome> #topic Discussion
[19:33] <knome> #subtopic Raspberry Pi images in 16.10 (dkessel)
[19:33] <knome> dkessel, you're up!
[19:33] <dkessel> wow, that's fast.
[19:33] <knome> that happens... :)
[19:33] <nairwolf> I'm here
[19:33] <AuroraAvenue> o/
[19:33] <dkessel> well i want to propose testing the raspi images this cycle
[19:33] <knome> hello nairwolf, AuroraAvenue 
[19:34] <knome> dkessel, they are already being built, i assume so ;)
[19:34] <knome> (well i know they are...)
[19:34] <dkessel> sure
[19:34] <flocculant> who's going to do this testing? 
[19:34] <knome> i would suggest the following:
[19:35] <knome> let's create unofficial testcases for them for 16.10 in the iso tracker -- obviously leading to an unofficial, community-driven project at most
[19:35] <knome> if we seem to get a lot of interest and testing, then we can re-evaluate whether we want to make it official for 17.04
[19:35] <flocculant> hang on
[19:36] <knome> yes
[19:36] <flocculant> I still want to know who's going to do this testing ... 
[19:36] <dkessel> well i have a pi and i can test.
[19:36] <knome> i would imagine dkessel at least
[19:36] <dkessel> flocculant: want a pi? ;)
[19:36] <knome> the rest - we/i don't know
[19:36] <flocculant> dkessel: no thanks - I have enough on my plate as it is ;)
[19:37] <knome> if only dkessel tests them, then we can say "ok, at least we tried" and not release it even as an unofficial community project
[19:37] <nairwolf> Badly, I don't have a pi, but I have an Odroid from hardkernel
[19:37] <akxwi-dave> i have a pi as well
[19:37] <flocculant> frankly I'm more interested in us getting Core and testing that
[19:37] <knome> since the building of the images is done already, we don't get any more workload from that
[19:37] <dkessel> nairwolf: if you want a pi - no problem :)
[19:38] <knome> flocculant, same here, but otoh, since this comes from team, and there are people who are willing/volunteering to test it...
[19:38] <flocculant> mmm
[19:38] <flocculant> nothing to stop us adding something to the tracker - same was a the community core thing
[19:38] <knome> we just communicate it's unofficial and least priority ATM
[19:39] <knome> flocculant, indeed - and it's pretty fast to do that, especially if they can use the same testcases
[19:39] <flocculant> I'm not willing to put much QA towards it - hard enough to do what we need to do 
[19:39] <nairwolf> dkessel: I should be able to find one. 
[19:39] <flocculant> assuming lts+1 cycle follows normal behaviour
[19:39] <knome> we probably should do a quick round on the mailing list about this as well
[19:40] <knome> dkessel, want to send some kind of an email with a plan how we would go forward with this to the -devel mailing list?
[19:40] <flocculant> personally I'm still the same as I was last time this was brought up - but let's see what we get from the rest of team
[19:40] <knome> dkessel, if you want, i can help you write that
[19:41] <dkessel> knome: i can make a draft and check that with you before sending
[19:41] <nairwolf> dkessel: Are you using a Pi with Xubuntu actually ?
[19:41] <knome> ok, great
[19:41] <knome> #action dkessel to draft a mail about pi image testing for 16.10, knome to review
[19:41] <meetingology> ACTION: dkessel to draft a mail about pi image testing for 16.10, knome to review
[19:41] <knome> #link https://ubuntu-pi-flavour-maker.org/
[19:42] <knome> note that xubuntu is already on that list with "no" on "community support"
[19:42] <knome> anything else on this subject?
[19:43] <knome> ok, moving on
[19:43] <knome> #topic New Project Lead (ochosi/knome)
[19:44] <knome> since we don't have ochosi around, let's not start the process quite yet, but feel free to discuss!
[19:44] <knome> (mostly team i guess...)
[19:45] <knome> nothing? ok, let's continue via email
[19:45] <knome> #topic Schedule next meeting
[19:45] <Unit193> I'm pretty certain everyone is fine with the council idea.
[19:45] <knome> it's ochosi's turn! lucky winner!
[19:45] <knome> #action ochosi to schedule next meeting
[19:45] <meetingology> ACTION: ochosi to schedule next meeting
[19:46] <knome> pleia2, want to say something to get your name on the nicks list?
[19:46] <pleia2> I'll follow up in email re leader/council ;)
[19:46] <knome> hooray!
[19:46] <knome> #endmeeting
[19:46] <meetingology> Meeting ended Mon May  2 19:46:22 2016 UTC.  
[19:46] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/xubuntu-devel/2016/xubuntu-devel.2016-05-02-19.30.moin.txt
[19:46] <knome> thanks everybody
[19:46] <knome> fast meeting today :P
[19:46] <flocculant> thanks knome 
[19:46] <knome> np as always
[19:46] <knome> comes from the spine already
[19:46] <flocculant> :)
[19:47] <nairwolf> Really fast meeting ^^
[19:47] <knome> and minutes are up
[19:47] <knome> and hooray, i said more lines than the rest combined
[19:47] <knome> way to go me
[19:48] <flocculant> :)
[19:48] <Unit193> Would the meeting chair go to the council or stick with project leads?  I think I said before, but could talk to kcouncil and see if they have any input too.
[19:48] <knome> imo, the meeting chair could stay with team leaders
[19:48] <flocculant> I think we should carry on as we already do
[19:48] <knome> it spreads the work more evenly
[19:49] <knome> which is always a good idea
[19:49] <knome> i don't want the council to be another one of those "i don't want to apply because it means $toomuchwork"
[19:49] <knome> because there definitely are such
[19:49] <flocculant> mmm
[19:50] <Unit193> Have to make sure and keep the members responsive too.
[19:50] <flocculant> yes
[19:51] <flocculant> that said - it'd be nice to see team responsive to mails for team too ;)
[19:51] <akxwi-dave> just map me xpl and i';ll get you lot to do the work  :-)
[19:51] <flocculant> ha ha 
[19:52] <Unit193> I think generally people are responsive to emails.
[19:52] <knome> yes
[19:53] <knome> except a few people, who probably shouldn't be on the team *cough*
[19:53] <AuroraAvenue> that's me :)
[19:53] <knome> AuroraAvenue, you aren't on the team :P
[19:53] <knome> so we can't kick you out either!
[19:53]  * AuroraAvenue thinks the same still applies.
[19:54] <AuroraAvenue> bye o/ 'kick me'
[19:56] <Unit193> Could ping the two, see if they're still alive and if they actually want to stick on and plan to do anything.
[19:56] <akxwi-dave> :-)
[19:56]  * flocculant wonders which two 
[19:57] <Unit193> Jackson, Mica.
[19:57] <knome> yes
[19:57] <flocculant> just wondering if the same two :)
[19:57] <Unit193> Also maybe that Pasi guy, he's been in there a loooong time.
[19:58] <flocculant> and he's bad man as well 
[19:58] <knome> yes indeed
[20:07] <nairwolf> akxwi-dave
[20:08] <nairwolf> oups
[20:15] <ochosi> evening everyone
[20:15] <ochosi> sorry for arriving late :(
[20:15] <ochosi> just came home
[20:15] <ochosi> Unit193: when do i read that in  u-devel?
[20:17] <nairwolf> hi ochosi ;)
[20:18] <nairwolf> you want this ? http://ubottu.com/meetingology/logs/xubuntu-devel/2016/xubuntu-devel.2016-05-02-19.30.moin.txt ?
[20:18] <ochosi> hi nairwolf 
[20:18] <ochosi> i meanwhile skimmed the backlog
[20:18] <ochosi> so it's fine ;)
[20:18] <ochosi> but thanks
[20:19] <Unit193> ochosi: In this handy paste I doctored, I mean provided: https://paste.unit193.net/?dfe0377c27ee7099#NakKAUt8N6u/hvgkv9UyYmroc9iUAroh7nawAsb9Wkg=
[20:20] <nairwolf> I'm just doing a daily testing on real hardware. 
[20:20] <nairwolf> Have you ever seen this message "ubi-console-setup crashed" ? 
[20:21] <nairwolf> ubi-console-setup failed with exit code 1. Further information may be found in /var/log/syslog. Do you want to try running this step again before continuing ? If you do not, your installation may fail entirely or may be broken
[20:21] <nairwolf> I've chosen the option "erase disk and install"
[20:23] <nairwolf> Oh, it's this bug : https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1577540
[20:24] <nairwolf> How can I have access to /var/log/syslog if I'm just starting a new installation. Where is syslog in this case ? 
[20:24] <nairwolf> In the old OS installed ? 
[21:35] <nairwolf> good night