14:31:47 #startmeeting Documentation Working Group aka DaWGs 14:31:47 Meeting started Tue Aug 13 14:31:47 2019 UTC. 14:31:47 This meeting is logged and archived in a public location. 14:31:47 The chair is acozine. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:31:47 Useful Commands: #action #agreed #halp #info #idea #link #topic. 14:31:47 The meeting name has been set to 'documentation_working_group_aka_dawgs' 14:31:51 who's around? 14:32:13 me 14:32:21 #chair tributarian 14:32:21 Current chairs: acozine tributarian 14:32:22 just a little 14:32:26 thanks for the agenda item 14:32:38 #chair felixfontein 14:32:38 Current chairs: acozine felixfontein tributarian 14:33:01 gundalow: you joining in today? 14:33:48 alongchamps: andersson007_ belfast77 cyberpear dag dfed jmnk_ you folks actively here? 14:34:13 I am! 14:34:15 madonius: mrproper orthanc Pilou shaps theo-o Xaroth8 zoredache how about you folks? 14:34:20 #chair alongchamps 14:34:20 Current chairs: acozine alongchamps felixfontein tributarian 14:34:28 welcome everybody! 14:34:50 o/ 14:34:58 #topic PR 60492 14:35:32 submitted by tributarian - it addresses one of our more ancient docs issues: https://github.com/ansible/ansible/issues/12533 14:35:40 PR link: https://github.com/ansible/ansible/pull/60492 14:35:51 first off, thanks tributarian for picking up the issue! 14:36:03 You are welcome 14:38:09 I confess that in my sysadmin career with Ansible, I didn't make much use of tags, so this isn't as familiar to me 14:39:15 i normally use tags on my 'diagnossis playbooks' .. my config ones are discrete enough that i dont need to use tags 14:39:34 I use them all time 14:39:53 I tend to use them on the main playbook that assigns various roles. 14:40:07 excellent! 14:40:12 I always saw tags as a dangerous introduction of dependency trees, however I use them heavily developing lockdown 14:40:23 The current functionality of --list-tags isn't really useful vs --list-tasks which also displays tags. 14:40:24 especially ffor testing 14:40:28 I also use them all the time, though I've never used --skip-tags or --list-tasks 14:40:35 dangerous and useful are often closely related 14:40:41 #chair dfed 14:40:41 Current chairs: acozine alongchamps dfed felixfontein tributarian 14:40:51 if a feature isn't dangerous, it isn't powerful enough ;) 14:40:52 morrning 14:41:02 felixfontein: indeed 14:41:24 I'm sure I 14:41:33 've done some stupid things with them. 14:41:52 tributarian: I noticed you made your PR "related to" the issue, not "fixes" or "closes" - do you think there's work left to be done on the issue? 14:42:18 From what I could tell, the issue is a 'works as expected in the current devel' 14:42:35 But the documentation wasn't clear. 14:43:00 I think the issue can be closed. 14:43:06 awesome 14:43:25 I put testing output in the issue. That output is what really closes it. 14:43:41 the notes on the issue are clear and complete, so anyone who finds that issue should understand the current state of the code 14:43:49 and the docs updates look good to me 14:44:39 I'm +1 to merging the PR and closing the issue 14:44:50 other votes? 14:45:49 I'm +1, more clarity for something that's particular like this is a good thing 14:46:03 I'm +1 on merging, +0 on closing (since I haven't really looked at it :) ) 14:46:26 merge, close and let's all have a beer. 14:46:38 dfed++ 14:46:41 it's a bit early for the beer, but . . . I'll take a rain check 14:46:56 I mean it's perfectly normal time to have a beer in Australia. 14:46:58 its 5pm somewhere (benefit of international and remote workforce) 14:47:08 it's almost lunchtime for me, so close enough 14:47:12 bam 14:47:14 There is a country song about it being 5 o'clock somewhere 14:47:16 GitHub is having one of its "are you sure?" days 14:47:25 I'm trying to merge, but it keeps bouncing back 14:47:35 there we go 14:47:54 ^ its new 'clippy' functin in azure cloud (where github is hosted) 14:48:20 yay! 14:48:28 Thank you. 14:48:47 #topic open floor 14:49:02 felixfontein: shall we look at your latest magnum opus as a group? 14:49:25 tributarian: you're welcome, and thank you! 14:50:03 oh, FYI, the automated docs build is temporarily down on Jenkins, so updates to `devel` will be delayed 14:50:41 also, tributarian if you want that change to show up in the `latest` docs (as soon as the Jenkins job is fixed), feel free to open a backport 14:51:13 acozine: is there a doc on that? 14:51:21 haven't opened a backport before 14:51:38 tributarian: https://docs.ansible.com/ansible/devel/community/development_process.html#backport-process 14:51:45 thanks 14:52:19 #topic module renames for Ansible 2.9 14:53:28 we're changing the `cloud_utility_facts` modules to `cloud_utility_info` modules, since the information they return is not, strictly speaking, `ansible_facts` 14:53:48 this means there are a lot of renamed modules in 2.9 14:54:06 which leads us to https://github.com/ansible/ansible/pull/60483 14:55:50 felixfontein: you alphabetized the list, that's awesome 14:55:50 acozine: why not :) 14:56:07 yeah, I thought it would be a lot better readable this way 14:56:12 it is, it is 14:56:53 the diff looks a bit strange partly because of that; I didn't add/remove text, I just moved the list items around and sorted them 14:57:22 the list items were previously a part of `Noteworthy module changes`, now they are all part of `Renamed modules` 14:58:07 yeah, it took me a full read-through to figure out what you were doing 14:58:23 it looks much better now, but the diff makes it look like more changes than it really is 14:58:36 +1 to merging 15:00:02 I'm also +1, unsurprisingly ;) 15:00:55 heh, glad you're not disavowing your own PR 15:02:28 quiet all of a sudden . . . 15:03:19 (this is why it's helpful to have the discrete manipulations in separate commits) 15:03:34 hah! ansibot has added `has_issue` because of the mention on the DaWGs agenda 15:03:41 cyberpear: true 15:04:27 cyberpear: yes, though in this case I think the "just get it over with" approach works fine 15:04:38 #chair cyberpear 15:04:38 Current chairs: acozine alongchamps cyberpear dfed felixfontein tributarian 15:04:49 indeed 15:05:25 hearing no objections, I'm merging 60483 15:05:40 w00t, merged on the first try 15:05:48 GitHub is feeling better, I guess 15:05:58 thanks felixfontein 15:06:11 #topic open floor 15:06:17 ah, so it's not just me who sometimes has to try to merge something x times before it works... 15:06:27 thanks for reviewing and merging! 15:07:06 yw, glad to get the porting guide in better shape well ahead of the release 15:07:15 oh, speaking of which . . . 15:07:53 Dev Freeze for 2.9 release is August 29 15:08:08 we can make docs-only changes after that, but not code changes 15:08:28 * cyberpear glad to see a shorter release cycle 15:08:48 for anyone here with code PRs in mind (or in flight), keep the deadline front and center! 15:09:05 still a lot of PRs I need to create and get merged before of that :) 15:09:30 felixfontein: yep, it's crunch time 15:09:35 2 weeks and 2 days 15:11:06 oh, I have another item to discuss 15:11:12 forgot to put it on the agenda 15:11:18 #topic changes to tables 15:12:02 We've started updating the way we do tables in the documentation 15:12:25 abadger1999 started with https://github.com/ansible/ansible/pull/60148 15:12:55 trying to get away from all the `-------+-------` stuff 15:13:11 two current open PRs in the same realm of work: 15:13:43 https://github.com/ansible/ansible/pull/60177 15:13:50 and, slightly more specialized 15:14:09 https://github.com/ansible/ansible/pull/60171 15:15:21 ultimately it would be great to have a page in the Style Guide that talks about how to create and edit tables in our docs 15:15:26 hmm that's interesting 15:15:56 Style Guide main page: https://docs.ansible.com/ansible/devel/dev_guide/style_guide/index.html 15:16:20 having plain-text docs being more useful w/o processing is always a plus in my book, so these look like good changes 15:17:12 thanks cyberpear 15:17:25 I will not miss editing the dashes and lines 15:19:08 #topic open floor (again) 15:19:27 we've got ten minutes left 15:19:45 anybody have an issue or PR to highlight? concern to address? question to ask? 15:20:38 there are currently 80 open docs PRs, which means we're back on 4 pages on GitHub 15:20:49 I try to keep it under 75 / 3 pages 15:21:25 all PR reviews, pointers, comments, etc. welcome! 15:23:12 samccann will be back next week 15:23:50 all right, thanks everybody for talking docs today 15:24:13 concerns, questions, comments, etc. welcome in the chat any time 15:24:43 agenda items for next week encouraged - add them by adding a comment to https://github.com/ansible/community/issues/389 15:24:58 thanks again 15:25:02 #endmeeting