14:30:41 #startmeeting Docs Working Group aka DaWGs 14:30:41 Meeting started Tue Mar 3 14:30:41 2020 UTC. 14:30:41 This meeting is logged and archived in a public location. 14:30:41 The chair is acozine. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:30:41 Useful Commands: #action #agreed #halp #info #idea #link #topic. 14:30:41 The meeting name has been set to 'docs_working_group_aka_dawgs' 14:30:54 is anybody around? 14:31:07 I see felixfontein is out . . . anybody else 14:31:10 ? 14:31:26 * samccann waves 14:31:39 #chair samccann 14:31:39 Current chairs: acozine samccann 14:32:29 heh, maybe today really will be just "us chickens" 14:32:36 could be 14:33:34 #topic collections update 14:33:51 devel branch is currently frozen 14:33:57 so no PRs can be merged 14:34:00 joining late here 14:34:07 welcome cbudz 14:34:11 #chair cbudz 14:34:11 Current chairs: acozine cbudz samccann 14:35:07 core team is working on stripping the core repo down to its core essentials 14:35:25 that work is happening on a separate branch, for safety's sake 14:37:14 How long is the freeze? is it till March 11? 14:37:32 I'm hunting for the link to the letter that details everything 14:37:44 as they say at the train stations, "there will be a short delay" 14:37:52 it's here . . . somewhere 14:38:40 found it! 14:38:54 #info details on the freeze at https://groups.google.com/forum/#!msg/ansible-devel/6UAfogEDtG8/wMTgxBGWCgAJ 14:39:21 kewl thanks! 14:40:30 to summarize: 14:40:36 So I'm unclear about what should go in the temp branch (once it's opened), from a docs perspective? I'm guessing no reason to work on the temp branch for .rst docs? 14:40:51 unless something brakes the docs build 14:41:15 I think from a docs perspective, we should do all work on rst files locally against devel and hold off on opening PRs until the freeze is lifted 14:41:49 module docs changes can move ahead for modules that are already in collections 14:42:09 and also for modules that appear in collections during the transition 14:42:28 unfortunately, we have no way currently to publish the collections docs until the freeze is over 14:43:24 module docs changes should happen in migrated collection repo, right? 14:43:30 correct 14:43:45 #info - any .rst docs works should happen on devel and hold off on opening the PR until the devel freeze is over 14:44:25 #info module docs changes should happen in the migrated collection repo 14:47:25 there are some changes in the works for the post-migration documentation pipeline 14:48:06 I hope to have more details next week 14:49:30 what else do we have on the agenda? 14:49:48 let's see, agenda is at https://github.com/ansible/community/issues/521#issuecomment-590924964 14:50:38 #topic status updates 14:50:50 cbudz or samccann, one of you want to go first? 14:51:00 sure i'll go 14:51:48 I still have a few issues in the pipeline i'm working on that have gotten sidetracked a bit by the catalog onboarding guide work and their api doc, which are due soon_ish 14:52:51 I did also get some info to update collections docs on the review of AH FAQ that I'll need to add to the collections docs 14:52:53 that's it for me 14:53:37 #info worked to get docs PR count down before the freeze 14:53:38 cbudz: where/who did the collections docs updates come from? 14:54:45 samccann: ++ for getting the docs PR count lower 14:54:55 Initially via Anshul but some updates were added by Andrius 14:56:38 I'll follow-up offline, have to drop for the aaS docs meeting 14:56:41 cbudz: let's make sure the AH docs and the Ansible docs stay in sync 14:56:47 on the topic of collections 14:56:48 agreed 14:57:09 docs PR count stands at 73 14:57:37 I wonder if we have a label for "this should go to collections" 14:57:58 we already have two new PRs that change module docs 14:58:02 there is supposed to be some tool in the works that will help move PRs/issues to new locations 14:58:08 (new since the freeze) 14:58:24 so I think we followup with gundalow before we give any answers to those PRs etc 14:58:27 I'm thinking a standard comment for new PRs and issues would be helpful 14:58:40 samccann: sounds like a good idea 14:59:10 samccann: any other status updates for today? 14:59:14 #info there may be help 'down the road' with identifying and moving PRs/issues that belong in a new collection instead of ansible/ansible. Timeline TBD 14:59:43 #info working on updating examples in Networking guides to use collections since they are all active already on Galaxy (though in prerelease form) 14:59:52 oh and while I'm at it... 15:00:38 #info ansible-galaxy collection install - for the prerelease networking collections, use a version in that command. Currently it won't pick the 'latest' as it's a prerelease number 15:00:48 learned that yesterday :-) 15:00:52 that's it for me 15:01:11 my update is simple 15:02:23 handling last-minute changes to the post-migration docs publication pipeline 15:02:25 and 15:02:38 working intermittently on my User Guide overhaul 15:03:12 #info work progressing on post-migration docs publication pipeline 15:03:26 oh, thanks samccann 15:03:28 #info continued overhaul for the User guide 15:03:40 :-) makes me feel like I'm contributing 15:04:24 someday I will become fluent in IRC meeting-speak 15:04:33 but today's not the day 15:04:41 lol 15:05:00 looking at the agenda, the last three items are PRs, issues, and Open Floor 15:05:08 i honestly only know info and link. there are more.. maybe that's a goal for this year.. sprinkle meetings with more IRC meeting goodness 15:05:45 maybe if we lurk in the ansible-devel meetings we'll get the hang of it 15:05:56 we can't do anything about PRs this week (or for the next two weeks either) 15:06:07 so that leaves Issues and Open Floor 15:06:36 #topic Docs Issues 15:06:40 #info no PRs will be merged on ansible/ansible until late March 15:07:02 #info as of today we have 222 open issues on ansible/ansible with the label `docs` 15:07:05 https://github.com/ansible/ansible/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+label%3Adocs 15:07:15 so I think we could spend some time with the issues backlog and close out some that may no longer apply or have been fixed etc 15:07:32 do you mean in general? or right now? 15:08:32 maybe we could set aside half an hour or an hour each day while devel is frozen, and post issues in this channel? 15:08:50 samccann: I think you're right that a lot of the older ones are irrelevant now 15:08:52 oh I mean in general forsure 15:09:17 but I like the idea of using this channel for help with what we can't figure out yeah 15:09:39 and if we did it 30 min a day, that would force us to actually DO it.. .vs other stuff 15:09:47 agreed 15:10:11 what do you think would be a good time of day? 15:10:30 I'm thinking early for us, so European folks could still join us 15:11:02 for tomorrow, let's try my usual logging-on time (which is about now0 15:11:08 sounds good. Say 10am ET? 15:11:14 sounds great 15:11:27 we'll see how much participation we get at that hour 15:11:41 #agreed will we do docs issue triage every day here at 10am ET to work through the docs issues backlog. Community participation would be most welcome! 15:12:11 hooray! it would feel great to get the docs issues down under 100 15:12:13 hmm... there will be days with meetings tho 15:12:32 so I think on those days, we post here as soon as we can on when the docs issue triage would move to? 15:12:54 tomorrow at 10am ET works for me 15:13:23 if it works for you tomorrow, then we can set a rhythm where at the end of each day's session, we announce the time for the next day 15:13:39 I'll be travelling to a doc(tor) apt that happens at 10:30. But I should in theory be able to log in from there as i'll be sitting in the waiting room (not my doc apt) 15:14:15 ah, okay, shall we start a little earlier tomorrow? 15:14:19 and alas, just to be the problem child - I signed up for a class on jupyter notebooks on Thurs that starts at 10 and runs for 4 hrs 15:14:20 usual DaWGs time? 15:14:29 ok by me 15:14:52 okay, let's do the usual DaWGs meeting time tomorrow and spend 30 minutes 15:14:54 see how it goes 15:15:00 then take it day by day 15:15:21 #info tomorrow's docs issue triage will happen early - 9:30am ET. We will post start times on a day by day basis 15:15:33 meetings meetings meetings.. ah the joys 15:15:35 heh 15:15:50 this one is less a meeting and more a public working session 15:16:13 and by "this one" I mean the issue-review thing 15:16:47 and now it's time for . . . 15:16:52 #topic Open Floor 15:16:54 oh I meant my schedule conflicts 15:17:01 heh 15:18:03 if anybody on the channel has a question, comment, idea, suggestion, or complaint, now is your chance! 15:18:22 there is no such thing as a stupid question 15:18:29 beginners welcome 15:19:47 agenda items encouraged also 15:20:01 and also... chocolates 15:20:15 if you want dedicated time during this weekly meeting for a topic you are interested in, please add a comment to https://github.com/ansible/community/issues/521 15:20:20 mmm, chocolates? 15:23:30 🍫 15:23:39 nice!! 15:24:00 hearing no topics for the open floor today, we will close this meeting a few minutes early 15:24:20 (and I'm going to get a snack, then go vote) 15:24:42 heh enjoy! 15:25:19 #endmeeting