#245 Create audience-focused talking points
Opened 3 years ago by jflory7. Modified 2 years ago

This ticket serves as a stub for the long-term vision of reconstructing how we offer our talking points to be based on audience instead of edition / lab / spin, as they have in the past.


Discussed in 2017-02-07 meeting.

The original ticket didn't get much detail since I filed it immediately before the meeting began, but we still have a lot of time left for this one. Here's the key points from the meeting…

Getting the wiki pages in shape

@mailga is prepping the wiki pages for the Fedora 26 talking points that we will use for gathering this information, and they should be ready by next week's meeting on 14 February. This doesn't mean the pages will be filled, but they will be ready for us to start pointing other folks towards to add information once F26 development changes settle down.

Waiting for the change window to close

28 February is the last major change checkpoint before the Alpha release and also the date that Fedora 26 is branched from Rawhide. From this point, it will be more clear about major changes in Fedora and we can begin gathering and collecting information for F26 talking points. This is when the real work will start for this ticket.

The page was already created, so I just populated it (following the talking points SOP) with changes accepted by FESCo.

We need to involve WG to get it readable and improved.

Thanks.

Gabri

Mentioned in the SIGs (irc channels) I'm part of ( save mktg /commops), will continue to plug on social and in irc channels / MLs.

The Talking Points SOP includes:

There are different types of talking points for different types of people: general desktop users/everyone, developers, and sysadmins. They are meant to provide a short, effective answer to the question "What cool stuff is in the latest release of Fedora?" They are compelling, not necessarily comprehensive.

I don't see where the template for 26 (or in fact several previous versions) includes this idea. Perhaps in F26 we can prioritize talking to different kinds of users instead of just talking about features? I think our message is much more effective if we talk to/about users/use cases and not about outputs (editions, spins, etc.). This is not to say that we shouldn't have TPs for the various outputs, but to specifically say we need to include users.

F19 (chosen a bit at random) kind of does this: https://fedoraproject.org/wiki/Fedora_19_talking_points

If I am missing something, please let me know.

@bex I absolutely agree with this – in past cycles, we haven't done this, but there's no reason we can't refocus on this for the coming release cycle. It's still early, so we have time to improve on this. :smile:

That's is exactly what I'm thinking since I'm in the mktg group.

The problem (IMO) is cramming the wiki with 4/5 pages each release and also keep the groups focused to the TPs.

Thanks.

Gabri

It might be helpful to specifically consider the audiences for each of the three editions:

... uh, well, two. The Cloud one needs to be updated for Atomic, and it would be nice for it to also have personnas like the above two do. It currently just has a broad statement about "Developers and operators creating scale out applications on top of public and private clouds, and organizations and users running those applications." https://fedoraproject.org/wiki/Cloud/Cloud_PRD?rd=Cloud_PRD#Target_Market_.2F_Audience

I have a question -- how does each release really impact the targeted users. I suspect the overall talking points will not change significantly with each release.

Do we have user stories for each targeted group?

I suggest taking two or three groups and working on these for F26 and then expanding for F27.

Now we have the following Labs Editions:

  • Astronomy
  • Design Suite
  • Games
  • Jam
  • Robotics
  • Scientific
  • Security Lab

And the Spins:

  • KDE Plasma
  • XFCE Desktop
  • LXDE Desktop
  • MATE-Compiz Desktop
  • Cinnamon Desktop
  • SOAS Desktop

And we have the following dnf groups (tagged by developers):

  • Fedora Custom Operating System
  • Minimal Install
  • Fedora Server Edition
  • Fedora Workstation
  • Fedora Cloud Server
  • KDE Plasma Workspaces
  • Xfce Desktop
  • LXDE Desktop
  • Hawaii Desktop
  • LXQt Desktop
  • Cinnamon Desktop
  • MATE Desktop
  • Sugar Desktop Environment
  • Development and Creative Workstation
  • Web Server
  • Infrastructure Server
  • Basic Desktop
  • 3D Printing
  • Administration Tools
  • Ansible node
  • Audio Production
  • Authoring and Publishing
  • Books and Guides
  • C Development Tools and Libraries
  • Cloud Infrastructure
  • Cloud Management Tools
  • Container Management
  • D Development Tools and Libraries
  • Design Suite
  • Development Tools
  • Domain Membership
  • Fedora Eclipse
  • Editors
  • Educational Software
  • Electronic Lab
  • Engineering and Scientific
  • FreeIPA Server
  • Games and Entertainment
  • Headless Management
  • LibreOffice
  • MATE Applications
  • MATE Compiz
  • Medical Applications
  • Milkymist
  • Network Servers
  • Office/Productivity
  • Robotics
  • RPM Development Tools
  • Security Lab
  • Sound and Video
  • System Tools
  • Text-based Internet
  • Window Managers

