Hello Tracy, If it is different from ILP, what is it? Will there be a doc describing it much like a project proposal. Any technical papers? Is there code you would like to bring in? Best, Vipin

Hi, Chris and other TSC members. The item that you are talking about (Helm charts, etc) is not the interoperability project that we want to contribute to Hyperledger. That will be separate discussion

I could be wrong, of course. Tracy is the expert here. Chris

Hi Chris, Thanks for the response. First, on bloat: we avoid bloat by having customizable builds (that only incorporate what people themselves need). For instance, right now we have and

Hart, I am not suggesting that you bust up Ursa, though TBH, I have not looked closely at how you avoid bloat as we add more algorithms but a consumer only needs one of them. I am saying that my

Hi Chris, I’m not sure I necessarily agree with this. I don’t know the full details of the interoperability proposals, so I can’t say for sure, but I can elaborate from my experiences on

First, Thanks Brian for articulating this and explaining the history in more detail. It greatly helps me understand the rational a bit better. Folks I am torn on this one and will enjoy following the

(b) is way more compelling to me also, though I would personally get a kick out of a centralized product to manage decentralized interop. -dc

So, I find myself thinking that we'd be better off with a number of smaller, component-level projects that can be (re)used and composed, than adding (or adding to) larger sprawling ones. I say this

Hi TSC, continuing the conversation we had started but didn't have enough time to fully articulate on the call.  So that makes this the "Quilt Update" due for today. A few months ago, we started

I enabled 2FA today. A feature I did not know GitHub has is that if you remove someone, when they enable 2FA and are re-invited, you have the option to re-apply the permissions they had at the time

Nice point, vipin. Libra is a totally different project, but it's appealing to see if there's any collaborative potentials in techniques, e.g., their BFT algorithm. -- Best wishes! Baohua Yang

https://wiki.hyperledger.org/display/HYP/2019+06+20+TSC+Minutes Dave --- David Huseby Security Maven, Hyperledger The Linux Foundation +1-206-234-2392 dhuseby@...

Hi all, I have published an article on Libra on medium. https://medium.com/@vipinsun/libra-a-balanced-view-i-89c985c57aa8 This part is on the money supply and governance; will dig further into the

> Itwould be better to call these "points of contact", as to notconfuse it with a decision-making capability. > Within some of the projects, wehave a team of long-term maintainers for decision making,

Examples of similar roles at other OSS projects: TPL or PTL or PLT are all terms that can be searched on for more examples of roles and additional responsibilities.

Point of contact (POC seems an overloaded, if not charged, acronym): While I can appreciate the intent here (thanks, Brian for the elaboration), it is less clear that a single point of contact, even

I think "point of contact" is fine. I'll take the blame for the word "Chair" - as we were discussing some of the issues Silona mentioned in her original email (and which we could have

I think this is the right idea. We can even generalize this system and have a project “point of contact for X” where X could be security, quarterly reporting, press releases, etc. Most (or

I want to point out that for the last two years, I have maintained a list of "security volunteers" that are "points of contact" in each project that are also on the security@... mailing list. I try