I'm cc'ing the TSC, as I think this is something that affects the technical efforts project-wide, and should be decided as an HL standard (or at least intend towards one). Follow-ups

Maintenance is now completed -- Anton Baranov Systems and Network Administrator The Linux Foundation

The work will be starting in 10 minutes. -- Anton Baranov Systems and Network Administrator The Linux Foundation

There were several indications of support and no veto to the ideal of cancelling tomorrow's meeting, so let's consider it confirmed. See you all next Thursday. Brian -- Brian Behlendorf Executive

Given half of us are here at the hackfest and talking about some of these issues, and then travelling on Thursday, Chris F and I would like to propose cancelling Thursday's call. There were a number

When: Saturday , July 30, 2016 at 08:00AM - 10:00AM PT (15:00 - 17:00 UTC) What: All Hyperledger services Why: Monthly security and service udpates Impact: Services will be temporarily unavailable

+1 Cheers, Christopher Ferris IBM Distinguished Engineer, CTO Open Technology IBM Cloud, Open Technologies email: chrisfer@... twitter: @christo4ferris blog:

Hi folks, Since many of us are in transit on Monday, I am moving our 10am EDT Monday meeting to Tuesday morning f2f in San Francisco. I haven't seen any specific agenda requests this week, so I would

(This will be the last of these announcements posted to multiple email lists. If you want to see these announcements, please subscribe to the <hyperledger-announce@...> email list) A reminder that our

Hyperledger Project Technical Steering Committee (TSC) Meeting July 21, 2016 (7:00am - 8:30am PT) via GoToMeeting TSC Members Emmanuel Viale Accenture Ajit Krishnamohan Airbus Yes Stan

Chris/Todd, I don’t see my email address in the contributor’s list. I oversee the development/contribute/guide/review of java chain code from DTCC. I also came up with hyperledger

Action Item Review Hackfest preparation and updates (Todd) July 26-27, San Francisco register / agenda (draft) August 24-25, virtual (confirmed) October 3-4, Amsterdam (tentative) Take table and

As requested, Bill Sparks and I have spoken offline on the fit-for-what-purpose challenge. We wrote up some thoughts on an risk-assessment-based

Per my action items I renamed the "Mature"state to "Active" in the Project Lifecycle document, I cleanedup the Incubation criteria draft, and moved Jeremy's and Rick's contentto a new doc: Updated

If you are planning on attending the Hyperledger Project July Hackathon in San Francisco, please be sure to register now at https://www.regonline.com/hyperledgerhackfestjuly2016. -- Todd

Hyperledger Project Technical Steering Committee (TSC) Meeting July 14, 2016 (7:00am - 8:30am PT) via GoToMeeting TSC Members Emmanuel Viale Accenture Ajit Krishnamohan Airbus Yes Stan

Agreed on driving towards a common API. Yes, there could be different plugins at the UI for chaincode vs transaction families, but I think that other aspects might be shared... eg throughput rate,

Yes, that makes sense. There are probably some core common elements to be queried like /block/<id> and /transaction/<id>. Beyond elements like that, as the architectures differ so too would a UI.

Hi TSC-ers! Just one more ping to see if anyone's interested in this, I've not heard back. I realize we're all busy but I know some of us are either in or could make a quick hop to London, and

Yes to a "Hyperledger Blockchain Explorer" project, with three products under their scope (I don't know if that has to mean "three repositories" - seems like one repo per project is