Crossing these list, IMHO the first groups to be targeted should be:

  • University Students/Teachers
  • High-school Students/Teachers
  • Kids Students/Teachers
  • Developers
    • Java Devs
    • Python Devs
    • PHP Devs
    • Ruby Devs
    • Scripters
  • Sysadmins/DevOps (This include cloud and VM techs)
  • Administrators/Office workers/Lawyers
  • Network Engineers
  • Electronic Engineers
  • Medics/Sciences researchers
  • Musicians
  • Designers
  • Advanced Users/Linux Legends
  • Packagers
  • Gamers

I'm new into fedora-marketing but can have an opinion? let's see:
- will be great if this groups will have a targets to be accomplish, not just by: need to be;
- this might muddle new users to basically seeking information in real-time configuration and development ( config and fix , web structure, programming languages, learning Fedora) ;
- I think that these groups should be grouped: criteria for "using the Fedora" , for specific groups of users by social issues ( Fedora Artists groups - musicians, design , gamers, Fedora Science - engineers, medics, researchers, workers, Fedora Office - office workers, lawyers, writers) ;
- this will keep Fedora teams sustainability and will be more easy to work with users.

Discussed in 2017-02-21 meeting… sort of.

Where we are

We had most of our discussion in the IRC channel after the meeting slot. For the most part, there was agreement that the list should be consolidated mostly because we don't have enough hands to thoroughly cover all of those different audiences in a way where we're still producing quality content. I think it makes sense for us to focus on 4-5, and then focus in on building strong sets of talking points that would be engaging to those audiences.

This is also assuming that our talking points would be received in the way they normally are, by the WGs and SIGs about their projects, and then we do the interpretative work of putting them into buckets.

Choosing the audiences

This is something @bex encouraged us to get some Council input on too in addition to team member input, which makes sense. To help get some kind of start here:

  • Python developers: Seems like a must because there's already a lot of content available a la Fedora <3 Python
  • University students / teachers: Still a little torn because students and teachers are both different audiences in themselves
  • Designers: Of the Labs, the Design Lab is one of the strongest ones and I think we could put together strong talking points for this
  • Advanced users / Linux legends: Maybe better promoting our Spins / Labs?

This is a hasty list, but I have to head out shortly, so bear with me. Feedback and comments welcome!

My first pass:
* Education
* Developers
* Sysadmins/DevOps (This include cloud and VM techs)
* Professionals
* Science and Engineering
* Artists
* Gamers

Metadata Update from @jflory7:
- Issue untagged with: meeting
- Issue priority set to: 40 (was: 20)
- Issue set to the milestone: Future releases (was: Fedora 26)

3 years ago

Discussed in 2017-03-07 meeting.

Splitting off into two tickets

The majority of our discussion was about splitting off the two main tasks of this ticket into their own tickets. The idea of creating audience-based talking points will require more time and planning than originally thought, and we need to have a first deliverable prepared roughly in time for the Alpha release on March 21st. In the meanwhile, we're going to move forward with generating the Fedora 26 talking points as usual, and then aim to change this for future cycles (we're just not sure we're going to be able to have something ready in time for Fedora 26 if we focus on implementing this now).

Fedora 26 in new ticket, and help needed!!

A new ticket will be filed specific to Fedora 26. Also, please see the call for help to sort through the existing list of talking points!

Metadata Update from @x3mboy:
- Assignee reset
- Issue tagged with: blocked

2 years ago

This ticket is blocked by mindshare, as they need to define the "audiences" or targets to built the TPs on those targets.

Login to comment on this ticket.

Metadata