Monday, 2019-09-02

*** brinzhang has joined #openstack-doc00:35
*** jamesmcarthur has joined #openstack-doc03:48
*** jamesmcarthur has quit IRC04:06
*** jamesmcarthur has joined #openstack-doc04:09
*** jamesmcarthur has quit IRC04:14
*** jamesmcarthur has joined #openstack-doc04:23
*** jamesmcarthur has quit IRC04:56
*** jamesmcarthur has joined #openstack-doc05:25
*** jamesmcarthur has quit IRC05:33
*** miloa has joined #openstack-doc05:50
*** jamesmcarthur has joined #openstack-doc06:29
*** jamesmcarthur has quit IRC06:34
*** brinzhang has quit IRC06:40
*** brinzhang has joined #openstack-doc06:40
*** kopecmartin has joined #openstack-doc06:53
*** tesseract has joined #openstack-doc06:56
*** rcernin has quit IRC07:08
*** rcernin has joined #openstack-doc07:24
*** jamesmcarthur has joined #openstack-doc07:30
*** tosky_ has joined #openstack-doc07:34
*** jamesmcarthur has quit IRC07:35
*** rcernin has quit IRC07:48
*** pcaruana has joined #openstack-doc07:49
*** alexmcleod has joined #openstack-doc08:27
*** jamesmcarthur has joined #openstack-doc08:31
*** tosky_ is now known as tosky08:32
*** jamesmcarthur has quit IRC08:36
*** jamesmcarthur has joined #openstack-doc09:33
*** jamesmcarthur has quit IRC09:44
asettletosky, that's an odd one (cant can't)10:08
asettleAJaeger_, amotoki - apologies for being entirely out last week. During training I was very sick and came home and did not return to work until today.10:08
asettleI need to catch up on everything.10:08
*** jamesmcarthur has joined #openstack-doc10:29
*** jamesmcarthur has quit IRC10:34
stephenfinasettle: weak.10:43
asettlestephenfin, ain't I just10:47
*** brinzhang_ has joined #openstack-doc10:50
*** brinzhang has quit IRC10:53
toskyasettle: should I add them to the etherpad, even though I don't have neither a workaround nor a solution?10:58
asettletosky, yes I think that's suitable. Something weird is happening there11:04
amotokiasettle: no worries. I hope you've recovered.11:11
asettleMuch better, thank you amotoki :) I have meetings now but I will soon read scrollback and go through your requests11:11
asettleThank you for sending the update email11:11
asettleI will also include a patch to update the goal11:12
amotokiasettle: I have some questions to you. I will drop them later.11:12
asettleamotoki, please do11:12
asettleI will be busy today but I will do my best :)11:12
asettleCatching up, you know how it is :P11:12
*** jamesmcarthur has joined #openstack-doc11:14
*** jamesmcarthur has quit IRC11:24
*** jamesmcarthur has joined #openstack-doc11:25
*** jamesmcarthur has quit IRC11:35
*** jamesmcarthur has joined #openstack-doc12:09
*** jamesmcarthur has quit IRC12:13
*** brinzhang has joined #openstack-doc12:25
*** brinzhang_ has quit IRC12:28
*** jamesmcarthur has joined #openstack-doc12:45
amotokiasettle: when I read "Completion Criteria" in the goal definition and have some questions.13:00
amotokiregarding 1. you said the criteria is to succeed to build a PDF doc but it says "Each team needs to ensure ... that the PDFs look respectable". which is the criteria?13:00
amotokiregarding 4, I am not sure how we can do it. Do you have any idea on this?13:00
asettleLet me review amotoki :)13:01
asettle1. Do you mean, how to define "respectable"?13:02
asettle4. My idea was to have a stamp. So when the guide is generated, the template has a faded background that provides the release name. What do you think?13:04
asettleOr even if the PDF is generated and a notice is included in the build.13:04
toskyif I may, in the meantime... in some cases we need to set a few values in latex_elements; but don't we lose the options set by default then? (like, for example, the A4 paper size and the font size)?13:11
amotokiasettle: 1. yes, from my experience on neutron, even after we can build PDF doc, we need some improvements to make PDF docs ready for use. for example, in case of neutron, we need to adjust TOC levels and toctree so that readers can jump to a section they want easily.13:23
amotokiI am not sure what we expect to individual project teams.13:23
asettleamotoki, that's a good point. I think the hard thing is that it's subjective to the project. Whihc is why it was quite a vague statement at the beginning13:24
asettleLike, make it respectable as far as you see fit. Ensure it is readable13:24
amotoki:-)13:24
amotokiA document with hundred of pages without appropriate TOC is hard to read :p13:25
asettleExactly. So, that is how you've defined it as "respectable". Perhaps I can define that as "respectable and readable to a human user audience"?13:26
amotokiasettle: regarding 4., it would be nice. Can we get a branch name when generating the PDF guide?13:26
asettleWould that be helpful? I can also include that this may differ per project team13:26
asettleamotoki, hmmm I would think so. I think it is something we have done before, but I'd have to ask AJaeger_13:26
amotokiasettle: (on 1.) yes, it would be helpful.13:27
asettleamotoki, okay will do. So I have a few updates to do :) I will let you know when I push it up.13:27
amotokiasettle: thanks!13:28
asettleamotoki, okay, I have rephrased to:13:44
asettle"The doc gate job should run and produce PDFs for all projects, it may also13:44
asettle   depend on in-repository declarations of new dependencies or a new tox env.13:44
asettle   The intention is to keep these changes at a minimum. "13:44
asettleAny suggestions?13:44
*** jamesmcarthur has quit IRC13:49
amotokiasettle: generally looks good. one question: what do you mean by "in-repository declarations of new dependencies"?13:49
asettleamotoki, that was the language already included.13:50
amotokiasettle: Ah, I see13:50
asettleI can adjust if it is unclear.13:51
asettleBut I did not change it.13:51
amotokiasettle: The current version was written before investigating the detail, so I think it covers possible changes. We can update it to something like "Each team needs to define a new tox env to enable the PDF build". it is an idea from me.13:54
asettleamotoki, I think that sounds reasonable.13:55
asettleamotoki, https://review.opendev.org/67965413:56
asettleAlso stephenfin andymccr ^13:57
asettle... sorry13:57
asettleAJaeger_, ^13:57
*** KeithMnemonic has joined #openstack-doc14:03
*** kopecmartin is now known as kopecmartin|off14:54
*** jamesmcarthur has joined #openstack-doc15:25
*** jamesmcarthur has quit IRC15:31
*** jamesmcarthur has joined #openstack-doc16:02
*** jamesmcarthur has quit IRC16:06
*** alexmcleod has quit IRC16:19
*** jamesmcarthur has joined #openstack-doc16:49
*** miloa has quit IRC17:07
*** miloa has joined #openstack-doc17:07
*** jamesmcarthur has quit IRC17:20
*** KeithMnemonic1 has joined #openstack-doc17:27
*** KeithMnemonic1 has quit IRC17:27
*** jamesmcarthur has joined #openstack-doc17:29
*** tesseract has quit IRC17:30
*** KeithMnemonic has quit IRC17:31
*** jamesmcarthur has quit IRC17:57
*** miloa has quit IRC18:12
*** pcaruana has quit IRC18:19
*** pcaruana has joined #openstack-doc18:19
AJaeger_amotoki: branch name? What do you have in mind? We publish to branch/<project>.pdf - to display branch name in the PDF itself, you can use the zuul.branch variable for example. stephenfin should be able to help with that18:52
*** pcaruana has quit IRC20:36
openstackgerritBrian Rosmaita proposed openstack/openstack-manuals master: Update the VM Image Guide  https://review.opendev.org/67885621:09
*** jamesmcarthur has joined #openstack-doc21:24
*** jamesmcarthur has quit IRC22:02
*** tosky_ has joined #openstack-doc22:04
*** tosky has quit IRC22:06
*** tosky_ is now known as tosky22:09
*** jamesmcarthur has joined #openstack-doc22:31
*** rcernin has joined #openstack-doc22:54
*** jamesmcarthur has quit IRC22:59
*** jamesmcarthur has joined #openstack-doc23:03
*** jamesmcarthur has quit IRC23:05
*** jamesmcarthur has joined #openstack-doc23:05
*** jamesmcarthur has quit IRC23:23
*** jamesmcarthur has joined #openstack-doc23:27
*** jamesmcarthur has quit IRC23:32
*** jamesmcarthur has joined #openstack-doc23:56

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!