fabric@lists.hyperledger.org

Re: Maintainer nominations

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

By Jay Guo · #7272 ·

Re: Maintainer nominations

The intent of my proposal was exactly as Yacov says - doc maintainers would be comprised of the core Fabric maintainers in addition to heavy doc contributors/reviewers. I do understand Brian's point,

By David Enyeart · #7271 ·

Re: #fabric Certificates and Keys generation and sharing #fabric

Something I forgot to mention, I'm also going investigate the use of a HSM. Maybe this could make things easier as apparently peers and orderers can connect to the HSM. If it enabled the retrieval of

By Jean-Gaël Dominé <jgdomine@...> · #7270 ·

#fabric Certificates and Keys generation and sharing #fabric

Hi all, I would like to expose some ideas to have your feelings and ideas about the generation and sharing of the artifacts because I'm not sure about which path to take. In my network (deployed in

By Jean-Gaël Dominé <jgdomine@...> · #7269 ·

Re: Proposal : Hyperledger Fabric block archiving

Hi Atsushi - Thanks for sharing your efforts to date. Overall, I like the idea of providing a utility to do this as generally we tell people that they can do this but don't provide any tools for

By Gari Singh <garis@...> · #7268 ·

Re: Maintainer nominations

I think the best solution for these 2 seeminglyconflicting ideas is: All maintainers of code repositoriesshould be able to merge documentation contributions Maintainers of the documentation shouldnot

By Yacov · #7267 ·

Re: Maintainer nominations

Thank you Pam. I'm very much in favour of these two nominations, and personally, I'd like to see more maintainers and contributors to Hyperledger Fabric in general, and documentation in particular. On

By Anthony O'Dowd <a_o-dowd@...> · #7266 ·

Re: #fabric #raft Orderers and organization, how to organize them? #fabric #raft

I do not think you’d benefit by using different root CA’s for orderer and peer of the same org. Each org already need 2 root CA’s, one for signing cert, the other for TLS. If you double that,

By Yueming Xu · #7265 ·

Re: Maintainer nominations

On 11/25/19 6:09 PM, David Enyeart wrote: Are there separate maintainer pools for different fabric-* repos? If so, I can understand the argument, coming from a world

By Brian Behlendorf <bbehlendorf@...> · #7264 ·

Re: Maintainer nominations

Our intent has been to split Fabric docs into its own repository after the transition to GitHub and Azure Pipelines. We only have one more repository to switch over (fabric-test), then will proceed

By David Enyeart · #7263 ·

Re: Hyperledger Fabric GitHub Migration

The transition to GitHub for source control management, and Azure Pipelines for CI, is now complete for all Fabric development repositories. The final repository to shift will be fabric-test in early

By David Enyeart · #7262 ·

Re: Maintainer nominations

> and wasrecently recognized as a Hyperledgersignificant contributor. Just for the record.... only IBMerscan access this link.... From: "Pam Andrejko"<pama@...> To:

By Yacov · #7261 ·

Maintainer nominations

All, I would like to nominate two new Documentation maintainers for the Hyperledger Fabric project. They are Chris Gabriel (Hyperchain Labs) and Joe Alewine (IBM). Chris has been an instrumental

By Pam Andrejko · #7260 ·

Re: Proposal : Hyperledger Fabric block archiving

Hey Atsushi, one thing I noticed while skimming thecode, is that while you send the ArchivedBlockFileMsg via gossip, you arenot ensuring it is eventually propagated to peers successfully. This means

By Yacov · #7259 ·

Re: Proposal : Hyperledger Fabric block archiving

Hi Atsushi, Thanks for your proposal and at high level the objective makes sense to me and below is my high level observations that you may want to consider. First, the fundamental assumption that

By Manish · #7258 ·

Re: Multi-network node deployments #fabric

Private VLAN/VPN, or do a proper public IP p2p setup w/o docker swarm. Again, docker swarm and k8s are great for distributed microservices and big load balanced, asymmetrical

By Nye Liu <nye@...> · #7257 ·

Re: Multi-network node deployments #fabric

I highly suggest that you look into cello ansible agent to deploy your network onto k8s environment. Here is the doc on how to do that. hyperledger/cello hyperledger/cello Operating System for

By email4tong@gmail.com · #7256 ·

Re: Multi-network node deployments #fabric

Thanks Tong. We are currently using Docker swarm as a method of deploying a Fabric network across multiple hosts. However, this solution can only be properly applied to hosts inside the same LAN.

By Nancy Min · #7255 ·

Next Hyperledger Fabric Application Developer Community call - Thursday Nov 28th @ 4pm UTC (4pm UK) - 11am ET, 8am PT

dear Fabric ApplicationDeveloper, the next FabricApplication Developer community call is scheduled for this ThursdayNov 28th @ 4pm UTC (4pm UK) - 11am ET (-5 hrs), 8am PT(-8 hrs)- seetime zones. It

By Paul O'Mahoney <mahoney@...> · #7254 ·

Re: #fabric #raft Orderers and organization, how to organize them? #fabric #raft

Why is it a "best practice" to have different CAs for peers and for orderers? What potential problems is this solving over having a single CA for both? Regards, Todd

By Todd Little <toddjlittle@...> · #7253 ·

Messages