| Status | ||||
|---|---|---|---|---|
|
...
Note that following current best practices within Hydra, Working and Interest groups should use an existing channel unless and until it becomes clear that a dedicated channel is needed. This section should specify which existing channel(s) will be used: e.g., samvera-tech, samvera-partners, samvera-community@googlegroups.com. When using a shared channel, individual working groups should start the subject line with their name in []s, such as [archives] for the Archives Working Group. If and when a dedicated channel is needed, the new channel should be well publicized and open to any interested subscribers/participants in the community.
We The group will have a slack channel in the samvera slack community, and will use existing channels for other communications. Meetings will use Google Hangouts, or similar, for calls.
A regular meeting time will be agreed to suit the members of the group.
Members
Note that Working Groups must have participants from three different Partners. All members of a working group producing software must be licensed Samvera contributors covered by the appropriate CLAs. Other types of contributions such as requirements, design, best practices, documentation, etc. - do not require CLAs but participants should accept that the materials to which they contribute may be released under a Creative Commons Attribution 4.0 International License..
- Tom Johnson, CoFacilitator (Data Curation Experts (DCE))
- Julie Allinson, Facilitator (CoSector, University of London)
- Jim Coble (Duke)
- Brian McBride (University of Utah)
- Alexandra Dunn (UCSB)
- Chrissy Rissmeyer (UCSB)
- James Van Mil (U Cincinnati)
- Gregory Reser (UC San Diego)
- Gabriela Montoya (UC San Diego)
- wgcowan (Indiana University)
- Carrick Rogers (Northwestern University)
- Juliet Hardesty (Indiana University)
- Andrew Myers (WGBH)
- Anna Goslen (UNC-Chapel Hill)
- George Wheeler (Notch8)
...