14:31:24 <acozine> #startmeeting Docs Working Group aka DaWGs
14:31:24 <zodbot> Meeting started Tue Nov 24 14:31:24 2020 UTC.
14:31:24 <zodbot> This meeting is logged and archived in a public location.
14:31:24 <zodbot> The chair is acozine. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:31:24 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
14:31:24 <zodbot> The meeting name has been set to 'docs_working_group_aka_dawgs'
14:31:30 <samccann> o/
14:31:31 <acozine> felixfontein: hi!
14:31:38 <acozine> #chair felixfontein samccann
14:31:38 <zodbot> Current chairs: acozine felixfontein samccann
14:31:44 <lmodemal> I will see you all next week. I am on PTO for the holidays :)
14:31:47 <acozine> #topic opening chatter
14:31:58 <acozine> have a restful week lmodemal
14:32:08 <acozine> and happy Thanksgiving!
14:32:16 <gundalow> lmodemal: enjoy
14:32:17 <felixfontein> lmodemal: enjoy your PTO! :)
14:32:21 <lmodemal> acozine: thanks! Happy Thanksgiving!
14:32:24 <acozine> #chair gundalow
14:32:24 <zodbot> Current chairs: acozine felixfontein gundalow samccann
14:32:27 <lmodemal> thank you felixfontein!
14:32:36 <lmodemal> thanks gundalow!
14:32:52 <gundalow> I'm in training at the moment, though I'll skim here occasionally
14:33:08 <acozine> today's agenda: https://github.com/ansible/community/issues/521#issuecomment-729054696
14:33:17 <acozine> gundalow: okay, we won't distract you too much
14:33:23 <acozine> who else is around?
14:34:09 <acozine> aminvakil: andersson007_ baptistemm briantist cybette madonius mrproper persysted tremble you chatting docs today?
14:36:02 <acozine> #topic slimming down the tarballs by removing docs
14:36:06 <acozine> this one is quick
14:36:13 <aminvakil> hi!
14:36:37 <acozine> we investigated, and discovered that removing the docs files would not make installing Ansible noticeably quicker
14:36:40 <acozine> so we will not do it
14:36:43 <acozine> aminvakil: hi!
14:36:45 <acozine> #chair aminvakil
14:36:45 <zodbot> Current chairs: acozine aminvakil felixfontein gundalow samccann
14:36:51 <baptistemm> I'm here and available
14:36:57 <acozine> baptistemm: hi!
14:37:02 <baptistemm> Hi there
14:37:03 <acozine> #chair baptistemm
14:37:03 <zodbot> Current chairs: acozine aminvakil baptistemm felixfontein gundalow samccann
14:38:11 <felixfontein> acozine: not at all, or very low priority (i.e. maybe somewhen in the future)?
14:38:15 <acozine> so though it seemed like a nice thing to do (We can make Ansible lighter weight! We can provide an easy way for people to install just the docs!), it turns out the effort is larger than we hoped and the benefit is smaller
14:38:18 <dmsimard> o/
14:38:22 <felixfontein> #chair dmsimard
14:38:22 <zodbot> Current chairs: acozine aminvakil baptistemm dmsimard felixfontein gundalow samccann
14:38:50 <felixfontein> I guess the main benefit now is that you could get .html docs
14:39:02 <acozine> felixfontein: I'd say very low priority
14:39:07 <dmsimard> acozine: is the methodology for the tests as well as the results available ?
14:39:20 <acozine> we can certainly do it in future
14:39:55 <acozine> dmsimard: good question, let me dig back and see if I can find the stats
14:40:21 <felixfontein> acozine: good, so in case someone asks, we can always say "if you volunteer to implement it..." ;)
14:40:24 <dmsimard> ok, this is in part for personal curiosity as I'd like to get a better grasp on the install performance regression from 2.9 to 2.10
14:40:56 <acozine> felixfontein: heh, yep
14:41:07 <samccann> So as she's digging up info, what i recall is that the size difference is somewhere around 5% less if we pull out all the docs
14:41:08 <felixfontein> dmsimard: it's probably mostly "more content => slower"
14:41:09 <dmsimard> thanks for looking, can wait until later for the data
14:41:32 <acozine> dmsimard: rst files are 983 out of 32624 files and 25MB out of 225MB
14:41:42 <samccann> And speed increase was just a one-off quick test ( hardly scientific) but maybe shaved off a similar amount
14:42:07 <acozine> compressed size difference was 28MB vs 29MB with docs included
14:42:08 <felixfontein> shaving off tests will yield a LOT more (both in file count and size)
14:42:41 <felixfontein> once tests have been moved to a separate tarball, docs would be interesting again. before that, not really
14:42:44 <samccann> and it didn't seem worth it on the docs side to go through all that and coordinate w/ Legal to see if we are even allowed to pull source out of the source tarball for example.
14:42:45 <dmsimard> felixfontein: yeah I'm a bit dubious, mostly because the delta between 2.9 and 2.10 shouldn't be /that/ significant considering it mostly boils down to moving files out of tree
14:42:45 <acozine> with and without docs, installing took between 90 and 100 seconds
14:42:56 <acozine> no repeatable difference
14:42:58 <dmsimard> but somewhat off topic
14:43:18 <dmsimard> acozine: thanks
14:43:27 <samccann> #info Compressed size w/o docs is 28MB vs 29MB today. Installing took 90 sec w/o docs vs 100 sec with
14:43:33 <felixfontein> dmsimard: might be both. but yeah, someone would have to take a closer look
14:43:52 <samccann> #info decision was made that it wasn't worth removing docs from the tarballs at this point.
14:43:56 <acozine> samccann: thanks, having that in the minutes will be useful for Future Us
14:44:33 <acozine> #topic uses of the collection `/docs/` folder
14:44:39 <samccann> having gone through a bunch of old minutes, yep, most definitely it helps!
14:45:37 <acozine> I know this has been on the agenda for a while
14:45:59 <acozine> and i feel we should make better use of the docs folder
14:46:13 <samccann> Toshio created a draft of ideas... now i just need to find it!
14:46:35 <acozine> oh, excellent
14:46:37 <samccann> The Powers That Be also have ideas/plans for that folder wrt Automation Hub/Galay-ng
14:46:57 <felixfontein> dmsimard: 2.9 has 4219 files in modules/ and plugins/, while 2.10 has 7247 files (not including ansible-base's modules and plugins)
14:47:14 <dmsimard> felixfontein: thanks, worth investigating
14:48:08 <samccann> #info some ideas about the collections /docs folder etc - https://hackmd.io/pPeMLaFYSt2W8RAqm-ZkXA
14:49:39 * acozine has a pressing domestic issue, BRB
14:50:56 <samccann> ok so Toshio created that draft doc of ideas on the collections /docs folder etc.
14:51:02 <dmsimard> being able to link to collection docs means they are hosted somewhere
14:51:38 <dmsimard> do we render collections docs somewhere now ?
14:51:39 <samccann> Well the idea is that, in the future - the rst files in /docs would be visible within Automation Hub and Galaxy NG (I think... that's still TBD)
14:51:56 <samccann> And/or we would also bring them in via the docs pipeline to docs.ansible.com
14:52:11 <samccann> should have info'd that... but anyway.
14:52:48 <samccann> #info the goal is to allow collection owners to write 'user guide' and more complex examples etc within the collection /docs folder and then render them in either docs.ansible.com or some future galaxy-ng
14:53:00 <samccann> so we don't render them at all right now.
14:53:38 <acozine> the only docs we render from collections now are the module/plugin docs
14:53:54 <samccann> But we also have people using that folder for 'other things' already - like the network collections that generate module docs rst files so they can link to them from their readme. I feel like other collection owners have put other things in there too. Maybe rendering on their own docsite somewhere? That might just be my baseless worry though
14:54:43 <felixfontein> that's a good question
14:55:20 <dmsimard> is there any existing convention or standard for the docs/ directory at all ?
14:55:21 <felixfontein> I would suggest that we only include docs that we are explicitly suggested to do so by the collection, for example by looking at a `docs/antsibull.yml` file and only using files references in there
14:55:25 <felixfontein> dmsimard: no
14:55:33 <samccann> dmsimard - no
14:55:52 <samccann> It was created for 'future use' and we are only now grappling with what we want that future use to be
14:56:39 <samccann> #info  we could only include /docs that are explicitly suggested by the collection - e.g. looking ad docs/anstibull.yml file to find rst files to include
14:56:56 <samccann> Thanks felixfontein - seemed like an idea worth remembering :-)
14:57:58 <felixfontein> samccann: that file could also contain tags, or other kind of categorizations - as well as the order in which they should be referenced
14:58:34 <felixfontein> it definitely would be good to have some validation for anchors. no idea how hard that is to do though
14:58:41 <samccann> The difficulties in general - creating an RST user guide (and I'm assuming RST because that's what WE want... but Galaxy-ng only recognizes .md right now for the readme).
14:59:28 <samccann> A guide is a set of files, related, crossreferenced, etc etc.  So we  would have to be very specific about what we can support (we being either docs.ansible.com or some future galaxy version)
14:59:37 <acozine> yeah, currently Automation Hub renders rst files sort of like GitHub does
14:59:55 <felixfontein> but in that case, it does support .rst?
15:00:08 <samccann> automation hub doesnt render rst at all.. just md... and a considerable less amount than github for sure.. alas
15:00:19 <samccann> but of course that's just today as all they render is the readme
15:00:53 <felixfontein> ah, so AH also doesn't render anything in docs/?
15:01:01 <acozine> samccann: I thought AH "rendered" rst without actually processing it (so no links), am I misremembering?
15:02:15 <samccann> the only info I have is that it is .md only and only the readme. I could be wrong tho.. .worth asking
15:02:35 <samccann> #action samccann ask galaxy team what they render today - md/rst and if they look at all in the /docs folder
15:02:36 <dmsimard> I don't know about automation hub but galaxy does require a readme.md, won't let you publish otherwise
15:02:50 <dmsimard> readme.rst not good enough
15:03:19 <samccann> agreed. I'll gather some facts later to see if my info is woefully outdated or not
15:03:33 <acozine> samccann: thanks!
15:03:46 <felixfontein> AH is essentially galaxy-ng, right?
15:03:59 <acozine> felixfontein: yes
15:04:53 <abadger1999> felixfontein: alternative to a file which lists the files to include would be a different directory.  Like docsite/ instead of docs/
15:05:09 <acozine> abadger1999: good morning!
15:05:21 <acozine> do you want to be furniture?
15:05:23 <abadger1999> (but i like the idea of someplace to put tags)
15:05:27 <abadger1999> Sure
15:05:32 <acozine> #chair abadger1999
15:05:32 <zodbot> Current chairs: abadger1999 acozine aminvakil baptistemm dmsimard felixfontein gundalow samccann
15:05:54 <dmsimard> furniture, haha :D
15:06:26 <felixfontein> abadger1999: docsite/ would make it harder to decide how and in which order to link to files from the antsibull-generated default page
15:07:08 <samccann> we could say it all starts with index.rst  and that links to whatever comes next and it the order listed
15:07:46 <samccann> but we'd still have problems if someone wanted to put TWO or more guides in there... they'd have to create subdirs maybe with their on index.rst for those subdir rst files, etc etc
15:08:59 <acozine> samccann: I like the "you must have an index.rst file that points in some way to all your other content" rule
15:09:16 <acozine> they could have an index file that was a list of guides if they want multiple guides
15:09:38 <abadger1999> Felixfontein: how are you imagining the config file addresses that?
15:11:56 <felixfontein> abadger1999: if you don't want to allow collections to template the main index.rst, you could allow the .yml to provide a list with RST references and optional titles, and these are inserted as a list at the top. or you could allow sections (with titles), each containing lists of links
15:12:18 <abadger1999> <nod>
15:12:29 <felixfontein> if collections use this to also document filter and test plugins and roles, having sections is very useful
15:13:09 <felixfontein> then you can maybe add a section `Roles` at the top of https://docs.ansible.com/ansible/latest/collections/community/general/ with one entry per role (and link to the role's documentation)
15:13:22 <abadger1999> Okay, so something like: the collection index page we generate has a section that links to a list of pages that they've listed?
15:13:45 <acozine> is there a collection that would be a good "guinea pig", one where we could try these ideas out?
15:14:30 <acozine> even if we just make something with lorem ipsum, it would help to have an example, I think
15:14:31 <samccann> so filter and test plugins would be solved by the PR/work bcoca is doing, wouldn't it?  as in once that's done, the antsibull is modified to bring it in the same as we do for all other plugin?
15:14:45 <felixfontein> acozine: for lorem ipsum, a test collection would be best :)
15:14:47 <abadger1999> The only issue with that which i see is that a list of links isn't very enticing
15:14:54 <acozine> felixfontein: ah, of course!
15:14:58 <samccann> acozine a test collection is easy.. the difficulty is getting everyone to agree on the strategy
15:14:59 <felixfontein> samccann: yes, but no idea how long it takes until that will be available
15:15:02 <acozine> heh
15:15:03 <samccann> which imo has to come first
15:15:35 <felixfontein> the same could be said about roles, and eventually playbooks
15:15:38 <samccann> (clarifying the strategy has to come first.. not necessarily the test/plugin docs pr
15:16:06 <samccann> #info whateve solution we have for collection /docs needs to cover roles, playbooks, as well as any other guides collectoin owners want to create
15:16:14 <acozine> my brain likes to have a tangible example so I can look at it and say, 'Oh, I see how this fits together - this part works really well, could we do that part some other way?'
15:16:58 <abadger1999> @samccann: yes. Although I'm a bit worried that we don't have a seat at that table.  We should have only on the format of DOCUMENTATION strings since we have to template using them
15:17:53 <felixfontein> does anyone know if there's actually a PR now for test/filter plugins? bcoca has been talking about that more than once, but I've never seen anything
15:18:23 <samccann> abadger1999 - seat at which table?  :-) the /docs folder, or how roles documentation will work? or both tables in an all you can eat docs buffet?
15:18:25 <abadger1999> No
15:19:05 <abadger1999> How filter and test documentation is structured
15:19:36 <abadger1999> The docs for my impression is no one wants to touch that except us at the moment
15:19:36 <felixfontein> I was hoping to get an idea from a PR (or branch)
15:20:15 <samccann> #action - we need to get involved in how filter/test docs are structured, how the collection /docs folder works, how roles documenttion will work.. many seats... many tables
15:20:42 <acozine> is there anything we can do in the next week to move this topic forward?
15:21:04 <samccann> can we prioritize the list of things maybe today?
15:21:16 <abadger1999> (no was to "is there a pr")
15:21:38 <abadger1999> Maybe scope?
15:21:43 <samccann> like which do we want to tackle/get involved with first - roles (which I think has an argspec already?) test/filter - which has ideas in someone's head) or collection /docs folder use?
15:22:25 <abadger1999> What do we want a collection owner to be able to do?  [X] include ad hoc documentation from the collection (example: guides)
15:23:03 <abadger1999> [?] Create their own index to the autogenerated and static content
15:23:38 <samccann> can you elaborate on that 2nd one?
15:24:09 <felixfontein> I guess the main thing people want to do is inserting something at the top of the index (below the main title)
15:24:36 <felixfontein> (though the main title 'Plugin Index' should maybe also be adjustable?)
15:24:50 <acozine> Collection-level documentation
15:25:15 <acozine> and documentation for all included objects (roles, filter plugins, etc.)
15:25:28 <abadger1999> samccann: So right now we generate this index page at the toplevl of a collection: https://docs.ansible.com/ansible/2.10/collections/amazon/aws/index.html#plugins-in-amazon-aws
15:26:00 <abadger1999> do we want collectionowners to be able to replace this?  Or augment it?
15:26:11 * baptistemm dioes not participate because he is clueless
15:26:56 <felixfontein> abadger1999: to prevent total chaos, I would prefer augment over replace
15:26:59 <acozine> baptistemm: reading is also a form of participation
15:27:00 <samccann> abadger1999 - augment
15:27:10 <acozine> +1 for augment
15:27:49 <abadger1999> Or a different option: We start pointing people at a different page a the toplevel for the collections and then this page, intact, is what they come to if they click on the "Included plugins" section of that page.
15:28:05 <samccann> the vision imo is that as a user, I want to look at a collection (say amazon.aws) and find all the info I need to decide IF I want to use the collection, what I can do with the collection, and how to do those fancy things
15:28:09 <felixfontein> Maybe we should make the main title the collection's name, allow some subsections, and then have a subsection called 'Plugin Index'
15:28:40 <felixfontein> so that the plugin index is always also on the main page, and the collection name is there as well, but collections can insert things between these two
15:28:59 <abadger1999> It feels like a user would probably be best served if there was a larger amount of information on a collection than just the list of included plugins.
15:29:12 <samccann> ^^ agreed
15:29:45 <felixfontein> +1
15:29:57 <acozine> if the collection has roles, do we also add a 'Role Index'?
15:30:18 <felixfontein> for network collections, some general "small example how to actually use this" would be useful at that level
15:30:33 <samccann> acozine: imo, yes.
15:30:46 <samccann> and separate from the plugin index
15:30:48 <abadger1999> How about I make a mock up (image) of what that page could look like with extra sections?
15:31:13 <felixfontein> f.ex. for community.routeros we added that to the README: https://github.com/ansible-collections/community.routeros/#using-this-collection but if someone looks at the plugin index https://ansible.fontein.de/collections/community/routeros/ that's a lot harder to figure out
15:31:15 <acozine> that sounds great, thanks abadger1999
15:31:20 <samccann> +1 so long as it's note a lot of work abadger1999
15:31:30 <samccann> s/note/not/g
15:32:00 <samccann> great point felixfontein - some readmes have a good bunch of info that never gets to docs.ansible.com
15:32:04 <baptistemm> does looking how it is done on puppet help ? https://forge.puppet.com/modules/puppetlabs/stdlib
15:32:13 <abadger1999> #info would like the collection index to have collection defined: Summary section, auto generated plugin index, links to static content section.
15:32:51 <acozine> baptistemm: interesting, yes, thanks
15:33:17 <baptistemm> it takes the readme.md but they are other folders in the github repo (likes examples/).
15:33:23 <felixfontein> abadger1999: and auto-generated collection name and version at the top :)
15:33:56 <abadger1999> <nod>  It would probably be nice to do that immediately :-)
15:34:27 <abadger1999> #info we should put collection name and collection version onto the collection index page (regardless of how the rest of the page is structured)
15:34:47 <samccann> #info see how puppet does some of this https://forge.puppet.com/modules/puppetlabs/stdlib - with  tabs for changelogs, example foler from github etc
15:36:44 <acozine> we're just over one hour
15:36:50 <baptistemm> already
15:36:59 <acozine> I'd like to shoe-horn one more topic in, if I may
15:37:38 <acozine> are we happy with next steps for the `/docs` folder work?
15:37:51 <acozine> (in collections)
15:38:08 <acozine> baptistemm: time flies when you're chatting about docs!
15:38:09 <samccann> #action abadger1999 to do a slight mockup of what a new collectoin page could look like
15:38:28 <acozine> samccann: thanks
15:38:28 <abadger1999> I like the puppet labs page.... I think I like it because it's more split up.
15:38:40 <acozine> they pack a LOT of information into a single screen
15:39:00 <abadger1999> yeah, without even getting to the huge list that we're trying to push in there.
15:39:01 <acozine> access to multiple versions through the drop-down, different types of documentation on panes, etc.
15:39:08 <baptistemm> but documentation is just a single README.md
15:39:20 <abadger1999> They also have separate tabs/pages for more info, though
15:39:56 <acozine> yeah, but it's easy to see that the other info is available
15:40:00 <abadger1999> Yep
15:40:01 <baptistemm> I think the examples directory is just for those pulling the source code, I assume you want to expose that somewhere from a UI, right ?
15:40:13 <baptistemm> s/from/in/
15:41:02 <abadger1999> Heh.  Maybe.  Or maybe once people have a documentation directory they'll just push examples into there.
15:41:54 <abadger1999> (Which might be better.  examples might contain raw playbooks whereas documentation might contain annotated, formatted examples with links to the reference information..... Hey, I can dream, right? ;-)
15:42:19 <acozine> dreaming about what docs could do got us the excellent module docs we have today
15:42:30 <felixfontein> annoated, formatted examples sounds better
15:42:32 <baptistemm> changelog is equivalent https://github.com/puppetlabs/puppetlabs-stdlib/blob/main/REFERENCE.md for puppet
15:42:38 <abadger1999> acozine: Getting back on topic.  I'm satisfied we have a next step ;-)  We might need to spend some time exploring different mockups before we settle on where to go next, though.
15:42:46 <acozine> sounds good
15:43:06 <baptistemm> .... with a full feature documentation
15:43:12 <acozine> this is something we can chat about here in the channel between meetings
15:43:28 <acozine> so if folks find other good examples, please post them!
15:43:45 <acozine> #topic docs user survey
15:44:06 <acozine> thanks for last week's feedback
15:44:19 <acozine> it helped me focus the draft survey
15:44:37 <acozine> our main goal is to find out how well our documentation is serving different groups of users
15:44:46 <acozine> and whether different groups of users want different things
15:45:03 <acozine> revised draft: https://hackmd.io/JemYBo_8QbqqO9cULo3rJQ#
15:45:32 <acozine> Sections 1 and 2 should tell us how well our documentation is doing
15:45:45 <acozine> Section 3 lets us "slice and dice" the data by different types of users
15:46:15 <acozine> for example, are systems administrators happier with the docs than network administrators?
15:46:47 <acozine> do folks who wish the docs were in their native language have different difficulties than folks who are happy reading the docs in English?
15:47:14 <acozine> all feedback welcome
15:47:18 <acozine> i also have a specific question
15:47:23 <samccann> #info revised user survey draft https://hackmd.io/JemYBo_8QbqqO9cULo3rJQ#
15:47:30 <cybette> if you'd like to include the survey in Bullhorn newsletter, please let me know by Tuesday Dec 1 (newsletter goes out Dec 2).
15:47:48 <samccann> #info Sections 1 and 2 should tell us how well our documentation is doing
15:47:48 <samccann> Section 3 lets us "slice and dice" the data by different types of users
15:47:52 <samccann> dag nammit!
15:48:02 <acozine> I added Question 3.2 so we can identify Red Hat employees' responses
15:48:11 <samccann> #info Section 3 lets us "slice and dice" the data by different types of users
15:48:23 <acozine> does it feel like a comfortable question?
15:48:32 <felixfontein> acozine: how can you distinguish between RH employees and RH AH customers?
15:48:45 <acozine> felixfontein: that's a problem, true
15:48:55 <acozine> we're really asking two questions in one
15:49:12 <baptistemm> acozine: to whom and by which way this survey will be done ? pop-up on the website randomly ?
15:49:28 <samccann> well if our focus is community docs, it would lump all the 'non community' people together?
15:49:30 <acozine> Do you use Ansible at work? and Do you work for Red Hat or for a company with a relationship to Red Hat
15:49:33 <abadger1999> Cool, has gwmngilfen been helping you with the survey?
15:49:45 <acozine> abadger1999: yes, gwmngilfen has been awesome
15:49:52 <abadger1999> Excellent :-)
15:50:08 <acozine> he asked us to include the "how long have you been using Ansible" question
15:50:23 <acozine> so he can cross-refernce this data with other data he has collected
15:50:55 <acozine> baptistemm: we will put it on survey monkey and publicize it through social media, the Bullhorn, etc.
15:51:08 <gwmngilfen> Ty [abadger1999](https://matrix.to/#/@freenode_abadger1999:matrix.org) :)
15:51:53 <acozine> how long of a survey is "too long"?
15:52:22 <felixfontein> I think it has a good length. it's not too long, but contains a good amount of questions.
15:52:36 <felixfontein> for some people, more than one question is already too long. let's ignore those :)
15:53:11 <acozine> I considered adding "Is there a question you wish we'd asked you, that we didn't ask you?" but I think we'd get more snark than data from that.
15:54:10 <acozine> for question 3.2, I really want to make sure community voices are heard, and not drowned out by a high response rate from within RH
15:54:13 <samccann> We could also add it to the docs banner on latest/devel if we wanted to go that far
15:54:21 <samccann> (the survey link)
15:54:47 <acozine> but I'm worried that the question seems like it's motivated the other way - that RH votes or customer votes will "count extra"
15:55:47 * gwmngilfen is just getting tea but will review the current draft in a few mins :)
15:56:28 <felixfontein> acozine: I see what you mean, but I don't think it should be a big problem
15:56:34 <acozine> so the final deadline is one week from today, so we can include a link in the next issue of The Bullhorn
15:56:36 <samccann> I'd just get greg's advice and go w/ it. He's the data guru
15:56:51 <acozine> thanks felixfontein samccann
15:57:14 <samccann> #info feedback deadline is Dec 1 so we can get the survey link into the next Bullhorn
15:57:26 * gwmngilfen blushes
15:57:35 <acozine> okay, we're half an hour over
15:57:40 <acozine> #topic open floor
15:58:03 <acozine> all questions welcome
15:58:11 <acozine> bring your PRs yearning to get merged
15:58:23 <felixfontein> you said, all?
15:58:48 <felixfontein> :)
15:58:54 <acozine> heh, yes, though existential questions will be answered with "42"
15:59:12 <samccann> heh
15:59:13 <felixfontein> I don't have any docs-related PR right now I think (except the collection versions PR for antsibull and I first have to go through abadger1999's feedback)
15:59:36 <acozine> we're behind on reviewing/merging docs PRs
15:59:40 <acozine> so there are a lot out there
16:00:03 <acozine> it's Thanksgiving week in the US . . . Pandemic Thanksgiving
16:00:19 <acozine> so there's a lot of logistics being debated
16:00:24 <samccann> I'll put another plug out there for review/feedback on the proposal to split the docsite
16:00:43 <acozine> samccann: link?
16:00:49 <acozine> I'll info it
16:00:50 <samccann> #info please provide feedback by Dec 3 on Separating Ansible 3.0.0 collection docs from ansible-core - https://hackmd.io/TQmzyhCUSSKa22iFR_079A?both
16:00:59 <acozine> heh, you beat me to it
16:01:04 <samccann> a link and a deadline.
16:01:18 * samccann feeling accomplished this am
16:01:43 <acozine> #info No supplementary meeting on Nov. 26, since it's Thanksgiving Day for the US-based docs team
16:01:51 <felixfontein> Pandemic Thanksgiving = virtual turkey eating?
16:02:02 <abadger1999> felixfontein: https://github.com/ansible-community/antsibull/issues/219
16:02:07 <samccann> virtual pie eating for my family
16:02:15 <samccann> since we'll zoom-pie later in the day
16:02:17 <acozine> felixfontein: my usual group is doing a "drive-through Thanksgiving"
16:02:31 <felixfontein> abadger1999: I'll fix that ;)
16:02:40 <abadger1999> hee hee :-)
16:02:48 <felixfontein> acozine: also sounds interesting
16:02:54 <acozine> we've done a pot-luck dinner for so many years, everyone makes the same dish year after year
16:02:57 <abadger1999> I like this!  felix finds a problem, I open a ticket for it, then he fixes it ;-)
16:03:05 <felixfontein> hehe
16:03:13 <samccann> woot!
16:03:18 <gwmngilfen> contributing++ :)
16:03:24 <felixfontein> mostly because I already fixed the hard part ;)
16:03:30 <acozine> so we're packaging them in individual servings, driving by my brother's house to drop them off, then driving by again to pick up one of each dish to take home
16:03:32 <abadger1999> :-)
16:03:58 <gwmngilfen> abadger1999: that is some A-grade community manipulation^w management there *chef kiss*
16:05:09 <acozine> anything else for open floor?
16:06:01 <acozine> going once
16:06:06 <acozine> going twice
16:06:18 <samccann> sold to the little lady w/ the turkey cooking!
16:06:27 * acozine brings down the gavle
16:06:31 <acozine> er, gavel
16:06:36 <samccann> NOT ON THE TURKEY!!!!
16:06:47 <acozine> heh
16:06:51 <acozine> thanks abadger1999 aminvakil baptistemm dmsimard felixfontein gundalow samccann
16:06:58 <acozine> to those in the US, Happy Thanksgiving
16:06:58 <dmsimard> \o/
16:07:04 <acozine> #endmeeting