16:00:43 <pkovar> #startmeeting docteam
16:00:44 <openstack> Meeting started Wed Nov  1 16:00:43 2017 UTC and is due to finish in 60 minutes.  The chair is pkovar. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:00:45 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:00:47 <openstack> The meeting name has been set to 'docteam'
16:01:20 <pkovar> hey team, who's around?
16:01:20 <eumel8> o/
16:01:26 <chason> o/
16:01:40 <pkovar> \o
16:02:05 <pkovar> let's give it 4.5 mins before we start
16:05:18 <ianychoi> Oh here is the meeting channel. Hi all
16:05:37 <AJaeger> o/
16:05:41 <pkovar> ianychoi: hey
16:05:50 <ianychoi> pkovar, hello :)
16:06:12 <pkovar> alright, first topic is
16:06:19 <pkovar> #topic Docs team vision document
16:06:26 <pkovar> #info At final review
16:06:31 <pkovar> #link https://review.openstack.org/#/c/514779/
16:06:37 <pkovar> #info Sent a reminder asking for more input
16:06:42 <pkovar> to Mls
16:06:47 <pkovar> #info Let's close by Thu, before the Summit
16:06:53 <pkovar> unless there are objections?
16:07:15 <pkovar> thanks for voting and reviews, everybody
16:07:30 <pkovar> by close i mean merge
16:07:58 <ianychoi> Good good :)
16:08:26 <pkovar> we've got 5 +2's so that's not that bad
16:08:35 <AJaeger> that's a lot ;)
16:08:45 <pkovar> actually, you're right, it is AJaeger
16:09:33 <pkovar> any other comments on this? let the team know :)
16:10:12 <pkovar> next topic
16:10:16 <pkovar> #topic Docs retention policy changes
16:10:27 <pkovar> #info We've just approved this spec. Thanks Doug for putting this together!
16:10:31 <pkovar> #link https://review.openstack.org/#/c/507629
16:10:33 <pkovar> #link https://review.openstack.org/#/c/507629
16:10:38 <pkovar> well, not just...
16:10:49 <pkovar> related to this is
16:10:52 <pkovar> #info Flagging deprecated releases
16:10:57 <pkovar> #link http://lists.openstack.org/pipermail/openstack-dev/2017-October/123381.html
16:11:24 <pkovar> people are preparing for summit so the progress has been slower
16:11:35 <pkovar> than right after the ptg
16:12:16 <pkovar> but we've got volunteers who expressed interest in helping out with badges
16:12:31 <pkovar> so i think we are on track with this
16:13:12 <pkovar> next topic?
16:13:28 <pkovar> #topic Branches vs "everything in master"
16:13:41 <pkovar> this came up yesterday in this channel
16:13:50 <pkovar> #info Common Install Guide content should be branched/split up per-release?
16:14:09 <pkovar> though it's not just about the install guide, for sure
16:14:40 <ianychoi> (Sorry - I need to go out. I will see and follow the meeting minute.)
16:14:46 <pkovar> we kinda made a decision to document multiple releases in a single install guide doc for pike
16:15:46 <pkovar> if we branched or split up the install guide doc, it would allow for a better content flow and structure, i think
16:16:16 <pkovar> chason proposed creating a branch
16:16:20 <pkovar> #link https://review.openstack.org/#/c/516523/
16:16:37 <pkovar> ianychoi: nw, see you later
16:17:02 <pkovar> what are everybody's thoughts on pros and cons re branching?
16:17:06 <chason> Yes, I agree with asettle, just like it all clean and separated. :)
16:17:45 <pkovar> chason: are there other documents that would benefit from branching? or just the install guide common content?
16:18:01 <AJaeger> we always have the challenge with multiple versions. A new distro release might come out at any time - and then our newest release documents a previous one. So, if we branch, let's make clear what we document where.
16:18:39 <AJaeger> One option: Document the current version at OpenStack release time; no distro update in stable - only in master.
16:18:52 <AJaeger> But there are others as well...
16:20:13 <pkovar> AJaeger: so the current version would stay in master until the next version is released?
16:20:49 <AJaeger> pkovar: yes
16:20:50 <pkovar> no draft content?
16:21:03 <AJaeger> pkovar: we got rid of draft content - and draft was always master
16:21:04 <pkovar> or latest as in devel
16:21:12 <AJaeger> yes, we use latest = master
16:21:34 <pkovar> so latest would be stable, not "devel"?
16:21:53 <AJaeger> lastest is devel
16:22:14 <AJaeger> latest = devel = master = the next release - iff we branch
16:22:53 <pkovar> and current = branch = the current release - iff we branch?
16:23:10 <pkovar> current stable i mean
16:23:37 <AJaeger> iff we branch, then we follow the same method as the projects, so we would have stable/queens once/after they branch
16:24:37 <pkovar> right, i got confused by the location of where current stable content would live
16:26:17 <pkovar> i'll try to get more input from ppl attending summit next week
16:26:22 <AJaeger> sure
16:26:40 <pkovar> but if you have a preference for any of the possible options, please let us know :)
16:26:42 <chason> Agree
16:27:08 <pkovar> i can see that by following what other projects do, we would be more consistent
16:27:53 <pkovar> other comments?
16:28:43 <pkovar> okay, next is summit
16:28:44 <AJaeger> branching is always extra work, let's write down the options and figure out what is easier...
16:29:02 <pkovar> AJaeger: do we need a new spec for that?
16:29:19 <AJaeger> pkovar: yes, please
16:29:34 <pkovar> /me is updating the team's todo list
16:30:42 <pkovar> #topic OpenStack Summit Sydney
16:30:55 <pkovar> #info Quite a few docs-related sessions scheduled
16:31:03 <pkovar> #info Installation Guides and Tutorials Updates and Testing
16:31:09 <pkovar> #link https://www.openstack.org/summit/sydney-2017/summit-schedule/events/20448/installation-guides-and-tutorials-updates-and-testing
16:31:16 <pkovar> #info Docs - Project Update
16:31:21 <pkovar> #link https://www.openstack.org/summit/sydney-2017/summit-schedule/events/20373/docs-project-update
16:31:26 <pkovar> #info Docs/i18n - Project Onboarding
16:31:31 <pkovar> #link https://www.openstack.org/summit/sydney-2017/summit-schedule/events/20550/docsi18n-project-onboarding
16:31:35 <pkovar> #info Ops Guide Transition and Maintenance
16:31:40 <pkovar> #link https://www.openstack.org/summit/sydney-2017/summit-schedule/events/20446/ops-guide-transition-and-maintenance
16:31:45 <pkovar> #info Documentation and relnotes, what do you miss?
16:31:50 <pkovar> #link https://www.openstack.org/summit/sydney-2017/summit-schedule/events/20468/documentation-and-relnotes-what-do-you-miss
16:31:55 <pkovar> #info How Zanata powers upstream collaboration with OpenStack internationalization
16:31:59 <pkovar> #link https://www.openstack.org/summit/sydney-2017/summit-schedule/events/20007/how-zanata-powers-upstream-collaboration-with-openstack-internationalization
16:32:09 <pkovar> hope i didn't miss anything :)
16:32:21 <pkovar> who will be around?
16:32:45 <pkovar> if you are, you are most welcome to join the sessions
16:32:59 * AJaeger won't
16:33:01 <pkovar> esp, project onboarding
16:33:47 <pkovar> i'm hoping we could attract new people to work on core suite or project docs
16:34:56 <pkovar> get updates on what's the progress of install guide testing, if this is something we want to continue doing
16:35:07 <pkovar> talk about ops docs
16:35:21 <pkovar> provided they are people interested in maintaining the content
16:35:26 <pkovar> that used to live in ops guide
16:35:32 <pkovar> that we had to kill
16:35:52 <pkovar> etc.
16:37:18 <pkovar> is there anything the team wants to bring up as a topic with summit people?
16:39:01 <pkovar> okay, a couple of announcements from previous meeting brought forward
16:39:07 <pkovar> #topic sitemap automation suggestions
16:39:11 <pkovar> #link http://lists.openstack.org/pipermail/openstack-dev/2017-October/123228.html
16:39:29 <pkovar> feedback still welcome wrt potential scope, etc.
16:40:29 <pkovar> #topic Bug Triage Team
16:40:34 <pkovar> #link https://wiki.openstack.org/wiki/Documentation/SpecialityTeams
16:40:59 <pkovar> you can still sign up if you are into triaging fun
16:41:08 <pkovar> or just want to help out
16:41:33 <pkovar> big thanks to those who have been traiging last month
16:41:58 <pkovar> even if they didn't officially sign up :)
16:42:15 <pkovar> triaging, rather
16:42:29 <pkovar> #topic PDF builds
16:42:34 <pkovar> #link https://review.openstack.org/#/c/509297/
16:42:51 <chason> pkovar After the doc migration, we have little bug report.
16:42:51 <pkovar> ianychoi had to leave, so i guess we skip this one?
16:43:04 <pkovar> chason: good point
16:43:15 <pkovar> do we still need a bug triage team then?
16:44:02 <chason> Maybe not. ;(
16:45:05 <pkovar> #topic Open discussion
16:45:43 <pkovar> other thoughts, opinions, comments, concerns?
16:46:13 <chason> https://review.openstack.org/#/c/512136/
16:46:44 <chason> Can we try to merge this patch? :)
16:46:57 <pkovar> i think we can! :)
16:47:09 <pkovar> thanks for working on this, chason
16:47:17 <chason> yw
16:47:30 <pkovar> i will review
16:47:51 <chason> Thanks! :D
16:47:51 <pkovar> #info cores, if you are available, please review
16:47:59 <pkovar> #link https://review.openstack.org/#/c/512136/
16:48:41 <pkovar> any other issues with deploy guides?
16:49:39 <chason> guess no
16:49:51 <AJaeger> hope we finally solved them all ;)
16:49:55 <pkovar> thanks goes to all of you who have been fixing issues
16:50:10 <pkovar> thumbs up
16:50:23 <eumel8> https://docs.openstack.org/pike/deploy/ the OSA link is still not working for me
16:50:50 <pkovar> hmm, https://docs.openstack.org/project-deploy-guide/openstack-ansible/pike/ works for me
16:51:00 <chason> eumel8 But I am fine.
16:51:46 <eumel8> ah
16:51:53 <pkovar> cache issue?
16:51:55 <eumel8> firefox hard core caching
16:51:58 <AJaeger> eumel8: both work for me
16:52:04 <chason> eumel8 maybe you need to clean your web browser's cache or change your web browser.
16:52:12 <eumel8> it works with IE ;)
16:52:12 <pkovar> try incognito mode
16:52:43 <pkovar> IE ftw hehe
16:52:46 <eumel8> chason: I never clean the cache ;)
16:53:54 <chason> eumel8 Aha..I could say, me too.. :P
16:55:40 <pkovar> alright, i think we can end this mtg then
16:55:56 <pkovar> thank you for attending
16:55:59 <pkovar> #endmeeting