Add a target audience to each book file's information so that it outputs with the Abstract
Bug #1319394 reported by
Anne Gentle
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
openstack-manuals |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
In each book file, best to describe the target audience -- possibly study the personas and match up with those.
Changed in openstack-manuals: | |
milestone: | none → juno |
Changed in openstack-manuals: | |
milestone: | juno → kilo |
importance: | Medium → Wishlist |
tags: | removed: install-guide |
Changed in openstack-manuals: | |
milestone: | kilo → liberty |
Changed in openstack-manuals: | |
milestone: | liberty → mitaka |
assignee: | nobody → Brian Moss (bmoss) |
Changed in openstack-manuals: | |
assignee: | Brian Moss (bmoss) → nobody |
Changed in openstack-manuals: | |
milestone: | mitaka → none |
Changed in openstack-manuals: | |
importance: | Wishlist → Undecided |
To post a comment you must log in.
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.