Rebrand org identity: AISViz -> MAPS Lab

CODE_OF_CONDUCT.md

@@ -59,7 +59,7 @@ representative at an online or offline event.
 ## Enforcement
 
 Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported to the community leaders responsible for enforcement at aisviz@dal.ca.
+reported to the community leaders responsible for enforcement at mapslab@dal.ca.
 All complaints will be reviewed and investigated promptly and fairly.
 
 All community leaders are obligated to respect the privacy and security of the

CONTRIBUTING.md

@@ -1,6 +1,6 @@
-# Contributing to AISViz
+# Contributing to MAPS Lab
 
-We appreciate your interest in contributing to the AISViz organization. This document outlines how you can contribute to our projects, including AISdb, and what you can expect during the process. It applies to every repository in the organization unless a repository provides its own contributing guide.
+We appreciate your interest in contributing to the MAPS Lab organization. This document outlines how you can contribute to our projects, including AISdb, and what you can expect during the process. It applies to every repository in the organization unless a repository provides its own contributing guide.
 
 ## Table of Contents
 - [Code of Conduct](#code-of-conduct)
@@ -17,7 +17,7 @@ We appreciate your interest in contributing to the AISViz organization. This doc
 Before contributing, please read our [Code of Conduct](CODE_OF_CONDUCT.md) to understand the expectations for behavior. All participants are required to adhere to the Code of Conduct.
 
 ## Questions and Discussions
-Have a question or want to discuss a topic related to an AISViz project? Please check the [documentation](https://aisviz.gitbook.io/documentation/) and [tutorials](https://aisviz.gitbook.io/tutorials/) first. If your question remains unanswered, feel free to open an issue on the relevant repository to start a discussion, or reach us at aisviz@dal.ca.
+Have a question or want to discuss a topic related to a MAPS Lab project? Please check the [documentation](https://aisviz.gitbook.io/documentation/) and [tutorials](https://aisviz.gitbook.io/tutorials/) first. If your question remains unanswered, feel free to open an issue on the relevant repository to start a discussion, or reach us at mapslab@dal.ca.
 
 ## How to Contribute
 You can contribute in many ways, such as improving documentation, submitting bug reports, proposing new features, and submitting pull requests with code changes.
@@ -60,11 +60,11 @@ While we don't have a formal style template, we encourage you to keep your contr
 - Keep your code DRY (Don't Repeat Yourself).
 
 ## Community and Support
-Join the AISViz community! Here are some ways you can participate.
+Join the MAPS Lab community! Here are some ways you can participate.
 
 - Star our projects on GitHub.
 - Share our work on social media.
 - Contribute to the conversations in issues.
-- Share your experiences with AISViz tools at meetups or conferences.
+- Share your experiences with MAPS Lab tools at meetups or conferences.
 
-Thank you for your contributions to AISViz!
+Thank you for your contributions to MAPS Lab!

README.md

@@ -1,7 +1,7 @@
-# AISViz community defaults
+# MAPS Lab community defaults
 
-This repository holds the org-wide community defaults for the [AISViz](https://github.com/AISViz)
+This repository holds the org-wide community defaults for the [MAPS Lab](https://github.com/MAPS-Lab)
 organization. GitHub applies the contributing guide (`CONTRIBUTING.md`), security policy
-(`SECURITY.md`), and code of conduct (`CODE_OF_CONDUCT.md`) kept here to every AISViz repository
-that does not define its own, and the organization profile shown on the AISViz landing page lives
+(`SECURITY.md`), and code of conduct (`CODE_OF_CONDUCT.md`) kept here to every MAPS Lab repository
+that does not define its own, and the organization profile shown on the MAPS Lab landing page lives
 in [`profile/README.md`](profile/README.md).

SECURITY.md

@@ -1,18 +1,18 @@
 # Security Policy
 
-This policy applies to every repository in the AISViz organization unless a repository provides its own security policy.
+This policy applies to every repository in the MAPS Lab organization unless a repository provides its own security policy.
 
 ## Supported Versions
 
-AISViz is committed to maintaining the security of our software and promptly addressing security vulnerabilities. Security fixes target the latest release of each actively maintained project. Older releases do not receive security updates, so please upgrade to the most recent version before reporting an issue.
+MAPS Lab is committed to maintaining the security of our software and promptly addressing security vulnerabilities. Security fixes target the latest release of each actively maintained project. Older releases do not receive security updates, so please upgrade to the most recent version before reporting an issue.
 
 ## Reporting a Vulnerability
 
-The AISViz team takes security vulnerabilities seriously. If you discover a security issue within any AISViz project, please report it by following the guidelines below. This allows us to assess the risk and take the necessary steps to mitigate the vulnerability as quickly as possible.
+The MAPS Lab team takes security vulnerabilities seriously. If you discover a security issue within any MAPS Lab project, please report it by following the guidelines below. This allows us to assess the risk and take the necessary steps to mitigate the vulnerability as quickly as possible.
 
 ### How to Report a Security Vulnerability
 
-- **Email.** Send an email to aisviz@dal.ca. Please include a detailed description of the issue, including the steps to reproduce the vulnerability and the affected repository. If possible, include patches, scripts, or other resources that could help evaluate the vulnerability.
+- **Email.** Send an email to mapslab@dal.ca. Please include a detailed description of the issue, including the steps to reproduce the vulnerability and the affected repository. If possible, include patches, scripts, or other resources that could help evaluate the vulnerability.
 - **GitHub issue.** For findings that do not immediately impact the security of a project or its users (such as potential optimizations or best practices), consider opening a GitHub issue on the relevant repository.
 
 ### Response Expectations
@@ -22,4 +22,4 @@ The AISViz team takes security vulnerabilities seriously. If you discover a secu
 - **Confidentiality.** Please keep the communication regarding the security issue confidential until we have assessed the impact and publicly disclosed the vulnerability.
 - **Disclosure.** Once the vulnerability has been addressed, we will provide a report about the issue, the steps taken to resolve it, and any applicable acknowledgments to those who reported it.
 
-We appreciate your support in making AISViz projects more secure. By following these guidelines, we can work together to ensure the security and integrity of our software.
+We appreciate your support in making MAPS Lab projects more secure. By following these guidelines, we can work together to ensure the security and integrity of our software.