16:30:38 <jwf> #startmeeting Fedora CommOps (2017-04-25)
16:30:38 <zodbot> Meeting started Tue Apr 25 16:30:38 2017 UTC.  The chair is jwf. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:30:38 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
16:30:38 <zodbot> The meeting name has been set to 'fedora_commops_(2017-04-25)'
16:30:43 <jwf> #meetingname commops
16:30:43 <zodbot> The meeting name has been set to 'commops'
16:30:48 <jwf> #nick commops
16:30:53 <jwf> #topic Agenda
16:30:57 <jwf> #link https://fedoraproject.org/wiki/Meeting:CommOps_2017-04-25
16:31:00 <jwf> #info (1) Roll call / Q&A
16:31:01 <x3mboy> #info Eduard Lucena; UTC-3;CommOps, Marketing, Magazine, Social Media
16:31:03 <jwf> #info (2) Announcements
16:31:07 <jwf> #info (3) Action items from last meeting
16:31:11 <jwf> #info (4) Tickets
16:31:14 <jwf> #info (5) Community Blog
16:31:18 <jwf> #info (6) Open floor
16:31:25 <jwf> #topic Roll call / Q&A
16:31:26 <jwf> #info Name; Timezone; Sub-projects/Interest Areas
16:31:32 <jwf> #action commops New members, make sure you introduce yourself on the CommOps mailing list [ https://fedoraproject.org/wiki/CommOps/Join ]
16:31:37 <jwf> 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.
16:31:37 <x3mboy> #info Eduard Lucena; UTC-3;CommOps, Marketing, Magazine, Social Media
16:32:03 <jwf> #info Justin W. Flory; UTC+2; CommOps, Marketing, Magazine, Diversity, Ambassadors, and more…
16:32:24 <bt0> #info Alberto Rodriguez S;UTC-5;Commops, Metrics, Infra, DotNet
16:34:30 <jwf> #chair x3mboy bt0
16:34:30 <zodbot> Current chairs: bt0 jwf x3mboy
16:34:36 <jwf> Okay, my IRC client woke up. :P
16:34:43 <jwf> Hiya, x3mboy and bt0 o/
16:34:49 <linuxmodder> .hello linuxmodder
16:34:50 <zodbot> linuxmodder: linuxmodder 'Corey W Sheldon' <sheldon.corey@openmailbox.org>
16:34:50 <bt0> o/
16:35:24 <x3mboy> bt0, o/
16:35:30 <x3mboy> linuxmodder, o/
16:35:34 <linuxmodder> o/
16:36:16 * jwf waves to linuxmodder
16:36:19 <jwf> #chair linuxmodder
16:36:19 <zodbot> Current chairs: bt0 jwf linuxmodder x3mboy
16:36:43 <jwf> Just dropped a ping in #fedora-commops, might wait another three or four minutes, and also give me a chance to add more to the agenda since I'm behind today.
16:37:04 <bt0> ok
16:40:20 <jwf> Okay, finished it enough
16:40:32 <jwf> We can go ahead and get started, and anyone else who arrives late can chime in when they're here.
16:40:40 <jwf> #topic Announcements
16:40:47 <jwf> #info === "Help translate the Fedora User Handbook" ===
16:40:52 <jwf> #link https://communityblog.fedoraproject.org/translate-fedora-user-handbook/
16:40:58 <jwf> #help Native English speakers are needed to help bring the Fedora user handbook to English. Check out this CommBlog post to see how you can help.
16:41:03 <jwf> #info === "Share Fedora: Difficult Conversations" ===
16:41:08 <jwf> #link https://fedoramagazine.org/share-fedora-difficult-conversations/
16:41:13 <jwf> #info The Opensource.com blogging challenge continues this week, asking for people like you to share your experience about open source communities. This week's topic are difficult conversations. Check it out on the Fedora Magazine.
16:41:28 <jwf> ^^ I would encourage anyone following this community series to consider participating :)
16:41:32 <jwf> #info === "FLISoL 2017 – Linux in Latin America" ===
16:41:37 <jwf> #link https://communityblog.fedoraproject.org/flisol-2017-linux-latin-america/
16:41:43 <jwf> #info FLISoL is an international open source event held across LATAM each year since 2005. Fedora was a part of it, and you can get a quick overview in this introductory article by x3mboy!
16:41:45 <jwf> <eof>
16:41:51 <jwf> Anyone else have anything they'd like to throw out there?
16:42:20 <x3mboy> Nothing from me
16:42:23 <bt0> no
16:42:34 <Rhea> sorry guys i am late
16:42:54 <Rhea> (I went to just quickly pee but i saw imperfection in my makeup...) :D
16:43:18 <Rhea> AM I CONNECTED?
16:43:35 <bt0> :D
16:43:51 <Rhea> Ok i think that it works... I never know when I lock the pc
16:43:54 * jwf waves to Rhea
16:43:58 <jwf> #chair Rhea
16:43:58 <zodbot> Current chairs: Rhea bt0 jwf linuxmodder x3mboy
16:44:08 <jwf> #topic Action items from last meeting
16:44:13 <jwf> #link https://meetbot.fedoraproject.org/teams/commops/commops.2017-04-11-16.29.html
16:44:22 <jwf> #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 it if needed. If no status, we'll try to get a quick update and move forward.
16:44:28 <jwf> #info === [COMPLETE] jwf File ticket upstream with FAmSCo about Ambassador event reports ===
16:44:32 <jwf> #link https://pagure.io/famsco/issue/422
16:44:36 <jwf> #info === [COMPLETE] jwf Assign ticket #70 to x3mboy ===
16:44:40 <jwf> #link https://pagure.io/fedora-commops/issue/70
16:44:46 <jwf> #info === [COMPLETE] bee2502 File ticket #108 on geographic-based metrics :) ===
16:44:50 <jwf> #link https://pagure.io/fedora-commops/issue/109
16:44:56 <jwf> #link https://pagure.io/fedora-commops/issue/109
16:45:02 <jwf> #info === [IN PROGRESS] jwf Continue working on new editor guidelines for how folks can help with editing / scheduling articles ===
16:45:09 <jwf> #action jwf Continue working on new editor guidelines for how folks can help with editing / scheduling articles
16:45:15 <jwf> #info === [COMPLETE] jwf Share the hack session details on the mailing list ===
16:45:17 <jwf> <eof>
16:45:24 <jwf> That was it for action items… :)
16:45:24 <Rhea> Justin had an action item "when do we hack thing again"
16:45:35 <Rhea> :D
16:45:50 <jwf> Rhea: Yeah, we can likely throw one on again for this week… I think it would be helpful too.
16:45:52 <jwf> #topic Tickets
16:45:56 <jwf> #link https://pagure.io/fedora-commops/issues?tags=meeting
16:46:06 <jwf> So, as a brief note here first—
16:46:26 <jwf> (1) I didn't have a chance to really look at tickets before the meeting for what to cover or not in the meeting
16:46:56 <jwf> (2) However, I think it would be more helpful to make sure some of the important tickets we're working on are assigned, and then leave it to the ticket assignee to choose whether to add it to the meeting agenda or not
16:47:26 <jwf> (3) So I was thinking we can go through the two tickets on the agenda now, and then after, make sure some of our relevant tickets have a lead person working on them
16:47:28 <jwf> <eof>
16:47:37 <jwf> Does this all sound reasonable?
16:48:25 <bt0> yup
16:48:29 <Rhea> Hmm.
16:48:44 <Rhea> Mhm.
16:49:08 <x3mboy> +1
16:49:17 <jwf> Okay, cool. For the first ticket, #70, I actually think we do have some stuff we can cover now!
16:49:29 <jwf> #info === Ticket #70: "FOSS Student Pack" ===
16:49:33 <jwf> #link https://pagure.io/fedora-commops/issue/70
16:49:42 * jwf takes a minute to do a mental CTRL+R
16:50:40 <x3mboy> This one is mine
16:50:57 <jwf> x3mboy: Want to take the floor for a quick update?
16:51:33 <x3mboy> I roll out the survey in my FLISoL, I need to upload results, but I want to wait until FLISoL ends (There are some locations that relocate their event)
16:51:59 <bt0> (like Mexico City :D)
16:52:14 <jwf> Okay, cool. So still expecting some responses? Also, how much feedback are we looking at right now?
16:53:14 <x3mboy> The feedback I hope from the surveys are the commonest packages of software used by students, and how they saw Linux and FLOSS
16:53:50 <x3mboy> That would help us to create the first draft list about what software should be included inthe Pack
16:54:31 * jwf nods
16:54:33 <x3mboy> Also, I want to run a survey inside the community, (probably through an CommBlog Article) about the Pack, most thinking on presentation of the pack
16:54:57 <bt0> sounds good
16:55:05 <x3mboy> With this 2 feedbacks we can discuss the final steps to follow
16:55:23 <jwf> +1. Sounds like you have two action items here to keep momentum on this ticket. :)
16:55:40 <x3mboy> I'm hoping end of June (sorry if it feels lfar away, but at the end of May I will be on vacations)
16:56:15 <x3mboy> Also, anyone is invited to take the lead when it feels needed
16:56:43 <jwf> I think you've got a good timeline here. :)
16:56:48 <jwf> Let me take some quick notes for the minutes.
16:57:18 <jwf> #info Survey was given out during FLISoL by x3mboy and bt0 (some still in progress, so not yet finalized).
16:57:39 <jwf> #info Most feedback about the most common software used by students and how they see Linux and open source
16:57:44 <bt0> question, Mexico is in NA or Latam?
16:57:52 <x3mboy> bt0 Latam
16:57:58 <jwf> Heh, interesting question, but I guess LATAM
16:58:01 <jwf> Yeah
16:58:14 <bt0> in the ambassadors is listed in NA
16:58:24 <Southern_Gentlem> can we get some of these surveys on a someplace like google or some other site that all of us can use for events
16:58:30 <jwf> Hmmm… probably needs to be clarified.
16:58:35 <Southern_Gentlem> bt0,  its latam
16:58:44 <bt0> ok, :)
16:58:46 <jwf> x3mboy / bt0: How did you distribute the surveys? Google form?
16:58:49 <Southern_Gentlem> clarified many times
16:59:17 <x3mboy> jwf I did manually
16:59:21 <Southern_Gentlem> can see something like this to be coming out of marketing
16:59:34 <x3mboy> I have to upload the results in the GForm
16:59:47 <Rhea> o.o
17:00:05 <x3mboy> Southern_Gentlem, It is at: https://docs.google.com/forms/d/e/1FAIpQLSf0vm8MOoCc05Nyv_fXBBBsKHroeYzzUUkidSSv3WHwuteWiA/viewform?usp=sf_link
17:00:31 <jwf> #info Next steps are to create draft list about what tools in Fedora would be helpful to include and also running a survey to Fedora community about how to present the pack
17:01:00 <jwf> #info Once this feedback is collected, a first draft of what this looks like can be expected around end of June
17:01:15 <jwf> bt0: Curious, where did you see Mexico referred to as part of NA?
17:01:43 <Southern_Gentlem> jwf there are some older docs that need to be weeded
17:01:45 <Rhea> Just a random thought based on discussion i had earlier about something else... what about physical pack?
17:01:51 <jwf> x3mboy: Okay, cool. A spreadsheet would probably be easiest to process, but we can probably deal with that once you have it all collected. :)
17:02:04 <x3mboy> :D
17:02:05 <jwf> Southern_Gentlem: Probably. If we have a place to update it, might as well do it now.
17:02:11 * bt0 here: https://fedoraproject.org/wiki/Ambassadors/MembershipService/Verification?rd=Ambassadors/CountryList
17:02:23 <jwf> Rhea: I think that would require budget that we're not yet in a place to request or work with.
17:02:50 <jwf> bt0: Ooh, that page… that's managed by a script in Infra that uses literal continents / regions for grouping Ambassadors.
17:02:52 <Rhea> physical pack - could be just a flyer with a bunch of short links, such as the six different locations to download Fedora (workstation, spins, labs, cloud, server, arm) and then list of the tools and stuff
17:02:54 <x3mboy> bt0, https://fedoraproject.org/wiki/Fedora_Ambassadors_Latin_America_(FAMLATAM)?rd=Fedora_Ambassadors_LATAM here is listed as LATAM
17:03:23 <jwf> Not sure how we could go about updating that specific page, but you're right, that is confusing.
17:03:33 <bt0> Ok :)
17:03:34 <Rhea> place where to - easy - universities, random students/ambassadors can get them printed locally, and deliver to university where they can ba randomly placed in the hall, chill place, etc
17:03:36 <Rhea> libraries
17:04:22 <x3mboy> Rhea, https://x3mboy.fedorapeople.org/StudentPackSurveyEN.pdf
17:04:46 <jwf> Rhea: This sounds a bit like a press kit that Marketing might try / is trying to produce, to help assist Ambassadors with these in-person kinds of advertising / promotion. :)
17:04:51 <x3mboy> I'm pretty sure the email is in both list (Ambassadors LATAM and CommOps), but glad to share it here
17:05:00 <Rhea> well maybe, i dont know about those things...
17:05:12 <Rhea> i'm just thinking of student-targetted
17:05:17 * jwf nods
17:05:37 <x3mboy> Rhea, maybe QR Codes???
17:05:49 <x3mboy> Maybe publicize the Play Store Apps???
17:06:12 <Rhea> o.o
17:06:30 <jwf> Rhea: I understand what you mean. I think this is a ball we'd want to leave in Marketing's court, since this is more of their area, particularly with flyers / promotional material / etc. Ideally, we'd want to coordinate with Marketing once we have this idea finished out a bit.
17:07:30 <x3mboy> +1
17:07:36 <jwf> Okay, so—
17:08:03 <x3mboy> I have 2 actions with this ticket
17:08:08 <x3mboy> Should we move on???
17:08:27 <jwf> x3mboy: I think we can action you for two things here, no? One, to collect feedback from the surveys and begin working on a draft once you have it collected, and two, putting together a CommBlog article to try to poll the community on how they would like to see this pack presented?
17:08:42 <x3mboy> Yes
17:08:43 <Rhea> Well my point is also that everyone who does these things never includes all the locations to download fedora, and the getfedora page doesnt have them all, it's hidden-as-F****
17:08:48 <jwf> Not all of these to be completed by next week, of course, but just as two bigger visions here :)
17:08:52 <Rhea> six different download pages
17:09:02 <jwf> Rhea: With the Spins / Labs pages, you mean?
17:09:03 <Rhea> getfedora lists two or three
17:09:22 <Rhea> workstation, server, cloud, arm, spins, labs
17:09:38 <jwf> #action x3mboy Work on collecting FLISoL feedback to use for putting together a first draft of what to include in Student Pack
17:09:44 <x3mboy> And don't forget about alt
17:10:01 <Rhea> alt?
17:10:19 * x3mboy didn't know about its existence until last week
17:10:24 <jwf> #action x3mboy Begin drafting a Community Blog article to poll community on ways they think the student pack should be presented
17:10:28 <x3mboy> Rhea, https://alt.fedoraproject.org/
17:10:38 <jwf> x3mboy: One more thing—do you think it makes sense to bump this off the meeting tag until you have news to share?
17:10:47 <Rhea> okay lets make it seven (i did know about this page but it doesnt bring anything new to the table, does it?)
17:10:50 <jwf> So then, once you need feedback or want to discuss, you can add the meeting tag back. :)
17:11:16 <x3mboy> jwf, open to hear feedback and opinion, but nothing more from me
17:11:24 * jwf nods
17:11:47 <jwf> x3mboy: Okay, cool. So whenever you want to hear feedback or get thoughts of others, just add the meeting tag back in Pagure. :)
17:11:50 <x3mboy> Rhea, the minimal and netinstaller
17:12:06 <jwf> #agreed Meeting tag will be removed from this ticket until there are more updates, but x3mboy will add it back when feedback / thoughts are needed
17:12:26 <jwf> #info === Ticket #92: "Start a yearly Fedora Appreciation Day" ===
17:12:27 <linuxmodder> and the cloud / nightly images jwf  Rhea
17:12:33 <jwf> #link https://pagure.io/fedora-commops/issue/92
17:12:53 <jwf> Okay, so this ticket is mostly an "oops" for me, because I finished my re-write of this ticket, but it's not yet done
17:13:04 <jwf> I'm strongly pushing for this to be done in the next week and it's a high priority item for me
17:13:31 <jwf> #action jwf Finish rewriting Fedora Appreciation Week ticket based on feedback from old ticket, comments in Diversity WG Pagure, and in-person discussions
17:13:51 <jwf> I don't have many other comments to add in here right now, though
17:14:02 <jwf> Past week or two has been a little crazy
17:14:51 <jwf> However, unless anyone has something they want to put out for Appreciation Week, this does leave us a little time to take a moment to look at other tickets in the big picture
17:15:10 <x3mboy> Not for now
17:15:54 <jwf> And a typo above that I missed, * because I never finished my re-write, rather. :P But it is started.
17:16:06 <jwf> Anyways…
17:16:13 <jwf> #info === Looking at other tickets ===
17:16:47 <jwf> So, this is an idea that I think would be helpful for us in the long run, and also, might make it a little less intimidating to chair some of the CommOps meetings. :P But basically…
17:17:59 <jwf> #idea Every active ticket should have an owner or assignee, and during meetings, it is the ticket assignee's responsibility to give updates or ask for feedback, if it's needed. Otherwise, if the assignee doesn't have anything to share, the ticket can be kept off of the meeting agenda until feedback is needed. Tickets without assignees can be brought up during meetings to find out how to move forward.
17:18:34 <jwf> Hmm, maybe I should have split that up in multiple lines, but hopefully that makes sense still.
17:19:00 <x3mboy> #idea if a ticket get more than a X time (fixed and voted for the team), can be taken by other to work on
17:19:14 <Rhea> OH just off topic - x3mboy i forgot, atomic has its own page as well, that makes it 8 download pages :D
17:19:24 <jwf> x3mboy: Ah, so you mean if there hasn't been any progress or updates?
17:19:32 <x3mboy> jwf, yeap
17:19:38 <jwf> x3mboy: +100.
17:19:41 <x3mboy> Rhea, :S
17:19:46 <bt0> jwf, +1
17:20:01 <bt0> x3mboy,+1
17:20:25 <Rhea> About this thing jwf did you work on F-appreciation day/week? (new ticket)
17:20:48 <jwf> Rhea: Heh, see above… not yet, but it's on my high priority list for this business week
17:21:03 <jwf> Got jumbled up somewhere along the way into this week. :P
17:21:10 <Rhea> oh sorry i missed that item
17:21:38 <Rhea> okay, when you do you can assign it to me if you want
17:21:48 <jwf> No worries. There's a lot of "jwf" lines above, sometimes it looks like a little sea of text, heheh
17:22:02 <jwf> Rhea: Okay, cool, that's good to know – I'd be happy to pass it off to you while I'm away
17:22:46 <jwf> Anyways, bt0, I see you have #109 on geographic-based metrics (and also saw that Pagure repo pop up), so I think you're making progress there. :)
17:23:00 <jwf> Was there anything worth bringing up now, or is it still a work-in-progress?
17:23:09 <bt0> yeah
17:23:22 <bt0> work in progress
17:23:31 * jwf nods
17:23:50 <bt0> I need  the bee and skamath review
17:24:15 <jwf> #info #109 (Metrics based on Geographical location in FAS) is still a work in progress. bt0 is working through this ticket, needs review by bee2502 / skamath
17:24:30 <bt0> :D
17:24:49 <Rhea> hey lovely people, i'm gonna bail on you because i need to be somewhere else before my next meeting!
17:25:00 * Rhea disappears in a poof of smoke
17:25:14 <jwf> Rhea: Okay, makes sense – see you around. :)
17:25:17 * bt0 lol
17:26:00 <jwf> Okay, looking through everything else, I think it's pretty clear what we're all up to. Hopefully in future meetings, we can try to lean a little more on ticket owners to take the floor for some of their topics. :)
17:26:20 <jwf> I feel like we're all pretty clear on what's going on right now, though… is anyone confused on what to work on or need clarification on anything?
17:26:29 <jwf> Otherwise, I think we're good on tickets for the time being
17:28:30 <jwf> Tickets, going once…
17:28:40 <jwf> Going twice…
17:28:46 <jwf> And thrice…
17:29:01 <jwf> #topic Community Blog
17:29:04 <jwf> #info Skipping for this week, will pick up in time next week!
17:29:06 <jwf> jwf-- :P
17:29:10 <jwf> #topic Open floor
17:29:37 <jwf> Okay, so… anything else we want to cover here for open floor?
17:29:57 <x3mboy> Yes
17:30:07 <jwf> x3mboy: Floor is yours!
17:30:17 * jwf also digs for his laptop charger in the meanwhile
17:30:43 <x3mboy> I think we can/could/should schedule another hacking session
17:31:02 <x3mboy> Like the one we did 2 weeks ago
17:31:51 <jwf> Oh, yeah, we were going to talk about that too!
17:32:28 <jwf> Is there any other day / time than Thursday that works for you all? As of a few hours ago, I had my entire Thursday crossed off for free time…
17:32:38 <jwf> I'm partially flexible for Wednesday and Friday
17:33:40 <bt0> Friday is good for me (because I don't have social live)
17:33:49 <bt0> :D
17:35:05 <jwf> :)
17:35:16 <jwf> Okay, Friday afternoon here is good for me, let me check the specific times…
17:35:29 <x3mboy> Friday works for me
17:37:12 <jwf> Between 14:30-16:00 CEST works for me, so that's 12:30-14:00 UTC, and 8:30-10:00 US ET.
17:37:37 <jwf> Or, I could maybe do 19:00-20:00 CEST too
17:38:28 <jwf> 19:00-20:00 CEST == 17:00-18:00 UTC == 13:00-14:00 US ET
17:38:28 <jwf> Any of these times open for either of you?
17:39:45 <bt0> 12:30-14:00 UTC
17:41:20 <jwf> bt0: That's preferable for me :)
17:41:34 <jwf> We can ping on the mailing list to see if this works for more folks, but let's tentatively aim for then
17:41:52 <bt0> ok, fine
17:42:11 <jwf> #agreed Tentatively aiming for Friday, 2017 April 28, 12:30-14:00 UTC hack session
17:42:24 <jwf> #action jwf Get feedback about proposed hack session time on mailing list
17:42:28 <jwf> Okay, cool. :)
17:42:32 <jwf> Anything else to cover here?
17:42:55 <resilva87> Hi guys! Let me ask, how can I find more about this hacking session? :)
17:43:11 <jwf> resilva87: Hiya!
17:43:22 <jwf> resilva87: Did you catch the details of the last one or is this new to you?
17:44:00 <resilva87> jwf I'm kind of following your conversation but I don't know what this is about :P
17:44:15 <jwf> resilva87: You can see more about what a hack session is here. :) https://fedoraproject.org/wiki/Hack_session
17:44:23 <resilva87> great :D, ty
17:44:36 <jwf> resilva87: They're mostly times for us to all sync up in audio/video calls to work on tasks, ask questions, and collaborate. :)
17:44:55 <jwf> resilva87: Sometimes they can be noisy, other times, we're all quietly working on things until someone has a question or wants to bring something up. :)
17:45:23 <jwf> In an international setting, it's the best we can get to working in the same office or building, and leaning over to ask a neighbor a question on something.
17:45:51 <jwf> Or at least, that's kind of how I've thought about them. Other times though, they can be quite talkative if we have something to discuss. :)
17:46:33 <jwf> resilva87: If you happen to be free at that time, you're definitely more than welcome to join! We either use a BlueJeans instance or Google Hangouts.
17:46:49 <resilva87> hehe that sounds cool, a bit chaotic though :P
17:47:06 <resilva87> jwf sure, I think 12:30 utc is fine for me
17:47:29 <jwf> Sometimes, but we usually do get work done. There's a light agenda prepared ahead of time too, but maybe we can have an open Etherpad or doc somewhere for people to put what they want to work on.
17:47:35 <jwf> Actually, I think this would help a lot
17:47:55 <jwf> #action jwf Create Etherpad and put out open call for what folks want to work on specifically before the hack session
17:48:02 <jwf> Will include this on the mailing list post :)
17:48:20 <jwf> Anything else we want to cover before closing? Comments, questions, concerns, ideas?
17:49:10 <jwf> Going once…
17:49:17 <bt0> nop
17:49:20 <jwf> Going twice…
17:49:26 <jwf> And thrice…
17:49:38 <jwf> Okay, folks, thanks for coming out today! Until next time… :)
17:49:40 <jwf> #endmeeting