remove release procedure PR template, my username --> NOAA-GFDL everywhere i can find it

ilaflott · ilaflott · commit 0d94e5024d52 · 2026-04-27T13:13:30.000-04:00
diff --git a/.codecov.yml b/.codecov.yml
@@ -1,4 +1,4 @@
-# Codecov configuration for ilaflott/fremorizer
+# Codecov configuration for NOAA-GFDL/fremorizer
 # Reference: https://docs.codecov.com/docs/codecovyml-reference
 
 coverage:
diff --git a/.github/PULL_REQUEST_TEMPLATE/release_procedure.md b/.github/PULL_REQUEST_TEMPLATE/release_procedure.md
diff --git a/.github/workflows/publish_conda.yml b/.github/workflows/publish_conda.yml
@@ -28,7 +28,7 @@ jobs:
           activate-environment: base
           conda-remove-defaults: true
           miniforge-version: latest
-          channels: conda-forge,noaa-gfdl,ilaflott
+          channels: conda-forge,noaa-gfdl
 
       - name: Configure Conda
         run: |
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -1,8 +1,8 @@
 ## **For Developers**
 
 * Developers are free to use this repository's `README.md` to familiarize with the CLI and save time from having to install any dependencies, but development within a Conda environment is heavily recommended regardless
-* Gain access to the repository with `git clone --recursive git@github.com:ilaflott/fremorizer.git` or your fork's link (recommended) and an SSH RSA key
-    - Once inside the repository, developers can test local changes by running a `pip install .` inside of the root directory after activating a virtual environment, installing the fremorizer package locally with the newest local changes on top of the installed Conda fremorizer dependencies. the `-e` flag can be used for an editable installation
+* Gain access to the repository with `git clone --recursive git@github.com:NOAA-GFDL/fremor.git` or your fork's link (recommended) and an SSH RSA key
+    - Once inside the repository, developers can test local changes by running a `pip install .` inside of the root directory after activating a virtual environment, installing the fremor package locally with the newest local changes on top of the installed Conda fremor dependencies. the `-e` flag can be used for an editable installation
     - Test as a normal user would use the CLI
 * Create a GitHub issue to reflect your contribution's background and reference it with Git commits
 
@@ -13,10 +13,10 @@ With few exceptions, pull requests always require an issue.
 ### **Adding Tools From Other Repositories**
 
 * Currently, the solution to this task is to approach it using Conda packages. The tool that is being added must reside within a repository that contains a meta.yaml that includes Conda dependencies like the one in this repository and ideally a setup.py (may be subject to change due to deprecation) that may include any potentially needed pip dependencies
