Where: Google Hangouts: https://hangouts.google.com/call/a3x36uncwfgghfr4fjn3znytuye
Moderator: Andrew Myers (WGBH)
Notetaker: Matthew Barnett
- Review action items†
- User Stories, commenting and potentially adding (Everyone)
- Discuss and vote on candidates (Everyone)
- Any objections to a Github group in projecthydra-labs to make it easier to nag one another?
- Review Roadmap†
- Identify any blockers for the following milestones:
- Hydra plugin projects have github repos.
- Hydra plugin github repos have initial tickets.
- Guidelines v0.1.0 pushed to github.
- Request for feedback on Guidelines v0.1.0 has been posted.
- What can we do right now, in this meeting?
- Write the plugins for Hyrax?
- Make tickets for these, including any blockers, and get them assigned.
- Building off of the Hydra's Contributing Guidelines
- None of our Guidelines should contradict these.
- We should refer to this document before creating any new Guideline, to be sure we're covering something new and useful.
- For instance, see Noah Botimer's comment on issue #6.
- What more do we need to say about documentation for Plugins that is not stated in Hydra's contributing guidelines?
- New/Carryover Action Items†
- Next Meeting†
- The group is happy with current state of user stories
- Discussion & Voting on candidates:
- Discussion of adding "Social Media" plugin (the larger community seems to think we're working on this)
- Questioning Authority received no votes, ruled out
- Browse Everything. Small and self-contained like Google Analytics, but Google Analytics had more votes
- Google Analytics & Geoconcerns received the most votes
- Social Media Sharing Buttons needs to hook into a part of the UI, which presents different challenges than Google Analytics if it's purely a non-UI plugin.
- Social Media Sharing Buttons may need to integrate more (Authentication?) whereas Google Analytics is a bit more additive and less integrative.
- Everyone is onboard with Geoconcerns
- After some discussion, the group is making Google Analytics the second plugin to consider
- No objections
- Milestone progress:
- Action items created for repos/branches
- "W3C-style" for guidelines discussed
- Blocker on Guidelines publication – no Table of Contents
- initial version of ToC blocking Request for feedback (would like to solicit feedback beginning of day Friday or Monday)
- Discussion of whether we should be considering targeting Hyrax vs Sufia/CurationConcerns. The group is currently using the older verbiage until things settle down, but we think Hyrax will be a target platform (along with lower levels of the stack, like hydra-works)
- Hydra Contributing Guidelines contains some advice relevant to what we're targeting. Good to check with and defer to existing community documentation; ensures our work is in line with community expectations. Discussion of encouraging varying degrees of conformance, working with different parts of the community to reduce learning curve when integrating with the many different gems in the Hydra world, and where our role in providing good documentation can help raise the community's quality of life.
- Eliot to create branch in GeoConcerns for plugin work
- Jenn to create repo for Google Analytics Hydra plugin
- Andrew to double-check that everyone is in the group, can create tickets, be assigned to issues, etc
- Everyone to work on building Table of Contents for Guidelines, as a skeleton on which to build the entire document. Target having this done before Friday or Monday morning.
- Andrew to create a ticket/repo and push first version of guidelines we can discuss/use to build ToC
- Greg to follow up with Mike Giarlo as to whether Hyrax is a good target for the group to consider targeting right now, or if it is still early days.
† - Standing agenda items