[00:07] <Unit193> bluesabre: So did you do all the changes in x-d-s and update whisker? :--D
[00:07] <bluesabre> Unit193, not yet D-------------:
[00:09]  * Unit193 waves.
[00:10] <Unit193> (FWIW, you can pretty much skip all other recent releases, I've already done something with 'em.  All but sensors and mount.)
[00:36] <bluesabre> :)
[12:28] <flocculant> bluesabre ochosi - ok so this is driving me nuts :p
[12:28] <bluesabre> ?
[12:28] <flocculant> thunar 
[12:28] <bluesabre> uh oh
[12:28] <flocculant> *now* I'm seeing the reload issue again
[12:29] <bluesabre> which one is the reload issue?
[12:29] <flocculant> where a file that's been moved on still shows in the origin
[12:30] <bluesabre> ah
[12:30] <bluesabre> :\
[12:30] <bluesabre> that might be a gvfs thing
[12:30] <bluesabre> I saw that on nautilus this week
[12:30] <flocculant> oh good 
[12:31] <flocculant> now of course after telling corsac and ochosi it crashed - it won't :p
[12:32] <bluesabre> :D
[12:32]  * flocculant does something entirely different 
[12:33] <flocculant> might install some other *buntu for 17.04 and test this with that file manager - ubuntu and nautilus sounds like the best plan :p
[13:52] <flocculant> that was a moderately horrid experience - seems to be no way to select files in nautilus with a mouse window
[13:52] <flocculant> bluesabre: anyway - didn't manage to crash nautilus there
[17:23] <knome> flocculant, http://staging.xubuntu.org/tracker/
[17:24] <knome> flocculant, this is PoC/betaish stage, but see how the timeline acknowledges that the done item has been closed 2 times
[17:24] <knome> flocculant, also note task groups vs. blueprints - you can now have multiple overlapping
[17:25] <knome> this has probably been more of a problem with community/website/marketing stuff, but things that really belong to more than one blueprint have been painful
[17:25] <flocculant> yea ack that point ^^
[17:26] <flocculant> my issue is still an issue - real-time(as far as it goes) with where bugs are reported - so we would still be hitting lp api I guess
[17:27] <flocculant> and if we mvoe on one stage then upstream reporting where it's listed on lp
[17:27] <knome> yes, but much less
[17:27] <flocculant> eg a lp bug with upstream link
[17:27] <knome> i think bugzilla has an API as well, so we should be able to work with that as well
[17:27] <knome> and yes, now we can do dozens of cool things
[17:28] <knome> one thing i was considering is that we might want to create tasks for "all bugs"
[17:28] <knome> and then link the bugs into those tasks
[17:28] <knome> so eg. "fix thunar" is the task
[17:28] <knome> and then it could have 1-3 bugs linked to it
[17:28] <knome> if we want
[17:28] <knome> or then just one
[17:28] <knome> or then we can just do what we always did
[17:29] <knome> one feature i haven't been exposing much on the PoC yet is that we can now have a full description for each task ála wordpress articles
[17:29] <knome> so the tasks are not just titles, they can have all kinds of extra data
[17:29] <knome> and this comes without extra work too
[17:31] <flocculant> being able to multiple link bugs to a 'task' is good 
[17:31] <knome> yes, i gathered this would be a good thing
[17:31] <knome> also, one more thing
[17:31] <knome> remember the bug targets are sometimes weird when you have a bug linked to multiple packages?
[17:31] <knome> well, now we could allow you to select which package to show...
[17:37] <flocculant> that would be a positive ;)
[17:37] <knome> yep
[17:37] <knome> all kinds of little things
[17:37] <knome> but most importantly from my POV to be able to track a single task better - even if its title changed
[17:40] <flocculant> I will take some convincing - because most bp's I'm involved with have to talk to lp
[17:40] <flocculant> and I imagine docs too
[17:41] <knome> sure, i'll try to get some kind of testing stuff going soonish
[17:41] <knome> i'm not doing anything re: bugs quite yet
[17:41] <knome> but since i can reuse most of the code, it should be quick
[17:41] <flocculant> and how about linking with the dev side of things?
[17:41] <knome> what do you mean with that?
[17:41] <knome> you mean linking with dev.xubuntu.org?
[17:42] <flocculant> well - if we lose blueprints - how does all the LP stuff currently linking together - link outside? 
[17:42] <knome> how does it need to?
[17:42] <flocculant> bugs > fixes for one I guess
[17:42] <knome> i mean, there's not much synergy we can from tracking stuff in blueprints at the moment anyway :(
[17:43] <flocculant> other than bugs and fixes 
[17:43] <knome> i'm not sure what that stuff is
[17:43] <knome> we aren't using the LP milestones
[17:43] <knome> so no loss there
[17:43] <flocculant> not sure anyway - I will be keeping my powder dry for the moment :)
[17:43] <knome> hehe
[17:44] <knome> also, one thing i forgot to mention which is fun
[17:44] <knome> we can have multiple assignees per task
[17:44]  * flocculant always has a match though ...
[17:44] <knome> i just don't know how we'll show that but...
[17:44] <flocculant> not that you need telling that :p
[17:44] <knome> and we can also add anything we want to the assignee
[17:44] <knome> doesn't have to be LP team
[17:44] <knome> or user
[17:44] <flocculant> right
[17:44] <knome> which is a slight advantage too
[17:46] <flocculant> :)
[17:46] <flocculant> always happy to be involved as you know 
[17:46] <knome> yep
[17:46] <knome> i'll need some testing once stuff is set up
[17:46] <knome> mostly the bugs
[17:46] <Unit193> thunar 1.6.10-6 uploaded by Yves-Alexis Perez (corsac) (Closes: #800723)
[17:47] <flocculant> just not ever going to be someone you can rely on saying 'that's awesome' till I really mean it :D
[17:47] <knome> i'm still not sure if i want to handle that as i do now (via real cron jobs) or if i should do something else
[17:47] <knome> probably at least a button that says "reload all bug data"
[17:47] <knome> when you need that now
[17:47] <flocculant> personally I think that last would make more sense
[17:47] <flocculant> then when 'person' needs real time - they can get it
[17:48] <knome> yes, that AT LEAST
[17:48] <knome> but the automatic side...
[17:48] <knome> maybe i'll move more to a "poor man's cron" kind of thing
[17:48] <flocculant> could be weekly at that point? 
[17:48] <knome> eg. not have a real cron job, but some kind of timestamp in the db
[17:48] <knome> so it only updates if somebody is actually looking
[17:48] <knome> yeah, something like that
[17:48] <flocculant> as long as all know when it was last globally updated
[17:48] <knome> yep
[17:48] <knome> that's more than easy to achieve now
[17:49] <knome> we can even allow per-bug updates
[17:49] <knome> and show that date too
[17:49] <knome> as that's again a less resource-requiring task than updating all bugs
[17:49] <flocculant> I tend to err on the side of not adding bugs because of what bp says tbh
[17:50] <knome> hmm?
[17:50] <flocculant> if berty reads bp and it says things we'll fix this cycle - why would they not expect them to be fixed
[17:50] <knome> right
[17:50] <flocculant> should just edit the 'words'
[17:50] <knome> we can just change the description
[17:50] <knome> :)
[17:50] <knome> yep
[17:50] <flocculant> yea :)
[17:50] <knome> ok, so
[17:50] <knome> gone for a while
[17:51] <flocculant> and the thunar issue would probably always be better linking upstream not xubuntu
[17:51] <flocculant> yea - same - sunday evening stuff - bbl
[17:51] <knome> hf
[21:05] <Unit193> greybird-gtk-theme 3.22.1-1 uploaded by Yves-Alexis Perez (corsac)
[22:41] <bluesabre> Unit193, nice!