1. tsc@lists.hyperledger.org
   Date   
Re: [Hyperledger Project TSC] CII Badge as graduation/1.0 requirement

Richard Brown <richard@...>
 

+1

 

Richard G Brown | R3. | Chief Technology Officer

City Tower, 15th Floor, 40 Basinghall Street | London, EC2V 5DE

M: +44 7764 666821 | T: @gendal

richard@... . www.r3.com

 

 

From: <hyperledger-tsc-bounces@...> on behalf of Sheehan Anderson via hyperledger-tsc <hyperledger-tsc@...>
Reply-To: Sheehan Anderson <sranderson@...>
Date: Friday, 19 May 2017 at 03:39
To: "hyperledger-tsc@..." <hyperledger-tsc@...>
Subject: Re: [Hyperledger Project TSC] CII Badge as graduation/1.0 requirement

 

+1

 

-Sheehan

 

On Thu, May 18, 2017 at 4:09 PM, Hart Montgomery via hyperledger-tsc <hyperledger-tsc@...> wrote:

+1 from me as well.

 

Thanks Dave!

 

From: hyperledger-tsc-bounces@... [mailto:hyperledger-tsc-bounces@...] On Behalf Of David Huseby via hyperledger-tsc
Sent: Thursday, May 18, 2017 9:16 AM
To: hyperledger-tsc <hyperledger-tsc@...>
Subject: [Hyperledger Project TSC] CII Badge as graduation/1.0 requirement

 

Thank you everybody for the discussion about my proposal.  Because we lot quorum right at the last minute, the decision was made to move this discussion and vote to the mailing list.  The amended proposal is this:

 

A team seeking to graduate from incubation shall have started the CII Badge application and be nearly complete with incomplete badge requirements referenced in their graduation proposal.  100% of the applicable criteria for the CII Badge is a requirement for releasing a 1.0 of the project.  That does not mean the project must have 100% of all criteria, just 100% of the applicable criteria.  This is to allow for projects such as test harnesses, that have "N/A" answers for questions that don't offer that as an option.

 

If everybody is good with the proposal language, I ask Chris to conduct an electronic vote on including this language in the Hyperledger guidelines document and adopt this as evaluation criteria for graduation and 1.0 approval.

 

Dave

 


---
David Huseby
Security Maven, Hyperledger
The Linux Foundation
+1-206-234-2392
dhuseby@...
Skype: dwhuseby


_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@...
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc

 

www.r3.com/email-disclaimer

Re: [Hyperledger Project TSC] CII Badge as graduation/1.0 requirement

Sheehan Anderson
 

+1

-Sheehan

On Thu, May 18, 2017 at 4:09 PM, Hart Montgomery via hyperledger-tsc <hyperledger-tsc@...> wrote:

+1 from me as well.

 

Thanks Dave!

 

From: hyperledger-tsc-bounces@lists.hyperledger.org [mailto:hyperledger-tsc-bounces@...] On Behalf Of David Huseby via hyperledger-tsc
Sent: Thursday, May 18, 2017 9:16 AM
To: hyperledger-tsc <hyperledger-tsc@lists.hyperledger.org>
Subject: [Hyperledger Project TSC] CII Badge as graduation/1.0 requirement

 

Thank you everybody for the discussion about my proposal.  Because we lot quorum right at the last minute, the decision was made to move this discussion and vote to the mailing list.  The amended proposal is this:

 

A team seeking to graduate from incubation shall have started the CII Badge application and be nearly complete with incomplete badge requirements referenced in their graduation proposal.  100% of the applicable criteria for the CII Badge is a requirement for releasing a 1.0 of the project.  That does not mean the project must have 100% of all criteria, just 100% of the applicable criteria.  This is to allow for projects such as test harnesses, that have "N/A" answers for questions that don't offer that as an option.

 

