14:30:58 #startmeeting Docs Working Group aka DaWGs 14:30:58 Meeting started Tue Sep 8 14:30:58 2020 UTC. 14:30:58 This meeting is logged and archived in a public location. 14:30:58 The chair is acozine. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:30:58 Useful Commands: #action #agreed #halp #info #idea #link #topic. 14:30:58 The meeting name has been set to 'docs_working_group_aka_dawgs' 14:31:10 #topic opening chatter 14:31:13 who's around? 14:31:19 samccann is out today 14:31:37 gundalow is out as well 14:32:03 official agenda begins with https://github.com/ansible/community/issues/521#issuecomment-684942921 14:33:30 andersson007_: briantist cyberpear felixfontein madonius persysted shaps tremble wangbaoshan_ zbr are you talking docs today? 14:36:03 sounds like I'm on my own today 14:36:08 I'll post a couple of updates 14:36:26 #topic status updatest 14:36:29 er 14:36:36 #topic status updates 14:36:49 it wouldn't do to have typos in the topics!!! 14:36:55 hey! 14:37:01 felixfontein: hey~ 14:37:07 heh, I can't type today 14:37:11 #chair felixfontein 14:37:11 Current chairs: acozine felixfontein 14:37:22 isn't it still early for you? ;) 14:37:37 not super early - 9:30 AM 14:37:44 I'm in the midwest 14:38:07 for some people, that qualifies as almost in the middle of the night ;) 14:38:18 heh, that is true 14:38:35 I see US people posting at 1:00 AM 14:39:41 I'm just posting a couple of updates about the release 14:40:16 #info the Ansible 2.10.0 package release date has slipped to September 15 14:41:36 #undo 14:41:36 Removing item from minutes: INFO by acozine at 14:40:16 : the Ansible 2.10.0 package release date has slipped to September 15 14:41:44 it's September 22 14:41:49 ??? 14:41:57 Sept 15 will be RC1 14:42:02 oh, the 15th is the final freeze 14:42:03 (since ansible-base 2.10.1 slipped) 14:42:15 I was reading the PR for the roadmap 14:42:25 ah. I was looking at T.'s email :) 14:42:26 guess I need some coffee 14:42:49 #info see https://docs.ansible.com/ansible/devel/roadmap/COLLECTIONS_2_10.html for the latest schedule details 14:43:20 looks like we are not committing to an actual release date ;-) 14:44:12 I guess we'll try, but first we need ansible-base 2.10.1 to be released 14:44:17 oh, we are, we just didn't update it 14:44:30 https://github.com/ansible/ansible/pull/71647/files#diff-6813b85d2e1c466d67be180ed2f57b74R38 14:44:52 okay, I think I'm up to date now 14:47:16 #info Ansible 2.10.0 package release date is September 22 14:47:16 from my side there are zero updates, I've not done anything with changelogs or ansible release this last week 14:47:47 I know I did things last week 14:48:04 but what they were . . . . well, that's a bit fuzzy in my mind 14:48:35 ah, I was working on updating more pages for the collections ecosystem 14:48:39 https://github.com/ansible/ansible/pull/71606/files 14:48:41 etc. 14:48:58 #topic updating docs for collections 14:49:40 #info if you notice a docs page that needs updates to reflect the collections ecosystem, please post a note in the ansible-docs channel 14:49:50 (PRs always welcome as well) 14:51:29 oh, we had the first conversation with the web team about the "bitflip" release process - it looks like we will be able to store built artifacts on the webservers to have them ready for the release 14:52:00 more details to come on that 14:52:10 #topic redirect status 14:52:31 docs team needs to publish the redirects to the testing site - that should happen this week 14:52:40 then we can try them out 14:53:12 bitflip: cool! 14:53:20 redirects: also cool! :) 14:53:29 it's coming together 14:53:40 kinda last minute, but it's coming together 14:54:01 oh, and I'm having a pre-collections redirect mystery 14:54:02 indeed 14:54:36 if you hit http://docs.ansible.com/ping_module.html it redirects to a nonsense URL 14:54:44 I thought I'd found the problem and fixed it 14:54:54 the fix worked on the test site 14:55:10 but I published to production and the problem has not gone away 14:56:21 * acozine digs for the regex 14:56:32 what do you mean by nonsense URL? 14:57:00 for me, it first redirects to https, then to https://docs.ansible.com/ansible/ping_module.html, then to https://docs.ansible.com/ansible/latest/ping_module.html, and then finally to http://docs.ansible.com/ansible/latest/modules/ping_module.html (which actually works) 14:57:32 huh, okay that's how it's supposed to work 14:57:48 * abadger1999 waves 14:57:49 why is it still sending me to https://docs.ansible.com/ansible/latest/ping_module/modules/.html ? 14:57:56 morning abadger1999! 14:57:58 must be a local cacheing issue 14:58:19 welcome abadger1999 14:58:21 #chair abadger1999 14:58:21 Current chairs: abadger1999 acozine felixfontein 14:58:30 acozine: it uses 301 Moved Permanently, so in case the redirect was broken once when you tried it in your browser, your browser stores it indefinitely 14:58:49 clearing the/some sort of cache should solve it 14:58:57 phew, this is great 14:59:06 I was racking my brains, trying to figure out why it wasn't fixed 14:59:19 I usually prefer to trace redirects manually with `curl -i` to see what they really are, because browsers are too clever ;) 15:00:11 that sounds like a great approach - you just post the first URL in a terminal? 15:00:38 TIL 15:00:57 yes, I start with `curl -i http://docs.ansible.com/ping_module.html`, and then look at its `Location:` header, curl that one, etc. 15:01:36 that is going to be a sanity-saver with collections 15:01:40 thanks! 15:03:36 you can probably also use the browser's dev tools by going to the network tab, disable caching (usually a checkbox), and set it so it won't clear on a redirect; then you can also follow redirects pretty well 15:03:54 I'm not sure if the disable caching checkbox affects the 301 Moved Permanently cache though 15:04:05 good to know - I like the command-line solution, though 15:04:25 it makes the process visible 15:06:01 #topic more status updates 15:06:09 I have a couple of other changes to report 15:06:28 we've started interviewing candidates for the open Technical Writer position 15:06:55 if anyone in the community is interested, please reach out to me as quickly as you can! 15:07:29 good news :) 15:07:43 and, because we expect to welcome a third writer to the internal team, samccann and I are experimenting with an agile process for docs work 15:08:20 as we figure out what works for us, we will post updates and invitations to participate to the DaWGs 15:08:41 (up until now we have organized our work very informally) 15:09:03 just don't make it too formal :) 15:09:14 heh, we won't 15:10:05 but some sense of "what are we hoping to achieve on what time-scale" would probably be helpful 15:10:52 and it might be fun to post weekly challenges for docs 15:11:11 15:11:38 "this is community.general week" or something, that would give new contributors some direction 15:12:42 hm, I should info the job one 15:13:13 #info if you are interested in the open Technical Writer position on the Ansible team, reach out to acozine as quickly as you can! Interviews have begun. 15:13:47 that's all I can remember for now . . . 15:13:56 there's a reason we didn't schedule this meeting for Mondays 15:14:04 :-) 15:14:12 Question about the redirects. 15:14:16 I need a day back at my desk to pick up the threads 15:14:37 abadger1999: excellent, I may or may not have an answer 15:14:37 What's the next step? Should we check the .htaccess files I have on toshio.fedorapeople.org into the private repo? 15:15:13 Next step on redirects: open a PR against the private repo so we can publish to the testing site 15:15:15 * abadger1999 hasn't looked if there's a way to send them just to the testing server and not to the production site 15:15:20 yes, there is 15:15:21 Cool. 15:15:33 which has saved me many times 15:16:17 I'd like to try putting that .htaccess file in a subdirectory 15:16:25 15:16:50 do you have that file as a commit against ansible/docsite? 15:16:53 or just as a file? 15:16:55 Currently we have two .htaccess files. They end up in the ansible/X.Y/ directories. 15:17:04 ah, that sounds even better 15:17:22 acozine: They're just files. There's a WIP PR in antsibull for the script which generates them. 15:17:37 okay, I can pull them into the repo 15:18:03 acozine: I can try to break it up by collection on the 2.10+ directories if you want (or that could be an enhancement for later) 15:18:16 Cool 15:18:21 hmmm 15:18:34 acozine: I will get you the files.... tarball to download sound good? 15:18:40 sure, that sounds fine 15:19:18 despite the XKCD classic cartoon, I do have one `tar` command embedded in my memory 15:19:27 `tar -xvzf` 15:19:37 we'll see if that works in this instance ;-) 15:19:40 you can also leave the `-` away 15:19:59 felixfontein: no doubt, but then my fingers get confused 15:20:13 * acozine types that again without the - 15:20:21 `tar xvzf` 15:20:38 huh, that works from muscle memory too 15:20:40 I always forget which one of zZjJ are needed for which compression algorithm... 15:21:37 that muscle-memory command works with the specific tarballs we used at my old job (on a digital library project) 15:21:47 I could not tell you what algorithm we used, though 15:21:50 http://toshio.fedorapeople.org/ansible/ansible-docs-redirects.tar.gz 15:22:08 Untarring will create 2.10/.htaccess and 2.9/.htaccess 15:22:20 I just did it so often it got hardwired into my fingers 15:22:55 heh, or there's the built-in mac utility, which figures it out for you 15:22:58 * acozine gets lazy 15:23:01 :-) 15:28:21 all right, I need more caffeine before I tackle that task 15:28:27 thanks abadger1999 15:28:34 No problem :-) 15:28:37 anything else for the DaWGs today? 15:28:57 I saw andersson007_'s PR to postgresql_user docs 15:29:07 I'll go through that later today 15:30:20 considering it was a long weekend in the US, the PR count isn't too bad 15:30:28 up to 70 open docs PRs on ansible/ansible 15:31:15 I was worried it would be back to 90 or so 15:31:23 Cool :-) 15:31:51 hey, we're going to finish in exactly an hour 15:31:54 amazing~ 15:32:07 s/~/! 15:32:42 A sure sign that we're forgetting something ;-) 15:33:08 heh, true - I forgot to do an open floor 15:33:14 #topic open floor 15:34:08 this is an opportunity to ask questions, make comments, request help, or raise topics related to documentation for Ansible 15:34:40 anyone can add a topic to the formal agenda by adding a comment to https://github.com/ansible/community/issues/521 15:34:45 :) 15:34:55 or bring it up in open floor any time 15:35:22 is there anyone who has been waiting patiently to chat? 15:36:05 we welcome all participants and all questions, from beginner to advanced 15:36:56 hearing none for this week, I'm going to close out the official meeting 15:37:02 thanks again abadger1999 felixfontein 15:37:05 #endmeeting