== Meeting information == * #ubuntu-meeting: Community Council Regular Meeting - May 5, 2021, started by teward, 05 May at 23:08 — 23:56 UTC. * Full logs at https://new.ubottu.com/meetingology/logs/ubuntu-meeting/2021/ubuntu-meeting.2021-05-05-23.08.log.html == Meeting summary == === Forum Council === Discussion started by teward at 23:10. === "Confusion over ESM Messaging" - ongoing, ML === Discussion started by teward at 23:12. === "Confusion over 'Community Team' naming" - src: Eickmeyer via ML === Discussion started by teward at 23:14. * ''LINK:'' https://lists.ubuntu.com/mailman/private/community-council/2021-May/019964.html (teward, 23:15) === Community Team Proposal: Communications Council === Discussion started by teward at 23:27. == People present (lines said) == * teward (67) * madhens (28) * toddy (19) * nhaines (18) * Eickmeyer (18) * jose (14) * meetingology (3) == Full log == 23:08 #startmeeting Community Council Regular Meeting - May 5, 2021 23:08 Meeting started at 23:08:42 UTC. The chair is teward. Information about MeetBot at https://wiki.ubuntu.com/meetingology 23:08 Available commands: action, commands, idea, info, link, nick 23:08 #chairs madhens toddy jose teward 23:09 Oh, I see how it is. 23:09 you meant nhaines? :) 23:09 #chair nhaines toddy jose teward 23:09 Current chairs: jose, nhaines, teward, toddy 23:09 yes, sorry, fubar command :) 23:09 So, a regular community council meeting again. 23:09 looks like the last meeting never happened because nothing to discuss so 23:09 guess we'll start with some bits to the CC at the moment. 23:10 #topic Forum Council 23:10 The Forum Council, via Monica (madhens), told us they were about to expire. Unilaterally at the time, I extended their roles for 30 days to the end of this month. 23:10 at some point we need to handle an FC election process. 23:10 do we have the process documented? 23:10 but I believe Monica made a proposal that may make that moot 23:11 I might've missed that? 23:11 jose: ERR: Undocumented, we may need to create a new process from scratch. Frankly, unless there's a major need to redo the FC (and everyone on it currently is still happy to be doing the job) I don't see a need to do much. 23:11 jose: it went on the list 23:11 i'll dredge it up when I get to that topic 23:11 I forwarded the request to the CC list 23:11 ah I remember seeing that 23:12 yep 23:12 #topic "Confusion over ESM Messaging" - ongoing, ML 23:13 we continue to hear back from Rhys on the process of updating ESM definitions, etc. including that there is a change in place in the next months(?) RE: UA-I coverage for the 'free' edition 23:13 and what it does/doesn't provide. (i.e. no limitations) 23:13 I don't see any more actions that we need to do, as Nathan raised a question to RHys and that was answered I believe? 23:14 yep, I think comms have been flowing good on that one 23:14 yep, thank you madhens again for getting that one where it needs to go so things can be less confusing to the masses :) 23:14 indeed 23:14 #topic "Confusion over 'Community Team' naming" - src: Eickmeyer via ML 23:14 You're welcome! But yes, Rhys has been doing a great job 23:15 #link https://lists.ubuntu.com/mailman/private/community-council/2021-May/019964.html 23:15 * Eickmeyer is here 23:15 Erich Eickmeyer of the Ubuntu Studio team made known a concern to the CC regarding the Canonical Community Team's naming. 23:15 FYI: this is teeeechnically out of the CC's purview. 23:15 I'll let Eickmeyer summarize so madhens can be aware of his concern. 23:15 *drags Eickmeyer to center-stage* 23:15 Go ahead! 23:15 Eickmeyer: madhens is our contact on the Community Team at Canonical ;) 23:16 she's always here, you have the floor for a couple minutes. 23:16 Possibly, but the name of the team is very ambiguous vis-a-vis the Community Council. It wasn't about the name of the IRC chatroom, but about the name of the teams. 23:16 Community Council and Community Team are way too close. 23:17 I believe that we might want to think more about it and see if we can make any proposals. 23:17 It only adds to the confusion between Canonical and Ubuntu. 23:17 Monica, if you, Rhys, or Ken have any ideas, happy to hear as well 23:17 I submit that we are *already* the "Ubuntu Community Council": https://discourse.ubuntu.com/t/what-is-the-ubuntu-community-council/706 23:17 i don't disagree with Jose. However, we should be very clear: whether Canonical chooses to rename the Community Team is their decision, not a CC one. We can weigh in on our opinions, however it's up to Canonical to make the decision 23:17 hence my pinging madhens on this one. 23:17 and the "Canonical Community Team" 23:18 nhaines: Correct we are. The concern is that the Community Team is a team at Canonical. 23:18 madhens: fyi I'll forward that msg over to you for your awareness. 23:18 Indeed. I don't think that this is a high-prio concern (at least for me) but would like to explore options 23:18 teward: Agreed, but we can definitely make recommendations. 23:18 Eickmeyer: if we do anything, I'd like to make a change of the name to "Community Relations Team" 23:18 Eickmeyer: Correct, but since there was the suggestion that we should change our name from "Community Council" to "Ubuntu Community Council," I thought it relevant. 23:18 because that is more clear that that's more the team that's go-between between Community (Council or otherwise), and Canonical's internal teams. 23:18 I think I'd definitely like to loop Ken in, and whoever our Head of Community will be 23:18 which... is madhens' job. 23:18 madhens: 👍 23:19 i'll forward you the email, but i'd like for the CC to be kept in the loop if you do make a change to the name, and we can make some proposed names as well. 23:19 And I think Community Relations or Community Engagement is a better description of what we do. 23:19 I don't really think this is a friction point, but happy to be proven wrong or to hear other points of view. 23:19 Correct, teward, except that there have been recent news articles about the "Community Team" and that can spark confusion. 23:19 Aww, I was going to suggest Community Engagement Team sounded dynamic and buzzwordy. I was beat to the punch. :) 23:19 Eickmeyer: That's more of a problem for the news outlets. 23:19 Eickmeyer: that's more a UWN problem than our issue 23:20 teward: It wasn't just uWN. 23:20 if you want we can have madhens go after em about it 23:20 And the sooner resolved, the less it will matter. 23:20 I think we used that term because it was what had been used in the past. 23:20 Eickmeyer: UWN sent the article, others picked it up 23:20 i think at the MOMENT your point that there's confusion is valid 23:20 but not the highest priority thing on the CC's plate at this moment 23:20 (and more a Canonical executive call not CC) 23:20 my 2 cents with the hat on :) 23:20 No, it's not a huge priority, but I think there should be a recommendation from our end. 23:21 Maybe not today, but I'd like to see some brainstorming. 23:21 Again, maybe not today. 23:21 If anything, the recommendation should be to the media outlet. Happy to reach out to any of them - I have some contacts in the OSS media world too. 23:21 But we can forward that proposal to Ken and then on to Dean (and Mark if needed). So put one together? 23:21 CC can discuss internally on name proposals, and provide them. You're free to submit recommendations to the CC as well. But yes, the MEdia Outlets need to eb the ones yelled at ;) 23:21 madhens: i think that's a good idea, it won't be a "tonight" brainstorming session though I think ;) 23:21 To be fair, they were only reporting what we wrote. 23:21 Because we picked up the previous nomenclature. 23:22 I think we should keep looking into the root of the issue, but I agree it's not something we can do in the span of this meeting 23:23 * Eickmeyer was just hoping it would be a discussion in the email and never intended it to be added as an agenda item 23:23 Eickmeyer: one of the things we bring up is 'current ML items" sometimes ;) 23:23 and besides, Monica's here so :) 23:23 teward: Monica was CC'd. 23:23 looks like it got stripped from the mail system then 23:23 👍 23:23 Probably. I CC'd Rhys and Monica. 23:24 I wonder who didn't hit Reply All... looks at teward 23:24 jose: i didn't reply to it ;) 23:24 ^ 23:24 in any case, I think we can continue the discussion since we also have Rhys voicing in on it as well :) 23:25 So to summarize, this topic has been raised and we are making good progress on it. 23:25 Perhaps in a meeting or two we'll have some nice results. :) 23:25 yep. :) 23:25 Indeed. :) 23:26 I... don't see any other items on *my* list or in the ML that still need our attention that I didn't bring up (latest being the FC issue) 23:26 anyone else have anything? 23:26 * Eickmeyer salts his alarm for not going off at the right time 23:26 not on my end, things are flowing okay 23:26 teward: no, I have nothing. 23:27 I've got nothing myself, that I haven't otherwise raised up. 23:27 nhaines: anything from you? 23:27 teward: no, I'm satisfied. 23:27 I think the only thing I had was the Forum Council in the context of the proposal, but that's all. 23:27 ah that's right i forgot about that 23:27 Combination Forum/IRC Council, the Communication Council. 23:27 #topic Community Team Proposal: Communications Council 23:28 madhens: this one's your lead you sent to the ML, if you want to bring it up here. 23:28 *gives madhens the floor for now* 23:28 So, this was sent probably right as you all modified the IRCC to 3 instead of 5 23:28 So there was a bit of a 'ships in the night' thing happening there. 23:29 at the request of the existing IRCC, yes. Unfortunate that happened. 23:30 But we did want to float the proposal as a way to perhaps consolidate governance in the hopes of keeping them more sustainable, and to allow other community platforms to have a means of staying in touch with and involved with the rest of the community - but in a non-voting way. 23:31 And if we did end up adding another 'official' communication platform, like Mattermost, then we'd already have governance for them, since this council would be tied to function, not a specific platform. 23:31 So, those were our primary reasons, and I'd be happy to answer any questions or concerns, no matter how you decided to go forward (or not) on it. 23:33 But the specific platforms are very different from each other. I don't know if it makes sense to have the channels run from one communication council. 23:34 I think that was the intent of 'peripheral' members, who could just attend for coordination purposes, not governance. But I agree, they are very different. 23:34 I find the idea intriguing. 23:34 But I haven't really dealt with the matter yet either. 23:36 Do we actually have any other official communication channels besides the forum and IRC at the moment? 23:37 all things in Telegram, Slack, foobar are not official I think 23:37 Wasn't there something in Rocket.Chat? 23:38 Is AskUbuntu official? 23:38 nhaines: yes, in Rocket:chat was also something 23:38 Yes, AskUbuntu is. 23:38 but I think it is dead 23:39 A year ago, I looked into it and I have not seen any activity there. 23:39 Maybe it was two years ago 23:40 Also, I think Ubuntu Discourse would be included 23:40 We have quite a mess there with those different platforms. 23:41 Maybe we should really sort this out a bit. 23:41 Fragmentation is something that does happen - we wanted a way for official platforms to govern AND unofficial platforms to connect and coordinate. Maybe those are two separate things. 23:41 Well Ubuntu Discourse is the Ubuntu Community Hub. I'm not sure who's in charge of that. 23:42 But I know one thing we're trying to do is find and meet the community where they are at - and that's a lot more places in 2021. 23:42 I think it's a good idea to have some type of shared contact point, even if it's just a mailing list. 23:42 nhaines: It's kind of sad I have no idea either, but I will ask. We do have a lot of admin and moderators. 23:43 madhens: i think we have to keep the existing councils in place though for the purpose of FC's things. FC members are admins. That's going to be a consideration point 23:43 Good point! And I figured tonight would be an initial conversation. 23:43 madhens: and RE: Discourse, some of us have mod who don't need it, but only need it for a specific section (and it was a issue we couldn't get past because of how Discourse is made) 23:45 ah, here is a list of official platforms: https://ubuntu.com/community 23:46 We will also work on trying to clear up some of the Discourse things, while acknowledging some things we have to do because of just how Discourse is 23:47 How do we continue with the topic? 23:47 Should we continue? 23:50 We support any way you all want to continue, or if you don't want to continue. 23:51 I want to sit down and look at the proposals again and think about it some more. 23:51 Because I think the idea of a shared communication method for any of these issues would be useful for users. 23:52 Then we share more ideas about the ML? 23:52 sorry i'm getting called away for work at the moment 23:52 i think continuing the discussion on the ML is a good idea, it's not something we're going to solve in the scope of this meeting :) 23:53 but we should continue to keep in touch on the issue and madhens please share any more thoughts you have on the matter there as well 23:53 Of course! 23:53 I don't have anything else, anyone else got anything? 'cause i'mma have to nip out for work in about 3 minutes 23:53 That's it from me 23:54 ok, I think I need to go to bed. 23:54 Thank you all so much! 23:54 I'm good. 23:54 madhens: thanks for being here and bringing up these interesting topics. :) 23:54 madhens: thank you for bringing up the topics. 23:54 Of course :) 23:56 #endmeeting Generated by MeetBot 0.4.0 (https://wiki.ubuntu.com/meetingology)