toc@lists.hyperledger.org

Downtime for updates of WIKI & JIRA

The update of JIRA (jira.hyperledger.org) has been completed. The update of WIKI (wiki.hyperledger.org) is still underway. We expect to be complete within the hour. Tim

By Tim Johnson <tijohnson@...> · #2832 ·

Hyperledger Fabric quarterly report 2020 Q1

https://wiki.hyperledger.org/x/miR6AQ Cheers, Chris

By Christopher Ferris <chris.ferris@...> · #2831 ·

TSC Agenda for Jan 23, 2030

Hi, The agenda for this week's call is online. This is still a light agendabut I don't want to cancel again so we'll just have a short call and ifanyone wants to take the opportunity to add anything,

By Arnaud Le Hors · #2830 ·

Promoted Releases vs Major Releases

Hi all, Following up onthe discussion we had on our last call in December, I have now revisedthe proposal related to the introduction of "Promoted Releases"as a replacement for the "First Major

By Arnaud Le Hors · #2829 ·

Re: [Hyperledger Technical WG China] [i18n] Status report on translation of Fabric docs

Hi, Sara! I agree with you, Transifex has good features like manage updates, but it's really inefficient, we have tried transifex for months and amlost finished Fabric 2.0 alpha translation, by the

By Yang Cheng · #2828 ·

Re: [Hyperledger Fabric] [Hyperledger Technical WG China] [i18n] Status report on translation of Fabric docs

Hi, Brain, Thanks for your replay, for now our translating work is mainly for fabric project and Chinese language, and just a dozen translators, so that the workflow is good for us now. We are also

By Yang Cheng · #2827 ·

Re: [i18n] Status report on translation of Fabric docs

Thank you for sharing the workflow. As someone who has in the past contributed to i18n for Indian languages, I can relate to how this makes it easy for a well knit group to focus on the work. I am

By sankarshan · #2826 ·

Re: [Hyperledger Technical WG China] [i18n] Status report on translation of Fabric docs

Hello everyone! In Iroha, we were also trying to figure out a new way of translating our docs – we used POEditor before but it is so bad when it comes to automation. Ry helped us with getting

By Sara Garifullina <garifullina@...> · #2825 ·

Identity Working Group zoom call Wednesday Jan 22, 2020 12 noon EST

Hi all, Announcing a call of the ID WG When: Wednesday Jan 22, 2020 12 noon EST (1700 UTC) Where: Call is on hyperledger zoom. The zoom channel is https://zoom.us/my/hyperledger.community Main

By Vipin Bharathan · #2824 ·

In Memoriam, Tamas Blummer

Hi all, Tamas Blummer, former member of Hyperledger TSC passed away on Jan 12, 2020. He had been battling cancer for the last couple of years. Tamas was elected to the TSC following the dissolution

By Vipin Bharathan · #2823 ·

Re: DCO topic

I like the idea, I think. I've forwarded it along to LF Legal for comment. I would caution against any solution that requires work on LF's product department, it's undermanned and

By Brian Behlendorf <bbehlendorf@...> · #2822 ·

Re: DCO topic

Perhaps a MOSS; Measure of Software Similarity system would work. Some open source available although they may need a good bit of additional languages added, etc. Many paid platforms available.

By bill · #2821 ·

Re: [Hyperledger Technical WG China] [i18n] Status report on translation of Fabric docs

This has gone without a reply since it was posted so I thought I would add one, It's terrific to see this energy for expanding the global footprint for Fabric! And for taking such a well researched

By Brian Behlendorf <bbehlendorf@...> · #2820 ·

Re: DCO topic

Hi Everyone, Thanks for the informative responses. I’m with Chris here—it might be time to consider a CLA model. I highly doubt the board will let us keep doing what we’ve done so far

By hmontgomery@us.fujitsu.com <hmontgomery@...> · #2819 ·

Re: DCO topic

Fabric, having moved from Gerrit (which required a LF ID) to GitHub (which does not) now opens up a bit of risk unless the maintainers reviewing patches also know who the submitter is. With Linux

By Christopher Ferris <chrisfer@...> · #2818 ·

Re: DCO topic

Thanks Brian forthe update. As a reminder, Danno laid out the problem quite nicely on thewiki: https://wiki.hyperledger.org/display/TSC/DCO+and+Pseudonyms If Legal couldgive us specific guidance on

By Arnaud Le Hors · #2817 ·

DCO topic

LF legal looked at the item and were wondering what underlying need was motivating the ask. "In the Linux kernel for example the maintainers are expected to know the identity of anyone

By Brian Behlendorf <bbehlendorf@...> · #2816 ·

Re: Call for agenda items for TSC call of Jan 16

Thanks for the reminderHart. Brian was going to bring this up to LF legal. Brian, any update? -- Arnaud Le Hors - Senior Technical Staff Member, Blockchain &Web Open Technologies - IBM From:

By Arnaud Le Hors · #2815 ·

Re: Call for agenda items for TSC call of Jan 16

Hi Everyone, Thanks for all the emails, and it’s great to hear from you all post-winter holidays. I had a question: has any progress been made on the DCO front? An email update would be

By hmontgomery@us.fujitsu.com <hmontgomery@...> · #2814 ·

Cancelled Event: Technical Steering Committee (TSC) - Thursday, 16 January 2020 #cal-cancelled

Cancelled: Technical Steering Committee (TSC) This event has been cancelled. When: Thursday, 16 January 2020 7:00am to 8:00am (UTC-08:00) America/Los

By tsc@lists.hyperledger.org Calendar <tsc@...> · #2813 ·

Messages