[18:00] <elkybirthday> ooher, I get to attend one of these meetings
[18:01] <Pici> Yay.  Meetings.
[18:01] <topyli> elkybirthday: ooh is that nick current? congratulations :)
[18:01] <Pici> elkybirthday: Happy bday!
[18:01] <elkybirthday> :D
[18:01]  * Seeker` provides cake
[18:01] <elkybirthday> depends which timezone you ask, but the one my body is in, it is indeed current
[18:02] <elkybirthday> om nom nom
[18:04] <topyli> ok, least resistant chairing
[18:05] <topyli> #startmeeting
[18:05] <MootBot> Meeting started at 13:05. The chair is topyli.
[18:05] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[18:05] <Pici> Although my -ot support policy item is first on the list, I propose defering it until some of the more pressing issues are attended do.
[18:05] <Pici> s/do/to/
[18:05] <Pici> [link] https://wiki.ubuntu.com/IRC/IrcCouncil/MeetingAgenda
[18:05] <MootBot> LINK received:  https://wiki.ubuntu.com/IRC/IrcCouncil/MeetingAgenda
[18:05] <topyli> ok Pici, good idea
[18:05] <nhandler> o/
[18:05] <bilalakhtar> Is this the IRCC meeting?
[18:05] <nhandler> Yes bilalakhtar
[18:05] <topyli> bilalakhtar: yes
[18:06] <topyli> [TOPIC] Failure to document blanket ban policy
[18:06] <MootBot> New Topic:  Failure to document blanket ban policy
[18:06] <topyli> ikonia: you around?
[18:06] <topyli> let's group this and the next one
[18:06] <ikonia> I am
[18:06] <ikonia> sounds reasonable
[18:06] <ikonia> they are the same thing
[18:06] <ikonia> I just wanted to be clear there are two actions here
[18:06] <Pici> Indeed.
[18:07] <ikonia> topyli: do you want me to just talk, or do you want to start ?
[18:07] <Pici> ikonia: Do you want to summarize for those present who may not be familiar with the issue?
[18:07] <ikonia> certainly
[18:08] <ikonia> There is an "appeals" process for users who are banned/miss-treated from the Ubuntu IRC name space, I have raised the issue that there needs to be the reverse of this for long term trouble users. This was agreed should happen, it has not been documented, or implemented on the requested trouble users
[18:09] <ikonia> the reverse should include a blanket ban from the ubuntu IRC council controlled ubuntu name sapce
[18:09] <ikonia> space
[18:09] <ikonia> (sorry should have been clear about that, hence blanket ban policy)
[18:09] <topyli> this is true, we are in talks with staff but we are/i am slow
[18:09] <nhandler> ikonia: We are currently working with freenode staff to find a way to effectively implement and enforce this
[18:10] <ikonia> nhandler: I thought it was as simple as putting a ban in all the channels controlled ?
[18:10] <Seeker`> ikonia: how long ago did you raise the issue?
[18:10] <elkybirthday> can we not do it manually until then?
[18:10] <Pici> ikonia: We control a lot of channels.
[18:10] <nhandler> ikonia: Not really, since IP addresses change (and they use proxies)
[18:10] <ikonia> Seeker`: approx 6 months ago but I can't be exact
[18:10] <topyli> it is an old issue yes
[18:10] <ikonia> nhandler: the main ones in the examples I raised do not change
[18:11] <tsimpson> it's also difficult to enforce if we do it manually, we can't watch each join in all the channels, so it's possible they'd still slip in
[18:11] <ikonia> ok - so lets move from the implementation for a while, where is the documetned process and critera that was discussed about
[18:11] <Seeker`> so either we implement a complete ban or none at all?
[18:11] <Seeker`> thats stupid
[18:11] <elkybirthday> I'd like to point out that in the mean time, ikonia is getting targetted for harrassment from one of the individuals, in a manner that * is* disrupting various channels
[18:11] <nhandler> ikonia: That will partially depend on what freenode staff end up deciding wrt this issue
[18:12] <Pici> Would it be amenable to allow operators to manually place the bans if the target joined a channel, but before they acted in a manner that would get them banned in normal circumstances.
[18:12] <ikonia> nhandler: why are freenode staff controlling the critera for the process ?
[18:12] <Pici> Like 'ban on sight'?
[18:12] <elkybirthday> the individual is feeling enabled by the council's lack of action or response or anything public really
[18:12] <ikonia> Pici: totally
[18:12] <ikonia> Pici: the point is to document and recognise that user is not allowed in the ubuntu name space
[18:12] <ikonia> Pici: how we act to that is seconady
[18:12] <ikonia> secondary
[18:12] <nhandler> ikonia: Because it is ugly setting bans in all #ubuntu-* channels and enforcing them, and we are trying to find a better way to handle that
[18:13] <ikonia> nhandler: ok, that doesn't change the processof applying for the ban, or the critera
[18:13] <elkybirthday> nhandler, can we not deal with the social side in the interim at least?
[18:13] <ikonia> why has that not been documented ?
[18:13] <Pici> Perhaps we should action and document that while we find a way to work with freenode.
[18:13] <ikonia> Pici: I thought that action had already been taken
[18:13] <ikonia> the reverse of the appeals process, and the critera must be met before applying
[18:13] <Pici> ikonia: I don't see it documented.
[18:13] <ikonia> it's not
[18:14] <ikonia> it was an action the council agreed to do
[18:14] <topyli> we agreed on it, but we never documented it
[18:14] <Seeker`> why not?
[18:14] <ikonia> the documenting was part of the agreement
[18:14] <topyli> yes
[18:15] <Seeker`> This is starting to verge on the next topic too
[18:15] <elkybirthday> yeah
[18:15]  * nhandler notes that there is nothing stopping people not on the council from helping with some of these tasks
[18:15] <ikonia> nhandler: actually there is
[18:15] <ikonia> nhandler: I offered to do it, but was told it was not acceptable as the council had to set the critera
[18:15] <Pici> Hm.
[18:16] <elkybirthday> sure there is. we can't decree non grata status on someone on behalf of the council. that's what's being requested. we cannot do that. only ircc can do that
[18:16] <nhandler> ikonia: No. Anyone in the community is capable of proposing a draft for the council to approve
[18:16] <tsimpson> as long as the council approves it, I see no issue
[18:16] <ikonia> nhandler: that was a different discussion I had then
[18:16] <ikonia> nhandler: I was told it was not appropriate for me to do it as the council had to set the policy, and I can't do that
[18:16] <Pici> But it is our fault for not correcting that information that you were provided with.
[18:16] <Seeker`> ultimately, someone on the council will have to do something with any documents generated, and that seems to be the part that is failing
[18:17] <nhandler> ikonia: Yeah, we'll have to ultimately ACK the content of such a document, but who actually writes it up is irrelevant imo
[18:17] <Pici> I'm not sure when that happened, but we have had a few documents drafted by our operators in the past that we're working to bring into policy.
[18:17] <elkybirthday> I rather suspect that ikonia basically wrote the policy in his emails
[18:18] <topyli> it could be transferred to wiki and we could accept it rather easily
[18:18] <Seeker`> do it then?
[18:18] <Pici> Would you like me to do that?
[18:18] <ikonia> elkybirthday: it was spelt out quite clear in the emails
[18:19] <elkybirthday> ikonia, im aware of what your emails are like :)
[18:19] <nhandler> Pici: If you are up for it, I doubt there will be any objections
[18:19] <topyli> Pici: yes, with ikonia's help
[18:19] <ikonia> just tell me what you need
[18:20] <ikonia> I've pushed this multiple times on email and either got no response or being told "it's been worked on"
[18:20] <Pici> [action] Pici to document ikonia's namespace ban proposal.
[18:20] <ikonia> the correct reponse is "can you help with $X" if you need help/input
[18:20] <Pici> Er, or does the chair need to do that?
[18:20] <topyli> [ACTION] Pici to document ikonia's namespace ban proposal.
[18:20] <MootBot> ACTION received:  Pici to document ikonia's namespace ban proposal.
[18:20] <Pici> topyli: thanjs.
[18:20] <topyli> apparently
[18:20] <elkybirthday> Pici, yeah, otherwise anyone can set actions
[18:20] <Pici> ikonia: Let me read over the email you sent and I'll let you know what else I need.
[18:21] <topyli> [TOPIC] Failure to respond / follow up on pending actions
[18:21] <MootBot> New Topic:  Failure to respond / follow up on pending actions
[18:21] <ikonia> Pici: just shout/mail
[18:21] <topyli> is this the same issue or another one? :)
[18:21] <Pici> What do you want us to say about this?
[18:21] <ikonia> do you want an overview again ?
[18:21] <Pici> I don't think we need an overview, unless someone else thinks we do.
[18:21] <Seeker`> isn't this one kinda obvious?
[18:21] <nhandler> I think the big issue is that we are simply not delegating enough
[18:22] <nhandler> We are trying to handle too many things at once, and we are only 5 people
[18:22] <ikonia> I personally have raised multiple issues with the IRC council, I'm also aware of other operators doing the same, the lack of response or time to implimenting these requests is beyond crazy
[18:22] <Seeker`> nhandler: It actually just seems like the council isn't do anything they say they will
[18:22] <ikonia> nhandler: what is the blocker ?
[18:22] <ikonia> nhandler: responding to an email to at least acknowledge it's been read isn't a massive task, unless you ar getting 100+ requests per week
[18:22] <Pici> I think we're all to blame.
[18:23] <Pici> Er, I mean the IRCC members.
[18:23] <elkybirthday> does the ircc need to be expanded?
[18:23] <Seeker`> just how much work does the ircc have each week that 5 people can't get it done?
[18:23] <nhandler> elkybirthday: Well, part of the issue is that due to real life issues, we only had a partial council for a period of time
[18:23] <topyli> i don't think the council needs to be bigger, we've been a bit unfortunate lately
[18:24] <ikonia> topyli: define latley for perspective please
[18:24] <topyli> a few months or so
[18:24] <topyli> everybody's back now though
[18:24] <elkybirthday> nhandler, that should have been said before now so it could be fixed
[18:24] <ikonia> k
[18:24] <ikonia> ok
[18:24] <Pici> I could come up with excuses, but I'd rather just have us get back on the horse and get to resolving everyone's problems.
[18:24] <ikonia> Pici: agreed
[18:24] <topyli> aye
[18:25] <Seeker`> surely if that is **that** much work to do and someone isn't going to be around for a while, replace them?
[18:25] <ikonia> Pici: people have things to deal with, no question, but an email to explain why it's not happenening or just a response to say, we got it, thanks, is all that is needed
[18:26] <nhandler> What we should probably do is go through what remaining actions we have and try and give a few of them to members of the OP team.
[18:26] <Pici> If its appropriate of course.
[18:26] <topyli> indeed, we should at least reply always. we (at least i) should also review our task list more often
[18:26] <ikonia> council, that last issue was more a heads up/ shake up, nothing needs to happen beyond as pici said, getting back on the hourse
[18:27] <ikonia> horse
[18:27] <topyli> ikonia: the overviews?
[18:27] <Pici> ikonia: We do have our team reports, but as I discussed at our IRC session at UDS, we will be working to provide more detail in them.
[18:27] <ikonia> topyli: the failure to respond / follow up on pending items
[18:27] <Pici> Oh
[18:28] <Pici> Sorry, I thought you were talking about the next items.
[18:28] <ikonia> I'll summarise the next two points quikely as they are the same
[18:28] <topyli> ok
[18:28] <topyli> let me open it
[18:28] <elkybirthday> one thing i tried to get set up whilst I was n the ircc is a request tracker. because we're not email people and we already work on an issue-based workflow with the bantracker
[18:28] <topyli> [topic] high level council overviews
[18:28] <MootBot> New Topic:  high level council overviews
[18:28] <ikonia> I hear a massive amount of talk about great things happening, yet based on the points I raised earlier, I see none of it. I don't see the council doing anything activly for the community or the ops team beyond creating red tape
[18:29] <Pici> ikonia: We do have our team reports, but as I discussed at our IRC session at UDS, we will be working to provide more detail in them.
[18:29] <ikonia> if you are doing something that benifits either of the groups mentioned, I'd like to hear about it
[18:29] <topyli> elkybirthday: i would love to have bugs on launchpad
[18:29] <Seeker`> the IRCC team reports aren't linked from the IRCC wiki page, afaics
[18:29] <Pici> Seeker`: They should be...
[18:29] <ikonia> Pici: up until now, I see nothing, so going forward reports are great, but I want to know what's happened in the year this council has been together
[18:29] <ikonia> I see notyhing
[18:29] <nhandler> Seeker`: They are linked from https://wiki.ubuntu.com/IRC/IrcCouncil/MeetingAgenda
[18:29] <tsimpson> Seeker`: only from the meeting agenda page
[18:29] <ikonia> I see nothing
[18:30] <elkybirthday> topyli, im not sure LP bugs is a suitible place, to be honest. the IS team in canonical don't use it, they have an rt instance
[18:30] <nhandler> We have done stuff. For instance, https://wiki.ubuntu.com/IRC/Membership is the most recent thing we have been up to (currently a draft)
[18:30] <ikonia> nhandler: a draft document, anything else ?
[18:30] <Pici> I've brought this up a few times, but we're going to be making more of an effort to document our day-to-day stuff.
[18:30] <nhandler> ikonia: It is waiting on CC approval
[18:30] <ikonia> nhandler: anything else/
[18:30] <Seeker`> where can the team reports be found?
[18:30] <Seeker`> oh, there
[18:31] <nhandler> Seeker`: https://wiki.ubuntu.com/IRCCouncil/TeamReport
[18:31] <ikonia> I'm just looking for one thing the council has done in a year
[18:31] <ikonia> it shouldn't be that hard
[18:31] <ikonia> or whats the big achievement, something you feel is a real benifit
[18:32] <Seeker`> see the lnik elky posted in -ops a while ago? about docs being placed "on display" in a basement with no lights, no stairs, in a locked filing cabinate, stuck in a disused lavatory, with a sign on the door saying "Beware of the Leopard"?
[18:32] <nhandler> ikonia: We created a Charter
[18:32] <ikonia> nhandler: poor
[18:32] <ikonia> ok - I think I'm happy with that topic, I think I get a feel for what's been achieved in a year
[18:32] <nhandler> ikonia: Not really. We have a policy for bots to be in the channel. We've recruited new ops
[18:33] <Seeker`> so, in a year you have created a charter. How about something to make operators lives easier?
[18:33] <ikonia> nhandler: stuff that happened beefore
[18:33] <ikonia> nhandler: but without as much lip service and more common sense
[18:33] <topyli> i'm not keen on shaking up things just to be able to say we changed stuff
[18:33] <ikonia> but I get the drift of what's been achieved I think, so I'm happy to move on
[18:33] <Seeker`> btw, recruiting more ops isn't an achievement, it is something that should be actively going on all the time
[18:33] <Seeker`> as people leave / aren't around as much, they should be replaced
[18:33] <ikonia> Seeker`: yes, but there is now a joke of a process to go through
[18:33] <elkybirthday> Seeker`, agreed
[18:34] <Pici> The process was new.
[18:34] <Pici> And we've learned our lessons from it.
[18:34] <topyli> what makes it a joke?
[18:34] <ikonia> yes, and pointless lip service
[18:34] <ikonia> but that's just my opinion
[18:34] <ikonia> topyli: we'll discuss that at another meeting, lets get through the issues
[18:34] <elkybirthday> topyli, is rww on the team yet?
[18:35] <topyli> elkybirthday: nope
[18:35] <elkybirthday> there's an example of the joke
[18:35] <elkybirthday> you have willing people who you're failing to convert
[18:35] <Seeker`> where is the operator recruitment process linked from on the wiki?
[18:35] <topyli> rww's access is not what we're here for right now
[18:36] <ikonia> lets move on
[18:36] <ikonia> get throughthe issues
[18:36] <topyli> good idea
[18:36] <Seeker`> where is the operator recruitment process linked from on the wiki?
[18:36] <ikonia> Seeker`: it's there I'll dig it out
[18:36] <ikonia> it's also in a factoid
[18:36] <topyli> [topic] Discussion about approved/non-approved shell hosts access to Ubuntu channels (revisit)
[18:36] <MootBot> New Topic:  Discussion about approved/non-approved shell hosts access to Ubuntu channels (revisit)
[18:37] <topyli> this is important. ikonia, still have steam to summarize this one? :)
[18:37] <ikonia> there are a number of shell providers with no active or usable usage policy, known users have been a problem on these shell hosts, I have raised an issue a long time ago in an email to the council saying which shell hosts needed to be banned in the same way as using the floodbots
[18:37] <ikonia> this is a long standing issue with the council that I have raised and chaied
[18:38] <ikonia> I have taken the action myself in #ubuntu #kubuntu #ubuntu-offtopic where the problem was most visible
[18:38] <ikonia> I did this due to lack of reponse from the council (approx 6 months)
[18:38] <ikonia> if the council wish me to undo this, they need to say so
[18:39] <topyli> there are shells with a pronounced policy of no policy on their users, i support your action
[18:39] <Pici> I think this is just a matter of documenting and sactioning the bans.
[18:40] <ikonia> I would agree, and I'm happy to put that up on the wiki as known blocked shells
[18:40] <ikonia> I've not done this again due to lack of feedback on my actions from the council
[18:40] <nhandler> Getting anything changed in the floodbots would require talking to ljl
[18:40] <ikonia> agreed, however as I stated in the mail, they are just forwaded to -ops until it is agreed
[18:40] <nhandler> Are the details of the current handling of webchat users on the wiki anywhere?
[18:41] <ikonia> I have been explaining to the efffected users manually in -ops to complain to their shell providers to get a usage policy
[18:41] <Pici> nhandler: I have an action item from UDS to work with LjL and rww to document the floodbots.
[18:41] <ikonia> nhandler: as it's recently changed I doubt it
[18:42] <nhandler> Well, having a page explaining "Why can't I get into #ubuntu" might be useful (and ties into both of those items)
[18:42] <nhandler> It could talk about shells like this, the web gateway, being banned, using a proxy, etc
[18:42] <ikonia> agreed, but I'm not writing that until I get a response from the council supporting the process
[18:42] <topyli> Pici: so you can merge this in your existing action item?
[18:43] <Pici> topyli: Which part?
[18:43] <topyli> floodbots and shells
[18:43] <nhandler> ikonia: Supporting the process of blocking an entire shell? Or for these particular shells?
[18:43] <Pici> As much as I'd like to get everything handled, I don't want to be the only one taking items.
[18:43] <ikonia> nhandler: more a case of if a shell host has a usage process that is not managed or not compatible with ubuntu's usage, then we block them
[18:44] <ikonia> the ones I raised where an example and have been updated as we now have an excellent relationship with shellium
[18:44] <Pici> I think a technical solution should be secondary to the documenting/sanctioning.
[18:44] <ikonia> Pici: agreed but 6 months with no response, I acted
[18:45] <nhandler> ikonia: I am fine with that. In general, I don't like unnecessarily broad bans like this, but if we determine the provider to be uncooperative and the shells are being abused, we have little choice (other than blocking all the individual users or exempting the good users)
[18:45] <topyli> the technical solution is there, simple bans
[18:45] <Pici> I mean the floodbots.
[18:45] <ikonia> Pici: ah yes,
[18:46] <ikonia> council, if I get a formal mail agreeing to my actions, I'll document it
[18:47] <topyli> ikonia: i'll send mail and we'll fix it
[18:47] <Pici> I have no problems with that.
[18:47] <ikonia> I'll be happy to document it
[18:47]  * Pici [actions] topyli 
[18:48] <topyli> [action] topyli to send formal agreement to ikonia's shell fix
[18:48] <MootBot> ACTION received:  topyli to send formal agreement to ikonia's shell fix
[18:49] <topyli> Seeker`: i'm skipping your item unless you reformulate it so that we understand
[18:49] <Seeker`> There is an ever increasing dependance on the IRCC to decide something before an operator action can be taken - decisions that can take 6-12 months to be made. There seem to be increasing levels of red tape to get anything done. I made a request several months ago that all operators be given +o, and was told that this was dependant on the definition of a "Core Op", which still hasn't been meaningfully described and enacted. For some reason, ther
[18:50] <topyli> is this any different from ikonia's earlier items?
[18:50] <Seeker`> no
[18:50] <Seeker`> well
[18:50] <topyli> ok
[18:50] <Seeker`> ish
[18:50] <topyli> moving on
[18:50] <Seeker`> the specific thing I want to talk about now is the core ops
[18:51] <Seeker`> why do we need "core ops" and "normal ops"?
[18:51] <Seeker`> and why has it taken so long to define them
[18:52] <topyli> i suggest we move that a bit further down, as we really need to get the ban list item now before people have to go
[18:52] <nhandler> Seeker`: There was an email sent out about that asking for suggestions on how to define them. There were very few suggestions
[18:52] <Seeker`> nhandler: that doesn't answer why we need them
[18:52] <Pici> And I suspect that Jussi will want to be present for the core-ops discussion.
[18:52] <Seeker`> Pici: well, its been on the agenda for 6 days
[18:52] <Pici> As he and I both have strong feelings about it. (differing opinions I might add)
[18:53] <elkybirthday> Seeker`, his flights have been booked longer
[18:53] <topyli> i see nothing about core ops on the agenda
[18:53] <ikonia> defer it if jussi is a core factor hee
[18:53] <ikonia> here
[18:54] <Pici> topyli: Well my re-org item was actually supposed to be about that...
[18:54] <Pici> Sort of.
[18:54] <topyli> ah ok
[18:54] <topyli> however, let's get to the ban list issue
[18:54] <topyli> [topic] Clearing the ban list
[18:54] <MootBot> New Topic:  Clearing the ban list
[18:55] <nhandler> I've been thinking about this for a while, just never added it to the agenda
[18:55] <Pici> I propose going through the bans on the bantracker and removing all of them that do not have a comment.
[18:55] <Pici> And removing all bans that don't have matches in the bantracker.
[18:55] <nhandler> If we clear the ban lists, we will get some trolls (previously banned) who return. But would could easily re-ban them. However, this would also allow us to remove the hundreds of probably stale/old bans that are just sitting there
[18:56] <elkybirthday> oh finally
[18:56] <ikonia> Pici: I like pici's approach
[18:56] <topyli> agreed, there is a lot of dead weight
[18:56] <ikonia> give the ops 1 week to documentimportant bans
[18:56] <ikonia> then anything that's not important kill
[18:56] <ikonia> sorry my keyboard batteries appear to be dying
[18:57] <Pici> ikonia: Right, we wouldn't do it without notice.
[18:57] <ikonia> Pici: surprising but I'm backing it
[18:58] <nhandler> Is there an easy way to get a list of of such bans Pici ?
[18:58] <topyli> so an email to the mailing list, a week, clean?
[18:58] <Pici> nhandler: Well I can pull down the bans database and query it for all bans that don't have a comment.
[18:58] <Pici> nhandler: So, yes, it is rather easy to do.
[18:59] <Pici> Does anyone have any objections?
[19:00] <nhandler> Nope.
[19:00] <topyli> not me
[19:00] <ikonia> surprisingly not
[19:00] <topyli> ikonia: :)
[19:00] <Pici> Who wants to write it up?
[19:00] <Pici> The email?
[19:01] <topyli> i can do it, but i'll have to consult you over irc first :)
[19:01] <nhandler> Pici: If you can get me a list of bans that would be affected, I can write up the email
[19:01] <Pici> Or does this warrant having a vote/
[19:01] <topyli> oh nhandler is probably more competent
[19:01] <ikonia> don't list the bans
[19:01] <ikonia> just tell everyone a week to document important bans
[19:01] <ikonia> then clear down the rest
[19:02] <Pici> I'll get a number of bans at least.
[19:02] <Pici> the count, rather.
[19:02] <nhandler> ikonia: The bans are all public already. I won't include them in the email, but I want to have it available for OPs who aren't sure which of their bans will be affected
[19:03] <ikonia> thats why we have BT
[19:03] <ikonia> each op log in, and sort your bans out
[19:03] <ikonia> don't need lists sending around
[19:03] <ikonia> better still remove the ones you know aren't important
[19:03] <nhandler> ikonia: But the BT doesn't have an easy way to find bans without comments
[19:03] <ikonia> no, but operators do, you search on your own bans and read them
[19:04] <ikonia> send it out if you want though, just a suggestion
[19:05] <nhandler> ikonia: I wasn't going to send the list of bans with the email, I just wanted to have it to give to individual OPs who ask me (as I'm sure some will) afterwards
[19:05] <ikonia> that shouldn't be a requirement of sending out the email though
[19:05] <nhandler> ikonia: It isn't
[19:05] <ikonia> great,
[19:06] <topyli> so mail. nhandler, you'll send it?
[19:06] <nhandler> topyli: Yeah
[19:07] <topyli> [action] nhandler to send mail about ban list clearing
[19:07] <MootBot> ACTION received:  nhandler to send mail about ban list clearing
[19:07] <topyli> we should be closing. any other items will have to be deferred
[19:07] <topyli> anything really really quick?
[19:08] <Seeker`> I want a meeting scheduled before the next IRCC meeting to discuss the core op issue
[19:08] <Seeker`> I'm pretty sure it was said in the UDS IRCC discussion that it could be brought up today
[19:08] <ikonia> +1
[19:08] <ikonia> this core ops stuff has gone on way too long
[19:08] <topyli> please try and schedule one then, we probably can't do it now
[19:09] <nhandler> The next IRC Meeting is in 2 weeks on the 13th otherwise
[19:09] <topyli> [endmeeting]
[19:09] <topyli> gah
[19:09] <Seeker`> a week today?
[19:09] <topyli> #endmeeting
[19:09] <MootBot> Meeting finished at 14:09.
[19:09] <Seeker`> same time?
[19:09] <topyli> two weeks
[19:09] <topyli> oh, the extra meeting, sorry
[19:09] <Seeker`> no, that was my suggestion for the core-op meeting
[19:10]  * nhandler might not be around that day (possible LoCo event)
[19:10] <Seeker`> well, if it has to wait until all the ircc memebers are around, it will never get discussed
[19:10] <Seeker`> or is that one of the problems that is causing the IRCC to be so slow about everything?
[19:11] <elkybirthday> i suspect it's not helping
[19:12] <Seeker`> Can enough ircc members attend a meeting a week today, at 1800 UTC, to make the meeting quorate?
[19:13] <elkybirthday> *chirp*
[19:13] <Pici> Seeker`: I'll let you know.
[19:14] <Pici> Seeker`: I personally should be free.
[19:14]  * Pici has no life
[19:14] <Seeker`> mmm, well I've just wasted an hour and a quarter of mine waiting for the issue I want to be discussed to be passed over
[19:15] <Pici> There were a number of items that were not discussed.
[19:16] <Seeker`> there were 3 things, two referring to the same thing
[19:16] <Pici> Given unlimited time and everyone present we would have covered them, but we don't have that luxury.
[19:17] <Seeker`> is there ever an occasion when everyone is present?
[19:18] <Pici> Yes.
[19:19] <Pici> I want to get this worked out also, hence my item on the agenda.
[19:19] <elkybirthday> lets move this continued discussion to -ops