WIP: Migration to new approach

.github/workflows/count.yml

@@ -0,0 +1,38 @@
+name: Count Files and Publish to badge-info
+
+on:
+  push:
+    branches:
+      - main
+      - angular
+
+permissions:
+  contents: write
+
+jobs:
+  count_files_and_publish_to_badgeinfo:
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+
+      - name: Count files in wallet folder
+        id: file_count
+        run: |
+          file_count=$(find wallets -type f | wc -l)
+          echo "wallet-count=$file_count" >> $GITHUB_OUTPUT
+
+      - name: Create JSON file
+        run: |
+          mkdir values
+          echo "{ \"schemaVersion\": 1, \"label\": \"Wallets\", \"message\": \"${{ steps.file_count.outputs.wallet-count }}\", \"color\": \"green\" }" > values/wallets.json
+
+      # Deploy to local repo
+      - name: Deploy
+        uses: s0/git-publish-subdir-action@develop
+        env:
+          REPO: self
+          BRANCH: badge-info
+          FOLDER: values
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

.github/workflows/main.yml

@@ -0,0 +1,92 @@
+name: Publish GitHub Pages
+
+on:
+  pull_request:
+    types:
+      - opened
+      - synchronize
+  push:
+    branches:
+      - main
+      - angular
+
+# Sets permissions of the GITHUB_TOKEN to allow deployment to GitHub Pages
+permissions:
+  contents: read
+  pages: write
+  id-token: write
+
+# Allow only one concurrent deployment, skipping runs queued between the run in-progress and latest queued.
+# However, do NOT cancel in-progress runs as we want to allow these production deployments to complete.
+concurrency:
+  group: 'pages'
+  cancel-in-progress: false
+
+jobs:
+  validate:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+
+      - name: Set up Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: 18
+
+      - name: Install dependencies
+        run: cd viewer && npm ci
+
+      #TODO: we are not validating the schemas of the data files yet.
+      # - name: Validate
+      #   run: cd viewer && npm run validate
+
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+
+      - name: Set up Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: 18
+
+      - name: Install dependencies
+        run: cd viewer && npm ci
+
+      - name: Build Angular app
+        run: cd viewer && npm run build -- --configuration production
+
+      - name: upload artifacts
+        uses: actions/upload-artifact@v4
+        with:
+          name: viewer
+          path: viewer/dist/browser
+
+  publish:
+    # only run on the main branch
+    if: github.ref == 'refs/heads/main'
+    needs: [validate, build]
+    runs-on: ubuntu-latest
+    environment:
+      name: github-pages
+      url: ${{ steps.deployment.outputs.page_url }}
+    steps:
+      - name: Download artifact from build job
+        uses: actions/download-artifact@v4
+        with:
+          name: viewer
+
+      - name: Setup Pages
+        uses: actions/configure-pages@v4
+
+      - name: Upload artifact
+        uses: actions/upload-pages-artifact@v1
+        with:
+          # Upload entire repository
+          path: '.'
+
+      - name: Deploy to GitHub Pages
+        id: deployment
+        uses: actions/deploy-pages@v2

MAINTAINERS.md

@@ -0,0 +1,30 @@
+# Maintainers
+
+| Maintainer        | GitHub ID       | Company Affiliation |
+| ----------------- | --------------- | ------------------- |
+| Maaike van Leuken | maaikevanleuken | TNO                 |
+| Samuel Rinnetmäki | samuelmr        | Findynet            |
+| Mirko Mollik      | cre8            | Fraunhofer FIT      |
+
+## 1. What Does Being a Maintainer Entail
+
+- Reviewing code contributions.
+- Managing issues and bugs.
+- Maintaining documentation.
+- Communicating with the community.
+- Managing version control.
+- Participating in project decisions.
+- Building and sustaining a contributor community.
+
+## 2. How to Become a Maintainer
+
+Before being considered as a maintainer, contributors should meet the following requirements:
+
+- A history of substantial and consistent contributions to the project.
+- A deep understanding of the project's goals, codebase, and best practices.
+- Active involvement in the community, including helping others and engaging in discussions.
+- Ultimately, the maintainers decide who will become the new maintainer through a majority vote.
+
+## 3. How Maintainers are Removed or Moved to Emeritus Status
+
+- Inactivity or consensus decision can lead to removal.

README.md

