14:31:19 #startmeeting DaWGs aka Docs Working Group 14:31:19 Meeting started Tue Sep 17 14:31:19 2019 UTC. 14:31:19 This meeting is logged and archived in a public location. 14:31:19 The chair is acozine. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:31:19 Useful Commands: #action #agreed #halp #info #idea #link #topic. 14:31:19 The meeting name has been set to 'dawgs_aka_docs_working_group' 14:31:31 #chair gundalow samccann 14:31:31 Current chairs: acozine gundalow samccann 14:31:35 who else is around? 14:31:42 not me 14:31:57 tough luck coca, you get turned into furniture anyway 14:32:01 I C U!! 14:32:02 #chair bcoca 14:32:02 Current chairs: acozine bcoca gundalow samccann 14:33:01 nothing added to the agenda from the community issue 14:33:20 for future reference, anyone can add agenda items to https://github.com/ansible/community/issues/389 14:33:54 I'd like to call out andersson007_ for his heroic work on fixing typos in the module documentation 14:34:11 thank you andersson007_ for all the painstaking, careful work you put in 14:34:25 woot!! 14:34:42 acozine: thanks! I’m happy it has been done:) 14:34:47 no one thanks me for creating the typos for him to fix? 14:34:51 * bcoca hugs andersson007_ 14:35:03 bcoca: you cannot possibly have created all of them 14:35:15 bcoca: thank you! But it wasn’t a typo:) 14:35:32 acozine: im not alone! 14:36:02 heh, nope, everyone makes typos 14:36:08 he is legion! 14:36:15 many people follow up on the original typos by copying and pasting them into many files 14:36:27 given how many typos I generate in a day... we are legion! 14:36:29 I previously fixed mine:) 14:36:32 or maybe the typos themselves just breed, who knows? 14:37:09 Will do it next year again:) 14:37:34 awesome! 14:37:55 typos will always be with us, it's nice to know that typo hunters will too 14:38:31 I'd also like to announce that DaWGs has a logo now 14:38:44 we've had stickers made, and I'll be bringing them to AnsibleFest 14:39:12 if you're coming to Atlanta, find me and I'll make sure you get some 14:40:12 Thank you! 14:40:21 andersson007_: are you coming to Fest? 14:42:14 acozine: Unfortunately no, because it is a challenge to get the visa here. If officials reject my request it might be impossible to get it in the future 14:42:24 andersson007_: ugh, sorry about that 14:42:37 Np:) 14:42:58 Anyway I should improve my English before that :) 14:43:09 Maybe next time :) 14:43:13 I hope so! 14:43:39 meanwhile if you'd like some stickers, IM me and I'll mail them 14:44:36 last item I had for today's agenda is a call for comments on the WIP changes to the User Guide pages 14:45:36 it's not a PR yet, but the branch is here: https://github.com/acozine/ansible/tree/user_guide_overhaul 14:45:38 Ok, would be cool ! I’ll send my contacts to you later, thanks! 14:45:49 excellent! 14:46:29 current round of changes is on the `devel` version of the docs testing site at http://docs.testing.ansible.com/ansible/latest/user_guide/index.html 14:47:09 ah, wait, that's the `latest` version I linked 14:47:11 hang on 14:47:29 here we go: http://docs.testing.ansible.com/ansible/devel/user_guide/index.html 14:47:43 vs. current published at http://docs.ansible.com/ansible/devel/user_guide/index.html 14:47:51 acozine: This is good stuff. I like the high level flow. 14:48:16 tributarian: thanks 14:48:19 oh 14:48:26 #chair andersson007_ tributarian 14:48:26 Current chairs: acozine andersson007_ bcoca gundalow samccann tributarian 14:49:08 feel free to nominate pages for revision 14:49:11 big improvement acozine 14:49:27 I'm working on the "Working with patterns" page now and have some feedback to incorporate 14:49:37 hope to open a PR by Friday 14:50:13 biggest change is I turned the long list of examples into a table 14:51:02 next thing to fix is to tie it more closely to inventory, since the example patterns only work if the hosts/groups exist in inventory 14:52:56 oh, I never set a topic 14:53:01 This taxonomy should make contributing easier. 14:53:33 tributarian: that's great, what taxonomy do you mean? 14:55:10 speaking of contributing, I saw a PR yesterday that updates the inventory page - I need to look at it and see if I can incorporate it into my rewrite easily 14:56:14 ah, looks like bcoca and samccann have reviewed it 14:56:19 https://github.com/ansible/ansible/pull/62323/files 14:57:49 #topic open floor 14:58:10 what's on your minds, folks? 14:58:57 I got the logo up on our wiki - https://github.com/ansible/community/wiki/Docs 14:58:59 :-) 14:59:03 w00t! 14:59:32 acozine: I was mistaken on the taxonomy. The TOC hasn't changed as much as I thought. The changes are great though. 15:00:21 tributarian: yeah, the TOC seems pretty good, but the content needs cleaning up, and more "connective tissue" from one page to another would help 15:00:37 and some better titles 15:01:09 "Working with patterns" doesn't give the new reader any idea of why that content would be useful for her 15:01:16 which TOC are we talking now? user guide? 15:01:23 Yes 15:02:14 can you elaborate on what you were hoping for in an updated TOC? 15:02:32 I think we were agreeing that it's pretty good 15:02:43 acozine: The pattern changes are especially good. I find myself referring back to the pattern documentation often. 15:02:44 ah ok... my mistake 15:03:16 samccann: It is more that the TOC has been updated since the last time I saw it. (a long time ago) I mostly use search. 15:03:31 tributarian: most people do 15:04:21 speaking of search... we are experimenting with moving the lower-left search into the upper right search (they use two different search engines) 15:04:22 what would folks think of adding more levels to the User Guide TOC, so the top-level sections were `Working with inventory` and `Working with playbooks` and then the other pages were under those in the TOC? 15:04:59 I do find the current length of the user guide TOC a bit ...daunting 15:05:28 oh, right - tributarian when you say search, do you mean searching on Google/DuckDuckGo/other search platform? or do you use the docs.ansible.com site search? 15:06:08 ^^^ is a question for everyone 15:06:24 (not just tributarian) 15:06:36 I primarily use google search as I find it produces generally more relevant results. 15:06:59 If I'm already on a page, Ill sometimes use the top left search. 15:08:06 is your preference for top left just because of location? or because the engine produces better results? 15:08:16 Although, I just tried "Search this site" and the results are far better. Namely, it returns some of the page content and not just page titles. 15:08:33 It is definitely the more eye-catching search option on the page. 15:08:34 yes that's one of the reasons we want to switch to that search engine 15:08:42 I would agree with that move. 15:09:32 #info - investigating move the site search (lower left) to replace the search box in the upper right on docs.ansible.com 15:10:38 sorry to derail the user guide TOC discussion 15:11:05 samccann: the search discussion is an important one, glad you brought it up! 15:11:08 but for the user guide, I'd be in favor of simplifying the TOC if possible to some high-level sections etcc 15:12:50 I also wonder - could we move ad-hoc and cli commands into the getting started section? 15:13:28 that's a good idea 15:14:28 I would say keep the CLI commands section and move the ad-hoc commands under the ansible cli tool 15:14:40 And make the quickstart a child of getting started 15:15:21 hmm. The individual cli pages are autogenerated. 15:15:53 ah, i see that now 15:15:54 tributarian: where do you mean by "under the ansible cli tool" 15:16:11 though I see the connection between 'ansible' in the cli section, and the adhoc content etc 15:16:33 https://docs.ansible.com/ansible/devel/cli/ansible.html 15:17:49 Yeah that was the page I was thinking, but I understand that it is auto generated. 15:18:11 I think having the list of commands front and center is good. 15:19:18 it looks like most of the examples on https://docs.ansible.com/ansible/latest/user_guide/intro_adhoc.html are for `ansible` 15:19:30 was just about to type that :-) 15:20:04 we might be able to put ad-hoc below the ansible cli page... but would that disrupt the flow of the cli section? (aka is it worth it?) 15:20:44 we could add it at the end of the cli section as "examples of `ansible` commands" 15:22:11 or put it in the Getting Started section as samccann suggested - it makes a nice flow to say "here are some things you can do at the command line . . . if you do these tasks repeatedly, you want to turn them into playbooks" and then transition to the playbooks section 15:23:55 then at the end of the playbooks section introduce the idea that "now you want to be able to run that playbook on some servers and not on others . . . Ansible lets you control that with inventory" 15:24:53 okay just did a quick check of our docsite hits and the ad-hoc page gets about 5% of our total website hits (23rd most visited page) 15:25:12 huh, that's higher than I expected 15:25:26 yeah same here! So we should 'proceed with caution'. 15:25:44 well, we can move it around in the TOC without disrupting most of that traffic 15:25:52 yeah was thinking that. 15:25:53 as long as we keep the page name the same 15:26:28 my guess is that people use that page as a reference/reminder 15:27:50 we have three minutes left 15:28:18 any other topics/ideas/concerns/questions folks want to bring up? 15:29:34 thanks everyone for your support for Ansible docs! 15:30:06 thanks especially to samccann tributarian andersson007_ bcoca for participating in today's meeting 15:30:25 we'll post the minutes at https://github.com/ansible/community/issues/389 15:30:43 hope to see some folks in person in Atlanta for AnsibleFest 15:31:26 add agenda items for next week - PR review, issue triage, brainstorming, all items welcome! 15:31:40 #endmeeting