If everybody is good with the proposal language, I ask Chris to conduct an electronic vote on including this language in the Hyperledger guidelines document and adopt this as evaluation criteria for graduation and 1.0 approval.

 

Dave

 


---
David Huseby
Security Maven, Hyperledger
The Linux Foundation
+1-206-234-2392
dhuseby@...
Skype: dwhuseby


_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@lists.hyperledger.org
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc
Re: [Hyperledger Project TSC] CII Badge as graduation/1.0 requirement

Hart Montgomery
 

+1 from me as well.

 

Thanks Dave!

 

From: hyperledger-tsc-bounces@... [mailto:hyperledger-tsc-bounces@...] On Behalf Of David Huseby via hyperledger-tsc
Sent: Thursday, May 18, 2017 9:16 AM
To: hyperledger-tsc <hyperledger-tsc@...>
Subject: [Hyperledger Project TSC] CII Badge as graduation/1.0 requirement

 

Thank you everybody for the discussion about my proposal.  Because we lot quorum right at the last minute, the decision was made to move this discussion and vote to the mailing list.  The amended proposal is this:

 

A team seeking to graduate from incubation shall have started the CII Badge application and be nearly complete with incomplete badge requirements referenced in their graduation proposal.  100% of the applicable criteria for the CII Badge is a requirement for releasing a 1.0 of the project.  That does not mean the project must have 100% of all criteria, just 100% of the applicable criteria.  This is to allow for projects such as test harnesses, that have "N/A" answers for questions that don't offer that as an option.

 

If everybody is good with the proposal language, I ask Chris to conduct an electronic vote on including this language in the Hyperledger guidelines document and adopt this as evaluation criteria for graduation and 1.0 approval.

 

Dave

 


---
David Huseby
Security Maven, Hyperledger
The Linux Foundation
+1-206-234-2392
dhuseby@...
Skype: dwhuseby
Re: [Hyperledger Project TSC] CII Badge as graduation/1.0 requirement

Gregory Haskins <gregory.haskins@...>
 

On Thu, May 18, 2017 at 2:18 PM, Middleton, Dan <dan.middleton@intel.com> wrote:
I think the current wording of Dave's proposal recognizes that there are subjective questions in
that list. Between the Hyperledger Security Maven role and the TSC we should apply appropriate
scrutiny when it comes to "Not-applicable". I think trying to define and document that in absolute
terms for all projects apriori will be less effective than just doing an interactive review with each
project.
Fair point, Dan. I agree with this.
Re: [Hyperledger Project TSC] CII Badge as graduation/1.0 requirement

Murali Krishna Katipalli
 

+1

 

From: hyperledger-tsc-bounces@... [mailto:hyperledger-tsc-bounces@...] On Behalf Of David Huseby via hyperledger-tsc
Sent: Thursday, May 18, 2017 12:16 PM
To: hyperledger-tsc
Subject: [Hyperledger Project TSC] CII Badge as graduation/1.0 requirement

 

Thank you everybody for the discussion about my proposal.  Because we lot quorum right at the last minute, the decision was made to move this discussion and vote to the mailing list.  The amended proposal is this:

 

A team seeking to graduate from incubation shall have started the CII Badge application and be nearly complete with incomplete badge requirements referenced in their graduation proposal.  100% of the applicable criteria for the CII Badge is a requirement for releasing a 1.0 of the project.  That does not mean the project must have 100% of all criteria, just 100% of the applicable criteria.  This is to allow for projects such as test harnesses, that have "N/A" answers for questions that don't offer that as an option.

 

If everybody is good with the proposal language, I ask Chris to conduct an electronic vote on including this language in the Hyperledger guidelines document and adopt this as evaluation criteria for graduation and 1.0 approval.

 

Dave

 


---
David Huseby
Security Maven, Hyperledger
The Linux Foundation
+1-206-234-2392
dhuseby@...
Skype: dwhuseby


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.

Re: [Hyperledger Project TSC] CII Badge asgraduation/1.0requirement

