2018-01-18 Meeting notes

Date

1:00 pm  - 2:00 pm CST

Attendees

Discussion items

ItemWhoNotes
Roll call and note taker
Updates on new tech docs repo

Bobbi: Raising an issue (e.g., when you see something is unclear in the documentation but don't know the answer to it). Laney: Seems like the way to go.

Laney: Seems like people on this sub-team should be able to merge. What do people think? NC State documentation policy: two people have to review it before it's merged. Could build it into this meeting. Core Committers example was that there becomes a group mentality that somebody else must know this better. Laney ends up assigning them. Sub-team leader (Scott) could be the monitor-er and assign-er. Folks are in agreement.

Ways for people to raise issues for people don't have GitHub accounts–wait until it's a problem.

We'll go with NC State model, Scott facilitating, but then have a check-in time during this meeting. It's good to have someone assigned to an issue.


-- Feedback from last TAC callAll
-- Workplan Goal 1. Enhance provisioning documentation

Rachel Maderik (Unlicensed), Bobbi Fox (Unlicensed), Trevor Thornton

Documentation for HTTPS. Configuring your web server and configuring ArchivesSpace. Available here: https://github.com/maderikra/tech-docs/blob/master/provisioning/https.md

Will submit a PR for that, other questions will be thrown out as issues. Will use FIXME as a convention.


-- Workplan Goal 2. Enhance plugin documentation

Dallas PillenBobbi Fox (Unlicensed)

Have a plan to move forward. Dallas is working on adding additional documentation for existing "exemplar" plug-ins. Bobbi is identifying issues, working on plug-ins README. Documenting issues is good, even when there's not solution.


Wrap-up and next steps

Action items