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

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

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

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

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

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.

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

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

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

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

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

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:

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

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

All right, let'scancel the call this week again but, please, let's make sure we make progressfor next week. Chris, I willtake over the issue on promoted release, so you can focus on trying tomake

Yeah, I've been tied up in an offsite and haven't been able to make any progress on my actions (including the Fabric report). Apologies. Cheers, Christopher Ferris IBM Fellow, CTO Open

so no meeting?

Thanks Dan for yourinput. The thing is thatwe do have owners for the open issues. Chris is leading the repo structureTF, and volunteered to make a clean proposal on the promoted release one.Silona

I have added a couple DCI announcements, but these announcements do not warrant a meeting. DCI: The DCI survey has incorporated edits from the fall review. HL marketing suggests it launch ahead of the

Hi all, I'd rather notcancel this week's call but I can't say that I've seen much evidence ofprogress on the open issues. So, I'm hereby inviting everyone to chimein on what the agenda should cover