[06:53] fyi: unattended-upgrades is planned to allow installing from -updates in addition to -security by default: https://github.com/mvo5/unattended-upgrades/pull/100 === ubott2 is now known as ubottu [16:00] * slangasek waves [16:00] \o [16:00] o] [16:00] #startmeeting [16:00] Meeting started Thu Mar 1 16:00:28 2018 UTC. The chair is slangasek. Information about MeetBot at http://wiki.ubuntu.com/meetingology. [16:00] Available commands: action commands idea info link nick [16:00] |o| [16:00] [TOPIC] Lightning round === meetingology changed the topic of #ubuntu-meeting to: Lightning round [16:00] o/ [16:00] $ echo $(shuf -e slangasek bdmurray xnox tdaitx doko sil2100 rbalint infinity cyphermox mwhudson rcj philroche Odd_Bloke tribaal fginther juliank) [16:00] fginther Odd_Bloke bdmurray juliank sil2100 philroche doko infinity rcj cyphermox mwhudson slangasek xnox tdaitx rbalint tribaal [16:01] fginther: ? [16:03] nice, I got time to make some coffee [16:03] I can go. [16:03] * Continued refactoring of internal codebases to support minimal images [16:03] * Preparation for engineering sprint next week [16:03] * Preparation for partner visits in the two weeks after that [16:03] * Switched GCE artful image publication to our new build system [16:03] * Removed unscd from the Azure bionic images, we're replacing it with the built-in systemd-resolved [16:03] * Various other small bits for partners [16:03] (done) [16:03] SRU team duties [16:03] merged my changelog changes for partner images [16:03] investigated retracer workload (created a couple of cards w/ ideas) [16:03] sponsored xenial patch for LP: #1652641 [16:03] investigated, tested update-manager details & conf prompt window size [16:03] Launchpad bug 1652641 in apt-xapian-index (Ubuntu Xenial) "crash in indexer.py, AttributeError: 'NoneType' object has no attribute 'unlink'" [Medium,In progress] https://launchpad.net/bugs/1652641 [16:03] uploaded fix for update-manager config file prompt size (LP: #1689668) [16:03] uploaded fix for update-manager details window size (LP: #1690541) [16:03] struggled to figure out LP: #1752053 was causing by desktop issues [16:03] wrote a bug pattern for LP: #1705345 (consolidated duplicates too) [16:03] tested some mini.iso installation issues [16:03] Launchpad bug 1689668 in aptdaemon (Ubuntu Artful) "dialog to resolve config file conflicts can be only one line high" [High,Confirmed] https://launchpad.net/bugs/1689668 [16:03] Launchpad bug 1690541 in update-manager (Ubuntu) "Scrolled windows in update-manager are too small to read" [High,Confirmed] https://launchpad.net/bugs/1690541 [16:03] Launchpad bug 1752053 in nvidia-graphics-drivers-390 (Ubuntu) "nvidia-390 fails to boot graphical display" [Critical,Confirmed] https://launchpad.net/bugs/1752053 [16:03] Launchpad bug 1705345 in plymouth (Ubuntu) "Installing packages hangs on plymouth --ping" [Critical,Triaged] https://launchpad.net/bugs/1705345 [16:04] done [16:04] juliank: [16:05] sil2100: [16:05] - SRU reviews and releases [16:05] - Kernel SRU reviews and releases [16:05] - NEW reviews of pyxs and rax-nova-agent [16:05] - 16.04.4 [16:05] (done) [16:05] * Cloud image build system maintenance [16:05] * Completed EOL process for Zesty on major public clouds [16:05] (done) [16:06] doko is off [16:06] infinity is off [16:06] rcj: [16:06] philroche, whoop whoop [16:06] present [16:08] HIGHLIGHT: Migrated Google Compute Engine images to use default gzip compression for initramfs for all releases. This reverts the customization from bug #1527405 that used XZ for compression. This change improves boot time. [16:08] Error: Launchpad bug 1527405 could not be found [16:09] * Cloud-image design work for new publication tooling. [16:09] * Debugging work for cloud-image boot failure due to grub config issue. [16:09] (done) [16:10] cyphermox: [16:10] - netplan: [16:10] - rework routing [16:10] - autopkgtests! [16:10] - various bugfixing (bridge prio, NM snap support, etc.) [16:10] - systemd [16:10] - post-review PR fixes [16:10] (done) [16:11] ubottu, i think you should still generate links, even if the bug is not found, cause you know - some people can see private bugs.... [16:11] xnox: I am only a bot, please don't think I'm intelligent :) [16:11] * was off on Tuesday, swap for the upcoming travel [16:11] * work on resolving migrations stuck in -proposed [16:11] * autopkgtest queue nudging [16:11] * discussions about gnupg pulling lots of extra stuff into minimal [16:11] * discussions around archive rebuilds for spectre v2 [16:11] (done) [16:11] xnox: [16:11] xnox: it's a LP thing (iirc) -- you can't distinguish between non-existent and not-visible bugs without auth [16:11] uploading things to transition ruby2.5 as only ruby [16:11] uploading new releases / patches for z14 crypto support [16:11] uploaded new powerpc-utils [16:11] uploaded livecd-rootfs, which builds multi-lowerdir overlayfs squashfs for maas installation in subiquity (something similar maybe used for desktop-minimal in the future too, Laney didrocks [16:11] test point release s390x images [16:11] done [16:11] xnox: i guess the link is the same regardless [16:11] * OpenJDK 9 as default JDK [16:11] - patching, tracking status on debian, rebuilding [16:11] - moved to stage 2, same failures as stage 1 [16:11] - armhf is unstable, got a few intermittent segfaults and rebuilding eventually fixes those [16:11] * OpenJDK 8 & 7 security updates [16:11] - Planned to ship 8 to the security team today [16:11] - OpenJDK 7 still requires some work, few patches no long apply cleanly (ongoing) [16:12] (done) [16:12] nacc, yeah, there are bugs/# url that should always work. [16:12] rbalint: [16:14] tribaal: [16:14] * CVE tracking [16:14] * Vanguard for a 3rd week in a row. Send valium plz. [16:14] * Sent code to snapcraft to enable LXD profiles in cleanbuild (https://github.com/snapcore/snapcraft/pull/1969) [16:14] (done) [16:14] * Developing automated testing and publication updates for a partner cloud [16:14] * Reviewing design proposal for improved satellite cloud publication [16:14] * Helped debug a publication issue [16:14] (done) [16:15] any questions? [16:17] [TOPIC] Bugs === meetingology changed the topic of #ubuntu-meeting to: Bugs [16:17] [LINK] http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-bb-incoming-bug-tasks.html#foundations-bugs [16:17] we are taking on bug 1385524 correct? [16:17] bug 1385524 in update-manager (Ubuntu Bionic) "[SRU] update-manager-text crashes in all supported releases" [High,Confirmed] https://launchpad.net/bugs/1385524 [16:18] yes [16:18] bug 1751011 is new [16:18] bug 1751011 in bash (Ubuntu) "bash crashes in qemu-user environments (bionic)" [Undecided,Confirmed] https://launchpad.net/bugs/1751011 [16:19] do we even support qemu-user..... [16:19] bdmurray: that one seems like it's just a merge? [16:20] xnox: generally no [16:20] yeah, a merge [16:20] but it seems to be a trivial merge [16:20] o/ [16:20] * xnox ponders if i can just upload it [16:20] hmm the solution was to drop building with -pie [16:21] Ah, yeah I'd looked at that. [16:21] do we want a no-pie bash in order to support qemu-user? [16:21] bdmurray: I'd decline this one [16:21] slangasek: ack [16:22] Jean-Baptiste reported bug 1751252 [16:22] bug 1751252 in glib2.0 (Ubuntu) "ubiquity crashed with signal 5 in _XEventsQueued()" [Medium,New] https://launchpad.net/bugs/1751252 [16:22] xnox: qemu-user* is universe - and best effort + community support [16:23] invalid literal for int() - ugh [16:23] probably locale-dependent [16:23] slangasek, maybe you should remove it from -proposed then.... [16:23] and yeah, seems we should take that [16:24] xnox: done. :P [16:26] anything else on bugs? [16:27] [TOPIC] AOB === meetingology changed the topic of #ubuntu-meeting to: AOB [16:27] anything else? [16:29] * sil2100 is fine [16:29] oh [16:29] rbalint: did you want to give status? [16:30] guess not [16:30] #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 [16:30] Meeting ended Thu Mar 1 16:30:19 2018 UTC. [16:30] Minutes: http://ubottu.com/meetingology/logs/ubuntu-meeting/2018/ubuntu-meeting.2018-03-01-16.00.moin.txt [16:30] thanks, all [16:30] o/ [16:46] ahoneybun: flexiondotorg: wxl: jose: marcoceppi: we meet in 15 minutes. [16:59] ahoneybun: flexiondotorg: wxl: jose: marcoceppi: elacheche: everybody here? [17:06] * elacheche is here [17:06] ok now i'm here [17:10] o/ [17:11] alright, lets start [17:11] #startmeeting Community Council meeting, 20180301 [17:11] Meeting started Thu Mar 1 17:11:56 2018 UTC. The chair is elopio. Information about MeetBot at http://wiki.ubuntu.com/meetingology. [17:11] 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, 20180301 | Current topic: [17:12] We start the meeting with elacheche, wxl, flexiondotorg and elopio present. marcoceppi, ahoneybun and jose missing. [17:12] #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, 20180301 | Current topic: report since last meeting [17:13] Anybody has work in progress that we discussed on the previous meetings? [17:14] I collected the list of ressources we have, unfortunately, I didn't had time to analyse and ask about our need of those.. The draft is in here → https://pad.tn/p/cc [17:15] we can move it somewhere else later for a final repport for future CC members (and us) [17:15] we can remove the GSoC app. too late for that. [17:16] elacheche: thanks. Why don't you make it a wiki post on the community hub? Also, do you need help to finish this task? [17:16] wxl: yep, didn't happen. Which I think was a good call, we need some time to rest from all the mentoring earlier in the year. Maybe, for next year, we can apply together with debian. [17:17] elopio: I will do that on the Wiki or the Hub once it's done, so we can have a final article about this in there.. And yes I need your personnal feedback (all CC folks) about the use of those ressources and why not we add a priority usage rating [17:18] We have multiple Wiki legacy pages, we can learn from those I guess.. But all new activities were moved to the hub (I don't like it, I like wiki more, but after all that's a personnal pref) [17:19] elacheche: yes, we agreed in previous meetings to give a try to the hub. We can still discuss about it if you want, but for now, we should follow that and put everything there. [17:20] I'm concerned about those 70 wiki pages, that's a lot to review. I can give you a hand with that, see what's old and we can drop, and what would be useful to update. [17:21] anything else to talk about related to work in progress? [17:23] I will take that as a no. [17:23] no [17:23] since we don't have any topics on the agenda, flexiondotorg, elacheche and wxl, if you have something to discuss, please say so. [17:23] I would like to talk a little about these meetings [17:23] Not from me [17:24] i would agree with that idea [17:24] lets start with that, and you can add other topics as we go. [17:24] #topic community council meetings === 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, 20180301 | Current topic: community council meetings [17:25] we tried rotating the role of the person who leads the meetings every month. That didn't happen very well, not just because of the leaders, but also because we have had a hard time adjusting since the christmas holidays. [17:25] i don't think having leaders is the problem [17:25] unless somebody else wants to take this role, I will keep doing it. [17:26] and at any time, if somebody thinks we should go back to rotate, or try a different approach, just say it and I will step down. [17:26] i think the bigger issue is getting everyone to show up [17:27] or even communicate that they're not going to show up [17:27] yes, that's what I want to talk about next. [17:27] This time I made a small change on the template with the call for the meeting. [17:28] I'm happy to contribute more to the running of these meetings. [17:28] it's very boring to be pinging everybody every day as the meeting approaches. So I would like all of us to reply on that topic saying if you are going to come, or not. [17:28] I've been busy in recent months. [17:28] I think getting up front commitment to attend is a good idea. [17:28] i think the assumption should be that you WILL show up and the responsibility will be on the person who is not showing up to make sure everyone knows [17:28] this only makes sense [17:28] i don't call into work every day and confirm with them that i'm coming in. do you guys? [17:29] flexiondotorg: what kind of contribution would you like to do? Taking the leader role? something else? [17:29] Perhaps we could automate a reminder for the CC members. [17:29] elopio: Yeah, chairing the meeting from time to time and getting back to updating the Community Hub. [17:29] wxl: my problem is that I don't know if you are not replying because you didn't get the message, or because all's good and you are going to attend [17:29] wxl: +1 [17:30] elopio: this is why we need to set the expectations [17:30] evidence shows that it's neither of those. So in order to see who I need to ping, it's easier for now while we get this under control to get an explicit yes or no. [17:30] and the expectation, as members of the council, is that we will attend the meetings [17:30] wxl: I agree on that [17:30] so *WE* shouldn't have to do anything to accomodate people not showing up [17:30] but if we get repeated "no" replies, or "yes" replies but no-show in the end, we can start doing something about it [17:30] those people who can't show up need to make it clear that they can't [17:30] find a replacement, for example. [17:31] the yes/no replies don't really matter so much as the actual attendance [17:31] wxl: it matters for who is trying to organize the meeting. [17:31] i frankly find it a little silly that we're even discussing this. we are all adults here, right? we show up to the things that we need to show up at and inform affected parties otherwise? [17:32] elopio: what difference would it make? [17:32] wxl: that's my expectation, but it's not working like that. [17:32] wxl: if you say "no", and give a reason, I don't have to continue pinging you all week. [17:32] but you shoudln't have to in the first place [17:32] that should be a reasonable expectation [17:33] this is not a huge team of which we are small outside contributors to. this is a core team of core people. we should consider it crucial to be there [17:33] I agree. But we are not there. We are not working that well as a group to trust that everybody will just show up and participate on the meeting. [17:34] here's my suggestion: email the list. let everyone know that the expectation is that they will be there. their presence is a requirement for continued membership on the council. then it will work great, i assure you. [17:35] wxl, elopio I think that both of you are right.. The idea of asking for a Yes or No and see if that answer goes with the attendency rate can be useful for doing some stats about this issue and have some real "data".. And maybe the next step should be doing stats about topics progress, because this is an issue too (I know I am being part of this issue :'( but the truth should be said anyways) [17:35] as a general rule, you have at least shown up enough to say you couldn't be there, elacheche. [17:36] wxl: so, let's set some rules to that. Say, one missed meeting without giving a reason means you are out of the council and we will find a replacement. Something like that? [17:36] the meetings are on my calendar but I don't get a notification to remind me so I need to fix that [17:37] ahoneybun: yeah, i'd say that's a personal problem not one for the council :) [17:37] elopio: yes [17:37] works for me. [17:37] elacheche: flexiondotorg: ahoneybun: do you agree? [17:37] wxl: honestly, I don't care if my past self shared the info that he'll be here or not, but if he didn't attend "enough" meetings and didn't contribute to tasks in progress my present self should be excluded from the CC.. And it's good to have stats to know that and help improving things, even if it will lead to exclude myself from the board :) [17:37] cross that it's not on my calendar at all [17:38] idk the fridge calendar is broken for me or something. [17:38] elopio: Agree with what, ejecting people for not showing up? [17:38] elacheche: that's fair. the work does need to get done and there's only a few of us. maybe 4 excused absences and you're out? [17:39] elopio, I don't agree. One time is a bit strong [17:39] flexiondotorg: not showing up without giving us a reason ahead of time. [17:39] Seems reasonable. [17:40] ahoneybun: the following meetings of the year are already scheduled. I think the least we can expect is people saying *all* the times if they are not going to come. [17:40] that's not a lot to ask. [17:40] one time unexecused is perfectly reasonable [17:41] there's a higher amount for execused absences [17:41] Three strikes? [17:41] sounds good to me too. [17:41] over what time period, too? [17:42] Per year? [17:42] i think the 1 unexecused absence should be regardless of time but there should be a time associated with the excused ones [17:42] flexiondotorg: I would prefer 6 months. [17:43] flexiondotorg: that allows someone to be excused every 2 months [17:43] I think we should have a higher upper limit for excused absence. [17:43] I was thinking about unexcused absence. [17:43] i think 3/12 months [17:44] so, wait, lets make full sentences, because this is confusing :) [17:44] hahahha [17:44] * elacheche agrees with any ratio.. [17:44] flexiondotorg: are you proposing to allow 1 unexcused absense per year? [17:44] i think we do a huge amount of our work in these meetings. they're crucial. we only have 24 of them a year. [17:45] * ahoneybun feels likes he is in high school again. [17:45] I was thinking 3 unexcused absence per year. [17:45] we have to keep in mind that even missing 3 of those is pretty dramatic [17:45] Because is demonstrates a trend of not turning up. [17:45] ahoneybun: ditto. people not showing up is SO high school [17:45] flexiondotorg: no, that's too much. You can excuse yourself 10 minutes before the meeting starts. But if you don't excuse yourself at all, that makes us waste a lot of time. [17:45] I've missed a few because I depend on notifications but I think I've fixed it now. [17:46] I don't like having to use the Hub to say "Here" [17:46] I never go to the Hub anyway [17:46] ahoneybun: we need you in the hub. [17:46] ahoneybun: then come to irc. or use the mailing list. you have lots of options [17:46] elopio, for? I do [17:46] but you can tell the leader directly, no need to post. [17:46] ahoneybun: It's not about us (you or me or anyone else).. We as a board should make a such decision of ourselves and for future board.. We see a problem we fix it :) [17:47] ahoneybun: we are trying to build the hub, and we need the help of everybody on the council for that. [17:47] i couldn't agree with elacheche more [17:47] I don't use forums often. [17:47] ahoneybun: we need you to post about your tasks in there. [17:47] my tasks? [17:48] * elacheche really hate the HUB because people can't edit his posts and help improving them :D x) :p → Wiki ROCKS [17:48] Yes, the things you do as part of the council to improve the community. But that's a different topic. If you disagree on using the hub, you should bring that to discussion on the next meeting [17:48] can we stay on the topic of these rules for the time being? [17:48] elacheche: saying that you hate the hub all the time doesn't help either :) We noted it when we discussed, and agree to give it a try anyway. [17:49] are we close to deciding on the rules for showing up? [17:49] I think we have a disagreement [17:50] wxl, elacheche and I agreed to be zero tolerant to not showing up without giving an excuse before [17:50] ahoneybun and flexiondotorg think we should allow a few of those. [17:50] is that right? [17:50] at least 1. [17:51] i would concede to one throughout one's entire term [17:51] We can make posts in the Hub "wiki posts" [17:51] I'm ok with one. [17:51] flexiondotorg: do you agree with one instead of three? [17:51] 1 out of 48 meetings. [17:52] 1/24 x 2 [17:52] yes. [17:52] People make mistakes. I think one transgression only is too strict. [17:52] what about 2 per term? [17:53] A term being 2 years, right? [17:53] yes [17:53] I think 2 per year, as a minimum. [17:53] I can live with that. wxl? [17:53] So four over the course of the 2 year term. [17:53] elacheche says he agrees with any ration, so I'm assuming he's +1 on this. [17:53] *ratio [17:54] let's go for the middle road: 3/term [17:54] Yep.. The idea is that WE ALL agree about the same principale :) [17:54] lol, wxl we were so close to agree to 2/term [17:55] alright, 3 per term. flexiondotorg proposed that so he's happy, I'm ok, elacheche and wxl seem to be +1 too. ahoneybun ? [17:55] +1 [17:56] Great! [17:56] #AGREED we will look for a replacement for whoever is absent to the community council meeting 3 times during their term [17:56] #agreed we will look for a replacement for whoever is absent to the community council meeting 3 times during their term [17:56] +42 [17:57] Agreed. [17:57] damn, that command doesn't work. [17:57] ok. I will communicate this to the mailing list. [17:57] it should go on the hub too [17:57] and the hub, where I will post the summary of this meeting [17:58] I have another proposal. Just showing up is not enough. I would like everybody to come at least with one topic to discuss or report to make, per month. [17:59] how does that sound? We can't enforce that, but sounds to me like a reasonable expectation, we should all be doing something every month. [17:59] +1 too [17:59] expectation not requirement. [17:59] i agree with expectation rather than requirement [18:01] anyone else? [18:01] yes. We will have stats to collect looking at the agendas, to confront somebody who is only attending the meetings, without doing any useful work. It's just something that will trigger us discussing if that person should continue on the council, not something that will expell them immediately. [18:02] I think useful work is bringing their POV to a problem and offering a solution. [18:02] Not always bringing something to do. [18:02] ahoneybun: not enough. We should expect a lot more than that. [18:02] mm. [18:02] and I'm sure there's other people in the community who are willing to work more than just attending a meeting twice a month. [18:03] i think we should write all this up [18:03] so people know what it means to be on the council [18:03] I think we need to realize that if we are not doing a good job on the council, we need to step down and let somebody else replace us. [18:03] +1 elopio [18:04] +1 elopio [18:06] I think this is just food for thought now. We have one strong rule defined now: attending the meetings. We can continue discussing about the role and expectations, and write them down as wxl suggests. [18:07] agreed [18:07] maybe, topic for next meeting: bring your expectations from your council peers? We can discuss them and see if we agree on a few. [18:08] add it to the hub. [18:09] i think that's a reasonable idea, elopio [18:09] I have nothing else to discuss. Any other topic ahoneybun, wxl, elacheche, flexiondotorg? [18:09] nope. [18:10] 10... [18:10] Not this time. [18:10] 9... [18:10] 8... [18:10] 7... [18:10] 6... [18:10] 5... [18:10] 4... [18:10] But I have an idea, for next meeting. [18:10] go for it flexiondotorg [18:10] Next time :-) [18:10] mine might be for next meeting too [18:10] ah, ok, make sure to add it to the agenda [18:10] or we need to schedule a time to work on it specifically [18:10] 3... [18:10] 2... [18:10] 1... [18:11] and that's frmo the last agenda i put together: going over CoC bugs [18:11] I will prepare the next meeting, unless somebody else wants to lead that one. If so, just ping me any time. [18:11] thank you for coming, and making proposals, and discussing! [18:12] #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 [18:12] Meeting ended Thu Mar 1 18:12:10 2018 UTC. [18:12] Minutes: http://ubottu.com/meetingology/logs/ubuntu-meeting/2018/ubuntu-meeting.2018-03-01-17.11.moin.txt [20:02] Good day everyone. [20:02] Just popping in for my Ubuntu membership interview. Standing by as needed. [20:03] very quiet! [20:03] Heyo [20:03] wxl etc. where you at? [20:04] i'm here :) [20:04] Y'all chairing or am I? [20:04] o/ [20:04] not it [20:04] It is. ha ha elacheche is checking out who is around and once we have 4 members - the meeting will begin. [20:05] Fine then, I call dibs on chairing [20:05] wxl: What's quorum? [20:05] Well I could chair - but somehow that does not seem appropriate. :-) [20:05] ;D [20:05] you know, honestly, i have no freaking idea. but 4 sounds good :) [20:06] Sounds good to me. elacheche, you still around? :) [20:06] tsimonq2: wxl it is 4.. It was always 4 :D [20:06] the minimum number of members of an assembly or society that must be present at any of its meetings to make the proceedings of that meeting valid. [20:06] according to the documention, we tend to follow Robert's Rules http://www.dummies.com/careers/business-skills/roberts-rules-for-defining-a-quorum/ [20:06] OK :D [20:06] yeahhh - I had to look it up for hte proper def. [20:06] i intend to have the cc more clearly define this in the future [20:06] We need one more board member [20:06] Sec, let me RTFM on how to do this again XD [20:06] it's too darn vague [20:06] popey's here, elacheche [20:07] #startmeeting [20:07] Meeting started Thu Mar 1 20:07:00 2018 UTC. The chair is tsimonq2. Information about MeetBot at http://wiki.ubuntu.com/meetingology. [20:07] Available commands: action commands idea info link nick [20:07] #topic bashfulrobot === meetingology changed the topic of #ubuntu-meeting to: bashfulrobot [20:07] Hi [20:07] Hello [20:07] Please introduce yourself. [20:09] bashfulrobot: Hello? :) [20:09] Well, I am Dustin Krysak located in Canada. I have been a member of the Ubuntu Budgie team since Nov-Dec of 2016. I come from an operations background (and a consumer of Linux). I had wanted to get involved with the OSS aspect to become a contributor to somethign I have used for a long time. [20:10] Currently I am also involved in the snacrafters community as well, both in the forum as well as interacting with project maintainers to hopefully introduce or assist with snap packaging. [20:10] In the past I have also volunteered on the release management for the alpha/betas (17.10 +) as well. [20:11] OK, cool! Can you please share a link to your wiki and LP page? [20:11] https://wiki.ubuntu.com/bashfulrobot [20:11] https://launchpad.net/~bashfulrobot [20:12] Alright, any questions from the board? [20:13] I like the tesimonials :) [20:13] bashfulrobot: I'd like to know if you're involved with the LoCo? [20:13] (or any other comments etc., I saw fossfreedom earlier :) ) [20:14] Yes I appreciate everyone who took the time to do so (THANK YOU!) [20:14] It would be great if a contributor like you helps in the LoCo too :D [20:14] hi bashfulrobot [20:15] bashfulrobot: tell us a bit about how things are going in Ubuntu Budgie land [20:15] ^ [20:15] I am not yet involved with the loco, but had reached out the members as it seems to have gone dormant to a degree. Where I have done work locally is with our local linux desktop LUG. I have recently been added as a co-host, but previously had done a talk on Ubuntu Budgie. [20:15] Nice! [20:17] Good, the LoCo should not be different from the LUG :) Yes, we have LoCos activity issues :) So contributions to LoCos should be always needed and apreciated :) [20:18] Agreed! [20:18] bashfulrobot: you're going to be at lfnw this year? [20:18] ^^^^ [20:18]