tkuhrt (Tue, 08 May 2018 23:06:11 GMT):
Improving Indy Developer Experience

tkuhrt (Tue, 08 May 2018 23:06:11 GMT):
Group focused on improving the Hyperledger Indy developer experience for both contributors and users. This includes onboarding and getting started documentation, as well as, videos and training material.

tkuhrt (Tue, 08 May 2018 23:06:28 GMT):
mdb

tkuhrt (Tue, 08 May 2018 23:06:31 GMT):
esplinr

tkuhrt (Tue, 08 May 2018 23:16:11 GMT):
Let's continue the discussion here on ways that we can improve the developer journey for contributors and users.

mboyd (Tue, 08 May 2018 23:16:51 GMT):
Great, thanks for starting the channel

mboyd (Tue, 08 May 2018 23:18:06 GMT):
Here's a read-only link to our notes: https://docs.google.com/document/d/1VAqbz0-9pNmHt4LW7OLgEMA-zD3DPBrYPqTBWv_i6Bw/edit?usp=sharing

tkuhrt (Tue, 08 May 2018 23:18:57 GMT):
One thing that we are looking to add to the Hyperledger website are pointers to material for people to get started using each of the different projects. I found the following tutorials for Hyperledger Indy that I thought I could include, but would love pointers to any additional material: * [Hyperledger Indy Getting Started](https://github.com/hyperledger/indy-node/blob/stable/getting-started.md) * [Setting up a Test Indy VM Network with Vagrant](https://github.com/hyperledger/indy-node/blob/stable/environment/vagrant/training/vb-multi-vm/TestIndyClusterSetup.md) * [Setting up a DEV Environment with Vagrant](https://github.com/hyperledger/indy-node/blob/master/environment/vagrant/sandbox/DevelopmentEnvironment/Virtualbox/Vagrantfile) * [Create a network and start nodes](https://github.com/hyperledger/indy-node/blob/master/docs/start-nodes.md)

mboyd (Tue, 08 May 2018 23:28:30 GMT):
IBM recently published their own implementation of the [Alice tutorial](https://github.com/IBM-Blockchain-Identity/indy-ssivc-tutorial)

esplinr (Wed, 09 May 2018 18:58:37 GMT):
Thank you for setting up the channel @tkuhrt !

mboyd (Wed, 09 May 2018 19:04:29 GMT):
@esplinr I am about to go through the current links on https://wiki.hyperledger.org/projects/indy/documentation and remove the deprecated ones. I will then begin adding links to all the resources I can find that are at a reasonably polished and useful state. Once I'm finished on my end, I'd appreciate it if you could look it over and revise/add anything you feel will also be useful.

esplinr (Wed, 09 May 2018 19:04:47 GMT):
Excellent. Will do.

mboyd (Wed, 09 May 2018 19:54:54 GMT):
I've just added all the links I think are useful. There are undoubtedly more we can add

vidor (Wed, 09 May 2018 22:07:21 GMT):
Has joined the channel.

maestrus (Thu, 10 May 2018 06:57:14 GMT):
Has joined the channel.

guido.santos (Thu, 10 May 2018 09:14:16 GMT):
Has joined the channel.

the_identity_guy (Thu, 10 May 2018 15:12:56 GMT):
Has joined the channel.

kdenhartog (Thu, 10 May 2018 15:14:13 GMT):
Has joined the channel.

ianco (Thu, 10 May 2018 15:14:38 GMT):
Has joined the channel.

brycecurtis (Thu, 10 May 2018 15:15:32 GMT):
Has joined the channel.

stevenmilstein (Thu, 10 May 2018 15:15:34 GMT):
Has joined the channel.

arjanvaneersel (Thu, 10 May 2018 15:15:40 GMT):
Has joined the channel.

twshelton (Thu, 10 May 2018 15:30:32 GMT):
Has joined the channel.

swcurran (Thu, 10 May 2018 15:30:37 GMT):
Has joined the channel.

jonathanreynolds (Thu, 10 May 2018 15:38:05 GMT):
Has joined the channel.

arjanvaneersel (Thu, 10 May 2018 18:23:29 GMT):
I agree that this initiative is very good and it would definitely help. I started to develop materials for Indy for the Hyperledger meetups I'm running here in Bulgaria, but if it's useful I'd love to contribute to this initiative instead of making something on my own.

mboyd (Thu, 10 May 2018 18:33:23 GMT):
I'm happy to hear that @arjanvaneersel. What kind of materials do you think would be most helpful for you in Bulgaria?

arjanvaneersel (Thu, 10 May 2018 18:42:58 GMT):
My idea is to make materials with a similar approach as we do for fabric on the meetup: General principles, the network, development and deployment. However I didn’t intend to make it just for Bulgaria, but in a form that other meetups can use it as well.

arjanvaneersel (Thu, 10 May 2018 18:45:08 GMT):
In March I spoke about Indy and Sovrin in Plovdiv and noticed that people are interested, but that the concept of SSI is still unknown. So I mainly spoke about that than getting into technical stuff.

arjanvaneersel (Thu, 10 May 2018 18:46:50 GMT):
With Fabric it’s easier, because it’s a general purpose Blockchain and doesn’t focus on solving a very specific thing like SSI.

nage (Mon, 14 May 2018 17:23:36 GMT):
Has joined the channel.

Sean_Bohan (Thu, 17 May 2018 13:21:38 GMT):
Has joined the channel.

qrz (Thu, 17 May 2018 14:02:16 GMT):
Has joined the channel.

qrz (Thu, 17 May 2018 14:02:45 GMT):
Has left the channel.

trthhrtz (Thu, 17 May 2018 15:12:30 GMT):
Has joined the channel.

darrell.odonnell (Fri, 18 May 2018 13:36:31 GMT):
Has joined the channel.

kdenhartog (Fri, 18 May 2018 16:31:17 GMT):
User User_1 added by kdenhartog.

Sarah.Conway (Mon, 21 May 2018 20:13:21 GMT):
Has joined the channel.

Sarah.Conway (Mon, 21 May 2018 20:13:30 GMT):
hi all. I am new to working on marketing/PR for Hyperledger. We are writing a follow up Consensus blog for the HL site that focuses on interoperability. Can someone share a few sentences, maybe 2-3, on what concrete progress we have made or are we planning to make with #indy-outreach on this front? Or feel free to point me to some urls, PPTs, etc. Thanks!

mboyd (Mon, 21 May 2018 20:29:43 GMT):
hi @Sarah Conway, I can share our progress for #indy-outreach, and also hope that @tkuhrt can offer her feedback as well. We are working on two initiatives to help contributors and users interact easier with Hyperledger Indy. First, we are consolidating all the current documentation and training resources in one place on the hyperledger wiki page: https://wiki.hyperledger.org/projects/indy/documentation. In addition, we are creating interactive tutorials on how to use the indy-sdk and build applications that utlizing the indy-node ledger. Check out the current [getting started guide](https://github.com/hyperledger/indy-sdk/blob/master/doc/getting-started/getting-started.md). Second, #indy-outreach pairs interested contributors and users with good first-time projects and mentors to help them get started. @kdenhartog and I are happy to meet with any contributors or interested users for 10-20 minutes and introduce them to the Indy ecosytem. We have a list of [good first bugs/projects](https://jira.hyperledger.org/secure/RapidBoard.jspa?rapidView=149&projectKey=IS&view=planning&selectedIssue=IS-574&quickFilter=447) on our JIRA account.

mboyd (Mon, 21 May 2018 20:29:43 GMT):
hi @Sarah Conway, I can share our progress for #indy-outreach, and also hope that @tkuhrt can offer her feedback as well. We are working on two initiatives to help contributors and users interact easier with Hyperledger Indy. First, we are consolidating all the current documentation and training resources in one place on the hyperledger wiki page: https://wiki.hyperledger.org/projects/indy/documentation. In addition, we are creating interactive tutorials on how to use the indy-sdk and build applications that utlizing the indy-node ledger. Check out the current [getting started guide](https://github.com/hyperledger/indy-sdk/blob/master/doc/getting-started/getting-started.md). Second, #indy-outreach pairs interested contributors with good first-time projects and mentors to help them get started. @kdenhartog and I are happy to meet with any contributors for 10-20 minutes and introduce them to the Indy ecosytem. We have a list of [good first bugs/projects](https://jira.hyperledger.org/secure/RapidBoard.jspa?rapidView=149&projectKey=IS&view=planning&selectedIssue=IS-574&quickFilter=447) on our JIRA account.

tkuhrt (Mon, 21 May 2018 23:07:52 GMT):
@Sarah Conway : Still catching up from being out at Consensus. Did you reach out on the #indy channel? I assume when you ask about interoperability, you are asking about it from the perspective of how Hyperledger Indy interoperates with the other Hyperledger projects (e.g., Fabric, Sawtooth).

jayapalreddy (Tue, 22 May 2018 12:02:18 GMT):
Has joined the channel.

Sarah.Conway (Tue, 22 May 2018 12:17:55 GMT):
Thanks @mdb. Will check out this info.

Sarah.Conway (Tue, 22 May 2018 12:19:00 GMT):
I will ask the same question on #indy channel. @tkuhrt would like to know about interoperability with our own projects and other blockchains. both perspectives would be interesting to include in the blog.

esplinr (Wed, 23 May 2018 13:53:05 GMT):
Someone posted this today in the Sovrin channels. I think it's a good example of the type of introductory deck we need for the Indy project more generally: https://drive.google.com/file/d/1dJ3pguixk_c0T3oYiIdFZaCZQLe4X69s/view

esplinr (Wed, 23 May 2018 13:53:05 GMT):
Someone posted this recently in the Sovrin channels. I think it's a good example of the type of introductory deck we need for the Indy project more generally: https://drive.google.com/file/d/1dJ3pguixk_c0T3oYiIdFZaCZQLe4X69s/view

vidor (Wed, 23 May 2018 14:30:18 GMT):
@esplinr Do you think that Indy will implement something like the proposed Token in the Sovrin whitepaper?

esplinr (Wed, 23 May 2018 14:30:58 GMT):
No.

esplinr (Wed, 23 May 2018 14:31:32 GMT):
Hyperledger projects don't want to be in the cryptocurrency business. But we are implementing a way to plug in a payment process that will be used by Sovrin and other deployments of Indy.

esplinr (Wed, 23 May 2018 14:32:04 GMT):
So the Indy CLI in LibIndy already has a "nullpayments" interface that can be replaced with the payment method that your deployment prefers.

esplinr (Wed, 23 May 2018 14:32:30 GMT):
Does that make sense @vidor?

vidor (Wed, 23 May 2018 14:36:00 GMT):
Yes it makes sense. Thank you. The one thing that I'm confused by is how will the payment interface work. Will it allow to build a custom token that would help with circulating a value within a network. Or would it give the possibility to integrate external blockchains (cryptocurrencies)? If the latter, how would the cross-chain integration work? Because if running a custom payment plugin on every indy instance that communicates with external components, it introduces non-pure functions and reaching a consensus between nodes could prove to be very hard?

esplinr (Wed, 23 May 2018 14:39:54 GMT):
The intention is that it could be used to either allow a custom token or be used to integrate external blockchains.

esplinr (Wed, 23 May 2018 14:40:21 GMT):
But there isn't yet a real implementation of either, so there are likely some unforeseen problems.

esplinr (Wed, 23 May 2018 14:40:52 GMT):
The libnullpay is expected in the next release, so this is all new ground.

kbreite27 (Wed, 23 May 2018 15:01:30 GMT):
Has joined the channel.

troyronda (Wed, 23 May 2018 15:50:21 GMT):
Has joined the channel.

tomislav (Wed, 23 May 2018 17:08:55 GMT):
Has joined the channel.

esplinr (Thu, 24 May 2018 14:37:09 GMT):
@tkuhrt What is the best way to add our sprint demo videos to the Hyperledger YouTube channel? Should we upload them to our YouTube account and add them to a Hyperledger playlist, or should we upload them directly to the Hyperledger channel?

esplinr (Thu, 24 May 2018 19:24:50 GMT):
Concerns with the Getting Started Guides came up again in the Indy Maintainers meeting and in the other chat channels. I'm encouraging everyone interested to come here to collaborate.

esplinr (Thu, 24 May 2018 19:24:50 GMT):
@rjones Do you also work with the YouTube channel?

rjones (Thu, 24 May 2018 19:24:50 GMT):
Has joined the channel.

rjones (Thu, 24 May 2018 19:27:00 GMT):
@esplinr what we've done in the past is for you to upload it to google drive and send a share link. Someone from our social media team will upload it to the Hyperledger channel.

rjones (Thu, 24 May 2018 19:27:41 GMT):
@esplinr it would be best if you emailed us directly with the share link - {rjones,tkuhrt}@linuxfoundation.org

esplinr (Thu, 24 May 2018 19:29:11 GMT):
Sounds good. Thanks!

jeremi 24 (Fri, 25 May 2018 07:06:07 GMT):
Has joined the channel.

burdettadam (Tue, 29 May 2018 19:16:14 GMT):
Has joined the channel.

jwaup (Wed, 30 May 2018 13:58:25 GMT):
Has joined the channel.

bdeva (Thu, 07 Jun 2018 15:16:34 GMT):
Has joined the channel.

bdeva (Thu, 07 Jun 2018 15:28:52 GMT):
Has left the channel.

Katie_Wei (Wed, 20 Jun 2018 18:46:03 GMT):
Has joined the channel.

esplinr (Mon, 25 Jun 2018 22:47:48 GMT):
A quick update on YouTube videos. I haven't got our videos published to the Hyperledger YouTube channel yet. I was going to add Hyperledger bumpers, but never got around to it. My current plan is to add them to the Evernym YouTube channel, then I can share that Playlist with Hyperledger. That will let me manage them more dynamically instead of exclusively through email.

esplinr (Mon, 25 Jun 2018 22:50:43 GMT):
Concerns with the quality of the Getting Started Guides keep coming up in the Indy chat channels, and there was a brief discussion about this in the Indy Maintainers meeting this morning. I'm encouraging everyone interested to join this channel to collaborate. To assist, I pulled together this list of issues as good starting points for long-term solutions. * INDY-792 * INDY-1294 * INDY-1211 * IS-770 * IS-771 * IS-322 Of course, anyone who wants to fix a Getting Started Guide can immediately send a pull request and ignore the above work.

n3m4nja (Tue, 26 Jun 2018 06:00:29 GMT):
Has joined the channel.

alvaradojl (Tue, 26 Jun 2018 07:57:47 GMT):
Has joined the channel.

mjmckean (Tue, 26 Jun 2018 15:32:26 GMT):
Has joined the channel.

dbluhm (Tue, 26 Jun 2018 15:32:35 GMT):
Has joined the channel.

TechWritingWhiz (Tue, 26 Jun 2018 15:35:43 GMT):
Has joined the channel.

TechWritingWhiz (Tue, 26 Jun 2018 15:38:55 GMT):
Hey Everyone! Recently, I published some information the Hyperledger Wiki Indy page in regards to what types of habits should be followed when it comes working with and maintaining the Indy documentation. Here is the link: https://wiki.hyperledger.org/projects/indy/contributing_docs For those of you who don't know me, I'm the Technical Writer at Evernym.

esplinr (Tue, 26 Jun 2018 17:12:58 GMT):
Thanks @TechWritingWhiz ! @all I'm interested to hear what feedback you have on that document.

alain2sf (Wed, 27 Jun 2018 13:38:53 GMT):
Has joined the channel.

mjmckean (Thu, 28 Jun 2018 21:07:52 GMT):
"Never, at any time, should there be more than one copy of an official document living in more than one place." What do we think about creating an indy-docs repo? This could help reduce confusion for users wanting to know how/where to start, and would make having an Indy ReadTheDocs possible.

LuigiRiva (Fri, 29 Jun 2018 13:23:35 GMT):
Has joined the channel.

n3m (Wed, 11 Jul 2018 07:32:43 GMT):
Has joined the channel.

ksista (Thu, 12 Jul 2018 16:32:54 GMT):
Has joined the channel.

esplinr (Tue, 24 Jul 2018 21:40:35 GMT):
I'm catching up on messages that came while I was on vacation.

esplinr (Tue, 24 Jul 2018 21:40:55 GMT):
There is a trade-off between having all the docs in one place, and having the documentation in the first place someone expects to find it.

esplinr (Tue, 24 Jul 2018 21:41:44 GMT):
@mjmckean How does a new developer learn about the indy-docs repository? That's the advantage to having the docs with the deliverable. But once they are in indy-docs, they have everything, which is the advantage to a single repo.

esplinr (Tue, 24 Jul 2018 21:42:29 GMT):
We provided some feedback on the pull request to use ReadTheDocs for Indy-SDK. We are glad you are doing the work, but the team reviewing the PR would appreciate a bit more information about what you are doing. How does the documentation get published to ReadTheDocs?

mjmckean (Tue, 24 Jul 2018 21:50:44 GMT):
@esplinr thank you for the response on the PR—I’m working on a more descriptive response for the team, and I’ll get that out hopefully tonight or tomorrow morning. From what I understand, ReadTheDocs compiles documentation into an html format through a web hook that I’ve attached to my fork of indy-sdk. Each time my fork updates, the RTD recompiles. One of the advantages of having an indy-docs repo would be to eliminate any inconvenience these cosmetic PRs create in indy-sdk and separate the consumer-facing documentation from the more gritty dev docs. So with my current thoughts, the indy-docs repo could receive PRs from consumers and developers who think of ways to improve/update the documentation. I’m not married to this idea, I just think it would help divert certain PRs from clogging up indy-sdk.

esplinr (Tue, 24 Jul 2018 21:56:56 GMT):
That's a good explanation. I'm not against an indy-docs repo. I just want to recognize the trade-offs. Perhaps it's time for a Documentation HIPE?

esplinr (Tue, 24 Jul 2018 21:57:18 GMT):
I thought that ReadTheDocs directly published the markdown, so I was surprised by the build step.

mjmckean (Tue, 24 Jul 2018 22:08:40 GMT):
That’s what I thought initially, and there is a markdown build option, but I had trouble organizing the files into a less than random format when I built with .md.

mjmckean (Tue, 24 Jul 2018 22:09:13 GMT):
If you’d like, I can throw a HIPE together this week!

esplinr (Wed, 25 Jul 2018 15:11:18 GMT):
@mjmckean Interesting to know about the ordering of markdown files. That's a big problem.

esplinr (Wed, 25 Jul 2018 15:12:21 GMT):
I think I HIPE would be really useful. It could wait until next week if you are busy, but it will help so that in the next maintainers meeting we can discuss your approach and make sure that others understand what you are doing.

EvelynEvergreene (Wed, 25 Jul 2018 17:29:57 GMT):
Has joined the channel.

EvelynEvergreene (Wed, 25 Jul 2018 17:30:27 GMT):
Here because @esplinr told me to be. How can I help?

esplinr (Wed, 25 Jul 2018 17:36:47 GMT):
@swcurran was just asking me about improving the links in the wiki to the documentation.

swcurran (Wed, 25 Jul 2018 18:32:30 GMT):
Specifically, looking to have added *the definitive place* for someone new to Indy to start - a pointer that is maintained over time that always points to the current "Getting Started" instructions. The place that people like Kyle and Richard point people to on RocketChat when they ask "How do I get started?". In the past, the challenge has been that changes, and people find the old place and start there. We could then point them to this section of the wiki, confident that as the actual place to get started changes, it will be updated on the wiki. I'm not sure if there are different starting places for different types of people (business, vs. devs), but if so, this section could explain that and have multiple pointers. I can add this myself, but I'm not certain what the official starting point is right now.

EvelynEvergreene (Wed, 25 Jul 2018 19:29:00 GMT):
I know some of the people at sovrin have also been discussing this. I know that there are some other things that have to happen before we can do so.

EvelynEvergreene (Wed, 25 Jul 2018 19:29:19 GMT):
I'd love to help where I can.

vladan.divac (Thu, 26 Jul 2018 15:39:19 GMT):
Has joined the channel.

mjmckean (Thu, 26 Jul 2018 21:55:34 GMT):
@burdettadam and I threw together a [Documentation HIPE](https://github.com/hyperledger/indy-hipe/pull/24) today. We are open to any and all feedback :)

esplinr (Tue, 31 Jul 2018 18:24:20 GMT):
That Documentation HIPE is a great way for us to get organized and work in the same direction. Have you looked it over @TechWritingWhiz ?

RyanWest (Tue, 31 Jul 2018 21:37:08 GMT):
Has joined the channel.

danielhardman (Tue, 31 Jul 2018 21:37:27 GMT):
Has joined the channel.

nhelmy (Tue, 31 Jul 2018 21:38:01 GMT):
Has joined the channel.

esplinr (Tue, 31 Jul 2018 22:02:52 GMT):
Notice: @mdb volunteered to work with @mjmckean to implement the idea @swcurran was pushing to create a canonical list of resources for new members of the Indy community. We're calling it the "Disneyland itinerary". Probably in the wiki, but maybe in some other location that they recommend.

esplinr (Tue, 31 Jul 2018 22:03:43 GMT):
cc @mboyd

esplinr (Fri, 03 Aug 2018 18:52:22 GMT):
@burdettadam and @mjmckean please meet @dkulic and @jankokrstic

jankokrstic (Fri, 03 Aug 2018 18:52:22 GMT):
Has joined the channel.

dkulic (Fri, 03 Aug 2018 18:52:22 GMT):
Has joined the channel.

esplinr (Fri, 03 Aug 2018 18:52:46 GMT):
They are assigned to get LibVCX merged into the Indy SDK, and could use your guidance on the right way to handle the documentation.

esplinr (Fri, 03 Aug 2018 18:53:03 GMT):
Preferably, we would like to start generating the API documentation as part of the CI pipeline.

mero (Wed, 08 Aug 2018 10:44:25 GMT):
Has joined the channel.

TechWritingWhiz (Mon, 20 Aug 2018 14:20:42 GMT):
[ ](https://chat.hyperledger.org/channel/indy-outreach?msg=BNsuy7MrmpqjEEn5J) @esplinr Yep, I reviewed it and placed comments on it. Just now seeing your mention.

InfoMiner (Fri, 24 Aug 2018 19:40:42 GMT):
Has joined the channel.

kdenhartog (Mon, 27 Aug 2018 19:31:55 GMT):
@esplinr @mboyd @mjmckean have we completed Disneyland itinerary yet?

kdenhartog (Mon, 27 Aug 2018 20:52:43 GMT):
I wrote an email that covered very similar topics as what the Disneyland itinerary might look like. Here's a good place to start since I couldn't find one ` 1. First, I'd recommend checking out this video to understand the first use case which is implemented in our getting started guide linked to in number 3. 2. My next recommendation would be to start exploring the main repositories of Indy and the #indy-sdk channel on Hyperledger rocketchat. Here's a good wiki that links to many great Indy resources. 3. Once you've familiarized yourself with the repositories I'd recommend going through the Getting Started Guide paying close attention to the code that calls indy functions. These are what you'll be using to build PoCs. 4. Since this getting started guide is only one use case, the next place I'd recommend is the How To guides. The Python is kept up to date the best and node.js is the next best, by not as well kept up to date. These are guides about how to perform common actions in the Indy ecosystem like creating decentralized Identifiers, issuing credentials, and other actions related to these topics. 5. Once you've got a general understanding of these functions in the Indy-SDK you'll be ready to start writing a PoC, which is what agents are for. An agent today has the mental model of being a pieces of software that uses SSI protocols (Starting to be defined in the Indy-HIPE repo most of which are still pull requests) to accomplish some task like storing credentials and managing cryptographic keys. In the future, I expect that an agent will be any applications that consumes Indy-SDK. The mental models for a lot of this are very early, so we're still learning as we go. I expect that you'll have a lot of questions as you go, so when you find that things aren't clear feel free to reach out on the Indy-SDK channel or DM me on rocketchat. I'd be happy to help explain things or just generally be an advocate in connecting you with people in the community. Also since documentation is a big thing we need help with right now, if you find a solution to your problems would you mind making PRs with fixes or clarification? If you're really feeling helpful, the How-to guides for wrappers still need to be ported from python over to the other languages. That would be tremendous help in helping to build the Indy community.`

kdenhartog (Mon, 27 Aug 2018 20:52:43 GMT):
I wrote an email that covered very similar topics as what the Disneyland itinerary might look like. Here's a good place to start since I couldn't find one. `1. First, I'd recommend checking out this video to understand the first use case which is implemented in our getting started guide linked to in number 3. 2. My next recommendation would be to start exploring the main repositories of Indy and the #indy-sdk channel on Hyperledger rocketchat. Here's a good wiki that links to many great Indy resources. 3. Once you've familiarized yourself with the repositories I'd recommend going through the Getting Started Guide paying close attention to the code that calls indy functions. These are what you'll be using to build PoCs. 4. Since this getting started guide is only one use case, the next place I'd recommend is the How To guides. The Python is kept up to date the best and node.js is the next best, by not as well kept up to date. These are guides about how to perform common actions in the Indy ecosystem like creating decentralized Identifiers, issuing credentials, and other actions related to these topics. 5. Once you've got a general understanding of these functions in the Indy-SDK you'll be ready to start writing a PoC, which is what agents are for. An agent today has the mental model of being a pieces of software that uses SSI protocols (Starting to be defined in the Indy-HIPE repo most of which are still pull requests) to accomplish some task like storing credentials and managing cryptographic keys. In the future, I expect that an agent will be any applications that consumes Indy-SDK. The mental models for a lot of this are very early, so we're still learning as we go. I expect that you'll have a lot of questions as you go, so when you find that things aren't clear feel free to reach out on the Indy-SDK channel or DM me on rocketchat. I'd be happy to help explain things or just generally be an advocate in connecting you with people in the community. Also since documentation is a big thing we need help with right now, if you find a solution to your problems would you mind making PRs with fixes or clarification? If you're really feeling helpful, the How-to guides for wrappers still need to be ported from python over to the other languages. That would be tremendous help in helping to build the Indy community.`

kdenhartog (Mon, 27 Aug 2018 20:52:43 GMT):
I wrote an email that covered very similar topics as what the Disneyland itinerary might look like. Here's a good place to start since I couldn't find one. ```1. First, I'd recommend checking out this video to understand the first use case which is implemented in our getting started guide linked to in number 3. 2. My next recommendation would be to start exploring the main repositories of Indy and the #indy-sdk channel on Hyperledger rocketchat. Here's a good wiki that links to many great Indy resources. 3. Once you've familiarized yourself with the repositories I'd recommend going through the Getting Started Guide paying close attention to the code that calls indy functions. These are what you'll be using to build PoCs. 4. Since this getting started guide is only one use case, the next place I'd recommend is the How To guides. The Python is kept up to date the best and node.js is the next best, by not as well kept up to date. These are guides about how to perform common actions in the Indy ecosystem like creating decentralized Identifiers, issuing credentials, and other actions related to these topics. 5. Once you've got a general understanding of these functions in the Indy-SDK you'll be ready to start writing a PoC, which is what agents are for. An agent today has the mental model of being a pieces of software that uses SSI protocols (Starting to be defined in the Indy-HIPE repo most of which are still pull requests) to accomplish some task like storing credentials and managing cryptographic keys. In the future, I expect that an agent will be any applications that consumes Indy-SDK. The mental models for a lot of this are very early, so we're still learning as we go. I expect that you'll have a lot of questions as you go, so when you find that things aren't clear feel free to reach out on the Indy-SDK channel or DM me on rocketchat. I'd be happy to help explain things or just generally be an advocate in connecting you with people in the community. Also since documentation is a big thing we need help with right now, if you find a solution to your problems would you mind making PRs with fixes or clarification? If you're really feeling helpful, the How-to guides for wrappers still need to be ported from python over to the other languages. That would be tremendous help in helping to build the Indy community.```

kdenhartog (Mon, 27 Aug 2018 20:52:43 GMT):
I wrote an email that covered very similar topics as what the Disneyland itinerary might look like. Here's a good place to start since I couldn't find one. ```1. First, I'd recommend checking out this video (https://www.youtube.com/watch?v=cz-6BldajiA) to understand the first use case which is implemented in our getting started guide linked to in number 3. 2. My next recommendation would be to start exploring the main repositories of Indy and the #indy-sdk channel on Hyperledger rocketchat. Here's a good wiki(https://wiki.hyperledger.org/projects/indy/documentation) that links to many great Indy resources. 3. Once you've familiarized yourself with the repositories I'd recommend going through the Getting Started Guide (https://github.com/hyperledger/indy-sdk/blob/master/doc/getting-started/getting-started.md) paying close attention to the code that calls indy functions. These are what you'll be using to build PoCs. 4. Since this getting started guide is only one use case, the next place I'd recommend is the How To guides (https://github.com/hyperledger/indy-sdk/tree/master/doc/how-tos). The Python is kept up to date the best and node.js is the next best, by not as well kept up to date. These are guides about how to perform common actions in the Indy ecosystem like creating decentralized Identifiers, issuing credentials, and other actions related to these topics. 5. Once you've got a general understanding of these functions in the Indy-SDK you'll be ready to start writing a PoC, which is what agents (https://github.com/hyperledger/indy-agent) are for. An agent today has the mental model of being a pieces of software that uses SSI protocols (Starting to be defined in the Indy-HIPE (https://github.com/hyperledger/indy-hipe/pulls) repo most of which are still pull requests) to accomplish some task like storing credentials and managing cryptographic keys. In the future, I expect that an agent will be any applications that consumes Indy-SDK. The mental models for a lot of this are very early, so we're still learning as we go. I expect that you'll have a lot of questions as you go, so when you find that things aren't clear feel free to reach out on the Indy-SDK channel (https://chat.hyperledger.org/channel/indy-sdk) on rocketchat. I'd be happy to help explain things or just generally be an advocate in connecting you with people in the community. Also since documentation is a big thing we need help with right now, if you find a solution to your problems would you mind making PRs with fixes or clarification? If you're really feeling helpful, the How-to guides for wrappers still need to be ported from python over to the other languages. That would be tremendous help in helping to build the Indy community.```

kdenhartog (Mon, 27 Aug 2018 20:52:43 GMT):
I wrote an email that covered very similar topics as what the Disneyland itinerary might look like. Here's a good place to start since I couldn't find one. ``` 1. First, I'd recommend checking out this video (https://www.youtube.com/watch?v=cz-6BldajiA) to understand the first use case which is implemented in our getting started guide linked to in number 3. 2. My next recommendation would be to start exploring the main repositories of Indy and the #indy-sdk channel on Hyperledger rocketchat. Here's a good wiki(https://wiki.hyperledger.org/projects/indy/documentation) that links to many great Indy resources. 3. Once you've familiarized yourself with the repositories I'd recommend going through the Getting Started Guide (https://github.com/hyperledger/indy-sdk/blob/master/doc/getting-started/getting-started.md) paying close attention to the code that calls indy functions. These are what you'll be using to build PoCs. 4. Since this getting started guide is only one use case, the next place I'd recommend is the How To guides (https://github.com/hyperledger/indy-sdk/tree/master/doc/how-tos). The Python is kept up to date the best and node.js is the next best, by not as well kept up to date. These are guides about how to perform common actions in the Indy ecosystem like creating decentralized Identifiers, issuing credentials, and other actions related to these topics. 5. Once you've got a general understanding of these functions in the Indy-SDK you'll be ready to start writing a PoC, which is what agents (https://github.com/hyperledger/indy-agent) are for. An agent today has the mental model of being a pieces of software that uses SSI protocols (Starting to be defined in the Indy-HIPE (https://github.com/hyperledger/indy-hipe/pulls) repo most of which are still pull requests) to accomplish some task like storing credentials and managing cryptographic keys. In the future, I expect that an agent will be any applications that consumes Indy-SDK. The mental models for a lot of this are very early, so we're still learning as we go. I expect that you'll have a lot of questions as you go, so when you find that things aren't clear feel free to reach out on the Indy-SDK channel (https://chat.hyperledger.org/channel/indy-sdk) on rocketchat. I'd be happy to help explain things or just generally be an advocate in connecting you with people in the community. Also since documentation is a big thing we need help with right now, if you find a solution to your problems would you mind making PRs with fixes or clarification? If you're really feeling helpful, the How-to guides for wrappers still need to be ported from python over to the other languages. That would be tremendous help in helping to build the Indy community. ```

gskerry (Wed, 29 Aug 2018 15:55:29 GMT):
Has joined the channel.

mhomaid (Thu, 30 Aug 2018 15:26:50 GMT):
Has joined the channel.

mhailstone (Thu, 30 Aug 2018 15:26:50 GMT):
Has joined the channel.

sureshtedla (Fri, 31 Aug 2018 17:30:02 GMT):
Has joined the channel.

thPart (Mon, 03 Sep 2018 07:34:41 GMT):
Has joined the channel.

SRibeiro (Wed, 05 Sep 2018 12:58:11 GMT):
Has joined the channel.

esplinr (Fri, 07 Sep 2018 18:02:21 GMT):
That's a great summary of the current state of the materials @kdenhartog . Thank you for sharing.

swcurran (Fri, 07 Sep 2018 18:23:11 GMT):
Assuming this is still accurate :-), I'm planning on adding that to the wiki shortly and I'll try to monitor to see if it changes. I'm working on a course for Indy, so I have a vested interest in it being accurate :-). However, if there an existing mechanism in Indy or Evernym to keep the contents up to date, it would be great to use that. E.g. a checklist that is executed each time release of a product is made.

esplinr (Fri, 07 Sep 2018 18:25:39 GMT):
The Sovrin Foundation has been tracking the developer documentation, so the Evernym team has focused on other areas. The backlog they have been working on is here: IS-320.

mboyd (Wed, 12 Sep 2018 16:33:55 GMT):
@swcurran I would love to hear more about the course you are planning!

swcurran (Wed, 12 Sep 2018 16:43:56 GMT):
It's a an addition to the current EdX course - a chapter on Indy and Identity. The content is currently in a pull request - https://github.com/hyperledger/education/pull/79

swcurran (Wed, 12 Sep 2018 16:44:16 GMT):
I've been working on it on and off for a bit, and need to wrap it up shortly.

swcurran (Wed, 12 Sep 2018 16:45:08 GMT):
This is the course - https://www.edx.org/professional-certificate/linuxfoundationx-blockchain-for-business

kenebert (Wed, 12 Sep 2018 16:58:34 GMT):
Has joined the channel.

Rantwijk (Thu, 13 Sep 2018 13:39:48 GMT):
Has joined the channel.

nage (Thu, 13 Sep 2018 14:25:59 GMT):
The TSC is considering a task force to help with community improvement and perhaps statistics and information that will help us improve community health. @esplinr, I have volunteered you, is there anyone else here who would like to be volunteered?

tkuhrt (Fri, 14 Sep 2018 22:31:31 GMT):
^^ if so, DM me. I will get you added to the lab

freeman (Mon, 24 Sep 2018 14:29:56 GMT):
Has joined the channel.

esplinr (Thu, 04 Oct 2018 15:49:35 GMT):
@burdettadam @mjmckean we discussed the documentation effort a bit on the Indy Working Group call today. You should check out the recording, about 40 minutes in.

esplinr (Thu, 04 Oct 2018 15:49:56 GMT):
@phaniac and @jmason900 had great insights.

phaniac (Thu, 04 Oct 2018 15:49:56 GMT):
Has joined the channel.

jmason900 (Thu, 04 Oct 2018 15:49:56 GMT):
Has joined the channel.

phaniac (Thu, 04 Oct 2018 15:59:16 GMT):
ty. Can you point us to the proposed ideas for improving Indy docs?

esplinr (Thu, 04 Oct 2018 16:13:37 GMT):
Our first step was to improve the tooling for publishing documentation. Then we were going to look into actually improving the documentation. https://github.com/hyperledger/indy-hipe/pull/24

jlin (Fri, 05 Oct 2018 15:08:29 GMT):
Has joined the channel.

lijiachuan (Tue, 09 Oct 2018 01:22:16 GMT):
Has joined the channel.

lijiachuan (Tue, 09 Oct 2018 01:26:55 GMT):
Hi, I translated some Indy documents to Chinese, also include partial of Sovrin white paper(From abstract to party 5), not sure whether I can contribute this to somewhere. Below is my translates URL: https://blog.csdn.net/li_jiachuan/article/category/8094510

kdenhartog (Tue, 09 Oct 2018 18:11:40 GMT):
thanks @lijiachuan! @nage or @esplinr do you have any ideas where we'd like to collect docs like this?

lijiachuan (Wed, 10 Oct 2018 01:02:53 GMT):
Thanks, may I know is there any official China developer group?

esplinr (Wed, 10 Oct 2018 16:58:03 GMT):
I'm not aware of an official China developer group.

esplinr (Wed, 10 Oct 2018 16:59:02 GMT):
I'm concerned about bringing translations of the documentation into the main repository, because we aren't equipped to keep it current over time.

esplinr (Wed, 10 Oct 2018 16:59:26 GMT):
@lijiachuan I suggest that we create a section in the Hyperledger wiki that links to translations of the documentation.

esplinr (Wed, 10 Oct 2018 16:59:55 GMT):
@lijiachuan And I forgot to say "Thank You"! It's great that you would do that.

esplinr (Wed, 10 Oct 2018 17:00:06 GMT):
We haven't yet discussed multi-lingual documentation much.

esplinr (Wed, 10 Oct 2018 17:01:29 GMT):
On other projects I contribute to, we prioritize officially translating the consumer documentation. But we only maintain the official developer documentation in English, though we link to unofficial translations.

esplinr (Wed, 10 Oct 2018 17:01:39 GMT):
I'm interested to know what other Indy people think.

jlin (Wed, 10 Oct 2018 17:38:46 GMT):
I believe most of the Composer developers are from China. You might want to try to hook up with them?

lijiachuan (Wed, 10 Oct 2018 21:29:46 GMT):
@esplinr so may I know what is the condition to be a translated documents which can be unofficially linked from wiki? I think you can officially created on repository for other language translated documents and it can be maintained from the community, and put one disclaimer on it. This just provide one learning approach for developers who are not good at English.

kdenhartog (Fri, 12 Oct 2018 09:54:27 GMT):
I just put together a simple development environment to run IndySDK code in a docker environment. If anyone is having trouble getting IndySDK setup or wants an easy way to develop with the SDK on any OS, check out this repo. https://github.com/kdenhartog/Indy-dev

esplinr (Fri, 12 Oct 2018 21:30:31 GMT):
@lijiachuan I don't think documents linked from the wiki need to meet any quality standard. If they aren't kept up to date, we can remove them or add additional information at the point of the link. It's reasonable to keep translations of documentation in the repository. My concern is that the documents won't be kept up to date and then people will get confused because they look official. Our current approach is that everything within the repository should always be up-to-date (though we don't currently meet that bar even with the English docs). I'm just sharing an opinion. @mboyd had volunteered to be the owner of a documentation strategy, so I'll let him decide. Or someone else could volunteer to push forward an approach.

esplinr (Fri, 12 Oct 2018 21:30:36 GMT):
@kdenhartog Nice!

gudkov (Thu, 25 Oct 2018 06:57:34 GMT):
Has joined the channel.

wip-abramson (Tue, 30 Oct 2018 12:51:20 GMT):
Has joined the channel.

dallavecchia (Tue, 30 Oct 2018 13:07:25 GMT):
Has joined the channel.

wip-abramson (Tue, 30 Oct 2018 13:34:09 GMT):
@kdenhartog thank you - this is the first time I have managed to get the indy example working.

tkuhrt (Thu, 01 Nov 2018 17:39:32 GMT):
[ ](https://chat.hyperledger.org/channel/indy-outreach?msg=A9Xh2gLhmegaQ6Xto) @lijiachuan : Have you connected with the Technical WG China #twg-china ? They have been working on translation for Fabric, and it would be good to add some folks to that group who are interested in other projects like Indy. They may also have some good ideas about ways to keep translated documents in place. Maybe we create a similar lab project to https://github.com/hyperledger-labs/fabric-docs-cn, which is a project to translate the Fabric documentation. cc: @baohua

baohua (Thu, 01 Nov 2018 17:39:34 GMT):
Has joined the channel.

lijiachuan (Thu, 01 Nov 2018 22:27:51 GMT):
@tkuhrt thanks for your information, I will connect with @baohua

baohua (Fri, 02 Nov 2018 13:55:45 GMT):
thanks, and connected!

kdenhartog (Tue, 06 Nov 2018 00:39:29 GMT):
cool layout I found that would help us with developer outreach. This reminded me of our "disneyland doc" to help developers. https://developer.rchain.coop/

TechWritingWhiz (Tue, 06 Nov 2018 17:19:46 GMT):
Until official and regular maintainers exist for the documentation found in the Indy repo's (and thus change them), the standards as laid out here: https://wiki.hyperledger.org/projects/indy/contributing_docs for contributing the documentation need to be followed. Thank you.

mxs1491 (Thu, 08 Nov 2018 10:43:17 GMT):
Has joined the channel.

haggs (Fri, 09 Nov 2018 09:08:49 GMT):
Has joined the channel.

haggs (Fri, 09 Nov 2018 13:32:52 GMT):
[ ](https://chat.hyperledger.org/channel/indy-outreach?msg=SDsNNfsaDwcyBBrq4) @kdenhartog It's picking up steam! I think we should lock down at a safe version of libindy (1.6.2) and maybe upgrade to python3.6...ideally align it with indy-agent. Then we could have some consistent documentation and upgrade the how-to's properly and fully with all error codes. Going through all how-to's is at least a 2-3 week process if done well in a teaching way.

InfoMiner (Sat, 17 Nov 2018 04:55:37 GMT):
first, I dropped this in #indy ... but then decided this might be the more appropriate channel

InfoMiner (Sat, 17 Nov 2018 04:55:39 GMT):
watch high maint

InfoMiner (Sat, 17 Nov 2018 04:56:20 GMT):
https://github.com/infominer33/awesome-decentralized-id

InfoMiner (Sat, 17 Nov 2018 04:57:03 GMT):
its just a draft and still can use a lot of work, but pretty useful as it stands

InfoMiner (Sat, 17 Nov 2018 05:00:05 GMT):
would love to get some input... I still have to go through the wiki a bit.. but if you have any resources you'd like included, let me know

baohua (Mon, 19 Nov 2018 03:31:44 GMT):
Has left the channel.

InfoMiner (Tue, 20 Nov 2018 10:07:41 GMT):
https://sovrin-discourse-uploads.s3.dualstack.us-east-1.amazonaws.com/original/1X/b1130a375e93a15b614e42d3fc22d825d78a95f1.jpeg

InfoMiner (Tue, 20 Nov 2018 10:09:15 GMT):
even if you already seen it, there is a linked ToC now...

InfoMiner (Tue, 20 Nov 2018 10:11:26 GMT):
\mapsto

InfoMiner (Tue, 20 Nov 2018 10:12:47 GMT):
⟹

esplinr (Tue, 20 Nov 2018 23:27:43 GMT):
That is really useful @InfoMiner !

kdenhartog (Mon, 26 Nov 2018 23:47:16 GMT):
@mboyd @burdettadam any update on this HIPE? https://github.com/hyperledger/indy-hipe/pull/24

mboyd (Mon, 26 Nov 2018 23:57:12 GMT):
Good question! I've been working on a central readthedocs website that will build documentation from each of our respective repos. Today I just finished a prototype of it. The content is still a little outdated, but I think the framework will really allow us to improve developer outreach. I'm going to write up a hipe on it tonight, I think we can just close the PR you are referencing and open a new one. If you'd like to take a sneak peak, here's what I've been building: http://sovrin.readthedocs.io

mboyd (Mon, 26 Nov 2018 23:57:41 GMT):
Id appreciate ant feedback you can give me on the hipe once its been written

kdenhartog (Tue, 27 Nov 2018 00:03:51 GMT):
Yea, I'll give this a look. @TechWritingWhiz I'd guess you'll want to take a look at this too.

mboyd (Tue, 27 Nov 2018 00:05:59 GMT):
Each of the repositories have the option to build their docs locally, or host their own version online, but I've provided some extra features on Sovrin's readthedocs site to build all of the repositories together I haven't edited any of the content yet, except for a little bit of organizing on the Indy-SDK repo. I'd love to get your feedback as I write my HIPE proposal

mboyd (Tue, 27 Nov 2018 00:07:31 GMT):
These have all been built from my forks of the repository [found here](https://github.com/michaeldboyd?utf8=%E2%9C%93&tab=repositories&q=indy&type=&language=)

mboyd (Tue, 27 Nov 2018 00:08:21 GMT):
I've only added 4 of the indy repositories, but my plan is to add all of them. (ok, now I'll go write a HIPE)

kdenhartog (Tue, 27 Nov 2018 00:09:20 GMT):
@mboyd On first quick glance this looks awesome! The one thing I'd add in the HIPE is how a person who wants to contribute to docs can add content, what the contribution process is, and link to this in the Introduction page so we can community source the content over time.

infominer33 (Tue, 27 Nov 2018 06:02:28 GMT):
Has joined the channel.

infominer33 (Tue, 27 Nov 2018 06:03:14 GMT):
thanks @esplinr ! I'm now working on one more specific to sovrin\indy

infominer33 (Tue, 27 Nov 2018 06:04:19 GMT):
https://github.com/infominer33/awesome-decentralized-id/tree/master/awesome-sovrin

infominer33 (Tue, 27 Nov 2018 06:05:30 GMT):
thanks for the work you did on the Edx course @swcurran much appreciated

infominer33 (Tue, 27 Nov 2018 06:06:25 GMT):
generally speaking both sovrin and indy have really improved their documentation over the past few months. then again, I'm just starting to understand what I'm looking at, too

swcurran (Tue, 27 Nov 2018 07:54:37 GMT):
FYI @mboyd - I just did a big update to our VON_anchor (a python equivalent to libvcx) ReadTheDocs repo - check it out: https://von-anchor.readthedocs.io/en/latest/ I added the prose sections (Anchors, Anchor Interactions, etc.), and we already had the auto-generated extractions from the code ("Code: VON Anchor Packages"). The source for the docs are here: https://github.com/PSPC-SPAC-buyandsell/von_anchor/tree/master/docs/source

swcurran (Tue, 27 Nov 2018 07:56:21 GMT):
It might be helpful for you as you provide guidance to folks on how to do this. RST is a little obscure - not my favourite - but got it working in the end. It's handling of headings is just silly (IMHO :-) ), and tables are a pain - much worse than markdown.

swcurran (Tue, 27 Nov 2018 07:59:58 GMT):
I've also created a bash/docker script I can run locally to generate the docs locally and test them out. This saves having to install and setup sphinx - the docker image contains it, so as long as I have docker and bash, I'm able to run locally.

mboyd (Tue, 27 Nov 2018 15:24:20 GMT):
@swcurran This will be helpful! Good job. RST isn't my favorite either, so I think I'm going to continue support of markdown files, and have the .rst files just act as the framework for sphinx. What rst lacks, I think sphinx more than makes up for in its power and ease of use. If you end up wanting the functionality to combine multiple repositories on one readthedocs site, let me know and I'll be happy to share the process I used

kdenhartog (Tue, 27 Nov 2018 23:27:28 GMT):
@mboyd How do I change the links in the sovrin read the docs? The getting started for the Intro links to the deprecated version, which should link to the SDK version.

kdenhartog (Tue, 27 Nov 2018 23:28:05 GMT):
Eventually, I'll try to get my Indy Dev to be the original guide, but it's not to the point where I want it yet.

kdenhartog (Tue, 27 Nov 2018 23:28:54 GMT):
Still need to fix how-to guides and incorporate agents and Stephen C's education course work.

kdenhartog (Tue, 27 Nov 2018 23:29:18 GMT):
and make it docker-compose based (adding these so I can refer back when I update the repo of next things to do.)

mboyd (Tue, 27 Nov 2018 23:30:46 GMT):
Right now I'm building it off of my forked indy-sdk repo, I think you could probably find the relevant document on the upstream repo and submit a pr? Once I can merge in the sphinx changes as well it will build correctly. Yes! Let's try to make a clear path to successful Indy onboarding and link to any and all useful educational resources

mboyd (Wed, 28 Nov 2018 21:46:33 GMT):
@kdenhartog @swcurran I've published my HIPE for a new Indy documentation framework: https://github.com/hyperledger/indy-hipe/pull/63 I've also changed the prototype a bit to be purely within the Indy scope: http://indy.readthedocs.io

mboyd (Wed, 28 Nov 2018 21:46:48 GMT):
Let me know your feedback on the HIPE if you get a chance!

mboyd (Wed, 28 Nov 2018 21:55:41 GMT):
@TechWritingWhiz ^^

tkuhrt (Thu, 29 Nov 2018 01:57:15 GMT):
@mboyd : Would you be amenable to us changing https://www.hyperledger.org/projects/hyperledger-indy to link to this documentation (https://indy.readthedocs.io) instead of the Github repos that we do right now in the "Get Started with Hyperledger Indy" section of the web page? Or should we leave it for now?

mboyd (Thu, 29 Nov 2018 02:00:36 GMT):
I think that's a great idea @tkuhrt, but let's wait until the HIPE gets reviewed and the community is on board with the initiative

tkuhrt (Thu, 29 Nov 2018 02:02:29 GMT):
sounds good

mboyd (Thu, 29 Nov 2018 02:03:09 GMT):
The readthedocs site is still being built from my own forks of the repos, so it might be confusing if there are inconsistencies. I don't think there's a problem in informally telling people to go check it out right now, though.

tkuhrt (Thu, 29 Nov 2018 02:04:05 GMT):
Okay...we definitely want to wait until it is being built from the official repos. But I will definitely point people that direction who might be interested in looking at it.

Silona (Thu, 29 Nov 2018 17:02:17 GMT):
Has joined the channel.

jljordan_bcgov (Fri, 30 Nov 2018 04:00:56 GMT):
Has joined the channel.

infominer33 (Tue, 04 Dec 2018 18:43:51 GMT):
https://medium.com/axiom-tech/hyperledger-indy-the-future-of-decentralized-identity-9de5c2459e4e

infominer33 (Tue, 04 Dec 2018 18:44:34 GMT):
not sure if this is the best channel for this ^^^ pretty good overview of the history and ecosystem surrounding Indy

mboyd (Tue, 04 Dec 2018 22:07:42 GMT):
I have incorporated the changes proposed thus far to the [Indy Documentation HIPE](https://github.com/michaeldboyd/indy-rfc/blob/master/text/indy-docs-framework/README.md) in the [Pull Request](https://github.com/hyperledger/indy-hipe/pull/63), and would like to invite all here to give any final feedback or improvements to it. The community is unofficially using the prototyped indy.readthedocs.io that is currently being built off of my own forks of the Indy repos. Merging this HIPE will allow us to build the docs through the original repos.

esplinr (Thu, 06 Dec 2018 00:09:50 GMT):
@mboyd : Have you embedded a Google Analytics ID into the docs? I would love to see how many people are visiting the different pages.

esplinr (Thu, 06 Dec 2018 00:10:00 GMT):
@infominor

esplinr (Thu, 06 Dec 2018 00:10:00 GMT):
@infominer33 Thanks for sharing the link.

kdenhartog (Thu, 06 Dec 2018 17:18:34 GMT):
I'm hesitant, but not completely opposed to tracking people reading the docs as a matter of example. Only reason I'm not completely opposed is because it generally doesn't reveal too much info to us, but Google keeps gobbling the data in.

esplinr (Thu, 06 Dec 2018 22:10:48 GMT):
Without the data, it is really hard to tell how to improve the documentation.

kdenhartog (Thu, 06 Dec 2018 22:47:10 GMT):
yeah, there would be some great value in knowing it. There's the alternative method of having people tell us what parts of our docs aren't good as well as identifying the persistent questions that people ask. Main reason I bring it up is because I want us limit our use of tracking as much as possible so we learn new methods to gather data with consent, but if I'm the only one bringing this concern up then don't let me hold it back.

kdenhartog (Thu, 06 Dec 2018 22:48:29 GMT):
Also, I can't complain about this too much because my blog uses google analytics. I've yet to remove it, but I've strongly considered it so far.

infominer33 (Fri, 07 Dec 2018 05:09:22 GMT):
ooh ooh, pick me!

infominer33 (Fri, 07 Dec 2018 05:09:37 GMT):
hehe

infominer33 (Fri, 07 Dec 2018 05:10:24 GMT):
I like complaining about documentation, and I plan on spending quite a bit of time in the indy docs over the next month or so

infominer33 (Fri, 07 Dec 2018 05:14:45 GMT):
Its been a while, but I put this together: https://www.ernesto.net/hyperledger-indy-architecture/

infominer33 (Fri, 07 Dec 2018 05:15:19 GMT):
I remember having to go everywhere to patch that material together

infominer33 (Fri, 07 Dec 2018 05:15:19 GMT):
I remember going everywhere to put that together

infominer33 (Fri, 07 Dec 2018 05:15:35 GMT):
it would be nice to have something like that in the docs

infominer33 (Fri, 07 Dec 2018 05:15:35 GMT):
it would be nice to have something like that in the docs where you get the whole system in a glance

infominer33 (Fri, 07 Dec 2018 05:17:26 GMT):
but probably I left out a few points :shrug_tone2:

infominer33 (Fri, 07 Dec 2018 05:28:44 GMT):
https://www.ernesto.net/ernesto-net-5-minute-course-on-indy-and-what-goes-on-the-blockchain-ledger/

infominer33 (Fri, 07 Dec 2018 05:32:36 GMT):
the sovrin version is a bit wordy and maybe not straightforward enough, imo idk if indy has its own version yet

infominer33 (Fri, 07 Dec 2018 05:32:36 GMT):
the sovrin version is a bit wordy and maybe not straightforward enough, imo i dont think indy has its own version

infominer33 (Fri, 07 Dec 2018 05:51:02 GMT):
I would have shared here, but I didn't know it had been published already.

mboyd (Fri, 07 Dec 2018 15:19:00 GMT):
Hi all, would there be any interest in this group to do an informal call in the next several days to discuss our progress for indy outreach and set some community goals? I think if we can coordinate our efforts better, we'll be able to drive adoption and get rid of roadblockers more quickly.

mboyd (Fri, 07 Dec 2018 15:19:38 GMT):
I know some people don't want to create more calls, but I think there is a genuine need for us to coordinate in closer lockstep

mboyd (Fri, 07 Dec 2018 15:21:33 GMT):
Let me know if you'd be interested in joining, and I'll find a time next week that works for as many of us as possible

esplinr (Fri, 07 Dec 2018 21:23:13 GMT):
@mboyd I like the idea

esplinr (Fri, 07 Dec 2018 21:23:49 GMT):
@infominer33 I agree with the need for a broad overview. Now that stuff is being published to readthedocs, you can submit a PR with the improvements you are suggesting.

tkuhrt (Fri, 07 Dec 2018 23:08:30 GMT):
If you do decide to go forward with Google Analytics, Hyperledger has an account and can provide a project ID and access to view the information to folks with a Google account.

tkuhrt (Fri, 07 Dec 2018 23:08:53 GMT):
Just let @rjones or myself know.

infominer33 (Sat, 08 Dec 2018 12:40:51 GMT):
thank you! I'm going to keep working on my end of things and try to figure out how best to participate

kdenhartog (Sat, 08 Dec 2018 13:58:28 GMT):
https://twitter.com/dakami/status/1071333397136531456?s=19

kdenhartog (Sat, 08 Dec 2018 13:59:06 GMT):
Semi relevant guide on how documentation might approach a problem

mboyd (Sat, 08 Dec 2018 20:10:37 GMT):
@kdenhartog That is a good video. I think we can really use multimedia in our docs. While text based instructions are necessary, I'd like us to use video demos/tutorials liberally if possible. @tkuhrt I think we will go ahead with the documentation analytics. Would you help us get connect to the Google account and project ID? This also brings up a good point - right now I have an account with Readthedocs that I've used to build the prototype indy.readthedocs.io. It will probably be better if we use hyperledgers account on readthedocs to host it. I'm not sure how fabric is doing it with their docs, but we may want to talk about the best way for HL to manage this new site as well. It will require minimal maintenance.

mxs1491 (Tue, 11 Dec 2018 08:51:03 GMT):
@mboyd Hello Michael, I am familiar with Sovrin and the overall architecture and concepts. I have installed and worked through the demo @swcurran went through on the weekly call a couple of weeks ago. Are there education or documentation tasks that are in the queue that would help cement knowledge, and help the project move forward? As a background, I have been more on the business side for the past while, but do have a programming background (though a little rusty).

mxs1491 (Tue, 11 Dec 2018 08:51:03 GMT):
@mboyd Hello Michael, I am familiar with Sovrin and the overall architecture and concepts. I have installed and worked through the demo @swcurran went through on the weekly call a couple of weeks ago. Are there education or documentation tasks that are in the queue that would help cement knowledge? As a background, I have been more on the business side for the past while, but do have a programming background (though a little rusty).

kdenhartog (Tue, 11 Dec 2018 20:27:17 GMT):
[ ](https://chat.hyperledger.org/channel/indy-outreach?msg=oBvPBPuzYWrnBSFNp) @mxs1491 check out anchor.readthedocs.io for some good documentation. Additionally @infominer33 work with in his awesome-decentralized-id links to quite a few good docs. https://github.com/infominer33/awesome-decentralized-id

kdenhartog (Tue, 11 Dec 2018 20:27:17 GMT):
@mxs1491 check out von-anchor.readthedocs.io for some good documentation. Additionally @infominer33 work with in his awesome-decentralized-id links to quite a few good docs. https://github.com/infominer33/awesome-decentralized-id

yisheng (Wed, 12 Dec 2018 03:41:20 GMT):
Has joined the channel.

mboyd (Wed, 12 Dec 2018 16:47:06 GMT):
@mxs1491 One of the biggest helps that we need is to refine our documentation to improve a new developer's experience with Hyperledger Indy. If you are willing, could you please analyze indy.readthedocs.io and tell me how to structure the docs so that new developers who are interested in using Indy within their applications have an easier time getting started? @infominer33's list is a great place to start. I'd love to add some of his things to our documentation. This will be a good task to start out with because it will require you to find the things that are working well, learn how to use them, and then help spread that knowledge throughout the community. Does that make sense? Let me know if you'd like to hop on a call at some point

mxs1491 (Wed, 12 Dec 2018 21:41:45 GMT):
[ ](https://chat.hyperledger.org/channel/indy-outreach?msg=DfmCWWcsMwKaCmaoC) @mboyd @mboyd I will take a look over the next couple of days and come back to you with any questions.

esplinr (Thu, 13 Dec 2018 00:34:06 GMT):
Incorporating into the Indy docs the work of @infominer33 and @kdenhartog would be super useful.

tkuhrt (Sat, 15 Dec 2018 08:24:01 GMT):
@mboyd : Sorry for my delay in getting back. Regarding the Google Analytics ID, we will need a website URL in order to set it up. Do you want me to set up the one that you have above (indy.readthedocs.io) or do you want me to wait until we have the final URL

mxs1491 (Mon, 17 Dec 2018 14:05:31 GMT):
@mboyd Hi Michael, I have looked through indy.readthedocs.io, looked at @infominer33 's work and here are some thoughts. Current readthedocs structure is pretty basic. infominer33's work provides nearly encyclopedic information around SSI which is excellent. I have also looked at Holochain's developer documentation (https://developer.holochain.org/guide/latest/) which I believe provides a good structure that could be used as a starting point for Indy to stitch this all together. I do have more questions than may be useful to resolve purely by chat, so let me know if you have some time this week to discuss.

infominer33 (Mon, 17 Dec 2018 16:58:26 GMT):
I'm getting around to the indy side of things as I go, @mxs1491 :bow: I'm just kinda methodical and want a thorough understanding of where Indy fits in the greater landscape (which paints quite a compelling picture, as I've learned)

infominer33 (Mon, 17 Dec 2018 16:59:43 GMT):
and really it's kinda difficult to piece together Evernym's history.. but I've basically got that in order

infominer33 (Mon, 17 Dec 2018 17:02:36 GMT):
right now I'm beginning my research into really filling the gaps around */awesome-indy* https://github.com/infominer33/awesome-decentralized-id/blob/master/awesome-indy/README.md which has gotten a lot of re-organization, and hope for it to be as "nearly encyclopedic" for indy as I can manage

infominer33 (Mon, 17 Dec 2018 17:04:10 GMT):
and by then I'll have a lot better understanding of the documentation, and how I could help

infominer33 (Mon, 17 Dec 2018 17:12:12 GMT):
oh, haha, I'm just seeing you responded to me over there, too

infominer33 (Mon, 17 Dec 2018 17:12:12 GMT):
oh, haha, I'm just seeing you responded to me over in #indy

infominer33 (Mon, 17 Dec 2018 17:12:12 GMT):
oh, haha, I'm just seeing you responded to me over in #indy too

mxs1491 (Mon, 17 Dec 2018 19:45:19 GMT):
@infominer33 I'm new to this, so welcome any comments/feedback. The structure of your effort versus readthedocs versus something like what Holochain has put together. All different flavors looking to achieve similar goals. Do you see any effort or technical capability reasons for a specific approach? My two cents would be that for all the work you are putting in, it would be an awful waste to have to re-lay out all that content to fit another 'style guide'. I do think the readthedocs or Holochain structure is a little more 'polished', but I don't have a good appreciation (yet) on how much extra work is added to meet that format.

infominer33 (Mon, 17 Dec 2018 19:47:08 GMT):
I'm pretty new, also, @mxs1491. I've been studying indy and ssi over the past 5 months, and this is my first time as part of an open source project, so I'm just figuring out where I fit in

infominer33 (Mon, 17 Dec 2018 19:51:20 GMT):
Indy needs readthedocs to have a polished presentation for the world. My efforts are a bit more expansive, also. Certainly there is room in the world for both indy.readthedocs and /awesome-ind /awesome-decentralized-id the readthedocs will have detailed documentation from 0 to :loop: specifically about what indy is, how it works, how to run it, to the end user experience where my github repos are mainly just supposed to be a collection of links that can assist in research "beyond the docs"

infominer33 (Mon, 17 Dec 2018 19:51:20 GMT):
Indy needs readthedocs to have a polished presentation for the world. My efforts are a bit more expansive, also. Certainly there is room in the world for both indy.readthedocs and /awesome-ind /awesome-decentralized-id the readthedocs will have detailed documentation from 0 to :loop: specifically about what indy is, how it works, how to run it, to the end user experience where my github repos are supposed to be a collection of links that can assist in research "beyond the docs"

infominer33 (Mon, 17 Dec 2018 19:51:20 GMT):
Indy needs readthedocs to have a polished presentation for the world. My efforts are a bit more expansive, also. There is room in the world for both indy.readthedocs and /awesome-indy /awesome-decentralized-id Readthedocs will have detailed documentation from 0 to :loop: specifically about what indy is, how it works, how to run it, to the end user experience where my github repos are supposed to be a collection of links that can assist in research "beyond the docs"

infominer33 (Mon, 17 Dec 2018 19:52:57 GMT):
everything, some of which is 3rd party documentation, needs to be linked or reproduced in the official documentation and lookin all pretty

infominer33 (Mon, 17 Dec 2018 19:52:57 GMT):
everything directly related to indy, some of which is 3rd party documentation, needs to be linked or reproduced in the official documentation and lookin all pretty

infominer33 (Mon, 17 Dec 2018 19:55:00 GMT):
https://hyperledger-fabric.readthedocs.io/en/release-1.3/ is a pretty shining example, as they've had the time and community support

infominer33 (Mon, 17 Dec 2018 19:57:25 GMT):
but from what I can tell, "the world" is kinda just starting to catch on to the fact of indy.. how transformative it is. so the docs gotta convey that, but it will take time.

mxs1491 (Mon, 17 Dec 2018 20:00:16 GMT):
Thanks for the pointer to the Hyperledger docs, I had not thought to look there. From the very quick scan, the approach looks very similar to what Holochain did, so good to see on the same thought pattern.

infominer33 (Mon, 17 Dec 2018 20:00:24 GMT):
I think specifically work that @esplinr was talking about incorporating into indy.readthedocs.io was reproductions of this material: https://www.ernesto.net/hyperledger-indy-architecture/ https://www.ernesto.net/ernesto-net-5-minute-course-on-indy-and-what-goes-on-the-blockchain-ledger/

infominer33 (Mon, 17 Dec 2018 20:01:30 GMT):
those are a nice start content wise, but the presentation could use work.

infominer33 (Mon, 17 Dec 2018 20:02:45 GMT):
that "what goes on the ledger" is more concise and precise (imo) than the sovrin whitepaper of that title

infominer33 (Mon, 17 Dec 2018 20:02:45 GMT):
this "what goes on the ledger" is more concise and precise (imo) than the sovrin whitepaper of that title

infominer33 (Mon, 17 Dec 2018 20:03:42 GMT):
and I don't think indy docs has an architecture page like that.. to describe the whole system in a page or two.

infominer33 (Mon, 17 Dec 2018 20:04:57 GMT):
and surely there are other details, and supporting information that could be filled in around that content and it will be glorious

swcurran (Mon, 17 Dec 2018 20:20:33 GMT):
FYI - readthedocs just inhales RST and markdown files, so the work that @infominer33 is doing could easily be sucked into readthedocs build process. Really just a matter of getting a good place to connect it in. There might need to be some minor structural changes, but not much - the formatting is handled by the automated RTD process. And it can continue to be accessed directly from github as it is now.

infominer33 (Tue, 18 Dec 2018 20:25:35 GMT):
to be clear, I think what I've been doing is great and all, but mostly it's just a collection of links. Although, if I were writing documentation for Indy, I would probably find it pretty handy as a reference. That said, everything I've created on github is cc0 with no restrictions, so there's no problem of reproducing it in whole or in parts via readthedocs. still, I've got a lot of work ahead of me before I'll have anything that *I* think is worthy of submitting to Indy Docs

xadhoom76 (Wed, 19 Dec 2018 18:22:05 GMT):
Has joined the channel.

esplinr (Wed, 19 Dec 2018 22:53:48 GMT):
I got some time on the agenda in tomorrow's working group call for us to talk about documentation. Will you be able to attend @mboyd ?

esplinr (Wed, 19 Dec 2018 22:54:35 GMT):
At a minimum, I want to discuss where the architecture docs are, and how the Evernym team is using the "design" subdirectory for our "POA / Plan of Attack" documents as we collaborate on new features. But it would be great to discuss ReadTheDocs as well.

esplinr (Wed, 19 Dec 2018 22:54:45 GMT):
Especially given your recent pull requests.

allisongs (Thu, 20 Dec 2018 03:57:43 GMT):
Has joined the channel.

mxs1491 (Thu, 20 Dec 2018 09:50:52 GMT):
@infominer33 Another couple links for your page: https://www.bundesblock.de/wp-content/uploads/2018/10/ssi-paper.pdf https://stories.jolocom.com/a-universal-identity-layer-we-can-only-build-together-e297ed5ae4ed

mboyd (Thu, 20 Dec 2018 15:55:54 GMT):
Yep, I'll be on that call

esplinr (Thu, 20 Dec 2018 16:47:25 GMT):
I hope that I showcased your work appropriately and that I didn't put you too much on the spot @mboyd . Thanks for your leadership with the documentation.

esplinr (Thu, 20 Dec 2018 16:47:48 GMT):
Sean mentioned yesterday that there was a spot in the schedule, and I wanted to discuss the design documentation, so I grabbed the spot without checking with you first.

esplinr (Thu, 20 Dec 2018 16:48:04 GMT):
Thanks for letting us cover both topics.

mboyd (Thu, 20 Dec 2018 18:21:27 GMT):
@esplinr it was a exactly the introduction I was hoping for, thank you for including it!

mxs1491 (Thu, 20 Dec 2018 18:52:17 GMT):
Hi @esplinr @mboyd I am interested in helping out with documentation, even if it is approaching from the 'user' side with a beginners mind.

mxs1491 (Thu, 20 Dec 2018 18:52:39 GMT):
(right now I'm won't even have to fake it.... :D)

esplinr (Thu, 20 Dec 2018 19:14:23 GMT):
That's great. Based on the conversation that you had with infominer33 and kdenhartog , I think that you are on the right track.

esplinr (Thu, 20 Dec 2018 19:14:23 GMT):
That's great @mxs1491 . Based on the conversation that you had with infominer33 and kdenhartog , I think that you are on the right track.

infominer33 (Fri, 21 Dec 2018 00:02:04 GMT):
excellent! thx for the link! @mxs1491 I look forward to catching up to speed with how the working groups go, and figuring out the workflow around here. I'll begin digging deep into indy docs around the new year, I'm still working on the necessary background \ introductory material

xadhoom76 (Fri, 21 Dec 2018 22:11:20 GMT):
Hi, i'm from italy and would like to help you, nathan told me to ask here about the needs of translation , i would do documentation in italian if needed.

esplinr (Fri, 21 Dec 2018 22:18:00 GMT):
Welcome @xadhoom76

esplinr (Fri, 21 Dec 2018 22:18:25 GMT):
You can learn about how to help with documentation here: https://github.com/hyperledger/indy-hipe/tree/master/text/0025-indy-docs-framework

esplinr (Fri, 21 Dec 2018 22:18:48 GMT):
We haven't discussed how to handle localized documentation yet. It would be great if you could propose something for us to discuss.

esplinr (Fri, 21 Dec 2018 22:19:00 GMT):
I think it's premature to translate the existing documentation, as we have discussed making significant changes.

xadhoom76 (Fri, 21 Dec 2018 22:19:16 GMT):
ah ok

esplinr (Fri, 21 Dec 2018 22:19:17 GMT):
@mboyd has been coordinating most of the effort.

mxs1491 (Thu, 10 Jan 2019 16:26:47 GMT):
@esplinr This channel has been pretty quiet for the holidays. Anything happening in this direction?

mxs1491 (Thu, 10 Jan 2019 16:27:02 GMT):
Still interested in helping out.

esplinr (Thu, 10 Jan 2019 17:24:15 GMT):
Happy New Year @mxs1491

esplinr (Thu, 10 Jan 2019 17:25:43 GMT):
I've been focused on other priorities. The last update I got was that @mboyd has documentation published to readthedocs. Now anyone who wants to take the initiative can start to reorganize and improve the docs by submitting PRs to the correct source code repositories.

esplinr (Thu, 10 Jan 2019 17:26:00 GMT):
Is that the current state @mboyd ?

mboyd (Thu, 10 Jan 2019 17:36:35 GMT):
We are in the middle of merging the pull requests and configuring the readthedocs site with an official hyperledger readthedocs account. You may view the beta version at indy.readthedocs.io.

mwherman2000 (Thu, 17 Jan 2019 16:59:55 GMT):
Has joined the channel.

mwherman2000 (Thu, 17 Jan 2019 17:00:35 GMT):
Hi from the INDY ARM guy ...I've just joined this channel (https://hyperonomy.com/2019/01/13/hyperledger-indy-sovrin-comprehensive-architecture-reference-model-arm/).

esplinr (Thu, 17 Jan 2019 17:00:48 GMT):
Welcome!

esplinr (Thu, 17 Jan 2019 17:01:16 GMT):
The main HIPE documenting our work: https://github.com/hyperledger/indy-plenum/pull/1044/files#diff-0412a8378ac39b168d3fef8e73ec0bbc

esplinr (Thu, 17 Jan 2019 17:01:34 GMT):
In the channel history, you can see some of the documentation people have drafted.

mwherman2000 (Thu, 17 Jan 2019 17:17:50 GMT):
[ ](https://chat.hyperledger.org/channel/indy-outreach?msg=eirNpHyzPqGSNakn6) Is this the correct URL? ...it's titled "INDY-1924: Catchup and audit design proposal (#1044)"

esplinr (Fri, 18 Jan 2019 18:38:06 GMT):
@mwherman2000 Sorry, copy and paste error.

esplinr (Fri, 18 Jan 2019 18:38:21 GMT):
This is the link I intended: https://github.com/hyperledger/indy-hipe/tree/master/text/0025-indy-docs-framework

mwherman2000 (Fri, 18 Jan 2019 18:44:19 GMT):
Have there been any (recent) discussions about standards and tool sets for modeling and diagrams? For example, I favor the Open Group ArchiMate standard for higher-level modeling using the Archi open source modeling tool as well as the OMG BPMN (Business Process Model and Notation) with the Camunda open source BPMN modeling tool. (Links to follow...)

mwherman2000 (Fri, 18 Jan 2019 18:44:19 GMT):
Has there been any (recent) discussions about standards and tool sets for modeling and diagrams? For example, I favor the Open Group ArchiMate standard for higher-level modeling using the Archi open source modeling tool as well as the OMG BPMN (Business Process Model and Notation) with the Camunda open source BPMN modeling tool. (Links to follow...)

mwherman2000 (Fri, 18 Jan 2019 18:44:19 GMT):
Has there been any (recent) discussions about standards and tool sets for visual modeling and diagrams? For example, I favor the Open Group ArchiMate standard for higher-level modeling using the Archi open source modeling tool as well as the OMG BPMN (Business Process Model and Notation) with the Camunda open source BPMN modeling tool. (Links to follow...)

mwherman2000 (Fri, 18 Jan 2019 18:45:44 GMT):
ArchiMate and Archi: http://pubs.opengroup.org/architecture/archimate3-doc/ and https://www.archimatetool.com/, respectively.

mwherman2000 (Fri, 18 Jan 2019 18:45:44 GMT):
ArchiMate and Archi: http://pubs.opengroup.org/architecture/archimate3-doc/ and https://www.archimatetool.com/, respectively. The INDY ARM is an example: https://hyperonomy.com/2019/01/13/hyperledger-indy-sovrin-comprehensive-architecture-reference-model-arm/

mwherman2000 (Fri, 18 Jan 2019 18:47:46 GMT):
BPMN and Camunda: https://en.wikipedia.org/wiki/Business_Process_Model_and_Notation and https://camunda.com/download/modeler/, respectively.

kdenhartog (Fri, 18 Jan 2019 22:29:26 GMT):
I don't believe so. We've not had much work on visual modeling or diagrams either other than your work so at this point I'd consider what ever you chose de facto.

jljordan_bcgov (Sun, 20 Jan 2019 00:16:34 GMT):
PUML is used for interaction diagrams, class diagrams, and high level architecture as it's text based and therefore open and version controllable

jljordan_bcgov (Sun, 20 Jan 2019 00:17:00 GMT):
eg https://vonx.io/getting_started/bc-architecture/

jljordan_bcgov (Sun, 20 Jan 2019 00:17:00 GMT):
eg https://vonx.io/getting_started/bc-architecture/ and https://von-anchor.readthedocs.io/en/latest/design/class-hierarchy.html

kdenhartog (Mon, 21 Jan 2019 03:35:43 GMT):
I hadn't thought of PUML in that context. Thanks for pointing it out @jljordan_bcgov. Has anyone tried building architecture diagrams with PUML? I believe it can be done based on a quick search, but I haven't tried it before.

mwherman2000 (Mon, 21 Jan 2019 12:03:38 GMT):
[ ](https://chat.hyperledger.org/channel/indy-outreach?msg=8WR5c2RNny4cN26aD) Both the ArchiMate and BPMN model languages are text based as well (XML) - with specific schema defined by their respective standards (XML) for help ensure interoperability between modeling tools. They are open and version controllable. Archi, the open source modeling tool also supports direct integration with Github: https://github.com/archimatetool/archi-modelrepository-plugin.

mwherman2000 (Mon, 21 Jan 2019 12:03:38 GMT):
[ ](https://chat.hyperledger.org/channel/indy-outreach?msg=8WR5c2RNny4cN26aD) Both the ArchiMate and BPMN modeling languages are text based as well (XML) - with specific schema defined by their respective standards (XML) for help ensure interoperability between modeling tools. They are open and version controllable. Archi, the open source modeling tool also supports direct integration with Github: https://github.com/archimatetool/archi-modelrepository-plugin. Both ArchiMate and BPMN are creating actual models; for example, they are queryable. Metadata can be attached to any element or relationship.

mwherman2000 (Mon, 21 Jan 2019 12:04:11 GMT):
[ ](https://chat.hyperledger.org/channel/indy-outreach?msg=8WR5c2RNny4cN26aD) Are there any visual modeling apps for PUML?

mwherman2000 (Mon, 21 Jan 2019 12:04:11 GMT):
[ ](https://chat.hyperledger.org/channel/indy-outreach?msg=8WR5c2RNny4cN26aD) Are there any visual modeling apps for PUML? [I couldn't find as part of a quick google search for "PlantUML" as well as pursuing http://plantuml.com/]

mwherman2000 (Mon, 21 Jan 2019 12:04:11 GMT):
[ ](https://chat.hyperledger.org/channel/indy-outreach?msg=8WR5c2RNny4cN26aD) Are there any visual modeling apps for PUML? [I couldn't find any as part of a quick google search for "PlantUML" as well as pursuing http://plantuml.com/]

mwherman2000 (Mon, 21 Jan 2019 12:04:11 GMT):
[ ](https://chat.hyperledger.org/channel/indy-outreach?msg=8WR5c2RNny4cN26aD) Are there any visual modeling apps for PUML? [I couldn't find any modeling tool as part of a quick google search for "PlantUML" as well as pursuing http://plantuml.com/]

mwherman2000 (Mon, 21 Jan 2019 12:04:11 GMT):
[ ](https://chat.hyperledger.org/channel/indy-outreach?msg=8WR5c2RNny4cN26aD) Are there any visual modeling apps for PUML? [I couldn't find any modeling tools as part of a quick google search for "PlantUML" as well as pursuing http://plantuml.com/]

mwherman2000 (Mon, 21 Jan 2019 12:07:44 GMT):
[ ](https://chat.hyperledger.org/channel/indy-outreach?msg=8WR5c2RNny4cN26aD) Is Plant UML the drawing language you're referring?

mwherman2000 (Mon, 21 Jan 2019 12:07:44 GMT):
[ ](https://chat.hyperledger.org/channel/indy-outreach?msg=8WR5c2RNny4cN26aD) Is Plant UML the drawing language you're referring to? https://www.google.com/search?q=%22plant+uml%22+modeling+tools

mwherman2000 (Mon, 21 Jan 2019 12:07:44 GMT):
[ ](https://chat.hyperledger.org/channel/indy-outreach?msg=8WR5c2RNny4cN26aD) Is it the Plant UML drawing language that you are referring to? https://www.google.com/search?q=%22plant+uml%22+modeling+tools

mwherman2000 (Mon, 21 Jan 2019 15:50:59 GMT):
@kdenhartog Is there a diagram that visualizes the main steps in the `indy-dev` `getting_started.py` script (https://github.com/kdenhartog/indy-dev#test-python-environment)? ...either exactly (or anything close that I can build off of). It's a very good example - thank you.

kdenhartog (Mon, 21 Jan 2019 16:10:40 GMT):
No, not at this time. If you want to create one it would be useful for both Indy-dev and the official getting started guide because they're the same.

mwherman2000 (Mon, 21 Jan 2019 17:27:42 GMT):
[ ](https://chat.hyperledger.org/channel/indy-outreach?msg=936d323d-fb39-40c5-b8f3-d6149ac1da36) Thank you Kyle. 1. Is the following page the best/more accurate/more recent narration for the `getting_started.py` scenario? https://github.com/hyperledger/indy-sdk/blob/master/doc/getting-started/getting-started.md#infrastructure-preparation 2. I found this sequence diagram ...is it a good/current resource to use? https://github.com/hyperledger/indy-sdk/blob/master/doc/getting-started/getting-started.svg

mwherman2000 (Mon, 21 Jan 2019 17:27:42 GMT):
[ ](https://chat.hyperledger.org/channel/indy-outreach?msg=936d323d-fb39-40c5-b8f3-d6149ac1da36) Thank you @kdenhartog 1. Is the following page the best/more accurate/more recent narration for the `getting_started.py` scenario? https://github.com/hyperledger/indy-sdk/blob/master/doc/getting-started/getting-started.md#infrastructure-preparation 2. I found this sequence diagram ...is it a good/current resource to use? https://github.com/hyperledger/indy-sdk/blob/master/doc/getting-started/getting-started.svg

mwherman2000 (Mon, 21 Jan 2019 17:39:45 GMT):
@kdenhartog Does the Docker image created in `indy-dev` have a _Ledger Browser/Ledger Explorer_? If so, how do you invoke it?

haggs (Mon, 21 Jan 2019 18:46:41 GMT):
@mwherman2000 Not to my knowledge, but it's been a while since I've played around with the repo. I can let @kdenhartog answer, but your best bet would be the `std_out` of one of the nodes from the docker `indy-pool.dockerfile`

haggs (Mon, 21 Jan 2019 18:46:46 GMT):
https://github.com/kdenhartog/indy-dev/blob/20eb31e03dbe7ff7d01c04241acf41b8c7ca03ce/indy-pool.dockerfile#L61

haggs (Mon, 21 Jan 2019 18:47:04 GMT):
That's my best stab at finding out what you're maybe interested in

mwherman2000 (Mon, 21 Jan 2019 22:13:17 GMT):
A follow-up question re: this sequence diagram: https://github.com/hyperledger/indy-sdk/blob/master/doc/getting-started/getting-started.svg . Question 1: Is this diagram/scenario used for any other Indy samples/demos besides the `getting_started.py" script (https://github.com/kdenhartog/indy-dev/blob/master/python/getting_started.py)? The reason I'm asking is that it suggests there's an agent in addition to a wallet for each of the Actors (e.g. Sovrin Steward, Government, Faber, and Trust). From reading the Python code, I don't think this is technically accurate. For example, ... ``` logger.info("\"{}\" -> Anoncrypt connection response for \"{}\" with \"{} {}\" DID, verkey and nonce" .format(to, _from, to, _from)) connection_response = json.dumps({ 'did': to_from_did, 'verkey': to_from_key, 'nonce': connection_request['nonce'] }) anoncrypted_connection_response = await crypto.anon_crypt(from_to_verkey, connection_response.encode('utf-8')) logger.info("\"{}\" -> Send anoncrypted connection response to \"{}\"".format(to, _from)) logger.info("\"{}\" -> Anondecrypt connection response from \"{}\"".format(_from, to)) decrypted_connection_response = \ json.loads((await crypto.anon_decrypt(from_wallet, from_to_key, anoncrypted_connection_response)).decode("utf-8")) ``` Question 2: It looks like the `run()` method calling into the Indy SDK API to work directly with Wallets and the Ledger. i.e. `getting_started.py` doesn't create or use any actual agents. Can someone confirm this? If true, then getting-started.svg is well... ...sort of... misleading.

mwherman2000 (Mon, 21 Jan 2019 22:13:17 GMT):
A follow-up question re: this sequence diagram: https://github.com/hyperledger/indy-sdk/blob/master/doc/getting-started/getting-started.svg . Question 1: Is this diagram/scenario used for any other Indy samples/demos besides the `getting_started.py" script (https://github.com/kdenhartog/indy-dev/blob/master/python/getting_started.py)? The reason I'm asking is that it suggests there's an agent in addition to a wallet for each of the Actors (e.g. Sovrin Steward, Government, Faber, and Trust). From reading the Python code, I don't think this is technically accurate. For example, this "Send.../ receive..." is a no-op... ``` logger.info("\"{}\" -> Send anoncrypted connection response to \"{}\"".format(to, _from)) logger.info("\"{}\" -> Anondecrypt connection response from \"{}\"".format(_from, to)) decrypted_connection_response = \ json.loads((await crypto.anon_decrypt(from_wallet, from_to_key, anoncrypted_connection_response)).decode("utf-8")) ``` Question 2: It looks like the `run()` method calling into the Indy SDK API to work directly with Wallets and the Ledger. i.e. `getting_started.py` doesn't create or use any actual agents. Can someone confirm this? If true, then getting-started.svg is well... ...sort of... misleading.

mwherman2000 (Mon, 21 Jan 2019 22:13:17 GMT):
A follow-up question re: this sequence diagram: https://github.com/hyperledger/indy-sdk/blob/master/doc/getting-started/getting-started.svg . Question 1: Is this diagram/scenario used for any other Indy samples/demos besides the `getting_started.py" script (https://github.com/kdenhartog/indy-dev/blob/master/python/getting_started.py)? The reason I'm asking is that it suggests there's an agent in addition to a wallet for each of the Actors (e.g. Sovrin Steward, Government, Faber, and Trust). From reading the Python code, I don't think this is technically accurate. For example, this "Send.../ receive..." is a no-op... ``` logger.info("\"{}\" -> Send anoncrypted connection response to \"{}\"".format(to, _from)) logger.info("\"{}\" -> Anondecrypt connection response from \"{}\"".format(_from, to)) decrypted_connection_response = \ json.loads((await crypto.anon_decrypt(from_wallet, from_to_key, anoncrypted_connection_response)).decode("utf-8")) ``` Question 2: It looks like the `run()` method calling into the Indy SDK API to work directly with Wallets and the Ledger. i.e. `getting_started.py` doesn't create or use any actual agents. Can someone confirm this? If true, then `getting-started.svg` is well... ...sort of... ...a bit... misleading.

mwherman2000 (Mon, 21 Jan 2019 22:13:17 GMT):
A follow-up question re: this sequence diagram: https://github.com/hyperledger/indy-sdk/blob/master/doc/getting-started/getting-started.svg . Question 1: Is this diagram/scenario used for any other Indy samples/demos besides the `getting_started.py` script (https://github.com/kdenhartog/indy-dev/blob/master/python/getting_started.py)? The reason I'm asking is that it suggests there's an agent in addition to a wallet for each of the Actors (e.g. Sovrin Steward, Government, Faber, and Trust). From reading the Python code, I don't think this is technically accurate. For example, this "Send.../ receive..." is a no-op... ``` logger.info("\"{}\" -> Send anoncrypted connection response to \"{}\"".format(to, _from)) logger.info("\"{}\" -> Anondecrypt connection response from \"{}\"".format(_from, to)) decrypted_connection_response = \ json.loads((await crypto.anon_decrypt(from_wallet, from_to_key, anoncrypted_connection_response)).decode("utf-8")) ``` Question 2: It looks like the `run()` method calling into the Indy SDK API to work directly with Wallets and the Ledger. i.e. `getting_started.py` doesn't create or use any actual agents. Can someone confirm this? If true, then `getting-started.svg` is well... ...sort of... ...a bit... misleading.

mwherman2000 (Mon, 21 Jan 2019 22:13:17 GMT):
A follow-up question re: this sequence diagram: https://github.com/hyperledger/indy-sdk/blob/master/doc/getting-started/getting-started.svg . Question 1: Is this diagram/scenario used for any other Indy samples/demos besides the `getting_started.py` script (https://github.com/kdenhartog/indy-dev/blob/master/python/getting_started.py)? The reason I'm asking is that it suggests there's an agent in addition to a wallet for each of the Actors (e.g. Sovrin Steward, Government, Faber, and Thrift). From reading the Python code, I don't think this is technically accurate. For example, this "Send.../ receive..." is a no-op... ``` logger.info("\"{}\" -> Send anoncrypted connection response to \"{}\"".format(to, _from)) logger.info("\"{}\" -> Anondecrypt connection response from \"{}\"".format(_from, to)) decrypted_connection_response = \ json.loads((await crypto.anon_decrypt(from_wallet, from_to_key, anoncrypted_connection_response)).decode("utf-8")) ``` Question 2: It looks like the `run()` method calling into the Indy SDK API to work directly with Wallets and the Ledger. i.e. `getting_started.py` doesn't create or use any actual agents. Can someone confirm this? If true, then `getting-started.svg` is well... ...sort of... ...a bit... misleading.

mwherman2000 (Mon, 21 Jan 2019 22:13:17 GMT):
A follow-up question re: this sequence diagram: https://github.com/hyperledger/indy-sdk/blob/master/doc/getting-started/getting-started.svg . Question 1: Is this diagram/scenario used for any other Indy samples/demos besides the `getting_started.py` script (https://github.com/kdenhartog/indy-dev/blob/master/python/getting_started.py)? The reason I'm asking is that it suggests there's an agent in addition to a wallet for each of the Actors (e.g. Sovrin Steward, Government, Faber, and Thrift). From reading the Python code, I don't think this is technically accurate. For example, this "Send.../ receive..." is a no-op... ``` logger.info("\"{}\" -> Send anoncrypted connection response to \"{}\"".format(to, _from)) logger.info("\"{}\" -> Anondecrypt connection response from \"{}\"".format(_from, to)) decrypted_connection_response = \ json.loads((await crypto.anon_decrypt(from_wallet, from_to_key, anoncrypted_connection_response)).decode("utf-8")) ``` Question 2: It looks like the `run()` method is calling into the Indy SDK API to work directly with Wallets and the Ledger. i.e. `getting_started.py` doesn't create or use any actual agents. Can someone confirm this? If true, then `getting-started.svg` is well... ...sort of... ...a bit... misleading.

mwherman2000 (Mon, 21 Jan 2019 22:13:17 GMT):
A follow-up question re: this sequence diagram: https://github.com/hyperledger/indy-sdk/blob/master/doc/getting-started/getting-started.svg . Question 1: Is this diagram/scenario used for any other Indy samples/demos besides the `getting_started.py` script (https://github.com/kdenhartog/indy-dev/blob/master/python/getting_started.py)? The reason I'm asking is that it suggests there's an agent in addition to a wallet for each of the Actors (e.g. Sovrin Steward, Government, Faber, and Thrift). From reading the Python code, I don't think this is technically accurate. For example, this "Send.../ receive..." is a no-op... ``` logger.info("\"{}\" -> Send anoncrypted connection response to \"{}\"".format(to, _from)) logger.info("\"{}\" -> Anondecrypt connection response from \"{}\"".format(_from, to)) decrypted_connection_response = \ json.loads((await crypto.anon_decrypt(from_wallet, from_to_key, anoncrypted_connection_response)).decode("utf-8")) ``` Question 2: It looks like the `run()` method is calling into the Indy SDK API to work directly with Wallets and the Ledger. i.e. `getting_started.py` doesn't create or use any actual agents. Can someone confirm this? If true, then `getting-started.svg` is well... ...sort of... ...a bit... misleading?

mwherman2000 (Mon, 21 Jan 2019 22:13:17 GMT):
A follow-up question re: this sequence diagram: https://github.com/hyperledger/indy-sdk/blob/master/doc/getting-started/getting-started.svg . Question 1: Is this diagram/scenario used for any other Indy samples/demos besides the `getting_started.py` script (https://github.com/kdenhartog/indy-dev/blob/master/python/getting_started.py)? The reason I'm asking is that it suggests there's an agent in addition to a wallet for each of the Actors (e.g. Sovrin Steward, Government, Faber, and Thrift). From reading the Python code, I don't think this is technically accurate. For example, this "Send.../ receive..." is a no-op... ``` logger.info("\"{}\" -> Send anoncrypted connection response to \"{}\"".format(to, _from)) logger.info("\"{}\" -> Anondecrypt connection response from \"{}\"".format(_from, to)) decrypted_connection_response = \ json.loads((await crypto.anon_decrypt(from_wallet, from_to_key, anoncrypted_connection_response)).decode("utf-8")) ``` Question 2: It looks like the `run()` method is calling into the Indy SDK API to work directly with Wallets and the Ledger. i.e. `getting_started.py` doesn't create or use any actual agents. In effect, `run()` is simulating all of the agents at once. Can someone confirm this? If true, then `getting-started.svg` is well... ...sort of... ...a bit... misleading?

mwherman2000 (Mon, 21 Jan 2019 22:13:17 GMT):
@kdenhartog A follow-up question re: this sequence diagram: https://github.com/hyperledger/indy-sdk/blob/master/doc/getting-started/getting-started.svg . Question 1: Is this diagram/scenario used for any other Indy samples/demos besides the `getting_started.py` script (https://github.com/kdenhartog/indy-dev/blob/master/python/getting_started.py)? The reason I'm asking is that it suggests there's an agent in addition to a wallet for each of the Actors (e.g. Sovrin Steward, Government, Faber, and Thrift). From reading the Python code, I don't think this is technically accurate. For example, this "Send.../ receive..." is a no-op... ``` logger.info("\"{}\" -> Send anoncrypted connection response to \"{}\"".format(to, _from)) logger.info("\"{}\" -> Anondecrypt connection response from \"{}\"".format(_from, to)) decrypted_connection_response = \ json.loads((await crypto.anon_decrypt(from_wallet, from_to_key, anoncrypted_connection_response)).decode("utf-8")) ``` Question 2: It looks like the `run()` method is calling into the Indy SDK API to work directly with Wallets and the Ledger. i.e. `getting_started.py` doesn't create or use any actual agents. In effect, `run()` is simulating all of the agents at once. Can someone confirm this? If true, then `getting-started.svg` is well... ...sort of... ...a bit... misleading?

jljordan_bcgov (Mon, 21 Jan 2019 22:52:32 GMT):
[ ](https://chat.hyperledger.org/channel/indy-outreach?msg=vtZy9NCH5GszPEPEw) @mwherman2000 https://github.com/bcgov/von-network does have a ledger browser ... you can see various networks we have running for our dev and test environments on this page https://vonx.io/clickythings/#latest-development-environment

mwherman2000 (Mon, 21 Jan 2019 22:54:14 GMT):
[ ](https://chat.hyperledger.org/channel/indy-outreach?msg=2r5Mo5zgbG6Rspzs7) @jljordan_bcgov Does the VON docker image have the `python getting_started.py` example installed (from the `indy-dev` project)?

mwherman2000 (Mon, 21 Jan 2019 22:54:14 GMT):
[ ](https://chat.hyperledger.org/channel/indy-outreach?msg=2r5Mo5zgbG6Rspzs7) @jljordan_bcgov Does the VON docker image have the `python3 getting_started.py` example installed (from the `indy-dev` project)?

jljordan_bcgov (Tue, 22 Jan 2019 00:04:39 GMT):
@swcurran ^^

swcurran (Tue, 22 Jan 2019 00:28:58 GMT):
@mwherman2000 - not that I'm aware. Looks like there is no VON stuff in indy-dev.

kdenhartog (Tue, 22 Jan 2019 02:06:35 GMT):
@swcurran That's correct, however I do intend to bring your browser explorer in (higher priority) and later want the von-anchor work to be able to be worked with (lower priority). I'm especially keen to start building off their dev images.

kdenhartog (Tue, 22 Jan 2019 02:06:35 GMT):
@swcurran @mwherman2000 That's correct, `indy-dev` doesn't currently use any VON stuff. however I do intend to bring your browser explorer in (higher priority) and later want the von-anchor work to be able to be worked with (lower priority). I'm especially keen to start building off their dev images.

kdenhartog (Tue, 22 Jan 2019 02:06:35 GMT):
@swcurran @mwherman2000 That's correct, `indy-dev` doesn't currently use any VON stuff. however I do intend to bring their browser explorer in (higher priority) and later want the von-anchor work to be able to be worked with in that repo as well(lower priority). I'm especially keen to start building off their dev images.

ianco (Tue, 22 Jan 2019 17:44:40 GMT):
[ ](https://chat.hyperledger.org/channel/indy-outreach?msg=WCgnGpcZGDgnHvLTA) @mwherman2000 None of the python samples are in the VON image - just the sdk, python wrapper, postgres storage and CLI

swcurran (Tue, 22 Jan 2019 17:56:35 GMT):
FYI - VON Image has indy-node as well. It was small enough that it was easier to just have it included vs. a separate one for node and sdk. The image is still ubuntu 16.04-based, but some time was spent optimizing for size.

mwherman2000 (Tue, 22 Jan 2019 18:47:38 GMT):
@swcurran @jljordan_bcgov @kdenhartog I think it's important to have a single reference Docker image focused on the needs for new developers as well as experienced Indy developers. For example, one image to focus all of our documentation, etc. around.

swcurran (Tue, 22 Jan 2019 19:09:36 GMT):
Currently, there is only one docker image artifact that I'm aware of - von-image. I agree it's important, but no ring to rule them all is probably not right. But I agree that more sub-projects should consider a versioned container image as their artifact. On the other end of the specturm, I cringe when I hear suggestions about using specific github branches...

mwherman2000 (Wed, 23 Jan 2019 18:09:42 GMT):
FYI (what I'm working on next after the INDY ARM): Next I'm making a slow but deep dive into the Indy SDK. The first task (which I completed this "morning") was to create a set of flow diagrams that illustrate the 201 tasks that comprise the `https://github.com/kdenhartog/indy-dev/blob/master/python/getting_started.py` script. I've numbered each of the tasks in a hierarchical fashion (i.e. not a simple serial numbering scheme). I'm now working (with @kdenhartog 's guidance) to add these numbers into the `getting_started.py` script itself. So that we can have (caution: dirty word) strong correlation between the script code, the script logger msgs, the new diagrams, the sequence diagram (eventually) and the textual narration. We're tracking this here: https://github.com/kdenhartog/indy-dev/issues/17

mwherman2000 (Wed, 23 Jan 2019 18:09:42 GMT):
FYI (what I'm working on next after the INDY ARM): Next I'm making a slow but deep dive into the Indy SDK. The first task (which I completed this "morning") was to create a set of flow diagrams that illustrate the 201 tasks that comprise the `https://github.com/kdenhartog/indy-dev/blob/master/python/getting_started.py` script. I've numbered each of the tasks in a hierarchical fashion (i.e. not a simple serial numbering scheme). I'm now working (with @kdenhartog 's guidance) to add these numbers into the `getting_started.py` script itself. So that we can have (caution: dirty word ;-)) strong correlation between the script code, the script logger msgs, the new diagrams, the sequence diagram (eventually) and the textual narration. We're tracking this here: https://github.com/kdenhartog/indy-dev/issues/17

rjones (Wed, 23 Jan 2019 19:48:51 GMT):
Has left the channel.

mogamboizer (Thu, 24 Jan 2019 20:45:02 GMT):
Has joined the channel.

mwherman2000 (Fri, 25 Jan 2019 01:34:14 GMT):
[ ](https://chat.hyperledger.org/channel/indy-outreach?msg=mNq6DERFoxpeNesXZ) @swcurran @swcurran Does the VON Docker image run an actual Indy Agent? `getting_started.py` is somewhat unique in that is primarily a single Python function that calls directly into the SDK to work with Wallets and the Ledger directly ...no actual intermediary Agent (as far as I can tell).

mwherman2000 (Fri, 25 Jan 2019 01:34:14 GMT):
[ ](https://chat.hyperledger.org/channel/indy-outreach?msg=mNq6DERFoxpeNesXZ) @swcurran @swcurran Does the VON Docker image run an actual Indy Agent? The `getting_started.py` script is somewhat unique in that is primarily a single Python function that calls directly into the SDK to work with Wallets and the Ledger directly ...no actual intermediary Agent (as far as I can tell).

mwherman2000 (Fri, 25 Jan 2019 01:35:39 GMT):
First draft of the `getting_started.py` visualizations (flow diagrams) can be found here: https://hyperonomy.com/2019/01/24/indy-sdk-getting_started-py-visualizations-light-table/

swcurran (Fri, 25 Jan 2019 05:12:47 GMT):
@mwherman2000 - no it does not. It has indy-sdk (libindy), indy-node, python and two agent components (von_anchor - object model on indy-sdk, and von-x - indy agent web service based on von_anchor). We use those as the basis for the VON agents. That gives us a versioned entity on which to build our agents, and to operate indy networks (hence the inclusion of indy-node). The image makes our build process for what we are working on (agents, TheOrgBook) WAY faster than what is typically done.

firewater (Fri, 25 Jan 2019 12:59:59 GMT):
Has joined the channel.

mwherman2000 (Fri, 25 Jan 2019 15:19:37 GMT):
@swcurran To be more clear, I was asking about a headless Agent ...perhaps best referred to as a Cloud Agent (vs. an Edge Agent App)?

mwherman2000 (Fri, 25 Jan 2019 15:19:37 GMT):
@swcurran To be more clear, I was asking about a headless Agent ...perhaps best referred to as a Cloud Agent Node (vs. an Edge Agent App)?

mwherman2000 (Fri, 25 Jan 2019 15:19:37 GMT):
@swcurran To be more clear, I was asking about a headless Agent ...perhaps best referred to as a Cloud Agent Node (vs. an Edge Agent App)? ...elements (31) and (32) in the INDY ARM: https://hyperonomy.com/2019/01/13/hyperledger-indy-sovrin-comprehensive-architecture-reference-model-arm/

mwherman2000 (Sun, 27 Jan 2019 17:06:14 GMT):
FYI ...progress update: 1. The code and the output from the `getting_started.py` script is now numbered (and correlated with the flow model/diagrams): e.g. https://github.com/mwherman2000/indy-dev/blob/master/python/doc/getting_started-numbered.log 2. The flow model/diagrams are stabilizing: https://github.com/mwherman2000/indy-dev/tree/master/python/doc/images 3. I've dropped the images into a copy of `getting_started.md` ...still very rough ...At this point, I literally just dropped the images into the existing text. Fair bit of editing/tweaking to be completed. Here's what it currently looks like: e.g. https://github.com/mwherman2000/indy-dev/blob/master/python/doc/getting_started.md#step-0-connect-to-the-indy-nodes-pool Cheers, Michael

infominer33 (Mon, 28 Jan 2019 08:51:52 GMT):
https://github.com/infominer33/awesome-decentralized-id/blob/master/indy-sovrin-evernym/HyperledgerGlobalForum-VON-transcript.md

infominer33 (Mon, 28 Jan 2019 08:53:23 GMT):
Idk about anyone else, but I don't like having a video only source for information, so I made a start at cleaning up the transcript from youtube.

stefan.vogl (Tue, 29 Jan 2019 10:43:32 GMT):
Has joined the channel.

mwherman2000 (Wed, 30 Jan 2019 20:13:36 GMT):
@kdenhartog In `getting_started.py`, the generated DIDs don't have a scheme:method prefix. For example... ``` INFO:__main__:1.1.0 == Getting Trust Anchor credentials - Government Onboarding == INFO:__main__:------------------------------ INFO:__main__:1.1.1 "Sovrin Steward" -> Create and store in Wallet "Sovrin Steward Government" DID (from to) Create and store DID from DID: Th7MpTaRZVRYnPiabds81Y Create and store DID from_to DID: BuET6hZ72P1XxrxSjDamwK INFO:__main__:1.1.2 "Sovrin Steward" -> Send Nym to Ledger for "Sovrin Steward Government" DID (from to) SEND_NYM: {"reqId":1548802321443421300,"identifier":"Th7MpTaRZVRYnPiabds81Y","operation":{"dest":"BuET6hZ72P1XxrxSjDamwK","type":"1","verkey":"6wb6bzDPk9ER1hKLq1Bxm27anVmY5L7oUJ1A6CJgwqFK"},"protocolVersion":2} ``` Is there a series of SDK API calls that can be added to the script to add "did:mymethod" to the generated DIDs?

mwherman2000 (Wed, 30 Jan 2019 20:13:36 GMT):
@kdenhartog In `getting_started.py`, the generated DIDs don't have a scheme:method prefix. For example... ``` INFO:__main__:1.1.0 == Getting Trust Anchor credentials - Government Onboarding == INFO:__main__:------------------------------ INFO:__main__:1.1.1 "Sovrin Steward" -> Create and store in Wallet "Sovrin Steward Government" DID (from to) Create and store DID from DID: Th7MpTaRZVRYnPiabds81Y Create and store DID from_to DID: BuET6hZ72P1XxrxSjDamwK INFO:__main__:1.1.2 "Sovrin Steward" -> Send Nym to Ledger for "Sovrin Steward Government" DID (from to) SEND_NYM: {"reqId":1548802321443421300,"identifier":"Th7MpTaRZVRYnPiabds81Y","operation":{"dest":"BuET6hZ72P1XxrxSjDamwK","type":"1","verkey":"6wb6bzDPk9ER1hKLq1Bxm27anVmY5L7oUJ1A6CJgwqFK"},"protocolVersion":2} ``` Is there a simple series of SDK API calls that can be added to the script to add "did:mymethod" to the generated DIDs?

mwherman2000 (Wed, 30 Jan 2019 20:13:36 GMT):
@kdenhartog In `getting_started.py`, the generated DIDs don't have a scheme:method prefix. For example... ``` INFO:__main__:1.1.0 == Getting Trust Anchor credentials - Government Onboarding == INFO:__main__:------------------------------ INFO:__main__:1.1.1 "Sovrin Steward" -> Create and store in Wallet "Sovrin Steward Government" DID (from to) Create and store DID from DID: Th7MpTaRZVRYnPiabds81Y Create and store DID from_to DID: BuET6hZ72P1XxrxSjDamwK INFO:__main__:1.1.2 "Sovrin Steward" -> Send Nym to Ledger for "Sovrin Steward Government" DID (from to) SEND_NYM: {"reqId":1548802321443421300,"identifier":"Th7MpTaRZVRYnPiabds81Y","operation":{"dest":"BuET6hZ72P1XxrxSjDamwK","type":"1","verkey":"6wb6bzDPk9ER1hKLq1Bxm27anVmY5L7oUJ1A6CJgwqFK"},"protocolVersion":2} ``` Is there a simple series of SDK API calls that can be added to the script to add the prefix "did:mymethod:" to the generated DIDs?

haggs (Thu, 31 Jan 2019 01:12:00 GMT):
@mwherman2000 I think the literal strings could be added for the "did:method" onto those specific DID's

haggs (Thu, 31 Jan 2019 01:12:59 GMT):
Specifically in your example, this call 'await onboarding` https://github.com/kdenhartog/indy-dev/blob/20eb31e03dbe7ff7d01c04241acf41b8c7ca03ce/python/getting_started.py#L61

haggs (Thu, 31 Jan 2019 01:12:59 GMT):
Specifically in your example, this call ```await onboarding``` https://github.com/kdenhartog/indy-dev/blob/20eb31e03dbe7ff7d01c04241acf41b8c7ca03ce/python/getting_started.py#L61

haggs (Thu, 31 Jan 2019 01:16:20 GMT):
Are you looking to add them there or verbosity's sake? I don't think they would have the `did:method` inside of them, as they are just wallet config "id's" to be written to the ledger.

mwherman2000 (Thu, 31 Jan 2019 01:29:35 GMT):
[ ](https://chat.hyperledger.org/channel/indy-outreach?msg=HzrW876FWiNpwGXiT) @haggs That sounds like a bit of a hack. The underlying method is called `did.create_and_store_my_did()`, I expect the method to return a syntactically valid DID (i.e. with the did: schema and some sort of mymethod: ) - it's not. Code reference: https://github.com/kdenhartog/indy-dev/blob/20eb31e03dbe7ff7d01c04241acf41b8c7ca03ce/python/getting_started.py#L53 ...what you get back (for this specific call) is: ``` INFO:__main__:1.0.2 "Sovrin Steward" -> Create and store in Wallet DID from seed Sovrin Steward DID: Th7MpTaRZVRYnPiabds81Y ``` I would expect there is some sort of config settings or something that says the "domain" for all DIDs in this app are (for example): `did:mymethod:`

mwherman2000 (Thu, 31 Jan 2019 01:29:35 GMT):
[ ](https://chat.hyperledger.org/channel/indy-outreach?msg=HzrW876FWiNpwGXiT) @haggs That sounds like a bit of a hack. The underlying method is called `did.create_and_store_my_did()`, I expect the method to return a syntactically valid DID (i.e. with the did: schema and some sort of mymethod: ) - it's not. Code reference: https://github.com/kdenhartog/indy-dev/blob/20eb31e03dbe7ff7d01c04241acf41b8c7ca03ce/python/getting_started.py#L53 What you get back (for this specific call) is: ``` INFO:__main__:1.0.2 "Sovrin Steward" -> Create and store in Wallet DID from seed Sovrin Steward DID: Th7MpTaRZVRYnPiabds81Y ``` I would expect there is some sort of config settings or something that says the "domain" for all DIDs in this app are (for example): `did:mymethod:`

mwherman2000 (Thu, 31 Jan 2019 01:29:35 GMT):
[ ](https://chat.hyperledger.org/channel/indy-outreach?msg=HzrW876FWiNpwGXiT) @haggs That sounds like a bit of a hack. The underlying method is called `did.create_and_store_my_did()`, I expect the method to return a syntactically valid DID (i.e. with the did: schema and some sort of mymethod: ) - it's not. Code reference: https://github.com/kdenhartog/indy-dev/blob/20eb31e03dbe7ff7d01c04241acf41b8c7ca03ce/python/getting_started.py#L53 What you get back (for this specific call) is: ``` INFO:__main__:1.0.2 "Sovrin Steward" -> Create and store in Wallet DID from seed Sovrin Steward DID: Th7MpTaRZVRYnPiabds81Y ``` I would expect there to be some sort of config settings or something in the SDK/API that says the "domain" for all DIDs in this app are (for example): `did:mymethod:`

mwherman2000 (Thu, 31 Jan 2019 01:29:35 GMT):
[ ](https://chat.hyperledger.org/channel/indy-outreach?msg=HzrW876FWiNpwGXiT) @haggs That sounds like a bit of a hack. The underlying method is called `did.create_and_store_my_did()`, I expect the method to return a syntactically valid DID (i.e. with the did: schema and some sort of mymethod: ) - it's not. Code reference: https://github.com/kdenhartog/indy-dev/blob/20eb31e03dbe7ff7d01c04241acf41b8c7ca03ce/python/getting_started.py#L53 What you get back (for this specific call) is: ``` INFO:__main__:1.0.2 "Sovrin Steward" -> Create and store in Wallet DID from seed Sovrin Steward DID: Th7MpTaRZVRYnPiabds81Y ``` I would expect there to be some sort of config settings or something in the Indy SDK/API that says the "domain" for all DIDs in this app are (for example): `did:mymethod:`

mwherman2000 (Thu, 31 Jan 2019 01:35:16 GMT):
....or some sort of DID helper library that provides this functionality.

haggs (Thu, 31 Jan 2019 01:55:26 GMT):
@mwherman2000 I'm looking over at the DID Spec so our terminology is consistent (https://w3c-ccg.github.io/did-spec/)

haggs (Thu, 31 Jan 2019 02:01:23 GMT):
I think the correct terminology would be that the Indy SDK produces (or in actuality in Sovrin, the Indy CLI) a "specific-idstring", called "Sovrin Steward DID"

haggs (Thu, 31 Jan 2019 02:02:16 GMT):
This is written to the ledger and then taken into context to form the generic DID scheme, `did = "did:" method ":" specific-idstring"`

mwherman2000 (Thu, 31 Jan 2019 02:07:20 GMT):
Then these methods need to be renamed to reflect that and a new set of replacement methods (with the old method names) created that return valid DIDS.

haggs (Thu, 31 Jan 2019 02:08:16 GMT):
I'll say I'm by no means an expert on this and could be very wrong, maybe someone else can chime in to where I'm semantically messing everything up.

haggs (Thu, 31 Jan 2019 02:08:16 GMT):
Maybe someone else can help and chime in :D I'm confused as well

mwherman2000 (Thu, 31 Jan 2019 02:25:19 GMT):
Flipping this thread over to #indy-sdk ...

mwherman2000 (Thu, 31 Jan 2019 19:21:50 GMT):
Moving this thread back to #indy-outreach ... FYI: For https://github.com/mwherman2000/indy-dev/blob/master/python/getting_started-verbose.py to use syntactically valid DIDs (and not idstrings), I wrote some idstring <> DID wrappers: https://github.com/mwherman2000/indy-dev/blob/master/python/getting_started-verbose.py#L771-L815 Now `getting_started-verbose.py` only uses DIDs from a [workshop] developer perspective. For example, ``` INFO:__main__:1.1.1 "Sovrin Steward" -> Create and store in Wallet "Sovrin Steward Government" DID (from to) Create and store DID from DID: did:mymethod:Th7MpTaRZVRYnPiabds81Y Create and store DID from_to DID: did:mymethod:WDFUCaFHrqQdMhCgbVMZ6h INFO:__main__:1.1.2 "Sovrin Steward" -> Send NYM for "Sovrin Steward Government" DID (from to) to Ledger SEND_NYM: {"reqId":1548960780222513800,"identifier":"Th7MpTaRZVRYnPiabds81Y","operation":{"dest":"WDFUCaFHrqQdMhCgbVMZ6h","type":"1","verkey":"GvRZogqnpDf73aVCDLsWwoE8wHN4BZS5RQnj45zoZp2M"},"protocolVersion":2} INFO:__main__:1.1.3 "Sovrin Steward" -> Send Connection Request to Government with "Sovrin Steward Government" DID and Nonce (simulated) Connection Request: {"did": "did:mymethod:WDFUCaFHrqQdMhCgbVMZ6h", "nonce": 123456789} ``` idstrings are still used on the Ledger.

haggs (Thu, 31 Jan 2019 20:02:26 GMT):
Great work @mwherman2000!, I think that helper set of functions is PR worthy, at least for those wanting verbose and correct output just getting started!

vo2vo (Fri, 01 Feb 2019 04:43:16 GMT):
Has joined the channel.

mwherman2000 (Tue, 05 Feb 2019 15:43:16 GMT):
Links from Google search results are breaking: e.g. https://github.com/hyperledger/indy-node/blob/master/docs/transactions.md ...does it make sense to leave stubs or some sort of redirections in place?

mwherman2000 (Tue, 05 Feb 2019 15:44:00 GMT):
Original Google search query: https://www.google.com/search?q=nym+indy

nanspro (Wed, 06 Feb 2019 15:29:13 GMT):
Has joined the channel.

esplinr (Thu, 07 Feb 2019 23:45:36 GMT):
@SteveGoob Lynn mentioned that one of the last tasks for exiting Hyperledger incubation is to document Indy use cases. Do you know who is working on that task? Once you have a draft, @TechWritingWhiz and I can review it for you.

SteveGoob (Thu, 07 Feb 2019 23:45:36 GMT):
Has joined the channel.

SteveGoob (Thu, 07 Feb 2019 23:47:37 GMT):
So we've got a collaborative document for that was given to the community on the Indy WG call a couple weeks ago

esplinr (Thu, 07 Feb 2019 23:49:51 GMT):
I missed it. Do you have a link handy?

haggs (Fri, 08 Feb 2019 02:13:21 GMT):
@esplinr https://docs.google.com/document/d/1EMiqzdd-6TB2puzamDGJSLrDTwUz_QW46xdEp2FLnbI/edit if this is the one you're looking for

esplinr (Fri, 08 Feb 2019 23:35:20 GMT):
Thanks @haggs

esplinr (Fri, 08 Feb 2019 23:35:46 GMT):
@SteveGoob The document shared by haggs looks pretty complete. What is left before it can be submitted to Hyperledger?

SteveGoob (Fri, 08 Feb 2019 23:37:08 GMT):
That's the one, thank you @haggs

SteveGoob (Fri, 08 Feb 2019 23:39:07 GMT):
@esplinr, I want to get it reviewed for accuracy, completeness, and to make sure Indy does have all the functionality to provide for these use cases *right now*

SteveGoob (Fri, 08 Feb 2019 23:40:23 GMT):
Otherwise, it shouldn't be on the use cases document, as it's a metric for determining whether the product is complete enough for 1.0

SteveGoob (Fri, 08 Feb 2019 23:41:13 GMT):
If you have some eyes that could help out with that verification, it would be very appreciated.

esplinr (Fri, 08 Feb 2019 23:41:30 GMT):
Thanks. That sounds like something @techwritingw

esplinr (Fri, 08 Feb 2019 23:41:30 GMT):
Thanks. That sounds like something @TechWritingWhiz , @kdenhartog and I can help with.

esplinr (Fri, 08 Feb 2019 23:42:36 GMT):
Especially with regards to accuracy and that the functionality already exists to fulfill the use cases. I'm more nervous about "completeness", as we have literally hundreds of use cases we have put together at Evernym. We probably want to focus on the 10 most interesting ones like you have in the doc.

SteveGoob (Fri, 08 Feb 2019 23:43:40 GMT):
By completeness, I'm more referring to the distribution and generality of the use cases themselves.

SteveGoob (Fri, 08 Feb 2019 23:45:28 GMT):
I don't want 6 use cases about passwords and websites, and only 1 about a digital drivers license, for example

SteveGoob (Fri, 08 Feb 2019 23:46:20 GMT):
I'd like the use cases to be fewer, more general, and adequately distributed across industries and applications.

SteveGoob (Fri, 08 Feb 2019 23:48:43 GMT):
Either way, we just need an MVP that the community can continue to edit and contribute to after it's in the wiki

haniavis (Tue, 12 Feb 2019 22:08:30 GMT):
Has joined the channel.

TechWritingWhiz (Wed, 13 Feb 2019 16:44:30 GMT):
Just a heads up everyone: My employment with Evernym has recently ended. I've updated my profile information and I'll log back in here periodically to see if I'm able to be of assistance. The next two to three weeks will be spent doing other things as I search for another position as a Technical Writer, but I'm always happy to help here when possible.

esplinr (Thu, 14 Feb 2019 01:05:08 GMT):
Thank you for all you have done @TechWritingWhiz !

haggs (Tue, 19 Feb 2019 22:55:09 GMT):
[ ](https://chat.hyperledger.org/channel/indy-outreach?msg=3yF73Wvxjfm7gZkJg) I'm noticing this as well, a simple search for google led me to a broken link in Indy-SDK, is there any way to reset google robots on GitHub repos?

mboyd (Wed, 20 Feb 2019 18:20:19 GMT):
@haggs thanks for the notification. I'm looking into this.

mboyd (Wed, 20 Feb 2019 18:20:31 GMT):
Do you remember what your google search was?

haggs (Wed, 20 Feb 2019 18:25:08 GMT):
@mboyd https://www.google.com/search?q=agent+authorization+policy+hyperledger&oq=agent+autho&aqs=chrome.0.69i59j69i57j69i60j0l3.1970j0j7&sourceid=chrome&ie=UTF-8

haggs (Wed, 20 Feb 2019 18:25:27 GMT):
"agent authorization policy hyperledger"

haggs (Wed, 20 Feb 2019 18:25:37 GMT):
Let me know if I can help

mwherman2000 (Wed, 20 Feb 2019 19:48:23 GMT):
[ ](https://chat.hyperledger.org/channel/indy-outreach?msg=ZhSDfqy9t2ALt2xKE) @mboyd I think it was something like the following: https://www.google.com/search?rlz=1C1CHBF_enUS763US763&ei=ia5tXN25GtH_-gTUk7PACQ&q=indy+nym+transaction&oq=indy+nym+transaction&gs_l=psy-ab.3..33i160.9966.16659..17128...0.0..0.235.3516.0j15j5......0....1..gws-wiz.......0i71j35i39j0i131j0j0i67j0i22i30j33i21.OA66_BU8XKI The correct link is not showing up as 3rd in the search results.

haggs (Thu, 21 Feb 2019 18:12:25 GMT):
https://github.com/kdenhartog/indy-dev for reference

haggs (Thu, 21 Feb 2019 18:13:28 GMT):
@mwherman2000 Addressing your issue from this morning now, where did you notice the large messages? Since we do a full tear down and bring up in the repo - mind giving spec as to where

mwherman2000 (Thu, 21 Feb 2019 18:29:38 GMT):
Let me do a proper summary ...one area was Credential Definitions

mwherman2000 (Thu, 21 Feb 2019 18:33:59 GMT):
Here's a link to the (very) raw logs: https://github.com/mwherman2000/indy-dev/blob/master/python/doc/getting_started-verbose.log

mwherman2000 (Thu, 21 Feb 2019 18:34:11 GMT):
This is a fork of Kyle

mwherman2000 (Thu, 21 Feb 2019 18:34:11 GMT):
This is a fork of Kyle's repo that I've adding a lot of new instrumentation, documentation, and visualizations to.

mwherman2000 (Thu, 21 Feb 2019 18:36:17 GMT):
For example...

mwherman2000 (Thu, 21 Feb 2019 18:37:40 GMT):

Clipboard - February 21, 2019 11:37 AM

mwherman2000 (Fri, 22 Feb 2019 16:16:49 GMT):
Has anyone created (or considered creating) an Indy Developer FAQ page?

esplinr (Fri, 22 Feb 2019 20:11:59 GMT):
That sounds really useful.

esplinr (Fri, 22 Feb 2019 20:12:09 GMT):
I'm not aware of an existing one.

nanspro (Sat, 23 Feb 2019 02:11:40 GMT):
Has left the channel.

mwherman2000 (Thu, 28 Feb 2019 15:57:13 GMT):
Context: I've been working on visualizing @kdenhartog 's version of the Getting Started python script including adding numbering to the script that makes it easy to directly correlate each task in the script source code with each diagram and with the console output generated by the script (e.g. https://github.com/mwherman2000/indy-dev/blob/master/python/doc/getting_started-5.0%20Raw%20Message%20Flows.md). I now want to fold the diagrams into the text of the "best version" of the longer descriptive narration of the "Alice buys a car" scenario. Question: What is the "best version of the longer descriptive narration of the "Alice buys a car" scenario" for me to use? ...for example, is it this one? https://github.com/hyperledger/indy-sdk/blob/master/docs/getting-started/indy-walkthrough.md CC: @mboyd

callahan (Thu, 28 Feb 2019 16:29:04 GMT):
Has joined the channel.

lorenz.loesch (Mon, 04 Mar 2019 15:37:11 GMT):
Has joined the channel.

mwherman2000 (Tue, 05 Mar 2019 17:37:01 GMT):
FYI: I've found a specific, and I believe useful, focus and scope for the Indy Getting Started project I've been working on (let's just say for quite some time now :-)). I'm looking forward to finishing the first complete draft this week. Checkout https://github.com/mwherman2000/indy-dev/blob/master/python/doc/getting_started-enterpise.md#hyperledger-indy-getting-started-guide-for-enterprise-architects-and-developers-gsg-ea Abstract The _HyperLedger Indy Getting Started Guide for Enterprise Architects and Developers (GSG-EA)_ documents an end-to-end framework for taking a business problem represented by the _Alice Buys a Car_ user story and how to work through the analysis, design, and implementation of an executable self-sovereign identity (SSI) solution that addresses the requirements of this (or any similar purchasing) user story. This guide also introduces the use of several enterprise architecture concepts into the new world of SSI application analysis, design, and implementation. To achieve this goal, the guide using the ArchiMate visual modeling language and the Archi open source, enterprise modeling tool for analysis and design. The implementation is a simple Python script. Architects and developers who are new to the HyperLedger Indy SSI software platform and the Sovrin SSI governance framework will gain significant new knowledge and understanding about the design and implementation of SSI solutions using the approach documented in this guide. CC: @danielhardman @kdenhartog @nage

mwherman2000 (Tue, 05 Mar 2019 17:37:01 GMT):
FYI: I've found a specific, and I believe useful, focus and scope for the Indy Getting Started project I've been working on (let's just say for quite some time now :-)). I'm looking forward to finishing the first complete draft this week. Checkout https://github.com/mwherman2000/indy-dev/blob/master/python/doc/getting_started-enterpise.md#hyperledger-indy-getting-started-guide-for-enterprise-architects-and-developers-gsg-ea Abstract The _HyperLedger Indy Getting Started Guide for Enterprise Architects and Developers (GSG-EA)_ documents an end-to-end framework for taking a business problem represented by the _Alice Buys a Car_ user story and how to work through the analysis, design, and implementation of an executable self-sovereign identity (SSI) solution that addresses the requirements of this (or any similar purchasing) user story. This guide also introduces the use of several enterprise architecture concepts into the new world of SSI application analysis, design, and implementation. To achieve this goal, the guide uses the ArchiMate visual modeling language and the Archi open source, enterprise modeling tool for analysis and design. The implementation is a simple Python script. Architects and developers who are new to the HyperLedger Indy SSI software platform and the Sovrin SSI governance framework will gain significant new knowledge and understanding about the design and implementation of SSI solutions using the approach documented in this guide. CC: @danielhardman @kdenhartog @nage @swcurran @John_Jordan @pknowles

mwherman2000 (Tue, 05 Mar 2019 17:37:01 GMT):
FYI: I've found a specific, and I believe useful, focus and scope for the Indy Getting Started project I've been working on (let's just say for quite some time now :-)). I'm looking forward to finishing the first complete draft this week. Checkout https://github.com/mwherman2000/indy-dev/blob/master/python/doc/getting_started-enterpise.md#hyperledger-indy-getting-started-guide-for-enterprise-architects-and-developers-gsg-ea Abstract The _HyperLedger Indy Getting Started Guide for Enterprise Architects and Developers (GSG-EA)_ documents an end-to-end framework for taking a business problem represented by the _Alice Buys a Car_ user story and how to work through the analysis, design, and implementation of an executable self-sovereign identity (SSI) solution that addresses the requirements of this (or any similar purchasing) user story. This guide also introduces the use of several enterprise architecture concepts into the new world of SSI application analysis, design, and implementation. To achieve this goal, the guide uses the ArchiMate visual modeling language standard and the Archi open source, enterprise modeling tool for analysis and design. The implementation is a simple Python script. Architects and developers who are new to the HyperLedger Indy SSI software platform and the Sovrin SSI governance framework will gain significant new knowledge and understanding about the design and implementation of SSI solutions using the approach documented in this guide. CC: @danielhardman @kdenhartog @nage @swcurran @John_Jordan @pknowles

mwherman2000 (Tue, 05 Mar 2019 17:37:01 GMT):
FYI: I've found a specific, and I believe useful, focus and scope for the Indy Getting Started project I've been working on (let's just say for quite some time now :-)). I'm looking forward to finishing the first complete draft this week. Checkout https://github.com/mwherman2000/indy-dev/blob/master/python/doc/getting_started-enterpise.md#hyperledger-indy-getting-started-guide-for-enterprise-architects-and-developers-gsg-ea Abstract The _HyperLedger Indy Getting Started Guide for Enterprise Architects and Developers (GSG-EA)_ documents an end-to-end framework for analysing a business problem such as the by the _Alice Buys a Car_ user story; then undertaking the design and implementation of an executable self-sovereign identity (SSI) solution that meets the requirements of this (or any similar purchasing) user story. This guide also introduces the use of several enterprise architecture concepts into the new world of SSI application analysis, design, and implementation. To achieve this goal, the guide uses the ArchiMate visual modeling language standard and the Archi open source, enterprise modeling tool for analysis and design. The implementation is a simple Python script. Architects and developers who are new to the HyperLedger Indy SSI software platform and the Sovrin SSI governance framework will gain significant new knowledge and understanding about the design and implementation of SSI solutions using the approach documented in this guide. CC: @danielhardman @kdenhartog @nage @swcurran @John_Jordan @pknowles

mwherman2000 (Tue, 05 Mar 2019 17:37:01 GMT):
FYI: I've found a specific, and I believe useful, focus and scope for the Indy Getting Started project I've been working on (let's just say for quite some time now :-)). I'm looking forward to finishing the first complete draft this week. Checkout https://github.com/mwherman2000/indy-dev/blob/master/python/doc/getting_started-enterpise.md#hyperledger-indy-getting-started-guide-for-enterprise-architects-and-developers-gsg-ea Abstract The _HyperLedger Indy Getting Started Guide for Enterprise Architects and Developers (GSG-EA)_ documents an end-to-end framework for analysing a business problem such as the _Alice Buys a Car_ user story; then undertaking the design and implementation of an executable self-sovereign identity (SSI) solution that meets the requirements of this (or any similar purchasing) user story. This guide also introduces the use of several enterprise architecture concepts into the new world of SSI application analysis, design, and implementation. To achieve this goal, the guide uses the ArchiMate visual modeling language standard and the Archi open source, enterprise modeling tool for analysis and design. The implementation is a simple Python script. Architects and developers who are new to the HyperLedger Indy SSI software platform and the Sovrin SSI governance framework will gain significant new knowledge and understanding about the design and implementation of SSI solutions using the approach documented in this guide. CC: @danielhardman @kdenhartog @nage @swcurran @John_Jordan @pknowles

danielhardman (Tue, 05 Mar 2019 19:03:21 GMT):
Great work, @mwherman2000! This will be a nice resource.

fhmarino (Fri, 08 Mar 2019 02:01:18 GMT):
Has joined the channel.

mwherman2000 (Fri, 08 Mar 2019 16:55:52 GMT):
Cross-posted to https://chat.sovrin.org/channel/general ...

mwherman2000 (Fri, 08 Mar 2019 16:56:07 GMT):
While modeling the Indy/Sovrin roles for the "Alice Buys a Car" scenario (https://github.com/mwherman2000/indy-dev/blob/master/python/doc/getting_started-enterpise.md#additional-actors), I found the Sovrin Glossary to be very useful from a data and knowledge perspective but it wasn't of much help when it came to understanding the relationships between and across roles. Yesterday, this gave birth to what will become the Sovrin Governance Comprehensive Architecture Reference Model (SOVRIN ARM): https://github.com/mwherman2000/sovrin-arm/blob/master/README.md So far, it's just focused on actors and their Sovrin roles (that start with the letters A through H :-)) Feedback appreciated. What would you like to see added next?

mwherman2000 (Fri, 08 Mar 2019 23:36:35 GMT):
Finished ...almost 90 elements

mwherman2000 (Thu, 14 Mar 2019 19:45:48 GMT):
ANNOUNCEMENT: *SOVRIN ARM Interactive Explorer*. Checkout https://mwherman2000.github.io/sovrin-arm/ @drummond @windley @telegramsam @pknowles @nage @danielhardman Click on _Views_ in the left pane, pick a viewpoint and #gowild 🙂 Try and to do something like that with your *PUML* text! 🙂 ...build models - not one-off drawings. This effort was inspired by @telegramsam 's suggestion that I needed to find a way to improve the digestibility of these models. Thank you Sam.

mwherman2000 (Thu, 14 Mar 2019 19:45:48 GMT):
ANNOUNCEMENT: *SOVRIN ARM Interactive Explorer*. Checkout https://mwherman2000.github.io/sovrin-arm/ @drummond @windley @telegramsam @pknowles @nage @danielhardman Click on _Views_ in the left pane, pick a viewpoint and #gowild 🙂 Try and to do something like that with your *PUML* text! 🙂 ...build models - not one-off drawings. This effort was inspired by @TelegramSam 's suggestion that I needed to find a way to improve the digestibility of these models. Thank you Sam.

mwherman2000 (Thu, 14 Mar 2019 19:45:48 GMT):
ANNOUNCEMENT: *SOVRIN ARM Interactive Explorer*. Checkout https://mwherman2000.github.io/sovrin-arm/ @drummondreed @windley @TelegramSam @pknowles @nage @danielhardman Click on _Views_ in the left pane, pick a viewpoint and #gowild 🙂 Try and to do something like that with your *PUML* text! 🙂 ...build models - not one-off drawings. This effort was inspired by @TelegramSam 's suggestion that I needed to find a way to improve the digestibility of these models. Thank you Sam.

mwherman2000 (Thu, 14 Mar 2019 19:45:48 GMT):
ANNOUNCEMENT: *SOVRIN ARM Interactive Explorer*. Checkout https://mwherman2000.github.io/sovrin-arm/ @drummondreed @windley @TelegramSam @pknowles @nage @danielhardman Click on _Views_ in the left pane, pick a viewpoint and #gowild 🙂 ...click on any of the colored elements in any of the views. Try and to do something like that with your *PUML* text! 🙂 ...build models - not one-off drawings. This effort was inspired by @TelegramSam 's suggestion that I needed to find a way to improve the digestibility of these models. Thank you Sam.

mwherman2000 (Thu, 14 Mar 2019 19:45:48 GMT):
ANNOUNCEMENT: *SOVRIN ARM Interactive Explorer*. Checkout https://mwherman2000.github.io/sovrin-arm/ @drummondreed @windley @TelegramSam @pknowles @nage @danielhardman @darrell.odonnell Click on _Views_ in the left pane, pick a viewpoint and #gowild 🙂 ...click on any of the colored elements in any of the views. Try and to do something like that with your *PUML* text! 🙂 ...build models - not one-off drawings. This effort was inspired by @TelegramSam 's suggestion that I needed to find a way to improve the digestibility of these models. Thank you Sam.

pknowles (Thu, 14 Mar 2019 19:45:48 GMT):
Has joined the channel.

windley (Thu, 14 Mar 2019 19:45:48 GMT):
Has joined the channel.

mwherman2000 (Thu, 14 Mar 2019 19:47:15 GMT):
The INDY ARM Interactive Explorer is going to take some extra time because I've been using that ArchiMate model file as a scratch pad and it has a lot off extra junk that needs to be removed first.

danielhardman (Thu, 14 Mar 2019 20:25:46 GMT):
That is a thing of beauty, @mwherman2000 !

mwherman2000 (Thu, 14 Mar 2019 20:26:42 GMT):
Thank you Daniel ...can my thing also have a DID? :-) :-)

mwherman2000 (Mon, 18 Mar 2019 19:45:04 GMT):
ANNOUNCEMENT: The INDY ARM Interactive Explorer is available as of right now: https://github.com/mwherman2000/indy-arm/blob/master/README.md#indy-arm-interactive-explorer ...with about a dozen different viewpoints to start with. Click on any of the views on the left side of the web app to get going.

mwherman2000 (Mon, 18 Mar 2019 19:45:41 GMT):

indy-arm-explorer.png

pknowles (Mon, 18 Mar 2019 20:54:09 GMT):
[ ](https://chat.hyperledger.org/channel/indy-outreach?msg=bc6HKWuRa8diSu6jr) @mwherman2000 Really cool!!!

brycebudd (Wed, 20 Mar 2019 17:01:37 GMT):
Has joined the channel.

gskerry (Tue, 09 Apr 2019 19:43:27 GMT):
Hi all :wave:

gskerry (Tue, 09 Apr 2019 19:44:35 GMT):
(hopefully this is right place to ask)... am at a conference and have had a few discussions with folks working on projects around identity and looking for development providers with experience on Indy

gskerry (Tue, 09 Apr 2019 19:44:52 GMT):
Is there any such list hosted anywhere today?

gskerry (Tue, 09 Apr 2019 19:54:27 GMT):
(Or anyone who be interested to get put in touch directly?)

VicCooper (Wed, 10 Apr 2019 00:48:12 GMT):
Has joined the channel.

esplinr (Wed, 10 Apr 2019 23:06:22 GMT):
I'm not aware of such a list. There are various businesses and independent consultants who specialize in Indy, but no directory of providers.

esplinr (Wed, 10 Apr 2019 23:07:53 GMT):
@gskerry You can ask in #indy for consultants interested in the work. My employer (Evernym) can also help out with many of these projects.

jadhavajay (Thu, 11 Apr 2019 18:20:17 GMT):
Has joined the channel.

esplinr (Mon, 15 Apr 2019 22:25:33 GMT):
I created a new documentation index page, since we didn't have one in the new wiki. It has an easy place to add community resources. https://wiki.hyperledger.org/display/indy/Documentation+Index

esplinr (Mon, 15 Apr 2019 22:28:10 GMT):
It is better than what we had, but it needs a lot more work.

esplinr (Mon, 15 Apr 2019 22:28:10 GMT):
I incorporated much of the information on the old page. It is now better than what we had, but it needs a lot more work.

stone-ch (Fri, 26 Apr 2019 00:50:18 GMT):
Has joined the channel.

helengarneau (Thu, 09 May 2019 18:22:43 GMT):
Has joined the channel.

circlespainter (Sat, 18 May 2019 07:36:26 GMT):
Has joined the channel.

ilya1w (Wed, 22 May 2019 03:53:24 GMT):
Has joined the channel.

PaulA (Thu, 18 Jul 2019 06:19:27 GMT):
Has joined the channel.

Rick (Thu, 24 Oct 2019 13:47:11 GMT):
Has joined the channel.

tkuhrt (Mon, 11 Nov 2019 20:38:36 GMT):
Does anyone have any good training material for helping folks develop applications that use Hyperledger Indy?

swcurran (Mon, 11 Nov 2019 23:47:31 GMT):
Hey @tkuhrt - we've developed an Indy/Aries/Ursa edX course for the Linux Foundation that should launch on Nov. 21. It's not a devs course, but provides an overview to the technology. We're working on a follow up course to be launched in early 2020 that does target devs. For devs, you could use this as a starting place - https://github.com/hyperledger/aries-cloudagent-python/tree/master/docs/GettingStartedAriesDev. Not complete yet, but it should provide sufficient context.

tkuhrt (Mon, 11 Nov 2019 23:48:37 GMT):
Thanks, @swcurran

esplinr (Tue, 12 Nov 2019 00:12:42 GMT):
The Sovrin Foundation prepared a great training here: https://docs.google.com/document/d/1UZz2IMTP94W-nXx2qkEiMRGaFz8JKfmAGBipMaWieKI/edit

Silona (Fri, 15 Nov 2019 04:01:17 GMT):

foravneet (Mon, 18 Nov 2019 22:55:41 GMT):
Has joined the channel.

athira (Mon, 25 Nov 2019 19:03:18 GMT):
Has joined the channel.

lsl88 (Wed, 27 Nov 2019 15:37:01 GMT):
Has joined the channel.

iampukar (Thu, 28 Nov 2019 10:00:19 GMT):
Has joined the channel.

lijiachuan (Mon, 02 Dec 2019 14:55:51 GMT):
@swcurran , thanks for the great course about Indy/Aries/Ursa on edX. Here I need your some helps for an problem I am encountering. I already setup one VON network in one VM server, then I plan to use Aries Cloud Agent to setup one agent, based on this document https://github.com/hyperledger/aries-cloudagent-python/blob/master/DevReadMe.md#docker, after I run "scripts/run_docker --version", there are two docker images created aries-cloudagent-run and bcgovimages/von-image, and I think to have one new agent, I should use the provision command to provision a new agent, then use the start command to start a new agent, is my understanding correct? I tried to use "scripts/run_docker provision" to create one agent for node 1, with different parameters such as --genesis-url with my genesis file's URL, --seed with my node1's seed value, but it didn't go through. May I have a sample provision command script as a reference? This document has one sample start command script, that is very useful. Hope can have your guidance here. Thanks.

swcurran (Mon, 02 Dec 2019 17:01:36 GMT):
I've pinged the devs to help. We have examples in a couple of repos of starting ACA-Py that might help - https://github.com/bcgov/identity-kit-poc (a verifier), https://github.com/bcgov/indy-email-verification. The aca-py start command to start the Identity-Kit-Poc is here: https://github.com/bcgov/identity-kit-poc/blob/118ac5a398447fc7ff75f74eb4101e60440eb641/docker/docker-compose.yml#L196

SigmaS 1 (Wed, 04 Dec 2019 07:03:32 GMT):
Has joined the channel.

Silona (Tue, 14 Jan 2020 16:50:16 GMT):
Help Us Help you! Attend the Developer Relationship Meeting with Myself and our Marketing Dept. tomorrow at 9:00am Pacific Time. For the agenda and Dial in info https://wiki.hyperledger.org/display/Marketing/2020-01-15+Meeting+notes

Silona (Tue, 14 Jan 2020 17:05:09 GMT):
Calling all Projects, SIG, and WG!!! We will have a Video recording Studio setup at HGF (Hyperledger Global Forum). We are asking that all projects and groups help us create a 5 minute video about your group so that we can promote it afterward. Sign up Here! https://wiki.hyperledger.org/display/HGF/Video+Recording+Schedule

rileyphughes (Thu, 16 Jan 2020 22:21:14 GMT):
Has joined the channel.

EdEykholt (Mon, 20 Jan 2020 03:30:08 GMT):
Has joined the channel.

pknowles (Thu, 23 Jan 2020 17:47:08 GMT):
A colleague has just brought "BlokSec" to my attention. Does anyone know if they are part of the "Decentralized Identity" community (i.e. Hyperledger Aries/Indy, DIF, etc.)? https://www.bloksec.com

esplinr (Fri, 24 Jan 2020 01:18:35 GMT):
I haven't heard of them.

NikhilPrakash (Wed, 12 Feb 2020 00:51:17 GMT):
Has joined the channel.

PatrikStas (Sat, 21 Mar 2020 15:21:43 GMT):
Has joined the channel.

mohammadhossein73 (Tue, 31 Mar 2020 20:02:03 GMT):
Has joined the channel.

hcsatish (Tue, 07 Jul 2020 16:41:20 GMT):
Has joined the channel.

JakeZ2020 (Wed, 12 Aug 2020 15:57:08 GMT):
Has joined the channel.

Xand (Tue, 01 Sep 2020 16:25:45 GMT):
Has joined the channel.

troyronda (Wed, 28 Oct 2020 17:42:34 GMT):
Has left the channel.

windley (Sun, 17 Jan 2021 22:33:54 GMT):
Has left the channel.

darrell.odonnell (Wed, 22 Sep 2021 15:45:49 GMT):
Question - what are the top 3 HL-Indy improvements that we would all like to see. As ideas I have heard from many leaders the following - in no particular order: * did:indy support * DID Document support native to the ledger (as opposed to using Universal Resolver) * KERI support - anchoring KERI data into the Indy ledger * embedded support for JSON or JSON-LD BBS+ credentials (I note ongoing debate over JSON/JSON-LD and the lack of predicate support in BBS+) * other ideas that I have managed to lose!

swcurran (Wed, 22 Sep 2021 19:28:48 GMT):
Some notes: - "did:indy" as defined would provide support for using JSON-LD/BBS+ VCs. "did:indy" includes support for arbitrary DIDDocs on an Indy ledger, and once you have that, you can support the keys needed for BBS+. Note that for JSON-LD signature VCs (the "sign the whole credential" approach) -- Indy has the necessary support already. - With the "did:indy" support, stretching it to support a KERI mechanism is a relatively small step. - With "did:indy" implemented, stretching it to add native DIDDoc support (e.g. a transaction that returns the DIDDoc directly) is a pretty small step. - For those not aware -- "did:indy" provides (a) a way to reference the ledger of the identifier in the did, and (b) full DIDDoc support.

rjones (Sat, 12 Feb 2022 22:00:19 GMT):
Has joined the channel.

rjones (Sat, 12 Feb 2022 22:00:20 GMT):
[Please move to Discord](https://discord.com/channels/905194001349627914/905205711850594336)

rjones (Sat, 12 Feb 2022 22:00:20 GMT):
[Please get an account on the Hyperledger discord](https://discord.gg), then [join Indy](https://discord.com/channels/905194001349627914/905205711850594336)

rjones (Sun, 13 Feb 2022 01:34:48 GMT):
Has left the channel.

rjones (Wed, 23 Mar 2022 17:25:47 GMT):