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

Hello TSC, We have completed the switch over of the community calendar to a community managed system using lists.hyperledger.org. The new aggregate community calendar information is

Hi Hyperledger Contributors, We hope that you'll join the next Hyperledger Developer Relations-Marketing Committee Meeting, happening Jan 15 at 9am PT. The purpose of the call is to discuss marketing

In a little over a week, the Fabric project has the first update for 2020 due. https://wiki.hyperledger.org/display/TSC/2020+TSC+Project+Update+Calendar I will be setting up the automatic reminders,

Dear Hyperledger community, We are a small group of volunteers that have been translating Fabric docs to Chinese since 2018. We’d like to share our current status and rationale behinds some

Dear Hyperledger Administrators, As reported previously, a group of volunteers from Technical Working Group China have translated Fabric 1.4 docs into Chinese, and we would like some help to

Hi all, Announcing We will have the first call of the CM SIG in the new decade on Jan 15 at 10 am EST (15:00 UTC). Wishing everyone the best. Some items have been entered into the Agenda on the

Hi Everyone, I made one last pass through the old community calendar this morning an emailed the organizers of any meetings that are still on the old Hyperledger Community Calendar that didn't have