Discussed in 2017-11-28 Marketing meeting, first filed as fedora-marketing#267.
Collaborate together on producing one to two feature profiles per release cycle for new major features in Fedora
Every release, the Marketing Team is supposed to create feature profiles for new, major features in Fedora. For the last few years, this has not happened due to high turnover and a high, initial bar to get started (it requires researching the technical aspects of new features).
Feature profiles are helpful because they document some of the new, exciting changes in Fedora that the community already knows about. The goal is to share some of the exciting changes with the rest of the world. To an extent, this is sometimes done with the Magazine, but it needs to fit into a marketing strategy (instead of getting lucky when a developer decides to write one for the Magazine on their own).
An SOP exists in the Marketing wiki space, but likely needs an update.
The Fedora Magazine is the ideal "vehicle" for Marketing to work closely with. Design input is needed so we could create material for our Ambassadors or other community members to represent new features in the project (think of a small brochure or handout introducing Wayland, systemd, GNOME3, etc.). There are multiple ways to output the feature profiles, both to an internal audience (i.e. Ambassadors attending events) and an external audience (i.e. Fedora Magazine readers).
The new Mindshare Committee should help revive the feature profiles by committing to produce one to two feature profiles for the Fedora 28 cycle (or help support Marketing in producing these deliverables with input from other committee members).
In addition to publishing them externally, consider producing design assets or supporting material for Ambassadors to use at events worldwide to promote major, new features of upcoming Fedora releases.
Metadata Update from @jflory7: - Issue priority set to: awaiting triage - Issue set to the milestone: Future releases - Issue tagged with: marketing, needs feedback
This is on hold while we finish the ambassadors conversation. This is not blocked by that conversation (nor does this block that conversation), we are just short of effort to do both items of work at once.
Metadata Update from @bex: - Issue priority set to: None (was: awaiting triage) - Issue set to the milestone: None (was: Future releases) - Issue tagged with: blocked
Metadata Update from @jflory7: - Issue untagged with: needs feedback - Issue priority set to: no deadline - Issue set to the milestone: Future releases
Do we still have things to be completed before jumping onto this discussion?
@x3mboy I think we lack people power
In retrospect, this Features Profile task previously managed by Fedora Marketing sounds similar to the Fedora Docs Release Notes process that @pbokoc drives each release. If this ticket were picked back up, we'd likely want to align effort into this pre-existing work in the existing Fedora Docs workflow.
https://pagure.io/fedora-docs/release-notes
The Community Outreach Revamp team took a look at this ticket. We think this is a great idea, and we also think that it is happening already, just in a different form. We are now having virtual release parties, which we intend to keep for the foreseeable future. These parties generate a lot of content, videos, polls, and event stats. That paired with the release notes, we really have a lot of info about features for each release.
We are also looking at Marketing initiatives as a topic at the edge of the Revamp scope. So far, we have seen that the Marketing team is in a lull, and there is nothing wrong with that. Fedora sees ups and downs for participation in every team. Based on that, there simply isn't the person power to drive the idea further than what exists.
Our thought is if and when the Marketing Team is revitalized, this will be a great initiative for them to take up. For the time being, closing this ticket as stale.
Metadata Update from @riecatnor: - Issue close_status updated to: Stale - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.