14:36:43 #startmeeting Fedora CommOps (2018-07-02) 14:36:43 Meeting started Mon Jul 2 14:36:43 2018 UTC. 14:36:43 This meeting is logged and archived in a public location. 14:36:43 The chair is bt0. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:36:43 Useful Commands: #action #agreed #halp #info #idea #link #topic. 14:36:43 The meeting name has been set to 'fedora_commops_(2018-07-02)' 14:37:01 #meetingname commops 14:37:01 The meeting name has been set to 'commops' 14:37:16 #chair dhanesh95 14:37:16 Current chairs: bt0 dhanesh95 14:37:31 #nick commops 14:37:43 #topic Agenda 14:37:58 #link https://infinote.fedoraproject.org/cgit/infinote/tree/meeting-templates/fedora-commops-meeting-next 14:37:58 #info (1) Roll call / Q&A 14:37:58 #info (2) Announcements 14:37:58 #info (3) Action items from last meeting 14:37:58 #info (4) Tickets 14:38:00 #info (5) Open floor 14:38:22 #topic Roll call / Q&A 14:38:30 #info Name; Timezone; Sub-projects/Interest Areas 14:38:42 action commops New members, make sure you introduce yourself on the CommOps mailing list [ https://fedoraproject.org/wiki/CommOps/Join ] 14:38:49 #action commops New members, make sure you introduce yourself on the CommOps mailing list [ https://fedoraproject.org/wiki/CommOps/Join ] 14:39:01 If this is your first time at a CommOps meeting, feel free to introduce yourself to everyone and say hello! If anyone has any questions before we get started with the rest of the agenda, now is also a good time to ask. 14:39:35 .hello bt0dotninja 14:39:36 bt0: bt0dotninja 'Alberto Rodriguez Sanchez' 14:39:53 #info Alberto Rodriguez S; UTC-5;CommOps (Metrics, Community engagement), DotNet (Testing), Infrastructure(Apprentice), Marketing (Member), Ambassadors (Member), Cats (lover) 14:40:40 so we we'll wait a little :D 14:41:11 Hello! 14:41:55 Hello Algogator o/ 14:42:19 .hello bee2503 14:42:24 .hello bee2502 14:42:39 Hey, so I am a little free, but mostly lurking – I'll try to keep as we go 14:44:11 amazing :) 14:45:12 #info Dhanesh B. Sabane, UTC+5:30, CommOps, Packaging, Python, Join 14:45:12 .hello bee2502 14:45:13 bt0: bee2502 'Bhagyashree Padalkar' 14:45:16 .hello jflory7 14:45:17 jwf|matrix: jflory7 'Justin W. Flory' 14:45:43 #chair jwf|matrix bee2502 14:45:43 Current chairs: bee2502 bt0 dhanesh95 jwf|matrix 14:46:03 #chair algogator 14:46:03 Current chairs: algogator bee2502 bt0 dhanesh95 jwf|matrix 14:46:04 #info Justin W. Flory; UTC-6;CommOps, Diversity & Inclusion, Mindshare, Ambassadors, Badges sysadmin 14:47:52 bt0: Let's move ahead, shall we? 14:48:16 cool 14:48:28 #topic Announcements 14:48:55 #info === "Fedora Classroom Session: Ansible 101/102" === 14:49:14 #link https://fedoramagazine.org/fedora-classroom-session-ansible-101-102/ 14:49:51 #info === New FPM === 14:50:08 #link https://communityblog.fedoraproject.org/hello-fedora-program-manager/ 14:50:58 ! 14:51:04 bcotton++ ftw, also!! 14:51:05 go ahead 14:51:20 And jkurik++ for his years as FPM too 14:51:41 yeah 14:51:56 bcotton++ 14:51:56 dhanesh95: Karma for bcotton changed to 1 (for the f28 release cycle): https://badges.fedoraproject.org/tags/cookie/any 14:52:05 jkurik++ 14:52:05 dhanesh95: Karma for jkurik changed to 3 (for the f28 release cycle): https://badges.fedoraproject.org/tags/cookie/any 14:52:06 jkurik++ bcotton++ 14:52:08 bt0: Karma for jkurik changed to 4 (for the f28 release cycle): https://badges.fedoraproject.org/tags/cookie/any 14:52:11 bt0: Karma for bcotton changed to 2 (for the f28 release cycle): https://badges.fedoraproject.org/tags/cookie/any 14:52:42 #info === CommOps hack session accepted at Flock 2018 === 14:52:45 #link https://pagure.io/flock/issue/51 14:53:00 Yayy! 14:53:04 awesome 14:53:57 * FranciscoD lurks :) 14:54:00 without comments 14:54:07 Hi FranciscoD 14:54:25 hello! Please continue. :) 14:54:34 someone has another announcements? 14:55:18 Nothing from my side. 14:56:01 well... 14:56:21 #topic Action items from last meeting 14:56:38 14:57:58 #link https://meetbot.fedoraproject.org/fedora-commops/2018-06-18/commops.2018-06-18-14.44.html 14:58:11 #info How This Works: We look at past #action items from the last meeting for quick follow-up. If a task is completed, we move on to the next one. If it isn't, we get an update and re-action if needed. If no status, we'll try to get a quick update and move forward. 14:59:06 #info === [COMPLETED] "bt0 Split up onboarding guidelines ticket (#117) into smaller sub-tickets for different steps of work to produce the final deliverable" === 14:59:53 #link https://pagure.io/fedora-commops/issue/117 15:00:40 Ohh! And this is late, but congrats @algogator on her accepted talk too!! https://pagure.io/flock/issue/55 15:00:46 πŸŽ‰πŸ’―πŸŽ‰ 15:00:53 well i split the ticket in four parts, maybe we need another ones but is a start 15:01:00 Sorry for off-topic 15:01:14 it's amazing 15:01:23 bt0++ Thanks for splitting this up! 15:01:33 I'll try and review them later today 15:02:27 cool, thanks jwf 15:02:31 #topic Tickets 15:03:01 algogator++ 15:03:08 bt0++ 15:03:11 #link https://pagure.io/fedora-commops/issues?status=Open&tags=next+meeting 15:03:17 algogator++ 15:03:58 #topic Ticket #110: "Fedora Appreciation Week 2017" 15:04:14 #link https://pagure.io/fedora-commops/issue/110 15:04:15 #link https://screenshots.firefox.com/ZTV0ZlHbq16vevZt/etherpad.persephone.cloud 15:04:15 #link https://communityblog.fedoraproject.org/?p=5376&preview=1&_ppp=dbe0f8ee96 15:04:58 well we have the bee2502 / jonatoni / algogator talk, it's awesome 15:06:06 Happiness Packets is definitely a part of this πŸ™‚ 15:06:16 sure 15:06:47 we need talk about the logistics off the FAW, right? 15:07:09 Kudos to jwf for a detailed comment on the issue. 15:08:42 bt0: That's what I was thinking 15:08:50 I think setting goals and mapping out a game plan for "week of" FAW will help 15:08:56 I need to step away for a moment, be back soon 15:09:38 Is it possible to have a webpage dedicated for this event? 15:10:22 sounds great 15:10:53 I had a couple of ideas for this. 15:10:59 maybe a magazine post and a wiki can do the work too 15:11:07 1. We put down a counter on the web page which will build up to the event 15:11:21 but the page sounds better 15:11:29 2. The web page describes what FAW is and how anyone can get involved. 15:12:26 3. We can have small introduction to happiness packets on the page 15:12:39 4. And finally, we can use it to collect contributor stories. 15:12:50 yeah it well be a section 15:14:03 bt0: Magazine post and wiki will work too. But I think a web page can give us more visibility. Like fedoralovespython.org 15:14:24 how can i resume it as a single idea??? 15:14:48 A web page would be nice, but I am a little concerned if it will be possible to put together and build in time for FAW. We could probably achieve most of these things with a new documentation page on docs.fp.o 15:15:27 We need to leave time in for other parts of FAW like more contributor story collection and also general outreach to build awareness 15:16:05 bt0: I didn't get your question. 15:16:22 If we have time and bandwidth, we could use fedorapeople.org as a test bed for something like this, but I think it might be better to keep things simple for now 15:16:45 jwf|matrix: That's a valid concern. If docs.fp.o can give us what we need, we can go with that too. 15:16:53 jwf|matrix: That 15:16:54 We also have Flock planning this month too, which will take away some time we have until later in August 15:17:18 i want a #idea with the complete webpage functions as you describe dhanesh95 15:17:58 dhanesh95: We don't get an interactive timer, but we can get a dedicated web space for it, use our Pagure repo to collect contributions (so anyone can contribute and work on it), and give us a dedicated web presence to point people to 15:18:03 AFK again… 15:18:10 jwf|matrix: A little help there? :P 15:19:09 the docs.fp.o will work for the static things 15:20:07 i loved the counter idea too :) 15:21:41 ok, possible FAW goals can be: 15:21:56 What I had in mind was to make it easy for contributors. Not ask them to jump to 2-3 different places for thanking someone, or writing a contributor story or just send an anonymous happiness packet. 15:22:10 * bt0 wants ideas here 15:22:46 sure is better a centralized place for all FAW things 15:23:06 our problem will be the time 15:23:34 Maybe we can identify these goals as long time and try to achieve them for the next FAW. 15:23:41 s/time/term 15:24:39 yeah 15:25:34 dhanesh95: I think a dedicated website is probably a good goal to shoot for next year 15:25:54 The reason I'm a little unsure about it is because we had similar types of discussion at the 2017 Diversity FAD about this 15:25:58 But I think we overthought it and then we ended up pushing it out another year 15:26:22 I think the docs.fp.o page gives us the compromise of centralizing information and instructions for FAW 15:26:29 I have that tickle of writing #ideas and #actions, but I do not know which ones 15:26:31 Because I definitely agree it is valuable to keep people in one place and not redirect them around 15:26:51 For this FAW, I'm not able to see beyond the usual Magazine, CommBlog, social media, wiki and docs.fp.o promotions 15:27:02 bt0: I think first we figure out what direction we want to take 15:27:18 What do you all think about the docs.fp.o approach of adding a new page in our CommOps docs for FAW? 15:27:33 +1 15:27:34 jwf|matrix: +1 for that. 15:27:39 +1 15:27:57 +1 15:28:06 * dhanesh95 looks at the clock 15:28:23 Awesome, then I think it is #agreed πŸ™‚ 15:28:54 #idea Create a new page in our CommOps docs for FAW 15:29:33 Oops, even I lost track of the time 15:29:34 I have to prep for an IRL meeting soon 15:29:46 I need to run out, but I will catch up later 15:29:47 #agreed Create a new page in our CommOps docs for FAW 15:29:59 bt0++ Thanks (in advance) for chairing this meeting! 15:30:02 * jwf|matrix & 15:30:15 awesome 15:30:57 another goals for FAW?? 15:31:21 If we can't think of a direction to take now, maybe we can take some time to think and add a comment on Pagure? 15:31:58 sure 15:33:00 #idea add possible goals and logistics for FAW in the ticket #110 15:33:08 looks fine? 15:34:07 #action CommOps team add possible goals and logistics for FAW in the ticket #110 15:34:23 (sorry, i have some lag because everybody is looking brazil vs. Mexico) 15:34:29 +1 :P 15:34:33 +1 15:36:03 Shall we move on to the next ticket? 15:36:11 yep 15:36:58 #topic Ticket #155: "Fedora Podcast Episode" 15:37:24 #link https://pagure.io/fedora-commops/issue/155 15:38:11 Okay. So with this, I think bt0, x3mboy and jwf|matrix still need to figure out a feasible time, right? 15:38:16 Thursday 5 15:38:55 i will send a email and drop a message here when we confirm the hour 15:40:12 everyone is welcome 15:43:12 so, open floor 15:43:22 #topic Open floor 15:43:41 Ok, a little friendly talk... anyone? 15:43:48 I am lagging behind.. just read the docs.. +1 to docs.fpo and not jumping out too much 15:44:25 bee2502: Do jot down 15:44:28 btw, @algogator is working on fedora happiness packet website and if someone wants to do some usability testing with it.. it would be great! 15:44:51 yep 15:44:53 @bee2502: Do jot down your ideas for what are the goals that can be achieved for this years FAW. 15:45:12 @algogator: Count me in. 15:45:23 dhanesh95 sure! 15:45:41 i will put visit and test happiness packets in my agenda 15:45:45 :) 15:47:35 * dhanesh95 is heading out now. Getting back to work. 15:47:42 Thanks bt0 for chairing! 15:47:47 See you guys around! 15:48:19 bye dhanesh95++ 15:49:04 i'm need run too, it's fine if i close the meeting?? 15:51:27 Β―\_(ツ)_/Β― 15:52:30 #endmeeting