@Silas and @Silona These are great points and great help, thank you! I will definitely update my proposal on the wiki to include the feedback. Many of the research topics you mentioned are of great

Ooops the new wiki form's checklist got converted to Bullets. Dan wasn't there but everyone else was. -- Silona Bonewald VP of Community Architecture, Hyperledger Mobile/Text:

January 24, 2019 (7:00am - 8:00am PT) via Zoom TSC Members Present? Arnaud Le Hors Baohua Yang Binh Nguyen Christopher Ferris Dan Middleton Hart Montgomery Kelly Olson Mark Wagner Mic Bowman Nathan

Could I ask any interested party to edit this page and add requirements? https://wiki2.hyperledger.org/pages/viewpage.action?pageId=2393810 I think it would be better for SNR if I wasn't filtering

Sofia, we will adding you to the agenda for next Thursday. You might want to update your proposal on the wiki as you receive feedback from this list. Here's the page for everyone's

If you would like to propose a Workgroup, our process is outlined here. Be sure to incorporate the advice given here in this thread :-)

That would be good Dan.... I was just looking at the Ergo compiler today in fact :)

Sound good Silas. I’d be happy to contribute and to represent Accord Project. Dan -- Dan Selman CTO Email: dan@... Mobile: +44 7785-792717 clause.io This message is confidential and its

Hi Sofia, I took a look at your proposal. My immediate reaction to the idea of a smart contracts working group is that it is a good idea. Smart contracts are the thing that attracted me to blockchain

+1. We definitely need to be in charge of pipeline settings, as it is in our interests to provide a reasonable quality gate for the project. Nikolai

not away from Jenkins, but away from use of Jenkins pipelines. We are currently in the process of transitioning from using JJBs to pipelines. JJB are specific configs to jenkins, where as pipelines

Thanks Chris, >> Seems to me that the process for a build should be in the control of the project's maintainers, not LFIT. ^^^ I agree and I used to believe that this was indeed the case. I see.

Reading the linked note from Ry, it seems that this has little to do with CI/CD and more to do with LFIT process and policies. Opaque process for adding new projects to Jenkins Opaque

Hello, I have made a proposal for the smart contracts working group and send an email before a couple of days. I wanted to know if there is going to be a meeting tomorrow in order to present it to

Adding the HL Fabric team, in case there are new issues that I was not aware of. Jonathan Levi HACERA - To Blockchain with Confidence https://hacera.com

Hi everybody, This is really great - thanks. 1. Just to confirm, the issues with the Fabric CI/CD were resolved (at least the stuff I have expressed in the quotes thread, well before the latest HL

Nikolai, Great. I look forward to working with you to make Hyperledger's Jenkins useful to the broader community. Ry-- Ry Jones Community Architect, Hyperledger Chat: @ry

Hi Ry! In HL Iroha we also heavily use Jenkins. We would love to contribute to the process, I cc’ed our DevOps engineers to the thread. Nikolai Project manager at Soramitsu

Last year, there was a thread expressing frustration with the Hyperledger CI/CD process as it exists. This morning, I heard from the Ursa team that this is still an issue. I have created a very bare

Announcement: Internships for 2019 Discussion: APAC bootcamp, Hong Kong, March 7-8 Maintainers Summit ODPi TSC's request surrounding Big Data, AI, and Blockchain Quarterly updates: Hyperledger