|
Re: Project Lifecycle taskforce
Arnaud
I'd like to help if needed.
Thanks!
--
Best wishes!
Baohua Yang
Arnaud
I'd like to help if needed.
Thanks!
--
Best wishes!
Baohua Yang
|
By
Baohua Yang
·
#2272
·
|
|
Project Lifecycle taskforce
Hi all,
I accepted last week to take the leadershipon having another look at the Project Lifecycle to try and come up witha proposal to address the gaps that have surfaced over the last
Hi all,
I accepted last week to take the leadershipon having another look at the Project Lifecycle to try and come up witha proposal to address the gaps that have surfaced over the last
|
By
Arnaud Le Hors
·
#2271
·
|
|
Upcoming Event: Hyperledger Composer Quarterly Update Due #tsc-project-update - Thu, 05/30/2019
#tsc-project-update
#cal-reminder
Reminder: Hyperledger Composer Quarterly Update Due #tsc-project-update
When: Thursday, 30 May 2019
View Event
Organizer: community-architects@...
Description: The Hyperledger Composer
Reminder: Hyperledger Composer Quarterly Update Due #tsc-project-update
When: Thursday, 30 May 2019
View Event
Organizer: community-architects@...
Description: The Hyperledger Composer
|
By
tsc@lists.hyperledger.org Calendar <tsc@...>
·
#2270
·
|
|
Re: Projects and Subprojects
Hey Dan,
Forgive our ignorance. Stickers stuck 😬
Please help us develop a basis for marginal cost for a new project.
Vipin
Hey Dan,
Forgive our ignorance. Stickers stuck 😬
Please help us develop a basis for marginal cost for a new project.
Vipin
|
By
VIPIN BHARATHAN
·
#2269
·
|
|
Re: Projects and Subprojects
I like that "stickers" is one of the top three things you guys think we do ;-P
Dan O'Prey
CMO & Head of Community
c: +1 646-647-5957
e: dan@... 
Digital Asset Holdings, LLC
4 World Trade Center
I like that "stickers" is one of the top three things you guys think we do ;-P
Dan O'Prey
CMO & Head of Community
c: +1 646-647-5957
e: dan@... 
Digital Asset Holdings, LLC
4 World Trade Center
|
By
Dan O'Prey <dan@...>
·
#2268
·
|
|
Re: Projects and Subprojects
Hi all,
It is clear that there are many sub-projects already in an informal sense. I agree with Shawn that these have to be managed and governed by the maintainers of the enveloping projects. Maybe
Hi all,
It is clear that there are many sub-projects already in an informal sense. I agree with Shawn that these have to be managed and governed by the maintainers of the enveloping projects. Maybe
|
By
Vipin Bharathan
·
#2267
·
|
|
Re: Projects and Subprojects
> Frankly, I think that before we add in any additional top level framework
> projects, we should have a good long think about the implications.
I completely agree though I would drop "framework"
> Frankly, I think that before we add in any additional top level framework
> projects, we should have a good long think about the implications.
I completely agree though I would drop "framework"
|
By
Mic Bowman
·
#2266
·
|
|
Re: Projects and Subprojects
I want to respond to one point specifically:
While this may not be a formal requirement, that is in fact what we're doing. I had a phone call yesterday with a company that is very eager to contribute
I want to respond to one point specifically:
While this may not be a formal requirement, that is in fact what we're doing. I had a phone call yesterday with a company that is very eager to contribute
|
By
Ry Jones
·
#2265
·
|
|
Re: Projects and Subprojects
Chris is right that the more mature large projects already kind of have sub-projects. In Sawtooth, we are usually careful to call them components to avoid confusion. But basically, each repo within
Chris is right that the more mature large projects already kind of have sub-projects. In Sawtooth, we are usually careful to call them components to avoid confusion. But basically, each repo within
|
By
Shawn Amundson
·
#2264
·
|
|
Re: Friday fun: Rusty python
Python is a very vigorous, and it is still evolving!--
Best wishes!
Baohua Yang
Python is a very vigorous, and it is still evolving!--
Best wishes!
Baohua Yang
|
By
Baohua Yang
·
#2263
·
|
|
Friday fun: Rusty python
I came across python like this in Indy:
defverify_multi_sig(self, signature:str, message: bytes, pks: Sequence[str]) ->bool:
[Link]
Are those types in the function parameters
I came across python like this in Indy:
defverify_multi_sig(self, signature:str, message: bytes, pks: Sequence[str]) ->bool:
[Link]
Are those types in the function parameters
|
By
Middleton, Dan <dan.middleton@...>
·
#2262
·
|
|
Re: Gid DID spec work
I forgot to add that I've been slowly writing a new signing tool called BetterSign that uses DIDDir keyrings for the identity information. It will be the first signing tool that Git will use to handle
I forgot to add that I've been slowly writing a new signing tool called BetterSign that uses DIDDir keyrings for the identity information. It will be the first signing tool that Git will use to handle
|
By
Dave Huseby <dhuseby@...>
·
#2261
·
|
|
Re: Gid DID spec work
You're right, I was confused. Now, I understand.That's pretty cool!
Thanks. :-)
--
Arnaud Le Hors - Senior Technical Staff Member, Blockchain &Web Open Technologies - IBM
From: David Huseby
You're right, I was confused. Now, I understand.That's pretty cool!
Thanks. :-)
--
Arnaud Le Hors - Senior Technical Staff Member, Blockchain &Web Open Technologies - IBM
From: David Huseby
|
By
Arnaud Le Hors
·
#2260
·
|
|
Re: Gid DID spec work
Hi Arnaud,
Thanks for poking me this morning. I think you're confused about this. This isn't *Github* this is just Git. There is a Github DID method spec and also a Facebook one that I think suffers
Hi Arnaud,
Thanks for poking me this morning. I think you're confused about this. This isn't *Github* this is just Git. There is a Github DID method spec and also a Facebook one that I think suffers
|
By
Dave Huseby <dhuseby@...>
·
#2259
·
|
|
Brasil Bootcamp - Details and Ask
Hi Everyone,
My apologies I had sound issues on the call earlier today. To recap what Daniela said, we're organizing the next bootcamp to take place in São Paulo, Brazil on June 24-25th. We are
Hi Everyone,
My apologies I had sound issues on the call earlier today. To recap what Daniela said, we're organizing the next bootcamp to take place in São Paulo, Brazil on June 24-25th. We are
|
By
Karen Ottoni
·
#2258
·
|
|
Identity WG
Hello all,
As we have had some cancellations of calls we have not had the opportunity to report on the Identity Working Group paper. We also have a backlog of presentations (see below). This is a
Hello all,
As we have had some cancellations of calls we have not had the opportunity to report on the Identity Working Group paper. We also have a backlog of presentations (see below). This is a
|
By
Vipin Bharathan
·
#2257
·
|
|
Re: Projects and Subprojects
This is a good discussion, and I am sorry I will miss the call.
I think that sub-projects is an interesting thought, but we kind of have that now, do we not?
I agree that there isn't necessarily
This is a good discussion, and I am sorry I will miss the call.
I think that sub-projects is an interesting thought, but we kind of have that now, do we not?
I agree that there isn't necessarily
|
By
Christopher Ferris <chrisfer@...>
·
#2256
·
|
|
Re: Projects and Subprojects
Thanks for putting this together Hart, the history is useful. Sorry for taking nearly 3 weeks to respond to it.
It seems like there are a few different resources that people are concerned with when
Thanks for putting this together Hart, the history is useful. Sorry for taking nearly 3 weeks to respond to it.
It seems like there are a few different resources that people are concerned with when
|
By
Silas Davis
·
#2255
·
|
|
Perf and Scale Q2 update
Sorry for the delay. The update is here :
https://wiki.hyperledger.org/display/HYP/2019+Q2+Performance+and+Scale+WG
Some stuff we should probably have a discussion on at a TSC call in a week or
Sorry for the delay. The update is here :
https://wiki.hyperledger.org/display/HYP/2019+Q2+Performance+and+Scale+WG
Some stuff we should probably have a discussion on at a TSC call in a week or
|
By
mark wagner <mwagner@...>
·
#2254
·
|
|
Re: Updated agenda for TSC call May 23, 2019
Regrets, again. (sorry) Need to cover for someone at Congressional Blockchain Caucus Smart Contracts forum tomorrow.
Chris
Regrets, again. (sorry) Need to cover for someone at Congressional Blockchain Caucus Smart Contracts forum tomorrow.
Chris
|
By
Christopher Ferris <chris.ferris@...>
·
#2253
·
|