14:00:43 #startmeeting Council (2020-06-24) 14:00:44 Meeting started Wed Jun 24 14:00:43 2020 UTC. 14:00:44 This meeting is logged and archived in a public location. 14:00:44 The chair is bcotton. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:44 Useful Commands: #action #agreed #halp #info #idea #link #topic. 14:00:44 The meeting name has been set to 'council_(2020-06-24)' 14:00:45 #meetingname council 14:00:45 The meeting name has been set to 'council' 14:00:47 #chair bookwar dcantrell jonatoni riecatnor dgilmore mattdm bcotton pbrobinson asamalik sumantrom 14:00:47 Current chairs: asamalik bcotton bookwar dcantrell dgilmore jonatoni mattdm pbrobinson riecatnor sumantrom 14:00:48 #topic Introductions, Welcomes 14:00:49 .hello2 14:00:50 asamalik: asamalik 'Adam Samalik' 14:00:55 .hello2 14:00:56 dcantrell: dcantrell 'David Cantrell' 14:01:00 .hello2 14:01:05 mattdm: mattdm 'Matthew Miller' 14:01:35 morning 14:02:09 .hello2 14:02:10 riecatnor: riecatnor 'None' 14:02:21 .hello2 14:02:22 bookwar: bookwar 'Aleksandra Fedorova' 14:02:24 Good morning (and etc) everyone! 14:02:45 good morning 14:02:59 good etc! 14:03:49 hullo! 14:04:05 alrighty, let's do this 14:04:11 yes! 14:04:15 #topic Today's agenda 14:04:16 #info Comings and goings 14:04:18 #info Project directory 14:04:19 #info Diversity & Inclusion ticket 135 14:04:21 #info Your topics here! 14:04:43 #topic Comings and goings 14:04:44 #info psabata's time as Engineering representative has ended 14:04:46 #info dcantrell is the new Engineering representative 14:04:47 #info till's time as elected representative has ended 14:04:49 #info bookwar is the new elected representative 14:04:50 #info sumantrom's time as Mindshare representative is ending, selection of his replacement is ongoing 14:05:01 o/ 14:05:02 hi bcotton 14:05:11 hi everyone 14:05:26 welcome bookwar 14:05:30 welcome dcantrell 14:05:32 welcome bookwar and dcantrell! 14:05:39 thanks! 14:05:42 my goal for next couple of weeks is to understand what council actually does, so please expect stupid questions :) 14:05:47 welcome bcotton and dcantrell ! \o/ 14:06:01 nope, bookwar I mean 14:06:03 contyk++ till++ sumantrom++ so long and thanks for all the fish 14:06:06 bcotton: Karma for till changed to 1 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 14:06:09 bcotton: Karma for sumantrom changed to 7 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 14:06:24 bookwar: that's a good goal! 14:06:31 contyk++ till++ sumantrom++ 14:06:31 riecatnor: Karma for psabata changed to 11 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 14:06:34 riecatnor: Karma for till changed to 2 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 14:06:38 bookwar: let me know when you figure it out ;-) 14:06:48 thank you sumantrom, till, and psabata! 14:07:20 This brings up the thing we talked about at the last Council face to face 14:07:28 (remember face to faces? ahhhh.) 14:07:37 what are faces? 14:07:38 Namely: "council-buddies" 14:08:08 bcotton: those things in mirrors that grin weirdly 14:08:35 That is, every new council member should get someone assigned to help them figure out what the council is all about 14:08:55 As I recall, we almost said "mentor" but that seemed too strong 14:09:21 1. Should we do that now?2 14:09:29 2. bookwar, dcantrell would that be helpful? 14:09:36 3. Volunteers? 14:09:49 I would find it helpful, yes 14:10:31 if someone volunteers to have an informall call to discuss council topics - it would be nice. If not - i'll just bother random people anyway 14:10:38 Thanks to all the people, who supported me ! :D 14:10:52 and for all the work and fun :) 14:10:56 sumantro++ 14:10:56 mattdm: Karma for sumantro changed to 4 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 14:11:30 * bcotton volunteers 14:11:36 bcotton++ 14:11:58 anyone else? if not, it's me :) 14:12:07 bcotton is a default volunteer in Fedora :) 14:12:18 yes, I volunteer him for things all the time! 14:12:35 * bcotton is very bad at saying no to more work :-) 14:12:46 okay, it's me. 14:13:04 https://justflipacoin.com/ 14:13:18 says bcotton - dcantrell, mattdm - bookwar :) 14:13:31 #action bcotton to help onboard dcantrell 14:13:39 #action mattdm to help onboard bookwar 14:13:42 bcotton++ 14:13:51 mattdm: we should compare notes afterward and turn it into something reproducible 14:13:54 #info need more cookies for bcotton 14:14:10 * bcotton has a pack of Chips Ahoy in the kitchen 14:14:21 bcotton: that would be my first assignment probably 14:14:23 bookwar: find time on my calendar tomorrow, friday, or early next week? 14:14:27 bookwar++ 14:14:27 bcotton: Karma for bookwar changed to 2 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 14:14:33 mattdm: will do 14:14:36 okay, shall we move on to the next topic then? 14:14:54 sounds good to me. what's the next topic? 14:14:58 oh, I'd be happy to help, too! 14:15:08 #topic Project directory 14:15:09 #link https://pagure.io/Fedora-Council/tickets/issue/295 14:15:21 asamalik has been furiously working away in the ticket in the last hour or so 14:15:31 ha, and here's my chance I guess 14:15:32 yep! 14:16:24 asamalik :) 14:16:25 I figured out how to store reusable data in the docs, and render it in multiple places multiple ways 14:16:32 asamalik++ 14:16:58 I believe I'll finally get it done this week 14:18:19 hooray! 14:18:19 asamalik that sounds useful. is there a document for how to do that? :) 14:19:03 mattdm: in the ticket right now, it's all very fresh as bcotton has pointed out :) 14:19:24 but yeah, I could add it to the docs for the docs part 14:19:47 asamalik++ 14:19:52 anything else on this topic? 14:19:55 here I mean: https://docs.fedoraproject.org/en-US/fedora-docs/contributing/ 14:20:01 asamalik++ 14:20:01 mattdm: Karma for asamalik changed to 9 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 14:20:51 all from my side! 14:20:58 okay, next! 14:21:03 #topic Diversity & Inclusion ticket 135 14:21:04 #link https://pagure.io/fedora-diversity/issue/135 14:21:11 riecatnor: the floor is yours 14:21:31 ok :) 14:21:54 I would request council members read this ticket and comment 14:22:12 D&I and Mindshare are both asking for the Councils input on this 14:22:18 OK 14:22:42 that's a long read, will try to get to it after all my meetings today 14:23:08 we don't have another business meeting for some time.. and I do see the need for swift responses 14:23:11 riecatnor: do you have a deadline? 14:23:34 I think a week is reasonable for folks. Please review by July 1st. 14:23:44 sound ok? doable? 14:23:57 riecatnor: just to have us individually weigh in, you mean? 14:24:03 #info Council members are requested to provide feedback in the D&I ticket by 1 July 14:24:07 ack 14:24:21 shouldn't we review the actual text by that time? 14:24:30 Well, we could start a mailing list thread to discuss if it makes more sense 14:24:56 if we just agree on the idea by July 1st, then the actual text will probably take a week more 14:25:11 Agreed, bookwar 14:25:13 I think it's okay to discuss there I'm just trying to figure out the intended outcome 14:25:38 riecatnor: you want me to drop in the ticket what we said yesterday about surveys? 14:25:54 mattdm, I don't want to distract that thread further. 14:25:56 I think the discussion is starting to get away from the topic: a short letter requesting that the fedora council make a statement about racism against black people and offer of support to black members of the community who may be having a hard time right now. Could a plan be made for such a letter to get written with a time frame for it being sent? 14:25:59 this is the heart of the request. 14:26:10 Specifically: Red Hat legal has had some changes, and now is apparently not as frightened by surveys 14:26:27 so wait. are they asking council to write the letter or they asking to write the letter for council to approve 14:26:38 because those are two very distinct requests 14:27:15 jflory says: The Fedora D&I Team writes a "Letter of Collaboration" to the Fedora Council to come forward and make a statement of support and action for Black Lives Matter on behalf of Fedora Leadership. 14:27:32 so.. unclear? 14:28:04 I think it should come from Fedora Council & D&I together. 14:28:18 I would also like to have some real actions to go along with any letter. Talk is -- well, not actually cheap. But insufficient. 14:28:33 my read is that they're asking for council's input to frame the draft they'll write 14:29:04 yes, it should come from council and d&i, but as mattdm can attest, the name on the statement doesn't always match who wrote it 14:29:20 bcotton, fair ;) 14:29:47 I'll sign anything bcotton puts in front of me! 14:29:49 iow, if we want the council to draft something, be prepared to wait a long time. if someone wants to write a draft for council to edit and approve, that's much faster. and also means there's not a lot of action required of the council until such a draft appears 14:30:11 bcotton: indeed 14:30:35 I do think having us look and say "yes this is a good idea go ahead" is what they actually want 14:31:05 and I can write a comment about our discussion. I do think its important for the Council members to be aware of the different things being said there. 14:31:07 as sensitive as this topic is, it is hard to commit to/approve something, without actually reading what we are approving 14:31:13 Let's do it this way. Everyone who is not Marie or me tell Marie and me your thoughts. We will synthesize them for the ticket. 14:31:24 riecatnor: so they're asking for permission to write a draft? 14:31:36 That way it isn't just a big free-for-all of further discussion 14:31:38 bookwar++ 14:32:11 does that make sense? 14:32:15 bcotton, I want to say this sensitively. Sometimes people just need leadership to say ok, proceed. 14:32:34 understood, just trying to make sure i understand 14:32:46 I do think peoples individual opinions here should be taken into account, which is why I am +1 to mattdm idea 14:32:48 well that was an awkward statement. anyway 14:32:58 #undo 14:32:58 Removing item from minutes: INFO by bcotton at 14:24:03 : Council members are requested to provide feedback in the D&I ticket by 1 July 14:33:41 okay, so. is there anyone opposed to giving D&I permission to pursue this (not asking for pre-approval of any text, just "yes, write a draft and let's see how it goes")? 14:33:42 I will comment on the ticket something to the extent of what we said here? We would like to review a draft 14:34:14 giving permission isn't even the right phrasing. more of "yes, please do this and come to us when you have something to look at" 14:34:20 yes, that 14:34:52 yep, that sounds good, and I'm absolutely not opposed 14:35:14 so hearing no objections, we'll move on to the request 14:35:21 riecatnor yes. 14:35:34 sounds good, commenting now. 14:35:44 ? #info Council members are requested to provide input on the content of the proposed letter to mattdm and riecatnor by 1 July 14:36:12 does this seem reasonable to everyone? (riecatnor and bookwar in particular, since you both brought up concerns about action and timing) 14:36:49 Well, I think you were right. maybe there isn't much to do beyond just reading and being aware 14:36:57 so that when they statement comes, review time will be quick 14:37:22 bcotton: ok for me 14:37:37 #info Council members are requested to provide input on the content of the proposed letter to mattdm and riecatnor by 1 July 14:37:54 if people don't have input, they can wait for the draft :-) 14:38:21 yeah. 14:38:37 anything else on this topic for now? 14:38:39 yep 14:38:40 nope 14:39:33 #topic Next meeting 14:39:35 #info The next Fedora Council meeting is 8 July. It will be a video meeting featuring rdieter from Fedora KDE 14:39:36 #info The next regular business meeting will be 22 July 14:39:59 #topic Do we have anything to announce? 14:40:01 #info This is a regular check to make sure we're communicating to the contributor (via CommBlog) and user (via Magazine) communities 14:40:17 hopefully I will have an exciting Lenovo announcement soon 14:40:21 but I do not right now 14:41:21 sounds like there's nothing else 14:41:34 if i want to add topic to the next meeting, what should I do? file a ticket or just ask bcotton? 14:41:42 bookwar: yes! 14:41:44 hi! I remembered some annoucements 14:41:48 announcements* 14:42:16 bookwar: if it requires a decision, definitely open a ticket. if it's more of a discussion, you can do either (or start a thread on council-discuss). if you're not sure, ping me :-) 14:42:21 riecatnor: ack. stand by 14:42:48 bcotton: ok, i might have one for the next regular business thing, regarding third-party CI. So i'll reach out to you 14:43:00 bookwar: sounds good 14:43:03 riecatnor: go ahead 14:43:05 Basically, we have chosen dates and a platform for Nest with Fedora and I am working on the other details now. August 6th-9th. We will be using Hopin, as the Open Source Program Office within Red Hat has a contract that we can use that will make the option very affordable. 14:43:19 yay! 14:43:42 riecatnor++ 14:43:42 mattdm: Karma for riecatnor changed to 10 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 14:43:50 riecatnor++ 14:43:50 Conan_Kudo: Karma for riecatnor changed to 11 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 14:43:54 #info Nest With Fedora will be August 6th-9th using the Hopin platform provided by Red Hat's Open Source Program Office 14:44:03 It would be cool for folks to keep an eye out for potential keynotes. Topics I was thinking of include diversity, resilience, teamwork 14:44:06 riecatnor: commblog post coming? ;-) 14:44:08 riecatnor++ 14:44:08 asamalik: Karma for riecatnor changed to 12 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 14:44:11 keynote speakers** 14:44:20 bcotton, why do you torture me so lol. yes! I will do it 14:44:54 If anyone else has some topic ideas for keynotes, or just speakers you have seen and loved, please feel free to send my way :) 14:44:56 do we have deadlines for CfP? 14:45:07 deadlines, themes, etc. would be helpful 14:45:18 bookwar, not quite. these are the details i speak of ;) 14:46:03 I have nothing else on Nest for the moment 14:46:12 I have another thing, not an announcement, but a quick topic to discuss 14:46:23 any other announcements before we move to open floor? 14:47:04 sounds like no 14:47:07 #topic Open floor 14:47:10 riecatnor: go ahead 14:48:08 I wanted to bring awareness to Code of Conduct within Fedora. The reason being, we have experienced unprecedented numbers of incidents. This work has taken up a lot of mine and mattdms time. I was mentioning this to bcotton, and he said there was a decision once upon a time to report that back to the Council. 14:48:52 I strongly believe the reason we are experiencing these is because of the chaos and unfamiliarity of the world we are living in. Pandemic fatigue, if you will, is effecting everyone, and certainly our community. 14:49:29 So, I ask, is a report needed and wanted? How often should that be done? What should be included? 14:49:31 I agree with that--pandemic fatigue. not an excuse, but as a cause of behavior changes among everyone 14:50:06 Yeah. Everyone is super-stressed out and it comes out in a lot of ways. 14:50:31 i think a monthly report of tickets opened and the general disposition (e.g. not a violation, person suspended from mailing list for a month, person kicked out of the project, etc) without identifying information sent to council-discuss would be appropriate 14:51:15 in general, i think we want to avoid naming (or implying) parties in a CoC report, but we do want the fact that we enforce our CoC to be visible 14:51:19 Does monthly seem like it could be identifying the folks in the incidents? Confidentiality is of utmost concern 14:51:36 Quarterly? 14:51:49 considering i didn't even know it was taking up so much time until you told me yesterday, i don't think that's a major concern 14:51:58 Fair enough. 14:52:04 i'd be okay with quarterly, but no longer than that 14:53:04 Ok, I need to work this into my schedule. I think if I make a template, should be no issue to do it monthly. 14:53:21 one advantage to monthly is that it gives us a sense of whether things are getting bad and thus giving us the opportunity to be on the look out and try to descalate issues before they rise to CoC violations (in cases where that's possible) 14:53:42 true 14:54:00 ignatenkobrain++ 14:54:00 dcantrell: Karma for ignatenkobrain changed to 16 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 14:54:07 these damn windows 14:54:12 lol :) 14:54:21 XD 14:54:44 that's all I got. 14:54:54 really, concurrent meetings in irc is beyond frustrating 14:55:05 dcantrell: i feel your pain. i was in three at the beginning of the hour :-( 14:55:26 anyone else? i have two things but they'll both become mailing list threads anyway 14:55:37 bcotton: but you're a chair, that doesn't count :P 14:55:58 ..just as one 14:56:58 asamalik: do you have something for open floor or did i misunderstand your last comment? 14:57:34 uh, is FESCo now at this same time? 14:57:36 * asamalik was just attempting to make a joke, no other topic for open floor from me 14:57:39 mattdm: yes 14:58:00 that seems like a particularly bad conflict. should we look at rescheduling this? 14:58:18 mattdm: yes, because with fesco it's basically a no go. we moved from Mon to Wed at this slot for the new members 14:58:25 mattdm: we're already working on that :-) 14:58:29 bcotton: ok :) 14:58:39 mattdm: moving anywhere else is a conflict, so if the council can move that would be very much appreciated 14:58:53 okay, it sounds like there's nothing else for open floor, i'll post my things to the mailing list 14:58:55 *nod* 14:58:58 thanks bcotton! 14:59:00 thanks all! 14:59:04 thanks everyone, and welcome again to our new members! 14:59:17 bcotton++ 14:59:17 dcantrell: Karma for bcotton changed to 22 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 14:59:21 #endmeeting