Ory is the largest open source community in the world for cloud software application security. We maintain advanced open source security software solving authentication, authorization, access control, application network security, and delegation. Ory implements a variety of industry and best-practice standards including OAuth 2.0 / OAuth 2.1, OpenID Connect, Zero Trust Networking, Google Zanzibar Policy Framework, FIDO2 U2F, WebAuthn, TOTP, and more.

Ory Community

Ah no, it's not that critical.
We are using ory/fosite in our product.
Also, we are using square/go-jose as well. But the library was archived, so we are trying to move to go-jose/go-jose, but can't move completely because there are some implementations for fosite interface.
So just curios about how ory want to deal with it. Is it acceptable for us to try to make a PR just for replacing square/go-jose by go-jose/go-jose?

Hey <@U01Q3LFENCW>
feel free to propose a plan of action in a “<https://github.com/ory/fosite/issues/new?assignees=&amp;labels=rfc&amp;template=DESIGN-DOC.yml|Design Document>” (the template should make it clear what to fill in) and once that is accepted by the maintainers you can put up a PR.
That would make the process smooth for all parties involved.
Thanks a lot for taking a look at it :raised_hands: