| 2016-07-09 12:56:27 |
Ian Y. Choi |
bug |
|
|
added bug |
| 2016-07-09 12:59:11 |
Ian Y. Choi |
description |
The following images files are designed for illustrating Training guides
: image00~image49 (extension: png or jpg)
: openstack-arch-havana-logical-v1.jpg
: openstack-training-example-image.png
: openstack-training-remote-content-not-available.png
(Note that some of them were for icehouse, which is too old.)
The problem is that it is so difficult to manage images with Training guides contents.
I would like to re-organize the structure of image names like
"[training-guide type]-[section number]-[incremental number]-[description].[image file extension]".
For example, "associate-01-01-heartbeats.png" means
"the first image in Associate guide section 01, explaining heartbeats, and image type is png". |
The images files for Training guides are in
: http://git.openstack.org/cgit/openstack/training-guides/tree/doc/training-guides/figures .
(Note that some of them were for icehouse, which is too old.)
The problem is that it is so difficult to manage image file names with Training guides contents. Also, just simple file names such as image00~image49 cannot explain any contextual details.
I would like to re-organize the structure of image names like
"[training-guide type]-[section number]-[incremental number]-[description].[image file extension]".
For example, "associate-01-01-heartbeats.png" means
"the first image in Associate guide section 01, explaining heartbeats, and image type is png". |
|
| 2016-07-09 12:59:17 |
Ian Y. Choi |
openstack-training-guides: assignee |
|
Ian Y. Choi (ianychoi) |
|
| 2016-08-10 14:18:11 |
Ian Y. Choi |
openstack-training-guides: status |
New |
Confirmed |
|
| 2016-08-10 14:26:50 |
OpenStack Infra |
openstack-training-guides: status |
Confirmed |
In Progress |
|
| 2016-08-29 23:23:13 |
Ian Y. Choi |
description |
The images files for Training guides are in
: http://git.openstack.org/cgit/openstack/training-guides/tree/doc/training-guides/figures .
(Note that some of them were for icehouse, which is too old.)
The problem is that it is so difficult to manage image file names with Training guides contents. Also, just simple file names such as image00~image49 cannot explain any contextual details.
I would like to re-organize the structure of image names like
"[training-guide type]-[section number]-[incremental number]-[description].[image file extension]".
For example, "associate-01-01-heartbeats.png" means
"the first image in Associate guide section 01, explaining heartbeats, and image type is png". |
The images files for Training guides are in
: http://git.openstack.org/cgit/openstack/training-guides/tree/doc/training-guides/figures .
(Note that some of them were for icehouse, which is too old.)
The problem is that it is so difficult to manage image file names with Training guides contents. Also, just simple file names such as image00~image49 cannot explain any contextual details.
The proposed image file name convention is: "[A]-[B]-[C](-[D]).[E]" where
- A: training guide type (e.g., "associate")
- B: section number
- C: image number incremented in each section
- D: description of the image (optional)
- E: image file extension (e.g., "jpg", "png")
For example, "associate-01-01-heartbeats.png" means
"the first image in Associate guide section 01, explaining heartbeats, and image type is png". |
|
| 2016-09-05 13:28:36 |
Ian Y. Choi |
summary |
[Training guides] Re-organization of image name structure |
[Training guides] better descriptions on image file names |
|
| 2016-09-05 13:30:29 |
Ian Y. Choi |
description |
The images files for Training guides are in
: http://git.openstack.org/cgit/openstack/training-guides/tree/doc/training-guides/figures .
(Note that some of them were for icehouse, which is too old.)
The problem is that it is so difficult to manage image file names with Training guides contents. Also, just simple file names such as image00~image49 cannot explain any contextual details.
The proposed image file name convention is: "[A]-[B]-[C](-[D]).[E]" where
- A: training guide type (e.g., "associate")
- B: section number
- C: image number incremented in each section
- D: description of the image (optional)
- E: image file extension (e.g., "jpg", "png")
For example, "associate-01-01-heartbeats.png" means
"the first image in Associate guide section 01, explaining heartbeats, and image type is png". |
The images files for Training guides are in
: http://git.openstack.org/cgit/openstack/training-guides/tree/doc/training-guides/figures .
(Note that some of them were for icehouse, which is too old.)
The problem is that it is so difficult to understand what it describes from image file names with Training guides contents.
For example, let's use "horizon-actions.png" instead of "image30.png" for an image file which describes 'Actions' in Horizon. |
|
