[00:52] <bluesabre> back again
[00:52] <knome> :)
[01:01] <micahg> bluesabre: breeze recommends orion-gtk-theme
[01:01] <micahg> but kubuntu packageset shouldn't be grabbing in that scenario
[01:08] <bluesabre> breeze recommends orion-gtk-theme?  that seems odd
[01:10] <micahg> added in vivid by riddell
[01:11] <bluesabre> feels like a typo... its listed in debian breeze as well, but the package does not exist in debian
[01:11] <bluesabre> or maybe not
[01:12] <bluesabre> maybe he chose it because it happens to be a white theme?
[01:12] <micahg> idk
[01:13] <bluesabre> alrighty
[01:14] <micahg> but, I"ll see about getting the script fixed
[01:14] <bluesabre> thanks
[01:15] <bluesabre> if you want to upload it, I can give you a tarball of the package ready to upload
[01:16] <micahg> I could do that
[01:19] <bluesabre> https://copy.com/qkWTWvcHRC09gMSQ
[01:20] <bluesabre> since its a multi-source package
[01:44] <knome> off to bed, see you tomorrow
[01:48] <bluesabre> have a good night knome
[04:24] <micahg> bluesabre: is shimmer-themes not stored in a VCS?
[04:29] <micahg> bluesabre: I also realized, I'll need a signed sha1 sum file for the tarball you gave me to confirm authenticity
[06:23] <Jake2234> hi everyone
[06:33] <astraljava> Hello!
[06:34] <astraljava> Oh, gone already. =/
[07:34] <knome> good morning astraljava 
[09:59] <bluesabre> micahg: the themes are all individually on https://github.com/shimmerproject
[10:03] <bluesabre> dc8ad71119b2d5849bc670ac7fc2c10562c81e2e  shimmer-themes_2.0.0.orig-albatross.tar.gz
[10:03] <bluesabre> a0f31c8276c29f7325c0dbe371fdc69407c503d4  shimmer-themes_2.0.0.orig-bluebird.tar.gz
[10:03] <bluesabre> a01e6d35a7148fcc89191f1e8cbce256d194b8ad  shimmer-themes_2.0.0.orig-greybird.tar.gz
[10:03] <bluesabre> 4c6202ffac02c2319193eb60d99f863f9cba424e  shimmer-themes_2.0.0.orig-numix.tar.gz
[10:03] <bluesabre> ef900a5a8e6ceddae89b979dcc86db7de610f937  shimmer-themes_2.0.0.orig-orion.tar.gz
[10:03] <bluesabre> ab3311a31e796117f6c4ab8176ac1382aef100f3  shimmer-themes_2.0.0.orig.tar.gz
[10:03] <bluesabre> 838b575ca8210bc67e53eedfb9aa3bda69235cc0  shimmer-themes_2.0.0.orig-wallpapers.tar.gz
[10:04] <bluesabre> oh, signed sha1sum file
[10:05] <slickymasterWork> Unit193, everything went almost smooth with the -core installation 
[10:05] <slickymasterWork> there was a small hick up in ubiquity after setting up the partitions 
[10:06] <slickymasterWork> ubi-timezone crashed -> http://i.imgur.com/jtAta3f.jpg
[10:06] <slickymasterWork> but it installed nonetheless 
[10:07] <slickymasterWork> you you want any logs just ping mre
[10:13] <bluesabre> micahg: https://copy.com/i3CPChMUaZlNrM6o
[10:45] <astraljava> ochosi: bluesabre: bug 1303736
[10:45] <astraljava> You had played with this? I'm seeing _occasionally_ the same symptoms on vivid, except that in my case I never even see the password dialog, when this problem occurs.
[10:54] <bluesabre> astraljava: it might be related to the proprietary graphics drivers
[10:55] <bluesabre> vt switch with nvivia can take over 10 seconds
[10:55] <bluesabre> then the greeter defaults to a sleeped display
[10:55] <bluesabre> as a "screensaver"
[10:55] <bluesabre> so keep clicking and wiggling
[11:00] <bluesabre> !team | Feature Freeze in one month
[11:00] <bluesabre> https://wiki.ubuntu.com/WilyWerewolf/ReleaseSchedule
[11:11] <astraljava> bluesabre: Good to know, thanks! By the way, I need to remove the $vt_switch from my grub boot parameter list, otherwise I will not get the passphrase for LVM encryption.
[11:11] <astraljava> Is it in any way related?
[11:11] <bluesabre> astraljava: I have no idea
[11:11] <bluesabre> Unit193 might know something about that though
[11:11] <astraljava> Ok, figured as much. Nobody seems to have a clue. :D
[11:12] <astraljava> Great, now he'll probably be annoyed enough for the ping, but it wasn't me, so I'm off the hook. :D
[11:12] <astraljava> Thanks for your assistance!
[11:12] <bluesabre> np
[11:12] <bluesabre> we ping Unit193 all the time
[11:13] <bluesabre> Unit193 likes talking to us
[11:13] <bluesabre> Unit193 is almost always around
[11:13] <bluesabre> it's probably because of what we did the to other 192 Units
[11:13] <bluesabre> >:D
[11:17] <astraljava> Aaahhhahahaha!
[11:18] <astraljava> So in essence he just keeps respawning when the earlier revision explodes?
[11:18] <bluesabre> seems to be the case
[11:18] <bluesabre> this one seems more durable than the last
[11:18] <astraljava> A bit like that Tom Cruise movie.
[11:18] <bluesabre> ... mixed with Groundhog Day
[11:19] <astraljava> Yep.
[11:19] <knome> boo, this is the development channel, not #bad-jokes
[11:19] <astraljava> Probably much more like that than epic fighting with space aliens.
[11:19] <bluesabre> lol
[11:19] <bluesabre> that's okay knome, I'm done now
[11:19] <bluesabre> gotta get ready for work
[11:19] <astraljava> Oh, oops. Sorry, knome, Unit193!
[11:19] <bluesabre> hf today guys :D
[11:19] <astraljava> You too!
[11:19] <knome> you too
[15:47] <dkessel> mhh newest parole no longer freezes on startup, but on exit... :)
[16:11] <knome> !team | meeting in 20mins
[16:28] <knome> #startmeeting Xubuntu community meeting
[16:28] <meetingology> Meeting started Mon Jul 20 16:28:37 2015 UTC.  The chair is knome. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[16:28] <meetingology> Available commands: action commands idea info link nick
[16:28] <knome> who's here for the meeting?
[16:29] <jjfrv8> o/
[16:29] <knome> (let's wait for 5 or so more for people to turn up)
[16:29] <knome> hey jjfrv8 :)
[16:29] <jjfrv8> hey, knome
[16:29] <micahg_work> o/
[16:29] <knome> allö micahg_work 
[16:31] <dkessel> hellooo
[16:31] <knome> hey dkessel :)
[16:31] <slickymasterWork> sorry, being nagged by my boss :P
[16:31] <slickymasterWork> but here, now
[16:32] <knome> heh, hey slickymasterWork 
[16:32] <knome> let's start then
[16:32] <knome> not much on the agenda, so likely a short meeting
[16:32] <knome> #topic Open action items
[16:32] <slickymasterWork> yeah
[16:32] <knome> -> dkessel to investigate automated image testing 
[16:32] <knome> is that done?
[16:32] <knome> (whatever that means, seems like a huge scope)
[16:33] <dkessel> knome: well... i did what i could
[16:33] <knome> okay, so what's the current status of that?
[16:34] <dkessel> i contacted balloons, he told me that DanChapman would be working on it.
[16:34] <knome> right
[16:34] <dkessel> i then asked DanChapman about it again.... this time by mail, just yesterday. no response yet.
[16:34] <knome> let's not carry that action item on then
[16:35] <dkessel> i hope mail will cause a response...
[16:35] <knome> ultimately, it would be nice to turn that into work items in the blueprints if there is something we can benefit from and that is realistic to achieve
[16:35] <knome> thanks for taking care!
[16:35] <dkessel> i guess we can create a new item once we have some response
[16:36] <knome> yeah, and in the blueprints rather than meetings if at all appropriate, to have it actually tracked
[16:36] <knome> -> xubuntu-dev to review requirements for xubuntu-core iso, investigating patches to livecd-rootfs, ubuntu-cdimage and debian-cd
[16:36] <knome> micahg_work, do you know the status of this review?
[16:36] <knome> or is it ochosi/bluesabre/Unit193 who are working on it?
[16:36] <micahg_work> nope, but I can help, I think Unit193 was driving this
[16:36] <slickymasterWork> that eas my impression also knome 
[16:36] <slickymasterWork> s/eas/was
[16:37] <knome> i don't know much about it, so let's just carry it on and you can get on with working it later :)
[16:37] <knome> #action xubuntu-dev to review requirements for xubuntu-core iso, investigating patches to livecd-rootfs, ubuntu-cdimage and debian-cd
[16:37] <meetingology> ACTION: xubuntu-dev to review requirements for xubuntu-core iso, investigating patches to livecd-rootfs, ubuntu-cdimage and debian-cd
[16:37] <knome> #nick xubuntu-dev
[16:37] <knome> those were the only action items carried
[16:37] <knome> #topic Team updates
[16:38] <knome> #info knome worked on a PoC for a work items tracker specifically for Xubuntu
[16:38] <knome> ^ more on that under other discussions
[16:38] <slickymasterWork> nothing from -docs to report
[16:39] <knome> #info background: http://status.ubuntu.com/ubuntu-w/ was last updated on 13 July
[16:40] <micahg_work> broken cron?
[16:40] <knome> i have no further information on that
[16:41] <knome> the tracker is only used by us and some openstack people, so there's no guarantee that it will be kept running in the future
[16:41] <micahg_work> File a bug? https://bugs.launchpad.net/launchpad-work-items-tracker/
[16:42] <micahg_work> is there some new shinier tool people are using?
[16:42] <knome> the project isn't active, and it's not those people who control the instance anyway i believe, it'd be IS who could work on that
[16:42] <knome> let's move on and get back to the subject
[16:42] <knome> just a sec...
[16:42] <knome> #topic Announcements
[16:42] <knome> anything?
[16:43] <micahg_work> oh, I supposed I could've mentioned dev stuff
[16:43] <knome> #info Feature Freeze on August 20th
[16:43] <knome> yes... you could have :)
[16:43] <knome> #undo
[16:43] <meetingology> Removing item from minutes: INFO
[16:43] <knome> #undo
[16:43] <meetingology> Removing item from minutes: TOPIC
[16:43] <knome> go ahead
[16:43] <micahg_work> #info bluesabre packaged shimmer-themes 2.0.0 with the latest themes, micahg will upload soon
[16:44] <micahg_work> #info bluesabre is working to get QT apps to appear better in Xubuntu by setting environment variables appropriately
[16:45] <micahg_work> #info micahg to work on getting shimmer-themes back into the Xubuntu packageset
[16:45] <micahg_work> there's probably more, but that's what I remember at the moment
[16:45] <knome> ok
[16:45] <knome> #topic Announcements
[16:45] <knome> #info Feature Freeze on August 20th
[16:46] <knome> any other announcements?
[16:46] <micahg_work> not that I can think of
[16:46] <knome> #topic Discussion
[16:47] <knome> #subtopic Work items tracker
[16:47] <knome> so basically, the project you linked to has been inactive for a long time
[16:47] <knome> and it would be canonical IS who to contact about cron jobs not working
[16:47] <knome> but i hacked together a replacement last night already
[16:48] <knome> it doesn't do all the same things as the current one, but we should discuss what we want from the tracker at some point
[16:48] <micahg_work> well, code is public right?
[16:48] <micahg_work> we could just set up an instance
[16:48] <slickymasterWork> isn't pitti who maintains it>?
[16:49] <knome> if you are volunteering to do that and work on the improvements on the python code, then certainly
[16:49] <knome> slickymasterWork, the code, most likely not the instance
[16:49] <micahg_work> not me, but there are others on the team with enough python experience that if they so desired they could
[16:49] <knome> this has been discussed since ages, and nobody has stepped up
[16:50] <knome> which proves there isn't enough interest to do it with the current codebase
[16:51] <knome> i'm all for using existing tools... but idealism doesn't carry us too far, actions need to be taken if we want to go somewhere with it
[16:52] <knome> #action knome to follow up with team about the features the team would like to see in a status tracker, should we decide to use knome's code
[16:52] <meetingology> ACTION: knome to follow up with team about the features the team would like to see in a status tracker, should we decide to use knome's code
[16:52] <knome> any ideas/feedback on this now?
[16:53] <knome> (i'll post the PoC url for the team later)
[16:55] <knome> #subtopic Other discussions
[16:55] <knome> anything else?
[16:58] <knome> #topic Schedule next meeting
[16:58] <slickymasterWork> it's ochosi turn, I believe knome 
[16:58] <knome> ochosi is up next for XPL duties
[16:58] <knome> yep
[16:58] <knome> #endmeeting
[16:58] <meetingology> Meeting ended Mon Jul 20 16:58:42 2015 UTC.  
[16:58] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/xubuntu-devel/2015/xubuntu-devel.2015-07-20-16.28.moin.txt
[16:59] <slickymasterWork> thanks knome 
[16:59] <knome> minutes are up
[16:59] <knome> micahg_work, https://rt.ubuntu.com/Ticket/Display.html?id=26792
[17:00] <micahg_work> I'll have to look later
[17:00] <micahg_work> thanks
[17:00] <knome> well it's just a ticket saying status.ubuntu.com isn't updating
[17:00] <knome> but if you want to follow-up with it...
[17:00] <knome> or follow
[19:15] <ochosi> knome, micahg_work: i asked "the maintainers" (i don't know who it was anymore) at the beginning of the cycle about status.ubuntu, because it initially didn't even get set up for wily for a few weeks
[19:16] <ochosi> then they set it up, but reluctantly, saying it could be retired
[19:16] <ochosi> so this lack of updates is sort of in line with that, and not a huge surprise
[19:16] <micahg_work> maintainer was cjohnston IIRC
[19:20] <ochosi> right, i guess then it must've been him i talked to
[19:21] <ochosi> either way, one definitive advantage of using knome's code over the current implementation is that we can make it flexible and suit our needs, whereas general interest in status.ubuntu seemingly faded away
[19:22] <ochosi> and we can always make our code available, maybe that'll inspire interest in other teams as well (e.g. those who use trello atm)
[21:41] <bluesabre> hello all
[21:43] <knome> hey bluesabre 
[21:43] <ochosi> hey
[21:44] <ochosi> bluesabre: good timing, please try: https://github.com/shimmerproject/Greybird/commit/1745782e1928fd28fdd44530cd7b3bf6fb3283d1
[21:44] <ochosi> also, in wily, the overlay scrollbars are not disabled in all apps
[21:44] <ochosi> e.g. mousepad still has them
[21:44] <ochosi> so that env-var seems to work only with gnome apps that implement it, not gtk-wide
[21:44] <bluesabre> yeah, seemingly thats the case :(
[21:45] <ochosi> so anyway, with my patch they should be usable
[21:46] <bluesabre> checking it out now
[21:52] <ochosi> soon it's taking you longer to check out the patch than it took me to write it ;)
[21:52] <bluesabre> took a while
[21:52] <bluesabre> :D
[21:52] <bluesabre> yeah, that seems ok
[21:52] <ochosi> yeah, the tweaking took most of the time
[21:52] <ochosi> wasnt sure what look to go for
[21:53] <ochosi> i don't mind adwaita's look
[21:53] <ochosi> but then again, this one looks more like current greybird
[21:53] <bluesabre> yup
[21:53] <ochosi> so yeah, personally i wouldn't disable the overlay scrollbars
[21:53] <ochosi> especially not like we're doing it now, cause it's not working so well
[21:55] <bluesabre> if it disables any at all its more consistent with the overall desktop
[21:55] <bluesabre> but yeah, I can remove it for next themes upload
[21:56] <bluesabre> it seems like a silly feature
[21:56] <ochosi> oh right, the themes haven't been uploaded yet, right?
[21:56] <bluesabre> apps are able to declare whether to support the overlay scrollbars
[21:56] <ochosi> it's something iOS has, is all i can think of :)
[21:56] <ochosi> right, that is a bit silly
[21:56] <ochosi> either they should always work or they shouldn't
[21:57] <ochosi> maybe that option will be dropped and was only added as a compromise because some app devs didn't like the scrollbars or something
[21:57] <bluesabre> maybe
[21:58] <ochosi> either way, the patch should make those cases where users have those scrollbars a lot better
[21:58] <bluesabre> yup
[21:58] <ochosi> be they always or just seldomly or never
[21:58] <bluesabre> thanks for that
[21:58] <bluesabre> :D
[21:58] <ochosi> no problem, just had to read a bit of gtk+ git commit backlog ;)
[21:58] <ochosi> (and convert the scss to css)
[21:59] <ochosi> (and make a consistent style)
[21:59] <bluesabre> gotta love the great documentation
[21:59] <ochosi> yeah, it's all in git log!
[21:59] <ochosi> :>
[21:59] <ochosi> recently someone emailed me about making gtk themes and where to find docs for that, i guess this will be my reply
[22:00] <ochosi> a new shimmer-themes hasn't been uploaded yet, right? still out of our package-set..?
[22:00] <bluesabre> yup
[22:01] <ochosi> k
[22:04] <bluesabre> 1 month to work on new software releases now :)
[22:04] <bluesabre> going to aim for 1/week
[22:04] <bluesabre> might lower some of my loftier goals ;)
[22:05] <ochosi> heh
[22:05] <ochosi> yeah, makes sense
[22:05] <ochosi> after all, this is the "summer cycle"
[22:05] <ochosi> not the one where most of the work usually happens
[22:05] <bluesabre> :D
[22:06] <bluesabre> gotta get in a good position for LTS though
[22:06] <ochosi> yep, we better make that one cound
[22:06] <ochosi> count too
[22:07] <ochosi> some things like xfpanel-switch should really see a release so we can test it in wily
[22:07] <ochosi> and iron out in x
[22:07] <bluesabre> yeah
[22:07] <bluesabre> I might get that one out next week
[22:07] <ochosi> i mean that one is "basically ready" iirc
[22:08] <ochosi> it still has some glitches with the save/restore routine iirc
[22:08] <bluesabre> this is a short week for me (anniversary), so aiming for a bugfix menulibre release tomorrow hopefully
[22:08] <ochosi> oh congarats!
[22:08] <ochosi> !congarats | bluesabre 
[22:08] <ochosi> oh
[22:08] <ochosi> i thought ubottu knew something about congarats. or maybe it was conga-rats
[22:09] <bluesabre> !congarays-#ubuntu-devel or something like that
[22:09] <bluesabre> !congarats-#ubuntu-devel or something like that
[22:09] <bluesabre> !conga-rats-#ubuntu-devel or something like that
[22:09] <bluesabre> or nope
[22:09] <ochosi> :D
[22:09] <bluesabre> :D
[22:14] <bluesabre> ochosi: got anything you need me to look at tonight?
[22:14] <ochosi> btw, i think the UI for panel-switch could be two simple buttons in the panel config dialog
[22:14] <bluesabre> in the xfpanel dialog?
[22:15] <ochosi> like, just put a "save" and "load" button next to the "+" and "-" http://i.imgur.com/mm8S8SC.png
[22:15] <ochosi> naturally, that would only save the currently selected panel, so slightly different functionality
[22:15] <ochosi> but maybe just copying the xml would suffice there
[22:16] <ochosi> or was it still using .rcs
[22:17] <bluesabre> xml
[22:17] <bluesabre> its reading/writing xfconf
[22:17] <ochosi> i vaguely remember it being a bit hacky
[22:17] <ochosi> but it's been too long that i actually looked at the code
[22:18] <bluesabre> same here
[22:18] <ochosi> branching...
[22:19] <ochosi> hm, no module named panelconfig
[22:19] <ochosi> what did i miss there
[22:20] <bluesabre> hm
[22:20] <bluesabre> one sec
[22:22] <ochosi> (fwiw, i think xfpanel-switch is more likely to make it than that parole workitem)
[22:23] <bluesabre> yup
[22:24] <ochosi> unless ofc packagekit is as easy as they say and one of us has a spark of motivation + time
[22:25] <bluesabre> was pretty sure this worked at one point
[22:25] <bluesabre> but I think I have a fix
[22:25] <ochosi> heh
[22:26] <ochosi> "worked at some point" sounds like a nice release message
[22:28] <bluesabre> lol
[22:28] <bluesabre> pull it
[22:28] <bluesabre> ./configure; make; make install
[22:29] <ochosi> did that though
[22:29] <ochosi> no new revs
[22:29] <bluesabre> where are you looking?
[22:30] <ochosi> oh cra
[22:30] <ochosi> p
[22:30] <bluesabre> https://code.launchpad.net/~xfpanel-switch-dev/xfpanel-switch/trunk
[22:30] <bluesabre> ;)
[22:30] <ochosi> sry, was looking at your junk
[22:30] <knome> haha
[22:30]  * ochosi puts on his innocent not-native-speaker hat
[22:30] <bluesabre> lol
[22:32] <ochosi> looks
[22:32] <ochosi> good
[22:32] <bluesabre> ish
[22:32] <bluesabre> probably
[22:32] <ochosi> :)
[22:32] <bluesabre> :D
[22:32] <ochosi> well, enough for a 0.1 release and getting it into the archive imo
[22:33] <ochosi> then the way is paved for future updates in terms of looks and functionality
[22:33] <ochosi> and we might get some (useful) feedback too
[22:33] <bluesabre> yeah
[22:33] <bluesabre> might be difficult to get in, and maybe not
[22:33] <ochosi> so imo you can release it as is now
[22:33] <ochosi> and then we can start the process of getting it in, and into our packageset
[22:34] <bluesabre> I'll work on it a bit still
[22:34] <ochosi> dunno, have little experience with that
[22:34] <ochosi> you mean now?
[22:34] <bluesabre> probably, or at least tonight
[22:34] <ochosi> cause if you mean "in the near future", better release it now ;)
[22:34] <bluesabre> lol
[22:34] <ochosi> that was were we left things last time, iirc
[22:34] <bluesabre> true
[22:34] <ochosi> what do you wanna improve?
[22:35] <bluesabre> upload frequency?
[22:35] <ochosi> haha
[22:35] <ochosi> yeah, in terms of xfpanel-switch though
[22:35] <bluesabre> I'll do it
[22:36] <bluesabre> bug me about it if no action by this time tomorrow ;)
[22:36] <bluesabre> going to work on it now
[22:37] <ochosi> heh
[22:37] <ochosi> under the hood or UI wise though?
[22:38] <bluesabre> probably both
[22:38] <bluesabre> I'll get it to something I'd want to blog about
[22:39] <ochosi> hm, anything i can help you with?
[22:39] <ochosi> it'd have to be within the scope of 20mins though
[22:39] <ochosi> after that i gotta get some sleep
[22:40] <bluesabre> if you have any ui tweaks you'd like to make, go for it
[22:40] <ochosi> if you're not adding functionality, i'm not sure tbh :)
[22:41] <ochosi> other than an "import" button, i can't really think of much
[22:41] <ochosi> or an infobar saying "your current configuration hasn't been saved. [save] [x]"
[22:41] <bluesabre> yeah
[22:41] <ochosi> but that'd mean somehow checking whether it has been saved
[22:43] <bluesabre> can timestamp the xml file
[22:43] <ochosi> sure, but then it'd still be almost always visible
[22:44] <ochosi> oh, or did you mean something like "you haven't backed up your configuration in a week. [save now] [x]" ?
[22:45] <bluesabre> the message would only be displayed when this app is open
[22:45] <bluesabre> so if there are unsaved changes, can notify
[22:46] <bluesabre> or maybe not do that at all for this release
[22:46] <ochosi> yeah
[22:46] <ochosi> that's why i meant maybe this is for later cause it needs changes under the hood too
[22:47] <bluesabre> yeah
[22:50] <ochosi> so anyway, i got no ideas how to do this basic UI significantly better for the moment
[22:50] <ochosi> the app is still a bit rough/dumb, and so is the UI
[22:50] <bluesabre> definitely not release ready
[22:50] <bluesabre> lots of buttons do nothing
[22:50] <bluesabre> particularly saving
[22:50] <ochosi> oh
[22:51] <bluesabre> was pretty sure I made more progress than this
[22:51] <ochosi> that's interesting
[22:51] <bluesabre> :\
[22:51] <ochosi> didn't it "work at some point"?
[22:51] <bluesabre> pretty sure
[22:51] <Unit193> I was sure bluesabre was patching cdimage/livecd-rootfs.
[22:51] <bluesabre> I'll work on this
[22:52] <bluesabre> er, not that
[22:52] <knome> haha
[22:52] <bluesabre> Unit193: I don't know what changes are needed there
[22:53] <Unit193> That's OK, nor do I.
[22:54] <bluesabre> nice
[22:54] <bluesabre> we'll need to start asking around then
[22:58] <bluesabre> ochosi: I'll get it up to par tonight
[22:58] <ochosi> this is why workitems should really be assigned to individuals rather than teams
[22:58] <ochosi> i mean the -core issue
[22:58] <knome> YES
[22:58] <ochosi> (xfpanel-switch too though)
[22:59] <ochosi> Unit193: you ok with getting assigned to the xubuntu-core workitem?
[22:59] <knome> being assigned a work item shouldn't mean that you do 100% of the work either, just that you are the one that oversees the progress
[22:59] <ochosi> exactly
[22:59] <knome> (except maybe when it's a specific task, eg. a bug or a new feature)
[23:00] <ochosi> bluesabre: btw, it also doesn't set an appicon yet, so no icon in tabwin
[23:00] <Unit193> Eh, I'll likely put it off as long as I can, tbh.
[23:00] <knome> Unit193, pick another work item then? [:
[23:01]  * ochosi takes that as a "yes"
[23:01] <knome> ochosi, you'll take anything as a yes...
[23:01] <bluesabre> ochosi: yeah
[23:01] <bluesabre> will fix it all
[23:01] <bluesabre> pretty sure it was past this stage :D
[23:01] <ochosi> bluesabre: oh also, isn't the x-d-s workitem already done?
[23:02] <bluesabre> yeah, why do you ask?
[23:02] <bluesabre> :D
[23:02] <ochosi> heh
[23:02] <knome> bluesabre, it isn't marked as such?
[23:03] <bluesabre> knome: you must have an outdated page, reload once in a while
[23:03] <bluesabre> ;)
[23:03] <ochosi> knome: i think "he asked knowingly"
[23:05]  * bluesabre is being mean
[23:05] <knome> hah :P
[23:05] <knome> ochosi, you know, his wife likes photography
[23:05] <knome> ochosi, could be holidays
[23:05] <ochosi> lol
[23:05] <ochosi> that is just too befitting
[23:06] <ochosi> yeah, i think he's a man of the world, he's been around
[23:06] <knome> yeah, he's always going
[23:06] <ochosi> bluesabre: let us know if you need context ;))
[23:06] <knome> i bet she goes too
[23:06]  * bluesabre is lost
[23:06] <bluesabre> again
[23:07] <knome> bluesabre, you STILL haven't watched that sketch
[23:07] <bluesabre> oh wait
[23:07] <bluesabre> I think you gave me this one to watch once
[23:07] <bluesabre> its been a while
[23:07] <knome> yes...
[23:07] <bluesabre> didn't absorb it completely
[23:07] <ochosi> bluesabre: try again: https://www.youtube.com/watch?v=SrDFGa0juCM
[23:07] <knome> ooh, absorb
[23:07] <bluesabre> didn't marinade in it for a few years
[23:07] <knome> says he knowingly
[23:07] <ochosi> 4mins not wasted
[23:08] <ochosi> knome: yeah, he's a go-er
[23:17] <ochosi> bluesabre: good luck with xfpanel-switch, gotta hit the sack
[23:18] <bluesabre> seeya ochosi: pull from the repo again tomorrow and give it a spin
[23:18] <ochosi> will, and i hope it'll spin!
[23:18] <ochosi> ;)
[23:18] <knome> ooh, spin
[23:19] <knome> i'm off as well
[23:19] <knome> nighty and ttyl
[23:29] <bluesabre> saving fixed
[23:54] <bluesabre> cleared out deprecated widgets
[23:54] <bluesabre> progress!