search

hyperledger / aries-rfcs

Hyperledger Aries is infrastructure for blockchain-rooted, peer-to-peer interactions
https://hyperledger.github.io/aries-rfcs/
Apache License 2.0
326 stars 217 forks source link

Add status STALLED and change status of many proposed RFCs #827

Closed swcurran closed 6 months ago

swcurran commented 7 months ago

We have many RFCs that are in the "Proposed" status that are very unlikely to be progressed any further. To clear them out so that people have a better view of the active work in Aries, a new status "STALLED" has been added, and the status of many proposed RFCs have been changed to either STALLED, DEMONSTRATED or ACCEPTED, as appropriate based on the work done on the RFCs.

STALLED differs from the RETIRED state in that STALLED is direct from PROPOSED, whereas RETIRED is from a more advanced state, where implementation work was done, evaluated and found to be no longer of use. STALLED just means that the idea never got beyond the idea stage.

Updated statuses:

JamesKEbert commented 7 months ago

I'm highly in favor of adding a stalled status. :+1:

Here's some additional RFCs I'd propose for status changes: ACCEPTED: features/0183-revocation-notification/README.md (it's included in AIPv2, so it should probably move to accepted--even though revocation notification v2 would be preferable for implementation) ACCEPTED: features/0721-revocation-notification-v2/README.md ACCEPTED: features/0685-pickup-v2/README.md ADOPTED: features/0015-acks/README.md ADOPTED: concepts/0017-attachments/README.md ADOPTED: features/0035-report-problem/README.md ADOPTED: features/0092-transport-return-route/README.md ADOPTED: concepts/0094-cross-domain-messaging/README.md ADOPTED: features/0211-route-coordination/README.md ADOPTED: features/0360-use-did-key/README.md ADOPTED: concepts/0441-present-proof-best-practices/README.md ADOPTED: features/0557-discover-features-v2/README.md

swcurran commented 6 months ago

At the Aries Working Group meeting 2024-05-01, we went through a list of all of the proposed changes in this PR, as listed in this spreadsheet.

There was agreement and no objections to the following actions:

As of the writing of this comment, all of those changes have been made.

@JamesKEbert -- could I get you to review the changes to make sure I didn't make a mistake in applying the spreadsheet changes? Or anyone else. The PR is approved so in theory COULD be applied, but I'd appreciate another pair of eyes on it.

Thanks!

swcurran commented 6 months ago

Sorry about that @JamesKEbert — I ran the site generator script thinking that would be update the index as well. So, changed the script so now it does that, and included the updated index.md in this PR. The index.md will can/will be removed once the published site is the “go to” location, as the site is maintained by GitHub Actions, while the index.md requires a PR (like this one!).

Also fixed 213 that I missed.

Fixed - please confirm and let’s get this puppy merged! :-)