/srv/irclogs.ubuntu.com/2018/03/01/#ubuntu-meeting.txt

rbalintfyi: unattended-upgrades is planned to allow installing from -updates in addition to -security by default: https://github.com/mvo5/unattended-upgrades/pull/10006:53
=== ubott2 is now known as ubottu
* slangasek waves16:00
philroche\o16:00
rcjo]16:00
slangasek#startmeeting16:00
meetingologyMeeting started Thu Mar  1 16:00:28 2018 UTC.  The chair is slangasek. Information about MeetBot at http://wiki.ubuntu.com/meetingology.16:00
meetingologyAvailable commands: action commands idea info link nick16:00
Odd_Bloke|o|16:00
slangasek[TOPIC] Lightning round16:00
=== meetingology changed the topic of #ubuntu-meeting to: Lightning round
gaugheno/16:00
slangasek$ echo $(shuf -e slangasek bdmurray xnox tdaitx doko sil2100 rbalint infinity cyphermox mwhudson rcj philroche Odd_Bloke tribaal fginther juliank)16:00
slangasekfginther Odd_Bloke bdmurray juliank sil2100 philroche doko infinity rcj cyphermox mwhudson slangasek xnox tdaitx rbalint tribaal16:00
slangasekfginther: ?16:01
tdaitx_nice, I got time to make some coffee16:03
Odd_BlokeI can go.16:03
Odd_Bloke* Continued refactoring of internal codebases to support minimal images16:03
Odd_Bloke* Preparation for engineering sprint next week16:03
Odd_Bloke* Preparation for partner visits in the two weeks after that16:03
Odd_Bloke* Switched GCE artful image publication to our new build system16:03
Odd_Bloke* Removed unscd from the Azure bionic images, we're replacing it with the built-in systemd-resolved16:03
Odd_Bloke* Various other small bits for partners16:03
Odd_Bloke(done)16:03
bdmurraySRU team duties16:03
bdmurraymerged my changelog changes for partner images16:03
bdmurrayinvestigated retracer workload (created a couple of cards w/ ideas)16:03
bdmurraysponsored xenial patch for LP: #165264116:03
bdmurrayinvestigated, tested update-manager details & conf prompt window size16:03
ubottuLaunchpad 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/165264116:03
bdmurrayuploaded fix for update-manager config file prompt size (LP: #1689668)16:03
bdmurrayuploaded fix for update-manager details window size (LP: #1690541)16:03
bdmurraystruggled to figure out LP: #1752053 was causing by desktop issues16:03
bdmurraywrote a bug pattern for LP: #1705345 (consolidated duplicates too)16:03
bdmurraytested some mini.iso installation issues16:03
ubottuLaunchpad bug 1689668 in aptdaemon (Ubuntu Artful) "dialog to resolve config file conflicts can be only one line high" [High,Confirmed] https://launchpad.net/bugs/168966816:03
ubottuLaunchpad bug 1690541 in update-manager (Ubuntu) "Scrolled windows in update-manager are too small to read" [High,Confirmed] https://launchpad.net/bugs/169054116:03
ubottuLaunchpad bug 1752053 in nvidia-graphics-drivers-390 (Ubuntu) "nvidia-390 fails to boot graphical display" [Critical,Confirmed] https://launchpad.net/bugs/175205316:03
ubottuLaunchpad bug 1705345 in plymouth (Ubuntu) "Installing packages hangs on plymouth --ping" [Critical,Triaged] https://launchpad.net/bugs/170534516:03
bdmurraydone16:04
bdmurrayjuliank:16:04
slangaseksil2100:16:05
sil2100- SRU reviews and releases16:05
sil2100- Kernel SRU reviews and releases16:05
sil2100- NEW reviews of pyxs and rax-nova-agent16:05
sil2100- 16.04.416:05
sil2100(done)16:05
philroche* Cloud image build system maintenance16:05
philroche* Completed EOL process for Zesty on major public clouds16:05
philroche(done)16:05
slangasekdoko is off16:06
slangasekinfinity is off16:06
slangasekrcj:16:06
xnoxphilroche, whoop whoop16:06
rcjpresent16:06
rcjHIGHLIGHT: 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
ubottuError: Launchpad bug 1527405 could not be found16:08
rcj* Cloud-image design work for new publication tooling.16:09
rcj* Debugging work for cloud-image boot failure due to grub config issue.16:09
rcj(done)16:09
rcjcyphermox:16:10
cyphermox- netplan:16:10
cyphermox  - rework routing16:10
cyphermox  - autopkgtests!16:10
cyphermox  - various bugfixing (bridge prio, NM snap support, etc.)16:10
cyphermox- systemd16:10
cyphermox  - post-review PR fixes16:10
cyphermox(done)16:10
xnoxubottu, 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
ubottuxnox: I am only a bot, please don't think I'm intelligent :)16:11
slangasek * was off on Tuesday, swap for the upcoming travel16:11
slangasek * work on resolving migrations stuck in -proposed16:11
slangasek * autopkgtest queue nudging16:11
slangasek * discussions about gnupg pulling lots of extra stuff into minimal16:11
slangasek * discussions around archive rebuilds for spectre v216:11
slangasek(done)16:11
slangasekxnox:16:11
naccxnox: it's a LP thing (iirc) -- you can't distinguish between non-existent and not-visible bugs without auth16:11
xnoxuploading things to transition ruby2.5 as only ruby16:11
xnoxuploading new releases / patches for z14 crypto support16:11
xnoxuploaded new powerpc-utils16:11
xnoxuploaded 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 didrocks16:11
xnoxtest point release s390x images16:11
xnoxdone16:11
naccxnox: i guess the link is the same regardless16:11
tdaitx_* OpenJDK 9 as default JDK16:11
tdaitx_  - patching, tracking status on debian, rebuilding16:11
tdaitx_  - moved to stage 2, same failures as stage 116:11
tdaitx_  - armhf is unstable, got a few intermittent segfaults and rebuilding eventually fixes those16:11
tdaitx_* OpenJDK 8 & 7 security updates16:11
tdaitx_  - Planned to ship 8 to the security team today16:11
tdaitx_  - OpenJDK 7 still requires some work, few patches no long apply cleanly (ongoing)16:11
tdaitx_(done)16:12
xnoxnacc, yeah, there are bugs/# url that should always work.16:12
slangasekrbalint:16:12
slangasektribaal:16:14
tribaal* CVE tracking16:14
tribaal* Vanguard for a 3rd week in a row. Send valium plz.16:14
tribaal* Sent code to snapcraft to enable LXD profiles in cleanbuild (https://github.com/snapcore/snapcraft/pull/1969)16:14
tribaal(done)16:14
fginther* Developing automated testing and publication updates for a partner cloud16:14
fginther* Reviewing design proposal for improved satellite cloud publication16:14
fginther* Helped debug a publication issue16:14
fginther(done)16:14
slangasekany questions?16:15
slangasek[TOPIC] Bugs16:17
=== meetingology changed the topic of #ubuntu-meeting to: Bugs
slangasek[LINK] http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-bb-incoming-bug-tasks.html#foundations-bugs16:17
bdmurraywe are taking on bug 1385524 correct?16:17
ubottubug 1385524 in update-manager (Ubuntu Bionic) "[SRU] update-manager-text crashes in all supported releases" [High,Confirmed] https://launchpad.net/bugs/138552416:17
slangasekyes16:18
bdmurraybug 1751011 is new16:18
ubottubug 1751011 in bash (Ubuntu) "bash crashes in qemu-user environments (bionic)" [Undecided,Confirmed] https://launchpad.net/bugs/175101116:18
xnoxdo we even support qemu-user.....16:19
slangasekbdmurray: that one seems like it's just a merge?16:19
slangasekxnox: generally no16:20
xnoxyeah, a merge16:20
slangasekbut it seems to be a trivial merge16:20
rbalinto/16:20
* xnox ponders if i can just upload it16:20
slangasekhmm the solution was to drop building with -pie16:20
bdmurrayAh, yeah I'd looked at that.16:21
slangasekdo we want a no-pie bash in order to support qemu-user?16:21
slangasekbdmurray: I'd decline this one16:21
bdmurrayslangasek: ack16:21
bdmurrayJean-Baptiste reported bug 175125216:22
ubottubug 1751252 in glib2.0 (Ubuntu) "ubiquity crashed with signal 5 in _XEventsQueued()" [Medium,New] https://launchpad.net/bugs/175125216:22
cpaelzerxnox: qemu-user* is universe - and best effort + community support16:22
slangasekinvalid literal for int() - ugh16:23
slangasekprobably locale-dependent16:23
xnoxslangasek, maybe you should remove it from -proposed then....16:23
slangasekand yeah, seems we should take that16:23
slangasekxnox: done. :P16:24
slangasekanything else on bugs?16:26
slangasek[TOPIC] AOB16:27
=== meetingology changed the topic of #ubuntu-meeting to: AOB
slangasekanything else?16:27
* sil2100 is fine16:29
slangasekoh16:29
slangasekrbalint: did you want to give status?16:29
slangasekguess not16:30
slangasek#endmeeting16:30
=== 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
meetingologyMeeting ended Thu Mar  1 16:30:19 2018 UTC.16:30
meetingologyMinutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2018/ubuntu-meeting.2018-03-01-16.00.moin.txt16:30
slangasekthanks, all16:30
sil2100o/16:30
elopioahoneybun: flexiondotorg: wxl: jose: marcoceppi: we meet in 15 minutes.16:46
elopioahoneybun: flexiondotorg: wxl: jose: marcoceppi: elacheche: everybody here?16:59
* elacheche is here17:06
wxlok now i'm here17:06
flexiondotorgo/17:10
elopioalright, lets start17:11
elopio#startmeeting Community Council meeting, 2018030117:11
meetingologyMeeting started Thu Mar  1 17:11:56 2018 UTC.  The chair is elopio. Information about MeetBot at http://wiki.ubuntu.com/meetingology.17:11
meetingologyAvailable commands: action commands idea info link nick17:11
=== 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:
elopioWe start the meeting with elacheche, wxl, flexiondotorg and elopio present. marcoceppi, ahoneybun and jose missing.17:12
elopio#topic report since last meeting17:12
=== 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
elopioAnybody has work in progress that we discussed on the previous meetings?17:13
elachecheI 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/cc17:14
elachechewe can move it somewhere else later for a final repport for future CC members (and us)17:15
wxlwe can remove the GSoC app. too late for that.17:15
elopioelacheche: 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
elopiowxl: 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:16
elachecheelopio: 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 rating17:17
elachecheWe 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:18
elopioelacheche: 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:19
elopioI'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:20
elopioanything else to talk about related to work in progress?17:21
elopioI will take that as a no.17:23
ahoneybunno17:23
elopiosince we don't have any topics on the agenda, flexiondotorg, elacheche and wxl, if you have something to discuss, please say so.17:23
elopioI would like to talk a little about these meetings17:23
flexiondotorgNot from me17:23
wxli would agree with that idea17:24
elopiolets start with that, and you can add other topics as we go.17:24
elopio#topic community council meetings17:24
=== 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
elopiowe 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
wxli don't think having leaders is the problem17:25
elopiounless somebody else wants to take this role, I will keep doing it.17:25
elopioand 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
wxli think the bigger issue is getting everyone to show up17:26
wxlor even communicate that they're not going to show up17:27
elopioyes, that's what I want to talk about next.17:27
elopioThis time I made a small change on the template with the call for the meeting.17:27
flexiondotorgI'm happy to contribute more to the running of these meetings.17:28
elopioit'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
flexiondotorgI've been busy in recent months.17:28
flexiondotorgI think getting up front commitment to attend is a good idea.17:28
wxli 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 knows17:28
wxlthis only makes sense17:28
wxli don't call into work every day and confirm with them that i'm coming in. do you guys?17:28
elopioflexiondotorg: what kind of contribution would you like to do? Taking the leader role? something else?17:29
flexiondotorgPerhaps we could automate a reminder for the CC members.17:29
flexiondotorgelopio: Yeah, chairing the meeting from time to time and getting back to updating the Community Hub.17:29
elopiowxl: 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 attend17:29
elachechewxl: +117:29
wxlelopio: this is why we need to set the expectations17:30
elopioevidence 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
wxland the expectation, as members of the council, is that we will attend the meetings17:30
elopiowxl: I agree on that17:30
wxlso *WE* shouldn't have to do anything to accomodate people not showing up17:30
elopiobut if we get repeated "no" replies, or "yes" replies but no-show in the end, we can start doing something about it17:30
wxlthose people who can't show up need to make it clear that they can't17:30
elopiofind a replacement, for example.17:30
wxlthe yes/no replies don't really matter so much as the actual attendance17:31
elopiowxl: it matters for who is trying to organize the meeting.17:31
wxli 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:31
wxlelopio: what difference would it make?17:32
elopiowxl: that's my expectation, but it's not working like that.17:32
elopiowxl: if you say "no", and give a reason, I don't have to continue pinging you all week.17:32
wxlbut you shoudln't have to in the first place17:32
wxlthat should be a reasonable expectation17:32
wxlthis 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 there17:33
elopioI 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:33
wxlhere'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:34
elachechewxl, 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
wxlas a general rule, you have at least shown up enough to say you couldn't be there, elacheche.17:35
elopiowxl: 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
ahoneybunthe meetings are on my calendar but I don't get a notification to remind me so I need to fix that17:36
wxlahoneybun: yeah, i'd say that's a personal problem not one for the council :)17:37
wxlelopio: yes17:37
elopioworks for me.17:37
elopioelacheche: flexiondotorg: ahoneybun: do you agree?17:37
elachechewxl: 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
ahoneybuncross that it's not on my calendar at all17:37
ahoneybunidk the fridge calendar is broken for me or something.17:38
flexiondotorgelopio: Agree with what, ejecting people for not showing up?17:38
wxlelacheche: 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:38
ahoneybunelopio, I don't agree. One time is a bit strong17:39
elopioflexiondotorg: not showing up without giving us a reason ahead of time.17:39
flexiondotorgSeems reasonable.17:39
elopioahoneybun: 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
elopiothat's not a lot to ask.17:40
wxlone time unexecused is perfectly reasonable17:40
wxlthere's a higher amount for execused absences17:41
flexiondotorgThree strikes?17:41
elopiosounds good to me too.17:41
wxlover what time period, too?17:41
flexiondotorgPer year?17:42
wxli think the 1 unexecused absence should be regardless of time but there should be a time associated with the excused ones17:42
elopioflexiondotorg: I would prefer 6 months.17:42
wxlflexiondotorg: that allows someone to be excused every 2 months17:43
flexiondotorgI think we should have a higher upper limit for excused absence.17:43
flexiondotorgI was thinking about unexcused absence.17:43
wxli think 3/12 months17:43
elopioso, wait, lets make full sentences, because this is confusing :)17:44
wxlhahahha17:44
* elacheche agrees with any ratio..17:44
elopioflexiondotorg: are you proposing to allow 1 unexcused absense per year?17:44
wxli think we do a huge amount of our work in these meetings. they're crucial. we only have 24 of them a year.17:44
* ahoneybun feels likes he is in high school again.17:45
flexiondotorgI was thinking 3 unexcused absence per year.17:45
wxlwe have to keep in mind that even missing 3 of those is pretty dramatic17:45
flexiondotorgBecause is demonstrates a trend of not turning up.17:45
wxlahoneybun: ditto. people not showing up is SO high school17:45
elopioflexiondotorg: 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
ahoneybunI've missed a few because I depend on notifications but I think I've fixed it now.17:45
ahoneybunI don't like having to use the Hub to say "Here"17:46
ahoneybunI never go to the Hub anyway17:46
elopioahoneybun: we need you in the hub.17:46
wxlahoneybun: then come to irc. or use the mailing list. you have lots of options17:46
ahoneybunelopio, for? I do17:46
elopiobut you can tell the leader directly, no need to post.17:46
elachecheahoneybun: 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:46
elopioahoneybun: we are trying to build the hub, and we need the help of everybody on the council for that.17:47
wxli couldn't agree with elacheche more17:47
ahoneybunI don't use forums often.17:47
elopioahoneybun: we need you to post about your tasks in there.17:47
ahoneybunmy tasks?17:47
* elacheche really hate the HUB because people can't edit his posts and help improving them :D x) :p → Wiki ROCKS17:48
elopioYes, 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 meeting17:48
wxlcan we stay on the topic of these rules  for the time being?17:48
elopioelacheche: 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:48
ahoneybunare we close to deciding on the rules for showing up?17:49
elopioI think we have a disagreement17:49
elopiowxl, elacheche and I agreed to be zero tolerant to not showing up without giving an excuse before17:50
elopioahoneybun and flexiondotorg think we should allow a few of those.17:50
elopiois that right?17:50
ahoneybunat least 1.17:50
wxli would concede to one throughout one's entire term17:51
flexiondotorgWe can make posts in the Hub "wiki posts"17:51
elopioI'm ok with one.17:51
elopioflexiondotorg: do you agree with one instead of three?17:51
ahoneybun1 out of 48 meetings.17:51
ahoneybun1/24 x 217:52
elopioyes.17:52
flexiondotorgPeople make mistakes. I think one transgression only is too strict.17:52
ahoneybunwhat about 2 per term?17:52
flexiondotorgA term being 2 years, right?17:53
ahoneybunyes17:53
flexiondotorgI think 2 per year, as a minimum.17:53
elopioI can live with that. wxl?17:53
flexiondotorgSo four over the course of the 2 year term.17:53
elopioelacheche says he agrees with any ration, so I'm assuming he's +1 on this.17:53
elopio*ratio17:53
wxllet's go for the middle road: 3/term17:54
elachecheYep.. The idea is that WE ALL agree about the same principale :)17:54
elopiolol, wxl we were so close to agree to 2/term17:54
elopioalright, 3 per term. flexiondotorg proposed that so he's happy, I'm ok, elacheche and wxl seem to be +1 too. ahoneybun ?17:55
ahoneybun+117:55
elachecheGreat!17:56
elopio#AGREED we will look for a replacement for whoever is absent to the community council meeting 3 times during their term17:56
elopio#agreed we will look for a replacement for whoever is absent to the community council meeting 3 times during their term17:56
elacheche+4217:56
flexiondotorgAgreed.17:57
elopiodamn, that command doesn't work.17:57
elopiook. I will communicate this to the mailing list.17:57
wxlit should go on the hub too17:57
elopioand the hub, where I will post the summary of this meeting17:57
elopioI 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:58
elopiohow 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
elacheche+1 too17:59
ahoneybunexpectation not requirement.17:59
wxli agree with expectation rather than requirement17:59
ahoneybunanyone else?18:01
elopioyes. 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:01
ahoneybunI think useful work is bringing their POV to a problem and offering a solution.18:02
ahoneybunNot always bringing something to do.18:02
elopioahoneybun: not enough. We should expect a lot more than that.18:02
ahoneybunmm.18:02
elopioand 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:02
wxli think we should write all this up18:03
wxlso people know what it means to be on the council18:03
elopioI 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
wxl+1 elopio18:03
elacheche+1 elopio18:04
elopioI 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:06
ahoneybunagreed18:07
elopiomaybe, topic for next meeting: bring your expectations from your council peers? We can discuss them and see if we agree on a few.18:07
ahoneybunadd it to the hub.18:08
wxli think that's a reasonable idea, elopio18:09
elopioI have nothing else to discuss. Any other topic ahoneybun, wxl, elacheche, flexiondotorg?18:09
ahoneybunnope.18:09
elopio10...18:10
flexiondotorgNot this time.18:10
elopio9...18:10
elopio8...18:10
elopio7...18:10
elopio6...18:10
elopio5...18:10
elopio4...18:10
flexiondotorgBut I have an idea, for next meeting.18:10
elopiogo for it flexiondotorg18:10
flexiondotorgNext time :-)18:10
wxlmine might be for next meeting too18:10
elopioah, ok, make sure to add it to the agenda18:10
wxlor we need to schedule a time to work on it specifically18:10
elopio3...18:10
elopio2...18:10
elopio1...18:10
wxland that's frmo the last agenda i put together: going over CoC bugs18:11
elopioI will prepare the next meeting, unless somebody else wants to lead that one. If so, just ping me any time.18:11
elopiothank you for coming, and making proposals, and discussing!18:11
elopio#endmeeting18:12
=== 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
meetingologyMeeting ended Thu Mar  1 18:12:10 2018 UTC.18:12
meetingologyMinutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2018/ubuntu-meeting.2018-03-01-17.11.moin.txt18:12
bashfulrobotGood day everyone.20:02
bashfulrobotJust popping in for my Ubuntu membership interview. Standing by as needed.20:02
fossfreedomvery quiet!20:03
tsimonq2Heyo20:03
tsimonq2wxl etc. where you at?20:03
wxli'm here :)20:04
tsimonq2Y'all chairing or am I?20:04
popeyo/20:04
wxlnot it20:04
bashfulrobotIt is. ha ha elacheche is checking out who is around and once we have 4 members - the meeting will begin.20:04
tsimonq2Fine then, I call dibs on chairing20:05
tsimonq2wxl: What's quorum?20:05
bashfulrobotWell I could chair - but somehow that does not seem appropriate. :-)20:05
tsimonq2;D20:05
wxlyou know, honestly, i have no freaking idea. but 4 sounds good :)20:05
tsimonq2Sounds good to me. elacheche, you still around? :)20:06
elachechetsimonq2: wxl it is 4.. It was always 4 :D20:06
bashfulrobotthe 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
wxlaccording 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
tsimonq2OK :D20:06
bashfulrobotyeahhh - I had to look it up for hte proper def.20:06
wxli intend to have the cc more clearly define this in the future20:06
elachecheWe need one more board member20:06
tsimonq2Sec, let me RTFM on how to do this again XD20:06
wxlit's too darn vague20:06
wxlpopey's here, elacheche20:06
tsimonq2#startmeeting20:07
meetingologyMeeting started Thu Mar  1 20:07:00 2018 UTC.  The chair is tsimonq2. Information about MeetBot at http://wiki.ubuntu.com/meetingology.20:07
meetingologyAvailable commands: action commands idea info link nick20:07
tsimonq2#topic bashfulrobot20:07
=== meetingology changed the topic of #ubuntu-meeting to: bashfulrobot
tsimonq2Hi20:07
bashfulrobotHello20:07
tsimonq2Please introduce yourself.20:07
tsimonq2bashfulrobot: Hello? :)20:09
bashfulrobotWell, 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:09
bashfulrobotCurrently 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
bashfulrobotIn the past I have also volunteered on the release management for the alpha/betas (17.10 +) as well.20:10
tsimonq2OK, cool! Can you please share a link to your wiki and LP page?20:11
bashfulrobothttps://wiki.ubuntu.com/bashfulrobot20:11
bashfulrobothttps://launchpad.net/~bashfulrobot20:11
tsimonq2Alright, any questions from the board?20:12
elachecheI like the tesimonials  :)20:13
elachechebashfulrobot: I'd like to know if you're involved with the LoCo?20:13
tsimonq2(or any other comments etc., I saw fossfreedom earlier :) )20:13
bashfulrobotYes I appreciate everyone who took the time to do so (THANK YOU!)20:14
elachecheIt would be great if a contributor like you helps in the LoCo too :D20:14
popeyhi bashfulrobot20:14
popeybashfulrobot: tell us a bit about how things are going in Ubuntu Budgie land20:15
tsimonq2^20:15
bashfulrobotI 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
tsimonq2Nice!20:15
elachecheGood, 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:17
tsimonq2Agreed!20:18
wxlbashfulrobot: you're going to be at lfnw this year?20:18
tsimonq2^^^^20:18
bashfulrobotWell, my perception is that we are slowly growing. As one of the newer flavours, there are always things we can do to help herald that in the right direction. Some of the items can be welcomed challenges (not having a developer background), but very interesting. I like having the exposure the larger Ubuntu ecosystem (and hope to get more involved there). Our LTS application is in progress pending final20:18
bashfulrobotapproval by the TB. So we are moving forward nice and steady.20:18
tsimonq2I will be20:18
bashfulrobotAs for the Loco - I have been thinking about attempting to merg it in some capacity if applicable.20:19
elacheche:)20:19
tsimonq2Alright, anything else before we vote, everyone?20:20
bashfulrobotwxl: I will be at LFNW this year. I fact tsimonq2 have been discussing doing some planning and working on a few things while we are both there. While not officially part of hte booth plan to offer assistance as well.20:20
* elacheche is ready to vote :)20:20
wxlbashfulrobot: cool. we should try to coordinate20:20
bashfulrobotif you are there, would love to!20:20
popeybashfulrobot: do you have any big plans for ubuntu budgie, or is it more slow-and-steady?20:20
tsimonq2#voters wxl tsimonq2 elacheche popey20:21
meetingologyCurrent voters: elacheche popey tsimonq2 wxl20:21
wxl+1 great work; keep it up!20:21
wxloops20:21
popeyhang on20:21
wxltoo jumpy20:21
* tsimonq2 is waiting on bashfulrobot to answer popey ;)20:22
tsimonq2Oh, should also set this...20:22
tsimonq2#votesrequired 420:22
meetingologyvotes now need 4 to be passed20:22
tsimonq2bashfulrobot: hi :)20:24
bashfulrobotWell there is a small consideration with Budgie in the longer term. If you consider upstream has started work on the version 11 of the desktop, there is going to be a lot of work there. Efforts (this is my opinion - Other team members may see it differently) are going to need to ramp up there to get to a sane baseline. And with that come a lot of decisions for the applications, how our community will20:24
bashfulrobotreact to the chang from GTK to QT. So while I say slow and steady - that is more of a self-assessment vs. a project assessment. Being rather new to the overall developer related tasks and hte community I have a slight ramp up time. In newer tasks vs someone who has worked withing the larger ecosystem.20:24
bashfulrobotSorry -was typing20:24
bashfulrobotwell spell correcting. :-)20:25
tsimonq2It's all good :)20:25
tsimonq2I think that's fair, thanks20:25
popey:)20:25
popeyI'm good.20:26
popeyThanks bashfulrobot20:26
bashfulrobotBut with that ramp up time and as I formulate relationships with other contributors - I know there is nothing but improvement (on my part) coming. And hopefully more cross project collab.20:26
tsimonq2#vote bashfulrobot's Ubuntu Membership20:26
meetingologyPlease vote on: bashfulrobot's Ubuntu Membership20:26
meetingologyPublic votes can be registered by saying +1, +0 or -1 in channel, (for private voting, private message me with 'vote +1/-1/+0 #channelname)20:26
elacheche+1 Good work bashfulrobot :)20:26
meetingology+1 Good work bashfulrobot :) received from elacheche20:26
tsimonq2+1 keep up the awesome work, I hope tosee you around :D20:26
meetingology+1 keep up the awesome work, I hope tosee you around :D received from tsimonq220:26
tsimonq2*ahem* wxl ;)20:27
popey+120:27
meetingology+1 received from popey20:27
popey /kick wxl20:27
elacheche:)20:28
wxl+1 great work; keep it up!20:29
meetingology+1 great work; keep it up! received from wxl20:29
wxlsorry work called me away20:29
tsimonq2#endvote20:29
meetingologyVoting ended on: bashfulrobot's Ubuntu Membership20:29
meetingologyVotes for:4 Votes against:0 Abstentions:020:29
meetingologyMotion carried20:29
tsimonq2Congrats!20:29
bashfulrobotThank yo uall!20:29
kyrofaCongratulations bashfulrobot, you deserve it :)20:29
fossfreedomwell done bashfulrobot20:29
elachecheCongrats bashfulrobot :)20:29
bashfulrobotAppreciate the feedback.20:30
tsimonq2#topic AOB?20:30
=== meetingology changed the topic of #ubuntu-meeting to: AOB?
bashfulrobotAnd invite critique for improvement if you see me floating around in the community.20:30
tsimonq2Anything else, y'all?20:30
tsimonq2bashfulrobot: :D20:30
bashfulrobotAre there any next steps or action items on my side of th efence for this process?20:30
bashfulrobot(runnig nto the wiki)20:31
tsimonq2I can catch up with you in a bit20:31
tsimonq2AOB...20:31
tsimonq21020:31
tsimonq2920:31
tsimonq2820:31
popeyKeep doing what you're doing :)20:31
tsimonq2720:31
bashfulrobotok. Sounds good.20:31
tsimonq2620:31
popeyThat's your action item :)20:31
tsimonq2520:31
tsimonq2420:31
tsimonq2320:31
bashfulrobotha ha - done!!20:31
tsimonq2220:31
tsimonq2120:31
tsimonq2:D20:31
tsimonq2#endmeeting20:31
=== 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
meetingologyMeeting ended Thu Mar  1 20:31:48 2018 UTC.20:31
meetingologyMinutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2018/ubuntu-meeting.2018-03-01-20.07.moin.txt20:31
bashfulrobotHave a good day / evening everyone.20:31
tsimonq2+1 popey :)20:32
tsimonq2You too!20:32
bashfulrobotThank you kyrofa, fossfreedom, tsimonq2, elacheche !21:05
tsimonq2Thank YOU!21:29

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!