Hello All, Due to our colleaguesin the US celebrating Thanksgiving there will not be a call this week!Our next call will be Dec 6. You can read thesummary minutes for last week's call:

Joson, I just did as per your suggestion, signed config changes (envelop) with orderer MSP admin. As I already mentioned in below mail, "When we create certificates using cryptogen tool, for peer

thanks. this is helpful.

You can see an explanation and proposal to enforce the database target here: https://jira.hyperledger.org/browse/FAB-17163 Dave Enyeart "Siddharth Jain" ---11/27/2019 01:01:52 PM---I read somewhere in

I read somewhere in the docs that all nodes have to either use LevelDB or CouchDB. I can't find link to where I read this but am wondering why is that so? Since each peer's db is independent, I would

For those of you not attending the Fabric contributor meeting today where this topic was discussed... - There was general agreement that documentation should not be split from Fabric repository unless

Hello Jason, When we create certificates using cryptogen tool, for peer organizations, the user admin certificate has OU as "Admin", but in the case of Orderer Organization, Certificate has OU as

I’m glad to see doc is being a hot topic. Technical Working Group China(TWGC) has been working more than a year translating fabric doc into Chinese. There are more than 10 active volunteers who

I think that it is important not to conflate things. There's a request to add two maintainers who's role will be to help manage the Fabric documentation. I think that should be handled independent of

We could gate the DocBuild, UT and IT behind the success of VerifyBuild like we do today, and can set variables (BuildDoc and RunTests) as true or false and make them the conditions on which the

I have no clue in AZP, perhaps Brett canshed some light here, but - can't you just put in our scripts somethingthat does a git show --name-only and returns immediately in casethere are only changes to

Ok, we're getting closer. CODEOWNERS does indeed buy us some options. I think that would take us down to two remaining concerns with docs in Fabric repo. Anybody have ideas on solving these? 1) Doc

I too believe that the documentation belongs with the code. I also do not believe that every person who contributes should become a maintainer ... especially when they do not have a history of

I also feel that the 'default' position should be that docs reside with the code repo, and there would need to be a compelling reason to split them out. In my opinion given the recent changes, there

I agree that these would be two good additions to the docs maintainership. I approve. Chris

The SDK documentation and CA is only documentationabout APIs, it's not documentation about concepts, ideas, and tutorials. I don't think that extracting the fabricdocumentation files out of the fabric

For the record, I am not in favor of extracting the documentation. I strongly feel that the doc and the code should live together where feasible. My perspective is that lowering the barriers to

+1 for Jay's suggestion 发件人: fabric@... <fabric@...> 代表 Jay Guo <guojiannan1101@...> 发送时间: 2019年11月26日 22:11 收件人: Jay Guo <guojiannan1101@...> 抄送: David Enyeart

Just in case i wasn't stating my opinion clearly, i'd suggest to separate docs from code, and have multiple languages dirs within it, e.g. content |- en |- zh |- de - J

from translation point of view, i've seen some popular projects like k8s and tensorflow that separate docs from code, where i18n is first class citizen within the dir structure, for example [1] and