Identity WG Meeting Notes
Vipin Bharathan
Hi all, Notes from April 17th Identity WG call are available All Videos/Audio/ links and links to Agenda and a precis can be found. You can also go down the rabbit hole of the hyperlinks to explore the DiD and Agent 2 Agent Communication as well. Feedback, questions etc. are welcome. Best, Vipin
|
|
Re: Transact Project Proposal
Brian Behlendorf
I'm super excited about this, as I've
long hoped for a intermediate layer between DLT and smart
contracts that might allow better componentization within HL as a
whole. And I'm happy to see the very thoughtful description of
how this would relate to other Hyperledger projects, both planned
and possible. It'd be great to hear on-list or as comments to the
proposal from devs involved in these other projects, and people
thinking about other smart contract engines (like DAML) that could
be plugged in. Very happy to see Gari's name on the proposal as a
sponsor, and hope this indicates a willingness from the Fabric
team to spend more time with this.
Brian
On 4/17/19 6:21 PM, Shawn Amundson
wrote:
-- Brian Behlendorf Executive Director, Hyperledger bbehlendorf@... Twitter: @brianbehlendorf
|
|
Seeking volunteers for the CI/CD Committee
Dave Huseby <dhuseby@...>
Hi TSC, In light of this morning's TSC call, I would like to extend the invitation to everybody to join the CI/CD committee. If you would like to join, just reply to this email or email me at dhuseby at linuxfoundation.org and I will add you to the list. Q: What is the CI/CD committee and what are we trying to accomplish? A: The CI/CD committee is gathering all of the CI/CD requirements for the HL projects and creating a recommendation for a solution that meets everybody's requirements so that we can unify and streamline the CI/CD system HL projects use. Q: What is expected of the committee members? A: We meet weekly on Fridays to give updates and discuss next steps. We will be studying each team's CI/CD setup and working with the teams to get requirements they must have and features/capabilities they would like to have. In the end we'll be writing a document that outlines the common requirements and themes and then make recommendations for a possible solution by the end of June. Dave
|
|
Transact Project Proposal
Shawn Amundson
I'm happy to extend this proposal to the TSC for future consideration on behalf of its sponsors: Please provide feedback to help us enhance this proposal! Thanks, -Shawn
|
|
project readiness not ready for discussion
Dave Huseby <dhuseby@...>
Hi TSC, I've been working on trying to come up with a coherent checklist with descriptions for all of the areas of concern that make a project "ready" and how we measure that in each stage of the project lifecycle. I'm not quite ready to present it but I plan on sending it out to the TSC tomorrow or Friday for discussion ahead of next week's call. My main focus is to identify the roles of the people involved in an open source project and also take the different stages we've already identified and then describe the primary concerns for a project to be "ready" at each stage and how the expectations for the people in each role at each stage. I'm weaving in the already "blessed" documents that the TSC has already approved for the exit criteria by using them as the minimum set of goals for a project to accomplish in each stage of their life cycle. If you have any thoughts on things you'd like to see me include in this report, reply to this email and let me know. The draft I send out will be just the first iteration and I'm hoping that it will undergo several cycles of revisions until we get to something that outlines exactly what we should be looking for and measuring with analytics as well as the cultural goals of a project that contribute to project health and resiliency. So no project readiness in tomorrow's TSC call but look for the initial draft of the report soon. Dave
|
|
Re: [Hyperledger Performance and Scale WG] [Hyperledger TSC] some thoughts on the future of the PSWG
Dan Hyperledger
With respect to PSWG specifically, I think the most significant thing that working group can do is mature our ability to quantify integrity and availability. The thing that makes blockchain different from other enterprise transaction systems is the use of decentralization in protecting the integrity and availability of the system. The first output of the PSWG was a metrics document that made strides in measuring performance in that context. What does it mean if a network can execute 1000 TPS but can be taken down by a single node failure? The best we could do was be clear that performance should always be published in the context of the size of the network (as a proxy for a measure of availability and integrity). We had a lot of discussion about measurements in the presence of faults. We even had some material started by a few of our contributors and while it wasn’t a fit for that draft of the metrics document, it seemed like a good seed for the next round of work. A different direction of exploration is in workload design. In this case contributors from companies adopting blockchain are invaluable to help inform actual workload characteristics. One reason I don’t list benchmark design with higher importance is I believe it’s better developed by an organization like TPC. Regards, Dan Middleton
On Tue, Mar 19, 2019 at 7:44 AM Vipin Bharathan <vipinsun@...> wrote:
|
|
Hyperledger Identity WG Quarterly Update Due #tsc-wg-update - Thu, 04/18/2019
#tsc-wg-update
#cal-reminder
tsc@lists.hyperledger.org Calendar <tsc@...>
Reminder: When: Organizer: Description:
|
|
Hyperledger Iroha Quarterly Update Due #tsc-project-update - Thu, 04/18/2019
#tsc-project-update
#cal-reminder
tsc@lists.hyperledger.org Calendar <tsc@...>
Reminder: When: Organizer: Description:
|
|
Re: DAML open sourcing!
Dan O'Prey <dan@...>
FYI, exciting announcement today: Hyperledger related news coming soon... ![]() 4 World Trade Center 150 Greenwich Street, 47th Floor New York, NY 10007, USA digitalasset.com On Thu, Apr 11, 2019 at 9:40 AM Dan O'Prey via Lists.Hyperledger.Org <dan=digitalasset.com@...> wrote:
This message, and any attachments, is for the intended recipient(s) only, may contain information that is privileged, confidential and/or proprietary and subject to important terms and conditions available at http://www.digitalasset.
|
|
Re: DAML open sourcing!
Dan O'Prey <dan@...>
Awesome! Is indeed: https://github.com/digital-asset/daml Dan O'Prey Chief Marketing Officer c: +1 6464680213 e: dan@... Digital Asset Digital Asset Holdings, LLC 96 Spring Street, 7th Floor New York, NY 10012 digitalasset.com On Thu, Apr 11, 2019, 09:38 Silas Davis <silas@...> wrote:
This message, and any attachments, is for the intended recipient(s) only, may contain information that is privileged, confidential and/or proprietary and subject to important terms and conditions available at http://www.digitalasset.
|
|
Re: DAML open sourcing!
Silas Davis
We are collating survey document for smart contract languages for the Smart Contacts WG. I will include DAML. Is there a public source code repo? I'd be interested to look at the compiler/interpreter machinery. Silas
|
|
Agenda for TSC call 11 APR 2019
https://wiki.hyperledger.org/display/HYP/2019+04+11+TSC+Agenda Please note: there are three updates to review (Sawtooth, Fabric, Architecture WG)
|
|
Re: Hyperledger Sawtooth Quarterly Update Due #tsc-project-update - Thu, 04/11/2019
#cal-reminder
#tsc-project-update
Andrea Gunderson
The update has been posted. Apologies for the late upload.
|
|
Hyperledger Sawtooth Quarterly Update Due #tsc-project-update - Thu, 04/11/2019
#cal-reminder
#tsc-project-update
tsc@lists.hyperledger.org Calendar <tsc@...>
Reminder: When: Organizer: Description:
|
|
Hyperledger Architecture WG Quarterly Update Due #tsc-wg-update - Thu, 04/11/2019
#tsc-wg-update
#cal-reminder
tsc@lists.hyperledger.org Calendar <tsc@...>
Reminder: When: Organizer: Description:
|
|
Re: DAML open sourcing!
Dan O'Prey <dan@...>
Hi all, Vipin, thanks for sharing here and very happy to discuss. As noted in the Coindesk article yesterday, we are very keen for DAML to work on the various Hyperledger frameworks in particular, but also integrate with tools and provide libraries. The open sourcing of DAML was only step 1. We very much welcome, and are proactively working on and releasing tools that will enable, integration with Hyperledger projects (more on that soon). As Brian noted, it's important first of all that the project is open source, under a compatible license, is reviewable, and we can demonstrate a community around the project with multivendor interest in it. It's also very important to me that it's not a standalone project under the umbrella and fits within the suite of Hyperledger projects by adding value to what's already there, so that is step 2. As of now, we are not formally submitting a project proposal to the TSC for consideration for DAML itself, but are working on how we can achieve the kind of characteristics that make an open source project valuable to be contributed; namely ongoing maintenance and community interaction, integration with other projects already under the umbrella (and outside), and diversity of contributions. We very much welcome anyone willing to support these goals. The code is available under Apache 2.0 here and we have an open slack org here for any discussions. Also happy to discuss over email, copying the core members of our team if any further questions. ![]() 4 World Trade Center 150 Greenwich Street, 47th Floor New York, NY 10007, USA digitalasset.com On Thu, Apr 4, 2019 at 7:32 PM Brian Behlendorf <bbehlendorf@...> wrote:
This message, and any attachments, is for the intended recipient(s) only, may contain information that is privileged, confidential and/or proprietary and subject to important terms and conditions available at http://www.digitalasset.
|
|
Re: DAML open sourcing!
Brian Behlendorf
We are of course happy to see this too.
I'll let Chris Clason or Dan O'Prey chime in if they want to
answer your question, but they know the pathway in is through a
project proposal to the TSC, and that the TSC has in the past
expressed a preference for proposals where the code is already
open sourced, so it can be more easily reviewed and vetted for
license compliance and other atttributes.
Brian
On 4/4/19 9:10 AM, Vipin Bharathan
wrote:
-- Brian Behlendorf Executive Director, Hyperledger bbehlendorf@... Twitter: @brianbehlendorf
|
|
DAML open sourcing!
Vipin Bharathan
Hi all, Now that DA has open sourced DAML under Apache 2.0, will we see a natural way back into HL codebase for DA? We did start HL hackathon by putting together the front end of DA with Open Blockchain. The name Hyperledger was also donated by DA. Of course kudos to DA & Dan O'Prey for this effort and of course continuing to lead the HL Marketing committee. Open sourcing of DAML will close the circle and bring a valuable tool that can be integrated into any of the DLTs in HL. Great news, Vipin
|
|
Re: Documentation Multi-Language Support Proposal
Christopher Ferris <chris.ferris@...>
Thanks, Rich!
On Thu, Apr 4, 2019 at 2:40 AM Zhenhua Zhao <zhao.zhenhua@...> wrote:
|
|
Documentation Multi-Language Support Proposal
Zhenhua Zhao <zhao.zhenhua@...>
Dear TSC members, This is Zhenhua Zhao from Technical Working Group China. Hyperledger projects uses English as primary documentation language. If supporting other languages, it can benefit a lot of hyperledger users, contributors. Fabric, Iroha, Sawtooth, Indy uses Sphinx to manage documentation and use readthedocs.io to host documentation. For those projects, it is very easy to support multiple languages. I have a proposal here for you review. In my proposal, an online translating tool http://transifex.com used, it is a paid tool, but it can be easily replaced with other tool, or offline text editor. My proposal is at https://docs.google.com/document/d/1lOF9kxjN4hK0b4YzlEVsHO8BcB2BjA3CMSemkfdDTdM/edit?usp=sharing May I kindly ask you review it and give me your feedback? Many thanks!
|
|