feat/presentation exchange

.devcontainer/Dockerfile

@@ -0,0 +1,23 @@
+FROM ghcr.io/findy-network/findy-base:indy-1.16.ubuntu-22.04 AS indy-base
+
+ARG VARIANT="jammy"
+
+FROM mcr.microsoft.com/devcontainers/base:jammy
+
+RUN apt-get update && \
+  apt-get install -y curl libsodium23 openssl libzmq5 git zsh python3 build-essential ca-certificates
+
+COPY --from=indy-base /usr/include/indy /usr/include/indy
+COPY --from=indy-base /usr/lib/libindy.a /usr/lib/libindy.a
+COPY --from=indy-base /usr/lib/libindy.so /usr/lib/libindy.so
+COPY --from=indy-base /usr/lib/libssl.so.1.1 /usr/lib/libssl.so.1.1
+COPY --from=indy-base /usr/lib/libcrypto.so.1.1 /usr/lib/libcrypto.so.1.1
+
+USER vscode
+
+RUN curl https://raw.githubusercontent.com/creationix/nvm/master/install.sh | bash && \
+  export NVM_DIR="$HOME/.nvm" && \
+  [ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh" && \
+  nvm install v16 && \
+  npm install yarn -g
+

.devcontainer/devcontainer.env

@@ -0,0 +1,7 @@
+#
+# Any environment variables that the container needs
+# go in here.
+#
+# Example(s)
+# GENESIS_TXN_PATH=/work/network/genesis/local-genesis.txn
+#

.devcontainer/devcontainer.json

@@ -0,0 +1,15 @@
+// For format details, see https://aka.ms/devcontainer.json. For config options, see the
+// README at: https://github.com/devcontainers/templates/tree/main/src/ubuntu
+{
+	"name": "Ubuntu",
+  "build": {
+  	"dockerfile": "Dockerfile",
+		"args": { "VARIANT": "bionic" }
+  },
+	"runArgs": ["--env-file", ".devcontainer/devcontainer.env"],
+  "workspaceMount": "source=${localWorkspaceFolder},target=/work,type=bind",
+  "workspaceFolder": "/work",
+	"features": {
+		"ghcr.io/devcontainers/features/docker-outside-of-docker:1": {}
+	}
+}

.dockerignore

@@ -1 +1,6 @@
-db
+caddy
+README.md
+docker-compose.yml
+.env
+.env.sample
+node_modules

.env.sample

@@ -0,0 +1,4 @@
+MEDIATOR_CONTROLLER_ADMIN_API_KEY=insecure-hello-world-1
+MEDIATOR_AGENT_ADMIN_API_KEY=insecure-hello-world-2
+MEDIATOR_ALIAS=MOON
+LOG_LEVEL=INFO

.gitignore

@@ -1,3 +1,8 @@
 .aws
 *.db-wal
 *.db-shm
+.env
+postgres-db
+node_modules/
+.DS_Store
+afj/dist/

MAINTAINERS.md

@@ -0,0 +1,69 @@
+# Maintainers
+
+## Active Maintainers
+
+<!-- Please keep this sorted alphabetically by github -->
+
+| Name           | Github | LFID |
+| -------------- | ------ | ---- |
+| Ian Costanzo   | ianco  |      |
+| Jason C. Leach | jleach |      |
+
+## Emeritus Maintainers
+
+| Name | Github | LFID |
+| ---- | ------ | ---- |
+|      |        |      |
+
+## Becoming a Maintainer
+
+Aries Mediator Service within the Hyperledger Aries community welcomes contributions. Contributors may progress to become a maintainer. To become a
+maintainer the following steps occur, roughly in order.
+
+- 3 **significant** changes have been authored by the proposed maintainer and
+  accepted.
+- The proposed maintainer has the sponsorship of at least one other maintainer.
+  - This sponsoring maintainer will create a PR modifying the list of
+    maintainers.
+  - The proposed maintainer accepts the nomination and expresses a willingness
+    to be a long-term (more than 6 month) maintainer.
+  - This would be a comment in the above PR.
+  - This PR will be communicated in all appropriate communication channels. It
+    should be mentioned in any maintainer/community call. It should also be
+    posted to the appropriate mailing list or chat channels if they exist.
+- Approval by at least 2 current maintainers within two weeks of the proposal or an absolute majority of current maintainers.
+  - These votes will be recorded in the PR modifying the list of maintainers.
+- No veto by another maintainer within two weeks of proposal are recorded.
+  - All vetoes must be accompanied by a public explanation as a comment in the
+    PR for adding this maintainer
+  - The explanation of the veto must be reasonable.
+  - A veto can be retracted, in that case the approval/veto time-frame is reset.
+  - It is bad form to veto, retract, and veto again.
+- The proposed maintainer becomes a maintainer
+  - Either two weeks have passed since the third approval,
+  - Or an absolute majority of maintainers approve.
+  - In either case, no maintainer presents a veto.
+
+## Removing Maintainers
+
+Being a maintainer is not a status symbol or a title to be maintained
+indefinitely. It will occasionally be necessary and appropriate to move a
+maintainer to emeritus status. This can occur in the following situations:
+
+- Resignation of a maintainer.
+- Violation of the [Hyperledger Code of
+  Conduct](https://wiki.hyperledger.org/display/HYP/Hyperledger+Code+of+Conduct) warranting removal.
+- **Inactivity**.
+  - A general measure of inactivity will be no commits or code review comments
+    for one reporting quarter, although this will not be strictly enforced if
+    the maintainer expresses a reasonable intent to continue contributing.
+  - Reasonable exceptions to inactivity will be granted for known long term
+    leave such as parental leave and medical leave.
+- Other unspecified circumstances.
+
+Like adding a maintainer the record and governance process for moving a
+maintainer to emeritus status is recorded in the github PR making that change.
+
+Returning to active status from emeritus status uses the same steps as adding a
+new maintainer. Note that the emeritus maintainer already has the 3 required
+significant changes as there is no contribution time horizon for those.