Time |
Nick |
Message |
00:21 |
|
sandbergja joined #evergreen |
07:01 |
|
agoben joined #evergreen |
07:09 |
|
rjackson_isl joined #evergreen |
07:52 |
|
Dyrcona joined #evergreen |
08:15 |
|
rlefaive joined #evergreen |
08:27 |
|
collum joined #evergreen |
09:14 |
|
aabbee joined #evergreen |
09:21 |
|
tlittle joined #evergreen |
09:24 |
|
mmorgan joined #evergreen |
09:32 |
|
yboston joined #evergreen |
09:38 |
|
sandbergja joined #evergreen |
10:40 |
|
alynn26 joined #evergreen |
10:42 |
|
alynn26 joined #evergreen |
11:01 |
pinesol |
News from qatests: Failed Installing Angular web client <http://testing.evergreen-ils.org/~live/test.29.html#2019-11-07T11:00:51,274639219-0500 -0> |
11:27 |
jeff |
Anyone have a favorite thermal printer that prints on sticky paper? Our go-to was the Epson TM-T88 ReStick series, but that and the Star models we've looked at to replace it are both becoming difficult to find. I think the Epson one is being discontinued, unclear if the other is just a temporary shortage. |
11:31 |
jeff |
MAXStick paper seems to be similar to the ReStick. |
12:04 |
|
jihpringle joined #evergreen |
12:09 |
|
tlittle joined #evergreen |
12:25 |
|
Christineb joined #evergreen |
12:27 |
|
collum joined #evergreen |
12:37 |
|
tlittle joined #evergreen |
12:39 |
|
khuckins joined #evergreen |
12:40 |
Bmagic |
After upgrading a test machine from 3.1 to 3.3 - it was noticed that the subject browse results are different and in a different order. Is that expected? (after upgrade, reingest was performed and completed) |
12:40 |
|
jwoodard joined #evergreen |
12:49 |
* csharp |
stopped working on testing hopeless holds because he just couldn't do it anymore |
12:49 |
stephengwills |
holding off on that, eh? |
12:50 |
|
yboston joined #evergreen |
12:52 |
csharp |
stephengwills: just trying out a joke I thought of when the word "hopeless" was in every commit message :-) |
12:53 |
jeffdavis |
I think both of your jokes were pretty on target |
12:53 |
stephengwills |
now I have CSNY stuck in my head in the stupidest way. |
12:53 |
csharp |
:-D |
12:54 |
csharp |
stephengwills: I went the same direction - Neil Young: hopeless hopeless ho-opeless |
12:54 |
stephengwills |
csharp++ |
12:55 |
csharp |
Bmagic: I don't recall anyone mentioning browse issues after our 3.0-3.2 upgrade, so it might be a 3.3 issue? |
12:57 |
Dyrcona |
csharp++ |
12:57 |
Dyrcona |
Bmagic: I have the same thought as csharp. Could be a 3.3 thing or quantum software effects. |
13:11 |
Bmagic |
I thought there were some fundamental changes to search between 3.1 and 3.3? |
13:14 |
Dyrcona |
We went from 3.0 to 3.2 last Spring and there were some changes there, but no one has really complained about browse changing. |
13:15 |
Bmagic |
good to know - I'll dig more |
13:15 |
Dyrcona |
Have you a) checked the release notes and b) checked the git log? |
13:15 |
Bmagic |
I checked the notes |
13:15 |
Dyrcona |
:) |
13:16 |
Dyrcona |
OK. I was about to look at the release notes again out of curiosity. |
13:17 |
Dyrcona |
Actually, that's not a bad idea: looking at the release notes. I haven't really looked at the 3.3 and 3.4 notes, yet. |
13:18 |
Dyrcona |
Apparently, I have looked at the 3.3 release notes, since a couple of the section links show up as "visited" in my browser. :) |
13:20 |
Dyrcona |
Nothing about browse in there, but steps about update to Pg 9.6 or later that i should do on my training and test database servers. Bmagic++ # for serendipity |
13:21 |
berick |
Bmagic: there was some browse code refactoring in 3.3 |
13:22 |
berick |
intention was to avoid any changes, but some may have snuk in |
13:22 |
berick |
@band add Snuk |
13:22 |
pinesol |
berick: Band 'Snuk' added to list |
13:22 |
csharp |
@blame [band] for [praise] |
13:22 |
pinesol |
csharp: I come to bury Dyrcona csharp, not to praise them. for (praise [<channel>] [<id>] <who|what> [for <reason>]) -- Praises <who|what> (for <reason>, if given). If <id> is given, uses that specific praise. <channel> is only necessary if the message isn't sent in the channel itself. |
13:23 |
csharp |
@blame [band] for [praise [quote random]] |
13:23 |
* pinesol |
Fit Fetch forgot to give the gerbils their chocolate-frosted sugar bombs for The Quote #136: "< Dyrcona> Come! Witness the heat death of the universe." (added by csharp at 09:51 AM, January 06, 2016) abides. |
13:23 |
Dyrcona |
Talk about quantum software effects... |
13:26 |
berick |
@ana quantum software effects |
13:26 |
pinesol |
berick: New fame cutoff squatters |
13:27 |
Dyrcona |
@band add New Fame Cutoff Squatters |
13:27 |
pinesol |
Dyrcona: Band 'New Fame Cutoff Squatters' added to list |
13:28 |
berick |
that is a good one |
13:28 |
Dyrcona |
Hmm... This seems odd: ERROR: index "actor_usr_first_given_name_unaccent_idx" does not exist. If I look in another database before running the DROP INDEX, the index is there. |
13:30 |
csharp |
@band add [ana hopeless holds] |
13:30 |
pinesol |
csharp: Band 'Slosh so helped' added to list |
13:34 |
Dyrcona |
Ah ha. It works if I schema qualify the index with "actor." |
13:38 |
Dyrcona |
@praise [band] for their first album, Schema Qualified. |
13:38 |
* pinesol |
In days of old, it was prophesied that a hero would come and restore karmic balance to #evergreen. Fly Taser is that hero. for their first album, Schema Qualified. |
13:44 |
|
sandbergja joined #evergreen |
13:49 |
dluch |
Reminder that DIG will be meeting here in 12 minutes |
13:49 |
Bmagic |
dluch++ |
13:50 |
remingtron |
dluch: the Antora Team is ready! |
13:51 |
dluch |
remingtron: awesome! |
13:52 |
Bmagic |
Dyrcona: what does it mean when there are more than one browse entry for the same set of bib records? Search results are doubled but they have unique browse_entry ID's |
13:54 |
Dyrcona |
Bmagic: I'm not really the search expert, but you could try a browse reingest with pingest.pl. |
13:54 |
Bmagic |
that's been done |
13:55 |
Bmagic |
I think there is some trouble in the custom browse field configuration somewhere |
13:56 |
sandbergja |
Bmagic: there's bug 1772981, which results in a bunch of superfluous author browse entries |
13:56 |
pinesol |
Launchpad bug 1772981 in Evergreen "Bibliographic browse headings show relator information" [Medium,Confirmed] https://launchpad.net/bugs/1772981 |
13:57 |
csharp |
@band add "Superfluous Authors" |
13:57 |
pinesol |
csharp: Band 'Superfluous Authors' added to list |
13:57 |
Bmagic |
sandbergja++ |
13:57 |
sandbergja |
Might not be what you're looking for, but I found dbwells' troubleshooting advice really helpful on that bug |
13:58 |
|
yboston joined #evergreen |
13:59 |
Dyrcona |
sandbergja++ |
14:00 |
dluch |
#startmeeting 2019-11-07 - Documentation Interest Group Meeting |
14:00 |
pinesol |
Meeting started Thu Nov 7 14:00:58 2019 US/Eastern. The chair is dluch. Information about MeetBot at http://wiki.debian.org/MeetBot. |
14:00 |
pinesol |
Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. |
14:00 |
|
Topic for #evergreen is now (Meeting topic: 2019-11-07 - Documentation Interest Group Meeting) |
14:00 |
pinesol |
The meeting name has been set to '2019_11_07___documentation_interest_group_meeting' |
14:01 |
dluch |
#topic Agenda |
14:01 |
|
Topic for #evergreen is now Agenda (Meeting topic: 2019-11-07 - Documentation Interest Group Meeting) |
14:01 |
dluch |
#info The agenda can be found here: https://wiki.evergreen-ils.org/doku.php?id=evergreen-docs:dig_meetings:20191107-agenda |
14:01 |
dluch |
Welcome everyone! Today's meeting will be business, followed by collaboration and working on documentation. |
14:01 |
dluch |
#topic Introductions |
14:01 |
|
Topic for #evergreen is now Introductions (Meeting topic: 2019-11-07 - Documentation Interest Group Meeting) |
14:01 |
dluch |
Please paste "#info <username> is <name>, <affiliation>" to identify who you are and what organization, if any, you represent. |
14:01 |
dluch |
#info dluch is Debbie Luchenbill, MOBIUS |
14:02 |
remingtron |
#info remingtron is Remington Steed, Hekman Library (Calvin University) |
14:02 |
Bmagic |
#info Bmagic is Blake GH, MOBIUS |
14:02 |
jihpringle |
#info jihpringle is Jennifer Pringle, BC Libraries Cooperative (Sitka) |
14:02 |
alynn26 |
#Info alynn26 is Lynn Floyd (Evergreen Indiana) |
14:02 |
abneiman |
#info abneiman is Andrea Buntz Neiman, Equinox |
14:02 |
sandbergja |
#info sandbergja is Jane Sandberg, Linn-Benton Community College |
14:03 |
jweston |
#info jweston is Jennifer Weston, Equinox |
14:03 |
|
adurrence joined #evergreen |
14:04 |
dluch |
Thank you all for coming! If you come in later, feel free to introduce yourself when you arrive. |
14:04 |
dluch |
Also, before we get started, I have a doctor's appointment I should have canceled but forgot to, so need to leave on the half hour. If we're still going then (which I assume we will be), will someone volunteer to become the meeting "runner" to finish and close out the meeting? Please? (I can email you my "script" outline for the meeting, if you want.) |
14:05 |
abneiman |
dluch: I can do that - script would be appreciated tho :) |
14:05 |
dluch |
abneiman: Thank you! I'll get that to you in just a minute! |
14:05 |
dluch |
abneiman++ |
14:05 |
dluch |
#topic Helpful Information: Documentation contributions and collaboration |
14:05 |
|
Topic for #evergreen is now Helpful Information: Documentation contributions and collaboration (Meeting topic: 2019-11-07 - Documentation Interest Group Meeting) |
14:06 |
dluch |
#info You can find the Documentation Needs List at https://wiki.evergreen-ils.org/doku.php?id=evergreen-docs:documentation_needs |
14:06 |
dluch |
#info DIG Roles can be found at https://wiki.evergreen-ils.org/doku.php?id=evergreen-docs:digparticipants |
14:06 |
dluch |
#topic Old and Ongoing Business |
14:06 |
|
Topic for #evergreen is now Old and Ongoing Business (Meeting topic: 2019-11-07 - Documentation Interest Group Meeting) |
14:06 |
dluch |
#info Previous Action Items |
14:06 |
dluch |
How are we doing on these? I'll take them in order... |
14:06 |
dluch |
#1, adding ideas for simple topics in the Quick Starts section of the wiki (https://wiki.evergreen-ils.org/doku.php?id=evergreen-docs:documentation_needs, scroll past the Easy Tasks section). I see some there. Anyone added anything recently? Do we need to keep this as an action item? |
14:07 |
stephengwills |
#info stephengwills Maine Balsam Libraries |
14:07 |
sandbergja |
I think we don't need to keep it as an action item |
14:08 |
dluch |
Cool. I agree, but didn't want to arbitrarily make that call. :-) |
14:08 |
dluch |
#2, sandbergja: video for proof of concept there? (I haven't looked recently.) |
14:08 |
sandbergja |
haha nope |
14:08 |
alynn26 |
I do too, getting back in the swing of things since the Job change, |
14:08 |
sandbergja |
can we push that until next time please? |
14:08 |
dluch |
sandbergja: Yep! |
14:09 |
dluch |
alynn26: what's your new job? |
14:09 |
alynn26 |
Jason Boyers old job. |
14:09 |
alynn26 |
at the Indiana State Library |
14:09 |
dluch |
#action sandbergja will make a proof of concept for the Quick Starts section |
14:09 |
dluch |
Awesome, congratulations! |
14:09 |
alynn26 |
Thanks |
14:10 |
dluch |
#3, jweston or abneiman: Did CWG talk about MARC Edit, right-clicking, and accessibility? I didn't remember that coming up at the October meeting. |
14:10 |
jweston |
We talked about Angular Staff Catalog in October and lots of launchpad bugs -- now combined on cwg wiki so I would say it is covered |
14:11 |
dluch |
Okay, so remove the action item? |
14:11 |
jeff |
aside: I *think* I just added abneiman as chair of this meeting, so that the dluch -> abneiman handoff should be uneventful. |
14:11 |
abneiman |
dluch: we talked about it in the August meeting |
14:11 |
abneiman |
jeff++ |
14:11 |
dluch |
jeff: Thanks! |
14:11 |
dluch |
jeff++ |
14:11 |
jweston |
yes, I think it is fine to remove the action item - thanks |
14:11 |
dluch |
jweston++ abneiman++ |
14:11 |
abneiman |
link: https://docs.google.com/document/d/1DrKYz3N3qDwcGSTWIQ-fV0EVonptphqp2PMQh1QUF0k/edit?usp=sharing |
14:12 |
dluch |
Thanks! |
14:12 |
dluch |
#4, sandbergja: Did you explore how to and then request abneiman be given docs committing privileges? Do I remember correctly that actually getting done before the end of the September DIG meeting? |
14:12 |
sandbergja |
Yep, abneiman has all sorts of powers now :-D |
14:12 |
jweston |
abneiman: ++ thanks for finding it on the cwg notes :) |
14:12 |
dluch |
Awesome, thanks! |
14:12 |
dluch |
sandbergja++ |
14:12 |
dluch |
#5, gmcharlt and/or rsoulliere: How's work coming on moving the docs server? |
14:13 |
abneiman |
jweston: np, I knew we HAD discussed it but I couldn't recall when :) |
14:13 |
abneiman |
gmcharlt is not available right now but I can follow up with him |
14:13 |
dluch |
Okay, thanks. |
14:13 |
dluch |
#6, abneiman: Did you have a chance to look into/plan a community crash course on ascii? |
14:13 |
dluch |
(For folks who weren't there, this idea came up in the discussion at the (very brief) October DIG meeting.) |
14:14 |
abneiman |
not beyond thinking about it, and getting some feedback to the effect of "Yes, great idea!" LOL |
14:14 |
dluch |
:-) |
14:14 |
jweston |
+1 still a great idea! |
14:14 |
alynn26 |
I am thinking of doing my full asciidoc presentation at the Conference. |
14:14 |
dluch |
Yep, still +1 to that! |
14:14 |
abneiman |
but I do still think it would be valuable, and my November is shaping up to be way less wild than my October so it can stay on my plate |
14:15 |
abneiman |
alynn26: that would be great! |
14:15 |
alynn26 |
Not the Asciidoc in 5 minutes or less |
14:15 |
dluch |
#action abneiman will look into/plan a community crash course on ascii |
14:15 |
remingtron |
alynn26++ |
14:15 |
dluch |
alynn26: fantastic! |
14:15 |
dluch |
alynn26++ |
14:15 |
dluch |
Any other old or ongoing business to discuss? |
14:15 |
abneiman |
yeah, the "crash course" I was thinking about was mostly "asciidoc in 15 minutes or less" and I will definitely refer people to alynn26's upcoming presentation |
14:16 |
dluch |
abneiman++ |
14:16 |
alynn26 |
abneiman: I can share my presentation with you, if you want |
14:17 |
abneiman |
alynn26++ thanks! that would be great |
14:17 |
dluch |
Okay, moving on.. |
14:17 |
dluch |
#topic New Business |
14:17 |
|
Topic for #evergreen is now New Business (Meeting topic: 2019-11-07 - Documentation Interest Group Meeting) |
14:18 |
dluch |
#info Switching to Antora |
14:18 |
dluch |
bmagic and remingtron: take it away! |
14:18 |
alynn26 |
I really like Antora |
14:18 |
Bmagic |
:) |
14:18 |
remingtron |
we hacked away at the hackaway |
14:18 |
remingtron |
and Bmagic has a live demo to show you what we accomplished! |
14:18 |
Bmagic |
#info branch is here: https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/collab/blake/LP1848524_antora_ize_docs |
14:19 |
Bmagic |
#info the temporary site you can browse RIGHT NOW: http://antora.mobiusconsortium.org/prod/ |
14:19 |
Bmagic |
This is as far as we got |
14:19 |
remingtron |
summary: I think we've answered all the hard questions, but there's plenty of cleanup to do |
14:20 |
Bmagic |
The navigation needs to be fleshed out. I went ahead and made the theme "Evergreen-ized" |
14:20 |
Bmagic |
I added links in the dropdown menus on the top right |
14:20 |
remingtron |
Bmagic also got the search working, Bmagic++ |
14:20 |
Bmagic |
Right now, since the navigation isn't completed, some pages are only accessible through search |
14:21 |
alynn26 |
bmagic++ |
14:21 |
sandbergja |
Bmagic++ |
14:21 |
sandbergja |
remingtron++ |
14:21 |
alynn26 |
Remingtron++ |
14:21 |
Bmagic |
aww shucks |
14:21 |
Bmagic |
remingtron++ |
14:21 |
jweston |
bmagic++ |
14:21 |
jweston |
remingtron++ |
14:21 |
remingtron |
thanks everybody! |
14:22 |
jihpringle |
bmagic++ |
14:22 |
jihpringle |
remingtron++ |
14:22 |
jeff |
is it expected that there is no search results page, just an autocomplete-style pop-up of matching titles? |
14:22 |
Bmagic |
I got "hooked" on working on it and worked through the airport and in the car up to 2am |
14:22 |
Bmagic |
jeff: yep, out of the box |
14:22 |
abneiman |
I know this is a WIP but will the pages eventually be more "broken up" by lower-level section? |
14:22 |
jeff |
Bmagic++ |
14:22 |
Bmagic |
info: using antora "lunr" https://github.com/Mogztter/antora-lunr |
14:22 |
dluch |
bmagic++ |
14:22 |
dluch |
remingtron++ |
14:22 |
abneiman |
see http://antora.mobiusconsortium.org/prod/docs/latest/admin/acquisitions_admin.html vs http://docs.evergreen-ils.org/reorg/3.2/staff_client_admin/_acquisitions_administration.html#_acquisitions_settings |
14:23 |
alynn26 |
Can we share this with others to get additional opinions? |
14:23 |
Bmagic |
I like to do that - compare two pages. Though it's not always apples to apples because our current production documents slice and dice stuff |
14:23 |
alynn26 |
That page I think is missing the TOC |
14:24 |
Bmagic |
alynn26: I think we need a more "permanent" server to stage this stuff - the new server perhaps? |
14:24 |
remingtron |
yeah, once gmcharlt has the new docs server ready, we'll setup a more public demo of Antora |
14:24 |
abneiman |
right - what I'm asking is that, in Antora, the Acq Admin is one big long page - there's value to some slicing and dicing via lower level section headings, and I want to know if that's in the plan |
14:24 |
dluch |
abneiman: I think we'd be able to do that if we wanted to? bmagic/remingtron? |
14:25 |
dluch |
Or is it just all scrolling? |
14:25 |
Bmagic |
we spoke briefly about that at the Hack-a-way - we thought the scrolling was better |
14:25 |
remingtron |
we can break pages into smaller pages, but that would take some manual work, case by case |
14:25 |
Bmagic |
for orgainization/search reasons too |
14:26 |
jihpringle |
it's often helpful to be able to send links to specific section |
14:26 |
abneiman |
ok. obviously I forgot that from hackaway :) I think in some cases, breaking up reallllly long pages (like Acq Admin) is more user friendly for several reasons |
14:26 |
Bmagic |
yep, that page is seriously long |
14:26 |
dluch |
I think we'd need some sort of menu, though, linking to sub-sections, otherwise it'll be a pain scrolling through |
14:26 |
dluch |
Yes |
14:26 |
remingtron |
jihpringle: Antora gives you a section link when you hover a section title |
14:26 |
sandbergja |
One question: how close are we keeping to the original antora default UI? Is there an easy way to bring in improvements made to the default UI into our customized UI? I ask because there are a few accessibility issues with the original UI, and want to know if an upstream fix would eventually trickle down into the layout you made, Bmagic. |
14:26 |
Bmagic |
The TOC at the top would help that page with a one-liner |
14:27 |
abneiman |
right. and big +1 to jihpringle's comment about linking to a specific section - whether that's by anchor links or splitting pages, that's an important feature to preseve |
14:27 |
remingtron |
yeah, that's one suggestion: add a Table of Contents to top of each page in Antora |
14:27 |
jweston |
+1 to TOC |
14:28 |
Bmagic |
yep, this line ":toc:" added to the top of each page will go a long way |
14:28 |
dluch |
cool |
14:28 |
abneiman |
+1 to TOC definitely |
14:28 |
abneiman |
thanks remingtron++ Bmagic++ |
14:28 |
dluch |
#chair abneiman |
14:28 |
pinesol |
Current chairs: abneiman dluch |
14:28 |
dluch |
later, all! |
14:28 |
remingtron |
sandbergja: good question. Bmagic, thoughts on how we'd handle UI upgrades? |
14:28 |
Bmagic |
dluch++ |
14:28 |
jweston |
dluch++ |
14:28 |
jihpringle |
dluch++ |
14:28 |
abneiman |
dluch++ |
14:28 |
remingtron |
dluch++ |
14:29 |
Bmagic |
UI upgrades - git is our friend there |
14:29 |
Bmagic |
right now, because we didn't want to "nest" a git repo within a git repo. We hvae the files simply "copied" into the Evergreen repo |
14:30 |
Bmagic |
we could keep it outside of the Evergreen repo for ease of merging upstream |
14:31 |
sandbergja |
Bmagic: keeping the layout in its own repo might be good! |
14:32 |
Bmagic |
I think if we do that (correct me) we can have it "track" the github repo? |
14:33 |
Bmagic |
You git experts in the room - there is a way to nest the repo within Evergreen, thereby avoiding adding another root repo? gmcharlt and I spoke briefly and he favored not doing that |
14:34 |
Bmagic |
This project actually uses two upstream repos: https://github.com/Mogztter/antora-lunr and https://gitlab.com/antora/antora-ui-default |
14:35 |
abneiman |
as noted gmcharlt is unavailable right now, but do one of our other core committers have thoughts about bmagic's proposal? |
14:35 |
sandbergja |
I know you can set up git submodules -- https://git-scm.com/book/en/v2/Git-Tools-Submodules -- but I'd defer to others who have worked with those more |
14:36 |
jeff |
I'm in agreement with gmcharlt about not adding a git submodule. It looks like based on the Antora docs the UI code is intended to be a distinct git repo. |
14:36 |
Dyrcona |
Git submodules can be interesting. |
14:36 |
Dyrcona |
Not necessarily in a good way. |
14:36 |
Bmagic |
I nested the repos at first. And it caused gitolite to have a heart attack |
14:36 |
csharp |
I think the objection was that submodules get really complicated really fast and git is already a hurdle for most |
14:36 |
jeff |
(based on a quick skim of https://docs.antora.org/antora/2.2/features/#interchangeable-ui just a few minutes ago) |
14:36 |
Bmagic |
It was clear that we needed to introduce some code into the repo to make it play nice with the repo above it |
14:36 |
jeff |
"Antora interfaces with a site UI that is stored and managed as a separate project." |
14:37 |
sandbergja |
I think it's okay to have part of the build process be "run git clone [URL of ui repo]" |
14:37 |
sandbergja |
as long as that build process is really well documented |
14:37 |
csharp |
I think a separately cloned git repo with instructions for integration would be best (there were also concerns about licensing conflicts between antora [Mozilla Public License] and EG [GNU GPL v2]) |
14:38 |
jeff |
I believe that's what Antora expects to do by default -- there's no need to add on something special to make that happen. |
14:38 |
Bmagic |
jeff: sandbergja: yep! - I think that's the way forward |
14:38 |
csharp |
+1 |
14:38 |
Dyrcona |
Well, cmake is really good at managing dependencies like that without resorting to git submodules. |
14:39 |
Bmagic |
and the lunr repo gets put into the ui repo.... it's like Inception |
14:39 |
sandbergja |
I'm curious about how Windows users would contribute to antora-ized docs |
14:39 |
Bmagic |
I wouldn't be surprised if the lunr repo get's wrapped into the default UI before too long anyway |
14:39 |
* csharp |
plays the Inception soundtrack whenever Bmagic speaks |
14:40 |
sandbergja |
Building antora seems like a lot to ask of casual documentation contributors to test their changes |
14:40 |
Bmagic |
sandbergja: contribution hurdles remain the same |
14:40 |
sandbergja |
(not that our current stack isn't also a lot to ask) |
14:40 |
Bmagic |
I've been recommending folks use ascidocfx https://asciidocfx.com/ |
14:41 |
Bmagic |
1. clone the Evergreen repo. 2. Open Asciidocfx. 3. Browse the file system to the document you want to edit. 4. Save the file |
14:42 |
sandbergja |
On a related note: in my perfect world, when somebody throws a documentation pull request at the github repo, antora runs on their branch, and generates a preview view of what the documentation looks like with their changes |
14:42 |
Bmagic |
If anything, the orgainization that Antora requires might make it *easier* to contribute |
14:43 |
jeff |
setting up CI for docs would have benefits beyond just helping Windows users contribute |
14:43 |
sandbergja |
Angular does that with docs pull requests, and I was really impressed: https://github.com/angular/angular/pull/31630#issuecomment-512934983 |
14:43 |
jeff |
There are two options for local preview, as long as you can run antora on your Windows PC: static pages, or run the local server. |
14:44 |
Dyrcona |
CI for docs would be a nice start in the general direction of CI. |
14:45 |
abneiman |
Bmagic: remingtron: what do you see as next steps here? |
14:45 |
abneiman |
and thank you Dyrcona++ csharp++ jeff++ sandbergja++ for committer perspective |
14:47 |
Bmagic |
abneiman: I think we need the staging server. Keep hammering out the navigation. Edit all of the headings (with script). Add the TOC. Elicit feedback, Review, and finally publish |
14:47 |
Bmagic |
Once it's in master, it will propigate down the version trees, and we get the full advantage of "version" of the docs (shown on the UI in the bottom left corner) |
14:48 |
Bmagic |
Starting with 3.5 is a reasonable goal I would say |
14:48 |
abneiman |
And DIG members present, are we +1 to moving forward here? (I don't think we really need a formal vote but I can call one if desired) |
14:49 |
jweston |
+1 to moving forward |
14:49 |
jihpringle |
+1 from me |
14:49 |
stephengwills |
+1 Marchon |
14:50 |
sandbergja |
+1 from me! |
14:51 |
abneiman |
ok - hearing no objections to the general concept, let's toss some action items in |
14:51 |
abneiman |
#action abneiman will prod gmcharlt about the test server |
14:51 |
abneiman |
Bmagic and remingtron, are you working on the nav? are there others who want to help here? |
14:52 |
Bmagic |
I believe there are 70+ links/lines needed |
14:52 |
Bmagic |
we could divide and conquer. Anyone who wants to help... can! |
14:53 |
sandbergja |
Bmagic: would they just need access to the working repo to be able to help with that task? |
14:53 |
Bmagic |
make that 192 lines needed (roughly) |
14:54 |
Bmagic |
sandbergja: that's correct - which I don't think there is an issue, it's out there ready for cloning/merging/patching/pushing |
14:55 |
Bmagic |
192 from `ll modules/*/pages/*|wc` |
14:55 |
sandbergja |
Is now the right time to set up another git repo for the ui/layouts? |
14:55 |
Bmagic |
yep, that'd be great |
14:56 |
abneiman |
sandbergja: will you set that repo up? |
14:56 |
sandbergja |
I can volunteer to work with gmcharlt and Dyrcona on that |
14:56 |
abneiman |
heh |
14:56 |
Bmagic |
probably just the one for the UI - not sure about lunr - we don't make changes to that (yet) |
14:56 |
sandbergja |
that sounds good! |
14:56 |
abneiman |
#action sandbergja gmcharlt and Dyrcona will work on setting up a git repo for ui (and maybe layouts) |
14:57 |
abneiman |
#action bmagic, remingtron, and players to be named later will work on the nav, of which there are approx 192 lines needed |
14:57 |
abneiman |
anything else for the near term? we're coming up on the hour |
14:57 |
sandbergja |
Bmagic: will your demo version be up for a while -- so I can gather some feedback from my colleagues locally? |
14:58 |
Bmagic |
yeah but not for long! It's not a machine that should be online |
14:58 |
sandbergja |
okay! |
14:58 |
Bmagic |
how's end of day today? |
14:58 |
sandbergja |
Sure, I can gather some quick feedback by then |
14:58 |
remingtron |
...sorry I stepped away, but I'm back! |
14:58 |
Bmagic |
remingtron: lol, I was wondering |
14:59 |
abneiman |
ok - any additional business for DIG? |
15:00 |
abneiman |
hearing none... |
15:00 |
abneiman |
#endmeeting |
15:00 |
|
Topic for #evergreen is now Welcome to the #evergreen library system channel! | We are publicly logged: http://irc.evergreen-ils.org/evergreen | Large pastes at http://paste.evergreen-ils.org | Can't speak? Make sure your nickname is registered and that you are identified to freenode services: https://freenode.net/kb/answer/registration |
15:00 |
pinesol |
Meeting ended Thu Nov 7 15:00:14 2019 US/Eastern. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) |
15:00 |
pinesol |
Minutes: http://evergreen-ils.org/meetings/evergreen/2019/evergreen.2019-11-07-14.00.html |
15:00 |
pinesol |
Minutes (text): http://evergreen-ils.org/meetings/evergreen/2019/evergreen.2019-11-07-14.00.txt |
15:00 |
pinesol |
Log: http://evergreen-ils.org/meetings/evergreen/2019/evergreen.2019-11-07-14.00.log.html |
15:00 |
remingtron |
abneiman++ |
15:00 |
Bmagic |
abneiman++ |
15:00 |
jweston |
abneiman++ |
15:00 |
sandbergja |
abneiman++ |
15:00 |
sandbergja |
dluch++ |
15:00 |
jihpringle |
abneiman++ |
15:00 |
abneiman |
thanks Bmagic++ remingtron++ # to the future! |
15:00 |
Bmagic |
and beyond! |
15:26 |
|
yboston joined #evergreen |
15:43 |
|
sandbergja joined #evergreen |
16:51 |
|
khuckins joined #evergreen |
17:04 |
|
mmorgan left #evergreen |
17:06 |
|
sandbergja_ joined #evergreen |
17:07 |
|
aabbee joined #evergreen |
17:33 |
|
Dyrcona joined #evergreen |
17:33 |
Dyrcona |
@later tell csharp: I dropped by to pick up a reason. |
17:33 |
pinesol |
Dyrcona: The operation succeeded. |
17:33 |
* Dyrcona |
signs out and goes back to listening to Neil Young. |
17:42 |
|
sandbergja_ joined #evergreen |
17:45 |
csharp |
@later tell Dyrcona you'd probably like Echo in the Canyon, which is Jakob Dylan's (& friends') tribute to the Laurel Canyon influence on rock in the late 60s |
17:45 |
pinesol |
csharp: The operation succeeded. |
17:51 |
sandbergja |
remingtron: Bmagic: one thing that trips me up every time on the antora README is that it assumes that gulp is ready to go in the user's PATH |
17:52 |
sandbergja |
(for me it's not, and Ubuntu helpfully recommends to me that I apt-get an outdated version of gulp that can't even handle antora) |
17:52 |
sandbergja |
Any objection to me push a change to that README |
17:52 |
sandbergja |
so that instead of just `gulp`, it's `node_modules/gulp/bin/gulp.js`? |
17:53 |
sandbergja |
which'll be sure to be there because of the npm install step? |
18:16 |
csharp |
https://docs.antora.org/antora-ui-default/set-up-project/ implies that gulp is available after npm install (just reading, not tried it ;-) ) |
18:19 |
|
sandbergja_ joined #evergreen |
18:20 |
sandbergja |
csharp: I guess it's also possible that I've done something odd to my PATH on my laptop; I'll try it again in a fresh VM |
18:22 |
csharp |
sandbergja++ |
18:34 |
sandbergja |
hmmm... still not working for me. I'll throw some info into launchpad |
18:59 |
jeff |
really really wish github issues import would support things like issue numbers. |
19:00 |
jeff |
(and wasn't an unreleased api with docs updated in 2016) |
21:00 |
|
sandbergja joined #evergreen |
21:36 |
|
sandbergja joined #evergreen |
23:01 |
pinesol |
News from qatests: Failed Installing Angular web client <http://testing.evergreen-ils.org/~live/test.29.html#2019-11-07T23:00:51,224589584-0500 -0> |