=== _cpaelzer is now known as cpaelzer === bashfulrobot_ is now known as bashfulrobot === slashd- is now known as slashd === Kamilion|ZNC is now known as Kamilion === broder_ is now known as broder === diddledan_ is now known as diddledan === tyhicks` is now known as tyhicks === tyhicks is now known as Guest65850 === Guest65850 is now known as tyhicks === tyhicks is now known as Guest1006 [15:01] * slangasek waves [15:03] \o [15:03] #startmeeting [15:03] Meeting started Thu Mar 15 15:03:15 2018 UTC. The chair is slangasek. Information about MeetBot at http://wiki.ubuntu.com/meetingology. [15:03] Available commands: action commands idea info link nick [15:03] [TOPIC] Lightning Round === meetingology changed the topic of #ubuntu-meeting to: Lightning Round [15:03] $ echo $(shuf -e slangasek bdmurray xnox tdaitx doko sil2100 rbalint infinity cyphermox mwhudson rcj philroche Odd_Bloke tribaal fginther juliank) [15:03] xnox Odd_Bloke tdaitx bdmurray cyphermox sil2100 rbalint mwhudson fginther slangasek philroche infinity rcj tribaal juliank doko [15:03] xnox: HELLO [15:03] meeting moved up one hour in europe I think [15:04] IIRC [15:04] maybe we're all confused :D [15:04] sure, per the calendar :) [15:04] I'm not confused about the meeting time, lots of other things though. [15:06] Odd_Bloke is out today [15:06] tdaitx said he might miss the meeting [15:06] bdmurray: [15:06] * OpenJDK 9 as default JDK [15:06] - ongoing fixes and rebuilds [15:06] - syncing & waiting updates from debian [15:06] (done) [15:06] discussion with webops regarding retracer nagios alerts [15:06] uploaded software-properties fix for LP: #1693032 [15:06] uploaded Artful SRUs for (LP: #1690541, LP: #1689668) [15:06] developed test case, uploaded fix for LP: #1693038 [15:06] Launchpad bug 1693032 in software-properties (Ubuntu) "missing dependency on gnome-session-bin" [Medium,Fix released] https://launchpad.net/bugs/1693032 [15:06] Launchpad bug 1690541 in aptdaemon (Ubuntu Artful) "Scrolled windows in update-manager are too small to read" [High,Fix released] https://launchpad.net/bugs/1690541 [15:06] Launchpad bug 1689668 in aptdaemon (Ubuntu Artful) "dialog to resolve config file conflicts can be only one line high" [High,Fix released] https://launchpad.net/bugs/1689668 [15:06] Launchpad bug 1693038 in software-properties (Ubuntu) "needs to support restart on Lubuntu and Xubuntu" [Medium,Fix released] https://launchpad.net/bugs/1693038 [15:06] RU verification of aptdaemon (LP: #1690541, LP: #1689668) [15:07] investigation into retracer hangs (LP and ET) [15:07] discovered cause of retrace hangs (sandbox & glibc issue) [15:07] removed a bunch of core files from swift [15:07] updated retracer process clean up job for gdb call [15:07] investigation into rsyslog log rotation bug (LP: #940030) [15:07] Launchpad bug 940030 in rsyslog (Ubuntu Bionic) "rsyslog stops working after logrotate until restarted" [Critical,Fix released] https://launchpad.net/bugs/940030 [15:07] research into how plymouth --ping works (LP: #1705345) [15:07] found a way to make plymouth --ping hang [15:07] wrote a couple of tools to clean up unnecessary core files [15:07] Launchpad bug 1705345 in plymouth (Ubuntu) "Installing packages hangs on plymouth --ping" [Critical,Triaged] https://launchpad.net/bugs/1705345 [15:07] review of https://code.launchpad.net/~xnox/ubuntu-release-upgrader/lp1749199/+merge/341342 [15:07] commented on LP: #1725359 again [15:07] Launchpad bug 1725359 in ubuntu-release-upgrader (Ubuntu) "release detection relies on lsb-release" [Low,In progress] https://launchpad.net/bugs/1725359 [15:07] manual retracing / review of some Launchpad retracer failures [15:07] done [15:07] email discussion regarding snap errors at errors.u.c [15:08] uh, out of order done marker confused me [15:08] - MIR reviews [15:08] - doc/website/blog writing for netplan [15:08] - grub2 review for initramfs-less fallback [15:08] - [HIGHLIGHT] netplan.io 0.34 release [15:08] - preparing netplan.io 0.34.1: small bugfixes, build easier on other distros [15:08] - [HIGHLIGHT] made ubuntu-archive-assistant its own project [15:08] - investigating lubuntu ubiquity issues [15:08] - investigating casper netboot issues [15:08] (done) [15:08] Argh, timezone madness [15:09] o/ [15:09] sil2100: good timing, you're up :) [15:09] sil2100: your turn [15:09] I'm... I'm not ready! [15:09] At least you're here :) [15:09] (please skip me for now, I'll go last) [15:10] rbalint: [15:11] ok; and no fginther? [15:11] hmm, ok, me then [15:11] um no [15:11] fginther is on site today [15:11] surprise meeting ... [15:12] * juliank looked at unshuffled list... [15:12] * sprint last week; off Monday [15:12] * shepherding cloud kernels into bionic [15:12] * discussions around archive rebuild with retpoline; ultimately decided against based on most current information [15:12] * continued work on +1 maintenance (e.g. ruby), to clear the backlog for 18.04 release [15:12] * worked with tribaal to prepare an MP to grub2 to let systems do opportunistic initramfsless boot with fallback https://code.launchpad.net/~ubuntu-core-dev/grub/+git/ubuntu/+merge/341272 [15:12] (done) [15:13] * Canonical sprint last week in Budapest [15:13] * Release review-gator snap https://dashboard.snapcraft.io/snaps/review-gator/ [15:13] * Monday swap day [15:13] * Cloud image build system maintenance and feature development [15:13] * Cloud image build system vanguard this week [15:13] * Worked on providing 18.04 preview to cloud partners. Users can grap a daily from http://cloud-images.ubuntu.com/bionic/current/ for testing. [15:13] (done) [15:13] * sil2100 is ready [15:13] sil2100: go ahead [15:14] - Last week: sprinting [15:14] - SRU reviews and releases [15:14] - Kernel reviews and releases [15:14] - FFe reviews [15:14] - Publishing the new google-cloud-sdk [15:14] - Working on and testing of proof-of-concepts for grub2 --auto-nvram [15:14] - Minor archive cleanups (stale/failed SRUs, removal of nplan) [15:14] - Trying to reproduce ubuntu-image issues with system-data + content: syntax [15:14] (done) [15:14] rcj: [15:15] * Engineering sprint in Budapest last week [15:15] * Discussed tweaks to improve to cloud-image CVE process [15:15] * Worked on image publication improvements to improve error handling [15:15] * Added squashfs image to final Precise MAAS serial to enable re-installs for ESM (amd64) [15:15] * Reviewing netplan.io site documentation [15:15] * Vacation day on Monday [15:15] (done) [15:17] tribaal: [15:17] tribaal is OoO [15:18] oh, tribaal is not here [15:18] - gnutls28 3.5.18 merge [15:18] - zstd emails [15:18] - got IS to enable https for changelogs.ubuntu.com (for meta-release files), changed update-manager and u-r-u to use that (bug 1744318), made apt(-get) changelog use it too ;) [15:18] - finding bugs on my newly setup bionic on my new laptop :) [15:18] (done) [15:18] oh, he is [15:18] well he's in the channel, how did I miss that [15:18] bug 1744318 in update-manager (Ubuntu Bionic) "changelogs.ubuntu.com should be using HTTPS" [High,Fix committed] https://launchpad.net/bugs/1744318 [15:18] doko: [15:18] - GCC 7 & GCC 8 updates, including cross compilers [15:18] - enabled the sanitzer in GCC on s390x (nobody noticed before ...) [15:18] - cross-toolchain-base updates, built from glibc-2.27 [15:18] - forwarded three GCC & binutils issues upstream [15:18] - python 3.7 beta2 [15:18] - python 3.6 release candidate 1 [15:18] - updated openjdk-10 package [15:18] - new openjdk-11 package \o/ [15:18] - made LLVM 6.0 the default LLVM [15:18] - processed around 10 MIRs [15:18] - fixing autopkg test failures ... ongoing saga [15:19] (done) [15:19] * xnox is very confused [15:19] xnox: do as the calendar says :) [15:19] xnox: daylight shreddings time [15:19] xnox: are you ready to give status? [15:21] • finished fixing keyring/invocation_id in containers both in systemd & kernel [15:21] • moving ruby transition along [15:21] • working on fixing network-manager <-> resolved integration [15:21] • fixing minimal image builds (in progress [15:21] • MIR/components missmatches zstd done [15:21] • done [15:21] * juliank is lucky gnome-online-account calendar stuff is broken so he looked at calendar a lot [15:21] xnox: "finished fixing" - oooh? [15:22] juliank: haha [15:22] any questions on status? [15:22] slangasek, yes; will resend kernel patch & will upload systemd patch. Basically i can make it work either way now. so to be fair kernel patch is redundant, but i know a lot more about keyrings now.... [15:23] xnox: but can you attach gif keychains to your keyrings [15:23] [TOPIC] Bugs === meetingology changed the topic of #ubuntu-meeting to: Bugs [15:24] [LINK] http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-bb-incoming-bug-tasks.html#foundations-bugs [15:24] LP: #1753361 - xnox that looks like a straightforward request? [15:24] Launchpad bug 1753361 in systemd (Ubuntu) "Please set a maximum size for the sytemd journal" [High,New] https://launchpad.net/bugs/1753361 [15:24] huh? [15:25] it does have one [15:25] I'll take #1751011 [15:25] slangasek, it's already set [15:25] It's use up to 10%, and keep 15% free [15:26] there is a hard cap of 4GB as well [15:26] ok. should we take it for more investigation? [15:26] Well, 4.5G is about 4 [15:26] doko: to do what with it? [15:26] doko: we discussed this bug previously and we had nacked changing bash to make qemu-user happy [15:27] in fact, I'm going to take that off the incoming list [15:27] slangasek, set that bug to invalid. [15:28] xnox: ok [15:29] slangasek: hmm [15:29] JFTR: I installed my T480s yesterday evening, and now at 4pm, journal is already using 4GB [15:29] slangasek: that's not recorded in the bug report ... [15:29] but might have been broken chrome :) [15:29] doko: I thought I commented on the bug [15:30] doko: but you also shouldn't be grabbing things from the rls-bb-incoming queue and committing to them individually, as that's an untriaged incoming queue that anyone can throw bugs into [15:30] or I could merge bash ... [15:30] juliank, good! please read your journal to figure out if it is gnome-shell spamming it! [15:31] to me it pukes stacktraces into journal all the time.... [15:31] I had a broken .cache/google-chrome and chrome was logging that multiple times a second :) [15:31] charming [15:31] xnox: is LP: #1662137 still present? you claimed it a year ago, now someone has tagged it for 18.04 [15:32] Launchpad bug 1662137 in systemd (Ubuntu) "16.04 recovery shell works only for two minutes" [High,Confirmed] https://launchpad.net/bugs/1662137 [15:32] (it's a symlink to /run/user/1000/google-chrome which I create with systemd-tmpfiles) [15:32] slangasek, we outht to fix that yes.... [15:32] xnox: ok, claiming/tagging [15:32] slangasek, i believe this is friendly-recovery vs systemd issue, e.g. friedly-recovery should conflict / pause the emmergency shell; or for example, use the emergency shell things [15:34] LP: #1750403 - I think this is already in progress and probably not actually a casper issue [15:34] Launchpad bug 1750403 in casper (Ubuntu) "Live Session - Increased memory usage with preinstalled snap (fails to start with - gnome-session timeout)" [High,Confirmed] https://launchpad.net/bugs/1750403 [15:35] (will punt that for now, so we keep tabs on it) [15:35] LP: #1592405 definitely needs fixing; claiming [15:35] Launchpad bug 1592405 in plymouth (Ubuntu) "plymouth hook in initramfs needs font but doesn't Depend on it" [High,Triaged] https://launchpad.net/bugs/1592405 [15:36] LP: #1601997 ? [15:36] Launchpad bug 1601997 in e2fsprogs (Ubuntu) "Ubuntu 16.10+ installer uses ext4 feature 'metadata_csum' which is incompatible with older (LTS) e2fsprogs" [High,Triaged] https://launchpad.net/bugs/1601997 [15:36] slangasek, my opinion is that there are no actions to take. [15:36] +1 [15:36] I agree [15:37] +1 [15:38] the only place where this is an issue is dual-boot [15:39] someone did bring up the idea of an iscsi disk hosted on 16.04 serving out as a target to 18.04 [15:39] I don't see how dual boot is an issue. It's -new- filesystems, not old ones suddenly changing :D [15:39] the 18.04 would add a filesystem flag that the 16.04 host wouldn't be able to handle [15:39] dunno if that's a realistic case or not, but it's something i hadn't considered before [15:40] nacc: so that falls on its face, and the user remakes the fs with -O -metadata_csum; done? [15:41] nacc, why would iscsi disk server; touch the exported disks? surely what filesystems client puts on iscsi disk, is none of the iscsi disk server problems...?! [15:41] slangasek: yes, that's probably true [15:41] xnox: fair response; I believe NAS-like devices do fs consistency checks periodically, but I might be wrong [15:41] it also wouldn't fail an fsck [15:41] xnox: it was simply a thought that was brought up by a responsive community member [15:41] nacc, no no no no =) that would be bad [15:42] sure. [15:42] it's not like new e2fsprogs can't understand filesystems made with old options [15:42] I think we all agree it's an "expert" use case, and those who do something affected should know to disable metadata_csum [15:42] I think you can even r/o mount it on an older _kernel_ release that does not understand metadata_csum, or am I wrong? [15:42] and 16.04 will get bionic's kernel [15:42] and that, yes [15:42] via hwe [15:42] discussed to death yet? [15:43] but there are people not using hwe :D [15:43] I've marked the bug wontfix [15:43] LP: #1682637 [15:43] Launchpad bug 1682637 in friendly-recovery (Ubuntu) "during recovery mode, enable network failed due to /etc/resolv.conf not being present" [High,Triaged] https://launchpad.net/bugs/1682637 [15:43] xnox probably wants this one too :) [15:43] sure [15:48] ok there are still a few more in the queue but I think that's enough time spent on these for now [15:48] [TOPIC] AOB === meetingology changed the topic of #ubuntu-meeting to: AOB [15:48] anything else? [15:49] Nope [15:49] Nope [15:49] #endmeeting === meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds: Please leave swords by the door | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendars | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology [15:49] Meeting ended Thu Mar 15 15:49:54 2018 UTC. [15:49] Minutes: http://ubottu.com/meetingology/logs/ubuntu-meeting/2018/ubuntu-meeting.2018-03-15-15.03.moin.txt [15:49] thanks, all! [15:58] o/ [15:58] Thanks! [16:24] wxl, flexiondotorg, elacheche, jose, ahoneybun, marcoceppi: we have a meeting today. I might not have access to my computer on the next 30 minutes, so can one.of you please send an email to the list with a reminder? [16:25] also, I will be able to lead only the first 30 minutes, then somebody else will have to do it. I'm running to get my machine ready, sorry. [16:35] elopio2: Roger that! :) [16:47] nop, my machine is still very unhappy [16:47] any takers for leading today? [16:48] We'll figure that out elopio-webchat :) [17:01] elacheche: I think you agreed to run this one, right? :-) [17:02] flexiondotorg: OK [17:02] meeting time :) [17:03] marcoceppi, jose, wxl, flexiondotorg, ahoneybun and elopio-webchat all here? [17:03] o/ [17:03] yep [17:04] #startmeeting Community Council meeting, 20180315 [17:04] Meeting started Thu Mar 15 17:04:04 2018 UTC. The chair is elacheche. Information about MeetBot at http://wiki.ubuntu.com/meetingology. [17:04] Available commands: action commands idea info link nick === meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds: Please leave swords by the door | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendars | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | Community Council meeting, 20180315 | Current topic: [17:05] We start the meeting, in the meanwhile I am sure the marcoceppi and ahoneybun and jose will show up :) [17:05] #topic report since last meeting === meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds: Please leave swords by the door | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendars | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | Community Council meeting, 20180315 | Current topic: report since last meeting [17:05] Do we have any news about things we discussted last time? [17:06] I'm around [17:06] Hey ahoneybun [17:06] I didn't finish my task. [17:06] Sorry, lots of things moving here. [17:07] But I should be home for next meeting, so I'll take the same action item again, review the CC meetig pages [17:07] s/meeting/wiki [17:08] elopio-webchat: IS that the actual wiki or wiki posts on the Hub? [17:08] flexiondotorg: The actual wiki [17:09] I didn't advanced on defining what we use each ressource for, I will send a mail about that so you can help me instead of waiting for having some spare time to talk to you via IRC [17:09] flexiondotorg: elacheche made a list of pages on the wiki. We need to review them, and see what can be moved, droped, updated... [17:09] Understood. Was just confirming. [17:10] #action elacheche will email the list of ressources to discuss/debate the need of each via the ML [17:10] ACTION: elacheche will email the list of ressources to discuss/debate the need of each via the ML [17:11] oh, the other thing was that I sent an email to the list, mentioning our decision from the last meeting about missing this meeting without an excuse [17:11] #action elopio still reviewing the wiki pages [17:11] ACTION: elopio still reviewing the wiki pages [17:11] we start counting today, looking at the summary posts. [17:11] elopio-webchat I confirm we got that :) I hope that everyone noticed that while readingthe email [17:12] I think that not attending, and not even reading the summaries makes it twice as bad :D [17:13] Do we have other news? [17:13] not here [17:14] OK, should we move then? [17:14] Yep [17:15] * elacheche like to add 2 more subjects later, one about taking decisions (as example the case of the Ubuntu Europe Federation thread), and the other about the news team [17:16] I just shar ed that now because I know I will forget it later.. [17:16] ok [17:16] Next topic [17:16] #topic Bold bug triaging - issues with contacting a LP user Community Council === meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds: Please leave swords by the door | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendars | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | Community Council meeting, 20180315 | Current topic: Bold bug triaging - issues with contacting a LP user Community Council [17:17] I sent an email to him/her last week [17:17] Let's start by sharing the HUB thread again → https://community.ubuntu.com/t/bold-bug-triaging-issues-with-contacting-a-lp-user/4334 [17:17] dino99 right? [17:17] one week without a reply is more than enough time. So next action for me will be to contact the launchpad team to deactivate the account. [17:17] And Mark had this to say: "Yes, I think we can be firm about an expectation of engagement if folks are active." [17:17] they recently just did another round of their thing [17:17] wxl: yes [17:18] yes. It could be that the email is wrong, or anything. The idea is that deactivating the account should prompt them to talk to us, and then we figure out if it was a misunderstanding or a CoC violation. [17:18] YOu can't properly participate on LP with broken email. [17:18] So deactivating for that alone is reasonable. [17:18] +1 [17:18] if they just disappear, then the problem is solved too. If they make another acccount and continue, then it's a clear violations and we follow that other path. [17:19] Who'll contact the LP team? [17:19] i think we should just send this to canonical sysadmin [17:19] no? [17:19] hmm [17:19] Hey jose [17:19] acting as the community council, they should be able to just follow suit [17:20] LP Owner can deactivate the team [17:20] It depends on who's administrating the LP.. a LP team or just canonicals sysadmins [17:20] however, they need proof of the discussion/matter in order to do that [17:20] there is a launchpad owner team in launchpad who has the current launchpad admin [17:20] and we can send them an email if it's a private matter [17:20] great then, jose I think the HUB link and the log of this current session can be that proof [17:21] I'll take care of finding the right person, contacting them with links, and follow up [17:21] and documenting on the hub for future reference. [17:21] Sorry elopio-webchat I don't agree with that.. [17:21] actually, gimme a sec and I'll give you a link to the team [17:21] elacheche: tell me more :) [17:22] I think someone else should do the task, we should share the tasks, you already take care of other tasks [17:22] ah, I was taking it because I started [17:22] I'm happy to do it, I'm already halfway there anyways [17:22] I have no particular interest in doing it myself. Anybody, feel free to take it. [17:23] Great! elopio-webchat share what you have with jose :) I don't want any of use to have too much tasks, because we can't blame hime later if there is no progress on multiple tasks :) [17:23] Looks like jose has grabbed that action :-) [17:24] I have contacted them with no reply. That's what I have. The discussion is on the hub, and the summary of this meeting. [17:24] yep, will share progress when I have it! [17:24] jose: just please make sure to make a post on the hub explaining how to deactivate a user. [17:24] #action jose will find the good person to deactivate the LP user account, this log can be the proof with the HUB URL [17:24] ACTION: jose will find the good person to deactivate the LP user account, this log can be the proof with the HUB URL [17:24] And Marks reply on the ML. [17:24] flexiondotorg: That was a surprise x) [17:25] Do you have any other comments about this topic or should we move to the next one ? [17:25] Move on. [17:25] #topic Review, triage, and fix Code of Conduct bugs - @wxl === meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds: Please leave swords by the door | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendars | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | Community Council meeting, 20180315 | Current topic: Review, triage, and fix Code of Conduct bugs - @wxl [17:27] ping wxl [17:27] oh hey sorry :) [17:27] No problem, I know you're @work [17:28] so during GCI i made a task to have students sign and file bugs on the CoC [17:28] it was actually very successful, even with the fact that many of them were using GPG for the very first time [17:28] i could probably fix the directions a bit to make it a little bit easier, but that's not my point for this topic [17:28] the topic is we now have a lot of bugs and we should go through them and see where we can improve the CoC [17:29] that's not going to be a five minute thing, i don't think [17:29] so i was going to suggest perhaps we schedule a time to get together expressly for that purpose [17:29] thoughts? [17:29] wxl: I am sorry, can you please explain more the task? Or share a bug link [17:29] I don't think all the bugs need to be actioned. [17:30] not actioned, but at least triaged, I'd say [17:30] So just need review and explaination as to why we aren't incorporating the changes. [17:30] how many bugs? [17:30] elacheche: the task is irrelevant. what came out of it-- bugs against the CoC-- is what we need to worry about [17:30] we currently have 23 new bugs [17:31] i think some of them are actually valid, so saying we're not going to incorporate the change may not be appropriate for all of them [17:31] ok [17:32] I think we can meet again and triage those together as jose & wxl suggested [17:32] so do we want to schedule a time now to do that? [17:33] I'd prefer a weekend, but not sure if you can do that [17:33] I'm travelling around the US right now for work, so my schedule is a bit hectic [17:33] i'm fine with that [17:33] Emm.. What about starting a ML thrread about this.. So we don't have to be all online in the same time and we can discuss those [17:34] i don't love that idea as it will take us much longer [17:35] maybe we can meet up with those who are available, and then send a summary to the ML for commenting, for those who weren't available? [17:36] that seems reasonable. or we could just all take it upon ourselves to have the discussion within the bug reports themselves [17:36] wxl: OK, as you lead the task you pick the time and others will try to join you (remeber we have different TZs ;-) ) [17:36] yes, except hub instead of mailing list please. [17:37] if we're just going to make it a non-realtime public chat, let's just do it on the bug reports themselves [17:37] which means that everyone has an action to go get on that [17:38] OK wxl that seems the good choice [17:38] +1 [17:38] agree [17:38] there ya go then :) [17:38] wxl: can you share the url please? [17:38] So, is the action: Triage CoC bugs and discuss them on LP? [17:39] yep [17:39] elopio-webchat: https://bugs.launchpad.net/ubuntu-codeofconduct [17:39] thanks [17:39] #action ALL CC will Triage CoC bugs and discuss them on LP? → https://bugs.launchpad.net/ubuntu-codeofconduct [17:39] ACTION: ALL CC will Triage CoC bugs and discuss them on LP? → https://bugs.launchpad.net/ubuntu-codeofconduct [17:40] Any other thoughts? [17:40] We still have 20 min before ending the meeting [17:40] We move on then.. [17:41] #topic Clearly define governance seats, terms, and quorum - @wxl === meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds: Please leave swords by the door | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendars | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | Community Council meeting, 20180315 | Current topic: Clearly define governance seats, terms, and quorum - @wxl [17:41] I think you're talking about the UMB quorum? [17:41] i mean for all the governance boards, but especially the umb and lc which have faced issues over time of understanding what's what [17:42] robert's rules don't really help in re: quorum as it's basically like "the maximum number of people you'd expect might show up given the weather" or something ridiculous like that :) [17:42] is we have x number of seats, we should be able to define y number of people to make quorum [17:42] but that's the other problem: we don't even knwo what x number of seats is sometimes :) [17:43] Afaik, the quorum was always 4 members, I remember that I read it somewhere + some old UMB announced it during meetings when I was joining the meetings before I become a Ubuntu Member, later when I joined the UMB we used that too [17:43] I may dig the old wikis again to try to find it (reading some diffs can helo I guess) [17:44] so that would be 4/10 which is not a majority === kees_ is now known as kees [17:44] i've never seen any of that documented anywhere for anyone [17:44] hmm. in general, I'd say quorum for meetings should be 1/2, and for voting 2/3, but that's just me [17:45] wxl: Let's don't forget that not all the 10 members should be present at the same timen that's why the UMB have multiple slots.. not only for candidates, but for board members too [17:45] so you're saying a majority then, jose? [17:45] yes. but now, the UMB is a special case... [17:45] elacheche: true. we'd need to define it based on that, i.e. there would have to be a minimum number of folks at each slot [17:45] I remember beforehand there used to be two UMB teams [17:45] s/at/signed up for/ [17:46] one for the 10 and another for the 22 UMBs. then, both teams in a general UMB team for lp admin purposes [17:46] also i'll add if "4" is the magic number then that means that most of the LC needs to be there: 4/5 [17:47] and for us that's not a majority either: 4/8 [17:47] wxl: True, when I signed up for the UMB seat I signed up for all the slots, same for multiple others, because we are near the UTC TZ [17:48] that might be a good reason to suggest more than one team [17:48] let's imagine the situation where you leave-- that means both boards are affected, but we might get a replacement that can only do one [17:48] so then we need to add another person [17:49] i think it would be better to have two teams but either team can participate in the other one [17:49] Just a side note.. I think that I read in one of the meetings (yeeaaaaaaaaaaaars ago, I don't know what/when) that CC members can help if the quorum is not enough, like if the UBM need 1 more person, and there is a CC around he can vote [17:49] I am note sure if that's documented somewhere or not too [17:49] right. and i've seen that happen... and i've seen it not work because they're not around [17:50] my understanding of it was that the cc as a whole was entitled to one vote [17:50] so if you were down 2, even with two cc members, that wouldn't get you there [17:50] but again, this all needs to be defined and most importantly, documented [17:50] OK, we should document all that somewhere for future CC [17:50] it sounds to me that the first step is to dig out the current rules. Then, figure out if we need to add rules or modify the process entirely. [17:51] That ^ [17:51] Which I was just hunting for. [17:51] i've never seen the rules but elacheche seems to think he has [17:51] so maybe next action, elacheche goes hunting? [17:52] wxl: I think I saw them in here during some meetings before I become a Ubuntu member, and saw some on the wiki.. That's why digging the wikis will be a good start [17:52] OK, I will do that.. [17:54] #action Get in touch with current and former board members, ask about seats, terms, and quorum, and try to find writen evidence on the Wiki or IRC/MLs logs [17:54] ACTION: Get in touch with current and former board members, ask about seats, terms, and quorum, and try to find writen evidence on the Wiki or IRC/MLs logs [17:54] #action elacheche will get in touch with current and former board members, ask about seats, terms, and quorum, and try to find writen evidence on the Wiki or IRC/MLs logs [17:54] ACTION: elacheche will get in touch with current and former board members, ask about seats, terms, and quorum, and try to find writen evidence on the Wiki or IRC/MLs logs [17:55] We're late.. Any other suggestions, or should we move? [17:55] Next.. [17:55]