14:00:10 #startmeeting 2020-04-02 - Documentation Interest Group Meeting 14:00:10 Meeting started Thu Apr 2 14:00:10 2020 US/Eastern. The chair is dluch. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:10 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:10 The meeting name has been set to '2020_04_02___documentation_interest_group_meeting' 14:00:27 #topic Agenda 14:01:12 #info The agenda can be found here: https://wiki.evergreen-ils.org/doku.php?id=evergreen-docs:dig_meetings:20200402-agenda 14:01:12 Welcome everyone! Today's meeting will be some discussion and updates but hopefully we'll still have lots of time for collaboration and working on documentation. 14:01:24 #topic Introductions 14:01:37 Please paste "#info is , " to identify who you are and what organization, if any, you represent. 14:01:42 #info alynn26 is Lynn Floyd, Evergreen Indiana 14:01:50 #info dluch is Debbie Luchenbill, MOBIUS 14:02:31 #info jihpringle is Jennifer Pringle, BC Libraries Cooperative (Sitka) 14:02:42 #info abneiman is Andrea Buntz Neiman, Equinox 14:03:55 If you're just joining us for the DIG meeting, Please paste "#info is , " to identify who you are and what organization, if any, you represent. 14:04:39 #info Bmagic is Blake GH, MOBIUS 14:05:18 Thank you all for coming! If you join in later, feel free to introduce yourself when you arrive. 14:05:27 #info adurrence is April Durrence, NC Cardinal 14:05:50 #topic Helpful Information: Documentation contributions and collaboration 14:05:53 #info You can find the Documentation Needs List at https://wiki.evergreen-ils.org/doku.php?id=evergreen-docs:documentation_needs 14:06:05 #info DIG Roles can be found at https://wiki.evergreen-ils.org/doku.php?id=evergreen-docs:digparticipants 14:06:17 We are going to do some quick business items, but let's try to get through them fairly quickly... 14:06:31 (Also, dang, this is a lot harder with only one screen, lol!) 14:06:45 #topic Business 14:06:59 #info Update on Documentation server move 14:07:18 gmcharlt: (or anyone) This is done, yes? 14:08:08 We had a meeting a couple weeks ago (?) right before everything went wonky, and several of us got logins 14:08:48 I was hoping to attend that meeting, but I had another one at the same time. 14:09:17 alynn26: \Yes, I remember now. gmcharlt was also going to get you access 14:09:22 Server is up and running. Bare bones right now 14:09:38 eg-docs.georgialibraries.org/prod/ 14:09:44 Okay, thanks. 14:10:05 what can we do to help flesh it out. 14:11:38 The antora stuff is on there right now - I'm not sure about any other pieces that need to be hosted there (if any). I think there are some. Perhaps the SQL->HTML generator? 14:11:44 It looks really good. 14:12:04 Yes, it does! 14:12:15 All of the legacy documentation will need to be copied over. Keeping the links the same 14:12:48 Yeah, that's what I was remembering, too...we'll need to copy stuff over 14:13:11 I'm going to move on, and we can talk about it in more depth next meeting or after business, maybe, in collaboration time. 14:13:20 #info Quick update on Antora progress 14:13:33 remingtron and bmagic: Where are we with Antora nav progress? 14:14:18 I made some tweaks to it during the server setup. I think* it's all been addressed 14:14:33 Awesome! 14:14:37 bmagic++ 14:14:46 Bmagic++ 14:14:53 Remingtron++ 14:15:00 So, are you still wanting us to go in and look for more things to tweak? 14:15:05 remingtron++ 14:15:09 need click-through's and testing though 14:15:25 I did notice the index was not working. 14:16:01 Haha, okay, cool. We have that as an action item from last meeting...everyone go through and test things, so keep doing that! 14:16:17 I had a thought the other day> If we merge this branch into master, it will delete the current docs stuff (which is fine as long as all of the latest stuff has been forwarded to the antora branch as well) - I was trying to think of a way we could query our git repo to see if there are any non-merged branches that touch /docs/* files? 14:16:36 Bmagic: very good thought 14:16:57 (n.b. I have no idea how to do that, though) 14:17:26 probably some clever bash tricks for it. Haven't looked into it further than just thinking about it. 14:17:53 So, bmagic: you good doing some more exploring/thinking about it? 14:18:04 yes 14:18:12 Sweet 14:18:21 Want an action item for it? 14:18:23 Bmagic++ exploring++ 14:18:27 sure 14:19:22 #action bmagic will think about and explore how to query our git repo to see if there are any non-merged branches that touch /doc/* files 14:19:46 bmagic++ 14:19:55 #info Quick update on DIG Bug Squashing Week Activity 14:20:09 I know here it was totally insane during Bug Squashing Week, so I did nothing. I assume the same for you all. Did anyone get docs worked on at all? 14:20:26 With the 3.5 release getting pushed back a bit, we have a little more time, so that's good. 14:20:29 I had plans for Bug Squashing week, then the Governer sent us all home. 14:21:23 I've not even looked at them recently. To many other issues getting staff connected remotely. 14:21:34 Yep, me, too (well, not the governor, but our city and county sent us home, lol) 14:21:50 I had good intentions for BSW (even told Bmagic I'd look at docs stuff) but then everything happened 14:22:29 Yep. I think we're all in the same boat. Let's not stress too much about it atm, but try working on docs as we can squeeze it in. 14:22:31 what happend? 14:22:37 (lol) 14:22:52 eyeroll 14:22:59 ha! 14:23:04 Bmagic, have you seen the news? :) 14:23:13 lol 14:23:20 Okay, moving on, lol 14:23:23 #info Discussion: Ways to promote DIG info and Docs-related sessions without in-person Conference 14:23:40 We had several DIG- and docs-related sessions for the conference in Atlanta, which is now cancelled, of course. 14:24:01 As you hopefully saw earlier, Outreach Committee is working on organizing a virtual conference 14:24:06 I am planning on doing the AsciiDoc Session if there is an Virtual conference. 14:24:13 or when 14:24:19 alynn26++ 14:24:25 virtual conference ++ 14:24:40 definitely 14:24:45 let's say "when" :) 14:24:50 * abneiman crosses fingers 14:24:59 Also, I can do the presentation anytime for anyone. 14:25:02 and abneiman++ for spearheading it! 14:25:19 abneiman++ 14:25:56 I forgot to change up the agenda after we had the outreach meeting yesterday, so I guess really discussion should be on whether other folks are willing/able to do their presentation for virtual conference 14:26:36 I think Benjamin and I will be glad to do ours - depending on timeframe and barring conflicts 14:27:29 Excellent! adurrence++ benjamin++ (I don't know what his nick is, lol) 14:27:46 (me neither) 14:27:57 lol 14:28:02 all planned presenters should've received an email from me this morning, asking if they are willing to retool their presentation(s) for a virtual conference - so if you are a presenter please let me know if you want to partake (abneiman@equinoxinitiative.org) 14:28:19 maybe BAMkubasa 14:28:35 yep, we haven't had a chance to chat about it yet 14:28:37 and if interest groups want virtual space to meet, that's cool too, but similarly let me know 14:28:38 sound right 14:28:53 Thanks, abneiman! So, we don't need to hash it out here, jusst let abneiman know! 14:29:41 I was thinking that since IGs have dedicated meeting times already set up, we probably didn't need one...but there's something to be said for seeing each other... 14:30:10 (also, my s key is only working half the time, lol. Weird!) 14:30:24 yeah, the groups that meet regularly probably don't need to do something special, but groups that only meet at the conference might want to get something together. 14:30:34 True 14:31:03 I'm going to move on to the next discussion thing, then we should still have good time for collaboration 14:31:05 #info May DIG meeting 14:31:24 The plan we decided on at the last meeting was to hold this April meeting, then have the in-person hackfest and DIG meeting at conference, and no May meeting. Since there's no conference, I think it would be fine to have the May meeting. But I'm also fine if everyone would like to not do so. Thoughts? 14:32:42 I say lets have the May meeting. Hopefully, we will have time to do some docuementation between now and then. 14:32:54 +1 to May meeting 14:33:30 Great, thanks! May meeting it is! 14:33:45 #info We will catch up on other action items at business at the next meeting 14:33:57 #info Anything else pressing? 14:34:52 Hearing nothing, we will move on to 14:34:54 #topic Collaboration time 14:35:11 What is everyone planning to work on today? Please let us know here, and feel free to talk and work with each other. If you'd like extra accountability, I can make an action item to show up in the minutes, but it's not necessary. 14:36:29 The landing page on the antora docs still has a untitled 14:36:55 Untitled :: Evergreen Documentation 14:39:54 Like, should it just be Evergreen Documentation with the Untitled removed? 14:41:13 Also, everyone, in my haste hopping back and forth between my meeting outline and here, I forgot to just ask at the beginning...How is everyone doing right now? 14:42:50 dluch: this tweet really summed it up... https://twitter.com/MeredithIreland/status/1245359302300360712 14:43:37 :) 14:43:47 yup :) 14:44:02 LOL, that's perfect 14:44:10 abneiman++ 14:45:13 https://twitter.com/UnHelpDesk/status/1239915255054155776/photo/1 14:45:50 alynn26++ 14:45:53 also perfect 14:46:07 (though I was the vpn person earlier this week, lol) 14:46:21 Bmagic: question - (this may have been previously answered but I can't recall) - will past versions of docs be moved over to Antora? If not, there should be a) an easy to find link to past versions and b) an indication of what versions you're looking at in antora 14:46:36 alynn26++ 14:47:10 so maybe that should be in the title, if possible: "3.4 :: Evergreen Documentation" 14:47:19 The other issue is people crashing our Reporter, Wanting ridiculous reports. 14:47:36 Good point, abneiman! 14:47:52 I'm thinking title should be Evergreen Documentation :: 3.4. 14:48:04 alynn26: lol 14:48:27 Hmm. Yes, alynn26, that does seem more logical 14:48:50 alynn26: so, since it shows in the browser tab, I was thinking that having the "narrower term" (so to speak) made sense first. But not a hill to die on. 14:49:31 I see your point their also. 14:49:36 Ohhh, I didn't think about that 14:49:42 Either way would work for me. 14:51:15 yep 14:59:13 We are just about at time. Thanks for all the great work, everyone! Feel free to keep going after the meeting! 14:59:25 The next meeting will be May 7. Same time, same place. Business meeting first then collaboration time (if there's time). 14:59:46 Please continue using the email list and/or Launchpad for questions and other things that come up in between meetings. 15:00:04 Thanks for coming! 15:00:08 #endmeeting