=== Ursinha is now known as Ursinha-afk === Ursinha-afk is now known as Ursinha === vladk|offline is now known as vladk === vladk is now known as vladk|offline === vladk|offline is now known as vladk === vladk is now known as vladk|offline === vladk|offline is now known as vladk === vladk is now known as vladk|offline === psivaa is now known as psivaa-afk === greyback is now known as greyback|food === vladk|offline is now known as vladk === doko_ is now known as doko === greyback|food is now known as greyback === psivaa-afk is now known as psivaa === vladk is now known as vladk|offline === vladk|offline is now known as vladk [14:54] * xnox goes to grab a coffee [15:00] * slangasek waves [15:00] hello [15:00] * mvo waves as well [15:00] * barry wavers [15:01] o/ [15:01] #startmeeting [15:01] Meeting started Thu May 15 15:01:48 2014 UTC. The chair is slangasek. Information about MeetBot at http://wiki.ubuntu.com/meetingology. [15:01] Available commands: action commands idea info link nick [15:01] [TOPIC] lightning round === meetingology changed the topic of #ubuntu-meeting to: lightning round [15:01] $ echo $(shuf -e barry doko stgraber jodh bdmurray slangasek cjwatson xnox caribou infinity mvo) [15:01] barry caribou bdmurray stgraber infinity mvo jodh doko xnox slangasek cjwatson [15:02] \o/ [15:02] mostly working on debian bug #732703. i have a full working stack, discussed with debian pythonistas on various forums, and ready to be applied and uploaded. currently writing some documentation, and then will release new debian packages for DPMT maintained packages, with bugs and diffs for non-team maintained packages. should have all this finished today, modulo interacting with maintainers and nmus. [15:02] Debian bug 732703 in python3.4 "python3.4: cannot create a virtualenv" [Normal,Open] http://bugs.debian.org/732703 [15:02] other: patch piloted. debian bug #744300 + SRU'd to trusty. LP: #1317660. scripttest 1.3-1. python-pip 1.5.5-1. [15:02] Debian bug 744300 in pexpect "missing dependency on dh-python" [Wishlist,Fixed] http://bugs.debian.org/744300 [15:02] Launchpad bug 1317660 in pexpect (Ubuntu) "[SRU] Bug: AttributeError: 'error' object has no attribute 'errno'" [High,In progress] https://launchpad.net/bugs/1317660 [15:02] meet with q/a folks re: system-image testing for utopic. need to get nose2-conv packages in debian (debian bug #740195) so that i can capture coverage output for q/a dashboard. [15:02] Debian bug 740195 in wnpp "ITP: nose2-cov -- A coverage plugin for the nose2 Python testing framework." [Wishlist,Open] http://bugs.debian.org/740195 [15:02] todo: triage and planning utopic work for system-image. [15:02] done [15:02] * makedumpfile 1.5.6 now published in Debian unstable [15:02] * Worked on adding remote kernel dump functionality to Debian/Ubuntu. Now working with SSH & NFS [15:02] * Worked on Bug 1313602 now waiting for merge proposal [15:02] * Started initial work for PPU application to the DMB [15:03] bug 1313602 in nova-cloud-controller (Juju Charms Collection) "Nova-cloud-controller charms failed to sync ssh keys between compute nodes" [Undecided,In progress] https://launchpad.net/bugs/1313602 [15:03] done [15:03] research into successfully retried retaces by the error tracker [15:03] research into indicator-sound retracing failures [15:03] updated the daisy retracer to be more informative when failing to retrace [15:03] irc discussion regarding RecoverableProblem duplicate signatures [15:03] reported apport bug 1319099 regarding whoopsie-upload-all not uploading RecoverableProblems [15:03] bug 1319099 in apport (Ubuntu) "whoopsie-upload-all does not upload RecoverableProblem reports" [High,Fix committed] https://launchpad.net/bugs/1319099 [15:04] reported apport bug 1319477 regarding whoopsie-upload-all waiting period [15:04] bug 1319477 in apport (Ubuntu) "whoopsie-upload-all waits for crash files to upload that have failed to upload" [High,New] https://launchpad.net/bugs/1319477 [15:04] replied to mailing list thread regarding the error tracker [15:04] research into phased-update of nautilus (manually set to 100%) [15:04] helped infinity tracker down errors made by the phased updater [15:04] testing of whoopsie on the nexus 4 [15:04] reported bug 1319213 regarding android dual boot and files in /var/crash/ [15:04] bug 1319213 in android (Ubuntu) "keeping user data keeps files in /var/crash which makes little sense" [Undecided,New] https://launchpad.net/bugs/1319213 [15:04] submitted apport merge proposal fixing bug 1316841 [15:04] bug 1316841 in Daisy "apportcheckresume does not create a duplicate signature" [Medium,Triaged] https://launchpad.net/bugs/1316841 [15:04] submitted merge proposal with fixes for bugs 1319099, 1316763 [15:04] SRU verification of bug 1277706 (failed?) [15:04] SRU verification of apport upload to trusty-proposed [15:04] bug 1316763 in apport (Ubuntu Trusty) "bucketing of recoverable problems is done poorly" [Medium,Triaged] https://launchpad.net/bugs/1316763 [15:04] bug 1277706 in ubiquity (Ubuntu Precise) "ubiquity in precise-updates, doesn't have tight enough dependency on python-apt leading to crashers" [High,Fix committed] https://launchpad.net/bugs/1277706 [15:04] uploaded apport fix for bug 1235436 [15:04] bug 1235436 in apport (Ubuntu) "/etc/init/apport-noui.conf is non-functional on the phone" [Critical,Fix released] https://launchpad.net/bugs/1235436 [15:04] bug bot modifications for mythbuntu installer bug, flightgear upgrade failure [15:04] added 13.10 iso verification code to the bug bot [15:04] ran bug bot against ubiquity bugs for 13.10 isos [15:04] updated pMRE report for vlc, sent email to tech board [15:04] patch pilot [15:04] ✔ done [15:05] stgraber is off today, so presumably not reporting despite being in the channel [15:06] looks like mvo is next [15:06] Shorter week, 2*0.5 days off [15:06] Did: [15:06] - click: bug triage, create some feature/bugfix branches, ride the CI train for the first time (yeah!) [15:06] - hwe-eol: work on corner cases in detection script [15:06] - merges: look at some old-merges [15:06] - misc: explore unity8 in the desktop [15:06] - apt: work on abi-break branch, bugfix/ensure-optional-targets, bugfix/update-progress-reporting, bugfix for robustness on corrupted Translation-$lang files [15:06] Todo: [15:06] - hwe eol [15:06] - sprint preparing [15:06] (done) [15:06] slangasek: no infinity today? [15:06] * foundations-1305-upstart-work-items: [15:06] mvo: I've pinged him, but he's not in the channel so go ahead [15:06] - cgroup+async support: [15:06] - wrote a new test to ensure jobs not auto-started until cgmanager available. [15:06] - Fixed a async re-exec issue. [15:06] - Currently working on another re-exec issue whilst [15:07] * other: [15:07] - Out tomorrow and Monday. [15:07] Ꜯ [15:08] Oops! '- Currently working on another re-exec issue whilst working with xnox on async branch re-jiggling' :) [15:08] - work on GCC warning regressions PR 61106 and 61126 [15:08] - work on GCC 4.8.3 updates before the upstream release [15:08] - fix gnat link issues on AArch64 [15:08] - openjdk-8 packaging [15:08] (done) [15:08] * upstart/async: [15:08] - completing refactoring async branch [15:08] - all/most code is merged into lp:upstart/async staging branch [15:08] - everything is synchronous in that branch at the moment, next [15:08] starting flipping to async process-by-process [15:08] * gcc-4.9: [15:08] - trianged / sent patches for 10 FTBFS bugs [15:08] * python2/autopilot: [15:08] - DONE autopilot1.5 has landed [15:08] - TODO camera, gallery, sudoku apps declare py3 compat in their [15:08] trunks, but not on the images yet. [15:08] - TODO make python2-autopilot depend on python2-evdev. [15:09] * insserv/systemd: [15:09] - ongoing in-distro init systems improvements, e.g. UPSTART_SESSION [15:09] in the environment should no longer affect package [15:09] configuration/installation. Progressing with pitti/vorlon to enable insserv. [15:09] * was off mon-wed [15:09] .. [15:09] * short week, out sick this past Monday [15:09] * Java engineer hired, starts Monday [15:09] * prepping for Malta [15:09] * discussing UEFI on arm64 with the hyperscale and server teams [15:09] * TODO: [15:09] * look at systemd integration with nfs-utils and rpcbind (Debian bug #622394) [15:09] Debian bug 622394 in nfs-common "nfs-common: breaks systemd - dependency cycle in require-start leads to removal of critical jobs" [Normal,Open] http://bugs.debian.org/622394 [15:09] * more malta prep [15:09] (done) [15:09] xnox: image #29 is still pulling in py2. [15:09] livefs in LP: [15:09] - Worked on a scheme to pass additional arguments through. I've uploaded the livecd-rootfs part of this, although I'm holding off on my Launchpad code for now since it probably wants separate review and isn't needed for the initial deployment. [15:10] - Finished writing browser tests and pushed https://code.launchpad.net/~cjwatson/launchpad/livefs-browser/+merge/219505. [15:10] - Got initial cdimage code working. [15:10] - Did a successful end-to-end ubuntu-touch build with local cdimage and Launchpad instances! [15:10] - Released and got webops to deploy launchpad-buildd bug fixes. [15:10] barry: correct, as it should. [15:10] A few merges. Synced r-base, which unblocked a pile of stuff. [15:10] Reviewed some of Michael's click changes, although he is currently outpacing me. Helped with some CI Train handling. [15:10] xnox: why did you send patches for the gcc-4.9 bugs instead of NMUing? :) [15:10] Fixed libfreehand/ppc64el FTBFS. [15:10] To do before Malta: finish cdimage/Launchpad integration; experiment with autopilot on x86 emulator; respond to any LP review feedback; sort through some more of Michael's click branches [15:10] .. [15:11] slangasek: because they ain't yet RC. And i've been told off about 0-day NMU for "good" reasons, when it's "not RC yet". [15:11] xnox: hmm. didn't the ap changes to remove py2 land in #29? [15:11] xnox: ah, well, that's what delayed NMUs are for, then.. .but ok :) [15:11] slangasek: joined Debian GNOME team to do "team uploads" of my pending patches. Most of gcc-ftbfs are not team managed packages =( [15:11] xnox: python2> what do we need to do to drive this to completion? how do we get these apps from trunk to image? [15:12] slangasek: i was expecting for that to just happen whilst i was away. but it didn't. [15:12] slangasek: will poke people about it. [15:12] ok, cool [15:12] note that i just dropped the thos python2 packages in touch [15:13] barry: so in autopilot-touch metapackage, i still explicitely hold on to py2, because i can only drop that once all clicks on the image correctly declare their py3 alignment. [15:13] (test image is building right now) [15:13] *the two [15:13] ogra_: so you're breaking the click apps that are still missing their py3 declarations? [15:13] python2-autopilot and python2-evdev [15:13] slangasek, i had three independed people ping me to drop these two packages today [15:13] maybe we can talk about this after the meeting? [15:14] ogra_: you will fail autopackage tests in gallery-app, sudoku-app and camera-app. As well as breaking all the deb based python2 autopackage tests. [15:14] which i now did [15:14] ogra_: well, you should talk to TIL first. [15:14] robru even with high urgency [15:14] referring to barry [15:14] ok, deep topic, let's take this out of the meeting :) [15:14] * ogra_ is in meetings for the next 2h and then gone [15:15] but we definitely should not be pulling python2 off the images before the click packages are all resolved per https://blueprints.launchpad.net/ubuntu/+spec/core-1311-python3-roadmap [15:16] [TOPIC] AOB === meetingology changed the topic of #ubuntu-meeting to: AOB [15:17] anything else here? [15:17] everyone ready for the sprint? [15:18] * mvo nods [15:18] GCC bug squashing tomorrow and Saturday! [15:19] reminder to put sprint agenda items on https://wiki.canonical.com/UbuntuEngineering/Sprints/ClientSprint-May2014/Foundations please [15:19] yep [15:20] ok then [15:21] short meeting - thanks all, now let's get the python sorted on the phone images :0 [15:21] #endmeeting === meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology [15:21] Meeting ended Thu May 15 15:21:55 2014 UTC. [15:21] Minutes: http://ubottu.com/meetingology/logs/ubuntu-meeting/2014/ubuntu-meeting.2014-05-15-15.01.moin.txt [15:21] thanks [15:21] thanks! [15:21] thanks! [15:21] thanks [17:00] hi pen [17:00] o/ [17:00] o/ [17:00] #startmeeting Community Council [17:00] Meeting started Thu May 15 17:01:09 2014 UTC. The chair is pleia2. Information about MeetBot at http://wiki.ubuntu.com/meetingology. [17:00] Available commands: action commands idea info link nick === meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | Community Council Meeting | Current topic: [17:00] * pleia2 rounds up usual suspects [17:01] o/ [17:01] o/ [17:01] hi lyz, michael [17:01] o/ [17:01] #chair elfy cprofitt dholbach czajkowski [17:01] Current chairs: cprofitt czajkowski dholbach elfy pleia2 [17:01] Hiya :) [17:01] hiza [17:01] #chair mhall119 [17:01] Current chairs: cprofitt czajkowski dholbach elfy mhall119 pleia2 [17:01] there we go [17:02] https://wiki.ubuntu.com/CommunityCouncilAgenda [17:02] oh, that was unexpected [17:02] oh, we're all chair, ok then [17:03] who's up first? [17:03] so first up on our agenda is Membership Board [17:03] #topic Membership Board catch up === meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | Community Council Meeting | Current topic: Membership Board catch up [17:03] I see Pendulum and s-fox here from the board, anyone else? [17:04] IdleOne might be coming (I've just poked him to check) [17:04] good to see you again Pendulum, haven't chatted with you in a long time :) [17:05] how have things been going on the Membership Board? :) [17:05] Generally okay, few items we'd like to go over with the cc though [17:05] In general things have been pretty good. [17:05] shall we talk about quorum? [17:05] oh hi [17:06] yeah, quorum seemed to be the biggest obstacle [17:06] sure, okay [17:06] that is, membeship meeting without enough people to actually vote on the applicants [17:07] In general, I think that's been improving. [17:07] I don't think that's the issue.. I think the issue is how many votes are required for an approval [17:07] it has been improving, but we're finding it hard to decide if someone is approved or not. [17:07] cjohnston: that's really dependent on how many people are there to vote though [17:07] some of us were chatting a bit about it since you last brought it up, and I can't remember who brought up the idea, but one approach we talked about was that we could ask applicants to hand in their application earlier (let's say a few days), so members of the board who can't make it could send in their vote by mail [17:07] for example if everyone votes +0 and then someone goes +1 it is technically approved. [17:08] it just doesn't look right with the lack of support [17:08] another idea was that if there weren't enough members of the board around to make a decision during the meeting, the vote could be taken to mail [17:08] ... which is what the DMB has been doing [17:08] If we do the voting by mail, we might as well not have meetings and just do all voting by mail [17:08] We have been moving applications when there isn't quorum to e-mail [17:08] the advantage of both ideas is that we wouldn't get into voting arithmetics :) [17:08] so let's tackle these one at a time, quorum first then what technically consitutes approval [17:08] Pendulum: so the voting and discussions continue over email after the meeting? [17:09] cjohnston, I disagree - it's always worth having a chat and resolving questions which might be not answered on the wiki [17:09] mhall119: If there isn't quorum it does [17:09] cjohnston: no, DMB still has public meetings so people can apply in public and everything is recorded [17:09] dholbach: in that case, the people who have already voted have voted without those answers [17:09] Pendulum: out of the number of times the discussion and voting went to email, how often was a final vote taken? [17:09] cjohnston, some might already know that person, etc [17:10] It could sway my vote, but was never given the opportunity to sway someone elses vote [17:10] cjohnston: afaik on list voting happens after the meeting [17:10] pleia2: +1 [17:10] pleia2: that wasn't dholbach's suggestion [17:10] mhall119: I think we have had final votes on all of them. Very few in those situations have been rejected [17:10] ok, so that's been effective then, that's good to hear [17:10] We do have some meetings where a member who isn't going to make it has let us know in advance either on IRC or the mailing list what their vote would be. [17:11] We also, I think, have really mostly been making qorum [17:11] cjohnston: dholbach was suggesting votes via email as a fallback when you can't attend the meeting, not at the preferred method [17:11] mhall119, thanks for clarifying this [17:11] and it sounds like that's already been happening [17:12] Things have improved a lot in recent meetings, especially with regards to voting on the mailing list in advance if you are likely to be able to unattend [17:12] so it sounds like quorum typically isn't the issue, mostly it's a numbers thing, if quorum to hold a meeting is 4 does three +1s and one -1 equal approval [17:12] here [17:12] My impression is that it's the 12:00 UTC board that is having more problem, but that may just be due to my being on that board :) (the members who never show on that board are among those expiring at the end of the month) [17:12] pleia2: exactly [17:12] so do we need to officially endorse email votes as a fallback, or can we just say "carry on" with doing it? [17:12] "ask applicants to hand in their application earlier (let's say a few days), so members of the board who can't make it could send in their vote by mail" what is the point of turning them in earlier if the voting doesn't start until later? [17:12] mhall119: ^ [17:12] cjohnston: so people have longer time to read them [17:13] cjohnston: I read that as voting by mail after the meeting, not before [17:13] then they don't need to turn them in earlier. [17:13] cjohnston: shouldn't applicants already submit their application early enough for board members to review before the meeting? [17:13] I believe there already is a requirement [17:13] currently it's 24 hours on the wiki [17:13] so they have time to read app, read meeting, send in vote; I think the only time there would be an exception is if they know something specific about the applicant that would make them reject them regardless [17:13] so then there's no change to what's happening, just making what's happening officially approved [17:14] that sounds good to me :) [17:14] i do a review roughly 3 or 4 days before the meeting in my own time. i have been known to be a slow reader and also be sure i understand the applicant [17:14] pleia2: or when they would approve them regardless [17:14] mhall119: yeah [17:14] anyway, quorum [17:15] my impression was always that it was 4 to hold a meeting, then a majority of those folks had to +1 [17:15] a majority had to vote +1, or the the final tally had to be >= +1? [17:15] We all agree on the 4.. it's the latter part as mhall119 says [17:15] majority had to vote +1 [17:15] so +3-1 would be approved? [17:16] or a minimum of 4 +1's regardless of final tally [17:16] but when I was on the board it wasn't usually an issue because we had a back channel where we typically came to a consensus [17:16] if someone felt really strongly about a -1, we all took that pretty seriously [17:16] we end up with +0 and +1 normally in this situation [17:16] In most cases we do come to consensus [17:16] cjohnston: is that because of a lot of +0s, or because of a balance of +1 and -1? [17:16] Unless I am mistaken we had an applicant who was technically approved on the 22:00 UTC meeting but we were concerned by lack of +1's from the board and went to the mailing list. Can any of the board remember who it was? [17:17] so is 2 +0's and 2 +1's approved? [17:17] s-fox: are you refereing to the Canonical employee? [17:17] cjohnston: a majority of 4 would mean 3 :) [17:17] We do have a back channel. The question in my mind is do we need a majority in favor regardless of the number of voting members. or do we need a minimum of positive votes [17:17] if the rule is "majority of votes are +1" then 4 votes would require 3 +1s [17:17] No cjohnston , i think it was after that. [17:17] pleia2: I understand majority.. but that wasn't the only thing thrown out [17:17] hi folks, sorry to be late [17:17] welcome sabdfl [17:18] hello [17:18] it seems there was some confusion as to what the actual rule on approval was [17:18] hi sabdfl [17:18] hiya, sorry I was late [17:18] hi shadeslayer sabdfl [17:18] mhall119: correct. and that's what we need defined [17:18] pleia2: so the rule is "majority of votes are +1", regardless of final tally, and a quorom of 4, is that correct? [17:18] mhall119: that's always been my understanding [17:19] so 3 or more +1s, depending on how many votes are cast [17:19] that would make sense to me [17:19] The bot does give a verdict for us, but sometimes it just feels wrong. [17:19] then we should put this in writing somewhere [17:19] Can the bot be reworked? [17:19] yes it can [17:19] I think the bot does math, becasue that's how some teams do it [17:19] !meetingology [17:19] meetingology is a bot that runs !meetings and produces minutes - information at https://wiki.ubuntu.com/meetingology [17:19] ubottu: Error: "is" is not a valid command. [17:20] lol [17:20] bot fight [17:20] ok... shall we talk about the nominations as well? [17:20] can we tell meeting-ology about the decisions so far recarding quorum and approval rules? [17:21] so it's in the minutes [17:21] mhall119: it says there's a way to tell it a minimum number of +1s to pass [17:21] Pendulum: the bot does? [17:21] Pendulum: per session? [17:21] ah, yes, # votesrequired, nice [17:21] the bot has a command to set #requiredvotes [17:22] Pendulum: you just have to know how many votes will be cast ahead of time and calculate the majority value [17:22] so I just want to be clear.. to be approved it is 1/2 of the voters +1, correct? [17:22] mhall119: ^ [17:22] that is not the issue though, what we would like defined is what that number is [17:22] cjohnston: 50%+1 [17:22] ack [17:22] can this be tested with the bot? === vladk is now known as vladk|offline [17:22] s-fox: yep, #meetingology is the playground for that [17:23] does anybody mind if I tell the bot about what's been agreed to so far about getting quorum via email votes when it's not achieved in the meeting? [17:23] mhall119: please do [17:23] #agreed when quorum is not reached in a meeting, votes can continue via email until quorum is reached [17:24] * mhall119 assumes the bot got that [17:24] yeah, it doesn't echo anymore [17:24] now, on that note, does voting via email automatically stop when quorum is reached? [17:24] Would you like us to test and come back to the CC, or is this something you will be looking into yourself ? [17:24] mhall119: I'd say so [17:24] pleia2: that wouldn't allow everybody to vote then [17:24] mhall119: nope, it's as it's always been [17:25] We can set a time limit for email voting [17:25] 1 week? [17:25] IdleOne: that works for me [17:25] if there are 3 people at the meeting, there is no quorum, so it goes to email, then the very next person to vote would end the voting [17:25] I like seeing folks walk away from a meeting with an answer, not wait on email voting unless there is an issue [17:25] agreed [17:26] pleia2: that's ideal - but not what always happens [17:26] dholbach: agreed to which? [17:26] mhall119, sorry, what pleia2 said before [17:26] elfy: hence "unless there isan issue" :) [17:26] pleia2: I think we're all on the same page there, the preference is to have quorum at the meeting and give people a yes or no answer then and there [17:26] the question now is how to handle where there isn't quorum at the meeting [17:27] then it goes to e-mail [17:27] I think typically the meeting isn't held if there isn't quorum, or they grab CC members to fill in [17:27] if there are, say, 3 board members who are absent and it goes to email, do we wait for all 3 to vote or do we end voting as soon as quorum is reached and the others don't get a chance? [17:27] speaking of going to email: shall we move some of the discussion to mail? I'm just raising this because we're meeting up with the kubuntu folks today as well [17:28] mhall119: I think the best thing is to set a time limit on the email voting. Those members who get the vote in on time get counted. [17:28] IdleOne: but only if there isn't quorum at the meeting, right? [17:28] pleia2: correct [17:28] mhall119: if it goes to e-mail I see no reason why not just wait the week as IdleOne suggests and use all the votes [17:28] correct [17:28] wfm [17:29] and me [17:29] cool :) [17:29] if there is quorum (4 voting members) at the meeting there is no need for email votes [17:29] great [17:29] #agreed if voting goes to email for quorum, board members will be given a deadline of one week to cast their vote [17:30] can I note down the approval rule as agreed to? [17:30] "majority of votes cast must be +1"? [17:30] please do [17:30] so the other thing with membership boards should be pretty quick - we don't have enough applicants for the spaces available on the boards [17:30] it looks like we're lacking some nominations for the 12UTC meetings, so it probably might make sense to extend the time on the board for the expiring members and have another call for help? maybe ask the EMEA people on the loco contacts list? [17:30] * pleia2 nods [17:30] #agreed applicants are approved when a majority of votes cast are +1, regardless of the final total, as long as quorum is reached [17:31] Quite honestly, only 1 of the expiring members on 12UTC has shown up for meetings for at least a year [17:31] :\ [17:31] Pendulum, is the time popular among applicants? [17:31] that time zone region has always been tough to staff [17:32] I tried to stimulate getting this resolved by changing the time. It was generally not received well and people were saying they would struggle even more. [17:33] Part of what happened is that most of the 12UTC board is actually people on the East Coast of the US. So moving it earlier makes it more difficult for us, but moving it later means that the A/O folks can't make it [17:33] is it worth having a 12UTC board then? [17:34] My impression was that when we had 3 boards and that one met at 10UTC, there was even more trouble reaching quorum than we have at 12UTC [17:34] if it's difficult for the board, surely it's difficult for applicants too [17:34] It is a shame that time is in the middle of the working day in europe. [17:34] We do get applicants who would not be able to make 22UTC [17:34] mhall119: I think that it's more that it's difficult to get the board there rather than applicants from what I've seen [17:35] exactly [17:35] mhall119: we want more APAC applicants, I fear removing the board spot would make it harder for them and prepetuate the imbalance [17:35] We have never had a problem with applicants. the list is usually well populated [17:35] s-fox: thanks [17:35] the problem is the board voting. [17:35] I do think we've gotten better with getting quorum for 12UTC [17:35] and is that because it's in the middle of their work day and they can't attend? [17:36] or too early in the morning/late at night to attend? [17:36] can we try to mail locos in those regions? [17:36] mhall119: it's more because it's either really early or really late. I don't think there's anyone from EMEA on that board [17:36] dholbach: that's what I'm thinking [17:37] ok... I'll send a mail to the CC and membership board to organise this [17:37] I'm not actually sure if there are many, if any, EMEA folks on either board these days. [17:37] dholbach: thank you :) [17:37] dholbach: thanks :) [17:37] I would look to get myself put on that board, except it conflicts with my work day [17:37] is there anything else for membership boards, before we run out of time to sync with kubuntu folks? [17:38] thank you, mhall119 [17:38] Pendulum, i think this is the time to mention the renewals [17:38] mhall119: That's it :) [17:38] #agreed extend nomination period for membership boards so we can reach out to locos to find more for 1200 slot [17:38] lol [17:38] I'd like to thanks everyone on the Membership Boards for their hard working and stepping in when other board members couldn't make it. It's fun to get to chat with aspiring Ubuntu members, but it's also hard to make a decision. So thanks a lot everyone! :) [17:39] #topic Kubuntu catch up === meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | Community Council Meeting | Current topic: Kubuntu catch up [17:39] o/ [17:39] \o/ [17:40] hi folks, we took notes in advance of this meeting: https://wiki.kubuntu.org/Kubuntu/CCmeeting [17:40] hello everyone! [17:40] yay notes! [17:40] however I can put in the items one at a time so they are here in the backlog [17:40] first, thank you for asking to catch up with us [17:40] it's lovely to meet with y'all [17:41] so, since we last met, we've encountered some issues. Summing up: [17:41] heya [17:41] Since last year, the threats of legal action against Mint and other derivative distributions have upset our community. We were disappointed in the reaction of the CC -- it seemed to us that the CC was just doing as Canonical directed, rather than work with Mint to bring them into the community. [17:42] comments? [17:42] first I'd like to say that the CC intesely discussed this for months trying to A) understand it and B) come to consensus on it [17:43] we don't expect a change, frankly [17:43] but we're disappointed about that [17:43] it's a complex issue that has little to do with technology or community, and a lot to do with vague legal precedence and laws [17:44] from our pov, legal issues never had to come into it, if a friendly hand had been extended [17:44] extended to whom? [17:44]