[18:58] <slashd> o/
[18:59] <sil2100> o/
[19:00] <rbasak> o/
[19:00] <marcustomlinson> o/
[19:01] <slashd> I'll be back in 5 minutes-ish but I'll be attending the meeting
[19:01] <sil2100> We still need one more for quorum
[19:01] <sil2100> But even if we don't have quorum, I'd like us to discuss the DMB elections
[19:02] <rbasak> As usual I'd like to call time and disappear if we don't get quorum by 1910 as this is my evening.
[19:07] <sil2100> Ok, since it's unlikely we'll get quorum today, just wanted to bring up the topic of the needed DMB elections for the two seats we have free
[19:08] <rbasak> Clearly we need an election
[19:08] <rbasak> I'm not sure how that's normally operated
[19:08] <rbasak> Would it be a TB member usually?
[19:08] <sil2100> We have it in the KnowledgeBase, it's us that start the election
[19:08] <sil2100> But the TB then adds the elected people to the team
[19:09] <sil2100> So question now: any volunteers to drive the election?
[19:09] <slashd> I agree to go back on election, last time was in 2017 anyway
[19:09] <slashd> IIRC
[19:09] <sil2100> I guess I could drive it, but I'm worried it might slip for after the release
[19:09] <rbasak> We could just agree to do it after the release
[19:09] <kenvandine> How often do you not get a quorum?
[19:09] <rbasak> As we know that people are busy before
[19:09] <sil2100> kenvandine: very often
[19:10] <sil2100> kenvandine: we're discussing ways to make it better
[19:10] <ddstreet> quorum is at 45% so far this year
[19:11] <slashd> sil2100, I can have a look at it starting next week or we can wait after the release
[19:11] <slashd> release is soon anyway
[19:12] <sil2100> Ok, let's do it after release
[19:12] <slashd> lgtm
[19:19] <sil2100> marcustomlinson: ok, so sadly it seems we can't really review your application - let's try doing that on the next meeting
[19:20] <sil2100> We're working on some process changes to make the lack of quorum less of an issue
[19:20] <marcustomlinson> sil2100: alright, better luck next time hopefully :)
[19:20] <sil2100> Hopefully next time we might not have the same issue
[19:20] <slashd> marcustomlinson, very sorry
[19:21] <marcustomlinson> I appreciate that you guys showed up at least ;)
[19:21] <marcustomlinson> I understand, no worries
[19:22] <sil2100> Thanks for appearing everyone o/
[19:22] <slashd> \o
[22:45] <MajB> I just scheduled a re-verification for the Ubuntu-Arizona Local Community Team on the LoCo Council's Agenda page but it states that the next meeting is in August.  Obviously it hasn't been updated.  Is there something else that I need to do to ensure that our team gets voted on at the November or December LoCo Council meeting.
[22:46] <sarnold> MajB: you'll probably need to talk to someone specific about it -- not many people pay attention to this channel outside of the meetings they themselves go to
[22:48] <MajB> The reason I brought it up is we had some scheduling problems back in 2015 and again in 2017 and I wanted to get ahead of any possible problem .
[22:49] <dax> i haven't dealt with the LC in years and years, but back when i did loco-council@lists.ubuntu.com was the best way of getting a message to all of them
[22:49] <MajB> Thank you
[23:09] <MajB> Well that email goes to a mod who will decide if it should be forwarded. :)
[23:11] <dax> yup, everyone on the LC is a mod of that list, so they should have gotten an email :)
[23:12] <MajB> Sounds good to me