Wiki account
You need an account for this wiki so that you can contribute to Samvera's pages. If you do not have one already, please request an account by sending an email to sysadmin@duraspace.org.
Mailing Lists
Samvera-Slack-Admins
This is a closed list available to Samvera Slack administrators. Send email to slack@samvera.org if you're having trouble with Slack.
Samvera-Releases (1-2 messages a month)
Subscribe to this list at https://groups.google.com/forum/#!forum/samvera-releases/join if you want notification of every new point (bugfix) release of Samvera and related software. Most people will not need this density of release information. Major releases are notified to the Samvera-Announces list.
Samvera-Announces (2-5 messages a month)
Subscribe to this list at https://groups.google.com/forum/#!forum/samvera-announces/join if you want the minimum mailings - only the most important security, major release, and event announcements
Samvera-Community (5-10 messages a week on average)
Subscribe to this list at https://groups.google.com/forum/#!forum/samvera-community/join if you want a broader spectrum of non-technical information related to Samvera
- All messages to Samvera-Announces are sent also to the Samvera-Community list - if you’re subscribed to Samvera-Community, you don’t need to subscribe to Samvera-Announces
Samvera-Tech (15-20 messages per week on average)
Subscribe to this list at https://groups.google.com/forum/#!forum/samvera-tech/join if you want to follow current technical discussions about Samvera and all of its components
- All messages to Samvera-Announces are sent also to the Samvera-Tech list - if you’re subscribed to Samvera-Tech, you don’t need to subscribe to Samvera-Announces
Samvera-Metadata
Subscribe to this list at https://groups.google.com/forum/#!forum/samvera-metadata/join if you want to get help with or discuss metadata issues in Samvera
Samvera-Partners https://groups.google.com/forum/?hl=en#!forum/samvera-partners
This is a closed list available only to formal Samvera Partners and is typically used only for community governance discussions
Samvera-Steering
This is a closed list available to Steering Group members and is typically used for community maintenance and licensing activities
Blacklight http://groups.google.com/group/blacklight-development
Not a Samvera list as such but possibly of interest to those whose focus is on the Blacklight layer. The primary mailing list for anyone using or improving Blacklight.
QUESTIONS?
If you have general questions about adopting Samvera, project planning, requirements definition, etc., feel free to e-mail the samvera-community list
If you have technical questions about implementing or developing with Samvera, feel free to e-mail the samvera-tech list
If you have questions about becoming a partner, code licensing, or usage rights, please e-mail the samvera-steering list
Slack
The Samvera community's primary realtime communication mechanism is a Slack workspace. We use this for discussion, questions, announcements, interest groups, and working groups. Anyone can create a new channel within the Samvera Slack workspace once they have registered for an account.
Slack workspace: https://samvera.slack.com
Joining a Slack workspace requires an invitation, but anyone can generate an automatic invite using the following form: http://slack.samvera.org/. If you need help getting connected, ping slack@samvera.org and someone will be in touch.
A tutorial can be found at https://samvera.slack.com/getting-started. Slack has clients for Mac, PC, Linux, and mobile devices, and may be used via any web browser.
Social Media
- Twitter: @SamveraRepo
Calls
Technical Call
There is a weekly Samvera technical call for developers and other folks who are contributing code or are actively using the core Samvera plugins & components. Contributors should consult the Getting Connected page in the Developers section of this wiki for more information.
- Wednesdays at 9:00 AM Pacific Time;
- Check out this helpful time zone translation
Conference Line Information
How to connect: https://psu.zoom.us/j/613720745 (this link will launch the Zoom client – if you do not have Zoom, expand the instructions below)
Monthly Partner Call
There is a monthly Samvera Partner Calls among (signed) partners. This call complements the technical calls (above), but instead of a focus on code, the Partners call focuses on community & functional progress.
- 2nd Friday of the month;
- 8:30 AM - 9:30 AM Pacific Time;
- Check out this helpful time zone translation
This call used to use the conference line above but has recently been exploring other systems. For a given call, check the agenda on the right of the Samvera Partner Calls page for the dial-in (etc) information.
Samvera Connect, Partner & Steering Group Meetings
Once each academic year, there is a global Samvera Connect Meetings meeting; this is a chance for all Samvera Partners and users to meet at one time in one place to promote connections and collaboration throughout the rest of the year. The Samvera Partners also gather for a multi-day (usually three), face-to-face meeting a couple of times a year. These events provide regular forums for partners to focus on aligning road maps, coordinating resources, and extending the technical, community, documentation and training framework. See the Samvera Partner Meetings page for more details. The Samvera Steering Group, a smaller group of institutions that stewards the overall effort and provides central administration, also meets separately during these sessions.
Web Site, Wikis, Issue Tracking & Code Repos
- Samvera's Web Page https://samvera.org
- Samvera Wiki (this site) https://wiki.duraspace.org/display/samvera
- Code Repository https://github.com/samvera
Further Information
If you have a question that is not addressed on these pages, send email to the samvera-tech email list. Or if you have an inquiry that's not appropriate for any of the above channels, then try one of the Samvera Partners. If you don't know whom to contact and you really need to get in touch with someone, try Richard Green in the first instance.