[04:18] <darkxst> octoquad, thanks
[04:18] <darkxst> octoquad, btw any bugs which are feature requests get marked wishlist
=== JockeTF1 is now known as JockeTF
[08:23] <flexiondotorg> darkxst, Are you participating in 15.10 Beta 1?
[08:24] <darkxst> flexiondotorg, didnt ali already update the wiki page? yes we are
[08:25] <flexiondotorg> Thanks.
[08:25] <flexiondotorg> Just double checking. I'm helping with the flavour releases again.
[08:25] <darkxst> flexiondotorg, although I might just run off and hide in a corner, it could be bad, with some big updates in the last week that havent really been tested widely
[08:26] <flexiondotorg> darkxst, You and me both ;-)
[08:26] <darkxst> flexiondotorg, great thanks for helping again
[08:27] <darkxst> flexiondotorg, but I made it onto ubuntu-desktop team
[08:27] <darkxst> next stop could be core-dev, at which point I would probably have the permissions to flick the buttons on the other side
[08:27] <flexiondotorg> darkxst, Cool. Is that a community role or ful time?
[08:28] <darkxst> flexiondotorg, community, still looking for full time work
[08:29] <darkxst> and well 90+% of members on that team are Canonical, but I get upload rights to alot of the overlapping stuff
[08:34] <darkxst> flexiondotorg, in fact the ubuntu-gnome packageset is more or less completely borked, by that overlap! only really has a dozen packages of interest in it
[08:35] <flexiondotorg> I suspected that maintain Ubuntu GNOME must be tricky given how much Unity leans on GNOME3 components.
[08:36] <darkxst> flexiondotorg, its been a long haul, sometimes it easy we do the work for them, othertimes, shit fucking breaks them and we get stuck on old crap, having to revert patches for ages
[08:37] <darkxst> bluez5 was a good example of that
[08:38] <flexiondotorg> darkxst, Yep. I feel the pain with Bluez5 too.
[08:38] <darkxst> next up will be gnome-user-share and I'm just waiting on reports that the sharing panel is completely stuffed atm
[08:39] <flexiondotorg> Bluetooth is still pretty busted in Ubuntu MATE 15.10. Looks like 16.04 it will finally be sorted.
[08:39] <darkxst> lots of things are busted, because the touch team can't keep up with the changes!
[08:40] <darkxst> network-manager 1.0 release and packagekit 1.0 are noticeably missing
[08:41] <flexiondotorg> Yeah. It is amazing just how similar the MATE and GNOME3 requirements are, even today.
[08:41] <flexiondotorg> But I am in a way better situation that you I think.
[08:47] <darkxst> flexiondotorg, but how much isnt forked?
[08:47] <flexiondotorg> Well, Not as much as you'd think now. We've aligned with GNOME3 libs quite extensively.
[08:48] <darkxst> flexiondotorg, so you on gtk3, etc
[08:48] <flexiondotorg> And will continue to do so.
[08:48] <flexiondotorg> darkxst, GTK2 and GTK3 a build targets.
[08:48] <flexiondotorg> In Debian/Ubuntu it is still GTK2 because GTK3 was still considered experimental when MATE 1.10 released.
[08:49] <flexiondotorg> That said, I maintain MATE in Arch Linux and provide GTK2 and GTK3 builds. I've used GTK3 as my main desktop for months, no major issues.
[08:49] <flexiondotorg> Fedora also have a GTK3 build too.
[08:50] <darkxst> gtk3 breaks something every  cycle, still waiting for that to drop in 3.18 though
[08:50] <flexiondotorg> And we've improved GTK3 support signifcantly since 1.10 release just a few months ago. So I expect GTK3 will be stable for 1.12.
[08:50] <flexiondotorg> darkxst, Yes, this is one reason why we've helpd off "promoting" the GTK3 version.
[08:51] <flexiondotorg> We see regressions with every GTK3 release.
[08:51] <darkxst> but really its just the canonical guys don't dog-food the gtk3 updates during dev cycles
[08:52] <darkxst> flexiondotorg, and it has settled down a lot since the early days!
[08:54] <darkxst> the breakage back circa 3.6-3.10 was far worse
[08:55] <flexiondotorg> I agree.
[08:58] <darkxst> flexiondotorg, the biggest issue for us has been getting useful dev's
[08:58] <flexiondotorg> For Ubuntu GNOME specifically?
[08:59] <darkxst> flexiondotorg, yes
[08:59] <flexiondotorg> In what respect? Updating packages and such or coding new features?
[09:01] <darkxst> well both really, noskcaj is great with packaging but can't code
[09:03] <darkxst> most of the interested people to try to come on board have no experience with either ;(
[09:04] <flexiondotorg> Yeah, I know where you're coming from.
[09:04] <flexiondotorg> This is why I do most of my work on MATE in Debian. There is an established developer community around MATE there.
[15:22] <octoquad> darkxst, I marked it as opinion because I remember there was a reason for it being like that (couldn't remember details) and I wasn't sure of implementation problems. In short, up for discussion (opinion) until a resolution has been proposed.
[15:23] <octoquad> darkxst, of those three items I have to work on, do they have to be done this week? I'm not finding much time to help out this week unfortunately.
=== neopss is now known as neops
=== neopss is now known as neops
=== ccar_away is now known as ccarella