Merge pull request #282 from geoblacklight/279_update-community-page

rmseifried · web-flow · commit 478d72c31d56 · 2025-08-17T16:49:07.000-04:00
closes 279 update community page
diff --git a/docs/community.md b/docs/community.md
@@ -1,59 +1,15 @@
-Participants in the GeoBlacklight community come from a variety of professional and intellectual backgrounds (including librarians, software developers, metadata specialists, applied researchers, and others), but we share a common interest in making reliable and high-quality geospatial data easily accessible to members of the research community and the broader public. Many of us work in libraries and other cultural heritage institutions that deploy (or are planning to deploy) GeoBlacklight instances to disseminate and publicize their spatial data collections.
 
-Discovery services and metadata are key challenges for organizations who provide geospatial data. GeoBlacklight connects expertise from the digital library and geospatial communities to provide a better experience for users to find geospatial data.
+## Join the Conversation
 
-Anyone interested in spatial data infrastructures, libraries, GIS, maps, data curation, open source software, and related topics, is welcome to join us. Depending on their skills and interests, participants contribute to the community in any number of ways (for instance, by attending meetings, writing documentation, developing metadata best practices, engaging in outreach, and writing code). Participating in the community is especially beneficial to those who are implementing or maintaining GeoBlacklight as a spatial data discovery interface within their own home institutions.
+Have a question about GeoBlacklight or want to connect with other users and developers?
 
