== Meeting information == * #ubuntu-meeting: Community Council meeting: 20180419, 19 Apr at 17:36 — 18:23 UTC * Full logs at [[http://ubottu.com/meetingology/logs/ubuntu-meeting/2018/ubuntu-meeting.2018-04-19-17.36.log.html]] == Meeting summary == ''ACTION:'' jose will forward the email to Wimpress, Wimpress will follow up. ''ACTION:'' Wimpress will send the emails to liri and enlightenment contacts ''ACTION:'' Make a post on the hub about the guerrilla marketing campaign. Share the draft. @Wimpress ''LINK:'' https://community.ubuntu.com/t/reconcidering-workflows/4656 ''LINK:'' https://community.ubuntu.com/t/member-for-life-the-wrong-policy/5257/1 ''ACTION:'' If people from the CC have opinions about the topic, join the discussion on the hub. == Vote results == == Action items, by person == * jose * jose will forward the email to Wimpress, Wimpress will follow up. * Wimpress * jose will forward the email to Wimpress, Wimpress will follow up. * Wimpress will send the emails to liri and enlightenment contacts * Make a post on the hub about the guerrilla marketing campaign. Share the draft. @Wimpress == Done items == * (none) == People present (lines said) == * elopio (71) * Wimpress (53) * jose (11) * meetingology (7) * ahoneybun (2) == Full Log == 17:36 #startmeeting Community Council meeting: 20180419 17:36 Meeting started Thu Apr 19 17:36:15 2018 UTC. The chair is Wimpress. Information about MeetBot at http://wiki.ubuntu.com/meetingology. 17:36 17:36 Available commands: action commands idea info link nick 17:36 So, we start with Wimpress and elopio present, jose and ahoneybun in and out. elacheche excused himself, wxl and marcoceppi haven't reported themselves 17:37 wxl said he's attending to a medical emergency 17:37 noted. 17:37 #topic Progress from last meeting 17:38 #subtopic Bold bug triaging - jose and Wimpress 17:38 can you please tell us how did that go? 17:39 I am perhaps under the incorrect assumption jose was dealing with that? 17:39 I offered to help but I think jose was onit? 17:40 I emailed about it and had no response, I will re-email about it 17:40 jose: Thanks. Who did you mail? 17:40 jose was on it but you said you would sync with him and help if needed. 17:41 lemme check 17:41 jose: Just forward me the email and I'll chase it. 17:42 wgrant 17:42 gotcha 17:42 will do that later on 17:42 fwd the mail and I'll talk to wgrant 17:42 Thanks. 17:43 #action jose will forward the email to Wimpress, Wimpress will follow up. 17:43 * meetingology jose will forward the email to Wimpress, Wimpress will follow up. 17:43 thank you. Next 17:43 #subtopic Triage CoC bug - all CC. 17:43 Haven't looked at all, sorry. 17:44 I didn't do it. I made some progress about CoC, that I will tell you about on a future topic. And I'm not going to take any actions today, I will just focus on CoC 17:44 jose: ahoneybun? 17:44 Wise 17:45 I haven't checked CoC bugs - I though we were going to set times for us to group-review them? 17:46 reading. 17:46 on the previous meetings, we have said that all the issues need triaging first, and that we should all take a few 17:47 none of us have done it, so it remains for the next meeting. 17:47 Sounds good. 17:47 #subtopic Clearly define governance seats, terms, and quorum. @elacheche 17:47 elacheche: please update the status on the community hub post for this meeting. 17:48 #subtopic Contact the liri and enlightenment community, to start with those two. @Wimpress 17:48 I have done the discovery. 17:48 Have contacts from Bohdi Linux and an Ubuntu community contributor maintaining a PPA for E21. 17:48 Also have several contacts for Liri, two also with LP active accounts. 17:49 Have sent emails yet. 17:49 Will send emails in the next day or two. 17:49 Bit crazy with the 18.04 release around the corner. 17:49 #action Wimpress will send the emails to liri and enlightenment contacts 17:49 * meetingology Wimpress will send the emails to liri and enlightenment contacts 17:49 thank you. Next 17:50 #subtopic Make a post on the hub about the guerrilla marketing campaign. @Wimpress 17:50 I have started a draft, it isn't finished. 17:50 I'll get around to finishing and posting this after 18.04 and UbuCon Europe. 17:50 So probably the week of our next CC meeting. 17:51 Wimpress: I will have time in may, if you need a hand with it. Should I keep the same action? 17:51 can we put it in a gdoc or etherpad? that way maybe we can all contribute and get it off the door asap 17:51 Yes, keep the action. 17:51 I post in a gist and share with you. 17:51 Or a gdoc or whatever. Sure. 17:51 I will circulate the draft. 17:51 #action Make a post on the hub about the guerrilla marketing campaign. Share the draft. @Wimpress 17:51 * meetingology Make a post on the hub about the guerrilla marketing campaign. Share the draft. @Wimpress 17:52 But it won't be this week or next week. 17:53 I think we are in no hurry with that one. It would be nice for 18.10 17:53 so start anytime next month should be more than enough. 17:53 sounds great :) 17:53 #subtopic Talk to the translations coordinators and the launchpad team to join the discussion on the hub. @elopio 17:54 one of the translations coordinator was already participating in the hub discussion. 17:54 let me paste the link here for later reference 17:54 https://community.ubuntu.com/t/reconcidering-workflows/4656 17:54 my point there is to work closer with upstreams, and less with launchpad. 17:55 gunnarhj said that has been always the idea. I didn't now this, at all. If that's the case, maybe we can close launchpad translations for all the packages that are not patched in ubuntu, and things like that, to make it clearer. 17:56 I'm not sure where the discussion will lead, but it's good to have it. Feel free to leave your thoughts in there. 17:56 #subtopic Figure out how to do a private backlog on the hub or on launchpad @elacheche, @Wimpress 17:57 anything happening there? 17:57 Sorry, no. 17:57 I don't think that elacheche collected the actions of the previous 3 meetings, so I'm not sure if this is going to work. 17:58 elacheche: please report on the topic on the hub. 17:58 ok, that's what we have from the previous meeting. 17:58 something else to report about the work of the past two weeks? 17:58 Not from me. 17:59 FYI - final freese for 18.04 today. 17:59 *freeze even. 17:59 \o/ awesome! 17:59 Let's jump to the next point on the agenda. 17:59 I'm looking forward to getting to bed before 3am again :-) 18:00 :) please don't burn out Wimpress, we need you! 18:00 #topic Add a section about inclusiveness to the code of conduct - @elopio 18:01 sorry, I phased out. 18:02 I was at an interesting event on the weekend. We were learning from Mozilla about enforcing the code of conduct. 18:02 that's very relevant for us, because we have had three reports already. And we have responded, but it's always hard to know how to do it. 18:03 they are forming a community of communities, to discuss about these issues. Their next call is going to be on may 4th. 18:04 I'll join for sure. And I'll send you the details in case somebody else wants to join. 18:04 That's one thing. The other is that on our first meeting we talked about being more inclusive, but we didn't have a clear idea of how to do it. 18:04 Sounds interesting. 18:05 I'd be interested in joining to. 18:05 we can get some good ideas from the Mozilla team, because they are doing an awesome job there. 18:05 Yep. 18:05 my first goal is to add a section about inclussiveness into our code of conduct. Probably, copying what mozilla has on their contributor guidelines. 18:06 For that, I first need to convince you that we need it. So I will work on finding data to support it, and planning the next steps to make it more than letter in a website. 18:06 Do we need to make proposals to change the CoC and get sign off from Mark or are we the custodians? 18:06 so, I don't have a lot to tell yet, but I will have in the upcoming meetings. 18:07 Wimpress: I think should get a sign off even if it's not required. And I have no idea how it works for the people who have already signed it, I saw something about versions on lauchpad 18:07 but that's part of the work to do, figure out all the details. 18:08 OK, so we need to find out what the process is. 18:08 any questions? suggestions? 18:08 I have no objection to updating the CoC. 18:08 Just want to learn what the correct process for doing so is. 18:09 I think in the past it's been discussion, review, and merge into the CoC branch in LP 18:09 I will also consult with Jono, because I know this was not added by design. I think we will disagree, but it would be good to have his opinion. 18:10 Yep. 18:10 ok, feel free to join me if you want to help. Next. 18:10 #topic Member for life, the wrong policy - @om26er 18:10 I don't think omer is around 18:12 a short summary is that he's making two proposals: first, do not let people renew their membership after it expires. Second, make a check with the current members (every two years I think) to see if their ar still active. 18:12 I guess the actions for us is to get involved in that topic 18:12 I think Mark had a said on that a while ago, saying something around the words of 'if you had valuable contributions to Ubuntu once, we thank you for them and consider you a member for life', I think it'd be worth consulting with Mark 18:12 https://community.ubuntu.com/t/member-for-life-the-wrong-policy/5257/1 18:13 Peoples circumstances change. 18:13 I live being a member for life. But the discussion is interesting. 18:13 I was active in the Ubuntu community from 2004 to 2009. Then dissappeared until 2014. 18:13 Because I started a family. 18:14 Let's make this action 18:14 #action If people from the CC have opinions about the topic, join the discussion on the hub. 18:14 * meetingology If people from the CC have opinions about the topic, join the discussion on the hub. 18:14 I think people who acheived membership in the past and elect to renew their membership should be permitted to do so. 18:14 It is possible they will once again become active, as I did. 18:14 then, if there's something actionable related to membership status, we can discuss here again, and involve Mark. 18:15 I would like to take this as an opportunity to start thinking about ways to get new members and recover the old ones. 18:17 on the post, I used the communitheme as an example. How do we get all that energy into people signing the code of conduct, planning for future activities with their communities, and being proud members? 18:17 I've replied on the Hub. 18:17 but, I said I would take no actions this meeting, so I will push it to may, unless somebody else wants to do something about it now. 18:17 Well the flavour bootstrapping is my idea to get some new members. 18:17 yes, and the guerrilla marketing. Those are great. 18:21 ok, the last topic was the review of actions with elacheche. So, there's nothing left. 18:21 Any other business? 18:22 I need to go and read bedtime stories. So... 18:22 5... 18:22 I'm still angry, so I would like to point out: ahoneybun: you have taken no actions on this meeting. jose: your only action is to forward an email. 18:22 4... 18:22 3... 18:23 the problem is not only the meeting, to me. We can discuss more in the next one. 18:23 2... 18:23 OK 18:23 1.. 18:23 Right, that's all folks. See you in two weeks. 18:23 #endmeeting Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)