We plan to start authoring and submitting PRs for ADRs against the credentials repos to capture decisions related to the work to support sharing Open edX credentials as verifiable credentials.
List of candidate ADRs and their proposed statuses. Any of these decisions could be merged into a single ADR if that made sense. Statuses should be considered stakes in the group, any disagreements should discussed.
DECIDED: The initial release will target the OpenBadges V3 specification only.
DECIDED: Related functionality will be developed as a separate Django application or applications that will be optional to run for deployers of the Open edX platform. This ADR will describe the mechanisms for enabling or disabling the feature.
DECIDED: For the initial release only Program certificates are in scope.
DECIDED: Decision to target the DCC wallet for v1
DECIDED: User-facing screens for sharing verifiable credentials will be added to the existing credentials MFE
DISCOVER: We need a design to handle reissuing credentials when they are updated on the platform.
DISCOVER: Mechanism for storing and provide the revocation list.
DISCUSS: Extending hooks and signals API (basic Django signals) – initial conversation to determine whether we should do this now.
DISCUSS: Creation of a python sign-and-verify library
DISCUSS: Dual signatories will be implemented via a new organization that subsumes all signatories.
DISCUSS: The DID will come from the DCC wallet for the first version.
DISCUSS: Need decision about storing the DID
DISCOVER: Gather and store issuer information in the platform.
DISCUSS: How many issuers should we support initially.
DISCUSS: Feature Flags based mechanism in MFEs
DISCUSS: Should we consider a plugin framework for the credentials application that is similar to what is available in edx-platform and goes beyond the simple model of creating a new Django app?