21:00:27 <jflory7> #startmeeting Fedora Marketing meeting (2016-07-06)
21:00:28 <zodbot> Meeting started Wed Jul  6 21:00:27 2016 UTC.  The chair is jflory7. Information about MeetBot at
21:00:28 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
21:00:28 <zodbot> The meeting name has been set to 'fedora_marketing_meeting_(2016-07-06)'
21:00:28 <jflory7> #meetingname marketing
21:00:28 <zodbot> The meeting name has been set to 'marketing'
21:00:32 <jflory7> #topic Roll Call
21:00:36 <jflory7> #info Name; Timezone; Other sub-projects / interest areas
21:01:01 <jflory7> #info Justin W. Flory; UTC-4; Marketing / Magazine, CommOps, Ambassadors, Diversity, Infrastructure-fi, and more
21:01:23 <bkp> #info Brian Proffitt; UTC-4; Social Media
21:01:58 <jflory7> #chair bkp
21:01:58 <zodbot> Current chairs: bkp jflory7
21:02:02 <jflory7> Hey Brian!
21:02:11 <bkp> Hello!
21:02:49 <jflory7> For reference, here is the meeting agenda:
21:04:24 <jflory7> Hmm, might just be us two today.
21:04:54 <MooDoo> I'll watch if that's ok
21:05:00 * jflory7 has been wondering about putting out a vote for a different meeting time again
21:05:09 <jflory7> MooDoo: Hey! Yeah, sure thing.
21:05:20 <jflory7> Will go ahead and move to announcements.
21:05:26 <jflory7> #topic Announcements
21:05:32 <bkp> I'm always down for earlier in the day
21:05:32 <jflory7> #info === "Fedora 22: End Of Life, 2016 July 19" ===
21:05:37 <jflory7> #link
21:05:42 <jflory7> #info With the recent release of Fedora 24, Fedora 22 will officially enter End Of Life (EOL) status on July 19th, 2016. After July 19th, all packages in the Fedora 22 repositories will no longer receive security, bugfix, or enhancement updates, and no new packages will be added to the Fedora 22 collection.
21:05:57 <jflory7> bkp: I'm thinking that might pull in some others who are in later timezones, like in EMEA.
21:06:02 <jflory7> #info === Fedora 24 release parties in progress ===
21:06:06 <jflory7> #link
21:06:11 <bkp> jflory7 +1
21:06:11 <jflory7> #link
21:06:16 <jflory7> #link
21:06:27 <jflory7> #info More event reports in the meeting agenda.
21:06:31 <jflory7> #link
21:06:36 <jflory7> #info There are Fedora 24 release parties happening all over the world both this month and the end of last month. You can see reports or event pages from Ambassadors at all of the above links. See if there are any release parties happening in your region! If you're interested in organizing one, check out this post on the Community Blog.
21:06:41 <jflory7> #link
21:06:45 <jflory7> #info === Flock 2016: August 2-5, 2016 ===
21:06:50 <jflory7> #link
21:06:55 <jflory7> #info Reminder that Flock, Fedora's annual contributor conference, is coming up at the beginning of next month.
21:07:06 <jflory7> eof
21:07:29 <bkp> Add: If anyone is actually going, be sure to confirm their hotel if they are staying at the conference hotel.
21:07:47 <jflory7> bkp: I think I'll put together a WhenIsGood poll for selecting a new time and send that out on the list.
21:07:48 * jflory7 nods
21:07:50 <bkp> That hotel is rather old-fashioned with their reservation procedures.
21:07:58 <jflory7> That's good to know.
21:08:09 <bkp> Like fax-machine old-fashioned.
21:08:33 <jflory7> #info If staying at the conference hotel, make sure you confirm your room ahead of time (the hotel is old-fashioned with their reservation procedures)
21:08:36 <jflory7> Heheh, oh man
21:09:00 <jflory7> Alrighty. If no other announcements, can move to action items real fast.
21:09:06 <jflory7> #topic Action items from last meetings
21:09:10 <jflory7> #link
21:09:17 <jflory7> #info === [INCOMPLETE] jflory7 Work on creating an initial "template" draft for Friends of Fedora websites example ===
21:09:22 <jflory7> #action jflory7 Work on creating an initial "template" draft for Friends of Fedora websites example
21:09:29 <jflory7> #info === [OPEN] marketing-team-member Take screenshots for F24 KDE and Xfce and upload to the screenshots page on the wiki ===
21:09:33 <jflory7> #nick marketing-team-member
21:09:38 <jflory7> #action marketing-team-member Take screenshots for F24 KDE and Xfce and upload to the screenshots page on the wiki
21:09:45 <jflory7> #info === [COMPLETE] jflory7 Post to Marketing mailing list about F24 retrospective ===
21:09:50 <jflory7> #link
21:09:55 <jflory7> #info === [COMPLETE] jflory7 Update ticket #230, remove from meeting agenda for now ===
21:10:04 <jflory7> Alright, and that's all the action items.
21:10:17 <jflory7> We have one ticket on the agenda tonight, one hopefully you can add some thoughts on, bkp :)
21:10:22 <jflory7> #topic Tickets
21:10:27 <jflory7> #link
21:10:31 <jflory7> #info === Ticket #229 ===
21:10:35 <jflory7> #link
21:10:40 <jflory7> #info "Shared, secure password distribution"
21:10:51 <jflory7> There's been some new comments in the ticket about choosing a solution.
21:10:55 <bkp> Wait, on the screenshots: I will take those
21:11:08 <jflory7> bkp: Oh, for KDE and Xfce? That would be awesome!
21:11:10 <jflory7> bkp++
21:11:19 <bkp> Now, on 229, yes, caught up with that post-Summit
21:11:34 <bkp> Was not happy to hear Rattic might be dead.
21:11:39 <jflory7> #action bkp Take screenshots of F24 KDE and Xfce desktops, add to screenshot library wiki page
21:11:53 <jflory7> Yeah, I didn't realize it was no longer under active development either.
21:12:05 <jflory7> It's a shame, it looks like a very powerful and useful tool...
21:12:30 <bkp> I've liked it so far. We can look at pass, though.
21:12:49 <jflory7> Yeah, it sounds like Infrastructure was more of a fan of that
21:13:07 <bkp> Actually, tbh, my main concern was about policy, and less about tool.
21:13:21 <bkp> Like, who holds the keys?
21:13:34 <jflory7> Me too, pass would require having an idea of how we implement it since it isn't as modular
21:13:42 <bkp> How is access determined?
21:14:16 <bkp> The nice thing about using any tool like this is that it should ensure that only authorized people have the right password.
21:14:41 <jflory7> bkp: If I recall correctly, one of the keys already being used has to be the one that allows another key, although I'm not 100% on that.
21:14:43 <bkp> If a password is leaked, we change it, and ideally only pass-authorized people can get the updated password.
21:15:03 <bkp> jflory7: Okay, will need to look
21:15:07 <jflory7> linuxmodder was saying it could be done on a directory basis in terms of having certain keys have access to only some directories, but apparently doing that isn't the cleanest thing.
21:15:42 * jflory7 nods
21:15:59 <bkp> Yeah, yick.
21:16:19 <jflory7> I was trying to think of a way we could have a caretaker sort of role, because as far as I can tell, everyone in the repository would really have the same abilities / access as someone else.
21:16:42 <bkp> Another way of doing this is using a tool like Hootsuite and assigning roles through that.
21:16:54 <jflory7> If we choose to do it on a repository basis, the entire repository's passwords would need to be changed if a key is ever removed.
21:17:05 <jflory7> bkp: Yeah, I was thinking about that. But it would be a cost factor there, right?
21:17:19 <bkp> But HS and similar tools are (a) non-free as in freedom and (b) as in beer.
21:17:26 * jflory7 nods
21:17:30 <bkp> Yeah, per seat.
21:17:58 <jflory7> Hmm.
21:18:16 <bkp> Supposedly HS is going to come up with a mid-range procing scheme that would be less expensive for organizations like Fedora. But they ain't in a hurry.
21:18:28 <jflory7> Yeah, I can imagine they're not
21:18:36 <bkp> Becuse once you get past 10 users, it jumps in cost hugely.
21:18:47 <bkp> "Enrprise" pricing.
21:18:53 <bkp> *Enterprise
21:18:58 * bkp rolls eyes
21:19:12 <jflory7> I could bring this topic up at the Infra meeting tomorrow and see if we can get technical advice about what may or may not work if we went with pass. We could then try to come up with the policy based on what would or would not work.
21:19:25 <jflory7> Heh, yeah, that's always been my biggest issue with HS.
21:19:29 <bkp> I think that would be best.
21:19:40 <jflory7> Okay, I'll bring this up with Infra at the meeting tomorrow.
21:19:44 <bkp> Key policy suggestions:
21:19:55 <bkp> Transparency
21:20:08 <bkp> Continuity
21:20:24 <bkp> Capability to slam things closed if there's a breach
21:21:11 <jflory7> #action jflory7 Bring up topic of using pass for shared password management within Fedora's infrastructure at meeting tomorrow due:2016-07-07T14:00
21:21:12 <jflory7> #idea Key policy suggestions: (1) Transparency, (2) continuity, and (3) capability to slam things closed if there's a breach
21:21:14 <bkp> "Transparency" is trickiest. We'd need to ensure people were well versed in our policy
21:21:44 <jflory7> Right. I think one thing we'd need to definitely decide up front is *how* someone is added to the repository, or what justifies someone being added.
21:21:53 <bkp> Right.
21:22:50 <jflory7> I think for me to come up with an idea about how to do that, I'd be curious to know who already has access to the accounts. I also wonder if we could use something like a FAS group to easily manage who should or should not have permissions to social media keys
21:22:53 <bkp> That's why TweetDeck or HS is attractive. The actual "real" password is never accessed. So if someone gets squirrelly, there's no issue dropping them.
21:23:01 * jflory7 nods
21:23:12 <bkp> We can always do it the mean way.
21:23:46 <jflory7> I guess we can still propose an option like that too, with HS. Maybe just consider the pricing tiers and if we could keep it down under 10 accounts or however many (not sure how many people have access now).
21:24:07 <jflory7> I feel like it might be 10 already, although not sure how many are actively using the handles.
21:24:09 <bkp> There are an unknown people who have access to @gluster, and we can't figure out who they are. So we are likley going to change the password for the account and then re-assign access from scratch
21:24:30 <jflory7> Makes sense.
21:24:39 <bkp> Like I said, kinda mean
21:24:53 <bkp> But it will determine who has the keys.
21:25:22 <jflory7> #idea Using a FAS group to keep a list of authorized users (who also have GPG keys in their FAS accounts) for managing privileges
21:25:26 <bkp> We can try to ask first in Fedora-land, though.
21:25:55 <jflory7> Right. I can bring it up with Infra, get their take on it, and we can make a decision on it next week with the info.
21:26:07 <bkp> +1, sir
21:26:30 <jflory7> #agreed Will bring the topic up with Infrastructure, get their take, and revisit next week to make a decision or work on a policy
21:26:34 <jflory7> Awesome.
21:26:46 <jflory7> Anything else here for this ticket?
21:27:08 * jflory7 doesn't have anything he can think of
21:27:12 <bkp> (FYI, will be in Tokyo next week for LinuxCon Japan. Should be at meeting, but time zones are evil.)
21:27:21 <bkp> Only that aside.
21:27:33 <jflory7> Ahhh, wow! That will be fun. :) Thanks for the heads-up.
21:27:58 <jflory7> I'll try to post out on the mailing list about it too after the Infra meeting tomorrow.
21:28:01 <jflory7> #topic Upcoming Tasks
21:28:07 <jflory7> #link
21:28:12 <jflory7> #info The Marketing Fedora 24 retrospective wiki page is now up. Anyone who has contributed or participated in Marketing this release cycle is HIGHLY encouraged to add feedback to the page with their thoughts and opinions about our performance as a team this release. Please take 10 - 20 minutes to add your own thoughts and ideas to the page this week. This helps us improve and grow as a team.
21:28:16 <jflory7> #link
21:28:27 <jflory7> I was going to try to add my notes to it after today's meeting.
21:29:23 <jflory7> I might see if decause has anything to add to this one before he gets too far away. :)
21:29:25 <bkp> I will take a crack at it this week.
21:29:36 <jflory7> bkp++ That would be great.
21:29:59 <jflory7> I'll see if mailga has anything to add to it as well.
21:30:22 <jflory7> #topic Open Floor
21:31:22 <jflory7> Okay, this meeting went by pretty quickly.
21:31:24 <bkp> Speaking of decause...
21:31:26 <bkp>
21:31:32 <jflory7> :)
21:31:43 <bkp> Just spreading the word!
21:31:57 <jflory7> There's been a lot of buzz about that slot
21:32:33 <bkp> It's a great opportunity!
21:32:38 <jflory7> Absolutely.
21:32:50 <jflory7> As for open floor, the only other topic I had was an earlier meeting time
21:33:01 <bkp> Though no guarantees of getting picked up by a presidential campaign...
21:33:16 <jflory7> Heheh :)
21:33:27 <bkp> As I noted, an earlier time would work out, if you want to send a poll around.
21:33:37 <jflory7> I'll take an action for that now.
21:34:04 <jflory7> #action jflory7 Create a WhenIsGood for a new Marketing time meeting, try to choose a new time for maybe two weeks from this meeting
21:34:18 <jflory7> We'll see how it goes based on the responses received.
21:34:21 <bkp> jflory7++
21:34:42 <jflory7> Alrighty! Nothing else from me.
21:35:05 <bkp> I'm good. Busy with world domination.
21:35:22 <jflory7> Heheh, priorities!
21:35:30 <bkp> +1
21:35:42 <jflory7> Alright, thanks for coming out tonight, bkp! Have a good time in Japan. :)
21:35:44 <jflory7> #endmeeting