Update docs to reflect organization change

CITATION.cff

@@ -24,4 +24,4 @@ identifiers:
   - description: Latest release.
     type: doi
     value: "10.5281/zenodo.15422620"
-url: "https://github.com/intel/code-base-investigator"
+url: "https://github.com/P3HPC/code-base-investigator"

CODE_OF_CONDUCT.md

@@ -59,8 +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
-CommunityCodeOfConduct AT intel DOT com.
+reported to the community leaders via e-mail.
 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

@@ -6,8 +6,8 @@ welcome community contributions. You can:
 - Submit your changes directly with a [pull request][1].
 - File a bug or open a feature request with an [issue][2].
 
-[1]: https://github.com/intel/code-base-investigator/pulls
-[2]: https://github.com/intel/code-base-investigator/issues
+[1]: https://github.com/P3HPC/code-base-investigator/pulls
+[2]: https://github.com/P3HPC/code-base-investigator/issues
 
 # Pull Requests
 

README.md

@@ -16,7 +16,7 @@ portability and maintainability of an application's source code.
 - Identify stale, legacy, code paths that are unused by any compilation target.
 
 - Export metrics and code path information required for P3 analysis using [other
-  tools](https://intel.github.io/p3-analysis-library/).
+  tools](https://p3hpc.github.io/p3-analysis-library/).
 
 
 ## Table of Contents
@@ -49,7 +49,7 @@ The latest release of CBI is version 2.0.0. To download and install this
 release, run the following:
 
 ```
-pip install git+https://github.com/intel/code-base-investigator@2.0.0
+pip install git+https://github.com/P3HPC/code-base-investigator@2.0.0
 ```
 
 We strongly recommend installing CBI within a [virtual
@@ -60,7 +60,7 @@ environment](https://docs.python.org/3/library/venv.html).
 After installation, run `codebasin -h` to see a complete list of options.
 
 A full tutorial can be found in the [online
-documentation](https://intel.github.io/code-base-investigator/).
+documentation](https://p3hpc.github.io/code-base-investigator/).
 
 
 ## Contribute
@@ -81,14 +81,13 @@ See [SECURITY](SECURITY.md) for more information.
 
 The main branch of CBI is the development branch, and should not be used in
 production.  Tagged releases are available
-[here](https://github.com/intel/code-base-investigator/releases).
+[here](https://github.com/P3HPC/code-base-investigator/releases).
 
 
 ## Code of Conduct
 
-Intel has adopted the Contributor Covenant as the Code of Conduct for all of
-its open source projects. See [CODE OF CONDUCT](CODE_OF_CONDUCT.md) for more
-information.
+We have adopted the Contributor Covenant as the Code of Conduct for this
+project. See [CODE OF CONDUCT](CODE_OF_CONDUCT.md) for more information.
 
 
 ## Citations

SECURITY.md

@@ -1,5 +1,5 @@
 # Security Policy
-Intel is committed to rapidly addressing security vulnerabilities affecting our customers and providing clear guidance on the solution, impact, severity and mitigation.
 
 ## Reporting a Vulnerability
-Please report any security vulnerabilities in this project [utilizing the guidelines here](https://www.intel.com/content/www/us/en/security-center/vulnerability-handling-guidelines.html).
+
+To report a security issue, please use the GitHub Security Advisory ["Report a Vulnerability"](https://github.com/P3HPC/code-base-investigator/security/advisories/new) tab.

codebasin/file_source.py

@@ -521,7 +521,7 @@ def c_file_source(fp, directives_only=False):
     if parsing_failed:
         raise RuntimeError(
             "Parsing failed. Please open a bug report at: "
-            "https://github.com/intel/code-base-investigator/issues/new?template=bug_report.yml",  # noqa: E501
+            "https://github.com/P3HPC/code-base-investigator/issues/new?template=bug_report.yml",  # noqa: E501
         )
 
     return (total_sloc, total_physical_lines)
@@ -602,7 +602,7 @@ def fortran_file_source(fp):
     if parsing_failed:
         raise RuntimeError(
             "Parsing failed. Please open a bug report at: "
-            "https://github.com/intel/code-base-investigator/issues/new?template=bug_report.yml",  # noqa: E501
+            "https://github.com/P3HPC/code-base-investigator/issues/new?template=bug_report.yml",  # noqa: E501
         )
 
     return (total_sloc, total_physical_lines)

codebasin/schema/analysis.schema

@@ -1,6 +1,6 @@
 {
   "$schema": "https://json-schema.org/draft/2020-12/schema",
-  "$id": "https://raw.githubusercontent.com/intel/code-base-investigator/main/codebasin/schema/analysis.schema",
+  "$id": "https://raw.githubusercontent.com/P3HPC/code-base-investigator/main/codebasin/schema/analysis.schema",
   "title": "Code Base Investigator Analysis File",
   "description": "Analysis options for Code Base Investigator.",
   "type": "object",

codebasin/schema/cbiconfig.schema

@@ -1,6 +1,6 @@
 {
   "$schema": "https://json-schema.org/draft/2020-12/schema",
-  "$id": "https://raw.githubusercontent.com/intel/code-base-investigator/main/codebasin/schema/cbiconfig.schema",
+  "$id": "https://raw.githubusercontent.com/P3HPC/code-base-investigator/main/codebasin/schema/cbiconfig.schema",
   "title": "Code Base Investigator Configuration File",
   "description": "Configuration options for Code Base Investigator.",
   "type": "object",

codebasin/schema/compilation-database.schema

@@ -1,6 +1,6 @@
 {
   "$schema": "https://json-schema.org/draft/2020-12/schema",
-  "$id": "https://raw.githubusercontent.com/intel/code-base-investigator/main/codebasin/schema/compilation-database.schema",
+  "$id": "https://raw.githubusercontent.com/P3HPC/code-base-investigator/main/codebasin/schema/compilation-database.schema",
   "title": "Compilation Database",
   "description": "Compilation database format used by many projects.",
   "type": "array",

codebasin/schema/coverage.schema

@@ -1,6 +1,6 @@
 {
   "$schema": "https://json-schema.org/draft/2020-12/schema",
-  "$id": "https://raw.githubusercontent.com/intel/p3-analysis-library/main/p3/data/coverage.schema",
+  "$id": "https://raw.githubusercontent.com/P3HPC/p3-analysis-library/main/p3/data/coverage.schema",
   "title": "Coverage",
   "description": "Lines of code used in each file of a code base.",
   "type": "array",

docs/source/emulating-compiler-behavior.rst

@@ -15,7 +15,7 @@ additional options when emulating certain compilers.
     If you encounter a situation that is not supported by CBI and which cannot
     be described by our existing configuration files, please `open an issue`_.
 
-.. _`open an issue`: https://github.com/intel/code-base-investigator/issues/new/choose
+.. _`open an issue`: https://github.com/P3HPC/code-base-investigator/issues/new/choose
 
 
 Motivating Example
@@ -138,7 +138,7 @@ CBI ships with a number of compiler definitions included (see `here`_), and the
 same syntax can be used to define custom compiler behaviors within the
 ``.cbi/config`` file.
 
-.. _`here`: https://github.com/intel/code-base-investigator/tree/main/codebasin/compilers
+.. _`here`: https://github.com/P3HPC/code-base-investigator/tree/main/codebasin/compilers
 
 For example, the TOML file below defines behavior for the ``gcc`` and ``g++`` compilers:
 

docs/source/index.rst

@@ -33,8 +33,8 @@ Code Base Investigator
    :hidden:
    :caption: Contributing
 
-   How to Contribute <https://github.com/intel/code-base-investigator/blob/main/CONTRIBUTING.md>
-   GitHub <https://github.com/intel/code-base-investigator>
+   How to Contribute <https://github.com/P3HPC/code-base-investigator/blob/main/CONTRIBUTING.md>
+   GitHub <https://github.com/P3HPC/code-base-investigator>
    notices-and-disclaimers
 
 
@@ -53,7 +53,7 @@ portability and maintainability of an application's source code.
 - Export metrics and code path information required for P3 analysis using
   `other tools`_.
 
-.. _other tools: https://intel.github.io/p3-analysis-library/index.html
+.. _other tools: https://p3hpc.github.io/p3-analysis-library/index.html
 
 
 Installation
@@ -62,7 +62,7 @@ Installation
 The latest release of CBI is version 2.0.0. To download and install this
 release, run the following::
 
-    $ pip install git+https://github.com/intel/code-base-investigator@2.0.0
+    $ pip install git+https://github.com/P3HPC/code-base-investigator@2.0.0
 
 We strongly recommend installing CBI within a virtual environment, to simplify
 dependency management and improve security. Some alternative methods of
@@ -72,7 +72,7 @@ creating a virtual environment are shown below.
 
     .. code-block:: text
 
-        $ git clone --branch 2.0.0 https://github.com/intel/code-base-investigator.git
+        $ git clone --branch 2.0.0 https://github.com/P3HPC/code-base-investigator.git
         $ python3 -m venv cbi
         $ source cbi/bin/activate
         $ cd code-base-investigator
@@ -82,7 +82,7 @@ creating a virtual environment are shown below.
 
     .. code-block:: text
 
-        $ git clone --branch 2.0.0 https://github.com/intel/code-base-investigator.git
+        $ git clone --branch 2.0.0 https://github.com/P3HPC/code-base-investigator.git
         $ cd code-base-investigator
         $ uv tool install .
 

docs/source/notices-and-disclaimers.rst

@@ -14,4 +14,4 @@ License
 =======
 
 Code Base Investigator (CBI) is licensed under the BSD-3-Clause License, and
-made available at http://github.com/intel/code-base-investigator/.
+made available at http://github.com/P3HPC/code-base-investigator/.

docs/source/sample-code-base.rst

@@ -11,7 +11,7 @@ This tutorial uses a sample code base designed to showcase the features of CBI.
    It can be downloaded from :download:`here<sample-code-base.zip>` or copied
    from the ``docs/source/sample-code-base`` directory `on GitHub`_.
 
-.. _on GitHub: https://github.com/intel/code-base-investigator/tree/main/docs/sample-code-base/
+.. _on GitHub: https://github.com/P3HPC/code-base-investigator/tree/main/docs/sample-code-base/
 
 
 Directory Structure

docs/source/specialization.rst

@@ -21,7 +21,7 @@ with the `P3 Analysis Library`_:
    https://doi.org/10.1016/j.future.2017.08.007
 
 .. _P3 Analysis Library:
-   https://intel.github.io/p3-analysis-library/
+   https://p3hpc.github.io/p3-analysis-library/
 
 This definition is deliberately very flexible, so a platform can represent
 **any** execution environment for which code may be specialized. A platform

pyproject.toml

@@ -6,7 +6,7 @@ requires = ["setuptools>=64", "setuptools-scm>=8"]
 
 [project]
 authors = [
-  {"name" = "S. John Pennycook", "email" = "john.pennycook@intel.com"},
+  {"name" = "S. John Pennycook", "email" = "john.pennycook@gmail.com"},
 ]
 description = "Code Base Investigator"
 dynamic = ["version", "readme"]
@@ -39,9 +39,9 @@ cbi-cov = "codebasin.coverage:__main__.main"
 cbi-tree = "codebasin:tree.main"
 
 [project.urls]
-"Github" = "https://www.github.com/intel/code-base-investigator"
-"Issues" = "https://www.github.com/intel/code-base-investigator/issues"
-"Pull requests" = "https://www.github.com/intel/code-base-investigator/pulls"
+"Github" = "https://www.github.com/P3HPC/code-base-investigator"
+"Issues" = "https://www.github.com/P3HPC/code-base-investigator/issues"
+"Pull requests" = "https://www.github.com/P3HPC/code-base-investigator/pulls"
 
 [project.optional-dependencies]
 dev = [