16:00:32 #startmeeting docteam 16:00:33 Meeting started Wed Jan 10 16:00:32 2018 UTC and is due to finish in 60 minutes. The chair is pkovar. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:35 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:00:37 The meeting name has been set to 'docteam' 16:00:49 #topic roll call 16:01:02 who's around for today's meeting? :) 16:01:23 o/ 16:01:42 o/ 16:02:31 welcome :) 16:04:04 since ianychoi is around, let's begin with... 16:04:06 #topic PDF builds 16:04:15 #link https://review.openstack.org/#/c/509297/ 16:04:26 this is an older review, possibly stalled 16:05:14 ianychoi: do you know if there's an update/request for comments/help needed wrt that spec proposal? 16:08:51 okay, let's do a couple of announcements since we don't have that many people around today :) 16:08:59 #topic Docs retention policy changes 16:09:07 #link http://specs.openstack.org/openstack/docs-specs/specs/queens/retention-policy.html 16:09:49 Oh sorry - I just sent an e-mail for different task. Let's talk about PDF things after discussing other topics first. 16:10:09 okay, no worries 16:10:11 #info we have a pending review for adding deprecation badges 16:10:23 #link https://review.openstack.org/#/c/530142/ 16:10:56 which is a good start in a long process involving updating openstackdocstheme as well, as pointed out by dhellmann 16:11:19 if you have feedback for this initial change, please add comments :) 16:12:09 next announcement 16:12:12 #topic Rocky PTG 16:12:29 #link https://www.openstack.org/ptg/ 16:12:38 #info Planning etherpad for docs+i18n created 16:12:53 #link https://etherpad.openstack.org/p/docs-i18n-ptg-rocky 16:13:02 #info Sign up and tell us your preference wrt parcel time into small chunks or have full-day focus on one team agenda? 16:13:20 # info add your own topics to the list of what we want to cover at the ptg 16:13:35 for both docs & i18n 16:14:00 questions, comments so far? :) 16:14:50 #topic Bug Triage Team 16:15:05 Cool :) 16:15:09 #info you can still sign up 16:15:11 #link https://wiki.openstack.org/wiki/Documentation/SpecialityTeams 16:15:52 this is for bug triage for openstack-manuals 16:16:08 since project teams have their own bug triage processes 16:16:19 and that includes docs related bugs 16:16:26 #topic PDF builds 16:16:32 back to the topic :) 16:17:12 Thank u :) 16:17:14 #link http://lists.openstack.org/pipermail/openstack-dev/2017-November/124863.html 16:17:51 Doug asked whether PDF builds target all (always build) or not 16:18:04 And I posted several perspectives. 16:18:23 pkovar, Do u have some preferences on such perspectives? 16:18:43 Or which documents should be targeted for PDF builds? 16:20:10 ianychoi: i'm not sure we have enough date now to understand if there is a strong user requirement for pdf builds for project team docs, for example 16:20:39 but i take it as translators are one of the interest groups? 16:21:27 as for openstack-manuals docs, if we already build pdfs for some, i see no reason why not enable it for others 16:21:52 As far as I know, China has interests on PDF builds because of some rather slow Internet environment 16:22:35 sounds like a big customer then :) 16:22:39 For interests in translators, translated PDF build generation needs to be implemented but IMHO project doc translation support needs to be implemented first. 16:23:00 That topic would be on the top in Rocky PTG for I18n team. 16:23:06 Haha.. yes :) 16:23:07 right, good point, so that would be a separate topic rather 16:23:13 great 16:23:14 can't comment on the potential slowness of the build process, is that a big concern? 16:24:07 Not a big concern if infra team thinks that such slowness is acceptable 16:27:13 * stephenfin arrives really late 16:27:25 one more question about project team pdfs, are we going to build a single pdf file per project? 16:27:59 for larger project docs, having one big pdf might affect its usability 16:28:04 Per 16:28:13 Aha.. per document 16:28:56 okay 16:28:58 Yep.. each project team has just one conf.py in doc/source 16:29:06 right 16:29:54 well, in any case that's a usability question, not a technical blocker 16:30:40 For example, https://docs.openstack.org/ha-guide/HAGuide.pdf#30 => #30 indicates page 30 16:31:05 that works pretty well 16:31:08 cool 16:31:31 I will more find options using "#" things.. maybe several section name would be supported but I am not sure now. 16:31:51 Unfortunately I have so less possibility to go to Rocky PTG, but would u help later on updating PTI document to include PDF things? PDF builds were not included in https://review.openstack.org/#/c/508694/ and I think that is needed before removing WIP in https://review.openstack.org/#/c/509297/ 16:33:10 ianychoi: i will do my best to help, yes :) 16:33:36 okay, so let's keep the -1 on /509297/ for now 16:34:18 Thank u yep :) 16:34:44 ianychoi: what would be the next step here then? 16:35:38 pkovar, I think writing an update as a patch on governance repository would be a good idea. 16:36:08 since PTI applies to all OpenStack projects 16:36:37 And finally, is there a plan to update openstackdocstheme version? I think newer version will enable not to write release information for PDFs if not configured in conf.py 16:38:09 ianychoi: can you initiate the pti change? i am afraid i don't know many details to move that forward on my own 16:40:54 pkovar, yep but plz give some time to me and I will try to do that before PTG for Docs team to discuss this topics with other PTI experts who would be in PTG (e.g., Doug, Monty) 16:41:18 sounds good! 16:41:53 ianychoi: let's postpone this until the week before ptg 16:42:12 Thank u :) 16:42:32 #info updating PTI will be needed in order to unblock the pdf spec 16:43:08 #info let's discuss again before the rocky ptg and then try to work together on the update at the ptg 16:43:35 stephenfin: you around? we got a q about openstackdocstheme :) 16:43:48 Shoot 16:43:56 (05:36:37 PM) ianychoi: And finally, is there a plan to update openstackdocstheme version? I think newer version will enable not to write release information for PDFs if not configured in conf.py 16:44:21 * stephenfin goes to find the commit in question 16:44:38 pkovar: You're looking for 9219e0b38838bb8c788849b792180e4502e2b3a6 16:44:45 (Change ID I0401e913658eff75a53e39c564e7f5ea88bd6b35) 16:44:55 https://github.com/openstack/openstackdocstheme/commit/9219e0b38838bb8c788849b792180e4502e2b3a6 16:45:09 I simply saw github: https://github.com/openstack/openstackdocstheme/tree/1.17.0 and the latest commit was about 3 months ago 16:45:29 But PDF release functionality was implemented about 2 months ago as far as I know 16:45:49 ianychoi: In that case, I guess we best release it 16:45:50 ianychoi: https://review.openstack.org/#/c/531768/ 16:45:53 but there is one blocker 16:46:04 that certain patch for source path detection? :) 16:46:14 The very same :) 16:46:28 Oh 1.18.0 patch is on-going :) Good! 16:47:03 My approach is not so cool but fast just from my simple trial :) 16:48:14 So yeah, we can definitely release that once the source path detection thing is resolved 16:48:23 Guess we'll leave that to dhellmann 16:48:28 stephenfin: what is the blocking patch chage id again? 16:48:49 https://review.openstack.org/#/c/532163/ 16:48:57 and the preceding patch 16:49:06 #info openstackdocstheme 1.18.0 on the way but blocked by https://review.openstack.org/#/c/532163/ 16:49:16 thanks, stephenfin 16:49:29 Thanks stephenfin ! 16:49:46 np 16:50:41 and many more pending changes in https://review.openstack.org/#/q/topic:bug/1732630+(status:open+OR+status:merged) 16:51:24 also, thanks goes to tosky :) 16:51:42 and thank you, ianychoi 16:51:53 pkovar, thank u! 16:52:00 we should have like a kudos meeting item for this meeting 16:52:06 :) 16:52:17 :) 16:53:38 #topic Open discussion 16:53:48 any other comments, concerns? 16:54:03 * tosky didn't do anything O.o 16:54:35 tosky: i see your comments everywhere :) 16:54:44 ah, the -1 16:55:15 yeah, sometimes a -1 is more important than anything, tosky 16:58:42 alright, thanks again for joining the meeting today 16:58:55 #endmeeting