[00:03] <Unit193> There you go, you have mail.
[00:04] <ochosi> ty :)
[00:06] <ochosi> sergio-br2: hey, i think we should pull in the new system-software-update and the new ubiquity icon
[00:06] <ochosi> sergio-br2: obviously there are still a few sizes missing for either...
[00:20] <ochosi> Unit193: it sounds ridiculous, but it could be that we also need to add shimmer-themes
[00:20] <ochosi> or we need to fix something in xubuntu-default-settings
[00:21] <ochosi> https://bugs.launchpad.net/ubuntu/+source/xfce4-settings/+bug/1322305
[00:21] <ochosi> i would actually prefer to fix that somehow other than adding shimmer-themes as a depends
[00:22] <Unit193> ochosi: https://sigma.unit193.net/xubuntu.utopic/core-d.html#_other xubuntu-artwork deps on shimmer-themes, I made sure they were installed.
[00:22] <Unit193> I also quite agree that xfce4-session shouldn't have that as a dep.
[00:25] <ochosi> -session? you mean -settings?
[00:25] <ochosi> either way, yeah, -artwork should depend on it
[00:25] <ochosi> and we should probably look into the xfce session this cycle
[00:25] <ochosi> i.e. whether it really makes sense to distinguish between the xubuntu and the xfce session
[00:25] <ochosi> wanna look at that too, Unit193 ^ ?
[00:26] <ochosi> since you're already dealing with a similar problem-set with -core
[00:27] <Unit193> ochosi: Unless you want to lose the Xubuntu panel, power manager settings, themes, and stuff, you want to keep the Xubuntu session.
[00:29] <ochosi> no, i mean in the standard iso we have a xubuntu and an xfce session
[00:29] <ochosi> i wonder whether the xfce session really makes sense
[00:30] <ochosi> we haven't really taken very good care of it during the last cycles, frankly, i've rarely started one and when i did, it always felt somewhat "broken"
[00:31] <Unit193> The xfce session comes from upstream.
[00:32] <Unit193> xfce4-session: /usr/share/xsessions/xfce.desktop
[00:33] <ochosi> humm, right :/
[00:33] <ochosi> still, that doesn't necessarily mean we can't or should't get rid of it
[00:38] <Unit193> Hmm.  So 'tasksel' method installs indicator-application but not xfce4-indicator-plugin, thus no nm-applet.
[00:50] <ochosi> but nm-applet also has a fallback trayicon, no?
[00:50] <ochosi> so why would we need indicators in -core?
[00:51] <Unit193> It seems it 'detects' indicator-application..
[00:51] <ochosi> meh
[00:51] <ochosi> so that pulls in the whole indicator stack i presume?
[00:51] <Unit193> The ISO/--no-install-recommends is fine, so that method you still won't get indicators, but tasksel has the problem so I've got it so tasksel will also pull in the plugin, see?
[00:52] <Unit193> Meh, it's not so bad.
[00:52] <Unit193> 3 packages*
[00:57] <ochosi> how is the overall comparison of -desktop vs. -core atm in terms of size and packages?
[01:02] <Unit193> tasksel'd core is 2.3G all installed.  Seed is not bad in terms of diff (seen the link?)  Booted up my utopic Xubuntu, and it's 3.2G but I've removed abiword, gnumeric, gmusicbrowser, and others so isn't a good thing to compare to.
[01:11] <ochosi> i think it'd be nice to have a comparison in terms of iso-size, installed size and ram-usage
[01:13] <ochosi> hm, indicator-power can't go?
[01:13] <ochosi> or is it just because our default settings hide the trayicon that that's still there?
[01:13] <ochosi> (fwiw, i hope we can get rid of indicator-power with the next xfpm release...)
[01:14] <ochosi> started to look at the diff now, makes sense to me
[01:14] <Unit193> Erm, not trying to turn that into an indicator are you? :/
[01:14] <Unit193> And yeah, I can drop that one too.
[01:14] <ochosi> no, xfpm will have a panel-plugin instead of a trayicon
[01:15] <Unit193> Yey! \o/  (I like the mouseover, indicators don't get that.)
[01:15] <ochosi> imo indicator-messages should also go
[01:15] <ochosi> what would it be used by?
[01:15] <Unit193> Done and done.
[01:15] <ochosi> if pidgin and thunderbird arent
[01:16] <ochosi> datetime-plugin?
[01:16] <ochosi> that's kinda usesless too, as the panel's clock plugin does all we want/need now
[01:16] <ochosi> we don't even use it in our default panel layout anymore
[01:17] <Unit193> So basically how it works, we get two for the price of one.  We get a core barebones with --no-install-recommends, and we get a minimal one with tasksel.  I keep forgetting that the clock one is built in, click for calendar right?
[01:17] <ochosi> yup, both open a calendar on left-click
[01:17] <Unit193> So, done.
[01:18] <ochosi> ah, so -core barebones is everything in the list (including the ones in brackets), tasksel is without the ones in brackets?
[01:19] <Unit193> Reverse that.
[01:19] <ochosi> oh , right, whoopsie :)
[01:19] <ochosi> gucharmap?
[01:20] <ochosi> i also wonder if we need appfinder when we have whiskermenu in -core...
[01:20] <Unit193> Thought I'd just dropped that one..
[01:20] <Unit193> appfinder is also alt+f2, soo...
[01:20] <ochosi> maybe you did, i'm looking here: https://sigma.unit193.net/xubuntu.utopic/core.html
[01:20] <ochosi> yeah, but whisker also executes commands
[01:20] <Unit193> That's the right link.
[01:20] <ochosi> ok
[01:21] <ochosi> just saying, it's not a huge problem if we install appfinder too
[01:21] <ochosi> it's tiny
[01:21] <ochosi> libasound2-plugins does what?
[01:22] <Unit193> I'm not really sure, so I left it.
[01:22] <ochosi> i see
[01:22] <ochosi> frankly, if we're not shipping indicator-sound, we should install xfce4-mixer
[01:22] <ochosi> since we're not using pulseaudio, it should work fine, but it might pull some gstreamer stuff...
[01:23] <Unit193> barebones doesn't, minimal gets pulseaudio.
[01:23] <ochosi> humm
[01:23] <Unit193> FWIW, volumeicon is great for alsa. :P
[01:24] <ochosi> yeah, but if minimal has pulse, we need *some* mixer for it
[01:24] <ochosi> i'd really love to replace pavucontrol somehow
[01:24] <ochosi> but i fear we'll have to write the replacement ourselves..
[01:24] <ochosi> and i think it's a rather complicated thing to do
[01:25] <ochosi> (the panel plugin for pulseaudio is already kinda written, so maybe we can at some point get rid of that indicator too)
[01:25] <Unit193> So for minimal I can add pavucontrol, or even indicator-sound+pavu
[01:25] <ochosi> why screenshooter?
[01:25] <Unit193> "Some screenshot application is handy" --I don't know. :P
[01:26] <ochosi> without screenshooter, what happens when you hit the PrintScreen button?
[01:26] <Unit193> Remember, that only gets into minimal.
[01:26] <ochosi> right, true
[01:26] <Unit193> But can remove it too, no big deal.
[01:27] <Unit193> xfce4-places-plugin can go right?
[01:27] <ochosi> nah, it's kinda fine i guess
[01:27] <ochosi> yeah, we don't use that by defualt
[01:27] <ochosi> and imo it's an additional feature
[01:27] <Unit193> Yeah, it's weird and unused IMO. :P
[01:28] <ochosi> ok, i think libasound-plugins is pulled because it depends on libasound
[01:28] <ochosi> which is basically alsa support 
[01:28] <ochosi> (as far as i understand)
[01:29] <Unit193> So you end up with pavucontrol in minimal?  Without indicator?
[01:30] <ochosi> kinda okayish, although the indicator doesn't hurt if we have indicator-application anyway
[01:31] <ochosi> humm, can we get rid of plymouth for !minimal?
[01:31] <Unit193> You can't get rid of plymouth in Ubuntu.
[01:32] <ochosi> righty
[01:32] <ochosi> looks good to me then
[01:32] <ochosi> thanks for this!
[01:32] <ochosi> gotta get some sleep now
[01:34] <Unit193> ochosi: Thanks a ton for the review!  Everything's been refreshed now.
[01:34] <ochosi> awesome
[01:34] <ochosi> looking forward to this in .10
[01:34] <ochosi> this should be our answer to all the "install libreoffice" requests from then on :p
[01:38] <Unit193> Well huh, less depends on plymouth than it used to, but you still lose some core things. :P
[03:26] <Unit193> Erm, zenity is worse than I thought.  (Also, core and minimal ISOs up.)
[09:53] <brainwash> elfy: just read the forums thread about pkexec, maybe we could provide 1 policy for a general wrapper which could be used like gksudo
[09:54] <brainwash> for 14.10
[09:55] <brainwash> if this idea does not cause any negative side effects
[10:03] <knome> not being able to distinguish what needs the permission?
[10:04] <knome> also, wouldn't it pretty much defeat the purpose?
[10:07] <brainwash> which purpose?
[10:07] <brainwash> to see in the password window which app really needs the permissions?
[10:12] <elfy> brainwash: I've been mulling that business over
[10:15] <elfy> closest I've got is to doing one for those that we decide - mousepad/thunar - things that a *normalish* user might find they need
[10:16] <elfy> or - seed gksu :)
[15:26] <drc> pleia2: http://www.dedoimedo.com/computers/xubuntu-trusty.html  Here, as requested.
[15:36] <brainwash> your review?
[15:37] <drc> no. dedoimedo's
[15:37] <brainwash> ok
[15:39] <drc> a while back she requested news stuff to be mentioned here, as she will read the backlogs here :)
[15:40]  * drc is assuming that she has not been "shot while trying to escape in the latest coup" :)
[15:54] <drc> Sorry...how come everything sounds funnier in your head than it does coming out of your mouth (or fingers)?
[15:55] <drc> I meant to say "assuming she still has the responsibility for such things."
[16:29] <Unit193> elfy: Yes, I like that idea.  Lets seed gksu.
[17:45]  * pleia2 adds dedoimedo link to press page and resumes day off
[18:41] <elfy> ty pleia2 - I guess I could have done that - I forget I've the key too
[18:53] <Unit193> ali1234: Hello.  Have you noticed it xfwm git master whenever you alt+tab you get 'xfwm4-Message: (nil)' in the terminal output (or .cache/upstart/startxfce4.log)?
[18:54] <ali1234> no i haven't noticed that
[18:54] <ali1234> i do not use alt-tab
[18:57] <ochosi> bluesabre: so far no negative reports on the xfpm/lls patch. i suggest you go ahead and push that towards utopic so we can SRU it back to trusty
[18:58] <bluesabre> yeah, I'll be sure to do that today
[18:58] <bluesabre> got a few things going on, looking at getting a new car/place to live
[18:58] <bluesabre> :)
[18:59] <bluesabre> also, glade-gtk2 is oficially unusable in 14.04
[18:59] <bluesabre> *as far as I am concerned
[19:01] <ochosi> oh wow
[19:01] <Unit193> ali1234: OK, only asked since you've done the most with xfwm so know it better.  Thanks.
[19:01] <ochosi> yeah, same here, glade-gtk2 is totally messed up
[19:02] <ochosi> bluesabre: i'll try to work on the devices tab a bit tonight so i can hopefully get you that screenshot i promised yesterday
[19:02] <bluesabre> oh good, wasn't going to say anything about that
[19:02] <bluesabre> :D
[19:02] <ochosi> heh
[19:02] <ochosi> well the devices tab still needs tweaks tweaks tweaks
[19:02] <ochosi> mostly packing though
[19:03] <bluesabre> s/tweak/hack/g
[19:03] <elfy> bluesabre ochosi bug 1322384
[19:03]  * bluesabre hides
[19:03] <ochosi> fwiw, i think all patches we're carrying in xubuntu are in xfpm master now
[19:03] <elfy> linked it 
[19:03] <bluesabre> elfy, I'll take a look at it
[19:03] <ochosi> elfy: i guess bluesabre screwed that up when he fixed the dvd support ;)
[19:03] <bluesabre> gotta find an audio cd
[19:03] <bluesabre> or burn one
[19:03] <elfy> lol
[19:03] <ochosi> hehe
[19:05] <ochosi> bluesabre: i don't remember right now, did we wanna work on something specific this weekend?
[19:05] <Unit193> ochosi: That's great, does that bother the BSD folks? :P
[19:05] <ochosi> Unit193: no, as eric made suspend without systemd work again
[19:05] <Unit193> Nice.
[19:06] <bluesabre> ochosi: nothing specific, got some hacking going on and need to get releases to utopic/trusty
[19:06] <ochosi> so the next xfpm release will be quite a treat i think
[19:06] <ochosi> bluesabre: yeah, and we need to get you upload rights...
[19:06] <bluesabre> yeah, need to get to that
[19:06] <bluesabre> and need to apply for tech lead
[19:06] <ochosi> yup, not so many days left ;)
[19:07] <ochosi> even though there hasnt exactly been a flood of applicants :p
[19:07] <bluesabre> surprisingly
[19:07] <bluesabre> :D
[19:07] <ochosi> hehe
[19:08] <elfy> did mine get lost? 
[19:08] <elfy> :p
[19:08] <ochosi> huhu
[19:08] <ochosi> elfy: re-send please ;)
[19:08] <Unit193> micahg has been offline entirely a week, should we be worried?
[19:08] <elfy> only had one stamp ochosi 
[19:08] <Unit193> elfy: I got it for you, let me send it in. ;)
[19:09] <ochosi> Unit193: he told me he got promoted @work, so i guess he'll be busier than before
[19:09] <bluesabre> also, thanks for the monday mtg ochosi, I should be able to make it (holiday in the states)
[19:09] <Unit193> Yey!  And boo.
[19:10] <elfy> I read that in channel somewhere I'm sure
[19:10] <ochosi> bluesabre: cool
[19:10] <Unit193> I think I did too, elfy.
[19:10] <ochosi> i guess cycling meeting-times isn't such a bad thing then
[19:11] <elfy> lol
[19:12] <ochosi> bluesabre: we still have a few greeter branches to review btw
[19:13] <bluesabre> yeah, I know
[19:13] <ochosi> oh, and my parole branch :p
[19:29] <bluesabre> hey elfy
[19:29] <bluesabre> can you add my to the trello board?
[19:29] <bluesabre> "seandavis5"
[19:30] <elfy> bluesabre: done :)
[19:30] <bluesabre> thanks!
[19:30] <elfy> welcome ;)
[19:32] <bluesabre> ochosi, elfy, are we interested in tracking development on there as well?  Should it have a label, or go with community/new features?
[19:33] <elfy> ran out of labels - and given that there appeared to be an enormous interest I didn't worry too much :)
[19:34] <elfy> if you think that it'll help to track development I'm all for it 
[19:34] <bluesabre> yay, now I'm @bluesabre on there
[19:34] <Unit193> elfy: Anything you'd like me to put on there or update?
[19:34] <elfy> ochosi is an admin on there - I guess that any leads can be too 
[19:34] <elfy> then they can add boards - not sure a 'user' can do that 
[19:35] <elfy> Unit193: just use common sense - if you think it should be there - put it on - certainly for any QA stuff go ahead
[19:35] <elfy> bluesabre: try and add a board
[19:36] <elfy> list 
[19:36] <bluesabre> elfy, added a "Dev 14.04" list
[19:37] <ochosi> so we keep an overview per team?
[19:37] <ochosi> and the team updates the blueprints so the XPL and everyone else have the grand total overview?
[19:38] <Unit193> elfy: OK, I didn't think I had anything, but trying to do the "Annoy elfy as little as possible." task.
[19:39] <elfy> ochosi: that's was how I'd initially set it up
[19:39] <bluesabre> I think this will work well
[19:40] <elfy> ochosi: but then you wanted my QA stuff there - and I'm greedy and have a bunch 
[19:40] <elfy> bluesabre: well I did too :)
[19:40] <ochosi> elfy: yeah, then let's go back to that, a huge overview board doesn't make any sense
[19:40] <ochosi> unless you can conditionally show/hide stuff
[19:40] <elfy> you can filter labels 
[19:41] <ochosi> right
[19:42] <elfy> ochosi: a general board for everything is how kubuntu do it
[19:42] <elfy> https://trello.com/b/fNxJO1Ac/14-10
[19:43] <ochosi> oh, they also use trello?
[19:43] <elfy> yea - that information is on our spec ;)
[19:43] <elfy> nice to see the XPL read that lol
[19:43] <ochosi> :)
[19:44] <elfy> personally I think if we were all to have to do/doing and done - it'll be a nightmare
[19:44] <ochosi> then let's stick with per-team management
[19:44] <ochosi> i'm fine with that, just means more power/trust to the leadas
[19:44] <ochosi> leads
[19:45] <elfy> if we are going to use it - we need to think about labels now 
[19:45] <elfy> then have one to do list, 1 doing, 1 done
[19:45] <elfy> then the 'team' can filter the label to see there stuff or any other lists they want to see
[19:46] <elfy> if you add dates to things - you can toggle the calendar sheet
[19:46] <ochosi> elfy: well you're the trello expert, i've never used it for anything serious... what would you wanna do?
[19:47] <elfy> well - knowing that at least one other person/team is interested in using it I can invest a bit more time in it 
[19:48] <Unit193> I try, and I'm trying to look at it more than last time.
[19:48] <elfy> I know that Unit193 :)
[19:49] <ochosi> well for artwork it doesnt make too much sense as i'm more or less a one-man show
[19:49] <elfy> it's not quite what I mean though :)
[19:49] <ochosi> and sergio-br2 and me are mostly using github to track issues/bugs in the icon-theme
[19:49] <ochosi> and gtk themes are also in port/bugfix mode
[19:49] <ochosi> not much else to do there
[19:49] <elfy> ochosi: yea I agree - but as XPL you'd be able to catch more detail perhaps there than on blueprints
[19:50] <ochosi> yeah, but as i'm also the artwork lead...
[19:50] <ochosi> i'm just sayin, i see the value where we're really working collaboratively
[19:50] <ochosi> so for dev/features i think it can be quite good
[19:51] <elfy> is there value in people knowing what QA plans are?
[19:52] <ochosi> well i'm not saying i want to *hide* my artwork workitems... :)
[19:52] <Unit193> ochosi: abortx in #xubuntu has something about indicator-plugin.
[19:52] <elfy> do we need a label for every team - or could art/web have one to share - as there's not going to be much in it?
[19:52] <ochosi> elfy: yeah, maybe they could
[19:53] <ochosi> Unit193: he just joined, you know more than i, i presume?
[19:53] <bluesabre> dev could drop some items into -qa
[19:53] <Unit193> "Hi, I use Xubuntu 14.04 fresh install. Indicator Plugin keeps crashing. It seems to happen because of the application menus (?) Any ideas?"
[19:53] <Unit193> There you go.
[19:54] <Unit193> ochosi: Thought you were looking to fix that?
[19:54] <elfy> ochosi: we have 7 blueprints - which more or less = teams - we have 6 labels we can use
[19:55] <ochosi> Unit193: nah, why did you think that? :) andrzejr was just asking about it, but then there seem to be some patches necessary and ... tedium
[19:55] <bluesabre> I'm finally able to get interested in 14.10 since we've started fixing the critical 14.04 bugs
[19:55] <ochosi> +1
[19:56] <elfy> ochosi: tomorrow I will move the QA stuff into the general to do/doing/done lists after I've labelled them - have a look after that and at filtering
[19:56] <ochosi> elfy: sounds good to me!
[19:56] <ochosi> can we also link to the filtered trello page?
[19:56] <ochosi> or will links always show everything
[19:57] <elfy> the link is the board 
[19:57] <elfy> I might want to see QA - you might want to see something else - so you'd filter that
[19:57] <ochosi> ok, so no way of bookmarking filters/views
[19:57] <elfy> not that I know of 
[19:58] <ochosi> ok
[19:58] <elfy> bluesabre: so perhaps don't do too much in your lists till we've come to some sort of plan 
[19:59] <bluesabre> trello has an api, we might be able to bend it to our will https://trello.com/docs/
[19:59] <ochosi> meh, we can always copypaste stuff
[19:59] <ochosi> that'd be awesome
[19:59] <ochosi> hooking it up to launchpad
[19:59] <bluesabre> but I'll investigate that myself when I have time
[19:59] <bluesabre> or if anybody else is interested ;)
[19:59] <elfy> if we did that I would guess 6 boards - 14.04.1 todo/doing/done and the same for 14.10
[19:59] <ochosi> maybe knome, pleia2 or someone else from the web side of the force
[20:00] <elfy> obviously uses a cookie - if I go and come back it's filtered to how I left it
[20:00] <ochosi> i suggest that bluesabre still drops in all his stuff for dev, we can always juggle stuff around and it's not sooo much time that's lost with that
[20:01] <ochosi> elfy: so we send ppl cookies instead of hyperlinks, problem solved!
[20:01] <bluesabre> +1
[20:01] <bluesabre> send me two cookies
[20:01] <bluesabre> also, trello irc bot https://github.com/oisin/trellobo
[20:01] <elfy> so - new features and dev share a label?
[20:02] <elfy> bluesabre ochosi ^^
[20:02] <elfy> do we need a community label?
[20:02] <ochosi> +1
[20:02] <bluesabre> +1
[20:02] <elfy> roadmap?
[20:02] <ochosi> no idea what goes in the community blueprint, aren't  *we* the community? ---p
[20:02] <bluesabre> community = social media?
[20:02] <elfy> :)
[20:02] <bluesabre> or
[20:02] <elfy> I'd call that web
[20:03] <bluesabre> mm
[20:04] <elfy> bluesabre: I built this up against blueprints - so community was the increase devs type stuff last time
[20:05] <bluesabre> ah
[20:05] <elfy> I'd say that QA/Doc/Dev& New Features will be the most full 
[20:05] <bluesabre> that makes sense
[20:05] <elfy> art/website share one
[20:06] <elfy> there is one for roadmap - does that really need one - that's an overacrhing thing - trello would be more detail, so perhaps roadmap can just stay as blueprint only
[20:06] <bluesabre> yeah, roadmap and community I think would be fine as just blueprints
[20:06] <bluesabre> not much active tracking needed there
[20:06] <elfy> so we can split dev and new features 
[20:07] <elfy> if that is of use to us
[20:07] <elfy> oh 
[20:07] <elfy> so if we kept the read for "DON'T LOSE TRACK HERE" type thing for everyone
[20:07] <ochosi> i gotta run off for 1hr or so, i'll be back then though
[20:08] <elfy> so I could use green for qa - and green and red for urgent QA 
[20:08] <elfy> dev could use blue and blue/red
[20:08] <elfy> I'll fiddle 
[20:08] <bluesabre> :)
[20:08] <bluesabre> your patience is unmatched
[20:09] <elfy> bluesabre: would it better to have dev and new feature seperate?
[20:09] <bluesabre> I think so, they're related but not quite the same
[20:10] <elfy> bluesabre: you still on there atm?
[20:10] <bluesabre> yes
[20:11] <elfy> if you are add a random card to one of the dev boards - then you can add a label - the list will tell you which to use 
[20:12] <bluesabre> cool, looks good
[20:12] <elfy> ok - so now in the sidebar - filter cards - just choose 'your' colour 
[20:13] <elfy> then you'll just see those 
[20:13] <elfy> if it helps to see what dates QA have include green
[20:13] <elfy> then if everyone wanted to see 'urgent' - filter red :)
[20:14] <bluesabre> excellent
[20:14] <elfy> once things are set up - you can click the calendar at the top and everything is there 
[20:14] <bluesabre> :)
[20:15] <elfy> what *I'm* wanting to do is try and make it as easy and logical now - so I don't end up fiddling later on lol
[20:15] <bluesabre> yeah, just let me know if I need to switch gears with the dev-related stuff
[20:15] <Unit193> bluesabre: Sadly I found no terminal client.
[20:16] <elfy> bluesabre: now for SRU stuff - would that be date sensitive? eg - got to be done by such a day? 
[20:16] <bluesabre> Unit193: for trello? :)
[20:16] <elfy> you can put those in - they have to have dates to show on calendar 
[20:16] <bluesabre> elfy: perhaps by 14.04.1
[20:17] <elfy> so if all my stuff that is date sensitive is there - you could filter and see exactly when I'm doing something - then you know *when* you can easily fit something in :)
[20:17] <bluesabre> heh
[20:18] <bluesabre> does 14.04.1 have any freeze dates, or is that something that will come up closer to release?
[20:18] <elfy> bluesabre: I would imagine so - but the schedule is STILL draft and 14.04.1 isn't even on it :(
[20:20] <bluesabre> I set the date for two weekends pre-.1
[20:20] <bluesabre> so that should be 
[20:20] <bluesabre> particularly since I should have it done this weekend
[20:20] <bluesabre> or at least moving forward 
[20:20] <elfy> bluesabre: now look ath the calendar for July and you can see that there's call for package testing the week prior - so you know I'm not planning anything for just prior to that
[20:22] <bluesabre> cool
[20:22] <bluesabre> yeah, this should help with coordinating team efforts
[20:22] <elfy> is that making sense?
[20:22] <bluesabre> yeah
[20:23] <elfy> cool - I'll do some work on that later tonight - so the dev stuff will end up moving into general boards - make sure they've got labels :)
[20:23] <bluesabre> done
[20:23] <bluesabre> thanks elfy!
[20:23] <elfy> I'll do 3 for 14.04.1, 3 for 14.10 
[20:24] <elfy> and leave the notes thing 
[20:26] <bluesabre> good deal
[20:54] <elfy> bluesabre: done playing now :)
[21:02] <ochosi> back
[21:03] <elfy> hi 
[21:03] <ochosi> i see there are some updates in trello
[21:04] <elfy> ochosi: yep
[21:04] <elfy> I think that this will be the best way for us
[21:04] <ochosi> cool
[21:04] <elfy> 3 boards for 14.04.1 and for 14.10
[21:04] <elfy> if we keep to our label colour - we can filter 'our's stuff
[21:05] <ochosi> currently i only see 1 board
[21:05] <elfy> if we use red for urgent/important etc then everyone can filter that with 'their' colour
[21:05] <elfy> lists I meant
[21:05] <ochosi> ah right
[21:05] <elfy> sorry :)
[21:05] <ochosi> don't mess with the terminology!! :)
[21:05] <elfy> heh
[21:06] <elfy> and then finally - if we date stuff that needs a date - everyone can see that on the calendar
[21:06] <elfy> so 
[21:06] <ochosi> what calendar?
[21:06] <ochosi> trello or google?
[21:06] <elfy> trello
[21:06] <ochosi> humm, >1 calendar...
[21:07] <elfy> well if someone can sync the 2 then \o/
[21:07] <ochosi> heh
[21:07] <elfy> where was I ... 
[21:08] <elfy> so - if I use green and red (for urgent) and date where needed I can filter green and red and see my stuff
[21:09] <elfy> if you use the purple and red - I would not see the basic stuff - but anything that was red I would see as well
[21:09] <ochosi> yup
[21:09] <elfy> does that make sense ?
[21:09] <ochosi> sure
[21:09] <ochosi> so urgent stuff cannot be filtered by tetam
[21:09] <ochosi> team
[21:09] <ochosi> unless you can filter multiple colors
[21:09] <elfy> yea 
[21:09] <ochosi> with AND not OR
[21:10] <elfy> sorry meant to add that
[21:10] <elfy> so I could filter QA and say dev and know what was going on with those two 
[21:10] <elfy> which is actually what I've done :)
[21:11] <elfy> so - now it's up to people to start using it - then we can make an informed decision on it's usefulness to us as a team
[21:13] <elfy> I hope that it does work - if it makes life easier for the whole of us
[21:13] <elfy> I expect that slickymaster will make a lot of use of it - he did last cycle
[21:21] <ochosi> elfy: well i'd say let's try it and if it doesn't work we can always go back/forth during the cycle
[21:21] <elfy> yep
[21:21] <ochosi> i'm not too concerned as long as the big picture in the blueprints still works
[21:21] <elfy> yea 
[21:21] <elfy> I agree 
[21:22] <elfy> that's just going to be down to people doing it 
[21:23] <elfy> once I started using it last cycle I found it a lot easier to keep on top of things that needed to be done by a certain date
[21:24] <ochosi> yeah, i agree that from the blueprints the individual progress/state of workitems is sometimes not easy to judge
[21:24] <ochosi> but in the end it'll always be the ppl knowing/using it
[21:24] <elfy> yep
[21:24] <ochosi> bluesabre: still around?
[21:24] <bluesabre> ochosi: ish, brb
[21:24] <bluesabre> running to starbucks
[21:24] <bluesabre> :)
[21:25] <elfy> ochosi: what I am hoping for is that all of us can get a better picture of what the rest are up to 
[21:25] <elfy> which *should* make things easier - I'm guessing that it'll help those that cross-over - like dev/new features/qa
[21:25] <elfy> more than - say artwork or website
[21:26] <ochosi> yeah
[21:26] <ochosi> frankly, artwork as it is currently is wallpapers, icons and themes
[21:26] <ochosi> and those are mostly evolving slowly per cycle
[21:26] <elfy> it might be that in a month or so we could say - there doesn't seem any point in knowing when a wallpaper is changing
[21:26] <elfy> and website stuff could be all in a rush right at the end
[21:27] <ochosi> yeah, the wallpaper is probably most connected to the slideshow
[21:27] <ochosi> or the screenshots for the release
[21:27] <ochosi> but those things usually always happen at the last minute, and that's also somewhat logical
[21:28] <ochosi> website stuff, not sure, was never too involved in that
[21:28] <elfy> so slickymaster might like to see a date on there for wallpaper for instance if he's running docs
[21:29] <elfy> bluesabre might like to know when I'm planning the next call 
[21:29] <ochosi> i don't think the wallpaper is featured anywhere in the docs though
[21:29] <ochosi> no imagery is in our docs, which makes the docs so resistant :)
[21:29] <elfy> but he got involved with slideshow and I guess will again
[21:30] <ochosi> btw, can we put the filter cards in a more prominent place?
[21:30] <ochosi> they're somewhat hidden but rather essential
[21:30] <ochosi> or do you just never change the sidebar's content?
[21:31] <elfy> not sure I know what you mean
[21:31] <elfy> oh
[21:32] <elfy> hang on - click on the top 14.04.1 card
[21:32] <ochosi> yup
[21:32] <ochosi> and then?
[21:32] <elfy> then see at the top - the current dev label - the + next to it
[21:32] <elfy> you'll get the list of labels 
[21:32] <ochosi> yup, i rather thought the filtering stuff that is currently in the sidebar
[21:33] <ochosi> which was 1) hidden for me before (maybe i did that myself though) and 2) the most important view for me (filter cards) is yet another click away
[21:33] <ochosi> just wanted to say it would be nice to have that in a more obvious place
[21:33] <ochosi> although i guess the learning curve for trello isn't so bad
[21:33] <elfy> yea - not sure we can do anything with that 
[21:34] <ochosi> btw, why would you keep 14.04.1 and 14.10 in one board?
[21:34] <elfy> and once you ARE filtering - then you get a box at the top - clicking on THAT - opens the filter list
[21:34] <elfy> because it's current? 
[21:35] <elfy> we can keep the same board if we carry on - archive 14.10 - still have 14.01 ( or change title to 14.04.2) then add 15.04 to the board
[21:36] <ochosi> right
[21:36] <elfy> I think at the moment the thing is to get people to try it - if it works then carry on, then we can look at if we want to do it differently
[21:36] <ochosi> ok
[21:37] <elfy> does that make sense to you?
[21:37] <elfy> what I don't want is for us to end up with a bunch of stuff in different places while we're seeing if it works for us as a team
[21:40] <ochosi> well if it gets too confusing and we decide we have to axe trello, it'll have to be merged back to LP
[21:40] <ochosi> but it's still early in the cycle, let's try it
[21:41] <elfy> none of this is on LP though :)
[21:41] <elfy> well some is 
[21:42] <elfy> but all the different testing things here for calls is one line in LP not 15 seperate lines 
[21:44] <elfy> ochosi: one last thing if you subscribe/join a card - then everytime something happens to that card - you get an e-mail
[21:44] <ochosi> yeah, that i've already tried/known :)
[21:44] <elfy> last cycle I didn't do that 
[21:44] <elfy> ok - wasn't sure what you've done with it 
[21:45] <elfy> I've only been using it for a while myself 
[21:45] <ochosi> while we probably won't use scrum in xubuntu, this article looks interesting: http://www.civicactions.com/blog/2012/oct/10/five_tips_for_using_trello_for_scrum
[21:46] <ochosi> there is a bit of terminology that i'm unsure about still with trello
[21:46] <ochosi> checklists?
[21:46] <elfy> doing 14.10 list - the package testcases card - I've got a checklist in there
[21:47] <ochosi> it all looks very powerful (as long as ppl use it enough)
[21:47] <elfy> yea 
[21:48] <ochosi> i'm wondering though, after skimming through the article above, whether 14.04.1 and 14.10 isn't TMI
[21:48] <ochosi> depends a bit on what we wanna get into 14.04.1
[21:48] <elfy> I really don't want people to use it just because - and I wouldn't ask them to either
[21:49] <elfy> you could just have one list  for 14.04.1 
[21:49] <elfy> if it's there then we ARE doing it for 14.04.1 
[21:49] <elfy> I guess
[21:51] <elfy> perhaps have one list for 14.04.1 - when it's done just archive it 
[21:51] <ochosi> well i guess "doing"==inprogress no?
[21:51] <elfy> yea
[21:52] <ochosi> one thing i miss here is the easy way to add bugs and get their status synced
[21:52] <elfy> yep
[21:52] <ochosi> that's a nice thing in blueprints
[21:52] <elfy> yep
[21:52] <elfy> I agree 
[21:52] <ochosi> and the main reason why i guess for 14.04.1 ppl *will* have to look in two places
[21:52] <ochosi> and the -bugs blueprint will most likely also only stay in launchpad
[21:53] <elfy> I see no reason for that to be on this 
[21:53] <elfy> and would be a nightmare anyway
[21:53] <ochosi> well, other than just use one platform to rule them all
[21:53] <ochosi> not necessarily, if it's a separate board
[21:53] <elfy> except the manual syncing
[21:54] <elfy> and why look at 2 lists that say the same thing?
[21:55] <ochosi> elfy, Unit193: could you two get together and organize some feedback-testing for xubuntu-core? while i think that Unit193's seed file makes a lot of sense, it'd be nice to get some real feedback (most likely no need for specific test cases though, but just ask experienced users for feedback)
[21:55] <ochosi> elfy: yeah, obviously i'm thinking of trello doing the syncing for us :)
[21:55] <elfy> ochosi: :)
[21:55] <ochosi> if someone ever gets on this and hacks up the trello api
[21:57] <elfy> and yep - the -core thing is fine - we'll get together and sort something out soonish
[21:59] <ochosi> great, thanks!
[21:59] <Unit193> Crap, right...
[22:21] <brainwash> Unit193: did you already see bug 1309849 ?
[22:24] <Unit193> brainwash: No I hadn't.
[22:32] <brainwash> bug 1302462
[22:32] <brainwash> bug heat over 100
[22:32] <elfy> night all
[22:33] <brainwash> should be added to the bug blueprint I guess
[22:34] <ochosi> right so upgraders have leftover desktop files for indicators...
[22:34] <ochosi> yeah, feel free to
[22:36] <brainwash> and what's the deal with bug 1322305 ?
[22:37] <brainwash> I suggest dropping the xubuntu patch
[22:37]  * ochosi shrugs
[22:37] <ochosi> frankly, i've no idea why that patch was added
[22:39] <brainwash> question is, can it be fixed in 14.04?
[22:39] <brainwash> not sru worthy or?
[22:40] <Unit193> There, I'll be annoyed no more.  Put in a domain redirect.
[22:41] <ochosi> brainwash: nah, actually that's one of the reasons i wanted to discuss what we wanna do with the xfce session we're shipping
[22:42] <ochosi> making it more meaningful might be good (or dropping it)
[22:43] <brainwash> more meaningful? it's the default Xfce session
[22:43] <brainwash> it's like the little brother
[22:44] <ochosi> yeah, but we havent really looked at it and taken care of it for a few releases
[22:44] <ochosi> every time i logged into the xfce session, it felt like a messed up xubuntu session
[22:50] <brainwash> but that's the user's fault
[22:51] <brainwash> if he manages to mix default settings of both sessions
[22:52] <brainwash> personally I don't feel like a change is needed here
[22:52] <ochosi> please comment on the bugreport
[22:53] <brainwash> and suggest to drop the patch?
[22:53] <brainwash> we still don't know why it was added in the first place :D
[22:56] <brainwash>  A vanilla Xfce session will use Xfce and Rodent as default themes, but
[22:56] <brainwash>  they are not shipped anymore on our images, so replace them with existing
[22:56] <brainwash>  themes in order to provide a better experience to people choosing the
[22:56] <brainwash>  'Xfce Session' over the 'Xubuntu Session'.
[22:56] <brainwash> bug 947603
[22:57] <brainwash> ah lol
[22:58] <brainwash> so we a debian and a xubuntu patch
[23:01] <brainwash> lucky it's late already and I don't feel like bothering with this right now :)
[23:02] <ochosi> well if you can come up with a good solution, i'd appreciate it
[23:02] <ochosi> i can't look at every bugreport myself there
[23:07] <ochosi> brainwash: oh, i overlooked that this user is talking about an Ubuntu install
[23:07] <ochosi> so actually i don't care so much about this bug
[23:07] <ochosi> bug-heat -100 :)
[23:09] <brainwash> well.. ofc he wasn't talking about xubuntu :D
[23:09]  * ochosi is tired + distracted
[23:47] <ochosi> night everyone