Added LICENSE

Author: nabobalis

LICENSE

@@ -0,0 +1,29 @@
+BSD 3-Clause License
+
+Copyright (c) 2021--2025, Scientific Python project
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions are met:
+
+1. Redistributions of source code must retain the above copyright notice, this
+   list of conditions and the following disclaimer.
+
+2. Redistributions in binary form must reproduce the above copyright notice,
+   this list of conditions and the following disclaimer in the documentation
+   and/or other materials provided with the distribution.
+
+3. Neither the name of the copyright holder nor the names of its
+   contributors may be used to endorse or promote products derived from
+   this software without specific prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
+AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
+FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
+SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
+CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
+OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
+OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

readme.md

@@ -1,19 +1,13 @@
 # SPEC 0 Version Action
 
-This repository contains a GitHub Action to generate the
+This repository contains a GitHub Action to generate the files required for the SPEC-0 documentation.
 
-### Drop Schedule
+## Using the action
 
-Below is an auto generated schedule with recommended dates for dropping support. We suggest that the next release in a given quarter is
-considered as the one removing support for a given item.
+## Automatically updating dependencies
 
-You may want to delay the removal of support of an older Python version until your package fully works on the newly released Python, thus keeping the number of supported minor versions of Python the same for your package.
-
-{{< include-md "schedule.md" >}}
-
-### Automatically updating dependencies
-
-To help projects stay compliant with this spec, we additionally provide a `schedule.json` file that can be used by CI systems to deterime new version boundaries. The structure of the file is as follows:
+To help projects stay compliant with this spec, we additionally provide a `schedule.json` file that can be used by CI systems to determine new version boundaries.
+The structure of the file is as follows:
 
 ```json
 [
@@ -26,7 +20,9 @@ To help projects stay compliant with this spec, we additionally provide a `sched
 ]
 ```
 
-All information in the json file is in a string format that should be easy to use. The date is the first timestamp of the relevant quarter. Thus a workflow for using this file could be:
+All information in the json file is in a string format that should be easy to use.
+The date is the first timestamp of the relevant quarter.
+Thus a workflow for using this file could be:
 
 1. fetch `schedule.json`
 2. determine maximum date that is smaller than current date
@@ -35,21 +31,18 @@ All information in the json file is in a string format that should be easy to us
 You can obtain the new versions you should set by using this `jq` expression:
 
 ```sh
-
 jq 'map(select(.start_date |fromdateiso8601 |tonumber  < now))| sort_by("start_date") | reverse | .[0].packages ' schedule.json
-
 ```
 
 If you use a package manager like pixi you could update the dependencies with a bash script like this:
 
 ```sh
 curl -Ls -o schedule.json https://raw.githubusercontent.com/scientific-python/specs/main/spec-0000/schedule.json
 for line in $(jq 'map(select(.start_date |fromdateiso8601 |tonumber  < now))| sort_by("start_date") | reverse | .[0].packages | to_entries | map(.key + ":" + .value)[]' --raw-output schedule.json); do
-	package=$(echo "$line" | cut -d ':' -f 1)
-	version=$(echo "$line" | cut -d ':' -f 2)
+  package=$(echo "$line" | cut -d ':' -f 1)
+  version=$(echo "$line" | cut -d ':' -f 2)
   if pixi list -x "^$package" &>/dev/null| grep "No packages" -q; then
-  	pixi add "$package>=$version";
+    pixi add "$package>=$version";
   fi
 done
-
 ```