@@ -1,23 +1,67 @@
+//TODO: set correct path to repo
+![Wallets](https://img.shields.io/endpoint?url=https%3A%2F%2Fraw.githubusercontent.com%2Fcre8%2Fdigital-wallet-and-agent-overviews-sig%2Fbadge-info%2Fwallets.json)
+
 # Digital Wallet and Agent Overviews Special Interest Group (SIG)
 
-The objectives of this SIG is to further develop and maintain the Digital Wallet Overview and including the digital identity agents/SDKs in the overview. The overview can be found [here](https://openwallet-foundation.github.io/digital-wallet-and-agent-overviews-sig/). These overview should provide transparency of the characteristics of wallets and agents in order to allow for comparison and effective decision making on which wallet is applicable for your use case. By creating awareness of these overviews, this work can lead to less fragmentation of the SSI playing field and increase adoption.
+The objectives of this SIG is to further develop and maintain the Digital Wallet Overview and including the digital identity agents/SDKs in the overview. The overview can be found [here](https://openwallet-foundation.github.io/digital-wallet-and-agent-overviews-sig/). These overview should provide transparency of the characteristics of wallets and agents in order to allow for comparison and effective decision-making on which wallet is applicable for your use case. By creating awareness of these overviews, this work can lead to less fragmentation of the SSI playing field and increase adoption.
 
 This SIG was accepted by the TAC on [September 20, 2023](../meetings/2023/2023-09-20.md). See [Digital Wallet and Agent Overviews SIG Proposal](https://github.com/openwallet-foundation/tac/issues/56) for more details.
 
 ## Participating
+
 This SIG is an open group. Anyone in the OpenWallet Foundation community can join and participate. There is no formal sign up process. Just show up and participate.
 
-If you are interested in participating, please join the [OpenWallet Foundation Discord](https://discord.gg/openwalletfoundation) and participate in the discussion in the [#digital-wallet-and-agent-overviews-sig](https://discord.com/channels/1022962884864643214/1154111877077532814) channel. 
+If you are interested in participating, please join the [OpenWallet Foundation Discord](https://discord.gg/openwalletfoundation) and participate in the discussion in the [#digital-wallet-and-agent-overviews-sig](https://discord.com/channels/1022962884864643214/1154111877077532814) channel.
 
 Upcoming meetings:
+
 - November 16th, 7:00 AM PT / 16:00 CET
 - November 30th, 7:00 AM PT / 16:00 CET
 - December 14th, 7:00 AM PT / 16:00 CET
 
 ## Target Audience
+
 This overview should be usable by persons and organisations. Anyone willing to use digital wallets or agents for digital credential purposes should be able to objectively compare the characteristics of wallets/agents and create a short-list of candidates for their use case. It can also serve as resource for market awareness and visibility of wallets/agents for wallet/agent vendors.
 
 ## Scoping
+
 We use the terminilogy on digital credentials, wallets and agents as described in the [ToIP glossary](https://docs.google.com/document/d/1fZByfuSOwszDRkE7ARQLeElSYmVznoOyJK4sxRvJpyM/edit).
 
 Included in the overview are holder agents+wallets, issuer agents and verifier agents. Initially, we will only include wallets and agents that at least have the functionality to store and exchange digital credentials.
+
+## Connection to other OWF groups
+
+This SIG was accepted by the TAC on [September 20, 2023](../meetings/2023/2023-09-20.md). See [Digital Wallet and Agent Overviews SIG Proposal](https://github.com/openwallet-foundation/tac/issues/56) for more details.
+
+There is a strong connection with the credential format comparison SIG. The credential formats are incorporated as separate characterics (columns) in the overview, forming the basis of the technology stack.
+
+We foresee that the safe wallet SIG provided us with new characteristics in the category of 'Security'. 
+
+## Contributing
+
+### Why should I add my digital wallet or agent?
+
+We strive to create a comprehensive and unbiased platform where every provider can showcase their solution at no cost. Recognising the challenge in quantifying subjective aspects, such as user-friendliness, our focus is on objective parameters. These include resource links and compliance with specific standards, ensuring clear, fact-based comparisons. By allowing and encouraging community contributions through pull requests, we maintain an up-to-date and inclusive matrix. Your active participation by submitting updates or new entries is invaluable, as it not only ensures the overview is correct and complete, but also supports a more informed and diverse user base.
+
+### How can I add my digital wallet or agent?
+Contributing to the overview can be done through filling in the form provided when clicking "Add Wallet/agent" in the upper right corner of the overview (soon to be added). This creates the JSON that should be added to `wallets.json` via a pull request.
+
+## Participating
+This SIG is an open group. Anyone in the OpenWallet Foundation community can join and participate. There is no formal sign-up process. Just show up and participate.
+
+If you are interested in participating, please join the [OpenWallet Foundation Discord](https://discord.gg/openwalletfoundation) and participate in the discussion in the [#digital-wallet-and-agent-overviews-sig](https://discord.com/channels/1022962884864643214/1154111877077532814) channel. 
+### Upcoming meetings
+- February 22th, 2024
+- March 7th, 2024
+- March 21th, 2024
+- April 4th, 2024
+
+### Slides past meetings
+- [November 16, 2023](meetings/2023/16-11-2023.pdf)
+- [November 30, 2023](meetings/2023/30-11-2023.pdf)
+- [January 11, 2024](meetings/2024/11-01-2024.pdf)
+- [January 25, 2024](meetings/2024/25-01-2024.pdf)
+- [TAC quarterly update meeting, February 21st, 2024](https://docs.google.com/presentation/d/19jO1Mi4-7d8-XdjyuGsEjuiwH6KCb5We9S99tjYgSmQ/edit?usp=sharing)
+
+### Meeting recordings
+See the [LFX meetings](https://zoom-lfx.platform.linuxfoundation.org/meeting/92821499615?password=bfd9bdad-249d-454e-97a5-727bc5fc2190).