bmos299 (Fri, 03 Feb 2017 16:45:31 GMT):
Welcome to the fabric-documentation channel.

charlesbrandontheis (Fri, 03 Feb 2017 20:22:37 GMT):
Has joined the channel.

bfuentes@fr.ibm.com (Sat, 04 Feb 2017 09:20:02 GMT):
Has joined the channel.

joshhus (Mon, 06 Feb 2017 17:30:55 GMT):
@cbf Can this get voted in ... https://gerrit.hyperledger.org/r/#/c/5007/

bmos299 (Tue, 07 Feb 2017 17:12:53 GMT):
cleaning up the docs seems to need three pieces.. 1. an agreed upon toc (like mkdocs.yml) 2. the technologies (rtd with sphinx, etc) with help from a designer that is expert in this area. 3. tech writers assigned items from the mkdocs and a technical partner ....is just my take

cbf (Tue, 07 Feb 2017 17:49:59 GMT):
so, IMNSHO, DEVELOPERS are responsible for documenting the code, especially how to use it etc

cbf (Tue, 07 Feb 2017 17:50:23 GMT):
does not need to be pretty or grammatically perfect, but they need to be committing doc changes as the code evolves

cbf (Tue, 07 Feb 2017 17:51:07 GMT):
what the tech writers should be looking to do is cleaning up the mess;-) and making the docs more UX friendly

joshhus (Tue, 07 Feb 2017 18:06:57 GMT):
#2 was vetted last year, and approved with distinction. It matches Sawtooth Lake, and we are limited to the "themes" that are provided by ReadTheDocs. ... I don't think #2 is a problem or a priority. ... It already uses a Sphinx theme.

joshhus (Tue, 07 Feb 2017 18:07:41 GMT):
That said, yeah the heading emphasis has some limitations - an ideal world would have a UX person on this consistently.

joshhus (Tue, 07 Feb 2017 18:12:21 GMT):
RTD is "free" with GitHub account; so we don't get customization of look and feel, or a 'vanity' URL, for example. This was decided/agreed upon last year.

joshhus (Tue, 07 Feb 2017 18:13:33 GMT):
#1 - The TOC that we had for v0.6 didn't get complaints, so I think if we can make the content organized more clearly by ROLES, that will help the perception/reception.

joshhus (Tue, 07 Feb 2017 18:17:08 GMT):
here's sawtooth lake, which uses our theme. ... notice the simple/short/collapsed TOC - subtopics don't expand UNTIL you click on one. ... @rameshthoomu and I could look at this possibility for us.

joshhus (Tue, 07 Feb 2017 18:17:28 GMT):
Sawtooth Lake doc: http://intelledger.github.io/

joshhus (Tue, 07 Feb 2017 18:19:29 GMT):
#3, sounds good, but that's not the open source method, where "community" takes ownership of work items. The current process is Nick and I (and any others) create CRs for new doc and doc changes, and assign those to Reviewers. Reviewers include Maintainers, who vote on the content being in or out. To my knowledge there is no mechanism to assign a specific developer to a doc CR, using Gerrit.

joshhus (Tue, 07 Feb 2017 18:20:28 GMT):
i.e. the current review process is more a request for the named folks to Review, Comment, and also vote if a Maintainer.

cbf (Tue, 07 Feb 2017 18:22:12 GMT):
We need to have a splash page which could lead to the RTD site

joshhus (Tue, 07 Feb 2017 18:22:13 GMT):
What @cbf says above, his .02, is how it actually works, when we have only a few writers for many developers and designers.

cbf (Tue, 07 Feb 2017 18:22:39 GMT):
we need some design help, and some html/css mad skillz

joshhus (Tue, 07 Feb 2017 18:23:18 GMT):
Splash page nice, the Corda one is nice: https://www.corda.net/ ... notice that this is a splash page for all of corda however, not just corda docs. ... "Documentation" link at top.

joshhus (Tue, 07 Feb 2017 18:24:04 GMT):
I have HTML/css, but not javascript. And then I'm not doing content. This yells out for an FT UX resource (experienced).

joshhus (Tue, 07 Feb 2017 18:33:18 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=MTQtBJnBkzRvQnvRL) @cbf ... right this is how it traditionally works, with a few writers per a lot of developers and testers. Back in the old days each functional dev. team would have one or more writers, and the writers would then be more expert on that area of doc/tech.

joshhus (Tue, 07 Feb 2017 18:33:18 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=MTQtBJnBkzRvQnvRL) @cbf ... right this is how it traditionally works, with a few writers per a lot of developers and testers. Back in the old days each functional dev. team would have one or more writers per few devs/testers, and the writers could then become more expert on a focused area of doc/tech.

bmos299 (Tue, 07 Feb 2017 18:35:13 GMT):
I took Chris' patch, https://gerrit.hyperledger.org/r/#/c/5615/ and built a new RTD and made a 'Home' tab. Ramesh will make this a toggle as we move to Sphinx. http://fabric-rtd.readthedocs.io/en/latest/

joshhus (Tue, 07 Feb 2017 18:35:57 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=vAYFmyZNN3bkDGWEK) @joshhus ... Agree Chris, ideally.

bmos299 (Tue, 07 Feb 2017 18:36:38 GMT):
@cbf on the splash page....absolutely.

joshhus (Tue, 07 Feb 2017 18:38:12 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=JyESaK25Yxv63NpoA) @bmos299 ... This is sphinx. @rameshthoomu can anything be done to make the "Introduction" and "Chaincode Developer" etc. Headings more prominent ... even a red color and/or larger / underlined? ... I don't know if the themes in RTD are fixed or if can be tweaked - do you know?

bmos299 (Tue, 07 Feb 2017 18:38:24 GMT):
@nickgaski and I were chatting. If someone creates a new document, meaning they have to update the mkdocs.yml for RTD, then we require they run private RTD which we will provide instructions how to setup. If they are just changing an existing doc, the needs isn't really there as they won't break anything.

bmos299 (Tue, 07 Feb 2017 18:38:47 GMT):
@joshhus we are not using the sphinx theme right now. @rameshthoomu is working on that.

bmos299 (Tue, 07 Feb 2017 18:39:51 GMT):
the issue, from the past, was the .md needs to be converted to .rst for Sphinx. Hopefully, this goes smoothly. I think the splash page is where the the high level, business type info goes.

joshhus (Tue, 07 Feb 2017 18:41:52 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=FiAurZTocH5n4JrLs) @bmos299 Right, and we don't need to to get the same RTD build. Perhaps you guys are talking about doing something else/more/different.

joshhus (Tue, 07 Feb 2017 18:41:52 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=FiAurZTocH5n4JrLs) @bmos299 Right, and we don't need to use Sphinx proper to get the same RTD build. Perhaps you guys are talking about doing something else/more/different by adding Sphinx.

bmos299 (Tue, 07 Feb 2017 18:42:20 GMT):
please ping Ramesh and we can chat about what we are doing. I'll be offline for an hour.

simsc (Tue, 07 Feb 2017 18:45:30 GMT):
I created a documentation board. It filters on fabric-docs created by Chris

cbf (Tue, 07 Feb 2017 18:46:34 GMT):
@joshhus I wish that were the case, because if it were, we wouldn't be so delinquent in our documentation

cbf (Tue, 07 Feb 2017 18:46:53 GMT):
we don't operate in the way I described by a long shot

cbf (Tue, 07 Feb 2017 18:47:22 GMT):
this is something I am trying to affect with @simsc and @weeds

cbf (Tue, 07 Feb 2017 19:22:59 GMT):
@bmos299 might I ask that you pick up my latest changeset and rebuild the staging site?

joshhus (Tue, 07 Feb 2017 22:08:56 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=PXQcLpGPirNJCKbzp) @bmos299 "private RTD" is what, this? -- https://github.com/rameshthoomu/fabric1/blob/tools/readthedocs.md ... This won't solve the case where there are two pending adds (pending votes in Gerrit) that both would affect mkdocs.yml, but we don't know which one or both might be voted in or not. - right?

joshhus (Tue, 07 Feb 2017 22:12:13 GMT):
Gerrit tricky errors today; new gossip topic text is here for now: https://jira.hyperledger.org/browse/FAB-2018

bmos299 (Tue, 07 Feb 2017 22:13:05 GMT):
@cbf I updated with your changes... http://fabric-rtd.readthedocs.io/en/latest/whyfabric/

bmos299 (Tue, 07 Feb 2017 22:13:22 GMT):
Please double check if you can make sure it looks ok.

bmos299 (Tue, 07 Feb 2017 22:17:27 GMT):
@joshhus i don't see the need for private builds being all that common. If someone changes mkdocs.yml, we give instructions for them to make sure the docs still build. This seems pretty straight forward? For this particular instance, we are doing a pretty major structural overhaul, that is why I am using my repo as a sandbox.

bmos299 (Tue, 07 Feb 2017 22:33:10 GMT):
@joshhus we will add automated building the rtd to the backlog to ensure the build is successful and the display renders properly.

cbf (Tue, 07 Feb 2017 22:45:46 GMT):
I think the next CR should be the TOC sidebar changes

joshhus (Tue, 07 Feb 2017 23:49:38 GMT):
Seems Chris wants to continue with the current process - no private builds. I'm fine with that, I think private builds will confuse things even more for reviews and votes. My opinion. Let's get the content updated ASAP for v1.0 that's the top priority. Then we can look at alternative build things later. The primary issue here for short term is not build. It is content development, review, and voting in.

joshhus (Tue, 07 Feb 2017 23:51:49 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=rhEaWHBHnnhD8qnqR) @bmos299 Okay can you point me to the instructions; I've hit problems with multiple mkdocs.yml updates being tied to various pending CRs.

bmos299 (Wed, 08 Feb 2017 00:24:04 GMT):
I created a story for the splash page and assigned to Mark. -- https://jira.hyperledger.org/browse/FAB-2115

bmos299 (Wed, 08 Feb 2017 00:24:04 GMT):
@joshhus @nickgaski @rameshthoomu @simsc @markparz @cbf For the short term, in your gerrit patch set for toc, push to my repo. I have made nick, mark, josh all collaborators so if you push your doc changes to master the rtd will be dynamically updated. We just need to ensure no conflicts. Nick owns mkdocs.yml, so please talk to him before changing that one. The push command is: git push -f https://github.com/bmos299/fabric master

bmos299 (Wed, 08 Feb 2017 02:28:19 GMT):
@markparz @simsc @rameshthoomu I have created Epic https://jira.hyperledger.org/browse/FAB-2117 ...each has a story assigned to one of you (splash page, doc writing, rendering sphinx). Please check it out and let me know if it makes sense.

markparz (Wed, 08 Feb 2017 13:16:22 GMT):
thanks @bmos299 I don't know that I'm sold on using sphinx, what's the benefit vs our current process

bmos299 (Wed, 08 Feb 2017 14:02:39 GMT):
Hi Mark, We can show you and get your take. It renders it a little better.

simsc (Wed, 08 Feb 2017 14:16:18 GMT):
part - when i look at corda and kafka documentation the ux experience is much better. sphinx seems to be one option that can help provide a better experience. i am not a expert on this space is there something different that sphinx that should be consider?

simsc (Wed, 08 Feb 2017 14:17:01 GMT):
i meant to say parz got autocorrected to part :)

arvindupadhyaya (Wed, 08 Feb 2017 15:04:32 GMT):
Here, http://fabric-rtd.readthedocs.io/en/latest/gettingstarted/#curl-the-application-source-code-and-sdk-modules for npm install to succeed for Mac, Xcode is required.

cbf (Wed, 08 Feb 2017 16:30:23 GMT):
@markparz FWIW, I am also not convinced wew need a new style for the RTD

cbf (Wed, 08 Feb 2017 16:33:11 GMT):
could we get someone working on the github page today, paired with someone from Sean's team (I see he hasn't moved over)

cbf (Wed, 08 Feb 2017 16:34:41 GMT):
I'd do it myself but am traveling this afternoon

cbf (Wed, 08 Feb 2017 16:35:01 GMT):
maybe I could work on plane - will see what kind of room I have

cbf (Wed, 08 Feb 2017 16:36:38 GMT):
@arvindupadhyaya good point, though for just about any development activities you would need that. We could add to pre-requisites

arvindupadhyaya (Wed, 08 Feb 2017 16:37:29 GMT):
yes.. it should be added to the pre-requisites list here http://hyperledger-fabric.readthedocs.io/en/latest/gettingstarted/#prerequisites-and-setup

nickgaski (Wed, 08 Feb 2017 16:38:45 GMT):
hi @arvindupadhyaya - thank you. I realized after I upgraded to Sierra that you need X Code for git and other tooling. I will also add some versioning dependencies for node, npm and docker

nickgaski (Wed, 08 Feb 2017 16:39:07 GMT):
did you catch anything else missing from the instructions?

arvindupadhyaya (Wed, 08 Feb 2017 16:41:59 GMT):
@nickgaski my npm install step was failing since I didn't have Xcode. After installation of Xcode I had to remove the node_modules and re-install by `rm -rf node_modules && npm i`

arvindupadhyaya (Wed, 08 Feb 2017 16:42:27 GMT):
this point can be added as a troubleshooting tip

nickgaski (Wed, 08 Feb 2017 16:43:24 GMT):
I concur. Everything run smoothly after you executed `npm install` with X Code? Also out of curiosity, can you share your versions for node, npm and docker please

arvindupadhyaya (Wed, 08 Feb 2017 16:44:52 GMT):
I was initially on node version 5.0.0.. I was getting a warning with npm install

arvindupadhyaya (Wed, 08 Feb 2017 16:45:32 GMT):
currently my node version `v6.9.5` npm is `3.10.10` and docker is `1.13.0`

arvindupadhyaya (Wed, 08 Feb 2017 16:46:31 GMT):
I used `nvm` to quickly switch between my existing version of node to `v6.9.5`

arvindupadhyaya (Wed, 08 Feb 2017 16:46:54 GMT):
everything is working smoothly now

nickgaski (Wed, 08 Feb 2017 16:51:13 GMT):
great. those are the versions that we are seeing success with on a repeated basis

markparz (Wed, 08 Feb 2017 16:56:37 GMT):
@cbf I pinged Sean earlier.... I think we can work something with his team

balakrishna.devasani (Wed, 08 Feb 2017 17:11:01 GMT):
Has joined the channel.

cbf (Wed, 08 Feb 2017 17:52:10 GMT):
cool, I should have interwebz on the plane to AMS and can help review any mockups etc

markparz (Thu, 09 Feb 2017 02:27:49 GMT):
Hi everyone, Based off the results from the hackathon documentation discussions, just this past week, and a common drumbeat of feedback I am reaching out and requesting your assistance. During the discussions we had talked about the direction of the Fabric documentation, which I would like to propose and get any feedback on the layout/direction and identification of any gaps here. If you would also like to take some pieces, that would be fantastic. Please provide feedback to this email or via rocketchat #fabric-documentation. The plan we devised in SF and over the last few days is as follows: Creation of a HL Fabric website / splash page--> that leads to documentation for both a developer and a business person.... plan to work on some mock ups this week & next (so contact me @markparz on rocketchat #fabric-documentation channel or privately) The proposed layout of documentation index to replace/revamp the current info at : http://hyperledger-fabric.readthedocs.io/en/latest/ (pointers at the top) - Rocket chat - Stack overflow - Linux Email Distribution lists Key Concepts - ~Paragraph at length Overview and why blockchain - High level overview of the architecture, pluggable framework, permissioned Use cases - ??? Possibly link to relevant requirements-WG page Glossary of terms Transaction data model - like Corda's... definition of the transactions, what is the data & why is it important these elements work together Security Model - Plugin model to use their own membership providers & crypto (high level, not fabric CA), immutable pluggable ledger Multi channel - data isolation, concurrency Chaincode (smartcontract) - what it means in an executable environment Consensus - not BFT (process of endorsement, ordering & validation) enable tx to not worry about non-determinism. You can insert human centric interactions into the workflow. Getting started What is included Getting setup Software requirement - pre-reqs Installing Docker Images Running Demos Running Asset transfer within CLI Running Asset Transfer with Node.js SDK Marbles Art Auction Interfaces CLI for developers Node.js SDK ( need to do breakout of this section in more detail) Java SDK ( need to do breakout of this section in more detail) Python SDK -> @Baohua, hoping you can help with this section Starting the network (bootstrap) Recipe book for best practices/templates - Next steps Tutorials Learn docker compose files (marrying configuration/compose files) Learn Chaincode Example 2: describing in detail the snippets of code and the purpose of the code for the sample - Better biz example would be good if possible (Anyone have one? ) - Library books or Art auction app ? Application (marble?) how to use SDK thru app Hyperledger Fabric youtube.com channel &videos Administration and operations Debugging and Logging Architecture (Detail level) Peer Endorsing Committing Policies - (peer/endorser/comitter) - describe what - policies, signing, committing Ordering transactions (consensus) Security (fabric-ca items) What is chaincode and endorsement (point to tutorials) Transaction flow (show things like flow diagrams of the transactions) Troubleshooting and FAQs Appendix Release process How to contribute to Hyperledger-fabric project Development process and code Getting an account Maintainer Process Navigating JIRA Fabric developer setup Buildling fabric Gerrit Testing process and tests Incubation Notice Licenses Release notes Criteria on quality

markparz (Thu, 09 Feb 2017 02:29:19 GMT):
I sent this to hyperledger-fabric email distro, but in case you don't subscribe to it... looking for feedback

passkit (Thu, 09 Feb 2017 04:03:53 GMT):
@markparz - I would also like to see the following topics which are either currently either undocumented, or difficult to find authoritative advice: - Production considerations: deployment options (private network & cloud), security, resilience considerations (particularly fabric-ca and orderers), backup, audit, maintenance/upgrades - Operational considerations: adding / retiring peers, updating chaincode

passkit (Thu, 09 Feb 2017 04:03:53 GMT):
@markparz - I would also like to see the following topics which are either currently undocumented, or difficult to find authoritative advice: - Production considerations: deployment options (private network & cloud), security, resilience considerations (particularly fabric-ca and orderers), backup, audit, maintenance/upgrades - Operational considerations: adding / retiring peers, updating chaincode

bmos299 (Thu, 09 Feb 2017 15:34:37 GMT):
The url that gets updated for every push is: fabric-rtd.readthedocs.io/en/latest/

bmos299 (Thu, 09 Feb 2017 15:35:09 GMT):
@ramesh is working on a solution using Nexus moving forward.

bmos299 (Thu, 09 Feb 2017 15:35:09 GMT):
@nickgaski @joshhus @simsc @markparz @cbf. For the short term, with documentation gerrit patch sets, make sure to include the url: fabric-rtd.readthedocs.io/en/latest. This is a short-term staging environment. I have given Nick, Josh, Mark, Ramesh all collaborator access. You simple need to do a push to master: git push -f https://bmos299/fabric master. The url will automatically be updated, assuming you don't break the build. Nick is the only one who should change mkdocs.yml. I don't anticipate merge conflicts. @ramesh is working on a long-term solution using Nexus moving forward.

bmos299 (Thu, 09 Feb 2017 15:35:09 GMT):
@nickgaski @joshhus @simsc @markparz @cbf. For the short term, with documentation gerrit patch sets, make sure to include the url: fabric-rtd.readthedocs.io/en/latest. This is a short-term staging environment. I have given Nick, Josh, Mark, Ramesh all collaborator access. You simple need to do a push to master: git push -f https://github.com/bmos299/fabric master. The url will automatically be updated, assuming you don't break the build. Nick is the only one who should change mkdocs.yml. I don't anticipate merge conflicts. @ramesh is working on a long-term solution using Nexus moving forward.

bmos299 (Thu, 09 Feb 2017 15:41:04 GMT):
This will help the maintainers/reviewers see the actual document and the rendering.

markparz (Thu, 09 Feb 2017 16:00:35 GMT):
Thanks @passkit lots of good enterprise type of info request!

schwentker2 (Thu, 09 Feb 2017 17:08:56 GMT):
@markparz & @passkit may i suggest for the "Creation of a HL Fabric website / splash page--> that leads to documentation for both a developer and a business person" that there's also documentation for a sys admin/dev ops person? So there'd be three links: for business, developers & sys admin.

joshhus (Thu, 09 Feb 2017 17:44:03 GMT):
Barry does your dir URL presume anything on the "pusher's" end? e.g. for /fabric/docs I use this local path: /c/Go/mygoworkpath/src/github.com/hyperledger/fabric

bmos299 (Thu, 09 Feb 2017 18:36:02 GMT):
git push -f https://bmos299/fabric master

bmos299 (Thu, 09 Feb 2017 18:36:02 GMT):
git push -f https://github.com/bmos299/fabric master

bmos299 (Thu, 09 Feb 2017 18:36:32 GMT):
you need to do the git add, git commit

joshhus (Thu, 09 Feb 2017 18:38:05 GMT):
joshh@joshh MINGW64 /c/Go/mygoworkpath/src/github.com/fabric (master) $ git push -f https://bmos299/fabric master fatal: unable to access 'https://bmos299/fabric/': Couldn't resolve host 'bmos299' joshh@joshh MINGW64 /c/Go/mygoworkpath/src/github.com/fabric (master)

joshhus (Thu, 09 Feb 2017 18:39:24 GMT):
not urgent, Barry, just trying to test the process.

bmos299 (Thu, 09 Feb 2017 18:41:02 GMT):
does that machine have internet connectivity

joshhus (Thu, 09 Feb 2017 18:41:58 GMT):
maybe I need to upload my SSH credentials ...

bmos299 (Thu, 09 Feb 2017 18:44:39 GMT):
git push -f https://github.com/bmos299/fabric

bmos299 (Thu, 09 Feb 2017 18:46:59 GMT):
Hi Josh, try this: git push -f https://github.com/bmos299/fabric master

joshhus (Thu, 09 Feb 2017 18:48:04 GMT):
joshh@joshh MINGW64 /c/Go/mygoworkpath/src/github.com/fabric (master) $ git push -f https://github.com/bmos299/fabric master remote: Permission to bmos299/fabric.git denied to joshhus. fatal: unable to access 'https://github.com/bmos299/fabric/': The requested URL returned error: 403

joshhus (Thu, 09 Feb 2017 18:48:25 GMT):
note I'm on master. we're not doing branches right.

joshhus (Thu, 09 Feb 2017 18:52:24 GMT):
I cloned the dir no prob. So it's a push issue.

joshhus (Thu, 09 Feb 2017 18:56:13 GMT):
joshh@joshh MINGW64 /c/Go/mygoworkpath/src/github.com $ git clone https://github.com/bmos299/fabric.git Cloning into 'fabric'... remote: Counting objects: 21936, done. remote: Total 21936 (delta 0), reused 0 (delta 0), pack-reused 21936 Receiving objects: 100% (21936/21936), 42.13 MiB | 4.37 MiB/s, done. Resolving deltas: 100% (11691/11691), done. Checking connectivity... done. Checking out files: 100% (3056/3056), done.

passkit (Fri, 10 Feb 2017 04:55:50 GMT):
@schwentker2 that would be perfect.

markparz (Fri, 10 Feb 2017 14:25:57 GMT):
@schwentker2 & @passkit LOVE the idea.... what sort of topics would you foresee ? I'm guessing like "my peer's ledger isn't updating"... check these things, debugging a peer, reading the log, etc... Let's build a table of contents together or at minimum a list of topics.

bmos299 (Sat, 11 Feb 2017 17:54:51 GMT):
Please feel free to comment on a sample of the new TOC for the documentation. It is being staged at: http://fabric-rtd.readthedocs.io/en/latest/

bmos299 (Sat, 11 Feb 2017 17:58:29 GMT):
...there are new docs in some of the links and some of the documents are a wip.

arvindupadhyaya (Sun, 12 Feb 2017 04:53:45 GMT):
Hi @bmos299 in this section, I ran into a issue with mac for the `npm install` part in which I needed to install Xcode. Please add that as a pre-req. Also if the error points out its an Xcode issue, the node_modules folder should be removed completely and re-installed using `rm -rf node_modules && npm i`

arvindupadhyaya (Sun, 12 Feb 2017 04:53:45 GMT):
Hi @bmos299 in this section http://fabric-rtd.readthedocs.io/en/latest/asset_setup/#curl-the-application-source-code-and-sdk-modules, I ran into a issue with mac for the `npm install` part in which I needed to install Xcode. Please add that as a pre-req. Also if the error points out its an Xcode issue, the node_modules folder should be removed completely and re-installed using `rm -rf node_modules && npm i`

arvindupadhyaya (Sun, 12 Feb 2017 04:55:19 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=TquAYm7ZMsh9fZLK9)

weeds (Mon, 13 Feb 2017 13:32:55 GMT):
Talking with Nick Gaski- the plan for documentation this week is to get - key concepts which includes overview, why fabric, use cases, glossary, and the models (which we need to come up with a better title for). Getting started is done- so we could use comments on getting started.

weeds (Mon, 13 Feb 2017 13:33:10 GMT):
Under architecture, they want to get ledger and Python piece done (python is under interfaces)

weeds (Mon, 13 Feb 2017 13:33:30 GMT):
The team has a staging environment at this location that should be seen by the community: http://fabric-rtd.readthedocs.io/en/latest/glossary

weeds (Mon, 13 Feb 2017 13:33:50 GMT):
At this point it would be helpful if people could comment on use cases and glossary as it stands now

weeds (Mon, 13 Feb 2017 13:34:40 GMT):
Josh said he's going to get why blockchain and is going to get gossip done

rameshthoomu (Mon, 13 Feb 2017 19:00:18 GMT):
@nickgaski We have to update gettingstarted.md once this patch is merged https://gerrit.hyperledger.org/r/#/c/5617

joshhus (Mon, 13 Feb 2017 20:59:19 GMT):
why blockchain and gossip are already done. I also added "capabilities" ... I'm on to channels and ledger.

rameshthoomu (Mon, 13 Feb 2017 23:46:38 GMT):
RTD (fabric documentation) builds are failing while installing python modules.. Could be network issue.. Will re-trigger build after sometime..

rameshthoomu (Mon, 13 Feb 2017 23:46:38 GMT):
RTD (fabric documentation) builds are failing while installing python modules as part of the build process.. Could be network issue.. Will re-trigger build after sometime..

murrekatt (Tue, 14 Feb 2017 13:33:00 GMT):
are there pending changes to the docs for the protocol? https://github.com/hyperledger/fabric/blob/master/docs/protocol-spec.md

rameshthoomu (Tue, 14 Feb 2017 16:27:06 GMT):
RTD build is still failing.. Seems everyone hitting the same issue. https://github.com/rtfd/readthedocs.org/issues/2640

markparz (Tue, 14 Feb 2017 18:46:36 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=Zkon9B5PRCyNY52gW) @murrekatt It's a dated Doc for sure... we will either have to fix it up, or trash it. It could be a great start to a tech whitepaper

mcoblenz (Tue, 14 Feb 2017 21:00:01 GMT):
Is the Chaincode-setup.md page up to date? I'm having issues; it seems "deploy" may have been renamed "instantiate," and also it wants an endorser, which I'm not sure how to create.

mcoblenz (Tue, 14 Feb 2017 21:00:10 GMT):
(I'm referring to https://github.com/hyperledger/fabric/blob/master/docs/Setup/Chaincode-setup.md#chaincode-deploy-via-cli-and-rest)

rameshthoomu (Tue, 14 Feb 2017 23:16:09 GMT):
Documentation build is now working..https://github.com/rtfd/readthedocs.org/issues/2640

nickgaski (Wed, 15 Feb 2017 00:43:21 GMT):
@mcoblenz use the getting started guide for now http://hyperledger-fabric.readthedocs.io/en/latest/gettingstarted/

nickgaski (Wed, 15 Feb 2017 00:44:06 GMT):
we are in the process of updating the docs to reflect the myriad changes in v1. the getting started will show you a simple approach using docker and a basic node application

nickgaski (Wed, 15 Feb 2017 00:45:03 GMT):
bear with us, and feel free to contribute any doc! we're always on the lookout :telescope:

murrekatt (Wed, 15 Feb 2017 06:52:07 GMT):
are the terms non-validating and validating still in v1 or replaced by endorser and committer?

jwolpert (Wed, 15 Feb 2017 13:36:25 GMT):
Yeah, there isn't much point in the distinction anymore. Peers are Peers...they can endorse and they can commit.

murrekatt (Wed, 15 Feb 2017 13:40:04 GMT):
thanks @jwolpert what about accessibility to endorsers from a client that sends the initial transaction proposal which needs to get to all/enough endorsers. will the endorsers forward the proposal to the others or how does that work?

nickgaski (Wed, 15 Feb 2017 14:51:06 GMT):
@murrekat - the application will hold the endorsement policy, because it will bear responsibility for interpreting the proposal responses which return from the endorsers. As such, at proposal time, it knows which peers to target for endorsement. If the policy is fulfilled, you forward this "proposal response" on to the ordering service. Then at validation phase, the peers will double check to make sure that a. enough signatures are present & b. these signatures are authentic and arrived from the correct entities. Then the real magic happens at ledger phase where a versioning check takes place... essentially is the world state (the version of the keys that was used during simulation) still the same? If so, then the write set is appended and the world state & versions are updated. Does this help?

murrekatt (Wed, 15 Feb 2017 15:18:52 GMT):
@nickgaski thanks! yes that helped. I am aware of the flow, just not clear in the docs i have checked have accessible the endorsers are. especially when it might be that the client must use a peer as proxy to reach the orderer(s) i thought it might be the same in case the client just has access to a single endorser. but you mean that a client MUST have access to all endorsers directly?

nickgaski (Wed, 15 Feb 2017 15:32:28 GMT):
it's a good question. I believe that the client is able to target all peers for that specific chaincode, and then receive and aggregate back the responses. Let me give you back a concrete answer for "does your endorsing peer act as a proxy for proposals and responses?" I'm fairly certain the answer is no. Also, the tx does not pass back through the peers on the way to OS. The application will parse the responses and then use the SDK to send a grpc call to the Ordering Service with the payload

murrekatt (Wed, 15 Feb 2017 15:48:47 GMT):
it's mentioned that if a client does not have direct access to the ordering service it can use a proxy (a trusted peer)...let me give link

murrekatt (Wed, 15 Feb 2017 15:49:09 GMT):
http://hyperledger-fabric.readthedocs.io/en/latest/arch-deep-dive/#23-the-submitting-client-collects-an-endorsement-for-a-transaction-and-broadcasts-it-through-ordering-service

murrekatt (Wed, 15 Feb 2017 15:51:38 GMT):
based on this and what you say the clients all have direct access to all (required per endorsement policy) endorsers which might be split off from the committer part of the peers, and the client might or might not have direct access to the orderers so it can thus use and of the endorser peers (assuming just one is picked)

nickgaski (Wed, 15 Feb 2017 15:57:52 GMT):
no anything with endorser, committer, ordering service is all v1.0 nomenclature. so yes, it appears you are correct that in certain scenarios if a client does not direct access to an OS, it will broadcast the tx through a peer of its choice who will then forward on to the OS. I suppose this makes sense once you start getting into deeper areas of abstraction and access control

markparz (Thu, 16 Feb 2017 01:14:10 GMT):
I went and played on squarespace briefly and came up with these

markparz (Thu, 16 Feb 2017 01:14:25 GMT):
@cbf basically used what you had... and added some icons and such

markparz (Thu, 16 Feb 2017 01:15:28 GMT):
trying to figure out how to get it somewhere that people can see live

markparz (Thu, 16 Feb 2017 01:16:26 GMT):
Let me know if you think this is good, or use the other mock up

markparz (Thu, 16 Feb 2017 01:23:40 GMT):
Trust me, my feelings aren't hurt if we like the first mock up, and I can work to add the icons to it, or whatever

passkit (Thu, 16 Feb 2017 05:58:24 GMT):
Is there a documentation available on the msp certificates that are required to provision an orderer. What is the role/purpose of each certificate and how should they be maintained/provided in a production environment?

RajkumarNatarajan (Fri, 17 Feb 2017 03:56:19 GMT):
Has joined the channel.

passkit (Fri, 17 Feb 2017 07:10:10 GMT):
I am using the certificates returned by enrolling with fabric-ca server, but I receive the following error when trying to use the generated peer certificate in the `signcerts` folder: `Failed associating self PKIID to cert: A CA certificate cannot be used directly by this MSP`

smithbk (Fri, 17 Feb 2017 19:12:11 GMT):
openssl x509 -in $1 -text -noout -serial

joshhus (Sat, 18 Feb 2017 02:48:51 GMT):
I like the green thing - note there's a blockchain color palette now - see Kayla BLue and BLockchain seem to go together intuitively ... The BOLD HL text is too bold though, back it off a bit, and increase the text below it, and decide on some capitalization consistency. ... as for the descriptive text in the other screenshot, that's been upgraded substantially, fyi. ... e.g. I don't think we're an implementation of blockchain technology, we're more fundamental -- we're a fabric that enables implementations of blockchain technology. e.g. Bitcoin is an implementation. My $0.02.

passkit (Sat, 18 Feb 2017 05:50:14 GMT):
It was created by the latest build of fabric-ca

passkit (Sat, 18 Feb 2017 05:50:14 GMT):
@smithbk It was created by the latest build of fabric-ca

passkit (Sat, 18 Feb 2017 05:52:10 GMT):
Certificate: Data: Version: 3 (0x2) Serial Number: 31:fb:a2:f6:dc:74:28:85:30:38:c0:11:40:e0:3b:78:e4:82:99:f0 Signature Algorithm: ecdsa-with-SHA256 Issuer: C=US, ST=Delaware, L=Wilmington, O=PassKit, Inc., OU=Blockchain Applications, CN=ca.blockchain.passkit.com Validity Not Before: Feb 15 08:43:00 2017 GMT Not After : Feb 15 08:43:00 2022 GMT Subject: C=HK, ST=Central and Western District, L=Sheung Wan, O=PassKit, Inc., OU=Blockchain Applications, CN=pkpeer1 Subject Public Key Info: Public Key Algorithm: id-ecPublicKey Public-Key: (256 bit) pub: 04:aa:b9:ee:6d:b5:1a:e2:74:76:e6:46:48:3d:99: ae:3c:51:1d:ce:d3:93:78:5a:01:c3:81:52:e1:d5: 2b:a0:7c:73:02:b5:39:d8:16:76:6c:6c:90:a1:9c: 72:d3:a0:16:29:77:87:8c:68:71:42:16:95:f2:eb: 40:9c:5d:0e:2a ASN1 OID: prime256v1 NIST CURVE: P-256 X509v3 extensions: X509v3 Key Usage: critical Certificate Sign X509v3 Basic Constraints: critical CA:TRUE X509v3 Subject Key Identifier: E0:FE:1A:9A:DE:9D:B7:E2:91:8B:F7:15:44:42:7F:9B:C7:F4:DD:1B X509v3 Authority Key Identifier: keyid:3D:13:BE:2A:3A:B3:53:2C:4F:54:E6:1A:84:2C:31:F2:2C:F1:D3:C6 Signature Algorithm: ecdsa-with-SHA256 30:46:02:21:00:b3:bb:a5:1e:13:c4:18:f9:5e:bf:fc:51:41: 27:e6:e4:88:9d:7b:0d:35:be:8a:1b:22:49:1c:8d:08:56:1c: 04:02:21:00:c0:42:94:97:64:52:ac:66:74:7a:23:56:cc:36: b4:54:79:19:c3:ab:4a:ba:d5:4f:f0:9e:c7:14:77:6b:60:31 serial=3Certificate: Data: Version: 3 (0x2) Serial Number: 31:fb:a2:f6:dc:74:28:85:30:38:c0:11:40:e0:3b:78:e4:82:99:f0 Signature Algorithm: ecdsa-with-SHA256 Issuer: C=US, ST=Delaware, L=Wilmington, O=PassKit, Inc., OU=Blockchain Applications, CN=ca.blockchain.passkit.com Validity Not Before: Feb 15 08:43:00 2017 GMT Not After : Feb 15 08:43:00 2022 GMT Subject: C=HK, ST=Central and Western District, L=Sheung Wan, O=PassKit, Inc., OU=Blockchain Applications, CN=pkpeer1 Subject Public Key Info: Public Key Algorithm: id-ecPublicKey Public-Key: (256 bit) pub: 04:aa:b9:ee:6d:b5:1a:e2:74:76:e6:46:48:3d:99: ae:3c:51:1d:ce:d3:93:78:5a:01:c3:81:52:e1:d5: 2b:a0:7c:73:02:b5:39:d8:16:76:6c:6c:90:a1:9c: 72:d3:a0:16:29:77:87:8c:68:71:42:16:95:f2:eb: 40:9c:5d:0e:2a ASN1 OID: prime256v1 NIST CURVE: P-256 X509v3 extensions: X509v3 Key Usage: critical Certificate Sign X509v3 Basic Constraints: critical CA:TRUE X509v3 Subject Key Identifier: E0:FE:1A:9A:DE:9D:B7:E2:91:8B:F7:15:44:42:7F:9B:C7:F4:DD:1B X509v3 Authority Key Identifier: keyid:3D:13:BE:2A:3A:B3:53:2C:4F:54:E6:1A:84:2C:31:F2:2C:F1:D3:C6 Signature Algorithm: ecdsa-with-SHA256 30:46:02:21:00:b3:bb:a5:1e:13:c4:18:f9:5e:bf:fc:51:41: 27:e6:e4:88:9d:7b:0d:35:be:8a:1b:22:49:1c:8d:08:56:1c: 04:02:21:00:c0:42:94:97:64:52:ac:66:74:7a:23:56:cc:36: b4:54:79:19:c3:ab:4a:ba:d5:4f:f0:9e:c7:14:77:6b:60:31 serial=31FBA2F6DC7428853038C01140E03B78E48299F01FBA2F6DC7428853038C01140E03B78E48299F0

passkit (Sat, 18 Feb 2017 05:54:06 GMT):
`Certificate: Data: Version: 3 (0x2) Serial Number: 31:fb:a2:f6:dc:74:28:85:30:38:c0:11:40:e0:3b:78:e4:82:99:f0 Signature Algorithm: ecdsa-with-SHA256 Issuer: C=US, ST=Delaware, L=Wilmington, O=PassKit, Inc., OU=Blockchain Applications, CN=ca.blockchain.passkit.com Validity Not Before: Feb 15 08:43:00 2017 GMT Not After : Feb 15 08:43:00 2022 GMT Subject: C=HK, ST=Central and Western District, L=Sheung Wan, O=PassKit, Inc., OU=Blockchain Applications, CN=pkpeer1 Subject Public Key Info: Public Key Algorithm: id-ecPublicKey Public-Key: (256 bit) pub: 04:aa:b9:ee:6d:b5:1a:e2:74:76:e6:46:48:3d:99: ae:3c:51:1d:ce:d3:93:78:5a:01:c3:81:52:e1:d5: 2b:a0:7c:73:02:b5:39:d8:16:76:6c:6c:90:a1:9c: 72:d3:a0:16:29:77:87:8c:68:71:42:16:95:f2:eb: 40:9c:5d:0e:2a ASN1 OID: prime256v1 NIST CURVE: P-256 X509v3 extensions: X509v3 Key Usage: critical Certificate Sign X509v3 Basic Constraints: critical CA:TRUE X509v3 Subject Key Identifier: E0:FE:1A:9A:DE:9D:B7:E2:91:8B:F7:15:44:42:7F:9B:C7:F4:DD:1B X509v3 Authority Key Identifier: keyid:3D:13:BE:2A:3A:B3:53:2C:4F:54:E6:1A:84:2C:31:F2:2C:F1:D3:C6 Signature Algorithm: ecdsa-with-SHA256 30:46:02:21:00:b3:bb:a5:1e:13:c4:18:f9:5e:bf:fc:51:41: 27:e6:e4:88:9d:7b:0d:35:be:8a:1b:22:49:1c:8d:08:56:1c: 04:02:21:00:c0:42:94:97:64:52:ac:66:74:7a:23:56:cc:36: b4:54:79:19:c3:ab:4a:ba:d5:4f:f0:9e:c7:14:77:6b:60:31 serial=31FBA2F6DC7428853038C01140E03B78E48299F0`

vdods (Mon, 20 Feb 2017 00:57:17 GMT):
HLF 1.0 deprecated the table interface for ChaincodeStub in favor of rich query-language DB. Where is the documentation on that? I can't find anything relevant in https://github.com/hyperledger/fabric/blob/master/docs/protocol-spec.md which presumably would have that info.

murrekatt (Mon, 20 Feb 2017 08:57:55 GMT):
i just tried the multi-channel docs (https://github.com/hyperledger/fabric/blob/master/docs/channel-setup.md) and ran into errors when i run create channel command in the cli container `CORE_PEER_COMMITTER_LEDGER_ORDERER=orderer:5005 peer channel create -c myc1`

murrekatt (Mon, 20 Feb 2017 08:58:20 GMT):
`Received block: header:<6:39 0:"\x00" } 0:4 4:4204454237677 5:/* unexpected EOF */ 9:14548527764448451823 1415527029 { 15 { 1:/* unknown wire type 6 */ 7:/* unknown wire type 7 */ 6:80421075`...

murrekatt (Mon, 20 Feb 2017 08:59:08 GMT):
i'm on master latest `e829d2ecfd9a2bfc378a08a9364215f241a0a09b`

philippemail-infos (Mon, 20 Feb 2017 12:26:53 GMT):
Has joined the channel.

rameshthoomu (Mon, 20 Feb 2017 19:04:40 GMT):
http://hyperledgerdocs.readthedocs.io/en/latest/

markparz (Mon, 20 Feb 2017 22:08:57 GMT):
@cbf looking for feedback on this revision of the TOC

markparz (Mon, 20 Feb 2017 22:09:18 GMT):
dangit.. hang.. need to put in a doc

weeds (Tue, 21 Feb 2017 02:56:14 GMT):
I'm wondering if title of Getting started is really "QuickStart"?

weeds (Tue, 21 Feb 2017 03:04:24 GMT):
In most of the open source projects I've been looking at- "education" was called "tutorial" (Kubernetes is a good example here)

weeds (Tue, 21 Feb 2017 03:06:21 GMT):
I would like to know @cbf opinion, but I think "Administration and operation" might be titled better "configurations"?

weeds (Tue, 21 Feb 2017 03:07:58 GMT):
For Tutorials section- I thought we had put the SDK information here- this is what people will program most to, yes? Seems like the better place versus under architecture

weeds (Tue, 21 Feb 2017 03:09:21 GMT):
Under peer- seems like policies should right after endorser

weeds (Tue, 21 Feb 2017 03:10:49 GMT):
I don't know when fabric-composer goes into incubation- I'm wondering where we might provide a pointer to it?

weeds (Tue, 21 Feb 2017 03:12:10 GMT):
Also, we do get asked about events specifically a lot. I'm wondering if right after the SDK sections at the same level we have events?

weeds (Tue, 21 Feb 2017 03:13:12 GMT):
Maybe instead of the title gossip- we should use communication protocols and then go into depth in the material itself

weeds (Tue, 21 Feb 2017 03:15:33 GMT):
scratch that- administration and operation is a better set of terms

weeds (Tue, 21 Feb 2017 03:21:23 GMT):
@murrekatt I suggest asking your question on fabric-peer-endorser-comitter

weeds (Tue, 21 Feb 2017 03:21:52 GMT):
@vdods i think i answered your question on the fabric-questions channel

cbf (Tue, 21 Feb 2017 19:32:45 GMT):
SDK and Fabric CA sections will need to be linked for now

greg.haskins (Mon, 27 Feb 2017 13:52:18 GMT):
Hello all, I currently maintain the documentation for chaintool as github markdown, was contemplating migrating it to readthedocs

greg.haskins (Mon, 27 Feb 2017 13:52:53 GMT):
In its current form its these three pages: https://github.com/hyperledger/fabric-chaintool

greg.haskins (Mon, 27 Feb 2017 13:53:04 GMT):
https://github.com/hyperledger/fabric-chaintool/blob/master/documentation/platforms/golang/README.md

greg.haskins (Mon, 27 Feb 2017 13:53:21 GMT):
https://github.com/hyperledger/fabric-chaintool/blob/master/examples/example02/README.md

greg.haskins (Mon, 27 Feb 2017 13:53:36 GMT):
though I may do some refactoring as I update the docs for 1.0

greg.haskins (Mon, 27 Feb 2017 13:54:08 GMT):
I could just go create a readthedocs setup, but figured I should ask in case there is a more cohesive way to do it

rameshthoomu (Mon, 27 Feb 2017 14:52:48 GMT):
@greg.haskins Shall I setup one for fabric-chaintool in RTD? and submit patch to fabric-chaintool with docs changes..

greg.haskins (Mon, 27 Feb 2017 14:53:53 GMT):
@rameshthoomu wait for community input

mrkiouak (Tue, 28 Feb 2017 17:51:48 GMT):
Hi all -- is there a v1 component architecture diagram already somewhere? http://hyperledger-fabric.readthedocs.io/en/latest/components/ references one but as wip it isn't availablet yet. Before I reinvent the wheel on this one and generate, is there one somewhere else I can pull from?

markparz (Tue, 28 Feb 2017 18:18:14 GMT):
@mrkiouak we have so many different versions, but I don't think we have the one we want yet... would you like to work together on it? It's a top priority item in my mind

markparz (Tue, 28 Feb 2017 18:21:56 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=x45BX8cTycNGu28d7) @greg.haskins AWESOME! @nickgaski suggestion on the most prudent way? My thought is to have a new topic in the TOC called tooling? Could have a link to chaintool & composer at min to start with...

mrkiouak (Tue, 28 Feb 2017 18:26:15 GMT):
@markparz sure.. let me ping you a little later in the day on this, have meetings till 4

mrkiouak (Wed, 01 Mar 2017 00:41:16 GMT):
@markparz let me know when we can do a quick chat on topology doc, apologies i got caught up the rest of the day

markparz (Wed, 01 Mar 2017 03:07:51 GMT):
No worries, will ping you tomorrow, are you east coast?

SyneBlockChainTeam (Wed, 01 Mar 2017 11:41:45 GMT):
Has joined the channel.

greg.haskins (Wed, 01 Mar 2017 15:26:39 GMT):
FYI, I completed the conversion with chaintool: https://gerrit.hyperledger.org/r/#/c/6675/

greg.haskins (Wed, 01 Mar 2017 15:26:54 GMT):
previews here: http://fabric-chaintoolghaskins.readthedocs.io/en/latest/

greg.haskins (Wed, 01 Mar 2017 15:27:27 GMT):
still needs a little more work to bring the example documentation in, but its a start

greg.haskins (Wed, 01 Mar 2017 15:28:15 GMT):
I stole the front-page README.md from fabric: https://github.com/ghaskins/fabric-chaintool

greg.haskins (Wed, 01 Mar 2017 19:32:37 GMT):
new doc is live: http://fabric-chaintool.readthedocs.io/en/latest/

nickgaski (Thu, 02 Mar 2017 19:42:41 GMT):
new TOC - proposal http://fabric-rtd.readthedocs.io/en/latest/

lehors (Thu, 02 Mar 2017 20:00:45 GMT):
Nick, I will take the time to go through some of this

lehors (Thu, 02 Mar 2017 20:00:45 GMT):
@nickgaski I will take the time to go through some of this

lehors (Thu, 02 Mar 2017 20:01:13 GMT):
at first glance it looks great but I think the first page is too crowded

lehors (Thu, 02 Mar 2017 20:01:54 GMT):
half page long paragraphs are hard to look at

cbf (Thu, 02 Mar 2017 20:05:43 GMT):
https://chat.hyperledger.org/channel/fabric-maintainers?msg=mbCQfPqsgbpdkobCx

cbf (Thu, 02 Mar 2017 20:27:55 GMT):
@nickgaski @markparz @bmos299 ok, monster patch merged

cbf (Thu, 02 Mar 2017 20:28:10 GMT):
we need the incubation message updated as per what was just removed

bmos299 (Thu, 02 Mar 2017 20:33:57 GMT):
@cbf http://hyperledger-fabric.readthedocs.io/en/latest/ is now updated.

rameshthoomu (Thu, 02 Mar 2017 20:34:32 GMT):
@cbf @nickgaski @bmos299 I have changed from mkdocs to "sphinx" in RTD and started build..

bmos299 (Thu, 02 Mar 2017 20:35:59 GMT):
@rameshthoomu is completed and looks great. @cbf no more monster patches

nickgaski (Thu, 02 Mar 2017 20:47:03 GMT):
thanks @rameshthoomu - we all owe you a :clap: for the styling and the intricacies that go into these builds. It looks pretty groovy. Still work to do, but at least we're heading down the right path. Thanks @cbf @mastersingh24 @JonathanLevi for the merge. No more big patch sets we promise

lehors (Thu, 02 Mar 2017 21:00:20 GMT):
Would have been nice to fix the status stuff before the merge

lehors (Thu, 02 Mar 2017 21:00:42 GMT):
I now have a tweet with a broken link out there

lehors (Thu, 02 Mar 2017 21:13:24 GMT):
What is the police doing about it?! ;-)

JonathanLevi (Thu, 02 Mar 2017 21:56:51 GMT):
OK, @nickgaski, @lehors, @cbf: so for the record, you heard this here first: *too-large-patchset-citations wrt the blockchain - on the blockchain*

lehors (Thu, 02 Mar 2017 22:00:17 GMT):
@JonathanLevi No disagreement from us

lehors (Thu, 02 Mar 2017 22:07:03 GMT):
I realize everybody was stressing over my broken tweet so I deleted it. You can all relax.

lehors (Thu, 02 Mar 2017 22:08:00 GMT):
More seriousy, LF is working on some PR

lehors (Thu, 02 Mar 2017 23:51:58 GMT):
ok, I just submitted a change to fix the status

lehors (Fri, 03 Mar 2017 00:09:42 GMT):
I'll be in a plane for the next 12h so if something is wrong someone else will need to fix it

gauthampamu (Mon, 06 Mar 2017 00:01:53 GMT):
In documentation, three SDK are referenced java, node and python. http://hyperledger-fabric.readthedocs.io/en/latest/txflow.html Are we planning to provide these three SDK with v1.0. In the documentation navigation, there is reference to just Node SDK ? Are we just support only NodeSDK.

jeffchi (Mon, 06 Mar 2017 08:04:18 GMT):
On this page https://chat.hyperledger.org/channel/fabric-documentation, one obvious error in the `Asset Transfer with SDK' section; the code for Linux&OS should be

jeffchi (Mon, 06 Mar 2017 08:04:18 GMT):
On this page https://chat.hyperledger.org/channel/fabric-documentation, one obvious error in the `Asset Transfer with SDK` section; the code for Linux&OSX should be

jeffchi (Mon, 06 Mar 2017 08:09:31 GMT):
or `export GOPATH=$PWD && node deploy.js`

markparz (Mon, 06 Mar 2017 15:52:40 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=iaWikqoZisdWKM3Qe) @gauthampamu Thanks @gauthampamu we should just change to reflect SDK(s) more generic, as they should all run the same, and we also have a Go SDK being submitted soon.

markparz (Mon, 06 Mar 2017 15:53:46 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=Xxvz4X67jBQMfK4cG) @jeffchi Good point, we made the assumption the path was already set... good add

markparz (Mon, 06 Mar 2017 16:07:00 GMT):
Would like it if any and all could go out to the docs and start reviewing items. http://hyperledger-fabric.readthedocs.io/en/latest/fabric_model.html here is the list to start with.. just review any section(s) you are interested in, all feedback is welcomed for sure: Overview What's Offered Architecture Explained Endorsement Policies Fabric Model Glossary (Virtually finalized IMHO completed several reviews already) What’s included Transaction Flow Logging control Ledger (Virtually finalized IMHO completed several reviews already) Read-Write set Semantics End to End Flow Contributors welcome Using Jira to understand current work items setting up dev Enc building the fabric building outside of vagrant Generating gRPC code

markparz (Mon, 06 Mar 2017 16:07:28 GMT):
and of course any additional pieces missing we welcome the help, including identification of any gaps

lehors (Tue, 07 Mar 2017 12:52:56 GMT):
@markparz where should the feedback be sent to? this channel?

weeds (Tue, 07 Mar 2017 14:54:43 GMT):
we need access control question added to doc -- I've asked Binh to write something up if he can

lehors (Tue, 07 Mar 2017 21:06:11 GMT):
I have a simple question: have we settled on using chaincode rather than chain-code?

lehors (Tue, 07 Mar 2017 21:06:34 GMT):
I believe chaincode is the term most commonly used but I saw several occurences of chain-code

warong (Fri, 10 Mar 2017 10:11:23 GMT):
Hi all, I was curious if v0.6 documentation is still available anywhere?

nickgaski (Fri, 10 Mar 2017 16:46:49 GMT):
hey @warong - we changed some styling and formatting features for our docs and currently v0.6 does not build in our Read The Docs output. However you can navigate through the github library - https://github.com/hyperledger/fabric/tree/v0.6 - and track down individual markdown files that you might need

cbf (Sat, 11 Mar 2017 00:08:06 GMT):
@nickgaski @markparz @joshhus @bmos299 @weeds some feedback on the latest rev of the docs follows

cbf (Sat, 11 Mar 2017 00:08:55 GMT):
should be titled 'Introduction' rather than 'Welcome to Fabric'

cbf (Sat, 11 Mar 2017 00:09:20 GMT):
2. the index page is a bit too market-y for my tastes.

cbf (Sat, 11 Mar 2017 00:12:15 GMT):
3. the 'What's Offered' page is just weird - there should simply be one top-level TOC entry that breaks out when clicked into sections (like the 'Getting Setup' page)

cbf (Sat, 11 Mar 2017 00:12:58 GMT):
I really find it weird that the TOC section titles are not reflected in the docs themselves in the navigation, I really think that is odd

cbf (Sat, 11 Mar 2017 00:13:43 GMT):
so, I would change 'Getting Setup' to 'Getting Started' and include the 'What's offered content in the Getting Started page as the first sub-section

cbf (Sat, 11 Mar 2017 00:15:19 GMT):
why is this not one page (the Fabric Model page)? and just one line in the TOC?

cbf (Sat, 11 Mar 2017 00:16:05 GMT):
5. Use cases should not be a sub-section of Key Concepts, it should be its own top-level entry in TOC

cbf (Sat, 11 Mar 2017 00:17:16 GMT):
6. I really don't like 'Education' - the docs themselves are 'education'

cbf (Sat, 11 Mar 2017 00:18:46 GMT):
we should NOT be teaching people how to Docker Compose or anything that isn't us. We should have a reference section that points people at related informational content - like how to use docker-compose or whatever

cbf (Sat, 11 Mar 2017 00:20:34 GMT):
7. the 'Configuration Considerations' section should be renamed 'Operations Guide' as that is what it is

cbf (Sat, 11 Mar 2017 00:21:18 GMT):
8. can we please be consistent about how we label v1.0 - it is v1.0 not v1 or V1 or V1.0

cbf (Sat, 11 Mar 2017 00:22:24 GMT):
9. Troubleshooting and Faqs should be two sections, not one

cbf (Sat, 11 Mar 2017 00:22:39 GMT):
and I think the content needs to be revisited

cbf (Sat, 11 Mar 2017 00:23:38 GMT):
10. ok, now I am pissed... we relegated contributor guide etc to the Appendix section - bzzzt

cbf (Sat, 11 Mar 2017 00:23:47 GMT):
that whole section needs to be rethought

cbf (Sat, 11 Mar 2017 00:24:08 GMT):
sorry that I have been out of the loop, but this needs some serious work still

weeds (Sat, 11 Mar 2017 13:35:19 GMT):
@jwolpert Hi John- you had stepped into help me so see above ^^

markparz (Mon, 13 Mar 2017 17:41:03 GMT):
Anyone that is interested, we are going to have a playback on documentation Wed at 2:30pm EST... I will send out meeting details on Wed prior to the meeting, along with a reminder... but you might want to block your calendars now :)

lehors (Wed, 15 Mar 2017 15:54:30 GMT):
1. Navigation panel It is missing a pointer to the Welcome page It's weird that the section headers in green are not clickable Overall, I feel like this should map more closely to the pages. 2. Welcome page As Chris said, it reads too much like marketing material. I think the paragaphs are too long and this page goes into too many details Not every concept needs to be introduced up front. It is better to start with the very basics and let people dig further to find out more details. The sentence "If you're still reading, you clearly have some knowledge and an interest in distributed ledger technology..." is very odd. Most people won't fall into that category and yet you would hope they read the whole page (once it is shrunk to a more reasonable size) 3. What's offered This title doesn't ring right. This sounds like a brochure for a product. I'd suggest something like "What will it take?" or "What's in a basic setup?", something like that. I think that instead of referring to the "SOLO" Ordering Service which raises the question "what's that?" this would read better as "a basic Ordering Service" or if you really want to name it: a basic Ordering Service called "SOLO". Kill the second paragraph. This is not the place to explain all this. 4. Getting Setup On Windows if npm install fails due to missing VCBuild.exe, user should do 'npm install --global windows-build-tools' as Administrator as explained in https://github.com/felixrieseberg/windows-build-tools or check https://github.com/nodejs/node-gyp#installation for other options Unfortunately while the above helped me I still haven't managed to get the whole node stuff to work but that's a different story... Create the initial channel - this whole section isn't really useful at this point because the reader has already gone through everything and the channel was created. This fails to point out that one would have to reset the whole network then (docker-compose down+up). Trouble shooting "This occurs because you are attempting to create a channel named myc1, and this channel already exists! There are two options. Try issuing the peer channel create command with a different channel name - myc2." The text after that is essentially a repeat of the CLI section above. Just delete the repeat and change the above with: Try issuing the peer channel create command with a different channel name - myc2 as described in the CLI section above OR, if you want your channel called - myc1 -, remove your docker containers and then follow the same commands in the Manually create and join peers to a new channel topic. Helpful Docker tips - I agree with Chris, just put a link to the docker doc 5. Key Concepts Overview - chaincode links to glossary section instead of the model one Assets - "using the included Fabric Composer tool." It is not included. I suggest changing to something like "using a tool such as Fabric Composer". It seems to me that this section is too detailed at this point in the documentation and it's too much to read if what I want is to get going. I just got my environment set up and the next thing I want to do is to try to modify the example to start doing my own thing. I would expect a section explaining that most of the development will focus on two key areas: chaincode and client side/SDK and how to go at starting to do that. Once people get started with that they can then dig up for more information as they try to do more and more complicated stuff.

lehors (Wed, 15 Mar 2017 22:59:14 GMT):
@markparz in case you didn't see this ^^^

lehors (Wed, 15 Mar 2017 23:00:56 GMT):
as I said, I'd be happy to submit some CR if it helps, I just don't want to create any conflict if someone else is working on those sections already

asadhayat (Thu, 16 Mar 2017 11:05:40 GMT):
Hey all, can any one know when the education part of v1 documentation will be completed..

mastersingh24 (Thu, 16 Mar 2017 11:50:00 GMT):
@asadhayat - very soo we hope

mastersingh24 (Thu, 16 Mar 2017 11:50:00 GMT):
@asadhayat - very soon we hope

mastersingh24 (Thu, 16 Mar 2017 17:29:56 GMT):
@nickgaski - we are not mentioning the e2ecli as a sample in the docs are we?

nickgaski (Thu, 16 Mar 2017 17:31:16 GMT):
yes I'd like it to become the new getting started material

mastersingh24 (Thu, 16 Mar 2017 17:34:04 GMT):
hmm - ok - need to think about how we deal with versioning for the scripts. For the Docker images we should be all set (as by default you should get the ones published to dockerhub). We might need to think about publishing a ZIP file of the other contents

mastersingh24 (Thu, 16 Mar 2017 17:35:00 GMT):
because if we make changes to the master branch, it's possible that things in e2e might change and then that would break the existing alpha

mastersingh24 (Thu, 16 Mar 2017 17:35:49 GMT):
also - who has the ability to publish the fabric-sdk-node readthedocs?

nickgaski (Thu, 16 Mar 2017 17:39:27 GMT):
is there specific content you want out of the SDK repo? If so we can poach the .md files and put them in our source directory. If not then we will have to create a separate build and separate URL for the SDK docs.

mastersingh24 (Thu, 16 Mar 2017 17:58:05 GMT):
we have this http://fabric-sdk-node.readthedocs.io/en/master/ already

mastersingh24 (Thu, 16 Mar 2017 17:58:33 GMT):
I guess we should decide how we want to handle the SDK docs

mastersingh24 (Thu, 16 Mar 2017 17:59:15 GMT):
and this https://www.npmjs.com/package/fabric-client points to https://www.npmjs.com/package/fabric-client

mastersingh24 (Thu, 16 Mar 2017 17:59:59 GMT):
in an idea world, I'd actually like to have the API docs published rather than people have to build them locally

tkuhrt (Thu, 16 Mar 2017 23:46:36 GMT):
Hoping this is the right channel...I made a modification to https://wiki.hyperledger.org/projects/fabric.md -- changed the date that the project moved out of incubation. Now when I look at the page, I see the markdown syntax instead of the formatted page. Any idea what I did wrong? I only changed a single character.

subbu165 (Fri, 17 Mar 2017 15:43:36 GMT):
Hi, If I want to set up Hyperledger V1.0 latest, can you please tell me from where should I start? I need to write chain code and deploy it and I want invoke them using nodesdk, I'm looking at doing this outside of vagrant.

subbu165 (Fri, 17 Mar 2017 15:49:52 GMT):
is this the one for V1.0? https://hyperledger-fabric.readthedocs.io/en/latest/asset_setup.html, but the version is never mentioned there

lehors (Fri, 17 Mar 2017 17:57:38 GMT):
@subbu165 yes, that's the right doc for v1.0

lehors (Fri, 17 Mar 2017 17:58:49 GMT):
@tkuhrt I saw the same thing earlier and fixed it. We use a plugin to handle the markdown and it's flaky unfortunately

lehors (Fri, 17 Mar 2017 17:59:01 GMT):
sometimes it stops rendering properly

lehors (Fri, 17 Mar 2017 17:59:40 GMT):
then it's a matter of luck to get it back on its feet - it typically takes to edit - add a blank line, a space, or remove on, save back - and maybe it's back

lehors (Fri, 17 Mar 2017 17:59:40 GMT):
then it's a matter of luck to get it back on its feet - it typically takes to edit - add a blank line, a space, or remove one, save back - and maybe it's back

tkuhrt (Fri, 17 Mar 2017 18:00:02 GMT):
@lehors: Thanks. i will try to re-edit it to get it back to normal.

lehors (Fri, 17 Mar 2017 18:02:39 GMT):
I've reported the problem to LF which is responsible for this but it seems that my report went nowhere

kuangchao (Mon, 20 Mar 2017 08:04:01 GMT):
I have a Facebook Fabirc forum on Facebook, welcome to join https://www.facebook.com/groups/876837335752599

dave.enyeart (Tue, 21 Mar 2017 14:06:25 GMT):
@nickgaski What is the status of Getting Started? I assumed this page http://hyperledger-fabric.readthedocs.io/en/latest/asset_setup.html (which has the instructions from hackfest timeframe) was going to be replaced with content from the e2e example from alpha timeframe: https://github.com/hyperledger/fabric/blob/master/examples/e2e_cli/end-to-end.rst . Is that a true statement? People are asking where to start...

nickgaski (Tue, 21 Mar 2017 14:07:01 GMT):
@dave.enyeart - hopefully today. working on it now

rahulhegde (Tue, 21 Mar 2017 18:47:38 GMT):
Is there a documentation/guildeline/playback = to help setup Kafka and Zookeeper with the Fabric Alpha Release?

jeffgarratt (Tue, 21 Mar 2017 18:50:30 GMT):
@rahulhegde this will do it for you https://gerrit.hyperledger.org/r/#/c/7227/

jeffgarratt (Tue, 21 Mar 2017 18:53:32 GMT):
if you run the behave system per https://github.com/hyperledger/fabric/tree/master/bddtests#welcome-to-the-behavioral-driven-development-bdd-subsytem-for-fabric

jeffgarratt (Tue, 21 Mar 2017 18:54:17 GMT):
you can simply choose you config in the examples section and then remove the comment on doNotDecompose

jeffgarratt (Tue, 21 Mar 2017 18:56:37 GMT):
this example will show you what your looking for =>docker-compose-next-4.yml ./environments/orderer-1-kafka-1/docker-compose.yml orderer-3-kafka-1.yml

rahulhegde (Tue, 21 Mar 2017 20:03:18 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=9A2st7pi2ZqzkzmoR) @jeffgarratt This should be good to start, Thanks.

rickr (Thu, 23 Mar 2017 17:12:37 GMT):
Look for a doco link on how developer can set up dev environment ? Particularly one that explains running with Vagrant. We used to have that but I now find 404 .. thx

rickr (Thu, 23 Mar 2017 17:12:37 GMT):
Lookin for a doco link on how developer can set up dev environment ? Particularly one that explains running with Vagrant. We used to have that but I now find 404 .. thx

rickr (Thu, 23 Mar 2017 17:13:34 GMT):
https://github.com/hyperledger/fabric if you look at Contributing the link there is just a 404

rickr (Thu, 23 Mar 2017 17:15:27 GMT):
I'm not finding _easily_ where as one wanting to contribute to setup the fabric and fabric_ca so I can help develop ... development env via vagrant

nickgaski (Thu, 23 Mar 2017 17:18:33 GMT):
@rickr - http://hyperledger-fabric.readthedocs.io/en/latest/dev-setup/devenv.html

rickr (Thu, 23 Mar 2017 17:21:46 GMT):
nice but the link there for build the fabric is a sorry page does not exist

nickgaski (Thu, 23 Mar 2017 17:31:38 GMT):
@rickr - easy fix. will take care of it

rickr (Thu, 23 Mar 2017 17:33:02 GMT):
thx -- can you tell me when it's done ... Maybe you can also address the "Contributing the link there is just a 404" in the readme.md ?

rickr (Thu, 23 Mar 2017 17:33:27 GMT):
I'm guessing it should point to the first link

ersudiplama (Thu, 23 Mar 2017 18:25:22 GMT):
Hi I worked with http://hyperledger-fabric.readthedocs.io/en/latest/asset_setup.html documentation and I have questions as I tried some test and it show that the image which is being in this documentation is older version of V1. As the images dont support install and instantiate chaincode instruction. And in my few test case with the docker image provided that document shows that the global state is inconsistent. So could anybody share or update the steps in the hyperledger documentation which work with current version of V1 docker image.

ersudiplama (Thu, 23 Mar 2017 18:26:12 GMT):
If someone need the steps and operation performed on test, I can share with anyone who need it.

ersudiplama (Thu, 23 Mar 2017 18:27:35 GMT):
I hope that have been addressed with the new version of V1 so Could anyone update the documentation on above link that would be great help so I can work or test out more cases.

ersudiplama (Thu, 23 Mar 2017 18:28:25 GMT):
Thank you in advance ....:relaxed:

markparz (Thu, 23 Mar 2017 19:45:48 GMT):
Hi @ersudiplama we are working a patch set right now for the new instructions using the docker images.. however you can use the e2e flow off this page for now... we are waiting for the patchset to be merged so set up a staging site for doc http://hyperledger-fabric.readthedocs.io/en/latest/learn_chaincode.html

markparz (Thu, 23 Mar 2017 19:45:48 GMT):
Hi @ersudiplama we are working a patch set right now for the new instructions using the docker images.. however you can use the e2e flow off this page for now... we are waiting for the patchset to be merged so set up a staging site for doc http://fabric-rtd.readthedocs.io/en/latest/end-to-end.html

markparz (Thu, 23 Mar 2017 19:47:24 GMT):
Here's the priority list I see that we need to tackle

markparz (Thu, 23 Mar 2017 19:47:26 GMT):
fixed e2e - Nick is on it, and patch set will be in today. There were some issues that were hell to get through, missing files, etc. (You can ask Bobbie) e2e moved up to replace the getting started - Will be in today Chaincode Development Chaincode migration Demo page FAQ We have several things that are waiting to be merged for awhile as well: Gossip Testing TOC work and a couple of others.

markparz (Thu, 23 Mar 2017 19:47:26 GMT):
fixed e2e - Nick is on it, and patch set will be in today. e2e moved up to replace the getting started - Will be in today Chaincode Development Chaincode migration Demo page FAQ We have several things that are waiting to be merged for awhile as well: Gossip Testing TOC work and a couple of others.

markparz (Thu, 23 Mar 2017 19:47:55 GMT):
if anyone sees anything missing let me know... and we should open corresponding Jira items

ersudiplama (Thu, 23 Mar 2017 19:49:02 GMT):
@markparz Thanks for the update..

markparz (Thu, 23 Mar 2017 19:49:39 GMT):
Let me know if you see anything else missing... or things you'd like to see

rrader (Sun, 26 Mar 2017 14:48:44 GMT):
Is there a way to disable reading from Hyperledger for a period of time?

rrader (Sun, 26 Mar 2017 14:48:54 GMT):
I need this to allow only to write in hyperledger for a period of time, after this to allow only reading from hyperledger.

lehors (Mon, 27 Mar 2017 15:54:25 GMT):
@rrader I assume when you say "hyperledger" you really mean "hyperledger fabric"

lehors (Mon, 27 Mar 2017 15:54:36 GMT):
there are several frameworks so beware

lehors (Mon, 27 Mar 2017 15:55:06 GMT):
I don't know what level of control you want but you could handle this in your chaincode

lehors (Mon, 27 Mar 2017 15:56:04 GMT):
you will need to maintain a state that tells you whether you are in readonly mode or writeonly mode

lehors (Mon, 27 Mar 2017 15:56:34 GMT):
you can then switch between the two by invoking your chaincode

lehors (Mon, 27 Mar 2017 15:57:24 GMT):
but this may not be what you want, you need to be more specific

jeffgarratt (Mon, 27 Mar 2017 21:46:15 GMT):
@ersudiplama think it is libtools is required

ersudiplama (Tue, 28 Mar 2017 15:14:36 GMT):
Hello Can anyone let me know how to run the chaincode test as I see sample of chaincode_test file inside fabric/examples/chaincode/go/chaincode_example02. Thank you in advance.

AdnanC (Tue, 28 Mar 2017 15:39:48 GMT):
Hi @ersudiplama please see `fabroc/examples/e2e_cli/end-to-end.rxt` for direction on how to do that. And the #fabric-questions channel is more suitable for these questions.

ersudiplama (Tue, 28 Mar 2017 15:41:45 GMT):
I have place same question on #fabric-questions but didnt hear back anything so i posted here

mrkiouak (Fri, 31 Mar 2017 13:16:34 GMT):
nice job on the getting started page!

cbf (Sat, 01 Apr 2017 19:43:38 GMT):
@nickgaski @rameshthoomu the v0.6 version of the docs is broken. I suspect it is because we changed to RST. We need to fix that.

cbf (Sat, 01 Apr 2017 19:43:56 GMT):
http://hyperledger-fabric.readthedocs.io/en/v0.6/

cbf (Sat, 01 Apr 2017 19:44:34 GMT):
also, the index page is not in the TOC. That seems odd to me.

cbf (Sat, 01 Apr 2017 19:44:54 GMT):
http://hyperledger-fabric.readthedocs.io/en/latest/index.html

bmos299 (Mon, 03 Apr 2017 13:20:11 GMT):
@cbf @nickgaski @rameshthoomu I suspect the easiest fix may be to convert .6 to Sphinx?

cbf (Mon, 03 Apr 2017 13:43:26 GMT):
yes, or create a separate RTD project for v0.6

mastersingh24 (Sat, 08 Apr 2017 11:48:51 GMT):
supposedly RTD supports both at the same time?

jojocheung (Mon, 10 Apr 2017 08:05:07 GMT):
Install chaincode with the SDK locally

mastersingh24 (Mon, 10 Apr 2017 18:37:45 GMT):
@nickgaski @bmos299 - did anyone ever successfully try the getting started steps on Windows 7?

swettdj (Tue, 11 Apr 2017 08:37:43 GMT):
Hi, I'm a newbie in hyperledger tecnology and I'm looking for some fabric 1.0 technical documentation. Could anyone help me?

smallant (Tue, 11 Apr 2017 08:38:34 GMT):
@swettdj http://hyperledger-fabric.readthedocs.io/en/latest/getting_started.html

nickgaski (Tue, 11 Apr 2017 12:50:19 GMT):
@mastersingh24 - it will work with vagrant if that's any consolation

mastersingh24 (Tue, 11 Apr 2017 13:20:23 GMT):
@nickgaski - well not really since it's not clearly documented that it won't work on Windows directly with Docker :(

mastersingh24 (Tue, 11 Apr 2017 13:20:29 GMT):
but no worries - I am on the case

swettdj (Tue, 11 Apr 2017 15:02:25 GMT):
Sorry again, some documentation on fabric SDK 1.0?

achraf17 (Wed, 12 Apr 2017 10:18:33 GMT):
@here Hello I'm trying to run the marbles example on the fabric v1.0 in my local machine but i can't find any documentation how to run your local network fabric. Is there any?

SyneBlockChainTeam (Wed, 12 Apr 2017 13:05:15 GMT):
Hi, Please let us know if there is some discrepancy in the "What happened behind the scenes" section on "chat.hyperledger.org/channel/fabric-ledger" page and "docker-compose.yaml" file ? As per chat.hyperledger.org/channel/fabric-ledger" page :- ----------------------------------------------------------------------- we have a channel consisting of four peers, and two organizations. PEER0 and PEER3 belong to Org0; PEER1 and PEER2 belong to Org1 Recall that these relationships are defined in the configtx.yaml As per "docker-compose.yaml" file :- ----------------------------------------------------------------------- peer0: environment: - CORE_PEER_LOCALMSPID=Org0MSP peer1: environment: - CORE_PEER_LOCALMSPID=Org0MSP peer2: environment: - CORE_PEER_LOCALMSPID=Org1MSP peer3: environment: - CORE_PEER_LOCALMSPID=Org1MSP >>> Differences between both sources, we noticed are as below :- "chat.hyperledger.org/channel/fabric-ledger" > PEER0 and PEER3 belong to Org0; PEER1 and PEER2 belong to Org1 "docker-compose.yaml" > PEER0 and PEER1 belong to Org0; PEER2 and PEER3 belong to Org1 Thanks

SyneBlockChainTeam (Wed, 12 Apr 2017 13:05:15 GMT):
Hi, Please let us know if there is some discrepancy in the "What happened behind the scenes" section on "chat.hyperledger.org/channel/fabric-ledger" page and "docker-compose.yaml" file ? As per chat.hyperledger.org/channel/fabric-ledger" page :- ----------------------------------------------------------------------- we have a channel consisting of four peers, and two organizations. PEER0 and PEER3 belong to Org0; PEER1 and PEER2 belong to Org1 Recall that these relationships are defined in the configtx.yaml As per "docker-compose.yaml" file :- ----------------------------------------------------------------------- peer0: environment: - CORE_PEER_LOCALMSPID=Org0MSP peer1: environment: - CORE_PEER_LOCALMSPID=Org0MSP peer2: environment: - CORE_PEER_LOCALMSPID=Org1MSP peer3: environment: - CORE_PEER_LOCALMSPID=Org1MSP We have noticed below Differences between both sources :- ------------------------------------------------------------------------- "chat.hyperledger.org/channel/fabric-ledger" > PEER0 and PEER3 belong to Org0; PEER1 and PEER2 belong to Org1 "docker-compose.yaml" > PEER0 and PEER1 belong to Org0; PEER2 and PEER3 belong to Org1 Thanks

nickgaski (Wed, 12 Apr 2017 14:52:08 GMT):
@SyneBlockChainTeam - let me confirm the MSPs. Will make appropriate updates

yhelal (Wed, 12 Apr 2017 15:19:04 GMT):
Hi all, i have a question about the right to be forgotten it is possible to deal with it with hyperldger fabric ?

nickgaski (Wed, 12 Apr 2017 16:41:51 GMT):
@here - for those interested there is a preliminary draft of documentation to run the marbles application. It currently functions against the v1 alpha images. http://fabric-rtd.readthedocs.io/en/latest/marbles.html Have a go if you're so inclined.

MikeMayori (Thu, 13 Apr 2017 16:08:55 GMT):
looking to find out api documentation for fabric?? ex: 0.0.0.0:7050/chain/block/0

MikeMayori (Thu, 13 Apr 2017 16:08:55 GMT):
looking to find out api documentation for fabric?? ex: 0.0.0.0:7050/chain/block/0 ------- version Fabric 1

MikeMayori (Thu, 13 Apr 2017 16:08:55 GMT):
looking to find out the api documentation for fabric?? ex: 0.0.0.0:7050/chain/block/0 ------- version Fabric 1

cbf (Thu, 13 Apr 2017 18:16:17 GMT):
@MikeMayori all interactions with peer are gRPC

cbf (Thu, 13 Apr 2017 18:17:02 GMT):
the various SDKs are the means of interacting

MikeMayori (Thu, 13 Apr 2017 18:17:59 GMT):
Thanks for answering, any documentation to see how to use the equivalents..??

cbf (Thu, 13 Apr 2017 18:20:49 GMT):
SDK docs here http://fabric-sdk-node.readthedocs.io/en/master/

MikeMayori (Thu, 13 Apr 2017 18:23:09 GMT):
Is is not updated , links are missing and do not have any description about calls and data response

nickgaski (Thu, 13 Apr 2017 23:53:03 GMT):
@MikeMayori - use `gulp doc` to build the documentation on the APIs classes and various methods

mastersingh24 (Sat, 15 Apr 2017 10:15:20 GMT):
@MikeMayori - we have also published the alpha docs for fabric-client / fabric-ca-client here: https://fabric-sdk-node.github.io/ (we are waiting to figure out the "official location" for these)

weeds (Mon, 17 Apr 2017 20:20:11 GMT):
Nick and I are discussing with Gari some of our documentation and where it needs help and maybe we get input at the Hackfest. If you think about it, we need write an chaincode... application, create a channel, join a channel, install/instnatiate.. and write to different ledgers. We should then explain basics of MSP relation to all of this. We need a good javascript program apart from this end to end cli thing we have. If we have that? any scripts we have should become a true official nodejs.sdk sample, so that get clone is not required... Is this the right direction? We have all these pieces, but the flow is not good in the documentation today which is confusing people.

weeds (Mon, 17 Apr 2017 20:22:52 GMT):
We really need to have the release artifact-

tkuhrt (Tue, 18 Apr 2017 00:45:21 GMT):
I notice that the documentation source still contains .md; whereas, the documents seem to have been converted to .rst. I was going to go through and make the change, but wanted to be sure that I should be changing the .md links to point to the .rst files.

nickgaski (Tue, 18 Apr 2017 13:44:14 GMT):
@tkuhrt - you are correct. we still need to convert a few files in the library to .rst and update the links accordingly. Please attach any commits to FAB 3201. Thanks for the offer to help! And I'm happy to comb through with you

jojocheung (Wed, 19 Apr 2017 07:07:53 GMT):
Could we refrain from using acronyms? It's really a struggle for a beginner like me figuring out what's fcw/cb/etc.

jojocheung (Wed, 19 Apr 2017 07:10:12 GMT):
FYI fcw - fabric chaincode wrangler; cb - call back; I only know them after scratching my head off.

tkuhrt (Wed, 19 Apr 2017 16:54:58 GMT):
@nickgaski : I have put together a patch file for moving .md to .rst in the docs directory (https://gist.github.com/tkuhrt/de72dfde5f4970c633b2503fbdf5be85). Can you help me understand the best way to test or verify these changes before I attempt to work through the process of committing them.

nickgaski (Wed, 19 Apr 2017 17:58:27 GMT):
hi @tkuhrt - the best way to test/verify would be to create yourself an instance of read the docs from your personal github repo. It will compile all of the documentation with the same layout and incorporate your changes. That said, there are a handful of issues I noticed with your preliminary PS.

nickgaski (Wed, 19 Apr 2017 17:59:07 GMT):
I used a link checking tool and found 65 broken links in our docs!!!

tkuhrt (Wed, 19 Apr 2017 17:59:46 GMT):
Nick, teach me...I want to learn how to build the docs and run this link checking tool that you speak of.

tkuhrt (Wed, 19 Apr 2017 18:00:09 GMT):
And happy for any advise on moving this forward.

nickgaski (Wed, 19 Apr 2017 18:00:42 GMT):
ok lets get you an instance of read the docs first. Let me direct message you

ersudiplama (Thu, 20 Apr 2017 19:32:26 GMT):
Hi every one, I was am trying to follow the steps provided in hyperledger getting started for V 1 and I got the following output as specified in document after running the ./network_setup.sh up

ersudiplama (Thu, 20 Apr 2017 19:34:13 GMT):
But after this cli is exited after this execution

ersudiplama (Thu, 20 Apr 2017 19:36:07 GMT):
Is there any steps to run and demo custom chaincode through cli so we can test the node js application for interacting with custom blockchain network

ersudiplama (Thu, 20 Apr 2017 19:38:06 GMT):
Do we have any documentation for deploying the custom chaincode to V1? As I am not being able to access cli after above steps

nickgaski (Thu, 20 Apr 2017 19:41:14 GMT):
hey @ersudiplama if you'd like you can go into your docker-compose.yaml and throw a sleep flag on the cli container

ersudiplama (Thu, 20 Apr 2017 19:45:49 GMT):
@nickgaski thank you, i will and let you know

ersudiplama (Thu, 20 Apr 2017 20:30:26 GMT):
Hi @nickgaski, i tired it and cli is working. But when I try to create new channel using previous tutorial and it didnt work. Could any one provide steps to create custom channel and deploy custom chaincode to the custom channel as I am trying to build my own application using the V1 hyperledger.

nickgaski (Thu, 20 Apr 2017 20:32:56 GMT):
yea if you scroll down towards the latter half of the getting started, we expose all of the CLI commands for create and join

nickgaski (Thu, 20 Apr 2017 20:33:16 GMT):
you can use the same channel.tx artifact but just give the channel a unique name

ersudiplama (Thu, 20 Apr 2017 21:14:47 GMT):
@nickgaski thanks i will try and give my feedback if i have some problems

LoupTheron (Fri, 21 Apr 2017 09:54:33 GMT):
It would be nice to have a detailled doc on protocols used between components, as asked by the security team of enterprises for an integration in the IS

nickgaski (Fri, 21 Apr 2017 13:49:21 GMT):
@LoupTheron - can you elaborate a little more on specifically what you're after.. The txflow document gives a fairly nice outline of the information flow beginning at client and ending at commitment. In terms of protocol, the fabric communication layer is protobuffers over gRPC.

LoupTheron (Fri, 21 Apr 2017 14:08:19 GMT):
@nickgaski Sure, so: What protocols are used to get the TCert, ECert between the peers and the CA ? There is also Kafka messaging along the protobuf right ? Can you give me more details on it ?

LoupTheron (Fri, 21 Apr 2017 14:10:43 GMT):
Also, there a revocation process of the certificates ? How is managed the CRL ?

LoupTheron (Fri, 21 Apr 2017 14:23:20 GMT):
Another question if I may, when will be the beta launched ? As I can see it as be delayed, we are still in the alpha version

bkvellanki (Fri, 21 Apr 2017 15:30:52 GMT):
@here Lets say an org want to need to migrate from one version of fabric (alpha) to another (prod or beta). Is there any document that explains all the items to be backed up.. that we need to backed up..I can definitely see smart contracts, DB, tx, orderer, block..I trying to see if there is any atrifact that explains a smooth transition

bkvellanki (Fri, 21 Apr 2017 16:31:21 GMT):
https://jira.hyperledger.org/browse/FAB-3308 - Upgrade (Patch or Major release) process documentation.

markparz (Sun, 23 Apr 2017 15:00:36 GMT):
@bkvellanki Good thought ... nothing yet, there is potential that it might be a complete network restart until we get to an official v1 release... I don't see anything yet that would require it though

mrkiouak (Mon, 24 Apr 2017 21:26:28 GMT):
are there any WiP or plans for a https://github.com/hyperledger/fabric/blob/1c982e87f416c44a8556395c3ff774e233c6c422/docs/protocol-spec.md document that will reflect version 1 architecture?

passkit (Thu, 27 Apr 2017 07:26:19 GMT):
@markparz is there any insight as to when v1 may come? The delta between the current head and v1-0-0alpha is already huge and breaking changes are introduced almost daily. It may not be long until commercial pressures force us to look elsewhere for a stable solution.

lehors (Thu, 27 Apr 2017 11:04:44 GMT):
@passkit, the current target is June but meeting that deadline is not the priority, we will only release v1 if it's solid enough

lehors (Thu, 27 Apr 2017 11:05:08 GMT):
in the meantime you can expect several other intermediate releases - beta

lehors (Thu, 27 Apr 2017 11:05:57 GMT):
agreement among the maintainers is that no new code should be submitted

lehors (Thu, 27 Apr 2017 11:06:22 GMT):
once the CRs already submitted have been merged in, only bug fixes will be accepted

lehors (Thu, 27 Apr 2017 13:18:54 GMT):
@nickgaski @tkuhrt I'm interested in fixing the broken links in the docs if that helps

tkuhrt (Thu, 27 Apr 2017 13:21:57 GMT):
@lehors happy to have some help. Issue number FAB-3201.

lehors (Thu, 27 Apr 2017 13:22:41 GMT):
yeah, I saw it, but it's assigned to you so I didn't want to hijack it :)

lehors (Thu, 27 Apr 2017 13:28:28 GMT):
otherwise I'm wondering about all these absolute links all over the doc, I would think we want to use relative links as much as possible

tkuhrt (Thu, 27 Apr 2017 13:29:10 GMT):
Hijack away. :) Happy to continue working on it too. Just need to make sure we don't duplicate. I was wondering about creating tasks as a way to separate work.

lehors (Thu, 27 Apr 2017 13:30:46 GMT):
for full disclosure, I was editor of the html spec so I'm pretty anal about html docs :)

tkuhrt (Thu, 27 Apr 2017 13:30:48 GMT):
The absolute paths to source code is definitely an issue. Also, links to .txt files in the docs directory don't really work. If you have a solve for moving to relative links, let me know.

lehors (Thu, 27 Apr 2017 13:31:36 GMT):
our docs aren't valid html and it'd be nice to fix that at some point but I realize that this isn't for today

lehors (Thu, 27 Apr 2017 13:31:51 GMT):
so I'll settle on fixing what's outrageously broken for now

lehors (Thu, 27 Apr 2017 13:44:12 GMT):
the problem is that I don't think it's possible to use relative links that will work both on readthedocs and github

lehors (Thu, 27 Apr 2017 13:44:59 GMT):
the only way to make the links in github work is to have absolute links to readthedocs

lehors (Thu, 27 Apr 2017 13:45:57 GMT):
that's because the links have to point to the html file and in github we only have the rst file

lehors (Thu, 27 Apr 2017 13:47:35 GMT):
and that means every time we move to a new version which involves some documentation change impacting filenames we break the older doc

lehors (Thu, 27 Apr 2017 13:50:51 GMT):
and by the way of full disclosure: I have an aversion for things like for blahblah look _here_

lehors (Thu, 27 Apr 2017 13:51:16 GMT):
having "here" as the anchor for a link is a BIG NO NO in my book

nickgaski (Thu, 27 Apr 2017 13:51:53 GMT):
let's get every relative link that we can and then deal with the absolute paths once we clean up this initial portion. Arnaud you can easily change those titles to something more intuitive than "here"

nickgaski (Thu, 27 Apr 2017 13:52:25 GMT):
fwiw this would have been a nice candidate for "good first bug"

lehors (Thu, 27 Apr 2017 13:54:27 GMT):
to the risk of sounding like an old fart I even posted a blog on that topic several years ago: https://lehors.wordpress.com/2009/01/29/linking-the-proper-way/

lehors (Thu, 27 Apr 2017 13:55:53 GMT):
@nickgaski what do you mean by "let's get every relative link that we can" exactly?

lehors (Thu, 27 Apr 2017 13:56:28 GMT):
if we put a link a la in the rst file it will be broken when rst file is rendered on github

lehors (Thu, 27 Apr 2017 13:56:49 GMT):
so, I would think we're stuck with having an absolute link to readthedocs in this case

lehors (Thu, 27 Apr 2017 13:57:21 GMT):
so anyone clicking on a link while browsing an rst file on github will land on the readthedocs html file

nickgaski (Thu, 27 Apr 2017 13:58:05 GMT):
that makes sense Arnaud. I just meant that we can solve a lot of these by changing the tagging and removing the ``.md`` suffix on a lot of these paths

lehors (Thu, 27 Apr 2017 13:58:50 GMT):
I was hoping we could do away with foo instead of foo.html but apparently readthedocs doesn't automatically redirect

lehors (Thu, 27 Apr 2017 14:16:16 GMT):
@nickgaski does links to foo.rst get changed foo.html as part of sphinx-build?

lehors (Thu, 27 Apr 2017 14:16:16 GMT):
@nickgaski does links to foo.rst get changed to foo.html as part of sphinx-build?

lehors (Thu, 27 Apr 2017 14:16:16 GMT):
@nickgaski do links to foo.rst get changed to foo.html as part of sphinx-build?

lehors (Thu, 27 Apr 2017 14:25:41 GMT):
so then we should be good using links a la , they will work in github and get translated to something that works on readthedocs

lehors (Thu, 27 Apr 2017 14:25:59 GMT):
I actually see now that we already have some links like that

lehors (Thu, 27 Apr 2017 14:34:39 GMT):
unfortunately that's not quite the case apparently

lehors (Thu, 27 Apr 2017 14:36:19 GMT):
all the links to rst files in CONTRIBUTING are left as such and therefore are broken on readthedocs

lehors (Thu, 27 Apr 2017 14:36:45 GMT):
this is apparent in http://hyperledger-fabric.readthedocs.io/en/latest/CONTRIBUTING.html#working-with-a-local-clone-and-gerrit

lehors (Thu, 27 Apr 2017 14:47:42 GMT):
and more troubling sphinx linkcheck doesn't report them :(

lehors (Thu, 27 Apr 2017 18:11:15 GMT):
I would also like to know where how the doc gets built and published to readthedocs

lehors (Thu, 27 Apr 2017 18:11:15 GMT):
I would also like to know where how the doc gets built and published to readthedocs is documented

lehors (Thu, 27 Apr 2017 18:11:45 GMT):
I imagine it's part of the ci process but the Makefile gives no indication as to what exact command is run

lehors (Thu, 27 Apr 2017 18:12:10 GMT):
the help target doesn't really help because it gives all possible options and not the one that is actually used

lehors (Thu, 27 Apr 2017 18:17:10 GMT):
@nickgaski could you type it in here, please? otherwise the next person will ask again

lehors (Thu, 27 Apr 2017 18:18:12 GMT):
I'm happy to take what you type, clean it up if needed, and stick it somewhere into the source so the next person won't have to ask :)

lehors (Thu, 27 Apr 2017 18:18:55 GMT):
or if you prefer we can talk and I'll do the typing

nickgaski (Thu, 27 Apr 2017 18:21:57 GMT):
no I can do that, it's no problem. Does the "contributing" doc make the most sense?

nickgaski (Thu, 27 Apr 2017 18:22:55 GMT):
we can figure out where to put it in the source... Now for the docs

lehors (Thu, 27 Apr 2017 18:23:51 GMT):
as far as I'm concerned I think a README in the docs directory, next to the Makefile would do

nickgaski (Thu, 27 Apr 2017 18:24:02 GMT):
so if you wanted to add something into the Table of Contents you would simply modify that file in the same manner as all of the other topics. It's very self-explanatory once you look at it

lehors (Thu, 27 Apr 2017 18:24:40 GMT):
what make command gets run for the build?

nickgaski (Thu, 27 Apr 2017 18:24:59 GMT):
it has a hook for any new content that goes into docs/source

nickgaski (Thu, 27 Apr 2017 18:25:31 GMT):
you can easily build your own staging repo, I expect that's what most folks would like to do

nickgaski (Thu, 27 Apr 2017 18:26:20 GMT):
from your fork, go to `settings` in the upper right portion of the screen

nickgaski (Thu, 27 Apr 2017 18:28:16 GMT):
one of the first prompts will say link to github. Elect this

nickgaski (Thu, 27 Apr 2017 18:28:40 GMT):
navigate through the options to your fork (e.g. lehors/fabric)

nickgaski (Thu, 27 Apr 2017 18:29:20 GMT):
it will ask for a name for this project. Choose something intuitive. Your name will preface the URL. So for example, nickgaski.readthedocs.io/en/latest

nickgaski (Thu, 27 Apr 2017 18:29:47 GMT):
now anytime you add code (doc) to your fork, this URL will automatically get updated with your changes.

lehors (Thu, 27 Apr 2017 18:29:51 GMT):
oh, I see... so when you wrote "it has a hook for any new content that goes into docs/source", "it" meant readthedocs, right?

nickgaski (Thu, 27 Apr 2017 18:30:05 GMT):
If you like the content and formatting, then push to gerrit. Yes that is what I meant

lehors (Thu, 27 Apr 2017 18:30:47 GMT):
do you know how it does the build though?

nickgaski (Thu, 27 Apr 2017 18:32:05 GMT):
for the mechanics, I would ask @rameshthoomu . He's the CI savant

rameshthoomu (Thu, 27 Apr 2017 19:13:29 GMT):
@lehors I will prepare readme how RTD build process go through .. I have one prepared for `mkdcos` but the `sphinx` setup little different..

rameshthoomu (Thu, 27 Apr 2017 19:14:18 GMT):
`sphinx` supports `github`.. so when you submit your document changes to `github`, RTD (readthedocs) webhook pick that change and build it for you..

rameshthoomu (Thu, 27 Apr 2017 19:36:55 GMT):
@nickgaski @lehors here are the quick steps to achieve this in local machine without depending on RTD (be in fabric directory) ``` 1) sudo pip install Sphinx 2) sudo pip install sphinx_rtd_theme 3) cd fabric/docs/source/build (Be in this directory.. Makefile sits in this) 4) make html 5) sudo apt-get install apache2 (If don't want to use RTD for your experimental stuff and stick to apache webserver) 6) sudo cp -r * /var/www/html/ 7) open html files with `IP/gossip.html` (ex) ```

rameshthoomu (Thu, 27 Apr 2017 19:36:55 GMT):
@nickgaski @lehors here are the quick steps to achieve this in local machine without depending on RTD (be in fabric directory) ``` 1) sudo pip install Sphinx 2) sudo pip install sphinx_rtd_theme 3) cd fabric/docs (Be in this directory.. Makefile sits in this) 4) make html 5) sudo apt-get install apache2 (If don't want to use RTD for your experimental stuff and stick to apache webserver) 6) sudo cp -r * /var/www/html/ 7) open html files with `IP/gossip.html` (ex) ```

rameshthoomu (Thu, 27 Apr 2017 19:36:55 GMT):
@nickgaski @lehors here are the quick steps to achieve this in local machine without depending on RTD (be in fabric directory) ``` 1) sudo pip install Sphinx 2) sudo pip install sphinx_rtd_theme 3) cd fabric/docs (Be in this directory.. Makefile sits in this) 4) make html 5) sudo apt-get install apache2 (If don't want to use RTD for your experimental stuff and stick to apache webserver) 6) cd source/build/html 6) sudo cp -r * /var/www/html/ 7) open html files with `IP Address/gossip.html` (ex: 9.27.100.125/gossip.html) ```

lehors (Thu, 27 Apr 2017 19:44:09 GMT):
thanks @rameshthoomu !! that's exactly what I was looking for :)

lehors (Thu, 27 Apr 2017 19:44:49 GMT):
I'm glad to see I wasn't far actually :)

lehors (Thu, 27 Apr 2017 19:50:01 GMT):
one should really be able to browse the html locally, without going through an http server

lehors (Thu, 27 Apr 2017 19:50:33 GMT):
that's only true if we can have relative links though

lehors (Thu, 27 Apr 2017 20:10:51 GMT):
@nickgaski @tkuhrt when it comes to links to source file (.txt, .rst, etc.) we can either link to the file on github or on gerrit, which one should we take?

lehors (Thu, 27 Apr 2017 20:11:19 GMT):
I feel like gerrit is the only true source but it sucks for repository browsing

lehors (Thu, 27 Apr 2017 20:12:43 GMT):
so, I think we should use the gerrit one but I think I could be convinced to use github instead

tkuhrt (Thu, 27 Apr 2017 20:13:19 GMT):
For the .rst ones, you should be able to convert those to something like :doc:`descriptive text `. See https://gerrit.hyperledger.org/r/#/c/8325/2/docs/source/dev-setup/build.rst for an example. For the source files, I believe we have been linking to the github version.

tkuhrt (Thu, 27 Apr 2017 20:15:05 GMT):
At least not starting at gerrit.hyperledger.org and looking for a particular file.

lehors (Thu, 27 Apr 2017 20:15:20 GMT):
yeah, it's a pain to get there but there is a way...

lehors (Thu, 27 Apr 2017 20:15:34 GMT):
https://gerrit.hyperledger.org/r/gitweb?p=fabric.git;a=blob;f=docs/source/MAINTAINERS.rst;hb=HEAD

lehors (Thu, 27 Apr 2017 20:16:09 GMT):
you have to go to the top of the project and click on "tree"

lehors (Thu, 27 Apr 2017 20:16:18 GMT):
you get there: https://gerrit.hyperledger.org/r/gitweb?p=fabric.git;a=tree

lehors (Thu, 27 Apr 2017 20:16:55 GMT):
I read the piece about the links you're talking about, that would seem to be the better fix indeed

tkuhrt (Thu, 27 Apr 2017 20:19:30 GMT):
Not a fan of the gerrit links. For each one, I would need to go into gerrit to find it versus just looking at my source directory.

tkuhrt (Thu, 27 Apr 2017 20:19:49 GMT):
That makes it harder for a maintainer of the docs.

tkuhrt (Thu, 27 Apr 2017 20:20:50 GMT):
Now if it could find a way to make it truly relative, that would be ideal.

lehors (Thu, 27 Apr 2017 20:22:08 GMT):
there is at least one place where we actually want to link to the rst source file

lehors (Thu, 27 Apr 2017 20:22:34 GMT):
it's in the section on how to propose a new maintainer - which is done by submitting a change to the MAINTAINERS.rst file

lehors (Thu, 27 Apr 2017 20:22:45 GMT):
in this case we ought to link to the gerrit file

lehors (Thu, 27 Apr 2017 20:23:04 GMT):
because that's the one you want to modify, not the read-only mirrored github one

lehors (Thu, 27 Apr 2017 20:24:49 GMT):
otherwise, unfortunately github doesn't understand the :doc: syntax

lehors (Thu, 27 Apr 2017 20:25:33 GMT):
did you see this? https://github.com/hyperledger/fabric/blob/master/docs/source/dev-setup/build.rst

lehors (Thu, 27 Apr 2017 20:26:01 GMT):
I guess this may be something we have live with

lehors (Thu, 27 Apr 2017 20:26:01 GMT):
I guess this may be something we have to live with

lehors (Thu, 27 Apr 2017 21:03:17 GMT):
I've actually convinced myself that's the right thing to do...

nickgaski (Thu, 27 Apr 2017 21:03:33 GMT):
I am unequivocally against linking to gerrit. I don't understand why we would ever choose gerrit over github for display purposes?

lehors (Thu, 27 Apr 2017 21:04:11 GMT):
even when we point to the file one must submit a CR against?

lehors (Thu, 27 Apr 2017 21:05:21 GMT):
admittedly anyone at the point of proposing a new maintainer would know how to get to the actual source

nickgaski (Thu, 27 Apr 2017 21:05:33 GMT):
So here is my two cents. First, you can't edit the gerrit file directly, can you ? Secondly, we have the maintainers.rst building correctly in ReadTheDocs. Thirdly, what you just wrote

lehors (Thu, 27 Apr 2017 21:07:55 GMT):
I don't get the point about not editing the gerrit file I have to say but that's fine

nickgaski (Thu, 27 Apr 2017 21:08:40 GMT):
I guess my real point here is - if I ever want to read something, gerrit is the last place I want to read it from :)

lehors (Thu, 27 Apr 2017 21:09:28 GMT):
but this isn't about reading the file as much as pointing to it

lehors (Thu, 27 Apr 2017 21:10:13 GMT):
I'm talking about the section where we actually tell people they must submit a patch to the MAINTAINERS.rst file

lehors (Thu, 27 Apr 2017 21:10:43 GMT):
should we then point to the html file if it's just for display purposes?

nickgaski (Thu, 27 Apr 2017 21:11:56 GMT):
yes. Like you said, if anyone is going to nominate a maintainer then they will be able to navigate into docs/source and edit the rst file and then push

hshimo (Fri, 28 Apr 2017 06:34:15 GMT):
I followed this document, but it doesn't work. https://hyperledger-fabric.readthedocs.io/en/latest/getting_startedv2.html#getting-started >./../../$os_arch/bin/configtxgen -profile TwoOrgs -outputBlock orderer.block 2017-04-28 15:31:59.192 JST [common/configtx/tool] main -> INFO 001 Loading configuration 2017-04-28 15:31:59.193 JST [configtx/tool/localconfig] Load -> CRIT 002 Error reading configuration: Unsupported Config Type "" panic: Error reading configuration: Unsupported Config Type ""

hshimo (Fri, 28 Apr 2017 06:36:18 GMT):
env: * macOS 10.12.4 * go version go1.8.1 darwin/amd64

hshimo (Fri, 28 Apr 2017 06:36:18 GMT):
``` env: * macOS 10.12.4 * go version go1.8.1 darwin/amd64

hshimo (Fri, 28 Apr 2017 06:37:22 GMT):
It might be the cryptogen problem. ``` $ ./../../darwin-amd64/bin/cryptogen generate --config=./crypto-config.yaml org1.example.com 2017-04-28 15:27:49.165 JST [bccsp] GetDefault -> WARN 001 Before using BCCSP, please call InitFactories(). Falling back to bootBCCSP. 2017-04-28 15:27:49.190 JST [bccsp] GetDefault -> WARN 002 Before using BCCSP, please call InitFactories(). Falling back to bootBCCSP. 2017-04-28 15:27:49.193 JST [bccsp] GetDefault -> WARN 003 Before using BCCSP, please call InitFactories(). Falling back to bootBCCSP. 2017-04-28 15:27:49.197 JST [bccsp] GetDefault -> WARN 004 Before using BCCSP, please call InitFactories(). Falling back to bootBCCSP. 2017-04-28 15:27:49.201 JST [bccsp] GetDefault -> WARN 005 Before using BCCSP, please call InitFactories(). Falling back to bootBCCSP. org2.example.com ```

hshimo (Fri, 28 Apr 2017 06:37:22 GMT):
This link from https://wiki.hyperledger.org/projects/fabric.md is broken . http://hyperledger-fabric.readthedocs.io/en/latest/gettingstarted/

nickgaski (Fri, 28 Apr 2017 12:22:09 GMT):
@hshimo - you're seeing this error because the binary for configtxgen is looking for an unsupported config type. I suspect that you compiled the binaries yourself from the master branch at some point in time. At any rate, can you try the following. `network_setup.sh down` and then `network_setup.sh restart`. If that also fails, then we will need to truly start from scratch and whack your docker images.

pmcosta1 (Fri, 28 Apr 2017 15:54:51 GMT):
Hi @nickgaski I ran into the same situation as @hshimo ```network_setup.sh down``` and then ```network_setup.sh restart``` fails at the same point ```2017-04-28 16:49:43.100 WEST [common/configtx/tool] main -> INFO 001 Loading configuration 2017-04-28 16:49:43.100 WEST [configtx/tool/localconfig] Load -> CRIT 002 Error reading configuration: Unsupported Config Type "" panic: Error reading configuration: Unsupported Config Type "" ```

pmcosta1 (Fri, 28 Apr 2017 15:56:35 GMT):
@hshimo any progress with that situation?

hshimo (Fri, 28 Apr 2017 15:57:38 GMT):
Just hit ""export FABRIC_CFG_PATH=$PWD" instead of "export ORDERER_CFG_PATH=$PWD". Detail is https://github.com/hyperledger/fabric/pull/44

dklesev (Sat, 29 Apr 2017 19:18:55 GMT):
where can I find symbols used in the images like http://hyperledger-fabric.readthedocs.io/en/latest/txflow.html? thought to use it for my presentations

davidka1 (Sat, 29 Apr 2017 22:58:39 GMT):
not sure if this is where I post documentation errors, but in the "Getting Started" -> "Prerequisites and setup" -> "Curl the artifacts and binaries" section, the link to the release tar "https://logs.hyperledger.org/sandbox/vex-yul-hyp-jenkins-2/fabric-verify-x86_64_1/5/release.tar.gz" is broken

davidka1 (Sat, 29 Apr 2017 22:59:05 GMT):
` $ wget -c "https://logs.hyperledger.org/sandbox/vex-yul-hyp-jenkins-2/fabric-verify-x86_64_1/5/release.tar.gz" --2017-04-29 23:55:54-- https://logs.hyperledger.org/sandbox/vex-yul-hyp-jenkins-2/fabric-verify-x86_64_1/5/release.tar.gz Resolving logs.hyperledger.org (logs.hyperledger.org)... 199.19.212.106 Connecting to logs.hyperledger.org (logs.hyperledger.org)|199.19.212.106|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2017-04-29 23:55:55 ERROR 404: Not Found. `

davidka1 (Sat, 29 Apr 2017 22:59:05 GMT):
``` $ wget -c "https://logs.hyperledger.org/sandbox/vex-yul-hyp-jenkins-2/fabric-verify-x86_64_1/5/release.tar.gz" --2017-04-29 23:55:54-- https://logs.hyperledger.org/sandbox/vex-yul-hyp-jenkins-2/fabric-verify-x86_64_1/5/release.tar.gz Resolving logs.hyperledger.org (logs.hyperledger.org)... 199.19.212.106 Connecting to logs.hyperledger.org (logs.hyperledger.org)|199.19.212.106|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2017-04-29 23:55:55 ERROR 404: Not Found. ```

nickgaski (Sun, 30 Apr 2017 10:45:37 GMT):
@dklesev - check in the docs/source/images directory

nickgaski (Sun, 30 Apr 2017 10:47:00 GMT):
@rameshthoomu - please see above regarding the jenkins server. Perhaps it's down?

rameshthoomu (Sun, 30 Apr 2017 13:12:42 GMT):
@davidka1 @nickgaski yes I see the link is broken.. Will upload again and share the link here..

rameshthoomu (Sun, 30 Apr 2017 13:12:42 GMT):
@davidka1 @nickgaski yes the link is broken.. Will upload again and share the link here..

mrkiouak (Mon, 01 May 2017 16:12:19 GMT):
@rameshthoomu when will the link be corrected? I generally point colleagues to the getting started page as af irst step. It doesn't engender confidence when the public getting started is broken (apologies for the tone-- this isn't directed at you personally, just at the frequency of breaks like this).

nickgaski (Mon, 01 May 2017 16:19:46 GMT):
@mrkiouak - I wouldn't say that we are thrilled about this either. In the meantime, you can access all of the artifacts and binaries here - https://jenkins.hyperledger.org/sandbox/job/fabric-binaries-x86_64/3/

nickgaski (Mon, 01 May 2017 16:22:59 GMT):
@here - this is a comparable approach for Getting Started as well -https://github.com/hyperledger/fabric/blob/master/examples/e2e_cli/end-to-end.rst - It doesn't expose the cryptogen tool, however it does run against master images and new configuration protocols. No need to pull alpha images, simply do a `make docker` for this approach

rameshthoomu (Mon, 01 May 2017 16:23:38 GMT):
Nick will fix this in next 30 mins

tkuhrt (Mon, 01 May 2017 16:36:57 GMT):
Looking for the v1.0 equivalent for the Architecture of Fabric. I found this in master, but I am wondering if this has changed. I seem to recall this was the same in v0.6: https://github.com/hyperledger/fabric/blob/master/docs/source/images/refarch.png

mrkiouak (Mon, 01 May 2017 16:39:08 GMT):
@nickgaski thanks for the info nick, I appreciate it

nickgaski (Mon, 01 May 2017 18:42:17 GMT):
@here there is a CR in to fix the unfriendly URL provided in our Getting Started instructions. https://gerrit.hyperledger.org/r/#/c/8591/ You simply want to execute the following to retrieve the binaries and artifacts `curl -L https://logs.hyperledger.org/sandbox/vex-yul-hyp-jenkins-2/fabric-binaries/release.tar.gz -o release.tar.gz 2> /dev/null; tar -xvf release.tar.gz` - Cheers

nickgaski (Mon, 01 May 2017 21:20:18 GMT):
@tkuhrt - check out FAB-37. There is a HLF-Deep Dive pdf that has what you're after. https://jira.hyperledger.org/browse/FAB-37

zupan (Tue, 02 May 2017 10:21:50 GMT):
Is command `make couchdb` still needed in the http://hyperledger-fabric.readthedocs.io/en/latest/getting_startedv2.html#using-couchdb documentation?

foravneet (Tue, 02 May 2017 23:33:31 GMT):
Guys - I know there were some issue with getting started doc http://hyperledger-fabric.readthedocs.io/en/latest/getting_startedv2.html but stuck on create channel If I follow the instruction as given in the doc ```CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com CORE_PEER_LOCALMSPID="OrdererMSP" peer channel create -o orderer.example.com:7050 -c mychannel -f channel.tx``` then i get this error no such file or directory, err /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/signcerts But when i fix CORE_PEER_MSPCONFIGPATH to /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp (which seems to be the right path) then i get this error ```2017-05-02 23:18:41.904 UTC [logging] InitFromViper -> DEBU 001 Setting default logging level to DEBUG for command 'channel' 2017-05-02 23:18:41.905 UTC [msp] GetLocalMSP -> DEBU 002 Returning existing local MSP 2017-05-02 23:18:41.905 UTC [msp] GetDefaultSigningIdentity -> DEBU 003 Obtaining default signing identity Error connecting: rpc error: code = 14 desc = grpc: RPC failed fast due to transport failure Error: rpc error: code = 14 desc = grpc: RPC failed fast due to transport failure``` Any clues ? Stuck from long time. Have asked this question in #fabric channel as well as don't know the right place. Thanks.

tmath (Wed, 03 May 2017 00:31:58 GMT):
I'm getting similar errors on starting the network

tmath (Wed, 03 May 2017 00:33:28 GMT):
it seems that the script is expecting the code to be in /opt/gopath/ but there's nothing in the doc about installing it there

MadhavAchar (Wed, 03 May 2017 07:30:27 GMT):
@foravneet @tmath I had the exact same problem yesterday. For some reason all was fixed on my local machine when I used the release in the fabric-binaries folder as opposed to the one in fabric-binaries-x86_64. My development machine is a Mac. I believe we also switched from go 1.8 to 1.7.5. I'm not sure if that also helped in some way.

nickgaski (Wed, 03 May 2017 14:40:51 GMT):
@foravneet @tmath - Let me have a look. We'll get you sorted

MrBuggySan (Wed, 03 May 2017 17:25:33 GMT):
@pmcosta1 have you solved the problem with ``` `2017-05-03 11:22:23.749 MDT [common/configtx/tool] main -> INFO 001 Loading configuration 2017-05-03 11:22:23.749 MDT [configtx/tool/localconfig] Load -> CRIT 002 Error reading configuration: Unsupported Config Type "" panic: Error reading configuration: Unsupported Config Type "" ` ```

MrBuggySan (Wed, 03 May 2017 17:26:15 GMT):
@pmcosta1 have you solved the problem with ``` 2017-05-03 11:22:23.749 MDT [common/configtx/tool] main -> INFO 001 Loading configuration 2017-05-03 11:22:23.749 MDT [configtx/tool/localconfig] Load -> CRIT 002 Error reading configuration: Unsupported Config Type "" panic: Error reading configuration: Unsupported Config Type "" ```

MrBuggySan (Wed, 03 May 2017 17:27:36 GMT):
@pmcosta1 I also tried doing 'network_setup.sh down' , 'network_setup.sh restart' & 'export FABRIC_CFG_PATH=$PWD'

MrBuggySan (Wed, 03 May 2017 17:28:28 GMT):
it does not seem to work still for me. from the network_setup.sh I get `Channel creation failed`

richard.holzeis (Wed, 03 May 2017 18:59:20 GMT):
@nickgaski please have me updated as well if you have a solution for the rpc error: code 14. thx

nickgaski (Wed, 03 May 2017 19:00:40 GMT):
can you share a little more @richard.holzeis

tmath (Wed, 03 May 2017 19:14:16 GMT):
it seems getting_startedv2 doc has been removed and replaced with the old one now

tmath (Wed, 03 May 2017 19:15:50 GMT):
so was there some problem with the v2 doc?

tmath (Wed, 03 May 2017 19:24:26 GMT):
@MadhavAchar I resolved my issue - I edited the wrong yaml file when commenting out the line

richard.holzeis (Thu, 04 May 2017 06:13:50 GMT):
@nickgaski it looks like the same issue as as described by @foravneet. I've followed the instructions on http://fabric-rtd.readthedocs.io/en/latest/getting_started.html and when I try to setup the network with `./network_setup.sh up mychannel` I get the following error ```2017-05-01 19:40:15.798 UTC [msp] getMspConfig -> INFO 001 intermidiate certs folder not found at [/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peer/peer0/localMspConfig/intermediatecerts]. Skipping.: [stat /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peer/peer0/localMspConfig/intermediatecerts: no such file or directory] 2017-05-01 19:40:15.799 UTC [msp] getMspConfig -> INFO 002 crls folder not found at [/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peer/peer0/localMspConfig/intermediatecerts]. Skipping.: [stat /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peer/peer0/localMspConfig/crls: no such file or directory] 2017-05-01 19:40:15.799 UTC [msp] getMspConfig -> INFO 003 MSP configuration file not found at [/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peer/peer0/localMspConfig/config.yaml]: [stat /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peer/peer0/localMspConfig/config.yaml: no such file or directory] 2017-05-01 19:40:15.820 UTC [msp] GetLocalMSP -> DEBU 004 Returning existing local MSP 2017-05-01 19:40:15.820 UTC [msp] GetDefaultSigningIdentity -> DEBU 005 Obtaining default signing identity Error connecting: rpc error: code = 14 desc = grpc: RPC failed fast due to transport failure Error: rpc error: code = 14 desc = grpc: RPC failed fast due to transport failure```

lehors (Thu, 04 May 2017 13:03:16 GMT):
for what it's worth, I just tried going through the getting started doc and it doesn't work for me either

lehors (Thu, 04 May 2017 13:06:30 GMT):
with the very unhelpful error message: Error: Got unexpected status: BAD_REQUEST

lehors (Thu, 04 May 2017 13:12:16 GMT):
after several unsuccessful attempts, it just went through this time

lehors (Thu, 04 May 2017 13:26:09 GMT):
on the other hand I had no problem with the end to end doc using master

lehors (Thu, 04 May 2017 13:26:29 GMT):
so that's probably people's best option at this point

nickgaski (Thu, 04 May 2017 20:35:26 GMT):
@lehors - out of curiosity, can you do a `./network_setup.sh down` and then a `./network_setup.sh restart` and see if the all in one script will work for you

zupan (Fri, 05 May 2017 07:39:31 GMT):
@here Hello, I'm trying to deploy a custom chaincode on hyperledger and when writing it I followed http://hyperledger-fabric.readthedocs.io/en/latest/Setup/JAVAChaincode.html documentation (I know it is old). My chaincode is really simple because is just slightly changed chaincode_example02. Installing process goes through without any problems, but when *instantiating* it i get ``` Error: Error endorsing chaincode: rpc error: code = 2 desc = Error starting container: The command '/bin/sh -c cd /root/chaincode/src && gradle -b build.grad le clean && gradle -b build.gradle build' returned a non-zero code: 1 ```

lehors (Fri, 05 May 2017 08:30:33 GMT):
hi @zupan, please, beware that this is not "hyperledger" which is the consortium, but "hyperledger fabric" you're talking about

lehors (Fri, 05 May 2017 08:30:48 GMT):
as to your question, I don't think there is anything more for now

lehors (Fri, 05 May 2017 08:31:27 GMT):
if you have questions I suggest you ask on the dedicated channel #fabric-java-chaincode

zupan (Fri, 05 May 2017 08:38:14 GMT):
Thank you @lehors for clarification. After posting here I found #fabric-java-chaincode channel and already posted problem there.

highway (Fri, 05 May 2017 13:54:35 GMT):
hello I just had a student class installing all hyperledger fabric 1.0 on their laptops and we found two problems that occured several times following the 'getting started guide'. First in the 'network_setup.sh' line 86 ... export ORDERER_CFG_PATH=$PWD seems to be wrong? It works by using export FABRIC_CFG_PATH=$PWD and then the step export ARCH_TAG=$(uname -m) did not work as expected, since the variable was not (always) avialable in the docker file it helped to write the variable value (ARCH_TAG=x86_64) in a '.env' file in the same directory. So this variant worked.

lehors (Fri, 05 May 2017 14:36:54 GMT):
now, that's teaching cutting edge technology! :)

joe-alewine (Fri, 05 May 2017 15:21:47 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=CfNHQDXkSn4jasT82) @highway Neat! Any other comments/impressions you'd like to share?

joe-alewine (Fri, 05 May 2017 15:21:47 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=CfNHQDXkSn4jasT82) @highway Neat! Any other comments/impressions you can share?

nickgaski (Fri, 05 May 2017 16:28:13 GMT):
hi @highway - the ORDERER_CFG_PATH variable has been addressed; that problem should not have been present if the scripts and artifacts were curled from the provided path. Your observation about ARCH_TAG is indeed a good one. If we simply pass ARCH_TAG=x86_64 as a preface to our docker-compose command, everything works as expected. Let me do a bit of investigating, but many thanks for sharing your thoughts

MrBuggySan (Fri, 05 May 2017 16:56:34 GMT):
@lehors @nickgaski when I use network_setup.sh up I get the 'ERROR!! FAILED to execute End2-End Scenario' and 'Error connecting: rpc error: code = 14 desc = grpc: RPC failed fast due to transport failure Error: rpc error: code = 14 desc = grpc: RPC failed fast due to transport failure '

MrBuggySan (Fri, 05 May 2017 16:56:34 GMT):
@lehors @nickgaski when I use network_setup.sh up I get the `ERROR!! FAILED to execute End2-End Scenario` and `Error connecting: rpc error: code = 14 desc = grpc: RPC failed fast due to transport failure Error: rpc error: code = 14 desc = grpc: RPC failed fast due to transport failure `

MrBuggySan (Fri, 05 May 2017 16:56:34 GMT):
@lehors @nickgaski when I use network_setup.sh up I get the `ERROR!! FAILED to execute End2-End Scenario` and ```Error connecting: rpc error: code = 14 desc = grpc: RPC failed fast due to transport failure Error: rpc error: code = 14 desc = grpc: RPC failed fast due to transport failure```

MrBuggySan (Fri, 05 May 2017 17:03:53 GMT):
I've also set the option `down` then `up` again

nickgaski (Fri, 05 May 2017 18:01:20 GMT):
@MrBuggySan - what platform are you running on? If you message me directly I will help you debug

nickgaski (Fri, 05 May 2017 18:24:48 GMT):
and strangely enough, I just got the same error on my machine!

MrBuggySan (Sun, 07 May 2017 21:51:48 GMT):
For anyone trying to implement the instructions in Getting Started, this repo may help :https://github.com/yeasy/docker-compose-files/tree/master/hyperledger/1.0 . I have not tested it myself though

foravneet (Mon, 08 May 2017 11:42:53 GMT):
@MrBuggySan @nickgaski I'm getting the RPC error still.. I saw some more people above as well with the same problem..

foravneet (Mon, 08 May 2017 11:49:06 GMT):
@here Moderators - A lot of people were having issues just getting the getting started to work. Do you think you can start a temp channel (can be deleted once docs are stable) so getting started questions are not lost in other questions here? Also if you can define a way to collect & publish tech FAQs just on getting started, that people can contribute to as they are resolving their issues , might be very useful to not stumble upon same issues that others in community have solved already.

JonathanLevi (Mon, 08 May 2017 13:44:13 GMT):
@foravneet, I can tell you from other threads regarding channels... that many object(ed) to creating new channels... but due to the importance of this, you are all very welcome to also use the #fabric-release channel.

JonathanLevi (Mon, 08 May 2017 13:44:53 GMT):
(when and as you deem relevant)

michele (Tue, 09 May 2017 09:11:18 GMT):
Hello, I was reading this specific page https://hyperledger-fabric.readthedocs.io/en/latest/readwrite.html

michele (Tue, 09 May 2017 09:12:23 GMT):
T1 -> Write(k1, v1'), Write(k2, v2')

michele (Tue, 09 May 2017 09:12:46 GMT):
the documentation says "T1 passes validation because it does not perform any read. Further, the tuple of keys k1 and k2 in the world state are updated to (k1,2,v1'), (k2,2,v2')"

michele (Tue, 09 May 2017 09:13:21 GMT):
where the value 2 is set in the Write?

michele (Tue, 09 May 2017 09:14:23 GMT):
Should not be corrected in T1 -> Write(k1, 2, v1'), Write(k2, 2, v2') for better clarity?

nickgaski (Tue, 09 May 2017 14:55:07 GMT):
@michele - we use the middle integer in this context to represent the version of the world state. A write transaction is simply a key and a value - NOT a world state version. If the key/vals are validated, then we update the world state

markparz (Tue, 09 May 2017 18:45:27 GMT):
Hi everyone, a few folks are currently working on shaping up the key concepts, intro and what's becoming a planning guide... please feel free to join give feedback or thoughts ... our thought is that we need to get more focus on concepts and operational aspects

markparz (Tue, 09 May 2017 20:37:55 GMT):
Hi @tkuhrt anyway possible :) are there any particular parts you are most interested in writing and/or reviewing, identifying gaps? Anything & everything helps for sure.... Happy to have you, the more the merrier for sure!

tkuhrt (Tue, 09 May 2017 20:44:20 GMT):
Okay...didn't understand whether a group was forming around this and there was going to be a meeting or if you were just looking for feedback on this channel. I think it would be useful to separate our documentation into a section for Operations and a separate one for Developers. We need to make sure that the people who just want to set up a system for creating blockchain applications, without having to download and build the code, can do so.

michele (Wed, 10 May 2017 07:29:32 GMT):
@nickgaski that makes sense, thank you!

joe-alewine (Wed, 10 May 2017 19:58:38 GMT):
Some changes underway with the docs with the help of Anthony O'Dowd from the Blockchain Labs in Hursley. A new introductory section -- very high level, introducing people to the concept of blockchain and then some on Hyperledger Fabric as a particular iteration of blockchain. Then, a reworking of Key Concepts. And then finally, some new introductory high level stuff in Getting Started. Here's an image of what we've sketched out. Comment! Help out!

joe-alewine (Wed, 10 May 2017 20:00:25 GMT):
We're going to get some of the introduction pushed out to github as soon as we can. I'll post the link when we do

joe-alewine (Wed, 10 May 2017 21:05:11 GMT):
As promised: https://gerrit.hyperledger.org/r/#/c/9211/

joe-alewine (Wed, 10 May 2017 21:05:11 GMT):
And here it is: https://gerrit.hyperledger.org/r/#/c/9211/

highway (Thu, 11 May 2017 06:36:39 GMT):
Hello everybody. I wonder if there is a description of the generated crypto-config directory. So what is the function of the different certificates and why this directory structure maybe for the default crypto-config generated by ./network_setup.sh up. Is it in the documentation? Sorry if I overlooked it.

BlkchnDev (Thu, 11 May 2017 06:57:15 GMT):
can anyone let me know what is orderer? I know that we have peer nodes & membership services in a blockchain network

highway (Thu, 11 May 2017 07:01:39 GMT):
@BlkchnDev the ordering service is documented here: https://github.com/hyperledger/fabric/blob/6f9b4272f4e3a6d843866402fa4325f39124e044/orderer/README.md

BlkchnDev (Thu, 11 May 2017 07:21:13 GMT):
Yeah i have seen those @highway . But to make it clear I want to know if anyone can explain in terms of the blockchain network components. If you see the docker images needed to setup a blockchain network, you need - peer image, membership service image. Hence I want to know in that perspective, where does orderer come into picture in the scenario.

bmos299 (Thu, 11 May 2017 12:26:16 GMT):
@markparz @nickgaski There is a really good thread on the mailgroup. Sorin had a great post on the [Hyperledger-fabric] Proposal: the "alpha2 challenge" thread. Here is the update that pertains to doc and test. For docs: I would love to see the docs migrate to an SDK oriented > flow and deemphasize the CLI. I don't think certain aspects of the > CLI (such as invoking chaincode) are relevant to the real-world, but > we prominently feature this method in the guides. We should really > focus on simple yet clear SDK based flows. If something is not simple > or clear, we should figure out if we can fix the software so that it > is. > > For examples: I would love to see the chaincode examples (example02, > etc) we have be accompanied by SDK examples (minimally node+java, but > others welcome too if we have contributors versed in them). > > For the integration suite, I am envisioning some kind of umbrella > project (e.g. fabric-integration.git) that is designed to pull in say > fabric.git/fabric-ca.git/fabric-sdk-node.git/fabric-sdk-java.git and > run some CI-based integration tests. The idea would be similar to the > various e2e's that we have, with the emphasis on a) real-world (TLS > on, keys dynamic, multiple nodes, real SDK clients not CLI, etc) and > b) based on pulling HEAD from each of the projects. The idea would be > to catch ABI breaking changes as they occur since > fabric-integration.git would emulate our users own projects that do > not update in lockstep with fabric*.git trees. > > Thoughts?

bmos299 (Thu, 11 May 2017 12:45:48 GMT):
I know for docs we have chatted about a similar flow

nickgaski (Thu, 11 May 2017 13:31:50 GMT):
@highway - let me repost something from @mastersingh24 that you will find very helpful

nickgaski (Thu, 11 May 2017 13:32:05 GMT):
1. MSP (membership service provider) - this is a concept which allows for 2 things: - ability to use different types of membership providers. the default (and only one currently implemented) is an X509 provider - it allows for "identities" to be issued by different providers (e.g. if you have multiple companies participating in the blockchain, each company could manage/provide their own certificate authority for issuing certificates) 2. Based on 1), fabric peers / ordering nodes are not required to obtain their X509 material from fabric-ca but of course we provide fabric-ca for people with their own CAs to use 3. MSPs are used in 2 ways (and I admit this is confusing) - "LocalMSP" - think of local MSPs as "structures" which hold the cryptographic identity information for clients, peers and ordering nodes. They will contain the root CA which issued the identity as well as the signing certificate key pair for the client, peer, orderer. For example, when a peer starts up, it will populate its localMSP from the file artifacts reference in core.yaml and will use this information to actually sign endorsements (among other things) - "VerifyingMSPs" - similar to a "localMSP" except they DO NOT contain a signing identity (i.e. no reference to a private key for a signing keypair). (you'll note that one of the fields of an MSP is actually a revocation list and in the case of X509 provides this will be an X509 CRL 4. When channels are created, you actually specify which organizations are allowed to participate in that channel. Each organization will be associated with an MSP (and it would be a "verifying" MSP). When the genesis / config block for a channel is created, it will contain the list of organizations (each of which has its MSP info) 5. When a peer joins a channel, you give it the genesis / config block for the channel. The peer will parse that information and will have a map of channels with one of the properties of each channel being the list of MSPs for the channel 6. So let's say we have a channel (call it channelA) which has 3 orgs - Org1, Org2, Org3. Let's say that chaincode get's deployed with a policy that requires signatures from 2 out of the 3 orgs 7. So a client submits an endorsement proposal to peers from from at least 2 out of the 3 orgs, gots the proposal responses back, creates an transaction and submits it to the ordering service. A couple of things happened along the way: - each peer has the list of per channel MSPs and will actually check to make sure that the client who submitted the proposal is allowed to do so by verifying the signature of the proposal (the client signed it using its local MSP) and making sure that the client's certificate was issued by an MSP that's associated with the channel (there's more detail to how this works, but should be good enough for now) - when the client submits the transaction to the orderer, the same basic thing happens - signature is checked and orderer node checks to make sure that the certificate is valid / issue by one of the MSPs for the channel 8. Let's say a Peer is connected to channelA and receives a block of transactions. Let's say it got a block which had the transaction submitted in step 7) above. The peer now needs to make sure that the endorsement policy for the transaction has been met (the endorsement policy is assocaited with the chaincode against which endorsement was requested). From step 6), we said that this requires signatures from 2 out of the 3 orgs and from step 5) the peer knows which orgs (and MSPs) are part of the channel. So the peer can make sure that there are enough valid signatures which meet the policy 9. OK - so finally - let's say that a peer (we'll call it org1Peer1) from Org1 was compromised. For simplicity, let's say that Org1 is only part of channelA. So we need to be able to tell all peers which have joined channelA that the certificate for org1Peer1 has been revoked. All peers need to receive and process this information at the same time (this is to ensure that the committing logic is deterministic). So we need to update the MSP for Org1 and propogate that information to all peers connected to channelA. Recall that one fof the fields for an MSP structure is a revocation list, so what needs to happen is that an update transaction is submitted to the ordering service for channelA which updates Org1's MSP to know have a CRL containing the certificate for org1Peer1

nickgaski (Thu, 11 May 2017 13:33:48 GMT):
@here - this above post will do wonders in clearing up any confusion you may have with regards to MSPs in relation to the overall network, channels and tx flow. Thanks to Gari for the beyond thorough explanation

highway (Thu, 11 May 2017 13:35:21 GMT):
@nickgaski Thank you very much! That is awesome ;) Exactly the hint I needed

joe-alewine (Thu, 11 May 2017 14:20:06 GMT):
Following on to what I was saying about an Introduction, here's where you can preview the docs we're pushing out there. http://fabricstaging.readthedocs.io/en/latest/blockchain.html

joe-alewine (Thu, 11 May 2017 14:21:29 GMT):
Comments from the community are invaluable to making this as good as it can be, especially from people newer to blockchain. There's no way to comment on that particular page but you can post your comments here or go to the gerrit page I linked to above and post comments there

markparz (Thu, 11 May 2017 15:45:02 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=nvNm5MX3nrFEgKjm2) @tkuhrt Yea, I agree totally, and I also think it's a good thought to start forming a group, and we can section out some things... right now I'm focused on https://jira.hyperledger.org/browse/FAB-2308 which is sort of that operational aspect. As well as taking a step back and working with @joe-alewine and Anthony O'Dowd on https://jira.hyperledger.org/browse/FAB-3830. @nickgaski is working on getting a staging site up for easier reviews. We were thinking of hitting key concepts next. Anthony has a bunch of material he is piece mealing together to build a high level overview then drilling down to some more detail. Which of these Jira items would you like to help with, or is there another piece? I'd love to dig deeper on some of these operational aspects in the planning guide. Just been doing sections at a time.

markparz (Thu, 11 May 2017 15:47:10 GMT):
It's all high level WIP, and needs more drilling into from us all...

lehors (Thu, 11 May 2017 15:48:02 GMT):
@nickgaski what is the status of the usage_FAQ page?

lehors (Thu, 11 May 2017 15:48:50 GMT):
it doesn't seem to be used but the source file still exists and has some rather surprising claim about performance goal

lehors (Thu, 11 May 2017 15:48:58 GMT):
https://github.com/hyperledger/fabric/blob/master/docs/source/FAQ/usage_FAQ.rst

lehors (Thu, 11 May 2017 15:49:12 GMT):
The current performance goal for the fabric is to achieve 100,000 transactions per second in a standard production environment of about 15 validating nodes running in close proximity.

lehors (Thu, 11 May 2017 15:49:12 GMT):
"The current performance goal for the fabric is to achieve 100,000 transactions per second in a standard production environment of about 15 validating nodes running in close proximity."

markparz (Thu, 11 May 2017 15:49:35 GMT):
@tkuhrt here is a quick starter I put in for the ordering service

nickgaski (Thu, 11 May 2017 15:51:05 GMT):
hey arnaud. As you may have noticed, we still have some outdated and placeholder docs in our library. I think a good ticket would be to eliminate the unused documents and scrub current docs (regardless of whether they are in the TOC) for inaccurate information. I will defer to @bmos299 for anything regarding performance. However, I imagine we should be very careful about publishing these numbers until they are thoroughly vetted

markparz (Thu, 11 May 2017 15:51:34 GMT):
but wanna work on this together? or take :)

lehors (Thu, 11 May 2017 15:52:10 GMT):
this is apparently taken for granted and repeated around...

lehors (Thu, 11 May 2017 15:53:47 GMT):
I'll be happy to create a ticket for that and work on it

lehors (Thu, 11 May 2017 15:54:15 GMT):
are you confident that all the docs you want to keep are referenced in the index?

lehors (Thu, 11 May 2017 15:54:28 GMT):
meaning, can I assume that if it's not it can be removed

nickgaski (Thu, 11 May 2017 15:56:40 GMT):
However, if you see a placeholder that says WIP or coming soon, then we can nuke it

markparz (Thu, 11 May 2017 16:10:12 GMT):
also would like to point to SO for FAQ's @lehors

lehors (Fri, 12 May 2017 14:15:35 GMT):
@cbf you seem to have decided to retire the fabric.md wiki page in favor of the plain wiki page fabric, is that right?

lehors (Fri, 12 May 2017 14:15:57 GMT):
I think it's reasonable given the flakiness of the markdown plugin on our wiki

lehors (Fri, 12 May 2017 14:16:13 GMT):
but as a result we got some broken links

cbf (Fri, 12 May 2017 14:16:22 GMT):
any errors and it does not render properly

lehors (Fri, 12 May 2017 14:17:31 GMT):
well, the ones I see in the doc at least

lehors (Fri, 12 May 2017 14:18:53 GMT):
I put ONE line in fabric.md to link to fabric and it doesn't even work

lehors (Fri, 12 May 2017 14:21:42 GMT):
cbf: fixed the old page: https://wiki.hyperledger.org/projects/fabric.md :-)

lehors (Fri, 12 May 2017 14:21:42 GMT):
@cbf : fixed the old page: https://wiki.hyperledger.org/projects/fabric.md :-)

cbf (Mon, 15 May 2017 12:53:47 GMT):
@nickgaski we need to update getting started to work with v1.0.0-alpha2 images

cbf (Mon, 15 May 2017 12:54:09 GMT):
https://jira.hyperledger.org/browse/FAB-3925

dave.enyeart (Mon, 15 May 2017 14:54:44 GMT):
@nickgaski @Ratnakar I've gotten myself confused between the two sets of end-to-end instructions:https://github.com/hyperledger/fabric/blob/master/examples/e2e_cli/end-to-end.rst and https://hyperledger-fabric.readthedocs.io/en/latest/getting_started.html.

dave.enyeart (Mon, 15 May 2017 14:55:28 GMT):
What is the reason for having two different sets of instructions? Which one should new people follow? Which one is closest to working on latest master?

nickgaski (Mon, 15 May 2017 14:56:57 GMT):
hey dave. I will push an alpha2 version today. The getting started uses the baked alpha images. The examples/e2e_cli asks the user to run a `make docker` and `make release-all`. However, my README never got merged into that repository, so it's a little confusing what's going on with the new config stuff (e.g. consortiums, anchorPeer transactions, etc...).

dave.enyeart (Mon, 15 May 2017 14:58:08 GMT):
what will get updated for alpha2? the end-to-end.rst or getting_started.html or both?

dave.enyeart (Mon, 15 May 2017 14:59:05 GMT):
i just started the end-to-end.rst instructions and already see a problem...

nickgaski (Mon, 15 May 2017 15:00:10 GMT):
I'm aware. https://gerrit.hyperledger.org/r/#/c/8981/1/examples/e2e_cli/end-to-end.rst - This is the piece I have been begging for a merge since May 4

dave.enyeart (Mon, 15 May 2017 15:00:38 GMT):
ok, they are not mirrors currently. end-to-end.rst has the `Run the end-to-end test with Docker` section that automatically runs things, getting_started does not. Will they be in sync once you are done?

dave.enyeart (Mon, 15 May 2017 15:02:07 GMT):
ok, so is the best set of instructions for people to run today these ones: https://gerrit.hyperledger.org/r/#/c/8981/1/examples/e2e_cli/end-to-end.rst

dave.enyeart (Mon, 15 May 2017 15:02:23 GMT):
or do you still need to make significant updates on top of that?

nickgaski (Mon, 15 May 2017 15:02:48 GMT):
yes those should work. I'm doing it right now and will confirm

dave.enyeart (Mon, 15 May 2017 15:03:20 GMT):
ok, i'll run through that today as well and report any feedback

lehors (Mon, 15 May 2017 15:32:55 GMT):
@nickgaski I think we should discuss what to do with all the doc files that are not actually used but still in the tree

lehors (Mon, 15 May 2017 15:33:30 GMT):
the problem is that even though they aren't part of the build and readthedoc people go to them by browsing github

lehors (Mon, 15 May 2017 15:34:49 GMT):
I think we need to either segregate them to some different directory named something like "attic" with a note explaining these files aren't currently used or remove them from the source tree altogether

lehors (Mon, 15 May 2017 15:35:27 GMT):
I'd rather do the latter but could go with the former if you think we're going to use them eventually

lehors (Mon, 15 May 2017 16:27:52 GMT):
I'm happy to do the work but would like to know what others think before submitting a CR

bmos299 (Mon, 15 May 2017 18:34:15 GMT):
@lehors my gut feel is to purge them if not needed. Moving forward, files that are official release and outdated, we come up with a strategy to archive or put them in a folder labeled accordingly. @nickgaski

bmos299 (Mon, 15 May 2017 18:34:15 GMT):
@lehors my gut feel is to purge them if not needed. Moving forward, files that are associated with an official release and outdated, we come up with a strategy to archive or put them in a folder labeled accordingly. @nickgaski what do you think?

lehors (Mon, 15 May 2017 18:45:34 GMT):
@bmos299 now that the tree has been tagged for alpha2 I guess we could just remove them. We could get them back via the tag. We just need to get that documented so we can find them in the future if needed.

bmos299 (Mon, 15 May 2017 19:00:38 GMT):
@lehors agreed. There are also ways to tag the version of the doc itself. I think we are both saying we just dont want to see unused files cluttering the directories, but yet if we need something (for regression reasons) in the future, the file(s) are accessible.

lehors (Mon, 15 May 2017 20:30:49 GMT):
@tkuhrt thanks for the careful review of my CR!

tkuhrt (Mon, 15 May 2017 20:49:34 GMT):
@joe-alewine : Nice document introducing the concepts of blockchain. A few thoughts:(https://chat.hyperledger.org/channel/fabric-documentation?msg=2ejv4JLbiouDtZ2Mu)

tkuhrt (Mon, 15 May 2017 20:50:33 GMT):
1. In the section that states "* This property of immutability makes it simple to determine the provenance of information because participants can be sure that information has not been changed after the fact.", it would be nice to talk about how blocks link back to previous blocks to allow the network to more quickly understand if the data has been modified.

tkuhrt (Mon, 15 May 2017 20:51:31 GMT):
2. I was once told that contractions (they're, it's) make it harder for people where English is not their first language to understand. Not sure if that is true, but I always try to write my documents without contractions.

joe-alewine (Mon, 15 May 2017 21:26:45 GMT):
@tkuhrt Thanks for your comments! Your first suggestion seems reasonable and would be relatively simple. As for your second suggestion, I haven't heard that, but I suppose it's possible. I tend to make decisions about contractions in terms of flow and rhythm. Sometimes you need another syllable and sometimes you don't, that kind of thing.

hshimo (Tue, 16 May 2017 09:03:57 GMT):
Where can I find trust worthy document to setup environment? The document has been very messy and wrong, so I couldn't setup the docker environment. v1.0.0-alpha2 is released yesterday, but is following documents correct? (or for v0.6?) https://github.com/hyperledger/fabric/tree/v1.0.0-alpha2/docs/source/Setup

nickgaski (Tue, 16 May 2017 21:12:55 GMT):
@hshimo - have you run through this piece yet - https://github.com/hyperledger/fabric/blob/master/examples/e2e_cli/end-to-end.rst ? I agree that the dev environment piece is without doubt way too complicated. Moreover, it contains some outdated and unnecessary information. To put it simply, do the following: download Go, download docker, set your GOPATH, clone fabric into `$GOPATH/src/github.com/hyperledger` . Check out that piece though

nickgaski (Tue, 16 May 2017 21:13:39 GMT):
if you're on mac, you'll want xcode and homebrew too

tmath (Wed, 17 May 2017 00:07:00 GMT):
what is the difference between the getting started guide and the setting up dev env guide?

tmath (Wed, 17 May 2017 00:07:29 GMT):
also, is the following tutorial for v 0.6 or 1.0: http://hyperledger-fabric.readthedocs.io/en/latest/Setup/JAVAChaincode.html ?

guoger (Wed, 17 May 2017 03:51:28 GMT):
I found two docs: http://openblockchain.readthedocs.io and hyperledger-fabric.readthedocs.io, only the latter one is referenced at hyperledger.org. I wonder if the former one is still up-to-date? Why two separate doc webpage? thx

reoim10 (Wed, 17 May 2017 08:34:59 GMT):
@guoger The former one is outdated and it is for v0.6

guoger (Wed, 17 May 2017 08:42:37 GMT):
@reoim10 I see. The old one can actually be merged into new link under `v0.6`, instead of rotting at a separate link. More importantly, we *should* deprecate the old doc by stating _v0.6_ explicitly there. Furthermore, I found some sections in the old doc still valuable, e.g. Protocol Spec, which I failed to find in the new doc.

reoim10 (Wed, 17 May 2017 08:46:56 GMT):
@guoger I agree. Hope they update docs soon.

nickgaski (Wed, 17 May 2017 14:19:26 GMT):
@reoim10 @guoger - for what it's worth. If you access the main landing page for they fabric docs - http://hyperledger-fabric.readthedocs.io/en/latest/ - and look in the bottom left of the screen. There is an option to toggle between `latest` and `v0.6`. I agree that the outdated stuff (especially openblockchain) should be deprecated

guoger (Wed, 17 May 2017 15:07:12 GMT):
@nickgaski thx! The link seemed to be broken when I tried it, but it works now :D

mrkiouak (Wed, 17 May 2017 15:28:47 GMT):
anyone opposed to a Jira for updating http://hyperledger-fabric.readthedocs.io/en/latest/Setup/logging-control.html to include sdk logging controls?

cbf (Wed, 17 May 2017 22:49:51 GMT):
@here Getting Started is still not caught up to v1.0.0-alpha2

cbf (Wed, 17 May 2017 22:50:17 GMT):
when you curl curl -L https://nexus.hyperledger.org/content/repositories/snapshots/sandbox/vex-yul-hyp-jenkins-2/fabric-binaries/release.tar.gz -o release.tar.gz 2> /dev/null; tar -xvf release.tar.gz this still has scripts that download the v1.0.0-alpha docker images

cbf (Wed, 17 May 2017 22:58:29 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=JdZwxKa94YscJfHfT) @mrkiouak please do!

albert.lacambra (Thu, 18 May 2017 07:25:18 GMT):
some way to track changes done into the documentation from fabric v1.0

BlkchnDev (Thu, 18 May 2017 09:41:38 GMT):
Hi. How to edit membersrvc file to add our own users in fabric v0.6 with/ without using bluxmix as a service?

cbf (Thu, 18 May 2017 13:32:13 GMT):
bootstrap script for GS https://gerrit.hyperledger.org/r/#/c/9525/

cbf (Thu, 18 May 2017 13:33:26 GMT):
and it would download the correct tarbal, extract and leave the user in the correct directory... then it would download all the requisite docker images.

BlkchnDev (Fri, 19 May 2017 04:47:34 GMT):
can anyone let me know - How to edit membersrvc file to add our own users in fabric v0.6 with/ without using bluxmix as a service?

lehors (Fri, 19 May 2017 06:23:38 GMT):
the v0.6 service in bluemix was really just to start getting a sense of what you could do with fabric

lehors (Fri, 19 May 2017 06:23:54 GMT):
but all the configuration is built-in and can't be changed

lehors (Fri, 19 May 2017 06:24:38 GMT):
you need to do your own install - you can do that on pretty much any machine

lehors (Fri, 19 May 2017 06:24:54 GMT):
and then you will have full access to the configuration file

lehors (Fri, 19 May 2017 06:25:06 GMT):
beware that development on 0.6 has stopped

lehors (Fri, 19 May 2017 06:25:39 GMT):
1.0 alpha2 is being released and it would be worth for you to investigate using this instead

cbf (Fri, 19 May 2017 13:59:40 GMT):
I think that we should consider annotated automation scripts that we inline segments and add additional prose.

cbf (Fri, 19 May 2017 14:00:12 GMT):
let's be clear, I don't think anyone will be running the steps involved in setting up a cluster manually

cbf (Fri, 19 May 2017 14:00:36 GMT):
no, it will be automated in some manner

odowdaibm (Fri, 19 May 2017 14:01:13 GMT):
hi all. we're going to have our first call for documentation in an hour

cbf (Fri, 19 May 2017 14:01:20 GMT):
this is why I actually favor network_setup.sh and I think most developers have the same inclination

cbf (Fri, 19 May 2017 14:03:51 GMT):
have a conflicting call, leaving some thoughts here

cbf (Fri, 19 May 2017 14:04:34 GMT):
OpenStack had a similar plight - getting an openstack environment up and running was a complex problem

cbf (Fri, 19 May 2017 14:06:12 GMT):
https://docs.openstack.org/developer/devstack/

cbf (Fri, 19 May 2017 14:06:30 GMT):
now, it has come a long way but it started out as an annotated shell script

tkuhrt (Fri, 19 May 2017 14:07:18 GMT):
Chris, I agree that people are lazy. We do want to make sure that someone understands what they have just done by executing network_setup.sh. A picture would be nice at a minimum. Words and a picture would be better.

cbf (Fri, 19 May 2017 14:08:13 GMT):
here's the meat https://git.openstack.org/cgit/openstack-dev/devstack/tree/stack.sh

cbf (Fri, 19 May 2017 14:08:30 GMT):
of course, @tkuhrt, not suggesting otherwise

cbf (Fri, 19 May 2017 14:08:48 GMT):
but we don't have to force them to type in (or cut and paste) a bunch of commands

cbf (Fri, 19 May 2017 14:10:09 GMT):
IMO, we can and should provide such an annotated script, and rather than then decompose and have them run each command, we can make it clear that what we are doing is EXPLAINING what just happened when they ran network_setup.sh

cbf (Fri, 19 May 2017 14:11:27 GMT):
all I am really suggesting is that rather than having the doc say: "now run this command: blah.sh" with these args

cbf (Fri, 19 May 2017 14:12:34 GMT):
that we merely say: "the next step in network_setup.sh on line 100 creates the certificates for our network"

Asara (Fri, 19 May 2017 14:15:21 GMT):
On the Getting started page (http://hyperledger-fabric.readthedocs.io/en/latest/getting_started.html) it is stated that the documentation is valid for alpha2, but the link for the bootstrap script points to master.

Asara (Fri, 19 May 2017 14:15:36 GMT):
Might be better to point it to the actual release's bootstrap script :)

tkuhrt (Fri, 19 May 2017 14:17:36 GMT):
Agree, Chris. The flow is run the script followed by decomposition of the script and what just happened. The other thing I would like to see is that the script leave things in a state where you can then use the network. Yesterday when I ran the script, it did leave it running but not in the background where I could then run commands to query and add to the blockchain

Asara (Fri, 19 May 2017 14:17:43 GMT):
Looks like the bootstrap script is actually not in the alpha2 release's code

odowdaibm (Fri, 19 May 2017 14:23:27 GMT):
@here Just in case you're not aware, we're going to have our Western Hemisphere kick off for the documentation work group in 40 minutes or so. Details on how to join are here: https://lists.hyperledger.org/pipermail/hyperledger-fabric/2017-May/000992.html Or just use Zoom link: https://ibm.zoom.us/my/ajodowd

odowdaibm (Fri, 19 May 2017 14:26:02 GMT):
There's also a proposal on how to improve the Getting Started documentation here: https://drive.google.com/file/d/0B-n-iLEM1iXrTFdkRV82S0wweWM/view?usp=sharing Would very much value comments on mailing list on this thread: https://lists.hyperledger.org/pipermail/hyperledger-fabric/2017-May/000999.html

odowdaibm (Fri, 19 May 2017 14:53:13 GMT):
OK, I've opened the meeting a little early, just in case anyone hasn't tried out Zoom before

nickgaski (Fri, 19 May 2017 16:12:22 GMT):
@Asara - not to split hairs, but the disclaimer is simply stating that the instructions work against the alpha2 docker images and the artifacts/scripts/utilities that are extracted from the tarball. You are correct that the bootstraph.sh script lives in master, but it's simply a bash script that bundles our artifacts and downloads the docker images

Asara (Fri, 19 May 2017 16:29:56 GMT):
@nickgaski Understood, just worried that the script changes before alpha3/beta whatever, and then things break. But it is a baseless fear :)

nickgaski (Fri, 19 May 2017 16:32:52 GMT):
it's actually a good point. we'll likely pivot to a versioned URL to avoid that

odowdaibm (Fri, 19 May 2017 16:39:47 GMT):
@Yogendrasri and @tkuhrt thanks for your participation today

tkuhrt (Fri, 19 May 2017 16:42:59 GMT):
Sorry I had to run to another call. Interested to know where the meeting ended @odowdaibm

odowdaibm (Fri, 19 May 2017 16:44:30 GMT):
it was fine. We agreed to focus on GS, Writing First App, and Overall TOC. I've put a proposal up for new GS approach, and there are a couple of actions to agree terms and visuals, and rework GS along these lines

odowdaibm (Fri, 19 May 2017 16:44:52 GMT):
we also need to get together a proposal for Writing First Application, and for TOC/Structure

nickgaski (Fri, 19 May 2017 16:47:52 GMT):
@odowdaibm @tkuhrt - in the hopes of not duplicating work. I'm going to leverage what we already have into Anthony's proposal and see if we can get a preliminary draft of Getting Started onto a staging site. sound good?

odowdaibm (Fri, 19 May 2017 16:48:18 GMT):
@tkuhrt if you could review that with @Yogendrasri, that would help a lot.

odowdaibm (Fri, 19 May 2017 16:48:43 GMT):
it's here if you don't have the link https://drive.google.com/file/d/0B-n-iLEM1iXrTFdkRV82S0wweWM/view?usp=sharing

odowdaibm (Fri, 19 May 2017 16:49:38 GMT):
thank you; I'm writing up minutes, and will post, before I leave for the day. Have a great weekend when it starts for you

tkuhrt (Fri, 19 May 2017 16:50:43 GMT):
Nick, happy to review what you write and provide feedback. Anthony, have a great weekend too.

joe-alewine (Fri, 19 May 2017 17:43:33 GMT):
There requests on the call for a link to the high-level video that talks about differences between 0.6 and 1.0. I sent an email to the hyperledger listserve (hopefully). But here's a direct link: @tkhurt

joe-alewine (Fri, 19 May 2017 17:45:58 GMT):
I forget the name of the other person who wanted it @tkuhrt @odowdaibm

odowdaibm (Fri, 19 May 2017 18:04:23 GMT):
Minutes and Actions for Documentation workgroup posted here: https://lists.hyperledger.org/pipermail/hyperledger-fabric/2017-May/001006.html

odowdaibm (Fri, 19 May 2017 18:04:49 GMT):
Have a super weekend everyone. Looking forward to status updates on the mailing list from early next week ;)

borisbuechel (Sat, 20 May 2017 16:59:55 GMT):
first step in getting started is not working anymore, someone changed the bootstrap.sh. I got bash: line 6: cd: release/linux-amd64: No such file or directory sh: 0: Can't open download-dockerimages.sh. Someone with same issues? I'm using ubuntu 17.04 zesty. It had worked 2-3 days ago.

lehors (Sat, 20 May 2017 18:03:12 GMT):
@borisbuechel check #fabric for directions

nickgaski (Sat, 20 May 2017 20:30:32 GMT):
@here - please refresh the getting started page before kicking off. We made a few slight changes to the scripts - http://hyperledger-fabric.readthedocs.io/en/latest/getting_started.html

BlkchnDev (Mon, 22 May 2017 09:28:30 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=YQJLvJ2JnqHeh5h7b) @lehors Thank you @lehors .

BlkchnDev (Mon, 22 May 2017 09:29:31 GMT):
Need to know how to configure the service.credentials.json file for HFC SDK(from windows machine) to interact with blockchain in the own blockchain network setup using docker images in linux machine(not by using bluemix)

cbf (Mon, 22 May 2017 12:46:52 GMT):
@here there's wisdom here https://opensource.com/article/17/5/five-steps-documentation

jtclark (Mon, 22 May 2017 16:22:01 GMT):
Question: I was looking for a community calendar that perhaps showed when the documentation meetings take place....

jtclark (Mon, 22 May 2017 16:22:20 GMT):
can someone @here send me an invite, or point me in the right direction?

cbf (Mon, 22 May 2017 19:17:53 GMT):
@odowdaibm maybe you could update the wiki? https://wiki.hyperledger.org/projects/fabric see Meetings section. Thanks

hshimo (Tue, 23 May 2017 02:39:48 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=bFxabpXaFmMYoA797) @nickgaski We tried to setup Fabric by following end-to-end.rst, but it seems it downloads latest source code, currently alpha3. I want to setup stable or fixed version of Fabric otherwise it will break the setup procedure.

hshimo (Tue, 23 May 2017 02:39:48 GMT):
Now I followed latest alpha2 getting_started document. it was ok until docker setup. https://github.com/hyperledger/fabric/blob/59ec440d3f51aef510b149b8b3b0909ef093c8f4/docs/source/getting_started.rst#create--join-channel

lehors (Tue, 23 May 2017 05:16:30 GMT):
@hshimo try following Getting Started http://hyperledger-fabric.readthedocs.io/en/latest/getting_started.html

hshimo (Tue, 23 May 2017 05:16:48 GMT):
Now I followed this latest getting_started commit. https://github.com/hyperledger/fabric/blob/59ec440d3f51aef510b149b8b3b0909ef093c8f4/docs/source/getting_started.rst#create--join-channel

hshimo (Tue, 23 May 2017 05:16:48 GMT):
now i got this error, it looks like just file path problem root@14e41648eb86:/opt/gopath/src/github.com/hyperledger/fabric/peer# peer channel create -o orderer.example.com:7050 -c "channel_name" -f ./channel-artifacts/channel.tx --tls $CORE_PEER_TLS_ENABLED --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/cacerts/ca.example.com-cert.pem 2017-05-23 05:09:04.312 UTC [msp] getMspConfig -> INFO 001 intermediate certs folder not found at [/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp/intermediatecerts]. Skipping.: [stat /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp/intermediatecerts: no such file or directory] 2017-05-23 05:09:04.313 UTC [msp] getMspConfig -> INFO 002 crls folder not found at [/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp/intermediatecerts]. Skipping.: [stat /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp/crls: no such file or directory] 2017-05-23 05:09:04.314 UTC [msp] getMspConfig -> INFO 003 MSP configuration file not found at [/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp/config.yaml]: [stat /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp/config.yaml: no such file or directory]

hshimo (Tue, 23 May 2017 05:16:48 GMT):
Now I followed latest alpha2 getting_started document. it was ok until docker setup. https://github.com/hyperledger/fabric/blob/59ec440d3f51aef510b149b8b3b0909ef093c8f4/docs/source/getting_started.rst#create--join-channel

lehors (Tue, 23 May 2017 05:16:54 GMT):
this is similar to end-to-end but it should work

hshimo (Tue, 23 May 2017 05:18:08 GMT):
root@14e41648eb86:/opt/gopath/src/github.com/hyperledger/fabric/peer# peer channel create -o orderer.example.com:7050 -c "channel_name" -f ./channel-artifacts/channel.tx --tls $CORE_PEER_TLS_ENABLED --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/cacerts/ca.example.com-cert.pem 2017-05-23 05:09:04.312 UTC [msp] getMspConfig -> INFO 001 intermediate certs folder not found at [/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp/intermediatecerts]. Skipping.: [stat /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp/intermediatecerts: no such file or directory] 2017-05-23 05:09:04.313 UTC [msp] getMspConfig -> INFO 002 crls folder not found at [/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp/intermediatecerts]. Skipping.: [stat /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp/crls: no such file or directory] 2017-05-23 05:09:04.314 UTC [msp] getMspConfig -> INFO 003 MSP configuration file not found at [/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp/config.yaml]: [stat /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp/config.yaml: no such file or directory]

hshimo (Tue, 23 May 2017 05:18:08 GMT):
now I got this error. It seems there is no intermediatecerts directory in my env. root@14e41648eb86:/opt/gopath/src/github.com/hyperledger/fabric/peer# peer channel create -o orderer.example.com:7050 -c "channel_name" -f ./channel-artifacts/channel.tx --tls $CORE_PEER_TLS_ENABLED --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/cacerts/ca.example.com-cert.pem 2017-05-23 05:09:04.312 UTC [msp] getMspConfig -> INFO 001 intermediate certs folder not found at [/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp/intermediatecerts]. Skipping.: [stat /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp/intermediatecerts: no such file or directory] 2017-05-23 05:09:04.313 UTC [msp] getMspConfig -> INFO 002 crls folder not found at [/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp/intermediatecerts]. Skipping.: [stat /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp/crls: no such file or directory] 2017-05-23 05:09:04.314 UTC [msp] getMspConfig -> INFO 003 MSP configuration file not found at [/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp/config.yaml]: [stat /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp/config.yaml: no such file or directory]

hshimo (Tue, 23 May 2017 05:26:40 GMT):
Sorry It worked. I didn't specify correct channel name. but when is $CHANNEL_NAME set?

hshimo (Tue, 23 May 2017 05:28:02 GMT):
Are there "channel name" and "channel ID" in the doc? kind of confusing.

hshimo (Tue, 23 May 2017 05:28:02 GMT):
Are there "channel name", "channel-ID" and "channel-id" in the doc? kind of confusing.

greg.haskins (Tue, 23 May 2017 13:09:23 GMT):
@nickgaski https://jira.hyperledger.org/browse/FAB-4117

greg.haskins (Tue, 23 May 2017 13:09:39 GMT):
any time you see an MSPCONFIGPATH override come across your desk, it should raise an eyebrow

greg.haskins (Tue, 23 May 2017 13:09:47 GMT):
ill work to help clean up the ones that are there now

greg.haskins (Tue, 23 May 2017 13:10:19 GMT):
(do note that perhaps in some exceptional conditions, it may still be the right thing to do, but question every one that you see)

toddinpal (Tue, 23 May 2017 15:03:33 GMT):
Is there a list of the possible events generated by fabric? I haven't been able to find one.

odowdaibm (Wed, 24 May 2017 19:43:05 GMT):
@here A reminder that we're having the regular Documentation Workgroup call on Friday: Details here: https://lists.hyperledger.org/pipermail/hyperledger-fabric/2017-May/001051.html

odowdaibm (Wed, 24 May 2017 19:43:54 GMT):
There are some very interesting proposals to review, on Fabric Personae, Writing Your First Application, and Creating Your First Network

odowdaibm (Wed, 24 May 2017 19:44:47 GMT):
You can read these proposals in advance of the meeting - they are linked from the agenda, and shared here: https://drive.google.com/open?id=0B-n-iLEM1iXrWk9WWERhaHVyeWc

odowdaibm (Wed, 24 May 2017 19:45:52 GMT):
It would be excellent if you can review and post comments to mailing list, or attend the meeting. I realize US folks may be having an extended weekend due to a public holiday on Monday, but mailing list is ideal anyhow

seanbarclay (Wed, 24 May 2017 20:10:24 GMT):
Hey @odowdaibm - so Lucie on my team had created a proposal for an updated site navigation along with user flows. Would you like to include them?

seanbarclay (Wed, 24 May 2017 20:10:54 GMT):
@cbf- do we have a google drive folder to store visual assets?

seanbarclay (Wed, 24 May 2017 20:10:54 GMT):
@cbf - do we have a google drive folder to store visual assets?

seanbarclay (Wed, 24 May 2017 20:13:12 GMT):
if not i can share what we've done on a public facing folder

cbf (Wed, 24 May 2017 21:33:36 GMT):
eg what @markparz did here https://gerrit.hyperledger.org/r/#/c/9211/

cbf (Wed, 24 May 2017 21:34:31 GMT):
@odowdaibm note https://gerrit.hyperledger.org/r/#/c/9775/ - we should have done this from the outset so we can track downloads

cbf (Wed, 24 May 2017 21:34:45 GMT):
it will also tell us what platforms, which is important detail

seanbarclay (Wed, 24 May 2017 22:36:18 GMT):
@cbf - i think that's definitely one solution. However, my concern is it can bloat the repo over time. for instance, if we get into animations of the architecture or page comps in photoshop/sketch, would you want large binary files on a GH repo (not to mention the versions)? as an alternative, does linux provide anything we can leverage here for the community?

cbf (Wed, 24 May 2017 23:02:01 GMT):
@seanbarclay we need to have it versioned

cbf (Wed, 24 May 2017 23:02:19 GMT):
until GitHUb starts complaining, not my problem how large it is

cbf (Wed, 24 May 2017 23:03:09 GMT):
videos can go to the hyperledger youtube channel

odowdaibm (Thu, 25 May 2017 09:33:31 GMT):
thank you @seanbarclay Would Lucy be able to join the call on Friday - I know it's 8am PST, but it would really help

odowdaibm (Thu, 25 May 2017 11:06:12 GMT):
There is a standard proforma on the Google drive if Lucie would like to use that

seanbarclay (Thu, 25 May 2017 16:22:58 GMT):
@odowdaibm yes, her, Sarah and I will join the call tomorrow. 8am is not a problem and thanks for setting that up.

xchen1130 (Thu, 25 May 2017 16:23:40 GMT):
hello guys I am following the "getting started" docs: http://hyperledger-fabric.readthedocs.io/en/latest/getting_started.html when I issue the command "curl -sS https://raw.githubusercontent.com/hyperledger/fabric/master/examples/e2e_cli/bootstrap.sh | bash" I get error msg like "warning: fail to get default registry endpoint from daemon (got permission denied while trying to connect to ...." what is the problem?

nickgaski (Thu, 25 May 2017 17:16:08 GMT):
Hi @xchen1130 - do you have docker running?

nickgaski (Thu, 25 May 2017 17:16:48 GMT):
I should note that there is a new curl command too. `curl -sSL https://goo.gl/NIKLiU | bash`

seanbarclay (Fri, 26 May 2017 07:18:28 GMT):
@odowdaibm I posted files here temporarily: https://drive.google.com/drive/folders/0B2D2mmnqZVqqLWdPczZOMHFwZHM?usp=sharing I'll commit them to Gerrit ASAP

cbf (Fri, 26 May 2017 12:56:57 GMT):
@seanbarclay ok, what is this? when we were discussing earlier, I must have assumed you were referring to actual documentation artifacts (images etc)

cbf (Fri, 26 May 2017 12:57:16 GMT):
for posting discussion documents, google drive is fine

cbf (Fri, 26 May 2017 12:57:41 GMT):
also, without context, I have no idea what I am looking at

cbf (Fri, 26 May 2017 12:58:52 GMT):
the documentation feedback is good stuff, though

cbf (Fri, 26 May 2017 12:59:05 GMT):
the other docs obviously need some context

joe-alewine (Fri, 26 May 2017 13:22:11 GMT):
I agree with Chris -- that documentation feedback is excellent

joe-alewine (Fri, 26 May 2017 13:22:11 GMT):
I agree with Chris -- that documentation feedback in particular is excellent

odowdaibm (Fri, 26 May 2017 13:37:27 GMT):
thanks for this @seanbarclay feedback looks really interesting

odowdaibm (Fri, 26 May 2017 13:38:55 GMT):
I will read through it now, and capture the key points for the community

odowdaibm (Fri, 26 May 2017 13:39:42 GMT):
It would be good to capture in the minutes for today's call, as certain items are coming up repeatedly, and we're trying to factor into prioirty list

odowdaibm (Fri, 26 May 2017 13:39:53 GMT):
Same is true for structure/TOC, that has come up alot

odowdaibm (Fri, 26 May 2017 13:55:46 GMT):
Actually @seanbarclay , I'm going to ask you to go through this feedback as a proxy for those users on the call. I will capture as part of the minutes, and that way the community will see it. Hope that's OK. Thank you.

cbf (Fri, 26 May 2017 14:12:08 GMT):
if there are actionable items in the feedback, I strongly suggest that we track these in JIRA individually as improvements to documentation (or bugs if that is appropriate)

jeffgarratt (Fri, 26 May 2017 14:33:25 GMT):
@odowdaibm has the meeting already occurred?

odowdaibm (Fri, 26 May 2017 14:34:29 GMT):
Hi @cbf thanks for comment - I'm conscious that we need to get actions from doc WG linked into JIRA

odowdaibm (Fri, 26 May 2017 14:35:02 GMT):
I'm also conscious that we need a way for people who are not plugged into JIRA to contribute

odowdaibm (Fri, 26 May 2017 14:35:17 GMT):
(either through education, or relevant communication)

cbf (Fri, 26 May 2017 14:51:02 GMT):
@odowdaibm no reason for people not plugged into JIRA to avoid getting plugged in

cbf (Fri, 26 May 2017 14:52:39 GMT):
sadly, will miss the call - have a conflict

cbf (Fri, 26 May 2017 14:53:26 GMT):
@odowdaibm also note that JIRA already has a number of items in-flight and best that we not be split-brain about improving the docs

odowdaibm (Fri, 26 May 2017 14:53:53 GMT):
it might be the case @cbf, that we need a short piece of education on using it.

odowdaibm (Fri, 26 May 2017 14:54:16 GMT):
Many folks are used to GitHub and issues, but JIRA and Gerrit can be a little more daunting

cbf (Fri, 26 May 2017 14:54:51 GMT):
http://hyperledger-fabric.readthedocs.io/en/latest/CONTRIBUTING.html

odowdaibm (Fri, 26 May 2017 14:54:56 GMT):
anyway, its note that we need to get plugged in, and I've taken an action item toimprove that linkage

cbf (Fri, 26 May 2017 14:55:26 GMT):
there are links to JIRA and Gerrit edumacation

odowdaibm (Fri, 26 May 2017 14:56:34 GMT):
I think key thing then is to get WG Action items into JIRA items, so that we have linkage and tracking etc etc

odowdaibm (Fri, 26 May 2017 14:57:12 GMT):
OK, have a good weekend, when it starts. laters

odowdaibm (Fri, 26 May 2017 14:57:28 GMT):
@here workgroup call starting in 5 mins

odowdaibm (Fri, 26 May 2017 16:21:37 GMT):
@here thanks all for a great call today

odowdaibm (Fri, 26 May 2017 16:22:03 GMT):
I will circulate minutes for Western hemi call and wish all folks in the US a happy holiday

joe-alewine (Fri, 26 May 2017 16:27:34 GMT):
@odowdaibm A pint of bitter is calling for you...

joe-alewine (Fri, 26 May 2017 16:27:34 GMT):
@odowdaibm A pint of bitter is calling to you...

odowdaibm (Sat, 27 May 2017 07:10:12 GMT):
@lehors not a problem - minutes are here https://lists.hyperledger.org/pipermail/hyperledger-fabric/2017-May/001081.html

odowdaibm (Sat, 27 May 2017 07:10:41 GMT):
@here Two great meetings yesterday Minutes on mailing list. Comments very welcome. Thank you.

Yuvaraj_Ravi (Sun, 28 May 2017 18:49:19 GMT):
Hi, Can someone let me know the following details? What is the amount of time taken by orderer to create a block assuming it has sufficient amount of transactions? if it depends on different consensus mechanism, what is the latency for different mechanisms?

jeffgarratt (Tue, 30 May 2017 14:06:39 GMT):
@Yuvaraj_Ravi the time taken depends on the settings which affect block 'cutting', and the implementation of the orderer service. Currently only 'solo' and 'kafka' are available. Solo is for dev purposes only, so only kafka is recommended for production use. The latency is highly dependent on a multitude of factors, eg. TX payload size, network latency, etc. Work is under way to gather performance related information. You may be able to get a clearer answer by posting your question to the #fabric-consensus channel.

cbf (Tue, 30 May 2017 17:25:24 GMT):
I see fairly straight-forward "separate out pre-requisites as this can be reused elsewhere"

odowdaibm (Tue, 30 May 2017 17:45:11 GMT):
@here and @cbf I've incorporated everyone's comments into the Writing Your First Application proposal. There's an update on the mailing list here: https://lists.hyperledger.org/pipermail/hyperledger-fabric/2017-May/001091.html and the updated proposal is at https://drive.google.com/open?id=0B-n-iLEM1iXrZkNpSXNxQ0FZczg I think it looks good now, so I'm looking for volunteers to get started on this.

odowdaibm (Tue, 30 May 2017 17:46:37 GMT):
Yes @cbf, we'd like to have a really simple install for the network. We created a 1 liner to create a network under a JIRA request recently - we use that in Composer. Could we use that here please?

odowdaibm (Tue, 30 May 2017 17:46:56 GMT):
@sstone1 can you recall the JIRA for this please Simon?

odowdaibm (Tue, 30 May 2017 17:47:47 GMT):
I also need a volunteer to write a very simple application as described in the proposal using the node.js SDK

cbf (Tue, 30 May 2017 17:50:42 GMT):
I presume that first sdk sample will be node?

cbf (Tue, 30 May 2017 17:51:18 GMT):
ok, I will work on prereqs and network install

odowdaibm (Tue, 30 May 2017 17:51:47 GMT):
Simon may be back on in a bit, we have a nice one of these for composer

odowdaibm (Tue, 30 May 2017 17:52:04 GMT):
OK, all read OK to you -quite a few updates

cbf (Tue, 30 May 2017 17:52:21 GMT):
why does everyone need one of those - sigh

odowdaibm (Tue, 30 May 2017 17:52:26 GMT):
I was going ot basically steal that

odowdaibm (Tue, 30 May 2017 17:52:46 GMT):
Simon has the number, we're contributing it down

odowdaibm (Tue, 30 May 2017 17:52:56 GMT):
so I'd just like to expedite this

odowdaibm (Tue, 30 May 2017 17:53:57 GMT):
we need 1, like those other folks

sstone1 (Tue, 30 May 2017 19:00:33 GMT):
https://jira.hyperledger.org/browse/FAB-3714

sstone1 (Tue, 30 May 2017 19:01:46 GMT):
the aim is to use those same set of scripts across all places in composer which need to stand up a test fabric

sstone1 (Tue, 30 May 2017 19:04:09 GMT):
note we want to strip out the node.js parts of it and use `docker exec` to create & join the channel

cbf (Tue, 30 May 2017 19:33:48 GMT):
@odowdaibm https://gerrit.hyperledger.org/r/#/c/9945/

odowdaibm (Wed, 31 May 2017 08:29:00 GMT):
thanks @sstone1 and @mbwhite I'll be around a bit later. I also have longer term desires on connection profiles in fabric, so be warned ;)

hshimo (Wed, 31 May 2017 12:45:20 GMT):
Is this a latest Node.js SDK document for v1.0? https://fabric-sdk-node.readthedocs.io/en/master/ Some links are dead, and I'm not sure which document is currently trustworthy. https://github.com/hyperledger/fabric-sdk-node

hshimo (Wed, 31 May 2017 12:55:31 GMT):
probably this is the latest document, I guess http://hyperledger-fabric.readthedocs.io/en/latest/nodesdk.html

hshimo (Wed, 31 May 2017 12:56:59 GMT):
or maybe this one...umm.. https://github.com/hyperledger/fabric-sdk-node

hshimo (Wed, 31 May 2017 12:56:59 GMT):
or this one... so confusing Hyperledger Fabric SDK for node.js Index https://fabric-sdk-node.github.io/

nickgaski (Wed, 31 May 2017 13:27:56 GMT):
@hshimo - your last link ^^ is the most up to date

Asara (Wed, 31 May 2017 15:16:19 GMT):
what has newer/correct documentation? jimthematrix.github.io or fabric-sdk-node.github.io?

Asara (Wed, 31 May 2017 15:16:19 GMT):
what has newer/more correct documentation? jimthematrix.github.io or fabric-sdk-node.github.io?

Asara (Wed, 31 May 2017 15:21:48 GMT):
It seems like jimthematrix matches the function names of alpha2

markparz (Wed, 31 May 2017 18:19:18 GMT):
@odowdaibm @cbf @nickgaski @joe-alewine Based on the release criteria and such I'm going thru the yaml files and opening bugs based on what I see to help clarify things at least as I see them... Just opened https://jira.hyperledger.org/browse/FAB-4274 for orderer.yaml ...... Anyone else that wants to comment please do so, I'll post the issue numbers as I get thru my initial pass.

tkuhrt (Wed, 31 May 2017 19:33:25 GMT):
Before I go do this...has anyone created a bug to clean up all the different links for Hyperledger Fabric SDK documentation?

tkuhrt (Wed, 31 May 2017 19:53:07 GMT):
I could not find a matching bug, so I created: https://jira.hyperledger.org/browse/FAB-4284

Asara (Wed, 31 May 2017 20:02:57 GMT):
Aye! I made it into a Jira ticket, perfect. Thanks @tkuhrt

markparz (Thu, 01 Jun 2017 14:42:45 GMT):
created an improvement for more clarity on the configtxgen.yaml file https://jira.hyperledger.org/browse/FAB-4298

jtclark (Thu, 01 Jun 2017 15:10:50 GMT):
GM all. quick question.... and, I apologize if this is posted somewhere obvious.... I'd like to attend the docs meetings- is there a regularly schedule meeting notice somewhere?

joe-alewine (Thu, 01 Jun 2017 15:15:17 GMT):
@jtclark There's a weekly docs meeting hosted by @odowdaibm on zoom. Two of them, actually, one in the wee wee hours for Asia/Pacific and another at 11am EST. Are you on the hyperledger mailing list?

jtclark (Thu, 01 Jun 2017 15:25:20 GMT):
Hi @joe-alewine and yes, I'm on the mailing list. Perhaps I missed the calendar invite or the meeting announcement. I've ready the recent notes on the last couple of meetings

joe-alewine (Thu, 01 Jun 2017 15:28:12 GMT):
@jtclark Hi. Glad you've been following along with the minutes. Anthony does those and they're invaluable. I haven't gotten a calendar invite this week, either. Nevertheless I can give you the info. It's at 11am EST, as I said, and here's the link: https://ibm.zoom.us/my/ajodowd

joe-alewine (Thu, 01 Jun 2017 15:29:17 GMT):
The calls are scheduled for an hour, though last week I think we did more like an hour and 20

joe-alewine (Thu, 01 Jun 2017 15:29:37 GMT):
You'll need zoom if you don't already have it

bobbiejc (Thu, 01 Jun 2017 15:30:04 GMT):
@nickgaski I remember you were creating a glossary somewhere...

bobbiejc (Thu, 01 Jun 2017 15:30:21 GMT):
in that do you define "consortium"?

bobbiejc (Thu, 01 Jun 2017 15:31:45 GMT):
Also, any one know difference between 'leading peer' and 'anchor peer'?

jtclark (Thu, 01 Jun 2017 15:39:13 GMT):
@joe-alewine perfect. thank you! I will be joining tomorrow. I'm interested in participating in the docs-wg

jtclark (Thu, 01 Jun 2017 15:39:33 GMT):
alongside the ci work I'm doing in fabric...

nickgaski (Thu, 01 Jun 2017 15:43:41 GMT):
@bobbiejc - so funny you should ask. I just pushed a CR to add consortium today. I think we can keep it simple and say that a consortium is a grouping of MSP principals that forms the basis for a channel. A channel cannot exist outside the purview of a consortium. Moreover, it is the consortium that will decide upon the channel policies

joe-alewine (Thu, 01 Jun 2017 15:43:58 GMT):
@jtclark Awesome! And you're welcome! The more the merrier. If you've been following along you should know more or less what the agenda is likely to be. We're working on a Writing Your First App doc. The proposal for that is reasonably solid so hopefully we'll be able to start writing the actual doc soon. The design team is going to present the work they've been doing on branding. There's also a Getting Started/Network config thing being worked on

bobbiejc (Thu, 01 Jun 2017 15:46:32 GMT):
@nickgaski and then you need to define "MSP Principals"

nickgaski (Thu, 01 Jun 2017 15:47:12 GMT):
oh and @bobbiejc - anchor peer is the discovery mechanism that peers use when joining a channel. It allows one org's peers to become aware of the rest of the channel's peers, thus facilitating gossip. The notion of leading peer is also gossip related, however it's different. The leading peer simply receives the blocks from the ordering node and disseminates to the rest of the its org's peers on that channel. These are confusing because the anchor peer and leading peer can be the same, but they are not necessarily the same

bobbiejc (Thu, 01 Jun 2017 15:47:44 GMT):
uh oh --- i had myself convinced anchor peer was for gossip and that leader peers were for channels..

nickgaski (Thu, 01 Jun 2017 15:49:05 GMT):
it's an election of sorts. @yacovm - can you clarify?

bobbiejc (Thu, 01 Jun 2017 15:49:25 GMT):
it also means that for a single org "POC" we aren't really getting a good representation for how the algorithms work?

bobbiejc (Thu, 01 Jun 2017 15:49:51 GMT):
i know, Blockchain network, single org doesn't make sense, but a lot of 'getting started" will build their first network internally

nickgaski (Thu, 01 Jun 2017 15:50:08 GMT):
leading vs. anchor and why we need both?

yacovm (Thu, 01 Jun 2017 15:53:20 GMT):
so: Leader peer is a peer that is defined per channel, and org, (meaning, for each org there are leader peers regardless of other orgs, and also for each channel there is a leader peer for that channel). Its role is to connect to the ordering service and pull blocks. Anchor peer is/are endpoint(s), definitions that exists in the configuration block. But there should be real peers with these endpoints. They are found in the config block so that when peers join a channel, they would reach out to these endpoints and connect to peers that are (hopefully) already in the channel

yacovm (Thu, 01 Jun 2017 15:53:30 GMT):
for example- if we have 2 orgs - A and B and they share a channel

yacovm (Thu, 01 Jun 2017 15:53:47 GMT):
we'll have (hopefully) 2 anchor peers: peerA and peerB (each in org A and B)

yacovm (Thu, 01 Jun 2017 15:53:47 GMT):
we'll have (hopefully) 2 anchor peers: peerA and peerB (each in org A and B )

yacovm (Thu, 01 Jun 2017 15:54:05 GMT):
when a peer joins the channel it will connect to both anchor peers

yacovm (Thu, 01 Jun 2017 15:54:16 GMT):
and this way the membership of the channel is established

yacovm (Thu, 01 Jun 2017 15:54:25 GMT):
and all peers in the channel, even though from different orgs

yacovm (Thu, 01 Jun 2017 15:54:42 GMT):
@bobbiejc and @nickgaski any further questions? (feel free to ask)

yacovm (Thu, 01 Jun 2017 15:55:05 GMT):
the leader peer is elected between the peers in the org, that participate in the channel

yacovm (Thu, 01 Jun 2017 15:55:33 GMT):
there are all kinds of "rules" for the election but in short - the peer with the lowest "ID" wins as long as it is there for a long time

jtclark (Thu, 01 Jun 2017 15:55:43 GMT):
@joe-alewine although I'm not new to open-source projects, I am relatively new to Hyperledger. One of my tactics that allows me to learn the ins and outs of a new project/community is to first get involved with the documentation working group. it allows me to be valuable right out of the gate, while learning as I read and apply the documentation.

yacovm (Thu, 01 Jun 2017 15:55:47 GMT):
when this peer dies, re-election takes place

webdaford (Thu, 01 Jun 2017 15:55:54 GMT):
if there are two orgs each with its own leader peer and there is one for the channel as well, then are there 3 leader peers?

yacovm (Thu, 01 Jun 2017 15:56:39 GMT):
an example- if we have channel X with orgs A and B and channel Y with orgs A and B

yacovm (Thu, 01 Jun 2017 15:56:56 GMT):
then there will be at least 2 leader peers - one for A and one for B

joe-alewine (Thu, 01 Jun 2017 15:58:03 GMT):
@jtclark Sounds like a good strategy to me. Have you gone through our current docs? http://hyperledger-fabric.readthedocs.io/en/latest/

jtclark (Thu, 01 Jun 2017 15:58:36 GMT):
I'm making my way through them as we speak...

nickgaski (Thu, 01 Jun 2017 15:58:38 GMT):
hey yacov. I realize if the leading peer goes down then a new one can be elected. What happens if the anchor peer goes down?

yacovm (Thu, 01 Jun 2017 15:59:47 GMT):
well if all anchor peers die, then new peers that have joined the channel after they all died

yacovm (Thu, 01 Jun 2017 16:00:15 GMT):
if they are configured to use leader election they would declare themselves "alone" and declare themselves leaders

yacovm (Thu, 01 Jun 2017 16:00:22 GMT):
and connect to the ordering service themselves

joe-alewine (Thu, 01 Jun 2017 16:01:47 GMT):
@jtclark Cool. Look forward to hearing your thoughts on where they are and what you think we should be focusing on :thumbsup:

jtclark (Thu, 01 Jun 2017 16:02:59 GMT):
@joe-alewine Indeed. I'm probably the perfect candidate to test out your 'Writing Your First App' doc.

markparz (Thu, 01 Jun 2017 17:34:13 GMT):
https://jira.hyperledger.org/browse/FAB-4301 ->core.yaml clarification points @bobbiejc would love for you to look this one over as well!

bobbiejc (Thu, 01 Jun 2017 20:37:07 GMT):
@markparz is there a running jira for "getting started"

bobbiejc (Thu, 01 Jun 2017 20:37:25 GMT):
i think i found a typo in install and configure

bobbiejc (Thu, 01 Jun 2017 20:38:09 GMT):
i'm working through this now again fresh

markparz (Thu, 01 Jun 2017 20:38:12 GMT):
I don't think there is, however @nickgaski is working on some updates... so we need to create one for sure

bobbiejc (Thu, 01 Jun 2017 20:38:35 GMT):
so i am happy to opine on my experiences ;-)

markparz (Thu, 01 Jun 2017 20:39:56 GMT):
I'm going to open a jira item for a new readthedocs file on core.yaml too... so your thoughts there would be great... additional questions you see that need to be answered... my eyes are bleeding after reading thru 3 of these yamls :/

bobbiejc (Thu, 01 Jun 2017 21:59:57 GMT):
@weeds my comments are going to be 'elementary'

bobbiejc (Thu, 01 Jun 2017 22:00:09 GMT):
things that are so obvious to those of you on the ground...

bobbiejc (Thu, 01 Jun 2017 22:00:24 GMT):
@markparz waiting for my jira item ;-)

adc (Fri, 02 Jun 2017 09:17:04 GMT):
Hi All, is there already a JIRA item to cover changes in the documentation? I found inconsistencies here and there and I would like to fix them. Thanks :)

adc (Fri, 02 Jun 2017 11:16:24 GMT):
Hi @nickgaski, shall we coordinate in some way to update the documentation? There are so many things missing. Like: 1) which are the permissions needed to perform a certain operation, 2) which are the protobuf messages exchanged and the meaning of the fields, and so on

adc (Fri, 02 Jun 2017 11:17:12 GMT):
I'm not a native English speaker but I can tell you how things work, for example

markparz (Fri, 02 Jun 2017 12:39:40 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=FTd39vjJ6odfgmD8v) @bobbiejc @nickgaski did you say you had a getting started jira item open again?

markparz (Fri, 02 Jun 2017 12:41:48 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=hXXohzsBN6D2BF4tD) @adc we have a bunch of items open, however I do not think we either of those opened. Please feel free to open and grab :)

markparz (Fri, 02 Jun 2017 12:43:59 GMT):
you can see them all here https://jira.hyperledger.org/issues/?jql=project%20%3D%20FAB%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20fabric-docs%20AND%20labels%20%3D%20Documentation%20ORDER%20BY%20issuetype%20DESC%2C%20priority%20DESC%2C%20updated%20DESC

nickgaski (Fri, 02 Jun 2017 12:45:12 GMT):
let me open a new getting started JIRA ticket. @adc - thanks angelo; we definitely need to document the certificates and permissions. I worked with Jeff Garratt for a while yesterday and have a much better understanding of where and when the admin certs are used and so on. However we definitely need your expertise on that. Protobuffers are a little low level in the code for me. Shall I open a few JIRA issues and we can coordinate?

adc (Fri, 02 Jun 2017 12:46:04 GMT):
I have already opened this one: https://jira.hyperledger.org/browse/FAB-4321?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aall-tabpanel

adc (Fri, 02 Jun 2017 12:46:23 GMT):
if it can help. Feel free to open a new one if more appropriate :)

adc (Fri, 02 Jun 2017 12:46:52 GMT):
@markparz, thanks. There are many, actually :)

markparz (Fri, 02 Jun 2017 12:47:19 GMT):
All help welcome... and you know this backward and forward :)

bobbiejc (Fri, 02 Jun 2017 13:20:19 GMT):
I have a suggestion.. why don't we create separate jira items for separate areas of the doc. i.e https://jira.hyperledger.org/browse/FAB-4237?jql=project%20%3D%20FAB%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20fabric-docs%20AND%20labels%20%3D%20Documentation%20ORDER%20BY%20issuetype%20DESC%2C%20priority%20DESC%2C%20updated%20DESC

bobbiejc (Fri, 02 Jun 2017 13:20:48 GMT):
this one seems to be created for "Getting Started" and "Channel Configuration". So i can add to this my comments about "Getting Started"

bobbiejc (Fri, 02 Jun 2017 13:21:34 GMT):
@nickgaski I am happy to help with the writing, but i think we need someone to coordinate the writing. so feel free to toss some 'writing' or 'editing' back my way

nickgaski (Fri, 02 Jun 2017 13:32:20 GMT):
@bobbiejc - thanks for all the feedback. I think at this point we need to determine what we can realistically accomplish by the end of June, make the necessary JIRA tickets, and then begin soliciting help for the super technical stuff. I'm going to open a few additional tickets today for stuff that is still missing and/or inadequate

nickgaski (Fri, 02 Jun 2017 13:32:54 GMT):
and thanks for offering to help; I always need help

bobbiejc (Fri, 02 Jun 2017 13:59:15 GMT):
@nickgaski i'm not sure that my 'nits' can't be handled in a few hours by someone just taking a pen to the doc...

bobbiejc (Fri, 02 Jun 2017 13:59:38 GMT):
and then from there, if there is a place where you can't address in depth to extent you would want, create a new jira iem

odowdaibm (Fri, 02 Jun 2017 14:50:23 GMT):
@here Hi All, we're going to start the documentation call in 10 minutes

odowdaibm (Fri, 02 Jun 2017 14:50:42 GMT):
There will be full minutes as usual.

odowdaibm (Fri, 02 Jun 2017 14:51:21 GMT):
@here lots of interesting stuff today - finalizing personae, and Writing your first application proposals, as well as Jeff Garratt video.

jtclark (Fri, 02 Jun 2017 16:16:18 GMT):
will you also post the link to the video in your meeting notes? I know we didn't get a chance to review it....

odowdaibm (Fri, 02 Jun 2017 16:16:19 GMT):
@here, thanks all for today's meeting - lots of great input. I'll mute and update with people's comments

odowdaibm (Fri, 02 Jun 2017 16:16:32 GMT):
Yes let me ask the community about that

markparz (Fri, 02 Jun 2017 16:18:46 GMT):
off the wall question... what's this new icon thing on our doc.... it eats up a lot of space on the TOC....

joe-alewine (Fri, 02 Jun 2017 16:29:16 GMT):
Was wondering that myself. Is there a way to make it bigger? /sarcasm

joe-alewine (Fri, 02 Jun 2017 16:35:10 GMT):
@markparz you mentioned creating an epic on jira for some of these doc items. I was going to go ahead and create a jira for writing this "writing your first blockchain app" first draft and assign it to myself, but I'll hold off if you want to fold that into a larger effort

markparz (Fri, 02 Jun 2017 17:01:39 GMT):
I'm wondering if that should be an epic.... then subtask with persona write up, basic network start up, application writing, CC writing

markparz (Fri, 02 Jun 2017 17:01:55 GMT):
Lucie could grab the persona piece

markparz (Fri, 02 Jun 2017 17:02:08 GMT):
while Nick or work the network piece a

bobbiejc (Fri, 02 Jun 2017 21:46:35 GMT):
ok all, go read this page: https://fabric-sdk-node.github.io/tutorial-app-dev-env-setup.html

bobbiejc (Fri, 02 Jun 2017 21:46:50 GMT):
excellent job describing hyperledger-fabric and network topology...

bobbiejc (Fri, 02 Jun 2017 21:47:01 GMT):
good basic understanding -- would be a good pre-read to 'getting started'

cbf (Sat, 03 Jun 2017 00:27:24 GMT):
@joe-alewine @markparz guys, it REALLY DOES NOT MATTER if it is an epic or a sub-task - just create it, assign it and do it.

cbf (Sat, 03 Jun 2017 00:27:37 GMT):
you can always change the type of issue it is

markparz (Sat, 03 Jun 2017 00:29:57 GMT):
Just suggested to and will open epic since several folks are taking pieces no biggie we are working our tails off on all this

bobbiejc (Sat, 03 Jun 2017 18:21:56 GMT):
@markparz I was thinking about 'getting started' after reading the blurb i posted above from the sdk, and I think it would be really beneficial to make that first introduction *significantly* simpler

bobbiejc (Sat, 03 Jun 2017 18:22:33 GMT):
you don't need 2 peers per organizations, and 2 organizations in a consortium with an orderer.... why not the bare minimum to get started writing some chaincode and seeing how it all fits together

bobbiejc (Sat, 03 Jun 2017 18:23:07 GMT):
so 1 peer, 1 orderer. then expand to 2 peers and 1 orderer at the end.

bobbiejc (Sat, 03 Jun 2017 18:23:59 GMT):
because the changing of the environment variables is a pain, and then the logic for doing that in the script has 4 peers, 0,1,2,3, but those then toggle between organizations -- which is fine, but really not necessary for me to kick the tires...

bobbiejc (Sat, 03 Jun 2017 18:24:29 GMT):
and I think the very next thing I wanted to do was modify the chaincode...

bobbiejc (Sat, 03 Jun 2017 18:24:40 GMT):
and finally, call that from some 'hello world nodejs application'

bobbiejc (Sat, 03 Jun 2017 18:25:22 GMT):
I want to do this within the span of an afternoon..;

cbf (Sun, 04 Jun 2017 11:09:43 GMT):
@bobbiejc @markparz @odowdaibm Bobbie, that's what we're doing for the "writing your first blockchain app" which is the new getting started for Ade (app developer persona)

cbf (Sun, 04 Jun 2017 11:10:31 GMT):
There will be a separate GS for the operator persona that will be more complex and closer to the current e2e_cli example, I suspect

odowdaibm (Mon, 05 Jun 2017 11:46:32 GMT):
@bobbiejc Have a read of this - https://drive.google.com/open?id=0B-n-iLEM1iXrZkNpSXNxQ0FZczg and @joe-alewine is starting to put do together this week using this approach.

odowdaibm (Mon, 05 Jun 2017 11:47:30 GMT):
@bobbiejc I think you're on the same page. If you are interested in collaborating on the sample fab-car app please let me know

markparz (Mon, 05 Jun 2017 13:28:22 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=RK8NKwyxWRzGxqrPG) @cbf yup :money_mouth:

jarroyer (Tue, 06 Jun 2017 16:02:02 GMT):
http://hyperledger-fabric.readthedocs.io/en/latest/Setup/Network-setup I keep seeing this link places but it's broken Any idea on the page it's supposed to point to?

nickgaski (Tue, 06 Jun 2017 16:09:33 GMT):
https://github.com/hyperledger/fabric/blob/master/docs/source/Setup/Network-setup.rst - this is very dated. @jarroyer where are we referencing this link?

jarroyer (Tue, 06 Jun 2017 16:13:34 GMT):
@nickgaski it's in the Blockchain explorer documentation and used to be in the Composer docs (not sure if it still is). It's a Fabric Docs link that's why I thought this was the appropriate place to complain :) Thanks!

jimthematrix (Tue, 06 Jun 2017 19:33:14 GMT):
hi @odowdaibm just want to let you know that for the node SDK documentation I'm building a list of short, focused tutorials (as any good library or SDK would have). it'll be using the balance-transfer sample web app as the reference to tell the story and to use it to tease out the code snippets accompanying the texts in each tutorial

jimthematrix (Tue, 06 Jun 2017 19:33:25 GMT):
the list is captured here: https://drive.google.com/file/d/0B-n-iLEM1iXrZkNpSXNxQ0FZczg/view

jimthematrix (Tue, 06 Jun 2017 19:35:09 GMT):
it's basically circling around the capabilities of the SDK, so it's quite different than the "Build Your First Application" content that you guys are working on (which by the way I think is sourly needed so nice work getting that going!)

jimthematrix (Tue, 06 Jun 2017 19:35:38 GMT):
but still want to make sure you guys are aware of this since they may be some small overlap

jimthematrix (Tue, 06 Jun 2017 19:40:29 GMT):
and of course as I mentioned to you before, I'd be happy to contribute to the BYFA effort as needed

cbf (Tue, 06 Jun 2017 20:43:52 GMT):
@jim, why would your samples/GS be different? We should have one seamless set of docs

cbf (Tue, 06 Jun 2017 20:43:52 GMT):
@jimthematrix , why would your samples/GS be different? We should have one seamless set of docs

cbf (Tue, 06 Jun 2017 20:44:09 GMT):
I didn't realize this until recently but the node docs aren't RTD

lehors (Tue, 06 Jun 2017 20:53:54 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=GMPN6b9Q8y6up6RTm) @jarroyer It was the appropriate place to complain actually.. @nickgaski I decided not to make a fuss about all the URLs being changed without much consideration for backward compatibility for now because of all the existing stress already but in the future we should try and be more careful about how we handle URL changes for exactly the reason that it being brought up here: others have bookmarks and links that we are breaking

lehors (Tue, 06 Jun 2017 20:53:54 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=GMPN6b9Q8y6up6RTm) @jarroyer It was the appropriate place to complain actually.. @nickgaski I decided not to make a fuss about all the URLs being changed without much consideration for backward compatibility for now - because of all the existing stress already - but in the future we should try and be more careful about how we handle URL changes for exactly the reason that is being brought up here: others have bookmarks and links that we are breaking

lehors (Tue, 06 Jun 2017 20:55:50 GMT):
normally we could get away with having some http redirects but I don't know what RTD provides on that front (I wouldn't be surprised if it's nothing :-()

markparz (Tue, 06 Jun 2017 21:12:41 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=GMPN6b9Q8y6up6RTm) @jarroyer @sstone1 can you check this out and see if it is in composer doc ?

markparz (Tue, 06 Jun 2017 21:18:09 GMT):
was mentioned that there might be links from composer and explorer, but you might have got it already

sstone1 (Tue, 06 Jun 2017 21:18:34 GMT):
not sure we'd have linked to your dodgy docs from our pages :P

sstone1 (Tue, 06 Jun 2017 21:18:54 GMT):
that link just seems to be missing an .html off the end

cbf (Tue, 06 Jun 2017 23:35:43 GMT):
FYI https://gerrit.hyperledger.org/r/#/c/10247/ some tidying

jimthematrix (Wed, 07 Jun 2017 02:30:36 GMT):
@cbf the node.js community are used to seeing "prettyfied" doc pages like https://fabric-sdk-node.github.io, so we'll have to have a really strong reason to jettison that for the drab RTD pages

jimthematrix (Wed, 07 Jun 2017 03:51:14 GMT):
as for the content of the tutorials and why two separate samples: the "BYFA" content is focused on having lowest possible obstacle to entry, while the node SDK's series of tutorials need to be comprehensive in describing to developers how to use all the features. the balance-transfer sample is designed to be a web applications (but with UI, only REST APIs) to act as a repertoire of code samples for writing node.js based web apps using the node SDK, which is mostly what developers are doing. it's inherently more complex than "Your First Application"

mastersingh24 (Wed, 07 Jun 2017 10:25:18 GMT):
@cbf @jimthematrix : 1) We definitely should be sharing the same fabric configurations where possible 2) I agree with Jim - we cannot use RTD for the Node SDK docs - I thought we covered this several months back

cbf (Wed, 07 Jun 2017 10:26:15 GMT):
for the tutorials? I can certainly understand the API docs being jsdoc but why the tutorial?

mastersingh24 (Wed, 07 Jun 2017 10:27:09 GMT):
But I think we'll be getting the updated tutorial(s) as part of the getting started?

cbf (Wed, 07 Jun 2017 10:27:15 GMT):
we also need the javadoc hosted, but that can be fornext week's release

mastersingh24 (Wed, 07 Jun 2017 10:27:26 GMT):
I guess we'll need to think about on it as we progress post beta

cbf (Wed, 07 Jun 2017 10:27:28 GMT):
yes, but Jim is working on separate tutorials

odowdaibm (Wed, 07 Jun 2017 12:54:35 GMT):
@jimthematrix I'd be in favour of something a bit more like jekyll which would allow this kind of approach. RTD is ok for now, while we get content right, but it's not that pretty

odowdaibm (Wed, 07 Jun 2017 12:55:03 GMT):
Hyperledger Composer use it, and it's pretty nice

odowdaibm (Wed, 07 Jun 2017 12:55:32 GMT):
it is a little more markdown biased though, and I know that might be a source of frustration for some. Personally, I like markdown

cbf (Wed, 07 Jun 2017 12:56:56 GMT):
@odowdaibm that will need to be a post 1.0 thought, though I really think that RTD is fine and we need to stop churn that doesn't add value

joe-alewine (Wed, 07 Jun 2017 15:48:21 GMT):
Hello, all. An initial draft of Writing Your First Application has been written and put up in staging and on gerrit. Here it is staged so people can look at it (note: images are temporary, also this version does not reflect most recent version or changes): http://fabricstaging.readthedocs.io/en/latest/write_first_app.html In gerrit (this version reflects changes/patch sets): https://gerrit.hyperledger.org/r/#/c/10231/ If you look at the staged version and want to make comments, please take a look at gerrit to make sure your comments have not been addressed

odowdaibm (Wed, 07 Jun 2017 16:40:52 GMT):
@cbf, yes agreed, and I am totally fine with that.

cbf (Wed, 07 Jun 2017 16:41:22 GMT):
just want to keep us focused on what matters most, which is the content

cbf (Wed, 07 Jun 2017 16:41:37 GMT):
we can worry about how it is displayed another day

seanbarclay (Wed, 07 Jun 2017 18:40:39 GMT):
@mastersingh24 - can you provide context on your comment above: _2) I agree with Jim - we cannot use RTD for the Node SDK docs - I thought we covered this several months back - but we should link to the SDK docs_ is that because it's using JSDOCS?

seanbarclay (Wed, 07 Jun 2017 18:41:07 GMT):
using JSDOCS with the Node SDK docs

mastersingh24 (Wed, 07 Jun 2017 18:41:37 GMT):
@seanbarclay - this is sexy: https://fabric-sdk-node.github.io/

seanbarclay (Wed, 07 Jun 2017 18:42:24 GMT):
yeah i thought they were using jsdocs to compile and render

mastersingh24 (Wed, 07 Jun 2017 18:42:49 GMT):
and yeah - it uses jsdoc and I tried 15 plugins to render to RST for Sphinx and they were all terrible

mastersingh24 (Wed, 07 Jun 2017 18:43:21 GMT):
jsdoc to markdown is OK - but the default jsdoc templates are much better looking and more usable

seanbarclay (Wed, 07 Jun 2017 18:43:38 GMT):
right- that would be my suggestion- use MD

seanbarclay (Wed, 07 Jun 2017 18:43:52 GMT):
i played with that for the composer gang a while back

seanbarclay (Wed, 07 Jun 2017 18:43:57 GMT):
https://hyperledger.github.io/composer/jsdoc/index.html

mastersingh24 (Wed, 07 Jun 2017 18:44:39 GMT):
I think we should keep using gitpages and jsdoc ;)

mastersingh24 (Wed, 07 Jun 2017 18:45:01 GMT):
We should likely do something similar for the Javadoc as well

seanbarclay (Wed, 07 Jun 2017 18:45:04 GMT):
long as we can find the goods- i'm good

tkuhrt (Thu, 08 Jun 2017 00:31:09 GMT):
@joe-alewine : Yesterday, you posted http://fabricstaging.readthedocs.io/en/latest/write_first_app.html. I ran the steps specified, and I received errors. ``` # Create the channel on peer0. docker exec peer0 peer channel create -o orderer0:7050 -c mychannel -f /etc/hyperledger/configtx/mychannel.tx Received block: [bunch of stuff cut] 2017/06/08 00:27:38 proto: textWriter unindented too far 2017/06/08 00:27:38 proto: textWriter unindented too far 2017/06/08 00:27:38 proto: textWriter unindented too far 2017-06-08 00:27:38.491 UTC [main] main -> INFO 001 Exiting..... # Join peer0 to the channel. docker exec peer0 peer channel join -b mychannel.block 2017-06-08 00:27:38.587 UTC [main] main -> INFO 001 Exiting..... Join Result: # Fetch the channel block on peer1. docker exec peer1 peer channel fetch -o orderer0:7050 -c mychannel Received block: [bunch of stuff cut] 2017/06/08 00:27:38 proto: textWriter unindented too far 2017/06/08 00:27:38 proto: textWriter unindented too far 2017/06/08 00:27:38 proto: textWriter unindented too far 2017-06-08 00:27:38.669 UTC [main] main -> INFO 001 Exiting..... # Join peer1 to the channel. docker exec peer1 peer channel join -b mychannel.block 2017-06-08 00:27:38.769 UTC [main] main -> INFO 001 Exiting..... Join Result: ```

tkuhrt (Thu, 08 Jun 2017 00:34:46 GMT):
Also, it appears that the download of the docker images downloaded the alpha version and not the alpha2 version.

cbf (Thu, 08 Jun 2017 00:40:40 GMT):
@tkuhrt right, because we have not published the beta images

tkuhrt (Thu, 08 Jun 2017 00:41:02 GMT):
But we have published alpha2, right?

gkd720 (Thu, 08 Jun 2017 15:10:32 GMT):
I'm going through the documentation, currently on https://hyperledger-fabric.readthedocs.io/en/latest/blockchain.html, but I can't load some of the images. The first one (https://hyperledger-fabric.readthedocs.io/en/latest/images/Requirements.png) gets a not found. Do they exist? Thanks.

joe-alewine (Thu, 08 Jun 2017 15:13:22 GMT):
@odowdaibm Wanted you to see @tkuhrt comment above

joe-alewine (Thu, 08 Jun 2017 15:20:34 GMT):
@gkd720 Some images had to be scrubbed because they ended up being IBM specific images and therefore not appropriate for Hyperledger documentation. There are new images being created as we speak for a number of documents-in-progress

joe-alewine (Thu, 08 Jun 2017 15:20:34 GMT):
@gkd720 Some images had to be scrubbed because they ended up being IBM specific images and therefore were not appropriate for Hyperledger documentation. There are new images being created as we speak for a number of documents-in-progress

gkd720 (Thu, 08 Jun 2017 15:25:46 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=523sPsAZ2zeLJ3xrt) @joe-alewine Excellent. Thanks.

Asara (Thu, 08 Jun 2017 20:43:39 GMT):
Is there a way to peg documentation to release versions?

Asara (Thu, 08 Jun 2017 20:44:15 GMT):
Right now under readthedocs there is latest and 0.6. Any way to have versions for alpha2/beta/beta2 (if that comes out)?

cbf (Thu, 08 Jun 2017 20:44:28 GMT):
yes, when we cut a branch for 1.0.0 we will in

cbf (Thu, 08 Jun 2017 20:44:28 GMT):
yes, when we cut a branch for 1.0.0 we will pin

Asara (Thu, 08 Jun 2017 20:44:55 GMT):
so until 1.0.0 comes out, the docs are going to just be a moving target?

cbf (Thu, 08 Jun 2017 20:45:24 GMT):
if the docs were more stable/complete that might make sense but we are rapidly evolving the getting started and writing first app experience and that is all for the latest release

Asara (Thu, 08 Jun 2017 20:45:53 GMT):
Example code etc wasn't working until I upgraded to beta today. So it just feels like I was wasting time because the sdk docs were tracking beta, but the infra stuff was all pegged to alpha2

cbf (Thu, 08 Jun 2017 20:46:16 GMT):
yes, to be clear, nothing will change except to make it more relevant and consistent with beta

cbf (Thu, 08 Jun 2017 20:46:35 GMT):
there are no more code changes but bug fixes until post 1.0 so it isn't exactly a moving target

jrosmith (Thu, 08 Jun 2017 20:47:06 GMT):
Ran into the same issue, posted in fabric-sdk-node. Example code was not working with 1.0-alpha2 but now works with 1.0-beta, been working with the example code for the past few days but beta was released today

cbf (Thu, 08 Jun 2017 20:47:15 GMT):
that was point in time because we found a last minute bug in the docs and the sdk published first

jrosmith (Thu, 08 Jun 2017 20:47:28 GMT):
are all the docs and example code up to date with the beta now?

cbf (Thu, 08 Jun 2017 20:48:09 GMT):
though there may be some pockets of inconsistency we may have missed

Asara (Thu, 08 Jun 2017 20:48:15 GMT):
Would it be terrible to tag the current docs as beta, just so people can reference it and know it works (assuming latest docs will change etc)

cbf (Thu, 08 Jun 2017 20:49:09 GMT):
if you want to have alpha2 docs, you can pull the code from GH and build the locally by checking out the tag you want and then cd docs/ and make html

Asara (Thu, 08 Jun 2017 20:49:52 GMT):
I don't need the alpha2 docs, its just for some level of consistency. But if the docs are up to date for beta, its all good for me

cbf (Thu, 08 Jun 2017 21:44:09 GMT):
TBH, the docs weren't supposed to be updated before the release - someone pushed a merge prematurely

ersudiplama (Fri, 09 Jun 2017 14:07:54 GMT):
Hi, do someone know or have documentation of how can we connect two different hyperledger peers in different machine (physically ) and make a blockchain network. Thanks in advance

joe-alewine (Fri, 09 Jun 2017 14:21:38 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=rRMFadZc6oLFuCoZ2) @ersudiplama That's in the works. I can't give you exact estimate but it is something that's being worked on.

joe-alewine (Fri, 09 Jun 2017 14:21:38 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=rRMFadZc6oLFuCoZ2) @ersudiplama That's in the works. I don't want to pin down the people who are working on it but there should be a draft of in the next few weeks.

joe-alewine (Fri, 09 Jun 2017 14:21:38 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=rRMFadZc6oLFuCoZ2) @ersudiplama That's in the works. I don't want to pin down the people who are working on it but there should be a draft of it in the next few weeks.

joe-alewine (Fri, 09 Jun 2017 14:21:38 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=rRMFadZc6oLFuCoZ2) @ersudiplama That's in the works.

markparz (Fri, 09 Jun 2017 15:06:30 GMT):
https://ibm.zoom.us/my/ajodowd Doc group discussion

nasht00 (Sun, 11 Jun 2017 13:32:27 GMT):
Hello, I am following the instructions here: http://hyperledger-fabric.readthedocs.io/en/latest/getting_started.html The section "Want to run it now?" does not work

nasht00 (Sun, 11 Jun 2017 13:32:45 GMT):
`Error: Error getting chaincode code chaincode: Error getting chaincode package bytes: Error obtaining imports: go list: failed with error: "exit status 1" can't load package: package github.com/hyperledger/fabric/examples/chaincode/go/chaincode_example02: no buildable Go source files in /opt/gopath/src/github.com/hyperledger/fabric/examples/chaincode/go/chaincode_example02`

nasht00 (Sun, 11 Jun 2017 13:33:08 GMT):
I didn't write any line of code, just wanted to run the example as-is.

nasht00 (Sun, 11 Jun 2017 13:59:06 GMT):
I've opened a defect: https://jira.hyperledger.org/browse/FAB-4558

gkd720 (Sun, 11 Jun 2017 18:07:21 GMT):
I went through the steps manually a few days ago, and that worked without incident, so that's still an option for playing with this stuff. And the "./network_setup.sh down" worked too.

gkd720 (Sun, 11 Jun 2017 18:07:21 GMT):
@nasht00 I went through the steps manually a few days ago, and that worked without incident, so that's still an option for playing with this stuff. And the "./network_setup.sh down" worked too.

gkd720 (Sun, 11 Jun 2017 18:16:30 GMT):
I've been going through the documentation, and things are starting to clear up, so I couldn't wait to go through the "Best Practices" (https://hyperledger-fabric.readthedocs.io/en/latest/best_practices.html). But it's not there yet. Is there any ETA? And would this be the document that would describe a typical sequence to plan out and develop an application, decide how many clients, peers, orderers, etc. there should be, what machines they should run on (I'm assuming the demo in "getting started" having all functions in a Docker container is just an easy way to exhibit functionality?), etc? Thanks.

markparz (Mon, 12 Jun 2017 14:36:56 GMT):
hi @gkd720 there are a couple of items that would be awesome to have you look at. First is extremely early start of a doc, that is networking planning... and operational considerations. We might thrash and split into other docs... https://gerrit.hyperledger.org/r/#/c/8593/10/docs/source/planning_guide.rst

markparz (Mon, 12 Jun 2017 14:37:19 GMT):
The second is https://gerrit.hyperledger.org/r/#/c/10231/13/docs/source/write_first_app.rst regarding app development... writing my first application

markparz (Mon, 12 Jun 2017 14:37:49 GMT):
these are in gerrit and feel free to add any comments in the review or post here with me and @joe-alewine noted

gkd720 (Mon, 12 Jun 2017 18:11:07 GMT):
@markparz Thanks. Yes, those documents are more of what I had in mind to learn from. They're already sparking more questions. Should I ask them here as they come up, group into a list of questions, ask in the "general" channel? I might consider trying to set up a network/application on my own from what I know from the "Getting started" documentation, as I would expect this to generate a (probably huge) list of questions.

markparz (Mon, 12 Jun 2017 18:51:17 GMT):
you can ask them here, and as they become bigger doc issues we can open jira items

cbf (Tue, 13 Jun 2017 02:08:11 GMT):
@markparz @odowdaibm https://gerrit.hyperledger.org/r/#/c/10507/ stacked CRs that implement build your first network tutorial

cbf (Tue, 13 Jun 2017 10:30:56 GMT):
@odowdaibm are you working on a persona page for the docs that can be referenced?

cbf (Tue, 13 Jun 2017 23:54:47 GMT):
https://gerrit.hyperledger.org/r/#/c/9263/ With Binh's permission, I hijacked the chaincode tutorial and have refactored for Ade and Noah perspectives

cbf (Tue, 13 Jun 2017 23:55:05 GMT):
it is still a WIP but any comments welcome

kostas (Wed, 14 Jun 2017 02:30:53 GMT):
I'd like to link from one `.rst` doc to another - how do I do that?

SarahMills (Thu, 15 Jun 2017 17:52:28 GMT):
Initial documentation graphics and icons up for review and feedback in the *subtasks* of https://jira.hyperledger.org/browse/FAB-4234 and on @odowdaibm 's call tomorrow. Thanks!

odowdaibm (Fri, 16 Jun 2017 13:24:00 GMT):
@SarahMills thanks for this! Looking forward to goin through it on today's call

odowdaibm (Fri, 16 Jun 2017 14:55:10 GMT):
@here, the documentation workgroup call starts in 5 mins, if you're interested in joining.

joe-alewine (Fri, 16 Jun 2017 14:56:45 GMT):
Here's the link to that workgroup: https://ibm.zoom.us/my/ajodowd

lucie (Fri, 16 Jun 2017 16:10:29 GMT):
@odowdaibm link to jira: https://jira.hyperledger.org/browse/FAB-4234 link to google drive icons: https://docs.google.com/spreadsheets/d/1-kGOuaOW73-U4ufojDKbYnZ0bN9xoZhXA1hb-mgWMvA/edit?usp=sharing

anthonys (Fri, 16 Jun 2017 16:16:04 GMT):
Thanks for being so welcoming on the call! Hoping to participate & contribute more to the documentation as I dive deeper into the abstractions. How can I get access to the Jira? Will definitely have feedback once I’m ramped up

anthonys (Fri, 16 Jun 2017 16:24:51 GMT):
Also, some thoughts about green from the artist Kandinsky :P > In the hierarchy of colors, green represents the social middle class, self-satisfied, immovable, narrow… > Absolute green is the most restful color, lacking any undertone of joy, grief, or passion.

gauthampamu (Fri, 16 Jun 2017 16:41:44 GMT):
https://chat.hyperledger.org/channel/fabric?msg=o99SZksW88PLqw4BT

gauthampamu (Fri, 16 Jun 2017 16:42:25 GMT):
For the section Install and Instantiate, it would help if you add note that you should run these commands on the cli container

SarahMills (Fri, 16 Jun 2017 16:47:41 GMT):
Re: Green For now we need to focus on the content, as until this ticket is resolved https://jira.hyperledger.org/browse/FAB-2185, our images needs to be consistent with previous work (like here: http://hyperledger-fabric.readthedocs.io/en/latest/txflow.html). We'll change everything once branding and colors get decided. However, we will go back through and make sure accessibility and contrast are addressed :)

SarahMills (Fri, 16 Jun 2017 16:47:41 GMT):
Re: Green For now we need to focus on the content, as until this ticket is resolved https://jira.hyperledger.org/browse/FAB-2185, our images need to be consistent with previous work (like here: http://hyperledger-fabric.readthedocs.io/en/latest/txflow.html). We'll change everything once branding and colors get decided. However, we will go back through and make sure accessibility and contrast are addressed :)

odowdaibm (Fri, 16 Jun 2017 16:50:51 GMT):
@anthonys It was great for you to join, and to have another Anthony in the team. As @sarah says, we all need to focus on this topic right now, and your input via JIRA is incredibly helpful, so thanks!

odowdaibm (Fri, 16 Jun 2017 16:50:51 GMT):
@anthonys It was great for you to join, and to have another Anthony in the team. As @SarahMills says, we all need to focus on this topic right now, and your input via JIRA is incredibly helpful, so thanks!

joe-alewine (Fri, 16 Jun 2017 16:51:23 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=LukgF7hDkqAFyH5CQ) @anthonys Haha. That's great. However, and not to tread upon the ground of the #fabricartcriticism channel, I'd like to say that Kandisky's paintings are almost amazingly intense in their repulsiveness :smile:

tkuhrt (Fri, 16 Jun 2017 18:03:07 GMT):
https://chat.hyperledger.org/channel/fabric-documentation?msg=QyBXcHsy9XZqMRuFx : @anthonys : to gain access to Jira, you will need to log in with your Linux Foundation ID. This is the ID that you created to gain access to Rocket.Chat. So, should be `anthonys` for username and whatever you chose as the password for your Linux Foundation ID.

jimthematrix (Fri, 16 Jun 2017 18:11:40 GMT):
@nickgaski @odowdaibm is there plans to publish the protobuf API references? in a few places in the node SDK API reference I'd like to reference the protobuf definition of a few message types

cbf (Sat, 17 Jun 2017 02:43:42 GMT):
@anthonys https://jira.hyperldger.org - in fact, you will find that almost all of the services follow this pattern.

cbf (Sat, 17 Jun 2017 02:44:25 GMT):
you will also find just about everything you need here http://hyperledger-fabric.readthedocs.io/en/latest/CONTRIBUTING.html

cbf (Sun, 18 Jun 2017 02:10:32 GMT):
@odowdaibm @joe-alewine @markparz I have left some comments on https://gerrit.hyperledger.org/r/#/c/10231/14

cbf (Sun, 18 Jun 2017 02:11:40 GMT):
and I have also submitted the following CR that adds setup for the basic network that the app will use (well, assuming we agree to adopt it) https://gerrit.hyperledger.org/r/#/c/10743/

cbf (Sun, 18 Jun 2017 02:13:12 GMT):
this CR basically refactors Matt White's basic network setup for Composer (as used in the WYFA) but a) adds it to Fabric and b) simplifies it considerably (the Composer setup is unnecessarily complexified by virtue of trying to work for different versions of Fabric)

cbf (Tue, 20 Jun 2017 02:15:10 GMT):
@here https://gerrit.hyperledger.org/r/#/admin/projects/fabric-samples has been created to hold our sample applications - please add the writing your first app here as a subdirectory of the repository

jimthematrix (Tue, 20 Jun 2017 16:58:09 GMT):
@nickgaski I see there's a "Troubleshooting and FAQs" section in RTD, but only FAQs content so far. is there a list of troubleshooting topics to write? from the sdk channels we can collect a large number of recurring questions and user errors that would be useful to document as troubleshooting topics

markparz (Tue, 20 Jun 2017 19:46:33 GMT):
That would be great Jim, we're trying to balance the readthedocs pieces with stack overflow...

nickgaski (Tue, 20 Jun 2017 21:29:58 GMT):
yea I've aggregated a few so far. There's a gerrit open currently and I'll be adding the chaincode vendor dependencies error to it as well

nickgaski (Tue, 20 Jun 2017 21:33:18 GMT):
https://gerrit.hyperledger.org/r/#/c/10719/

ffilozov1 (Tue, 20 Jun 2017 21:48:18 GMT):
According to the latest documentation, there should be a `fabric-samples/first-network directory`, but there isn't one. Is the documentation ahead of the curve?

cbf (Tue, 20 Jun 2017 23:22:16 GMT):
@bretharrison If you don't mind, I'll work on https://gerrit.hyperledger.org/r/#/c/10795/ and align for the release with the incoming changes to fabric docs

cbf (Tue, 20 Jun 2017 23:23:14 GMT):
@markparz IMO, we probably should put all troubleshooting advise in SO and refer people to the various tags we're using

cbf (Tue, 20 Jun 2017 23:23:34 GMT):
I think it will only confuse people to have to look in multiple places

joe-alewine (Tue, 20 Jun 2017 23:43:14 GMT):
Newest version of "Writing Your First App" now on gerrit: https://gerrit.hyperledger.org/r/#/c/10231/18 I don't know why it says "Cannot Merge", though this version is obviously not getting merged so I'm not sure it matters. There is still a lot to add here (the one line code download, for example -- the network and app are hard to download otherwise -- as well as the edits to the "Update" section), but there are a lot of changes here to look at

markparz (Wed, 21 Jun 2017 00:33:17 GMT):
@cbf that works we have 99% of all there already

jimthematrix (Wed, 21 Jun 2017 17:12:49 GMT):
+1 for using SO so it's easier to search, we have so many questions that get asked over and over again in the channels. so we should basically start redirecting folks to SO if they ask technical questions on the channel? I feel like for all areas (node sdk, java sdk, fabric) the channels have become the mainstream channels to get support

gauthampamu (Thu, 22 Jun 2017 01:50:02 GMT):
I have a questions on Transaction Life Cycle and Fabric CA. In the Fabric Transaction life cycle, does any of the server Orderers or Peer make any API calls to certificate authority. Also does any of the peers make API calls to CA for any peer to peer communication.

jeffgarratt (Thu, 22 Jun 2017 02:58:59 GMT):
@gauthampamu no, the peers and orderes do NOT currently communicate with fabric-ca

jeffgarratt (Thu, 22 Jun 2017 03:00:17 GMT):
wrt to peer to peer communication, CA info is referenced from the channel specific configuration (i.e. the MSPConfig structure)

SarahMills (Fri, 23 Jun 2017 18:02:06 GMT):
Happy Friday everyone! The next round of icons is up for your feedback: https://jira.hyperledger.org/browse/FAB-4604

clessor (Fri, 23 Jun 2017 19:27:12 GMT):
Hello. I have a troubleshooting question from the fabric "getting started" instructions. Is this the correct forum? Or should I go right to the fabric group?

cbf (Fri, 23 Jun 2017 21:55:28 GMT):
@clessor the getting started is just about to be completely revamped when we release the v1.0.0-rc1 release this evening

mastersingh24 (Mon, 26 Jun 2017 14:26:22 GMT):
@nickgaski - can you take a look at https://gerrit.hyperledger.org/r/#/c/11149/ ?

nickgaski (Mon, 26 Jun 2017 14:33:45 GMT):
couple formatting things, will cherry pick and fix for you

mastersingh24 (Mon, 26 Jun 2017 14:58:21 GMT):
I'm too lazy to read how to build the docs locally ;)

Asara (Mon, 26 Jun 2017 15:38:53 GMT):
http://hyperledger-fabric.readthedocs.io/en/latest/samples.html

Asara (Mon, 26 Jun 2017 15:39:07 GMT):
Wouldn't nothing be named x86_64 since everything is set to amd64?

latitiah (Mon, 26 Jun 2017 18:49:54 GMT):
Is there a document (or a plan to document) a troubleshooting guide that outlines common errors and the possible cause for those failures/errors?

nickgaski (Mon, 26 Jun 2017 18:55:25 GMT):
@latitiah - we're trying to post everything on SO

vdods (Mon, 26 Jun 2017 21:13:29 GMT):
Hi there -- whoever is in charge of http://hyperledger-fabric.readthedocs.io -- could you please add version info to the generated docs, as well as time and date generated? Ideally the version would be something like v1.0.0-beta or v1.0.0-rc1, and would be specify the git commit it came from (or git tag, which hopefully would be the same as the version name). The time and date that the docs were generated would also be useful.

vdods (Mon, 26 Jun 2017 21:13:57 GMT):
"latest" is not terribly helpful, especially if there's no indication of the time/date it was generated :)

mastersingh24 (Mon, 26 Jun 2017 22:20:59 GMT):
@vdods - funny you should mention that. You'll notice that there are now 3 versions of the docs: - latest - master - 1.0.0-beta

mastersingh24 (Mon, 26 Jun 2017 22:21:32 GMT):
there's also links to view the builds as well in the versions dropdown at the bottom

mastersingh24 (Mon, 26 Jun 2017 22:21:41 GMT):
http://readthedocs.org/projects/hyperledger-fabric/versions/

mastersingh24 (Mon, 26 Jun 2017 22:21:53 GMT):
http://readthedocs.org/projects/hyperledger-fabric/builds/

vdods (Mon, 26 Jun 2017 22:25:14 GMT):
Ah ok.. The link to select the version is not very obvious.

vdods (Mon, 26 Jun 2017 22:27:10 GMT):
Perhaps a link to to "root" http://readthedocs.org/projects/hyperledger-fabric/ would be useful -- the existence of the two links you just posted wasn't obvious either.

vdods (Mon, 26 Jun 2017 22:27:10 GMT):
Perhaps a link to to "root" http://readthedocs.org/projects/hyperledger-fabric/ within the docs would be useful -- the existence of the two links you just posted wasn't obvious either.

vdods (Mon, 26 Jun 2017 22:31:08 GMT):
A common theme in my experience with the many components of HLF is that there is very little indication of the larger context -- it's sort of assumed that the reader already knows the larger context, but that's not necessarily true for an outsider or newcomer. An example is that I didn't know about the "version" capability of readthedocs.org. Another example is what the return values of ChaincodeStubInterface methods that return byte[] are -- how to interpret them -- what format, how to use them, and how to learn more about the relevant concepts (e.g. x509 certs).

newint (Tue, 27 Jun 2017 12:02:44 GMT):
Hello! I am studying e2e_cli example and I possibly have found two inaccuracies in https://github.com/hyperledger/fabric/blob/master/examples/e2e_cli/end-to-end.rst 1. *Create channel* section. Seems like value of flag *--cafile* -`/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/cacerts/ca.example.com-cert.pem` is not more valid. According to `script.sh` it should be `/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem` Also in all other commands, where is used `--cafile` should be changed value. 2. *peer chaincode instantiate* section. According to *help* of this command, flag `-p /path/to/chaincode` is not more supported (this is very logical, as we provide name of chaincode). After removing this flag, everything perfectly works. If I am right, I can do pull request by myself, and it will be just merged. p.s. Thanks for such detailed and well written documentation!!!

weeds (Tue, 27 Jun 2017 15:39:43 GMT):
i posted a comment on fabric-release that the people on documentation might want to read today-

odowdaibm (Thu, 29 Jun 2017 16:59:31 GMT):
@here Hi everyone. Re the WYFA app topic (http://hyperledger-fabric.readthedocs.io/en/latest/write_first_app.html) I would like folks to comment here as to why we're adding low level detail so early in this topic. I understand the desire to have other topics, and more detail, but loading them in WYFA is not maybe not the best place?

nehalshah50 (Thu, 29 Jun 2017 21:19:13 GMT):
Hi everyone...Just wanted to give my feedback about the documentation. I find some of the topic like membership services, orderer little confusing. A good visual diagram would be useful.

cbf (Fri, 30 Jun 2017 11:49:01 GMT):
@nehalshah50 thanks... it would help if you could provide specific feedback in the form of a JIRA report (s) seeking improvement. Specifically, it would help if you could elaborate a bit on what is confusing about these topics

yuki-kon (Fri, 30 Jun 2017 20:51:45 GMT):
Let me ask about prerequisites for Writing Your First Application. When executing "npm install" to set up fabric-sdk-node, I got an error message like "Error: Can't find Python executable "python", you can set the PYTHON env variable.". After installing python 2.7, "npm install" finished successfully. Does anyone have the same problem? If anyone has the same problem, I will submit an issue to JIRA to add "python 2.7" to prerequisites.

cbf (Fri, 30 Jun 2017 23:18:29 GMT):
@yuki-kon interesting... have not seen that previously... what OS and version are you running?

yuki-kon (Fri, 30 Jun 2017 23:25:47 GMT):
@cbf Thanks! I'm running sample on Ubuntu 16.04. Python 3.5 has been installed with Ubuntu 16.04 already. But "npm install" required python 2.7.

mrkiouak (Sat, 01 Jul 2017 14:23:28 GMT):
its specifically node-gyp, and node-gyp pre that require python 2.7

Rachitga (Mon, 03 Jul 2017 09:11:45 GMT):
Hello all, I was trying to run my orderer with kafka instead of solo, is there any documentation mentioning the changes in the docker-compose.yaml file and the configtx.yaml file??

yuki-kon (Mon, 03 Jul 2017 16:54:49 GMT):
@mrkiouak Thanks! As you mentioned, node-gyp requires python 2.7.

tkuhrt (Mon, 03 Jul 2017 19:09:25 GMT):
@Rachitga : Have you seen this: http://hyperledger-fabric.readthedocs.io/en/latest/kafka.html. At the end it talks about sample yaml files that you can look at.

Rachitga (Tue, 04 Jul 2017 04:49:45 GMT):
@tkuhrt , thanks!, I hadn't looked at this documentation.

weeds (Tue, 04 Jul 2017 11:31:49 GMT):
Hi @markparz @nickgaski there was an interesting conversation on the maintainers channel about what is/is not documented. I suggesting going to look there (happened over the weekend) Thanks.

markparz (Wed, 05 Jul 2017 14:05:01 GMT):
Cool, thanks, hope we got some Jira items out of it :)

jarroyer (Thu, 06 Jul 2017 15:49:19 GMT):
Could a blurb on read and write permissions be added to one of the Channel Configuration sections? Apparently its possible to delegate the permissions within a channel: https://stackoverflow.com/questions/43017514/roles-readwrite-in-hyperledger

jarroyer (Thu, 06 Jul 2017 15:49:42 GMT):
I just don't see anything in the documentation about it.

jarroyer (Thu, 06 Jul 2017 15:50:04 GMT):
Not sure on the syntax for changing it

tkuhrt (Thu, 06 Jul 2017 19:58:25 GMT):
@jarroyer : Would you be willing to enter an issue for this in Jira (https://jira.hyperledger.org/secure/Dashboard.jspa) for the FAB project? Jira utilizes the Linux Foundation ID that you set up to enter rocket.chat. Happy to help you with the process if needed.

jarroyer (Thu, 06 Jul 2017 20:16:50 GMT):
I just did it. First time submitting a JIRA ticket in the community so if something is wrong with it let me know :)

tkuhrt (Thu, 06 Jul 2017 20:21:42 GMT):
Thanks, @jarroyer. Looks good to me.

tkuhrt (Thu, 06 Jul 2017 20:21:52 GMT):
https://jira.hyperledger.org/browse/FAB-5199

kuperlen (Fri, 07 Jul 2017 22:36:39 GMT):
Hi, not sure if this is a right thread, but it looks like e2e example doc needs new paths for --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem in peer channel create, peer chaincode instantiate, and peer chaincode invoke examples for example02 and marbles02 examples. Examples stopped working with the old paths starting with fabric v1.0.0-rc1 tag.

rishabh1102 (Mon, 10 Jul 2017 12:31:32 GMT):
There is no proper documentation in terms of what one should do when they have to create their own network with their own specifications And how to connect to it using the SDKs The only thing explained properly is how to set up the examples already coded

rishabh1102 (Mon, 10 Jul 2017 12:33:07 GMT):
I want to set up my own network with 2 peers (where they both are endorsers) and one orderer with my own chaincode and connect to this using the Java or node sdk, but given the current documentation, I have no idea how to go about doing that

joe-alewine (Mon, 10 Jul 2017 20:50:39 GMT):
The newest patch set (w/updated images) has been uploaded to Mark Parzygnat's staging site. I tried to reflect the comments from a wide variety of people. Take a look, comment. http://fabricstaging.readthedocs.io/en/latest/write_first_app.html

joe-alewine (Mon, 10 Jul 2017 20:50:39 GMT):
The newest patch set of the Writing Your First App doc (w/updated images) has been uploaded to Mark Parzygnat's staging site. I tried to reflect the comments from a wide variety of people. Take a look, comment. http://fabricstaging.readthedocs.io/en/latest/write_first_app.html

tkuhrt (Tue, 11 Jul 2017 17:52:56 GMT):
Found the following document (with no title) when doing a search of the documents: http://hyperledger-fabric.readthedocs.io/en/latest/architecture.html

tkuhrt (Tue, 11 Jul 2017 17:54:55 GMT):
Created https://jira.hyperledger.org/browse/FAB-5259

jrosmith (Wed, 12 Jul 2017 15:40:53 GMT):
hey all, noticed an issue on https://fabric-sdk-node.github.io/FabricCAClient.html#register__anchor, it lists the arguments as `register(enrollmentID, enrollmentSecret, role, affiliation, maxEnrollments, attrs, signingIdentity)`, but when looking at the SDK and the actual `FabricCaClientImpl.js` its documented as: ``` * Register the member and return an enrollment secret. * @param {Object} req Registration request with the following fields: *
- enrollmentID {string}. ID which will be used for enrollment *
- enrollmentSecret {string}. Optional enrollment secret to set for the registered user. * If not provided, the server will generate one. *
- role {string}. An arbitrary string representing a role value for the user *
- affiliation {string}. Affiliation with which this user will be associated, like a company or an organization *
- maxEnrollments {number}. The maximum number of times this user will be permitted to enroll *
- attrs {{@link KeyValueAttribute}[]}. Array of key/value attributes to assign to the user. * @param registrar {User}. The identity of the registrar (i.e. who is performing the registration) * @returns {Promise} The enrollment secret to use when this user enrolls ```

ersudiplama (Wed, 12 Jul 2017 17:27:41 GMT):
Hi, Do anyone have any documentations related to multi host networking between hyper-ledger peers ? if so can someone share that doc? As I tried with docker swarm and other stuff where it throws alot of errors or the peers don't communicate with each other.

cbf (Thu, 13 Jul 2017 12:59:22 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=bp47Bj4RnT6uzHqkM) @ersudiplama we've done this a bunch. I think you make a good point that we haven't got a specific documentation section that describes how to do this

ersudiplama (Thu, 13 Jul 2017 13:29:23 GMT):
@cbf Thank you for mentioning that. We have achieved the multi host networking between peers residing at different physical machines using docker swarm but we are not sure that as the best option or not.

ersudiplama (Thu, 13 Jul 2017 13:29:55 GMT):
While trying to get multi host networking between peers, we had a lot of unknown errors ( unknown to us) but when we used new images of fabric, it worked well ( with some error for some time). So if anyone have some documentation which explains about options and standards which we can follow for achieving that. Then it would add great value in creating distribute blockchian network between peers residing at different servers or physical machine. Thank you in advance

yuleeandrea (Fri, 14 Jul 2017 16:04:44 GMT):
FYI - hi Anthony we took your advice to visualize the first app UI for users. I have created a Jira ticket for gathering comments/feedback from you and Joe before going any further: https://jira.hyperledger.org/browse/FAB-5302 there’s a pdf attached to this ticket. You can also see a prototype in invision and leave comment there as well: https://ibm.invisionapp.com/share/CMCJJ7HZP This is still an early stage of the UI/wires, there are some phrases may need your help to modify properly. Thank you. @joe-alewine @odowdaibm ^^

IvanPopkov (Mon, 17 Jul 2017 12:34:21 GMT):
https://chat.hyperledger.org/channel/fabric?msg=26bKcv5HGrS8tx2Ty Any glues, guys?

cbf (Mon, 17 Jul 2017 13:09:17 GMT):
@IvanPopkov https://jira.hyperledger.org/browse/FAB-5336

imtiyazbhat (Mon, 17 Jul 2017 16:40:20 GMT):
Hi there .... I have setup hyperledger and deployed basic sample fabcar. Next I want to know how to deploy a solution over a network and communicate with it using different peers (different machine). Documentation I am referring is just helpful for fabler sample "http://hyperledger-fabric.readthedocs.io/en/latest/write_first_app.html". Can anyone direct me help out deploying over network.

Rachitga (Tue, 18 Jul 2017 16:08:23 GMT):
Hi all, can anyone point me the documentation on the eventhub service?

rohitaneja8 (Wed, 19 Jul 2017 07:43:26 GMT):
i dont know incharge of https://hyperledger-fabric.readthedocs.io/en/v0.6/starter/fabric-starter-kit.html but seems version 0.6 docs are pulled down or hidden, get *permission denied* error when try to access it. Any advice?

rohitaneja8 (Wed, 19 Jul 2017 07:54:14 GMT):
Got it, can compile it myself from https://github.com/hyperledger/fabric/tree/v0.6/docs

mastersingh24 (Wed, 19 Jul 2017 13:36:55 GMT):
@rohitaneja8 - The community does not actively support v0.6 any more. Any reason you are not moving to the recently released v1.0.0 ?

jarroyer (Wed, 19 Jul 2017 16:23:24 GMT):
Is there any list of all the possible fields that can be used in the configtx.yaml file that is passed to the configtxgen tool? it seems every one I find through the various examples uses different fields and such

gauthampamu (Wed, 19 Jul 2017 22:44:32 GMT):
Hi Everyone, The first-network sample in Fabric example creates user User1 and Admin. I wanted to understand how to use these users from Nodejs application. It creates keystore, signercerts,admincerts and cacerts. How should we use these certs to login to the network to invoke or execute the query. In the wallet folder for fabcar, we have three files but here we have the keystore which is priv key and signercerts is the public key, how should we create the other file (like PeerAdmin in fabcar/cred) or do we need that file for the Nodejs application.

cbf (Thu, 20 Jul 2017 12:55:42 GMT):
@gauthampamu would you mind adding a JIRA requesting this be added to the docs so we can track it? Thanks!

gauthampamu (Thu, 20 Jul 2017 13:04:08 GMT):
Done https://jira.hyperledger.org/browse/FAB-5397

vukolic (Fri, 21 Jul 2017 14:00:05 GMT):
quick Q - who is maintaining http://hyperledger-fabric.readthedocs.io/en/latest/

vukolic (Fri, 21 Jul 2017 14:04:02 GMT):
We need to remove cross links to vukolic.com in http://hyperledger-fabric.readthedocs.io/en/latest/arch-deep-dive.html

CodeReaper (Tue, 25 Jul 2017 06:05:39 GMT):
Can anyone tell me how to make an actual environment for fabric. how to run peers separately in different machines?

yacovm (Tue, 25 Jul 2017 06:50:38 GMT):
@CodeReaper you can either use an orchestration engine for docker like swarm or kubernetes or just run them on bare metal VMs

CodeReaper (Tue, 25 Jul 2017 07:39:30 GMT):
@yacovm will look into it. thanks man.

yacovm (Tue, 25 Jul 2017 07:40:38 GMT):
I have a script that deploys to bare metal VMs assuming you have SSH keys configured: https://github.com/yacovm/fabricDeployment

cbf (Tue, 25 Jul 2017 13:42:17 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=i9GGL5rbv3XKeEGWQ) @CodeReaper https://chat.hyperledger.org/channel/fabric-questions?msg=GmwGv285tmdB98Bhe

kostas (Wed, 26 Jul 2017 11:54:00 GMT):
http://hyperledger-fabric.readthedocs.io/en/latest/arch-deep-dive.html

kostas (Wed, 26 Jul 2017 11:55:19 GMT):
Are `\bot` and `\in` supposed to be displayed like that, or are we dealing with formatting errors?

nickgaski (Wed, 26 Jul 2017 15:59:39 GMT):
does that syntax not make sense in this instance? that's how they are coded in the source

kostas (Wed, 26 Jul 2017 16:25:31 GMT):
@nickgaski: I'm fairly certain that this is LaTeX markup. \bot for example is https://en.m.wikipedia.org/wiki/Up_tack

nickgaski (Wed, 26 Jul 2017 16:31:30 GMT):
https://github.com/hyperledger/fabric/blob/master/proposals/r1/Next-Consensus-Architecture-Proposal.md#121-state

nickgaski (Wed, 26 Jul 2017 16:31:41 GMT):
@kostas - it seems to be mirrored against this

kostas (Wed, 26 Jul 2017 16:45:08 GMT):
@nickgaski: This syntax makes no sense as best as I can tell. Do we know the original author?

kostas (Wed, 26 Jul 2017 16:45:08 GMT):
@nickgaski: This displayed text makes no sense as best as I can tell. Do we know the original author?

nickgaski (Wed, 26 Jul 2017 16:46:19 GMT):
let's ask Dave or Manish how the key vals should be represented. This design doc is from Nov of last year I think!

dave.enyeart (Wed, 26 Jul 2017 18:25:36 GMT):
That document predates my time, I believe the author of that part was @vukolic . @vukolic, how to represent \bot in a way that the layman will understand it?

dave.enyeart (Wed, 26 Jul 2017 18:25:36 GMT):
That document predates my time, I believe the author of that part was @vukolic . @vukolic, how to represent `\bot` in a way that the layman will understand it?

dave.enyeart (Wed, 26 Jul 2017 18:27:10 GMT):
similar question for `k\in K` and `v\in V`

gauthampamu (Tue, 01 Aug 2017 03:22:11 GMT):
https://chat.hyperledger.org/channel/fabric-ca?msg=unDBhDa29CNk2GfPw

gauthampamu (Tue, 01 Aug 2017 21:36:35 GMT):
http://hyperledger-fabric.readthedocs.io/en/latest/chaincode4noah.html Documentation explains that other owners will have to sign the package using the command peer chaincode signpackage ccpack.out signedccpack.out. The documentation does not explain where they should run this command and what environment variables we have to setup before execute the command. How does the peer command know which certificates to use to sign the package. It does not provide details on how to use the signed package file signedccpack.out in later steps. If you look at the instructions for installing or instantiating the chaincode, I don't see any references to the signedccpack.out file.

DarshanBc (Wed, 02 Aug 2017 05:59:49 GMT):
Hi I am trying to execute fabcar example but when I execute node query.js its giving an error fabric-client was not found

nickgaski (Wed, 02 Aug 2017 13:59:48 GMT):
Hi @DarshanBc - please make sure you install the node modules (i.e. run `npm install`) from directly within the /fabcar sub-directory. Also please check that you have python 2.7 installed on your machine. We see incompatibility with 3.x versions. Get rid of your node modules (`rm -rf node_modules`), make sure you revert the python version and then try installing again. Feel free to direct message me and I will help you sort

nickgaski (Wed, 02 Aug 2017 13:59:48 GMT):
Hi @DarshanBc - please make sure you install the node modules (i.e. run `npm install`) from directly within the /fabcar sub-directory. Also please check that you have python 2.7 installed on your machine. We see incompatibility with 3.x versions. Get rid of your node modules - `rm -rf node_modules` - make sure you revert the python version and then try installing again. Feel free to direct message me and I will help you sort

subbu165 (Wed, 02 Aug 2017 14:22:18 GMT):
Hi, is there any example in hyperledger beta version using couch DB in the GitHub?

nickgaski (Wed, 02 Aug 2017 15:07:32 GMT):
@subbu165 - you want documentation that runs against the "beta" tagged images? That is my interpretation of your ask. Look at this past version of getting started, especially the bottom of the page, as it deals with the marbles chaincode and using couch for the state DB. - https://github.com/hyperledger/fabric/blob/ebea996283d560dd5c51651559ce6f3673c87048/docs/source/getting_started.rst

subbu165 (Wed, 02 Aug 2017 16:56:20 GMT):
@nickgaski Yes. Thanks I will go through this

cbf (Wed, 02 Aug 2017 18:51:06 GMT):
@subbu165 FWIW, you can build a release-specific version of the docs by cloning the repo, checking out the release and running `make html` in the docs directory

gauthampamu (Thu, 03 Aug 2017 03:16:25 GMT):
http://hyperledger-fabric.readthedocs.io/en/latest/Fabric-FAQ.html?highlight=Security For the question how I ensure data privacy ? In the response, it mentions you can set visibility settings. Can you please explain whether it is really supported in v1.0 and also how to set this settings and what is the API for it. Do we have any sample programs to play with the settings. "Second, within a channel you can restrict the input data to chaincode to the set of endorsers only, by using visibility settings. The visibility setting will determine whether input and output chaincode data is included in the submitted transaction, versus just output data. "

gauthampamu (Thu, 03 Aug 2017 03:18:02 GMT):
It would helpful to have document that explains the production/security considerations when implementing the network on premise.

gauthampamu (Thu, 03 Aug 2017 03:24:42 GMT):
For example: Data in-transit is not encrypted via TLS by default, we will have to enable it for all the peers and orderers. So I would assume that for production environment, you will have to enable it. On the main page we example hyperledger fabric is enterprise ready network security but we don't have any documentation that make the case on how it is enterprise ready. So it would helpful to have a security.

gauthampamu (Thu, 03 Aug 2017 03:26:22 GMT):
When you search on Security, you find one page on Security Model but it has very limited information. It is difficult to conclude how the security works.

DarshanBc (Thu, 03 Aug 2017 08:35:23 GMT):
for the fabcar example from where does chaincode gets installed I am trying to get it from .sh script but I am not able to understand

DarshanBc (Thu, 03 Aug 2017 11:43:54 GMT):
n this link they say there is a sample .js file https://fabric-sdk-node.readthedocs.io/en/latest/sample-standalone-app they say it is at https://raw.githubusercontent.com/hyperledger/fabric/master/examples/sdk/node/app.js but It gives error 404 can you help me in getting sample app

jimthematrix (Thu, 03 Aug 2017 12:33:31 GMT):
@DarshanBc please disregard the content at the link http://fabric-sdk-node.readthedocs.io, it should really be taken offline. latest node SDK doc is at fabric-sdk-node.github.io. the samples you are looking for can be found in https://github.com/hyperledger/fabric-samples

jimthematrix (Thu, 03 Aug 2017 12:33:55 GMT):
@nickgaski how do we take http://fabric-sdk-node.readthedocs.io offline?

nickgaski (Thu, 03 Aug 2017 12:46:21 GMT):
@jimthematrix - let me figure out who owns the build. It's as simple as just deleting the project from RTD, but we need to hone in on the creator.

cbf (Thu, 03 Aug 2017 18:55:51 GMT):
@jimthematrix IMO, we really should align tooling and use RTD

cbf (Thu, 03 Aug 2017 18:56:11 GMT):
I understand we need jsdocs but that can be hosted off of nexus

cbf (Thu, 03 Aug 2017 18:57:21 GMT):
@odowdaibm we should discuss this (common tooling across fabric-related projects) and l10n/i18n

cbf (Thu, 03 Aug 2017 18:57:38 GMT):
I have a dentist appt but will try to dial in tomorrow

DarshanBc (Fri, 04 Aug 2017 08:32:09 GMT):
when I run npm install these are the errors I am getting

DarshanBc (Fri, 04 Aug 2017 08:32:48 GMT):
ok when I run npm install after removing node_modules again its giving some error these are the errors I am getting npm WARN balance-transfer@1.0.0 No repository field. npm ERR! Linux 4.4.0-42-generic npm ERR! argv "/root/.nvm/versions/node/v6.0.0/bin/node" "/root/.nvm/versions/node/v6.0.0/bin/npm" "install" npm ERR! node v6.0.0 npm ERR! npm v3.8.6 npm ERR! file sh npm ERR! code ELIFECYCLE npm ERR! errno ENOENT npm ERR! syscall spawn npm ERR! pkcs11js@1.0.9 install: `npm run build` npm ERR! spawn ENOENT npm ERR! npm ERR! Failed at the pkcs11js@1.0.9 install script 'npm run build'. npm ERR! Make sure you have the latest version of node.js and npm installed. npm ERR! If you do, this is most likely a problem with the pkcs11js package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! npm run build npm ERR! You can get information on how to open an issue for this project with: npm ERR! npm bugs pkcs11js npm ERR! Or if that isn't available, you can get their info via: npm ERR! npm owner ls pkcs11js npm ERR! There is likely additional logging output above. npm ERR! Please include the following file with any support request: npm ERR! /home/.../fabric-samples/balance-transfer/npm-debug.log I am using normal internet I am not behinf firewall or proxy

DarshanBc (Fri, 04 Aug 2017 08:32:48 GMT):
these are the errors I am getting npm WARN balance-transfer@1.0.0 No repository field. npm ERR! Linux 4.4.0-42-generic npm ERR! argv "/root/.nvm/versions/node/v6.0.0/bin/node" "/root/.nvm/versions/node/v6.0.0/bin/npm" "install" npm ERR! node v6.0.0 npm ERR! npm v3.8.6 npm ERR! file sh npm ERR! code ELIFECYCLE npm ERR! errno ENOENT npm ERR! syscall spawn npm ERR! pkcs11js@1.0.9 install: `npm run build` npm ERR! spawn ENOENT npm ERR! npm ERR! Failed at the pkcs11js@1.0.9 install script 'npm run build'. npm ERR! Make sure you have the latest version of node.js and npm installed. npm ERR! If you do, this is most likely a problem with the pkcs11js package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! npm run build npm ERR! You can get information on how to open an issue for this project with: npm ERR! npm bugs pkcs11js npm ERR! Or if that isn't available, you can get their info via: npm ERR! npm owner ls pkcs11js npm ERR! There is likely additional logging output above. npm ERR! Please include the following file with any support request: npm ERR! /home/.../fabric-samples/balance-transfer/npm-debug.log I am using normal internet I am not behinf firewall or proxy

jimthematrix (Fri, 04 Aug 2017 13:37:28 GMT):
@cbf that's the current setup already, hosted off of github.io and linked from RTD. I don't see a benefit to host the website on nexus, we would need 1) web server to serve up the HTML, 2) CI integration so pushing commits to the repo would automatically trigger the update to the web site. github.io provides both for free

cbf (Fri, 04 Aug 2017 14:11:09 GMT):
@jimthematrix no, I think you misunderstand. I think that we should use a consistent approach for our documentation. That means for fabric using RST and RTD for tutorials and other prose, and linking to language specific API documentation (jsdoc, javadoc, godoc, etc) from that

cbf (Fri, 04 Aug 2017 14:11:22 GMT):
I don't think that we should be using a different scheme

cbf (Fri, 04 Aug 2017 14:11:56 GMT):
because we will soon be translating and we cannot be all over the map with how we deliver docs so that the translation process can be consistently applied across projects

cbf (Fri, 04 Aug 2017 14:12:03 GMT):
and also so that the release process is consistent

cbf (Fri, 04 Aug 2017 14:13:15 GMT):
this also makes it easier for people to engage in helping to write the documentation without having to use different skills/tools across the various repos

jimthematrix (Fri, 04 Aug 2017 18:00:16 GMT):
@cbf ah ok that makes sense, we have one prose (intro page) and one tutorial so far (creating channel), both specific to node.js SDK, that we can move out of jsdoc into RST/RTD, we should move them out of fabric-sdk-node and into fabric/docs

rameshthoomu (Mon, 07 Aug 2017 15:34:54 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=WbqiMe9qQcRpJLjzj) @jimthematrix Do you want me to delete this hook from RTD?

jimthematrix (Mon, 07 Aug 2017 15:45:38 GMT):
@rameshthoomu yes please, as discussed above, we'll use the main RTD project for fabric for the portion of the node SDK tutorials and proses, and keep the API doc on github.io

rameshthoomu (Wed, 09 Aug 2017 18:04:58 GMT):
@nickgaski regarding FAB-1821.. Do you know how to convert swagger json to html format?

nickgaski (Wed, 09 Aug 2017 18:08:28 GMT):
will look at it tomorrow with you Ramesh

JordanJ (Wed, 09 Aug 2017 22:00:46 GMT):
adding an org to a running hyperledger is not documented, does anyone know how to do this?

DarshanBc (Thu, 10 Aug 2017 10:03:51 GMT):
how to give access to a particular user over a particular channel

DarshanBc (Thu, 10 Aug 2017 11:13:21 GMT):
can we create channel dynamically after installing the chain code

joe-alewine (Thu, 10 Aug 2017 14:35:49 GMT):
@JordanJ What do you mean by "adding an org"?

jeffgarratt (Thu, 10 Aug 2017 15:47:25 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=jzZNkDZAYjNBuj6LQ) @DarshanBc In general you use either ROLE based org ORG based identities in your policies, which then allow you to simply give access by signing a CSR for that user using the identity referenced

jeffgarratt (Thu, 10 Aug 2017 15:48:18 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=8iZByBdFsx3QRLw2z) @DarshanBc You can always create a channel if you have the permission per the channel creation policy for the cosortium

jeffgarratt (Thu, 10 Aug 2017 15:49:30 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=Avqo5qC7P4aNjA9yz) @JordanJ This can be accomplished currently if you understand the underlying protobuf structures, but it is non-trivial

DarshanBc (Thu, 10 Aug 2017 16:21:35 GMT):
When will the documentation for java sdk will be released similar to this https://fabric-sdk-node.github.io

sdtsui (Sat, 12 Aug 2017 01:00:50 GMT):
Hi there! I'm a Node developer, and I'm interested in helping with documentation to learn about fabric. Is there a repo/wiki or list of issues that give me an idea of where I can be most useful? Thanks.

yacovm (Sun, 13 Aug 2017 12:58:54 GMT):
https://github.com/hyperledger/fabric-sdk-node

DarshanBc (Mon, 14 Aug 2017 08:55:19 GMT):
basically how genesis.block and channel.tx is generated

DarshanBc (Mon, 14 Aug 2017 08:55:19 GMT):
If I have 5 peers should I install chaincode all the 5 peers and instantiate?

DarshanBc (Mon, 14 Aug 2017 08:55:19 GMT):
If I have 5 peers should I install chaincode on all the 5 peers and instantiate?

DarshanBc (Mon, 14 Aug 2017 08:55:19 GMT):
If I have 5 peers should I install chaincode on all the 5 peers on a single organization and instantiate?

gauthampamu (Tue, 15 Aug 2017 13:39:24 GMT):
What is the progress to upgrade from Fabric v1.0 to v1.1. Will the Fabric v1.1 documentation provide guidance how to upgrade Fabric network. What is the sequence to upgrade ? 1) Should we stop the container for the Orderer first and restart the container with v1.1 image and use the same MSP configuration.

qsmen (Wed, 16 Aug 2017 03:00:59 GMT):
Hi, There is a project on github aiming to do code analysis. Knowing code's function is very important for developers outside of the Fabric team. So why not the Fabric team give some documents describing the function of the code in more details? Thank you.

qsmen (Wed, 16 Aug 2017 03:08:02 GMT):
the documents describe the functions of each package, describe the algorithms in the package. and the documents are different from the current design documents.

Asara (Wed, 16 Aug 2017 15:08:03 GMT):
Hey all, is there a page that contains the environment variables that can be passed to the orderer/peer?

cbf (Thu, 17 Aug 2017 14:55:29 GMT):
@Asara the closest thing is the sample config files in the source tree

cbf (Thu, 17 Aug 2017 14:56:02 GMT):
https://github.com/hyperledger/fabric/tree/release/sampleconfig

cbf (Thu, 17 Aug 2017 14:56:43 GMT):
all properties there, unused ones are commented out

rohitaneja8 (Fri, 18 Aug 2017 06:07:23 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=P5FW8NmSgryGHggtf) @mastersingh24 I have moved to 1.0, but i had to end an application of 0.6 at that time.. Thanks. :)

rohitaneja8 (Wed, 23 Aug 2017 06:37:23 GMT):
does anybody know what is the block size in hyperledger-fabric? How many transactions can be processed in one block?

jeffgarratt (Wed, 23 Aug 2017 19:33:36 GMT):
@rohitaneja8 block size is determined by both the max number of blocks config in conjunction with max window time for block cut

zupan (Fri, 25 Aug 2017 07:43:43 GMT):
Hi, does anybody know if there is a architecture schema of Fabric v1 in the documentation? I remember seeing it few months ago, when it was still alpha version, but I cannot find it now.

mastersingh24 (Fri, 25 Aug 2017 13:19:42 GMT):
@zupan - Have you looked at http://hyperledger-fabric.readthedocs.io/en/latest/txflow.html ? It explains the transaction flow and the components involved in each step

zupan (Fri, 25 Aug 2017 15:15:58 GMT):
@mastersingh24 yes, I've read that one. In my mind I have an architecture schema that shows the difference between v0.6 and v1, but maybe it wasn't from the docs. Tnx anyway :)

jtclark (Mon, 28 Aug 2017 16:06:43 GMT):
quick question: Is there a writing guide for the HL community? If there was something that I wanted to write on behalf of the community, is there a documentation guide that I should follow?

nickgaski (Mon, 28 Aug 2017 20:47:37 GMT):
@jtclark - super easy to contribute to the fabric docs. Just check out the README here - https://github.com/hyperledger/fabric/tree/release/docs

nickgaski (Mon, 28 Aug 2017 20:47:56 GMT):
what precisely are you thinking about writing? perhaps I can be of some assistance

jtclark (Mon, 28 Aug 2017 20:48:42 GMT):
@nickgaski great question. so, this is more for the community, but I'm thinking of doing a gap analysis document on our CI pipeline

jtclark (Mon, 28 Aug 2017 20:50:09 GMT):
something that documents in a high-level document what the bugs are, where the bottlenecks are, and the process. this could be an evolving document that explores what we've fixed (after fixes have been implemented)... just to give contributors a way of understanding the current state of CI in HL.

jtclark (Mon, 28 Aug 2017 20:50:09 GMT):
something that documents in high-level language what the bugs are, where the bottlenecks are, and the process. this could be an evolving document that explores what we've fixed (after fixes have been implemented)... just to give contributors a way of understanding the current state of CI in HL.

jtclark (Mon, 28 Aug 2017 20:51:39 GMT):
talked briefly to @tkuhrt about it, and she welcomed the idea.... but I'd like to hear what other think as well...

jtclark (Mon, 28 Aug 2017 20:51:39 GMT):
talked briefly to @tkuhrt about it, and she welcomed the idea.... but I'd like to hear what others think as well...

markparz (Mon, 28 Aug 2017 20:51:51 GMT):
@jtclark someone else was asking a very similar question before, and we determined since it was something that would change frequently we should create a wiki page, and point to it... it's less involved then changing the more static readthedocs

jtclark (Mon, 28 Aug 2017 20:52:29 GMT):
adheres to the evolution quite nicely in wiki form, I could see that.

markparz (Mon, 28 Aug 2017 20:52:43 GMT):
Lots of info here https://wiki.hyperledger.org/projects/fabric/quality_assurance

markparz (Mon, 28 Aug 2017 20:53:15 GMT):
but I think you have an excellent point and we need to point there from our readthedocs too

markparz (Mon, 28 Aug 2017 20:53:29 GMT):
I think we only have 1 obscure pointer

jtclark (Mon, 28 Aug 2017 21:08:33 GMT):
@markparz, @nickgaski - as a HL contributor, do I have access to add new pages to this wiki, or is this something that I have to request?

tkuhrt (Mon, 28 Aug 2017 22:36:14 GMT):
@jtclark : If you login with your LFID, you should have access. Please let me know if you don't

gauthampamu (Tue, 05 Sep 2017 18:30:32 GMT):
I am looking for information on how to update the certs when it expires. It would be helpful to have this documentation on the site. Do we already have JIRA request for it. Can I open the JIRA request for it.

nickgaski (Tue, 05 Sep 2017 19:18:47 GMT):
@gauthampamu - that would be a good JIRA to open. I like to think we have what you're after, but it's somewhat scattered across the fabric/examples and SDK repos. Take a quick look here - https://github.com/hyperledger/fabric/tree/release/examples/configtxupdate and here - https://fabric-sdk-node.github.io/tutorial-channel-create.html. Seems as if we need to aggregate a bit of info and provide some better tutorials. This would make for a good video in my opinion

DarshanBc (Wed, 06 Sep 2017 12:07:15 GMT):
In FAQ of the document how to I ensure the data privacy has this answer ``` within a channel you can restrict the input data to chaincode to the set of endorsers only, by using visibility settings. The visibility setting will determine whether input and output chaincode data is included in the submitted transaction, versus just output data. ``` Can somebody explain this

Sanjay_Nishank (Mon, 11 Sep 2017 10:02:26 GMT):
Hi, while going thru byfn, (following the Hyperledger fabric documentation), and creating a channel request, I got the following error:

Sanjay_Nishank (Mon, 11 Sep 2017 10:02:30 GMT):
Error: Error connecting to orderer.example.com:7050 due to open ./crypto-config/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem: no such file or directory

Sanjay_Nishank (Mon, 11 Sep 2017 10:03:12 GMT):
Is there any problem with the .pem file? should I point to any other location? Does someone here have any suggestion on this?

nickgaski (Mon, 11 Sep 2017 15:25:47 GMT):
@Sanjay_Nishank - the error is suggestive of a failure to properly mount the certificate libraries on your peer. Are you running on windows?

Sanjay_Nishank (Mon, 11 Sep 2017 17:14:46 GMT):
@nickgaski I am running it on mac OSx

nickgaski (Mon, 11 Sep 2017 17:15:14 GMT):
ok, weird it should definitely work then. send me a direct message and I'll help you sort

gauthampamu (Tue, 12 Sep 2017 18:08:18 GMT):
I have question on transaction lifecycle. Documentation says peer verifies when transaction proposal are sent to the peer. I have a question on this last verification 4.... How does the peer verify the operation performed on the channel ensures it has the permission to write to channel... Endorsing peers verify signature & execute the transaction The endorsing peers verify (1) that the transaction proposal is well formed, (2) it has not been submitted already in the past (replay-attack protection), (3) the signature is valid (using MSP), and (4) that the submitter (Client A, in the example) is properly authorized to perform the proposed operation on that channel (namely, each endorsing peer ensures that the submitter satisfies the channel’s Writers policy). https://hyperledger-fabric.readthedocs.io/en/latest/txflow.html

gauthampamu (Tue, 12 Sep 2017 18:09:23 GMT):
Let says you submit transaction to peer X for channel B and Peer x has not joined the channel, where does the transaction fail. Will it fail during endorsement or will it fail when it submit the responses from the peers to the orderer.

markparz (Wed, 13 Sep 2017 17:28:01 GMT):
Hi ya everyone.... based off previous conversations, I here are a few focus areas for v1.1 in regards to documentation.... In addition to the new features of course, more context needs to be added here: 1- Policies - at the multiple levels 2- Adding a peer / org 3- Adding fab CA & connect to LDAP 4- Adding ordering nodes 5- Revamp of the Glossary I think we'd be hard pressed to contain all this, but I suggest we make a run at 1,2 & 5 to start. @joe-alewine is starting 1 and @nickgaski is working on 2.... I believe there are Jira items open on all already, but we need to double check... lots of jira clean up that needs to happen.

markparz (Wed, 13 Sep 2017 17:28:08 GMT):
Would also be good to close on the logo

DarshanBc (Thu, 14 Sep 2017 08:08:10 GMT):
Does hyperledger-fabric supports PBFT? as per my knowledge its No but This literature from IBM says yes https://pdfs.semanticscholar.org/f852/c5f3fe649f8a17ded391df0796677a59927f.pdf can someone solve my confusion

Jay89 (Thu, 14 Sep 2017 12:13:30 GMT):
Can anyone direct me to a tutorial on how to create an app with user login

kostas (Thu, 14 Sep 2017 21:01:46 GMT):
@DarshanBc: PBFT was in on the 0.6 version. 1.0 is a significant rewrite and doesn't have that consensus module in yet.

guoger (Fri, 15 Sep 2017 05:07:24 GMT):
@odowdaibm are we going to have the meeting today?

joe-alewine (Fri, 15 Sep 2017 14:54:55 GMT):
@guoger @cbf The second meeting is still at the same time: 11 am EST

guoger (Fri, 15 Sep 2017 17:38:46 GMT):
Oh, I guess community google calendar should be updated then

joe-alewine (Mon, 18 Sep 2017 16:58:30 GMT):
I think moving that meeting was only a one time thing. @odowdaibm could answer better but I think the plan is to have the "early" meeting at the same time as usual this Friday

tkuhrt (Mon, 18 Sep 2017 21:26:12 GMT):
@odowdaibm : please let me know. I have updated the future meetings to represent the new time on the community calendar. Let me know if I need to update that again.

kesavannb (Tue, 19 Sep 2017 11:37:49 GMT):
Hi Folks, I have created a blog for Emerging Technology for Begginners , Also i added the setting up for Hyperledger fabric V 0.6 and V 1.0 on that. Kindly review and let me know your queries. Blog name : kesavannb.wordpress.com

holzeis (Thu, 21 Sep 2017 16:49:22 GMT):
Hi! I've found the following answer in the read-the-docs FAQ: `...Second, within a channel you can restrict the input data to chaincode to the set of endorsers only, by using visibility settings. The visibility setting will determine whether input and output chaincode data is included in the submitted transaction, versus just output data...`

nnao (Sat, 23 Sep 2017 05:42:31 GMT):
Is mkdocs.yml necessary? https://github.com/hyperledger/fabric/blob/release/mkdocs.yml I think this file was used by GitHub. But now fabric uses sphinx. May I delete this file?

albe-rosado (Sun, 24 Sep 2017 20:05:07 GMT):
doesn't using a hosted couch db instance for storing ledger data defeat the idea behind blockchain? or i'm missing something? do we save the blockchain data in every peer that use the same channel?

albe-rosado (Sun, 24 Sep 2017 20:05:07 GMT):
using a hosted couch db instance for storing ledger data defeat the idea behind blockchain? or i'm missing something? do we save the blockchain data in every peer that use the same channel?

cbf (Mon, 25 Sep 2017 12:33:09 GMT):
@albe-rosado correct, that file is no longer needed. We'd accept a CR

rock_martin (Thu, 28 Sep 2017 15:06:23 GMT):
Anyone let me know some links for using hyperledger fabric as for production based environment setup on multiple different hosts with respect to docker swarm or kubernates, Thanks in advance

guoger (Fri, 29 Sep 2017 06:02:59 GMT):
@odowdaibm do we have meeting today?

jrosmith (Fri, 29 Sep 2017 17:16:26 GMT):
@albe-rosado questions like this are better suited for #fabric in the future. couchdb is a state database, all of the transactions are still stored on the ledger. for example, say i have ItemA that I want to commit to the ledger. i submit my invoke to the chaincode, the transaction flow commits successfully, and now the ledger is aware of the existence of ItemA. when i query for ItemA, i will get its latest state from couchdb. now lets say my chaincode has a function that allows me to delete ItemA and i invoke that function. the next time i query for ItemA, i will get an error telling me that it is not found. that is because the key pointing to the state of ItemA has been deleted from couchdb. the ledger still has the history of ItemA's existence and all changes to it state (and queries if you decide to create blocks on query) are still stored on the ledger, including the fact that there was a request to delete it. ItemA is removed from the current state of the ledger (couchdb), but the fact that at one point it existed is still stored (ledger)

vu3mmg (Sat, 30 Sep 2017 05:26:58 GMT):
Hi , Could you please let me know the link to the latest documentation/process PPT/PDF , which is work in progress

tkuhrt (Sat, 30 Sep 2017 07:50:23 GMT):
@vu3mmg : Are you looking for something other than http://hyperledger-fabric.readthedocs.io/en/latest/

tkuhrt (Sat, 30 Sep 2017 07:51:31 GMT):
The source for the documentation can be found here: https://github.com/hyperledger/fabric/tree/release/docs

vu3mmg (Sun, 01 Oct 2017 01:10:03 GMT):
@tkuhrt during documentation meetings, Anthony was sharing a PPT with detailed process . Could you please share the link of the latest version of the PPT .

epm2wi (Sun, 01 Oct 2017 10:02:21 GMT):
Hi, where can find the original file for the png images in the document? Is these images draw with Visio

tkuhrt (Sun, 01 Oct 2017 10:29:52 GMT):
@odowdaibm : Can you help @vu3mmg locate the PPT containing the detailed process as above ^

debrajo (Wed, 04 Oct 2017 12:34:45 GMT):
Two dead links from https://hyperledger-fabric-ca.readthedocs.io/en/latest/users-guide.html#fabric-ca-client They are the chaincode lib and sample for API for Attribute-Based Access Control https://github.com/hyperledger/fabric/tree/release/core/chaincode/lib/cid/README.md https://github.com/hyperledger/fabric-samples/tree/release/fabric-ca/README.md

asadhayat (Thu, 05 Oct 2017 10:31:53 GMT):
```On *Architecture Explained* (https://hyperledger-fabric.readthedocs.io/en/latest/arch-deep-dive.html) page under section *2.1.1 `PROPOSE` message format* under bullet `polocies` for deploy transaction its written ```

asadhayat (Thu, 05 Oct 2017 10:31:53 GMT):
On *Architecture Explained* (https://hyperledger-fabric.readthedocs.io/en/latest/arch-deep-dive.html) page under section *2.1.1 `PROPOSE` message format* under bullet `polocies` for deploy transaction its written

asadhayat (Thu, 05 Oct 2017 10:32:34 GMT):
Note that endorsement policies are not supplied with txPayload in a deploy transaction, but txPayload of a deploy contains endorsement policy ID and its parameters

asadhayat (Thu, 05 Oct 2017 10:32:34 GMT):
`Note that endorsement policies are not supplied with txPayload in a deploy transaction, but txPayload of a deploy contains endorsement policy ID and its parameters`

asadhayat (Thu, 05 Oct 2017 10:33:21 GMT):
`Note that endorsement policies are not supplied with txPayload in a **invoke* transaction, but txPayload of a deploy contains endorsement policy ID and its parameters`

asadhayat (Thu, 05 Oct 2017 10:33:21 GMT):
`Note that endorsement policies are not supplied with txPayload in a invoke transaction, but txPayload of a deploy contains endorsement policy ID and its parameters`

asadhayat (Thu, 05 Oct 2017 10:33:21 GMT):
`Note that endorsement policies are not supplied with txPayload in a ~deploy~invoke transaction, but txPayload of a deploy contains endorsement policy ID and its parameters`

asadhayat (Thu, 05 Oct 2017 10:33:21 GMT):
Note that endorsement policies are not supplied with txPayload in a ~deploy~invoke transaction, but txPayload of a deploy contains endorsement policy ID and its parameters

asadhayat (Thu, 05 Oct 2017 10:33:21 GMT):
Note that endorsement policies are not supplied with txPayload in a ~deploy~ *invoke* transaction, but txPayload of a deploy contains endorsement policy ID and its parameters

bennythejudge (Fri, 06 Oct 2017 23:06:22 GMT):
I tried submitting a PR for a tiny contribution to the doc but I can't get the check on the signoff green - could anyone help?

bennythejudge (Fri, 06 Oct 2017 23:07:20 GMT):
this is the PR https://github.com/hyperledger/fabric/pull/73

tkuhrt (Fri, 06 Oct 2017 23:59:38 GMT):
@bennythejudge : Hyperledger Fabric uses Gerrit for code changes. GitHub is a mirror. I wrote this cheat sheet for myself that may be useful: https://docs.google.com/document/d/161sSQwflX4X7QC5iJXMoOih8lSHbnpahaJbeywOkCSY

tkuhrt (Sat, 07 Oct 2017 00:01:15 GMT):
And there is this: http://hyperledger-fabric.readthedocs.io/en/latest/CONTRIBUTING.html

bennythejudge (Sat, 07 Oct 2017 09:18:30 GMT):
@tkuhrt thanks a lot for the reply.I will read the docs.

DarshanBc (Wed, 11 Oct 2017 06:43:14 GMT):
Link mentioned here points to release tree but released tree doesn't have it but the master tree has http://hyperledger-fabric-ca.readthedocs.io/en/latest/users-guide.html#attribute-based-access-control this link should have been https://github.com/hyperledger/fabric/tree/master/core/chaincode/lib/cid/README.md instead of https://github.com/hyperledger/fabric/tree/release/core/chaincode/lib/cid/README.md

DarshanBc (Wed, 11 Oct 2017 06:43:14 GMT):
Link mentioned here points to release tree but released tree doesn't have the content but the master tree has http://hyperledger-fabric-ca.readthedocs.io/en/latest/users-guide.html#attribute-based-access-control this link should have been https://github.com/hyperledger/fabric/tree/master/core/chaincode/lib/cid/README.md instead of https://github.com/hyperledger/fabric/tree/release/core/chaincode/lib/cid/README.md

DarshanBc (Wed, 11 Oct 2017 06:43:14 GMT):
Link mentioned here points to release tree but released tree doesn't have the content but the master tree has http://hyperledger-fabric-ca.readthedocs.io/en/latest/users-guide.html#attribute-based-access-control this link should have contain https://github.com/hyperledger/fabric/tree/master/core/chaincode/lib/cid/README.md instead of https://github.com/hyperledger/fabric/tree/release/core/chaincode/lib/cid/README.md

DarshanBc (Wed, 11 Oct 2017 06:43:14 GMT):
Link mentioned here points to release tree but released tree doesn't have the content but the master tree has http://hyperledger-fabric-ca.readthedocs.io/en/latest/users-guide.html#attribute-based-access-control this link should have contained https://github.com/hyperledger/fabric/tree/master/core/chaincode/lib/cid/README.md instead of https://github.com/hyperledger/fabric/tree/release/core/chaincode/lib/cid/README.md

DarshanBc (Wed, 11 Oct 2017 06:43:14 GMT):
@tkuhrt @vu3mmg Link mentioned here points to release tree but released tree doesn't have the content but the master tree has http://hyperledger-fabric-ca.readthedocs.io/en/latest/users-guide.html#attribute-based-access-control this link should have contained https://github.com/hyperledger/fabric/tree/master/core/chaincode/lib/cid/README.md instead of https://github.com/hyperledger/fabric/tree/release/core/chaincode/lib/cid/README.md

mastersingh24 (Wed, 11 Oct 2017 11:03:24 GMT):
@DarshanBc - please file a bug in JIRA

mastersingh24 (Wed, 11 Oct 2017 15:37:00 GMT):
Posting here per @dave.enyeart

mastersingh24 (Wed, 11 Oct 2017 15:37:47 GMT):
Is it safe to assume that for Fabric we have not published any docs which are only applicable to v1.1 ?

mastersingh24 (Wed, 11 Oct 2017 15:43:14 GMT):
I think this is what we'll need to do: - hold off on merging any 1.1 specific doc - need to update the docs in the release branch. since we really only publish from master today, I've been a bit lazy about updating release branch with docs. I'll create a JIRA to take care of this - organize the RTD version scheme to work the way we want (I'm on it)

dave.enyeart (Wed, 11 Oct 2017 16:06:32 GMT):
@mastersingh24 It appears that readthedocs 'latest' is coming from 'master' branch. The content in readthedocs 'stable' appears to be from 1.0 timeframe so I can only assume that is coming from 'release' branch.

dave.enyeart (Wed, 11 Oct 2017 16:06:56 GMT):
There hasn't been much 1.1 content going to doc yet, but there are some examples such as attribute based access control: http://hyperledger-fabric-ca.readthedocs.io/en/latest/users-guide.html#attribute-based-access-control

mastersingh24 (Wed, 11 Oct 2017 16:15:12 GMT):
Right - I'm going to need to handle the fabric-ca docs as well

mastersingh24 (Wed, 11 Oct 2017 16:15:31 GMT):
I'm on it - since it's easier to do at the same time as figuring it out ;)

cbf (Wed, 11 Oct 2017 20:11:38 GMT):
right, the docs should be release branch and we should have a staging publication of the master branch docs for preview

cbf (Wed, 11 Oct 2017 20:12:13 GMT):
we should definitely NOT be holding docs back

cbf (Wed, 11 Oct 2017 20:12:24 GMT):
if anything, we need docs to be merged with the code

mastersingh24 (Wed, 11 Oct 2017 20:45:39 GMT):
I just need the 1.1 docs held back so that I can properly update release to be in sync with master. after that, we'll be all good

mastersingh24 (Wed, 11 Oct 2017 20:45:47 GMT):
Right now, we have a bit of a mess

mastersingh24 (Wed, 11 Oct 2017 20:46:48 GMT):
On the other hand, there have not been a ton of doc updates either ;)

dave.enyeart (Sun, 15 Oct 2017 13:05:04 GMT):
@mastersingh24 @nickgaski Are the gates open now for 1.1 doc to go into fabric master? I assume any changes will go into readthedocs 'latest' but not readthedocs 'stable'?

dave.enyeart (Sun, 15 Oct 2017 13:05:19 GMT):
I ask because @jimthematrix has a change ready: https://gerrit.hyperledger.org/r/#/c/14479/

mastersingh24 (Mon, 16 Oct 2017 12:26:52 GMT):
Yep - we are good to go. If people can make sure to mark in the JIRA that it's a new 1.1 doc versus a fix to a doc (by indicating 1.1 and 1.0.4) that would be great

dave.enyeart (Mon, 16 Oct 2017 13:17:59 GMT):
@mastersingh24 Can you provide some more guidance on the workflow, i.e. should new 1.1 doc be delivered to master (which goes to rtd 'latest') and doc fixes be delivered to both master (rtd 'latest') and release (rtd 'stable')? Or will the person cutting 3rd digit releases automatically copy master changes to release branch?

mastersingh24 (Mon, 16 Oct 2017 19:28:32 GMT):
It's easiest if you push fixes to both master and release, but definitely push to master and make sure to tag the JIRA so that as part of a fix pack release we can pick up any doc fixes

philviana (Thu, 19 Oct 2017 03:55:38 GMT):
Howdy. Not sure if this is the best place to post this, but I'm having a problem trying to run the "Build your first network" example from the documentation. I'm having the very same issue sent by this guy on StackOverflow and it doesn't seem like he found a fix:

philviana (Thu, 19 Oct 2017 03:55:49 GMT):
https://stackoverflow.com/questions/45707982/fabric-returns-error-got-unexpected-status-bad-request

philviana (Thu, 19 Oct 2017 03:56:50 GMT):
I was trying to manually run the example. using `byfn.sh -m up` works just fine

philviana (Thu, 19 Oct 2017 04:18:14 GMT):
One of the answers says that `BAD_REQUEST` may be returned from `peer channel create` if the submitter does not have channel creation rights (admin authority for an org).

Asara (Thu, 19 Oct 2017 16:50:45 GMT):
Hey all, been trying to run the fabric-ca by creating the binary (as per https://hyperledger-fabric-ca.readthedocs.io/en/latest/users-guide.html)

Asara (Thu, 19 Oct 2017 16:51:26 GMT):
In this documentation it states that the minimum version of golang required is 1.9, but using go get downloads from the 'release branch' (which is set as the default on git), which requires 1.7 in order to build.

dave.enyeart (Thu, 19 Oct 2017 16:58:12 GMT):
@Asara you are looking at a readthedocs 'latest' link. This is for new 1.1 content (uses golang 1.9). For the release branch of 1.0.x (uses golang 1.7), you want the 'stable' docs from readthedocs.

Asara (Thu, 19 Oct 2017 16:58:41 GMT):
welp that makes sense. Thanks @dave.enyeart

rameshthoomu (Fri, 20 Oct 2017 17:55:34 GMT):
@nickgaski @cbf I would like add a new CI verify job to test fabric documentation changes and publish the result as html format..

rameshthoomu (Fri, 20 Oct 2017 17:56:40 GMT):
I have created a job in sandbox and tested.. Please see the output here https://jenkins.hyperledger.org/sandbox/job/doc-test/HTML_Report/

rameshthoomu (Fri, 20 Oct 2017 17:58:07 GMT):
if you are agree to this.. will add this job in fabric verification builds

rameshthoomu (Fri, 20 Oct 2017 17:58:07 GMT):
if you are ok to this plan. will add this job in fabric verification builds

cbf (Mon, 23 Oct 2017 13:11:27 GMT):
so the docs would be available from the jenkins report?

rameshthoomu (Mon, 23 Oct 2017 13:26:10 GMT):
Only for the verify job.. once the patch is merged we can see the same output in RTD

rjones (Tue, 24 Oct 2017 19:36:23 GMT):
@cbf and channel in general: if I get control of fabric.rtd, how would we want to do the transition? I've only just asked for control of it. publish to both places for a while?

rjones (Tue, 24 Oct 2017 19:36:46 GMT):
http://fabric.readthedocs.io/zh_CN/latest/ points here: https://github.com/ooozws/fabric/

mikykey (Wed, 25 Oct 2017 18:04:41 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=TB7xC9Ytbcc59njqf) @philviana hi! did you solved this problem? I have the same problem too and I'm not able to solve it...

philviana (Wed, 25 Oct 2017 18:06:33 GMT):
Are the writers of the documentation/examples in this channel?

nickgaski (Wed, 25 Oct 2017 19:04:55 GMT):
@philviana @mikykey - what are you guys running into?

philviana (Wed, 25 Oct 2017 19:06:27 GMT):
```2017-08-16 01:34:13.902 UTC [msp] GetLocalMSP -> DEBU 00c Returning existing local MSP 2017-08-16 01:34:13.902 UTC [msp] GetDefaultSigningIdentity -> DEBU 00d Obtaining default signing identity 2017-08-16 01:34:13.902 UTC [msp/identity] Sign -> DEBU 00e Sign: plaintext: 0AC3060A1508021A060895C2CECC0522...7E2E59E3CFD14AC765C92FBF36614E79 2017-08-16 01:34:13.902 UTC [msp/identity] Sign -> DEBU 00f Sign: digest: FA75790826EF23E1A7C46AD3B9AE0DB7321DC271B8BE93A29BAC2F6EEACBB8B0 Error: Got unexpected status: BAD_REQUEST Usage: peer channel create [flags]```

philviana (Wed, 25 Oct 2017 19:07:24 GMT):
I made sure that the channel didn't exist

philviana (Wed, 25 Oct 2017 20:32:59 GMT):
For the record: the problem is that the line containing `script.sh` had not been commented out from `docker-compose-cli.yaml` - this was causing the channel to be created twice and hence the BAD_REQUEST error.

philviana (Wed, 25 Oct 2017 21:47:28 GMT):
@here I'm working with @nickgaski to update the documentation and add a troubleshooting tip for folks facing the same problem as myself and @mikykey. Should I open a defect in JIRA against FABRIC for this, with label `documentation`? (this will be my first issue, so not sure how to proceed...)

tkuhrt (Wed, 25 Oct 2017 21:50:20 GMT):
@philviana : That is how I have done it in the past.

markparz (Thu, 26 Oct 2017 00:25:21 GMT):
@philviana is this a problem in the doc or the script itself? The reason I'm asking, I'm wondering if we need to fix a code issue in the script, or if this is something to be updated in the doc itself. We've been doing FAQ type of things and issues in stack overflow. I will ask @nickgaski tomorrow as well, as I'm not sure which example this is.... Great catch either way!

mikykey (Thu, 26 Oct 2017 07:56:50 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=8bzFXwPJBNwcc57qe) @markparz It is a problem in the documentation (from my point of view). I was following the documentation step by step and I found this issue (it was not really explained what to do). @philviana solved my problem. thank you!

philviana (Thu, 26 Oct 2017 14:15:28 GMT):
@markparz It's a problem in the docs. The scripts works fine when invoked by the other scripts, but fails when the manual steps are run because the documentation wasn't explicit about commenting out the line that invokes the script. I connected with @nickgaski yesterday on this. Thanks!

nickgaski (Thu, 26 Oct 2017 14:23:46 GMT):
it's a single doggone colon that is preventing the `note` from appearing. Thanks for the CR

philviana (Thu, 26 Oct 2017 14:45:19 GMT):
Np @nickgaski . I assigned you as the reviewer by the way. thanks again

philviana (Thu, 26 Oct 2017 14:45:19 GMT):
Np @nickgaski. I assigned you as the reviewer by the way. thanks again

nickgaski (Fri, 27 Oct 2017 14:06:45 GMT):
@here - new content has been merged in the BYFN section that enables node.js chaincode. You will find this content on the `latest` branch of docs, which is the default view when you visit ReadTheDocs. Here's the caveat... you must build your Fabric images from the master branch in order for this new functionality to work. If you are operating against the `stable` documentation branch then everything will work as described. We are working to flip flop the initial doc view to the `stable` branch. Feel free to message this channel or DM me if you need help running the node chaincode. Happy Friday

mastersingh24 (Mon, 30 Oct 2017 11:20:24 GMT):
@nickgaski - I actually just changed RTD in terms of which versions we publish and which is the default: 1) We now publish: - release - this is the release branch - v1.0.3 - this is the v1.0.3 tag - master - master branch - latest - points to master 2) The default is "release" We cannot use "stable" because stable will always point to the latest tagged release

mastersingh24 (Mon, 30 Oct 2017 11:20:24 GMT):
@nickgaski - I actually just changed RTD in terms of which versions we publish and which is the default: 1) We now publish: - release - this is the release branch - v1.0.3 - this is the v1.0.3 tag - master - master branch - latest - points to release 2) The default is "release" We cannot use "stable" because stable will always point to the latest tagged release

mastersingh24 (Mon, 30 Oct 2017 11:29:36 GMT):
I can point latest to master if you want?

meridian (Mon, 30 Oct 2017 12:54:13 GMT):
sw means software should it not be written out as sw or at least made a note

dave.enyeart (Mon, 30 Oct 2017 14:53:22 GMT):
@mastersingh24 I like the new RTD structure, this will enable for example having a 1.0, 1.1, 1.2 version of the docs. I didn't realize it could be based on a tag.

dave.enyeart (Mon, 30 Oct 2017 14:53:37 GMT):
I think we'll need to do something similar for the node.js sdk documentation.

dave.enyeart (Mon, 30 Oct 2017 14:53:38 GMT):
https://fabric-sdk-node.github.io/

dave.enyeart (Mon, 30 Oct 2017 14:53:48 GMT):
I believe it currently gets built from master

dave.enyeart (Mon, 30 Oct 2017 14:53:55 GMT):
Which will confuse 1.0 consumers

dave.enyeart (Mon, 30 Oct 2017 14:54:40 GMT):
@rameshthoomu @mastersingh24 @cbf @jimthematrix @bretharrison Any ideas on how to resolve that?

dave.enyeart (Mon, 30 Oct 2017 14:55:52 GMT):
For example, we'd like to merge the 1.1 connection document tutorial in https://gerrit.hyperledger.org/r/#/c/14467/ , but dont want to confuse 1.0 consumers

bretharrison (Mon, 30 Oct 2017 14:58:39 GMT):
we could make sure that we tag the api's and tutorials wth a version number ?

dave.enyeart (Mon, 30 Oct 2017 14:59:24 GMT):
that would be the fallback, let's see if the infrastructure might offer anything

mastersingh24 (Mon, 30 Oct 2017 15:38:02 GMT):
@dave.enyeart - unfortunately (or maybe fortunately ;) ) Git Pages is pretty simplistic - i.e. it only publishes from the master branch. So I think we just need to take a simplistic approach in the repo ( https://github.com/fabric-sdk-node/fabric-sdk-node.github.io )

mastersingh24 (Mon, 30 Oct 2017 15:39:04 GMT):
We can just create a simple structure: index.html - list available versions with links v1.0.x - push 1.0.x docs to this folder v1.1.x - push 1.1.x docs to this folder ;)

dave.enyeart (Mon, 30 Oct 2017 15:41:38 GMT):
@mastersingh24 I assume v1.1.x docs be a superset of v1.0.x (rather than a delta) right?

mastersingh24 (Mon, 30 Oct 2017 15:43:24 GMT):
Basically, we build the full set of docs for every release and they each go in their own folder. So each version folder is completely self-contained

mastersingh24 (Mon, 30 Oct 2017 15:43:33 GMT):
So I guess the answer is "yes" ;)

dave.enyeart (Mon, 30 Oct 2017 15:43:46 GMT):
ok, that's a lot of baggage to keep in master over time, but i guess it is what it is

mastersingh24 (Mon, 30 Oct 2017 15:44:14 GMT):
We use a separate repo for the docs anyway

dave.enyeart (Mon, 30 Oct 2017 15:45:52 GMT):
would this apply for all the doc tabs? Modules, Classes, Tutorials, Global?

jimthematrix (Mon, 30 Oct 2017 15:46:32 GMT):
@bretharrison using inline tags to differentiate may not always work, and it requires a lot of diligence/discipline. i think doing the publish to separate folders as Gari suggested sounds like the best option

jimthematrix (Mon, 30 Oct 2017 15:46:32 GMT):
@bretharrison using inline tags to differentiate may not always work (like modifications to existing APIs), and it requires a lot of diligence/discipline. i think doing the publish to separate folders as Gari suggested sounds like the best option

mastersingh24 (Mon, 30 Oct 2017 15:46:42 GMT):
Think of it this way - we'll have a landing page which allows you to select the SDK version you want and then takes you to the full doc set for that version

jimthematrix (Mon, 30 Oct 2017 15:50:26 GMT):
@dave.enyeart @mastersingh24 do either of you want to open an improvement for this? we can then fill in the details with sub tasks (code, and CI work)

mastersingh24 (Mon, 30 Oct 2017 15:51:18 GMT):
@jimthematrix - sure - makes sense

dave.enyeart (Mon, 30 Oct 2017 15:57:58 GMT):
@jimthematrix @bretharrison I imagine it will take some time to get the doc fixed up... in the interim for the connection profile tutorial, could you simply indicate at the top that it requires 1.1? So that we can merge it and point people to it for 1.1 preview?

mastersingh24 (Mon, 30 Oct 2017 16:04:21 GMT):
@dave.enyeart - of course I am an optimist, but this could be done in less than an hour manually ;)

dave.enyeart (Mon, 30 Oct 2017 16:05:11 GMT):
It still isn't clear to me if this could be done for all - Modules, Classes, Tutorials, Global... I thought some of this was auto-generated

mastersingh24 (Mon, 30 Oct 2017 16:05:55 GMT):
The whole thing is automatically built today using gulp and jsdoc

mastersingh24 (Mon, 30 Oct 2017 16:06:10 GMT):
I can build the docs for any release on my laptop ;)

mastersingh24 (Mon, 30 Oct 2017 16:06:32 GMT):
Well actually only Jim can publish (as well as some lfid)

meridian (Mon, 30 Oct 2017 19:10:44 GMT):
can someone add the fact that you need Windows 10 professional to install and run docker

meridian (Mon, 30 Oct 2017 22:29:11 GMT):
i know that seems obvious but i have had 3-4 people not know that

UtkarshSingh (Tue, 31 Oct 2017 13:08:51 GMT):
How Consensus Algorithm is involved in Hyperledger Fabric ? What's the scope of it ?

nickgaski (Tue, 31 Oct 2017 13:31:29 GMT):
@UtkarshSingh - http://hyperledger-fabric.readthedocs.io/en/release/fabric_model.html#consensus . Consensus in Fabric v1.x is not confined to a specific algorithm. Rather, it encompasses the complete lifecycle of a transaction: proposal -> endorsement -> ordering -> validation. The current default for the ordering implementation is a kafka zookeeper ensemble. This is really just a messaging queue that orders transactions on a per channel basis.

meridian (Wed, 01 Nov 2017 14:10:45 GMT):
quick question- is there any plan on making "swappable" the DB embedded in fabric? So if i wanted to switch from LevelDB to lets say LMDB I could?

meridian (Wed, 01 Nov 2017 14:14:39 GMT):
obvious it would need porting to Go

meridian (Wed, 01 Nov 2017 14:14:50 GMT):
guess i answered my own question lol

tkuhrt (Wed, 01 Nov 2017 18:21:56 GMT):
@meridian : DB is already swappable to CouchDB. I assume you could have a look at the source code to see how that is done if you want to do the same does leveldb.

meridian (Wed, 01 Nov 2017 18:23:05 GMT):
@tkuhrt thanks , lack of sleep catches up to you :O

philviana (Wed, 01 Nov 2017 21:45:12 GMT):
I'm trying a modified version of the `sacc` example from the docs...

philviana (Wed, 01 Nov 2017 21:45:23 GMT):
I changed very little in the code - mostly removed comments.

philviana (Wed, 01 Nov 2017 21:45:39 GMT):
My code is behaving similarly to sacc except when I try to query.

philviana (Wed, 01 Nov 2017 21:46:53 GMT):
I always get "Asset not found". I'd like to know why for sure, but the error brings me to a different question: is there a way for me to navigate the transactions and look at the merkle tree from the CLI? For example, that would help me determine whether PutState is failing or GetState

philviana (Thu, 02 Nov 2017 00:38:58 GMT):
For the record, that's the "Chaincode for developers" tutorial

UtkarshSingh (Thu, 02 Nov 2017 10:16:12 GMT):
@nickgaski As, other consensus algorithms like, Proof of Work and Proof of Stake, are computationally secure algorithms (that's the backbone of security of those system architectures, even if any peer cheats). How, Hyperledger Fabric's consensus works to provide that security. 1. Is it efficient, as compared to Proof of Work & Proof of Stake ? 2. Is it also vulnerable to "51% attack" ? 3. What if the endorsers and validators cheat ?? One extra question I wanna ask :- 1. Hyperledger Fabric is using Gossip Dissemination Protocol, is it the backbone of its Consensus algorithm ?

UtkarshSingh (Thu, 02 Nov 2017 10:18:43 GMT):
@philviana you need to use "chaincode upgrade" command for it. Try this http://hyperledger-fabric-docs.readthedocs.io/en/latest/chaincode4noah.html#upgrade

joe-alewine (Thu, 02 Nov 2017 15:35:57 GMT):
@UtkarshSingh The plan is for Fabric to eventually use some sort of PBFT (there's an outline proposal here: https://arxiv.org/pdf/1709.06921.pdf), but for now the protection against "cheaters" is the fact that the network is permissioned. Let's say you're throwing a party. If there's going to be a ton of people you don't know, you might very well lock certain doors and put certain things away. But if it's just you and some friends, you probably wouldn't. That's the concept here. As networks scale eventually you will need PBFT to prevent against bad actors or peers that get hacked into. For now, the transaction flow itself -- as well as the assumption that you will only be inviting organizations that you trust into the network -- *is* the fault tolerant mechanism.

joe-alewine (Thu, 02 Nov 2017 15:35:57 GMT):
@UtkarshSingh The plan is for Fabric to eventually use some sort of PBFT (there's an outline proposal here: https://arxiv.org/pdf/1709.06921.pdf), but for now the protection against "cheaters" is the fact that the network is permissioned. Let's say you're throwing a party. If there's going to be a ton of people you don't know, you might very well lock certain doors and put certain things away. But if it's just you and some friends, you probably wouldn't. That's the concept here. As networks scale eventually you'll probably want PBFT to prevent against bad actors or peers that get hacked into. For now, the transaction flow itself -- as well as the assumption that you will only be inviting organizations into the network that you trust -- is what is protecting you.

joe-alewine (Thu, 02 Nov 2017 15:35:57 GMT):
@UtkarshSingh My understanding is that plan is for Fabric to eventually use some sort of PBFT (there's an outline proposal here: https://arxiv.org/pdf/1709.06921.pdf), but for now the protection against "cheaters" is the fact that the network is permissioned. Let's say you're throwing a party. If there's going to be a ton of people you don't know, you might very well lock certain doors and put certain things away. But if it's just you and some friends, you probably wouldn't. That's the concept here. As networks scale eventually you'll probably want PBFT to prevent against bad actors or peers that get hacked into. For now, the transaction flow itself -- as well as the assumption that you will only be inviting organizations into the network that you trust -- is what is protecting you.

joe-alewine (Thu, 02 Nov 2017 15:35:57 GMT):
@UtkarshSingh My understanding is that plan is for Fabric to eventually use some sort of PBFT (there's an outline proposal here: https://arxiv.org/pdf/1709.06921.pdf), but for now the protection against "cheaters" is the fact that the network is permissioned. Let's say you're throwing a party. If there's going to be a ton of people there you don't know, you might very well lock certain doors and put certain things away. But if it's just you and some friends, you probably wouldn't. That's the concept here. As networks scale eventually you'll probably want PBFT to prevent against bad actors or peers that get hacked into. For now, the transaction flow itself -- as well as the assumption that you will only be inviting organizations into the network that you trust -- is what is protecting you.

joe-alewine (Thu, 02 Nov 2017 15:35:57 GMT):
@UtkarshSingh My understanding is that plan is for Fabric to eventually use some sort of PBFT (there's an outline proposal here: https://arxiv.org/pdf/1709.06921.pdf), but for now the protection against "cheaters" is the fact that the network is permissioned. Let's say you're throwing a party. If there's going to be a ton of people there you don't know, you might very well lock certain doors and put certain things away. But if the party is just going to be you and some friends, you probably wouldn't do those things. That's the concept here. As networks scale eventually you'll probably want PBFT to prevent against bad actors or peers that get hacked into. For now, the transaction flow itself -- as well as the assumption that you will only be inviting organizations into the network that you trust -- is what is protecting you.

joe-alewine (Thu, 02 Nov 2017 15:35:57 GMT):
@UtkarshSingh My understanding is that plan is for Fabric to eventually use some sort of PBFT (there's an outline proposal here: https://arxiv.org/pdf/1709.06921.pdf), but for now the protection against "cheaters" is the fact that the network is permissioned. Let's say you're throwing a party. If there's going to be a ton of people there you don't know, you might very well lock certain doors and put certain things away. But if the party is just going to be you and some friends, you probably wouldn't do those things. That's the concept here. As networks scale eventually you'll probably want PBFT to prevent against bad actors or peers that get hacked into. For now, the transaction flow itself (the endorsement policy in particular) -- as well as the assumption that you will only be inviting organizations into the network that you trust -- is what is protecting you.

joe-alewine (Thu, 02 Nov 2017 15:35:57 GMT):
@UtkarshSingh My understanding is that plan is for Fabric to eventually use some sort of PBFT (there's an outline proposal here: https://arxiv.org/pdf/1709.06921.pdf), but for now the protection against "cheaters" is the fact that the network is permissioned. Let's say you're throwing a party. If there's going to be a ton of people there you don't know, you might very well lock certain doors and put certain things away. But if the party is just going to be you and some friends, you probably wouldn't. That's the concept here. As networks scale eventually you'll probably want PBFT to prevent against bad actors or peers that get hacked into. For now, the transaction flow itself (the endorsement policy in particular) -- as well as the assumption that you will only be inviting organizations into the network that you trust -- is what is protecting you.

joe-alewine (Thu, 02 Nov 2017 15:35:57 GMT):
@UtkarshSingh My understanding is that plan is for Fabric to eventually use some sort of PBFT (there's an outline proposal here: https://arxiv.org/pdf/1709.06921.pdf), but for now the protection against "cheaters" is the fact that the network is permissioned. Let's say you're throwing a party. If there's going to be a ton of people there you don't know, you might very well lock certain doors and put certain things away. But if the party is just going to be you and some friends, you probably wouldn't. That's the concept here. As networks scale eventually you'll probably want PBFT to prevent against bad actors or bad apps or peers that get hacked into. For now, the transaction flow itself (the endorsement policy in particular) -- as well as the assumption that you will only be inviting organizations into the network that you trust -- is what is protecting the network and the ledger from being corrupted.

joe-alewine (Thu, 02 Nov 2017 15:35:57 GMT):
@UtkarshSingh My understanding is that plan is for Fabric to eventually use some sort of PBFT (there's an outline proposal here: https://arxiv.org/pdf/1709.06921.pdf), but for now the protection against "cheaters" is the fact that the network is permissioned. Let's say you're throwing a party. If there's going to be a ton of people there you don't know, you might very well lock certain doors and put certain things away. But if the party is just going to be you and some friends, you probably wouldn't. That's the concept here. As networks scale eventually you'll probably want PBFT to prevent against bad actors or bad apps or peers that get hacked into. For now, the transaction flow itself (the endorsement policy in particular, which can outline specifically who needs to "sign" a transaction) -- as well as the assumption that you will only be inviting organizations into the network that you trust -- is what is protecting the network and the ledger from being corrupted.

joe-alewine (Thu, 02 Nov 2017 15:35:57 GMT):
@UtkarshSingh My understanding is that the plan is for Fabric to eventually use some sort of PBFT (there's an outline proposal here: https://arxiv.org/pdf/1709.06921.pdf), but for now the protection against "cheaters" is the fact that Fabric networks are permissioned. Let's say you're throwing a party. If there's going to be a ton of people there you don't know, you might very well lock certain doors and put certain things away. But if the party is just going to be you and some friends, you probably wouldn't. That's the concept here. As networks scale eventually you'll probably want PBFT to prevent against bad actors or bad apps or peers that get hacked into. For now, the transaction flow itself (the endorsement policy in particular, which can outline specifically who needs to "sign" a transaction) -- as well as the assumption that you will only be inviting organizations into the network that you trust -- is what is protecting the network and the ledger from being corrupted.

joe-alewine (Thu, 02 Nov 2017 15:35:57 GMT):
@UtkarshSingh My understanding is that the plan is for Fabric to eventually use some sort of PBFT (there's an outline proposal here: https://arxiv.org/pdf/1709.06921.pdf), but for now the protection against "cheaters" is the fact that Fabric networks are permissioned. Let's say you're throwing a party. If there's going to be a ton of people there you don't know, you might very well lock certain doors and put certain things away. But if the party is just going to be you and some friends, you probably wouldn't. That's the concept here. As networks scale eventually you'll probably want PBFT to prevent against bad actors or bad apps or peers that get hacked into. For now, the transaction flow itself (the endorsement policy in particular, which can outline explicitly who needs to "sign" a transaction) -- as well as the assumption that you will only be inviting organizations into the network that you trust -- is what is protecting the network and the ledger from being corrupted.

joe-alewine (Thu, 02 Nov 2017 15:35:57 GMT):
@UtkarshSingh My understanding is that the plan is for Fabric to eventually use some sort of PBFT (there's an outline proposal here: https://arxiv.org/pdf/1709.06921.pdf), but for now the protection against "cheaters" is the fact that Fabric networks are permissioned. Let's say you're throwing a party. If there's going to be a ton of people there you don't know, you might very well lock certain doors and put certain things away. But if the party is just going to be you and some friends, you probably wouldn't. That's the concept here. As networks scale eventually you'll probably want PBFT to prevent against bad actors or bad apps or peers that get hacked into. For now, the assumption that you will only be inviting organizations into the network that you trust -- as well as the transaction flow itself (the endorsement policy in particular, which can outline explicitly who needs to "sign" a transaction) -- is what is protecting the network and the ledger from being corrupted.

markparz (Thu, 02 Nov 2017 18:28:13 GMT):
You've all been waiting for this one!!!! Start with BYFN, then.... Watch how to add a new organizations to your existing Hyperledger Fabric network. https://youtu.be/DKuGU5CYV_E Great Video, thanks @NickGaski

philviana (Thu, 02 Nov 2017 19:52:23 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=XtnJf3SXNEDqJjz6w) @UtkarshSingh Thanks! Will give that a try later tonight.

philviana (Thu, 02 Nov 2017 20:39:37 GMT):
@UtkarshSingh Do I need to run `chaincode upgrade` even if I'm refreshing my entire environment? I deleted all Docker containers and spun them all up again (cli, chaincode, peer, orderer).

UtkarshSingh (Fri, 03 Nov 2017 10:59:09 GMT):
You must have noticed that chaincode is a program written in GO language, You can modify it in two way : 1. In Dynamically changing the chaincode, use upgrade command 2. If you wanna restart the everything, better make changes directly to the chaincodes in GO lang, and install the upgraded files to every peer

UtkarshSingh (Mon, 06 Nov 2017 10:24:17 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=qZ3EW6fmAEKZRssd2) @joe-alewine Yeah. All the peers are trustworthy and will not cheat, is pre-assumed

markparz (Tue, 07 Nov 2017 19:49:52 GMT):
Attribute based access controls video for v1.1 preview is now available at https://youtu.be/WTW9QVO28l0 Thanks @smithbk

markparz (Tue, 07 Nov 2017 21:04:12 GMT):
Generate crypto materials with Fabric CA ... watch how... https://youtu.be/KZ5HThNjaeI

markparz (Thu, 09 Nov 2017 15:51:52 GMT):
Start using Node JS Chaincode w/ v1.1 preview.... see how to here, with @jimthematrix 's new video!!! https://youtu.be/dzwR0dwzXNs

UtkarshSingh (Fri, 10 Nov 2017 11:34:38 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=wAdpbBtcHxmrXpYh4) @joe-alewine Actually, in testing environment, we are using solo, that's every peer is assumed to work honestly. see this : https://www.youtube.com/watch?v=8kRc2895uMY&index=3&list=PL7LSy0eQMvjvGM9ml1_ryjUOkO6CMEpDm

hhimanshu (Fri, 10 Nov 2017 16:09:22 GMT):
hello, I need help with fabric documentation, I created https://jira.hyperledger.org/browse/FAB-6962 outlining the entire issue. Thanks

mastersingh24 (Sat, 11 Nov 2017 12:15:35 GMT):
@hhimanshu - I added a comment to the JIRA, but while the .git stale error appears, the marble02 chaincode should actually be available in your CLI container

sstone1 (Sat, 11 Nov 2017 14:15:25 GMT):
hello - am trying to get byfn.sh to start a network that includes Fabric CAs. it looks like it includes a docker compose file that would do the trick `docker-compose-e2e.yaml` but the CLI container is not included, so the script falls over starting the network. any reason for that?

hhimanshu (Sun, 12 Nov 2017 16:40:22 GMT):
@mastersingh24 , Yes. Thanks. I believe that the documentation might be incorrect. I updated the JIRA as well. Please update that when you get a chance.

sstone1 (Mon, 13 Nov 2017 22:11:38 GMT):
I made a PR for `docker-compose-e2e.yaml` so that it works with `byfn.sh`: https://gerrit.hyperledger.org/r/#/c/15453/

UtkarshSingh (Tue, 14 Nov 2017 16:43:08 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=wAdpbBtcHxmrXpYh4) @joe-alewine hey, I got this, regarding consensus of Hyperledger Fabric: Hyperledger Fabric provides three ordering mechanisms: SOLO, Kafka, and Simplified Byzantine Fault Tolerance (SBFT), the latter of which has not yet been implemented in Fabric v1.0. SOLO is the Hyperledger Fabric ordering mechanism most typically used by developers experimenting with Hyperledger Fabric networks.SOLO involves a single ordering node. Kafka is the Hyperledger Fabric ordering mechanism that is recommended for production use. This ordering mechanism utilizes Apache Kafka, an open source stream processing platform that provides a unified, high-throughput, low-latency platform for handling real-time data feeds. In this case, the data consists of endorsed transactions and RW sets. The Kafka mechanism provides a crash fault-tolerant solution to ordering. SBFT stands for Simplified Byzantine Fault Tolerance. This ordering mechanism is both crash fault-tolerant and byzantine fault-tolerant, meaning that it can reach agreement even in the presence of malicious or faulty nodes. The Hyperledger Fabric community has not yet implemented this mechanism, but it is on their roadmap. These three ordering mechanisms provide alternate methodologies for agreeing on the order of transactions. Hope it will help you. Read in edX, official course provided by the Hyperledger team.

UtkarshSingh (Tue, 14 Nov 2017 16:45:09 GMT):
For all the beginners out there, like me. I would strongly recommend you all to go through a course, titled, Blockchain for Business - An Introduction to Hyperledger Technologies, on edX It will help you in building and visualizing the concepts.

laoqui (Wed, 15 Nov 2017 20:33:35 GMT):
hi everyone, i am not sure if this is the right channel to post this, but the `fabric-sdk-node` documentation page (https://fabric-sdk-node.github.io/) is not loading properly. seems like the css files for the theme are missing.

markparz (Thu, 16 Nov 2017 21:39:49 GMT):
Check out the playback 'playlist' off hyperledger fabric youtube channel for the latest recordings. https://www.youtube.com/channel/UCCFdgCWH_1vCndMPVqQlwZw/playlists?view_as=subscriber

rameshthoomu (Fri, 17 Nov 2017 04:31:40 GMT):
@laoqui fabric-sdk-node documentation issue is fixed https://fabric-sdk-node.github.io/

joe-alewine (Fri, 17 Nov 2017 13:00:28 GMT):
A note that our regular documentation workgroup call at 11 EST is canceled this week (the indespensible Anthony O'Dowd is probably in the air on the way back from Japan). It might possibly resume next week but there is no confirmation on that. Stay tuned

joe-alewine (Fri, 17 Nov 2017 13:00:28 GMT):
A note that our regular documentation workgroup call at 11 EST is canceled this week (the indespensible Anthony O'Dowd has been in Japan all week and flies back today iirc). The call might possibly resume next week -- RTP has a site holiday -- but a decision has not been made on that that. Stay tuned

qwertzu9 (Fri, 24 Nov 2017 08:54:14 GMT):
Hi guys, quick question: I just ran the "Tuna Fish Demo" on a VirtualBox. Are there more "Demos" like this available?

qwertzu9 (Fri, 24 Nov 2017 08:55:13 GMT):
(I found https://github.com/hyperledger/fabric-samples but I'm not sure whether These are different Demos.)

UtkarshSingh (Mon, 27 Nov 2017 07:09:34 GMT):
I somehow get confused on how to use hyperledger fabric in real world application for example, I want to apply permissioned blockchian in my institute having 100 users. Do I need to make 100 peers ? Or, I can make 5 peers, give 20 users per peer ?

nickgaski (Mon, 27 Nov 2017 14:53:18 GMT):
@UtkarshSingh - the peer has a direct correlation to a CA or intermediate CA that is defined in the scope of the network or in the scope of an application channel. You can use this CA to generate enrollment certificates for users to access peers and the channels the Org belongs to

MuhammadSalah (Mon, 27 Nov 2017 19:11:40 GMT):
@nickgaski can you please do a sample for interacting with CA? Issuing certs, and managing them to access peers, and invoke a chaincode?

joe-alewine (Mon, 27 Nov 2017 19:51:25 GMT):
@MuhammadSalah Take a look at these two YouTube videos from @smithbk -- https://www.youtube.com/watch?v=KZ5HThNjaeI and https://www.youtube.com/watch?v=WTW9QVO28l0

MuhammadSalah (Mon, 27 Nov 2017 19:55:28 GMT):
I have just added them on my list.

AutomatonPoliceman (Tue, 28 Nov 2017 12:55:09 GMT):
Has joined the channel.

AutomatonPoliceman (Tue, 28 Nov 2017 12:57:15 GMT):
I don't know who to direct this to but there is a dead link in the documentation: https://hyperledger-fabric.readthedocs.io/en/latest/samples.html#binaries The command curl -sSL https://goo.gl/fMh2s3 | bash referes to https://raw.githubusercontent.com/hyperledger/fabric/master/scripts/bootstrap-1.1.0-preview.sh which returns 404: Not Found

AutomatonPoliceman (Tue, 28 Nov 2017 13:01:04 GMT):
Alternative link: https://github.com/hyperledger/fabric/blob/v1.1.0-preview/scripts/bootstrap-1.1.0-preview.sh

UtkarshSingh (Thu, 30 Nov 2017 06:48:47 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=vfbjF7hG5Jdxnz2aB) @MuhammadSalah Yes, it would be helpful for us to understand Fabric CA, in more depth

UtkarshSingh (Thu, 30 Nov 2017 06:50:13 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=xnFytRExnf9mC9Wpa) @nickgaski Can I give privileges to some users ? For example, 2 are Admin, they have access of different chaincodes. Whereas, peers may have some chaincode installed in it. whose access should only be given to Admin only Since, as you said, any user can have access to any peers. So, How can I restrict other users (non-admin) to not use those chaincodes(meant only for admin)?

asuchit (Thu, 30 Nov 2017 09:21:38 GMT):
Is there any documentation online about how to write configtx.yaml file and how configtxgen works on msp directory ?

sravs (Thu, 30 Nov 2017 09:27:05 GMT):
I have completed the tutorial http://hyperledger-fabric.readthedocs.io/en/release/build_network.html and successfully deployed a business network over what it seems to be a generic hyperledger fabric blockchain. What i want to do now is to create a new peer in diffenrent machine but connected to the same blockchain. Can't find any information. Any help?

asuchit (Thu, 30 Nov 2017 09:52:13 GMT):
@sravs ou need to run it with docker swarm network.

asuchit (Thu, 30 Nov 2017 09:52:13 GMT):
@sravs you need to run it with docker swarm network.

nickgaski (Thu, 30 Nov 2017 15:55:36 GMT):
@UtkarshSingh - you can implement attribute based access control, such that a specific attribute in a user's enrollment certificate allows them call certain functions within a chaincode. The CA admin or registrar for the organization can register individual users with various attributes. Each organization will have a peer admin user, and it's this certificate that must be passed in order to perform peer-specific operations (install, instantiate, join).

nickgaski (Thu, 30 Nov 2017 15:57:13 GMT):
https://hyperledger-fabric-ca.readthedocs.io/en/latest/users-guide.html#attribute-based-access-control

wanghaihui (Fri, 01 Dec 2017 09:19:37 GMT):
[root@mgma fabcar]# node registerUser.js Store path:/opt/fabric-samples/fabcar/hfc-key-store Successfully loaded admin from persistence Failed to register: Error: fabric-ca request register failed with errors [[{"code":0,"message":"No identity type provided. Please provide identity type"}]] Hi everyone, any idea about this issue?

nickgaski (Fri, 01 Dec 2017 16:08:20 GMT):
@wanghaihui - let me take a look. Can you please share your version of node/npm and the tag on your docker images

joe-alewine (Fri, 01 Dec 2017 19:58:43 GMT):
@here just wanted to draw everyone attention to the work being done under the title FabricTOC at this repo: https://github.com/FabricTOC/FabricTOC This work has been the subject of the regular Friday Documentation Workgroup calls -- and has been mentioned in the hyperledger fabric mailing list -- but it's important for us to get as much feedback as possible. To allow collaboration easier than can be done in the main repo, this work is being maintained primarily by @odowdaibm and myself. Anyone who wants to make an edit can make one and then submit it to be merged by Anthony or myself. To get an idea where we're going with this, you can see the WIP TOC here: https://github.com/FabricTOC/FabricTOC/blob/master/docs/AdminGuide/AdminGuide.md And these are the two docs we've gotten farthest down the line. Here's one on Identity and MSPs: https://github.com/FabricTOC/FabricTOC/blob/master/docs/AdminGuide/KeyConcepts/IdentityandMembership/IdentityandMembership.md And here's a more general intro doc: https://github.com/FabricTOC/FabricTOC/blob/master/docs/AdminGuide/KeyConcepts/Network/Network.md Much of our focus right now is on Peers, which can be found here: https://github.com/FabricTOC/FabricTOC/blob/master/docs/AdminGuide/KeyConcepts/Peers/Peers.md As I said, we welcome all comments and suggestions!

joe-alewine (Fri, 01 Dec 2017 19:58:43 GMT):
@here just wanted to draw everyone attention to the work being done under the title "FabricTOC" at this repo: https://github.com/FabricTOC/FabricTOC This work has been the subject of the regular Friday Documentation Workgroup calls -- and has been mentioned in the hyperledger fabric mailing list -- but it's important for us to get as much feedback as possible from as many people as possible. To allow collaboration easier than can be done in the main repo, this work is being maintained primarily by @odowdaibm and myself with the current plan to merge docs over as they are completed. Anyone who wants to make an edit can make one in the repo and then submit a pull request for Anthony and myself to review To get an idea where we're going with this, you can see the WIP TOC here: https://github.com/FabricTOC/FabricTOC/blob/master/docs/AdminGuide/AdminGuide.md And these are the two docs we've gotten farthest down the line. Here's one on Identity and MSPs: https://github.com/FabricTOC/FabricTOC/blob/master/docs/AdminGuide/KeyConcepts/IdentityandMembership/IdentityandMembership.md And here's a more general intro doc: https://github.com/FabricTOC/FabricTOC/blob/master/docs/AdminGuide/KeyConcepts/Network/Network.md Much of our focus right now is on Peers, which can be found here: https://github.com/FabricTOC/FabricTOC/blob/master/docs/AdminGuide/KeyConcepts/Peers/Peers.md As I said, we welcome all comments and suggestions!

joe-alewine (Fri, 01 Dec 2017 19:58:43 GMT):
@here just wanted to draw everyone attention to the work being done under the title "FabricTOC" at this repo: https://github.com/FabricTOC/FabricTOC This work has been the subject of the regular Friday Documentation Workgroup calls -- and has been mentioned in the hyperledger fabric mailing list -- but it's important for us to get as much feedback as possible from as many people as possible. To allow collaboration easier than can be done in the main repo, this work is being maintained primarily by @odowdaibm and myself with the current plan to merge docs over as they are completed. Anyone who wants to make an edit can make one in the repo and then submit a pull request for Anthony and myself to review To get an idea where we're going with this, you can see the WIP TOC here: https://github.com/FabricTOC/FabricTOC/blob/master/docs/AdminGuide/AdminGuide.md And these are the two docs we've gotten farthest down the line. Here's one on Identity and MSPs: https://github.com/FabricTOC/FabricTOC/blob/master/docs/AdminGuide/KeyConcepts/IdentityandMembership/IdentityandMembership.md And here's a more general intro doc: https://github.com/FabricTOC/FabricTOC/blob/master/docs/AdminGuide/KeyConcepts/Network/Network.md Much of our focus right now (other than the work on the imminent alpha release) is on Peers, which can be found here: https://github.com/FabricTOC/FabricTOC/blob/master/docs/AdminGuide/KeyConcepts/Peers/Peers.md As I said, we welcome all comments and suggestions!

joe-alewine (Fri, 01 Dec 2017 19:58:43 GMT):
@here just wanted to draw everyone attention to the work being done under the title "FabricTOC" at this repo: https://github.com/FabricTOC/FabricTOC This work has been the subject of the regular Friday Documentation Workgroup calls -- and has been mentioned in the hyperledger fabric mailing list -- but it's important for us to get as much feedback as possible from as many people as possible. To allow collaboration easier than can be done in the main repo, this work is being maintained primarily by @odowdaibm and myself with the current plan to merge docs over as they are completed. Anyone who wants to make an edit can make one in the repo and then submit a pull request for Anthony and myself to review To get an idea where we're going with this, you can see the WIP TOC here: https://github.com/FabricTOC/FabricTOC/blob/master/docs/AdminGuide/AdminGuide.md And these are the two docs we've gotten farthest down the line. Here's one on Identity and MSPs: https://github.com/FabricTOC/FabricTOC/blob/master/docs/AdminGuide/KeyConcepts/IdentityandMembership/IdentityandMembership.md And here's a more general intro doc: https://github.com/FabricTOC/FabricTOC/blob/master/docs/AdminGuide/KeyConcepts/Network/Network.md Much of our focus right now (other than the work on the imminent alpha release) is on Peers, which can be found here: https://github.com/FabricTOC/FabricTOC/blob/master/docs/AdminGuide/KeyConcepts/Peers/Peers.md As I said, we welcome all comments and suggestions. And especially contributions!

joe-alewine (Fri, 01 Dec 2017 19:58:43 GMT):
@here just wanted to draw everyone attention to the work being done under the title "FabricTOC" at this repo: https://github.com/FabricTOC/FabricTOC This work has been the subject of the regular Friday Documentation Workgroup calls -- and has been mentioned in the hyperledger fabric mailing list -- but it's important for us to get as much feedback as possible from as many people as possible. To allow collaboration easier than can be done in the main repo, this work is being maintained primarily by @odowdaibm and myself with the current plan to merge docs over as they are completed. Anyone who wants to make an edit can make one in the repo and then submit a pull request for Anthony and myself to review To get an idea where we're going with this, you can see the WIP TOC here: https://github.com/FabricTOC/FabricTOC/blob/master/docs/AdminGuide/AdminGuide.md And these are the two docs we've gotten farthest down the line. Here's one on Identity and MSPs: https://github.com/FabricTOC/FabricTOC/blob/master/docs/AdminGuide/KeyConcepts/IdentityandMembership/IdentityandMembership.md And here's a more general intro doc: https://github.com/FabricTOC/FabricTOC/blob/master/docs/AdminGuide/KeyConcepts/Network/Network.md Much of our focus right now (other than the work on the imminent alpha release) is on Peers, which can be found here: https://github.com/FabricTOC/FabricTOC/blob/master/docs/AdminGuide/KeyConcepts/Peers/Peers.md As I said, we welcome all comments and suggestions. Healthy debate is important. And especially contributions!

habpygo (Sun, 03 Dec 2017 10:49:59 GMT):
Going through it right now @joe-alewine. Awesome! I like the pictures and so far my take is that finally some proper documentation is coming; something HLF deserves.

habpygo (Sun, 03 Dec 2017 10:49:59 GMT):
Going through it right now @joe-alewine . Awesome! I like the pictures and so far my take is that finally some proper documentation is coming; something HLF deserves.

paul.sitoh (Sun, 03 Dec 2017 14:21:24 GMT):
@here does anyone know where I can get hold of documentation explaining the source level structure/architecture of the fabric repo. In other words, something to describe the roles of the folders in github.com/hyperledger/fabric, etc.

joe-alewine (Sun, 03 Dec 2017 21:22:03 GMT):
@paul.sitoh If such a doc exists I'm unaware of it. But the contents of the folders should be pretty self explanatory if you browse around in them

wanghaihui @nickgaski [root@mgma fabcar]# node -v v6.9.5 [root@mgma fabcar]# npm -v 3.10.10 [root@mgma fabcar]# docker images REPOSITORY dev-peer0.org1.example.com-fabcar-1.0 dev-peer1.org2.example.com-mycc-1.0 dev-peer0.org1.example.com-mycc-1.0 dev-peer0.org2.example.com-mycc-1.0 hyperledger/fabric-tools hyperledger/fabric-tools hyperledger/fabric-couchdb hyperledger/fabric-couchdb hyperledger/fabric-kafka hyperledger/fabric-kafka hyperledger/fabric-zookeeper hyperledger/fabric-zookeeper hyperledger/fabric-orderer hyperledger/fabric-orderer hyperledger/fabric-peer hyperledger/fabric-peer hyperledger/fabric-javaenv hyperledger/fabric-javaenv hyperledger/fabric-ccenv hyperledger/fabric-ccenv hyperledger/fabric-ca hyperledger/fabric-ca hyperledger/fabric-baseos [root@mgma fabcar]# (Mon, 04 Dec 2017 02:38:13 GMT):
TAG IMAGE ID CREATED SIZE latest 7524f46a0244 43 seconds ago 173MB latest 801178cdc1a4 About a minute ago 173MB latest ebaae6b06bbe About a minute ago 173MB latest 6eac3396c08c 2 minutes ago 173MB latest 0403fd1c72c7 4 months ago 1.32GB x86_64-1.0.0 0403fd1c72c7 4 months ago 1.32GB latest 2fbdbf3ab945 4 months ago 1.48GB x86_64-1.0.0 2fbdbf3ab945 4 months ago 1.48GB latest dbd3f94de4b5 4 months ago 1.3GB x86_64-1.0.0 dbd3f94de4b5 4 months ago 1.3GB latest e545dbf1c6af 4 months ago 1.31GB x86_64-1.0.0 e545dbf1c6af 4 months ago 1.31GB latest e317ca5638ba 4 months ago 179MB x86_64-1.0.0 e317ca5638ba 4 months ago 179MB latest 6830dcd7b9b5 4 months ago 182MB x86_64-1.0.0 6830dcd7b9b5 4 months ago 182MB latest 8948126f0935 4 months ago 1.42GB x86_64-1.0.0 8948126f0935 4 months ago 1.42GB latest 7182c260a5ca 4 months ago 1.29GB x86_64-1.0.0 7182c260a5ca 4 months ago 1.29GB latest a15c59ecda5b 4 months ago 238MB x86_64-1.0.0 a15c59ecda5b 4 months ago 238MB x86_64-0.3.1 4b0cab202084 6 months ago 157MB

wanghaihui (Mon, 04 Dec 2017 02:39:38 GMT):
@nickgaski I was following the documents, and is this the image's issue?

wanghaihui (Mon, 04 Dec 2017 03:03:44 GMT):
@nickgaski I have found that is docker image issue, have to use ./fabric-preload.sh 1.1.0-preview to download images. Thanks for your recommandation.

paul.sitoh (Mon, 04 Dec 2017 20:40:25 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=uLZLTYm9KiD44Evp3) @joe-alewine Could you explain the difference between top level `peer` folder and the `peer` folder under `core` folder?

asuchit (Tue, 05 Dec 2017 10:30:21 GMT):
Is there any documentation for configtxgen and configtx.yaml ?

asuchit (Tue, 05 Dec 2017 10:36:40 GMT):
Where can I find the documentation for the msp directory structure in case of peer, orderer, root CA, intermediate CA ?

joe-alewine (Tue, 05 Dec 2017 13:17:34 GMT):
@asuchit configtx: http://hyperledger-fabric.readthedocs.io/en/release/configtx.html configtxgen: http://hyperledger-fabric.readthedocs.io/en/release/configtxgen.html A doc on that Identity/MSP information is currently in review. You can see a proto version here: https://github.com/FabricTOC/FabricTOC/blob/master/docs/AdminGuide/KeyConcepts/IdentityandMembership/IdentityandMembership.md

joe-alewine (Tue, 05 Dec 2017 15:33:27 GMT):
@paul.sitoh In general, the folders under "core" designate the configuration and management of components at an internal level. So in the case of core/peer, this is the lower level organization of the peer process, for example "peer node start". It's also where the peer channels are maintained. The higher level folders -- for example, that top level "peer" folder -- are about the entry points to the peer (as in "peer chaincode" and "peer node").

paul.sitoh (Tue, 05 Dec 2017 17:21:11 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=LyrWGyKdgszhyBTyq) @joe-alewine Thanks. Seemed strange not to lump all peer related stuff under one folder call `peer` and under that `core`, `interfaces`, etc.

paul.sitoh (Tue, 05 Dec 2017 17:21:11 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=LyrWGyKdgszhyBTyq) @joe-alewine Thanks for infomation. Seemed strange not to lump all peer related stuff under one folder call `peer` and under that `core`, `interfaces`, etc.

nickgaski (Wed, 06 Dec 2017 01:59:13 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=dAaZCTyJYhX92eiSq) @paul.sitoh +1 paul, but we'll find a way through; thanks joe

joe-alewine (Wed, 06 Dec 2017 12:48:29 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=EfPYsqShRBLAmNEg6) @asuchit You're welcome.

joe-alewine (Wed, 06 Dec 2017 12:50:13 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=CLJXJ5oQPA2FSHTsP) @nickgaski @paul.sitoh Agreed that would be a better organizational structure, but as @muralisr told me, "it's not organized until proven otherwise"

joe-alewine (Wed, 06 Dec 2017 12:50:13 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=CLJXJ5oQPA2FSHTsP) @nickgaski @paul.sitoh Agreed that would probably be a better organizational structure, but as @muralisr told me, when it comes to the folders on github, "it's not organized until proven otherwise" :)

nmpacheco@gmail.com (Tue, 12 Dec 2017 11:09:03 GMT):
Has joined the channel.

joe-alewine (Thu, 14 Dec 2017 16:38:23 GMT):
@here just wanted to draw everyone's attention once again to the work being done under the title "FabricTOC" at this repo: https://github.com/FabricTOC/FabricTOC This work has been the subject of the regular Friday Documentation Workgroup calls -- and has been mentioned in the hyperledger fabric mailing list -- but it's important for us to get as much feedback as possible from as many people as possible. To allow collaboration easier than can be done in the main repo, this work is being maintained primarily by @odowdaibm and myself with the current plan to merge docs over as they are completed. Anyone who wants to make an edit can make one in the FabricTOC repo and then submit a pull request for Anthony and myself to review. To get an idea where we're going with this, you can see the WIP TOC here (with proposals on where and how to include the documentation that currently resides in read the docs): https://github.com/FabricTOC/FabricTOC/blob/master/docs/Guide/Guide.md And these are the two docs we've gotten farthest down the line. Here's one on Identity and MSPs: https://github.com/FabricTOC/FabricTOC/blob/master/docs/Guide/KeyConcepts/IdentityandMembership/IdentityandMembership.md A version of this is currently in review to fold into read the docs: https://gerrit.hyperledger.org/r/c/15933/ And here's a more general intro doc: https://github.com/FabricTOC/FabricTOC/blob/master/docs/Guide/KeyConcepts/Network/Network.md Much of our focus right now is on Peers, which can be found here: https://github.com/FabricTOC/FabricTOC/blob/master/docs/Guide/KeyConcepts/Peers/Peers.md As I said, we welcome all comments and suggestions about this TOC and any of the documents within in (whatever their stage of development). Healthy debate is important and nothing has been set in stone. For example, it has been proposed to move the docs back to markdown after several months of them being in rst. @cbf has offered to take that task on, but even if you can automate much of that process there's always a lot of cleanup to do. And of course if you see a topic or a doc you want to contribute to, we welcome that too!

Roger12 1 (Thu, 14 Dec 2017 16:53:46 GMT):
hi, how to edit crypto config yaml file to generate crypto for four organization and also wants to change the name of organization from org1 to something else i.e instead of org1 I would like to have name like 'Unisef' and also wants to change domain from example.com to "KPLO.com" .so, Is it possible to do this in hyperledger 1.0 ??? because when I tried doing this changes , during user enroll i'm getting error : unable to fine the keyvaulestore. and when I'll again change the organization name to default i.e just 'org1' and domain to 'example.com'. Then everything works fine..? So what I'm trying to do is that thing is possible or not??? I want my network peer should look like Unisef.KPLO.com instead of org1.example.com?? Pls help?? Where I'll get documentation for this . In official documents They have not explained about this things.

odowdaibm (Fri, 15 Dec 2017 06:06:19 GMT):
@here documentation WG call starting for Eastern hemi now

odowdaibm (Fri, 15 Dec 2017 06:06:36 GMT):
@here will be run again later today for western hemi

odowdaibm (Fri, 15 Dec 2017 06:59:53 GMT):
Added new section to peer concept https://github.com/FabricTOC/FabricTOC/blob/master/docs/Guide/KeyConcepts/Peers/Peers.md#applications-and-peers

odowdaibm (Fri, 15 Dec 2017 07:00:36 GMT):
As @joe-alewine says, we're looking for comments on this section before adding to READTHEDOCS in the short term

simsc (Fri, 15 Dec 2017 17:41:13 GMT):
We are looking for additional collaborators for the https://github.com/fabrictoc/fabrictoc. If you would be interested in contributing, what can we do to help you take the first step?

rjones (Fri, 15 Dec 2017 17:46:05 GMT):
@simsc I notice this repo is not set up for DCO enforcement, and there are tons of unsigned commits.

rjones (Fri, 15 Dec 2017 17:47:00 GMT):
not sure why this repo is set up outside the hyperledger namespace.

rjones (Fri, 15 Dec 2017 17:47:11 GMT):
there will be a squash commit in the future ¯\_(ツ)_/¯

joe-alewine (Fri, 15 Dec 2017 19:22:42 GMT):
@rjones This repo was setup to allow easier collaboration on the creation and staging of documentation that will be moved into the hyperledger docs. It is not a new repo for docs in themselves, and anything written in FabricTOC will still be subject to community approval to get into the official docs. This is obviously not an ideal setup, but reflects the realities of how difficult it is to collaborate in the current structure. Fwiw, @odowdaibm and I have been working in this repo with the knowledge and approval of @tkuhrt

joe-alewine (Fri, 15 Dec 2017 19:22:42 GMT):
@rjones This repo was setup to allow easier collaboration on the creation and staging of documentation that will be moved into the hyperledger docs. It is not a new repo for docs in themselves. This is obviously not an ideal setup, but reflects the realities of how difficult it is to collaborate in the current structure. Fwiw, @odowdaibm and I have been working in this repo with the knowledge and approval of @tkuhrt

joe-alewine (Fri, 15 Dec 2017 19:22:42 GMT):
@rjones This repo was setup to allow easier collaboration on the creation and staging of documentation that will be moved into the hyperledger docs. It is not a new repo for docs in themselves, and anything written using FabricTOC will still be subject to community approval to get into the official docs. This is obviously not an ideal setup, but reflects the realities of how difficult it is to collaborate in the current structure. Fwiw, @odowdaibm and I have been working in this repo with the knowledge and approval of @tkuhrt

eperry (Sun, 17 Dec 2017 16:31:43 GMT):
Hi All, is there a good getting started guide , I found this one https://www.ibm.com/developerworks/cloud/library/cl-ibm-blockchain-101-quick-start-guide-for-developers-bluemix-trs/index.html but it does not seem to have any steps in it to validate what you are doing as you do it.

guoger (Mon, 18 Dec 2017 04:58:08 GMT):
@eperry have you tried this: http://hyperledger-fabric.readthedocs.io/en/latest/build_network.html

eperry (Tue, 19 Dec 2017 14:16:26 GMT):
I will look at that today, sort of got things working but deleted and want to start over

varun-raj (Wed, 20 Dec 2017 10:08:20 GMT):
Have anyone tried creating a network with more than one peer? Is there any place I can find any documentation for the same?

joe-alewine (Wed, 20 Dec 2017 13:13:12 GMT):
@varun-raj Try this: http://hyperledger-fabric.readthedocs.io/en/latest/build_network.html

keerthiGiridhari (Fri, 22 Dec 2017 07:52:35 GMT):
hey there hi need help with byfn.sh file in first-network sample...the terminal closes fast without allowing me to check the log don't know what i'm doing wrong...got everything installed perfectly help please.

gbodra (Tue, 26 Dec 2017 14:08:57 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=EKiF3Nst22qsPbHn7) @simsc I'm new to Fabric and hyperledger projects but I'm eager to contribute. Is there any area you need a hand?

thiago-moreira (Fri, 29 Dec 2017 12:56:39 GMT):
@keerthiGiridhari, try send output of command to a file that after could you look. Example: ./byfn.sh -m up >> logs

ronald.petty (Fri, 29 Dec 2017 13:33:36 GMT):
Hi. Just curious do minor doc updates go through Gerrit/Jira? (found a minor path issue, tried PR, but fails)

ronald.petty (Fri, 29 Dec 2017 13:33:36 GMT):
Hi. Just curious do minor doc updates go through Gerrit/Jira? I added the DCO (failed first as I did n't do it) but unclear if its passed now. Can a GH pro double check if this is good or not? https://github.com/hyperledger/fabric/pull/90 (can't tell if DCO error is resolved or still happening as there are no timestamps to compare on the history there)

tkuhrt (Fri, 29 Dec 2017 14:38:49 GMT):
@ronald.petty : documentation changes should be made through a pull request through Gerrit. It will require a Jira bug. See https://hyperledger-fabric.readthedocs.io/en/release/Gerrit/changes.html and https://hyperledger-fabric.readthedocs.io/en/release/Gerrit/gerrit.html

ronald.petty (Fri, 29 Dec 2017 14:50:03 GMT):
Thanks @tkuhrt will look into it

hennesb (Sat, 30 Dec 2017 11:49:34 GMT):
Hi all , I'm a newbie to HyperLedger just noticed a case problem on a function when trying out Writing Your First Application. In the changeCarOwner section I had to change the code fcn: 'changeCarOwner' to fcn: 'changeCarowner'.

Amir (Tue, 09 Jan 2018 19:34:55 GMT):
Hello, org3-artifacts subdirectory is missing in the github, which is referenced here (http://hyperledger-fabric.readthedocs.io/en/latest/channel_update.html#setup-the-environment). Thank you

nickgaski (Tue, 09 Jan 2018 21:15:42 GMT):
@Amir - switch to master branch. I bet you're on release

nickgaski (Tue, 09 Jan 2018 21:16:27 GMT):
https://github.com/hyperledger/fabric-samples/tree/master/first-network/org3-artifacts

philviana (Tue, 09 Jan 2018 22:34:34 GMT):
Hi. I am running a Hyperledger instance in Bluemix and I instantiated the `fabcar` example on my channel. I am pretty sure I was able to enroll the admin user and create the new `user1` user (respectively, `enrollAdmin.js` and `registerUser.js` files in fabcar), but I get the error below when I try to invoke the chaincode: ```[phil@oc4270681710 fabcar]$ node invoke.js /home/phil/go_workspace/src/github.com/hyperledger/fabric-samples/fabcar/node_modules/fabric-client/lib/Remote.js:146 throw new Error('PEM encoded certificate is required.'); ^ Error: PEM encoded certificate is required. at new Endpoint (/home/phil/go_workspace/src/github.com/hyperledger/fabric-samples/fabcar/node_modules/fabric-client/lib/Remote.js:146:11) at Peer.Remote (/home/phil/go_workspace/src/github.com/hyperledger/fabric-samples/fabcar/node_modules/fabric-client/lib/Remote.js:95:20) at Peer (/home/phil/go_workspace/src/github.com/hyperledger/fabric-samples/fabcar/node_modules/fabric-client/lib/Peer.js:53:3) at Client.newPeer (/home/phil/go_workspace/src/github.com/hyperledger/fabric-samples/fabcar/node_modules/fabric-client/lib/Client.js:173:14) at Object. (/home/phil/go_workspace/src/github.com/hyperledger/fabric-samples/fabcar/invoke.js:21:26) at Module._compile (module.js:570:32) at Object.Module._extensions..js (module.js:579:10) at Module.load (module.js:487:32) at tryModuleLoad (module.js:446:12) at Function.Module._load (module.js:438:3) ```

philviana (Tue, 09 Jan 2018 22:35:17 GMT):
Any idea why this happens? I found a developerWorks question that points to needing fabric-ca to be running locally (which is obviously not the case...)

nickgaski (Wed, 10 Jan 2018 01:07:31 GMT):
@philviana - this is actually a good one to debug. Did you send the enroll call to your CA on the IBM Bluemix Service? If so, and the certs were returned to the local `hfc-key-store` then this should still function as expected. Let's go through it tomorrow?

nickgaski (Wed, 10 Jan 2018 01:08:52 GMT):
obviously it will fail if you're using locally generated x509 certificates from the containers in the docker compose

nickgaski (Wed, 10 Jan 2018 01:08:52 GMT):
obviously it will fail if you're using locally generated x509 certificates from the CA container in the docker compose

nickgaski (Wed, 10 Jan 2018 01:10:08 GMT):
To expand... you would need to open your service credentials from your IBP instance and replace the CA admin username and password in the fabcar `enrollAdmin.js` program

nickgaski (Wed, 10 Jan 2018 01:10:50 GMT):
admin and adminpw won't correspond to your IBP instance. Let's work one on one through this tomorrow; it's worth making it work because the application code is very simple and consumable

philviana (Wed, 10 Jan 2018 01:36:27 GMT):
@nickgaski Thanks for your reply. Yes, I'd like to go through it tomorrow. I did enroll to Bluemix and got the user context into the `hfc-key-store` folder. I also replaced the CA admin and password in `enrollAdmin.js`. I did some more debugging between my message and your reply and I think I may have a lead - let me know if it makes sense: since I'm connecting to Bluemix using gRPCs, when the peer variable is created in `invoke.js` it actually has a null `pem` variable in it. I noticed that the original code uses gRPC and not gRPCs - perhaps the PEM is not needed then? By looking at the call stack, it seems that invoke.js instantiates a peer with `newPeer(url, opts)` from `Client.js`, not passing an `opts` parameter. It turns out that the `opts` parameter is necessary to read the PEM in `Remote.js`. Since `pem == null` I get the failure. Code from Remote.js: ``` constructor(url, opts) { var pem = null; var ssl_target_name_override = ''; var default_authority = ''; if (opts && opts.pem) { pem = opts.pem; } ```

philviana (Wed, 10 Jan 2018 01:36:27 GMT):
@nickgaski Thanks for your reply. Yes, I'd like to go through it tomorrow. I did enroll to Bluemix and got the user context into the `hfc-key-store` folder. I also replaced the CA admin and password in `enrollAdmin.js`. I did some more debugging between my message and your reply and I think I may have a lead - let me know if it makes sense: since I'm connecting to Bluemix using gRPCs, when the peer variable is created in `invoke.js` it actually has a null `pem` variable in it. I noticed that the original code uses gRPC and not gRPCs - perhaps the PEM is not needed then? By looking at the call stack, it seems that invoke.js instantiates a peer with `newPeer(url, opts)` from `Client.js`, not passing an `opts` parameter. It turns out that the `opts` parameter is necessary to read the PEM in `Remote.js`. Since `pem == null` I get the failure. Code from Remote.js: constructor(url, opts) { var pem = null; var ssl_target_name_override = ''; var default_authority = ''; if (opts && opts.pem) { pem = opts.pem; }

philviana (Wed, 10 Jan 2018 01:36:27 GMT):
@nickgaski Thanks for your reply. Yes, I'd like to go through it tomorrow if you're available :) I did enroll to Bluemix and got the user context into the `hfc-key-store/` folder. I also replaced the CA admin and password in `enrollAdmin.js`. I did some more debugging between my original message and your reply and I think I may have a lead - let me know if it makes sense: since I'm connecting to Bluemix using gRPCs, when the peer variable is created in `invoke.js` it actually has a null `pem` variable in it (that goes in the constructor). I noticed that the original fabcar code uses gRPC and not gRPCs - perhaps the PEM is not needed then and that's why the original fabcar code doesn't fail with the same message. By looking at the call stack, it seems that `invoke.js` instantiates a peer with `newPeer(url, opts)` from `Client.js`, not passing an `opts` parameter. It turns out that the `opts` parameter is necessary to read the PEM in `Remote.js`. Since `pem == null` and gRPCs is used (not gRPC) I get the failure. See the code from Remote.js: ``` constructor(url, opts) { var pem = null; var ssl_target_name_override = ''; var default_authority = ''; if (opts && opts.pem) { pem = opts.pem; } ``` So I guess a possible solution is to pass the PEM in the opts of the `fabric_client.newPeer()` call in `invoke.js`.

CodeReaper (Wed, 10 Jan 2018 14:29:16 GMT):
Any documents or examples on how to implement Intermediate CAs in a fabric network?

joe-alewine (Wed, 10 Jan 2018 15:50:16 GMT):
CAs have their own doc repo: http://hyperledger-fabric-ca.readthedocs.io/en/latest/

joe-alewine (Wed, 10 Jan 2018 15:50:16 GMT):
@CodeReaper CAs have their own doc repo: http://hyperledger-fabric-ca.readthedocs.io/en/latest/

philviana (Wed, 10 Jan 2018 17:19:20 GMT):
@nickgaski I'm debugging the issue now... the call to `grpc.credentials.createSsl(new Buffer(pem))` in the `Endpoint` constructor seems to not be passing the pem

nickgaski (Wed, 10 Jan 2018 17:27:34 GMT):
hey phi I forgot about this piece - https://www.ibm.com/developerworks/cloud/library/cl-deploy-sample-application-ibm-blockchain-platform/index.html

nickgaski (Wed, 10 Jan 2018 17:28:06 GMT):
we gotta add TLS to the client side

philviana (Wed, 10 Jan 2018 19:44:14 GMT):
@nickgaski Did some more digging. Something doesn't seem right... Per the instructions, I created the `extractCerts.js` file and ran it. It was able to retrieve the PEM but it stored it as a JSON containing the PEM contents. I expected them certificate to be delimited by `BEGIN CERTIFICATE` and `END CERTIFICATE` but instead I see this: ```{"pem":"-----BEGIN CERTIFICATE-----\r\nMIIElDCCA3ygAwIBAgIQAf2j ... ... ... ZWVbd4=\r\n-----END CERTIFICATE-----\r\n"}```

philviana (Wed, 10 Jan 2018 20:11:23 GMT):
Also, on line 95 of `Remote.js` I can see that the `pem` object is correct (same contents as the PEM file), but then on line 146 the pem object is null, meaning the parsing/instantiation of the Endpoint cause the PEM to be lost. https://github.com/hyperledger/fabric-sdk-node/blob/1d3facbfd952bac63db4b44c6c6a649c0d8ac9ab/fabric-client/lib/Remote.js#L95

philviana (Wed, 10 Jan 2018 20:45:59 GMT):
@nickgaski I realized what was wrong... The PEM was not being passed properly in the orderer instantiation. Thanks for the help! I was able to invoke and query using Bluemix.

nickgaski (Wed, 10 Jan 2018 22:08:42 GMT):
@philviana - we should update the devworks article; can you ping one of the authors with your fix. And are you saying that the transactionProposal to the orderer was not passing the cert properly?

philviana (Wed, 10 Jan 2018 22:13:53 GMT):
@nickgaski: About the orderer: I misplaced the addition of the `pem`, so it was a user error. About the update: I'll reach out to them. The current fabcar code no longer has the `var opts = { ... }` structure.

odowdaibm (Tue, 16 Jan 2018 09:28:57 GMT):
This is a great place for your questions

SjirNijssen (Tue, 16 Jan 2018 12:22:39 GMT):
In which code can I find the complete data structure of the blocks? Thanks for any help

toddinpal (Mon, 22 Jan 2018 13:24:35 GMT):
Is there any write-up/documentation that describes the various authorizations that are possible with Fabric? What I mean, is the current documentation is extremely lean on what does using a role of Admin allow you to do and what determines those permissions?

joe-alewine (Mon, 22 Jan 2018 15:35:46 GMT):
@toddinpal A doc like that (along with a number of similar conceptual docs) is in the works. We have a CR out for a doc on Identity and Membership that touches on some of that. It hasn't been merged yet but if you want to take a look here's a staged copy: https://github.com/joealewine/FabricTOC/blob/master/docs/Guide/KeyConcepts/IdentityandMembership/IdentityandMembership.md

Ammu (Tue, 23 Jan 2018 06:07:24 GMT):
front end application what are the things we need to use for hyperledger fabrics ?

joe-alewine (Tue, 23 Jan 2018 12:53:10 GMT):
@Ammu This will provide a high level overview of what Fabric applications can do: http://hyperledger-fabric.readthedocs.io/en/latest/write_first_app.html Then you'll probably want to check out the sdk documentation: https://fabric-sdk-node.github.io/

toddinpal (Tue, 23 Jan 2018 14:58:12 GMT):
Hi @joe-alewine That's a great document, really well done, but not really what I'm looking for. I'm more interested in authorization, i.e., who can do what and how is that defined/determined.

joe-alewine (Tue, 23 Jan 2018 15:07:01 GMT):
@toddinpal Yeah it sounds like you're looking for a conceptual doc that's more explicitly about policies -- ie, Explicit Policies and Implicit Metapolicies, and also how mod policies work. That's been in the works for a while but we haven't quite gotten there yet. We do have a tutorial that touches on how these policies work and can be changed, though (it's an extension of BYFN). http://hyperledger-fabric.readthedocs.io/en/latest/channel_update.html

joe-alewine (Tue, 23 Jan 2018 15:07:01 GMT):
@toddinpal Yeah it sounds like you're looking for a conceptual doc that's more explicitly about policies (Explicit Policies and Implicit Metapolicies, and also how mod policies work). That's been on the drawing board for a while but we haven't quite gotten there yet. We do have a tutorial that touches on how these policies work and can be changed, though. It's an extension of the BYFN tutorial: http://hyperledger-fabric.readthedocs.io/en/latest/channel_update.html

cbf (Mon, 29 Jan 2018 18:30:13 GMT):
@odowdaibm @joe-alewine so, where are we on docs? I believe that for 1.1.0-alpha we merged the ability to add .md files

cbf (Mon, 29 Jan 2018 18:30:47 GMT):
while I have a WIP CR up against fabric-docs with the converted .rst, we could take it a bit at a time

cbf (Mon, 29 Jan 2018 18:31:19 GMT):
but we also need to think about integrating better between the various repos (fabric-ca, fabric-sdk-* etc)

cbf (Mon, 29 Jan 2018 18:31:42 GMT):
and refactoring the TOC per the WIP in your repo

joe-alewine (Mon, 29 Jan 2018 18:48:01 GMT):
@cbf In the short term I don't there's any big necessity to switch over to markdown wholesale -- we can take that one doc at a time (as we add to or combine docs). The bigger need I think is to create a separate repo, and if possible do something you first brought up, which is to move to NACRs in that repo. That's going to be the biggest value add I think. Figuring out how to integrate fabric-ca and fabric-sdk is going to take some time. Anthony and I haven't really discussed that as yet, except to observe in passing that the fabric-ca stuff will probably make the most sense in the CA reference section.

joe-alewine (Mon, 29 Jan 2018 18:48:01 GMT):
@cbf Now that we can combine rst and markdown in the docs, in the short term I don't there's any big necessity to switch over to markdown wholesale -- we can take that one doc at a time (as we add to or combine docs). The bigger need I think is to create a separate repo, and if possible do something you first brought up, which is to move to NACRs in that repo. That's going to be the biggest value add I think. Figuring out how to integrate fabric-ca and fabric-sdk is going to take some time. Anthony and I haven't really discussed that as yet, except to observe in passing that the fabric-ca stuff will probably make the most sense in the CA reference section.

joe-alewine (Mon, 29 Jan 2018 18:48:01 GMT):
@cbf Now that we can combine rst and markdown in the docs, in the short term I don't there's any big necessity to switch over to markdown wholesale -- we can take that one doc at a time (as we add to or combine docs). The bigger need I think is to create a separate repo, and if possible do something you've mentioned, which is to move to NACRs in that repo. That's going to be the biggest value add I think. Figuring out how to integrate fabric-ca and fabric-sdk is going to take some time. Anthony and I haven't really discussed that as yet, except to observe in passing that the fabric-ca stuff will probably make the most sense in the CA reference section.

cbf (Mon, 29 Jan 2018 19:43:09 GMT):
fabric-docs already exists for this @joe-alewine @odowdaibm

AdnanC (Tue, 30 Jan 2018 16:10:48 GMT):
@joe-alewine @scottz a few comments and nits on the Couchdb doc at http://hyperledger-fabric.readthedocs.io/en/latest/couchdb_as_state_database.html 1. Period missing after "with the index definition formatted in JSON following the CouchDB index JSON syntax 2. “Any index in the chaincode’s META-INF/statedb/couchdb/indexes directory will be packaged up and installed with the chaincode on a peer” ---It is not clear what this sentence tries to convey. Does “with” here means “at the same time”? this sentence seems to indicate that the index is installed on a peer (incorrect) which is clarified in a correct way in next sentence. 3. “... the index will automatically be deployed to the peer’s channel state database” more precisely, it is deployed to the peer’s chaincode-channel state database 4. “For CouchDB installations outside of the docker images supplied with Fabric, the local.ini file must be edited….” it’d be helpful to provide the location of local.ini file. 5. “In fact, there is no guarantee the result set is stable between chaincode execution and commit time for rich queries, ”----this info probably merits a separate “! note” box.

joe-alewine (Tue, 30 Jan 2018 16:30:53 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=PK4AapNP9QqqCcwQv) @AdnanC @dave.enyeart

dave.enyeart (Tue, 30 Jan 2018 17:53:43 GMT):
@AdnanC I wrote that doc topic, and you are probably the next closest to it at this point. I agree with all your points. Could you draft a CR with the updates?

Ammu (Wed, 31 Jan 2018 07:32:09 GMT):
where our data's will store in couchdb?

cbf (Wed, 31 Jan 2018 14:11:12 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=smkfeoxNYEYeDS69k) @Ammu yes, if so configured

Dark_Knight (Wed, 31 Jan 2018 14:14:26 GMT):
Hello everyone, I am working on Hyperledger Fabric Consensus network. I wanted to know if it is possible to implement the rollback mechanism in case of transaction failure and if yes, which type of Consensus has to be employed. Or if some other properties have also to be taken into consideration?

rohitadivi (Thu, 01 Feb 2018 01:21:45 GMT):
@joe-alewine @scottz A suggestion on the capabilities in a configuration upgrade at http://hyperledger-fabric.readthedocs.io/en/master/upgrade_to_one_point_one.html#capabilities-in-a-configuration-update .. It would be nice to add a link to the Re-configuring your first network http://hyperledger-fabric.readthedocs.io/en/master/channel_update.html which shows how to do a channel configuration. This would be helpful for the users who are new to the concept of channel configuration

odowdaibm (Thu, 01 Feb 2018 11:51:46 GMT):
I'd welcome feedback on a new Peer topic a few of us have been working @joe-alewine @SjirNijssen and others. Here's a sandbox build in RTD: http://fabricdocs1.readthedocs.io/en/latest/peers/Peers.html# Happy to take questions here or on the mailing list. This is based on work we've being doing in the Documentation Workgroup. I've created a patch, which I'd like to get committed given satisfactory responses. Thanks for any input you might have.

odowdaibm (Thu, 01 Feb 2018 19:33:05 GMT):
Thanks to @SjirNijssen and john clark for their extensive comments. Topic now looking even better http://fabricdocs1.readthedocs.io/en/latest/peers/Peers.html

odowdaibm (Thu, 01 Feb 2018 19:33:33 GMT):
I've created a patch to include this, so hopefully you'll see it live soon

varun-raj (Sat, 03 Feb 2018 13:24:00 GMT):
Can someone explain me what all possible fields we can pass to getAttributeValue?

varun-raj (Sat, 03 Feb 2018 13:24:00 GMT):
Can someone explain me what all possible fields we can pass to ClientIdentity getAttributeValue?

joe-alewine (Sat, 03 Feb 2018 19:16:56 GMT):
@varun-raj That's probably a better question for #fabric-questions

paul.sitoh (Mon, 05 Feb 2018 15:34:27 GMT):
Folks, I have noticed that there are two docs site https://openblockchain.readthedocs.io and http://hyperledger-fabric.readthedocs.io/. Which one is the official version or which is more up to date?

joe-alewine (Mon, 05 Feb 2018 15:36:07 GMT):
The openblockchain stuff is very old -- even older than 0.6 I think. hyperledger-fabric.readthedocs.io is the current docs

joe-alewine (Mon, 05 Feb 2018 15:36:07 GMT):
@paul.sitoh The openblockchain stuff is very old -- even older than 0.6 I think. hyperledger-fabric.readthedocs.io is the current docs

paul.sitoh (Mon, 05 Feb 2018 15:38:10 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=sYYuQbJegSt3P8TpR) @joe-alewine thanks.

cbf (Wed, 07 Feb 2018 18:06:56 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=LBYGS4qGsQostiMEs) @paul.sitoh yeah, someone has published this from the archived version of the original repository... unfortunately, there isn't much we can do to get it taken down.

paul.sitoh (Fri, 09 Feb 2018 08:56:47 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=x5eJAY58hcAdFcKEa) @cbf Thanks

sachikoy (Sat, 10 Feb 2018 03:27:25 GMT):
Hi, I guess Fabric Node.js SDK now works with node v7.x, and v6.x is not supported. The reason I think so is that the balance-transfer sample (v1.1.0-alpha) didn't work with node v6.x. If my understanding is correct, could somebody please update the Prerequisites document? http://hyperledger-fabric.readthedocs.io/en/latest/prereqs.html#node-js-runtime-and-npm

yacovm (Mon, 12 Feb 2018 12:24:28 GMT):
This one is cool - can we have something like this too, @cbf , @joe-alewine ?

cbf (Mon, 12 Feb 2018 13:23:17 GMT):
they are likely using a custom (or alternative) template

paul.sitoh (Fri, 16 Feb 2018 11:48:37 GMT):
Anyone know where I can get hold of documentation for setting Kafka?

paul.sitoh (Fri, 16 Feb 2018 11:48:37 GMT):
Anyone know where I can get hold of documentation for setting Kafka? Or let me rephrase anyone know where I can get hold of documentation that is slightly more detailed that this http://hyperledger-fabric.readthedocs.io/en/release/kafka.html?

jyellick (Fri, 16 Feb 2018 15:00:27 GMT):
@paul.sitoh There is a plethora of documentation for Kafka https://kafka.apache.org/documentation/ I especially recommend at a minimum going through https://kafka.apache.org/documentation/#quickstart There are also many sources of Kafka documentation from assorted service providers, that are all readily found with a standard Google search.

paul.sitoh (Fri, 16 Feb 2018 15:01:20 GMT):
I am not refering to Kafka, I am referring to more details about Fabric-Kafka integration

paul.sitoh (Fri, 16 Feb 2018 15:01:20 GMT):
I am not refering to Kafka alone, I am referring to more details about Fabric-Kafka integration. For example, how Kafka and Fabric could be configured in, example, multi-cloud environment, etc

paul.sitoh (Fri, 16 Feb 2018 15:01:20 GMT):
@jyellick jyellick I am not refering to Kafka alone, I am referring to more details about Fabric-Kafka integration. For example, how Kafka and Fabric could be configured in, example, multi-cloud environment, etc

paul.sitoh (Fri, 16 Feb 2018 15:01:20 GMT):
@jyellick I am not refering to Kafka alone, I am referring to more details about Fabric-Kafka integration. For example, how Kafka and Fabric could be configured in, example, multi-cloud environment, etc

jyellick (Fri, 16 Feb 2018 15:08:57 GMT):
@paul.sitoh The fabric orderer network may simply be seen as a Kafka application. I think you'll find plenty of documentation for deploying Kafka applications in assorted environments. The fabric documentation deliberately does not discuss detailed Kafka deployment scenarios, as we could not hope to cover all potential deployment types, and the information would be redundant and difficult to maintain.

paul.sitoh (Fri, 16 Feb 2018 15:09:36 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=rbDbc87xdr75kggyo) @jyellick True, but just covering the basics will be helpful

paul.sitoh (Fri, 16 Feb 2018 15:09:36 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=rbDbc87xdr75kggyo) @jyellick True, but just covering the basics will be helpful. Give some broad brush use cases. You don't have to cover everthing. Say a sample case, two organisations. Where Kafka sits, where fabric instance sits, for instance.

dave.enyeart (Fri, 16 Feb 2018 19:02:43 GMT):
@mastersingh24 @cbf I believe you have investigated versioning options in readthedocs. Could you give a quick summary of what you've learned as good practices? For example are the rtd versions based strictly on our fabric tags? That is, does the v1.1.0 rtd docs have to match up exactly with the fabric commit at v1.1.0 tag? Or could we for example keep improving the v1.1.0 docs after fabric v1.1.0 is tagged and released? (ignore for now that we may move docs to a separate repository)

mastersingh24 (Sat, 17 Feb 2018 12:16:59 GMT):
@dave.enyeart @cbf With RTD you can use branches and/or tags as your versioning scheme. And you have the option to specify which branch "latest" should point at. We currently use a combination of tags and branches ... I think we can eliminate using tags if we do the following: 1) rename "release" branch to "release-1.0.x" 2) create branch "release-1.1.x" for v1.1.x release only publish docs for the "release-M.M.X" and "master" branches and publish docs for alpha,beta,rc tags if necessary (to ensure that incompatible doc changes in master do not confuse people) If this scheme were in place now, we'd have: release-1.0.x v1.1.0-alpha master once we release v.1.1.x, we'd have release-1.0.x release-1.1.x master

dave.enyeart (Sat, 17 Feb 2018 12:19:49 GMT):
ok, so we can continue to improve the 1.1 docs after GA, but it will require dual maintenance on both v1.1 and master branches

dave.enyeart (Sat, 17 Feb 2018 12:20:59 GMT):
so use branches primarily, but allow short term tags such as v1.1.0-alpha

mastersingh24 (Sat, 17 Feb 2018 12:21:12 GMT):
correct - if we need to make changes to existing docs, they'd need to go to master and release branches new functions would generally only go to master

mastersingh24 (Sat, 17 Feb 2018 12:21:58 GMT):
Yeah - I think that provides the most flexibility to keep rolling updates of docs (https://chat.hyperledger.org/channel/fabric-documentation?msg=iDJjW4Eo45FEy3egh) @dave.enyeart

chandrasekarangengadharan (Tue, 20 Feb 2018 12:42:20 GMT):
Has joined the channel.

tc-crypto (Thu, 22 Feb 2018 01:06:42 GMT):
In the latest doc it has the following command on page 39 to load the sample chaincode but it errors saying "Error: Error getting chaincode code chaincode: path to chaincode does not exist: /opt/gopath/src/github.com/chaincode/chaincode_example02/go" - command it says to run is - peer chaincode install -n mycc -v 1.0 -p github.com/chaincode/chaincode_example02/go/ - does anyone know how to fix this?

tc-crypto (Thu, 22 Feb 2018 21:08:40 GMT):
@joe-alewine - https://readthedocs.org/projects/hyperledger-fabric/downloads/pdf/latest/ - appears to have been written by Hyperledger

joe-alewine (Thu, 22 Feb 2018 21:15:53 GMT):
@tc-crypto This is the first I'm seeing of this -- it appears to be a pdf version of the documentation that can be found here: http://hyperledger-fabric.readthedocs.io/en/latest/ The doc you're looking at is Build Your First Network (BYFN): http://hyperledger-fabric.readthedocs.io/en/latest/build_network.html

joe-alewine (Thu, 22 Feb 2018 21:16:22 GMT):
Not sure what's going wrong there. Is your fabric-samples folder up to date?

joe-alewine (Thu, 22 Feb 2018 21:16:47 GMT):
Might be a question for #fabric-questions

cbf (Fri, 23 Feb 2018 01:17:37 GMT):
@odowdaibm take a look at https://gerrit.hyperledger.org/r/c/18233/ - Gari mentioned that the fabric-ca team had scripted generation of the command docs. This makes infinite sense as it will be easier to manage as the help text or commands change (e.g. no need to update multiple places)

cbf (Fri, 23 Feb 2018 01:18:21 GMT):
I think that what we should do is this, versus hand-crafted docs. What we should do over time (post 1.1) is to update the help text to be as helpful as possible on their own

cbf (Fri, 23 Feb 2018 01:18:44 GMT):
(we also need to i18n-ify them but that's another day)

cbf (Fri, 23 Feb 2018 14:20:05 GMT):
updated after I realized that the commands reference added usage info... I have adapted configtxgen and configtxlator accordingly. Thoughts?

odowdaibm (Fri, 23 Feb 2018 14:56:12 GMT):
How would we include sample (example) usage, and explanations?

odowdaibm (Fri, 23 Feb 2018 14:56:51 GMT):
I think that useful command reference material should not just been a simple translation of command syntax

cbf (Fri, 23 Feb 2018 15:00:48 GMT):
I sandwich the help text with preamble and postscript which includes the prose that @jyellick provided

cbf (Fri, 23 Feb 2018 15:04:52 GMT):
so this can include usage and additional insights we wish to impart

odowdaibm (Fri, 23 Feb 2018 15:06:28 GMT):
right I here you, and added comments to JIRA. Does this mean that writer now has a more complex update process? To me it seems the challenge is generating contents, not the mechanics of it.

odowdaibm (Fri, 23 Feb 2018 15:06:55 GMT):
(I'm not against automation, but I'm not sure I see the gain here)

odowdaibm (Fri, 23 Feb 2018 15:09:19 GMT):
btw, I understand the frustation with slowness, but that is a different issue

cbf (Fri, 23 Feb 2018 15:19:53 GMT):
over time, I would like to see the process I outlined become pure generated content by incorporating the usage info into the help text.

cbf (Fri, 23 Feb 2018 15:20:22 GMT):
This will also allow us to localize both the help text and the docs consistently

cbf (Fri, 23 Feb 2018 15:21:04 GMT):
so yes, for a short while a little more complicated (but not really... it took me 5 mins to adapt @jyellick work)

simsc (Fri, 23 Feb 2018 15:51:49 GMT):
@cbf - we have several different developers trying to complete by end of the weekend. given the timeline would you be able to do this for different pieces for v1.1 and the team can do this going forward in v1.2

odowdaibm (Fri, 23 Feb 2018 15:54:17 GMT):
again, I hear you @cbf, but wouldn't coherence come from the JIRAs identifying the changes in concepts, tasks, and reference material that need to be made whenever any feature is added. Listen, Im not against it, and I think it can have a place, but I think that we need to see how it can work when we have the example text in place

odowdaibm (Fri, 23 Feb 2018 15:55:15 GMT):
I'm just updating the last piece of the peer channel command now -- I will have in patch set before end of day, with sample build, so you can have a look at that and see where the synergy is @cbf. I hope that's reasonable

cbf (Fri, 23 Feb 2018 15:57:59 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=bnvCDkkpqs6qivc6o) @simsc it took me all of 30 minutes to write the script and then 5 minutes to adapt to jason's work.

cbf (Fri, 23 Feb 2018 15:59:35 GMT):
@elli-androulaki is working my comment on https://gerrit.hyperledger.org/r/c/17505/

cbf (Fri, 23 Feb 2018 16:36:16 GMT):
https://gerrit.hyperledger.org/r/c/17505/

cbf (Fri, 23 Feb 2018 16:36:26 GMT):
not sure if it is a problem... sorry I didn't notice it earlier

aambati (Fri, 23 Feb 2018 17:02:40 GMT):
@cbf @odowdaibm i looked at Chris' change set that has a script that produced command help documents..If i understand this is similar to what we do with fabric-ca commands. which is good to have. Fabric-ca doc also a detailed section for each command that goes in depth into each command. I think this is what Anthony is trying to do. So , I think there is a place for both what Chris has done and what Anthony's team is documenting. In fabric-ca, script produces two docs (one for client and server) , links to these docs is placed in the readme doc. And the readme doc has sections that use each of these commands (like enrolling a user, revoking a user)

aambati (Fri, 23 Feb 2018 17:02:40 GMT):
@cbf @odowdaibm i looked at Chris' change set that has a script that produced command help documents..If i understand this is similar to what we do with fabric-ca commands. which is good to have. Fabric-ca doc also has a detailed section for each command that goes in depth into each command. I think this is what Anthony is trying to do. So , I think there is a place for both what Chris has done and what Anthony's team is documenting. In fabric-ca, script produces two docs (one for client and server) , links to these docs is placed in the readme doc. And the readme doc has sections that use each of these commands (like enrolling a user, revoking a user)

cbf (Fri, 23 Feb 2018 20:14:35 GMT):
@odowdaibm the example output contains a bunch of debug and info logging that only confuses the reader. Strongly suggest we raise the logging level to ERROR to eliminate that nose (or we can simply edit the noise out)

cbf (Fri, 23 Feb 2018 20:22:44 GMT):
reviewed 18085 and LG except the debug messages in the example output - adds unnecessary noise

odowdaibm (Sun, 25 Feb 2018 08:07:37 GMT):
yes, those are done now @cbf - ty

odowdaibm (Sun, 25 Feb 2018 08:08:04 GMT):
doing some other updates now per Dave and Jason. All small, but worth having in. ty

Ammu (Mon, 26 Feb 2018 07:44:47 GMT):
How does it work? Configtxgen consumes a file - configtx.yaml - that contains the definitions for the sample network. There are three members - one Orderer Org (OrdererOrg) and two Peer Orgs (Org1 & Org2) each managing and maintaining two peer nodes. This file also specifies a consortium - SampleConsortium - consisting of our two Peer Orgs. Pay specific attention to the “Profiles” section at the top of this file. You will notice that we have two unique headers. One for the orderer genesis block - TwoOrgsOrdererGenesis - and one for our channel - TwoOrgsChannel. These headers are important, as we will pass them in as arguments when we create our artifacts. This file also contains two additional specifications that are worth noting. Firstly, we specify the anchor peers for each Peer Org (peer0.org1.example.com & peer0.org2.example.com). Secondly, we point to the location of the MSP directory for each member, in turn allowing us to store the root certificates for each Org in the orderer genesis block. This is a critical concept. Now any network entity communicating with the ordering service can have its digital signature verified.

odowdaibm (Mon, 26 Feb 2018 19:09:35 GMT):
Hi all -- I've staged http://fabricdocs1.readthedocs.io/en/issue-fab-7895/peers/peers.html for the Peer concept, and would appreciate reviews. I've incoporated lots of feedback from Will and Kostas, but this is a topic, where I'd like as much back as possible, as we get asked loads of questions.

odowdaibm (Mon, 26 Feb 2018 19:10:18 GMT):
See https://gerrit.hyperledger.org/r/c/17473/ for more - thanks!

odowdaibm (Mon, 26 Feb 2018 19:17:09 GMT):
@cbf @rameshthoomu @kostas @baohua @mastersingh24 @wlahti @dave.enyeart @simsc @joe-alewine @Yogendrasri I know you're all buys, but even if you have a quick look over https://gerrit.hyperledger.org/r/c/17473 I'd appreciate it. I can incorporate any comments, feedback. Ty

dave.enyeart (Mon, 26 Feb 2018 19:18:14 GMT):
Same for the Membership conceptual doc: https://gerrit.hyperledger.org/r/#/c/17505/

dave.enyeart (Mon, 26 Feb 2018 19:18:38 GMT):
Both the Peer and Membership have gone through multiple reviews, I would like to merge this afternoon

dave.enyeart (Mon, 26 Feb 2018 19:19:03 GMT):
Will give people a couple hours though in case any final changes are needed

dave.enyeart (Mon, 26 Feb 2018 19:19:03 GMT):
Will give people a couple hours though in case any large problems are found

dave.enyeart (Mon, 26 Feb 2018 19:22:32 GMT):
We can continue to make minor edits in follow-on CRs.

cbf (Mon, 26 Feb 2018 19:44:19 GMT):
we have had a long-standing position against use of t he term "smart contract"

cbf (Mon, 26 Feb 2018 19:44:39 GMT):
yet the peer doc is replete with mentions of "smart contracts"

kostas (Mon, 26 Feb 2018 19:46:58 GMT):
@cbf: Authors' response: https://gerrit.hyperledger.org/r/c/17473/3/docs/source/peers/peers.md#3

kostas (Mon, 26 Feb 2018 19:59:43 GMT):
That's fair. Just saying, that an answer has been given.

kostas (Mon, 26 Feb 2018 19:59:43 GMT):
That's fair. Just saying that an answer has been given.

kostas (Mon, 26 Feb 2018 19:59:43 GMT):
That's fair. Just saying that an answer has been given, in case this had slipped through the cracks.

baohua (Tue, 27 Feb 2018 01:10:00 GMT):
@odowdaibm seems u need to rebase with the latest master branch.

kostas (Tue, 27 Feb 2018 14:23:58 GMT):
Quick reminder: when linking to another doc in the documentation, do we do a relative link or use the URI? If it's the latter, which version of the readthedocs do we link against? Release?

baohua (Wed, 28 Feb 2018 00:48:23 GMT):
Seen a relative link is more common.

joe-alewine (Wed, 28 Feb 2018 02:16:36 GMT):
It took me a little while to figure out because it's a bit more difficult when linking to an rst doc in markdown, but I did figure it out eventually. The Identity and Membership docs do it the "wrong" way and when we go back through those after the release I'll fix the links as well

ramsailendravarma (Thu, 01 Mar 2018 02:26:25 GMT):
Has joined the channel.

george19120 (Thu, 01 Mar 2018 08:53:46 GMT):
hello, everyone .where can i get the hyperledger fabirc requirement docment? it include the function description/stability descpription/performance description.

joe-alewine (Thu, 01 Mar 2018 14:01:36 GMT):
I'm not really sure what you mean by requirement document. Can you elaborate?

Nabilel 1 (Thu, 01 Mar 2018 14:52:02 GMT):
Hello everyone. In a Hyperldeger fabirc, can I have peer nodes acting as clients? in other words each participant in the network needs to be a peer node as well?

joe-alewine (Thu, 01 Mar 2018 15:28:42 GMT):
@Nabilel 1 Peers are owned/managed/provisioned by Organizations. You can have as many peers as you want, and you could establish someone as the sole Admin for each peer. What are you trying to achieve?

joe-alewine (Thu, 01 Mar 2018 15:28:42 GMT):
@Nabilel 1 Peers are owned/managed/provisioned by Organizations. An org can have as many peers as it wants, and you could establish someone as the sole Admin for each peer (though typically you've have many different orgs, each with their own peers (if everything is under the umbrella of a single org, you don't really need Fabric -- just use a centralized database system). What are you trying to achieve?

cbf (Thu, 01 Mar 2018 19:02:25 GMT):
for publishing documentation on RTD, what we have now is a bit of a mess, and some of the published docs are redundant

cbf (Thu, 01 Mar 2018 19:03:34 GMT):
it appears that if you are following semantic versioning (we are) then it should be able to automatically pick from the tags the most stable release and publish that as stable (assuming it is an interim release)

cbf (Thu, 01 Mar 2018 19:03:55 GMT):
I'd like to consider that we use the following doc tags

cbf (Thu, 01 Mar 2018 19:06:10 GMT):
for each major or minor release and its subsequent patches (a branch) we publish the most recent tag as release-1.0 or release-1.1 etc for the master branch, we should tag stable releases (preview, alpha, rc, etc) and publish these as 'stable' and finally, latest would point to master.

cbf (Thu, 01 Mar 2018 19:06:50 GMT):
so, the 1.0.6 tag would be published as release-1.0

cbf (Thu, 01 Mar 2018 19:07:49 GMT):
thoughts? @mastersingh24 @dave.enyeart @odowdaibm

mastersingh24 (Thu, 01 Mar 2018 21:20:48 GMT):
So the mapping for RTD is either tags or branches .... So I'd suggest we have the following: - release-1.0.x - we rename the release branch to this and just publish this branch - release-1.1.x - we create this for 1.1.x and publish this branch - master - we could publish this branch as well we would make the latest M.M release the default docs stable / latest can be confusing .... I think just publishing our release branches is perfect as we can then have rolling docs updates per M.M release.

george19120 (Fri, 02 Mar 2018 03:38:18 GMT):
@joe-alewine the requirement document lists function/stability/performance/. function is what hyperledger fabric can do. for example,it can be used as a distute ledeger to record something. stability is how many times hyperledger fabric will can not work in a day or month or year. for example,it can not be Consensus.performance is how many transactions hyperledger fabric can do in a typical scene.

odowdaibm (Fri, 02 Mar 2018 06:13:15 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=5xvNtvCYhW7D6xkXj) @cbf Thanks! I think we definitely need a per MINOR build, but I don't think PATCH is necessary or desirable! MAJOR, as you say, is too infrequent. MINOR means that there's too many docs, but more importantly, MINOR should be semantically the same which implies the same docs. For example, I should just be able to read 1.1 docs and it include 1.1.0, 1.1.1... 1.1.x -- this creates real coherence for users.

odowdaibm (Fri, 02 Mar 2018 06:13:15 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=5xvNtvCYhW7D6xkXj) @cbf Thanks! I think we definitely need a per MINOR build, but I don't think PATCH is necessary or desirable! MAJOR, as you say, is too infrequent. PATCH means that there's too many docs, but more importantly, MINOR should be semantically the same which implies the same docs. For example, I should just be able to read 1.1 docs and it include 1.1.0, 1.1.1... 1.1.x -- this creates real coherence for users.

odowdaibm (Fri, 02 Mar 2018 06:13:15 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=5xvNtvCYhW7D6xkXj) @cbf Thanks! I think we definitely need a per MINOR build, but I don't think PATCH is necessary or desirable! MAJOR, as you say, is too infrequent. PATCH means that there's too many docs, but more importantly, MINOR builds should be semantically the same which implies the same docs. For example, I should just be able to read 1.1 docs and it include 1.1.0, 1.1.1... 1.1.x -- this creates real coherence for users.

odowdaibm (Fri, 02 Mar 2018 06:16:18 GMT):
I also think that there should be a default -- latest, and should be the highest semantic version available that is stable. i.e. right now it would be 1.0, and become 1.1 as soon as we release 1.1

cbf (Fri, 02 Mar 2018 14:01:03 GMT):
@odowdaibm I think we are saying the same thing... if you'll revisit, I am suggesting that the RTD tag would be one of 'latest' (master branch), 'release-1.0.x' (latest patch release of 1.0.x series), 'release-1.1.x' (latest patch release for 1.1.x series), and 'stable' (for the latest stable build of the master branch) - there would NOT be a published RTD with a tag of 1.1.3 for instance

odowdaibm (Fri, 02 Mar 2018 14:01:58 GMT):
so there wouldn't be docs release when patch was released

cbf (Fri, 02 Mar 2018 14:02:36 GMT):
as for default, I think that should be the release-1.1.x once we have formally released 1.1.0

akshay.sood (Mon, 05 Mar 2018 15:17:23 GMT):
What is the meaning of endorsement in Hyperledger fabric?

cbf (Mon, 05 Mar 2018 17:23:16 GMT):
an endorsed proposal is a transaction proposal that has been simulated by a peer node, and has had it's read/write set signed in the response to the proposer.

cbf (Mon, 05 Mar 2018 17:27:23 GMT):
when the client collects sufficient number of endorsed transaction proposal responses, and those responses match (read/write sets) then the lot are bundled up and submitted to the ordering service for inclusion in a block to be broadcast to the peers in the channel. The receiving peer nodes will then validate the transaction against the endorsement policy and if validated, will commit to the ledger and state db. See the transaction flow doc for complete details http://hyperledger-fabric.readthedocs.io/en/v1.1.0-rc1/txflow.html

cbf (Mon, 05 Mar 2018 20:58:52 GMT):
I've done a bit of a refactor of the fabric docs TOC at least from a presentation perspective.

cbf (Mon, 05 Mar 2018 20:59:11 GMT):
I think that this makes it much more approachable

cbf (Mon, 05 Mar 2018 21:16:13 GMT):
here's the build output https://logs.hyperledger.org/production/vex-yul-hyp-jenkins-3/fabric-rtd-verify-master/314/html/

cbf (Tue, 06 Mar 2018 17:04:57 GMT):
ping still looking for feedback on the TOC reformatting

joe-alewine (Tue, 06 Mar 2018 19:25:09 GMT):
Chris -- it looks nice. Cleaner. I would be worried that the text is getting pretty small, however. Also curious why the TOC sections repeat -- are you offering people a choice between two organizational options?

dave.enyeart (Wed, 07 Mar 2018 13:32:05 GMT):
Posted this to fabric-scrum, pasting here so that everybody working on doc is aware:

dave.enyeart (Wed, 07 Mar 2018 13:32:15 GMT):
For `fabric` and `fabric-ca`: - use `master` branch for new 1.2 code, but remember that we will require written motivation and design for anything significant starting in 1.2 (either in Jira Description for small items, or a linked google doc or slides for larger items). - use `release-1.1` branch for any doc improvements or critical fixes that need to be made prior to 1.1 GA release - every time you merge something, think about whether it needs to be cherry picked to the other branch, and make sure the Jira Fix Version includes both releases (v1.1 and v1.2 for master). For the other projects - there is not much 1.2 activity yet, so we’ll let 1.1 finalize in `master` before creating the release branches.

dave.enyeart (Wed, 07 Mar 2018 13:32:15 GMT):
For `fabric` and `fabric-ca`: - use `master` branch for new 1.2 code, but remember that we will require written motivation and design for anything significant starting in 1.2 (either in Jira Description for small items, or a linked google doc or slides for larger items). - use `release-1.1` branch for any doc improvements or critical fixes that need to be made prior to 1.1 GA release - every time you push a CR, think about whether it needs to be cherry picked to the other branch, and make sure the Jira Fix Version includes both releases (v1.1 and v1.2 for master). For the other projects - there is not much 1.2 activity yet, so we’ll let 1.1 finalize in `master` before creating the release branches.

odowdaibm (Wed, 07 Mar 2018 13:33:30 GMT):
All, We've started a piece of work to add to the Ledger Concept topic

odowdaibm (Wed, 07 Mar 2018 13:33:56 GMT):
JIRA: https://jira.hyperledger.org/browse/FAB-8689 Gerrit: https://gerrit.hyperledger.org/r/c/18813/

odowdaibm (Wed, 07 Mar 2018 13:34:16 GMT):
We're having regular, daily calls on this. incrementally enhancing

odowdaibm (Wed, 07 Mar 2018 13:35:01 GMT):
Please feel free to add yourself as reviewers @SjirNijssen and colleagues

odowdaibm (Wed, 07 Mar 2018 18:18:02 GMT):
More updates on this patch set for Ledger concept. Nothing ready for review, but you can see the basic structure here: http://fabricdocs1.readthedocs.io/en/issue-fab-8689/ledger/ledger.html

vishwasbalakrishna (Wed, 07 Mar 2018 21:32:23 GMT):
Has joined the channel.

akshay.sood (Sat, 10 Mar 2018 07:19:02 GMT):
Anyone knows what is core peer in docker compose cli envirement CORE_PEER

akshay.sood (Mon, 12 Mar 2018 15:31:44 GMT):
byfn always shows ```ERROR: for peer1.debutinfotech.com Cannot start service peer1.debutinfotech.com: driver failed programming external connectivity on endpoint DebutInfotechPeer1 (f808c3c48dfebbe508c66b81aeaceb137656520998d5089d895b698822910149): Bind for 0.0.0.0:1051 failed: port is already allocated``` even if the ports are changed

joe-alewine (Mon, 12 Mar 2018 15:38:40 GMT):
@akshay.sood Looks like you already have a peer using that port. Issue a ``docker ps -a``. That should show what components you have up and running

joe-alewine (Mon, 12 Mar 2018 15:38:40 GMT):
@akshay.sood Looks like you already have a peer using that port. Issue a `docker ps -a`. That should show what components you have up and running

dave.enyeart (Wed, 14 Mar 2018 02:21:48 GMT):
@cbf @mastersingh24 @joe-alewine @rameshthoomu @smithbk @skarim @aambati

dave.enyeart (Wed, 14 Mar 2018 02:21:48 GMT):
@cbf @mastersingh24 @joe-alewine @rameshthoomu @smithbk @skarim @aambati @odowdaibm

dave.enyeart (Wed, 14 Mar 2018 02:21:48 GMT):
@cbf @mastersingh24 @joe-alewine @rameshthoomu @smithbk @skarim @aambati @odowdaibm @pandrejko

dave.enyeart (Wed, 14 Mar 2018 02:21:54 GMT):
I’ve updated fabric-ca readthedocs to have `latest` (still points to master), `release-1.0`, `release-1.1`, `v1.1.0-rc1`. This is consistent with fabric now. Any fixes to docs in `release-1.0` or `release-1.1` branches will automatically get reflected in rtd. After we release 1.1, we’ll remove `v1.1.0-rc1` from both fabric and fabric-ca. Note that fabric also has `master` which is a dup of `latest`. I’m thinking we could remove `master`. Most of the links I’ve found point to `latest` rather than `master`.

Ammu (Wed, 14 Mar 2018 12:58:41 GMT):
what are the hyperledger fabrics tools?

cbf (Wed, 14 Mar 2018 14:14:04 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=jtDMtdxBimFjR7TAk) @dave.enyeart SGTM thanks

cbf (Wed, 14 Mar 2018 14:15:20 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=ezsBWW7qkMTegu5xi) @Ammu cryptogen, configtxgen configtxlator peer orderer and chaintool

Ammu (Thu, 15 Mar 2018 05:25:11 GMT):
cryptogen, configtxgen configtxlator peer orderer and chaintool what is the use case of it?

odowdaibm (Fri, 16 Mar 2018 05:55:06 GMT):
@here We're about to start our weekly documentation workgroup call https://ibm.webex.com/join/a_o-dowd All welcome - thanks!

odowdaibm (Fri, 16 Mar 2018 05:56:09 GMT):
@Ammu I would like to help you understand these, and create some documentation to support that

odowdaibm (Fri, 16 Mar 2018 05:57:18 GMT):
cyptogen is a tool that creates a set of x.509 certificates, used to identify the different components of the blockchain network. Eg. peers and orderers.

odowdaibm (Fri, 16 Mar 2018 05:59:02 GMT):
configtxgen creates configuration information relating to each of these components, for example channel configurations

odowdaibm (Fri, 16 Mar 2018 05:59:51 GMT):
Once you have these fundamental data (identities and configurations) you can now start creating compoonents, - starting with orderers, and adding peers

odowdaibm (Fri, 16 Mar 2018 06:00:22 GMT):
the peer command helps you interact with those peers, likewise the orderer command

odowdaibm (Fri, 16 Mar 2018 06:00:57 GMT):
the configtxlator tool allows you to view any configuration, including the initial and any previous

odowdaibm (Fri, 16 Mar 2018 06:03:01 GMT):
Fianlly, chaintool is a tool that helps you build chaincode (smart contracts) that are deployed to the peers, and accessed via the Fabric SDK API

odowdaibm (Fri, 16 Mar 2018 06:03:01 GMT):
Finally, chaintool is a tool that helps you build chaincode (smart contracts) that are deployed to the peers, and accessed via the Fabric SDK API

odowdaibm (Fri, 16 Mar 2018 06:11:56 GMT):
@tausifbadu we have started the call

Ammu (Fri, 16 Mar 2018 06:28:36 GMT):
@odowdaibm what is the use of order, peer, channel ? what it means in practical way?

odowdaibm (Fri, 16 Mar 2018 07:17:36 GMT):
@Ammu I think you'll find this new topic very helpful

odowdaibm (Fri, 16 Mar 2018 07:17:38 GMT):
http://hyperledger-fabric.readthedocs.io/en/release-1.1/peers/peers.html

odowdaibm (Fri, 16 Mar 2018 07:18:03 GMT):
Please read it -- it's quite easy to read, and post here any questions, thoughts comments etc and I will reply to you

odowdaibm (Fri, 16 Mar 2018 07:18:56 GMT):
@here Excellent call this morning - I've create JIRA https://jira.hyperledger.org/browse/FAB-8914 for us all to start working Orderer concept topic

odowdaibm (Fri, 16 Mar 2018 07:19:53 GMT):
Thanks to @luo @eramitg @Yogendrasrivastava @tausifbadu for your thoughts, help etc! Please add them to the JIRA

Yogendrasrivastava (Fri, 16 Mar 2018 07:19:53 GMT):
Has joined the channel.

odowdaibm (Fri, 16 Mar 2018 07:20:09 GMT):
I will create the skeleton for Orderer concept topic now

varun-raj (Fri, 16 Mar 2018 07:20:20 GMT):
@odowdaibm Do you think something from my article can go into official documentation? https://www.skcript.com/svr/understanding-hyperledger-fabric-s-architecture/

odowdaibm (Fri, 16 Mar 2018 07:21:51 GMT):
Hi @varun-raj Would you like to contribute to one of the existing topics?

varun-raj (Fri, 16 Mar 2018 07:22:22 GMT):
Mostly I'm trying write articles on the missing guides that people are trying to find

odowdaibm (Fri, 16 Mar 2018 07:22:52 GMT):
Great, at the moment, we have people working on a n udated ledger topic, and we've juststarted one on orderers, as a result of this morning's emeeting

varun-raj (Fri, 16 Mar 2018 07:23:06 GMT):
Like there are no articles on how to use the fabric node SDK and how to handle authentication with JWT etc

varun-raj (Fri, 16 Mar 2018 07:23:42 GMT):
Oh that's great :) I'll try to share my contributions on something related to me so that its more precise and proper

odowdaibm (Fri, 16 Mar 2018 07:23:54 GMT):
http://hyperledger-fabric.readthedocs.io/en/release-1.1/write_first_app.html

varun-raj (Fri, 16 Mar 2018 07:23:55 GMT):
This one? https://jira.hyperledger.org/browse/FAB-8914

odowdaibm (Fri, 16 Mar 2018 07:24:21 GMT):
I really recommend that you read that topic -- it will show you how to use the Fabric SDK in a very simple way

odowdaibm (Fri, 16 Mar 2018 07:25:11 GMT):
Please do read it, and let me know what you think

varun-raj (Fri, 16 Mar 2018 07:26:30 GMT):
Yeah, this looks really good. Now I think we need to write something about how to handle multi user authentication, like wallet based mechanism.

odowdaibm (Fri, 16 Mar 2018 07:27:17 GMT):
If you think about it, this application would normally expose an API to (say) a mobile device

varun-raj (Fri, 16 Mar 2018 07:27:30 GMT):
In our production application, we're using JWT tokens and card (inspired from composer) to handle authentication

odowdaibm (Fri, 16 Mar 2018 07:27:47 GMT):
this app has a certificate that is know to the blockchain network via one of the CA's

odowdaibm (Fri, 16 Mar 2018 07:28:16 GMT):
I think in your scenari, you've got (maybe) a mobile device with a security token that connects to the fabcar app, and oyu need to authenticate that?

odowdaibm (Fri, 16 Mar 2018 07:28:41 GMT):
right, so you're really interested in how to do identity mapping, authentication etc etc

odowdaibm (Fri, 16 Mar 2018 07:29:34 GMT):
Or, are you saying that you'd like that app to use different identities?

varun-raj (Fri, 16 Mar 2018 07:30:21 GMT):
Yeah the certificates are stored in the crypto store right. But we cant have it always there due to security issue. Thus we're uploading it when the user logs in and will check it with fabric ca and set the context

varun-raj (Fri, 16 Mar 2018 07:30:29 GMT):
When the user logs out we'll delete the keys

varun-raj (Fri, 16 Mar 2018 07:30:57 GMT):
Each org will have its own api server to access the network

odowdaibm (Fri, 16 Mar 2018 07:31:27 GMT):
so you want different end users to effectively have a different certificate when they access the ledger via this blockchain App -- the one behind the RESTful API?

odowdaibm (Fri, 16 Mar 2018 07:31:39 GMT):
yes, sorry, I meant the moral equvalnet of fabcar

varun-raj (Fri, 16 Mar 2018 07:31:50 GMT):
One org will have multiple users to access the network kinds

odowdaibm (Fri, 16 Mar 2018 07:31:58 GMT):
OK, so do you think you need to do that?

odowdaibm (Fri, 16 Mar 2018 07:32:38 GMT):
I'm not trying to design your app for you ;) but I think the identities that (say) your mobile users use, is different to your app's identity

odowdaibm (Fri, 16 Mar 2018 07:33:06 GMT):
If you think about it in terms of trust, then your app provides the trust to those mobile devices

odowdaibm (Fri, 16 Mar 2018 07:33:25 GMT):
and your app is trusted by the blockchain becuase of the certificate it has, and the rights it gets from ythat certificate

odowdaibm (Fri, 16 Mar 2018 07:33:37 GMT):
yes, the nodejs client that uses the fabric SDK

odowdaibm (Fri, 16 Mar 2018 07:34:01 GMT):
now your mobile apps that connect to that via REST are probably sending a different kind of securty token

varun-raj (Fri, 16 Mar 2018 07:34:15 GMT):
True that. So there is one set of certificates for nodejs client and one for users

odowdaibm (Fri, 16 Mar 2018 07:34:21 GMT):
it might be a cert, of SAML or user/password etc etc

varun-raj (Fri, 16 Mar 2018 07:34:28 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=j9ZrSYJB9r9BggpQ5) @odowdaibm Yeah

odowdaibm (Fri, 16 Mar 2018 07:34:30 GMT):
right one set for the differe users

odowdaibm (Fri, 16 Mar 2018 07:34:58 GMT):
all your nodejs app really needs to do is be oconfident that the end user is who they say they are, then it can use it's identity to write information to the blockchain

odowdaibm (Fri, 16 Mar 2018 07:35:30 GMT):
and you can do that by authenticating them in your nodejs app using whatever security mechanism

varun-raj (Fri, 16 Mar 2018 07:36:10 GMT):
Yeah, thats why we authenticate with the certificates that are generated by Fabric CA for the specific users to validate.

varun-raj (Fri, 16 Mar 2018 07:36:32 GMT):
We dont use username/password to identify the users. Instead we directly use the certificate pair

varun-raj (Fri, 16 Mar 2018 07:37:08 GMT):
And almost all our client's organization will set the nodejs client in the intranet thus nothing is exposed to public

varun-raj (Fri, 16 Mar 2018 07:37:31 GMT):
I think it's something similar to how composer does it

odowdaibm (Fri, 16 Mar 2018 07:37:57 GMT):
Composer has a REST server sample that uses a standard node package to o this

odowdaibm (Fri, 16 Mar 2018 07:38:18 GMT):
I think that's a much better security architecture

varun-raj (Fri, 16 Mar 2018 07:38:49 GMT):
We dont have to store the keys all the time, only when the user is logged in and wants to use the system

varun-raj (Fri, 16 Mar 2018 07:39:09 GMT):
And if we can store the keys in temp storage like RAM, it'll be much more secured

varun-raj (Fri, 16 Mar 2018 07:39:33 GMT):
I'm exploring the skip persistent part, not sure how it works though

odowdaibm (Fri, 16 Mar 2018 07:39:44 GMT):
well, you separate the keys, into those used by the end users, and the HLF one used by your nodejs Fabric SDK app, it's much easier

odowdaibm (Fri, 16 Mar 2018 07:40:26 GMT):
I think it wouldbe good to have a small topic on this, in a new section on Writing Applications?

varun-raj (Fri, 16 Mar 2018 07:40:33 GMT):
By which we can achieve multi-user and role-based validations as well

odowdaibm (Fri, 16 Mar 2018 07:40:35 GMT):
we could cover this kind of discussion

odowdaibm (Fri, 16 Mar 2018 07:40:44 GMT):
exactly, it allows you to d o all that

varun-raj (Fri, 16 Mar 2018 07:40:50 GMT):
Yeah make sense :) I'll be happy to do that :D

odowdaibm (Fri, 16 Mar 2018 07:41:01 GMT):
you can have differnet HLF certs in the node app that are used depending on the end user role

odowdaibm (Fri, 16 Mar 2018 07:41:10 GMT):
and just do the mapping in the nodejs app

varun-raj (Fri, 16 Mar 2018 07:41:10 GMT):
We define the roles in attributes thus we can fetch it from chaincode also

varun-raj (Fri, 16 Mar 2018 07:41:32 GMT):
We can do the mapping with chaincode itself :D

odowdaibm (Fri, 16 Mar 2018 07:41:36 GMT):
I think this would be an excellent short topic

odowdaibm (Fri, 16 Mar 2018 07:41:59 GMT):
you can do that checking against the roles in the nodejs certs

odowdaibm (Fri, 16 Mar 2018 07:42:22 GMT):
don't make it relate to those end users

odowdaibm (Fri, 16 Mar 2018 07:42:29 GMT):
do it based on the roles in the middle tier

varun-raj (Fri, 16 Mar 2018 07:42:29 GMT):
But if someone gets access to the nodejs client its easier for that to change it right

varun-raj (Fri, 16 Mar 2018 07:42:51 GMT):
and more over our clients for multiple users from the same org to have different roles

odowdaibm (Fri, 16 Mar 2018 07:43:02 GMT):
yes, absolutely, introduce different roles

odowdaibm (Fri, 16 Mar 2018 07:43:21 GMT):
and have different HLF certs for those, that get sleected in the nodejs app accoring to end user roles

odowdaibm (Fri, 16 Mar 2018 07:43:41 GMT):
you can absolutely encode access logic in the chaincode, just be careful to not make it too brittle

varun-raj (Fri, 16 Mar 2018 07:43:51 GMT):
You mean the certs that are used by the applicaiton?

odowdaibm (Fri, 16 Mar 2018 07:43:53 GMT):
you don't want to be changing the chaincode all the time

odowdaibm (Fri, 16 Mar 2018 07:44:09 GMT):
it's usually a good idea to keep access control and application logic separate from each other

odowdaibm (Fri, 16 Mar 2018 07:44:30 GMT):
no, the certs used by the nodejs app -- those are what you'll refer to in the chaincode

odowdaibm (Fri, 16 Mar 2018 07:44:42 GMT):
or rather the roles and other information

odowdaibm (Fri, 16 Mar 2018 07:45:24 GMT):
but make sure that you don't make that too depend on the on the cert in such a way that if the cert changes you have to update your chaincode

odowdaibm (Fri, 16 Mar 2018 07:45:24 GMT):
but make sure that you don't make that too dependent on the on the cert in such a way that if the cert changes you have to update your chaincode

varun-raj (Fri, 16 Mar 2018 07:45:39 GMT):
I mean when we register an user we're defining the roles as one of the attributes. If they are about to promoted or depromoted, we give them a different certificate

odowdaibm (Fri, 16 Mar 2018 07:46:02 GMT):
yes, and in your chaincode, you'll do different things dependent on that

varun-raj (Fri, 16 Mar 2018 07:46:21 GMT):
The chaincode just check if the current user is of which role. Thus if they use the new certificate they'll be of different role

odowdaibm (Fri, 16 Mar 2018 07:46:36 GMT):
just be careful to not have to change the logic if the cert changes, and try to separate logic from access control, as much as you cn

odowdaibm (Fri, 16 Mar 2018 07:46:36 GMT):
just be careful to not have to change the logic if the cert changes, and try to separate logic from access control, as much as you can

odowdaibm (Fri, 16 Mar 2018 07:46:49 GMT):
yes, if you're ust role checking that's great!

odowdaibm (Fri, 16 Mar 2018 07:47:19 GMT):
Let's think about a JIRA and topic on this subject

varun-raj (Fri, 16 Mar 2018 07:47:27 GMT):
We need to disable few functions for few roles, thus we check and just throw and error and stop propogating

odowdaibm (Fri, 16 Mar 2018 07:47:29 GMT):
Do you think it would be helpful?

varun-raj (Fri, 16 Mar 2018 07:47:42 GMT):
Yeah I think people are getting stuck at application part a lot

odowdaibm (Fri, 16 Mar 2018 07:48:03 GMT):
So if I created a JIRA, would you be able to pop some ideas into it

odowdaibm (Fri, 16 Mar 2018 07:48:19 GMT):
let me do that now, and you can drop some thoughts in it

varun-raj (Fri, 16 Mar 2018 07:48:22 GMT):
Keep me posted :D I'll share my inputs and experiences on this

odowdaibm (Fri, 16 Mar 2018 07:52:59 GMT):
@varun-raj what's your name for JIRA?

odowdaibm (Fri, 16 Mar 2018 07:54:15 GMT):
@varun-raj I've created https://jira.hyperledger.org/browse/FAB-8917

varun-raj (Fri, 16 Mar 2018 07:55:36 GMT):
It's same as rocket chat. : varun-raj

varun-raj (Fri, 16 Mar 2018 07:55:46 GMT):
Great, I'll write my suggestions. :)

odowdaibm (Fri, 16 Mar 2018 07:57:06 GMT):
Please add your thoughts, and thanks again!

varun-raj (Fri, 16 Mar 2018 08:16:31 GMT):
I'm excited to see other peoples responses as well :)

eramitg (Fri, 16 Mar 2018 15:06:43 GMT):
but webex is not working here to see anyone

joe-alewine (Fri, 16 Mar 2018 15:07:31 GMT):
@eramitg It's in an hour due to Daylight Savings Time

eramitg (Fri, 16 Mar 2018 15:08:34 GMT):
google calendar it showing 8:30 am in indian time

Ammu (Thu, 22 Mar 2018 06:50:03 GMT):
i ahve done balance transfer upto qury channel steps

Ammu (Thu, 22 Mar 2018 06:50:43 GMT):
Network configuration considerations topic i couldn't understand

cca88 (Thu, 22 Mar 2018 08:33:40 GMT):
When looking at the docs under - https://hyperledger-fabric.readthedocs.io/en/release-1.1/index.html - then certain topics listed under "Welcome..." are repeated again as top-level items below. For example, "Architecture reference" and "command reference". This seems strange, especially since they contain the same material. (but they are not in the same order). Also when I open the first "Architecture..." then its subcategories appear, but the second "Architecture.." below somehow appears opens as well with the categories. This seems strange. Is this by design? or just an oversight?

joe-alewine (Thu, 22 Mar 2018 15:03:35 GMT):
@cca88 We have a jira item open for that: https://jira.hyperledger.org/browse/FAB-8798 Do you have any suggestion for how to improve this within the context of ReadTheDocs?

cca88 (Thu, 22 Mar 2018 19:59:19 GMT):
@joe-alewine - I see, the issue has been recognized, thanks. I would simply have the top line (Welcome to...) not open to any subitems, it would only be that one welcome page which includes in its lowest parts the same menu of links again. Nothing would be lost. As it is, the submenu duplication seems to confuse not only myself, but also the others under FAB8798.

joe-alewine (Thu, 22 Mar 2018 22:07:41 GMT):
Yes, it is confusing and something we'd like to change. We welcome input from any RTD experts who can help us out (as the new TOC does have advantages we don't want to lose)

dampuero (Fri, 23 Mar 2018 08:02:12 GMT):
Sorry, I send this message for error.

cca88 (Fri, 23 Mar 2018 08:24:30 GMT):
What is "RTD" ? What are the other advantages of the TOC format compared to the my suggestion above?

andreamagagna (Fri, 23 Mar 2018 09:54:55 GMT):
Hi everybody, does anyone know how to run the query `GET host:port/chain/blocks/{block-id}` in Fabric?

cbf (Mon, 26 Mar 2018 12:53:42 GMT):
@rday thanks for all the patches! on this one, I'd like to be a bit more cautious as to referencing SDKs that aren't formally part of the release. Please see my comment https://gerrit.hyperledger.org/r/c/19733/

cbf (Mon, 26 Mar 2018 12:54:26 GMT):
@cca88 RTD is readthedocs, the service we use to generate our documentation

cbf (Mon, 26 Mar 2018 12:55:41 GMT):
As for the change you suggested, we could do that, it just makes navigation in long pages a bit harder since there are no shortcuts.

cbf (Mon, 26 Mar 2018 15:22:51 GMT):
@eramitg conversation on this (and any other) channel should not be limited to a point in time - in the case above, I was replying to Christian as he had a question that did not seem to get an answer.

SjirNijssen (Tue, 27 Mar 2018 16:08:46 GMT):
The members of the Fabric Documentation WG would appreciate an answer to the following: Given the following Topology3: 1. There are 9 orgs in a specific HLF network, org1 through org9; 2. There is a consortium c12, covering org1 and org2; 3. There is a consortium c34, covering org3 and org4; 4. There is a consortium C123456 covering consortium c12 and c34 and org 5 and org 6; 5. There is a consortium c789 covering org7, org8 and org9; 6. There is a consortium c123456789, covering consortium c123456 and consortium C789; 7. There is a consortium c123456789, covering org1, org2, arg3, org4, org5, org6, org7, org8 and org9. Which of these 7 facts are out of scope in HLF? Thanks in advance.

eramitg (Tue, 27 Mar 2018 20:04:08 GMT):
Dear Sir @odowdaibm why i am getting this error during checkout or pulling gerrit data as shown screenshot...

eramitg (Tue, 27 Mar 2018 20:05:53 GMT):
i used these commands one by one in terminal and encountered error git fetch ssh://eramitg@gerrit.hyperledger.org:29418/fabric refs/changes/13/18813/22 && git checkout FETCH_HEAD

eramitg (Tue, 27 Mar 2018 20:06:16 GMT):
git fetch ssh://eramitg@gerrit.hyperledger.org:29418/fabric refs/changes/13/18813/22 && git cherry-pick FETCH_HEAD

eramitg (Tue, 27 Mar 2018 20:06:27 GMT):
git fetch ssh://eramitg@gerrit.hyperledger.org:29418/fabric refs/changes/13/18813/22 && git format-patch -1 --stdout FETCH_HEAD

eramitg (Tue, 27 Mar 2018 20:06:38 GMT):
git pull ssh://eramitg@gerrit.hyperledger.org:29418/fabric refs/changes/13/18813/22

eramitg (Tue, 27 Mar 2018 20:06:54 GMT):
please any can help for this concern.

varun-raj (Wed, 28 Mar 2018 06:53:54 GMT):
Is there any documentation explaining th each and every environment variables?

rjones (Wed, 28 Mar 2018 16:08:07 GMT):
Hi. If you're making changes to the documentation, like this: https://gerrit.hyperledger.org/r/#/c/19681/ (to choose a recent example) please don't add a link to your staging repo to the commit message. Add it as a comment. Also: [ci-skip] does nothing. Also: All of the docs builds show up on the logs server. For this particular change, it is here: https://logs.hyperledger.org/production/vex-yul-hyp-jenkins-3/fabric-rtd-verify-master/399/html/ this will make it easier for people - you don't need to maintain a distinct RTD repo, for instance.

rjones (Wed, 28 Mar 2018 16:08:07 GMT):
If you're making changes to the documentation, like this: https://gerrit.hyperledger.org/r/#/c/19681/ (to choose a recent example) please don't add a link to your staging repo to the commit message. Add it as a comment. Also: [ci-skip] does nothing. Also: All of the docs builds show up on the logs server. For this particular change, it is here: https://logs.hyperledger.org/production/vex-yul-hyp-jenkins-3/fabric-rtd-verify-master/399/html/ this will make it easier for people - you don't need to maintain a distinct RTD repo, for instance. thank you.

rjones (Wed, 28 Mar 2018 16:11:25 GMT):
@eramitg did you get the gerrit checkout issue resolved?

rjones (Thu, 29 Mar 2018 17:12:06 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=7RQYm3CMyakqHtffn) @eramitg what if you check out over anonymous http?

eramitg (Thu, 29 Mar 2018 17:12:36 GMT):
just i am trying one ore time @rjones

eramitg (Thu, 29 Mar 2018 17:12:38 GMT):
git fetch ssh://eramitg@gerrit.hyperledger.org:29418/fabric refs/changes/13/18813/22 && git checkout FETCH_HEAD

rjones (Thu, 29 Mar 2018 17:13:51 GMT):
or using the new UI generate an http password and use authenticated https: https://gerrit.hyperledger.org/r/settings/preferences#HTTPCredentials

eramitg (Thu, 29 Mar 2018 17:18:41 GMT):
@rjones it's fetching my this command waiting for completion of this tak ,i hope today i will not encounter any error for this command git fetch ssh://eramitg@gerrit.hyperledger.org:29418/fabric refs/changes/13/18813/22 && git checkout FETCH_HEAD

eramitg (Thu, 29 Mar 2018 17:18:41 GMT):
@rjones it's fetching my this command waiting for completion of this tak ,i hope today i will not encounter eeror for this command git fetch ssh://eramitg@gerrit.hyperledger.org:29418/fabric refs/changes/13/18813/22 && git checkout FETCH_HEAD

eramitg (Thu, 29 Mar 2018 17:18:41 GMT):
@rjones it's fetching my this command waiting for completion of this tak ,i hope today i will not encounter not error for this command git fetch ssh://eramitg@gerrit.hyperledger.org:29418/fabric refs/changes/13/18813/22 && git checkout FETCH_HEAD

joe-alewine (Thu, 29 Mar 2018 19:03:34 GMT):
So we're currently developing plans and strategies around the next steps we want to take with Fabric documentation in 1.2. We've developed a backlog by prioritizing the (many) open jira items we have. The top 40 of these -- everything above `FAB-2185-Hyperledger Fabric Logo` is something we think is at least

joe-alewine (Thu, 29 Mar 2018 19:03:34 GMT):
@here So we're currently developing plans and strategies around the next steps we want to take with Fabric documentation as we approach 1.2. We've developed a backlog by prioritizing the (many) open jira items we have, with the most important items at the top. Roughly the top 40 of these -- everything above `FAB-2185-Hyperledger Fabric Logo` -- is something we think is at least considering. https://jira.hyperledger.org/secure/RapidBoard.jspa?rapidView=119&view=planning.nodetail We welcome feedback on this backlog. Some items are, obviously, more important than others, but also might represent a much bigger investment of time, so the list is not meant to precisely reflect most important to least important from the top down. What do you want to see? What should be higher? What should be lower?

joe-alewine (Thu, 29 Mar 2018 19:03:34 GMT):
@here So we're currently developing plans and strategies around the next steps we want to take with Fabric documentation as we approach 1.2. We've developed a backlog by prioritizing the (many) open jira items we have, with the most important items at the top. Roughly the top 40 of these -- everything above `FAB-2185-Hyperledger Fabric Logo` -- is something we think is at least considering. https://jira.hyperledger.org/secure/RapidBoard.jspa?rapidView=119&view=planning.nodetail We welcome feedback on this backlog. Some items are, obviously, more important than others, but also might represent a much bigger investment of time, so the list is not meant to precisely reflect most important to least important from the top down (though new features must of course be documented -- what will actually make it into 1.2 and what will be pushed to further releases is still in flux). What do you want to see? What should be higher? What should be lower?

joe-alewine (Thu, 29 Mar 2018 19:03:34 GMT):
@here So we're currently developing plans and strategies around the next steps we want to take with Fabric documentation as we approach 1.2. We've developed a backlog by prioritizing the (many) open jira items we have, with the most important items (generally speaking) at the top. Roughly the top 40 of these -- everything above `FAB-2185-Hyperledger Fabric Logo` -- is something we think is at least considering. https://jira.hyperledger.org/secure/RapidBoard.jspa?rapidView=119&view=planning.nodetail We *welcome* feedback on this backlog. Some items are, obviously, more important than others, but also might represent a much bigger investment of time, so the list is not meant to precisely reflect most important to least important from the top down (though new features must of course be documented -- what will actually make it into 1.2 and what will be pushed to further releases is still in flux). What do you want to see? What should be higher on the list? What should be lower? What should be on this "top 40" list that currently isn't? What's on the list that shouldn't be?

SjirNijssen (Fri, 30 Mar 2018 08:27:50 GMT):
I would recommend to give the extension of the Glossary a high priority. The sooner people apply the same concepts and terms in their communication and the same meaning, the sooner misunderstanding diminishes. I am happy to see that Consortium and Organization have been added and that Ledger has been given a substantial update. I would recommend that we include in the concept definition where applicable a short description of the why for the business. E.g with the current definition of Consortium people may ask the following: if all members of a channel must be in the same consortium and there is no inter-channel communication, make clear why there is the concept of consortium. Furthermore in the discussions in the Fabric-doc WG the assertion was made by a highly respected member that an organzation may only have a client application, hence no peer and no orderer. This is not consistent with the current definition of Consortium.

SjirNijssen (Fri, 30 Mar 2018 08:31:18 GMT):
Wrt the definition of Ledger. I believe we need more precision. The blockchain component of a ledger is immutable, the world state component is mutable.

SjirNijssen (Fri, 30 Mar 2018 11:43:48 GMT):
I propose to give top priority of include the term Blockchain in the Glossary

Ammu (Fri, 30 Mar 2018 13:09:28 GMT):
what is organization in hyperledger fabrics

SjirNijssen (Fri, 30 Mar 2018 13:30:40 GMT):
I believe there is inconsistency between the last sentence of the definition of Consortium in the Glossary and the last sentence in the definition of Organization.

joe-alewine (Fri, 30 Mar 2018 14:56:05 GMT):
@SjirNijssen The idea there is that technically orderers are also organizations (though they're not part of a consortium). But all of the organizations in a channel must be part of a consortium

joe-alewine (Fri, 30 Mar 2018 14:58:38 GMT):
The problem is that we call orderers "organizations". It would probably be preferable if we didn't do that, but we do

SjirNijssen (Fri, 30 Mar 2018 14:59:05 GMT):
Thanks, Joe for the explanation. Let us modify the definition such that this in crystal clear.

silliman (Fri, 30 Mar 2018 15:01:40 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=Wv7bw4PEYvxPrA7sc) @joe-alewine I thought that, although all organizations that are to be part of a channel at its creation time must be part of a consortium, one could update an existing channel to add organizations that are not defined to a consortium. Is my thought correct?

nickgaski (Fri, 30 Mar 2018 16:37:09 GMT):
@silliman - you're correct. that's exactly what the adding an org tutorial demonstrates. The new org - `org3` - has no presence in the system config block, only the channel.

silliman (Fri, 30 Mar 2018 16:37:59 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=pemgf7YZmXDzbkbgE) @nickgaski tx Nick, just making sure my understanding was still correct.

SjirNijssen (Fri, 30 Mar 2018 17:44:06 GMT):
@nickgaski - Hi Nick, thanks for your explanation. I have tried to answer the question, WHY this functionality is in HLF. My assumption is that an org that enters the network via a consortium only needs the permission of that consortium, while a-non-consortium org needs the permission of every consortium. Is that assumption correct?

SjirNijssen (Sat, 31 Mar 2018 19:23:52 GMT):
@jyellick Hi Jason. Thanks for your offer. For the record, I am not the author of the statement "All members of a channel must be in the same consortium." But I am happy that this statement has been made such that we now can find out exactly how the relationship is between channels, organizations and consortia. Let me summarize what I have learned so far: make a clear distinction between the system channel and the application channels. Let me ask the following question: suppose that all organizations and all consortia in a HLF network agree to have one application channel for all peers of all orgs, inside and outside a consortium but of course inside the HLF network, is that permitted? Any subset of the organizations (inside and outside a consortium in a HLF network) can have a second,separate application channel? A subset of said subset can have a third application channel. You have probably a much better formulation of what that relationship is. I am sure my colleagues in the documentation WG and myself really appreciate your help. Kind regards Sjir

jyellick (Sun, 01 Apr 2018 01:50:28 GMT):
@SjirNijssen > suppose that all organizations and all consortia in a HLF network agree to have one application channel for all peers of all orgs, inside and outside a consortium but of course inside the HLF network, is that permitted? A channel could be created by some subset of a consortium, and that channel's membership could be extended to include all other organizations. (Note, this would be a reconfiguration of a channel after its creation). > Any subset of the organizations (inside and outside a consortium in a HLF network) can have a second,separate application channel? Any subset of the organizations (inside and outside a consortium in a HLF network) can have a second,separate application channel? A subset of said subset can have a third application channel. Yes, in a similar fashion to the first, these configurations could be achieved > You have probably a much better formulation of what that relationship is. Yes, let me see if I can articulate this concisely. The orderer system channel defines consortiums When a channel is created, its initial membership must be only those organizations from within the consortium identified within the channel creation transaction. Once a channel has been created, the membership of the channel may be changed arbitrarily (to add other orgs from the consortium, or orgs from outside the consortium). So, initial channel creation restricts the membership to be a subset of a consortium. After creation, the channel membership may be arbitrary (assuming of course, the initial membership approves the modifications)

SjirNijssen (Sun, 01 Apr 2018 15:29:17 GMT):
@jyellick Thanks Jason. Let me try a set of scenario's to test my understanding of your response. Suppose we set up a new HLF network, called BYSN (Build Your Second Network). BYSN has the following organizations A, B, C, D, E, F and G. C and D are part of consortium CD; E, F and G are part of consortium EFG. I believe that all of the following channels are permitted: 1. Channel CnlA, for all the peers and all client apps of org A. 2. Channel CnlA-1, a channel for only a subset of the peers and client applications of A. 3. Channel CnlA-2, a channel with a subset of the peers and client applications of A, partly overlapping with the elements in CnlA-1 and partly having different elements. 4. Channel CnlAB, for all the peers and all the client applications of A and B. 5. Channel CnlB for all the peers and all the client applications of org B. 6. CnlBC-1 with a subset of the peers and client applications of org B and with a subset of the peers and client applications of org C. 7. CnlBC-2, with a subset of the peers and client application of org B and a subset of the peers and client applications of org C, partly overlapping with elements of CnlBC-1 and partly having elements not being in CnlBC-1. 8. CnlCD, a channel with all the peers and client applications from org C and similar of org D. 9. CnlEF, a channel for all the peers and all the client applications of both org E and org F. 10. CnlEFG with all the peers and client applications of all of org E, F and G. 11. CnlABCDEFG, a channel with all the peers and all the client applications of org A, B, C, D, E, F and G. My preliminary conclusion is that all these channels are permitted. Is that right, and where not, can you please say why not. Thanks for your attention. Sjir

jyellick (Sun, 01 Apr 2018 23:07:51 GMT):
> BYSN has the following organizations A, B, C, D, E, F and G. C and D are part of consortium CD; E, F and G are part of consortium EFG What consortium are A and B a part of? Also, theoretically, any channel configuration is achievable through reconfiguration. So it might help to clarify whether you are discussing the channel's initial configuration or some further reconfiguration.

jyellick (Sun, 01 Apr 2018 23:07:51 GMT):
> BYSN has the following organizations A, B, C, D, E, F and G. C and D are part of consortium CD; E, F and G are part of consortium EFG @SjirNijssen What consortium are A and B a part of? > 1. Channel CnlA, for all the peers and all client apps of org A. 2. Channel CnlA-1, a channel for only a subset of the peers and client applications of A. 3. Channel CnlA-2, a channel with a subset of the peers and client applications of A, partly overlapping with the elements in CnlA-1 and partly having different elements. 4. Channel CnlAB, for all the peers and all the client applications of A and B. 5. Channel CnlB for all the peers and all the client applications of org B. 6. CnlBC-1 with a subset of the peers and client applications of org B and with a subset of the peers and client applications of org C. 7. CnlBC-2, with a subset of the peers and client application of org B and a subset of the peers and client applications of org C, partly overlapping with elements of CnlBC-1 and partly having elements not being in CnlBC-1. 8. CnlCD, a channel with all the peers and client applications from org C and similar of org D. 9. CnlEF, a channel for all the peers and all the client applications of both org E and org F. 10. CnlEFG with all the peers and client applications of all of org E, F and G. 11. CnlABCDEFG, a channel with all the peers and all the client applications of org A, B, C, D, E, F and G. All of these channel configurations are possible. Not all of them are possible at initial channel creation time and would require reconfiguration. (I cannot say which are possible at channel creation time without knowing about the consortium of A and B)

jyellick (Sun, 01 Apr 2018 23:07:51 GMT):
> BYSN has the following organizations A, B, C, D, E, F and G. C and D are part of consortium CD; E, F and G are part of consortium EFG @SjirNijssen What consortium are A and B a part of? (as a side note, an organization may part of multiple consortia) > 1. Channel CnlA, for all the peers and all client apps of org A. 2. Channel CnlA-1, a channel for only a subset of the peers and client applications of A. 3. Channel CnlA-2, a channel with a subset of the peers and client applications of A, partly overlapping with the elements in CnlA-1 and partly having different elements. 4. Channel CnlAB, for all the peers and all the client applications of A and B. 5. Channel CnlB for all the peers and all the client applications of org B. 6. CnlBC-1 with a subset of the peers and client applications of org B and with a subset of the peers and client applications of org C. 7. CnlBC-2, with a subset of the peers and client application of org B and a subset of the peers and client applications of org C, partly overlapping with elements of CnlBC-1 and partly having elements not being in CnlBC-1. 8. CnlCD, a channel with all the peers and client applications from org C and similar of org D. 9. CnlEF, a channel for all the peers and all the client applications of both org E and org F. 10. CnlEFG with all the peers and client applications of all of org E, F and G. 11. CnlABCDEFG, a channel with all the peers and all the client applications of org A, B, C, D, E, F and G. All of these channel configurations are possible. Not all of them are possible at initial channel creation time and would require reconfiguration. (I cannot say which are possible at channel creation time without knowing about the consortium of A and B)

SjirNijssen (Mon, 02 Apr 2018 09:14:35 GMT):
@jyellick Hi Jason, thanks for your answer. If not all of them are possible at creation time, I would propose we document, which are not possible at initial channel creation time and why not, with sufficient examples. I am willing to put in the necessary time, and save your time, if you could direct me to the documents (incl FABs or code) where I can find the rules. Wrt the consortium of A and B, is it a necessity for an organziation to belong to a consortium? Otherwise assume A and B are elements of consortium AB.

jyellick (Mon, 02 Apr 2018 13:40:31 GMT):
@SjirNijssen https://github.com/hyperledger/fabric/blob/release-1.1/orderer/common/msgprocessor/systemchannel.go#L279-L299 is the code which enforces the membership at channel creation time.

bmos299 (Mon, 02 Apr 2018 14:29:00 GMT):
@joe-alewine based on your e-mail to the group on documentation prioritization. I want to add some general thoughts before looking at the lists.

bmos299 (Mon, 02 Apr 2018 14:29:00 GMT):
@joe-alewine based on your e-mail to the group on documentation prioritization. I want to add some general thoughts before looking at the lists. ``` 1. Creating tutorials strategically. For example, one showing security with Attribute-Based Access Control (ABAC) is one that could greatly benefit the community. 2. Every new feature definitely needs some documentation, but not necessarily a sample in the fabric-samples repository. 3. There is a little confusion with 'Tutorials and Operational Guide'. The operations guides can always have command syntax but doesn't necessarily need a detailed tutorial. 4. Concept documentations. These are very useful but tend to have a lot of comments, feedback, and discussion. I think these are best vetted out with the SMEs and the documentation team provide more editorial support once completed vetted to avoid slowing ay documentation writer down. ```

bmos299 (Mon, 02 Apr 2018 14:29:00 GMT):
@joe-alewine based on your e-mail to the group on documentation prioritization. I want to add some general thoughts before looking at the lists. ``` 1. Creating tutorials strategically. For example, one showing security with Attribute-Based Access Control (ABAC) is one that could greatly benefit the community. ``` ``` 2. Every new feature definitely needs some documentation, but not necessarily a sample in the fabric-samples repository. ``` ``` 3. There is a little confusion with Tutorials and Operational Guide. The operations guides can always have command syntax but doesn't necessarily need a detailed tutorial. ``` ``` 4. Concept documentations. These are very useful but tend to have a lot of comments, feedback, and discussion. I think these are best vetted out with the SMEs and the documentation team provide more editorial support once completed vetted to avoid slowing ay documentation writer down. ```

bmos299 (Mon, 02 Apr 2018 14:29:00 GMT):
@joe-alewine based on your e-mail to the group on documentation prioritization. I want to add some general thoughts before looking at the lists. ``` 1. Creating tutorials strategically. For example, one showing security with Attribute-Based Access Control (ABAC) is one that could greatly benefit the community. 2. Every new feature definitely needs some documentation, but not necessarily a sample in the fabric-samples repository. 3. There is a little confusion with Tutorials and Operational Guide. The operations guides can always have command syntax but doesn't necessarily need a detailed tutorial. 4. Concept documentations. These are very useful but tend to have a lot of comments, feedback, and discussion. I think these are best vetted out with the SMEs and the documentation team provide more editorial support once completed vetted to avoid slowing ay documentation writer down. ```

odowdaibm (Wed, 04 Apr 2018 23:28:59 GMT):
@all We're getting close on the new ledger topic: http://fabricdocs1.readthedocs.io/en/issue-fab-8689/ledger/ledger.html Have a read, and if you'd like to comment -- please do so here: https://gerrit.hyperledger.org/r/c/18813/ All comments very welcome!

cbf (Wed, 04 Apr 2018 23:40:24 GMT):
@odowdaibm seems odd to me to introduce world state before blockchain

cbf (Wed, 04 Apr 2018 23:43:32 GMT):
still do not like the repetitive "The visual vocabulary expressed in facts is as follows:" for every figure description... it is just more words to read

crissi (Thu, 05 Apr 2018 05:06:35 GMT):
Any explanation is available regarding the balancetransfer application?

notOccupanther (Thu, 05 Apr 2018 08:05:12 GMT):
HI .. is there anywhere I can find hardware specs for HL Nodes / Orderers etc?

crissi (Thu, 05 Apr 2018 08:40:02 GMT):
Can you please help me to setup an application similar to balancetransfer?

odowdaibm (Thu, 05 Apr 2018 16:06:35 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=DKM8ydwxSTgny4FfF) @cbf yes Chris, we discussed changing world state to be first -- it just makes the explanation flow a little easier. Also, we're sensitive to the repetitive nature of that phrase. It might make sense to carve that out as a short section -- we're trying to get people used to seeing standardized diagrams, but maybe using a less repetitive style might work better?

odowdaibm (Thu, 05 Apr 2018 16:10:11 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=mGGQv5EcaBhQ5Jzc2) @rjones ty Ry, very helpful indeed. It might be helpful to have an easy link for people to go to built docs?

odowdaibm (Thu, 05 Apr 2018 16:11:38 GMT):
@SjirNijssen Where was that discussion on chaincode and transactions you mentioned on the call?

SjirNijssen (Thu, 05 Apr 2018 16:13:46 GMT):
@odowdaibm @cbf From a mathematical point of view it is indeed odd as Ws = f(Bc). However from the point of view what people are most interested in, we hear that then Ws comes first. Of course in the Ledger topic it has been said very clear that Ws = f(Bc). As we are interested in building more support for HLF, we have used both approaches in the Ledger topic.

odowdaibm (Thu, 05 Apr 2018 16:15:19 GMT):
@SjirNijssen Apols, I meant with David on multiple ledger operations?

SjirNijssen (Thu, 05 Apr 2018 16:16:01 GMT):
@odowdaibm I will forward it in a minute

cbf (Thu, 05 Apr 2018 16:44:01 GMT):
@odowdaibm yeah, took a while for it to grow on me is all

SmartContract2018 (Thu, 05 Apr 2018 19:35:29 GMT):
Has joined the channel.

odowdaibm (Thu, 05 Apr 2018 22:54:56 GMT):
Hi All, we have our documentation workgroup weekly call tomorrow at the usual time: https://lists.hyperledger.org/pipermail/hyperledger-fabric/2018-April/003309.html We choose our next topic tomorrow to work on the daily calls. Please join if you'd like to work on a particular concept topic. Network topology (including channels), chaincode and transactions are current favourites.

odowdaibm (Fri, 06 Apr 2018 05:39:11 GMT):
https://ibm.webex.com/meet/a_o-dowd

odowdaibm (Fri, 06 Apr 2018 05:40:27 GMT):
We're also on now for the las 40 mins

odowdaibm (Fri, 06 Apr 2018 05:40:27 GMT):
We're also on now for the last 40 mins

odowdaibm (Fri, 06 Apr 2018 15:38:57 GMT):
http://arxiv-export-lb.library.cornell.edu/abs/1801.10228

rickr (Fri, 06 Apr 2018 17:24:26 GMT):
@dave.enyeart @jyellick Do we have any documentation that goes into to some detail why a user would get any of these errors in their transaction `TxValidationCode` ? Maybe then how to even remedy if possible ?

jyellick (Fri, 06 Apr 2018 17:27:38 GMT):
@rickr Do you mean https://github.com/hyperledger/fabric/blob/release-1.1/protos/peer/transaction.proto#L125-L151 ?

rickr (Fri, 06 Apr 2018 17:28:39 GMT):
Yeah some are obvious but having some more doucmention to point to users to than just a proto buf is IMO needed

rickr (Fri, 06 Apr 2018 17:29:58 GMT):
PHANTOM_READ_CONFLICT PHANTOM_READ_CONFLICT an explanation why that my occur and how to possible avoid/fxi ?

jyellick (Fri, 06 Apr 2018 17:29:59 GMT):
I don't disagree. I'm unaware of any more detailed explanations, would have to grep for them in the code to see when they are returned.

jyellick (Fri, 06 Apr 2018 17:30:10 GMT):
Ah, I think I can help you with those

jyellick (Fri, 06 Apr 2018 17:31:43 GMT):
I agree. FWIW, a phantom read conflict occurs when the chaincode does a range query whose result changes between execution and commit. E.g., the chaincode looks for "all people named Rick" then does some write. At commit time, there is a new person named Rick who would have appeared in the query. This is a phantom read.

rickr (Fri, 06 Apr 2018 17:33:33 GMT):
`Rick` you sure there's no PHANTOM_MENACE define for that ?

SjirNijssen (Fri, 06 Apr 2018 18:01:19 GMT):
@jyellick Hi Jason, interesting phenomenon called phantom. I try to understand why this has another name than a distributed concurrency update problem. Maybe I misunderstand the example: I assume it would be the following: give everybody a raise of 3 % with the name Rick. If the endorser reads 3 different personkeys having as first name Rick and the committer reads 4 with first name Rick, why does this get a special name?

jyellick (Fri, 06 Apr 2018 18:03:33 GMT):
This is simply re-using a well known name from traditional databases https://en.wikipedia.org/wiki/Isolation_(database_systems)#Phantom_reads

SjirNijssen (Fri, 06 Apr 2018 18:49:42 GMT):
@jyellick Thanks Jason, I learned a new synonym.

SmartContract2018 (Sat, 07 Apr 2018 19:15:56 GMT):
dear friends, can anybody please help me understand the currently available consensus mechanism on hyperledger fabric v1.0?

SmartContract2018 (Sat, 07 Apr 2018 19:22:31 GMT):
Is it correct to say that PBFT is not yet available on fabric 1.0?

rjones (Sat, 07 Apr 2018 19:24:08 GMT):
@SmartContract2018 best to ask in #fabric-questions

SmartContract2018 (Sat, 07 Apr 2018 19:53:25 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=BYyYXbuaBbxG9ovYo) @rjones Thanks

cbf (Mon, 09 Apr 2018 14:31:37 GMT):
@odowdaibm check out https://gerrit.hyperledger.org/r/c/18233/ please... following up on generating the syntax for the commands and sandwiching with preamble and postscript content

odowdaibm (Tue, 10 Apr 2018 17:23:50 GMT):
argh, yes will have a look tomorrow- and thanks for heads up

joe-alewine (Wed, 11 Apr 2018 13:43:18 GMT):
We're attempting to establish a visual vocabulary by adding images we've been using to describe components (or, in some cases, concepts) in the docs to the glossary. We welcome all feedback: https://gerrit.hyperledger.org/r/c/20377/

cbf (Wed, 11 Apr 2018 13:54:43 GMT):
I think that the images are a bit large and we need to provide context for them for the reader

joe-alewine (Wed, 11 Apr 2018 15:21:18 GMT):
Some of the images could be smaller as they're simple, but others are more complex and need to be large (or somewhat large).

eramitg (Wed, 11 Apr 2018 15:40:39 GMT):
Hi Folks , I am an Phd Candidate in www.nitrr.ac.in my Linkedind Profile is https://www.linkedin.com/in/eramitg/ for sake of earning an Phd Degree i was proposed Blockchain Technology research work area to my guide so oom I request all of you gyus ,please guide me and assign me some research oriented task so that we mutullay benifited research related to Hyperledger Umbrella Project , All of you feel free to catch me on twitter or skype to https://twitter.com/eramitg1 or amitg.iitb skype id also in Zoom to in Zoom ID 3649222703 or whatsapp +917773011100 Regards

richzhao (Thu, 12 Apr 2018 03:45:04 GMT):
@cbf The person's name is Mary Morris on the pictures, but the text uses John Doe. https://hyperledger-fabric.readthedocs.io/en/release-1.1/identity/identity.html

rjones (Thu, 12 Apr 2018 04:14:51 GMT):
@richzhao https://gerrit.hyperledger.org/r/#/c/20481/ https://gerrit.hyperledger.org/r/#/c/20479/ https://jira.hyperledger.org/browse/FAB-9477

richzhao (Thu, 12 Apr 2018 07:54:56 GMT):
the 1st see should be removed in We can see also see that whereas peers host the ledger and chaincodes, orderers most definitely do not. https://hyperledger-fabric.readthedocs.io/en/release-1.1/peers/peers.html#applications-and-peers

joe-alewine (Thu, 12 Apr 2018 13:00:26 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=gJEd5CbzLJ4TLw9vL) @rjones I had that as part of these changes: https://gerrit.hyperledger.org/r/c/19547/

rjones (Thu, 12 Apr 2018 13:01:18 GMT):
@joe-alewine I apologize. I didn't see that.

pandrejko (Thu, 12 Apr 2018 14:06:26 GMT):
Given the great new Ledger topic I'd like to add World State to the Fabric glossary. I wanted to socialize this proposal to get some feedback ```Current State See World state World State Also known as “current state”, the world state is a component of the HyperLedger Fabric ledger subsystem which describes the state of the ledger at a given point in time. It is the database of the ledger. The world state represents the latest values for all keys ever included in its chain transaction log. The world state makes it easy for a program to get the current value of these states, rather than having to calculate them by traversing the entire transaction log. The world state can change frequently, as states can be created, updated and deleted. Peers commit the latest values to ledger world state for each valid transaction included in a processed block. Chaincode executes transaction proposals against world state data. ```

SjirNijssen (Thu, 12 Apr 2018 15:57:24 GMT):
@pandrejko Pam, I gladly support this proposal. May I suggest we reconsider a part of it, the statement: The world state can change frequently, as states can be created, updated and deleted. I believe it would be more correct to say the following: The world state can change frequently, to be more precise every time a block is added to the chain with at least one valid update transaction. Regards Sjir

joe-alewine (Thu, 12 Apr 2018 16:24:18 GMT):
@pandrejko I might rephrase to say: ```Current State See World state World State Also known as the “current state”, the world state represents the latest values for all keys included in its chain transaction log. The world state makes it easy for a program to get the current value of these keys rather than having to calculate them by traversing the entire transaction log. The world state will change every time the value of a key changes (for example, when the ownership of a car -- the "key" -- goes from one person to another -- the "value") or when a new key is added (a car is created). As a result, the world state is critical to a transaction flow, since the current state of a key-value pair must be known before it can be changed. Peers commit the latest values to ledger world state for each valid transaction included in a processed block.

joe-alewine (Thu, 12 Apr 2018 16:29:00 GMT):
@rjones No worries. Rebased: https://gerrit.hyperledger.org/r/c/19547/

SjirNijssen (Thu, 12 Apr 2018 17:45:49 GMT):
@joe-alewine Would it not be more complete to extend the "modify" to cover insert (a new key enters the chain, and this the world state) and delete? Sjir

joe-alewine (Thu, 12 Apr 2018 17:48:44 GMT):
@SjirNijssen I didn't say anything about deleting a key, but I did mention that keys can be inserted when I said `or when a new key is added (a car is created)`. I don't think it's a good idea to cover too much about the nature of key-value pairs or the ways in which they can be modified here -- there's a key-value pair glossary term for that, or at least there should be ;). We just want people to have a good sense of what the world/current state reflects

SjirNijssen (Thu, 12 Apr 2018 17:55:34 GMT):
@joe-alewine Indeed, you included the insert. Excuse me for overlooking that.

joe-alewine (Thu, 12 Apr 2018 17:59:09 GMT):
@SjirNijssen As our British friend would say, no worries

toddinpal (Thu, 12 Apr 2018 21:30:33 GMT):
Is there any work being done to document protocols or is there any documentation on protocols?

CodeReaper (Fri, 13 Apr 2018 11:21:09 GMT):
Hi, where can I study side DB in proper implentation's perspective?

CodeReaper (Fri, 13 Apr 2018 11:21:09 GMT):
Hi, where can I study side DB from proper implentation's perspective?

eramitg (Fri, 13 Apr 2018 17:53:20 GMT):
successfully i was configure my mac and ubuntu machine with ssh key for sake of accesing Fabric documentation, if anyone new who would like to get my help for this concern related gerrit configure with ssh key for ubunty/mac machine , i am happy to help all of you.

eramitg (Fri, 13 Apr 2018 17:54:44 GMT):
@toddinpal which type of doucment your are looking for , like a bitcoin procol you are looking for fabric related protocols.

eramitg (Fri, 13 Apr 2018 17:54:44 GMT):
@toddinpal which type of doucment your are looking for , like a bitcoin protocol you are looking for fabric related protocols.

eramitg (Sat, 14 Apr 2018 18:41:06 GMT):
ssh://eramitg@gerrit.hyperledger.org:29418/fabric

mozkarakoc (Sun, 15 Apr 2018 09:45:50 GMT):
hi, Is there a tutorial with intermediate ca's that provide multiple configuration of msp?

mozkarakoc (Sun, 15 Apr 2018 09:46:09 GMT):
I know, it is documented here: https://hyperledger-fabric.readthedocs.io/en/release-1.1/membership/membership.html

varun-raj (Mon, 16 Apr 2018 04:51:57 GMT):
https://www.skcript.com/svr/top-7-things-you-should-know-before-developing-on-hyperledger-fabric/

SjirNijssen (Mon, 16 Apr 2018 10:48:41 GMT):
@varun-raj May I suggest to take a look at the recently added topic: http://fabricdocs1.readthedocs.io/en/issue-fab-8689/ledger/ledger.html Your use of the terms ledger, state data and blockchain is at variance with the use in the HLF documentation recently extended.

varun-raj (Mon, 16 Apr 2018 10:54:34 GMT):
Oh sure Let me check and update it

pandrejko (Mon, 16 Apr 2018 13:06:56 GMT):
Here is my proposal for the definition of Smart Contract in the Fabric Glossary - feedback/comments are welcome - ```A smart contract represents the business logic agreed to by members of the network which is expressed in the form of chaincode and provides controlled access to the ledger. A Smart contract is invoked by a client application external to the blockchain network when it needs to interact with the ledger. Smart contract chaincode runs on :ref:`Peer` nodes. ```

toddinpal (Mon, 16 Apr 2018 15:25:16 GMT):
@eramitg Hi, right now as far as I can tell, the only information about Fabric protocols is by examining the protobuf definitions provided in the source code. This makes it really difficult to try and understand the protocols. Ideally what would be nice is a something that makes it really easy to understand the content of each message type and the effect each message type has. Something like: https://blockchain-fabric.blogspot.com/2017/04/hyperledger-fabric-v10-block-structure.html only for protocol messages instead of ledger blocks, and then with an indication of when/why to use a specific message.

Blaise 4 (Mon, 16 Apr 2018 20:28:18 GMT):
I'm new to HL and golang... Is there a tool like Python's rST and `docutils` to make it easier to document APIs, eg. http://docs.python-requests.org/en/master/api/#requests.Response

Ammu (Tue, 17 Apr 2018 10:25:45 GMT):
if hackers taking information illegally from bank(AXIS bank), if the project into fabrics. if the data is taken from 1 peer how the owner of the bank get notification that our bank information has been stolen? in blockchain/fabrics

joe-alewine (Tue, 17 Apr 2018 12:07:04 GMT):
@Ammu Probably a better question for #fabric-questions. I'm sure it's also been discussed in any number of blog posts and articles about permissioned blockchains.

joe-alewine (Wed, 18 Apr 2018 13:29:17 GMT):
@Ammu Check out section 5.1 for information about Fabcoin: https://arxiv.org/pdf/1801.10228.pdf

pandrejko (Thu, 19 Apr 2018 12:03:03 GMT):
Nancy shared this link that might be interesting to our working group if you've not already seen it - https://www.ibm.com/developerworks/cloud/library/cl-blockchain-basics-glossary-bluemix-trs/index.html

jastisriradheshyam (Fri, 20 Apr 2018 07:41:37 GMT):
Has joined the channel.

Asara (Mon, 23 Apr 2018 21:11:16 GMT):
Hey all, just a heads up, it seems like the fabric-ca documentation is pretty outdated, and there hasn't been documentation to show how to successfully build the fabric-ca binary since the 1.1 release.

joe-alewine (Tue, 24 Apr 2018 16:34:25 GMT):
@Asara The CA documentation is maintained by the CA team. If you have specific issues probably best to mention those in #fabric-ca

cbf (Wed, 25 Apr 2018 18:59:41 GMT):
@odowdaibm per the guidance that Brian gave, I have incorporated our paper into the documentation https://gerrit.hyperledger.org/r/21013

kostas (Wed, 25 Apr 2018 21:21:22 GMT):
I thought this was quite useful: https://developers.google.com/style/

jmason900 (Wed, 25 Apr 2018 21:25:49 GMT):
@cbf Hyperledger Fabric is great framework that is getting better. I have interests in both documentation and training materials and will start attending working group meetings on those items. I also want to reuse the excellent documentation you have produced in presentations I do on blockchain. Where are the correct guidelines for documentation copyrights, references, approvals etc ?? Couldn't easily find them searching sites .. thanks for your help

jmason900 (Wed, 25 Apr 2018 21:25:49 GMT):
@cbf Hyperledger Fabric is a great framework that is getting better. I have interests in both documentation and training materials and will start attending working group meetings on those items. I also want to reuse the excellent documentation you have produced in presentations I do on blockchain. Where are the correct guidelines for documentation copyrights, references, approvals etc ?? Couldn't easily find them searching sites .. thanks for your help

cbf (Wed, 25 Apr 2018 21:41:39 GMT):
@jmason900 all Hyperledger docs produced under CCBY4.0 license

cbf (Wed, 25 Apr 2018 21:42:19 GMT):
https://creativecommons.org/licenses/by/4.0/

cbf (Wed, 25 Apr 2018 21:42:40 GMT):
basically you just have to attribute the source and identify any changes you make

cbf (Thu, 26 Apr 2018 00:35:41 GMT):
here's staged rendering of docs with the intro https://logs.hyperledger.org/production/vex-yul-hyp-jenkins-3/fabric-docs-build-x86_64/185/html/whatis.html

ondar07 (Thu, 26 Apr 2018 11:12:15 GMT):
I suppose this documentation (http://openblockchain.readthedocs.io/en/latest/API/CoreAPI/) has become a little outdated. Tell me please how to verify that the block containing the latest transaction now? I tried use _curl peer:7051/chain_ (i'm using chaincode-docker-devmode) as described http://openblockchain.readthedocs.io/en/latest/API/CoreAPI/#cli , but it doesn't work.

ondar07 (Thu, 26 Apr 2018 11:12:15 GMT):
I suppose this documentation (http://openblockchain.readthedocs.io/en/latest/API/CoreAPI/) has become a little outdated. Tell me please how to verify that the block contains the latest transaction now? I tried use _curl peer:7051/chain_ (i'm using chaincode-docker-devmode) as described http://openblockchain.readthedocs.io/en/latest/API/CoreAPI/#cli , but it doesn't work.

ondar07 (Thu, 26 Apr 2018 11:12:15 GMT):
I suppose this documentation (http://openblockchain.readthedocs.io/en/latest/API/CoreAPI/) has become a little outdated. Tell me please how to verify that the block contains the latest transaction now? I tried to use _curl peer:7051/chain_ (i'm using chaincode-docker-devmode) as described http://openblockchain.readthedocs.io/en/latest/API/CoreAPI/#cli , but it doesn't work.

cbf (Thu, 26 Apr 2018 12:09:40 GMT):
@ondar07 the openblockchain repo is deprecated, someone outside the communuty generated that documentation and we cannot get them to decommission it

cbf (Thu, 26 Apr 2018 12:10:19 GMT):
the Hyperledger Fabric documentation is here: http://hyperledger-fabric.readthedocs.io/en/latest/

vatsal.shah (Thu, 26 Apr 2018 20:27:42 GMT):
Can anyone point me to the documentation, that explains multiple ordering nodes and how multiple OSN's architecture works with kafka?

cbf (Thu, 26 Apr 2018 22:33:56 GMT):
@vatsal.shah that isn't currently documented

cbf (Thu, 26 Apr 2018 22:34:27 GMT):
I've begin the migration of fabric, fabric-ca etc docs to fabric-docs https://gerrit.hyperledger.org/r/21079

cbf (Thu, 26 Apr 2018 22:34:57 GMT):
@rjones has set up the RTD project and I'll adapt to match fabric

cbf (Thu, 26 Apr 2018 22:35:28 GMT):
we should get some eyes on the outstanding CRs so we can merge them and start moving content

cbf (Thu, 26 Apr 2018 22:35:48 GMT):
https://gerrit.hyperledger.org/r/c/21013/ https://gerrit.hyperledger.org/r/c/21043/ https://gerrit.hyperledger.org/r/c/20777/ https://gerrit.hyperledger.org/r/c/20469/ - may need to be resubmitted https://gerrit.hyperledger.org/r/c/19929/

rjones (Fri, 27 Apr 2018 03:28:23 GMT):
@rameshthoomu you could port the doc build parts to that repo

cbf (Fri, 27 Apr 2018 11:33:35 GMT):
@rjones @rameshthoomu I was going to take a shot at that

rjones (Fri, 27 Apr 2018 14:38:21 GMT):
@cbf there is a documentation build job that you get basically for free in global-jjb (which HYP-CI uses) talk to @jwagantall for details, all of the other projects use it https://github.com/lfit/releng-global-jjb

rjones (Fri, 27 Apr 2018 14:39:17 GMT):
we also ship a (slightly outdated) version of our CI as a lab for experimentation locally: https://github.com/lfit/releng-ci-workshop written by @bramwelt

rjones (Fri, 27 Apr 2018 14:39:56 GMT):
but the workshop is close enough to our current infra to be extremely useful

gauthampamu (Wed, 02 May 2018 16:41:08 GMT):
Links are not working...http://hyperledger-fabric-ca.readthedocs.io/en/release-1.1/users-guide.html#attribute-based-access-control For information on the chaincode library API for Attribute-Based Access Control, see https://github.com/hyperledger/fabric/tree/release/core/chaincode/lib/cid/README.md For an end-to-end sample which demonstrates Attribute-Based Access Control and more, see https://github.com/hyperledger/fabric-samples/tree/release/fabric-ca/README.md

gauthampamu (Wed, 02 May 2018 16:42:36 GMT):
About to figure it out but..it would helpful if the documentation is fixed.. https://github.com/hyperledger/fabric/tree/release-1.1/core/chaincode/lib/cid

cbf (Thu, 03 May 2018 11:40:38 GMT):
@gauthampamu I just tried http://hyperledger-fabric-ca.readthedocs.io/en/release-1.1/users-guide.html#attribute-based-access-control and it worked fine

cbf (Thu, 03 May 2018 11:41:49 GMT):
as for the next link, yes, I will fix that

songyuanjie (Fri, 04 May 2018 02:18:37 GMT):
The document describes the client can communicate with multiple endorsement nodes, but I did not find multiple links in the source code, but only one？branch is master

tkuhrt (Mon, 07 May 2018 18:05:09 GMT):
Hey all. Today in the #training-and-education-wg call, there were a couple of links shared: http://fabricdocs1.readthedocs.io/en/issue-fab-8689/ledger/ledger.html -and- https://logs.hyperledger.org/production/vex-yul-hyp-jenkins-3/fabric-docs-build-x86_64/223/html/key_concepts.html It is getting extremely confusing for people to be given access to so many different links that are all different copies of the same thing. Especially since http://hyperledger-fabric.readthedocs.io/en/latest/ should be the place where we want people to be looking. Is there anyway that we could stage stuff under http://hyperledger-fabric.readthedocs.io/en/staging/ or some similar manner so that no matter what people are always ending up at http://hyperledger-fabric.readthedocs.io/

rjones (Mon, 07 May 2018 18:21:38 GMT):
@tkuhrt the doc staging to the logs server was done to eliminate the need for developers to push unmerged changes to RTD for review. Nobody should be using those for anything other than review - they are ephemeral links. I say this to fill you in on the "why" not to say "this is the one true way"

tkuhrt (Mon, 07 May 2018 18:22:34 GMT):
Thanks, @ry. It is getting confusing for people to know where they should look.

rjones (Mon, 07 May 2018 18:25:12 GMT):
Confusion is understandable. I _feel_ for unmerged changes, the logs server is probably easiest. I'm not sure how we would handle publishing un-merged changes to RTD. I'm sure it could be worked out, if people would rather use RTD.

joe-alewine (Mon, 07 May 2018 18:32:05 GMT):
Pretty sure fabricdocs1 belongs to @odowdaibm, fwiw

Ammu (Tue, 08 May 2018 05:12:44 GMT):
According to my knowledge, With Fabric CA v1.0.x, you cannot modify attributes. With Fabric CA v1.1.x (which is currently in release candidate status) you can. I'm not sure I'm right or not, If you can help me to confirm this thing. It'll be great help for me!

hrt031293 (Thu, 10 May 2018 08:24:24 GMT):
Hello everyone, Is there anyone present, who had completed "Adding an Org to a Channel" tutorial?

rjones (Thu, 10 May 2018 13:25:39 GMT):
@hrt031293 I think it would be best to ask in #fabric-questions

hrt031293 (Thu, 10 May 2018 13:27:34 GMT):
OK, posted there also, but not getting any response there

pandrejko (Wed, 16 May 2018 12:51:14 GMT):
@SjirNijssen I've started writing a tutorial for SideDB and am grappling with the terminology as we speak, so your terminology proposal in the Fabric-scrum channel is very timely. I will be sure to include you in any terminology discussions we have. Nothing cast in stone, but I'd let to set a stake in the ground so we can all proceed forward with start of a unified set of terms

qsmen (Mon, 21 May 2018 06:22:35 GMT):
hi, in fabric the term chaincode is used instead of smartcontract. But I think the chaincode can function as a smart contract. However, the example in fabric release document hehaves not like any smartcontract, more like an api. In bitcoin the scripts hehave like a smartconstract. In ethereum, the smart constracts behave like smartcontract. I suggest in fabric document there should be some example chaincodes hehaving more like a smartcontract

kostas (Mon, 21 May 2018 18:59:06 GMT):
How do we handle links to markdown files of Github repos?

kostas (Mon, 21 May 2018 18:59:18 GMT):
Do we link to the latest master, or pin down to a version?

kostas (Mon, 21 May 2018 18:59:24 GMT):
Concretely, here's an example: https://gerrit.hyperledger.org/r/c/21823/

joe-alewine (Mon, 21 May 2018 19:36:31 GMT):
@kostas In here, I linked to master. I can understand what you're getting at, though. And I don't think there's a good answer. There's no good process for checking whether a git/code page has been updated and no longer reflects what's being said/shown in a doc

joe-alewine (Mon, 21 May 2018 19:36:31 GMT):
@kostas In here (https://gerrit.hyperledger.org/r/c/21447/), I linked to master. I can understand what you're getting at, though. And I don't think there's a good answer. There's no good process for checking whether a git/code page has been updated and no longer reflects what's being said/shown in a doc

joe-alewine (Mon, 21 May 2018 19:36:48 GMT):
We sort of end up relying on spotting these differences or someone noticing them and then patching things up

joe-alewine (Mon, 21 May 2018 19:37:21 GMT):
Which is of course less ideal than a proactive approach

joe-alewine (Mon, 21 May 2018 19:37:21 GMT):
Which is of course not as preferable as a proactive approach

cbf (Tue, 22 May 2018 11:39:31 GMT):
@qsmen I'm confused... how is chaincode not like smart contract?

dhrubesh (Tue, 22 May 2018 19:30:05 GMT):
Hey everyone. I'm a Front end developer from India. I have been reading a lot about hyperledger recently. In terms of development I couldn't find any good tutorials. Can anyone redirect me to some learning resources for beginners? I wish to explore Hyperledger Fabric.

joe-alewine (Tue, 22 May 2018 20:07:38 GMT):
@dhrubesh It's a bit disappointing you couldn't find any resources. Here is the Hyperledger Fabric documention: https://hyperledger-fabric.readthedocs.io/en/release-1.1/ There's a whole section in there on tutorials.

dhrubesh (Wed, 23 May 2018 05:13:03 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=kCvww4FPoHcfrtytj) @joe-alewine Thanks @joe-alewine

jmason900 (Thu, 24 May 2018 14:16:58 GMT):
has anyone started work on documenting Side Db and local collections yet ?? Side Db was experimental in v1.1 and local collections is targeted for v1.2 .. I've got use cases and want to see what we have for doc in draft mode .. thanks

KellyCooper (Thu, 24 May 2018 15:29:36 GMT):
#training-and-education-wg includes volunteers available to edit, test and contribute to tutorials and learning materials. Feel free to post possible collaboration in the wg or @KellyCooper. We have many volunteers for beginning projects and some volunteers for advanced. One way we can support your efforts is as users/consumers to comment on clarity, strengths and gaps in your documentation/materials. Your request(s) will be viewed by the group every Monday and we can track/manage on our end. Thanks, Kelly

hrt031293 (Fri, 25 May 2018 11:40:06 GMT):
Can anyone tell me, that how can I use my local storage file as a chaincode, for the installation of the chaincode?

joe-alewine (Fri, 25 May 2018 13:33:40 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=XEjjJmmB593ENvN8f) @jmason900 Yes, that's being worked on. We're hoping to have a conceptual-style doc as well as a tutorial for the v1.2 release of the docs

AlexanderZhovnuvaty (Wed, 30 May 2018 11:37:10 GMT):
Has joined the channel.

Ammu (Sat, 02 Jun 2018 07:18:48 GMT):
ccenv and zookeeper can u plz explain it?

cbf (Mon, 04 Jun 2018 11:29:12 GMT):
ccenv is the image from which we build the chaincode containers that are managed by the peers. zookeeper is necessary for kafka.

kostas (Mon, 04 Jun 2018 19:02:59 GMT):
This is how the sidebar on the readthedocs shows up here:

kostas (Mon, 04 Jun 2018 19:02:59 GMT):
This is how the sidebar on the readthedocs website looks:

kostas (Mon, 04 Jun 2018 19:03:25 GMT):
This has been going on for quite some time. Anybody else seeing this?

rameshthoomu (Mon, 04 Jun 2018 21:11:33 GMT):
@joe-alewine could you please the code in docs/source/_templates/layout.html?

joe-alewine (Mon, 04 Jun 2018 21:13:51 GMT):
I'm confused. This is the way it's rendering in the live docs

joe-alewine (Mon, 04 Jun 2018 21:13:51 GMT):
I'm confused @rameshthoomu . This is the way it's rendering in the live docs

rameshthoomu (Tue, 05 Jun 2018 03:04:47 GMT):
@joe-alewine I see the logos are appearing properly in jenkins docs build output https://logs.hyperledger.org/production/vex-yul-hyp-jenkins-3/fabric-docs-build-x86_64/393/html/ and I see the RTD and jenkins docs builds are using the same plugins from docs/requirements.txt

rameshthoomu (Tue, 05 Jun 2018 03:06:11 GMT):
I have crossed checked all the version between RTD and jenkins doc build and all are same.. Not sure what's wrong here.. Will check this tomorrow

hrt031293 (Tue, 05 Jun 2018 07:06:01 GMT):
What should be the query for fetching whole data of a channel, in couchDB?

joe-alewine (Tue, 05 Jun 2018 13:17:50 GMT):
@hrt031293 What do you mean, "whole data"? When a peer joins, it will get the ledger --- which includes channel config information --- either from the leading peer in its own organization or from the ordering service on that channel. The peers also communicate with each other via gossip Here are the peer channel commands: https://hyperledger-fabric.readthedocs.io/en/master/commands/peerchannel.html

MarcelvandeKerkhof (Tue, 12 Jun 2018 10:15:33 GMT):
Has joined the channel.

rickr (Tue, 12 Jun 2018 13:58:43 GMT):
Is there any documentation for the Private data aka side db aka collections FAB-1151 ?

Ammu (Tue, 12 Jun 2018 15:06:50 GMT):
curl -sSL https://goo.gl/6wtTN5 | bash -s 1.1.0 . In this command what is the meaning of -sSL?

cbf (Tue, 12 Jun 2018 20:41:53 GMT):
the 's' is silent, the 'S' is show error, the 'L' says follow a redirect https://curl.haxx.se/docs/manpage.html

rickr (Wed, 13 Jun 2018 12:35:36 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=khyYnGthgBAuSkEHL) No _user oriented_ documentation for this ?

joe-alewine (Wed, 13 Jun 2018 13:29:25 GMT):
We have three separate docs on Private Data in review right now: A lower level "architecture" doc: https://gerrit.hyperledger.org/r/c/22817/

joe-alewine (Wed, 13 Jun 2018 13:29:25 GMT):
We have three separate docs on Private Data in review right now: A high level "key concepts" doc: https://gerrit.hyperledger.org/r/#/c/22505/ A lower level "architecture" doc: https://gerrit.hyperledger.org/r/c/22817/ And a tutorial: https://gerrit.hyperledger.org/r/#/c/22357/

rickr (Wed, 13 Jun 2018 13:33:00 GMT):
Thanks Joe -- Will these make it to the Fabric's `hyperledger-fabric.readthedocs.io` ?

joe-alewine (Wed, 13 Jun 2018 13:34:26 GMT):
@rickr Yep. As things get merged they become available in the `master` or `latest` branch, which will become the `release-1.2` branch when we release

joe-alewine (Wed, 13 Jun 2018 13:35:04 GMT):
None of the private data docs have been merged yet, but the concept and architecture docs will get merged, at a minimum

rickr (Wed, 13 Jun 2018 13:36:19 GMT):
Great -- The reason for asking is the SDKs probably want to reference that in their release notes.

joe-alewine (Wed, 13 Jun 2018 13:39:48 GMT):
Gotcha, yeah. You'll want to reference the `release-1.2` branch, as that will be stable to that release. So something like: http://hyperledger-fabric.readthedocs.io/en/release-1.2/private-data/private-data.html (for the concept doc)

Dark_Knight (Thu, 21 Jun 2018 23:37:36 GMT):
Hello everyone, when a new organization or rather a peer is added to the channel, who specifies the ledger and which ledger is used for this new peer?

mbwhite (Fri, 22 Jun 2018 08:42:54 GMT):
Hi - q: is there a draft of the 1.2 docks for SDKs and Chaincode APIs available on line at all?

Dark_Knight (Tue, 26 Jun 2018 11:20:45 GMT):
Hello Everyone, I was reading the documents for Hyperledger fabric to add a new organization and a peer to the network. I could not get the answer as which peer ledger from the same channel will be used for this new joining peer and where is it specified which ledger to use? Also, how to make sure that the batching process in Ordering service is deterministic? Any help will be greatly appreciated.

joe-alewine (Tue, 26 Jun 2018 13:07:11 GMT):
@Dark_Knight Every peer on a channel maintains the ledger for that channel. These ledgers are all the same. So logically, you can think of there as being a channel ledger, which is maintained by every peer on the channel

Dark_Knight (Tue, 26 Jun 2018 13:10:55 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=k2SAuPL2hKG27LKYA) @joe-alewine but when adding a new peer don't we have to specify which ledger peer from the existing ones will be used for the new peer or is it randomly selected(assuming that no peer tampers with the local ledger and it is the same)

Dark_Knight (Tue, 26 Jun 2018 13:10:55 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=k2SAuPL2hKG27LKYA) @joe-alewine but when adding a new peer don't we have to specify which peer's ledger from the existing ones will be used for the new peer or is it randomly selected(assuming that no peer tampers with the local ledger and it is the same)

joe-alewine (Tue, 26 Jun 2018 13:13:26 GMT):
A peer is joined to a channel and that channel has a ledger, so there's no specification needed

Dark_Knight (Tue, 26 Jun 2018 13:19:47 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=WsGLQs2GyTjQ5KNZq) @joe-alewine Thanks for your reply. Can I also say then that it is the channel property that does not allow for a peer to tamper with its local ledger (since it will make the channel ledger inconsistent) and hence, same ledger is maintained on all the peers

joe-alewine (Tue, 26 Jun 2018 13:23:52 GMT):
@Dark_Knight That's a reasonable way to say it, sure. It is, however, possible to tamper with the ledger. It's just that, because of the way transactions are sequenced (each block contains a hash of the block before it), such tampering is rendered obvious. As a practical matter, all of the peers on a channel are *ordered* to write certain transactions in a certain order and a certain way on their ledger. That's how consistency is maintained across a channel

Dark_Knight (Tue, 26 Jun 2018 13:27:36 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=wFRWafurjuWYsRhF9) @joe-alewine Than you for your reply. That makes sense,I will do a litle more research on this :)

joe-alewine (Tue, 26 Jun 2018 13:28:26 GMT):
You're welcome. Check out the conceptual documentation on "peers" and the "ledger" here: https://hyperledger-fabric.readthedocs.io/en/master/key_concepts.html

joe-alewine (Tue, 26 Jun 2018 13:28:26 GMT):
@Dark_Knight You're welcome. Check out the conceptual documentation on "peers" and the "ledger" here: https://hyperledger-fabric.readthedocs.io/en/master/key_concepts.html

Dark_Knight (Tue, 26 Jun 2018 13:30:09 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=dLQnSkwctfN5YNyFM) @joe-alewine Sure will do that. Thanks

jwagantall (Thu, 28 Jun 2018 22:39:51 GMT):
User User_1 added by jwagantall.

SjirNijssen (Fri, 06 Jul 2018 15:21:32 GMT):
Why does in the docs of v1.2 (Operations Guide, section 5.2.2) Org3 have no anchor peer?

cbf (Tue, 10 Jul 2018 12:44:13 GMT):
it isn't required to have one. I guess that could be made clearer.

SjirNijssen (Tue, 10 Jul 2018 16:31:05 GMT):
Thanks Chris; but then the Glossary item Anchor peer needs correction (It currently says: ...should identify at least one of its peers as an anchor peer ...)

joe-alewine (Tue, 10 Jul 2018 17:15:04 GMT):
"Should" is reasonable, since you should. But it isn't *required*

joe-alewine (Tue, 10 Jul 2018 17:15:04 GMT):
"Should" is reasonable, since you should specify one. But it isn't *required*

SjirNijssen (Tue, 10 Jul 2018 17:37:22 GMT):
@joe-alewine Thanks Joe for the additional explanation. My recommendation for any Glossary is clarity as a service to the reader, above subtility.

Dark_Knight (Tue, 10 Jul 2018 22:17:14 GMT):
Hi everyone. Can someone please tell me how can we change the schema of the data model for the world state. Which file specifically have to be changed to modify the schema. For e.g. I want to have a schema as {'PersonName', 'VoteCount'}. So which file have to be modified?

Asch (Wed, 11 Jul 2018 10:43:02 GMT):
Hey guys, I am new to hyperledger fabric and wanted to know something. Let's say our organization uses hyperledger fabric to develop an application that interacts with other organizations and transactions happen between them using our app. So, my question is, will other organizations dealing with our organization need to install hyperledger fabric on their own network, or will our organization will be making channels and deploying chaincodes on these channels and updating ledgers.

jayeshjawale95 (Fri, 13 Jul 2018 12:20:41 GMT):
Hey Guys, can anyone help me without kafka setup, can't understand this step Orderers: Point each OSN to the genesis block. Edit General.GenesisFile in orderer.yaml so that it points to the genesis block created in Step 5 above. (While at it, ensure all other keys in that YAML file are set appropriately.)

jayeshjawale95 (Fri, 13 Jul 2018 12:20:41 GMT):
Hey Guys, can anyone help me with kafka setup, can't understand this step Orderers: Point each OSN to the genesis block. Edit General.GenesisFile in orderer.yaml so that it points to the genesis block created in Step 5 above. (While at it, ensure all other keys in that YAML file are set appropriately.)

jayeshjawale95 (Fri, 13 Jul 2018 12:20:41 GMT):
Hey Guys, can anyone help me with kafka setup, can't understand this step step 7 Orderers: Point each OSN to the genesis block. Edit General.GenesisFile in orderer.yaml so that it points to the genesis block created in Step 5 above. (While at it, ensure all other keys in that YAML file are set appropriately.) http://hyperledger-fabric.readthedocs.io/en/release-1.1/kafka.html

joe-alewine (Sun, 15 Jul 2018 19:28:57 GMT):
@jayeshjawale95 That's a better question for #fabric-questions or #fabric-orderer

qsmen (Wed, 18 Jul 2018 02:31:50 GMT):
several typical networks are given in the link https://hyperledger-fabric.readthedocs.io/en/release-1.2/network/network.html. If the corresponding config.yaml are given, it would be greater.

cagdasozt (Wed, 18 Jul 2018 17:05:33 GMT):
hey all I have a small question what is asset ? should say it like a variable ? for example, we can define integer or string parameter in java can we say same thing for hyperledger composer ? I am new in this area sorry for my stupid question

pandrejko (Thu, 19 Jul 2018 13:00:36 GMT):
@cagdasozt - There's some high level information around assets here: https://hyperledger-fabric.readthedocs.io/en/latest/fabric_model.html?highlight=asset to get you started.

SjirNijssen (Thu, 19 Jul 2018 13:23:07 GMT):
@cagdasozt @pandrejko I would like to add that the concept of state in Fabric is, in my opinion, much broader that only describing the state of monetary assets. For ease of understanding it may be used but Fabric is, happily, not restricted to monetary assets.

qsmen (Fri, 20 Jul 2018 02:09:21 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=AzEGXwfoDusPY74Na) the link above describes the dynamic expansion of a network. However, the whole 1.2 release doc does not describe how to implement the procedures. It would be very helpful if such description be provided.

qsmen (Fri, 20 Jul 2018 02:09:21 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=AzEGXwfoDusPY74Na) the link describes the dynamic expansion of a network. However, the whole 1.2 release doc does not describe how to implement the procedures. It would be very helpful if such description be provided.

qsmen (Fri, 20 Jul 2018 03:14:54 GMT):
THough they are not given explicitly, most of them are given implicitely except adding a new channel to an existing network. any idea about adding a new channel? Thank you.

StefanKosc (Wed, 25 Jul 2018 14:07:47 GMT):
Hi guys, I am investigating how identities work in fabric-ca sample and I have some doubts. in setup-fabric.sh function `registerPeerIdentities` in line 75 users are registered for all peer orgs and when switching to user identity using function `switchToUserIdentity` from env.sh line 263 I see `FABRIC_CA_CLIENT_HOME=/etc/hyperledger/fabric/orgs/$ORG/user`. My question is how user data got there? What distinguished them during registration from admin so they are exactly in that directory? Thanks in advance

dave.enyeart (Fri, 03 Aug 2018 12:35:10 GMT):
@pandrejko @joe-alewine @wlahti @jyellick I think there is general confusion about the various permission configurations in Fabric. I've created https://jira.hyperledger.org/browse/FAB-11461 and indicated what I think needs to be improved. Please add your thoughts there. Any chance some progress could be made in v1.3 timeframe? In the Jira I point to an open stack overflow question that highlights the confusion... I was going to try to answer by pointing to some doc pages but I could not find very direct answers in the docs.

jmason900 (Fri, 03 Aug 2018 15:08:32 GMT):
@joe-alewine - do you have the link to the meeting today ?? thanks Jim

joe-alewine (Fri, 03 Aug 2018 16:42:29 GMT):
@jmason900 I wasn't recording it. @odowdaibm should have it

jmason900 (Fri, 03 Aug 2018 16:43:20 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=cMnY5wqKrREscmJhP) @joe-alewine I was able to find the email with the zoom link - thanks..

joe-alewine (Fri, 03 Aug 2018 16:44:39 GMT):
Oh, the link to the meeting lol. Thought you were asking for the recording

rameshthoomu (Thu, 09 Aug 2018 19:26:50 GMT):
@joe-alewine @pandrejko updated comment in https://jira.hyperledger.org/browse/FAB-11441

Ammu (Mon, 13 Aug 2018 06:39:57 GMT):
Low latency of transaction confirmation . What is the meaning of this sentence?

qsmen (Tue, 14 Aug 2018 08:50:52 GMT):
hi,expert and moderator, I think the following link should be rewritten because of incorrect content. https://hyperledger-fabric.readthedocs.io/en/release-1.2/chaincode4noah.html#

qsmen (Tue, 14 Aug 2018 08:51:28 GMT):
in its present form, it wastes people time

joe-alewine (Tue, 14 Aug 2018 13:14:12 GMT):
A note from the Read the Docs team: ```We wanted to make you aware that on Saturday August 18 at approximately 10:00am PDT (1:00pm EDT, 17:00 UTC), Read the Docs will be having a scheduled downtime of approximately 4 hours. During this time, we will be moving our service to our new home on Microsoft Azure. To ensure the stability and performance of our system, we are performing this upgrade during the weekend which is our period of lowest usage. During this maintenance window, documentation will still be serving but new documentation builds will not trigger and the Read the Docs dashboard will not be available. New builds and webhooks will begin processing once the maintenance is over. For more details, see our blog post: https://urldefense.proofpoint.com/v2/url?u=https-3A__blog.readthedocs.com_azure-2Dmigration_&d=DwICAA&c=jf_iaSHvJObTbx-siA1ZOg&r=g2TmmAGPlDZEnJj18lhpjA&m=UgRn7TkWbHJG7hu-WPgjGkMtFEp5p6f260wnOsx5Rt4&s=od-YiRJAoGfiAqwQkgTElMUs8In1B1MxraLxV6rj2sM&e= ```

joe-alewine (Tue, 14 Aug 2018 13:15:01 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=nZ38ABAuNi3CaYAgW) @qsmen Can you be more specific?

qsmen (Wed, 15 Aug 2018 01:51:54 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=qTjfYFGbpm6gzsT2M) @joe-alewine Hi, Joe. Here is one about upgrade chaincode. According to sourcecode, the policy to upgrade a chaincode must be consistent to not only the existing chaincode’s instantiate policy, but also to the new chaincode’s instantiate policy. But the doc say only considering the existing chaincode's policy. Thanks.

qsmen (Wed, 15 Aug 2018 03:00:31 GMT):
another one: I run "peer chaincode package -n mycc .... " without -i option. According to release 1.2 doc, any org admin of the channel can run "peer chaincode instantiate -n sacc -v 1.0 -c '{"Args":["john","0"]}' -P "AND ('Org1.member','Org2.member' ....". However, the fact is that only the admin who package the chaincode can instanticate the chaincode.

qsmen (Wed, 15 Aug 2018 03:05:44 GMT):
and several unexpecte results because of our unproper understanding to the doc. in other words, the doc is not easy to understand.

SjirNijssen (Fri, 17 Aug 2018 11:21:23 GMT):
I propose to make a point in the documentation that with Fabric we have another step in the IT job specialization, namely all the UI sits in the Client Application and none of the UI in the Smart Contract. I look forward to comments.

jmason900 (Fri, 17 Aug 2018 16:12:15 GMT):
@joe-alewine good point that the topics is developing apps and should be focused on that without covering the world. I would "steal" all these items and wrap it into a case study project idea which is not the same at all

pandrejko (Fri, 17 Aug 2018 16:42:55 GMT):
@jmason900 As requested in the Documentation workgroup call this morning here is a link to all of the documentation work items in the backlog in jira https://jira.hyperledger.org/secure/RapidBoard.jspa?rapidView=119&view=planning.

jmason900 (Fri, 17 Aug 2018 17:15:01 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=6CGxtNwpmZAmiYuN2) @pandrejko Thank you !

jmason900 (Sat, 18 Aug 2018 15:19:51 GMT):
Here's the JIRA ticket to add image maps to RST files and Sphinx generation - https://jira.hyperledger.org/browse/FAB-11649

qsmen (Tue, 21 Aug 2018 05:50:12 GMT):
Hi expers here, In fabric doc 1.2, when packaging a chaincode, an instantiate policy can be dfined. especailly it is pointed out that instantiation policy can be defined as endorsement policies. Now my question is how to construct a proposal with an instantiatiion policy that need two signatures? and from the sourcecode analysis, this may be wrong again. only one creator is used in defining instantiation policy.

pandrejko (Tue, 21 Aug 2018 21:26:52 GMT):
@qsmen Did you see this information https://hyperledger-fabric.readthedocs.io/en/latest/endorsement-policies.html?highlight=endorsement%20policy#specifying-endorsement-policies-for-a-chaincode ```This command deploys chaincode mycc with the policy AND('Org1.member', 'Org2.member') which would require that a member of both Org1 and Org2 sign the transaction.```

qsmen (Wed, 22 Aug 2018 00:55:47 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=9xeGt9gJ6x5wZgux4) @pandrejko yes, I just read the link. However, I think instantication policy is different from endorsing policy. for endorsing policy, and policy is allowed.

AdityaV (Thu, 23 Aug 2018 06:17:48 GMT):
Hi I need to propose a change, how to create an issue? can someone suggest me the process ? Thanks :smile:

AdityaV (Thu, 23 Aug 2018 06:17:48 GMT):
Hi All I need to propose a change, how to create an issue? can someone suggest me the process ? Thanks :smile:

pandrejko (Thu, 23 Aug 2018 13:16:44 GMT):
@AdityaV Did you see this content" https://hyperledger-fabric.readthedocs.io/en/latest/CONTRIBUTING.html#making-feature-enhancement-proposals . In Jira click the `Create` button to open a new issue.

pandrejko (Thu, 23 Aug 2018 13:16:44 GMT):
@AdityaV Did you see this content: https://hyperledger-fabric.readthedocs.io/en/latest/CONTRIBUTING.html#making-feature-enhancement-proposals . In Jira click the `Create` button to open a new issue.

dave.enyeart (Thu, 30 Aug 2018 15:05:03 GMT):
@pandrejko @joe-alewine I've created a doc task that I think is important, and likely small if we just point to the existing reference info: https://jira.hyperledger.org/browse/FAB-11804

joe-alewine (Thu, 30 Aug 2018 15:34:51 GMT):
@dave.enyeart As I put in the jira, feels like the best place for this would be the Access Control doc https://hyperledger-fabric.readthedocs.io/en/release-1.2/access_control.html. Agreed?

dave.enyeart (Thu, 30 Aug 2018 16:25:27 GMT):
@joe-alewine That access control topic deals with access to functions on a channel and is more of an administrative thing, therefore that topic makes sense in the operations guide. The newly proposed topic deals with access control within chaincode logic, in fact at the key/value level, which is a very different thing. Unfortunately I don't think we have a good topic on chaincode to put this in, beyond the chaincode tutorial https://hyperledger-fabric.readthedocs.io/en/release-1.2/chaincode4ade.html. So perhaps for now mention it in the chaincode tutorial as another set of APIs available to chaincode authors, and link to the client identity library readme similar to how we link to the core chaincode api interface. And in https://hyperledger-fabric.readthedocs.io/en/release-1.2/access_control.html you can simply put a notice that for access control within chaincode, see the chaincode tutorial topic that describes it.

PradeepC (Fri, 31 Aug 2018 14:44:41 GMT):
hello group, i am new to this fabric eco system. can some one point me to architecture flow of things on how each component(like nodes) in the fabric what role it plays.

PradeepC (Fri, 31 Aug 2018 14:45:08 GMT):
and in the same light can i develop chain code in python

parsiya (Fri, 31 Aug 2018 15:17:46 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=pBQKNy5nY4YBbkK5F) @PradeepC You cannot develop chaincode in Python yet. Currently, only Go and Node.js are supported. Java is in the works and there's an experimental shim for .NET around.

PradeepC (Fri, 31 Aug 2018 15:29:06 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=eAvz6Ku7Ck5A7Hcyo) @parsiya thanks for the feedback. another follow up question to that is are there any tool kits that help with the Go or Node.js. or we have write them from scratch

parsiya (Fri, 31 Aug 2018 15:34:34 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=MrZauoj7WedjxTaBg) @PradeepC I am going to answer you in #fabric-chaincode-dev, this is the documentation channel.

jmason900 (Thu, 06 Sep 2018 04:12:38 GMT):
Developing_applications.html -- does anyone have a valid link for this document ?? ( this url is broken ( temporary ) -- vex-yul-hyp-jenkins-3/fabric-docs-build-x86_64/706/html/developing_applications.html ) -- thanks

sheetal-hlf (Thu, 06 Sep 2018 05:12:46 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=XsLkWYWpSEANXqkF3) @jmason900 the link is accessible ..

sheetal-hlf (Thu, 06 Sep 2018 06:13:55 GMT):
@odowdaibm is there any plan for documentation review meeting tomorrow?

jmason900 (Thu, 06 Sep 2018 11:13:29 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=7nmP2Dd3DQBxKcEeZ) @sheetal-hlf I can't even get a route to this url . is this an internal address only? is there a different external link? thanks -- https://vex-yul-hyp-jenkins-3/fabric-docs-build-x86_64/706/html/developing_applications.html

jmason900 (Thu, 06 Sep 2018 11:13:29 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=7nmP2Dd3DQBxKcEeZ) @sheetal-hlf I can't even get a route to this url . is this an internal address only? is there a different external link? thanks -- "https://vex-yul-hyp-jenkins-3/fabric-docs-build-x86_64/706/html/developing_applications.html"

sheetal-hlf (Thu, 06 Sep 2018 11:18:43 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=SXmLqkQQvfK8YoXNw) @jmason900 the url is https://logs.hyperledger.org/production/vex-yul-hyp-jenkins-3/fabric-docs-build-x86_64/706/html/developapps/scenario.html

joe-alewine (Thu, 06 Sep 2018 13:53:59 GMT):
@jmason900 The doc build only lasts until there's a subsequent patch set, I believe. So you might have to find the latest build

jmason900 (Thu, 06 Sep 2018 17:17:58 GMT):
if I follow the docs for master on pre-reqs and install is that the correct set to find and install the v1.3 docker images to run v1.3 test version now?

jmason900 (Thu, 06 Sep 2018 17:25:26 GMT):
I don't have anything I can use as a release id for v1.3-rc1 on github ( https://github.com/hyperledger/fabric/releases ). are there any docs on how to setup a v1.3 test environment for the v1.3 sample apps?

scottz (Thu, 06 Sep 2018 20:59:27 GMT):
v1.3 does not exist yet. This is the closest thing. https://github.com/hyperledger/fabric/tree/master

jmason900 (Fri, 07 Sep 2018 15:30:25 GMT):
in app-dev topic - this line "– when it expects to see cash flow from Daintree. DigiBank thinks that MagnetoCorp is creditworthy, and therefore doesn’t require much a premium above the central bank base rate of 2%, which would value " needs to add "of" after require much

ArianStef (Sat, 08 Sep 2018 18:59:57 GMT):
Hi team! Do you know where I can find good documentation about set-up distributed system of peer nodes in different machines? Thank you

Ryan2 (Sun, 09 Sep 2018 09:42:15 GMT):
https://hyperledger-fabric.readthedocs.io/en/latest/ledger/ledger.html#transactions I'm reading this section , but don't really understand below part, Can someone explain. `That’s because each endorsement effectively encodes its organization’s particular transaction response – meaning that there’s no need to include any transaction response that doesn’t match sufficient endorsements as it will be rejected as invalid, and not update the world state.`

mastersingh24 (Mon, 10 Sep 2018 19:34:34 GMT):
@Ryan2 - Endorsers each sign the proposal response they send back to the client ... so when the client packages up the transaction to send to the orderer, it only needs to include a single endorsement response and enough endorsements to meet the policy. An endorsement is really just a signature over the proposal response ... so essentially you end up with the endorsement proposal and enough detached signature (endorsements) to meet the policy. All peers which endorse will generate identical proposal responses ... therefore it need only be included once in the transaction sent to the orderer. Endorsements are checked by verifying the signature. The signature is created by signing the hash of the proposal response.

nithindj192 (Tue, 11 Sep 2018 06:20:20 GMT):
Here is an attempt to provide the complete instructions to adapt Caliper to existing Fabric network - https://medium.com/tallyx/adapting-hyperledger-caliper-to-custom-hyperledger-fabric-networks-3ffa650215a0

ArianStef (Tue, 11 Sep 2018 11:04:34 GMT):
Hi! Can anyone know where to find some material about how to distribuite an ordering service across the network? If the best choise is have just one organization for the ordering service or distribute it across multiple organization.

rickr (Wed, 12 Sep 2018 16:22:55 GMT):
@joe-alewine @pandrejko @Maria I'd like to in the JSDK reference Idemix concepts. As each SDK should not have to reproduce that. Is it known now the _link_ I can use for that ?

joe-alewine (Wed, 12 Sep 2018 16:43:19 GMT):
There are idemix docs currently merged but not in the TOC that look like they will get replaced. Hard to tell by what (or how many docs)

raviyelleni (Tue, 18 Sep 2018 03:09:55 GMT):
Nodejs document link in chaincode for developers is broken ......https://fabric-shim.github.io/ChaincodeInterface.html

joe-alewine (Tue, 18 Sep 2018 12:57:01 GMT):
@raviyelleni We're currently working on this: https://gerrit.hyperledger.org/r/c/26355/

Shyam_Pratap_Singh (Thu, 20 Sep 2018 06:27:10 GMT):
Has joined the channel.

halilkalkan (Fri, 21 Sep 2018 07:55:41 GMT):
Hi guys, I have noticed a mistake in fabric documentation, release 1.2. I want to inform you about that, https://hyperledger-fabric.readthedocs.io/en/release-1.2/private_data_tutorial.html under Store Private Data, export PEER0_ORG1_CA=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/peers/peer0.org1.example.com/tls/ca.crt have a mistake, it should take ca.crt from org1.example.com but it was written as org2.example.com. Have a nice day,

dave.enyeart (Fri, 21 Sep 2018 10:02:23 GMT):
@pandrejko ^^^^^^^^ Do you want to open a doc defect?

pandrejko (Fri, 21 Sep 2018 12:57:39 GMT):
@halilkalkan I opened https://jira.hyperledger.org/browse/FAB-12093 and will address this

halilkalkan (Fri, 21 Sep 2018 13:01:06 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=xegFhoz7jJjCnXmt8) @pandrejko Okey, thanks :v:

rickr (Fri, 21 Sep 2018 16:14:00 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=WHN2Z7Rku8qkay97R) Any updates ?

rickr (Fri, 21 Sep 2018 16:14:00 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=WHN2Z7Rku8qkay97R) Any updates ? Looking for a link in read the docs for idemix that the SDKs can reference

pandrejko (Fri, 21 Sep 2018 16:31:12 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=YabWrSkEgrx2XF25D) @halilkalkan Could you take a look at https://gerrit.hyperledger.org/r/#/c/26459/ to make sure I got it correctly?

joe-alewine (Fri, 21 Sep 2018 17:28:36 GMT):
@rickr Here's the main doc on Idemix. Ended up being the same file name that we already had out there: https://hyperledger-fabric.readthedocs.io/en/master/idemix.html A doc about the Idemixgen tool can be found here: https://hyperledger-fabric.readthedocs.io/en/master/idemixgen.html

joe-alewine (Fri, 21 Sep 2018 17:29:08 GMT):
Feel free to switch these to https://hyperledger-fabric.readthedocs.io/en/release-1.3/idemix.html when the release is cut

halilkalkan (Mon, 24 Sep 2018 05:42:28 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=xiNewhgZury2JBqJE) @pandrejko Yep, it looks correct.

Ryan2 (Tue, 25 Sep 2018 13:41:44 GMT):
Hi, on this document, https://hyperledger-fabric.readthedocs.io/en/latest/endorsement-policies.html#endorsement-policy-syntax stated that ` ROLE represents one of the four accepted roles: member, admin, client, and peer.` `'Org0.admin': any administrator of the Org0 MSP 'Org1.member': any member of the Org1 MSP 'Org1.client': any client of the Org1 MSP 'Org1.peer': any peer of the Org1 MSP` Can I ask, orderer will be `member` role or `peer` role, Thanks

joe-alewine (Tue, 25 Sep 2018 14:18:49 GMT):
@Ryan2 Orderers are also technically "orgs", so the same rules apply (though they won't have clients or peers --- at least I wouldn't think so!)

Ryan2 (Tue, 25 Sep 2018 14:35:53 GMT):
so when I generate crypto material for orderer nodes, I will assign `member` role for those node? is that true (due to you said that orderer doese have clients or peers ?)

akshay.sood (Fri, 28 Sep 2018 06:22:24 GMT):
I was going through the documentation of ‘idemixgen’ but could not understand its usage

akshay.sood (Fri, 28 Sep 2018 06:22:47 GMT):
Does anyone know anything about idemixgen? Like use case or just example?

akshay.sood (Fri, 28 Sep 2018 06:23:25 GMT):
Why we need identity mixer? Where it can be used

joe-alewine (Fri, 28 Sep 2018 13:23:26 GMT):
Hey @akshay.sood, try reading the "Idemix" doc first: https://hyperledger-fabric.readthedocs.io/en/release-1.3/idemix.html

joe-alewine (Fri, 28 Sep 2018 13:24:01 GMT):
Idemixgen is a tool for development environments

bairathirahul (Sun, 30 Sep 2018 17:54:05 GMT):
@akshay.sood Like in Bitcoin, the real identity of the user is not shared, Idemixgen is used to mask the identity. The proof that will be provided to the peers will only indicate that you are authenticated and you have the required permissions to execute the chaincode. The peer will not be able to determine your personal information like Name, Email, etc. which are present in your identity certificate.

atcvince (Sun, 30 Sep 2018 20:23:21 GMT):
Is it a fair statement to say that cryptogen is to certs as idemixgen is to credentials?

joe-alewine (Sun, 30 Sep 2018 21:03:58 GMT):
@atcvince I think so, yes. Though you'd want to ask the CA people to clarify

atcvince (Sun, 30 Sep 2018 22:44:58 GMT):
Thanks @joe-alewine @joe-alewine [ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=4vjQYaKZWETWhKqoF)

atcvince (Sun, 30 Sep 2018 22:44:58 GMT):
Thanks @joe-alewine [ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=4vjQYaKZWETWhKqoF)

akshay.sood (Mon, 01 Oct 2018 04:57:16 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=79Zwm5ZKfE32sjtLF) Thanks for detailed reply @bairathirahul. Can you provide a real case? other than bitcoin?

bairathirahul (Mon, 01 Oct 2018 14:18:42 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=dS7yQyBRccT6Y85Cm) @akshay.sood For e.g. you don't want your employee's information to be shared with peers from other companies. Those peers might store this information with them.

joe-alewine (Mon, 01 Oct 2018 16:57:48 GMT):
@bairathirahul @akshay.sood To clarify, idemixgen is used for development environments. It's not for production, where you'll want to use a CA and do proper enrolls

bairathirahul (Mon, 01 Oct 2018 17:23:01 GMT):
@joe-alewine Yes. Thanks for bringing that up. To add to that, even with the latest version of Fabric CA, we can generate Idemix credentials.

pvrbharg (Wed, 03 Oct 2018 19:01:56 GMT):
I am working on an effort to setup a customized use case that mimics fabric-samples/balance-transfer in release v1.1.0 - that features fabric-ca-server/client with fabric-sdk-node programming model. The sample works great. When I customize the sample with my PoC use case [4 orgs, 4 CAs, 1 orderer with customized crypto and domain names] - all is well and network comes up with with express webserver. However user registration for each org fails and this is because the fabric-ca-client-kv* contents are not created in the root sample folder or their backing storage defined in yaml files for each org [/tmp]. This only happens with customized network and crypto but not our-of-box sample. Sample works even if the fabric-ca-client-kv* contents are deleted and re-run. So do I have to do anything specific that I am not doing - in terms of missed step? We may have an opportunity to improve documentation or do we have a documentation defect here - potentially? Current I am blocked on this issue - how do I get the fabric-ca-client-kv* contents created to succeed with my PoC and what steps do I need to perform? Can you please guide me and tell me if this question needs to be posted elsewhere or an issue created? Thank you

paul.sitoh (Thu, 04 Oct 2018 07:46:54 GMT):
Folks, considering the pivotal role channel configuration plays in the orchestration of a Fabric network, there seemed to be a lack of documentation. The only one is this https://hyperledger-fabric.readthedocs.io/en/release-1.2/configtx.html, which is so focused on protobuf which is find for configtx developer. May I suggest that there be a section explaining the overall architecture of a channel, and another section on how it relates to say configtx.yaml, and a section on tools (configtxgen) and maybe the detail source architecture for dev all under one category call channel configuration. Main thing is separate the concerns of operations from developers.

paul.sitoh (Thu, 04 Oct 2018 07:48:19 GMT):
This is especially so if Hyperledger is to start certification and the lack of documentation is going make potential candidates feel that certification process is, too put it crude term, a money making scam rather than a way of certifying knowledge!

bairathirahul (Thu, 04 Oct 2018 12:42:34 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=Bsv9jkFgQBQ5f6XQN) @paul.sitoh +1 to this

joe-alewine (Thu, 04 Oct 2018 15:13:19 GMT):
@paul.sitoh @bairathirahul Have you guys seen these: https://hyperledger-fabric.readthedocs.io/en/release-1.2/config_update.html And a tutorial on updating a channel: https://hyperledger-fabric.readthedocs.io/en/release-1.2/channel_update_tutorial.html We have a section in our peers doc as it relates to channels: https://hyperledger-fabric.readthedocs.io/en/release-1.2/peers/peers.html#peers-and-channels

joe-alewine (Thu, 04 Oct 2018 15:13:19 GMT):
@paul.sitoh @bairathirahul Have you guys seen these? A doc on channels and channel updates generally (and the things you can update): https://hyperledger-fabric.readthedocs.io/en/release-1.2/config_update.html And a tutorial on updating a channel: https://hyperledger-fabric.readthedocs.io/en/release-1.2/channel_update_tutorial.html We have a section in our peers doc as it relates to channels: https://hyperledger-fabric.readthedocs.io/en/release-1.2/peers/peers.html#peers-and-channels

paul.sitoh (Thu, 04 Oct 2018 15:55:53 GMT):
@joe-alewine yes but it is unclear to whom the topic is aimed at. Operators or Dev. It talks about protobuf and does operator need to know that?

paul.sitoh (Thu, 04 Oct 2018 15:55:53 GMT):
@joe-alewine yes but it is unclear to whom the topic is aimed at. Operators or Dev. It talks about protobuf and does operator need to know that? Even as dev it could be hard push to tell what it is about.

paul.sitoh (Thu, 04 Oct 2018 15:56:32 GMT):
Imagine someone wanting to be hyperledger certified. Where would they start

paul.sitoh (Thu, 04 Oct 2018 15:57:10 GMT):
Or for that matter people who are setting exams for certification. Where is the definitive source of truth?

jmason900 (Thu, 04 Oct 2018 15:57:43 GMT):
I think the certification programs are only going to put more pressure on doc teams for better "role-based" navigation of content ( big time ) !

jmason900 (Thu, 04 Oct 2018 15:58:27 GMT):
a common content pile with many tags, hyperlinks, abstraction layers and multiple TOCs and indexes ?

paul.sitoh (Thu, 04 Oct 2018 16:02:23 GMT):
At the moment, to gain any knowledge of Fabric and its supporting tools such as configtxgen, I have to study the source code or run my own smoke tests to get a sense of how it is working.

joe-alewine (Thu, 04 Oct 2018 16:15:24 GMT):
Given the resources we have (both from the perspective of personnel and RTD), it's simply not practical for us to switch to role-based documentation. We don't have the time to write three or four times as much documentation, nor do we have a way to organize it in the TOC. The topics --- especially the newer topics --- are carefully written with a model of progressive disclosure (i.e., more general information first, followed by more granular information). The notion that someone would run the source code to figure out what configtxgen does is bizarre to me. There are at least a dozen references to configtxgen and what it does in the documentation.

joe-alewine (Thu, 04 Oct 2018 16:15:24 GMT):
Given the resources we have (both from the perspective of personnel and RTD), it's simply not practical for us to switch to role-based documentation at this time. We don't have the time to write three or four times as much documentation, nor do we have a way to organize it in the TOC. The topics --- especially the newer topics --- are carefully written with a model of progressive disclosure (i.e., more general information first, followed by more granular information). The notion that someone would run the source code to figure out what configtxgen does is bizarre to me. There are at least a dozen references to configtxgen and what it does in the documentation.

joe-alewine (Thu, 04 Oct 2018 16:15:24 GMT):
Given the resources we have (both from the perspective of personnel and RTD), it's simply not practical for us to switch to role-based documentation at this time. We don't have the time to write three or four times as much documentation, nor do we have a way to organize it in the TOC. The topics --- especially the newer topics --- are carefully written with a model of progressive disclosure (i.e., more general information first, followed by more granular information). We intend to continue along those lines. The notion that someone would run the source code to figure out what configtxgen does is bizarre to me. There are at least a dozen references to configtxgen and what it does in the documentation.

paul.sitoh (Thu, 04 Oct 2018 16:24:43 GMT):
@joe-alewine let's just say the documentation is not always align with what actually happens when things goes wrong!

paul.sitoh (Thu, 04 Oct 2018 16:25:05 GMT):
Configtxgen is only one example.

paul.sitoh (Thu, 04 Oct 2018 16:25:05 GMT):
Configtxgen is only one example of they myriad number of Fabric components

paul.sitoh (Thu, 04 Oct 2018 16:26:23 GMT):
All I am saying is that if Hyperledger wishes to have certification programme that don't smell like money raising effort. You have to have a source of truth that cannot be disputed.

paul.sitoh (Thu, 04 Oct 2018 16:26:23 GMT):
All I am saying is that if Hyperledger wishes to have certification programme that don't smell like money raising effort it is important to have sources of truth that cannot be disputed.

paul.sitoh (Thu, 04 Oct 2018 16:27:16 GMT):
I have sat certification exams that were testing stuff that were so out of date from the way the actual implementation works!

paul.sitoh (Thu, 04 Oct 2018 16:27:16 GMT):
I have sat certification exams that were verifying stuff that were so out of date from the way the actual implementation works!

paul.sitoh (Thu, 04 Oct 2018 16:27:16 GMT):
I have sat certification exams that were examining stuff that were so out of date from the way the actual implementation works!

paul.sitoh (Thu, 04 Oct 2018 16:29:42 GMT):
No fault of the doc team as I appreciate all are volunteers

joe-alewine (Thu, 04 Oct 2018 16:30:55 GMT):
I sympathize completely, and that sounds like a worthy point to take up with whoever is designing those courses (I don't work for Hyperledger, so I couldn't tell). I have no idea what is put into those courses or how the content for them is generated, beyond rumors that some of it is based on the Fabric docs

joe-alewine (Thu, 04 Oct 2018 16:30:55 GMT):
I sympathize completely, and that sounds like a worthy point to take up with whoever is designing those courses (I don't work for Hyperledger, so I couldn't tell you). I have no idea what is put into those courses or how the content for them is generated beyond rumors that some of it is based on the Fabric docs

joe-alewine (Thu, 04 Oct 2018 16:30:55 GMT):
I sympathize completely, and that sounds like a worthy point to take up with whoever is designing those courses (I don't work for Hyperledger, so I couldn't tell you). I have no idea what is put into those courses or how the content for them is generated beyond rumors that some of it is based on the Fabric docs/tutorials

paul.sitoh (Thu, 04 Oct 2018 16:32:27 GMT):
Here is an example, where some featured suddenly appeared: ```- &ExampleCom Name: ExampleCom ID: example.com AdminPrincipal: Role.ADMIN MSPDir: ./ordererOrganizations/example.com/msp Policies: Readers: Type: Signature Rule: "OR('example.com.member')" Writers: Type: Signature Rule: "OR('example.com.member')" Admins: Type: Signature Rule: "OR('example.com.admin')"```

paul.sitoh (Thu, 04 Oct 2018 16:32:27 GMT):
Here is an example, where I found some example yaml: ```- &ExampleCom Name: ExampleCom ID: example.com AdminPrincipal: Role.ADMIN MSPDir: ./ordererOrganizations/example.com/msp Policies: Readers: Type: Signature Rule: "OR('example.com.member')" Writers: Type: Signature Rule: "OR('example.com.member')" Admins: Type: Signature Rule: "OR('example.com.admin')"```

paul.sitoh (Thu, 04 Oct 2018 16:33:07 GMT):
I must admit I couldn't find any mention of what the RULES does

paul.sitoh (Thu, 04 Oct 2018 16:33:07 GMT):
I must admit I couldn't find any mention of what, for example, the RULES does

paul.sitoh (Thu, 04 Oct 2018 16:34:07 GMT):
Things are moving so fast I supposed it is not easy to keep up

joe-alewine (Thu, 04 Oct 2018 16:37:19 GMT):
``` Fabric uses access control lists (ACLs) to manage access to resources by associating a policy — which specifies a rule that evaluates to true or false, given a set of identities — with the resource. Fabric contains a number of default ACLs. In this document, we’ll talk about how they’re formatted and how the defaults can be overridden. ``` https://hyperledger-fabric.readthedocs.io/en/release-1.2/access_control.html

joe-alewine (Thu, 04 Oct 2018 16:38:26 GMT):
We are planning more extensive documentation on policies, but for now this should give you an overview

paul.sitoh (Fri, 05 Oct 2018 09:15:58 GMT):
@joe-alewine I guess, this might be a bit complex to explain in your documentation. But it might be useful when explaining ACL to distinguish between ACL as applied to a registered identity token (i.e. keys) that is associalted with an individual or ACL as applied to a peer (i.e. whoever has access to the peer is afforded the ACL and not restricted to individual). I don't know about you, ACL is a topic that often generates lots of confusion.

halilkalkan (Fri, 12 Oct 2018 06:39:48 GMT):
Hi guys, I have noticed a problem in Idemix Documentation. "For an example of using the cid library to retrieve these attributes, see this java SDK example." has a link and it's broken. The link for the page; https://hyperledger-fabric.readthedocs.io/en/release-1.3/idemix.html Have a nice day,

atirekg (Fri, 12 Oct 2018 12:04:48 GMT):
Guys, anyone have knowledge how to use this API https://fabric-sdk-node.github.io/AffiliationService.html

joe-alewine (Fri, 12 Oct 2018 14:08:05 GMT):
@halilkalkan The java-sdk hasn't released v1.3 quite yet. When it does, that link will work

joe-alewine (Fri, 12 Oct 2018 14:08:28 GMT):
@atirekg I'd check out the #fabric-sdk-node channel

qubing (Mon, 15 Oct 2018 06:59:25 GMT):
Hi all, I found a mistake in endorsement_policies.rst, and opened a issue to fix it. This is my first time to contribute in Hyperledger, and not familiar with the process. Any one can help me to review? Thank you very much. https://jira.hyperledger.org/browse/FAB-12453

sheetal-hlf (Wed, 17 Oct 2018 10:44:26 GMT):
Hi All, in Endorsement policies section(https://hyperledger-fabric.readthedocs.io/en/latest/endorsement-policies.html), four accepted roles: member, admin, client, and peer; are mentioned. I have used org "admin" to create channel, install/instantiate smart contract and "member" (dynamically added users via fabric-ca) to endorse the transactions. Could anyone please explain where and how the "client" and "peer" roles would be used?

joe-alewine (Wed, 17 Oct 2018 15:46:30 GMT):
The `client` role will often be used by an application (which shouldn't have a member, admin, or peer identity). The `peer` role is used when, for example, the peer signs something (such as an transaction proposal). You don't want your peer admin attaching their signature. You want the peer's signature

sheetal-hlf (Fri, 19 Oct 2018 10:23:37 GMT):
the transaction proposal is sent to the targets (peers) by the client which holds the member's identity; hence the member signs the transaction proposal

sheetal-hlf (Fri, 19 Oct 2018 10:24:17 GMT):
also we would like to know which member submitted the transaction for say auditing purpose

joe-alewine (Fri, 19 Oct 2018 12:35:05 GMT):
Any user attaches their signcert to any action (such as endorsing) which can be used to identify them (outside of an Idemix usage, obviously)

joe-alewine (Fri, 19 Oct 2018 12:35:05 GMT):
Any user/peer etc attaches their signcert to any action (such as endorsing) which can be used to identify them (outside of an Idemix usage, obviously)

nnao (Fri, 19 Oct 2018 17:44:00 GMT):
Hi all, I have a question about patch's title length. "Contributions Welcome! *" page mentions the patch title length is 50 or less. However, "Submitting a Change to Gerrit **" page mentions the length is 55 or less. Which is the correct length? * https://hyperledger-fabric.readthedocs.io/en/latest/CONTRIBUTING.html ** https://hyperledger-fabric.readthedocs.io/en/latest/Gerrit/changes.html

nnao (Fri, 19 Oct 2018 17:44:00 GMT):
Hi all, I have a question about patch's title length. "Contributions Welcome! 1)" page mentions the patch title length is 50 or less. However, "Submitting a Change to Gerrit 2)" page mentions the length is 55 or less. Which is the correct length? 1) https://hyperledger-fabric.readthedocs.io/en/latest/CONTRIBUTING.html 2) https://hyperledger-fabric.readthedocs.io/en/latest/Gerrit/changes.html

tijohnson (Fri, 19 Oct 2018 20:01:22 GMT):
https://chris.beams.io/posts/git-commit/ (50 chars wins by vote of 2-1)

paul.sitoh (Mon, 05 Nov 2018 14:22:23 GMT):
Hi this is the documentation related to Endorsement policy looks a bit confusing. You have example labelled with human names (i.e. Alice, Bob, Charlie, etc). Would it confuse people? It would give the impression that some human is responsible for endorsement?

jtclark (Wed, 07 Nov 2018 21:56:31 GMT):
@pandrejko - have you had a chance to review the latest updates to the doc build JIRAs ?

pandrejko (Thu, 08 Nov 2018 02:00:22 GMT):
@jtclark I responded to one of them - which one did I miss?

jtclark (Thu, 08 Nov 2018 02:27:25 GMT):
@pandrejko FAB-12677 (which you've commented on) and FABCI-27

jtclark (Thu, 08 Nov 2018 03:11:21 GMT):
@pandrejko replied to your comment on FAB-12677. JFYI.

enriquebusti (Thu, 08 Nov 2018 10:53:51 GMT):
hi everybody, in fabric, what's the real difference between solo and kafka?

odowdaibm (Thu, 08 Nov 2018 19:04:25 GMT):
Hi Guys, looking for some plus +2s on the following please. They really are very strightforward, and have been thorughly reviewed

odowdaibm (Thu, 08 Nov 2018 19:04:51 GMT):
https://gerrit.hyperledger.org/r/c/26306/

odowdaibm (Thu, 08 Nov 2018 19:05:18 GMT):
https://gerrit.hyperledger.org/r/c/26051/

odowdaibm (Thu, 08 Nov 2018 19:06:00 GMT):
@jtclark any suggestions for reviewers please?

odowdaibm (Thu, 08 Nov 2018 19:06:11 GMT):
I will also ask on maintainers channel of course

jtclark (Thu, 08 Nov 2018 22:15:27 GMT):
@odowdaibm I can only +1, but @rameshthoomu, @scottz, and @jwagantall can +2

rameshthoomu (Thu, 08 Nov 2018 22:40:26 GMT):
@odowdaibm pls post the same in #fabric-pr-review channel..

rameshthoomu (Thu, 08 Nov 2018 22:42:52 GMT):
We don’t have +2 permissions on fabric repo.. but that’s fine maintainers are very active in pr-preview channel.. pls post there

odowdaibm (Fri, 09 Nov 2018 15:45:59 GMT):
really appreciate the advice guys

AlexanderZhovnuvaty (Mon, 12 Nov 2018 11:05:49 GMT):
Has left the channel.

Ammu (Thu, 22 Nov 2018 13:28:24 GMT):
node registerUser.js Store path:/home/ubuntu/.hfc-key-store Successfully loaded admin from persistence Failed to register: Error: fabric-ca request register failed with errors [[{"code":20,"message":"Authentication failure"}]]

StefanKosc (Fri, 30 Nov 2018 08:57:51 GMT):
Hi, I have a general question about network design. Let's assume that I have one channel with two organisations in it. Is it possible that each of organisations hosts its own orderer?

joe-alewine (Fri, 30 Nov 2018 14:10:13 GMT):
@StefanKosc In a RAFT implementation, yes. But that's not something we have (yet), though it is in plan for v2.0

StefanKosc (Fri, 30 Nov 2018 14:21:47 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=RLDWN7hBnuvjoueWP) @joe-alewine Hi @joe-alewine, thanks for response, so if I would have kafka ordering service with 4 orderers they cannot be hosted by diferent organizations?

MattHamilton (Mon, 03 Dec 2018 13:43:00 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=ueBy6ZSNiNWJSHHJC) @StefanKosc Currently, the ordering service cluster would be hosted by a single organization. RAFT will bring the capability to distribute the nodes.

Pradeep_Pentakota (Wed, 05 Dec 2018 01:40:57 GMT):
Has joined the channel.

lehors (Tue, 11 Dec 2018 20:11:22 GMT):
@joe-alewine hi, I saw your reponse to my review - thank you for accepting my suggestions - but I'm confused about that one sentence: We can use the ``queryCar`` transaction to can query against any car, using its key (e.g. ``CAR0``) and get whatever make, model, color, and owner correspond to that car.

lehors (Tue, 11 Dec 2018 20:11:49 GMT):
what does it mean to "get [something] correspond to that car"??

lehors (Tue, 11 Dec 2018 20:12:18 GMT):
I must be missing something so I'm sorry I'm being dense but I can't sense of this sentence

lehors (Tue, 11 Dec 2018 20:12:18 GMT):
I must be missing something so I'm sorry I'm being dense but I can't make sense of this sentence

lehors (Tue, 11 Dec 2018 20:14:18 GMT):
isn't the intent to say it can be used to retrieve any attribute of the car?

lehors (Tue, 11 Dec 2018 20:14:18 GMT):
isn't the intent to say that queryCar can be used to retrieve any attribute of the car?

lehors (Tue, 11 Dec 2018 20:15:37 GMT):
ah, no, this is about selecting a car actually, isn't it?

joe-alewine (Tue, 11 Dec 2018 20:20:26 GMT):
`get whatever make, model, color, and owner correspond to that car` = values, as in a key/value pair

joe-alewine (Tue, 11 Dec 2018 20:20:26 GMT):
@lehors `whatever make, model, color, and owner correspond to that car` = values, as in a key/value pair

joe-alewine (Tue, 11 Dec 2018 20:21:25 GMT):
I suppose we could have made that more explicit, but it seemed clear enough

joe-alewine (Tue, 11 Dec 2018 20:22:13 GMT):
And with `queryCar` we're only querying a single key, as opposed to `queryAllCars` which queries a range

nickgaski (Wed, 12 Dec 2018 22:40:49 GMT):
@joe-alewine @pandrejko - in an effort to refresh my Fabric knowledge, I thought it would fun to run through BYFN manually. Everything was running smoothly until instantiate. I kept getting back `proposal responses do not match`. Good debug there, makes a lot of sense. But now I'm asking myself, how the heck can they not match. It's a trivial piece of chaincode using a/b for keys and ints for the value. The byfn script worked, so what is different here. Rather than start over I go to query `peer0.org2` and am greeted with ```Error: endorsement failure during query. response: status:500 message:"cannot retrieve package for chaincode mycc/1.0, error open /var/hyperledger/production/chaincodes/mycc.1.0: no such file or directory"```. And there's my problem, I never installed the chaincode on the second peer. My suggestion would be to explicitly inform the user to install the chaincode on the second Org's peer that is specified in the EP, immediately after instantiation, then tell them why. You do have this sentence ```If you want additional peers to interact with ledger, then you will need to join them to the channel, and install the same name, version and language of the chaincode source onto the appropriate peer’s filesystem``` , but do you really expect a user to interpret that as go export all the env variables for an Org2 peer and then install the cc because we just instantiated with a two party policy.

nickgaski (Wed, 12 Dec 2018 22:40:49 GMT):
@joe-alewine @pandrejko - in an effort to refresh my Fabric knowledge, I thought it would fun to run through BYFN manually. Everything was running smoothly until invoke. I kept getting back `proposal responses do not match`. Good debug there, makes a lot of sense. But now I'm asking myself, how the heck can they not match. It's a trivial piece of chaincode using a/b for keys and ints for the value. The byfn script worked, so what is different here. Rather than start over I go to query `peer0.org2` and am greeted with `Error: endorsement failure during query. response: status:500 message:"cannot retrieve package for chaincode mycc/1.0, error open /var/hyperledger/production/chaincodes/mycc.1.0: no such file or directory"`. And there's my problem, I never installed the chaincode on the second peer. My suggestion would be to explicitly inform the user to install the chaincode on the second Org's peer that is specified in the EP, immediately after instantiation, then tell them why. You do have this sentence ```If you want additional peers to interact with ledger, then you will need to join them to the channel, and install the same name, version and language of the chaincode source onto the appropriate peer’s filesystem``` , but do you really expect a user to interpret that as go export all the env variables for an Org2 peer and then install the cc because we just instantiated with a two party policy.

nickgaski (Wed, 12 Dec 2018 22:41:43 GMT):
very cool that CLI supports multi-party endorsement now.

pandrejko (Thu, 13 Dec 2018 21:03:32 GMT):
Hey Thanks @nickgaski for posting that here. We need to get that addressed!! I just noticed that this jira was created in Aug https://jira.hyperledger.org/browse/FAB-11734 and we missed it. We'll get it fixed

nickgaski (Thu, 13 Dec 2018 21:14:30 GMT):
Thanks Pam. It would also be good to add some content regarding instantiation and the role of instantiation policies. My understanding from back in the day was that instantiation followed the same flow as the enumerated endorsement (i.e Org1peer0 & Org2peer0 would each return a proposal response to the client and they would each spin up a cc container if something like `"AND ('Org1MSP.peer','Org2MSP.peer')"` was passed). This does not appear to be the case anymore bc I only notice a single container starting for the peer bootstrapped in the CLI container

lightcap (Thu, 20 Dec 2018 22:35:58 GMT):
Is there a repo out there to contribute to the documentation?

joe-alewine (Wed, 02 Jan 2019 01:28:07 GMT):
@lightcap Code commits --- whether more traditional commits or doc commits --- are done through the gerrit review process. A good first step is to check out jira: https://jira.hyperledger.org/browse/FAB-13463?jql=project%20%3D%20FAB%20AND%20component%20%3D%20fabric-docs (this is a list of issues opened against the documentation). If you want to make a commit, it should first be tied to a jira issue. Then, you'll need to set up gerrit. First, by getting a Linux foundation ID. Then, by setting up your SSH keys. Here's some documentation on the process: https://hyperledger-fabric.readthedocs.io/en/release-1.3/Gerrit/gerrit.html

joe-alewine (Wed, 02 Jan 2019 01:28:07 GMT):
@lightcap Code commits --- whether more traditional commits or doc commits --- are done through the gerrit review process. A good first step is to check out jira: https://jira.hyperledger.org/browse/FAB-13463?jql=project%20%3D%20FAB%20AND%20component%20%3D%20fabric-docs (this is a list of issues opened against the documentation). If you want to make a commit, it should first be tied to a jira issue. To actually make a commit, you'll need to set up gerrit first. First, by getting a Linux foundation ID. Then, by setting up your SSH keys. Here's some documentation on the process: https://hyperledger-fabric.readthedocs.io/en/release-1.3/Gerrit/gerrit.html

KellyCooper (Thu, 03 Jan 2019 14:10:30 GMT):
The Learning Materials Development working group is in need of contributors for our 2019 objectives: edX Fabric update, edX Sawtooth update, edX Iroha tutorial. At this time, over 133,000 learners have participated in the edX courses. If you, or someone you know (university student, freelance developer, researcher, etc) is interested in contributing, please see the worksheet: 2019 Team and Individual/Small Group Objectives, Key Results, Participants and Tasks - https://goo.gl/1HzKaD The worksheet has two tabs, one for contributions to the group's 2019 OKRs, and a second that notes individual contributions. Feel free to message or reply with any questions. Thank you, Kelly

pandrejko (Wed, 09 Jan 2019 22:40:49 GMT):
@cbf I noticed the documentation Copyright is now out of date https://jira.hyperledger.org/secure/RapidBoard.jspa?rapidView=119&view=planning&selectedIssue=FAB-13605

cbf (Thu, 10 Jan 2019 15:13:49 GMT):
ah, I think that is in the template under docs/source/_template/footer.html

{%- if show_copyright %} {%- if hasdoc('copyright') %} {% trans path=pathto('copyright'), copyright=copyright|e %}© Copyright {{ copyright }}.{% endtrans %} {%- else %} {% trans copyright=copyright|e %}© Copyright Hyperledger 2018.{% endtrans %} {%- endif %} {%- endif %}

spacemandev (Fri, 11 Jan 2019 12:11:14 GMT):
Has joined the channel.

toddinpal (Mon, 14 Jan 2019 19:26:29 GMT):
In the page https://hyperledger-fabric.readthedocs.io/en/release-1.3/idemix.html there is this statement just above the section labeled Current Limitations: "For an example of using the cid library to retrieve these attributes, see this java SDK example.", yet following the link takes one to the example_cc0 chaincode that doesn't use CID

pandrejko (Fri, 18 Jan 2019 12:44:38 GMT):
@toddinpal Interesting. That link works for me. It resolves to https://github.com/hyperledger/fabric-sdk-java/blob/release-1.3/src/test/fixture/sdkintegration/gocc/sample1/src/github.com/example_cc/example_cc.go

pandrejko (Fri, 18 Jan 2019 12:47:16 GMT):
@toddinpal Thank you for reporting this. I opened this jira to investigate and resolve it. https://jira.hyperledger.org/browse/FAB-13751

incarose (Wed, 23 Jan 2019 00:23:12 GMT):
Has joined the channel.

edisinovcic (Mon, 28 Jan 2019 13:16:20 GMT):
Has joined the channel.

ankur.walia (Wed, 30 Jan 2019 12:37:44 GMT):
Has joined the channel.

ankur.walia (Wed, 30 Jan 2019 16:36:13 GMT):
Hello...Can I create and resolve an issue with very small spelling mistakes in the tutorial documents? I have never contributed before and want to get involved in the process. Thanks

ankur.walia (Wed, 30 Jan 2019 16:36:13 GMT):
Hello...Can I create and resolve an issue involving small spelling mistakes in the tutorial documents? I have never contributed before and want to get involved in the process. Thanks

mreddy (Wed, 30 Jan 2019 17:17:33 GMT):
Has joined the channel.

bdjidi (Wed, 30 Jan 2019 20:12:07 GMT):
Has left the channel.

spmcnamara (Fri, 01 Feb 2019 16:51:12 GMT):
Has joined the channel.

spmcnamara (Fri, 01 Feb 2019 16:54:35 GMT):
Hi all. I think there may be an error in the install documentation for MacOSX (https://hyperledger.github.io/composer/v0.19/installing/installing-prereqs.html#macos). It indicates you should install the latest node LTS version (nvm install --lts && nvm use --lts) however this results in Node v10 being installed, which I believe is still unsupported. The docs *do* indicate you need 8.9 or greater, and that Node 9 is not supported, but I think that creates confusion around the status of v10 (which I believe is still unsupported.)

spmcnamara (Fri, 01 Feb 2019 16:55:18 GMT):
(note: that was a terribly redundantly repetitive sentence.) :-(

spmcnamara (Fri, 01 Feb 2019 16:56:46 GMT):
My bad. I see I wasn't looking at "latest" docs and the issue has been resolved.

pasimoes (Sat, 02 Feb 2019 01:00:12 GMT):
Has joined the channel.

Jonra1993 (Thu, 07 Feb 2019 14:33:22 GMT):
Has joined the channel.

MHBauer (Thu, 07 Feb 2019 17:09:03 GMT):
Has joined the channel.

pandrejko (Wed, 13 Feb 2019 15:08:23 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=rHebsyA2Zqmwq5x7T) @ankur.walia Yes! You start the process by creating an issue for it in Jira and then submitting the CR. See this topic https://hyperledger-fabric.readthedocs.io/en/latest/CONTRIBUTING.html#reporting-bugs for getting started

danacr (Thu, 14 Feb 2019 20:05:00 GMT):
Has left the channel.

ankur.walia (Fri, 15 Feb 2019 12:06:53 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=RiErGeB4WQ9wsjK3b) @pandrejko great! thanks!

Jonra1993 (Sun, 17 Feb 2019 02:53:58 GMT):

Clipboard - February 16, 2019 9:53 PM

Jonra1993 (Sun, 17 Feb 2019 02:54:03 GMT):
I think that the function should be transfer(car, seller, buyer) because you say it transfer ownership of a specific car from ORG1 to ORG2.

pandrejko (Tue, 19 Feb 2019 13:43:41 GMT):
@odowdaibm In the screenshot above, trying to understand @jonra1993's question. I notice that on the left and the right boxes the transfer function is transfer ([car], seller, buyer) but in the middle it is (transfer [car], buyer, seller). Is that intentional?

pandrejko (Tue, 19 Feb 2019 13:44:54 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=8PzhJgvPEafBxfYmN) @toddinpal @toddinpal This has been fixed now in release 1-3, release 1-4 and master with updated samples.

maxrobot (Wed, 20 Feb 2019 16:43:01 GMT):
Are the docs here deprecated, https://openblockchain.readthedocs.io/en/latest/Setup/Network-setup/ ?

silliman (Wed, 20 Feb 2019 18:39:15 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=XjK5nq5xXhBGB4XX9) @maxrobot yes, any URL that says openblockchain should be ignored as it is from circa 2016, that is, the stone ages

maxrobot (Thu, 21 Feb 2019 10:14:40 GMT):
ok great thanks :)

maxrobot (Thu, 21 Feb 2019 11:16:34 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=ivze8jxLuk8EZ8wJS) @silliman I am trying to develop fabric locally is there any documentation that helps aspiring fabric developers?

silliman (Thu, 21 Feb 2019 13:25:40 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=5EAu53c7pxFeKf7m3) @maxrobot https://hyperledger-fabric.readthedocs.io/en/release-1.4/developapps/developing_applications.html

maxrobot (Thu, 21 Feb 2019 14:08:17 GMT):
@silliman apoligies I was unclear, I mean I want to make changes to the source code and then run the network... So my question is how can I build the docker images locally and use them to run some of the tutorial examples

silliman (Thu, 21 Feb 2019 14:57:39 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=Tffsay7jDSuvwybEK) @maxrobot you can get the source code from either https://gerrit.hyperledger.org/r/fabric or https://github.com/hyperledger/fabric and build it yourself locally. The first repo I gave you is the official repo and the one you must use if you want to contribute source code to the project. the latter repo is a read-only mirror and you can also use to build. See this section of the official docs https://hyperledger-fabric.readthedocs.io/en/release-1.4/CONTRIBUTING.html# and look in the Related Topics section for a link on building Hyperledger Fabric (i.e., compiling from source)

silliman (Thu, 21 Feb 2019 14:57:39 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=Tffsay7jDSuvwybEK) @maxrobot you can get the source code from either https://gerritt.hyperledger.org/r/fabric or https://github.com/hyperledger/fabric and build it yourself locally. The first repo I gave you is the official repo and the one you must use if you want to contribute source code to the project. the latter repo is a read-only mirror and you can also use to build. See this section of the official docs https://hyperledger-fabric.readthedocs.io/en/release-1.4/CONTRIBUTING.html# and look in the Related Topics section for a link on building Hyperledger Fabric (i.e., compiling from source)

silliman (Thu, 21 Feb 2019 14:57:39 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=Tffsay7jDSuvwybEK) @maxrobot you can get the source code from either https://gerrit.hyperledger.org/r/fabric or https://github.com/hyperledger/fabric (via git clone) and build it yourself locally. The first repo I gave you is the official repo and the one you must use if you want to contribute source code to the project. the latter repo is a read-only mirror and you can also use to build. See this section of the official docs https://hyperledger-fabric.readthedocs.io/en/release-1.4/CONTRIBUTING.html# and look in the Related Topics section for a link on building Hyperledger Fabric (i.e., compiling from source)

joe-alewine (Thu, 21 Feb 2019 17:04:51 GMT):
@maxrobot Yes, the "open blockchain" docs are taken from **much** older Fabric docs and are not maintained by Hyperledger or anyone in the Fabric community (the name even precedes "Fabric"!) and does not represent the current architecture. Follow the links @silliman provided

Rajatsharma (Thu, 21 Feb 2019 21:10:30 GMT):
Has joined the channel.

tango107 (Mon, 25 Feb 2019 01:33:41 GMT):
Has joined the channel.

maxrobot (Mon, 25 Feb 2019 10:32:31 GMT):
@silliman @joe-alewine thanks both I had found this in the meantime but I appreciate your response... pardon my ignorance but when developing do you continually build and rebuild the docker images and run a test case or do you have a more effective way of working? If you are rebuilding docker images how are you rebuilding quickly? thanks for the advice and patience :)

joe-alewine (Mon, 25 Feb 2019 13:05:58 GMT):
@maxrobot I think the #fabric or #fabric-questions channels would be a better place to ask a question like that

Estebanrestrepo (Fri, 01 Mar 2019 19:38:47 GMT):
Has joined the channel.

braduf (Tue, 05 Mar 2019 00:04:37 GMT):
Has joined the channel.

calebfroese (Wed, 06 Mar 2019 05:23:42 GMT):
Has joined the channel.

calebfroese (Wed, 06 Mar 2019 05:29:42 GMT):
Ran into an issue following the private data tutorial when installing chaincode to the second peer in org1. *Install chaincode on all peers* task 2 says _Use the CLI to switch the active peer to the second peer in Org1 and install the chaincode. Copy and paste the following entire block of commands into the CLI container and run them._ Using the peer address `export CORE_PEER_ADDRESS=peer1.org1.example.com:7051` in the tutorial will result in a connection error, as peer1 is listening on port 8051 not 7051. Running instead `export CORE_PEER_ADDRESS=peer1.org1.example.com:8051` solves the issue. https://hyperledger-fabric.readthedocs.io/en/release-1.4/private_data_tutorial.html

sstone1 (Wed, 06 Mar 2019 09:10:51 GMT):
@calebfroese please can you raise a bug in JIRA and ping me the number? I didn’t spot that I needed to update that tutorial when I changed the ports recently.

sstone1 (Wed, 06 Mar 2019 12:56:40 GMT):
@calebfroese nevermind, raised https://jira.hyperledger.org/browse/FAB-14509 :-)

dave.enyeart (Wed, 06 Mar 2019 14:52:04 GMT):
@sstone1 it's a little tricky... most people will get the latest tagged samples which is v1.4.0, and they will need the already existing doc. if we merge a doc update in release-1.4 it will show up in the production fabric docs

dave.enyeart (Wed, 06 Mar 2019 14:54:23 GMT):
i'm not thinking of a good answer yet... we could roll back the port updates in release-1.4, or mention in the doc different instructions for v1.4.0 vs v1.4.1

dave.enyeart (Wed, 06 Mar 2019 14:54:42 GMT):
neither are good options

sstone1 (Wed, 06 Mar 2019 14:54:51 GMT):
ahh... I see - if you run the `curl` installer, you get the tagged release w/o my changes, if you just clone from GitHub you get the branch w/ my changes

dave.enyeart (Wed, 06 Mar 2019 14:54:59 GMT):
right

dave.enyeart (Wed, 06 Mar 2019 14:55:48 GMT):
fabric-samples is versioned to the 3rd digit, while doc is versioned to the 2nd digit

dave.enyeart (Wed, 06 Mar 2019 14:56:57 GMT):
ideally we'd version fabric-samples to the 2nd digit and people would grab the latest, we can entertain that...

dave.enyeart (Wed, 06 Mar 2019 14:56:57 GMT):
ideally we'd version fabric-samples to the 2nd digit and people would grab the latest (via instructions and script), we can entertain that...

dave.enyeart (Wed, 06 Mar 2019 14:57:57 GMT):
will think more about it... have to step away for now...

sstone1 (Wed, 06 Mar 2019 14:58:07 GMT):
okay, will leave it with you

calebfroese (Thu, 07 Mar 2019 00:30:28 GMT):
thanks @sstone1 found a dead link to `Encc Example` under https://hyperledger-fabric.readthedocs.io/en/release-1.4/chaincode4ade.html#chaincode-encryption also

Rajatsharma (Thu, 07 Mar 2019 09:47:03 GMT):
I had raised a issue on JIRA https://jira.hyperledger.org/browse/FAB-13176 which @dave.enyeart had asked @mastersingh24 to have a look. I know they are really busy but just wanted to know, is there anything I could do so that this issue gets resolved fast. As I guess many people might face similar issues in the future too.

braduf (Thu, 07 Mar 2019 22:57:30 GMT):
Hi all, is there any more documentation on policies and sub-policies besides https://hyperledger-fabric.readthedocs.io/en/release-1.4/policies.html ? To get a better understanding of what exactly every possible policy and sub-policiy is for.

ycarmel (Mon, 11 Mar 2019 09:49:04 GMT):
Has joined the channel.

Yogendrasri (Mon, 11 Mar 2019 14:33:33 GMT):
We are looking to create Ethereum ERC 20 tokens but within HL Fabric runtime. we have found that we need to use fab proxy to connect to Eth VM in HL Fabric env. And that there is a constraint of one user per fab proxy, This is a issue because we need to move tokens between users, and this means that if we need to create 5k users, which also implies that we need to create 5K Fab Proxies. is there any way fab proxy constraint can be managed/eliminated?

pandrejko (Mon, 11 Mar 2019 16:52:32 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=8zRrQgfaYQqbetiir) @calebfroese I opened this jira to address this broken link https://jira.hyperledger.org/browse/FAB-14586

pandrejko (Mon, 11 Mar 2019 16:53:47 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=hj9KvfLPc4fZyBCDo) @Yogendrasri You could try the #fabric-questions channel for that question

MarioPissardo (Mon, 11 Mar 2019 20:35:26 GMT):
Has joined the channel.

KyunghoKim (Tue, 12 Mar 2019 03:08:32 GMT):
Has joined the channel.

knagware9 (Tue, 12 Mar 2019 07:15:10 GMT):
Has joined the channel.

siddjain (Tue, 12 Mar 2019 16:35:37 GMT):
Has joined the channel.

PaddyBN (Fri, 15 Mar 2019 23:26:55 GMT):
Has joined the channel.

odowdaibm (Mon, 18 Mar 2019 12:10:00 GMT):
@andrew-coleman @mbwhite @aso @SjirNijssen @Yogendrasri @bestbeforetoday https://gerrit.hyperledger.org/r/c/27754/ is in pretty good shape now! If you could read https://logs.hyperledger.org/production/vex-yul-hyp-jenkins-3/fabric-docs-build-x86_64/1463/html/developapps/transactioncontext.html and provide feedback -- I'd be happy to incorporate. This topic has been hanging out on 1.4 and I'd really like to get it merged. Thank you again!

andrew-coleman (Mon, 18 Mar 2019 12:10:03 GMT):
Has joined the channel.

bestbeforetoday (Mon, 18 Mar 2019 12:10:03 GMT):
Has joined the channel.

aso (Mon, 18 Mar 2019 12:10:03 GMT):
Has joined the channel.

abedsau (Mon, 18 Mar 2019 21:32:40 GMT):
Has joined the channel.

akshay.lawange (Wed, 20 Mar 2019 11:01:04 GMT):
Has joined the channel.

dexhunter (Fri, 22 Mar 2019 07:45:39 GMT):
Has joined the channel.

yanli133 (Mon, 25 Mar 2019 06:53:13 GMT):
Has joined the channel.

zacpl (Wed, 27 Mar 2019 14:00:00 GMT):
The documentation under the Private Data Tutorial section of the docs might need a change. In the first "Try it yourself" section Step 1 gives the following as a command to install the chaincode sample on some peer from the cli container that is spun up by running the byfn.sh script: peer chaincode install -n marblesp -v 1.0 -p github.com/hyperledger/fabric-samples/chaincode/marbles02_private/go/ However, the docker-compose file that is used to spin up the cli container actually mounts the chaincode samples to the github.com/chaincode directory in the cli container. The result is that following the steps in the documentation throws an error: Error: error getting chaincode code marblesp: path to chaincode does not exist: /opt/gopath/src/github.com/hyperledger/fabric-samples/chaincode/marbles02_private/go Changing the code snippet to: peer chaincode install -n marblesp -v 1.0 -p github.com/chaincode/marbles02_private/go/ Should fix the problem. Totally understand if this is not the place to bring this sort of thing up - happy to redirect the comment elsewhere.

zacpl (Wed, 27 Mar 2019 14:00:00 GMT):
The documentation under the Private Data Tutorial section of the docs might need a change (here: https://hyperledger-fabric.readthedocs.io/en/latest/private_data_tutorial.html) In the first "Try it yourself" section Step 1 gives the following as a command to install the chaincode sample on some peer from the cli container that is spun up by running the byfn.sh script: peer chaincode install -n marblesp -v 1.0 -p github.com/hyperledger/fabric-samples/chaincode/marbles02_private/go/ However, the docker-compose file that is used to spin up the cli container actually mounts the chaincode samples to the github.com/chaincode directory in the cli container. The result is that following the steps in the documentation throws an error: Error: error getting chaincode code marblesp: path to chaincode does not exist: /opt/gopath/src/github.com/hyperledger/fabric-samples/chaincode/marbles02_private/go Changing the code snippet to: peer chaincode install -n marblesp -v 1.0 -p github.com/chaincode/marbles02_private/go/ Should fix the problem. Totally understand if this is not the place to bring this sort of thing up - happy to redirect the comment elsewhere.

dave.enyeart (Wed, 27 Mar 2019 14:04:07 GMT):
@lehors I assume this relates to https://gerrit.hyperledger.org/r/#/c/28701/... thoughts?

dave.enyeart (Wed, 27 Mar 2019 14:04:31 GMT):
we should probably cherry-pick to release-1.4 regardless

lehors (Wed, 27 Mar 2019 14:20:07 GMT):
@dave.enyeart indeed

lehors (Wed, 27 Mar 2019 14:21:13 GMT):
but, the problem comes from looking at the latest readthedocs, when using 1.4, doesn't it?

lehors (Wed, 27 Mar 2019 14:24:04 GMT):
yes, I think that's correct: there is no problem if one uses the 1.4 doc with the 1.4 release

lehors (Wed, 27 Mar 2019 14:24:27 GMT):
@zacpl can you please check?

lehors (Wed, 27 Mar 2019 14:25:04 GMT):
https://hyperledger-fabric.readthedocs.io/en/release-1.4/private_data_tutorial.html#pd-install-instantiate-cc

lehors (Wed, 27 Mar 2019 14:25:34 GMT):
this tells you to do: peer chaincode install -n marblesp -v 1.0 -p github.com/chaincode/marbles02_private/go/

dave.enyeart (Wed, 27 Mar 2019 14:37:55 GMT):
@lehors So we are ok if using v1.4 docs with v1.4 samples, and using latest docs with master (v2.0) samples?

dave.enyeart (Wed, 27 Mar 2019 14:39:00 GMT):
I'd rather not cherry pick to release-1.4 then... as the samples go to 3rd digit but the docs only goes to 2nd digit

lehors (Wed, 27 Mar 2019 14:40:57 GMT):
that's correct, I say nothing is broken

lehors (Wed, 27 Mar 2019 14:41:31 GMT):
one simply needs to use the corresponding doc - which is normal

zacpl (Wed, 27 Mar 2019 16:33:12 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=PT9LWE8kZPjMzEC36) @lehors sorry - slow off the mark That's right - thank you Only thing to add is that some sort of disclaimer on the home page for the /latest/ docs might come in handy. Currently, it's easy to mistake those pages for documentation about release 1.4: so a banner to direct people to the pages that are actually relevant to the Fabric release they want might - for example - save people from posting similar future messages in this chat.

lehors (Wed, 27 Mar 2019 16:49:41 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=8s3jYgTBT7dH9vgwY) @zacpl Ah, that makes sense. I agree

lehors (Wed, 27 Mar 2019 17:06:24 GMT):
I'll open a ticket and proposed a CR to address that

lehors (Wed, 27 Mar 2019 17:06:24 GMT):
I'll open a ticket and propose a CR to address that

lehors (Wed, 27 Mar 2019 20:15:58 GMT):
@zacpl https://gerrit.hyperledger.org/r/#/c/30481/

spartucus (Thu, 28 Mar 2019 02:45:07 GMT):
Has joined the channel.

zacpl (Thu, 28 Mar 2019 09:35:47 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=4tDmLfjBpYthkGoNh) @lehors thanks again

GuillaumeCisco (Thu, 28 Mar 2019 10:51:08 GMT):
Has joined the channel.

GuillaumeCisco (Thu, 28 Mar 2019 10:55:27 GMT):
I've just discovered an issue with the `peer chaincode` command: https://hyperledger-fabric.readthedocs.io/en/release-1.4/commands/peerchaincode.html The documentation say we can use `--peerAddresses` for subcommands `install`, `instantiate`, `invoke`, `list`, `query`, `upgrade`. But in the go code of the peer chaincode command we can see: ``` // currently only support multiple peer addresses for invoke if cmdName != "invoke" && len(peerAddresses) > 1 { return errors.Errorf("'%s' command can only be executed against one peer. received %d", cmdName, len(peerAddresses)) } ``` Looks like `--peerAddresses` is only supported for `invoke`. That's why when I do things like: `# peer chaincode -C businesschannel list --instantiated --peerAddresses=peer0.org1.example.com:7051 --peerAddresses=peer1.org1.example.com:7051 --tlsRootCertFiles='/etc/hyperledger/fabric/tls/ca.crt'` I get the error: `Error: error validating peer connection parameters: 'list' command can only be executed against one peer. received 2` We should update the documentation for telling uses, it won't work correctly.

GuillaumeCisco (Thu, 28 Mar 2019 10:56:51 GMT):
For context, I'm implementing the `list instantiated chaincode` command for the `fabric-sdk-py` and I wonder how I should handle this as I have the possibility to return an error if a chaincode has not been instantiated on a peer

ilyahq (Fri, 29 Mar 2019 19:47:19 GMT):
Has joined the channel.

charki (Fri, 05 Apr 2019 15:00:51 GMT):
Has joined the channel.

raidinesh80 (Tue, 09 Apr 2019 17:22:58 GMT):
Has joined the channel.

qsmen (Thu, 11 Apr 2019 07:42:09 GMT):
the network in release doc is wonderfully written. It would be better if the network configure file is given. Thank you.

joe-alewine (Thu, 11 Apr 2019 13:07:04 GMT):
@negupta Could you take a look at @GuillaumeCisco's comment above?

GuillaumeCisco (Thu, 11 Apr 2019 13:36:17 GMT):
Thank you @joe-alewine

qsmen (Fri, 12 Apr 2019 03:05:27 GMT):
continue the network topic, initially the org r4 control netconfig, then it share the control with R1. Tell readers how to do? by adding R1 as the order org?

qsmen (Tue, 16 Apr 2019 02:04:17 GMT):
a poor suggestion or what else?

GuillaumeCisco (Tue, 16 Apr 2019 07:45:33 GMT):
is this channel dead?

pandrejko (Tue, 16 Apr 2019 20:30:59 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=hkMe6vJ5xcAz8zBuT) @qsmen @odowdaibm - Any thoughts on this suggestion?

pandrejko (Tue, 16 Apr 2019 20:30:59 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=hkMe6vJ5xcAz8zBuT) @qsmen @odowdaibm - Any thoughts on this suggestion? I think we deliberately did not include it since this is high level introduction and the associated underlying topics delve into the guts of the configtx.yaml. But Anthony may have a different opinion.

negupta (Wed, 17 Apr 2019 00:09:05 GMT):
@joe-alewine Thanks joe. Those commands were not updated recently, but I will take a look.

qsmen (Wed, 17 Apr 2019 01:10:25 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=5ji6GMmqYFhwRYTYp) @pandrejko I think just the final configtx.yaml will be enough. It can tell readers how the network is constructed from the configtx.yaml and this will deepen the understanding of configtx.yaml.

GuillaumeCisco (Wed, 17 Apr 2019 10:10:10 GMT):
Following this page: https://hyperledger-fabric.readthedocs.io/en/release-1.4/peer_event_services.html The last link point us to the node sdk tutorial : https://fabric-sdk-node.github.io/tutorial-channel-events.html But this tutorial is out of date and does not reflect the real specifications of the channel event hub. Last documentation can be found here: https://fabric-sdk-node.github.io/release-1.4/index.html

GuillaumeCisco (Wed, 17 Apr 2019 17:43:20 GMT):
Interestingly the code can support both documentations: https://github.com/hyperledger/fabric-sdk-node/blob/release-1.4/fabric-client/lib/ChannelEventHub.js#L330 Which is a little ambiguous for users

pandrejko (Mon, 22 Apr 2019 12:34:21 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=7mSQ6S3nNHz4puxN2) @GuillaumeCisco @bretharrison ^^ Any comments on this question?

pandrejko (Mon, 22 Apr 2019 12:34:21 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=7mSQ6S3nNHz4puxN2) @GuillaumeCisco @bretharrison Any comments on this question

bretharrison (Mon, 22 Apr 2019 13:12:01 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=xA9myxmcjXaYPGH8d) @pandrejko @mbwhite Would you have a look, I thought that the default was to the latest pages

mbwhite (Tue, 23 Apr 2019 13:25:35 GMT):
@bretharrison @pandrejko yep I see the problem with the redirects...

bretharrison (Tue, 23 Apr 2019 13:26:20 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=E6BiMzvbjmWTsJdmg) @mbwhite Great, thanks

pandrejko (Wed, 24 Apr 2019 12:59:12 GMT):
@mbwhite Is this something you can correct?

mbwhite (Wed, 24 Apr 2019 13:21:38 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=TfKoQhpAePNbnQuh7) @pandrejko Yes its.. need to raise the issue for it...

Fias (Fri, 26 Apr 2019 06:53:55 GMT):
Has joined the channel.

stevenjowens (Mon, 29 Apr 2019 20:35:29 GMT):
Has joined the channel.

MHBauer (Wed, 01 May 2019 23:01:50 GMT):
If I make a change to a *rst, how do I check the rendering?

MHBauer (Wed, 01 May 2019 23:07:22 GMT):
ah, docs have their own readme

MHBauer (Wed, 01 May 2019 23:07:22 GMT):
https://github.com/hyperledger/fabric/blob/release-1.4/docs/README.md

MHBauer (Wed, 01 May 2019 23:07:26 GMT):
should star or pin that^

MHBauer (Wed, 01 May 2019 23:08:16 GMT):
why system install with pip? (aka why sudo ?)

yerganat (Fri, 03 May 2019 05:15:01 GMT):
Has joined the channel.

GuillaumeCisco (Fri, 03 May 2019 07:32:19 GMT):
Yes, sudo is a bad practice for pip

abitrolly (Fri, 03 May 2019 10:39:50 GMT):
Has joined the channel.

abitrolly (Fri, 03 May 2019 10:40:34 GMT):
Test are failing for docs edited from GitHub. https://github.com/hyperledger/fabric/pull/244

spacemandev (Mon, 06 May 2019 18:49:23 GMT):
Has left the channel.

c-an (Wed, 08 May 2019 01:25:19 GMT):
Has joined the channel.

c-an (Wed, 08 May 2019 01:40:46 GMT):
hello!

Silona (Wed, 08 May 2019 04:55:06 GMT):
Has joined the channel.

Silona (Wed, 08 May 2019 04:55:06 GMT):
If you, or your company, is interested in participating in the Linux Foundation Fabric developer workshop, please complete this short Form by May 15: https://forms.gle/v4CuDnHQ9QA9pf6p8

Fedor_SH (Thu, 09 May 2019 08:54:20 GMT):
Has joined the channel.

abitrolly (Fri, 10 May 2019 13:07:17 GMT):
I am interested, but travel expenses from Belarus for a blockchain based startup are too high.

Silona (Fri, 10 May 2019 21:18:41 GMT):
yes sorry as a NPO we don't typically have much budget for that either.

abitrolly (Sat, 11 May 2019 06:50:58 GMT):
I forwarded the proposal to investors. If they are interested, they may be some souls willing to next week.

abitrolly (Sat, 11 May 2019 06:50:58 GMT):
I forwarded the proposal to investors. If they are interested, they may be some souls willing to join next week.

mauricio (Tue, 14 May 2019 13:19:31 GMT):
Has joined the channel.

mauricio (Tue, 14 May 2019 14:11:46 GMT):
Hi, @Silona how can we (the community) help to improve the Fabric and fabric-sdks documentation?. Also I think that is important translate the docs to other languages to increase and improve our community. Maybe we can work in make the documentation more easy to read, with more updated examples, a better user experience. Keep in touch, thanks in advance.

mauricio (Tue, 14 May 2019 14:11:46 GMT):
Hi, @Silona how can we (the community) help to improve the Fabric documentation?. Also I think that is important translate the docs to other languages to increase and improve our community. Maybe we can work in make the documentation more easy to read, with more updated examples, a better user experience. Keep in touch, thanks in advance.

pandrejko (Tue, 14 May 2019 20:03:52 GMT):
@mauricio If you are interested in translation, I would encourage you to reach out to @richzhao who is initiating a process for translating Fabric content and community contribution is always welcomed of course. Also if you are interested in improving anything in the docs, see this fabric topic https://hyperledger-fabric.readthedocs.io/en/latest/CONTRIBUTING.html. There is a Documentation workgroup call that meets weekly on Fridays. There are 2 calls, one for the eastern hemishpere and one for the western hemisphere and they are run bu Anthony O'Dowd. He sends out an email agenda every week to the hyperledger fabric email list server. You can subscribe here: https://lists.hyperledger.org/g/main

richzhao (Wed, 15 May 2019 12:10:21 GMT):
@mauricio thank you for much for your advice. we have set up a translation tool set, translating into Chinese is on going.

mauricio (Wed, 15 May 2019 12:19:52 GMT):
I can help translating the fabric and fabric sdk docs to spanish

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

Bobbijn (Mon, 20 May 2019 12:40:45 GMT):

Clipboard - May 20, 2019 8:40 AM

Silona (Tue, 21 May 2019 23:59:28 GMT):
We are looking for Fabric Developers and training groups to help us design the next Fabric Developer Certification on July 8-11 at the LF offices in SF. If you have Fabric experience please apply here. ttps://forms.gle/v4CuDnHQ9QA9pf6p8

MohammedR (Wed, 22 May 2019 10:14:30 GMT):
Has joined the channel.

inalgnu (Thu, 23 May 2019 15:05:43 GMT):
Has joined the channel.

kn3118 (Thu, 23 May 2019 16:43:15 GMT):
Has joined the channel.

klenik (Thu, 30 May 2019 10:26:21 GMT):
Has joined the channel.

klenik (Thu, 30 May 2019 10:27:14 GMT):
Hi all, dropped an [issue](https://jira.hyperledger.org/browse/FAB-15583) about the Raft doc page, can someone confirm/clarify/fix it?

klenik (Thu, 30 May 2019 10:27:14 GMT):
Hi all, created an [issue](https://jira.hyperledger.org/browse/FAB-15583) about the Raft doc page, can someone confirm/clarify/fix it?

yacovm (Thu, 30 May 2019 20:25:16 GMT):
@klenik https://gerrit.hyperledger.org/r/#/c/fabric/+/31637/

yacovm (Thu, 30 May 2019 20:25:25 GMT):
thanks for the report

anand.fast (Fri, 07 Jun 2019 01:13:08 GMT):
Has joined the channel.

bhemeswararaoankireddy (Mon, 10 Jun 2019 06:46:53 GMT):
Has joined the channel.

brockhager (Wed, 12 Jun 2019 19:36:07 GMT):
Has joined the channel.

Puneeth987 (Thu, 27 Jun 2019 06:37:17 GMT):
Has joined the channel.

qsmen (Fri, 12 Jul 2019 07:25:33 GMT):
in release doc 1.4, By default, the Raft service is running on the same gRPC server as the client facing server . what 's cleint facing server?Thanks

yacovm (Sun, 14 Jul 2019 16:35:07 GMT):
@qsmen - the 7050 port

qsmen (Mon, 15 Jul 2019 03:37:18 GMT):
ok, thanks

ianco (Thu, 01 Aug 2019 20:23:49 GMT):
Has left the channel.

CT123 (Fri, 16 Aug 2019 16:00:41 GMT):
Working through this document: https://buildmedia.readthedocs.org/media/pdf/hyperledger-fabric/latest/hyperledger-fabric.pdf And on page 110, under 6.4 Smart Contract Processing, it points to "If you'd like, you can download the sample and even run it locally." BUT THE LINKS to both are broken. "download the sample" points to install.html -- but no domain or other info and "run it locally" points to tutorial/commercial_paper.html Can someone *please* point me to the correct URLs so that we can work through these examples? Please?

joe-alewine (Fri, 16 Aug 2019 21:20:26 GMT):
The links might be broken because you're using a pdf build of the docs. I'm not sure where you're getting this pdf, but try using the live docs. https://hyperledger-fabric.readthedocs.io/en/master/

joe-alewine (Fri, 16 Aug 2019 21:20:26 GMT):
@CT123 The links might be broken because you're using a pdf build of the docs. I'm not sure where you're getting this pdf, but try using the live docs. https://hyperledger-fabric.readthedocs.io/en/master/

mbwhite (Mon, 19 Aug 2019 08:29:08 GMT):
Hello could I get some +1 for this please :-) https://gerrit.hyperledger.org/r/c/fabric/+/32640

CT123 (Mon, 19 Aug 2019 20:46:51 GMT):
Thanks, that does work for me personally, but we're doing internal documentation for users and having a page # reference to point them to helps so we've been using the PDF. We'll try to map it using the live docs.

bjcawanglu (Tue, 20 Aug 2019 02:04:29 GMT):
Has joined the channel.

sarapaul (Sun, 25 Aug 2019 22:11:41 GMT):
Has joined the channel.

CT123 (Thu, 12 Sep 2019 18:27:37 GMT):
Are there any naming convention rules for HLF network entities? For example, can I name a peer widget3-peerXYZ.project-name.domain.xyz? with the domain being fully qualified of course? Same with CA, orderer, MSP, etc? I can find no info in the docs, so asking here. Thanks.

soumyanayak (Sun, 15 Sep 2019 05:04:20 GMT):
Has joined the channel.

generak (Sun, 15 Sep 2019 11:44:20 GMT):
Has joined the channel.

buvaneshkumar1 (Sun, 15 Sep 2019 12:43:44 GMT):
Has joined the channel.

buvaneshkumar1 (Sun, 15 Sep 2019 12:43:45 GMT):
update the ledger — updating requires the consent of other peers in the network. A peer requires other peers in the network to approve a ledger update before it can be applied to a peer’s local ledger. This process is called consensus, which takes much longer to complete than a simple query. how and when this is happening

francisco-rojas (Sat, 21 Sep 2019 16:23:51 GMT):
Has joined the channel.

francisco-rojas (Sat, 21 Sep 2019 16:51:26 GMT):
Hello, My name is Francisco and I started to learn about Blockchain an Hyperledger Fabric recently. For the last few weeks I've been reading the Hyperledger Fabric Docs and have found a few small inconsistencies. After reading the Contribution guidelines my understanding is that I should broadcast the doc bugs here. So here are a couple inconsistencies I found today while going through the "Writing Your First Application" tutorial (https://hyperledger-fabric.readthedocs.io/en/release-1.4/write_first_app.html) 1. In the "Enrolling the admin user" section (https://hyperledger-fabric.readthedocs.io/en/release-1.4/write_first_app.html) there is a note that says: "You may find it useful to stream the CA logs when running the upcoming programs by opening a new terminal shell and running docker logs -f ca.example.com" However, after launching the network with the `./startFabric.sh javascript` command there is no "ca.example.com" container therefore the command fails. There are, however, two CAs: ca_peerOrg1 and ca_peerOrg2. After checking the source code of enrollAdmin.js I can see that it uses: ca.org1.example.com which corresponds to ca_peerOrg1 according to the first-network/docker-compose-ca.yaml file So the actual command to inspect the logs is docker logs -f ca_peerOrg1 2. In the "Querying the ledger" section (https://hyperledger-fabric.readthedocs.io/en/release-1.4/write_first_app.html#querying-the-ledger) there are some references to the ../../basic-network/connection.json file when in reality the code references ../../first-network/connection-org1.json as you can see in fabcar/javascript/query.js I am happy to contribute fixes to the docs as I go through them if you would guide me how to.

pandrejko (Mon, 23 Sep 2019 13:34:11 GMT):
@francisco-rojas Thank you for this information! You can start by opening jira issues of type Documentation https://hyperledger-fabric.readthedocs.io/en/latest/CONTRIBUTING.html#reporting-bugs. We are actually in the midst of converting from gerritt to git as we speak. I can give you a link to a video in which the new process was presented and of course we will be udpating the Contributions welcome topic with that information.. Let me get that link for you.

francisco-rojas (Mon, 23 Sep 2019 21:37:43 GMT):
I've created the ticket in JIRA. When you send me the video I will try opening a pull request for the changes. Thanks

pandrejko (Mon, 23 Sep 2019 23:15:54 GMT):
Thank you Francisco! Yes. Still working on getting that link.

paranjan (Thu, 26 Sep 2019 17:58:30 GMT):
Has joined the channel.

pandrejko (Mon, 30 Sep 2019 13:06:32 GMT):
Here is the link to our video/discussion for others who are interested in learning about the process for creating PRs using the new process: https://drive.google.com/open?id=1ZJrkVzjB5LAheaVxeLINir20xJBtuiQM . The plan is to update the `How to contribute` documentation in the Fabric docs to provide detailed instructions.

davidkhala (Thu, 03 Oct 2019 05:46:55 GMT):
Has joined the channel.

davidkhala (Thu, 03 Oct 2019 05:49:42 GMT):
@joe-alewine Hi joe, I found issue https://jira.hyperledger.org/browse/FAB-16756 when try to migrate from kafka according to doc.

klenik (Wed, 09 Oct 2019 13:38:05 GMT):
Has left the channel.

ravinayag (Sat, 12 Oct 2019 11:08:14 GMT):
Has joined the channel.

diego_ (Mon, 14 Oct 2019 17:08:59 GMT):
Has joined the channel.

cbf (Tue, 15 Oct 2019 17:43:50 GMT):
I like the way that the Besu team have used a hyperledger domain for their docs using RTD http://besu.hyperledger.org/en/latest/

cbf (Tue, 15 Oct 2019 17:44:11 GMT):
can we do the same? Also, I also like their layout.

cbf (Tue, 15 Oct 2019 17:44:25 GMT):
maybe some outreach to the Besu team to get some insights?

pandrejko (Wed, 16 Oct 2019 14:20:26 GMT):
Also nice that users can easily provide feedback. We can def investigate.

cbf (Wed, 16 Oct 2019 17:03:07 GMT):
congrats, @pandrejko on becoming a maintainer!

Ammu (Thu, 17 Oct 2019 12:03:12 GMT):
what is the command for instantiate chaincode using node channel name mychannel

soumyanayak (Thu, 17 Oct 2019 13:09:15 GMT):
For any node SDK related query you can always use the channel #fabric-sdk-node this channel is for fabric documentation

pandrejko (Fri, 18 Oct 2019 21:19:22 GMT):
Documentation workgroup meetings and agenda are now visible on the Fabric wiki https://wiki.hyperledger.org/display/fabric/Documentation+Working+Group All are welcome to join us on Fridays, meeting information is available on the wiki. Thanks @odowdaibm for setting all of this up!

VijayKrishnan (Sat, 19 Oct 2019 22:28:25 GMT):
Has joined the channel.

guoger (Wed, 23 Oct 2019 07:37:22 GMT):
I think [validated ledger](https://hyperledger-fabric.readthedocs.io/en/latest/arch-deep-dive.html#validated-ledger-vledger) docs are outdated due to commit https://gerrit.hyperledger.org/r/c/fabric/+/31086 and should removed. wdyt @pandrejko (was it ever implemented?)

pandrejko (Wed, 23 Oct 2019 11:42:08 GMT):
I would agree. Let me look into this.

pandrejko (Wed, 23 Oct 2019 12:44:24 GMT):
@guoger There is a disclaimer at the top of the page. https://hyperledger-fabric.readthedocs.io/en/latest/arch-deep-dive.html#architecture-origins The intent of this doc was to capture the original v1.0 design thoughts. The recommendation is that from this section we point to the disclaimer as a reminder. Then, in v2.0 we retire it from master docs, it will be there in the release-1.x branches for posterity. What do you think?

guoger (Thu, 24 Oct 2019 05:07:03 GMT):
@pandrejko sorry for late reply, i agree! i also saw Dave has proposed the same in #fabric-maintainers as well. thx

cbf (Thu, 24 Oct 2019 15:43:00 GMT):
agree it should ne removed. I see no reason to keep it at all

pandrejko (Fri, 25 Oct 2019 13:28:30 GMT):
Thanks. I opened a jira https://jira.hyperledger.org/browse/FAB-16926to remove it. We can work on getting it removed.

cbf (Fri, 25 Oct 2019 17:30:55 GMT):
I'll submit a CR to remove it

nathalie-ckc (Sun, 03 Nov 2019 23:24:16 GMT):
Has joined the channel.

DilipManjunatha (Wed, 13 Nov 2019 13:08:32 GMT):
Has joined the channel.

vikas.kundz (Fri, 15 Nov 2019 14:08:22 GMT):
max channel

DayalMukati (Tue, 19 Nov 2019 06:17:38 GMT):
Has joined the channel.

maniankara (Thu, 21 Nov 2019 21:51:20 GMT):
Has joined the channel.

maniankara (Thu, 21 Nov 2019 21:51:21 GMT):
Hello guys, I was finding ways to contribute to fabric and found a silly bug in `release1.4` and hence created this: https://jira.hyperledger.org/browse/FAB-17128. The description has the fix, but I wanted to learn also your gerrit workflow. Apparently I found my bug ended up in backlog and from the `jira boards` I see only `v2`. Does that mean we can only contribute to v2.0 ?

maniankara (Thu, 21 Nov 2019 21:58:14 GMT):
@cbf and @pandrejko ^^ -> you guys were active in this channel ;)

pandrejko (Fri, 22 Nov 2019 13:03:05 GMT):
@maniankara Thanks for reporting this bug. release 1.4 is our long term support release so we definitely want to get it fixed there. @joe-alewine is in the process of writing the upgrade instructions for v2 right now so we will definitely evaluate it and can include there if it is applicable as well. We welcome community contribution! If you would like to add it release 1.4. Today, the fabric repo is officially moving from Gerritt to GitHub. See https://hyperledger-fabric.readthedocs.io/en/release-1.4/CONTRIBUTING.html# We have a community documentation workgroup call today at 11 am EST where we will be discussing the new github process for contributions https://wiki.hyperledger.org/display/fabric/Documentation+Working+Group You are welcome to join us or watch the recording. If you'd like to try the PR yourself you can - feel free to post here with questions about the process.

pandrejko (Mon, 25 Nov 2019 23:51:40 GMT):
You may have seen Brett Logan's post that the process to submit Documentation (and Fabric) updates has now moved from Gerritt to Github. - If you are an existing Github user, the process should be very familiar to you. - If you are new to Github, checkout https://hyperledger-fabric.readthedocs.io/en/latest/github/github.html to get started. - If you were used to the Gerritt process and want to see what's different start with the note here: https://hyperledger-fabric.readthedocs.io/en/latest/CONTRIBUTING.html. I also started a jira to record some of the differences I have noticed https://jira.hyperledger.org/browse/FAB-17122. PR reviewers now get automatically assigned when you create the PR. We've experienced some issues with assigning individual reviewers and are currently working through that process. Stay tuned for an update around that. Issues are still being tracked in JIRA. Nothing has changed there. We welcome your documentation contributions. Any problems or questions about the new process, feel free to post here.

Silona (Tue, 03 Dec 2019 17:50:30 GMT):
The Hyperledger Fabric Developer (CHFD) exam is scheduled to launch in late Q1 2020 and we are now looking for Beta testers. Interested parties should complete the CHFD Beta Sign-up Form by January 15, 2020. The CHFD Beta is FREE for the first 20 who qualify and after that it will be available at the low discount of $100. https://training.linuxfoundation.org/certification/certified-hyperledger-fabric-developer/ https://docs.google.com/forms/d/e/1FAIpQLScPxgBt6GvuTcrtjYCkWqW2D6o-2YrNd4vR--KXFGUw-5Ctsw/viewform

guoger (Mon, 09 Dec 2019 07:36:56 GMT):
a small question - in existing docs and new PRs, both single and double backticks are used, however the latter is not necessary in most cases (as we don't have backtick within string to be escaped). why is that? thx

guoger (Mon, 09 Dec 2019 07:37:11 GMT):
cc @pandrejko

pandrejko (Mon, 09 Dec 2019 14:37:03 GMT):
@guoger I checked with our expert @joe-alewine and he confirmed that RST requires double back tics but markdown requires only single back tics. The thinking is that double back tics are required in RST because a single back tics indicates the start of a link. Hope this helps.

guoger (Mon, 09 Dec 2019 16:54:44 GMT):
that does help :) i think we should at least keep consistency for markdowns - use single backtics

guoger (Mon, 09 Dec 2019 16:55:07 GMT):
and my next question would be - are we switching to markdowns?

pandrejko (Mon, 09 Dec 2019 17:45:09 GMT):
We've left it up to personal preference and have not mandated which format to use. Both are curently supported

joe-alewine (Mon, 09 Dec 2019 19:08:25 GMT):
@guoger Markdown is better in general but RST has its good points. It allows for "note" boxes and is the only file format we currently have that allows for the creation of toc trees (it also does a better job with enumerated lists). In general I'd advise people to use markdown, since it's a more ubiquitous format, but if they want to use RST they have my blessing. Double backtics in markdown aren't ideal but they do work --- the extra backtics resolve themselves without an issue.

Silona (Mon, 09 Dec 2019 21:47:03 GMT):
Reminder if you haven't submitted yet the Hyperledger Fabric Developer (CHFD) exam is scheduled to launch in late Q1 2020 and we are now looking for Beta testers. Interested parties should complete the CHFD Beta Sign-up Form by January 15, 2020. https://training.linuxfoundation.org/certification/certified-hyperledger-fabric-developer/ https://docs.google.com/forms/d/e/1FAIpQLScPxgBt6GvuTcrtjYCkWqW2D6o-2YrNd4vR--KXFGUw-5Ctsw/viewform

stone-ch (Sat, 14 Dec 2019 12:56:23 GMT):
Has joined the channel.

ChaoLiu (Sat, 21 Dec 2019 17:18:44 GMT):
Has joined the channel.

konda.kalyan (Thu, 26 Dec 2019 05:59:15 GMT):
Has joined the channel.

andreevym (Sun, 29 Dec 2019 10:48:23 GMT):
Has joined the channel.

guoger (Tue, 07 Jan 2020 02:08:56 GMT):
Let's have another discussion around i18n, would *Wed 2PM UTC (9am east coast, 10pm china)* work for everybody? cc @pandrejko @stone-ch @richzhao

Silona (Thu, 09 Jan 2020 20:17:40 GMT):
Last chance! The Linux Foundation worked with Hyperledger Fabric Developer subject matter expert volunteers to identify the core domains and competencies for the Certified Hyperledger Fabric Developer (CHFD) exam, scheduled to launch in March 2020. Are you interested in participating in the Beta and receiving an early peek? The CHFD Beta is FREE for the first 100 who take the exam. Complete the CHFD Beta Sign-up Form by January 15, 2020 for your chance. If you pass you will be CHFD Certified!

smithbk (Thu, 09 Jan 2020 20:24:22 GMT):
Has left the channel.

tatsu-sato (Thu, 09 Jan 2020 22:18:47 GMT):
Has joined the channel.

Silona (Tue, 14 Jan 2020 16:49:46 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

CT123 (Tue, 14 Jan 2020 21:45:42 GMT):
FYI -- found a documentation error in the following -- apologies if this is the wrong chat to post this to: From here: https://hyperledger-fabric.readthedocs.io/en/latest/test_network.html This: ```Because the endorsement policy for the fabcar chaincode requires the transaction to be signed by Org1 and Org2, any chaincode invoke using the peer binaries needs to target both peer0.org1.example.com and peer0.org1.example.com. You can pass the following values to your invoke commands to target both peers:``` should reflect `peer0.org1.example.com` and `peer0.org2.example.com` The embedded values in the example are also NOT correct. When passing the code snippet from a terminal command line it throws an error: ` --peerAddresses localhost:7051 --tlsRootCertFiles ${PWD}/organizations/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/ca.crt --peerAddresses localhost:9051 --tlsRootCertFiles ${PWD}/organizations/peerOrganizations/org2.example.com/peers/peer0.org2.example.com/tls/ca.crt` Hope this helps.

CT123 (Tue, 14 Jan 2020 21:45:42 GMT):
FYI -- found a documentation error in the following -- apologies if this is the wrong chat to post this to: From here: https://hyperledger-fabric.readthedocs.io/en/latest/test_network.html This: ```Because the endorsement policy for the fabcar chaincode requires the transaction to be signed by Org1 and Org2, any chaincode invoke using the peer binaries needs to target both peer0.org1.example.com and peer0.org1.example.com. You can pass the following values to your invoke commands to target both peers:``` should reflect `peer0.org1.example.com` and `peer0.org2.example.com` Also FWIW -- the embedded values referenced below the above text is CONFUSING. While the concept is correct and the snippet `---perrAddresses` is in-fact contained in the command the user used in the previous step, if the user passes the snippet while "following along with the tutorial", passing the code snippet from a terminal command line it throws an error as it's not a valid command. Hope this helps.

CT123 (Tue, 14 Jan 2020 21:45:42 GMT):
FYI -- found a documentation error in the following -- apologies if this is the wrong chat to post this to: From here: https://hyperledger-fabric.readthedocs.io/en/latest/test_network.html This: ```Because the endorsement policy for the fabcar chaincode requires the transaction to be signed by Org1 and Org2, any chaincode invoke using the peer binaries needs to target both peer0.org1.example.com and peer0.org1.example.com. You can pass the following values to your invoke commands to target both peers:``` should reflect `peer0.org1.example.com` and `peer0.org2.example.com` Also FWIW -- the embedded values referenced below the above text is CONFUSING. While the concept is correct and the snippet `---peerAddresses` is in-fact contained in the command the user used in the previous step, if the user passes the snippet while "following along with the tutorial", passing the code snippet from a terminal command line it throws an error as it's not a valid command. Hope this helps.

CT123 (Tue, 14 Jan 2020 21:45:42 GMT):
FYI -- found a documentation error in the following -- apologies if this is the wrong chat to post this to: From here: https://hyperledger-fabric.readthedocs.io/en/latest/test_network.html This: ```Because the endorsement policy for the fabcar chaincode requires the transaction to be signed by Org1 and Org2, any chaincode invoke using the peer binaries needs to target both peer0.org1.example.com and peer0.org1.example.com. You can pass the following values to your invoke commands to target both peers:``` should reflect `peer0.org1.example.com` and `peer0.org2.example.com` Also FWIW -- the embedded values referenced below the above text is CONFUSING. While the concept is correct and the snippet `---peerAddresses` is in-fact contained in the command the user used in the previous step, if the user passes the snippet while "following along with the tutorial", it throws an error as it's not a valid command. Hope this helps.

pandrejko (Wed, 15 Jan 2020 15:52:58 GMT):
@CT123 Thanks for surfacing this I'll open a jira and take a look.

pandrejko (Wed, 15 Jan 2020 15:59:49 GMT):
https://jira.hyperledger.org/browse/FAB-17402

CT123 (Tue, 21 Jan 2020 17:00:29 GMT):
FYI -- found this documentation issue, e.g., broken link. -- In this page: https://hyperledger-fabric.readthedocs.io/en/latest/developapps/connectionprofile.html -- last paragraph under the Usage section, last sentence where it says, "Read about the list of available connection options and when to use them." -- the link on "about" is broken - it points to this page which loads as "doesn't exist yet" https://hyperledger-fabric.readthedocs.io/en/latest/developapps/connectoptions.html

dineshthemacho1 (Wed, 22 Jan 2020 06:06:28 GMT):
Has joined the channel.

pandrejko (Wed, 22 Jan 2020 12:56:22 GMT):
Thanks I opened this jira to get it addressed https://jira.hyperledger.org/browse/FAB-17424

lzaouche (Tue, 28 Jan 2020 09:17:29 GMT):
Has joined the channel.

pandrejko (Thu, 30 Jan 2020 21:45:26 GMT):
Fix was merged today.

easeev (Mon, 03 Feb 2020 08:20:46 GMT):
Has joined the channel.

CT123 (Wed, 05 Feb 2020 00:19:46 GMT):
FYI -- the copyright for here -- all pages actually -- reads 2019: https://hyperledger-fabric.readthedocs.io/en/release-2.0/write_first_app.html

stone-ch (Wed, 05 Feb 2020 15:28:08 GMT):
Hi, @dave.enyeart @rjones as we talked in the meeting just now, I describe the steps how to add the Chinese translations into Fabric official documents in readthedocs here. Thanks very much for your helping. 1.Import a Project: Add repo “https://github.com/hyperledger-labs/fabric-docs-cn” to Fabric official document account in readthedocs. 2.Add translations: Choose the project “Hyperledger Fabric Docs Production”, then choose “Admin”- “Translations”- “Project”, choose the translations project added just now (default name is “hyperledger-fabric-cn(Chinese)”), then click “Add”. 3.View docs: Now you can change languages in the Fabric official document show page. @guoger @pandrejko

rjones (Wed, 05 Feb 2020 15:28:08 GMT):
Has joined the channel.

rjones (Wed, 05 Feb 2020 16:00:10 GMT):
@stone-ch I did that - let me know if I need to do more. I can't get it to show any Chinese, only English versions of text. Do I need to rebuild?

pandrejko (Wed, 05 Feb 2020 18:32:46 GMT):
Thanks for pointing this out. We are working on getting it updated.

stone-ch (Thu, 06 Feb 2020 01:57:24 GMT):
@rjones It already has the translation now, one more thing is that you need active "release-1.4" and "release-2.0" version in Chinese project.

rjones (Thu, 06 Feb 2020 02:35:38 GMT):
@stone-ch can you see these errors?

rjones (Thu, 06 Feb 2020 02:35:39 GMT):
https://readthedocs.org/projects/fabric-documentation-chinese-translation/builds/10391325/

stone-ch (Thu, 06 Feb 2020 02:36:27 GMT):
yes I can see it

rjones (Thu, 06 Feb 2020 02:36:32 GMT):
ok.

rjones (Thu, 06 Feb 2020 02:39:01 GMT):
I assume there is something you can fix in the repo?

stone-ch (Thu, 06 Feb 2020 02:43:16 GMT):
The build passed in my project, https://readthedocs.org/projects/hyperledger-fabric-cn/builds/ .

stone-ch (Thu, 06 Feb 2020 02:44:21 GMT):
It seems OK now, https://hyperledger-fabric.readthedocs.io/zh_CN/release-1.4/who_we_are.html

stone-ch (Thu, 06 Feb 2020 02:47:06 GMT):
Though it builds failed, the web page shows right.

stone-ch (Thu, 06 Feb 2020 02:47:06 GMT):
yes, the release-2.0 version is not updated now, release-1.4 is Chinese documents. I will have more test to find out the errors.

stone-ch (Thu, 06 Feb 2020 02:47:06 GMT):
Thouth builds failed, the web page shows right.

guoger (Thu, 06 Feb 2020 02:55:10 GMT):
by clicking on zh_CN and select release-1.4, i could see chinese docs being displayed. We probably need to cross check build failures and actual content in docs, to see if we have any broken formatting/references

stone-ch (Thu, 06 Feb 2020 03:21:56 GMT):
Yes, the release-2.0 version is not updated now , release-1.4 is Chinese documents. I will have more test to find out the errors.

pandrejko (Thu, 06 Feb 2020 18:05:23 GMT):
I can see the content in release-1.4 now!!

CT123 (Thu, 06 Feb 2020 22:56:05 GMT):
posted to questions but should have been posted here... Running 2.0 and following "Writing Your First Application" e.g, fabcar. All good until: ``` Enrolling the admin user Note The following two sections involve communication with the Certificate Authority. You may find it useful to stream the CA logs when running the upcoming programs by opening a new terminal shell and running docker logs -f ca.example.com. ``` There is NO ca.example.com that starts on docker. There are no logs to display. Dashboard shows peers0 & 1 for orgs1 and 2, couchdb's 0-3, orderers (orderer and orderer1-5), and ca_peerOrg1 and ca_peerOrg2. So what should I be logging ca_peerOrg1 or ca_peerOrg2 or? Thanks

CT123 (Thu, 06 Feb 2020 22:56:05 GMT):
posted to questions but should have been posted here... Running 2.0 and following "Writing Your First Application" e.g, fabcar. reading from here: https://hyperledger-fabric.readthedocs.io/en/release-2.0/write_first_app.html All good until: ``` Enrolling the admin user Note The following two sections involve communication with the Certificate Authority. You may find it useful to stream the CA logs when running the upcoming programs by opening a new terminal shell and running docker logs -f ca.example.com. ``` There is NO ca.example.com that starts on docker. There are no logs to display. Dashboard shows peers0 & 1 for orgs1 and 2, couchdb's 0-3, orderers (orderer and orderer1-5), and ca_peerOrg1 and ca_peerOrg2. So what should I be logging ca_peerOrg1 or ca_peerOrg2 or? Thanks

CT123 (Thu, 06 Feb 2020 22:58:56 GMT):
Also, when examining fabcar/javascript/query.js -- the provided files does not parse JSON -- the last two lines are missing from query.js ```The application connects to the network using a gateway: const gateway = new Gateway(); await gateway.connect(ccp, { wallet, identity: 'user1' }); This code creates a new gateway and then uses it to connect the application to the network. ccp describes the network that the gateway will access with the identity user1 from wallet. See how the ccp has been loaded from ../../first-network/connection.json and parsed as a JSON file: const ccpPath = path.resolve(__dirname, '..', '..', 'first-network', 'connection.json'); const ccpJSON = fs.readFileSync(ccpPath, 'utf8'); const ccp = JSON.parse(ccpJSON);```

negupta (Fri, 07 Feb 2020 15:46:45 GMT):
Hi @CT123 Thank you for posting this. These issues are known and are being addressed with Pull Requests that are outstanding to update the tutorial and move the tutorial to the new test network.

negupta (Fri, 07 Feb 2020 15:47:03 GMT):
In the meantime, you should be using ca_peerOrg1 to stream the CA logs

pandrejko (Fri, 07 Feb 2020 22:16:59 GMT):
@CT123 https://github.com/hyperledger/fabric/pull/648 I'll cherry pick this back to the release-2.0 branch. Thanks.

Silona (Thu, 13 Feb 2020 18:23:57 GMT):
Howdy Contributors and Maintainers! Are you wondering about tapping into Developer marketing for your group or project? Do you have a blog post idea? An awesome announcement? Please attend our Contributor/marketing meeting! https://wiki.hyperledger.org/display/Marketing/2020-02-19+Meeting+notes

cbf (Wed, 26 Feb 2020 12:40:56 GMT):
Q: shouldn't the default version of the documentation on RTD be v2.0?

dave.enyeart (Wed, 26 Feb 2020 14:14:10 GMT):
yep, i just updated it

braduf (Thu, 27 Feb 2020 13:40:27 GMT):
Hi all, I have seen that in the latest version of the documentation, in the new section: "_Deploying a production network_" , there is contrary info to the rest of the documentation. For example it says: "_Note that for CouchDB in particular it is a best practice to operate your state database external to the peer, as you will be better able to allocate specific resources to the database this way._" While in the section "_Using CouchDB_ " for reasons of latency and security the following is mentioned: "_A Docker image of CouchDB is available and we recommend that it be run on the same server as the peer._"

braduf (Thu, 27 Feb 2020 13:40:27 GMT):
Hi all, I have seen that in the latest version of the documentation, in the new section: _Deploying a production network_, there is contrary info to the rest of the documentation. For example it says: "_Note that for CouchDB in particular it is a best practice to operate your state database external to the peer, as you will be better able to allocate specific resources to the database this way._" While in the section "_Using CouchDB_ " for reasons of latency and security the following is mentioned: "_A Docker image of CouchDB is available and we recommend that it be run on the same server as the peer._"

braduf (Thu, 27 Feb 2020 13:40:27 GMT):
Hi all, I have seen that in the latest version of the documentation, in the new section: _Deploying a production network_, there is contrary info to the rest of the documentation. For example it says: _Note that for CouchDB in particular it is a best practice to operate your state database external to the peer, as you will be better able to allocate specific resources to the database this way._ While in the section _Using CouchDB_ for reasons of latency and security the following is mentioned: _A Docker image of CouchDB is available and we recommend that it be run on the same server as the peer._

braduf (Thu, 27 Feb 2020 13:40:27 GMT):
Hi all, I have seen that in the latest version of the documentation, in the new section: _Deploying a production network_, there is contrary info to the rest of the documentation. For example it says: _Note that for CouchDB in particular it is a best practice to operate your state database external to the peer, as you will be better able to allocate specific resources to the database this way._ While in the section _Using CouchDB_, for reasons of latency and security, the following is mentioned: _A Docker image of CouchDB is available and we recommend that it be run on the same server as the peer._

pandrejko (Fri, 28 Feb 2020 18:43:59 GMT):
In a follow on PR I have changed the statement to `Note that for CouchDB in particular it is a best practice to operate your state database external to the peer (for example, in a separate container), as you will be better able to allocate specific resources to the database this way.`

braduf (Fri, 28 Feb 2020 19:02:48 GMT):
I think it should be better specified that it can be a different container, but that it is best practice to have it on the same server as the peer for less latency, and with every access from outside of the machine closed off (so also without access to the Fauxton interface in production), only the peer container itself should have access to the CouchDB container, nothing else. That is still not clear to me from the PR you proposed. Or what is your point of view about having it on the same machine instance?

natewhiteblock (Mon, 02 Mar 2020 23:25:53 GMT):
Has joined the channel.

japidei (Tue, 03 Mar 2020 18:03:21 GMT):
Has joined the channel.

Abhishekkishor (Thu, 12 Mar 2020 19:24:36 GMT):
Has joined the channel.

skyliulu (Sun, 22 Mar 2020 09:04:24 GMT):
Has joined the channel.

skyliulu (Sun, 22 Mar 2020 09:12:24 GMT):
Hi All,for decentralized governance for smart contracts in fabric2.0, I want to know how organizations can extend the chaincode for their use cases??

pandrejko (Mon, 23 Mar 2020 17:15:35 GMT):
@skyliulu As long as the reads and the writes they perfrom are identical, the smart contracts on the peers can be different. So this mean that one smart contract could be written in Golang while the other can be written in Node.js. @jyellick Would you care to comment?

jyellick (Mon, 23 Mar 2020 17:31:32 GMT):
@pandrejko In general, we would never encourage smart contracts written in two different languages. The read and write-sets must match exactly, and getting this to happen consistently across languages would be very challenging to accomplish. Of course, you _could_, so long as the reads and writes are consistent. The stronger use cases for 'different' chaincodes are: 1) Simply allowing each organization to perform their own packaging, without having to worry about those "chaincode fingerprint mismatch" errors you might have seen in v1.x. 2) To allow small, backwards compatible changes to be rolled out individually. For instance, imagine there were a bug in the code which did not check that sufficiently many arguments were supplied before dereferencing them. This results in a crash if the client makes a mistake. So, an update could be pushed out to address this bug immediately by one org, and then slowly, over the course of days or weeks by the others.

jyellick (Mon, 23 Mar 2020 17:39:23 GMT):
As far as use cases for actually having different logic across peers for the same chaincode, this could be done too, though should generally be restricted to decisions about validity. Something like an additional assertion for which an organization has its own business logic. For instance, say your org does not want to endorse any transactions over $10 million. You could of course add this check into the common chaincode "if org == org1 && value > $10 million", or, you could implement it in your own chaincode only. The latter might make more sense if some of these decisions are private business logic.

jyellick (Mon, 23 Mar 2020 17:41:57 GMT):
You could also include custom operational metrics that are interesting to your org only. Maybe your org is invested in statsd monitoring, while another org is using prometheus. You might each want to include different instrumentation for monitoring your chaincode. But, I would generally encourage users to try to keep code the same across all organizations, and only bifurcate it if the need presents itself.

aberwag (Tue, 24 Mar 2020 08:09:09 GMT):
Has joined the channel.

pandrejko (Wed, 25 Mar 2020 12:06:43 GMT):
@joe-alewine Could you update the process overview with this detail?

nileshv (Thu, 02 Apr 2020 06:10:52 GMT):
Has joined the channel.

dave.enyeart (Thu, 02 Apr 2020 12:38:55 GMT):
@rjones Many users attempt to edit our docs by clicking the links in RTD to open a pull request in GitHub UI. However, GitHub UI does not ask user to sign the commit. This causes almost all the web submissions to fail DCO check.

dave.enyeart (Thu, 02 Apr 2020 12:39:12 GMT):
I see the open issue https://github.com/todogroup/gh-issues/issues/50 which you have commented on

dave.enyeart (Thu, 02 Apr 2020 12:40:23 GMT):
Any suggestions on this? Any good way to inform people to add `Signed-off-by`? Or a way to have them fix up the PR afterwards?

rjones (Thu, 02 Apr 2020 13:55:56 GMT):
@dave.enyeart you may have seen me doing some `--force-with-lease` fixes. I'd like to make a bot to do that, but not all changes will support that (if the user doesn't have a valid email, for instance)

dave.enyeart (Thu, 02 Apr 2020 14:08:33 GMT):
@rjones do you have to manually clone their fork and re-push? Could we write down those instructions so that the contributor does it themself?

rjones (Thu, 02 Apr 2020 14:20:48 GMT):
contributor, or maintainer?

rjones (Thu, 02 Apr 2020 14:33:16 GMT):
@dave.enyeart do you have a few seconds to talk about https://github.com/hyperledger-cicd/Test/pull/1

dave.enyeart (Thu, 02 Apr 2020 15:14:45 GMT):
@rjones sure

Adhavpavan (Tue, 07 Apr 2020 15:41:42 GMT):
Has joined the channel.

kumar89 (Fri, 10 Apr 2020 05:11:57 GMT):
Has joined the channel.

negupta (Thu, 07 May 2020 16:16:46 GMT):
hello

LideCui (Fri, 15 May 2020 03:35:29 GMT):
Has joined the channel.

LideCui (Fri, 15 May 2020 03:37:14 GMT):
Hi, I want to report a small bug in https://hyperledger-fabric.readthedocs.io/en/latest/deploy_chaincode.html

LideCui (Fri, 15 May 2020 03:37:46 GMT):
`CC_PACKAGE_ID=fabcar_1:69de748301770f6ef64b42aa6bb6cb291df20aa39542c3ef94008615704007f3`

LideCui (Fri, 15 May 2020 03:38:12 GMT):
`export CC_PACKAGE_ID=fabcar_1:69de748301770f6ef64b42aa6bb6cb291df20aa39542c3ef94008615704007f3`

LideCui (Fri, 15 May 2020 03:38:29 GMT):
I think export cmd is missing

pandrejko (Fri, 15 May 2020 21:14:27 GMT):
@negupta - Could you take a look at this?

negupta (Mon, 18 May 2020 12:42:10 GMT):
@LideCui Put in a PR to add the export commands to the tutorial: https://github.com/hyperledger/fabric/pull/1284

renatost (Mon, 15 Jun 2020 22:34:23 GMT):
Has joined the channel.

data_prime (Thu, 25 Jun 2020 19:03:35 GMT):
Has joined the channel.

ViokingTung (Mon, 29 Jun 2020 08:38:11 GMT):
Has joined the channel.

pandrejko (Mon, 29 Jun 2020 11:51:17 GMT):
Brett posted in the fabric-maintainers channel but reposting here for broader awareness. There is now the capability to view the a documentation PR formatted content in ReadTheDocs. We all should be doing local documentation builds to verify content before submitting PRs, but having the ability to see the formatted content for a doc pr in ReadTheDocs can make it easier for reviewers to ensure the formatting and links work. https://chat.hyperledger.org/channel/fabric-maintainers?msg=i5gFSRbnjYRXGgy77

pandrejko (Mon, 29 Jun 2020 11:51:17 GMT):
Brett posted in the fabric-maintainers channel but reposting here for broader awareness. There is now the capability to view the a documentation PR formatted content in ReadTheDocs. We all should be doing local documentation builds to verify content before submitting PRs, but having the ability to see the formatted content for a doc pr in ReadTheDocs can make it easier for reviewers to ensure the formatting and links work. Just click the Details button. https://chat.hyperledger.org/channel/fabric-maintainers?msg=i5gFSRbnjYRXGgy77

cryptopatrick (Sun, 05 Jul 2020 10:26:31 GMT):
Has joined the channel.

cryptopatrick (Sun, 05 Jul 2020 10:28:46 GMT):
Hi! I'm reading through the Fabric documentation and finding so minor typos and small fixes that could be made. Do you welcome PRs for such things, or are they normally cleaned up in the next version of the docs? Thanks!

cryptopatrick (Sun, 05 Jul 2020 10:28:46 GMT):
Hi! I'm reading through the Fabric documentation and finding some minor typos and small fixes that could be made. Do you welcome PRs for such things, or are they normally cleaned up in the next version of the docs? Thanks!

pandrejko (Mon, 06 Jul 2020 13:09:26 GMT):
@cryptopatrick We certainly do! You can submit them to the master branch and then we can cherry pick them back to the other branches where applicable. The most important thing is *to not forget to sign your commits*, otherwise we cannot approve and merge your PR. https://hyperledger-fabric.readthedocs.io/en/latest/docs_guide.html

pandrejko (Mon, 06 Jul 2020 13:11:27 GMT):
and this: https://hyperledger-fabric.readthedocs.io/en/latest/github/github.html

nekia (Thu, 09 Jul 2020 05:20:18 GMT):
Has joined the channel.

crgb (Tue, 21 Jul 2020 05:40:46 GMT):
Has joined the channel.

crgb (Tue, 21 Jul 2020 05:43:16 GMT):
Hello. Can anybody tell me what is the status of the Fabric documentation spanish translation? Has it been already started? who is the main contact?

pandrejko (Tue, 21 Jul 2020 11:43:36 GMT):
There is a Spanish working group wiki here: https://wiki.hyperledger.org/display/fabric/Spanish+Working+Group that you could reach out for status.

pandrejko (Tue, 21 Jul 2020 11:43:36 GMT):
@crgb There is a Spanish working group wiki here: https://wiki.hyperledger.org/display/fabric/Spanish+Working+Group that you could reach out for status.

pandrejko (Tue, 21 Jul 2020 11:43:36 GMT):
@crgb There is a Spanish working group wiki here: https://wiki.hyperledger.org/display/fabric/Spanish+Working+Group that you could reach out for status.to

crgb (Wed, 22 Jul 2020 09:11:38 GMT):
Thanks @pandrejko. I'll contact them.

sebastiantf (Sat, 25 Jul 2020 16:32:05 GMT):
Has joined the channel.

sebastiantf (Sat, 25 Jul 2020 16:36:22 GMT):
Hello. In the Commercial Paper tutorial, I saw the line `addToWallet.js is the program that Isabella is going to use to load her identity into her wallet,` but didn't see `addToWallet.js` being used. Only `enrollUser.js` is being used which actually `loads the identity into the wallet` So which is actually doing what? Is this an error in the documentation?

sebastiantf (Wed, 29 Jul 2020 04:59:09 GMT):
Hello again. In Develping Applications --> Application --> [Process Response](https://hyperledger-fabric.readthedocs.io/en/release-2.2/developapps/application.html#process-response), `return paper.toBuffer();` is being discussed saying, `the new paper needs to be converted to a buffer before it is returned to the application. Notice how issue.js uses the class method CommercialPaper.fromBuffer()` But `return paper.toBuffer();` has been changed to just `return paper;` in this [commit](https://github.com/hyperledger/fabric-samples/commit/9b1452508fe1d654def3b219d51b176fad856484#diff-5c1ca5c039e592d4d34c645a1f192616)

sebastiantf (Wed, 29 Jul 2020 10:38:44 GMT):
In Developing Applications --> Application design elements --> [Connection Profile](https://hyperledger-fabric.readthedocs.io/en/release-2.2/developapps/connectionprofile.html#structure), the GitHub link to the sample connection profile yaml file specified in the documentation is broken: [stored](https://github.com/hyperledger/fabric-samples/blob/master/commercial-paper/organization/magnetocorp/gateway/networkConnection.yaml) It seems those connection profile files where gitignored in this [commit](https://github.com/hyperledger/fabric-samples/commit/b89ee34ff745b76922f00049df07629baaf3fe5d#diff-4ccc1cf2aecf85c2f9124db0f7528b1bR3)

sebastiantf (Wed, 29 Jul 2020 10:38:44 GMT):
In Developing Applications --> Application design elements --> [Connection Profile](https://hyperledger-fabric.readthedocs.io/en/release-2.2/developapps/connectionprofile.html#structure), the GitHub link to the sample connection profile yaml file specified in the documentation is broken: [stored](https://github.com/hyperledger/fabric-samples/blob/master/commercial-paper/organization/magnetocorp/gateway/networkConnection.yaml) and [corresponding](https://github.com/hyperledger/fabric-samples/blob/master/commercial-paper/organization/magnetocorp/gateway/networkConnection.yaml) It seems those connection profile files where gitignored in this [commit](https://github.com/hyperledger/fabric-samples/commit/b89ee34ff745b76922f00049df07629baaf3fe5d#diff-4ccc1cf2aecf85c2f9124db0f7528b1bR3)

sebastiantf (Wed, 29 Jul 2020 10:38:44 GMT):
In Developing Applications --> Application design elements --> [Connection Profile](https://hyperledger-fabric.readthedocs.io/en/release-2.2/developapps/connectionprofile.html#structure), the GitHub link to the sample connection profiles yaml file specified in the documentation is broken: [stored](https://github.com/hyperledger/fabric-samples/blob/master/commercial-paper/organization/magnetocorp/gateway/networkConnection.yaml) and [corresponding](https://github.com/hyperledger/fabric-samples/blob/master/commercial-paper/organization/magnetocorp/gateway/networkConnection.yaml) It seems those connection profile files where gitignored in this [commit](https://github.com/hyperledger/fabric-samples/commit/b89ee34ff745b76922f00049df07629baaf3fe5d#diff-4ccc1cf2aecf85c2f9124db0f7528b1bR3)

pandrejko (Sun, 02 Aug 2020 16:14:10 GMT):
Thanks @sebastiantf, we can take a look.

camohe90 (Fri, 07 Aug 2020 21:06:22 GMT):
Has joined the channel.

ChrisSargent (Mon, 10 Aug 2020 16:44:21 GMT):
Has joined the channel.

clydedacruz (Tue, 18 Aug 2020 04:17:38 GMT):
Hi! I was just reading through the fabric 2.2 docs. IMO -- The name "Membership Service Provider" doesn't clearly explain what it does. especially the 'service' part of the name. Could use a bullet list like below to convey what exactly an MSP is used for. At present ,it just seemed to me that as a reader one needs to dig out the true purpose and use of an MSP from the whole text. - MSP identifies which Root CAs and Intermediate CAs are accepted to define the members of a trust domain by listing the identities of their members, or by identifying which CAs are authorized to issue valid identities for their members. - Used to assign certain roles to identities. eg. designate ID 1 as org admin, designate ID 2 as peer - Maintain a list of identities that have been revoked

pandrejko (Fri, 21 Aug 2020 13:28:34 GMT):
@clydedacruz We definitely agree that the name is confusing and a poor choice, but I don't think we can rename it now. Agree the clarifications you suggested would help. Which MSP documentation are you referring to specifically - https://hyperledger-fabric.readthedocs.io/en/latest/membership/membership.html https://hyperledger-fabric.readthedocs.io/en/latest/msp.html

davidkhala (Sun, 23 Aug 2020 14:08:20 GMT):
@rjones Hi Ry, for repos `fabric-docs-i18n` could it be configured to allow reviewer to squash commits before merge?

yuki-kon (Fri, 11 Sep 2020 07:43:15 GMT):
@cmgabriel Hello Chris. I heard you are working on the tokens at the Eastern hemisphere documentation WG. I posted a PR to add ERC20 fungible token to fabric-samples. I'm waiting for feedback from the community. If you have some time, could you take a look at this PR? https://github.com/hyperledger/fabric-samples/pull/327

cmgabriel (Fri, 11 Sep 2020 10:48:20 GMT):
Sure @yuki-kon, will do. Also, @dave.enyeart has a UXTO token PR in fabric-samples as well.

yuki-kon (Sat, 12 Sep 2020 08:17:14 GMT):
@cmgabriel Thank you! It sounds great to have various token samples. I will check a UTXO PR.

wangdong (Mon, 14 Sep 2020 13:00:13 GMT):
Has joined the channel.

rjones (Thu, 17 Sep 2020 15:27:54 GMT):
Hi, if you have anything you'd like to see added to the /dev/weekly newsletter, please comment in the next two hours: https://wiki.hyperledger.org/pages/viewpage.action?pageId=39618911

RodrigoAlejandroMelo (Fri, 18 Sep 2020 01:13:00 GMT):
Has joined the channel.

rjones (Tue, 22 Sep 2020 14:38:38 GMT):
Howdy, folks. Any progress on sunsetting RTD?

negupta (Wed, 23 Sep 2020 21:51:11 GMT):
What is the scalability of a raft ordering service? users should deploy multiple nodes for HA, and try to have the service run by a number of organizations. Is there any scalability issue with a large number of raft nodes?

cmgabriel (Mon, 28 Sep 2020 12:29:47 GMT):
Hi @yuki-kon, I reviewed and executed your fungible token sample. Well done! Thank you for contributing this. I think there is room to combine this with PR #319 from @dave.enyeart. I am doing further research, and will provide additional comments in the PR soon. Thanks again.

CT123 (Mon, 28 Sep 2020 21:51:12 GMT):
Feedback setting up the developer environment for current (latest) release -- readability issues -- https://hyperledger-fabric.readthedocs.io/en/latest/dev-setup/devenv.html Moving from 1.4x to 2.x and trying to document steps for team -- formatting leads the reader to believe that EVERYTHING below Steps -> Developing for Windows is *specifically* for windows only -- and don't believe that was your intent. When you pick up with "Before running any git clone commands...." -- is that for windows, mac, linux or ??? For Clone the hyperledger source -- do I really need to install the source under a github.com directory or can it go anywhere? And why do you need my userid? Am I not simply dropping this into a folder *somewhere* on my disk? etc., etc. -- takeaway is the steps could be clearer by OS -- and they're not. Even if it's repetitive. Thanks in advance.

yuki-kon (Tue, 29 Sep 2020 00:43:44 GMT):
@cmgabriel Thank you for reviewing the ERC20 token. I'm glad to hear the sample worked well on your environment. Merging token samples is a good idea. I'm looking forward to comments in the PR.

pandrejko (Tue, 29 Sep 2020 14:39:37 GMT):
@jyellick Would you be able to respond to Nik's questions here.

jyellick (Tue, 29 Sep 2020 19:09:51 GMT):
Raft is a leader based protocol, where a single leader establishes a total order and replicates the data (in our case blocks) out to the followers. Raft works based on quorum, so, so long as a majority of the Raft nodes are online, the Raft cluster stays available.

jyellick (Tue, 29 Sep 2020 19:10:36 GMT):
Therefore you have two different competing interests. On the one hand, the more Raft nodes you have, the more you may lose and still maintain a majority online. e.g. A 5 node cluster can tolerate 2 nodes down, while a 7 node cluster can tolerate 3 nodes down.

jyellick (Tue, 29 Sep 2020 19:11:51 GMT):
On the other hand, the more nodes in your cluster, the more followers the leader must replicate blocks to, and the more network overhead there is for the leader to stay in contact with the rest of the cluster.

jyellick (Tue, 29 Sep 2020 19:13:27 GMT):
Practically, Raft clusters of more than a few dozen nodes begin to see noticeable performance degradation. Once clusters reach on the order of one hundred nodes, they begin having trouble maintaining quorum. Of course this is all dependent on the networking, and other resources available, and there are tunables like the tick interval which can be used to mitigate the larger communications overhead.

jyellick (Tue, 29 Sep 2020 19:14:04 GMT):
Also keep in mind that each channel an orderer participates in is a separate Raft instance, so, an orderer participating in 100 channels is actually doing 100x the work as an orderer in a single channel.

jyellick (Tue, 29 Sep 2020 19:15:32 GMT):
All this to say, it really depends on your use case, your resources, and your topology. If you forced me to give concrete guidance, I would generally expect clusters of 3, 5, 7, or 9 nodes, with no more than about 50 channels per orderer.

pandrejko (Tue, 29 Sep 2020 19:15:36 GMT):
@joe-alewine ^^ This is great information for our upcoming Orderer deployment guide. Thank you Jason.

pandrejko (Wed, 30 Sep 2020 17:49:12 GMT):
@robmurgai See this comment ^^

pandrejko (Wed, 30 Sep 2020 18:01:54 GMT):
@CT123 Rob Murgai has done some really good around this in general and will be sharing it on our Documentation Community call on Fridy 10-9 at 11AM est. We invite you to join and share your thoughts :-) https://zoom.us/j/6223336701?pwd=dkJKdHRlc3dNZEdKR1JYdW40R2pDUT09 Meeting ID: 622 333 6701 Passcode: 475869

pandrejko (Wed, 30 Sep 2020 18:01:54 GMT):
@CT123 Rob Murgai has done some really good work around this in general and will be sharing it on our Documentation Community call on Fridy 10-9 at 11AM est. We invite you to join and share your thoughts :-) https://zoom.us/j/6223336701?pwd=dkJKdHRlc3dNZEdKR1JYdW40R2pDUT09 Meeting ID: 622 333 6701 Passcode: 475869

claudiocebpaz (Fri, 02 Oct 2020 15:09:02 GMT):
Has joined the channel.

claudiocebpaz (Fri, 02 Oct 2020 15:10:20 GMT):
Hello. I just tried to join: https://zoom.us/j/6223336701 But is asking me for a password.

rjones (Fri, 02 Oct 2020 15:11:01 GMT):
https://zoom.us/j/6223336701?pwd=dkJKdHRlc3dNZEdKR1JYdW40R2pDUT09

rjones (Fri, 02 Oct 2020 15:11:28 GMT):
@claudiocebpaz https://lists.hyperledger.org/g/fabric/message/9115

claudiocebpaz (Fri, 02 Oct 2020 15:12:18 GMT):
Thanks!

skulos (Sat, 03 Oct 2020 13:17:13 GMT):
Has joined the channel.

skulos (Sat, 03 Oct 2020 13:29:24 GMT):
Not sure if this is the play to post this, but can someone please just take note that both the 01/10 and the 27/09 hyperledger-fabricdocs Documentation have bad tables in the metrics references. In the 01/10 release, 8.14 Metrics Reference, and in the 27/09 release, 9.11 Metrics Reference, the tables goes off-page to the right. This isn't critical but, would be an improvement to someone else interested in metrics but that does not work with Prometheus/Prometheus style metrics every day. Maybe just use landscape instead of portrait?

skulos (Sat, 03 Oct 2020 13:29:24 GMT):
Not sure if this is the place to post this, but can someone please just take note that both the 01/10 and the 27/09 hyperledger-fabricdocs Documentation have bad tables in the metrics references. In the 01/10 release, 8.14 Metrics Reference, and in the 27/09 release, 9.11 Metrics Reference, the tables goes off-page to the right. This isn't critical but, would be an improvement to someone else interested in metrics but that does not work with Prometheus/Prometheus style metrics every day. Maybe just use landscape instead of portrait?

pandrejko (Mon, 05 Oct 2020 12:47:53 GMT):
I too find the scrolling very annoying. I found 2 custom configurations that could potentially address it. https://knowyourtoolset.com/2018/02/controlling-the-width-of-a-table-with-read-the-docs/ https://rackerlabs.github.io/docs-rackspace/tools/rtd-tables.html @BrettLogan could this be applied in our build?

pandrejko (Mon, 05 Oct 2020 12:48:14 GMT):
I too find the scrolling very annoying. I found 2 custom configurations that could potentially address it. https://knowyourtoolset.com/2018/02/controlling-the-width-of-a-table-with-read-the-docs/ https://rackerlabs.github.io/docs-rackspace/tools/rtd-tables.html @BrettLogan could this be applied in our build?

rjones (Mon, 05 Oct 2020 14:26:44 GMT):
@pandrejko could you give me a link to where this is rendered?

rjones (Mon, 05 Oct 2020 14:29:52 GMT):
n/m found it: https://hyperledger-fabric.readthedocs.io/en/release-2.2/metrics_reference.html?highlight=metrics

rjones (Mon, 05 Oct 2020 16:20:26 GMT):
@pandrejko take a look: https://hyperledger-fabric--1966.org.readthedocs.build/en/1966/metrics_reference.html https://github.com/hyperledger/fabric/pull/1966

pandrejko (Mon, 05 Oct 2020 16:25:50 GMT):
@rjones Thannk you. Yes it is wrapping now. Looks sooooo much better.

rjones (Mon, 05 Oct 2020 16:36:00 GMT):
once you merge it, I think you can label it to be picked to 2.2 without conflight

rjones (Mon, 05 Oct 2020 16:36:00 GMT):
once you merge it, I think you can label it to be picked to 2.2 without conflict

negupta (Wed, 07 Oct 2020 20:18:36 GMT):
I needed to test the operations service, and was going to use the IBM Blockchain platform, but found the dependencies on IBM Cloud a bit daunting.

negupta (Wed, 07 Oct 2020 20:18:45 GMT):
However this article helped me do it locally: https://medium.com/@jushuspace/hyperledger-fabric-monitoring-with-prometheus-and-statsd-f43ef0ab110e

negupta (Wed, 07 Oct 2020 20:19:36 GMT):
Deployed the test network, and prometheus in a docker image, and can now generate local transactions and see the metrics in my browser. Good tip that could be more widely shared.

robmurgai (Thu, 15 Oct 2020 15:56:55 GMT):
Has joined the channel.

jmason900 (Fri, 16 Oct 2020 15:07:05 GMT):
@odowdaibm what's the zoom meeting password ? it's not listed in the email invite or on the Confluence wiki for the group ? thanks

rjones (Fri, 16 Oct 2020 16:28:19 GMT):
@jmason900 https://lists.hyperledger.org/g/fabric/viewevent?repeatid=22053&eventid=879232&calstart=2020-10-16 and https://lists.hyperledger.org/g/fabric/viewevent?repeatid=21946&eventid=879237&calstart=2020-10-16

AndreaCovino (Wed, 28 Oct 2020 22:55:43 GMT):
Has joined the channel.

heena066 (Mon, 02 Nov 2020 09:31:15 GMT):
Has joined the channel.

dibyaranjan (Thu, 03 Dec 2020 12:02:09 GMT):
Has joined the channel.

dibyaranjan (Thu, 03 Dec 2020 15:15:05 GMT):
Is the weekly zoom meeting only for the hyperledger members? The joining link asks for password, and it is not mentioned on confluence wiki page. Can anyone help what to do?

rjones (Thu, 03 Dec 2020 15:16:22 GMT):
`475869`

dibyaranjan (Thu, 03 Dec 2020 15:35:15 GMT):
Thank you!

iLico (Thu, 03 Dec 2020 19:38:08 GMT):
Has joined the channel.

JPonna (Fri, 26 Feb 2021 15:28:06 GMT):
Has joined the channel.

JPonna (Fri, 26 Feb 2021 15:28:07 GMT):
Hi All, I am looking for a Hyperledger Fabric System Architecture Diagram thats very similar to the one contributed for Hyperldger Sawtooth. https://www.altoros.com/blog/hyperledgers-sawtooth-lake-bets-on-modular-blockchains-and-elapsed-time-consensus/

pandrejko (Tue, 02 Mar 2021 19:10:49 GMT):
A Fabric Documentation Translation Campaign has been started by the Linux Foundation to invite more translators and start the translation of additional languages. See the blog and video here: https://www.hyperledger.org/blog/2021/03/02/translating-hyperledger-fabric-documentation-into-multiple-languages

pandrejko (Tue, 02 Mar 2021 19:10:49 GMT):
A Fabric Documentation Translation Campaign has been started by the Linux Foundation to invite more translators and encourage the translation of additional languages. See the blog and video here: https://www.hyperledger.org/blog/2021/03/02/translating-hyperledger-fabric-documentation-into-multiple-languages

cmgabriel (Fri, 05 Mar 2021 16:50:00 GMT):
Question for the channel; Currently we have docs meeting (Western Hemisphere) once per week on Fridays. Are there any objections to moving this to every other week to more align with other meeting cadences?

rjones (Fri, 05 Mar 2021 16:52:19 GMT):
@cmgabriel not on my part. I noticed the APAC calls ended, so I think reducing the cadence would make sense.

cmgabriel (Fri, 05 Mar 2021 17:02:29 GMT):
Thanks Ry

JPonna (Tue, 09 Mar 2021 19:53:02 GMT):
Does the Fabric Client SDK in Fabric 2.0 handle System Admin Activity like Channel Instantiations, Network bootstrapping etc as well as the Client Transaction Requests and behind the scenes processing of the Transaction Request.

davidwboswell (Fri, 12 Mar 2021 16:21:11 GMT):
Has joined the channel.

CANEREMEC (Fri, 26 Mar 2021 08:39:13 GMT):
Has joined the channel.

toddinpal (Wed, 07 Apr 2021 20:33:59 GMT):
Is there or are there plans for a Fabric Security Guide? Something that would cover best practices for privacy and confidentiality? I ask this primarily due to the recent report of privacy and confidentiality issue with Fabric as posted to hackerone.com.

srikumarcs (Mon, 26 Apr 2021 09:33:46 GMT):
Has joined the channel.

cmgabriel (Mon, 26 Apr 2021 10:56:13 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-documentation?msg=TubnGD8y4SMr6s9iH) Is there a link to the actual concern, or are you just advertising?

rjones (Mon, 26 Apr 2021 16:11:36 GMT):
@cmgabriel I think the concern is valid; the issues on hackerone pointed out some unclear documentation

cmgabriel (Mon, 26 Apr 2021 20:02:10 GMT):
I cannot find the actual article on hackerone because only a general link was provided. I searched the site and no mention of Fabric that I could find. What am I missing?

rjones (Mon, 26 Apr 2021 20:09:27 GMT):
My error; [here is the start of an email thread](https://lists.hyperledger.org/g/fabric/message/9791) which points to the H1 issues

rjones (Mon, 26 Apr 2021 20:09:59 GMT):
[better link to thread](https://lists.hyperledger.org/g/fabric/topic/81699195#9791)

cmgabriel (Wed, 28 Apr 2021 12:54:57 GMT):
:pray:

cmgabriel (Wed, 28 Apr 2021 12:54:57 GMT):
:thanks:

cmgabriel (Wed, 28 Apr 2021 14:23:58 GMT):
@toddinpal I apologize for my initial confusion because the link you provided was not to the actual concern raised by the report but to the landing page for hackerone and after performing search on their site could not find any mention of what you were referencing. @rjones was kind enough to set me on the right path with links to the prior discussion around this. So first, thank you for raising this and second, we will be making an addition to the docs to address security guidelines in deployment to a production environment.

jeffdz40 (Sun, 23 May 2021 17:03:13 GMT):
Has joined the channel.

jeffdz40 (Sun, 23 May 2021 17:03:14 GMT):
Hey guys, my name is Jefferson. Fintech person and newly minted blockchain dev. Here to contribute to documentation if i can. Thank you for having me

RobertBetschinger (Fri, 28 May 2021 10:21:06 GMT):
Has joined the channel.

indranil32 (Wed, 09 Jun 2021 14:30:05 GMT):
Has joined the channel.

indranil32 (Wed, 09 Jun 2021 14:30:23 GMT):
few links like this - https://hyperledger-fabric.readthedocs.io/en/release-2.2/updating_a_channel.html are broken in the latest release docs

indranil32 (Wed, 09 Jun 2021 16:12:51 GMT):
https://hyperledger-fabric.readthedocs.io/en/release-2.2/test_network.html -> prerequisites link is broken

indranil32 (Wed, 09 Jun 2021 16:14:25 GMT):
https://hyperledger-fabric.readthedocs.io/en/release-2.2/prereqs.html -> is missing

rjones (Thu, 10 Jun 2021 16:01:26 GMT):
@indranil32 thank you - I filed a quartet of bugs, and gave credit to you here: https://lists.hyperledger.org/g/fabric/message/10109

Sungmin.Jeun (Thu, 10 Jun 2021 16:08:17 GMT):
Has joined the channel.

angelparrales (Fri, 18 Jun 2021 16:18:05 GMT):
Has joined the channel.

indranil32 (Fri, 02 Jul 2021 06:48:32 GMT):
https://hyperledger-fabric.readthedocs.io/en/latest/style_guide.html ==> For Markdown formatting. ==> points to a wrong page

indranil32 (Fri, 02 Jul 2021 06:48:59 GMT):
also => For RST formatting. => broken, on the same page

rjones (Fri, 02 Jul 2021 14:57:00 GMT):
thank you, @indranil32 !

shanedeconinck (Tue, 07 Sep 2021 11:18:47 GMT):
Has joined the channel.

shanedeconinck (Tue, 07 Sep 2021 11:18:48 GMT):
Hi, There's an issue with https://hyperledger-fabric.readthedocs.io/en/release/samples.html#download-platform-specific-binaries The bash script at https://goo.gl/kFFqh5 mentions https://nexus.hyperledger.org/content/repositories/releases/org/hyperledger/fabric/hyperledger-fabric/${ARCH}-${VERSION}/hyperledger-fabric-${ARCH}-${VERSION}.tar.gz But it seems nexus.hyperledger.org is no longer being used. I have no idea where the binaries are located now

davidkel (Tue, 07 Sep 2021 11:25:35 GMT):
That page is very old, try referring to this one https://hyperledger-fabric.readthedocs.io/en/release-2.2/install.html

shanedeconinck (Tue, 07 Sep 2021 11:26:15 GMT):
Aha thanks, i thought /release would point me to the latest docs

shanedeconinck (Tue, 07 Sep 2021 11:40:38 GMT):
Thanks, was confusing to me that /release didn't point to the latest version

rjones (Tue, 07 Sep 2021 16:16:45 GMT):
yes, we decommissioned nexus four years ago or so

justiny (Wed, 15 Sep 2021 06:28:19 GMT):
Has joined the channel.

justiny (Wed, 15 Sep 2021 06:50:30 GMT):
Hi, I reported a issue(https://github.com/hyperledger/fabric/issues/2920) and made a pull request (https://github.com/hyperledger/fabric/pull/2921) for that.

davidwboswell (Wed, 15 Sep 2021 16:47:26 GMT):
@cmgabriel -- would you be able to help justiny with the process of making an update to the fabric docs?

justiny (Thu, 16 Sep 2021 00:19:56 GMT):
It's already done and merged to master for the pull request for fabric (https://github.com/hyperledger/fabric/pull/2921). There is also a pull request for fabric-docs-i18n (https://github.com/hyperledger/fabric-docs-i18n/pull/551). Is it dealt with in #i18n ?

rjones (Thu, 16 Sep 2021 01:50:57 GMT):
merged

justiny (Thu, 16 Sep 2021 12:47:04 GMT):
@rjones Thanks!

joshhus (Fri, 29 Oct 2021 14:26:18 GMT):
Hello, I recently re-joined. I spoke to @davidwboswell about scheduling a regular call on docs.

davidwboswell (Fri, 29 Oct 2021 18:15:35 GMT):
hey @joshhus -- nice to see you here :)

s.vahidi (Tue, 30 Nov 2021 07:39:15 GMT):
Has joined the channel.

nikusingh (Mon, 17 Jan 2022 04:34:49 GMT):
Has joined the channel.

nikusingh (Mon, 17 Jan 2022 05:55:18 GMT):
Hey everyone I am Niku Singh a sophomore from India. I am new here and to the Blockchain world. I was surfing the net and came across Hyperledger and thought could be a part of it. So that I can learn more about its project. Really happy to be here :smile:

nikusingh (Mon, 17 Jan 2022 05:55:57 GMT):
are there any ways I can contribute to the docs, I have Knowledge of MERN stack.

rjones (Tue, 18 Jan 2022 16:29:32 GMT):
@nikusingh there is an [i18n project](https://github.com/hyperledger/fabric-docs-i18n); also, a [samples](https://github.com/hyperledger/fabric-samples) project that might work as well

jmason900 (Thu, 03 Feb 2022 19:20:17 GMT):
who is the current lead for the Fabric doc team? thanks

rjones (Sat, 12 Feb 2022 00:36:34 GMT):
Has left the channel.

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