Arnaud Le Hors
 

+1

I'm a strong believer in the application of proper judgement to the implementation of processes rather than blind execution. I trust that the TSC will be able to do that when it comes to dealing with the gray areas.
--
Arnaud  Le Hors - Senior Technical Staff Member, Web & Blockchain Open Technologies - IBM Cloud




From:        "Middleton,        Dan via hyperledger-tsc" <hyperledger-tsc@...>
To:        Gregory Haskins <gregory.haskins@...>, David Huseby <dhuseby@...>, "hyperledger-tsc@..." <hyperledger-tsc@...>
Cc:        "Barnes, Thomas J" <thomas.j.barnes@...>
Date:        05/18/2017 08:19 PM
Subject:        Re: [Hyperledger Project TSC] CII Badge as        graduation/1.0        requirement
Sent by:        hyperledger-tsc-bounces@...



+1 from Dan Middleton.

For those that have not been exposed to the CII badge details you can look at existing projects (here is sawtooth's:
https://bestpractices.coreinfrastructure.org/projects/954, for example.)

Tom might be updating this imminently based on Dave's feedback during today's TSC meeting. At the moment, however, you can see where Tom was conservative in his answers to subjective questions like "All medium and high severity exploitable vulnerabilities discovered with static code analysis MUST be fixed in a timely way after they are confirmed."

I think the current wording of Dave's proposal recognizes that there are subjective questions in that list. Between the Hyperledger Security Maven role and the TSC we should apply appropriate scrutiny when it comes to "Not-applicable". I think trying to define and document that in absolute terms for all projects apriori will be less effective than just doing an interactive review with each project.

Regards,
Dan


-----Original Message-----
From: hyperledger-tsc-bounces@... [mailto:hyperledger-tsc-bounces@...] On Behalf Of Gregory Haskins via hyperledger-tsc
Sent: Thursday, May 18, 2017 13:21
To: David Huseby <dhuseby@...>
Cc: hyperledger-tsc <hyperledger-tsc@...>
Subject: Re: [Hyperledger Project TSC] CII Badge as graduation/1.0 requirement

I don't really have a full understanding of what it entails to be CII compliant yet.  With that caveat, this kind of formally/neutrally defined criteria and evaluation mechanism sounds like a reasonable condition for acceptance to me.  I do think we should strive to classify, in advance, the rules in which we decide "applicable criteria" for a given type of proposal where possible so as to avoid the perception that the community is applying the rules unfairly.

+2 from me.

On Thu, May 18, 2017 at 12:15 PM, David Huseby via hyperledger-tsc <hyperledger-tsc@...> wrote:
> Thank you everybody for the discussion about my proposal.  Because we
> lot quorum right at the last minute, the decision was made to move
> this discussion and vote to the mailing list.  The amended proposal is this:
>
> A team seeking to graduate from incubation shall have started the CII
> Badge application and be nearly complete with incomplete badge
> requirements referenced in their graduation proposal.  100% of the
> applicable criteria for the CII Badge is a requirement for releasing a
> 1.0 of the project.  That does not mean the project must have 100% of
> all criteria, just 100% of the applicable criteria.  This is to allow
> for projects such as test harnesses, that have "N/A" answers for questions that don't offer that as an option.
>
>
> If everybody is good with the proposal language, I ask Chris to
> conduct an electronic vote on including this language in the
> Hyperledger guidelines document and adopt this as evaluation criteria
> for graduation and 1.0 approval.
>
> Dave
>
>
> ---
> David Huseby
> Security Maven, Hyperledger
> The Linux Foundation
> +1-206-234-2392
> dhuseby@...
> Skype: dwhuseby
>
> _______________________________________________
> hyperledger-tsc mailing list
> hyperledger-tsc@...
> https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc
>
_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@...
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc
_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@...
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc
Re: [Hyperledger Project TSC] CII Badge as graduation/1.0 requirement

Middleton, Dan
 

+1 from Dan Middleton.

For those that have not been exposed to the CII badge details you can look at existing projects (here is sawtooth's:
https://bestpractices.coreinfrastructure.org/projects/954, for example.)

Tom might be updating this imminently based on Dave's feedback during today's TSC meeting. At the moment, however, you can see where Tom was conservative in his answers to subjective questions like "All medium and high severity exploitable vulnerabilities discovered with static code analysis MUST be fixed in a timely way after they are confirmed."

I think the current wording of Dave's proposal recognizes that there are subjective questions in that list. Between the Hyperledger Security Maven role and the TSC we should apply appropriate scrutiny when it comes to "Not-applicable". I think trying to define and document that in absolute terms for all projects apriori will be less effective than just doing an interactive review with each project.

Regards,
Dan

-----Original Message-----
From: hyperledger-tsc-bounces@lists.hyperledger.org [mailto:hyperledger-tsc-bounces@lists.hyperledger.org] On Behalf Of Gregory Haskins via hyperledger-tsc
Sent: Thursday, May 18, 2017 13:21
To: David Huseby <dhuseby@linuxfoundation.org>
Cc: hyperledger-tsc <hyperledger-tsc@lists.hyperledger.org>
Subject: Re: [Hyperledger Project TSC] CII Badge as graduation/1.0 requirement

I don't really have a full understanding of what it entails to be CII compliant yet. With that caveat, this kind of formally/neutrally defined criteria and evaluation mechanism sounds like a reasonable condition for acceptance to me. I do think we should strive to classify, in advance, the rules in which we decide "applicable criteria" for a given type of proposal where possible so as to avoid the perception that the community is applying the rules unfairly.

+2 from me.

On Thu, May 18, 2017 at 12:15 PM, David Huseby via hyperledger-tsc <hyperledger-tsc@lists.hyperledger.org> wrote:
Thank you everybody for the discussion about my proposal. Because we
lot quorum right at the last minute, the decision was made to move
this discussion and vote to the mailing list. The amended proposal is this:

A team seeking to graduate from incubation shall have started the CII
Badge application and be nearly complete with incomplete badge
requirements referenced in their graduation proposal. 100% of the
applicable criteria for the CII Badge is a requirement for releasing a
1.0 of the project. That does not mean the project must have 100% of
all criteria, just 100% of the applicable criteria. This is to allow
for projects such as test harnesses, that have "N/A" answers for questions that don't offer that as an option.


If everybody is good with the proposal language, I ask Chris to
conduct an electronic vote on including this language in the
Hyperledger guidelines document and adopt this as evaluation criteria
for graduation and 1.0 approval.

Dave


---
David Huseby
Security Maven, Hyperledger
The Linux Foundation
+1-206-234-2392
dhuseby@linuxfoundation.org
Skype: dwhuseby

_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@lists.hyperledger.org
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc
_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@lists.hyperledger.org
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc
[Hyperledger Project TSC] Minutes / May 18th, 2017

Todd Benzies <tbenzies@...>
 

Hyperledger Project

Technical Steering Committee (TSC) Meeting

May 18, 2017 (7:00am - 8:00am PT)

via GoToMeeting


TSC Members

Arnaud Le Hors


Binh Nguyen


Christopher Ferris

Yes

Dan Middleton

Yes

Greg Haskins

Yes

Hart Montgomery

Yes

Mic Bowman

Yes

Murali Krishna Katipalli

Yes

Richard Brown

Yes

Sheehan Anderson

Yes

Tamas Blummer



Resources:


Beijing Hackfest

  • June 19-20, register now / agenda (draft)

  • 30 registered as of today, highly encourage the global technical community to travel for this Hackfest


Iroha Graduation

  • Takemiya-san provided an overview of the graduation proposal for Iroha

  • Q:  Are there any metrics on what proportion of outside contributions are?  Or, any significant pieces developed by outsiders?

    • No good #s at that level, hard to quantify some of the contributions.  Some is just testing or getting ideas.

    • Of the more interesting pieces, Iroha-Scala was contributed by someone completely outside of Iroha.

  • Q:  What is the plan for handling branching in code repo as you move towards 1.0?  Release branch that just manages releases and critical security bugs?

    • Branching policy is that anything in master should be shippable.  Before that is the developer branch (mostly usable).  For actual releases (1.0) handle in separate branches as much as possible.  The current release is in master, if we do a new release, then the master gets updated as well.  Once release is stable, will release in github using releases tag.

  • Q:  Can you comment about enforcing DCO?

    • Integration with CLA hub.  If you create a pull request, it shows the different checks (namely the CLA check).  If not the case, you’ll get a red X at the pull request.

  • VOTE:  Unanimously approved.


Sawtooth Graduation

  • Dan provided an overview of the graduation proposal for Sawtooth

  • Q:  DCO check?  What tool do you verify with?

    • WIthin jenkins, when someone submits a pull request, we run the test suite against that (one of those checks is looking for sign-off on the commit message).

  • VOTE:  Unanimously approved.


CII Badge and Security Bug Handling Process

  • Security Bug Handling Process Draft

  • Dave discussed thoughts around requiring CII Badge to graduate to Active status

  • Q:  Talked about retroactively looking at Active projects for CII badging -- need to look at Fabric, Sawtooth, and Iroha.

    • Fabric is at 100%.  Iroha is at 97% (need dynamic fuzzing tool still).  Sawtooth is at 85%, should be near 100% very shortly.

  • Q:  If every project needs to set up the same tools, is there is a core infra team that could go do that?

    • Teams can lean on Hyperledger staff for help and guidance (Dave & Tracy)

  • Suggesting 95% or better for graduation; 1.0 would need to require it at 100%.

  • ACTION:  Dave to put proposal out by email for vote (no longer at quorum during the end of TSC meeting).

--
Todd Benzies
Senior Program Manager
The Linux Foundation
+1 (415) 412-0310 (m)
Skype: tbenzies
Re: [Hyperledger Project TSC] CII Badge as graduation/1.0 requirement

Mic Bowman
 

+1

 

From: hyperledger-tsc-bounces@... [mailto:hyperledger-tsc-bounces@...] On Behalf Of David Huseby via hyperledger-tsc
Sent: Thursday, May 18, 2017 9:16 AM
To: hyperledger-tsc <hyperledger-tsc@...>
Subject: [Hyperledger Project TSC] CII Badge as graduation/1.0 requirement

 

Thank you everybody for the discussion about my proposal.  Because we lot quorum right at the last minute, the decision was made to move this discussion and vote to the mailing list.  The amended proposal is this:

 

A team seeking to graduate from incubation shall have started the CII Badge application and be nearly complete with incomplete badge requirements referenced in their graduation proposal.  100% of the applicable criteria for the CII Badge is a requirement for releasing a 1.0 of the project.  That does not mean the project must have 100% of all criteria, just 100% of the applicable criteria.  This is to allow for projects such as test harnesses, that have "N/A" answers for questions that don't offer that as an option.

 

If everybody is good with the proposal language, I ask Chris to conduct an electronic vote on including this language in the Hyperledger guidelines document and adopt this as evaluation criteria for graduation and 1.0 approval.

 

Dave

 


---
David Huseby
Security Maven, Hyperledger
The Linux Foundation
+1-206-234-2392
dhuseby@...
Skype: dwhuseby
Re: [Hyperledger Project TSC] CII Badge as graduation/1.0 requirement

Gregory Haskins <gregory.haskins@...>
 

I don't really have a full understanding of what it entails to be CII
compliant yet. With that caveat, this kind of formally/neutrally
defined criteria and evaluation mechanism sounds like a reasonable
condition for acceptance to me. I do think we should strive to
classify, in advance, the rules in which we decide "applicable
criteria" for a given type of proposal where possible so as to avoid
the perception that the community is applying the rules unfairly.

+2 from me.

On Thu, May 18, 2017 at 12:15 PM, David Huseby via hyperledger-tsc
<hyperledger-tsc@lists.hyperledger.org> wrote:
Thank you everybody for the discussion about my proposal. Because we lot
quorum right at the last minute, the decision was made to move this
discussion and vote to the mailing list. The amended proposal is this:

A team seeking to graduate from incubation shall have started the CII Badge
application and be nearly complete with incomplete badge requirements
referenced in their graduation proposal. 100% of the applicable criteria
for the CII Badge is a requirement for releasing a 1.0 of the project. That
does not mean the project must have 100% of all criteria, just 100% of the
applicable criteria. This is to allow for projects such as test harnesses,
that have "N/A" answers for questions that don't offer that as an option.


If everybody is good with the proposal language, I ask Chris to conduct an
electronic vote on including this language in the Hyperledger guidelines
document and adopt this as evaluation criteria for graduation and 1.0
approval.

Dave


---
David Huseby
Security Maven, Hyperledger
The Linux Foundation
+1-206-234-2392
dhuseby@linuxfoundation.org
Skype: dwhuseby

_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@lists.hyperledger.org
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc
Re: [Hyperledger Project TSC] CII Badge as graduation/1.0 requirement

Christopher Ferris
 

approve

Chris

On May 18, 2017, at 12:15 PM, David Huseby via hyperledger-tsc <hyperledger-tsc@...> wrote:

Thank you everybody for the discussion about my proposal.  Because we lot quorum right at the last minute, the decision was made to move this discussion and vote to the mailing list.  The amended proposal is this:

A team seeking to graduate from incubation shall have started the CII Badge application and be nearly complete with incomplete badge requirements referenced in their graduation proposal.  100% of the applicable criteria for the CII Badge is a requirement for releasing a 1.0 of the project.  That does not mean the project must have 100% of all criteria, just 100% of the applicable criteria.  This is to allow for projects such as test harnesses, that have "N/A" answers for questions that don't offer that as an option.

If everybody is good with the proposal language, I ask Chris to conduct an electronic vote on including this language in the Hyperledger guidelines document and adopt this as evaluation criteria for graduation and 1.0 approval.

Dave


---
David Huseby
Security Maven, Hyperledger
The Linux Foundation
+1-206-234-2392
dhuseby@...
Skype: dwhuseby
_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@...
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc
[Hyperledger Project TSC] CII Badge as graduation/1.0 requirement

Dave Huseby
 

Thank you everybody for the discussion about my proposal.  Because we lot quorum right at the last minute, the decision was made to move this discussion and vote to the mailing list.  The amended proposal is this:

A team seeking to graduate from incubation shall have started the CII Badge application and be nearly complete with incomplete badge requirements referenced in their graduation proposal.  100% of the applicable criteria for the CII Badge is a requirement for releasing a 1.0 of the project.  That does not mean the project must have 100% of all criteria, just 100% of the applicable criteria.  This is to allow for projects such as test harnesses, that have "N/A" answers for questions that don't offer that as an option.

If everybody is good with the proposal language, I ask Chris to conduct an electronic vote on including this language in the Hyperledger guidelines document and adopt this as evaluation criteria for graduation and 1.0 approval.

Dave


---
David Huseby
Security Maven, Hyperledger
The Linux Foundation
+1-206-234-2392
dhuseby@...
Skype: dwhuseby
[Hyperledger Project TSC] Agenda for May 18, 2017

Todd Benzies <tbenzies@...>
 

--
Todd Benzies
Senior Program Manager
The Linux Foundation
+1 (415) 412-0310 (m)
Skype: tbenzies
[Hyperledger Project TSC] Identity WG call today

Vipin Bharathan
 

All,

 

Identity WG call today May 17rd at 12 EDT. Details in wiki linkhttps://wiki.hyperledger.org/groups/identity/identity-wg.

 

Paper link:

https://docs.google.com/document/d/1ExFNRx-yYoS8FnDIUX1_0UBMha9TvQkfts2kVnDc4KE/edit?usp=sharing

 

Agenda: Added updates in bold

Call for volunteers

a.       Bridge to architecture WG paper ? Nathan George 

b.      TEEs & HSMs ? Steven from Rivetz

c.       ZK proofs and CLsignatures- Jan Camenisch (already provided some feedback)-maybe something more concrete

d.      Monax-Identity Benjamin Bollen  

e.      Iroha-Link

f.        Fabric CA team to provide some input on Fabric CA

g.       STL EPR ? (End Point Registry) https://docs.google.com/document/d/1gWlbsKtgApOTm1E5XJsw2J3U6AvIRxujWiG-vm6ELOM/edit?usp=sharing EPID as identity repository. Vipin Bharathan has added some material from the introduction of the EPR into the paper.

h.      Sovrin-Identity Model- Drummond

i.          DiD->DDO model-Drummond

j.        X.509 (Version 3.0), X.525 Jonathan Levi

k.       Verifiable claims - Nathan/Sean/Drummond

l.         Sketch out Identity Interface- Vipin Bharathan

 

Unassigned : Jan VerCammen, Daniela Merella, Hugo Toledo

 

We have to recognize the fact that this is conference season and people are very busy.

 

Regards,

Vipin
[Hyperledger Project TSC] Sawtooth to active status

Middleton, Dan
 

Technical Steering Committee:

 

The Sawtooth maintainers have fulfilled the “active” criteria and request to move the project to active status.

I have documented the Sawtooth status here:

 

https://docs.google.com/document/d/1suVFsXRK9smBlh5bPs3peXiZntQFDmOwb8FogyK1N2o/edit?usp=sharing

 

Feel free to ping me with any questions or comments.

 

(Thanks for the template, Takemiya-san)

 

 

Dan Middleton
   Hyperledger Sawtooth Maintainer

 
[Hyperledger Project TSC] Request to exit incubation status for Iroha

Makoto Takemiya
 

Hello All,

We would like to formally propose to the TSC that Iroha exit
incubation status and graduate to active. Our proposal is in the
following document, so please feel free to read through it and ask any
questions you may have.

https://docs.google.com/document/d/1Vi_Ii0omj8lqjt-tdwIiEQPSku8V5DEku2aS5lr1Vo0/edit#

Sincerely,

Makoto Takemiya
[Hyperledger Project TSC] Beijing Hackfest / June 19-20 [reminder to register]

Todd Benzies <tbenzies@...>
 

Hyperledger Technical Community,

If you are planning to attend and participate, please register as soon as possible for the Hyperledger Beijing Hackfest on June 19th & 20th.

Register now:  https://www.regonline.com/hyperledgerhackfestjune2017

Also, we have started a draft agenda doc so that there is a place to add suggested topics for the Hackfest.  If there is a topic you'd like to present on, or a topic you'd like to see get discussed, please add it to the list.

Hyperledger Hackfests are regular gatherings for developers working on the different projects hosted at Hyperledger.  The primary goal for a Hackfest is to facilitate software development collaboration and knowledge sharing between participants, with an eye towards reflecting all ideas and conclusions back outward to the public open source community afterwards.  A secondary goal is to bring new contributors and passive observers up the learning curve on the different technology platforms, and the cross-cutting issues affecting multiple projects (such as identity, security, development process, etc).  Often the most useful outcome, however, is the strengthened personal relationships between the participants.  Hackfests are public meetings, anyone is welcome to attend and participate no matter what their skill level, though the discussions will presume a significant familiarity with blockchain technologies and software development concepts.

Regards,

Todd

--
Todd Benzies
Senior Program Manager
The Linux Foundation
+1 (415) 412-0310 (m)
Skype: tbenzies
Re: [Hyperledger Project TSC] Proposal: Hyperledger blockchain-monitoring 1.0

Юрий Андреев <andreevym@...>
 

Hi, Baohua Yang,
Thank you for reply

Our project isn't idea - this is stable project.

Our team has great experience (on the current moment we integrated "'blockchain-monitoring" with two customer project).

On the current moment we have:
2) Grafana have Notifications (http://docs.grafana.org/alerting/notifications/)

We will have:
0) Make online demo dashboard
1) Prometheus, and more metrics
2) "Performance dashboard"
3) Make lib for integration projects build on Node.js and Golang with monitoring
4) More responsible error
5) Users dashboard
6) Make online service for Monitoring and Notification


