Re: [Hyperledger Project TSC] Agenda for July 21, 2016

Pardha Vishnumolakala



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 explorer  and had Konrad work on the concept. In other words, I am actively contributing to Hyperledger. I also had a minor commit..  My id is psaradhi@...






From: hyperledger-tsc-bounces@... [mailto:hyperledger-tsc-bounces@...] On Behalf Of Todd Benzies via hyperledger-tsc
Sent: Wednesday, July 20, 2016 8:21 PM
To: hyperledger-tsc@...
Subject: [Hyperledger Project TSC] Agenda for July 21, 2016


·  Action Item Review

o Hackfest preparation and updates (Todd)

§ July 26-27, San Francisco register / agenda (draft)

§ August 24-25, virtual (confirmed)

§ October 3-4, Amsterdam (tentative)

o Take table and Bill’s proposal and consolidate into doc to talk about maturity of software itself (Arnaud)


§ Jeremy/Bill doc:

o Adjust exit criteria using term “active” and bring forward for approval next week (Arnaud)

o Update Project Lifecycle and other reference documents to use term “Active” (Arnaud)

o Review Hyperledger Release Taxonomy v0.1 and look at semver (Brian)

o Review “contributor” list in preparation for the TSC election (Todd)

§ Election timeline

§ Contributor list (if you are not on this list, but should be, please email tbenzies@...)

o Revise Hyperledger Explorer proposal and bring back to the TSC next week for review/approval. (Chris)

·  WG Updates

o Requirements WG (Oleg Abdrashitov)

o Architecture WG (Ram Jagadeesan)

o Whitepaper WG (Dave Voell)

o Identity WG (Christopher Allen)

o CI WG (Chris Ferris)



Todd Benzies

Senior Program Manager

The Linux Foundation
+1 (415) 412-0310 (m)

Skype: tbenzies

DTCC DISCLAIMER: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error, please notify us immediately and delete the email and any attachments from your system. The recipient should check this email and any attachments for the presence of viruses.  The company accepts no liability for any damage caused by any virus transmitted by this email.

Join to automatically receive all group messages.