[prev in list] [next in list] [prev in thread] [next in thread]
List: hyperledger-tsc
Subject: Re: [Hyperledger Project TSC] hyperledger-tsc Digest, Vol 23, Issue 20
From: Kyle Smitz via hyperledger-tsc <hyperledger-tsc () lists ! hyperledger ! org>
Date: 2017-12-18 17:10:56
Message-ID: 20171218171337.305C6CE3 () mail ! linuxfoundation ! org
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
[Attachment #4 (text/plain)]
I have plenty of space in Downtown DC, and I can work with Gilles Hilary over at \
Georgetown University and the DC meetup group to put something together for the 2018 \
hackfest. Kyle
Sent from my T-Mobile 4G LTE Device
-------- Original message --------From: hyperledger-tsc-request@lists.hyperledger.org \
Date: 12/18/17 11:32 AM (GMT-05:00) To: hyperledger-tsc@lists.hyperledger.org \
Subject: hyperledger-tsc Digest, Vol 23, Issue 20 Send hyperledger-tsc mailing list \
submissions to hyperledger-tsc@lists.hyperledger.org
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc
or, via email, send a message with subject or body 'help' to
hyperledger-tsc-request@lists.hyperledger.org
You can reach the person managing the list at
hyperledger-tsc-owner@lists.hyperledger.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of hyperledger-tsc digest..."
Today's Topics:
1. Minutes / December 14, 2017 (Tracy Kuhrt)
----------------------------------------------------------------------
Message: 1
Date: Mon, 18 Dec 2017 09:32:03 -0700
From: Tracy Kuhrt <tkuhrt@linuxfoundation.org>
To: hyperledger-tsc <hyperledger-tsc@lists.hyperledger.org>
Subject: [Hyperledger Project TSC] Minutes / December 14, 2017
Message-ID:
<CALdv--kA0R7wwwzP+ooNW+7JtSJE2Z+Yosv5a4JSXpww=xWYxw@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Hyperledger Project
Technical Steering Committee (TSC) Meeting
December 14, 2017 (7:00am - 8:00am PT)
via GoToMeeting
TSC Members
Arnaud Le Hors
Yes
Baohua Yang
Yes
Binh Nguyen
No
Christopher Ferris
No
Dan Middleton
Yes
Greg Haskins
No
Hart Montgomery
Yes
Jonathan Levi
No
Kelly Olson
Yes
Mic Bowman
Yes
Nathan George
Yes
DID NOT REACH QUORUM
Resources:
-
Rocket.Chat: chat.hyperledger.org (you can use your LFID to login)
-
Github: www.github.com/hyperledger
-
Wiki: https://wiki.hyperledger.org/
-
Public lists: lists.hyperledger.org
-
Information on the TSC Members can be found at
https://www.hyperledger.org/about/tsc
-
Meetings: wiki.hyperledger.org/community/calendar-public-meetings
FYI: canceling 12/28 TSC meeting since many on holiday
2018 Hackfest planning [reminder thread
<https://lists.hyperledger.org/pipermail/hyperledger-tsc/2017-December/001277.html>
]
-
February - US [TBD]
-
April - Tel Aviv, Dubai, Japan? [TBD]
-
If you have potential venue space, please reach out to
tbenzies@linuxfoundation.org or indicate interest here
<https://docs.google.com/forms/d/e/1FAIpQLSc8zLYo07XlJSzz_kYcki6eJl8E7m4i3xpZwHfOS8U3jUwEzw/viewform>
.
-
Looking to have a database of venues that will allow us to schedule
hackfests further out.
-
Dan has found space in Minneapolis
-
Baohua asked about Hackathon schedule - Don't have a regular heartbeat
for Hackathons, but are interested in hearing about any that we should be
participating in
Project Reporting
-
Hyperledger Burrow update
<https://wiki.hyperledger.org/groups/tsc/project-updates/burrow-2017-dec>
-
No representation. Move to next week's meeting.
-
Hyperledger Cello update
<https://wiki.hyperledger.org/groups/tsc/project-updates/cello-2017-dec>
-
Releasing 0.8 at the end of December
-
Three maintainers. Contributors from 7 companies + individual
contributors
-
Concern - what platforms should be supported?
-
no blanket policy within Hyperledger
-
each project decides
Hyperledger Labs
-
Proposal
<https://docs.google.com/document/d/1VbgmlIqDnUnvjxSJ5QTUBV-Qn3eA7Gduw0edjYgDXIY/edit?usp=sharing>
-
Who are the maintainers? Prefer if proposal outlined who the TSC might
want as a maintainer
-
Two levels of maintainers.
-
Each lab would have its own set of maintainers.
-
The organization would need a set of maintainers that will define
what gets into labs.
-
How much control do we want to exercise over the labs? Trying to find
a spot between the extremes of completely free for anyone to add
a project
and total control.
-
We want volunteers for the maintainers, possibly even some of the TSC
members (Arnaud volunteers)
-
What are the criteria for entering the lab? More clarity on what we want
as a lab project.
-
Out of scope of Hyperledger or Blockchain technologies
-
Is there an expectation or constraint that a project will become a
project?
-
Code/projects being built of two classes
-
Too early, but could become a project
-
Demos/sample code
-
Labs shouldn't be a precursor to incubation. Could be used for
experimentation. Could be something that comes out of Hackfest.
-
Caliper as an example - could be a good candidate for a labs project
-
Does this need to be brought to the marketing committee for brand
concerns?
-
W3C community groups provide a good model
-
Want more specificity in the document
-
Project for incubation - is there a natural inclination to put that in
labs. We don't want that to be a place of rejected projects (see Apache
Labs <http://labs.apache.org/>)
-
Maintainers have a responsibility for what is in the labs. Maintainers
will need to recruit or potentially roll up a project into the attic if
there is a project that has gone dormant
-
Who will be evaluating lab projects for security issues?
-
Ultimately the maintainers should err on the side of allowing disruptive
ideas rather than waiting for it to be beautiful
-
A/I: Arnaud to update the text for more specificity
Releasing the Fabric 1.0 Security Audit report
-
Thread
<https://lists.hyperledger.org/pipermail/hyperledger-tsc/2017-December/001290.html>
-
Have the maintainers of the Fabric signed off on the release - Leave it
up to them to approve
-
Want to be sure all items have been addressed before releasing the report
-
A/I Dave will go to the maintainers of Fabric to get approval and then
send an email notification to the TSC to get final sign off
----
Tracy Kuhrt
Community Architect, Hyperledger
The Linux Foundation
tkuhrt@linuxfoundation.org
Rocket.Chat: @tkuhrt <https://chat.hyperleger.org/direct/tkuhrt>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hyperledger.org/pipermail/hyperledger-tsc/attachments/20171218/5a52ec42/attachment.html>
------------------------------
_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@lists.hyperledger.org
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc
End of hyperledger-tsc Digest, Vol 23, Issue 20
***********************************************
[Attachment #5 (text/html)]
<html><head><meta http-equiv="Content-Type" content="text/html; \
charset=UTF-8"></head><body><div><font face="sans-serif">I have plenty of space in \
Downtown DC, and I can work with Gilles Hilary over at Georgetown University and the \
DC meetup group to put something together for the 2018 \
hackfest.</font></div><div><br></div><div>Kyle</div><div><br></div><div><br></div><div \
id="composer_signature"><div style="font-size:85%;color:#575757" dir="auto">Sent from \
my T-Mobile 4G LTE Device</div></div><div><br></div><div \
style="font-size:100%;color:#000000"><!-- originalMessage --><div>-------- Original \
message --------</div><div>From: hyperledger-tsc-request@lists.hyperledger.org \
</div><div>Date: 12/18/17 11:32 AM (GMT-05:00) </div><div>To: \
hyperledger-tsc@lists.hyperledger.org </div><div>Subject: hyperledger-tsc Digest, Vol \
23, Issue 20 </div><div><br></div></div>Send hyperledger-tsc mailing list submissions \
to<br> hyperledger-tsc@lists.hyperledger.org<br><br>To subscribe or unsubscribe via \
the World Wide Web, visit<br> https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc<br>or, \
via email, send a message with subject or body 'help' \
to<br> hyperledger-tsc-request@lists.hyperledger.org<br><br>You can reach the person \
managing the list at<br> hyperledger-tsc-owner@lists.hyperledger.org<br><br>When \
replying, please edit your Subject line so it is more specific<br>than "Re: Contents \
of hyperledger-tsc digest..."<br><br><br>Today's Topics:<br><br> 1. \
Minutes / December 14, 2017 (Tracy \
Kuhrt)<br><br><br>----------------------------------------------------------------------<br><br>Message: \
1<br>Date: Mon, 18 Dec 2017 09:32:03 -0700<br>From: Tracy Kuhrt \
<tkuhrt@linuxfoundation.org><br>To: hyperledger-tsc \
<hyperledger-tsc@lists.hyperledger.org><br>Subject: [Hyperledger Project TSC] \
Minutes / December 14, \
2017<br>Message-ID:<br> <CALdv--kA0R7wwwzP+ooNW+7JtSJE2Z+Yosv5a4JSXpww=xWYxw@mail.gmail.com><br>Content-Type: \
text/plain; charset="utf-8"<br><br>Hyperledger Project<br><br>Technical Steering \
Committee (TSC) Meeting<br><br>December 14, 2017 (7:00am - 8:00am PT)<br><br>via \
GoToMeeting<br><br>TSC Members<br><br>Arnaud Le Hors<br><br>Yes<br><br>Baohua \
Yang<br><br>Yes<br><br>Binh Nguyen<br><br>No<br><br>Christopher \
Ferris<br><br>No<br><br>Dan Middleton<br><br>Yes<br><br>Greg \
Haskins<br><br>No<br><br>Hart Montgomery<br><br>Yes<br><br>Jonathan \
Levi<br><br>No<br><br>Kelly Olson<br><br>Yes<br><br>Mic \
Bowman<br><br>Yes<br><br>Nathan George<br><br>Yes<br><br>DID NOT REACH \
QUORUM<br><br>Resources:<br><br> -<br><br> Rocket.Chat: \
chat.hyperledger.org (you can use your LFID to login)<br> \
-<br><br> Github: www.github.com/hyperledger<br> \
-<br><br> Wiki: https://wiki.hyperledger.org/<br> \
-<br><br> Public lists: lists.hyperledger.org<br> \
-<br><br> Information on the TSC Members can be found at<br> \
https://www.hyperledger.org/about/tsc<br> -<br><br> \
Meetings: wiki.hyperledger.org/community/calendar-public-meetings<br><br><br>FYI: \
canceling 12/28 TSC meeting since many on holiday<br><br>2018 Hackfest planning \
[reminder thread<br><https://lists.hyperledger.org/pipermail/hyperledger-tsc/2017-December/001277.html><br>]<br><br> \
-<br><br> February - US [TBD]<br> -<br><br> April \
- Tel Aviv, Dubai, Japan? [TBD]<br> -<br><br> If you have \
potential venue space, please reach out to<br> \
tbenzies@linuxfoundation.org or indicate interest here<br> \
<https://docs.google.com/forms/d/e/1FAIpQLSc8zLYo07XlJSzz_kYcki6eJl8E7m4i3xpZwHfOS8U3jUwEzw/viewform><br> \
.<br> -<br><br> Looking to have a database of venues that \
will allow us to schedule<br> hackfests further out.<br> \
-<br><br> Dan has found space in Minneapolis<br> \
-<br><br> Baohua asked about Hackathon schedule - Don't have a regular \
heartbeat<br> for Hackathons, but are interested in hearing about any \
that we should be<br> participating in<br><br><br>Project \
Reporting<br><br> -<br><br> Hyperledger Burrow \
update<br> \
<https://wiki.hyperledger.org/groups/tsc/project-updates/burrow-2017-dec><br> \
-<br><br> No representation. Move to next week's \
meeting.<br> -<br><br> Hyperledger Cello \
update<br> \
<https://wiki.hyperledger.org/groups/tsc/project-updates/cello-2017-dec><br> \
-<br><br> Releasing 0.8 at the end of \
December<br> -<br><br> \
Three maintainers. Contributors from 7 companies + \
individual<br> \
contributors<br> \
-<br><br> Concern - what platforms should be \
supported?<br> \
-<br><br> no blanket policy within \
Hyperledger<br> \
-<br><br> each project \
decides<br><br><br>Hyperledger Labs<br><br> -<br><br> \
Proposal<br> \
<https://docs.google.com/document/d/1VbgmlIqDnUnvjxSJ5QTUBV-Qn3eA7Gduw0edjYgDXIY/edit?usp=sharing><br> \
-<br><br> Who are the maintainers? Prefer if proposal outlined who the \
TSC might<br> want as a maintainer<br> \
-<br><br> Two levels of \
maintainers.<br> \
-<br><br> Each lab would have its own \
set of maintainers.<br> \
-<br><br> The organization would need \
a set of maintainers that will \
define<br> what gets into \
labs.<br> \
-<br><br> How much control do we want to exercise over \
the labs? Trying to find<br> a spot between the \
extremes of completely free for anyone to add<br>a \
project<br> and total \
control.<br> -<br><br> We \
want volunteers for the maintainers, possibly even some of the \
TSC<br> members (Arnaud \
volunteers)<br> -<br><br> What are the \
criteria for entering the lab? More clarity on what we want<br> as a lab \
project.<br> -<br><br> Out of scope of \
Hyperledger or Blockchain technologies<br> \
-<br><br> Is there an expectation or constraint that a project will \
become a<br> project?<br> \
-<br><br> Code/projects being built of two \
classes<br> \
-<br><br> Too early, but could become \
a project<br> \
-<br><br> Demos/sample \
code<br> \
-<br><br> Labs shouldn't be a precursor to incubation. \
Could be used for<br> experimentation. Could be \
something that comes out of Hackfest.<br> \
-<br><br> Caliper as an example - could be a good candidate for a labs \
project<br> -<br><br> Does this need to be brought to the \
marketing committee for brand<br> concerns?<br> \
-<br><br> W3C community groups provide a good model<br> \
-<br><br> Want more specificity in the document<br> \
-<br><br> Project for incubation - is there a natural inclination to put \
that in<br> labs. We don't want that to be a place of rejected projects \
(see Apache<br> Labs <http://labs.apache.org/>)<br> \
-<br><br> Maintainers have a responsibility for what is in the labs. \
Maintainers<br> will need to recruit or potentially roll up a project \
into the attic if<br> there is a project that has gone \
dormant<br> -<br><br> Who will be evaluating lab projects for \
security issues?<br> -<br><br> Ultimately the maintainers \
should err on the side of allowing disruptive<br> ideas rather than \
waiting for it to be beautiful<br> -<br><br> A/I: Arnaud to \
update the text for more specificity<br><br><br>Releasing the Fabric 1.0 Security \
Audit report<br><br> -<br><br> Thread<br> \
<https://lists.hyperledger.org/pipermail/hyperledger-tsc/2017-December/001290.html><br> \
-<br><br> Have the maintainers of the Fabric signed off on the release - \
Leave it<br> up to them to approve<br> -<br><br> \
Want to be sure all items have been addressed before releasing the \
report<br> -<br><br> A/I Dave will go to the maintainers of \
Fabric to get approval and then<br> send an email notification to the TSC \
to get final sign off<br><br>----<br><br>Tracy Kuhrt<br>Community Architect, \
Hyperledger<br>The Linux Foundation<br>tkuhrt@linuxfoundation.org<br>Rocket.Chat: \
@tkuhrt <https://chat.hyperleger.org/direct/tkuhrt><br>-------------- next part \
--------------<br>An HTML attachment was scrubbed...<br>URL: \
<http://lists.hyperledger.org/pipermail/hyperledger-tsc/attachments/20171218/5a52ec \
42/attachment.html><br><br>------------------------------<br><br>_______________________________________________<br>hyperledger-tsc \
mailing list<br>hyperledger-tsc@lists.hyperledger.org<br>https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc<br><br><br>End \
of hyperledger-tsc Digest, Vol 23, Issue \
20<br>***********************************************<br></body></html>
_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@lists.hyperledger.org
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic