14:32:53 <acozine> #startmeeting Docs Working Group aka DaWGs
14:32:53 <zodbot> Meeting started Tue Nov  5 14:32:53 2019 UTC.
14:32:53 <zodbot> This meeting is logged and archived in a public location.
14:32:53 <zodbot> The chair is acozine. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:32:53 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
14:32:53 <zodbot> The meeting name has been set to 'docs_working_group_aka_dawgs'
14:33:00 <acozine> who's around?
14:33:53 <acozine> alongchamps: andersson007_ cyberpear dag felixfontein madonius Pilou Xaroth zoredache you folks ready to talk docs?
14:34:06 <alongchamps> I'm not around today
14:34:09 <acozine> gundalow: you around?
14:34:20 <acozine> we'll miss you alongchamps
14:34:41 <alongchamps> thanks!
14:35:17 <acozine> looks like our agenda today is All About Issues and PRs
14:36:41 <acozine> First, a quick update on 2.9
14:36:47 <acozine> #topic 2.9 release update
14:37:10 <acozine> Ansible 2.9 was released last Thursday (hooray!)
14:37:34 <acozine> the 2.9 docs are live on the site, and when you hit the `latest` URL, it should be the 2.9 docs
14:38:31 <felixfontein> I'm just lurking in the background, but I'm mostly busy with other stuff
14:38:33 <acozine> this means that Ansible 2.6 is now End Of Life - no changes will be made to the `stable-2.6` branch going forward
14:38:44 <felixfontein> RIP :)
14:38:52 <acozine> welcome felixfontein!
14:39:17 * tremble is also lurking, but busy with normal work-stuff
14:39:31 <acozine> so the versions available on the version-switcher now are `2.7`, `2.8`, `latest` (`2.9`) and `devel`
14:39:37 <acozine> hi tremble!
14:40:29 <acozine> docs for older versions are still available if you change the URL to the version you're looking for
14:41:30 <acozine> but whenever you find anyone using a version of Ansible older than `2.7`, please encourage them to upgrade
14:42:17 <acozine> if/when we find security issues, we only fix them in `devel` and the three versions available via the version-switcher
14:43:59 <acozine> #topic docs issues on github
14:44:01 <acozine> https://github.com/ansible/ansible/issues?q=is%3Aopen+is%3Aissue+label%3Adocs
14:44:49 <acozine> before Fest and the release, I was trying to keep the number of issues labeled `docs` down under 225 (9 pages on GitHub)
14:45:01 <acozine> it's gotten away from us a little bit ;-)
14:45:46 <acozine> here's one I created: https://github.com/ansible/ansible/issues/64296
14:46:47 <acozine> how does a developer know when to create a lookup plugin, when to create a `*_info` module, and when to create a `*_facts` module
14:47:06 <acozine> I could write the `facts vs. info` part easily enough
14:47:36 <acozine> does anyone have a good rule for the best use of lookup plugins?
14:48:52 <felixfontein> lookup plugins always run on the same machine where the playbook is executed. _facts/_info modules can run both on that machine or on remote machines
14:49:42 <felixfontein> i.e. modules can also operate on remote files, and connect to services only reachable from the remote machine
14:50:00 <acozine> ah, gotcha - so if the data the dev is looking for resides on a remote resource, it's got to be a module
14:50:09 <felixfontein> yes
14:50:14 <acozine> `info` for an API, `facts` for a macine
14:50:20 <acozine> s/macine/machine/g
14:50:59 <felixfontein> roughly, yes
14:52:02 <acozine> thanks felixfontein
14:52:45 <acozine> if anyone is looking for a first issue to tackle, anyone who is lurking on the channel and wants to contribute, feel free to do a draft for this issue
14:54:11 * samccann lurking
14:56:50 <acozine> here's an issue with a PR
14:56:53 <acozine> PR: https://github.com/ansible/ansible/pull/64041
14:57:05 <acozine> related issue: https://github.com/ansible/ansible/issues/64043
14:58:07 <acozine> the person is changing an example in the FAQ entry for `How do I access a variable name programmatically?`
14:59:00 <samccann> I think I got a thumbs up from the network team on that one but I’ll have to dig back and be sure
14:59:05 <acozine> the addition ensures that any IPv4 address that contains a dash `-` is transformed into an underscore `_`
14:59:52 <acozine> it looks correct to me
15:00:07 <acozine> anybody on this channel do network stuff regularly?
15:01:22 <acozine> sigh, the next one is Windows-related . . . any Windows users on the channel today?
15:01:23 <acozine> https://github.com/ansible/ansible/issues/63867
15:02:50 <acozine> ah, looks like we can close that one based on https://github.com/ansible/ansible/issues/63691#issuecomment-547176615
15:06:55 <acozine> Here's one about an error in `make webdocs`: https://github.com/ansible/ansible/issues/62902
15:07:43 <acozine> I haven't seen that error
15:08:07 <acozine> https://www.irccloud.com/pastebin/SlgMuzJD/make%20webdocs%20error%20reported%20in%20issue%2062902
15:09:07 <acozine> it looks like sphinx is complaining that a bunch of modules don't have any documentation at all
15:10:42 <acozine> hm, they're on `stable-2.8`
15:13:10 <acozine> I'm trying to reproduce this one now
15:19:14 <acozine> nope, the 2.8 build works fine for me
15:24:40 <acozine> I've updated the issue
15:24:45 <acozine> we've got about five minutes left
15:24:49 <acozine> #topic open floor
15:25:22 <acozine> open to questions, concerns, ideas, suggestions
15:25:47 <acozine> if you have an issue or PR you'd like to have highlighted, please post it!
15:27:22 <acozine> felixfontein: I wrote a paragraph about the `facts`-to-`info` changes in 2.9 here: https://docs.ansible.com/ansible/devel/porting_guides/porting_guide_2.9.html#renaming-from-facts-to-info
15:27:36 <acozine> comments/suggestions/clarifications welcome
15:27:53 <acozine> quiet day today
15:28:15 <acozine> oh, I have an announcement!
15:28:29 <acozine> the community team will be doing another Big PR Day next week
15:29:39 <acozine> next Thursday, I believe, in the ansible-community channel
15:29:58 <acozine> I'll post more details as I learn them
15:30:17 <acozine> one minute left . . .
15:30:22 <acozine> anyone for open floor?
15:31:06 <acozine> all right, thanks everybody!
15:32:14 <acozine> as always, agenda items welcome for next week's meeting . . . add a comment under https://github.com/ansible/community/issues/389#issuecomment-547483612
15:32:17 <gundalow> acozine: hi, was in another meeting
15:32:29 <acozine> hi gundalow, we're just wrapping up
15:32:38 <acozine> do you have details about the next Big PR Day?
15:33:09 <acozine> I heard it will happen next week
15:33:15 <felixfontein> acozine: thanks for that facts-to-info paragraph!
15:34:01 <acozine> felixfontein: you're welcome, we thought it would come in handy as a reference
15:34:04 <gundalow> acozine: erm, it could do
15:34:25 <acozine> gundalow: oh, has the date not been settled?
15:34:37 <acozine> sorry, I guess I got ahead of myself
15:34:53 <gundalow> acozine: Thursday 14th November
15:35:19 <acozine> Hooray!
15:35:41 <acozine> Big PR Day, next Thursday, November 14th, 2019 in the ansible-community channel
15:35:52 <acozine> hope to see a bunch of docs champions there!
15:36:03 <acozine> thanks again, folks
15:36:06 <acozine> #endmeeting