Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

KERI Suite Feedback: #78

Closed
3 of 11 tasks
daidoji opened this issue Nov 30, 2023 · 1 comment
Closed
3 of 11 tasks

KERI Suite Feedback: #78

daidoji opened this issue Nov 30, 2023 · 1 comment

Comments

@daidoji
Copy link
Contributor

daidoji commented Nov 30, 2023

How did you hear about KERI Suite?

via GitHub

Other Source

No response

Which part of the KERI Suite was your angle to look for?

  • key management
  • crypto currency
  • Self Sovereign Identity
  • KERI
  • ACDC
  • CESR
  • OOBI
  • IPEX
  • PTEL
  • KERIA
  • SIGNIFY

What was the point of interest for you as a developer?

It was because I've had a long running fascination with PKI systems and their challenges/benefits and I really liked the elegant nature of several of the key ideas KERI brought to the table. Namely key pre-rotation, SCIDs, and witnesses.

Why did you become involved?

Thought it was the best tech for a variety of things I wanted to build. So now I'm trying to gain experience and build them.

How did you become involved?

Just started coming to meetings in July of 2023 I think.

How did you build up you knowledge?

I read all the papers which I thought were pretty straightforward. Logically most of it makes sense even if I don't quite have the jargon down correctly. The toolchain though could use a lot of usability work and playing around with them and trying to just figure stuff out has been my main approach because as a community we still don't have a great set of tutorials or howtos other than some basic scripts.

How did you build up your skills?

Similar to above. Just tried playing around with things and building various prototypes/working on the codebases directly to solve bugs.

What learning resources lacked?

HOWTOs and tutorials on how to build the tools we already have and maybe roadmaps or tools that we need to have but no one has started to work on yet. Certainly, the community is a little insular at the moment.

I think that there exists the GLEIF technical recommendations which were really really really good from a security perspective (imo). If we could distill some of that into a "best practices" or a set of "security practices and KERI" I think it would really show just how super secure you can make KERI.

Also, a document or two on LMDB and HIO and architectural decisions of keripy would go a long way to helping developers get up to speed there.

What tips & tricks would you have for us?

That seems like pretty much what I did. The only comment I'd have is that we could do more as a community to make the above welcoming to newcomers. Probably everyone doesn't have time to dig into codebases and figure stuff out. Maybe a "learning path" like the above with tutorials/howtos/explainers would be good.

@henkvancann
Copy link
Collaborator

We'll use all the KERI Suite Feedback we've got for a larger upgrade planned this spring / summer. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants