Topics to Discuss
Repo Logistics
Github repo access
Must be added to the “Discovery” Team in the account by Gem Stone-Logan
Repo structure
Snippet format/template
Issue format/template (labels)
Group Logistics
Notes/wiki
Meeting frequency
Specific Enhancement Topics
HathiTrust
Decisions
Repo
We will organize the repo with a top level folder for each campus
Solutions to problems should be presented in a Markdown file documenting the problem and solution with JS and CSS snippets (and config settings) embedded inside.
We will use Github issues to create a list of known problems or enhancements with no solutions.
We should use labels to classify issues into a small set of high level buckets (e.g. bugs vs call for help vs repo housekeeping)
We could use the wiki as a way to make the solutions findable
Meetings/Comms
We do NOT need to meet biweekly
We will try out a new Slack channel in the UC Tech: #library-primo-code-share
Action Items
- Joshua Gomez will ask about using the SILS Discovery wiki space for Primo Repo team meetings notes
- Everyone join the new Slack channel
- Everyone send Joshua Gomez their Github handles
- Everyone should “watch” the repo
- Joshua Gomez will put together the intial structure and readme for the repo