|
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
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
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
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
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
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
·
#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.
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
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
·
#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
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
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
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
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
·
#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:
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
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
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
·
|
|
Re: Call for agenda items for TSC call of Jan 16
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
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
|
By
Arnaud Le Hors
·
#2812
·
|
|
Re: Call for agenda items for TSC call of Jan 16
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
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
|
By
Christopher Ferris <chrisfer@...>
·
#2811
·
|
|
Re: Call for agenda items for TSC call of Jan 16
so no meeting?
By
Mark Wagner
·
#2810
·
|
|
Re: Call for agenda items for TSC call of Jan 16
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
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
|
By
Arnaud Le Hors
·
#2809
·
|
|
Re: Call for agenda items for TSC call of Jan 16
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
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
|
By
Middleton, Dan <dan.middleton@...>
·
#2808
·
|
|
Call for agenda items for TSC call of Jan 16
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
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
|
By
Arnaud Le Hors
·
#2807
·
|