-## Join the Community
-
-<div class="grid cards" markdown>
-
-- ### Volunteer for a Community Role
-
-	We have several designated roles for building and sustaining our community. 
-	
-	[:material-human-handsup: Read about our roles and view vacancies.](#community-roles)
-	
-- ### Join a Workgroup or Interest Group
-
-	We have short term and ongoing groups devoted to specific topics. Or, start a new one!
-	
-	[:material-account-group: View our current groups](#workgroups-and-interest-groups)
-
-- ### Follow our Google Group
-		
-	Follow general project discussions and feature announcements.
-		
-	[ :material-google: Join the GeoBlacklight Google Group](https://groups.google.com/g/geoblacklight-community)
-    
-- ### Chat on Slack
-		
-	Chat with others in the community and to work through technical questions. 
-		
-	[:material-slack: Join GeoBlacklight Slack](https://geoblacklight.slack.com/join/shared_invite/zt-1p7dcay40-Ye_WTt5_iCqU8rDjzhkoWw#/shared-invite/email)
-
-- ### Attend a Monthly Community Meeting
-		    
-	The GeoBlacklight Community Meeting takes place on the second Wednesday of every month. The meetings are open to anyone interested in hearing more about the status of the GeoBlacklight software and associated projects.
-		
-	[:material-view-agenda-outline: Read past meeting agendas](https://z.umn.edu/gbl-meetings)
-  
-- ### Participate in a Community Sprint
-		   
-	The GeoBlacklight Community collaborates on a 2-week sprint every Winter and Summer. Participation in the sprint is open to anyone interested in working on GeoBlacklight. While similar to a traditional code sprint, the GeoBlacklight Community Sprints also include tackling issues around documentation, metadata, community governance, and more. 
-		
-	[:material-run-fast: Read about our sprints](../blog/category/sprints/)
-
-- ### Share Metadata
-	
-	GeoBlacklight gets even better when organizations share metadata. Contribute your metadata to OpenGeoMetadata or use it to populate your own GeoBlacklight installation.
-		
-	[:bootstrap-opengeometadata: Visit OpenGeoMetadata](https://opengeometadata.org)
-
-</div>
+- Join the [**Geo4Lib Slack**](https://join.slack.com/t/geo4lib/shared_invite/zt-3baz35i9x-gLVsSGz8MCDlkGePjk7Ejw) and look for the #geoblacklight channel
+- Join the [**Geo4Lib Google Group**](https://groups.google.com/g/geo4lib-community) to receive announcements and participate in discussions
 
 ## Contribute to the Software
 
+We welcome contributions from developers, metadata specialists, designers, and anyone interested in improving geospatial discovery.
+
 <div class="grid cards" markdown>
 
 - ### Report an Issue
@@ -64,103 +20,51 @@ Anyone interested in spatial data infrastructures, libraries, GIS, maps, data cu
 	
 - ### Contribute Code
 		  
-	As open-source software, GeoBlacklight depends on contributions from our developer community. Anyone is welcome to code for the community to review.
+	As open-source software, GeoBlacklight depends on contributions from our developer community. Anyone is welcome to code for review.
 	
 	[:material-github: Read our software contribution guide](https://github.com/geoblacklight/geoblacklight/blob/main/CONTRIBUTING.md)
 		
 - ### Write Documentation
     
-     Help keep our documentation up-to-date or fix information that is missing or unclear.
-
-     [:material-github: Read our website contribution guide](https://github.com/geoblacklight/geoblacklight.github.io/blob/main/CONTRIBUTING.md)
-    
+    Help keep our documentation up-to-date or fix information that is missing or unclear.
 
-</div>
-
-## Events
-
-<iframe src="https://calendar.google.com/calendar/embed?src=geo4lib%40gmail.com&ctz=America%2FChicago" style="border: 0" width="800" height="600" frameborder="0" scrolling="no"></iframe>
-
-## Community Roles
-
-### Administrative Roles
-
-**Meeting Facilitators**: Becky Seifried (July 2025–July 2026)
-
-* Manage Google calendar
-* Set up and host monthly meetings 
-* Prepare agendas
+    [:material-github: Read our website contribution guide](https://github.com/geoblacklight/geoblacklight.github.io/blob/main/CONTRIBUTING.md)
 
-**Platform Management Team**: ==2 vacancies==
+ - ### Help Triage Issues
+  
+    Join our Issue Triage Group, where developers meet quarterly to review and prioritize GitHub issues. [Reach out on Slack to join.](https://join.slack.com/t/geo4lib/shared_invite/zt-3baz35i9x-gLVsSGz8MCDlkGePjk7Ejw)
 
-* Manage GitHub users and roles
-* Manage Google group permissions, roles, etc.
-* Manage Google Drive members
-* Maintain Slack 
+    [:material-github: Review our ongoing project board](https://github.com/orgs/geoblacklight/projects/2) 
 
-### Documentation Roles
+</div>
 
-**Public Content Manager**: ==1 vacancy==
+## Join the Geo4Lib Community
 
-* Keep the public website(s) up to date
-* Write periodic blog posts, including sprint wrap-up posts
+GeoBlacklight is part of the [Geo4Lib Community](https://geo4lib.org), a community of practice for building tools, metadata, and platforms that improve access to geospatial resources in libraries. Visit [geo4lib.org](https://geo4lib.org) to:
 
-**Technical Writing Lead**: ==1 vacancy==
+- Connect via [communication channels](https://geo4lib.org/get-involved/)
+- Find out how to join and participate in [meetings, sprints, and conferences](https://geo4lib.org/events/)
+- Volunteer for a [community role](https://geo4lib.org/roles/)
 
-* Keep track of what code, metadata, and tutorials need updating
-* Manage GitHub issues related to documentation
-* Coordinate volunteers to update documentation as necessary
 
-### Technical Roles
+## GeoBlacklight Project Maintainers
 
-**Designated Code Mergers**: [see GitHub Teams](https://github.com/orgs/geoblacklight/teams)
+**Designated Code Mergers**: [GeoBlacklight Developers Team](https://github.com/orgs/geoblacklight/teams/geoblacklight-developers)
 
-* Members of the GeoBlacklight Developers team in GitHub
-* Review pull requests on behalf of the team, or assign individual code reviewers based on expertise  
+* Review pull requests
+* Assign individual code reviewers based on expertise  
 
 **Release Coordinators**: Eric Larson + ==1 vacancy==
 
 * Cut tags and releases in the GitHub repository, and write release notes
 * Publish the GeoBlacklight [Ruby gem](https://rubygems.org/gems/geoblacklight)
 * Publish Javascript to [npm](https://www.npmjs.com/package/@geoblacklight/frontend) 
 
-## Workgroups and Interest Groups
-
-<div class="grid cards" markdown>
-
-- ### Issue Triage Workgroup
-
-	Meets quarterly to review and prioritize GitHub issues related to code.
-	
-	* Eliot Jordan
-	* Eric Larson
-	* Karen Majewicz
-	* Keith Jenkins
-	* Maura Carbone
-
-- ### Governance Workgroup
-
-	Improves our communication around change management, connected projects, and community roles.
-	
-	* Karen Majewicz
-	* Becky Seifried
-	* Eliot Jordan
-
-- ### Georeferencing Interest Group
-
-	Discusses georeferencing projects and strategies to enhance GeoBlacklight’s georeferenced map capabilities.
-	
-	* Adam Cox
-	* Alex Marden
-	* Eliot Jordan
-	* Kim Leaman
-	* Marc McGee
-	* Michael Shensky
-	* Stephen Appel
-
-
-</div> 
+**Technical Writing Lead**: ==1 vacancy==
 
+* Keep track of code, metadata, and tutorials
+* Manage GitHub issues related to documentation
+* Coordinate volunteers to update documentation as needed
 
 
 ## GeoBlacklight Institutional Contributors
@@ -188,7 +92,7 @@ GeoBlacklight has been collaboratively developed by affiliates of the following
 
 !!! tip "Feedback"
 
-	Did we miss your institution? Have a suggestion for this website? Create an issue on the [GeoBlacklight Website Github page here](https://github.com/geoblacklight/geoblacklight.github.io/issues).
+	Did we miss your institution? Have a suggestion for this site? Create an issue on the [GeoBlacklight Website Github page here](https://github.com/geoblacklight/geoblacklight.github.io/issues).
 
 
 
diff --git a/docs/index.md b/docs/index.md
@@ -27,7 +27,7 @@ hide:
 <h3 style="text-align: center;">Participating institutions</h3>
 <ul>
 <li>GeoBlacklight provides a customizable platform for delivering geospatial information to end users</li>
-<li>Participants can connect to other contributors through our active <a href = "community/#how-to-connect">communication channels</a> and learn best practices for software and metadata implementation.</li>
+<li>Participants can connect to other contributors through our active <a href = "community">communication channels</a> and learn best practices for software and metadata implementation.</li>
 </ul>
 </div>
 
diff --git a/mkdocs.yml b/mkdocs.yml
@@ -2,7 +2,7 @@ site_name: GeoBlacklight
 site_url: https://geoblacklight.org
 repo_url: https://github.com/geoblacklight/geoblacklight
 repo_name: GeoBlacklight on GitHub
-copyright: GeoBlacklight Community &copy; 2015 - 2024
+copyright: GeoBlacklight Community &copy; 2015 - 2025
 theme:
   name: material
   logo: images/gbl-favicon.png
