Below is the general idea I had for how I think we can pursue a marketing campaign for promoting contributions.
What kind of structure will this project have?
First, we take one month to prepare for the next. Continuing with this EPEL example, which I think we should just do as our first go around, we take the month of July to prepare the content for August. It gives us time to do the work and get our ducks in a row without setting any expectations in the broader community before we’re ready.
Second, we choose three pieces of content to put out for the month. This could be something as small as a tweet to as big as a blog post. We can work on unique ways to present the needs of the EPEL team. Then in the month when the content gets published, we’ll have three opportunities throughout the month to highlight this need.
How do we make this happen?
Since there are three main people who seem to be the most focused on marketing right now, each of us can bring one thing to the table. It can be whatever we want, but we may want to check in with each other to see if we’re too similar to other ideas. We make sure everything is ready to go by July 31 and then coordinate with the appropriate channel owners to post the content we prepared.
Is that it?
Yup. At least in my opinion this should be. It’s a relatively basic plan, but I think that if we run one campaign and feel like this workflow works for us, then replicating it for the next month and the month after that will be easier. If it doesn’t work out, it is what it is, but I think it’s worth a shot.
In summary, we take a month to come up with three engaging pieces of content about the EPEL team that will be posted at spaced out intervals over the course of the following month.
For those of us in the marketing team who are less familiar with EPEL, Fedora has some great documentation on it. We also have good insight from @tdawson in our ticket for EPEL marketing that give us more context on where the need is. The main thing they need is actually contributors - not users.
Content Proposal #1: Tweet?
Here’s a tweet we can start the “series” with. I’m not happy with it, but I figure a simple call to action will get the job done and preface the two other things we want to post.
Do you use EPEL packages in your day to day? Consider giving back by helping with packaging and maintenance! EPEL has millions of users who would be grateful for the community support.
I’m not the most confident about it, but I just want to get the ball rolling.
Content Proposal #2: Blog post
I have an idea of writing a blog post that could look like a Q&A to show where EPEL is at right now and what the specific need is. Troy mentioned the business case for dedicating resources to supporting EPEL, which I think could also work as blog post that throws the idea out there for the broader FOSS community to discuss.
Any other ideas for blog posts would be helpful. As long as the scope isn’t crazy and we can get our heads around it, we’re good.
Content Proposal #3: ???
No idea what the third thing can be. Let’s think one up! May be another tweet or maybe something discussion oriented, like linking to Discussion topic that begs an interesting EPEL-related question? Ideas welcome.
If we can organize an interview for the podcast I think that would be cool, but I don’t think we’ll have as much luck with a YouTube video unless someone with experience can help us with the production. There’s already another thread for a YouTube video but it seems to have cooled down.
I’ve been out of town for a week, so I’ve not been able to comment until now.
I’d talked to a couple other EPEL Steering Committee members and they were thinking of doing a survey. Have it run all of August.
August we’ll also have two different conferences that we will be talking about EPEL. At Fedora Nest I’ll be giving a “State of EPEL” presentation (Virtual). Carl George and I will also be giving a “State of EPEL in CentOS” presentation (Live/Recorded) at the CentOS Dojo.
We would like to promote the survey, and any other marketing campains that we have at those presentations.
Fantastic! The marketing campaign is to increase awareness about EPEL and trying to show potential contributors why it’s worthwhile. Having something like a survey would be a great call to action. You get greater insight and it serves as a first step for someone who could be interested in working on EPEL.
I looked up the dates for the upcoming talks you mentioned just for reference. We got a little more incentive to get this done, haha.
Nest with Fedora: Thu - Sat, Aug 4-6
CentOS Dojo: Thu, Aug 25
Will you guys be putting together the survey and we get a link to pass around or do you want us to help with this? Just asking so we know who owns what and things don’t accidentally fall through the cracks.
This is what we’re looking at so far. I’m adding the two events so we can keep them in mind when “publishing” the other things we would like to do.
Just a thought, but I think the survey should be completed first so that we can link to it in all the events and pieces of content.
State of EPEL talk at Nest with Fedora (with survey available)
Tweet from official Fedora account (with a link to the survey I would think)
Podcast episode at some point
Blog post at some point
State of EPEL talk at CentOS Dojo
We have our work cut out for us, lol.
Survey: @tdawson, let us know what you are thinking for the survey so we can start on that and/or support.
@x3mboy, what do you need in order to make the podcast episode happen? Should we come up with a list of questions? Let us know how we can support.
@tdawson or @carlwgeorge, would one or both of you be available for an podcast interview sometime between now and next month? I expect Eduard will be driving this, but I want to ask as of now for scheduling purposes if we can get this to work.
I own this as of now, but I’m still trying to figure out what to write that adds to any discussions going on within EPEL instead of rehashing what will already be discussed this month. I am also limited by my lack of technical skill so I don’t want to talk above my pay grade. I hope I can make something work, lol. If anyone else would like to write something instead, I am open to that also.
I will be around the next couple of weeks for a podcast. I think @carlwgeorge will be also.
I will be meeting with the Red Hat EPEL employees (CPE team members) on Monday (July 25 15:00UTC) to talk about the survey. I could get you an invite if you or any of the other Fedora Marketing people wanted to attend. If any other EPEL Committee members want to attend also, let me know.
I’m working during that time, but I should be able to jump on unless something work-related pulls me away. If it’s ok for me to drop off at 15:30 UTC, then I would like to join if only to learn more about EPEL.
If I can’t join, the main thing that comes to my mind is to add a call to action at the end of the survey as well. If they just answered a bunch of questions about EPEL but aren’t contributing themselves, asking them if they would like to with appropriate links on where to start could be a great opportunity.
Here are some of the questions I’ve been thinking about for the interview. I figure there will be one part where we’re covering more introductory information and then the second part will be more of a discussion. Should we outline like an agenda? What do you recommend? EPEL Interview Show Notes
I’ve been listening to previous presentations on EPEL and I would like to try to take the conversation in a new direction that hasn’t already been covered. Specifically, the latest interview I found was with the excellent @itguyeric and his cohost Brian Smith. It could be worth (re)listening to - I finished listening to it today. Maybe there’s something we can add? Demystifying EPEL | Red Hat Enterprise Linux Presents 29
From a scheduling standpoint, I’m in EDT (UTC-4). For this (assuming I’m in it? I don’t want to assume, lol) as long as it’s after office hours I’m good. That may be tough, though.
Lastly, I assume you know what we should have for like the setup? I’ve never done anything like a podcast. Will we basically just jump on a call and you have all the recording things to make the magic happen?
I don’t know if the Fedora Podcast has a certain structure it should follow, but I am also a fan of longer podcasts. For planning purposes, I would like it to be between 30-60 minutes of duration. We’ll see what happens, lol.
Similar to the above point, I’m not sure if there are already set things like having an intro, going through a few details first, covering the meat of the episode, and then doing some kind of sign off. I have ideas of what we can do, but I want to take Eduard’s lead because he’s worked on this before.
This sounds interesting. What do you think this could look like? For something like this, I think your idea about this being branded in some way makes sense. Otherwise, you don’t have a way to identify the thing that supposedly has a schedule.
Thanks for setting it up, Eduard! I added in my notes and a general structure I think we can follow. This first episode may be experimental (like this whole campaign idea), but I’m excited for it.
EPEL team - we can have some links to resources for EPEL in the show notes. If you want, please provide the following details that you would like to include so we can make sure to add them.
Link to point of contact’s details if provided (if you want, understandable to not want to be pinged for everything, haha)
Insert link to main EPEL IRC/Matrix channel
Insert link to main EPEL long-form discussion channel, whether it’s in Fedora Discussion or a mailing list
Also, here is a WhenIsGood to schedule the interview. Just select the times that work best for you over the next two weeks and hopefully we can make this happen! Sorry that it’s after hours but otherwise it’d be hard to carve out time to record properly. Last, since we’re all in the Western Hemisphere, the schedule is in EDT. UTC breaks my brain so I figured this is easier. http://whenisgood.net/jk5jzwn
If Eduard, myself, and one representative from the EPEL team can find a time, we’re good to go, but other team members are also welcome!