Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create 2024-sd-jwt-kotlin-annual.md #171

Merged
merged 5 commits into from
Oct 29, 2024
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
39 changes: 39 additions & 0 deletions docs/projects/reviews/2024/2024-sd-jwt-kotlin-annual.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,39 @@
# 2024 sd-jwt-kotlin (SD-JWT Implementation)

## Project Health

The main focus of this project was to provide a Kotlin implementation for the
IETF SD-JWT draft. However, the project remain without any updates for a while and
tkuhrt marked this conversation as resolved.
Show resolved Hide resolved
the maintainer decided to post an announcement stating this project is no longer maintained.
However during TAC meeting for annual review, there was a volunteer stepped up to
take care of this project.


## Maintainer Diversity

As before, the project is maintained by a single maintainer.
It's expected to have a single maintainer for the next year as well.

## Project Adoption

This project was used by German Bundesdruckerei but not sure they are still using.

## Goals

### Performance Against Prior Goals

The project implemented with success to it's initial goal but not well maintained or used.
tkuhrt marked this conversation as resolved.
Show resolved Hide resolved

### Next Year's Goals

This project aims to have a cloned copy of eudi-reference-wallet-sdjwt to have every language
implementation stays under OWF umbrella.
Comment on lines +29 to +30
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Based on the discussion in the July 10th TAC meeting, it is important to note whether this will be a fork or a mirror. If it is a fork, how will it be different? If it is a mirror, is there a need for it or should we only have the redirect in the README?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Mirror to the EUDI repo


## Help Required

The project is maintainable with one maintainer and no further aid is needed.
We are planning to automate the process (maybe using github actions).
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Might be worth adding this as a goal for next year (although, at the same time, you may be asking for help from the community for automating).

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Goal


## Project Lifecycle Stage Recommendation

The project is recommended to remain in the Labs stage.