Re: Updating the DID method registry

On Fri, Jun 7, 2024 at 12:30 PM Phillip Shoemaker <phillip@identity.org>
wrote:

> Thanks Kevin, I completely agree. And if the DID method was deployed and
> maintained, I wouldn’t be asking this question. We are working with BNB on
> this and cannot deploy as is.
> - Never deployed
> - Nothing to maintain
> - Company is non-responsive and their GitHub is not touched in years
>
>
>    - No deployment -> Deprecate immediately
>
>
> How do we get to the above?
>
>
The registration process and registry probably needs some improvement to
help with this situation.
- The registry data files "status" field is somewhat useless right now as
they all are "registered" except for uport which is "deprecated".
- Improved flags or states should indicate if the method is in development
or actively deployed.
- Some of this involves good faith of method developers to accurately
indicate and update the status.  It's almost certain many of the
current methods authors had good intentions that didn't work out and they
are not in use anymore.  And I imagine updating a did method status is the
last thing on developers minds as a project winds down, especially if that
happens slowly over time.

One direction to take to figure out the process in this case is to try it
and see what happens:
- File a PR that removes the bnb method.
- Check github history and tag all the users that had related commits or
activity for that method.
- If related emails are available, send a message about the situation and
ask for a response to the PR.
- Add details on the rationale for the removal.  What was done to check for
activity or active use?  Who was contacted and when?
- What is the purpose of the removal?  Is it for general janitor reasons or
for reuse by another project?
- etc...

And then wait for at least a minimal reasonable time:
- If current maintainers or others respond, they may be fine with removal
and reuse, or have details on why not.
- If there is no response, and the community decides reasonable efforts
have been made, perhaps the removal can proceed.

As has been said, it's difficult to know for sure if removal would be ok.
But the community also should be pragmatic about not keeping unused
abandoned methods around forever.

-dave