Github

Community & Sustainability

  1. 230+ public sites, 1414 listserv members, 144 GitHub members, 28 Committers, 25+ Contributed Modules, 30+ Foundation members, 12 Interest Groups, 10 Community-led software releases, 19 Camps, 3 conferences, 2 major versions with 2 full time employees.
  2. In May 2020 the Islandora Foundation announced they joined the Drupal Association as part of their Supporting Partner Program. The Drupal Association is an educational non-profit organization that tasks itself with fostering and supporting the Drupal software project, the community and its growth.

Drupal Partnership

  1. The Islandora community is comprised of implementers, developers, service companies, and users working as transparently as possible toward better documentation and a better, always open-source, code base. We operate under a Code of Conduct. Membership formalizes involvement in the community and provides financial support for the project. Users get together across many channels, including:
    • Calls: Islandora holds regular Islandora 7 Committers Calls and Islandora 8 Tech Calls. Developers, testers, and other interested parties come together to review tickets, issues, and development goals for Islandora.
    • Islandora Interest Groups are gatherings of Islandora community members who come together around a particular topic relevant to the Islandora ecosystem. The purpose of the interest group is to provide a forum for information exchange, mentorship and development within a limited area of interest and to report findings, submit code, documentation, recommendations as appropriate to the Islandora Coordinating Committee on matters of wider interest relating to the area of expertise. A recent example of an interest group collaboration was the survey and development of the Institutional repository Delta document. This document specifies a commuinity definition of what an “out of the box” IR solution is. Although an IR repository is possible to assemble without a dedicated module it wouldn’t be a standardized process making community assistance a challenge. With help from the Google Scholar engineering team, the community developed with the help with feedback from the community drafted a document proposing an “Islandora Scholar” module that would bring together all the needed resources for a “turnkey” IR solution. Several options were left out deliberately that weren’t essential and could easily be accomplished with few steps from a tutorial. The Islandora interest group surveyed the community, reviewed existing IR options, and consulted with leading industry engineers. Creating a plan for a solution that meets the community’s needs and to precisely align the content in accordance with the Google Scholar engineering team’s feedback. Islandora has years of experience developing an institutional repository, originally developed in 2012 and the community is well equipped to handle the challenge of developing a solution that meets the community needs while maintaining the flexibility necessary for individual institutions.
  2. Vendors are constantly participating and contributing to the progression of the Islandora community and stack. They participate at a nearly daily occurrence and provide a lot of assistance to the community. See more on Vendors
  3. The onboarding process is well established with frequent workshops, video tutorials, 1-on-1 assistance from community members through zoom, and chat options. This makes the stack highly approachable to small colleges and large universities alike.
  4. The Islandora community is a self-sustaining community of over 300 universities and an unknown number of private institutions, it’s clear that the community is well established.
  5. With the platform mainly a “turnkey” repository option providing small and large repositories alike a relatively standardized solution with the flexibility of future growth built in.
  6. The community has gravitated towards providing the options for the users to implement the latest information technology standards, iteratively improve the quality of the platform and inclusivity for the community to meet all of their needs for a repository.
  7. The community engaged pedagogy embraces co-learning and is rooted in a respect for the prior knowledge and experiences that community partners bring to the conversation.
  8. Expert discovery efforts (identifying improvements and developing solutions).
  9. New efforts integrate the community into a broader community with Drupal. This means automated code review for security issues from Drupal, code hosting is hosted directly on Drupal’s Gitlab servers. Having all of Islandora and its contributed modules on Drupal means the update feature in the UI will recognize the modules and allow for module conflict avoidance and update integrations. This simplifies the update process greatly.

Interest Groups

Islandora Interest Groups are gatherings of Islandora community members who come together around a particular topic relevant to the Islandora ecosystem. The purpose of the interest group is to provide a forum for information exchange, mentorship and development within a limited area of interest and to report findings, submit code, documentation, recommendations as appropriate to the Islandora Coordinating Committee on matters of wider interest relating to the area of expertise. Most Interest Groups post meeting times and details to our Community Calendar and user listserv.

Events

The Islandora Foundation holds regular webinars and face-to-face events around the world, where you can access training and meet up with other Islandora users. For more information or to check out the upcoming schedule, please visit the Events Page.

Listservs

The Islandora community uses Google Groups to support two main listservs: a general list for all users, and a more targeted list for developers.

Slack

The Islandora community is active at islandora.slack.com. For an invite, please complete this form.

For more information on the community please see Islandora Community | https://islandora.ca/community