Point links and docs to the PyCalendar organization

.github/ISSUE_TEMPLATE/bug_report.md

@@ -46,6 +46,6 @@ Output:
 
 <!-- Add any other context about the issue here, including related issues and pull requests. -->
 
-- [ ] I tested it with the latest version. For example, I used the command `pip3 install --upgrade https://github.com/collective/icalendar.git`.
+- [ ] I tested it with the latest version. For example, I used the command `pip3 install --upgrade https://github.com/PyCalendar/icalendar.git`.
 - [ ] I attached the `.ics` sample file, or there is no `.ics` sample file.
       To remove private information, use icalendar-anonymizer either through its [website](https://icalendar-anonymizer.com/) or [install it locally](https://docs.icalendar-anonymizer.com/latest/installation.html).

.github/ISSUE_TEMPLATE/config.yml

@@ -1,5 +1,5 @@
 blank_issues_enabled: false
 contact_links:
   - name: Discussions
-    url: https://github.com/collective/icalendar/discussions
+    url: https://github.com/PyCalendar/icalendar/discussions
     about: For questions, ideas, and community discussions

.github/workflows/documentation.yml

@@ -38,7 +38,7 @@ jobs:
         with:
           # UV_VERSION can be set in the repository settings:
           # Settings -> Secrets and variables -> Actions or click here:
-          # https://github.com/collective/icalendar/settings/variables/actions
+          # https://github.com/PyCalendar/icalendar/settings/variables/actions
           # -> Variables -> UV_VERSION
           version: "${{ vars.UV_VERSION }}"
 

.github/workflows/generate_matrix.py

@@ -144,7 +144,7 @@ def generate_matrix(git_ref, review, event_name=""):
     #
     # Note: If you change test names, also make sure that the
     #       branch protection rules are adjusted to the new names.
-    #       https://github.com/collective/icalendar/settings/branches
+    #       https://github.com/PyCalendar/icalendar/settings/branches
     #
 
     for run in matrix:

.github/workflows/tests.yml

@@ -56,7 +56,7 @@ jobs:
         enable-cache: true
         # UV_VERSION can be set in the repository settings:
         # Settings -> Secrets and variables -> Actions or click here:
-        # https://github.com/collective/icalendar/settings/variables/actions
+        # https://github.com/PyCalendar/icalendar/settings/variables/actions
         # -> Variables -> UV_VERSION
         version: "${{ vars.UV_VERSION }}"
         python-version: ${{ matrix.python_version }}
@@ -134,7 +134,7 @@ jobs:
         enable-cache: false
         # UV_VERSION can be set in the repository settings:
         # Settings -> Secrets and variables -> Actions or click here:
-        # https://github.com/collective/icalendar/settings/variables/actions
+        # https://github.com/PyCalendar/icalendar/settings/variables/actions
         # -> Variables -> UV_VERSION
         version: "${{ vars.UV_VERSION }}"
         python-version: "3.14"

.pre-commit-config.yaml

@@ -1,7 +1,7 @@
 default_install_hook_types: [pre-commit, prepare-commit-msg, post-commit]
 
 repos:
-  - repo: https://github.com/pycalendar/ai-prompt-auto-commit
+  - repo: https://github.com/PyCalendar/ai-prompt-auto-commit
     rev: v0.0.10
     hooks:
       - id: prepare-ai-repository

.well-known/funding-manifest-urls

@@ -1 +1 @@
-https://github.com/collective/icalendar/raw/main/funding.json
+https://github.com/PyCalendar/icalendar/raw/main/funding.json

README.rst

@@ -12,11 +12,11 @@ icalendar supports multiple timezone implementations, including `zoneinfo <https
 ----
 
 :Homepage: https://icalendar.readthedocs.io/en/stable/
-:Discussions: https://github.com/collective/icalendar/discussions
-:Issues: https://github.com/collective/icalendar/issues
-:Code: https://github.com/collective/icalendar
+:Discussions: https://github.com/PyCalendar/icalendar/discussions
+:Issues: https://github.com/PyCalendar/icalendar/issues
+:Code: https://github.com/PyCalendar/icalendar
 :Dependencies: `python-dateutil <https://pypi.org/project/python-dateutil/>`_ and `tzdata <https://pypi.org/project/tzdata/>`_.
-:License: `2-Clause BSD License <https://github.com/collective/icalendar/blob/main/LICENSE.rst>`_
+:License: `2-Clause BSD License <https://github.com/PyCalendar/icalendar/blob/main/LICENSE.rst>`_
 :Contribute: `Contribute to icalendar <https://icalendar.readthedocs.io/en/latest/contribute/index.html>`_
 :Funding: `Open Collective <https://opencollective.com/python-icalendar>`_
 :icalendar chat: https://matrix.to/#/%23icalendar:chat.pycal.org
@@ -29,7 +29,7 @@ icalendar supports multiple timezone implementations, including `zoneinfo <https
     :target: https://pypi.org/project/icalendar/
     :alt: Python package version on PyPI
 
-.. image:: https://img.shields.io/github/v/release/collective/icalendar
+.. image:: https://img.shields.io/github/v/release/PyCalendar/icalendar
     :target: https://pypi.org/project/icalendar/#history
     :alt: Latest release
 
@@ -41,16 +41,16 @@ icalendar supports multiple timezone implementations, including `zoneinfo <https
     :target: https://pypistats.org/packages/icalendar
     :alt: Downloads from PyPI
 
-.. image:: https://img.shields.io/github/actions/workflow/status/collective/icalendar/tests.yml?branch=main&label=main&logo=github
-    :target: https://github.com/collective/icalendar/actions/workflows/tests.yml?query=branch%3Amain
+.. image:: https://img.shields.io/github/actions/workflow/status/PyCalendar/icalendar/tests.yml?branch=main&label=main&logo=github
+    :target: https://github.com/PyCalendar/icalendar/actions/workflows/tests.yml?query=branch%3Amain
     :alt: GitHub Actions build status for main
 
 .. image:: https://readthedocs.org/projects/icalendar/badge/?version=latest
     :target: https://icalendar.readthedocs.io/en/latest/
     :alt: Documentation status
 
-.. image:: https://coveralls.io/repos/github/collective/icalendar/badge.svg?branch=main
-    :target: https://coveralls.io/github/collective/icalendar?branch=main
+.. image:: https://coveralls.io/repos/github/PyCalendar/icalendar/badge.svg?branch=main
+    :target: https://coveralls.io/github/PyCalendar/icalendar?branch=main
     :alt: Test coverage
 
 .. image:: https://img.shields.io/endpoint?url=https://raw.githubusercontent.com/astral-sh/ruff/main/assets/badge/v2.json

SECURITY.md

@@ -3,8 +3,8 @@
 This security policy describes how to privately report _potential_ security issues with icalendar, and how the icalendar security team processes reports, all in a responsible manner.
 If you're unsure whether your issue qualifies as a security vulnerability, it's better to err on the side of caution and report it as one, allowing the icalendar security team to evaluate its merits and determine whether it's one.
 
--   [Report a _potential_ security issue](https://github.com/collective/icalendar/security/advisories/new).
--   [Security advisories](https://github.com/collective/icalendar/security/advisories)
+-   [Report a _potential_ security issue](https://github.com/PyCalendar/icalendar/security/advisories/new).
+-   [Security advisories](https://github.com/PyCalendar/icalendar/security/advisories)
 
 
 ## Supported versions
@@ -27,17 +27,17 @@ Once verified and fixed, the following steps will be taken:
     If it is compliant, they will submit it to the MITRE Corporation to generate a [CVE](https://www.cve.org/).
     This in turn submits the CVE to the [National Vulnerability Database (NVD)](https://nvd.nist.gov/vuln/search).
     GitHub notifies the team of their decision.
--   Assuming it is compliant, the team then publishes the [Security Advisory](https://github.com/collective/icalendar/security/advisories) on GitHub, which triggers the next steps.
+-   Assuming it is compliant, the team then publishes the [Security Advisory](https://github.com/PyCalendar/icalendar/security/advisories) on GitHub, which triggers the next steps.
 -   GitHub will publish the CVE to the CVE List.
 -   GitHub will broadcast the Security Advisory via the [GitHub Advisory Database](https://github.com/advisories).
 -   GitHub will send [security alerts](https://docs.github.com/en/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies) to all repositories that use icalendar and have opted into security alerts.
     This includes Dependabot alerts.
 -   The team will make a bug-fix release.
 -   The team will send an announcement through the usual channels:
 
-    - the [change log](https://github.com/collective/icalendar/CHANGES.rst)
-    - the [GitHub releases of icalendar](https://github.com/collective/icalendar/releases)
-    - [icalendar Discussions Announcements](https://github.com/collective/icalendar/discussions/categories/announcements)
+    - the [change log](https://github.com/PyCalendar/icalendar/blob/main/CHANGES.rst)
+    - the [GitHub releases of icalendar](https://github.com/PyCalendar/icalendar/releases)
+    - [icalendar Discussions Announcements](https://github.com/PyCalendar/icalendar/discussions/categories/announcements)
     - [icalendar Open Collective conversations](https://opencollective.com/python-icalendar/conversations)
     - [Plone's Security Announcements](https://plone.org/security/announcements)
     - [Plone Community Forum Announcements](https://community.plone.org/c/announcements/27)

docs/_include/configure-git-steps.inc

@@ -1,4 +1,4 @@
-#.  Start by `forking icalendar's repository <https://github.com/collective/icalendar/fork>`_ to your account through the GitHub interface.
+#.  Start by `forking icalendar's repository <https://github.com/PyCalendar/icalendar/fork>`_ to your account through the GitHub interface.
 
     .. seealso::
 

docs/_include/configure-git.inc

@@ -1,7 +1,7 @@
 Configure Git
 -------------
 
-Unless you're a maintainer or administrator, you don't have write access to push commits to GitHub repositories under the Collective organization or the icalendar repository.
+Unless you're a maintainer or administrator, you don't have write access to push commits to GitHub repositories under the PyCalendar organization or the icalendar repository.
 You can, however, push commits to your fork.
 Thus, a typical workflow will be circular in nature.
 You'll pull code from the upstream icalendar repository, push your work from your local clone to your remote fork, then make a pull request from your fork to the upstream icalendar repository.

docs/_templates/404.html

@@ -13,7 +13,7 @@ <h1>Page not found</h1>
     <h2>Why is this happening?</h2>
     <p>
         The icalendar documentation team has restructured documentation to redirect visitors to the most current and accurate information, archive previous versions, and identify outdated pages.
-        If you would like to report an issue or request a redirect be set up, you can <a href="https://github.com/collective/icalendar/issues/new?template=bug_report.md" rel="external">create a new issue in the GitHub issue tracker</a>.
+        If you would like to report an issue or request a redirect be set up, you can <a href="https://github.com/PyCalendar/icalendar/issues/new?template=bug_report.md" rel="external">create a new issue in the GitHub issue tracker</a>.
     </p>
 </div>
 

docs/conf.py

@@ -69,7 +69,7 @@
     "icon_links": [
         {
             "name": "GitHub",
-            "url": "https://github.com/collective/icalendar",
+            "url": "https://github.com/PyCalendar/icalendar",
             "icon": "fa-brands fa-square-github",
             "type": "fontawesome",
             "attributes": {
@@ -109,7 +109,7 @@
 }
 html_context = {
     #     "github_url": "https://github.com", # or your GitHub Enterprise site
-    "github_user": "collective",
+    "github_user": "PyCalendar",
     "github_repo": "icalendar",
     "github_version": "main",
     "doc_path": "docs",
@@ -129,16 +129,16 @@
     # Ignore pages that require authentication
     r"https://app.readthedocs.org/dashboard/icalendar/users/create/",
     r"https://docutils.sourceforge.io/rst.html",
-    r"https://github.com/collective/icalendar/fork",
-    r"https://github.com/collective/icalendar/issues/new",
-    r"https://github.com/collective/icalendar/settings/",
+    r"https://github.com/PyCalendar/icalendar/fork",
+    r"https://github.com/PyCalendar/icalendar/issues/new",
+    r"https://github.com/PyCalendar/icalendar/settings/",
     r"https://groups.google.com/g/icalendar-coc/",
     r"https://pypi.org/manage/project/icalendar/collaboration/",
     # Ignore specific anchors
     r"https://github.com/actions/python-versions#support-policy",
-    r"https://github.com/collective/icalendar/blob/7ca9db18c0847d1530520e01baf75f8ab8f4fa06/pyproject.toml#L32",
-    r"https://github.com/collective/icalendar/blob/main/CODE_OF_CONDUCT.md#enforcement",
-    r"https://github.com/collective/icalendar/blob/main/README.rst#related-projects",
+    r"https://github.com/PyCalendar/icalendar/blob/7ca9db18c0847d1530520e01baf75f8ab8f4fa06/pyproject.toml#L32",
+    r"https://github.com/PyCalendar/icalendar/blob/main/CODE_OF_CONDUCT.md#enforcement",
+    r"https://github.com/PyCalendar/icalendar/blob/main/README.rst#related-projects",
     r"https://up-for-grabs.net/#/filters",
     # Ignore links that are unstable
     r"https://www.unicode.org/cldr/cldr-aux/charts/29/supplemental/zone_tzid.html",
@@ -227,7 +227,7 @@
 
 
 # -- sphinx_issues configuration ----------------------------------
-issues_github_path = "collective/icalendar"
+issues_github_path = "PyCalendar/icalendar"
 
 
 # -- sphinx_reredirects configuration ----------------------------------
@@ -240,9 +240,9 @@
     "credits": "contribute/credits.html",
     "contributing": "contribute/index.html",
     "install": "how-to/install.html",
-    "license": "https://github.com/collective/icalendar/blob/main/LICENSE.rst",
+    "license": "https://github.com/PyCalendar/icalendar/blob/main/LICENSE.rst",
     "maintenance": "contribute/maintenance.html",
-    "security": "https://github.com/collective/icalendar/blob/main/SECURITY.md",
+    "security": "https://github.com/PyCalendar/icalendar/blob/main/SECURITY.md",
     "usage": "how-to/usage.html",
 }
 

docs/contribute/credits.rst

@@ -28,9 +28,9 @@ Contributors
 
 Become part of the list of :doc:`contributors <index>`.
 
-.. image:: https://contrib.rocks/image?repo=collective/icalendar&max=120&columns=10
+.. image:: https://contrib.rocks/image?repo=PyCalendar/icalendar&max=120&columns=10
     :alt: icalendar contributors
-    :target: https://github.com/collective/icalendar/graphs/contributors
+    :target: https://github.com/PyCalendar/icalendar/graphs/contributors
     :loading: lazy
 
 

docs/contribute/development.rst

@@ -76,7 +76,7 @@ You can automate this by using the :program:`ai-prompt-auto-commit` hooks.
 
 If you use :program:`Claude Code`, recording is automatic, once the repository is prepared.
 For other AI tools, you may need to manually record prompts or instruct the AI to do so.
-Consider adding support for your AI tool in the `project repository <https://github.com/pycalendar/ai-prompt-auto-commit>`_.
+Consider adding support for your AI tool in the `project repository <https://github.com/PyCalendar/ai-prompt-auto-commit>`_.
 
 Contributors to icalendar are encouraged to use prek.
 Any issues that would be caught by prek shall be caught by GitHub workflows when you push commits to a pull request for icalendar.

docs/contribute/documentation/build-check.rst

@@ -24,9 +24,9 @@ This chapter describes how to build and check the quality of documentation.
 File locations
 --------------
 
-Narrative documentation files are located in the `docs <https://github.com/collective/icalendar/tree/main/docs>`_ directory.
+Narrative documentation files are located in the `docs <https://github.com/PyCalendar/icalendar/tree/main/docs>`_ directory.
 
-:doc:`API reference documentation files </reference/api/icalendar>` are located in the `src <https://github.com/collective/icalendar/tree/main/docs>`_ directory.
+:doc:`API reference documentation files </reference/api/icalendar>` are located in the `src <https://github.com/PyCalendar/icalendar/tree/main/docs>`_ directory.
 
 
 .. _documentation-make-commands:

docs/contribute/documentation/index.rst

@@ -25,15 +25,15 @@ Find open issues to work on by clicking either button below.
 
     .. grid-item::
 
-        .. button-link:: https://github.com/collective/icalendar/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22doc%22
+        .. button-link:: https://github.com/PyCalendar/icalendar/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22doc%22
             :color: success
             :shadow:
 
             Documentation
 
     .. grid-item::
 
-        .. button-link:: https://github.com/collective/icalendar/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22good%20first%20issue%22
+        .. button-link:: https://github.com/PyCalendar/icalendar/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22good%20first%20issue%22
             :color: primary
             :shadow:
 

docs/contribute/documentation/small-edits.rst

@@ -9,8 +9,8 @@ For small edits to the documentation, use the GitHub web interface.
 #.  On every page in documentation, on the right-hand side, there is a link :guilabel:`Edit on GitHub`.
     When you click that link, you'll be taken to GitHub's web interface where you can edit files.
 
-    Alternatively, for narrative documentation files, you can navigate into the `docs <https://github.com/collective/icalendar/tree/main/docs>`_ directory to find the source file to edit.
-    For :doc:`API reference documentation files </reference/api/icalendar>`, you can instead navigate into the `src <https://github.com/collective/icalendar/tree/main/docs>`_ directory.
+    Alternatively, for narrative documentation files, you can navigate into the `docs <https://github.com/PyCalendar/icalendar/tree/main/docs>`_ directory to find the source file to edit.
+    For :doc:`API reference documentation files </reference/api/icalendar>`, you can instead navigate into the `src <https://github.com/PyCalendar/icalendar/tree/main/docs>`_ directory.
     For either file type, you can then click the :guilabel:`pencil icon` to edit the file in the browser.
 
     .. image:: /_static/edit-pencil-icon.png

docs/contribute/documentation/style-guide.rst

@@ -294,8 +294,8 @@ The following docstrings items are the most frequently used in icalendar, althou
 
     ..  seealso::
 
-        - `Document __new__ methods <https://github.com/collective/icalendar/issues/1118>`_
-        - `Merge __init__ or __new__ docstrings into their class's docstring <https://github.com/collective/icalendar/issues/1620>`_
+        - `Document __new__ methods <https://github.com/PyCalendar/icalendar/issues/1118>`_
+        - `Merge __init__ or __new__ docstrings into their class's docstring <https://github.com/PyCalendar/icalendar/issues/1620>`_
 
 Summary
     Docstrings must begin with a one-line summary of the Python object, terminated by a period.