Add a target audience to each book file's information so that it outputs with the Abstract

Bug #1319394 reported by Anne Gentle on 2014-05-14
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

In each book file, best to describe the target audience -- possibly study the personas and match up with those.

Stephen Gordon (sgordon) on 2014-06-03
Changed in openstack-manuals:
milestone: none → juno
Tom Fifield (fifieldt) on 2014-10-22
Changed in openstack-manuals:
milestone: juno → kilo
importance: Medium → Wishlist
tags: removed: install-guide
Tom Fifield (fifieldt) on 2015-05-01
Changed in openstack-manuals:
milestone: kilo → liberty
Brian Moss (bmoss) on 2015-11-20
Changed in openstack-manuals:
milestone: liberty → mitaka
assignee: nobody → Brian Moss (bmoss)
Lana (loquacity) wrote :

Audience-based segmentation is hard, mostly because audiences don't self-select their audience type very well, but also because the audiences within OpenStack are tricky to pin to a wall. At the Mitaka summit in Tokyo, we agreed that we want to move towards task-based segmentation rather than audience-based. Marking this as WONTFIX.

Changed in openstack-manuals:
status: Confirmed → Won't Fix
Brian Moss (bmoss) on 2016-02-19
Changed in openstack-manuals:
assignee: Brian Moss (bmoss) → nobody
Changed in openstack-manuals:
milestone: mitaka → none
Anne Gentle (annegentle) on 2016-04-18
Changed in openstack-manuals:
importance: Wishlist → Undecided
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers