No Project Lifecycle Badge found in your readme!

Hello! I scanned your readme and could not find a project lifecycle badge. A project lifecycle badge will provide contributors to your project as well as other stakeholders (platform services, executive) insight into the lifecycle of your repository.

What is a Project Lifecycle Badge?

It is a simple image that neatly describes your project's stage in its lifecycle. More information can be found in the project lifecycle badges documentation.

What do I need to do?

I suggest you make a PR into your README.md and add a project lifecycle badge near the top where it is easy for your users to pick it up :). Once it is merged feel free to close this issue. I will not open up a new one :)

The app is currently deloyed in the devex-von-prod namespace, it would make sense to migrate it to the ToIP OpenShift namespaces.

The app deployments need to be migrated to OCP4.

No special security policies are required, other than allowing ingress to the app's route, as this is a self-contained SPA.

Please deploy dev and test instances (no prod, see the param files already available) in our shared demo namespace a99fd4.

Once the apps have been deployed, please coordinate with me to update the settings in the relevant Keycloak realms.

Please merge the dependabot PRs and test that the app still works. Or should we archive this app?

Please address:

https://github.com/bcgov/law-society-demo/network/alert/a2a-demo/package-lock.json/moment/open

This issue is a kind reminder that your repository has been inactive for 180 days. Some repositories are maintained in accordance with business requirements that infrequently change thus appearing inactive, and some repositories are inactive because they are unmaintained.

To help differentiate products that are unmaintained from products that do not require frequent maintenance, repomountie will open an issue whenever a repository has not been updated in 180 days.

• If this product is being actively maintained, please close this issue.
• If this repository isn't being actively maintained anymore, please archive this repository. Also, for bonus points, please add a dormant or retired life cycle badge.

Thank you for your help ensuring effective governance of our open-source ecosystem!

TL;DR

Topics greatly improve the discoverability of repos; please add the short code from the table below to the topics of your repo so that ministries can use GitHub's search to find out what repos belong to them and other visitors can find useful content (and reuse it!).

Why Topic

In short order we'll add our 800th repo. This large number clearly demonstrates the success of using GitHub and our Open Source initiative. This huge success means its critical that we work to make our content as discoverable as possible; Through discoverability, we promote code reuse across a large decentralized organization like the Government of British Columbia as well as allow ministries to find the repos they own.

What to do

Below is a table of abbreviation a.k.a short codes for each ministry; they're the ones used in all @gov.bc.ca email addresses. Please add the short codes of the ministry or organization that "owns" this repo as a topic.

That's in, you're done!!!

How to use

Once topics are added, you can use them in GitHub's search. For example, enter something like org:bcgov topic:citz to find all the repos that belong to Citizens' Services. You can refine this search by adding key words specific to a subject you're interested in. To learn more about searching through repos check out GitHub's doc on searching.

Pro Tip 🤓

• If your org is not in the list below, or the table contains errors, please create an issue here.

• While you're doing this, add additional topics that would help someone searching for "something". These can be the language used javascript or R; something like opendata or data for data only repos; or any other key words that are useful.

• Add a meaningful description to your repo. This is hugely valuable to people looking through our repositories.

• If your application is live, add the production URL.

Ministry Short Codes

NOTE See an error or omission? Please create an issue here to get it remedied.

Provide a service that Issuers can use for the hosting of tails file needed for Credential Revocation.

One option is to tie this to TOB and only host tails files from Issuers registered with TOB. That allows for the use of the existing DID-Auth and endpoint security to be used to limit those writing to the service. The service would be open to readers - even though TOB would be the only reader initially.

Alternatively, we could allow any Issuer to write a tails file to the Service - independent of TOB. Issuers would have to register in some way - e.g. DID-Auth (separate from TOB), prove they own a Cred Def file, or it might even be possible to detect tails files based on their content and just use that.

What I like about the idea of having independent of TOB is that we can later separate the service and host it on a cheaper platform - e.g. a Cloud Service with cheaper storage.

Tasks:

• Discuss the options and settle on an approach
• Define a basic API
• Implement the design - presumably as a service within the TOB projects on OpenShift.