#48 [Onboarding Series] Marketing
Closed: Insufficient data 2 years ago Opened 3 years ago by decause.

This ticket is a stub for working out the artwork, concept, and steps involved for awarding a fedora badge for contributors who would like to officially join the Marketing team.


Originally discussed in 2016-10-18 meeting.
Briefly mentioned in 2016-11-29 meeting.

Apologies for how long it has taken me so long to get back to this ticket, but here's a breakdown of all of the ideas we had during our original meeting when we discussed this topic (to much high interest too).

Existing resources

Before diving in too deep, this section can serve as an index for useful pages to make note of with regards to the Marketing team.

Identifying problems

In order for us to find solutions to improving on-boarding to Marketing and retaining those contributors, we first have to identify the specific problems and issues that Marketing faces. The following list is a summary.

  • Unclear tasks
    • Isn't clear what kind of tasks Marketing is working on during a release cycle and how to participate
  • Visible tasks are overwhelming
    • Most visible tasks in Marketing are highly intimidating to a newcomer, like release announcements or talking points for new Fedora releases
  • Temporary contributor lifespan
    • Many Marketing contributors come in cycles. Some people contribute for one, maybe two releases, then they might drop off. Retainment is an issue both with members and Marketing team leaders
  • Oversimplified on-boarding
    • Current on-boarding steps are simple and don't provide a chance to engage: introduce self on mailing list, say hello in a meeting,and then…?
    • Strong need for more "easyfix" / low-hanging fruit type of tasks
  • Creativity is stifled
    • Because of difficulty engaging new members, is challenging to focus on non-essential but important tasks, things other than release announcements and talking points
    • With increased communication about how to contribute ideas, Marketing could push to be more innovative with how we engage users / Linux community

Creating solutions

In the same meeting, we discussed for a long time about some of the potential solutions we could pursue in trying to solve some of the above problems (think cause and effect). Some of the ideas we had are in bulletpoints below. Note that the list has not yet been refined.

  • Working closely with others
    • Presented itself in many ways
    • Collaborating with Join SIG to engage Marketing newcomers with other areas in Fedora they might be interested in
    • Inviting other sub-projects to request help with writing or summarizing something, and have Marketing team members help write a report or short article on something happening elsewhere in project
    • Highlighting a subproject every month to showcase the things they do in Fedora – newcomers could reach out to some members of those teams to gather info and write an article
  • Improving current on-boarding pipeline
    • Going beyond the mailing list introduction and meeting attendance
    • Break down the Tasks and roles wiki page into better communicated roles and smaller tasks (low-hanging fruit) to engage new contributors
  • Better communicating with press
    • Establishing relationships with contacts in media and how we can convey Fedora news to them (and how someone could contribute towards this)
  • Social media engagement
    • Creative strategies to promote stronger engagement on social platforms like Facebook/Twitter/Google+/etc.
    • Better ways to introduce newcomers to social media presence and encourage engaging with us there
  • How I use Fedora!
    • Similar to talking points, but more general
    • Things that contributors are currently doing with Fedora, and convert them into a format that can be spread widely or shared about doing that activity
    • Later can be used for videos, interviews, streaming, or example work to share on personal channels or platforms
  • Creating a badge
    • This should be considered a low priority task until we figure out a strategy for the bigger issues like retention – a badge will attract but won't retain
  • Podcasting
    • Low barrier way to encourage contributors of doing things like feature profiles or interviews, like Chris Ward's Flock Stories podcast on Community Blog

CC

There is a lot that is covered here, and it would be extremely helpful if some of the folks from the meeting checked out this ticket and offered some ideas or feedback to the above.

@meskarune @rhea @ankursinha @mailga @bex

I will also be publicizing this discussion on the Marketing mailing list to help gain the attention and feedback from other Marketing team members.

I think a lot of info in this ticket will be useful for Fedora Hubs UX for Marketing team members. Perhaps, someone from Hubs or Marketing can comment further. @mailga @jflory7

Regarding the onboarding process, it was decided in CommOps meeting on 2017-09-13, that CommOps would work towards an integrated document to guide different teams on how-to create effective onboarding guidelines and provide them with examples.

More Info here -
https://meetbot.fedoraproject.org/fedora-meeting/2017-09-13/commops.2017-09-13-17.05.log.html

Ticket for how-to document to guide different teams on creating and implementing effective onboarding guidelines is here -
https://pagure.io/fedora-commops/issue/117

As this ticket has a lot of information, we can decide future steps for this ticket after feedback in CommOps ticket

Metadata Update from @bee2502:
- Issue set to the milestone: None (was: Fedora 26)

2 years ago

Metadata Update from @bee2502:
- Issue tagged with: meeting

2 years ago

@bt0dotninja will work on Issue #48 and break the information into smaller actions for Marketing team, file tickets and/or contact Marketing team about it.
@jflory7 will File a new ticket against Fedora Hubs with research on Marketing team for designing the Marketing Hub later on.

Edit by @jflory7: See fedora-hubs#404

Metadata Update from @bee2502:
- Issue untagged with: meeting

2 years ago

Metadata Update from @bee2502:
- Issue untagged with: help wanted
- Issue tagged with: blocked

2 years ago

Metadata Update from @jflory7:
- Issue untagged with: blocked
- Issue close_status updated to: Insufficient data
- Issue set to the milestone: Fedora 28 (to May 2018)
- Issue status updated to: Closed (was: Open)

2 years ago

Ticket closed

In the CommOps FAD, we agreed to close the on-boarding series tickets since they have stalled out. Most of them are blocking on specific Fedora Badges (and there are tickets already filed). If we want to revisit a specific team, we should file a new ticket and start from a fresh slate.

I think it's worth noting a lot of awesome work was done on this series in our beginning two years – thanks everyone who has helped on the on-boarding work over the years.

Login to comment on this ticket.

Metadata