16:32:08 #startmeeting Mindshare 16:32:08 Meeting started Wed Apr 21 16:32:08 2021 UTC. 16:32:08 This meeting is logged and archived in a public location. 16:32:08 The chair is siddharthvipul. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:32:08 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:32:08 The meeting name has been set to 'mindshare' 16:32:08 #meetingname Mindshare 16:32:08 The meeting name has been set to 'mindshare' 16:32:17 :) 16:32:26 oh, Marie, can you send me the link? will help me with agenda. Meeting commands are fine 16:32:26 https://hackmd.io/pYt805UiQ4ug02Nsbe1Oqw 16:32:43 #chair bt0dotninja codeblock tyll hhlp nb pbokoc riecatnor x3mboy tatica siddharthvipul1 16:32:43 Current chairs: bt0dotninja codeblock hhlp nb pbokoc riecatnor siddharthvipul siddharthvipul1 tatica tyll x3mboy 16:32:43 #info About Mindshare: https://docs.fedoraproject.org/en-US/mindshare/ 16:32:55 #chair mizmo 16:32:55 Current chairs: bt0dotninja codeblock hhlp mizmo nb pbokoc riecatnor siddharthvipul siddharthvipul1 tatica tyll x3mboy 16:33:17 #topic Hello 16:33:30 .hello siddharthvipul1 16:33:31 siddharthvipul: siddharthvipul1 'Vipul Siddharth' 16:33:49 .hi 16:33:50 nb: nb 'Nick Bebout' 16:33:57 I am here from tg :) 16:34:54 let's wait for a minute or 2 before next agenda announcements and information 16:35:11 .hello bt0dotninja 16:35:11 bt0: bt0dotninja 'Alberto Rodriguez Sanchez' 16:35:12 if you have an announcement, time to fetch the link :) 16:36:16 .hello computerkid 16:36:17 computerkid: computerkid 'Grayson Penland' 16:36:29 let's move to next, I have a piece of information 16:36:59 #topic announcements and information 16:37:09 copying things from hackmd took longer than expected :P 16:37:13 I don't think I have anything new 16:37:16 lol 16:37:23 #info Fedora 34 go/no-go meeting tomorrow 16:37:32 @marie, release party this weekend? :P 16:37:39 https://hopin.com/events/fedora-linux-34-release-party 16:37:46 next weekend! 16:37:50 fri/sat 16:38:05 if folks want a preview of the schedule: https://fedoraproject.org/wiki/Fedora_Linux_34_Release_Party_Schedule# 16:38:10 #info Fedora 34 release party https://hopin.com/events/fedora-linux-34-release-party 16:38:21 #info schedule at https://fedoraproject.org/wiki/Fedora_Linux_34_Release_Party_Schedule# 16:38:22 I am just waiting to confirm times with 2 people 16:39:26 Websites & Apps Team is proposing an objective for a revamp 16:39:26 this time it seems we might slip the schedule :( 16:39:32 oh no 16:39:59 was talking to Release engineer and turns out he hasn't received a RC request yet.. waiting on new signed shim 16:40:03 also there is a discussion around the new program management team here: https://discussion.fedoraproject.org/t/help-wanted-program-management-team/28715 16:40:43 #info catch up with the new program management team discussion here: https://discussion.fedoraproject.org/t/help-wanted-program-management-team/28715 16:40:44 that's all I have for announcements :) 16:41:03 yeah same here.. we can wait for a minute if someone else has something.. else we can move on 16:41:15 I have a question 16:41:24 Sorry to interrupt the meeting 16:41:26 #info our friends at CentOS are also proposing new CoC - https://blog.centos.org/2021/04/code-of-conduct/ 16:41:34 I'm crossing my fingers for a go tomorrow :) 16:41:49 hey Eduard, sure 16:41:58 x3mboy, let's jump to next topic then :) we can discuss it there 16:42:04 #topic tickets and discussions 16:42:15 x3mboy, please go ahead 16:42:22 If the release is slip one week, the RP is still on time? 16:42:33 yes :) 16:42:34 I mean, the RP shouldn't be before the release 16:42:39 Excellent!!! 16:42:45 That's it 16:42:49 lol, either way it is next weekend 16:43:13 too many plans have been made :P and I guess we can talk about what failed lol 16:43:36 yeah, I see release party to be more than just an event after the release.. Understanding changes, appreciating efforts, meeting people etc etc 16:43:53 1-2 week range shouldn't be an issue 16:44:09 maybe from next time we can keep a buffer of 2-3 week 16:44:11 right 16:44:38 good idea 16:45:45 a release party related thing 16:45:53 we are going to test work adventure at the social hour this thursday 16:46:04 wow 16:46:22 Using outreachy intern applicants customized designs :) 16:47:06 everyone is welcome to come thursday if you are able to help test 16:47:16 Marie, if you need extra feedback or just want to have more testers, I can join! 16:47:22 2pm utc 16:47:31 tomorrow, right? 16:47:33 https://app.element.io/#/room/#fedora-social-hour:matrix.org 16:47:35 yep 16:47:41 count with me too :) 16:48:02 https://apps.fedoraproject.org/calendar/meeting/9743/ 16:48:09 Marie, If you have an event on calendar, could you extend it to me? :P if not, I can create and share it with you haha 16:48:24 oh, this! okay! 16:48:29 thank you :) 16:49:03 cool 16:49:06 siddharthvipul, I also added you to my calendar invite 16:49:15 thank you :") 16:49:37 hopefully it goes well, if not, we have the next social hour to test as well :P 16:50:17 can we talk about https://pagure.io/mindshare/issue/261 next 16:50:47 sure 16:50:55 #info https://pagure.io/mindshare/issue/261 16:51:42 Do we know someone (we as in mindshare) from Workstation team? I can't think of anyone 16:52:15 so now bcotton is not interested anymore? 16:52:17 mmm, no, but I don't see why we couldn't drive it. All that seems to be required is to staff a 45 minute booth session 16:52:38 the event is may 13-15 (thurs,fri,sat) 16:52:39 https://linuxappsummit.org/assets/2021LAS-Brochure.pdf 16:52:50 If the timezone is India or even EU friendly, I can be available for 45 minutes 16:53:08 I was looking for a sponsorship deadline, couldn't find one 16:53:24 depending on time, i could try to help 16:53:30 it seems like most folks are +1, is till here 16:54:12 I would also be happy to staff a 45 minute office hour session 16:54:55 yeah, +1 even if it's an exploratory sponsorship, I can help too 16:55:35 looks like we have good number of volunteers.. if needed, we can reach out to someone from FESCo to ensure technical presence as well 16:55:56 I think we could try out using some completed designs from : https://pagure.io/design/issue/745 16:56:44 this one is nice: https://pagure.io/design/issue/raw/files/209f927a8628b6a43438d888d39c44200671cbe004e37502d91dab50a02a8778-draft_5.png 16:56:52 yes, we can do a call to brainstorm on how to utilize the 45 hours with right materials. 16:56:56 I was also thinking about having this asset translated 16:56:59 very nice 16:57:18 needs the new logo, and a couple small changes, I have the source file 16:58:12 ok, so should I comment there that we are going to view this as somewhat exploratory, to foster new connections, to engage folks with new materials 16:58:27 and that we are moving forward with it? Because I need to get that moving.. the event is in May :) 16:58:52 (there is a chance they may say no?) 16:59:02 Marie, let's do that 16:59:18 we have 0 -1s and all concerns seem to be answered? 16:59:37 oh, and a lot of +1 and volunteer interests 16:59:37 right 17:00:26 cool, I will comment now, and on my priority to do list is send an email to the address provided 17:01:01 Can I interrupt and just say that I am very happy to get a new vps and will be moving from znc to old weechat running in tmux for IRC again :P 17:01:12 ok, next one? https://pagure.io/mindshare/issue/262 17:01:16 sorry, now we can continue 17:01:24 absolutely, Vipul :P 17:01:29 #info https://pagure.io/mindshare/issue/262 17:01:34 #undo 17:01:34 Removing item from minutes: INFO by siddharthvipul at 17:01:29 : https://pagure.io/mindshare/issue/262 17:02:03 #info ^, we agree to move forward with sponsorship and have enough volunteers to help with presence 17:02:05 #info https://pagure.io/mindshare/issue/262 17:02:53 hmmm 17:02:59 one thought 17:03:01 oh nooo, I totally missed the tag.. bt0 sorry 17:03:07 :P 17:03:16 should we invite someone from workstation? 17:03:23 don't worry 17:03:25 yes 17:03:34 this is something I can ask Matthew 17:03:36 should we invite someone from workstation? Yes 17:03:37 I will review it and comment, adding it to todo list so I don't forget 17:03:51 @riecatnor, for the conference? 17:05:02 yeah, it would be good to have an expert in the conference topic 17:05:13 unless folks are feeling fine about that 17:05:33 I just reached out to Matthew, I will see what he says before commenting 17:05:43 no no, I think it's good to have expertise or technical member there.. that's why I proposed the idea to reaching out to fesco 17:05:52 someone from workstation team would be great 17:06:06 sorry to backtrack 17:06:47 we are all wanderers in mind :) 17:08:14 which next ticket do we talk about? 17:08:32 this one, https://pagure.io/mindshare/issue/262 17:08:35 is it good to close? 17:08:58 I have not reviewed it but if you feel it's good, I have no reasons to think otherwise 17:09:11 I wasn't tracking if it got pushed out to the docs 17:09:21 not yet 17:09:31 don't see a pr 17:09:34 right, not yet 17:09:51 I can do that real quick - the text in the hackmd link is final, right? 17:09:57 yes 17:09:59 to me it seems that the discussion about making it a limited time of service got lost 17:10:43 please take a look pbokoc 17:10:51 checking 17:10:57 So it needs to say, two release cycles? 17:11:08 yep, bt0 In duration of service, should we mention 2 release cycles? 17:11:10 tyll OMG, right maybe we can discuss taht 17:11:11 https://hackmd.io/@ZBDPuu-UTnWdVWbWwAl6qg/SksTnQsr_ 17:11:16 sure 17:11:22 @riecatnor, yes, that's what I understand 17:11:26 sounds good and fair 17:12:01 yes, instead of "The representative will serve in this role until they wish to step down or the Council or Mindshare wish to replace them." it should be something like for two release cycles or until... 17:12:55 ok, I made a change 17:13:15 The representative will serve in this role for two release cycles. They may also step down before that time or the Council or Mindshare may wish to replace them. 17:13:38 +1 17:13:40 +1 17:13:51 ok, pbokoc, good to go now :) 17:14:13 pbokoc++ for docs work on #262 17:14:13 siddharthvipul: Karma for pbokoc changed to 8 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 17:14:30 and of course, bt0++ and riecatnor++ :) 17:15:05 next: https://pagure.io/mindshare/issue/31 17:15:10 I think we can close this?? 17:15:49 bt0, I see you already have a PR for issue 262 up, is it a different thing? 17:15:50 yes, I think the revamp handle this one 17:18:01 ohh right, close without merge please :) it's the same content of the hackmd but don't have the last correction 17:18:18 done 17:18:32 okay, as Marie said, let's jump to another ticket 17:18:41 #info https://pagure.io/mindshare/issue/31 17:19:26 +1 to closing 17:20:13 cool, I will go ahead and close then? 17:20:27 yes 17:20:31 +1 to close 17:20:40 let's do it.. always +1 to close tickets 17:20:46 lol 17:20:59 i think we can move to open floor 17:21:11 #topic open floor 17:21:34 I had a thing to ask (consider me a CPE liaison for a second) 17:21:44 I wanted to propose a monthly/bimonthly video call for mindshare- thoughts?? 17:21:59 We could use work adventure (free version) to make it more fun 17:22:01 let's go with Marie's question first 17:22:08 +1 for a monthly call 17:22:24 +1 for monthly call too 17:22:39 If we weren't dealing with covid, we would have def gotten together by now, and I miss everyones face! 17:22:42 about work adventure, if the experience is nice, +1 (I was facing some issues with audoio last time) 17:22:44 faces*;) 17:23:04 my face alone is enough to be called faces 17:23:10 lol 17:23:10 I can say it, no one else can XD 17:23:14 :p 17:23:19 the many faces of Vipul 17:23:24 haha 17:24:04 ok, so let's wait until after the release party :) how about may 5th? 17:24:27 sounds fine for me 17:24:31 Marie, I think monthly video call is great, to find date and time, should we do a whenisgood? or are you thinking of using one of these slots? 17:24:39 would this be to replace one of the IRC meetings? 17:24:56 tyll, that was my thought 17:25:18 we can take notes in irc and publish our log as usual 17:25:37 that is why I said bi-monthly, I wasn't sure if once a month was too much 17:26:03 wait, with bi-monthly you meant once in 2 months? 17:26:11 I thought twice per month.. always confuses me :P 17:26:11 yep 17:26:22 that would be fortnightly 17:26:23 :P 17:26:33 yeah, that's true! 17:26:33 or bi-weekly 17:26:41 for me, having an IRC meeting instead of a video meeting is quite relaxing 17:27:06 I agree.. every 2 months it is 17:27:17 tyll, I am with you, it is less pressure generally 17:27:19 for me too (hit enter too soon) 17:27:27 :P 17:27:27 I think it is nice to connect with faces and voices on occasion 17:27:58 ok, different idea. What if we organize a fun event for the team? 17:28:16 (like the ones we do with teambuilidng, but not those :) 17:28:23 * tyll is wondering if there would be value (at least for some topics) to do an audio meeting while everyone is walking, maybe for discussing ideas etc 17:28:30 maybe we could use social hours for those? 17:28:39 would be for something that does not require access to pagure 17:28:47 interesting 17:29:11 thats tough, the area i live in isn't really for walking around 17:29:37 so, there are a lot of ideas, maybe not enough time to agree on anything today 17:29:42 I can open a ticket 17:29:48 yep, let's do that (or a thread) 17:29:51 Vipul, go ahead with your CPE thing :) 17:29:52 better 17:29:56 right 17:30:14 Can I get a ping on open floor? 17:30:26 sure 17:30:35 today someone brought up the idea to have a social media account for CPE (to engage with community more).. and I think we very much consider CPE as a part of community. Could we use fedora-community for those? 17:30:56 x3mboy, we are already in open floor 17:31:03 Vipul, so this is for twitter? 17:31:05 also, just noticed, out of time 17:31:10 marie, yes! 17:31:30 @fedoracommunity.. sorry! I thought you all would be able to read my mind and get the context 17:31:33 I think this is a good idea, but I would like to work out the details on who has access 17:31:55 and I think it should be documented somehow, a ticket? ;) 17:31:57 https://twitter.com/fedoracommunity ? 17:31:59 Once I see that mindshare is happy with this, I can take it on ticket 17:32:16 well, I dont think we will come to an answer today, 17:32:19 tyll, right, that's the one 17:32:32 I don't think we even need access.. just a proxy to whom we can send things if needed 17:32:53 Marie, oh sure, we can discuss later.. I didn't expect an answer today.. just wanted to bring this to knowledge 17:33:29 what kind of engagement do you expect there? Would it be with contributors or users? 17:34:29 We need a ticket for follow up this. 17:34:29 tyll, so I imagine a couple of things.. what CPE is upto, once in a while sharing the work progress. definitely not high traffic (or even medium traffic). I don't see a lot of things 17:34:34 fair 17:34:51 let's close the meeting? we can continue the discussion though 17:35:17 sure 17:35:31 i can send an email to the list once you close th emeeting 17:35:37 thanks for chairing Vipul :) 17:35:42 #endmeeting