...
...
...
...
Scope & Objectives
Narrative text that should result in a common understanding of:
The overall domain into which the discussion falls
The shared needs and requirements within that domain
Use cases that demonstrate these needs and requirements
Deliverables & Timeframe
Narrative or bulleted text describing the tangible outcomes of the working group.
The timeframe for activities and producing deliverables should also be included in this section. Included should be a sunset date for the group (the date WG will end and announce the WG deliverables/accomplishments).
Meeting Times & Communication Channels
Note that following current best practices within Samvera, interest and working groups should use an existing communication 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.
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..
...
This working group is focused on developing a written set of community guidelines. According to consultant Annalee Flower Horne, "Community Guidelines communicate your community’s values and culture to new and existing community members. The reason to create specific guidelines instead of just saying 'be excellent to each other' or 'treat each other politely' is that there are a wide range of cultural norms across different communities–even micro-communities, like open source projects." Samvera has had pieces of such guidelines, but early versions have been lost over time and existing pieces need review and refreshing. This effort was originally in scope for the Community Safety Working Group active in 2021, but due to scheduling considerations, is now deferred and to be taken on by a spin-off Working Group in early 2022.
Deliverables & Timeframe
With the input and guidance of the consultant, the group will convene in January 2022 and plan to draft the written guidelines, iterate over them as necessary with stakeholders, and finalize them in advance of Virtual Connect in spring 2022.
Update on April 1, 2022: The Samvera Community Guidelines are drafted and feedback from the Community is invited through April 15, 2022.
Update on April 18, 2022: The guidelines received only positive feedback from the Community, so they were adopted as posted and the working group was sunsetted.
Meeting Times & Communication Channels
Meeting Times - scheduling has been ad hoc.
Communication Channels: samvera-community@googlegroups.com ; Slack channel #cdwg
Members
Hannah Frost, facilitator (Stanford University)
Bess Sadler (Princeton University)
Alicia Morris (Tufts University)
Jessica Hilt (UC San Diego)
Heather Greer Klein (Samvera)
Robin Ruggaber (University of Virginia)
your name here (your institution here)
Resources
Meeting Notes
- list of links
or table of meeting notes