Updates to Readme

.github/workflows/build.yml

@@ -1,7 +1,8 @@
 name: Build OpenAPI docs
 on:
-  - push
-  # - pull_request
+  push:
+  pull_request:
+      types: [opened, reopened, sychronize]
 jobs:
   docs-build:
     runs-on: ubuntu-latest
@@ -21,24 +22,5 @@ jobs:
         with:
           branch: gh-pages
           folder: .
-  deploy:
-    if: github.ref == 'refs/heads/master'  # Only run this job on the master branch
-    runs-on: ubuntu-latest
-    steps:
-      - name: Setup Node.js environment
-        uses: actions/setup-node@v4
-        with:
-          node-version: 14.x
-          # Comes with npm 6. For newer Node, encountered: https://github.com/npm/cli/issues/3359
-      - run: npm install -g @redocly/openapi-cli && npm install -g redoc-cli
-      - run: npm install -g gh-openapi-docs
-      - name: Check out repository code
-        uses: actions/checkout@v4
-      - run: gh-openapi-docs
-      - name: Deploy 🚀
-        uses: JamesIves/github-pages-deploy-action@v4
-        with:
-          branch: gh-pages
-          folder: . # Folder containing the built documentation
-          target-folder: docs/index.html # Deploy to docs/index.html if needed
-          clean: true
+          target-folder: ${{ github.ref == 'refs/heads/main' && 'docs/index.html' || '' }}  # Deploy to docs/index.html only if on main
+          clean: ${{ github.ref == 'refs/heads/main' }}  # Clean only if on the main branch

.github/workflows/ci.yml

@@ -1,7 +1,6 @@
 name: Lint and validate OpenAPI specs
 on:
-  - push
-  - pull_request_target
+  - pull_request
 jobs:
   lint:
     name: Lint OpenAPI definition
@@ -10,17 +9,16 @@ jobs:
       - name: Check out head branch
         uses: actions/checkout@v4
       - name: Run OpenAPI Lint Action
-        uses: nwestfall/openapi-action@v1.0.2
+        uses: mhiew/redoc-lint-github-action@v4
         with:
-          github_token: ${{ secrets.GITHUB_TOKEN }}
-          file: openapi/task_execution_service.openapi.yaml
+          args: 'openapi/task_execution_service.openapi.yaml'
   diff:
     name: Show OpenAPI differences relative to target branch
     runs-on: ubuntu-latest
     if: ${{ github.event_name == 'pull_request' }}
     steps:
       - name: Check out head branch
-        uses: aactions/checkout@v4
+        uses: actions/checkout@v4
         with:
           ref: ${{ github.ref }}
           path: head

CONTRIBUTING.md

@@ -13,7 +13,9 @@ Suggested changes to this schema can be initiated as [**Issues**](https://github
 
 Even those with write access to the main repository should in general create pull request branches within their own forks. This way when the main repository is forked again, the new fork is created with a minimum of extraneous volatile branches.
 
-> To facilitate review of external pull requests, users are encouraged to activate [**Travis CI**](https://travis-ci.org/) to monitor the build status (documentation, Swagger UI) of their fork. By following the documentation for [deployment to GitHub Pages](https://docs.travis-ci.com/user/deployment/pages/) and adding a `$GITHUB_TOKEN` environment variable to their repo configuration, pushes to the forked repo should be viewable relative to `https://[user-or-org].github.io/workflow-execution-service-schemas/preview/<branch>/`:
+
+> To facilitate the review of external pull requests, users are encouraged to activate [**GitHub Actions**](https://github.com/features/actions) to monitor the build status (documentation, Swagger UI) of their fork. By following the documentation for [deployment to GitHub Pages](https://docs.github.com/en/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site), pushes to the forked repository will be viewable at `https://[user-or-org].github.io/task-execution-service/preview/<branch>/`:
+
 
 + https://[user-or-org].github.io/task-execution-schemas/preview/\<branch\>/docs/
 + https://[user-or-org].github.io/task-execution-schemas/preview/\<branch\>/swagger-ui/
@@ -24,11 +26,4 @@ Even those with write access to the main repository should in general create pul
 
 If a security vulnerability is identified with the specification please send an email to [email protected] detailing your concerns.
 
-## Approving Changes
-
-### pre-TES v1.0.0 / Testbed Voting Procedure
-Changes for the release are to be approved by 2 TES specification leads.
-
-### post TES v1.0.0 Voting Procedure
-The post v1.0.0 voting group include stakeholders, such as server and client implementors.
-The membership of this group will be established as part of the v1.0.0 release.
+For more information please see the [Governance](GOVERNANCE.md) documentation.

GOVERNANCE.md

@@ -0,0 +1,23 @@
+TES Governance and Process
+==============================
+
+The Task Execution Service (TES) operates under a community-driven development model, where advancements to the specification occur exclusively through community contributions. The governance is steered by a core team of API champions that fosters collaboration and consensus among contributors. This team is tasked with overseeing the design and development processes, setting priorities, managing the release schedule, and making decisions in instances where consensus cannot be reached.
+
+Current API Product leads are:
+
+| Name               | Organization       | github                  |
+|:-------------------|:-------------|:------------------
+| Kyle Ellrot        | [Oregon Health and Science University](https://www.ohsu.edu/) | [kellrott](https://github.com/kellrott) |
+| Venkat Malladi     | [Microsoft](https://www.microsoft.com/en-us/genomics/)        | [vsmalladi](https://github.com/vsmalladi) |
+| Alex Kanitz        | [Swiss Institute of Bioinformatics / ELIXIR Switzerland](https://www.sib.swiss/)        | [uniqueg](https://github.com/uniqueg) |
+
+
+## Voting Procedure
+
+Voting group include stakeholders, such as server and client implementors.
+
+API Product leads review PR's on a reguarly cal (and also ping the mailing list), set a deadline by which drivers (and a few key non-drivers) need to respond by. Strive to reach consensus with our drivers and community. 
+
+Cloud Work Stream leads retain a veto if something goes off the rails.
+
+[GA4GH TES API mailing list](mailto:[email protected]): to stay updated about the latest news & developments around the TES API, in particular for soliciting comments on proposed spec changes and for notifications about TES subgroup meetings.