2017-05-13 4:28 GMT+03:00 Baohua Yang <yangbaohua@...>:

Dear andreev

Very nice to see your team also think the operational monitoring is important for a running blockchain system!

The Cello-analytics project was started several months ago as a sub-project for Hyperledger Cello. Cello-analytics targets collecting system status/logs/data, and do analytics works on it. You can also find in jira of what the team is working on.

Currently the design of the data collection is based on ELK, while i guess the influxDB one is also a good option in ur design.

Would be glad to know if there's opportunity to have any collaborations.

Pls feel free to let me know if you have any thoughts.

Thanks!

On Fri, May 12, 2017 at 8:56 AM, Юрий Андреев via hyperledger-tsc <hyperledger-tsc@lists.hyperledger.org> wrote:
HIP identifier: Hyperledger blockchain-monitoring 1.0
Sponsors: yury.andreev@..., ruslan.kryukov@...
Abstract: Fabric monitoring is a service which allows to control fabric activity like peer status, invoke and query logging, system resources usage etc.
Dependent Projects: influxDB, Grafafana: currently hyperledger fabric has no any instruments to monitor life activity, only log files.
Status: Proposal
Solution: We have created useful service to monitor fabric activity.
Effort and resources:

Proposed maintainers:
Yury Andreev (IBM)
Ruslan Kryukov (IBM)


