|
Re: Proposed release of the Composer security audit report
+1
By
Nathan George <nathan.george@...>
·
#2045
·
|
|
A reminder that the TSC Agenda is up
https://wiki.hyperledger.org/display/HYP/2019+02+21+TSC+Agenda
Remember to read and comment on the updates that have been posted!
For people doing check-ins tomorrow, it is expected that people have
https://wiki.hyperledger.org/display/HYP/2019+02+21+TSC+Agenda
Remember to read and comment on the updates that have been posted!
For people doing check-ins tomorrow, it is expected that people have
|
By
Silona Bonewald <sbonewald@...>
·
#2044
·
|
|
Re: Proposed release of the Composer security audit report
+1 to both.
Thanks
Binh
By
binh nguyen
·
#2043
·
|
|
Re: Proposed release of the Composer security audit report
Likewise! +1.
Thanks.
--
Arnaud Le Hors - Senior Technical Staff Member, Web & BlockchainOpen Technologies - IBM
From: "Mark Wagner"<mwagner114@...>
To: David Huseby <dhuseby@...>
Cc:
Likewise! +1.
Thanks.
--
Arnaud Le Hors - Senior Technical Staff Member, Web & BlockchainOpen Technologies - IBM
From: "Mark Wagner"<mwagner114@...>
To: David Huseby <dhuseby@...>
Cc:
|
By
Arnaud Le Hors
·
#2042
·
|
|
Proposed change in security audit report release process
Hi TSC,
I would like to propose changing the security audit report release process so that once all high and medium security vulnerabilities are resolved, the report can be published without the
Hi TSC,
I would like to propose changing the security audit report release process so that once all high and medium security vulnerabilities are resolved, the report can be published without the
|
By
Dave Huseby <dhuseby@...>
·
#2041
·
|
|
Re: Proposed release of the Composer security audit report
+1!
Thanks dave for the work!
--
Best wishes!
Baohua Yang
+1!
Thanks dave for the work!
--
Best wishes!
Baohua Yang
|
By
Baohua Yang
·
#2040
·
|
|
Re: Proposed release of the Composer security audit report
+1 to both releasing the report and proposing a change to the process.
mark
+1 to both releasing the report and proposing a change to the process.
mark
|
By
Mark Wagner
·
#2039
·
|
|
Re: Proposed release of the Composer security audit report
That's a good proposal Hart. The policy now is to ask for approval to release these but it probably should be revised to: "release them as soon as all high and medium issues are resolved and only ask
That's a good proposal Hart. The policy now is to ask for approval to release these but it probably should be revised to: "release them as soon as all high and medium issues are resolved and only ask
|
By
Dave Huseby <dhuseby@...>
·
#2038
·
|
|
Re: Proposed release of the Composer security audit report
+1
From: tsc@... [mailto:tsc@...]On Behalf Of hmontgomery@...
Sent: Tuesday, February 19, 2019 4:00 PM
To: Mic Bowman <cmickeyb@...>; Dave Huseby <dhuseby@...>
Cc: Hyperledger List
+1
From: tsc@... [mailto:tsc@...]On Behalf Of hmontgomery@...
Sent: Tuesday, February 19, 2019 4:00 PM
To: Mic Bowman <cmickeyb@...>; Dave Huseby <dhuseby@...>
Cc: Hyperledger List
|
By
Olson, Kelly M <kelly.m.olson@...>
·
#2037
·
|
|
Re: Proposed release of the Composer security audit report
+1. As usual, I’m pretty much always in favor of releasing these.
Can we automate this process? It seems like we should have some kind of policy in the vein of “release the security audits
+1. As usual, I’m pretty much always in favor of releasing these.
Can we automate this process? It seems like we should have some kind of policy in the vein of “release the security audits
|
By
hmontgomery@us.fujitsu.com <hmontgomery@...>
·
#2036
·
|
|
Re: Proposed release of the Composer security audit report
seems low risk to release.
+1
--mic
seems low risk to release.
+1
--mic
|
By
Mic Bowman
·
#2035
·
|
|
Proposed release of the Composer security audit report
Hello TSC,
The time has come for the TSC to approve the release of the Composer audit report. The Composer audit done by Nettitude found a total of five issues, 2 medium risk, 2 low risk, and 1 data
Hello TSC,
The time has come for the TSC to approve the release of the Composer audit report. The Composer audit done by Nettitude found a total of five issues, 2 medium risk, 2 low risk, and 1 data
|
By
Dave Huseby <dhuseby@...>
·
#2034
·
|
|
Hyperledger Technical WG China Quarterly Update Due #tsc-wg-update - Thu, 02/21/2019
#tsc-wg-update
#cal-reminder
Reminder:
Hyperledger Technical WG China Quarterly Update Due #tsc-wg-update
When:
Thursday, 21 February 2019
Organizer:
tkuhrt@...
Description:
The Hyperledger Technical WG China update to the TSC
Reminder:
Hyperledger Technical WG China Quarterly Update Due #tsc-wg-update
When:
Thursday, 21 February 2019
Organizer:
tkuhrt@...
Description:
The Hyperledger Technical WG China update to the TSC
|
By
tsc@lists.hyperledger.org Calendar <tsc@...>
·
#2033
·
|
|
Hyperledger Cello Quarterly Update Due #tsc-project-update - Thu, 02/21/2019
#cal-reminder
#tsc-project-update
Reminder:
Hyperledger Cello Quarterly Update Due #tsc-project-update
When:
Thursday, 21 February 2019
Organizer:
tkuhrt@...
Description:
The Hyperledger Cello update to the TSC was due February 18,
Reminder:
Hyperledger Cello Quarterly Update Due #tsc-project-update
When:
Thursday, 21 February 2019
Organizer:
tkuhrt@...
Description:
The Hyperledger Cello update to the TSC was due February 18,
|
By
tsc@lists.hyperledger.org Calendar <tsc@...>
·
#2032
·
|
|
Deadline Friday, February 22: Call for 2019 Hyperleger Internship Projects and Mentors
Dear Hyperledger Community Members,
Hyperledger is expanding the internship program to fund 15 internship projects this year. The internship program is aimed at creating a structured hands-on learning
Dear Hyperledger Community Members,
Hyperledger is expanding the internship program to fund 15 internship projects this year. The internship program is aimed at creating a structured hands-on learning
|
By
Min Yu
·
#2031
·
|
|
14 February, 2019 TSC meeting minutes
Hi Everyone,
The meeting minutes as well as the recordings of the TSC meeting on 14 February are now posted here:
https://wiki.hyperledger.org/display/HYP/2019+02+14+TSC+Minutes
Cheers!
Dave
---
David
Hi Everyone,
The meeting minutes as well as the recordings of the TSC meeting on 14 February are now posted here:
https://wiki.hyperledger.org/display/HYP/2019+02+14+TSC+Minutes
Cheers!
Dave
---
David
|
By
Dave Huseby <dhuseby@...>
·
#2030
·
|
|
Re: Agenda for TSC Valentines Day meeting is live
I am unable to attend the meeting today.
-mark
--
Mark Wagner
Senior Principal Software Engineer
Performance and Scalability
Red Hat, Inc
I am unable to attend the meeting today.
-mark
--
Mark Wagner
Senior Principal Software Engineer
Performance and Scalability
Red Hat, Inc
|
By
mark wagner <mwagner@...>
·
#2029
·
|
|
2019 Q1 Perf and Scale WG update
Distinguished Colleagues
I have published the 2019 Q1 PSWG update here https://wiki.hyperledger.org/display/HYP/2019+Q1+Performance+and+Scale+WG
I apologize for the tardiness in getting this
Distinguished Colleagues
I have published the 2019 Q1 PSWG update here https://wiki.hyperledger.org/display/HYP/2019+Q1+Performance+and+Scale+WG
I apologize for the tardiness in getting this
|
By
mark wagner <mwagner@...>
·
#2028
·
|
|
Re: [confluence] Hyperledger > Performance and Scale WG
Notice the Performance and Scale's TSC update page is up.
https://wiki.hyperledger.org/display/HYP/Performance+and+Scale+WG
TSC members please review and check your name off before the meeting on
Notice the Performance and Scale's TSC update page is up.
https://wiki.hyperledger.org/display/HYP/Performance+and+Scale+WG
TSC members please review and check your name off before the meeting on
|
By
Silona Bonewald <sbonewald@...>
·
#2027
·
|
|
Agenda for TSC Valentines Day meeting is live
https://wiki.hyperledger.org/display/HYP/2019+02+14+TSC+Agenda
Please feel free to add inline comments. Don't need to click "edit". simply highlight and wait a second and a comment button will
https://wiki.hyperledger.org/display/HYP/2019+02+14+TSC+Agenda
Please feel free to add inline comments. Don't need to click "edit". simply highlight and wait a second and a comment button will
|
By
Silona Bonewald <sbonewald@...>
·
#2026
·
|