[00:00] <flocculant> knome: and just how long do you think we should play this game with them? 
[00:00] <flocculant> I've got to have a cut off point 
[00:00] <knome> if they won't allow the core name, let's just change it then
[00:00] <knome> but if they don't, they'd better have a good argument
[00:00] <flocculant> and given they are just playing games then my cut off off point is the 1st 
[00:00] <flocculant> of January
[00:01] <knome> it's their infrastructure; i'm sure they'll happily let us run our own and call our products whatever we like
[00:01] <knome> do you have a link to LP where the naming discussion is?
[00:01] <flocculant> the more I see of this issue the more I can see why people were /o\ over other debian issues
[00:02] <flocculant> and yes it is the same ;)
[00:02] <flocculant> knome: no - the name discussion was with adam in -release
[00:02] <knome> maybe.
[00:02] <knome> ok, do you remember the date?
[00:02] <flocculant> 2015/4
[00:03] <Unit193> infinity didn't seem to care, just wanted to point it out.
[00:03] <flocculant> I've given up tbh on caring much, my position is if they eventually come through a day or so prior to release then that's really too bad and much much too late
[00:04] <flocculant> yea
[00:04] <Unit193> I'll poke again, I suppose.
[00:04] <knome> i haven't seen anybody explicitly say "no"
[00:04] <flocculant> then slangasek disapproved - and has ignored it since
[00:04] <flocculant> well
[00:05] <Unit193> And wonder why they don't get contributors?
[00:05] <flocculant> other than an apparent 'it's on my queue' comment to Unit193 
[00:05] <flocculant> which is as meaningless as any other comment
[00:07] <flocculant> oh good lord is the wiki down again 
[00:07] <flocculant> should make sure we bring this up on the pointless CC chat I guess
[00:08] <knome> the wiki works for me.
[00:08] <flocculant> mmm
[00:08] <flocculant> https://wiki.ubuntu.com/CommunityCouncilAgenda
[00:09] <flocculant> that one? 
[00:09] <knome> that too
[00:09] <flocculant> must be local for some reason then - I can get anywhere else
[00:12] <flocculant> or firefox - chromium landed fine
[00:12] <knome> i would personally find out if this is about the name or not
[00:12] <knome> if it's about the name, then get on with it and change to something else
[00:12] <knome> if it's something else... well, then just push forward
[00:14] <flocculant> cc meeting is 2 working days before b1 freeze so that's pointless
[00:14] <knome> and figure out possible blockers and see what we can do with it
[00:14] <knome> i don't think the CC is the right council to resolve this anyway
[00:15] <flocculant> I'll pinh mhall119 for the last 30 minutes of this discussion
[00:15] <flocculant> ping
[00:15] <knome> or if somebody feels like we'd like to get them involved, we can just poke them outside a meeting
[00:15] <knome> yes, something like that ^
[00:15] <flocculant> maybe not - but given they are all on holiday till god only knows when - who do we poke? 
[00:16] <knome> i don't know
[00:16] <flocculant> sorry, but I think this is about the name - perhaps amongst themselves - but ... 
[00:16] <knome> then they should clearly state that to us
[00:16] <flocculant> and any reason to slow is enough
[00:16] <knome> in which case we will come up with a new one
[00:16] <flocculant> I have no trust in them anymore tbh
[00:17] <flocculant> as a 'group' 
[00:17] <knome> i guess i can see that, but otoh, that attitude doesn't help at all (as you also know)
[00:17] <knome> we can blame them to the end of the world, but that won't make them do decisions we want
[00:17] <knome> might do quite the opposite
[00:18] <flocculant> knome: currently we're waiting for one person to find time in their queue 
[00:18] <knome> if that's the real status (and they just don't want to do it because of the name), then we should wait
[00:18] <knome> we should also be in touch with them and probably get an ETA at some point
[00:18] <flocculant> right now - they work for me, it's taking too long so I don't even have to think about testing it ;)
[00:18] <knome> but i don't think there is much more to do
[00:19] <flocculant> as far as I now 'we' can't do more than we have 
[00:19] <flocculant> Unit193: is that right ^^ ?
[00:19] <knome> not much at least
[00:19] <flocculant> we did what they asked
[00:20] <knome> yes, i have the same point of view to it
[00:21] <flocculant> anyway - bed for me now :)
[00:22] <knome> yep, have a good night and don't worry too much about things
[00:23] <flocculant> oh I won't :)
[00:23] <flocculant> if it turns up in March - too late ;)
[00:23] <knome> let's target for january.
[00:24] <flocculant> mmm
[00:24] <flocculant> night :)
[00:24] <knome> good night!
[00:31] <Unit193> Well we could fix it so it applies cleanly, but I've already done that before and don't see a reason to do so again unless it'll be reviewed before I'd have to fix it yet again.
[00:43] <knome> at least i'd make sure the name isn't a showstopper before doing that.
[00:44] <Unit193> I'd have thought they'd say that...
[01:16] <Unit193> flocculant: Hi.  So I'm still activly using Xenial somewhere, but haven't done much reporting except for the upgrade.  Is there something specific there that'd help you, or should I just continue to mention things/file reports as they crop up?
[07:29] <flocculant> Unit193: just carry on as you are is great :)
[13:39] <knome> some improvements about to land to xubuntu.org
[13:39] <knome> as soon as the IS team pushes the new branch revision
[13:51] <knome> bbl
[19:37] <pleia2> ooh, rt tickets being addressed \o/
[19:57] <knome> yup
[21:45] <mhall119> flocculant: I read the backlog, but I don't understand the problem or it's context, can you give me a tl;dr?
[23:31] <knome> mhall119, we've been waiting for a merge since september; merging this change would enable a new version of xubuntu (named "xubuntu core") to be built and thus appear on cdimage.ubuntu.com; we're not exactly sure what is taking so long
[23:31] <knome> mhall119, one possibility is the naming; some concerns have been raised because it conflicts with "ubuntu core", but afaik, nobody has said that's the reason
[23:32] <knome> mhall119, another possibility is that people are simply busy
[23:32] <knome> mhall119, this is more problematic for us every day because as long as the official builds aren't up, we can't do official testing