How to: just create config file with peers addresses and run docker container
References: http://blockchain-monitoring.org/
Closure: ---           

--
Kindest regards, Yuriy Andreev

_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@...ger.org
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc




--
Best wishes!

Baohua Yang



--
Kindest regards, Yuriy Andreev
Re: [Hyperledger Project TSC] [it-infrastructure-alerts] Hyperledger: Up to one hour chat outage 13-MAY-2017 10:00 Pacific

Jordan Evans <jevans@...>
 

This work has been completed.

On Sat, May 13, 2017 at 9:54 AM, Jordan Evans <jevans@...> wrote:
This work is beginning shortly.

On Thu, May 11, 2017 at 10:30 AM, Ry Jones <rjones@...> wrote:

Property: https://chat.hyperledger.org/

Impact: there will be an outage for Chat while the update is applied

Reason: Upgrading to latest version of rocket.chat to apply fix for https://github.com/RocketChat/Rocket.Chat/issues/6675
 
Use http://www.worldtimebuddy.com/pdt-to-utc-converter to convert Pacific to your local time zone.
Re: [Hyperledger Project TSC] [it-infrastructure-alerts] Hyperledger: Up to one hour chat outage 13-MAY-2017 10:00 Pacific

Jordan Evans <jevans@...>
 

This work is beginning shortly.

On Thu, May 11, 2017 at 10:30 AM, Ry Jones <rjones@...> wrote:

Property: https://chat.hyperledger.org/

Impact: there will be an outage for Chat while the update is applied

Reason: Upgrading to latest version of rocket.chat to apply fix for https://github.com/RocketChat/Rocket.Chat/issues/6675
 
Use http://www.worldtimebuddy.com/pdt-to-utc-converter to convert Pacific to your local time zone.
2501 - 2520 of 3318