Cleaning up for first merge to main

Author: carl-adams-planet

.github/workflows/release-build.yml

@@ -43,25 +43,28 @@ jobs:
           name: planet-auth-src-targz
           path: dist/planet_auth*.tar.gz
 
-  build-docs:
-    name: "Build Documentation Packages"
-    runs-on: ubuntu-latest
-    steps:
-      - name: "Checkout code"
-        uses: actions/checkout@v4
-      - name: Prepare common Python build environment
-        uses: ./.github/actions/python-build-env-setup
-        with:
-          python-version: ${{ env.PYTHON_VERSION }}
-      # - name: "Pull Build Number"
-      #   uses: ./.github/actions/version-dot-buildnum-fetch
-      #   with:
-      #     version-file: version-with-buildnum.txt
-      - name: "Nox: MKDocs Build"
-        run: |
-          nox -s mkdocs_build
-      - name: "Save Artifacts - MkDocs"
-        uses: actions/upload-artifact@v4
-        with:
-          name: planet-auth-mkdocs-site
-          path: site/**
+  # Not building this as a release artifact at this time.
+  # Docs are published to ReadTheDocs through other mechanisms.
+  #
+  # build-docs:
+  #   name: "Build Documentation Packages"
+  #   runs-on: ubuntu-latest
+  #   steps:
+  #     - name: "Checkout code"
+  #       uses: actions/checkout@v4
+  #     - name: Prepare common Python build environment
+  #       uses: ./.github/actions/python-build-env-setup
+  #       with:
+  #         python-version: ${{ env.PYTHON_VERSION }}
+  #     # - name: "Pull Build Number"
+  #     #   uses: ./.github/actions/version-dot-buildnum-fetch
+  #     #   with:
+  #     #     version-file: version-with-buildnum.txt
+  #     - name: "Nox: MKDocs Build"
+  #       run: |
+  #         nox -s mkdocs_build
+  #     - name: "Save Artifacts - MkDocs"
+  #       uses: actions/upload-artifact@v4
+  #       with:
+  #         name: planet-auth-mkdocs-site
+  #         path: site/**

.github/workflows/release-orchestrate.yml

@@ -4,10 +4,7 @@ permissions:
   actions: read
   contents: read
 
-# TODO: insure we can only release from privileged branches/tags?
-
 on:
-  # push:  # Just for testing  FIXME: Remove this.
   workflow_dispatch:
     inputs:
       build-variant:

.github/workflows/release-publish.yml

@@ -21,35 +21,8 @@ env:
   PYTHON_VERSION: "3.13"
 
 jobs:
-  # release-checkpoint:
-  #   name: "Final Release Checkpoint"
-  #   runs-on: ubuntu-latest
-  #   permissions:
-  #     actions: read
-  #     contents: write
-  #   # TODO: Gate actual prod deployment on a manual approval to bonk.
-  #   steps:
-  #     # - name: "Checkout code"
-  #     #   uses: actions/checkout@v4
-  #     # - name: "Prepare common Python build environment"
-  #     #   uses: ./.github/actions/python-build-env-setup
-  #     #   with:
-  #     #     python-version: ${{ env.PYTHON_VERSION }}
-  #     - name: "Record Release Tag"
-  #       # While we drop tags at the beginning of the release pipeline, we also record
-  #       # that we published the release here at the end of the release pipeline.
-  #       # Tests could fail, and this should record that difference between attempting
-  #       # a release, and publishing a release.
-  #       run: |
-  #         set -x
-  #         git config --global user.email "planet-auth-python-github-cicd@planet.com"
-  #         git config --global user.name  "CICD for github repository ${GITHUB_REPOSITORY}"
-  #         git tag -a -m "test tag comment" "release-${{inputs.version-with-buildnumber}}"
-  #         git push origin                  "release-${{inputs.version-with-buildnumber}}"
-
   release-pypi-test:
     name: "Release package to PyPi (Test)"
-    # needs: release-checkpoint
     runs-on: ubuntu-latest
     # environment: staging
     steps:
@@ -85,7 +58,6 @@ jobs:
 
   release-pypi-production:
     name: "Release package to PyPi (Production)"
-    # needs: release-checkpoint
     runs-on: ubuntu-latest
     # environment: staging
     steps:

CONTRIBUTING.md

@@ -0,0 +1 @@
+TODO: document submitting tickets and PRs.  We will likely lean on the SDK process.

DEVELOPMENT.md

@@ -0,0 +1,28 @@
+# Development
+
+## Development Tools
+All packages needed for different facets of development are specified as
+"extra" packages.  Each of these may be installed using `pip`.  For example,
+the following would install the extra packages needed for the operation of
+the code samples in the documentation:
+
+```console
+pip install planet-auth[examples]
+```
+
+The following extra packages have been defined:
+* `build` - Packages needed to build distribution packages.
+* `docs` - Packages needed to build the documentation.
+* `test` - Packages needed to run all the test and linting suites.
+* `examples` - Packages needed by example code.
+* `dev` - Meta package that combines `build`, `docs`, and `test`.
+
+## Nox
+[Nox](https://nox.thea.codes/) is the preferred mechanism for performing all
+common development activities.  This includes running unit tests, linting,
+code formatting, and static analysis.
+
+For a complete list of supported activities, list nox sessions.:
+```console
+nox -l
+```

README.md

@@ -0,0 +1,36 @@
+# Planet Auth Utility Library
+
+The Planet Auth Library provides generic authentication utilities for clients
+and for services.  For clients, it provides means to obtain access tokens that
+can be used to access network services.  For services, it provides tools to
+validate the same access tokens.
+
+The [Planet SDK for Python](https://developers.planet.com/docs/pythonclient/)
+leverages this library, and is pre-configured for the Planet Cloud Service used
+by customers.
+
+## Installation and Quick Start
+
+The Planet Auth Library for Python is [hosted on PyPI](https://pypi.org/project/planet-auth/)
+and can be installed via:
+
+```console
+pip install planet-auth
+```
+
+To install from source, first clone this repository, then navigate to the
+root directory (where [`pyproject.toml`](./pyproject.toml) lives) and run:
+
+```console
+pip install .
+```
+
+## Using the Planet Auth Library
+See the developer documentation at [Planet Auth on Read The Docs](TBD).
+
+## Development
+See [DEVELOPMENT](./DEVELOPMENT.md) for details on library development.
+
+## Releasing
+
+The release process is outlined in [RELEASE](RELEASE.md).