[openstack-dev] [docs] [training-guides] Team meeting reminder

[Pančur , Matjaž]

Hi all,

Just a reminder: Training guides team meeting is today (Tuesday) at 1300UTC, 
#openstack-meeting-3.

On the agenda [1] is moving from Hieroglyph for rendering slides [2].

-Matjaz

[1] https://etherpad.openstack.org/p/training-guides-meeting-agenda
[2] http://lists.openstack.org/pipermail/openstack-dev/2017-August/120598.html


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [docs] [training-guides] Moving from Hieroglyph for rendering slides

[Pančur , Matjaž]

Hi all,

Andreas filed a bug report [1] that can impact what will we use to render 
slides for Upstream University and other training related slide material in the 
future. We’ve already had many discussions at Training guides meetings about 
moving to some other more actively maintained/developed framework for slides.

We were leaning towards adopting a widely popular Reveal.js [2]. On the 
downside, that probably also means that we will have to convert slide material 
from RST to MD, as RST is not directly supported. With a shrinking 
(Docs guides) contributors, that could be a problem. 

Any other ideas or preferences?

Cheers,
Matjaz


[1] https://bugs.launchpad.net/openstack-training-guides/+bug/1708240
[2] https://github.com/hakimel/reveal.js/
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] Screenshots in reviews on Gerrit

[Pančur , Matjaž]

Repost from openstack-docs ML.
-Matjaz


Hi all,

I’ve been wondering if there is an already established or agreed on best 
practice for inclusion of screenshots in the review comment thread (like we 
have paste.openstack.org for text snippets and 
logs)? Sometimes I would like to include an annotated screenshot of the issue 
(eg. a slide that renders wrong only on a certain OS/browser combination).

People are usually pragmatic and just use their existing 
Dropbox/iCloud/GDrive/etc. cloud service and publish in the review a link to 
it, but this is not a permanent solution as links are usually 
ephemeral/short-lived. This causes some transparency/archival issues, so I 
would like to use a more permanent solution (like it is for logs/snippets in 
paste.openstack.org).

Any ideas on how should we deal with this?

Matjaz

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev