Skip to content
Snippets Groups Projects
Commit 6f9d1cc0 authored by Jonas Johan Solsvik's avatar Jonas Johan Solsvik :video_game:
Browse files

explain external deps

parent 63eea122
No related branches found
No related tags found
No related merge requests found
......@@ -93,7 +93,7 @@ Again the Rust Community Discord server helped me through the steepest part of t
- **Discord** - Most live discussion was conducted in Decentralized Identity Norden (DIN) Discord server.
- **Slack** - DIN also had a Slack-server, but this was never utiliized throughout the project period. DIF on the other hand, did most of their discussions through their Slack server.
- **Google hangouts** - The weekly domain-experts video-meeting was conducted using Google Hangouts.
- **MSTeams** - The weekly academic supervisor meeting was conducted in an MSTeams group.
- **MSTeams** - The weekly academic supervisor video-meeting was conducted in a MSTeams-group.
- **Github Issues** - When discussions gets complicated and/or lasts for an extended period of time, there was a need to create a dedicated Github issue, to keep track of everything. Creating a dedicated issue for every type discussion, would be the ideal situation, but tend to not be practical. There is an overhead of creating and maintaining an issue. The end results is that most issues are resolved directly through verbal conversation or through Discord, or any other kind of live chat/meeting.
- **Email** - Before getting into DIFs Slack-channel, there was a need to get in touch with some of the DIF-guys to ask questions about which direction the project should go in. We wanted to avoid doing uninteresting things. Snorre, which was the projects product manager, had some contact information to reach these key-industry-experts via email. The conversation always started with Snorre sending an email to one of these experts, with me (Jonas) as a CC-recipient, introducing me.
......@@ -110,16 +110,17 @@ Again the Rust Community Discord server helped me through the steepest part of t
### 1.5 Programming style guide including how to comment code
- We are using the Rust official style guide found here - https://doc.rust-lang.org/1.0.0/style/style/README.html
- We are following the official style guide religiously and want to avoid in-house style guides. Sticking to the offical one makes it easier and faster to onboard new developers.
- We are following the official style guide religiously and want to avoid in-house style guides.
- Sticking to the offical one makes it easier and faster to onboard new developers.
### 1.6 Use of and integration of libraries, modules, and other ways for modularisation of your product
One of the goals of the project, was to re-use as much as possible of existing libraries from the SSI community. This was the main reason Rust was chosen in the first place. The SSI community are already heavily invested into Rust, for many of the same strengths mentioned in section 1.
**External libraries integrated into DID-CLI**:
- ssi - https://github.com/spruceid/ssi
- didcomm-rs - https://github.com/decentralized-identity/didcomm-rs
- `did-key.rs` - https://github.com/decentralized-identity/did-key.rs
- `ssi` - Implements Verifiable Credentials - https://github.com/spruceid/ssi
- `didcomm-rs` - Implements DIDComm v2 - https://github.com/decentralized-identity/didcomm-rs
- `did-key.rs` - Implements did:key - https://github.com/decentralized-identity/did-key.rs
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment