17:30:29 #startmeeting Mindshare 17:30:29 Meeting started Wed Aug 19 17:30:29 2020 UTC. 17:30:29 This meeting is logged and archived in a public location. 17:30:29 The chair is riecatnor. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:30:29 Useful Commands: #action #agreed #halp #info #idea #link #topic. 17:30:29 The meeting name has been set to 'mindshare' 17:30:29 #meetingname Mindshare 17:30:29 The meeting name has been set to 'mindshare' 17:30:30 #chair bt0dotninja codeblock hhlp nb pbokoc riecatnor x3mboy tatica 17:30:30 #info Agenda is at: https://board.net/p/fedora-mindshare 17:30:30 #info About Mindshare: https://docs.fedoraproject.org/en-US/mindshare/ 17:30:30 Current chairs: bt0dotninja codeblock hhlp nb pbokoc riecatnor tatica x3mboy 17:30:30 #topic Hello 17:30:48 .hello bt0dotninja 17:30:49 bt0: bt0dotninja 'Alberto Rodriguez Sanchez' 17:30:52 .hello hhlp 17:30:53 hhlp: hhlp 'Héctor H. Louzao P.' 17:30:54 >) 17:30:55 .hello riecatnor 17:30:56 riecatnor: riecatnor 'None' 17:31:13 Did you mean how to install them or something else? 17:31:43 bugsmith, I followed the directions to install https://khalim19.github.io/gimp-plugin-export-layers/ and it still isn't working 17:31:54 How is everyone doing today? 17:32:09 fine and you :) 17:32:12 Hmm.. let me check the instructions 17:32:30 Great! How are you doing? 17:33:11 Great riecatnor :) 17:33:12 I am doing pretty well :) I feel antsy this week. Good thing I took a long weekend 17:33:27 cool 17:33:48 glad to read that 17:34:22 #topic commops/ambassador revamp 17:34:42 hi 17:34:49 @riecatnor can you check if it's related to a Python dependency issue? Might be a conflict from Python 2.x to 3.x. 17:34:52 I met with Sumantro & Mariana this week, things are proceeding. I wrote a blog post, I would like folks to take a look at to see if I am missing any important info 17:35:11 What is the best way for me to share a doc with folks? 17:35:45 That's great news? How about Google Docs or Etherpad? 17:36:01 maybe fedorapeople 17:36:50 https://etherpad.wikimedia.org/p/CommOps%2FAmbassador_Revamp_Blog_Posts 17:36:52 Or Pagure if an issue for it makes sense 17:36:59 right, both are good options 17:37:00 (it was in google docs but ehhhhhh) 17:37:15 We can use this moving forward 17:38:41 * bt0 is reading 17:38:48 * hhlp me too 17:39:28 bugsmith, I did confirm in GIMP it is using python 2.7 or greater (which is what the doc says, but now I need to think of 3?) 17:39:53 .hello2 17:39:54 nasirhm: nasirhm 'Nasir Hussain' 17:40:21 hey nasirhm ! 17:40:24 The end of the post appeared a bit abrupt to me. Though it's a trivial issue 17:40:31 riecatnor: Hey 17:41:00 I changed the wording a little 17:41:50 bugsmith, better? 17:42:04 I'm not sure but that is worth looking into it the are no error logs. To get a verbose log I usually try to execute gimp on a terminal window and keep an eye on the removal output to trace the issue. 17:42:13 Checking 17:42:56 Yup. Much better! 👍🏻 17:43:33 riecatnor: Thank you for working on it, I love the abbreviation: TTF 17:44:30 lol 17:44:38 reminds me of tiff files 17:44:46 or rather... truetype 17:45:09 anyways, is there any info missing in the blog post? 17:45:41 I couldn't find much missing. Is there any target timeline? 17:46:14 LGTM 17:46:55 bugsmith, I am hoping for a 6-8 month timeline. But there needs to be a fair amount of leniency as most of the work is volunteer 17:47:01 (Looks good to me) 17:47:33 it's fine, Personally I don't like the idea of putting the ambassadors program and commops in the same bucket of "dysfunction" 17:48:13 6-8 months sounds pretty lenient to me. I was wondering if a tiny hint of the timeline can also be added to the post. 17:48:27 But I'm fine with the text in general 17:48:52 I'm feeling similarly about `dysfunction` 17:49:40 mm ok, let me rethink that line 17:51:49 Changed it 17:52:01 riecatnor++ 17:52:04 :) 17:53:47 How about adding something like "The teams should hopefully be up and running to help us out with next year's Nest/Flock!" 17:54:16 That leaves it vague, and if they are helping with planning, that happens way before august :P 17:55:24 I like the idea 17:55:50 lgtm 17:56:09 How about the Both the teams will* hopefully be up and helping us with next year's Nest/Flock, ? 17:58:01 ok, added at the end 17:58:33 looks great +1 17:58:35 I had Sumantro review earlier, he was fine with it.. I just want to make sure Mariana sees it before I send it to the commblog 17:59:54 cool 18:00:25 I will stay on top of that, and hopefully get it out before the weekend :) 18:00:29 Sounds good 18:00:39 if bcotton lets me 18:01:07 * nasirhm is working on the TG <=> -ambassadors bridge. along with jwf and the IRC channel administrators 18:01:13 can we close the ticket on mindshare repo? 18:01:23 nasirhm, woohoo! thank you 18:01:50 https://pagure.io/mindshare/issue/231 18:01:52 this one 18:02:00 yes +1 to colse 18:02:05 *close 18:02:15 It would be good to close 18:03:24 done 18:04:06 #tickets 18:04:11 #topic tickets 18:04:12 lol 18:04:15 I got this guys 18:04:33 there are no new tickets, and only one updated ticket 18:04:41 #link https://pagure.io/mindshare/issue/87 18:05:38 * bt0 is reading again :p 18:06:19 participating or leading a mentor meetup at the global d&i summit(that is in the beginning phases of planning) 18:06:29 I think it is a great idea 18:07:41 +1 from my side, It would be great to collaborate with Open Source Diversity and participating or leading a session mentorship. 18:07:49 sounds great, the D&I POV will help us a lot with the new generation of contributors 18:09:48 Cool :) I am sure we will be getting updates 18:09:59 Yeah, the best part about the OS Diversity summit is, alot of us from Fedora Diversity Team are working on the organization part too 18:10:01 I can comment there that we are generally +1 18:10:14 Oh yea, I am there too lol 18:12:13 #topic open floor 18:12:35 whose got things? 18:12:53 Nothing from me 18:13:01 as a note there are 14 ticket taged as need_event_report since 5 month -> https://pagure.io/mindshare/issues?status=Open&tags=needs+event+report&close_status= 18:13:06 I have something, I think we need a new ticket 18:13:21 hhlp, good note. 18:13:25 Nothing from my side. 18:13:34 right 18:13:46 The events policy :( 18:13:53 yes bt0 18:14:02 Nice catch bt0 18:14:30 maybe we can give it a last advice before apply the policy 18:14:35 I can do it 18:14:58 I think instead of thinking "lets apply the policy", I think what is the measure of success, which is more blog posts 18:15:12 I would prefer to see that than implement some rules on people 18:15:23 I am curious if we can make that more simple for people 18:15:47 Create a template or questions to help generate the text 18:15:56 How about creating a Template for people to easily create the blog post ? 18:15:58 The event report is important 18:16:21 that is not a bad idea 18:16:22 +1 for template 18:16:25 do we have anything like that? 18:16:26 +1 18:16:38 not really 18:16:42 riecatnor: As far as I know, not yet. 18:16:54 yes not yet 18:17:09 BTW an event report could also be a few words and many photos 18:17:18 agreed Alessio 18:17:27 Who will open a new ticket for this? 18:17:39 I can 18:17:47 on Mindshare :) thanks nasirhm 18:17:48 We only need it published 18:18:16 bt0, ? 18:18:40 next add it (template) to mindshare docs 18:18:45 the event reports, 18:19:05 not matter if are only a few works and photos 18:19:34 Indeed 18:20:05 ok, so nasirhm will open a ticket, and we can begin to work on that 18:20:15 I had a different topic 18:20:24 +1 18:20:49 +1 18:20:50 Formalize a process for community to use the survey subscription we have 18:21:07 You will notice we have done a few surveys using an instance on limesurvey 18:21:45 yes we can have a open ticket forever waiting for and event report 18:22:19 *can't 18:22:36 an :) 18:22:46 I would like to add a new section here https://docs.fedoraproject.org/en-US/mindshare-committee/ 18:23:00 Under "attending and holding events" 18:23:31 oks 18:23:36 for surveys.. something like Developing and Running Surveys" 18:23:52 sounds good 18:23:53 I can open this ticket 18:25:07 Sounds good to me 18:25:50 :) 18:27:59 I am just busy writing that ticket out 18:28:11 hhlp let me update the tickets and then we will decide if need close it as not completed or something like that 18:28:11 I can close the meeting unless there is anything else? :) 18:28:27 I don't have enything more 18:28:35 *anything 18:28:46 not more from my side 18:29:47 cool 18:29:55 thanks, folks! you are the best 18:29:57 :D 18:29:57 Nothing from my side 18:30:12 #endmeeting