-    - Once published as a Conda package, ideally on the [NOAA-GFDL channel](https://anaconda.org/NOAA-GFDL), an addition can be made to the "run" section under the "requirements" category in the meta.yaml of the fremorizer following the syntax `channel::package`
-    - On pushes to the main branch, the [package](https://anaconda.org/ilaflott/fremorizer) will automatically be updated using the workflow file
+    - Once published as a Conda package, ideally on the [NOAA-GFDL channel](https://anaconda.org/NOAA-GFDL), an addition can be made to the "run" section under the "requirements" category in the meta.yaml of the fremor following the syntax `channel::package`
+    - On pushes to the main branch, the [package](https://anaconda.org/NOAA-GFDL/fremor) will automatically be updated using the workflow file
  
 ### **MANIFEST.in**
 
-* In the case where non-python files like templates, examples, and outputs are to be included in the fremorizer package, MANIFEST.in can provide the solution. Ensure that the file exists within the correct folder, and add a line to the MANIFEST.in following [this syntax](https://setuptools.pypa.io/en/latest/userguide/miscellaneous.html)
+* In the case where non-python files like templates, examples, and outputs are to be included in the fremor package, MANIFEST.in can provide the solution. Ensure that the file exists within the correct folder, and add a line to the MANIFEST.in following [this syntax](https://setuptools.pypa.io/en/latest/userguide/miscellaneous.html)
 
diff --git a/README.md b/README.md
@@ -1,40 +1,40 @@
-# `fremorizer` / `fremor`
-`fremorizer` CMORizes FRE output with `CMOR`. It is a `conda` package and it's documentation can be found on
-[`readthedocs`](https://fremorizer.readthedocs.io/en/latest/).
+# `fremor`
+`fremor` CMORizes FRE output with `CMOR`. It is a `conda` package and it's documentation can be found on
+[`readthedocs`](https://fremor.readthedocs.io/en/latest/).
 
-[![Anaconda-Server Badge](https://anaconda.org/ilaflott/fremorizer/badges/version.svg)](https://anaconda.org/ilaflott/fremorizer)
-[![Anaconda-Server Badge](https://anaconda.org/ilaflott/fremorizer/badges/latest_release_date.svg)](https://anaconda.org/ilaflott/fremorizer)
-[![Anaconda-Server Badge](https://anaconda.org/ilaflott/fremorizer/badges/latest_release_relative_date.svg)](https://anaconda.org/ilaflott/fremorizer)
+[![Anaconda-Server Badge](https://anaconda.org/NOAA-GFDL/fremor/badges/version.svg)](https://anaconda.org/NOAA-GFDL/fremor)
+[![Anaconda-Server Badge](https://anaconda.org/NOAA-GFDL/fremor/badges/latest_release_date.svg)](https://anaconda.org/NOAA-GFDL/fremor)
+[![Anaconda-Server Badge](https://anaconda.org/NOAA-GFDL/fremor/badges/latest_release_relative_date.svg)](https://anaconda.org/NOAA-GFDL/fremor)
 
-[![pylint](https://img.shields.io/badge/pylint-%E2%89%A59.7-brightgreen)](https://github.com/ilaflott/fremorizer/actions/workflows/pylint.yml)
-[![codecov](https://codecov.io/gh/ilaflott/fremorizer/branch/main/graph/badge.svg)](https://codecov.io/gh/ilaflott/fremorizer)
+[![pylint](https://img.shields.io/badge/pylint-%E2%89%A59.7-brightgreen)](https://github.com/NOAA-GFDL/fremor/actions/workflows/pylint.yml)
+[![codecov](https://codecov.io/gh/NOAA-GFDL/fremor/branch/main/graph/badge.svg)](https://codecov.io/gh/NOAA-GFDL/fremor)
 
-[![publish_conda](https://github.com/ilaflott/fremorizer/actions/workflows/publish_conda.yml/badge.svg?branch=main)](https://github.com/ilaflott/fremorizer/actions/workflows/publish_conda.yml)
-[![readthedocs](https://app.readthedocs.org/projects/fremorizer/badge/?version=latest&style=flat)](https://fremorizer.readthedocs.io/en/latest/)
-[![pylint](https://github.com/ilaflott/fremorizer/actions/workflows/pylint.yml/badge.svg?branch=main)](https://github.com/ilaflott/fremorizer/actions/workflows/pylint.yml)
+[![publish_conda](https://github.com/NOAA-GFDL/fremor/actions/workflows/publish_conda.yml/badge.svg?branch=main)](https://github.com/NOAA-GFDL/fremor/actions/workflows/publish_conda.yml)
+[![readthedocs](https://app.readthedocs.org/projects/fremor/badge/?version=latest&style=flat)](https://fremor.readthedocs.io/en/latest/)
+[![pylint](https://github.com/NOAA-GFDL/fremor/actions/workflows/pylint.yml/badge.svg?branch=main)](https://github.com/NOAA-GFDL/fremor/actions/workflows/pylint.yml)
 
-`python3.11`:[![3.11](https://github.com/ilaflott/fremorizer/actions/workflows/create_test_conda_env.yml/badge.svg)](https://github.com/ilaflott/fremorizer/actions/workflows/create_test_conda_env.yml?query=branch%3Amain+python-version%3A3.11)
+`python3.11`:[![3.11](https://github.com/NOAA-GFDL/fremor/actions/workflows/create_test_conda_env.yml/badge.svg)](https://github.com/NOAA-GFDL/fremor/actions/workflows/create_test_conda_env.yml?query=branch%3Amain+python-version%3A3.11)
 
-`python3.12`:[![3.12](https://github.com/ilaflott/fremorizer/actions/workflows/create_test_conda_env.yml/badge.svg)](https://github.com/ilaflott/fremorizer/actions/workflows/create_test_conda_env.yml?query=branch%3Amain+python-version%3A3.12)
+`python3.12`:[![3.12](https://github.com/NOAA-GFDL/fremor/actions/workflows/create_test_conda_env.yml/badge.svg)](https://github.com/NOAA-GFDL/fremor/actions/workflows/create_test_conda_env.yml?query=branch%3Amain+python-version%3A3.12)
 
-`python3.13`:[![3.13](https://github.com/ilaflott/fremorizer/actions/workflows/create_test_conda_env.yml/badge.svg)](https://github.com/ilaflott/fremorizer/actions/workflows/create_test_conda_env.yml?query=branch%3Amain+python-version%3A3.13)
+`python3.13`:[![3.13](https://github.com/NOAA-GFDL/fremor/actions/workflows/create_test_conda_env.yml/badge.svg)](https://github.com/NOAA-GFDL/fremor/actions/workflows/create_test_conda_env.yml?query=branch%3Amain+python-version%3A3.13)
 
-`python3.14`:[![3.14](https://github.com/ilaflott/fremorizer/actions/workflows/create_test_conda_env.yml/badge.svg)](https://github.com/ilaflott/fremorizer/actions/workflows/create_test_conda_env.yml?query=branch%3Amain+python-version%3A3.14)
+`python3.14`:[![3.14](https://github.com/NOAA-GFDL/fremor/actions/workflows/create_test_conda_env.yml/badge.svg)](https://github.com/NOAA-GFDL/fremor/actions/workflows/create_test_conda_env.yml?query=branch%3Amain+python-version%3A3.14)
 
 
 
 ## Background and Purpose
-`fremorizer` is a model output rewriter (CMORizer) for FRE/FMS based models and output. `fremorizer` (or `fremor` for short) is
+`fremor` is a model output rewriter (CMORizer) for FRE/FMS based models and output. `fremor` (or `fremor` for short) is
 geared for standardizing NOAA-GFDL datasets for further quality control checks, assessments and data publishing pipelines in the
 context of CMIP7 using the [`CMOR`](https://cmor.llnl.gov/) library.
 
 ### Relationship to `fre-cli`
-`fremorizer` was originally the `fre.cmor` submodule of [`NOAA-GFDL/fre-cli`](https://github.com/NOAA-GFDL/fre-cli) and so stands
+`fremor` was originally the `fre.cmor` submodule of [`NOAA-GFDL/fre-cli`](https://github.com/NOAA-GFDL/fre-cli) and so stands
 on the shoulders of it's contributors, retaining it's general structure and lessons learned from it. Future re-integrations back 
 into `fre-cli`, as a formal package dependency, are being assessed.
 
 ### Contributors
-[![Contributors](https://contrib.rocks/image?repo=ilaflott/fremorizer)](https://github.com/ilaflott/fremorizer/graphs/contributors)
+[![Contributors](https://contrib.rocks/image?repo=NOAA-GFDL/fremor)](https://github.com/NOAA-GFDL/fremor/graphs/contributors)
 
 #### AI Disclaimer
 AI was heavily used in the creation of this repository, primarily `github`'s `copilot` with `Claude` (`opus4.6` `sonnet4.6`, and `haiku`), and `Gemini` and `Chat-GPT` models to a lesser extent, in agent mode. `Claude` and `Codex` agents have also contributed.
@@ -57,59 +57,59 @@ For development and testing, `pylint`, `pytest`, and `pytest-cov` are all highly
 If you're trying to gain access to `fremor` functionality as quickly as possible:
 ```bash
 # the current post-release in main
-module load fremorizer/test
+module load fremor/test
 
-# a tagged version of fremorizer, post-releases will never be named modules
-module load fremorizer/X.Y.Z
+# a tagged version of fremor, post-releases will never be named modules
+module load fremor/X.Y.Z
 ```
 
 
 ### via `conda`
-If you have a path to a `fremorizer` environment you can activate it like so:
+If you have a path to a `fremor` environment you can activate it like so:
 ```bash
-conda activate some/path/to/fremorizer_env
+conda activate some/path/to/fremor_env
 ```
 
-If you want your own `fremorizer` environment:
+If you want your own `fremor` environment:
 ```bash
-# the environment will be named fremorizer_en
-conda create -n fremorizer_env ilaflott::fremorizer
+# the environment will be named fremor_en
+conda create -n fremor_env NOAA-GFDL::fremor
 
-# see fremorizer_env in the list --> activate it by name
+# see fremor_env in the list --> activate it by name
 conda env list
-conda activate fremorizer_env
+conda activate fremor_env
 ```
 
 or, if you've already activated a `conda` environment
 ```bash
 conda create -n empty_env
 conda activate empty_env
-conda install -c ilaflott fremorizer
+conda install -c NOAA-GFDL fremor
 
 # equivalent syntax
-conda install ilaflott::fremorizer
+conda install NOAA-GFDL::fremor
 ```
 
 
 ### `pip` install source/checkout into a virtual environment (`conda`/`venv`)
-If you're trying to develop `fremorizer` capabilities, or edit the code to your liking in either a big or small way,
+If you're trying to develop `fremor` capabilities, or edit the code to your liking in either a big or small way,
 **this is for you**. This checks out the code, creates and activates an environment, installs into the environment,
 and runs all unit-tests and `pylint` checks:
 ```bash
 # omit --recursive if you don't want tables as submodules
-git clone --recursive https://github.com/ilaflott/fremorizer.git
-cd fremorizer
+git clone --recursive https://github.com/NOAA-GFDL/fremor.git
+cd fremor
 
 # create an environment and install the local checkout
 conda env create -f environment.yaml
-conda activate fremorizer
+conda activate fremor
 pip install -e . 
 
 # Run tests
-pytest fremorizer/tests/
+pytest fremor/tests/
 
 # Run linter
-pylint --rcfile pylintrc fremorizer/
+pylint --rcfile pylintrc fremor/
 ```
 
 
@@ -144,7 +144,7 @@ If you've used the previous `fre cmor` command, there is a direct mapping of syn
 # past fre-cli command
 fre -vv -l logfile.txt cmor <COMMAND> [OPTIONS]
 
-# fremorizer equivalent
+# fremor equivalent
 fremor -vv -l logfile.txt <COMMAND> [OPTIONS]
 ```
 
@@ -165,7 +165,7 @@ For an overview of required inputs and sample commands, see the [CMOR Quickstart
 
 ### WCRP Compliance Checking (under development)
 
-[![wcrp_compliance_check](https://github.com/ilaflott/fremorizer/actions/workflows/wcrp_compliance_check.yml/badge.svg?branch=main)](https://github.com/ilaflott/fremorizer/actions/workflows/wcrp_compliance_check.yml)
+[![wcrp_compliance_check](https://github.com/NOAA-GFDL/fremor/actions/workflows/wcrp_compliance_check.yml/badge.svg?branch=main)](https://github.com/NOAA-GFDL/fremor/actions/workflows/wcrp_compliance_check.yml)
 
 The `wcrp_compliance_check` workflow validates CMORized NetCDF outputs against WCRP project
 specifications using [cc-plugin-wcrp](https://github.com/ESGF/cc-plugin-wcrp), a plugin for
@@ -193,16 +193,16 @@ Apache License 2.0 — see [LICENSE.md](LICENSE.md)
 
 
 ## Releases and Versioning
-`fremorizer` uses a post-release scheme to identify development beyond the latest tagged version and tie the current `main` branch to a
+`fremor` uses a post-release scheme to identify development beyond the latest tagged version and tie the current `main` branch to a
 `conda` package versioned as `develop`. To avoid confusion with `fre-workflows` and `fre-cli`, which often demand that the version tags 
-match, `fremorizer`'s version format is `X.Y.Z[.post]`. 
+match, `fremor`'s version format is `X.Y.Z[.post]`. 
 
 
 ### new published release procedure 
 To publish new release carefully follow the below procedure:
 1. create a new branch off of `main`, which is already published to `conda` under `develop`/the previous tagged version + `.post`
-2. edit the version number in `fremorizer/_version.py` from the current one, to the desired version tag, remove `.post`, then open a PR. edit nothing else (usually).
+2. edit the version number in `fremor/_version.py` from the current one, to the desired version tag, remove `.post`, then open a PR. edit nothing else (usually).
 3. confirm the branch is functional by letting workflows finish, if you see green checks only, proceed. otherwise, stop and debug.
 4. draft a new release pointing to the PR branch, click release. the publishing workflow should trigger and finish, and you should see the `X.Y.Z` version in the conda channel.
 5. *releases in this repository are immutable*, **so even if the release workflow fails, breathe and move on to the next step.**
-6. edit the version number in `fremorizer/_version.py` to `X.Y.Z.post`, and merge the PR to main workflow steps passed. **`publish_conda`** will trigger again and upload what is in `main` under the `conda` version `develop` and `pip` version `X.Y.Z.post`
+6. edit the version number in `fremor/_version.py` to `X.Y.Z.post`, and merge the PR to main workflow steps passed. **`publish_conda`** will trigger again and upload what is in `main` under the `conda` version `develop` and `pip` version `X.Y.Z.post`
diff --git a/docs/contributing.rst b/docs/contributing.rst
@@ -19,7 +19,7 @@ Get your own copy of the code:
 
 .. code-block:: bash
 
-   git clone --recursive git@github.com:ilaflott/fremor.git
+   git clone --recursive git@github.com:NOAA-GFDL/fremor.git
 
 Or replace with your fork's link (recommended).
 
diff --git a/docs/contributing_to_docs.rst b/docs/contributing_to_docs.rst
@@ -3,13 +3,13 @@ A decent cheat-sheet for reStructuredText can be found
 `at this gist <https://gist.github.com/SMotaal/24006b13b354e6edad0c486749171a70#sections>`__.
 
 
-With a PR to ilaflott/fremor (recommended)
+With a PR to NOAA-GFDL/fremor (recommended)
 ----------------------------------------------
 
 This approach is the easiest and most automated option for open-source contributors. It is completely
 appropriate for casual editing of the docs and previewing the changes.
 
-* Make a branch, either with ``ilaflott/fremor`` as the remote, or your own fork.
+* Make a branch, either with ``NOAA-GFDL/fremor`` as the remote, or your own fork.
 * Edit a file any non-zero amount, commit that change to your branch, and push. If the branch is
   identical to ``main``, you cannot open a PR.
 * Once the PR is opened, a ``readthedocs`` workflow will be run, even if that PR is in draft mode.
diff --git a/docs/usage.rst b/docs/usage.rst
@@ -64,5 +64,5 @@ Additional Resources
 * `CMIP6 Tables <https://github.com/pcmdi/cmip6-cmor-tables>`_
 * `CMIP6 Controlled Vocabulary <https://github.com/WCRP-CMIP/CMIP6_CVs>`_
 * `PCMDI CMOR User Guide <http://cmor.llnl.gov/>`_
-* `fremor on GitHub <https://github.com/ilaflott/fremor>`_
+* `fremor on GitHub <https://github.com/NOAA-GFDL/fremor>`_
 * `fre-cli (upstream) <https://github.com/NOAA-GFDL/fre-cli>`_
diff --git a/fremor/_version.py b/fremor/_version.py
@@ -3,5 +3,5 @@
 """
 
 import os
-version = os.getenv("GIT_DESCRIBE_TAG", "0.9.0post")
+version = os.getenv("GIT_DESCRIBE_TAG", "0.9.0.post")
 __version__ = version
diff --git a/meta.yaml b/meta.yaml
@@ -58,7 +58,7 @@ test:
     - pytest --durations=5 --log-level DEBUG fremor/
 
 about:
-  home: https://github.com/ilaflott/fremorizer
+  home: https://github.com/NOAA-GFDL/fremorizer
   license: Apache-2.0
   license_file: LICENSE.md
   summary: Model output rewriter (CMORizer) for FRE/FMS based models

Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,4 @@`
`1`		`-# Codecov configuration for ilaflott/fremorizer`
	`1`	`+# Codecov configuration for NOAA-GFDL/fremorizer`
`2`	`2`	`# Reference: https://docs.codecov.com/docs/codecovyml-reference`
`3`	`3`
`4`	`4`	`coverage:`