tkuhrt (Tue, 16 Jan 2018 23:12:52 GMT):
VipinB

tkuhrt (Tue, 16 Jan 2018 23:13:12 GMT):
lehors

tkuhrt (Tue, 16 Jan 2018 23:15:32 GMT):
Hyperledger Labs (https://github.com/hyperledger-labs)

tkuhrt (Tue, 16 Jan 2018 23:15:53 GMT):
Discussion related to different Hyperledger Labs.

trbs (Tue, 16 Jan 2018 23:28:04 GMT):
Has joined the channel.

tkuhrt (Tue, 16 Jan 2018 23:53:39 GMT):
trbs

tkuhrt (Wed, 17 Jan 2018 00:51:50 GMT):
I have started to put the Wiki page together for Hyperledger Labs: https://wiki.hyperledger.org/labs. I would appreciate your input @labs-stewards

trbs (Thu, 18 Jan 2018 13:56:58 GMT):
@tkuhrt look good :thumbsup:

trbs (Thu, 18 Jan 2018 13:58:39 GMT):
Thinking we might add to the wiki something outlining how a proposal can be made.

tkuhrt (Thu, 18 Jan 2018 16:38:49 GMT):
Agree @trbs - Any thoughts?

VipinB (Thu, 18 Jan 2018 19:53:54 GMT):
Looks like there are two likely candidates 1. Cicero 2. Crypto library - nothing definite yet

trbs (Thu, 18 Jan 2018 20:28:17 GMT):
The governance part of the proposal seems relevant. (copy some of that working in the wiki page)

trbs (Thu, 18 Jan 2018 20:28:17 GMT):
The governance part of the Hyperledger Labs Proposal seems relevant. (copy some of that working in the wiki page)

trbs (Thu, 18 Jan 2018 20:28:17 GMT):
The governance part of the Hyperledger Labs Proposal seems relevant. (copy some of that wording in the wiki page)

trbs (Thu, 18 Jan 2018 20:28:17 GMT):
The governance part of the Hyperledger Labs Proposal seems relevant. We can copy some of that wording in the wiki page.

trbs (Thu, 18 Jan 2018 20:36:10 GMT):
How exactly do we want to process to work ? In governance it hints to the accepting process to go through a PR. Something like a PR or wiki page or mail to ML, so people are able to use that to publish the request to the stewards and for everybody to keep track of it..

trbs (Thu, 18 Jan 2018 20:37:56 GMT):
Talking about keeping track of things... Do we want to have some kind of status page (wiki) or document in git (could be the same repo for the PR to be filled against) or similar to keep track of the lab projects over time ? Or keeping it lightweight for now and see how that goes and only put things in place when we need it.

tkuhrt (Fri, 19 Jan 2018 02:53:07 GMT):
@trbs : does this cover what you are looking for https://wiki.hyperledger.org/labs#proposals. Happy to expand table.

SyneBlockChainTeam (Fri, 19 Jan 2018 13:59:15 GMT):
Has joined the channel.

prithveesh (Mon, 22 Jan 2018 11:45:16 GMT):
Has joined the channel.

trbs (Mon, 22 Jan 2018 12:26:21 GMT):
https://www.coindesk.com/opening-hyperledger-consortium-create-experimental-labs-startups/

rajnish (Tue, 23 Jan 2018 20:20:46 GMT):
Has joined the channel.

blockhash (Wed, 24 Jan 2018 06:46:16 GMT):
Has joined the channel.

dexhunter (Wed, 24 Jan 2018 08:52:08 GMT):
Has joined the channel.

MicBowman (Thu, 25 Jan 2018 15:40:39 GMT):
Has joined the channel.

Gaspard (Sat, 27 Jan 2018 01:09:14 GMT):
Has joined the channel.

vishwasrao (Sat, 27 Jan 2018 02:32:11 GMT):
Has joined the channel.

vishwasrao (Sat, 27 Jan 2018 02:33:19 GMT):
Hi All

vishwasrao (Sat, 27 Jan 2018 02:33:32 GMT):
This is Vishwas from India...

vishwasrao (Sat, 27 Jan 2018 02:33:53 GMT):
Would like to volunteer for Labs

nhrishi (Tue, 30 Jan 2018 12:28:00 GMT):
Has joined the channel.

gdinhof (Wed, 31 Jan 2018 14:19:54 GMT):
Has joined the channel.

knagware9 (Wed, 31 Jan 2018 14:22:20 GMT):
Has joined the channel.

richbl (Thu, 01 Feb 2018 04:14:01 GMT):
Has joined the channel.

richbl (Thu, 01 Feb 2018 04:16:00 GMT):
Hello All, Checking in from the #healthcare-wg channel. Hoping to monitor this channel for anything in the healthcare context. BTW, I'm from Seattle, WA.

jadhavajay (Thu, 01 Feb 2018 05:33:40 GMT):
Has joined the channel.

guillermo.correa (Thu, 01 Feb 2018 13:18:36 GMT):
Has joined the channel.

tkuhrt (Thu, 01 Feb 2018 16:27:10 GMT):
Welcome, @richbl and @vishwasrao

tkuhrt (Thu, 01 Feb 2018 16:29:32 GMT):
@vishwasrao : Hyperledger Labs aims at providing a space (i.e., GitHub repos) where work can easily be started without the creation of an official Hyperledger project. Is there a particular lab that you would like to propose?

navalsinghIBM (Sun, 04 Feb 2018 11:04:22 GMT):
Has joined the channel.

vitorqshr (Thu, 08 Feb 2018 16:58:15 GMT):
Has joined the channel.

ChrisZhang (Fri, 09 Feb 2018 14:40:54 GMT):
Has joined the channel.

Everymans.ai (Tue, 13 Feb 2018 19:09:16 GMT):
Has joined the channel.

Everymans.ai (Tue, 13 Feb 2018 19:09:22 GMT):
✔ FREELANCER OPPORTUNITY: Need Blockchain - Business Strategist consultant / Subject Matter Expert / Optimize Student Online Learning Experience I am looking for a Blockchain / Business Strategist to join my team for the upcoming Oxford Blockchain course starting Feb. 28th. See https://goo.gl/m29zwf. It requires 10 to 15+ hours a week time commitment. It is remote/virtual work and pays very well. Please complete the form below to indicate your interest, qualifications and provide contact information. Here is a link to a form you can forward if you know someone that might be interested: https://goo.gl/viF7ow Please connect with me on http://Linkedin.com/in/georgepolzer

Dan (Thu, 15 Feb 2018 14:25:46 GMT):
Has joined the channel.

pasimoes (Tue, 20 Feb 2018 04:33:06 GMT):
Has joined the channel.

trbs (Tue, 20 Feb 2018 22:11:56 GMT):
@Everymans.ai Please use #jobs

Everymans.ai (Wed, 21 Feb 2018 02:39:44 GMT):
I will delete.

trbs (Wed, 21 Feb 2018 11:45:04 GMT):
thanks

MicBowman (Wed, 21 Feb 2018 17:39:47 GMT):
do we have a template for proposals?

lehors (Thu, 22 Feb 2018 00:52:46 GMT):
[ ](https://chat.hyperledger.org/channel/labs?msg=wDbnGNruM37E4HbST) @MicBowman please, have a look at https://github.com/hyperledger-labs and see if you can find the answer to your question and let us know

lehors (Thu, 22 Feb 2018 00:53:09 GMT):
all comments and suggestions for improvements welcome

mc (Thu, 22 Feb 2018 16:16:35 GMT):
Has joined the channel.

VipinB (Thu, 22 Feb 2018 16:22:28 GMT):
@MicBowman https://github.com/hyperledger-labs/hyperledger-labs.github.io/blob/master/proposal-template.md

VipinB (Thu, 22 Feb 2018 16:23:19 GMT):
@lehors saw your activity in labs, nice to do a dry run!

VipinB (Thu, 22 Feb 2018 16:24:15 GMT):
Are labs getting any interest at the hackfest- What about the crypto library

lehors (Thu, 22 Feb 2018 21:16:48 GMT):
[ ](https://chat.hyperledger.org/channel/labs?msg=goamxzh637KRtA3Qn) @VipinB Hart says he's been told the crypto library really ought to become a project

lehors (Thu, 22 Feb 2018 21:16:59 GMT):
but Mic has a proposal that he wants to make

lehors (Thu, 22 Feb 2018 21:17:11 GMT):
so he's going to be our guinea pig

MicBowman (Thu, 22 Feb 2018 21:28:38 GMT):
are there any expectations about naming conventions for projects? i know there is no HL branding... just want to make sure there are no other expectations...

VipinB (Thu, 22 Feb 2018 21:53:04 GMT):
@MicBowman name of repository hews to name of lab- (from template) - Should be unique (cant call it "Linux" or "Fabric" for example)- this is just common sense- these are very low barriers.

MicBowman (Thu, 22 Feb 2018 21:54:18 GMT):
thanks, vipin...

tkuhrt (Thu, 22 Feb 2018 22:13:30 GMT):
@MicBowman @VipinB : It does not have to start with lab- since it in the github.com/hyperledger-labs organization.

MicBowman (Thu, 22 Feb 2018 22:26:20 GMT):
i'm sure it will be "pdo" or something like that

VipinB (Thu, 22 Feb 2018 22:39:22 GMT):
I didn't mean it has to start with lab @tkuhrt -meaning repo and lab have the same name...

tkuhrt (Thu, 22 Feb 2018 22:46:55 GMT):
ah...yes.

VipinB (Tue, 27 Feb 2018 20:19:05 GMT):
@MicBowman what will pdo cover?

seth (Wed, 28 Feb 2018 03:28:03 GMT):
Has joined the channel.

alacrity (Wed, 28 Feb 2018 07:08:12 GMT):
Has joined the channel.

MicBowman (Wed, 28 Feb 2018 17:05:48 GMT):
@VipinB PDO == private data objects, its an "offchain" smart contract environment that uses SGX to ensure privacy/confidentiality; the ledger looks a lot like the GSL from a year ago

VipinB (Wed, 28 Feb 2018 17:12:37 GMT):
Any relation to TownCrier @MicBowman

MicBowman (Wed, 28 Feb 2018 17:16:51 GMT):
not really... fan was my intern last summer & we can write contracts using attestations generated by TC... but other than the fact that they both use SGX... no relationship

Daniela_Barbosa (Thu, 01 Mar 2018 02:55:15 GMT):
Has joined the channel.

albertocuriel (Thu, 01 Mar 2018 03:06:05 GMT):
Has joined the channel.

albertocuriel (Thu, 01 Mar 2018 03:10:36 GMT):
hello

albertocuriel (Thu, 01 Mar 2018 03:10:36 GMT):
I was on https://github.com/hyperledger-labs/hyperledger-labs.github.io , then in "Fork the hyperledger-labs.github.io repository" I pressed the "fork button" in the top tight of the page... basic question: how to fork it correctly?

creativemonk (Thu, 01 Mar 2018 08:06:01 GMT):
Has joined the channel.

albertocuriel (Thu, 01 Mar 2018 15:38:51 GMT):
@VipinB @lehors Good day Vipin, Arnaud. I sent a pull request for a lab -fresh air-. Hoping to hear from you. Alberto

lehors (Thu, 01 Mar 2018 15:39:26 GMT):
very nice, will have a look!

lehors (Thu, 01 Mar 2018 15:39:32 GMT):
thanks

lehors (Thu, 01 Mar 2018 15:39:50 GMT):
if you have any comments on the process & documentation so far, please, let us know

VipinB (Thu, 01 Mar 2018 15:40:07 GMT):
will take a look @albertocuriel

tkuhrt (Thu, 01 Mar 2018 18:26:13 GMT):
Hi, @albertocuriel I did not see your pull request in https://github.com/hyperledger-labs/hyperledger-labs.github.io. Did you follow the process outlined here: https://github.com/hyperledger-labs/hyperledger-labs.github.io/blob/master/README.md

tkuhrt (Thu, 01 Mar 2018 18:26:21 GMT):
Or am I missing something

MicBowman (Thu, 01 Mar 2018 18:57:29 GMT):
the last hangup we have for submitting the pdo proposal is that our legal wants to clear the name... i'm assuming we can change the name of the lab later if we need to?

albertocuriel (Thu, 01 Mar 2018 19:31:58 GMT):
@vipinb thank you

albertocuriel (Thu, 01 Mar 2018 19:33:21 GMT):
@tkuhrt yes, I followed the instructions there. https://github.com/m3m3m3m3/hyperledger-labs.github.io/pull/1 am I missing something? thanks

tkuhrt (Thu, 01 Mar 2018 19:34:35 GMT):
Note that you are in m3m3m3m3 and not hyperledger-labs

tkuhrt (Thu, 01 Mar 2018 19:34:43 GMT):
^ @albertocuriel

tkuhrt (Thu, 01 Mar 2018 19:34:59 GMT):
So we cannot see that in https://github.com/hyperledger-labs/hyperledger-labs.github.io

albertocuriel (Thu, 01 Mar 2018 19:35:00 GMT):
oops

tkuhrt (Thu, 01 Mar 2018 19:35:51 GMT):
Also, we would not want to delete the existing template, but rather copy the template to a new file which would then be part of the pull request

albertocuriel (Thu, 01 Mar 2018 19:52:04 GMT):
@tkuhrt , thank you . ok I just added the pull request on hyperledger. https://github.com/hyperledger-labs/hyperledger-labs.github.io/pull/9

MicBowman (Thu, 01 Mar 2018 20:20:13 GMT):
@tkuhrt @lehors @VipinB Just created the PR for the private data objects lab as well

tkuhrt (Thu, 01 Mar 2018 20:42:15 GMT):
@MicBowman : One minor comment added

VipinB (Thu, 01 Mar 2018 21:21:16 GMT):
@albertocuriel Please fill out "Initial committers"/ "Sponsor" and "Prexisting repository" if any; also let us try to rework the "manifesto" into engineering terms if possible

VipinB (Thu, 01 Mar 2018 21:37:49 GMT):
@MicBowman pdo seems well thought out

VipinB (Thu, 01 Mar 2018 21:38:16 GMT):
@albertocuriel I have made some comments

MicBowman (Thu, 01 Mar 2018 21:40:55 GMT):
@tkuhrt fixed the spelling error & pushed new commit

MicBowman (Thu, 01 Mar 2018 21:41:49 GMT):
@VipinB we should have a more complete overview by the end of next week

tkuhrt (Thu, 01 Mar 2018 22:29:47 GMT):
@MicBowman : Thanks. Another question surrounding the github repo. Obviously still some work to do on your side. Would you want us to create a repo or just do a transfer of the Intel repo?

tkuhrt (Thu, 01 Mar 2018 22:30:08 GMT):
Maybe I should add this as a question to the PR so we have history of it

MicBowman (Thu, 01 Mar 2018 22:30:29 GMT):
best to create a new one

tkuhrt (Thu, 01 Mar 2018 22:30:41 GMT):
Okay.

MicBowman (Thu, 01 Mar 2018 22:30:43 GMT):
we are using the intel github right now

MicBowman (Thu, 01 Mar 2018 22:30:57 GMT):
i'm not too worried about preserving history... though we could work that as well

MicBowman (Thu, 01 Mar 2018 22:31:19 GMT):
this is going through the research repo --> internal candidate repo --> hl labs

MicBowman (Thu, 01 Mar 2018 22:31:25 GMT):
so things are already kind of messy

tkuhrt (Thu, 01 Mar 2018 22:32:03 GMT):
Great...I will make a comment on the PR that a new repo would be created and then you or one of the other committers would do the migration.

tkuhrt (Thu, 01 Mar 2018 22:33:36 GMT):
other than that, I gave it a +1. We will let @VipinB @lehors and @trbs have a look and comment

shimos (Fri, 02 Mar 2018 03:34:51 GMT):
Has joined the channel.

albertocuriel (Fri, 02 Mar 2018 08:59:54 GMT):
@tkuhrt @vipinb It is my first time using git. I am using github on the browser. I have a basic question. I realize now that when the Hyperledge instructions says "Fork the hyperledger-labs.github.io repository." you are not saying "press the fork button in that page". you a re saying "press the create file button". Now when you say git commit -amend -s if not, you will need to squash your commit into a single commit and sign off (how to doall of the https://github.com/hyperledger-labs/hyperledger-labs.github.io webpage?

albertocuriel (Fri, 02 Mar 2018 09:00:22 GMT):
thanks

tkuhrt (Fri, 02 Mar 2018 21:30:02 GMT):
@MicBowman : Your lab repo has been created and invites sent to the committers: https://github.com/hyperledger-labs/private-data-objects

MicBowman (Fri, 02 Mar 2018 22:02:44 GMT):
thanks, @tkuhrt

b9lab-damien (Mon, 05 Mar 2018 22:13:32 GMT):
Has joined the channel.

vishwasbalakrishna (Wed, 07 Mar 2018 21:48:48 GMT):
Has joined the channel.

aldoussnow (Sun, 11 Mar 2018 10:19:22 GMT):
Has joined the channel.

aldoussnow (Sun, 11 Mar 2018 10:19:28 GMT):
Hi

aldoussnow (Sun, 11 Mar 2018 10:19:58 GMT):
@tkuhrt What can we do here?

gskerry (Mon, 12 Mar 2018 17:56:50 GMT):
Has joined the channel.

tkuhrt (Mon, 12 Mar 2018 19:06:41 GMT):
Hi, @aldoussnow : This is the channel for Hyperledger Labs -- https://hyperledger-labs.github.io/

tkuhrt (Mon, 12 Mar 2018 20:36:52 GMT):
@lehors @trbs @VipinB : If anyone is so inclined to offer another +1 to https://github.com/hyperledger-labs/hyperledger-labs.github.io/pull/16, we can get a second lab set up

VipinB (Mon, 12 Mar 2018 21:48:15 GMT):
I gave https://github.com/hyperledger-labs/hyperledger-labs.github.io/pull/16 a +1

tkuhrt (Mon, 12 Mar 2018 21:49:38 GMT):
Cool...thanks @VipinB

tkuhrt (Mon, 12 Mar 2018 21:49:49 GMT):
I will work on creating the repo then

Jiang (Wed, 14 Mar 2018 07:35:11 GMT):
Has joined the channel.

tkuhrt (Tue, 20 Mar 2018 20:31:05 GMT):
@stewards : Looks like we have a PR to review - https://github.com/hyperledger-labs/hyperledger-labs.github.io/pull/25

ShikarSharma (Tue, 20 Mar 2018 22:51:21 GMT):
Has joined the channel.

Dan (Tue, 20 Mar 2018 22:59:45 GMT):
That does not look like a legitimate request.

tkuhrt (Tue, 20 Mar 2018 23:23:58 GMT):
Agree, @Dan. The sponsorship is not correct. Is that what you are referring to?

tkuhrt (Tue, 20 Mar 2018 23:25:18 GMT):
@Dan ^^ (I hate how Rocket.Chat does not handle channel and at notifications when it is followed by a period)

Dan (Wed, 21 Mar 2018 12:30:49 GMT):
If that proposal had a proper sponsor then I would be questioning the sponsor.

VipinB (Wed, 21 Mar 2018 15:33:06 GMT):
This proposal keeps coming back

VipinB (Wed, 21 Mar 2018 15:33:35 GMT):
I had questioned the premise

VipinB (Wed, 21 Mar 2018 15:33:48 GMT):
Before, I have not read the current proposal

VipinB (Wed, 21 Mar 2018 15:37:19 GMT):
Does not seem very different this time either

albertocuriel (Thu, 22 Mar 2018 18:46:05 GMT):
@tkuhrt @VipinB @Dan. Dear Sirs/Madamme, the last 4 weeks we were trying to let you know our proposal for improvement using Hyperledger. We looked first as an associate project, with hyperledger, but the foundation reffer us to submit it to the hypeprledger lab becuase it was simpler and for this kind of projects.To fill the pull that is is why in the sponsorship field, we added our data to be able to send the proposal for your read. WE know what what we are going is revolutionary and makes what you are currently unable to do with any current blockchain.As IBM partners for Blockcain we submitted the proposal for Hyperledger consideration. He have found easy, open collaboration from other industrial players. We thank you for your time. It is a pitty that yHyperledger could read and study our proposal in that time. Unfortunately Hyperledger seems that not a desired blockchain solution.Thanks

albertocuriel (Thu, 22 Mar 2018 18:53:34 GMT):
@tkuhrt @VipinB @Dan correction:: coudnt read the poposal in that time.

VipinB (Thu, 22 Mar 2018 18:58:16 GMT):
I did read the proposal

VipinB (Thu, 22 Mar 2018 18:59:17 GMT):
Not changed the way we asked in the first place

lehors (Thu, 22 Mar 2018 19:35:24 GMT):
unlike @Dan I wouldn't necessarily declare this proposal out of scope because it is simply too vague for me to be able to make that determination but independently of that, this proposal still fails to meet the basic requirements set by our process, including having a sponsor who's Hyperledger project maintainer

lehors (Thu, 22 Mar 2018 19:35:51 GMT):
@albertocuriel while I can understand your frustration I would advise you to seek for such a sponsor

lehors (Thu, 22 Mar 2018 19:36:11 GMT):
of course it will require for you to engage and explain what your project really entails

lehors (Thu, 22 Mar 2018 19:38:09 GMT):
but I'm sure such a discussion would benefit everybody - this would help you better describe what your lab proposal is about and help us understanding how it fits within the scope of hyperleger

lehors (Thu, 22 Mar 2018 19:39:11 GMT):
the kind of flippant statement a la "Unfortunately Hyperledger seems that not a desired blockchain solution" doesn't help anyone

VipinB (Thu, 22 Mar 2018 22:14:00 GMT):
@lehors @albertocuriel I had made the same comments for an earlier PR- maybe not as a requirement that you need a sponsor, but we need a concrete proposal with a little bit of definition; I even offered to help you write it out, if language was an issue.

VipinB (Thu, 22 Mar 2018 22:16:30 GMT):
I am all for stretching the bounds of the possible and out of the box thinking- we need a path towards implementation for this to be a lab

KOttoni (Wed, 28 Mar 2018 16:55:21 GMT):
Has joined the channel.

tkuhrt (Thu, 29 Mar 2018 17:34:12 GMT):
@hartm : Created the repo for crypto-lib : https://github.com/hyperledger-labs/crypto-lib

hartm (Thu, 29 Mar 2018 17:34:12 GMT):
Has joined the channel.

hartm (Thu, 29 Mar 2018 17:47:10 GMT):
@tkuhrt Thanks so much Tracy!

MikeCohen (Fri, 30 Mar 2018 18:55:19 GMT):
Has joined the channel.

mheave (Tue, 03 Apr 2018 10:09:27 GMT):
Has joined the channel.

SummerLotus (Tue, 03 Apr 2018 16:43:12 GMT):
Has joined the channel.

SummerLotus (Tue, 03 Apr 2018 16:47:27 GMT):
is there a way to create enterprise crypto with hyperledger?. We are planning to use Fabric but need to generate enterprise Crypto for this project. For now, plan is to develop on Fabric and then later integrate with Crypto generator. Ex: Like Stellar or any other Crypto platform.. Any advice please..

VipinB (Tue, 03 Apr 2018 18:21:23 GMT):
@SummerLotus @hartm has a plan for a crypto-lib, I believe he is organizing regular calls around this. Do not know exactly what is meant by enterprise crypto.

hartm (Tue, 03 Apr 2018 19:08:19 GMT):
@SummerLotus We are planning a Hyperledger crypto-lib project. I don't know exactly what you mean by Enterprise crypto, but feel free to check out the crypto-lib rocket chat channel for more information on that.

yghazi (Tue, 03 Apr 2018 19:14:46 GMT):
Has joined the channel.

stanliberman (Wed, 04 Apr 2018 16:31:55 GMT):
Has joined the channel.

bee (Thu, 05 Apr 2018 14:23:05 GMT):
Has joined the channel.

richzhao (Sat, 07 Apr 2018 08:27:33 GMT):
Has joined the channel.

hartm (Sun, 08 Apr 2018 20:40:32 GMT):
Is it possible to have a mailing list for a labs project? I'm not sure what the policy on this is, and I can't find anything in the wiki. Thanks!

Dan (Mon, 09 Apr 2018 12:54:43 GMT):
IIRC I think we discussed having one labs mailing list for all of labs.

tkuhrt (Mon, 09 Apr 2018 17:50:25 GMT):
There should be one of those alreay, @Dan - https://lists.hyperledger.org/mailman/listinfo/hyperledger-labs

tkuhrt (Mon, 09 Apr 2018 17:50:25 GMT):
There should be one of those already, @Dan - https://lists.hyperledger.org/mailman/listinfo/hyperledger-labs

tkuhrt (Mon, 09 Apr 2018 17:51:42 GMT):
@hartm : As Dan mentioned, we had decided one mailing list and one chat channel for all labs. If it becomes necessary to break that out (due to one lab being really vocal), then we can decide to do that.

robinrob (Mon, 16 Apr 2018 21:36:23 GMT):
Has joined the channel.

unselect (Fri, 20 Apr 2018 17:35:44 GMT):
Has joined the channel.

Tommy109 (Sun, 22 Apr 2018 14:10:23 GMT):
Has joined the channel.

trthhrtz (Wed, 25 Apr 2018 07:24:14 GMT):
Has joined the channel.

rjones (Thu, 26 Apr 2018 14:15:34 GMT):
Has joined the channel.

BrunoVavala (Wed, 02 May 2018 17:25:54 GMT):
Has joined the channel.

EugeneYYY (Thu, 03 May 2018 16:05:39 GMT):
Has joined the channel.

lehors (Thu, 10 May 2018 15:00:33 GMT):
out some point we should report to the TSC on the labs related activities

lehors (Thu, 10 May 2018 15:01:00 GMT):
I know this is something we (the stewards) signed up to do

lehors (Thu, 10 May 2018 15:01:54 GMT):
I think it was like on a quaterly basis but I don't know when that starts @tkuhrt do you know?

tkuhrt (Thu, 10 May 2018 15:20:27 GMT):
We don't really have a schedule on that yet, @lehors

tkuhrt (Thu, 10 May 2018 15:20:37 GMT):
Do we think we are ready for an update?

tkuhrt (Thu, 10 May 2018 15:21:23 GMT):
I am happy to start a wiki page that begins to provide an update that we can edit.

tkuhrt (Thu, 10 May 2018 15:37:51 GMT):
@stewards : With the addition of Ry as a community architect, I was wondering if we should add him as a steward for labs. In the original proposal, we mentioned community architect(s) would be stewards. Is this something we can decide or is this something that we should take to the TSC for input.

tkuhrt (Thu, 10 May 2018 16:27:18 GMT):
https://wiki.hyperledger.org/labs/2018-q2-update -- what else should we add to this?

trbs (Mon, 14 May 2018 12:21:36 GMT):
@tkuhrt sorry for late reply. Makes sense to me to add Ry (if he wants)

trbs (Mon, 14 May 2018 12:24:46 GMT):
Update lgtm. Thanks for writing that up. Was looking at that we had 25 PR's closed but most are not really interesting to mention :smiley:

VipinB (Tue, 15 May 2018 13:10:33 GMT):
I am for adding @rjones - I agree that this is good to do as he is now a Community Architect

VipinB (Tue, 15 May 2018 15:29:43 GMT):
If we do we should mention in the update doc.

hartm (Tue, 15 May 2018 17:25:41 GMT):
Not a lab steward, but +1 for adding Ry.

VipinB (Wed, 16 May 2018 15:10:26 GMT):
As a tsc member @hartm your opinion counts more than lab stewards' - the interesting question is whether we should bring this to tsc. I need to look at the charter for labs to see whether this is possible without tsc approval- I believe it should be.

trbs (Wed, 16 May 2018 23:35:51 GMT):
For all the ways one could have uttered that sentence that it's hard to imaging not being able to find a more pleasant and less arrogant way...

VipinB (Thu, 17 May 2018 15:21:32 GMT):
@trbs apologies if it came through as arrogant.

VipinB (Thu, 17 May 2018 15:21:49 GMT):
From the charter: The following people have been approved by the TSC to be Labs Stewards. Please do not add your name unless you have been approved by the TSC to be a new Labs Steward.

VipinB (Thu, 17 May 2018 15:22:14 GMT):
So looks like we need approval from tsc to add Lab Stewards according to the charter

tkuhrt (Fri, 18 May 2018 18:37:19 GMT):
Thanks for finding that note, @VipinB

tkuhrt (Fri, 18 May 2018 18:37:32 GMT):
Sounds like we need to send an email to the TSC mailing list.

tkuhrt (Wed, 23 May 2018 16:44:13 GMT):
@VipinB @lehors : Any changes to the update for Labs (https://wiki.hyperledger.org/labs/2018-q2-update)? If not, I will send email off to TSC list on this.

tkuhrt (Wed, 23 May 2018 22:20:16 GMT):
@lehors @VipinB @trbs : Thoughts on creating Jira projects under jira.hyperledger.org? I have been asked to do so for Private Data Objects. I was under the impression that labs would be separate from projects and would use Github issues. But I would appreciate opinions/thoughts.

trbs (Wed, 23 May 2018 22:30:16 GMT):
@tkuhrt @stewards on the quarterly update; thoughts on maybe also adding the names of the lab proposals "in progress" and "out of scope/withdrawn" ? (maybe just the names, without further description) Otherwise LTGM :-)

tkuhrt (Wed, 23 May 2018 22:31:29 GMT):
Yes...could add the links to the PRs for `in progress` and `out of scope/withdrawn`

trbs (Wed, 23 May 2018 22:32:54 GMT):
@tkuhrt the idea for the labs was to be less strict/formal for this kinda stuff right ? thought they would (mostly) use github issues as well... I don't see the harm of them using Jira if they want, only that since this takes time & effort it should maybe only be done if there is a reasonable certainty that it will be used ? (otherwise seems like an unwanted burden for the Jira maintainers)

VipinB (Thu, 24 May 2018 15:19:30 GMT):
@tkuhrt @stewards was out of commission for a while. Hope the update went well today...

tkuhrt (Thu, 24 May 2018 15:31:45 GMT):
@VipinB : Hope you are well. We haven't done the update yet. I was waiting to hear back from you and @lehors before sending to the TSC.

VipinB (Thu, 24 May 2018 15:37:05 GMT):
In my opinion the less gating factors we have, the better. Since labs was conceived of that way.

Dan (Tue, 29 May 2018 14:53:19 GMT):
Mild preference for using jira. That way if the lab becomes a project it is already using the right infrastructure and processes.

Dan (Tue, 29 May 2018 15:34:06 GMT):
Do we have a mail list for labs? I don't see one at lists.hyperledger.org but wouldn't be the first time I missed a link that was staring me in the face.

tkuhrt (Tue, 29 May 2018 16:39:01 GMT):
@Dan : Can you see this? https://lists.hyperledger.org/g/labs

Dan (Tue, 29 May 2018 16:52:51 GMT):
yes! I was seaching within page for labs in the subgroup list, but missed that it covers 2 pages.

Dan (Tue, 29 May 2018 16:52:55 GMT):
thanks

PoojaVarshneya (Tue, 29 May 2018 17:23:40 GMT):
Has joined the channel.

PoojaVarshneya (Wed, 30 May 2018 15:16:10 GMT):
is crypto-lib meeting on for today ?

tkuhrt (Wed, 30 May 2018 15:28:25 GMT):
@PoojaVarshneya crypto-lib meeting was an hour ago

tkuhrt (Wed, 30 May 2018 15:28:37 GMT):
You might be interested in the #crypto-lib channel

PoojaVarshneya (Wed, 30 May 2018 16:06:13 GMT):
Thanks @tkuhrt

rogerwilcos (Wed, 30 May 2018 23:24:53 GMT):
Has joined the channel.

lehors (Thu, 31 May 2018 14:11:55 GMT):
@tkuhrt sorry for seemingly spacing out on this but I think the report looks fine

lehors (Thu, 31 May 2018 14:12:07 GMT):
I don't see any need to make it more complicated than necessary

lehors (Thu, 31 May 2018 14:12:22 GMT):
I do NOT think we should offer Jira support to the labs

lehors (Thu, 31 May 2018 14:13:55 GMT):
the whole idea is to offer a lightweight process and it seems to me that this would add a burden to the organizations resources

lehors (Thu, 31 May 2018 14:14:41 GMT):
but we could possibly raise this as a question to the TSC

lehors (Thu, 31 May 2018 14:16:57 GMT):
I agree with @Dan's point that allowing them to use Jira would ease transition in case a lab becomes a project eventually

lehors (Thu, 31 May 2018 14:17:42 GMT):
but unless we expect this to be the norm rather than the exception I don't know that it is worth it

lehors (Thu, 31 May 2018 14:19:21 GMT):
also I don't know where we'd draw the line, what if a project wants to use Gerrit rather than Github (so that "if the lab becomes a project it is already using the right infrastructure and processes" ;-)

Dan (Thu, 31 May 2018 15:18:26 GMT):
Together we can save people from Gerrit, one project at a time. ;)

hartm (Thu, 31 May 2018 15:48:18 GMT):
@Dan LOL.

MicBowman (Thu, 31 May 2018 21:03:46 GMT):
@lehors we have our own internal JIRA for the private data objects work... we just wanted to make the processes as open as possible

MicBowman (Thu, 31 May 2018 21:05:11 GMT):
we've been talking about just pinning rocket chat messages but that seems... rather ugly

rameshjhajharia (Sun, 03 Jun 2018 17:30:25 GMT):
Has joined the channel.

lehors (Mon, 04 Jun 2018 18:33:57 GMT):
@MicBowman well, once code is contributed to a lab I would expect the participants to stop using whatever internal tool they were using before

lehors (Mon, 04 Jun 2018 18:34:32 GMT):
unless you expect the LF staff to import your JIRA database I don't know how that makes a difference

lehors (Mon, 04 Jun 2018 18:37:03 GMT):
I guess I don't understand the point

lehors (Mon, 04 Jun 2018 18:37:49 GMT):
I do agree it would be easier to offer JIRA to those used to it and I'm not really against it if the staff think it's easy enough and is willing to do the extra work

adityasingh177 (Tue, 05 Jun 2018 12:51:21 GMT):
Has joined the channel.

Luxii (Tue, 05 Jun 2018 13:16:20 GMT):
Has joined the channel.

Luxii (Tue, 05 Jun 2018 13:18:23 GMT):
Hi , I'm getting ```[2018-06-05 14:57:53 WARNING pdo_connect_tp] Unexpected exception occurred on context.get_state([0b936f187fa874fe5bb01433cf07f60a5d602ac4d5c74dc6dfdec7a682f98416975cfd])``` when running pdo-tp and registering enclave with proof data

Luxii (Tue, 05 Jun 2018 13:21:02 GMT):
Hey Im having some trouble understanding Private data objects for sawtooth project. Can anyone help me with that ?

tkuhrt (Tue, 05 Jun 2018 19:18:31 GMT):
@Luxii - can you send your problems to #private-data-objects channel?

tkuhrt (Tue, 05 Jun 2018 19:19:23 GMT):
FYI...Quarterly update sent to the TSC mailing list today: https://lists.hyperledger.org/g/tsc/topic/hyperledger_labs_q2_update/21342368

Dan (Tue, 05 Jun 2018 23:55:32 GMT):
Oops sorry I sent @Luxii here for PDO questions. Forgot PDO has it's own channel on #private-data-objects .

ouijdenDhm (Wed, 06 Jun 2018 14:05:19 GMT):
Has joined the channel.

sheehan (Wed, 06 Jun 2018 15:02:18 GMT):
Has joined the channel.

DanielMcSheehy (Wed, 06 Jun 2018 15:18:33 GMT):
Has joined the channel.

DanielMcSheehy (Wed, 06 Jun 2018 15:22:45 GMT):
Posted a PR for the fabric chrome extension if anyone could check it out https://github.com/hyperledger-labs/hyperledger-labs.github.io/pull/28

tkuhrt (Wed, 06 Jun 2018 17:32:46 GMT):
Thanks, @DanielMcSheehy

dklesev (Thu, 07 Jun 2018 09:33:08 GMT):
Has joined the channel.

lehors (Thu, 07 Jun 2018 14:01:53 GMT):
@tkuhrt latest commit from @DanielMcSheehy looked good to me so I merged the patch only to realize the file needs to be renamed to end with .md to get properly rendered

lehors (Thu, 07 Jun 2018 14:01:53 GMT):
@tkuhrt latest commit from @DanielMcSheehy looked good to me so I merged the PR only to realize the file needs to be renamed to end with .md to get properly rendered

lehors (Thu, 07 Jun 2018 14:02:23 GMT):
can you make that change directly or do we have to go through the whole PR cycle (which is overkilling in this case...)

nage (Thu, 07 Jun 2018 14:43:43 GMT):
Has joined the channel.

DanielMcSheehy (Thu, 07 Jun 2018 14:48:10 GMT):
@lehors nice catch, i'll try to reopen it.

DanielMcSheehy (Thu, 07 Jun 2018 15:00:59 GMT):
@lehors Unfortunately I had to make another PR due to the other one being merged. This PR changes the file type https://github.com/hyperledger-labs/hyperledger-labs.github.io/pull/29 I'll be more careful next time :grinning:

lehors (Thu, 07 Jun 2018 15:01:55 GMT):
well, I wish I had caught that before clicking merge :)

lehors (Thu, 07 Jun 2018 15:02:06 GMT):
thanks

lehors (Thu, 07 Jun 2018 15:04:19 GMT):
ok, I merged it

lehors (Thu, 07 Jun 2018 15:04:54 GMT):
so, that part is done, your repo should be created next

lehors (Thu, 07 Jun 2018 15:06:08 GMT):
hmm, sorry I'm getting up to speed slowly on that one

lehors (Thu, 07 Jun 2018 15:06:55 GMT):
initial committer should list the id/email address

lehors (Thu, 07 Jun 2018 15:07:23 GMT):
we went through that for other labs, getting them to add that info

lehors (Thu, 07 Jun 2018 15:07:29 GMT):
so we ought to be consistent :)

lehors (Thu, 07 Jun 2018 15:07:55 GMT):
same for the sponsors

DanielMcSheehy (Thu, 07 Jun 2018 15:21:33 GMT):
@lehors Thank you! To clarify, you want me to make a new PR to add what kind of an id? Then add email address for initial committers and sponsors?

lehors (Thu, 07 Jun 2018 15:25:47 GMT):
github ids

lehors (Thu, 07 Jun 2018 15:26:00 GMT):
that's what the template calls for as a matter of fact

lehors (Thu, 07 Jun 2018 15:26:36 GMT):
and you can see how others have done it: https://github.com/hyperledger-labs/hyperledger-labs.github.io/blob/master/labs/SParts.md

tkuhrt (Thu, 07 Jun 2018 15:34:46 GMT):
Created https://github.com/hyperledger-labs/fabric-chrome-extension -- I added @DanielMcSheehy github ID to the project

tkuhrt (Thu, 07 Jun 2018 15:36:23 GMT):
And then I read the above where we want to add Github ID to the .md file

lehors (Thu, 07 Jun 2018 15:38:00 GMT):
that's ok, we can still do it

lehors (Thu, 07 Jun 2018 15:38:29 GMT):
will try to be more careful next time

DanielMcSheehy (Thu, 07 Jun 2018 17:10:21 GMT):
@lehors @tkuhrt Added that info in here: https://github.com/hyperledger-labs/hyperledger-labs.github.io/pull/30/commits/bf7384f5403aa9e3b3b6b342477beccac0668757 Thank's for the help.

lehors (Thu, 07 Jun 2018 19:31:52 GMT):
@DanielMcSheehy looks good. Thanks

abraham (Fri, 08 Jun 2018 05:12:10 GMT):
Has joined the channel.

angelagilhotra (Mon, 11 Jun 2018 18:15:06 GMT):
Has joined the channel.

sigma67 (Tue, 12 Jun 2018 22:51:53 GMT):
Has joined the channel.

VipinB (Wed, 13 Jun 2018 15:27:06 GMT):
@lehors @tkuhrt @trbs new lab proposal for z-mix came in I have already +1 the lab... Looks like they conform with template including committers github names etc.

trbs (Wed, 13 Jun 2018 20:13:39 GMT):
z-mix lgtm as well. In general (not specifically for z-mix) I wouldn't mind a bit more information (eg; how are they planning to deliver this ? something like libzmix.so or bindings or is it golang only ?) but we did not require that for other labs so +1 from me :smiley:

trbs (Wed, 13 Jun 2018 20:14:24 GMT):
btw are we checking with the sponsors before merging the PR's ?

trbs (Wed, 13 Jun 2018 20:14:44 GMT):
(tbh i have not contacted a sponsor to verify a PR before)

VipinB (Thu, 14 Jun 2018 15:27:34 GMT):
I heard on the cryptolib call that at least one sponsor (hart) is supporting them

trbs (Thu, 14 Jun 2018 19:25:53 GMT):
Anybody at the Hackfest in Amsterdam ? Would be nice to do a quick face-to-face with @stewards :-)

rjones (Thu, 14 Jun 2018 20:21:30 GMT):
@trbs I will be there for the hackfest, and Tracy will be as well

DuncanMuhoro (Sun, 17 Jun 2018 11:05:43 GMT):
Has joined the channel.

lehors (Mon, 18 Jun 2018 07:20:14 GMT):
likewise

lehors (Mon, 18 Jun 2018 12:46:23 GMT):
@rjones, @tkuhrt I think z-mix can be merged in and its repo created.

lehors (Mon, 18 Jun 2018 12:46:32 GMT):
thanks

rjones (Mon, 18 Jun 2018 13:14:44 GMT):
@lehors I don't want to do any operations until I'm actually awake but sure thing ✈️

lehors (Mon, 18 Jun 2018 13:15:17 GMT):
sure :)

tkuhrt (Mon, 18 Jun 2018 15:29:12 GMT):
@lehors @rjones - I will take care of this one

tkuhrt (Mon, 18 Jun 2018 16:03:35 GMT):
z-mix lab created

rjones (Mon, 18 Jun 2018 17:04:45 GMT):
thank you

st (Wed, 20 Jun 2018 12:12:14 GMT):
Has joined the channel.

pwx603 (Mon, 25 Jun 2018 21:02:43 GMT):
Has joined the channel.

hvandurme (Fri, 29 Jun 2018 07:58:03 GMT):
Has joined the channel.

Senthil1 (Thu, 05 Jul 2018 03:10:26 GMT):
Has joined the channel.

ongkhaiwei (Thu, 05 Jul 2018 13:51:37 GMT):
Has joined the channel.

PrafullKotecha (Thu, 12 Jul 2018 00:19:14 GMT):
Has joined the channel.

WadeLu (Thu, 12 Jul 2018 07:35:53 GMT):
Has joined the channel.

bobsummerwill (Fri, 13 Jul 2018 02:23:43 GMT):
Has joined the channel.

rjones (Fri, 13 Jul 2018 21:16:49 GMT):
I have sent a message to a subset of you on github, but this is the only way I can reach many of you, so... sorry not sorry:

rjones (Fri, 13 Jul 2018 21:16:51 GMT):
@all : 2FA will soon be required across all GitHub orgs. If you do not have 2FA enabled for your account, you will be automatically removed from the Hyperledger org and will need to be re-added. Please check to ensure you have 2FA enabled. https://help.github.com/articles/securing-your-account-with-two-factor-authentication-2fa/

rjones (Fri, 13 Jul 2018 22:58:48 GMT):
thank you @VipinB for enabling 2FA :)

VipinB (Mon, 16 Jul 2018 12:34:39 GMT):
NP @rjones, plus there is no real alternative if you want to be on Github

ynamiki (Wed, 18 Jul 2018 22:09:16 GMT):
Has joined the channel.

VipinB (Thu, 19 Jul 2018 21:57:18 GMT):
IBANP project was suggested as a new entrant into Hyperledger labs, we hope they will make a request

VipinB (Thu, 19 Jul 2018 22:05:33 GMT):
Is there a lab steward mailing list?

rjones (Fri, 20 Jul 2018 22:59:41 GMT):
@VipinB there is only https://lists.hyperledger.org/g/labs/topics , but it has only ever had 7 threads, so I think it could handle a discussion for stewards without much work. We could use #stewards perhaps?

hcsatish (Sat, 21 Jul 2018 17:17:07 GMT):
Has joined the channel.

alokmatta (Tue, 24 Jul 2018 23:11:58 GMT):
Has joined the channel.

ynamiki (Fri, 27 Jul 2018 04:09:44 GMT):
@stewards, I would like to propose a new lab, MinBFT. It is appreciated if you could review our proposal: https://github.com/hyperledger-labs/hyperledger-labs.github.io/pull/32

lehors (Fri, 27 Jul 2018 16:19:28 GMT):
[ ](https://chat.hyperledger.org/channel/labs?msg=LKCCJkJjviG74ryB9) @ynamiki Thanks, I just responded on github

trbs (Wed, 01 Aug 2018 13:32:51 GMT):
Thanks for updating the template @lehors, was about to do that but you already did :smiley:

lehors (Wed, 01 Aug 2018 15:30:48 GMT):
[ ](https://chat.hyperledger.org/channel/labs?msg=S8zRsiudXGhALBn7f) @trbs you're welcome :-)

lehors (Thu, 02 Aug 2018 23:54:16 GMT):
@tkuhrt @rjones I think I screwed around enough (unsuccessfully!) to try and amend a commit message that does have a sign-off that is not recognized. Someone with greater github skills should get us through it. Thanks. https://github.com/hyperledger-labs/hyperledger-labs.github.io/pull/38/commits

lehors (Thu, 02 Aug 2018 23:54:16 GMT):
@tkuhrt @rjones I think I screwed around enough unsuccessfully to try and amend a commit message that does have a sign-off that is not recognized. Someone with greater github skills should get us through it. Thanks. https://github.com/hyperledger-labs/hyperledger-labs.github.io/pull/38/commits

tkuhrt (Thu, 02 Aug 2018 23:55:15 GMT):
@lehors : How could you not sign-off your commit. :)

lehors (Thu, 02 Aug 2018 23:55:22 GMT):
but I did!

lehors (Thu, 02 Aug 2018 23:55:35 GMT):
the DCO checkout doesn't recognize it

lehors (Thu, 02 Aug 2018 23:55:35 GMT):
the DCO check doesn't recognize it

lehors (Thu, 02 Aug 2018 23:55:54 GMT):
is it because it's got some spurious leading spaces?

lehors (Thu, 02 Aug 2018 23:57:01 GMT):
(side note: I really don't know why people love github... )

tkuhrt (Thu, 02 Aug 2018 23:57:54 GMT):
DCO is always fun to try to figure out what went wrong

tkuhrt (Fri, 03 Aug 2018 00:00:17 GMT):
It looks the same as your other previous sign offs

tkuhrt (Fri, 03 Aug 2018 00:02:32 GMT):
@rjones do you see any issues? Or should we ask Jessica

rjones (Fri, 03 Aug 2018 00:08:07 GMT):
I hate GitHub. I'll look at it in an hour or so

lehors (Fri, 03 Aug 2018 00:32:41 GMT):
thanks, there is no rush

rjones (Fri, 03 Aug 2018 01:12:38 GMT):
well you figured it out, I se

rjones (Fri, 03 Aug 2018 01:12:38 GMT):
well you figured it out, I see

rjones (Fri, 03 Aug 2018 01:12:48 GMT):
mazel tov!

rjones (Fri, 03 Aug 2018 01:13:28 GMT):
_right before I force pushed the fix_

rjones (Fri, 03 Aug 2018 12:36:34 GMT):
it is the leading whitespace btw

rjones (Fri, 03 Aug 2018 12:37:45 GMT):
@lehors I thought you had pushed a fix. Do you want the PR merged? I can over-ride the DCO whitespace issue. You could also fix it by force pushing from your command line client.

rjones (Fri, 03 Aug 2018 12:38:19 GMT):
this exact issue tripped up @Mari499 - you can't edit commit messages in the GitHub UI.

Mari499 (Fri, 03 Aug 2018 12:38:19 GMT):
Has joined the channel.

lehors (Fri, 03 Aug 2018 13:48:17 GMT):
I know you can't you edit commit messages in the github id, I changed it locally and force pushed it but I don't know where it went :-)

lehors (Fri, 03 Aug 2018 13:48:39 GMT):
the PR doesn't seem to have changed

lehors (Fri, 03 Aug 2018 13:49:23 GMT):
so, I think the best is to ignore the bogus DCO error report and move forward

rjones (Fri, 03 Aug 2018 14:24:07 GMT):
OK.

tkuhrt (Fri, 03 Aug 2018 18:00:02 GMT):
Hey, @lehors @ry. I see that the PR was merged. When I was going to create the lab, I noticed a bit of discrepancy between the lab name and the file name. File name is hyperledger-docs-cn.md and lab name is Fabric Docs CN.

tkuhrt (Fri, 03 Aug 2018 18:00:19 GMT):
I would like to get this resolved. Is the lab only for Hyperledger Fabric documentation?

tkuhrt (Fri, 03 Aug 2018 18:00:35 GMT):
If so, can we rename the file to fabric-docs-cn.md?

lehors (Fri, 03 Aug 2018 18:00:39 GMT):
yes, I think that's correct

tkuhrt (Fri, 03 Aug 2018 18:00:52 GMT):
Okay...let me do a PR to fix that

tkuhrt (Fri, 03 Aug 2018 18:00:59 GMT):
and then I will create the lab

lehors (Fri, 03 Aug 2018 18:01:15 GMT):
sounds good, I didn't detect the problem with the filename but you're right

tkuhrt (Fri, 03 Aug 2018 18:01:34 GMT):
I didn't catch it either until I was getting ready to create the lab

rjones (Fri, 03 Aug 2018 19:30:53 GMT):
Sorry. I was over eager and merged it

ynamiki (Tue, 07 Aug 2018 22:41:47 GMT):
@tkuhrt I am going to bring our existing repo to the new repo hyperledger-labs/minbft (All commits have signed-off). Can I overwrite the default README (a copy of our proposal), or should I have the default README as is?

rjones (Tue, 07 Aug 2018 23:56:19 GMT):
@ynamiki what exactly are you asking? if you should have a PR that over-writes the README, which is a copy of your proposal?

ynamiki (Wed, 08 Aug 2018 01:03:02 GMT):
@rjones @tkuhrt Sorry, I turn down the question.

rjones (Wed, 08 Aug 2018 01:03:14 GMT):
?

ynamiki (Wed, 08 Aug 2018 01:04:01 GMT):
I would like to bring our existing repo to hyperledger-labs/minbft. Can I use this method? https://help.github.com/articles/about-repository-transfers/

rjones (Wed, 08 Aug 2018 01:04:19 GMT):
link to existing repo?

ynamiki (Wed, 08 Aug 2018 01:04:31 GMT):
https://github.com/nec-blockchain/minbft

rjones (Wed, 08 Aug 2018 01:06:40 GMT):
@ynamiki I'm OK with it, I want Tracy's input.

ynamiki (Wed, 08 Aug 2018 01:07:18 GMT):
Sure, thanks.

tkuhrt (Wed, 08 Aug 2018 01:13:04 GMT):
@rjones @ynamiki as long as sign offs are in place, I am okay.

rjones (Wed, 08 Aug 2018 01:13:30 GMT):
@ynamiki transfer it to me: ryjones on github

rjones (Wed, 08 Aug 2018 01:14:25 GMT):
@ynamiki https://github.com/ryjones

ynamiki (Wed, 08 Aug 2018 01:29:11 GMT):
@rjones @tkuhrt Thanks. I have added ryjones as Admin to nec-blockchain/minbft. Please give me some days before starting the transfer; I will close ongoing items then ask to start the transfer.

rjones (Wed, 08 Aug 2018 02:22:15 GMT):
Ok. The transfer creates a redirect. Nothing is lost

ynamiki (Wed, 08 Aug 2018 09:49:06 GMT):
@rjones We are ready for the transfer to hyperledger-labs/minbft. Could you start the process?

rjones (Wed, 08 Aug 2018 14:30:36 GMT):
[ ](https://chat.hyperledger.org/channel/labs?msg=P2N3a36LEmCW4k3Ht) @ynamiki Done

r808silva (Wed, 08 Aug 2018 15:51:32 GMT):
Has joined the channel.

ynamiki (Thu, 09 Aug 2018 00:38:49 GMT):
@rjones Thanks. I would like to setup CircleCI for https://github.com/hyperledger-labs/minbft . Could I ask you to connect the CircleCI application to hyperledger-labs organization? https://github.com/settings/connections/applications/78a2ba87f071c28e65bb

rjones (Thu, 09 Aug 2018 00:40:21 GMT):
done

ynamiki (Thu, 09 Aug 2018 00:43:15 GMT):
Thanks!

BrettR (Thu, 09 Aug 2018 22:12:13 GMT):
Has joined the channel.

Kwaks (Thu, 16 Aug 2018 08:02:58 GMT):
Has joined the channel.

rjones (Wed, 22 Aug 2018 18:04:27 GMT):
@sgurary looking at https://github.com/hyperledger-labs/hyperledger-labs.github.io/pull/13/commits it looks like something strange is going on

sgurary (Wed, 22 Aug 2018 18:04:27 GMT):
Has joined the channel.

rjones (Wed, 22 Aug 2018 18:06:18 GMT):
@sgurary it really should be one commit of one file.

sgurary (Thu, 23 Aug 2018 08:15:33 GMT):
There was the process that @tkuhrt recommended for solving an issue with older commits. The commit after that should probably include all the files.

LZDOscar (Wed, 29 Aug 2018 13:55:22 GMT):
Has joined the channel.

parsiya (Fri, 31 Aug 2018 17:11:54 GMT):
Has joined the channel.

mighty-pirate (Thu, 06 Sep 2018 17:56:20 GMT):
Has joined the channel.

mighty-pirate (Thu, 06 Sep 2018 17:56:34 GMT):
Has left the channel.

dijun (Sat, 08 Sep 2018 07:02:03 GMT):
Has joined the channel.

bbehlendorf (Mon, 10 Sep 2018 23:26:31 GMT):
Has joined the channel.

tkuhrt (Thu, 13 Sep 2018 20:03:21 GMT):
@VipinB @lehors @trbs @rjones : When you get a chance, [PR for Hyperledger Community Tools lab](https://github.com/hyperledger-labs/hyperledger-labs.github.io/pull/43) as we talked about on the #tsc channel.

mathmass (Tue, 18 Sep 2018 06:37:59 GMT):
Has joined the channel.

VipinB (Tue, 18 Sep 2018 13:12:52 GMT):
@tkuhrt was offline for a few days. Will take a look

tkuhrt (Tue, 18 Sep 2018 15:29:05 GMT):
Great. I will wait for feedback from you.

VipinB (Tue, 18 Sep 2018 20:07:50 GMT):
I see that there are two lgtms I will take another look

VipinB (Tue, 18 Sep 2018 20:19:09 GMT):
@tkuhrt left a comment.

VipinB (Tue, 18 Sep 2018 20:19:09 GMT):
@tkuhrt I left a comment.

cbf (Thu, 20 Sep 2018 14:26:45 GMT):
Has joined the channel.

ZC_Cuebiq (Fri, 28 Sep 2018 12:39:03 GMT):
Has joined the channel.

abaaz (Mon, 01 Oct 2018 14:50:51 GMT):
Has joined the channel.

abaaz (Mon, 01 Oct 2018 14:51:41 GMT):
hey @VipinB good to see you, are you managing HL labs?

abaaz (Mon, 01 Oct 2018 14:58:00 GMT):
we'd be interested in contributing some of our work around Corda / Indy integration under HL labs... let me know when you have some time to connect on this.

VipinB (Mon, 01 Oct 2018 15:36:25 GMT):
I am available in NY- Do you have a writeup? Please follow the instructions in https://wiki.hyperledger.org/labs

VipinB (Mon, 01 Oct 2018 15:38:05 GMT):
Create a labs proposal as outlined in https://wiki.hyperledger.org/labs

VipinB (Mon, 01 Oct 2018 15:38:56 GMT):
@abaaz I am one of the labs stewards

VipinB (Mon, 01 Oct 2018 15:39:53 GMT):
If you need a sponsor, it can be a WG chair, TSC member or project maintainer

VipinB (Mon, 01 Oct 2018 15:40:36 GMT):
Send me a zoom or meetup @vip@dlt.nyc

abaaz (Mon, 01 Oct 2018 15:46:28 GMT):
awesome, thanks... yes we have plenty of collateral I'll drop you a note would be good to catch up

abaaz (Mon, 01 Oct 2018 15:46:38 GMT):
I've relocated to London btw

VipinB (Mon, 01 Oct 2018 17:14:12 GMT):
@abaaz main thing is to create a proposal in line with the template and follow the instructions

abaaz (Mon, 01 Oct 2018 17:33:16 GMT):
ok I'll have a look thanks

wdmason (Tue, 02 Oct 2018 10:16:37 GMT):
Has joined the channel.

wdmason (Tue, 02 Oct 2018 10:20:20 GMT):
So from my understanding, the Hyperledger Labs is for projects now quite ready to be put forth as Incubation. Is there a #toolshed for those projects not quite ready for #labs ?

tkuhrt (Tue, 02 Oct 2018 14:40:05 GMT):
@wdmason: From [wiki page on Labs](https://wiki.hyperledger.org/labs): > The [current Hyperledger Project Lifecycle](https://wiki.hyperledger.org/community/project-lifecycle) provides for projects to be started in Incubation and graduate from there to Active projects. Hyperledger Labs provides a space where work can easily be started without the creation of an official Hyperledger project.

tkuhrt (Tue, 02 Oct 2018 14:40:32 GMT):
Labs is a space for things not ready for incubation.

wdmason (Tue, 02 Oct 2018 14:41:16 GMT):
Thank you. I've been actually studying those documents. In fact, I've already updated my repo with a issue around that project lifecycle.

wdmason (Tue, 02 Oct 2018 14:41:42 GMT):
https://github.com/dltnexus/dltnexus/issues/13

wdmason (Tue, 02 Oct 2018 14:42:37 GMT):
I've been searching for months for a framework to base my project on. Git has been it for the last while, and now Hyperledger is going to be the guidance. We are currently in the Conception phase.

wdmason (Tue, 02 Oct 2018 14:42:50 GMT):
That's why it's in the garage or toolshed rather than even in the Lab.

wdmason (Tue, 02 Oct 2018 14:43:23 GMT):
There are no collaborators as yet. No sponsors. I have yet to make myself known to the community as a whole. This is where it begins.

wdmason (Tue, 02 Oct 2018 14:44:38 GMT):
It makes no sense to start from scratch. Hyperledger has already done the heavy lifting. Now, it's simply a matter of following the best of the protocol as it has evolved to this point.

tkuhrt (Tue, 02 Oct 2018 14:48:25 GMT):
I added a comment to your issue. You might find this presentation interesting if you are considering contribution of source base to Hyperledger: https://docs.google.com/presentation/d/1O2v6t_TNoT8v0MswiwMr6ddE132eCNmK-m3KhD1pGGE/edit#slide=id.g3cf4a9ebda_0_647 (Let me know if you don't have access to Google Drive). Please feel free to ask additional questions here. And welcome to the community!

wdmason (Tue, 02 Oct 2018 14:52:28 GMT):
Thank you for the feedback and I do have Google Drive. I have added that document and will review it soon.

wdmason (Tue, 02 Oct 2018 14:56:21 GMT):
I've also updated the issue based on your feedback. This happily answers the question of whether others can comment on issues. Obviously, they can. ;)

uherr89 (Thu, 04 Oct 2018 19:49:26 GMT):
Has joined the channel.

uherr89 (Thu, 04 Oct 2018 19:56:51 GMT):
Hello everyone, in recent days I spoke with Arnaud on LinkedIn about a project that we released (Framework for Smart Contract Systems) and he recommended us to propose it in labs. I have a question, how is the project handled or governance once it has been accepted? :slight_smile:

dijun (Fri, 05 Oct 2018 16:22:40 GMT):
Hi, I would like to propose a new lab, blockly-chaincode. blockly-chaincode is based on Blockly, the web-based, graphical programming editor. It provides specific blocks and code generators for chaincode design. You can simply drag blocks together to design your own chaincode. It is appreciated if you could review README here https://github.com/flyinox/flyinox.github.io And you can have a try here https://flyinox.github.io/

VipinB (Fri, 05 Oct 2018 17:55:21 GMT):
@uherr89 @dijun Please read https://wiki.hyperledger.org/labs . This describes the labs ecosystem and what is needed to get a project into incubation

wyatt-noise (Tue, 09 Oct 2018 22:47:20 GMT):
Has joined the channel.

tkuhrt (Thu, 11 Oct 2018 16:59:32 GMT):
@rjones @VipinB @lehors @trbs : Can you all comment on the newest PR for labs: https://github.com/hyperledger-labs/hyperledger-labs.github.io/pull/44

SumanPapanaboina (Sun, 14 Oct 2018 15:36:16 GMT):
Has joined the channel.

nicezic (Mon, 15 Oct 2018 05:28:39 GMT):
Has joined the channel.

mwagner (Tue, 16 Oct 2018 19:20:32 GMT):
Has joined the channel.

salmanbaset (Sun, 21 Oct 2018 23:55:42 GMT):
Has joined the channel.

salmanbaset (Sun, 21 Oct 2018 23:57:12 GMT):
having trouble forking hyperledger-labs.github.io in order to submit a proposal for last 30 minutes. Here is a screenshot. A github issue perhaps?

salmanbaset (Sun, 21 Oct 2018 23:57:28 GMT):

Screen Shot 2018-10-21 at 7.56.28 PM.png

nicezic (Mon, 22 Oct 2018 02:14:06 GMT):
@salmanbaset https://status.github.com/messages I think github has some problems.

nicezic (Mon, 22 Oct 2018 02:14:23 GMT):
I can't push right now too.

nicezic (Mon, 22 Oct 2018 02:15:31 GMT):
oh... I can push, but the site hadn't updated. Now, I can't login to the site.

rjones (Mon, 22 Oct 2018 10:43:33 GMT):
GitHub is down for the last little while

nicezic (Tue, 23 Oct 2018 07:39:11 GMT):
@rjones yes, It has finally recovered.

nicezic (Tue, 23 Oct 2018 08:06:56 GMT):
I posted new pull request : https://github.com/hyperledger-labs/hyperledger-labs.github.io/pull/46

tahaf10 (Wed, 24 Oct 2018 05:46:21 GMT):
Has joined the channel.

john.d.sheehan (Thu, 25 Oct 2018 19:55:52 GMT):
Has joined the channel.

john.d.sheehan (Thu, 25 Oct 2018 20:00:15 GMT):
@rjones @tkuhrt Hi, I get an error when I try to push to `github.com/hyperledger-labs/fabric-vms-provision`, ``` remote: error: GH006: Protected branch update failed for refs/heads/master. remote: error: Required status check "DCO" is expected. ```

rjones (Fri, 26 Oct 2018 06:09:38 GMT):
@john.d.sheehan I apologize for the delay. I replied to your email. I think what you need to do is fork the repo to your personal repo, push there, then file a pull request

john.d.sheehan (Fri, 26 Oct 2018 07:54:25 GMT):
@rjones thank you, that worked

Techievena (Sat, 27 Oct 2018 16:21:35 GMT):
Has joined the channel.

Dan (Fri, 02 Nov 2018 19:56:37 GMT):
I think there were some minor miscommunications in this lab proposal (https://github.com/hyperledger-labs/hyperledger-labs.github.io/pull/49). Mainly that it pasted the PDO description instead of it's own. What do the stewards think about requiring the sponsor to also approve the PR? That would enforce active participation from the sponsor (and assurance that he/she/they had actually sponsored it).

tkuhrt (Fri, 02 Nov 2018 21:11:16 GMT):
Crap! I would be all for that, @Dan

tkuhrt (Fri, 02 Nov 2018 21:11:38 GMT):
Can we get a PR to update this proposal? What shall we do with the lab we created for this?

Dan (Fri, 02 Nov 2018 23:02:49 GMT):
If there's no commits maybe just delete it?

nicezic (Mon, 05 Nov 2018 01:50:14 GMT):
FYI, The Conflict sovled. https://github.com/hyperledger-labs/hyperledger-labs.github.io/pull/46

tkuhrt (Mon, 05 Nov 2018 16:42:29 GMT):
Okay. I will revert PR #49 via https://github.com/hyperledger-labs/hyperledger-labs.github.io/pull/50 and remove the lab that was created for this. Thanks for calling this out @Dan

tkuhrt (Mon, 05 Nov 2018 16:44:03 GMT):
Sometimes I hate Github. Using the revert button didn't do a DCO signoff. I guess I will have to do that in a local fork. New PR coming soon.

tkuhrt (Mon, 05 Nov 2018 16:50:45 GMT):
Lab removed. Let's try again with a new PR.

AlexanderZhovnuvaty (Wed, 07 Nov 2018 15:07:27 GMT):
Has joined the channel.

JonasM (Wed, 14 Nov 2018 15:45:21 GMT):
Has joined the channel.

Silona (Wed, 14 Nov 2018 21:38:59 GMT):
Has joined the channel.

lehors (Tue, 20 Nov 2018 16:39:04 GMT):
hi there

lehors (Tue, 20 Nov 2018 16:39:50 GMT):
I'm unsure what the status of the Convector Framework proposal is https://github.com/hyperledger-labs/hyperledger-labs.github.io/pull/48

lehors (Tue, 20 Nov 2018 16:40:05 GMT):
Is there any reason this is just sitting there?

lehors (Tue, 20 Nov 2018 16:41:19 GMT):
it looks like it's just been forgotten... @tkuhrt @rjones ?

tkuhrt (Mon, 26 Nov 2018 16:16:34 GMT):
Yes...I had somehow missed the last update. I followed up 6 days ago. It seems that we want to transfer the existing code over. This will require ownership modification in Github.

tkuhrt (Mon, 26 Nov 2018 16:17:21 GMT):
@lehors : Do you have a direct connection with the proposer. I want to make sure that we get this resolved.

tkuhrt (Mon, 26 Nov 2018 16:17:21 GMT):
@lehors : Do you have a direct connection with the proposer? I want to make sure that we get this resolved.

tkuhrt (Mon, 26 Nov 2018 20:56:46 GMT):
@lehors : Can you also have a look at https://github.com/hyperledger-labs/hyperledger-labs.github.io/pull/56?

lehors (Tue, 27 Nov 2018 15:04:10 GMT):
[ ](https://chat.hyperledger.org/channel/labs?msg=5rjH4DPWyzmoghaxw) @tkuhrt hi Tracy, I am in contact and following up with them, stay tuned.

lehors (Tue, 27 Nov 2018 15:04:47 GMT):
[ ](https://chat.hyperledger.org/channel/labs?msg=hj2wLkWtst7unvFPp) @tkuhrt done

tkuhrt (Tue, 27 Nov 2018 16:01:38 GMT):
Thanks, Arnaud

ynamiki (Wed, 28 Nov 2018 08:21:13 GMT):
I would like to use "Docker Hub Registry" application in GitHub to build Docker image automatically from our repository. https://github.com/hyperledger-labs/minbft Is it possible for you to grant access to the application in organization "hyperledger-labs"?

ynamiki (Wed, 28 Nov 2018 08:21:29 GMT):
I would like to use "Docker Hub Registry" application in GitHub to build Docker image automatically from our repository. https://github.com/hyperledger-labs/minbft Is it possible for you to grant access to the application in organization "hyperledger-labs"?

trbs (Wed, 28 Nov 2018 09:00:58 GMT):
@tkuhrt @rjones @lehors @VipinB shall we do a Q3 status update like https://wiki.hyperledger.org/labs/2018-q2-update ? (Happy to take a first go at it in the next couple of days)

lehors (Wed, 28 Nov 2018 09:01:27 GMT):
[ ](https://chat.hyperledger.org/channel/labs?msg=2zab5AtgcXocaRXQS) @trbs good idea!

tkuhrt (Wed, 28 Nov 2018 16:41:00 GMT):
+1 @trbs - I have been thinking about it, but it hasn't made it to the top of my list yet

VipinB (Thu, 29 Nov 2018 15:53:13 GMT):
I can help with the report

trbs (Thu, 29 Nov 2018 16:02:51 GMT):
When do we want to have the report done, before the next TSC call ?

trbs (Thu, 29 Nov 2018 16:03:21 GMT):
Also we have https://github.com/hyperledger-labs/hyperledger-community-management-tools/tree/master/project-reports which i am meaning to take a look at :-)

tkuhrt (Thu, 29 Nov 2018 16:13:19 GMT):
I think that before the next TSC call would be ideal @trbs so that we can report then.

tkuhrt (Thu, 29 Nov 2018 16:13:52 GMT):
If you need help on the project-reports, let me know. I wrote it. It is still a work in progress, but will probably give you a lot of detail. I was thinking it might be useful for gathering data for the labs

tkuhrt (Thu, 29 Nov 2018 16:29:43 GMT):

labs-1129.zip

VipinB (Thu, 29 Nov 2018 20:51:28 GMT):
Some of these metrics are quite puzzling like for example we have for crypto-lib dhuseby 2 2018-Sep-29 2018-Sep-29 54201 54197 That is on one day Sep-29-2018 he added 54201 and deleted 54197- What does this mean? Also cryptolib has now graduated to ursa.

VipinB (Thu, 29 Nov 2018 20:54:14 GMT):
For this TSC report, we should focus on the overall picture of the labs. Focus on the more successful projects and then on lessons learnt. Very difficult to tell about the success or efficacy just based on commit statistics which seem to be the main driver of this granular report.

VipinB (Thu, 29 Nov 2018 21:04:24 GMT):
trbs

VipinB (Thu, 29 Nov 2018 21:04:24 GMT):
the insights tab seems to have lots of interesting metrics, including "traffic" where applicable- also we should exclude the commits that were done to get the lab into our github framework-and see whether there are activities that persist beyond just the creation period

tkuhrt (Thu, 29 Nov 2018 22:50:58 GMT):
Agree...that we should only include non-setup commits

tkuhrt (Thu, 29 Nov 2018 22:51:30 GMT):
I did that on the first report: https://wiki.hyperledger.org/labs/2018-q2-update

tkuhrt (Thu, 29 Nov 2018 22:53:00 GMT):
crypto-lib and z-mix are probably labs we will be able to archive as they both went to Ursa.

tkuhrt (Thu, 29 Nov 2018 22:53:22 GMT):
Waiting for Ursa community to ensure we don't archive the repo if they want to move it over.

hartm (Thu, 29 Nov 2018 23:03:01 GMT):
We are planning on moving it over this week.

tkuhrt (Thu, 29 Nov 2018 23:50:26 GMT):
@hartm : are you transferring the repos between Github organizations or manually transferring the code?

hartm (Thu, 29 Nov 2018 23:58:18 GMT):
@tkuhrt I think we are transferring the repos, although I am not sure about the exact process. @MALodder wants to move the code over so that the history is preserved (which makes DCO, among other things, easier to deal with). You can read more specifics in our meeting minutes: https://docs.google.com/document/d/1Z_8o8k_PFRM4XfZyv9jH1_-IyN0CsCMI2JlrGsCX378/edit?usp=sharing.

MALodder (Thu, 29 Nov 2018 23:58:19 GMT):
Has joined the channel.

MALodder (Fri, 30 Nov 2018 00:00:04 GMT):
Yes I’m planning to do this tomorrow

ynamiki (Fri, 30 Nov 2018 06:02:03 GMT):
[ ](https://chat.hyperledger.org/channel/labs?msg=LnDutgjhxkJp7gCRW) @rjones is it possible for you to install "Docker Hub Registry" application in the GitHub organizaion "hyperledger-labs"?

tkuhrt (Fri, 30 Nov 2018 16:32:01 GMT):
@ynamiki : @rjones is on vacation. Can you send an email to helpdesk@hyperledger.org?

PatrickOrtell (Fri, 30 Nov 2018 21:11:23 GMT):
Has joined the channel.

VipinB (Sun, 02 Dec 2018 15:57:45 GMT):
@tkuhrt @lehors @trbs Anything else standing in the way of making the emerald test labs part of labs?

ynamiki (Mon, 03 Dec 2018 04:28:24 GMT):
[ ](https://chat.hyperledger.org/channel/labs?msg=fNNYC6eXqdHstjTop) @tkuhrt @tkuhrt Sure, thanks.

trbs (Mon, 03 Dec 2018 16:26:02 GMT):
@VipinB added comment to the emerald PR.

trbs (Mon, 03 Dec 2018 16:30:00 GMT):
@tkuhrt @lehors @VipinB I wanted to work on the Q3 status report this weekend but family matters happened :( I might not get too it before the next TSC meeting.. maybe somebody else can pick this up or we can delay it to next week ?

VipinB (Mon, 03 Dec 2018 16:35:34 GMT):
I can try

tkuhrt (Mon, 03 Dec 2018 23:40:28 GMT):
@trbs @VipinB @lehors @rjones : Can you check out the following: https://wiki.hyperledger.org/labs/2018-q4-update

lehors (Tue, 04 Dec 2018 12:12:57 GMT):
[ ](https://chat.hyperledger.org/channel/labs?msg=rzzSgFnf9EYP23Y7o) @tkuhrt this LGTM Tracy! Thanks for putting this together. I have one suggestion: I think it would be good to have the total number of PRs merged and the number of PRs merged in the last quarter if that can be figured out without too much headache. This is so one can see the trend. For instance, having 80, 2 would be very different from 80, 40. But it's ok if we don't have that this time around.

VipinB (Tue, 04 Dec 2018 14:02:07 GMT):
@tkuhrt Thanks for that. I was trying to get the Q3 update together (I thought it was Q3 since the last one was Q2); However Tracy has done great work with the Q4 report (should it be Q3 or Q4?). I do think it would be useful to have a list of issues and governance concerns. I do not think we need to go to granular level of PRs. @lehors @trbs @rjones

tkuhrt (Tue, 04 Dec 2018 17:19:34 GMT):
Yea...it looks like we missed the Q3 report so I just combined as information since last report.

tkuhrt (Tue, 04 Dec 2018 17:20:19 GMT):
@lehors for the existing projects, we can just use the last report's number

tkuhrt (Tue, 04 Dec 2018 17:20:55 GMT):
I think that will cover what you are asking for. Specifically, are we still seeing movement for existing labs. We can then just bring this over each time as a "reported last time"

tkuhrt (Tue, 04 Dec 2018 18:09:45 GMT):
@trbs @lehors @VipinB @rjones : I thought it might be good to do a summary of where we are at with our open pull requests so that we can see about moving these forward: * [Convector](https://github.com/hyperledger-labs/hyperledger-labs.github.io/pull/48): Approved. Waiting on transfer of repository to hyperledger-labs organization from the owners. @lehors : Can you follow up with @walmon and see where we are at? * [Private Transaction Families](https://github.com/hyperledger-labs/hyperledger-labs.github.io/pull/52): The last commit had a DCO issue. @Dan can you follow up with @sgurary on this? * [Sawtooth Healthcare](https://github.com/hyperledger-labs/hyperledger-labs.github.io/pull/53): Waiting for review from Lab Stewards. * [Payments Performance Test Harness](https://github.com/hyperledger-labs/hyperledger-labs.github.io/pull/60): It appears that we have one +1 and waiting on one more. * [IBAN Portability](https://github.com/hyperledger-labs/hyperledger-labs.github.io/pull/42): This seems to have had no response from the original submitter since October 8th. Do we leave open? Do we close? Do we attempt to reach back out?

walmon (Tue, 04 Dec 2018 18:09:45 GMT):
Has joined the channel.

Dan (Tue, 04 Dec 2018 18:12:19 GMT):
Yep. I'm told there's some other company process that needs to be done before they can push code out so I think that's the sticking point on Priv. Txn. Fams.

lehors (Tue, 04 Dec 2018 20:09:41 GMT):
[ ](https://chat.hyperledger.org/channel/labs?msg=T9MfJgvGmqB6i67BM) @tkuhrt That sounds good!

lehors (Tue, 04 Dec 2018 20:11:12 GMT):
[ ](https://chat.hyperledger.org/channel/labs?msg=TbQ2hJG28TH3k6mfE) @tkuhrt I actually had a video call with the convector guys. The request to transfer ownership of their repo gave them pause and wanting to know more about what the implications were. They seemed to be reassured and ready to proceed. We'll see.

tkuhrt (Tue, 04 Dec 2018 20:28:19 GMT):
Okay. If they are uncomfortable with the transfer, we can go ahead and create the lab and have them manually import their code. I have held off on this in favor of the transfer since this seemed to be what was desired.

trbs (Tue, 04 Dec 2018 21:34:37 GMT):
I'm +1 on `Payments Performance Test Harness` the only thing left on my previous comment is that I don't think we know what the repository name will be called but I'm sure this is not a big issue.

trbs (Tue, 04 Dec 2018 21:35:55 GMT):
Thanks @tkuhrt & @VipinB for putting the reports together :-)

tkuhrt (Tue, 04 Dec 2018 22:04:09 GMT):
Seems like right now, it will have a long name `payments-performance-test-harness`

tkuhrt (Tue, 04 Dec 2018 22:04:32 GMT):
I don't know that this is a problem. We have one other one that has a pretty long name.

trbs (Tue, 04 Dec 2018 22:41:07 GMT):
imo If it's only going to use emerald-benchmark it might as well has that in it's name and be shorter ;-) if they wish to implement emerald as one of the benchmarks a more generic name makes more sense...

VipinB (Tue, 04 Dec 2018 23:32:14 GMT):
I did not put any report together @trbs; started on Q3, I followed format of regular WG with issues and challenges- let me take another look at what @tkuhrt has put together. Sawtooth Healthcare- I had a comment

VipinB (Tue, 04 Dec 2018 23:32:30 GMT):
IBANP- I followed up but got no response

VipinB (Tue, 04 Dec 2018 23:32:38 GMT):
Will try again

VipinB (Tue, 04 Dec 2018 23:33:07 GMT):
I added +1 on Payments....

tkuhrt (Tue, 04 Dec 2018 23:34:27 GMT):
Thanks, Vipin

VipinB (Tue, 04 Dec 2018 23:51:17 GMT):
I would add to the format: (I can do it if everyone agrees) Overall Health: The labs are doing well, we have attracted many new contributions, many of the existing labs see a lot of continued activity. Two contributions have left the labs and have been welcomed as as a single project under incubation in Hyperledger, in the form of Hyperledger Ursa. Contributions to the labs continue to flow in not only from people associated with the larger projects, but also from newer participants. We have had some discussions about formalizing the role of the sponsor and come up with consensus around language to be added to the charter. There is an ongoing debate around the eligibility of LF staff to sponsor projects. We are also exploring the different metrics around commits and their frequency to surface the community health of the labs in general and individual labs in particular.

VipinB (Tue, 04 Dec 2018 23:52:30 GMT):
Please add to the report if you see fit @trbs, @tkuhrt, @lehors, @rjones

trbs (Wed, 05 Dec 2018 08:39:16 GMT):
@VipinB +1 on the overall health text.

trbs (Wed, 05 Dec 2018 08:40:50 GMT):
@tkuhrt @lehors @rjones @VipinB Idea to add 'latest' commit column to the labs in the report ? (although far from perfect it gives somewhat of a activity / staleness metric)

trbs (Wed, 05 Dec 2018 10:03:47 GMT):
I updated https://wiki.hyperledger.org/labs/2018-q4-update with @VipinB overall health text and last-commit column. Please take look if we want to keep it like this (or revert it back)

trbs (Wed, 05 Dec 2018 10:04:42 GMT):
Could somebody give me commit access on https://github.com/hyperledger-labs/hyperledger-community-management-tools ? I have some updated including but not limited to making it Python 2 & Python 3 compatible :-)

lehors (Wed, 05 Dec 2018 15:52:13 GMT):
[ ](https://chat.hyperledger.org/channel/labs?msg=eCz4fZQyxiDbQMo66) @tkuhrt understood. I told them this was still an option. Let's wait and see what they want to do.

lehors (Wed, 05 Dec 2018 15:58:26 GMT):
[ ](https://chat.hyperledger.org/channel/labs?msg=LEiNX5hYTBiFHHsMt) @VipinB I think that's a good addition, I would however be cautious about claiming that we have consensus on the definition of a sponsor until we have the actual text. Not that I think we disagree, but until we have the actual text it is a bit premature. :-)

lehors (Wed, 05 Dec 2018 15:59:06 GMT):
we might want to say "are converging"

VipinB (Wed, 05 Dec 2018 16:13:15 GMT):
I thought we agreed that your text will be used @lehors

VipinB (Wed, 05 Dec 2018 16:16:52 GMT):
Namely : The role of the sponsor is to officially endorse the proposed lab, indicating in doing so that they believe the proposal is worthy of being given a space among the hyperledger labs. Sponsors may also serve as mentors to the project but how much sponsors are involved in the lab beyond its launch is up to them.

VipinB (Wed, 05 Dec 2018 16:17:58 GMT):
Let us not get caught in endless edits by committee.

VipinB (Wed, 05 Dec 2018 16:19:30 GMT):
In fact we had an action item : Action Item: Lab Stewards to discuss further based on the discussion and come back with a suggestion for how we change the Lab charter.

VipinB (Wed, 05 Dec 2018 16:19:52 GMT):
I move that we adopt Arnaud's text

tkuhrt (Wed, 05 Dec 2018 16:20:06 GMT):
@trbs : I granted you commit access on the hyperledger-community-management-tools lab. Feel free to do a PR and I would be happy to review it.

tkuhrt (Wed, 05 Dec 2018 16:20:12 GMT):
+1 to Arnaud's text

VipinB (Wed, 05 Dec 2018 16:26:22 GMT):
Reporting on the health or status of individual labs back to the TSC was NEVER part of labs, I see that that Nathan has proposed that this be the sponsors responsibility (I do not agree to this). Another proposal was that the stewards report on the individual labs (by Hart and Mic). I do not agree to this as well, due to the opacity of the labs and the fact that there are more than 15 labs. We report on the general progress of the labs based on commit statistics and other indications to the TSC. We set labs up to have a low gating factor and we should push to keep it that way.

VipinB (Wed, 05 Dec 2018 16:27:06 GMT):
--bureaucracy

VipinB (Wed, 05 Dec 2018 16:45:32 GMT):
With the current growth spurt of regular WGs, projects under the greenhouse and SIGs- even quarterly reporting to TSC is facing some hurdles. Especially when people cavalierly ignore their scheduled reporting.

trbs (Wed, 05 Dec 2018 19:46:38 GMT):
@tkuhrt thanks will do

JulienTocci (Sat, 08 Dec 2018 16:48:23 GMT):
Has joined the channel.

MikePapaiacovou (Thu, 13 Dec 2018 07:03:32 GMT):
Has joined the channel.

MikePapaiacovou (Thu, 13 Dec 2018 07:03:36 GMT):
hello all

MikePapaiacovou (Thu, 13 Dec 2018 07:04:36 GMT):
I am looking to build an Open Marketplace with smart contracts, can anyone guide me through using Linux? thanks! :)

aviralwal (Mon, 17 Dec 2018 11:51:02 GMT):
Has joined the channel.

buts101 (Sat, 29 Dec 2018 05:31:50 GMT):
Has joined the channel.

rancifer (Tue, 01 Jan 2019 02:39:58 GMT):
Has joined the channel.

silasdavis (Fri, 04 Jan 2019 17:12:16 GMT):
Has joined the channel.

silasdavis (Fri, 04 Jan 2019 17:14:04 GMT):
Hello labs... I wanted to share project @seanyoung has started that I think has a lot of potential to grow into something rather interesting - we are looking for other maintainers and contributors but I think we would like to propose it to labs before too long. It is a solidity-to-LLVM compiler using modern compiler tooling to generate LLVM IR with an antlr grammar: https://github.com/seanyoung/solang. What we (Burrow) have in mind is using the LLVM WASM backend to create a migration path for existing solidity code and also thinking about WASM-EVM interop within Burrow that can bring with it a host of advantages. In the context of Hyperledger I would like to see WASM emerge as a cross-framework point of integration for different projects (and I know others would too). On top of this it has the advantage of running through sane, mature, modern compiling machinery. I would be grateful for any feedback or guidance - particularly from labs stewards

seanyoung (Fri, 04 Jan 2019 17:14:05 GMT):
Has joined the channel.

silasdavis (Fri, 04 Jan 2019 17:22:49 GMT):
One somewhat noteworthy from the perspective of Hyperledger's licensing practice is that if we license this Apache2 it would provide a compiler for Solidity that was not GPL... though it would not be able to compile to EVM bytecode

silasdavis (Fri, 04 Jan 2019 17:23:11 GMT):
Also perhaps some interest for EEA?

VipinB (Sun, 06 Jan 2019 18:42:45 GMT):
@silasdavis @seanyoung seems like a worthy endeavor to do a solidity to LLVM compiler. Will look further at your proposal or help you write one following the lab template. Thanks for this. I also speak as a lab steward!

tkuhrt (Mon, 07 Jan 2019 21:47:50 GMT):
+1. @silasdavis @seanyoung : Please consider submitting a proposal using the instructions here: https://hyperledger-labs.github.io/

tkuhrt (Mon, 07 Jan 2019 21:48:19 GMT):
@silasdavis : You can serve as a sponsor for this lab

DmitriPlakhov (Thu, 10 Jan 2019 12:04:42 GMT):
Has joined the channel.

LewisFreiberg (Mon, 14 Jan 2019 10:18:11 GMT):
Has joined the channel.

yoni (Sun, 27 Jan 2019 08:21:05 GMT):
Has joined the channel.

samirbalabantaray (Tue, 29 Jan 2019 09:27:15 GMT):
Has joined the channel.

seanyoung (Tue, 29 Jan 2019 12:23:57 GMT):
@VipinB @tkuhrt @silasdavis I've created a proposal for solang to be made a hyperledger labs project. Please let me know if there is anything I can do to improve the proposal. Thanks. https://github.com/hyperledger-labs/hyperledger-labs.github.io/pull/67

VipinB (Tue, 29 Jan 2019 13:52:37 GMT):
@seanyoung I signed off after reviewing the proposal; seems like a worthwhile endeavor

VipinB (Tue, 29 Jan 2019 13:52:37 GMT):
@seanyoung I signed off after reviewing the proposal; seems like a good project that can have unexpected payoffs...

seanyoung (Tue, 29 Jan 2019 14:36:06 GMT):
@VipinB thanks!

Hengming (Thu, 31 Jan 2019 02:52:19 GMT):
Has joined the channel.

MohammedR (Fri, 01 Feb 2019 05:52:10 GMT):
Has joined the channel.

dpitt3 (Tue, 05 Feb 2019 20:06:27 GMT):
Has joined the channel.

dpitt3 (Tue, 05 Feb 2019 20:09:37 GMT):
We've have created a couple of hyperledger fabric tools, here's a link where you'll find info and repo links https://byzantinetools.com . We are interested in submitting a lab proposal pull request for them...

tkuhrt (Tue, 05 Feb 2019 21:46:28 GMT):
We look forward to reviewing your pull request @dpitt 3

dpitt3 (Wed, 06 Feb 2019 20:56:21 GMT):
Thanks just submitted a pull request #70 for two lab projects.

VipinB (Thu, 07 Feb 2019 15:46:04 GMT):
@dpitt3 until DCO signoff as @tkuhrt commented.

walmon (Fri, 08 Feb 2019 15:20:34 GMT):
Hi everybody, sorry I didn't have this app downloaded so never got the notification of you mentioning me. We just transferred the repo and look forward to next steps and how we can work to graduate and make Convector a Hyperledger project!

tkuhrt (Fri, 08 Feb 2019 18:49:43 GMT):
Thanks, @walmon

diestrin (Fri, 08 Feb 2019 21:16:30 GMT):
Has joined the channel.

diestrin (Fri, 08 Feb 2019 21:17:31 GMT):
Hi everyone! We just submitted Convector to labs https://github.com/hyperledger-labs/convector but I notice we didn't get Admin access to the repo, just push access

MALodder (Mon, 11 Feb 2019 16:37:31 GMT):
Has left the channel.

diestrin (Mon, 11 Feb 2019 17:01:01 GMT):
Hey @tkuhrt, can you help us with that?

tkuhrt (Mon, 11 Feb 2019 20:40:27 GMT):
@diestrin : We don't give anyone Admin access to the different lab repositories. I know that @rjones made you a maintainer of the repo. What are you looking to do on the repo that you need Admin access?

diestrin (Mon, 11 Feb 2019 23:04:14 GMT):
hmmm, Arnaud mention we were still going to have admin access to the repo. We can't get to control settings of the repo, like default branches, or merge strategies, just to give an example.

dpitt3 (Tue, 12 Feb 2019 20:44:38 GMT):
We are looking for a labs sponsor for a couple open source HLF tools. Here's a a link to the tools https://byzantinetools.com. If anyone is interested, feel free to contact me at dpitt@keyholesoftware.com

walmon (Thu, 14 Feb 2019 15:55:15 GMT):
@tkuhrt I don't think we can do much without admin access. It's stopping us, for example I can't even assign tickets

rjones (Thu, 14 Feb 2019 15:56:11 GMT):
@walmon what are you trying to do?

rjones (Thu, 14 Feb 2019 15:57:49 GMT):
@walmon I see you still need to accept your invite to get write access. I think that is one step to take

rjones (Thu, 14 Feb 2019 15:58:56 GMT):
@walmon if you go here: https://github.com/hyperledger-labs you should be able to accept your invite.

rjones (Thu, 14 Feb 2019 15:59:11 GMT):
right now @diestrin is the only person that accepted an invite

walmon (Thu, 14 Feb 2019 16:08:53 GMT):
My bad then. Thanks! So it's more about what @diestrin was telling in previous messages. He's flying today though so maybe it's better to wait until he can chat again to explain further

rjones (Thu, 14 Feb 2019 16:14:34 GMT):
@walmon I see you now have write access to the repo. Are you able to assign issues, etc?

walmon (Thu, 14 Feb 2019 17:06:06 GMT):
Yes, all fine for me for now! Thanks

diestrin (Fri, 15 Feb 2019 16:17:39 GMT):
Hey @rjones, so with write access only we cannot for example control things like default branch, add or remove our own collaborators, define any branch strategy, set up any web hooks, integrations or even see any security vulnerability alerts

rjones (Fri, 15 Feb 2019 21:21:34 GMT):
@diestrin I'll break this down

rjones (Fri, 15 Feb 2019 21:22:37 GMT):
default branch: file helpdesk ticket or ask me.

rjones (Fri, 15 Feb 2019 21:24:20 GMT):
add or remove collaborators: this is a subtle thing. You can add existing members of the Hyperledger-labs org to your team or teams, and you can freely create subteams under the team I created for you. What you can't do is invite people to join the Hyperledger-labs org, because github requires org ownership to invite members. Feel free to manage your own team or teams as you like. Please send a helpdesk ticket to get someone invited to the hyperledger-labs org.

rjones (Fri, 15 Feb 2019 21:24:54 GMT):
web hooks, integrations: helpdesk@hyperledger.org

rjones (Fri, 15 Feb 2019 21:25:31 GMT):
security reports: this is an oversight on my part and I will fix that _tout de suite_

kh.nguyen (Fri, 15 Feb 2019 22:43:05 GMT):
Has joined the channel.

walmon (Tue, 19 Feb 2019 16:15:13 GMT):
Hi guys, I've been trying to find some one to help us on this, so I'm just going to share my question here: What's the expected process/path/roadmap for a project to graduate? Requirements or guidance will be very much appreciated, we'd like to focus our efforts and the communities' into this

VipinB (Wed, 20 Feb 2019 00:33:02 GMT):
@walmon graduate to what? a 1.0 in the labs or to a fully fledged project outside labs? For being a project in Hyperledger; you have to write up a project proposal doc which follows the template and get it through the tsc voting.

VipinB (Wed, 20 Feb 2019 00:35:51 GMT):
https://wiki.hyperledger.org/display/HYP/Proposal+Template+for+a+Hyperledger+Project

walmon (Wed, 20 Feb 2019 03:37:34 GMT):
To fully fledged, we were told that one of the main reason projects get to labs is to eventually graduate, and that there are some requirements to be met before (documentation, examples, community, etc). My question is more about what to do before submitting the proposal to have a more aligned proposal.

VipinB (Wed, 20 Feb 2019 03:58:33 GMT):
@walmon main TSC questions would be. What does this project proposal bring to the table that is unique? Usually they approve only proposals that are not client facing (i.e. applications). Other question will be about governance, diversity of contributors (are they from different companies? can the project survive if a group of people (from the same company) left?

VipinB (Wed, 20 Feb 2019 03:58:33 GMT):
@walmon main TSC questions would be. What does this project proposal bring to the table that is unique? Usually they approve only proposals that are not client facing (i.e. not applications). Other question will be about governance, diversity of contributors (are they from different companies? can the project survive if a group of people (from the same company) left?

VipinB (Wed, 20 Feb 2019 03:59:23 GMT):
Of course having greater documentation and other factors help.

alexvicegrab (Thu, 21 Feb 2019 15:35:35 GMT):
Has joined the channel.

dpitt3 (Thu, 28 Feb 2019 17:03:59 GMT):
Just updated our pull request for a lab proposal with DCO and sponsor information https://github.com/hyperledger-labs/hyperledger-labs.github.io/pull/70

avestaa (Fri, 01 Mar 2019 00:29:47 GMT):
Has joined the channel.

noah4477 (Mon, 04 Mar 2019 16:30:13 GMT):
Has joined the channel.

noah4477 (Mon, 04 Mar 2019 16:38:27 GMT):
@tkuhrt Do you have any idea why I can't import com.luxoft.blockchainlab.corda.hyperledger.indy.flow.AssignPermissionsFlow in cordentity? I'm getting an unresolved reference for corda in that import statement

tkuhrt (Tue, 05 Mar 2019 13:46:12 GMT):
@noah4477 : no idea. Is the error occurring when you do the build?

tkuhrt (Tue, 05 Mar 2019 13:47:15 GMT):
@dpitt3 : Just had. Look at your updates. Can you confirm sponsor on the byzantine-browser lab?

noah4477 (Tue, 05 Mar 2019 15:06:13 GMT):
@tkuhrt it sees that it potentially may be fixed in the hyperledger-labs version, but that isn't able to build because everything was migrated to sovrin

noah4477 (Tue, 05 Mar 2019 15:06:19 GMT):
https://jitpack.io/com/github/hyperledger-labs/cordentity/84922aaf03/build.log

noah4477 (Tue, 05 Mar 2019 16:20:34 GMT):
@tkuhrt I'd appreciate if you could approve my pull request. It's simply just changing the repo so that indy 1.7.0 will download

rjones (Tue, 05 Mar 2019 23:33:13 GMT):
@noah4477 add me to the PR please ryjones

noah4477 (Fri, 08 Mar 2019 01:47:53 GMT):
Sorry if it seems if I'm spamming but does anyone know what might cause this flow exception in cordentity net.corda.core.flows.FlowException: Corda service com.luxoft.blockchainlab.corda.hyperledger.indy.service.IndyService does not exist

dpitt3 (Fri, 08 Mar 2019 14:45:24 GMT):
@tkuhrt Don't have a sponsor for byzaninte-browser yet, just a sponsor for byzantine-config

tkuhrt (Mon, 11 Mar 2019 19:30:17 GMT):
@dpitt3 : It might be worth separating them into two distinct PRs then so that we can move the byzantine-config forward. Unless of course you want them to both come in together.

dpitt3 (Tue, 12 Mar 2019 02:56:22 GMT):
Yep.. agree will create a separate PR thanks

alexvicegrab (Thu, 14 Mar 2019 15:09:41 GMT):
Hello, what's teh best way of going forward with this one, @tkuhrt, anything required on our end?: https://github.com/hyperledger-labs/hyperledger-labs.github.io/pull/71

alexvicegrab (Thu, 14 Mar 2019 15:09:41 GMT):
Hello, what's the best way of going forward with this one, @tkuhrt, anything required on our end?: https://github.com/hyperledger-labs/hyperledger-labs.github.io/pull/71

rjones (Thu, 14 Mar 2019 15:12:12 GMT):
@alexvicegrab I think we just need to rattle enough cages to get it merged

VipinB (Thu, 14 Mar 2019 15:48:18 GMT):
I merged the pr since we have enough reviews and dco sign off has been fixed

rjones (Thu, 14 Mar 2019 15:53:17 GMT):
OK. I have created the repo and invited the proper members to both labs and as committers to that lab

rjones (Thu, 14 Mar 2019 15:54:12 GMT):
thank you @VipinB

nicolapaoli (Thu, 14 Mar 2019 16:15:54 GMT):
Has joined the channel.

alexvicegrab (Thu, 14 Mar 2019 22:12:38 GMT):
Thank you, I transfer the repository soon, most probably tomorrow.

noah4477 (Thu, 14 Mar 2019 23:28:05 GMT):
Does anyone have any idea why cordentity might give me an indyservice not found exception

noah4477 (Thu, 14 Mar 2019 23:29:06 GMT):
@tkuhrt Do you have any idea why I'm getting a net.corda.core.flows.FlowException: Corda service com.luxoft.blockchainlab.corda.hyperledger.indy.service.IndyService does not exist in Cordentity?

rjones (Thu, 14 Mar 2019 23:32:41 GMT):
@noah4477 it looks like you should ask:

rjones (Thu, 14 Mar 2019 23:32:47 GMT):
```- https://github.com/voddan - https://github.com/alkopnin - https://github.com/jeremiah - https://github.com/abaaz```

rjones (Thu, 14 Mar 2019 23:33:39 GMT):
Tracy is a lab steward, but those four are the people that proposed it: https://github.com/hyperledger-labs/hyperledger-labs.github.io/pull/57/files#diff-495b2c5440bc63fe26d241bf405bc869

dpitt3 (Fri, 15 Mar 2019 00:26:00 GMT):
@tkuhrt I've created a couple branch pull requests for our labs proposal attempting o get a DCO signoff having difficulty rebasing previous commits, wondering if you could close pull requests and I'll try again. Thanks, David

alexvicegrab (Fri, 15 Mar 2019 11:51:23 GMT):
Hi @rjones, thanks for approving and providing the `nephos` repo. I've migrated the repo, but now want to set up several CI/QA tools that I had in the original repo, namely `Travis CI`, `Snyk`, `SonarQube` and `CodeCov`, as well as setting up protection for the master branch so that I can ensure nobody commits directly to it but can only do PRs How should I do this, as I don't have permissions to do this (e.g. via the GitHub marketplace, and via the settings on the repo itself)? Thanks! Sasha

alexvicegrab (Fri, 15 Mar 2019 11:51:23 GMT):
Hi @rjones, thanks for approving and providing the repo. I've migrated the repo, but now want to set up several CI/QA tools that I had in the original repo, namely `Travis CI`, `Snyk`, `SonarQube` and `CodeCov`, as well as setting up protection for the master branch so that I can ensure nobody commits directly to it but can only do PRs How should I do the latter, as I don't have permissions to do this? Thanks! Sasha

alexvicegrab (Fri, 15 Mar 2019 11:51:23 GMT):
Hi @rjones, thanks for approving and providing the repo. I've migrated the repo, but now want to set up several CI/QA tools that I had in the original repo, namely `Travis CI`, `Snyk`, `SonarQube` and `CodeCov`, as well as setting up protection for the master branch so that I can ensure nobody commits directly to it but can only do PRs How should I do this, as I don't have permissions to do this (e.g. via the GitHub marketplace, and via the settings on the repo itself)? Thanks! Sasha

nicolapaoli (Fri, 15 Mar 2019 16:36:08 GMT):
Hi @tkuhrt @rjones , we already have some people from other companies interested in contributing to Nephos (which is currently included in Hyperledger Labs) but we don't have a place where to share thoughts yet. We are considering to make a public slack channel in our organisation, but probably one in Rocketchat would be the best option. In that way other people from Hyperledger can easily contribute to the project. Would it be possible to have a #Nephos channel for this? Thank you Nicola

rjones (Fri, 15 Mar 2019 17:02:44 GMT):
@nicolapaoli please direct them to this channel

rjones (Fri, 15 Mar 2019 17:03:18 GMT):
We're trying to keep labs in one channel

alexvicegrab (Fri, 15 Mar 2019 17:07:33 GMT):
[ ](https://chat.hyperledger.org/channel/labs?msg=3ACH3cPTBWiE5yvDa) @rjones, @VipinB, @tkuhrt, what's the best procedure to follow on this respect?

rjones (Fri, 15 Mar 2019 17:08:13 GMT):
@alexvicegrab I'm setting some of this up right now.

rjones (Fri, 15 Mar 2019 17:11:46 GMT):
@alexvicegrab time for quick screen share?

alexvicegrab (Fri, 15 Mar 2019 17:11:55 GMT):
Sure, can do now

alexvicegrab (Fri, 15 Mar 2019 17:12:01 GMT):
appear.in/alexvicegrab?

rjones (Fri, 15 Mar 2019 17:12:19 GMT):
does that let me share a window, or only my whole desktop?

alexvicegrab (Fri, 15 Mar 2019 17:12:28 GMT):
Desktop

alexvicegrab (Fri, 15 Mar 2019 17:12:40 GMT):
As far as I am aware

rjones (Fri, 15 Mar 2019 17:14:37 GMT):
join here please: https://zoom.us/j/2032622322

rjones (Fri, 15 Mar 2019 17:40:27 GMT):
oops sorry

rjones (Fri, 15 Mar 2019 17:40:37 GMT):
I didn't know ending the screen share would end the call :(

rjones (Fri, 15 Mar 2019 17:41:00 GMT):
what I was saying is I don't think we can delegate that access.

alexvicegrab (Fri, 15 Mar 2019 17:41:48 GMT):
Great, noted

alexvicegrab (Fri, 15 Mar 2019 17:41:53 GMT):
Many thanks for prompt help

rjones (Fri, 15 Mar 2019 17:50:40 GMT):
join call again plz

GabrieleOcyan (Fri, 15 Mar 2019 19:26:25 GMT):
Has joined the channel.

GabrieleOcyan (Fri, 15 Mar 2019 19:27:18 GMT):
Hello 🙂 I am Gabriele from Ocyan, my team and myself would like to actively collaborate on the Nephos project

gt (Fri, 15 Mar 2019 19:32:29 GMT):
Has joined the channel.

rjones (Fri, 15 Mar 2019 19:55:05 GMT):
@alexvicegrab do you want me to merge https://github.com/hyperledger-labs/nephos/pull/3 ?

gt (Fri, 15 Mar 2019 20:06:16 GMT):
Hello, I'm Genti from Ocyan, can I be added as a contributor on https://github.com/hyperledger-labs/nephos please? I have a pr ready to push.

rjones (Fri, 15 Mar 2019 20:08:03 GMT):
what is your github ID, @genti.t@gmail.com

gt (Fri, 15 Mar 2019 20:08:22 GMT):
genti-t

gt (Fri, 15 Mar 2019 20:08:33 GMT):
Thank you @rjones

rjones (Fri, 15 Mar 2019 20:09:58 GMT):
I sent an invite, but there will be a little turbulence while @alexvicegrab is sorting out CI

gt (Fri, 15 Mar 2019 20:11:15 GMT):
thanks, no prob

alexvicegrab (Fri, 15 Mar 2019 20:35:03 GMT):
[ ](https://chat.hyperledger.org/channel/labs?msg=CydWf66miaXdCSgRf) @rjones Not yet, I need to push an update to the branch to make SonarQube work correctly, but am unable to because all branches are *protected*, rather than only `master`

alexvicegrab (Fri, 15 Mar 2019 20:37:40 GMT):
Also, would it be possible to enable issue tracking and projects on the GitHub repo, or should we prefer doing this on the Hyperledger JIRA?

alexvicegrab (Fri, 15 Mar 2019 20:39:34 GMT):
@gt @GabrieleOcyan, welcome :)

alexvicegrab (Fri, 15 Mar 2019 20:39:49 GMT):
@gt, looking forward to your PR

rjones (Fri, 15 Mar 2019 20:44:59 GMT):
I'll be back home soon

alexvicegrab (Fri, 15 Mar 2019 21:13:01 GMT):
[ ](https://chat.hyperledger.org/channel/labs?msg=Lmz3F3LPt6iDkfCop) My bad, I should have made a fork and PRed from there. Will do this from now on. Thanks for your speedy help, @rjones, much appreciated

VipinB (Sat, 16 Mar 2019 16:31:54 GMT):
So @rjones is the question around individual communication channels for labs; whether they should use the public labs channel or other channels?

VipinB (Sat, 16 Mar 2019 16:35:29 GMT):
I know we probably cannot have individual rocketchat channels for each lab. What I have seen is that people have established channels that they are comfortable with like slack, reddit etc. They could also use the labs channel and mark it so that it is searchable. Iroha bas a telegram channel which they use a bot with to have bridges between RocketChat and Telegram

tkuhrt (Sat, 16 Mar 2019 17:58:03 GMT):
[ ](https://chat.hyperledger.org/channel/labs?msg=6eCaevs3oZXvxBEqy) @rjones in the past, we have created channels for labs. We want all mailing list traffic to go through labs@lists.hyperledget.org using hashtags with lab names, but chat channels are okay. Of course, I have no say over this anymore. Your call.

tkuhrt (Sat, 16 Mar 2019 17:58:04 GMT):
[ ](https://chat.hyperledger.org/channel/labs?msg=6eCaevs3oZXvxBEqy) @rjones in the past, we have created channels for labs. We want all mailing list traffic to go through labs@lists.hyperledget.org using hashtags with lab names, but chat channels are okay. Of course, I have no say over this anymore. Your call.

tkuhrt (Sat, 16 Mar 2019 18:00:30 GMT):
Okay. No idea why that posted twice. Anyways, see #private-data-objects for example

rjones (Sat, 16 Mar 2019 18:11:15 GMT):
@tkuhrt sorry, my confusion. I thought we were trying to limit channels.

rjones (Sat, 16 Mar 2019 18:12:38 GMT):
@tkuhrt as a lab steward you absolutely have the same say in how labs work as you had before.

rjones (Sat, 16 Mar 2019 18:12:42 GMT):
IMHO

epappas (Sat, 16 Mar 2019 18:31:08 GMT):
Has joined the channel.

gt (Mon, 18 Mar 2019 19:01:42 GMT):
@marcello_romani_ocyan

marcello_romani_ocyan (Mon, 18 Mar 2019 19:01:42 GMT):
Has joined the channel.

kenty (Tue, 19 Mar 2019 15:12:50 GMT):
Has joined the channel.

sunlidong (Wed, 20 Mar 2019 10:56:05 GMT):
Has joined the channel.

Vishwas1 (Tue, 02 Apr 2019 09:48:45 GMT):
Has joined the channel.

Vishwas1 (Tue, 02 Apr 2019 09:56:42 GMT):
```Hello everyone, I am going through paper of HL Fabric and trying to understand. I have few questions though, we know that we are planning to implement BFT, my question is, since HL fabric uses _passive replication_ how it is possible to implement BFT? My 2nd question is why do we need to implement BFT since we already know identities of actors (if they do wrong they can be caught right?)``` Pardon if my question does not makes any sense, I am still very new to distributed computing and blockchain stuffs.

walmon (Tue, 02 Apr 2019 12:45:44 GMT):
@Vishwas1 I believe you are in the wrong chat channel for your question, maybe #fabric would be more suitable, this channel is related to hyperledger-labs projects

Vishwas1 (Tue, 02 Apr 2019 12:56:54 GMT):
sorry and thanks @walmon :)

kjensen (Thu, 04 Apr 2019 13:43:03 GMT):
Has joined the channel.

dpitt3 (Tue, 09 Apr 2019 20:59:06 GMT):
I've submitted a pull request, PR#74, for contributing byzantine-config of** https://byzantinetools.com to HLF labs. Not sure of the next steps if any? Thanks, David

Luke_Chen (Wed, 10 Apr 2019 09:31:25 GMT):
Has joined the channel.

Bobbijn (Thu, 11 Apr 2019 17:58:05 GMT):
Has joined the channel.

mc (Fri, 12 Apr 2019 10:52:08 GMT):
Has left the channel.

JeganSelvaraj (Tue, 16 Apr 2019 09:00:49 GMT):
Has joined the channel.

VipinB (Thu, 18 Apr 2019 11:25:43 GMT):
I merged your PR @dpitt3

tkuhrt (Thu, 18 Apr 2019 16:34:07 GMT):
@dpitt3 Were you going to manually bring over the source? If so, @rjones can you create the repo?

rjones (Thu, 18 Apr 2019 16:51:55 GMT):
@tkuhrt I will do this in a little bit. I recently found the DCO check tool so I'd want to run that first

rjones (Fri, 19 Apr 2019 19:18:29 GMT):
@dpitt3 https://github.com/hyperledger-labs/byzantine-config

Silona (Wed, 24 Apr 2019 02:10:20 GMT):
Hey devs, anything exciting going on? please consider submitting a blog post! http://bit.ly/HLEDSubmission

dpitt3 (Fri, 26 Apr 2019 14:38:24 GMT):
Yes, I will bring source code over. @rjones, just let me know when repo is available. Thanks, David

rjones (Fri, 26 Apr 2019 15:46:10 GMT):
@dpitt3 it is available I posted a link above

rjones (Fri, 26 Apr 2019 15:46:45 GMT):
@dpitt3 https://github.com/hyperledger-labs/byzantine-config

Dan (Fri, 26 Apr 2019 19:20:55 GMT):
if anyone is working on a java based consensus implementation plz see #sawtooth-sdk-dev or #sawtooth-consensus-dev there is an open question about adding consensus API support to our java SDK.

dpitt3 (Fri, 26 Apr 2019 20:06:24 GMT):
sorry, will move it thanks..

dpitt3 (Mon, 29 Apr 2019 14:16:10 GMT):
@rjones, thanks for setting up byzantine-config repo... DCO signed all my commits locally, getting a "remote DCO status check error" while trying to push to master? wondering if this is a permission issue..

rjones (Mon, 29 Apr 2019 20:19:49 GMT):
@dpitt3 do you have a moment to screen share?

dpitt3 (Mon, 29 Apr 2019 21:32:26 GMT):
@rjones Just saw this.. I can screen share now if you're available?

rjones (Mon, 29 Apr 2019 21:36:55 GMT):
Ok let me start laptop

dpitt3 (Mon, 29 Apr 2019 21:37:26 GMT):
k

rjones (Mon, 29 Apr 2019 21:38:54 GMT):
https://zoom.us/j/2032622322

MicBowman (Tue, 30 Apr 2019 15:21:24 GMT):
already sent a note about this to the hyperledger helpdesk... but question about project naming... we would like to change the name of the labs project currently called "fabric secure chaincode" to "fabric private chaincode". Would it be easier to rename the repository or to just create a new one?

rjones (Tue, 30 Apr 2019 17:28:41 GMT):
Mic talk to me

rjones (Tue, 30 Apr 2019 17:28:41 GMT):
@MicBowman what exactly do you want changed?

MicBowman (Tue, 30 Apr 2019 17:40:53 GMT):
@rjones @bur can we change the name of the repository?

bur (Tue, 30 Apr 2019 17:40:54 GMT):
Has joined the channel.

rjones (Tue, 30 Apr 2019 17:51:26 GMT):
@MicBowman Perhaps a PR to update the repo name should happen, in the original proposal. That's one way the decision could be made in an open way, votes could be recorded, etc.

MicBowman (Tue, 30 Apr 2019 17:52:08 GMT):
thanks... I'll work with marcus to get that done

MicBowman (Tue, 30 Apr 2019 17:52:26 GMT):
we also talked about just creating a new project but that seems a little "wasteful"

rjones (Tue, 30 Apr 2019 17:53:15 GMT):
Renaming has another benefit which is not obvious - the forks and stars and followers will still exist.

rjones (Tue, 30 Apr 2019 17:54:02 GMT):
but, if you want a new project/repo, I'm not opposed to it, either

MicBowman (Tue, 30 Apr 2019 18:25:36 GMT):
thanks, @rjones** i'll check with @bur tomorrow (kinda late zurich time right now)

dpitt3 (Wed, 01 May 2019 18:27:22 GMT):
@rjones created a new branch but getting another dco status check when trying to push local commits to remote branch . commits in the branch have DCO signoff. Repo is byzantine-config wondering if you could advise? Thanks, David

bur (Thu, 02 May 2019 15:36:41 GMT):
[ ](https://chat.hyperledger.org/channel/labs?msg=MLdfgZsfYrqnNnB8z) @rjones thanks! I will create a PR as advised

bur (Thu, 02 May 2019 15:58:29 GMT):
@rjones @MicBowman you can find the PR here https://github.com/hyperledger-labs/hyperledger-labs.github.io/pull/75

rjones (Thu, 02 May 2019 23:38:27 GMT):
@bur I added @mastersingh24 as a reviewert

rjones (Thu, 02 May 2019 23:38:27 GMT):
@bur I added @mastersingh24 as a reviewer

mastersingh24 (Thu, 02 May 2019 23:38:28 GMT):
Has joined the channel.

AlbertCL (Fri, 03 May 2019 08:31:44 GMT):
Has joined the channel.

bur (Fri, 03 May 2019 08:42:12 GMT):
:thumbsup:

dpitt3 (Mon, 06 May 2019 17:46:55 GMT):
@rjones, another question, trying to push to a branch on byzantine-config, commits have DCO sigs.. getting a protected branch and DCO error?

rjones (Tue, 07 May 2019 17:11:41 GMT):
@dpitt3 don't push directly to a branch. fork to your repo, make changes, then make a PR

dpitt3 (Wed, 08 May 2019 00:51:27 GMT):
@rjones Thanks will do...

bur (Wed, 08 May 2019 08:09:01 GMT):
@rjones Do you think we have enough votes for renaming fabric-secure-chaincode lab? :) WDYT?

rjones (Thu, 09 May 2019 00:16:35 GMT):
@bur done

bur (Thu, 09 May 2019 05:55:28 GMT):
Thanks!

bur (Mon, 13 May 2019 19:12:11 GMT):
@rjones quick question; in fabric-private-chaincodes, for some reason we start collecting stale branches (most probably introduced by some github merging magic) and nobody has permission to delete those branches

bur (Mon, 13 May 2019 19:12:26 GMT):
see here

bur (Mon, 13 May 2019 19:12:27 GMT):
https://github.com/hyperledger-labs/fabric-private-chaincode/branches

bur (Mon, 13 May 2019 19:13:01 GMT):
What permission level do I need to clean up?

rjones (Mon, 13 May 2019 19:24:34 GMT):
@bur when I look here I don't see stale ones? https://github.com/hyperledger-labs/fabric-private-chaincode/branches/stale

bur (Mon, 13 May 2019 19:26:02 GMT):
oh sorry ... I did mean stale in the sense that we dont need them anymore; I was not awaare that the term stale is actually also used there on github. haha

bur (Mon, 13 May 2019 19:28:25 GMT):
for instance, today I've created accidentally mbrandenburger-patch-1 and *-issue-template;

bur (Mon, 13 May 2019 19:28:32 GMT):
how can I remove them again?

bur (Mon, 13 May 2019 19:28:48 GMT):
same for brunos branches

bur (Mon, 13 May 2019 19:28:54 GMT):
they are not needed anymore

rjones (Mon, 13 May 2019 20:04:41 GMT):
Don't worry about them, maybe? Even if you delete them, they're still in the reflog forever

ynamiki (Tue, 21 May 2019 03:15:38 GMT):
Dear Admin of GitHub hyperledger-labs organization, I am a member of MinBFT lab and would like to ask you to install CircleCI GitHub app for our lab. Our lab have been using the app for CI, but sometimes CI is not triggered. I advised to re-install the app for troubleshooting (I have removed the current installation). https://circleci.com/docs/2.0/enable-checks/

rjones (Tue, 21 May 2019 15:50:18 GMT):
@ynamiki Please send email to helpdesk@hyperledger.org

ynamiki (Tue, 21 May 2019 23:46:48 GMT):
@rjones Sure, thanks.

rjones (Thu, 23 May 2019 18:23:09 GMT):
@ynamiki I think circle CI is hooked up now

ynamiki (Fri, 24 May 2019 00:22:21 GMT):
@rjones Thanks, it looks good.

rjones (Mon, 10 Jun 2019 20:12:10 GMT):
If you use GitHub do this: https://help.github.com/en/articles/configuring-two-factor-authentication

rjones (Mon, 10 Jun 2019 20:14:20 GMT):
@all: GitHub two factor auth will be enabled very soon; people without 2FA enabled will be removed from the org. I looked, and about half of our Labs members have not enabled it. Please take a look: https://help.github.com/en/articles/configuring-two-factor-authentication

rjones (Mon, 10 Jun 2019 20:56:06 GMT):
Lab stewards: take a look: https://github.com/hyperledger-labs/hyperledger-labs.github.io/pull/78

YassineAmor (Wed, 12 Jun 2019 10:02:58 GMT):
Has joined the channel.

seanyoung (Sat, 15 Jun 2019 11:01:17 GMT):
@rjones I can no longer push to the solang repo. Do you know anything about this or who could help me? ``` $ git push origin master Enumerating objects: 5, done. Counting objects: 100% (5/5), done. Delta compression using up to 8 threads Compressing objects: 100% (3/3), done. Writing objects: 100% (3/3), 416 bytes | 416.00 KiB/s, done. Total 3 (delta 2), reused 0 (delta 0) remote: Resolving deltas: 100% (2/2), completed with 2 local objects. remote: error: GH006: Protected branch update failed for refs/heads/master. remote: error: Required status check "DCO" is expected. To github.com:hyperledger-labs/solang.git ! [remote rejected] master -> master (protected branch hook declined) error: failed to push some refs to 'git@github.com:hyperledger-labs/solang.git' ```

seanyoung (Sat, 15 Jun 2019 11:17:26 GMT):
Ok I can push to non-master. But branch protection is on so now I cannot delete my new branch "cargo-update". Please can branch protection nly be set for master and develop.

seanyoung (Sat, 15 Jun 2019 11:18:03 GMT):
I do not have access to the repo settings like I have for hyperledger/burrow

rjones (Sat, 15 Jun 2019 13:28:15 GMT):
I changed it for now.

seanyoung (Sat, 15 Jun 2019 14:27:17 GMT):
@rjones perfect thank you very much

EugeneYYY (Fri, 21 Jun 2019 18:11:01 GMT):
Hi, I submitted a HL labs proposal https://github.com/hyperledger-labs/hyperledger-labs.github.io/pull/80. When can I see a response?

VipinB (Wed, 26 Jun 2019 12:29:18 GMT):
The pr was merged.

VipinB (Wed, 26 Jun 2019 12:29:55 GMT):
Name of repository has to be set

rjones (Wed, 26 Jun 2019 12:37:28 GMT):
@EugeneYYY the repo is created. you are invited as maintainer

EugeneYYY (Wed, 26 Jun 2019 23:23:59 GMT):
@VipinB @rjones Thank you! Now I have a question. I don't see "Settings" in the GITHUB UI. Also it seems that anybody in HL Labs currently can approve PRs for TCF. Can you check that maintainer's list is set up correctly or let me know how I should proceed WRT the project contributors management?

rjones (Wed, 26 Jun 2019 23:34:57 GMT):
Please send email to community-architects@hyperledger.org @EugeneYYY

bur (Fri, 12 Jul 2019 09:26:32 GMT):
hey, I was removed from the hyperledger-labs team due to missing 2factor auth :/ After revealing my phone number to github I want to be back on that team :)

bur (Fri, 12 Jul 2019 09:32:25 GMT):
I've created a ticket on jira helpdesk; anything else one can do?

rjones (Fri, 12 Jul 2019 14:40:07 GMT):
Send me mail ry@walledcity.org with your GitHub id

bur (Fri, 12 Jul 2019 22:20:51 GMT):
@rjones thanks! Aric Gardner already added me!

tkuhrt (Thu, 18 Jul 2019 15:44:46 GMT):
@rjones @VipinB @lehors @trbs : question regarding recent PR -- sponsor definition = maintainer of Hyperledger project, TSC member or WG chair. PR lists SIG chair as sponsor. This doesn't meet the criteria. Difference between SIG and WG is the expectation of product output from WG. Thoughts on sponsorship change and presenting that to TSC. I am torn.

VipinB (Thu, 18 Jul 2019 15:53:25 GMT):
@tkuhrt I assume you are referring to https://github.com/hyperledger-labs/hyperledger-labs.github.io/pull/84/files If it helps I can step in as a sponsor as I was involved in the start of the project. However, we have to also look at the spirit and not the letter of the law. May help to clarify with tsc. However, the main idea for labs is to be lightweight and be backed by a community leader. SIGs did not exist at the time when we made this rule.

VipinB (Thu, 18 Jul 2019 15:54:45 GMT):
Telecommsig seems to be more technical than most others. I suspect this will be the same case with #capital-markets-sig

Dan (Fri, 19 Jul 2019 14:00:51 GMT):
We moved the SIGs out of the TSC because they tended to be discussion forums for business people. The intent of the Maintainer/TSC/WG connection for labs submissions is that the labs have some connection to the ongoing work. I'd ask that we require sponsors as indicated.

davidwboswell (Mon, 22 Jul 2019 17:23:18 GMT):
Has joined the channel.

davidwboswell (Mon, 22 Jul 2019 17:25:05 GMT):
@VipinB -- thanks for stepping in as sponsor for the TCSIG labs proposal. separate from the issue of if a SIG Chair can be a sponsor or not, i'm glad you can step in here to move things forward.

VipinB (Mon, 22 Jul 2019 21:28:27 GMT):
I was involved in the initial stages of the ICS write up and project.

VipinB (Mon, 22 Jul 2019 21:31:17 GMT):
It is a classic use case for collaboration between enterprises and seems to have clear benefits. Telecom SIG participants who work on this are clearly subject matter experts, and it is more technical than most SIGs

bur (Mon, 29 Jul 2019 17:56:22 GMT):
Hi here, I want to add more members to hyperledger-labs/fabric-private-chaincode. I've created a ticket at the jira helpdesk. Now I need a TSC approval

bur (Mon, 29 Jul 2019 17:56:30 GMT):
Why is this so complicated?

bur (Mon, 29 Jul 2019 18:00:40 GMT):
I thought the idea of labs is to "lower the pressure on the TSC"

rjones (Tue, 30 Jul 2019 00:41:47 GMT):
@bur because they're wrong.

rjones (Tue, 30 Jul 2019 00:41:52 GMT):
@bur who do you need added

Silona (Tue, 30 Jul 2019 03:21:11 GMT):
Hmm they must have been confused on a labs vs a project ..

Silona (Tue, 30 Jul 2019 03:21:42 GMT):
You can also do these requests to community-architects@hyperledger.org

rjones (Tue, 30 Jul 2019 03:22:03 GMT):
Even then the TSC is not involved in the process

viprat (Thu, 15 Aug 2019 17:45:42 GMT):
Has joined the channel.

viprat (Thu, 22 Aug 2019 08:01:13 GMT):
@rjones I made changes on my PR. I have added @VipinB as a sponsor.

AlexanderZhovnuvaty (Thu, 22 Aug 2019 10:22:01 GMT):
hi. does anybody know if this behavior is acceptable and what to do? trying to merge https://github.com/hyperledger-labs/sawtooth-healthcare/pull/13 pull request in hyperledger labs. But it shows that it is performing certain checks which never ends. It just simply hangs:

AlexanderZhovnuvaty (Thu, 22 Aug 2019 10:24:42 GMT):

Clipboard - August 22, 2019 1:23 PM

AlexanderZhovnuvaty (Thu, 22 Aug 2019 10:25:58 GMT):
It seems it works fine now!

rjones (Fri, 23 Aug 2019 18:27:44 GMT):
@viprat https://github.com/hyperledger-labs/inter-carrier-settlements

viprat (Fri, 23 Aug 2019 19:12:26 GMT):
Thanks @rjones @VipinB

davidwboswell (Tue, 27 Aug 2019 16:50:14 GMT):
@viprat -- thanks for making that addition to add @vipinB as a sponsor.

davidwboswell (Tue, 27 Aug 2019 16:50:48 GMT):
labs stewards -- can you please let us know what the next steps are with the inter carrier settlement labs process? do you need anything else from @viprat to get this set up?

davidwboswell (Tue, 27 Aug 2019 16:51:46 GMT):
@rjones @VipinB @tkuhrt @lehors -- pinging all reviewers on the inter carrier settlement pull request for details on next steps

rjones (Tue, 27 Aug 2019 17:37:56 GMT):
@davidwboswell it's as set up as it's going to be: https://github.com/hyperledger-labs/inter-carrier-settlements they need to start coding

davidwboswell (Tue, 27 Aug 2019 17:55:31 GMT):
oh great. it is set up. nice. ok, was just seeing if there was more that was needed of us and it sounds like there isn't. thank you.

rjones (Tue, 27 Aug 2019 17:55:45 GMT):
It's up to the interns :)

rjones (Tue, 27 Aug 2019 17:55:45 GMT):
It's up to the coders :)

viprat (Tue, 27 Aug 2019 18:25:40 GMT):
@rjones in Telecom SIG right now we have two subgroups one is ICS and other is SLA and we want to upload code for SLA as well. Now we have two options either we could have one repo for telco sig in which we will make sub repos for each use case or other option is we can request for new repo in Hyperledger lab for each use case. Please let me know which one is suitable according to lab rules?

rjones (Tue, 27 Aug 2019 18:36:16 GMT):
I'd create a new lab, honestly

lehors (Tue, 27 Aug 2019 21:13:08 GMT):
I don't think it's so much a matter of what the "rules" are as what makes most sense in terms of how labs are reorganized so that people can easily find the different pieces of code that exist and how they could evolve in the future

lehors (Tue, 27 Aug 2019 21:13:08 GMT):
I don't think it's so much a matter of what the "rules" are as what makes most sense in terms of how labs are organized so that people can easily find the different pieces of code that exist and how they could evolve in the future

lehors (Tue, 27 Aug 2019 21:14:42 GMT):
it seems to me that having everything under a single lab makes it harder for people to find the different sub repos

lehors (Tue, 27 Aug 2019 21:15:41 GMT):
and if one of them at some point were to graduate to a project I think it's cleaner to have them managed as individual repos

lehors (Tue, 27 Aug 2019 21:16:44 GMT):
you could group them by using a common prefix for their name if you'd like, this would give some grouping and yet keep the visibility and independence for each "sub-repo"

rjones (Tue, 27 Aug 2019 22:14:47 GMT):
please, I beg you, don't actually use `git` sub repos. thank you for your forbearance

VipinB (Wed, 28 Aug 2019 11:26:13 GMT):
Just start coding....this is the bane of all software projects

VipinB (Wed, 28 Aug 2019 11:28:17 GMT):
The labs for ICS and SLA need to be separate, unless the ICS depends on SLA and vice - versa @viprat

adlrocha (Mon, 16 Sep 2019 12:48:39 GMT):
Has joined the channel.

rjones (Wed, 18 Sep 2019 15:08:36 GMT):

shubham_aggarwal (Fri, 27 Sep 2019 17:36:23 GMT):
Has joined the channel.

VipinB (Thu, 03 Oct 2019 19:47:24 GMT):
Where is the ICS proposal readme.md is missing in ICS

VipinB (Thu, 03 Oct 2019 19:47:42 GMT):
Any idea @rjones

VipinB (Thu, 03 Oct 2019 19:51:45 GMT):
I found the ICS proposal in labs sub-directory

VipinB (Thu, 03 Oct 2019 19:53:08 GMT):
Just forgot about that.... I think the proposals also need to live in the individual labs for transparency or at least point to the initial proposal

rjones (Thu, 03 Oct 2019 21:48:06 GMT):
@VipinB I got a notification that you said something, but I don't see what/

VipinB (Thu, 03 Oct 2019 22:38:40 GMT):
I got the answer I was looking for

AlexanderZhovnuvaty (Fri, 04 Oct 2019 14:44:53 GMT):
@rjones to overcome DCO issue I followed this video: https://www.youtube.com/watch?v=xI6c-svQxBY&t=369s 1) Roll back to previous valid commit by: git reset and 2) git push force

rjones (Sat, 05 Oct 2019 07:13:07 GMT):
@VipinB @tkuhrt I was speaking of tightly coupled, actual git repos that are sub modules of others.

rjones (Sat, 05 Oct 2019 07:15:15 GMT):
like the kind the `ci-management` repo uses for `global-jjb` as you can see here: https://github.com/hyperledger/ci-management

VipinB (Sat, 05 Oct 2019 16:41:46 GMT):
@rjones I thought you were

shubham_aggarwal (Tue, 08 Oct 2019 11:35:26 GMT):
Can we use travis-ci for labs repo?

shubham_aggarwal (Tue, 08 Oct 2019 11:35:26 GMT):
@rjones Can we use travis-ci for labs repo?

shubham_aggarwal (Tue, 08 Oct 2019 11:35:33 GMT):
As of now it says "You don't have sufficient rights to enable this repo on Travis. Please contact the admin to enable it or to receive admin rights yourself."

VipinB (Tue, 08 Oct 2019 13:50:26 GMT):
@rjones in the case of the labs for inter carrier settlements there are only two committers, @viprat is having difficulty getting his fellow committer to review in time. I propose that in cases where there are only two committers the PR should only require one approval, especially in labs.

VipinB (Tue, 08 Oct 2019 13:51:41 GMT):
This may be due to holidays vacations etc.

VipinB (Tue, 08 Oct 2019 13:52:21 GMT):
I guess only you can make this change as admin @rjones

VipinB (Tue, 08 Oct 2019 13:58:50 GMT):
Are there any other admins for hyperledger git? @dhuseby? Any others?

dhuseby (Tue, 08 Oct 2019 13:58:50 GMT):
Has joined the channel.

rjones (Tue, 08 Oct 2019 21:48:22 GMT):
@VipinB One issue is @Viprat needs to work via pull requests, not directly in the repo.

rjones (Tue, 08 Oct 2019 21:50:43 GMT):
@VipinB there is one branch with any commits and it's a literal blank file. Where is the code?

davidkhala (Wed, 09 Oct 2019 03:13:21 GMT):
Has joined the channel.

davidkhala (Wed, 09 Oct 2019 03:14:09 GMT):
I saw a project in hyperledger labs called 'Hyperledger Fabric Lightweight Client'. I wonder whether this project will cover scope of a mobile application wallet for fabric. And looking forward to meet the project creator. Thanks

rjones (Wed, 09 Oct 2019 03:14:39 GMT):
I haven't seen any commits at all: https://github.com/hyperledger-labs/hyperledger-labs.github.io/blob/master/labs/fabric-lightweight-client.md

rjones (Wed, 09 Oct 2019 03:15:30 GMT):
that file has the documentation they came in with

davidkhala (Wed, 09 Oct 2019 03:25:38 GMT):
Do you have the project proposal or target description?

VipinB (Wed, 09 Oct 2019 09:45:50 GMT):
i saw that too. @viprat told me he deleted. He is using PRs

rjones (Wed, 09 Oct 2019 11:52:33 GMT):
There are no forks: https://github.com/hyperledger-labs/inter-carrier-settlements/network/members and no PRs.

AlexanderZhovnuvaty (Wed, 09 Oct 2019 15:13:20 GMT):

Clipboard - October 9, 2019 6:13 PM

AlexanderZhovnuvaty (Wed, 09 Oct 2019 15:13:21 GMT):
hey guys. can not pass automatic check before merging my commit mote han 30 min - it never ends. pls assist what do i do worng?:

AlexanderZhovnuvaty (Wed, 09 Oct 2019 15:13:52 GMT):
*more than

rjones (Wed, 09 Oct 2019 21:59:15 GMT):
@AlexanderZhovnuvaty those are advisory - not required. You don't need them to complete.

AlexanderZhovnuvaty (Thu, 10 Oct 2019 08:42:08 GMT):
thanks!

nekia (Mon, 14 Oct 2019 06:04:12 GMT):
Has joined the channel.

nekia (Mon, 14 Oct 2019 06:23:45 GMT):
Hi. Can I ask you to create a repository for [the Fabric block archiving project](https://github.com/hyperledger-labs/hyperledger-labs.github.io/blob/master/labs/fabric-block-archiving.md)? We have already had [the existing repository](https://github.com/nekia/fabric-block-archiving), but we'd like to continue development on a repository under the Hyperledger Labs. @rjones

rjones (Mon, 14 Oct 2019 08:48:22 GMT):
@nekia https://github.com/hyperledger-labs/fabric-block-archiving

nekia (Mon, 14 Oct 2019 09:11:12 GMT):
Thanks.

trbs (Wed, 16 Oct 2019 08:56:34 GMT):
FYI https://github.com/orgs/hyperledger-labs/teams/hyperledger-contributors/discussions/2

trbs (Wed, 16 Oct 2019 18:13:24 GMT):
@labstewards should we add to the instructions a bullet asking the submitter of a lab to make sure the sponsor comments on the PR with his/her approval ? Now we have to ask the sponsor either offline or in a comment to confirm sponsorship.

VipinB (Fri, 18 Oct 2019 17:33:42 GMT):
@trbs this assumes that sponsor's have github ids. That may not be the case always.

VipinB (Fri, 18 Oct 2019 17:34:08 GMT):
However, this might be a good thing to do in 95% of the cases

VipinB (Fri, 18 Oct 2019 17:34:08 GMT):
They will have a github id in 90+% of cases

VipinB (Fri, 18 Oct 2019 17:35:57 GMT):
So I am for adding this to the bullet with the caveat that we will do off channel confirmation with sponsor

VipinB (Fri, 18 Oct 2019 17:35:57 GMT):
So I am for adding this to the bullet with the caveat that we will do off channel confirmation with sponsor if they do not have a github id

trbs (Tue, 22 Oct 2019 07:24:45 GMT):
@rjones @lehors @tkuhrt I don't think I have enough permissions to help out @nekia with https://github.com/orgs/hyperledger-labs/teams/hyperledger-contributors/discussions/2?from_comment=1 maybe another steward can change their lab repo to be a clone of the fabric repo ?

rjones (Tue, 22 Oct 2019 07:48:34 GMT):
@trbs I asked a clarifying question ITT.

trbs (Tue, 22 Oct 2019 07:50:37 GMT):
Ack

peter_somogyvari (Thu, 31 Oct 2019 03:49:56 GMT):
Has joined the channel.

peter_somogyvari (Thu, 31 Oct 2019 18:11:58 GMT):
What's the npm package scope we must use for labs projects? @hyperledger/your-package-name or @hyperledger-labs/your-package-name? Would prefer the first option to avoid putting a migration burden on all early adopters in the event of the project graduating, but also understand if there has to be a strict distinction. Please advise. :-) This is the labs project to be specific: https://github.com/hyperledger-labs/blockchain-integration-framework

peter_somogyvari (Thu, 31 Oct 2019 18:13:46 GMT):
User User_1 added by peter_somogyvari.

rjones (Thu, 31 Oct 2019 18:15:59 GMT):
@peter_somogyvari I think if it doesn't collide, I don't have strong feelings. I'm also not a steward

peter_somogyvari (Thu, 31 Oct 2019 18:20:01 GMT):
Thanks @rjones ! Are you aware of a wiki perhaps that I could comb through for governing principles around this? I remember that there was one specifically for naming of the projects, but I lost the link. :/

rjones (Thu, 31 Oct 2019 19:42:21 GMT):
@trbs @tkuhrt @lehors @VipinB thoughts?

VipinB (Thu, 31 Oct 2019 20:29:19 GMT):
The npm package names have not yet come up IIRC. The naming of the projects says that the proposal file should have the same name as the repo (We will also check non-collision with project names). Labs have been setup as a separate organization in github. No problems either way about the npm naming- the labs names do not and will not collide with project names. But prefixing with @hyperledger instead of @hyperledger-labs may give the wrong impression. Therefore my choice is to use @hyperledger-labs. Please also estimate effort for the npm package name change in case of migration to project status; is this not just a change in the package.json file that is part of the release? Also if migrating there should be release notes that will tell users to do a npm install for changing dependencies in package.json. If this is a really heavy lift for early adaptors I can be persuaded to change my mind.

peter_somogyvari (Thu, 31 Oct 2019 21:34:06 GMT):
@VipinB Thank you for weighing in! The developer effort should be pretty minimal indeed, what may give extra headache to certain users is their own processes (new package name means new approval from legal, etc). It shouldn't be a huge effort anyhow and we could make it work with aliases to soften the punch. E.g. in the event of the project graduating we could publish the same package with both scopes, but until the graduation we can just stay on the @hyperledger-labs scope. Making the assumption that this would be fine based on the project names being unique anyway.

peter_somogyvari (Thu, 31 Oct 2019 21:40:48 GMT):
Moving on to my next question: Can we use MPL-2.0 licensed OSS components as part of our lab which is Apache 2.0? Specifically looking to use the distributed lock feature of Consul, but could switch to Apache Zookeeper if there is some issue with MPL-2.0. Consul repo: https://github.com/hashicorp/consul

VipinB (Fri, 01 Nov 2019 11:26:28 GMT):
@peter_somogyvari I think as long as the dependencies are also Apache 2.0 there should be no problem. I do not know what happens if the dependencies are open source but with a different kind of license. Also what happens with a graph of dependencies. This must be the case in any significant project, since the web of dependencies can spread pretty wide. Useful would be to know what would MPL-2.0 OSS depend on. Maybe any of our esteemed colleagues can jump in here with their take on this. @trbs @tkuhrt @lehors

tkuhrt (Fri, 01 Nov 2019 17:38:58 GMT):
For dependencies that are linked in, create a NOTICES file that lists the dependencies and their license. Someone may choose not to use code if they don’t like dependency’s license. If they are dependencies that you are including in the source base, go with Apache 2.0 licenses @peter_somogyvari

tkuhrt (Fri, 01 Nov 2019 17:39:56 GMT):
See the NOTICES file in https://GitHub.com/Hyperledger/sawtooth-core for an example

peter_somogyvari (Fri, 01 Nov 2019 18:46:50 GMT):
Thank you @tkuhrt ! Will go with Apache then.

nekia (Thu, 07 Nov 2019 00:37:09 GMT):
Hi, Now We’re working on [fabric-block-archiving]((https://github.com/hyperledger-labs/fabric-block-archiving) projects under Hyperledger Labs. Currently, our main efforts are put on improvement of reliability. If we can get some feedback on our project from Hyperledger Labs and Hyperledger Fabric community members at the implementation level, that’ll be quite useful for the improvement of UX, I think. Are there any recommended ways to achieve that?

nekia (Thu, 07 Nov 2019 00:37:09 GMT):
Hi, Now We’re working on [fabric-block-archiving](https://github.com/hyperledger-labs/fabric-block-archiving) projects under Hyperledger Labs. Currently, our main efforts are put on improvement of reliability. If we can get some feedback on our project from Hyperledger Labs and Hyperledger Fabric community members at the implementation level, that’ll be quite useful for the improvement of UX, I think. Are there any recommended ways to achieve that?

tkuhrt (Thu, 07 Nov 2019 23:18:39 GMT):
@nekia : I would engage with the Fabric community on their chat channels. You can also post to the Fabric mailing list. Another option might be talking with the Hyperledger Fabric contributes on their next scheduled call, which looks like it is November 13th (https://www.google.com/calendar/event?eid=MjM0bGFlYTUyMHR0N3RkZTA1bnNsMG9kMHBfMjAxOTExMTNUMTQwMDAwWiBsaW51eGZvdW5kYXRpb24ub3JnX25mOXU2NGc5azlydmQ5Zjh2cDR2dXIyM2IwQGc&ctz=Etc/GMT)

nekia (Fri, 08 Nov 2019 02:42:28 GMT):
Thanks @tkuhrt We are now in GMT+11. I'll think about which options are better for us.

sinoz (Tue, 12 Nov 2019 14:28:43 GMT):
Has joined the channel.

devteamdb (Tue, 12 Nov 2019 14:29:21 GMT):
Has joined the channel.

devteamdb (Tue, 12 Nov 2019 14:29:22 GMT):
Hi, we are working on a project in Convector, but running in the following error and have no clue..

devteamdb (Tue, 12 Nov 2019 14:29:36 GMT):

Clipboard - November 12, 2019 3:29 PM

devteamdb (Tue, 12 Nov 2019 14:30:19 GMT):
it started happening after I added a custom function in my convector controller. however, when i remove this function the problem persists. the error message isn't helping either. I have written unit tests that work perfectly fine and all pass. the API server i have regurgitates this error after packaging up my chaincode

rpocase (Tue, 12 Nov 2019 19:15:31 GMT):
Has joined the channel.

shubham_aggarwal (Thu, 14 Nov 2019 04:55:17 GMT):
hey @rjones can you please remove circleci from https://github.com/hyperledger-labs/fabric-chaincode-wasm

shubham_aggarwal (Thu, 14 Nov 2019 04:55:18 GMT):
We have decided to go with github actions

rjones (Thu, 14 Nov 2019 05:22:43 GMT):
@shubham_aggarwal done

shubham_aggarwal (Thu, 14 Nov 2019 05:23:06 GMT):
Thanks @rjones

nekia (Mon, 18 Nov 2019 23:29:57 GMT):
Hi @rjones can I setup azure pipeline for https://github.com/hyperledger-labs/fabric-block-archiving? Currently I can't choose this repository from my azure account(linked with Github).

rjones (Tue, 19 Nov 2019 00:29:16 GMT):
@nekia is there an existing YAML I should link to?

nekia (Tue, 19 Nov 2019 00:57:44 GMT):
We don't have azure-pipelines.yml for this repo yet.

nekia (Tue, 19 Nov 2019 01:20:12 GMT):
OK, I'll let you know after creating YAML for pipeline. @rjones

rjones (Tue, 19 Nov 2019 05:29:00 GMT):
@nekia I added you as an admin to https://dev.azure.com/Hyperledger/fabric-block-archiving so I think you have all of the permissions you should need to add and activate a pipeline - let me know if you hit any blockers, OK?

nekia (Tue, 19 Nov 2019 07:14:42 GMT):
That's great. Thanks @rjones

davidkhala (Tue, 19 Nov 2019 07:20:11 GMT):
@rjones Hi Ry, we have created a proposal of two repository originally incubated from internship program https://github.com/hyperledger-labs/hyperledger-labs.github.io/pull/103, could you help to notify maintainer to review and etc.?

rjones (Tue, 19 Nov 2019 07:46:59 GMT):
@davidkhala that's up to the lab stewards to handle, and they are already code reviewers. thanks.

VipinB (Tue, 19 Nov 2019 17:28:30 GMT):
Have commented on the PR @davidkhala

rjones (Thu, 21 Nov 2019 18:45:30 GMT):
Quick question for @tongli : did this lab get created? https://github.com/hyperledger-labs/hyperledger-labs.github.io/pull/82

tongli (Thu, 21 Nov 2019 18:45:30 GMT):
Has joined the channel.

rjones (Thu, 21 Nov 2019 19:16:10 GMT):
It doesn't look like this code ever came over: https://github.com/hyperledger-labs/hyperledger-labs.github.io/pull/97

tongli (Thu, 21 Nov 2019 19:25:12 GMT):
@rjones PR 82 was merged. The repo was created. and we have put code in the repo.

tongli (Thu, 21 Nov 2019 19:25:26 GMT):
https://github.com/hyperledger-labs/fabric-consortium-management

tongli (Thu, 21 Nov 2019 19:26:23 GMT):
it is just that I do not have awhole lot of permissions to change anything to the lab repo.

tongli (Thu, 21 Nov 2019 19:27:13 GMT):
if you @rjones can make me the admin, that will be really nice.

rjones (Thu, 21 Nov 2019 19:29:31 GMT):
have fun!

nekia (Fri, 22 Nov 2019 02:48:46 GMT):
I could activate a pipeline for our project. Thank you @rjones Can I also ask you to enable 'issue' menu on our repo? https://github.com/hyperledger-labs/fabric-block-archiving

rjones (Fri, 22 Nov 2019 17:56:56 GMT):
I started an email thread on archiving some inactive labs. Please read here: https://lists.hyperledger.org/g/labs/topic/61114709#74 and take a look at the pull request https://github.com/hyperledger-labs/hyperledger-labs.github.io/pull/107

nekia (Sat, 23 Nov 2019 12:17:27 GMT):
Thanks @rjones

rjones (Sat, 23 Nov 2019 18:54:26 GMT):
Let me know if you need adjustments

rjones (Mon, 25 Nov 2019 19:57:46 GMT):
https://wiki.hyperledger.org/display/labs/Umbra+25+NOV+2019

AlexanderZhovnuvaty (Tue, 26 Nov 2019 13:59:16 GMT):
Looking for fabric developer to join our team that works on open source project (healthcare sphere). DM me if anything:)

seanyoung (Tue, 26 Nov 2019 19:29:44 GMT):
Hello, I would like to ask if I can use hyperledger anywhere in the name/title/documentation of my solang labs project. I'm not sure what the right balance is there.

sarkoi (Wed, 27 Nov 2019 15:05:52 GMT):
Has joined the channel.

iampukar (Thu, 28 Nov 2019 06:12:38 GMT):
Has joined the channel.

tkuhrt (Thu, 05 Dec 2019 20:07:32 GMT):
@seanyoung : I believe you use it as such "solang, a Hyperledger Lab"

tkuhrt (Thu, 05 Dec 2019 20:11:22 GMT):
From the original Lab proposal "Labs representation It is not permitted to publicly refer to work under the hyperledger-labs org as an “Hyperledger project” and directly use the Hyperledger brand as in “Hyperledger ”. One may refer to this type of work as a “Hyperledger Lab” and use “, a Hyperledger Lab.” "

seanyoung (Fri, 06 Dec 2019 11:19:15 GMT):
great, thank you very much

rjones (Tue, 10 Dec 2019 22:26:49 GMT):
There has been a request to un-archive https://github.com/hyperledger-labs-archives/private-transaction-families .

rjones (Tue, 10 Dec 2019 22:27:18 GMT):
If the stewards want that, please file a PR to move the file back to the right place, merge it, and I'll move it over

tkuhrt (Wed, 11 Dec 2019 00:31:51 GMT):
@rjones : It would be great if the requester could file this PR so that the lab stewards can review/approve. Was this what you were suggesting?

rjones (Wed, 11 Dec 2019 02:42:17 GMT):
@tkuhrt yes.

rjones (Wed, 11 Dec 2019 02:43:08 GMT):
@yoni ^^^

Silona (Wed, 11 Dec 2019 21:46:45 GMT):
Hello everyone - Do you know of a developer event that we would like to get some Hyperledger representation at? Please submit it here. The marketing committee will review them all as we go thru our budget for 2020 Thank you! - Silona

Silona (Wed, 11 Dec 2019 22:02:11 GMT):
https://wiki.hyperledger.org/display/Marketing/Developer+Events

Hengming (Fri, 13 Dec 2019 04:09:46 GMT):
Great post for this year’s Mentorship Program. Thanks Hyperledger community! https://www.hyperledger.org/blog/2019/12/12/2019-summer-mentee-project-update-hyperledger-fabric-sdk-for-node-js-security-extension

harrywright (Wed, 18 Dec 2019 17:46:15 GMT):
Has joined the channel.

bobsummerwill (Mon, 23 Dec 2019 07:30:11 GMT):
Hey everyone! Thanks so much for accepting our https://ethercluster.com project into HL Labs :-) https://github.com/hyperledger-labs/hyperledger-labs.github.io/pull/108

bobsummerwill (Mon, 23 Dec 2019 07:30:30 GMT):
You can read more about Ethercluster at https://medium.com/ethereum-classic/ethercluster-an-open-source-alternative-to-infura-b8799b2122d3

bobsummerwill (Mon, 23 Dec 2019 07:31:17 GMT):
It is our crown jewel and I am delighted that it will now have a bigger stage within HL Labs.

bobsummerwill (Mon, 23 Dec 2019 07:31:40 GMT):
Current home = https://github.com/ETCCooperative/ethercluster

bobsummerwill (Mon, 23 Dec 2019 09:41:29 GMT):
https://ethereumclassic.org/blog/2019-12-22-coop-contributes-ethercluster-to-hyperledger-labs/

VipinB (Mon, 23 Dec 2019 23:10:39 GMT):
@bobsummerwill Yaz, welcome to HL Labs ! Ethercluster will be a good addition.

Yazanator (Thu, 26 Dec 2019 20:04:44 GMT):
Has joined the channel.

Yazanator (Thu, 26 Dec 2019 20:06:08 GMT):
@VipinB thank you very much, very happy to be here and thank you for everything!

Silona (Thu, 09 Jan 2020 20:18:48 GMT):
Last chance! The Linux Foundation worked with Hyperledger Fabric Developer subject matter expert volunteers to identify the core domains and competencies for the Certified Hyperledger Fabric Developer (CHFD) exam, scheduled to launch in March 2020. Are you interested in participating in the Beta and receiving an early peek? The CHFD Beta is FREE for the first 100 who take the exam. Complete the CHFD Beta Sign-up Form by January 15, 2020 for your chance. If you pass you will be CHFD Certified!

Silona (Tue, 14 Jan 2020 16:50:35 GMT):
Help Us Help you! Attend the Developer Relationship Meeting with Myself and our Marketing Dept. tomorrow at 9:00am Pacific Time. For the agenda and Dial in info https://wiki.hyperledger.org/display/Marketing/2020-01-15+Meeting+notes

Yazanator (Wed, 15 Jan 2020 16:27:02 GMT):
thanks @Silona I'll join this call

indirajith (Fri, 17 Jan 2020 11:25:55 GMT):
Has joined the channel.

gt (Mon, 20 Jan 2020 16:05:27 GMT):
ldap

dineshthemacho1 (Wed, 22 Jan 2020 06:07:37 GMT):
Has joined the channel.

swetha (Thu, 23 Jan 2020 16:13:12 GMT):
Has joined the channel.

jordy24 (Thu, 23 Jan 2020 16:29:18 GMT):
Has joined the channel.

jordy24 (Thu, 23 Jan 2020 16:29:19 GMT):
Hi , could some one please add me on the hyperledger-labs organization so I be added to the fabric-private-chaincode team

jordy24 (Thu, 23 Jan 2020 16:33:52 GMT):
my github is jordy24 (jordykaraze), thanks

rjones (Thu, 23 Jan 2020 16:36:39 GMT):
@jordy24 done

jordy24 (Thu, 23 Jan 2020 16:45:15 GMT):
thanks @rjones

jordy24 (Thu, 23 Jan 2020 16:48:52 GMT):
@rjones some of my team members can not see me on the list as a contributor..... how could I get on there??

rjones (Thu, 23 Jan 2020 16:49:26 GMT):
I don't know what you mean. What are you expecting, and where do you expect it?

jordy24 (Thu, 23 Jan 2020 16:52:05 GMT):
so basically I would like to be able to contribute on the fabric-private-chaincode

jordy24 (Thu, 23 Jan 2020 16:53:33 GMT):
@rjones could you add me on this https://github.com/orgs/hyperledger-labs/teams/hyperledger-contributors/members

rjones (Thu, 23 Jan 2020 16:54:50 GMT):
You need to accept the invite.

rjones (Thu, 23 Jan 2020 16:54:59 GMT):
you should have gotten an email

jordy24 (Thu, 23 Jan 2020 16:55:21 GMT):
oh okay let me check

rjones (Thu, 23 Jan 2020 16:56:07 GMT):
@MicBowman or @swetha will need to add you here to have merge ability: https://github.com/orgs/hyperledger-labs/teams/fabric-private-chaincode-committers/members but you need none of this to, for example, file pull requests and the like

jordy24 (Thu, 23 Jan 2020 17:01:21 GMT):
@rjones thanks, I had not seen the email... but now that works...

MicBowman (Thu, 23 Jan 2020 17:15:33 GMT):
@jordy24 i believe i just approved you

MicBowman (Thu, 23 Jan 2020 17:18:27 GMT):
@rjones i think @tkuhrt is the only maintainer on the private data objects repo. could you make/add me as maintainer?

rjones (Thu, 23 Jan 2020 17:49:24 GMT):
@MicBowman done: https://github.com/orgs/hyperledger-labs/teams/private-data-objects-committers/members

seanyoung (Fri, 24 Jan 2020 09:14:13 GMT):
I've accidentally accepted a PR with pseudonyms in the commit Signed-off-by (DCO). I have contacted the author and he has said it is okay to rebase with his real name. See: https://github.com/hyperledger-labs/solang/commit/1ae07d5d69c8e789e009a926062d35c40d076226 However, I do not have rights to force-push to master and neither am I convinced that it's a great idea. What's the best way to proceed here?

rjones (Fri, 24 Jan 2020 14:01:48 GMT):
@seanyoung I would have them sign an empty commit from the correct address. `git commit -s --allow-empty` with a message something like "I am $name, signing commit 1ae... for myself"

seanyoung (Fri, 24 Jan 2020 17:14:19 GMT):
@rjones good idea. Thanks

rjones (Fri, 24 Jan 2020 17:19:51 GMT):
@seanyoung I'm not sure exactly how to prove anything, but it would work. Easier than `git push -f`

seanyoung (Sun, 26 Jan 2020 12:50:44 GMT):
@rjones commit merged, see https://github.com/hyperledger-labs/solang/commit/c39025ff1b50274f0da7242122a113092772c706

Dan (Mon, 27 Jan 2020 17:14:28 GMT):
Hi Everyone, We are hoping to hear from everyone as we assess the health of our open source community. Please take 2 minutes to respond here: https://www.surveymonkey.com/r/DCIWGsurvey

rjones (Mon, 27 Jan 2020 20:43:01 GMT):
I would like feedback on this page: https://wiki.hyperledger.org/display/labs/Driving+growth+of+Hyperledger+Labs from anyone, but in particular stewards. I'd like to have a meeting after the TSC call on 06 FEB: https://lists.hyperledger.org/g/labs/viewevent?eventid=703905&calstart=2020-02-06

MicBowman (Mon, 27 Jan 2020 20:47:31 GMT):
@rjones i'm very interested in participating in the call but i'm not available on the 6th. is that date fixed?

rjones (Mon, 27 Jan 2020 20:49:36 GMT):
It is not. I was looking to attach onto the tail of a TSC call, but I'm not married to it. I also wanted to give time for the topic to develop in the wiki.

rjones (Mon, 27 Jan 2020 20:50:24 GMT):
would the week after be OK? I don't want to delay too long, but I also don't want to do it this week :)

MicBowman (Mon, 27 Jan 2020 20:50:31 GMT):
in general that time is fine... just in this case i'm traveling on the 6th. so... know that i'm interested & will gladly participate if we can find a day

MicBowman (Mon, 27 Jan 2020 20:50:38 GMT):
yes... 13th would be fine

rjones (Mon, 27 Jan 2020 20:51:42 GMT):
I'll wait a little bit for feedback from @tkuhrt @VipinB @trbs and @lehors and change it later today

tkuhrt (Mon, 27 Jan 2020 21:25:49 GMT):
Added some thoughts on the page. Can you provide more context on what is driving this discussion, @rjones ?

Silona (Mon, 27 Jan 2020 22:27:01 GMT):
The Linux Foundation’s CommunityBridge engineers are working on a tool to measure the health of critical open source projects and one of the key areas identified is QA Testing. They request that our communities provide honest and detailed information on testing tools and methodologies you use in your projects for us to come up with a detailed analysis, which they will share with all respondents and projects. https://www.surveymonkey.com/r/9H5G2GV. It’s only 5 questions long.

VipinB (Tue, 28 Jan 2020 15:12:42 GMT):
@rjones anything specific for the meeting. I have made some comments on the page.

VipinB (Tue, 28 Jan 2020 15:12:42 GMT):
@rjones anything specific for the meeting? I believe @tkuhrt also asked. I have made some comments on the page.

peter_somogyvari (Thu, 30 Jan 2020 20:27:14 GMT):
Looking to push `BIF` packages to npm. Does anyone know how can I get access to the @hyperledger-labs package scope/npm org? My npm username is `peter.somogyvari`

rjones (Thu, 30 Jan 2020 21:39:28 GMT):
@peter_somogyvari please send email to community-architects@hyperledger.org I’ll handle it

rjones (Thu, 30 Jan 2020 21:41:26 GMT):
Invite sent

peter_somogyvari (Thu, 30 Jan 2020 22:13:47 GMT):
Thank you @rjones accepted the invitation and now I (assume) I can publish publish packages under the @hyperledger org, but earlier we discussed that for labs projects it would be better if they published under @hyperledger-labs which I think means that there has to be another npm org with that name (not aware of npm having a feature where you can have multiple scopes under one org but if it exists then never mind everything I just said). Are you aware of another org on npm for labs? Also, if the situation have changed since we last talked about (on this channel, a few months back) and now it's okay for labs to publish on the main @hyperledger scope, then I am happy to do just that, just let me know.

rjones (Thu, 30 Jan 2020 22:20:07 GMT):
Give me a bit to work this out

peter_somogyvari (Thu, 30 Jan 2020 23:03:06 GMT):
Got the invite, cheers

rjones (Thu, 30 Jan 2020 23:03:38 GMT):
sure thing. I think you're good to go at this point?

peter_somogyvari (Thu, 30 Jan 2020 23:04:38 GMT):
I should be as far as I know. Will try to publish a package with the labs scope and report back if there's any issues (don't foresee having any) Thank you very much once again!

seanyoung (Thu, 06 Feb 2020 19:59:57 GMT):
Hello. I'm considering proposing Solang to go into incubation. Is there anything I need to do the repo to make that move possible, and maybe more importantly, what are people's opinion on Solang becoming a full project?

seanyoung (Thu, 06 Feb 2020 19:59:57 GMT):
Hello. I'm considering proposing Solang to go into incubation. Is there anything I need to do in the repo to make that move possible, and maybe more importantly, what are people's opinion on Solang becoming a full project?

tkuhrt (Thu, 06 Feb 2020 22:12:00 GMT):
Hi, @seanyoung. There should not be anything specific that you would need to do to the repository. You may have heard in the TSC call today the discussion around the [repository structure task force recommendations](https://wiki.hyperledger.org/display/TF/Repository+Structure+Task+Force) being a soft requirements for labs. Looking at the [contributors](https://github.com/hyperledger-labs/solang/graphs/contributors), I would imagine that one of the questions that will come up is surrounding diversity. As always, there will be conversations about how you would foresee this working with the other projects within Hyperledger.

seanyoung (Fri, 07 Feb 2020 10:13:00 GMT):
Thank you for htat

seanyoung (Fri, 07 Feb 2020 10:13:00 GMT):
Thank you

seanyoung (Fri, 07 Feb 2020 10:13:52 GMT):
I've started looking at repo structure, I'll make some more changes around that.

rjones (Fri, 07 Feb 2020 15:47:58 GMT):
I took a stab at your "good first bug" and, all I can say is - coming from C, rust is an experience :)

seanyoung (Fri, 07 Feb 2020 15:52:00 GMT):
It really is very different! I'm also very much a C-type person. It took quite some time to get used to rust.

jamesbarry (Mon, 10 Feb 2020 17:49:10 GMT):
Has joined the channel.

rpocase (Mon, 10 Feb 2020 19:41:32 GMT):
Has left the channel.

Silona (Thu, 13 Feb 2020 18:25:05 GMT):
Howdy Contributors and Maintainers! Are you wondering about tapping into Developer marketing for your group or project? Do you have a blog post idea? An awesome announcement? Please attend our Contributor/marketing meeting! https://wiki.hyperledger.org/display/Marketing/2020-02-19+Meeting+notes

Silona (Mon, 17 Feb 2020 22:18:47 GMT):
Are you wondering about tapping into Developer marketing for your group or project? Do you have a blog post idea? An awesome announcement? Please attend TOMORROW! https://wiki.hyperledger.org/display/Marketing/2020-02-19+Meeting+notes

VipinB (Tue, 18 Feb 2020 16:06:11 GMT):
https://github.com/hyperledger-labs/hyperledger-labs.github.io/pull/114 Please review. Would like to get this approved before TTF which is tomorrow.

VipinB (Tue, 18 Feb 2020 16:06:22 GMT):
TTF workshop

alifatemy (Wed, 19 Feb 2020 06:10:15 GMT):
Has joined the channel.

alifatemy (Wed, 19 Feb 2020 06:10:16 GMT):
Hello Mr Jonse Thanks a lots for about Umbera hyperledger fabric Project I am a senior student of E-Commerce and I want to use hyperledger fabric blockchain in iot field for my thesis. I have been installed and passed initial steps and i do'nt know how to use Umbera that means to use hyperledger fabric in containernet, this question because of not to be example for this .I have run the config_fabric_example.json but I dont know what i do after run, what was it happened there? Thanks a lot

alifatemy (Wed, 19 Feb 2020 06:12:25 GMT):
this is result of my run a simple its(umbera) case( config_fabric_simple.json):

alifatemy (Wed, 19 Feb 2020 06:13:22 GMT):
-> start

alifatemy (Wed, 19 Feb 2020 06:13:25 GMT):
->create docker network

alifatemy (Wed, 19 Feb 2020 06:13:35 GMT):
346571683....

alifatemy (Wed, 19 Feb 2020 06:13:51 GMT):
->start umbera_senarios

alifatemy (Wed, 19 Feb 2020 06:14:18 GMT):
->start umbera_orch

alifatemy (Wed, 19 Feb 2020 06:14:46 GMT):
running config_fabric_simple.json

alifatemy (Wed, 19 Feb 2020 06:15:06 GMT):
Deploy config in umbera_orch

alifatemy (Wed, 19 Feb 2020 06:16:01 GMT):
I dont know what i do now. please help me

alifatemy (Wed, 19 Feb 2020 06:33:24 GMT):
Hello Mr Jonse Thanks a lots for about Umbera hyperledger fabric Project I am a senior student of E-Commerce and I want to use hyperledger fabric blockchain in iot field for my thesis. I have been installed and passed initial steps and i do'nt know how to use Umbera that means to use hyperledger fabric in containernet, this question because of not to be example for this .I have run the config_fabric_example.json but I dont know what i do after run, what was it happened there? Thanks a lot this is result of my run a simple its(umbera) case( config_fabric_simple.json): -> start ->create docker network 346571683.... ->start umbera_senarios ->start umbera_orch running config_fabric_simple.json Deploy config in umbera_orch I dont know what i do now. please help me

alifatemy (Wed, 19 Feb 2020 07:56:33 GMT):
Hello Mr rjones Thanks a lots for about Umbera hyperledger fabric Project I am a senior student of E-Commerce and I want to use hyperledger fabric blockchain in iot field for my thesis. I have been installed and passed initial steps and i do'nt know how to use Umbera that means to use hyperledger fabric in containernet, this question because of not to be example for this .I have run the config_fabric_example.json but I dont know what i do after run, what was it happened there? Thanks a lot this is result of my run a simple its(umbera) case( config_fabric_simple.json): -> start ->create docker network 346571683.... ->start umbera_senarios ->start umbera_orch running config_fabric_simple.json Deploy config in umbera_orch I dont know what i do now. please help me

tkuhrt (Wed, 19 Feb 2020 13:54:27 GMT):
@dhuseby ^ can you help with questions on Umbra?

alifatemy (Thu, 20 Feb 2020 13:55:34 GMT):
yes, off corse I am knowing about fabric structure(linux fundation courses) and about cotainernet, but idont know for example

alifatemy (Thu, 20 Feb 2020 13:57:28 GMT):
for example, if i want to use containernet example, I can easy to see a running example in terminal and to use for test(pingall and etc) and etc

alifatemy (Thu, 20 Feb 2020 14:02:28 GMT):
and for umbera what i do now that can to customize for my work( use fabric in smart home)

ROHAN_SHROTHRIUM (Fri, 21 Feb 2020 14:51:45 GMT):
Has joined the channel.

ROHAN_SHROTHRIUM (Sat, 22 Feb 2020 09:44:59 GMT):
Hello everyone! I've been trying to set up Umbra but I am unable to run it as the 'config_fabric_simple.json' file is not getting generated after building the confiigs I tried running it with 'Fabric-Simple-01.json' but this gives a AttributeError: 'Client' object has no attribute 'api' in the scenario.log file. Can someone please help me with this...

alifatemy (Sun, 23 Feb 2020 16:27:19 GMT):
Hello again everyone

alifatemy (Sun, 23 Feb 2020 16:29:29 GMT):
I want for example to use a senario in umbera fabric in a way to see produce data and to be to write in terminal, i dont know what i do, please help me

alifatemy (Sun, 23 Feb 2020 16:47:14 GMT):
for exampl i know that , $ sudo -H ./run.sh start -c ./fabric/fabric_configs/config_fabric_simple.json $ sudo -H ./run.sh stop Or i know $ tail -f ./logs/broker.log $ tail -f ./logs/scenario.log for display log but which log or how do i log in brocker or desing log

alifatemy (Sun, 23 Feb 2020 16:47:15 GMT):
?

alifatemy (Sun, 23 Feb 2020 16:49:24 GMT):
Hello again everyone I want for example to use a senario in umbera fabric in a way to see produce data and to be to write in terminal, i dont know what i do, please help me: for example i know that , $ sudo -H ./run.sh start -c ./fabric/fabric_configs/config_fabric_simple.json is for run example or : $ sudo -H ./run.sh stop is for stop running Or i know $ tail -f ./logs/broker.log is for disply log $ tail -f ./logs/scenario.log is for display log but which log or how do i log in brocker or scenario log?

alifatemy (Sun, 23 Feb 2020 16:50:21 GMT):
Hello again everyone I want for example to use a senario in umbera fabric in a way to see produce data and to be to write in terminal, i dont know what i do, please help me: for example i know that , $ sudo -H ./run.sh start -c ./fabric/fabric_configs/config_fabric_simple.json is for run example or : $ sudo -H ./run.sh stop is for stop running Or i know $ tail -f ./logs/broker.log is for disply log $ tail -f ./logs/scenario.log is for display log but which log or how do i log in brocker or scenario log?

rjones (Sun, 23 Feb 2020 18:08:22 GMT):
@dhuseby ^^^

alifatemy (Tue, 25 Feb 2020 03:56:16 GMT):
Hello Mr rjones, please help me.

rjones (Tue, 25 Feb 2020 15:45:41 GMT):
I talked to David, he said he put you in touch with the developer directly

doomguy (Wed, 26 Feb 2020 11:48:33 GMT):
Has joined the channel.

doomguy (Wed, 26 Feb 2020 11:48:34 GMT):
Hello all ! I've found Cordenity project on github [https://github.com/hyperledger-labs/cordentity] to integrate Indy capabilities into the Corda platform. Is there something similar, but for HL Fabric ?

doomguy (Wed, 26 Feb 2020 12:07:59 GMT):
I mean a seamless way to integrate Indy features into Fabric blockchain.

alifatemy (Sun, 01 Mar 2020 03:53:39 GMT):
Hello Mr, Thanks a lot.

nekia (Mon, 02 Mar 2020 04:34:19 GMT):
@rjones Can you override `master` branch with `development-v2.0` branch. We rebased our codebase to fabric v2.0.1. We'd like to do our further development on this branch. https://github.com/hyperledger-labs/fabric-block-archiving

nekia (Mon, 02 Mar 2020 04:36:21 GMT):
And also want to do some tidy up of unused branches.

nekia (Mon, 02 Mar 2020 04:40:46 GMT):
Changing `Default branch` of the repository would be also OK. Thanks

rjones (Mon, 02 Mar 2020 17:42:48 GMT):
@nekia I think I set the permissions correctly so that you can do all of that by yourself - let me know if there is something you can't change

nekia (Mon, 02 Mar 2020 23:37:33 GMT):
Thanks, I could delete unused branches, but couldn't override or delete master branch. And I can't see ``` atsushi@orange:~/go/src/github.com/hyperledger/fabric$ git push -f labs development-v2.0:master Total 0 (delta 0), reused 0 (delta 0) remote: error: GH006: Protected branch update failed for refs/heads/master. remote: error: Required status check "DCO" is expected. At least 1 approving review is required by reviewers with write access. To https://github.com/hyperledger-labs/fabric-block-archiving.git ! [remote rejected] development-v2.0 -> master (protected branch hook declined) error: failed to push some refs to 'https://github.com/hyperledger-labs/fabric-block-archiving.git' atsushi@orange:~/go/src/github.com/hyperledger/fabric$ git push labs :master To https://github.com/hyperledger-labs/fabric-block-archiving.git ! [remote rejected] master (refusing to delete the current branch: refs/heads/master) error: failed to push some refs to 'https://github.com/hyperledger-labs/fabric-block-archiving.git' ```

nekia (Mon, 02 Mar 2020 23:43:55 GMT):
Options in `Settings` tab on the Github repository are also limited so that I can't change default branch, too.

nekia (Mon, 02 Mar 2020 23:44:49 GMT):

Settings - Options on Github repo

rjones (Thu, 05 Mar 2020 18:17:08 GMT):
@nekia are you here in Phoenix?

rjones (Thu, 05 Mar 2020 18:17:31 GMT):
I changed more settings, I think you should be able to sort it out now

nekia (Thu, 05 Mar 2020 21:29:38 GMT):
I wanted to go but I'm not. Thank you for the change. I'll try again. @rjones

nekia (Sat, 07 Mar 2020 12:09:40 GMT):
Thanks, I could do all I want.

shimos (Wed, 11 Mar 2020 21:58:12 GMT):
Hello, I’m a committer for a recently approved project, “Blockchain Verifier”. Can we get a GitHub repo under hyperledger-labs?

rjones (Wed, 11 Mar 2020 22:12:09 GMT):
@shimos please transfer the repo to me on GitHub - `ryjones`

shimos (Wed, 11 Mar 2020 22:18:54 GMT):
Thanks. I have requested transfer of "bcverifier"

rjones (Wed, 11 Mar 2020 22:22:34 GMT):
OK. I think it's set up now

rjones (Wed, 11 Mar 2020 22:22:52 GMT):
https://github.com/hyperledger-labs/blockchain-verifier

shimos (Wed, 11 Mar 2020 22:25:02 GMT):
Thank you!

Dan (Thu, 19 Mar 2020 15:46:41 GMT):
Similar question, I have a lab approved with an existing repo. Shall I just transfer that to `ryjones`or to `hyperledger-labs`?

rjones (Thu, 19 Mar 2020 16:29:19 GMT):
to me.

rjones (Thu, 19 Mar 2020 16:29:36 GMT):
does it need renamed? if so, please rename it before you send it

rjones (Thu, 19 Mar 2020 16:31:58 GMT):
you can transfer it to any org owner, but in practice, that's me.

Dan (Thu, 19 Mar 2020 17:35:21 GMT):
no rename required. it has a dumb name. I have decided that dumb names save me 400 hours of work on average. :D Look for a transfer request shortly. You will know it by the dumbness of the name.

rjones (Thu, 19 Mar 2020 17:36:48 GMT):
OK. @tkuhrt could I ask you to merge https://github.com/hyperledger-labs/hyperledger-labs.github.io/pull/120 ?

rjones (Thu, 19 Mar 2020 17:36:57 GMT):
(or @VipinB if he's around)

rjones (Thu, 19 Mar 2020 17:37:36 GMT):
@Dan I didn't know you were an ANCAP?

tkuhrt (Thu, 19 Mar 2020 17:38:43 GMT):
I cannot merge 120 until we get approvals on it.

tkuhrt (Thu, 19 Mar 2020 17:38:49 GMT):
No Force Merge available

rjones (Thu, 19 Mar 2020 17:39:22 GMT):
it was approved in 116

rjones (Thu, 19 Mar 2020 17:39:45 GMT):
Oh, I see what you mean.

Dan (Thu, 19 Mar 2020 17:39:47 GMT):
I'm all about anarcho-capitalism is the one true way

Dan (Thu, 19 Mar 2020 17:39:47 GMT):
anarcho-capitalism is the one true way

tkuhrt (Thu, 19 Mar 2020 17:39:49 GMT):
I understand...but Github doesn't let me click button. :)

rjones (Thu, 19 Mar 2020 17:39:59 GMT):
Sorry. I'm typing faster than I'm thinking - my usual state

tkuhrt (Thu, 19 Mar 2020 17:40:07 GMT):
No worries

rjones (Thu, 19 Mar 2020 17:40:35 GMT):
typing faster than thinking is how I got here

Dan (Thu, 19 Mar 2020 17:41:02 GMT):
that's the saddest thing about creating a lab... goodbye force merge to master :cry: I'll miss my sloppy development and rebasing.

rjones (Thu, 19 Mar 2020 17:41:07 GMT):
@lehors a thingy? https://github.com/hyperledger-labs/hyperledger-labs.github.io/pull/120

rjones (Thu, 19 Mar 2020 17:41:26 GMT):
@Dan I've been enabling that as I go

Dan (Thu, 19 Mar 2020 17:42:59 GMT):
tempt not the dan with force merge to master

Luxii (Fri, 20 Mar 2020 16:54:37 GMT):
Has left the channel.

seanyoung (Sat, 21 Mar 2020 19:52:58 GMT):
https://github.com/hyperledger-labs/solang has branch protection enabled so I can't remove an obsolete branch: $ git push origin :opt remote: error: GH006: Protected branch update failed for refs/heads/opt. remote: error: Cannot delete this protected branch To github.com:hyperledger-labs/solang.git ! [remote rejected] opt (protected branch hook declined)

seanyoung (Sat, 21 Mar 2020 19:53:28 GMT):
Can branch protection only be enabled for master please?

rjones (Sat, 21 Mar 2020 22:46:23 GMT):
You should have power to delete branches - let me check

rjones (Sat, 21 Mar 2020 22:48:39 GMT):
@seanyoung try now - I enabled the ability to delete protected branches

seanyoung (Sun, 22 Mar 2020 07:26:00 GMT):
@rjones thank you!

asadasad (Thu, 02 Apr 2020 10:34:05 GMT):
Has joined the channel.

sanjay_sharma87 (Sun, 05 Apr 2020 18:10:01 GMT):
Has joined the channel.

rjones (Fri, 10 Apr 2020 17:35:53 GMT):
@dpitt3 the repo exists [for your new lab](https://github.com/hyperledger-labs/keyhole-fabric-api-gateway)

dpitt3 (Fri, 10 Apr 2020 18:31:07 GMT):
thanks #rjones

kumar89 (Thu, 16 Apr 2020 14:55:35 GMT):
Has joined the channel.

smohanlinuxfnd (Fri, 17 Apr 2020 18:55:59 GMT):
Has joined the channel.

rjones (Mon, 20 Apr 2020 20:46:04 GMT):
Hi - [this pluggable consensus lab](https://github.com/hyperledger-labs/hyperledger-labs.github.io/blob/master/labs/pluggable-hcs.md) was approved, but the code was never moved over. Any insights as to what is going on there?

rjones (Tue, 21 Apr 2020 18:46:10 GMT):
@trbs @tkuhrt @lehors @VipinB ^^^

lehors (Tue, 21 Apr 2020 19:36:10 GMT):
@rjones sorry, I don't know

VipinB (Tue, 21 Apr 2020 21:29:56 GMT):
Ask the sponsor !

VipinB (Tue, 21 Apr 2020 21:30:09 GMT):
Chris

peter_somogyvari (Wed, 22 Apr 2020 13:57:00 GMT):
@rjones Sorry to bother! Could you take a look if there's a one-time setup step you could click through as an admin for BAF (blockchain-automation-framework) on CircleCI for the labs? I mean what they describe here: https://circleci.com/docs/2.0/getting-started/#setting-up-circleci Tried to do it myself but it's greyed out and says 'contact repo admin' by which they mean a github org owner according to their docs so I'm hoping that you won't have it greyed out. https://app.circleci.com/projects/project-dashboard/github/hyperledger-labs

rjones (Wed, 22 Apr 2020 14:00:10 GMT):
@peter_somogyvari could I screen share with you?

peter_somogyvari (Wed, 22 Apr 2020 14:05:56 GMT):
Yeah sure

rjones (Wed, 22 Apr 2020 14:06:05 GMT):
https://zoom.us/j/2032622322

rjones (Thu, 14 May 2020 14:11:43 GMT):
@lehors WRT the language lab: would it make more sense for projects like that to be in the main Fabric repo?

lehors (Thu, 14 May 2020 14:20:37 GMT):
I sure think so

lehors (Thu, 14 May 2020 14:21:22 GMT):
from what I remember the chinese went into a lab because of a reluctance from the fabric maintainers to take ownership of something they didn't understand

lehors (Thu, 14 May 2020 14:21:38 GMT):
I always felt it was a bit of a lame position to take

lehors (Thu, 14 May 2020 14:22:02 GMT):
so, I suppose we could ask for this to be revisited

lehors (Thu, 14 May 2020 14:27:14 GMT):
for that matter it would bring a set of new maintainers and increase diversity in the project which would certainly be a good thing

rjones (Thu, 14 May 2020 16:00:28 GMT):
Yes. I'd propose rolling the Malay request in a request for more /docs/ maintainers, and closing the Chinese lab with the same motion

lehors (Mon, 18 May 2020 19:50:04 GMT):
I will file a motion to the Fabric maintainers! :-)

lehors (Mon, 18 May 2020 19:50:04 GMT):
I will file a motion with the Fabric maintainers! :-)

lehors (Mon, 18 May 2020 19:50:04 GMT):
I will "file a motion" with the Fabric maintainers! :-)

Shyam_Pratap_Singh (Mon, 25 May 2020 19:52:46 GMT):
Has joined the channel.

VipinB (Tue, 26 May 2020 15:22:11 GMT):
It is Malayalam (the longest single word palindrome in the OED). My mother tongue @rjones - I see @lehors already did this.

VipinB (Tue, 26 May 2020 15:23:03 GMT):
Meaning filing a motion with the Fabric Maintainers. I cant wait to see what the Malayalam translation of fabric docs are going to look like.

trbs (Tue, 26 May 2020 22:44:17 GMT):
@lehors on https://github.com/hyperledger-labs/hyperledger-labs.github.io/pull/127 I think all review points are met. But will wait for @tkuhrt to approve :-)

trbs (Tue, 26 May 2020 22:46:58 GMT):
If @tkuhrt is busy I can second the PR as well, no need to give @tkuhrt extra work, I just don't want to force approval after you guys did all the review work :-)

lehors (Wed, 27 May 2020 03:36:33 GMT):
Sounds good

johnfranklin (Tue, 23 Jun 2020 10:09:16 GMT):
Has joined the channel.

seanyoung (Wed, 24 Jun 2020 11:52:10 GMT):
@rjones @sbalikondwar is working on a vscode extension for Solidity using Solang. The work has only just started but it is going well. Ideally this would be hosted as a separate repo. How do we got about request a labs repo for this? We were thinking solang-vscode but open to suggestions. WIP is here https://github.com/Hyperion101010/sls/tree/p1_work

sbalikondwar (Wed, 24 Jun 2020 11:52:10 GMT):
Has joined the channel.

rjones (Wed, 24 Jun 2020 13:19:17 GMT):
@seanyoung I think creating sub repos for a lab is fine - @lehors ? I don't think it needs a vote

lehors (Wed, 24 Jun 2020 13:29:28 GMT):
I agree, I don't see why this wouldn't be allowed

rjones (Wed, 24 Jun 2020 13:43:07 GMT):
https://github.com/hyperledger-labs/solang-vscode

rjones (Wed, 24 Jun 2020 13:44:35 GMT):
I also invited `Hyperion101010` to be a maintainer

seanyoung (Wed, 24 Jun 2020 13:53:18 GMT):
Perfect, thank you @rjones

trbs (Wed, 01 Jul 2020 19:36:26 GMT):
@lehors @tkuhrt @VipinB @rjones @stewards do we have a list of all eligible sponsors ? I'm reviewing https://github.com/hyperledger-labs/hyperledger-labs.github.io/pull/132 which LGTM but trying to figure out if RafaelAPB is a valid sponsor... (i.e. a maintainer of one of the Hyperledger projects, a TSC member or a WG chair)

lehors (Wed, 01 Jul 2020 19:48:38 GMT):
sadly we don't and short of being able to automatically generate such a list it would be a real pain to do that by hand

lehors (Wed, 01 Jul 2020 19:49:34 GMT):
this is something we actually talked about on a recent TSC call and it was suggested to put a page where people who qualify could volunteer to have their name on it to help lab submitters find a suitable sponsor

lehors (Wed, 01 Jul 2020 19:49:43 GMT):
unfortunately I don't think there were many takers

lehors (Wed, 01 Jul 2020 19:50:01 GMT):
@rjones would be able to say what the status is on that attempt

trbs (Wed, 01 Jul 2020 20:21:28 GMT):
Thanks, I will try again and see if i missed something on github or the hyperledger site tomorrow to verify if RafaelAPB qualifies as a sponsor..

rjones (Thu, 02 Jul 2020 01:06:43 GMT):
@lehors I made such a list, but I was told to delete it and ask for sponsors.

lehors (Thu, 02 Jul 2020 02:26:17 GMT):
@rjones but did anyone add themselves to the list?

rjones (Thu, 02 Jul 2020 02:27:04 GMT):
https://github.com/hyperledger-labs/sponsors no

lehors (Thu, 02 Jul 2020 02:27:12 GMT):
@trbs rather than going on a goose chase I would suggest you simply ask the submitter how

lehors (Thu, 02 Jul 2020 02:27:12 GMT):
@trbs rather than going on a goose chase I would suggest you simply ask the submitter how RafaelAPB qualifies

lehors (Thu, 02 Jul 2020 02:27:53 GMT):
@rjones ok that's what I thought, thanks

rjones (Thu, 02 Jul 2020 02:28:21 GMT):
@lehors this gets to a prickly issue about labs.

rjones (Thu, 02 Jul 2020 02:29:00 GMT):
actually, it touches on a lot of things.

lehors (Thu, 02 Jul 2020 02:29:10 GMT):
I agree

rjones (Thu, 02 Jul 2020 02:29:47 GMT):
I spent a lot of time trying to hunt down evidence that several of the mentorships marked successful actually were, and I don't think they were.

lehors (Thu, 02 Jul 2020 02:29:54 GMT):
one simple thing we could do is change the template to ask for the sponsor's "qualifications"

rjones (Thu, 02 Jul 2020 02:30:12 GMT):
or make being a mentor one of those roles?

rjones (Thu, 02 Jul 2020 02:30:34 GMT):
we also have TWGC which has split off into a new org, over my objections

lehors (Thu, 02 Jul 2020 02:30:58 GMT):
so instead of saying just "Joe Dalton" they would have to say "Joe Dalton, chair of the Brothers WG"

rjones (Thu, 02 Jul 2020 02:31:12 GMT):
https://github.com/Hyperledger-TWGC

rjones (Thu, 02 Jul 2020 02:31:30 GMT):
¯\_(ツ)_/¯

trbs (Thu, 02 Jul 2020 08:06:32 GMT):
https://github.com/hyperledger-labs/hyperledger-labs.github.io/blob/master/proposal-template.md#sponsor in the proposal template the definition of sponsor and requirement to specify how he/she/it (what is the correct pronoun ?) qualitifies it's already pretty clearly stated imho by asking for the role within hyperledger :-)

trbs (Thu, 02 Jul 2020 08:07:19 GMT):
guess that also answer my own question :grin: since "mentor" is not one of the valid qualifications.... (unless we change it to make it so... but guess that's an agenda topic for TSC meeting ?)

trbs (Thu, 02 Jul 2020 08:09:10 GMT):
I will make a PR to update the pull_request_template.md to be clearer about the sponsor requirements and for the submitter to make sure the sponsor also takes part of the PR so we don't have to case the sponsors every time for confirmation of sponsorship. (Which Rafael nicely did I shall add :-) )

lehors (Thu, 02 Jul 2020 09:22:51 GMT):
@trbs given that the template already calls for the role to be specified, we simply need to enforce its specification in the proposals

lehors (Thu, 02 Jul 2020 09:23:26 GMT):
if a proposal comes in with just a name we should make a request they specify the "sponsor qualifying role"

trbs (Thu, 02 Jul 2020 09:24:32 GMT):
@lehors right

trbs (Thu, 02 Jul 2020 09:24:54 GMT):
The PR is intended to make it a little bit easier and faster for everybody by having the proposers ask the sponsor to confirm their sponsorship after they submit the PR.

trbs (Thu, 02 Jul 2020 09:25:32 GMT):
(but also happy to close it, we if think it's not that helpful :-) )

lehors (Thu, 02 Jul 2020 09:27:43 GMT):
just looked at your PR

lehors (Thu, 02 Jul 2020 09:27:53 GMT):
I think we need to be more direct

lehors (Thu, 02 Jul 2020 09:28:20 GMT):
everytime we give people some leeway they end up tripping on it :)

lehors (Thu, 02 Jul 2020 09:29:34 GMT):
as you update your PR, please, also add something about the need to specify the "role of the sponsor which makes the person qualify as a sponsor"

trbs (Thu, 02 Jul 2020 09:29:48 GMT):
agreed, I was not sure if requiring a github account would be an easy for sponsors since HL mostly uses the linuxfoundation accounts ?

lehors (Thu, 02 Jul 2020 09:29:56 GMT):
there is probably a more elegant way to say that though :)

lehors (Thu, 02 Jul 2020 09:31:06 GMT):
I don't think having a github id is too much to expect from the sponsors

lehors (Thu, 02 Jul 2020 09:31:23 GMT):
I bet all qualifying people have one

trbs (Thu, 02 Jul 2020 09:31:37 GMT):
true :-)

gazelle (Thu, 02 Jul 2020 14:25:55 GMT):
Has joined the channel.

sbalikondwar (Mon, 06 Jul 2020 13:52:33 GMT):
@rjones we requested solang-vscode repo under hyperledger labs and I recieved a invitation for same which got expired cause I waited too long to check it

sbalikondwar (Mon, 06 Jul 2020 13:53:01 GMT):
Can you please re-send it please, my github id: Hyperion101010

sbalikondwar (Mon, 06 Jul 2020 13:53:01 GMT):
Can you please re-send it, my github id: Hyperion101010

sbalikondwar (Mon, 06 Jul 2020 13:55:01 GMT):
The repo https://github.com/hyperledger-labs/solang-vscode

rjones (Mon, 06 Jul 2020 19:43:31 GMT):
@sbalikondwar invite sent

sbalikondwar (Mon, 06 Jul 2020 20:10:19 GMT):
Thanks

ravinayag (Fri, 10 Jul 2020 05:03:46 GMT):
Has joined the channel.

anish-edx (Fri, 10 Jul 2020 05:33:16 GMT):
Has joined the channel.

romeokienzler (Mon, 13 Jul 2020 16:45:58 GMT):
Has joined the channel.

romeokienzler (Mon, 13 Jul 2020 16:45:58 GMT):
Hi, we are thinking of contributing a project to hyperledger-labs, is there a specific license required? or is Apache 2 or GPLv3 fine?

rjones (Mon, 13 Jul 2020 18:24:55 GMT):
Apache 2

romeokienzler (Mon, 13 Jul 2020 19:41:11 GMT):
mni tnx

rjones (Mon, 13 Jul 2020 21:36:43 GMT):
Hi, @tkuhrt @VipinB @lehors @trbs : looks like https://github.com/hyperledger-labs/hyperledger-labs.github.io/pull/132 is stuck in a catch 22. Since this is an mentorship project, I ask again the lab stewards consider allowing mentors as sponsors.

lehors (Mon, 13 Jul 2020 22:10:54 GMT):
hey, I tried to get the list of potential sponsors expanded...

lehors (Mon, 13 Jul 2020 22:11:06 GMT):
that's ok, I can have my name on it

domwoe (Fri, 17 Jul 2020 09:01:13 GMT):
Has joined the channel.

gaudelbiond (Sat, 18 Jul 2020 10:54:19 GMT):
Has joined the channel.

rjones (Mon, 03 Aug 2020 13:13:03 GMT):
Hi, for several reasons, I moved Labs under Hyperledger in stats. This makes getting stats for the overall project easier. https://lfanalytics.io/projects/hyperledger%2Fhyperledger-labs/dashboard

frank-bee (Tue, 18 Aug 2020 05:16:56 GMT):
Has joined the channel.

jcldnatv (Sat, 22 Aug 2020 17:22:06 GMT):
Has joined the channel.

choeppler (Mon, 31 Aug 2020 09:31:16 GMT):
Has joined the channel.

MicBowman (Thu, 03 Sep 2020 16:40:30 GMT):
question... we are starting a project to build a fairly substantial application for the fabric private chaincode lab (which will also use code from the private data objects lab), we want this to be very closely related to FPC but the group of committers would be different from the FPC core committers... would this be better handled as a branch of FPC or as a new HL Labs project?

rjones (Thu, 03 Sep 2020 16:41:00 GMT):
other projects seem to have multiple repos

MicBowman (Thu, 03 Sep 2020 16:41:25 GMT):
could we then request a second repo for FPC that we could use for that code?

rjones (Thu, 03 Sep 2020 16:41:44 GMT):
what do you want it named?

rjones (Thu, 03 Sep 2020 16:42:06 GMT):
is it a copy of the existing repo? who are the initial maintainers?

MicBowman (Thu, 03 Sep 2020 16:43:15 GMT):
fabric_private_chaincode_wasm and we can start with an empty repo, we'll just use git modules to connect to FPC

MicBowman (Thu, 03 Sep 2020 16:43:46 GMT):
for now... if you can copy the maintainers list from FPC and i'll get you the changes

MicBowman (Thu, 03 Sep 2020 16:44:04 GMT):
oh... and please use "-" instead of "_"... apparently i'm old school

MicBowman (Thu, 03 Sep 2020 16:44:05 GMT):
;-)

MicBowman (Thu, 03 Sep 2020 16:44:27 GMT):
right @bur ?

bur (Thu, 03 Sep 2020 16:44:40 GMT):
old? :thumbsup:

rjones (Thu, 03 Sep 2020 16:51:19 GMT):
https://github.com/hyperledger-labs/fabric-private-chaincode-wasm all yours

MicBowman (Thu, 03 Sep 2020 16:51:45 GMT):
thanks, @rjones

seanyoung (Thu, 03 Sep 2020 16:55:30 GMT):
@MicBowman just out of interest,what's the plan with with fpc-wasm? I'm asking, since Solang now supports almost all of Solidity (a few remaining items happening this month), is this something Solang can target?

MicBowman (Thu, 03 Sep 2020 16:59:30 GMT):
we should definitely talk! we've added support for WASM contracts in the private data objects project (meaning that we can build and execute contracts inside an SGX enclave using WASM), this new repository will be a port of the interpreter to FPC, initially it will run as a chaincode application with an expectation that we'll make the integration with FPC more "natural" if appropriate at a future time

MicBowman (Thu, 03 Sep 2020 16:59:55 GMT):
so... in theory, if we can support any native extensions you have, we should be able to run "now" in PDO and shortly in FPC

seanyoung (Fri, 04 Sep 2020 08:56:28 GMT):
So I'm very busy finishing language support in Solang, I don't have much time right now. But once that is done let's talk

MicBowman (Fri, 04 Sep 2020 16:11:22 GMT):
sounds good!

sbalikondwar (Mon, 07 Sep 2020 10:53:56 GMT):
i would like to know more about it!

sheru (Tue, 08 Sep 2020 08:11:53 GMT):
Has joined the channel.

choeppler (Wed, 09 Sep 2020 13:45:17 GMT):
@tkuhrt, now that the perun repos are up and running, we'd like to transition to more of an open mode of working. Two questions regarding infrastructure: (1) Would it be possible to setup a #perun channel in the Hyperledger Chat server so we can move development related conversations currently occurring on a closed system to a publicly accessible one? (2) Can we setup a GitHub project in the Hyperledger Labs Org that is connected with perun-node, perun-doc, and perun-proposals repos (like in the old org here: https://github.com/orgs/direct-state-transfer/projects/1) to help with planning and getting an overview on current development activity? Or is there some other system you typically use for Hyperledger projects?

tkuhrt (Wed, 09 Sep 2020 13:48:35 GMT):
@rjones : It looks like I can no longer create chat channels here. Can you help? Also, do we support projects in Github?

rjones (Wed, 09 Sep 2020 14:12:59 GMT):
@tkuhrt projects are A-OK.

rjones (Wed, 09 Sep 2020 14:16:24 GMT):
https://github.com/orgs/hyperledger-labs/projects/1

choeppler (Wed, 09 Sep 2020 14:21:20 GMT):
Wow, that was quick. Thank you, @rjones

rjones (Wed, 09 Sep 2020 14:22:35 GMT):
sure thing. I created #labs-perun and made you. an owner.

rjones (Wed, 09 Sep 2020 14:22:35 GMT):
sure thing. I created #labs-perun and made you an owner.

rjones (Wed, 09 Sep 2020 14:23:04 GMT):
the labs prefix makes it show up in the right places

choeppler (Wed, 09 Sep 2020 14:23:23 GMT):
Ah, okay. Great!

rjones (Wed, 09 Sep 2020 14:24:02 GMT):
however, I see that the labs prefix isn't consistently used. If you want it removed, I will do that.

choeppler (Wed, 09 Sep 2020 14:26:59 GMT):
In that case, I think perun would be nicer... :-)

rjones (Wed, 09 Sep 2020 15:13:30 GMT):
done!

tkuhrt (Wed, 09 Sep 2020 15:57:57 GMT):
Thanks, Ry

choeppler (Wed, 09 Sep 2020 16:24:11 GMT):
Perfect. Thanks!

choeppler (Thu, 10 Sep 2020 09:25:06 GMT):
:thumbsup: nice stats. I just browsed a bit around the dashboard. Is the mapping from committer's github account to Name and Organization done automatically? I've noticed some commits show up under the github account name, most under real name, same for organization (sometimes actual org, sometimes "Unknown")...

danielksan81 (Thu, 10 Sep 2020 10:11:20 GMT):
Has joined the channel.

seanyoung (Thu, 10 Sep 2020 11:01:21 GMT):
@MicBowman shall we have a call to talk about using Solang for FPC. I have a few minor ideas/concerns I'd like to discuss. @sbalikondwar would also like to attend.

seanyoung (Thu, 10 Sep 2020 11:01:54 GMT):
I've just finished Solidity function modifiers, the last of the major missing language features

MicBowman (Thu, 10 Sep 2020 14:08:27 GMT):
absolutely.

rjones (Thu, 10 Sep 2020 14:53:51 GMT):
A lot of it is manual, by which I mean, I do the typing :)

choeppler (Fri, 11 Sep 2020 08:58:47 GMT):
I see. :-) Would it be helpful if I sent you some of the missing mappings I've come across (mainly regarding colleagues from my org) or do you have that on the stack to by typed in, anyway... ;-)

choeppler (Fri, 11 Sep 2020 09:43:06 GMT):
My colleagues working on the business-partner-agent labs project, have asked me for a chat channel for their project. Could you please create a #business-partner-agent channel for that project, @rjones ?

rjones (Fri, 11 Sep 2020 13:21:18 GMT):
yes, please. My email is rjones@linuxfoundation.org

choeppler (Wed, 16 Sep 2020 11:08:12 GMT):
What's the preferred way to add an additional collaborator to a labs project on GitHub? Post name and required permission level here in the chat or open a ticket in the project and assign that to the labs steward who set up the project, or something else...?

rjones (Wed, 16 Sep 2020 16:55:16 GMT):
Update the wiki page and @ me

rjones (Wed, 16 Sep 2020 16:56:50 GMT):
please send email to community-architects@hyperledger.org

ynamiki (Wed, 23 Sep 2020 02:43:16 GMT):
Has left the channel.

knagware9 (Mon, 28 Sep 2020 10:48:36 GMT):
Hello community from the Hyperledger India Chapter, we are calling for speakers to engage with the community in Asia Pacific, Europe and Africa. Please see our event details here https://www.linkedin.com/feed/update/urn:li:activity:6715897303481372672 Calling the tech enthusiasts, maintainers to be part of it.

manoranjith (Thu, 01 Oct 2020 19:42:33 GMT):
Has joined the channel.

dgt1nsty (Fri, 02 Oct 2020 13:53:19 GMT):
Has joined the channel.

rjones (Fri, 02 Oct 2020 16:48:26 GMT):
@tkuhrt @VipinB @trbs @lehors could I ask for your review? https://github.com/hyperledger-labs/hyperledger-labs.github.io/pull/147

lehors (Fri, 02 Oct 2020 16:52:31 GMT):
Will do

rjones (Fri, 02 Oct 2020 16:53:10 GMT):
thanks.

VipinB (Fri, 02 Oct 2020 21:24:08 GMT):
@rjones @lehors @tkuhrt @trbs I have raised a query about the wisdom of archiving after 6 months of non-activity

lehors (Fri, 02 Oct 2020 21:51:16 GMT):
Have these labs achieved anything or were they just proposals that never really took off?

rjones (Fri, 02 Oct 2020 22:00:59 GMT):
@VipinB you're worried that people who started a lab, and let it lie fallow for six months, might not get picked up for the election because they've made no other contributions anywhere?

rjones (Fri, 02 Oct 2020 22:02:01 GMT):
regardless, archiving labs still keeps GitHub's magic redirects in place; also, these labs either have or have not contributed unique voters for the ongoing election, but that franchise won't be revoked.

rjones (Fri, 02 Oct 2020 22:02:29 GMT):
I think a larger issue is this weeding of fallow labs is a task that's on the lab stewards, but I'm the person doing it.

rjones (Fri, 02 Oct 2020 22:03:38 GMT):
When I asked that the lab activity reports come from the labs, I got pushback. I was reminded today that I haven't done one for 2020, which is why I looked into this at all.

VipinB (Sat, 03 Oct 2020 14:50:53 GMT):
@rjones it is not up to us to decide whether a one year contribution counts; it is in the charter. Does your statement mean that the redirects will allow for these labs to be picked back up when looking at electors? What exactly does this "weeding" achieve? I am curious. As far I know this was put into place by you. As far as the job of weeding falling to lab stewards, I have no problem with that, but all stewards need to agree.

VipinB (Sat, 03 Oct 2020 14:53:24 GMT):
Last time there was a "weeding", some parties asked for re-instatement

rjones (Mon, 05 Oct 2020 04:25:28 GMT):
@VipinB the weeding is literally a part of the description of what lab stewards are supposed to do. ```Archiving Stewards are responsible for curating the set of labs, moving to an archives space (see below) those that become dormant or unresponsive for an extended period (6+ months), or are explicitly deemed by the committers to be deprecated/obsoleted. Deprecated, obsoleted, or dormant labs (as defined above) will be moved to a GitHub org “hyperledger-labs-archives” that signifies that the lab is no longer maintained. Labs in the archives are read-only, and they can be moved back out of the archives, if there is interest in reviving them.```

rjones (Mon, 05 Oct 2020 04:25:28 GMT):
@VipinB the weeding is literally a part of the [description of what lab stewards are supposed to do](https://wiki.hyperledger.org/display/labs). ```Archiving Stewards are responsible for curating the set of labs, moving to an archives space (see below) those that become dormant or unresponsive for an extended period (6+ months), or are explicitly deemed by the committers to be deprecated/obsoleted. Deprecated, obsoleted, or dormant labs (as defined above) will be moved to a GitHub org “hyperledger-labs-archives” that signifies that the lab is no longer maintained. Labs in the archives are read-only, and they can be moved back out of the archives, if there is interest in reviving them.```

VipinB (Mon, 05 Oct 2020 11:05:45 GMT):
we wrote that a couple of years ago but the period can be changed in light of its effects on electors, this weeding idea was not in the initial conception. I agree that labs stewards should do it periodically. @rjones

rjones (Mon, 05 Oct 2020 14:42:18 GMT):
I'm fine with the lab stewards changing how labs are run. I defer to @tkuhrt , who was in Portugal, for history

tkuhrt (Mon, 05 Oct 2020 16:25:24 GMT):
Hi, @VipinB. The [original proposal](https://docs.google.com/document/d/1VbgmlIqDnUnvjxSJ5QTUBV-Qn3eA7Gduw0edjYgDXIY/edit#heading=h.9q0zl1wh5w2v) did include the archive clause. Basically, we wanted to make sure that labs were being actively maintained.

tkuhrt (Mon, 05 Oct 2020 16:25:24 GMT):
Hi, @VipinB -- The [original proposal](https://docs.google.com/document/d/1VbgmlIqDnUnvjxSJ5QTUBV-Qn3eA7Gduw0edjYgDXIY/edit#heading=h.9q0zl1wh5w2v) did include the archive clause. Basically, we wanted to make sure that labs were being actively maintained.

tkuhrt (Mon, 05 Oct 2020 16:26:35 GMT):
We may need a better process in ensuring that the lab proposers know that we are considering archiving the labs. Possible process could be: 1. Separate PR for each lab archival

VipinB (Wed, 07 Oct 2020 11:20:38 GMT):
@tkuhrt my main concern is the disconnect between the tsc charter which says contributors are valid electors if they contributed in the last year and the lab archive policy which covers 6 months. In my opinion this should be a yearly activity with the labs getting archived right after the electors are chosen, once a year. In that sense it makes sense to extend to 1 year of inactivity.

rjones (Wed, 07 Oct 2020 14:09:41 GMT):
You ignore that the archives are part of the gathering process, as I said above.

VipinB (Wed, 07 Oct 2020 14:17:35 GMT):
@rjones thanks for clarifying that

rjones (Wed, 07 Oct 2020 14:59:22 GMT):
@VipinB @trbs @tkuhrt for your consideration: https://github.com/hyperledger-labs/hyperledger-labs.github.io/pull/148 (it has one vote, already, from @lehors )

VipinB (Wed, 07 Oct 2020 15:06:31 GMT):
Approved and Merged

rjones (Fri, 09 Oct 2020 04:49:44 GMT):
More labs to archive: https://github.com/hyperledger-labs/hyperledger-labs.github.io/pull/149

rjones (Fri, 09 Oct 2020 14:57:42 GMT):
I reworked the website a little to show the labs on the front page: https://github.com/hyperledger-labs/hyperledger-labs.github.io/pull/150 see the rendered version here: https://ryjones.github.io/hyperledger-labs.github.io/

rjones (Fri, 09 Oct 2020 14:58:13 GMT):
There will be a follow-up PR to correct some wording.

rjones (Fri, 09 Oct 2020 16:21:10 GMT):
Hey, check this out: https://labs.hyperledger.org/

rjones (Wed, 21 Oct 2020 18:30:26 GMT):
@VipinB @tkuhrt @lehors @trbs I've been talking to the maintainer of Nephos, he wants to archive it. I seek your approval: https://github.com/hyperledger-labs/hyperledger-labs.github.io/pull/151

Darren-Matthews (Thu, 22 Oct 2020 00:07:30 GMT):
Has joined the channel.

Melwin_Sunny (Fri, 13 Nov 2020 06:10:21 GMT):
Has joined the channel.

rjones (Fri, 13 Nov 2020 18:03:23 GMT):
@VipinB @tkuhrt @lehors @trbs for your approval: https://github.com/hyperledger-labs/hyperledger-labs.github.io/pull/156

seanyoung (Mon, 16 Nov 2020 10:09:24 GMT):
@rjones please can you add @sbalikondwar as a maintainer of the solang labs repo. @sbalikondwar wrote a language server and vscode extension in solang-vscode repo, which we are now merging into solang repo https://github.com/hyperledger-labs/solang/pull/318

rjones (Mon, 16 Nov 2020 15:18:10 GMT):
@seanyoung invite extended!

seanyoung (Mon, 16 Nov 2020 15:21:59 GMT):
@rjones thank you

VipinB (Mon, 16 Nov 2020 20:11:02 GMT):
Done and dusted! @lehors thanks!

sbalikondwar (Tue, 17 Nov 2020 14:52:37 GMT):
@rjones I recently changed by email on GitHub. So when you sent the request it was sent to that email which is currently unusable. Can you resend the invite?

sbalikondwar (Tue, 17 Nov 2020 14:53:01 GMT):
I have changed my GitHub email

rjones (Tue, 17 Nov 2020 15:06:00 GMT):
I think if you visit https://github.com/hyperledger-labs when logged in you should see the invite at the top of the page

BrunoVavala (Wed, 02 Dec 2020 00:29:35 GMT):
Github/Travis has transitioned to a credit-based (or plan-based) CI service, and apparently Hyperledger Labs just ran out of credits. From Travis website (this should be related to the HL Labs organization): "Builds have been temporarily disabled for private and public repositories due to a negative credit balance. Please go to the Plan page to replenish your credit balance." Is there any intention to support Travis CI for HL Labs?

rjones (Wed, 02 Dec 2020 01:13:38 GMT):
@BrunoVavala no, there is not. Labs are running on the 10,000 credit OSS plan, which is gratis.

rjones (Wed, 02 Dec 2020 01:16:51 GMT):
It looks like Blockchain Automation Framework burned all 10,000 credits in under a day - impressive.

rjones (Wed, 02 Dec 2020 01:18:45 GMT):
@BrunoVavala I suggest switching to Azure Pipelines or GitHub Actions for CI.

BrunoVavala (Wed, 02 Dec 2020 01:22:40 GMT):
@rjones thanks for the suggestions!

vikramsharmacodes (Thu, 03 Dec 2020 10:33:41 GMT):
Has joined the channel.

seanyoung (Fri, 11 Dec 2020 11:34:33 GMT):
@rjones @sbalikondwar the work done during the mentorship here https://github.com/hyperledger-labs/solang-vscode/ has been merged into https://github.com/hyperledger-labs/solang . See https://solang.readthedocs.io/en/latest/extension.html What should we do with the old repo?

rjones (Fri, 11 Dec 2020 16:14:14 GMT):
@seanyoung I can archive it and transfer it to `hyperledger-labs-archives` if you like

seanyoung (Fri, 11 Dec 2020 16:16:07 GMT):
I think that makes sense. Will any links to it automatically redirect?

rjones (Fri, 11 Dec 2020 16:24:03 GMT):
yes, it's magic

rjones (Fri, 11 Dec 2020 16:24:48 GMT):
@seanyoung edit this file: `https://github.com/hyperledger-labs/solang-vscode/blob/master/.github/settings.yml` change line 14 to `true`

rjones (Fri, 11 Dec 2020 16:25:06 GMT):
after that, I'll move it over.

rjones (Fri, 11 Dec 2020 16:27:21 GMT):
https://github.com/hyperledger-labs/solang-vscode/pull/11

seanyoung (Fri, 11 Dec 2020 17:06:51 GMT):
merged

rjones (Fri, 11 Dec 2020 17:08:38 GMT):
https://github.com/hyperledger-labs-archives/solang-vscode transferred.

seanyoung (Fri, 11 Dec 2020 17:09:22 GMT):
@rjones Thank you!

rjones (Fri, 11 Dec 2020 17:10:11 GMT):
GitHub does magic redirects. If you visit https://github.com/hyperledger-labs/solang-vscode , it will land you in the right place. Git remotes also work

seanyoung (Fri, 11 Dec 2020 17:11:31 GMT):
perfect

seanyoung (Fri, 11 Dec 2020 17:15:05 GMT):
@rjones is possible to enable funding and discussions on the solang repo? I don't have those options in the repo settings. Thanks

rjones (Fri, 11 Dec 2020 17:22:05 GMT):
I've enabled discussions, but for funding, I need to check internally (LF)

seanyoung (Fri, 11 Dec 2020 18:11:21 GMT):
@rjones thanks for enabling discussions! For the funding, I think this would be very helpful. It would be useful for users to know that the project can use funding (not an immediate problem)

pritam_01 (Fri, 25 Dec 2020 03:58:19 GMT):
Has joined the channel.

bh4rtp (Sun, 10 Jan 2021 16:15:38 GMT):
Has joined the channel.

tatsu-sato (Thu, 21 Jan 2021 19:01:28 GMT):
Has joined the channel.

seanyoung (Sun, 24 Jan 2021 15:21:15 GMT):
@rjones is it possible to rename the master branch to main in my labs repo? I don't have access to this, I think.

rjones (Sun, 24 Jan 2021 16:03:30 GMT):
@seanyoung which repos?

rjones (Sun, 24 Jan 2021 16:03:30 GMT):
@seanyoung I renamed `solang`

rjones (Sun, 24 Jan 2021 18:15:34 GMT):
Hi, lab stewards. The following repos use `master` as a default branch instead of `main`. ``` "full_name": "hyperledger-labs/TrustID", "full_name": "hyperledger-labs/blockchain-automation-framework", "full_name": "hyperledger-labs/blockchain-verifier", "full_name": "hyperledger-labs/business-partner-agent", "full_name": "hyperledger-labs/byzantine-config", "full_name": "hyperledger-labs/dancap", "full_name": "hyperledger-labs/eThaler", "full_name": "hyperledger-labs/fabex", "full_name": "hyperledger-labs/fabric-block-archiving", "full_name": "hyperledger-labs/fabric-chaincode-haskell", "full_name": "hyperledger-labs/fabric-private-chaincode", "full_name": "hyperledger-labs/hyperledger-fabric-based-access-control", "full_name": "hyperledger-labs/keyhole-fabric-api-gateway", "full_name": "hyperledger-labs/minbft", "full_name": "hyperledger-labs/modern-pharmacy-management", "full_name": "hyperledger-labs/perun-doc", "full_name": "hyperledger-labs/perun-eth-contracts", "full_name": "hyperledger-labs/perun-proposals", "full_name": "hyperledger-labs/private-data-objects", "full_name": "hyperledger-labs/private-transaction-families", "full_name": "hyperledger-labs/umbra", "full_name": "hyperledger-labs/university-course", "full_name": "hyperledger-labs/voters", "full_name": "hyperledger-labs/xcsi", ```

VipinB (Sun, 24 Jan 2021 18:41:48 GMT):
Steps for this seem to be: # Step 1 # create main branch locally, taking the history from master git branch -m master main # Step 2 # push the new local main branch to the remote repo (GitHub) git push -u origin main # Step 3 # switch the current HEAD to the main branch git symbolic-ref refs/remotes/origin/HEAD refs/remotes/origin/main # Step 4 # change the default branch on GitHub to main # https://docs.github.com/en/github/administering-a-repository/setting-the-default-branch # Step 5 # delete the master branch on the remote git push origin --delete master

VipinB (Sun, 24 Jan 2021 18:42:20 GMT):
I will start the process for eThaler and xcsi

rjones (Sun, 24 Jan 2021 20:20:17 GMT):
I think you can just do it in the UI

rjones (Sun, 24 Jan 2021 20:20:24 GMT):
rename the branch and it Just Works

rjones (Sun, 24 Jan 2021 20:21:23 GMT):
@VipinB I think you can go here: https://github.com/hyperledger-labs/eThaler/settings/branches and just set the branch name.

rjones (Sun, 24 Jan 2021 20:22:10 GMT):
Same thing here: https://github.com/hyperledger-labs/xcsi/settings/branches

rjones (Sun, 24 Jan 2021 20:22:51 GMT):
You should have the permissions to delete these other two branches, if you like. https://github.com/hyperledger-labs/xcsi/branches

VipinB (Sun, 24 Jan 2021 20:26:28 GMT):
I deleted the branches

VipinB (Sun, 24 Jan 2021 20:26:56 GMT):
Rename the master branch to main?

rjones (Sun, 24 Jan 2021 20:28:09 GMT):
yes, you can click the pencil by master and type in main

rjones (Sun, 24 Jan 2021 20:28:26 GMT):

Screen Shot 2021-01-24 at 12.28.19 PM.png

rjones (Sun, 24 Jan 2021 20:28:31 GMT):
way on the right

VipinB (Sun, 24 Jan 2021 20:33:41 GMT):
Maybe you have a different view

VipinB (Sun, 24 Jan 2021 20:33:50 GMT):
Since you are admin

rjones (Sun, 24 Jan 2021 20:35:14 GMT):
dang. Do you want `main` for the new name?

VipinB (Sun, 24 Jan 2021 20:38:08 GMT):
Yes

VipinB (Sun, 24 Jan 2021 20:38:22 GMT):
I am able to do this for my own repos

VipinB (Sun, 24 Jan 2021 20:38:32 GMT):
(under vipinsun)

VipinB (Sun, 24 Jan 2021 20:40:03 GMT):
Same thing for eThaler

rjones (Sun, 24 Jan 2021 20:49:18 GMT):
Done and done. I'm not sure why that wasn't available for you - sorry for the mental density on my part.

VipinB (Mon, 25 Jan 2021 15:13:24 GMT):
Thanks

vmanolas (Sun, 31 Jan 2021 15:00:48 GMT):
Has joined the channel.

rjones (Wed, 03 Feb 2021 15:13:39 GMT):
Hi @VipinB @tkuhrt @lehors @trbs we have a request to un-archive cordentity: https://github.com/hyperledger-labs/hyperledger-labs.github.io/pull/159

VipinB (Wed, 03 Feb 2021 15:53:17 GMT):
Approved PR @rjones

rjones (Wed, 03 Feb 2021 16:19:58 GMT):
Thanks; I had to replace it with #160 for some reason.

rjones (Wed, 03 Feb 2021 16:19:58 GMT):
Thanks; I had to replace it with [160](https://github.com/hyperledger-labs/hyperledger-labs.github.io/pull/160) for some reason.

rjones (Wed, 03 Feb 2021 23:20:30 GMT):
OK; ScoreX code is over, Cordentity is un-archived.

rjones (Thu, 04 Feb 2021 14:29:31 GMT):
@VipinB @tkuhrt @lehors @trbs thoughts on [fabric-private-chaincode-wasm](https://github.com/hyperledger-labs/fabric-private-chaincode-wasm)? Repo created, nothing has happened since.

tkuhrt (Thu, 04 Feb 2021 14:33:13 GMT):
Should we reach out to the team on Github to see what the status is?

lehors (Thu, 04 Feb 2021 14:33:41 GMT):
yes, that seems like a good step to take

lehors (Thu, 04 Feb 2021 14:45:21 GMT):
@tkuhrt I DM'ed you but I'm guessing your RC client is failing to let you know...

sbalikondwar (Sat, 06 Feb 2021 13:56:29 GMT):
@rjones does linux(hyperledger) apply for gsoc?

sbalikondwar (Sat, 06 Feb 2021 13:56:58 GMT):
we had some ideas to list for contributes if we do have such opportunity

sbalikondwar (Sat, 06 Feb 2021 13:56:58 GMT):
we had some ideas to list for contributers if we do have such opportunity

sbalikondwar (Sat, 06 Feb 2021 13:56:58 GMT):
we had some ideas to list for contributers incase if we do have such opportunity

seanyoung (Sat, 06 Feb 2021 14:13:30 GMT):
@sbalikondwar gsoc is the google program. Hyperledger runs its own mentorship program.

seanyoung (Sat, 06 Feb 2021 14:14:37 GMT):
https://wiki.hyperledger.org/display/INTERN/Mentorship+Projects

seanyoung (Sat, 06 Feb 2021 14:15:00 GMT):
I will be apply for solang, in case you're interested. I haven't decided what I will be apply for.

seanyoung (Sat, 06 Feb 2021 14:15:00 GMT):
I will be apply for solang, in case you're interested. I haven't decided what I will be applying for.

VipinB (Fri, 12 Feb 2021 12:50:36 GMT):
https://wiki.hyperledger.org/display/LMDWG/Lab+Sponsors+Proposal @lehors @tkuhrt @trbs I have made an initial stab at the Labs Sponsors Proposal where I argue for getting rid of the sponsor requirement. Thanks to @Bobbijn.

tkuhrt (Fri, 12 Feb 2021 14:45:06 GMT):
Couple of points regarding licenses: 1. CC-By-4.0 is an acceptable Hyperledger license for documentation. 2. All new lab repos (non-transferred labs) are created with an Apache 2.0 license file. Both Ry and myself do this when creating labs. 3. I have caught labs that are being transferred having the incorrect license in the past. It seems that I missed the most recent MIT one. I am assuming the ones that do not have LICENSE file are also transferred labs due to #2 above.

tkuhrt (Fri, 12 Feb 2021 14:46:08 GMT):
Regarding the wiki page, I am not sure I see where the proposal is to remove the lab sponsor. Just some text around what the sponsor does today. Is this page intended to provide a concise recommendation? Or is it to discuss the role/need for a lab sponsor?

tkuhrt (Fri, 12 Feb 2021 14:46:33 GMT):
Sorry...I am sure that this was discussed in yesterday's call, but I have not had a chance to listen to the recording yet.

VipinB (Fri, 12 Feb 2021 15:49:24 GMT):
Before we propose removing the sponsor we look at the reality of today. I propose a specific recommendation for removal. However, I want to see what the other stewards think about this. This is meant to be a location where we can collaborate on our joint text. @lehors proposed removing sponsors- We need @trbs or you @tkuhrt to concur or demur. However, we want to address @bbehlendorf 's concern about harms that Sponsor's protect against.

VipinB (Fri, 12 Feb 2021 15:50:34 GMT):
In that context, my main argument is that Sponsor's as they function today DO NOT protect against any of those harms...

VipinB (Fri, 12 Feb 2021 15:50:34 GMT):
In that context, my main argument is that Sponsors as they function today DO NOT protect against any of those harms... If you make their duties more onerous you run the risk of putting gating functions and discourage participation. We have to create more automation to handle governance issues. That with intervention by stewards will keep the labs program running smoothly AND address governance concerns. These are my thoughts

rjones (Fri, 12 Feb 2021 15:50:37 GMT):
as a part of this, I looked over the lab repos, and there are quite a few that need archived or were never used so could be deleted.

VipinB (Fri, 12 Feb 2021 15:51:49 GMT):
That is a different point @rjones

VipinB (Fri, 12 Feb 2021 15:51:49 GMT):
That is a different but very important point @rjones

VipinB (Fri, 12 Feb 2021 15:58:26 GMT):
The sponsor proposal could spinoff into an endless argument with no closure.

VipinB (Fri, 12 Feb 2021 15:58:26 GMT):
The sponsor proposal could spinoff into another endless argument with no closure. With many people opining who have no skin in the game.

VipinB (Fri, 12 Feb 2021 15:58:26 GMT):
The sponsor proposal could spinoff into another endless argument with no closure. With many people opining who have no skin in the game as obliquely noted by @lehors

VipinB (Fri, 12 Feb 2021 16:36:25 GMT):
I have moved this proposal under Hyperledger Labs home https://wiki.hyperledger.org/display/labs/Sponsors+For+Labs-Proposal

rjones (Fri, 12 Feb 2021 19:02:17 GMT):
Stewards: I propose you take a look at the following labs for archiving. The date is the last commit on the default branch. ```private-transaction-families: Fri Jul 19 00:33:53 2019 +0300 keyhole-fabric-api-gateway: Thu Apr 9 07:59:46 2020 -0500 fabric-block-archiving: Wed May 6 19:11:02 2020 +1000 modern-pharmacy-management: Fri Jun 19 21:53:17 2020 +0300 pluggable-hcs: Thu Jul 30 17:34:08 2020 -0700 fabric-chaincode-wasm: Fri Jul 24 11:39:32 2020 +0800 besu-operator: Fri Aug 7 16:20:59 2020 +0530 ```

VipinB (Sun, 14 Feb 2021 16:56:19 GMT):
There should be no problem archiving these according to me, especially if unarchiving is relatively painless. @rjones

VipinB (Sun, 14 Feb 2021 17:10:16 GMT):
ALso made some more edits to streamline https://wiki.hyperledger.org/display/labs/Sponsors+For+Labs-Proposal

VipinB (Sun, 14 Feb 2021 17:10:16 GMT):
Made some more edits to streamline https://wiki.hyperledger.org/display/labs/Sponsors+For+Labs-Proposal

lehors (Mon, 15 Feb 2021 06:33:09 GMT):
+1

lehors (Mon, 15 Feb 2021 06:33:42 GMT):
I think this how labs should be managed: easy come easy go

lehors (Mon, 15 Feb 2021 06:33:42 GMT):
I think this is how labs should be managed: easy come easy go

rjones (Mon, 15 Feb 2021 14:41:44 GMT):
OK so... that's a thing for stewards, of which I am not one, to do. :)

lehors (Wed, 24 Feb 2021 17:28:20 GMT):
@rjones, given your involvement I think you're entitled and encouraged to speak up and share your thoughts on that issue...

seanyoung (Wed, 03 Mar 2021 14:05:15 GMT):
@rjones is it possible to push docker images to hyperledgerlabs/solang from github actions, or is this a little awkward with permissions? The docker hub builds are super slow, and github actions is already building a docker image, might as well push it from there.

rjones (Wed, 03 Mar 2021 14:19:05 GMT):
@seanyoung it is possible - take a look [at how this is published](https://github.com/hyperledger/aries-framework-go/blob/main/.github/workflows/build.yml). I'll add the secrets, `CR_*`, where needed

rjones (Wed, 03 Mar 2021 14:20:31 GMT):
ah wait, that's for publishing to GitHub packages. If that is an option for you, it is much easier

rjones (Wed, 03 Mar 2021 14:29:04 GMT):
@seanyoung use tokens: `DH_USER` and `DH_KEY` to publish.

seanyoung (Wed, 03 Mar 2021 15:00:01 GMT):
@rjones, perfect thank you! I'm also publishing to github packages

seanyoung (Thu, 04 Mar 2021 16:00:57 GMT):
Thanks, this works now.

christophe.charles (Tue, 09 Mar 2021 15:43:29 GMT):
Has joined the channel.

christophe.charles (Tue, 09 Mar 2021 15:43:30 GMT):
Hi :)

vramaiitkgp (Wed, 31 Mar 2021 11:35:32 GMT):
Has joined the channel.

vramaiitkgp (Wed, 31 Mar 2021 11:35:32 GMT):
@rjones @tkuhrt For my recently created Labs project (Weaver), I have documentation built on docusaurus that can publish to Github pages but needs the ability to create and edit a `gh-pages` branch in the main repository. Currently, I've just published from my fork, but I'd much prefer to be able to publish to `hyperledger-labs.github.io`. How can I go about doing that? More generally, what's the recommended way of publishing project docs? (Are there any ready instructions somewhere?)

rjones (Wed, 31 Mar 2021 14:26:52 GMT):
@vramaiitkgp once you publish to the new `gh-pages` branch it should be reflected on https://labs.hyperledger.org/weaver-dlt-interoperability/

vramaiitkgp (Thu, 01 Apr 2021 10:13:29 GMT):
@rjones I tried building and publishing to `gh-pages` but got the following (permission) error: ``` > weaver-dlt-interoperability@0.0.0 deploy-gh-pages /home/vagrant/go/src/github.com/hyperledger-labs/weaver-dlt-interoperability/documentation > gh-pages -d build remote: error: GH006: Protected branch update failed for refs/heads/gh-pages. remote: error: Required status check "DCO" is expected. At least 2 approving reviews are required by reviewers with write access. To https://github.com/hyperledger-labs/weaver-dlt-interoperability.git ! [remote rejected] gh-pages -> gh-pages (protected branch hook declined) error: failed to push some refs to 'https://github.com/hyperledger-labs/weaver-dlt-interoperability.git' npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! weaver-dlt-interoperability@0.0.0 deploy-gh-pages: `gh-pages -d build` npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the weaver-dlt-interoperability@0.0.0 deploy-gh-pages script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above. npm ERR! A complete log of this run can be found in: npm ERR! /home/vagrant/.npm/_logs/2021-04-01T10_08_54_128Z-debug.log ``` How do I get past this? FYI, I'm trying to publish documentation rooted in https://github.com/hyperledger-labs/weaver-dlt-interoperability/tree/main/documentation.

vramaiitkgp (Thu, 01 Apr 2021 10:22:14 GMT):
Does the documentation have to be in `/docs`? In the settings, I see an option to select that folder as the documentation root.

rjones (Thu, 01 Apr 2021 14:10:20 GMT):
the two options are `/docs` or `/`

vramaiitkgp (Thu, 01 Apr 2021 17:11:31 GMT):
OK, I moved `documentation` to `docs` and merged with main. But the `gh-pages` branch is behind main by a number of commits. So the pages aren't getting built.

rjones (Thu, 01 Apr 2021 17:20:20 GMT):
you'll need to update the branch, then.

vramaiitkgp (Thu, 01 Apr 2021 17:23:22 GMT):
OK, I manually published and it succeeded this time, but I'm getting a 404 where the project page should be: https://labs.hyperledger.org/weaver-dlt-interoperability/. Don't know what I am doing wrong.

vramaiitkgp (Thu, 01 Apr 2021 17:26:17 GMT):
Publish from my fork works fine: https://vramakrishna.github.io/weaver-dlt-interoperability/. All I then did was replace `VRamakrishna` with `hyperleder-labs` in the docusaurus configuration.

rjones (Thu, 01 Apr 2021 17:50:40 GMT):
https://labs.hyperledger.org/weaver-dlt-interoperability/

vramaiitkgp (Thu, 01 Apr 2021 17:55:04 GMT):
Oh, I guess there's a time lag?

vramaiitkgp (Thu, 01 Apr 2021 17:55:39 GMT):
Anyway, thanks for your help.

rjones (Thu, 01 Apr 2021 17:56:57 GMT):
sure thing. I changed the setting to publish from `gh-pages/` instead of `gh-pages/docs`

vramaiitkgp (Thu, 01 Apr 2021 17:57:28 GMT):
OK, I'll keep that in mind.

rjones (Thu, 01 Apr 2021 17:57:39 GMT):
it should just work going forward

vramaiitkgp (Thu, 01 Apr 2021 17:58:06 GMT):
One more thing: how do we get an entry on this page: https://labs.hyperledger.org/

rjones (Thu, 01 Apr 2021 18:00:51 GMT):
you have one - https://labs.hyperledger.org/labs/weaver-dlt-interoperability.html - the issue is the title in your lab proposal wasn't updated. you'll need to update it.

vramaiitkgp (Thu, 01 Apr 2021 18:03:32 GMT):
Oh, so I need to update the file in the `labs` folder in the proposal repo and submit a PR?

rjones (Thu, 01 Apr 2021 18:04:27 GMT):
yes. look at the format of one that shows up to see what needs edited

vramaiitkgp (Thu, 01 Apr 2021 18:04:54 GMT):
I found it. Will do as you say. Thanks!

lehors (Thu, 08 Apr 2021 09:34:45 GMT):
In an effort to help bridge the gaps between the various parts of the Hyperledger community the TSC has invited SIGs, WGs, and projects to join a TSC call and give a short presentation on what they are doing if they'd like. I'd like to extend that offer to labs as well. So, please, consider yourself invited and contact me if you're interested.

rjones (Tue, 13 Apr 2021 15:32:53 GMT):
@jyellick who should I contact to move [Mir-BFT](https://labs.hyperledger.org/labs/mir-bft.html) repo to labs?

jyellick (Tue, 13 Apr 2021 15:32:53 GMT):
Has joined the channel.

nizos (Mon, 26 Apr 2021 07:01:34 GMT):
Has joined the channel.

nizos (Mon, 26 Apr 2021 07:01:34 GMT):
@rjones Hi!

nizos (Mon, 26 Apr 2021 07:01:44 GMT):
I am 405 not found :)

nizos (Mon, 26 Apr 2021 07:04:06 GMT):

Architecture

nizos (Mon, 26 Apr 2021 07:05:01 GMT):
I am working on a graduation project to develop a financial ecosystem built on blockchain technology. We chose to use Hyperledger Fabric for this.

nizos (Mon, 26 Apr 2021 07:06:03 GMT):
I have started by modifying the code of the test network and the token erc-20 example in the fabric samples repo.

nizos (Mon, 26 Apr 2021 07:07:15 GMT):
The current implementation is a simple 1 org, 1 peer, 1 orderer, 1 ca, 1 cli + couchdb configuration and it works.

nizos (Mon, 26 Apr 2021 07:07:57 GMT):
I am trying to now make it so that the hole thing can be deployed with a single docker compose up command

nizos (Mon, 26 Apr 2021 07:09:12 GMT):
But I wonder if it is meant to be deployed that way since a lot of scripts seem to need to run first. Scripts to create crypto, artifacts, etc...

nizos (Mon, 26 Apr 2021 07:10:03 GMT):
The goal is simply to make it easier for the other teams on the project to quickly deploy it locally when they need to work with it during development.

nizos (Mon, 26 Apr 2021 07:10:13 GMT):
Am I making much sense?

rjones (Mon, 26 Apr 2021 07:42:11 GMT):
Yes. Have you considered [minifab](https://github.com/hyperledger-labs/minifabric)? It makes automating stuff like this very easy

rjones (Mon, 26 Apr 2021 07:42:22 GMT):
@nizos ^^

nizos (Mon, 26 Apr 2021 07:42:47 GMT):
@rjones Interesting! never heard of it. I will look it up now

rjones (Mon, 26 Apr 2021 07:43:30 GMT):
There is a chat channel for it as well. #fabric-mini

tatsu-sato (Wed, 28 Apr 2021 05:32:50 GMT):
Hi, I'm an initial committer for fabric-opssc, one of the labs projects. We would like to create a new channel on the Hyperledger Rocket.Chat for discussion and information sharing on this tool. How can we request this? Our requested channel name: fabric-opssc

nizos (Wed, 28 Apr 2021 08:05:11 GMT):
Hi, can I use affiliations with minifabric?

heenas06 (Tue, 04 May 2021 06:18:33 GMT):
Has joined the channel.

rjones (Mon, 10 May 2021 18:25:38 GMT):
@VipinB I've started documenting some of the questions for you: https://wiki.hyperledger.org/display/CA/Archive+a+lab

waqaswahid1 (Thu, 03 Jun 2021 11:21:26 GMT):
Has joined the channel.

stevecerveny (Thu, 03 Jun 2021 15:58:41 GMT):
Has joined the channel.

stevecerveny (Thu, 03 Jun 2021 15:58:42 GMT):
Hi, can someone confirm who are the current lab stewards? We'd like to get FireFly in

tkuhrt (Thu, 03 Jun 2021 16:36:46 GMT):
Current Lab Stewards : @lehors @VipinB @trbs and myself

tkuhrt (Thu, 03 Jun 2021 16:36:46 GMT):
@stevecerveny : Current Lab Stewards : @lehors @VipinB @trbs and myself

lehors (Thu, 03 Jun 2021 16:48:50 GMT):
just ask if you have any problems but the process is very straight forward and I'm sure @rjones can the repo setup quickly so you can get your lab running within a day or 2

lehors (Thu, 03 Jun 2021 16:48:50 GMT):
just ask if you have any problems but the process is very straight forward and I'm sure @rjones can get the repo setup quickly so you can get your lab running within a day or 2

stevecerveny (Thu, 03 Jun 2021 17:50:35 GMT):
thanks all

rjones (Thu, 03 Jun 2021 17:57:49 GMT):
@stevecerveny @lehors I don't think there are any repo setup steps needed - file the PR, transfer in the repos

lehors (Thu, 03 Jun 2021 17:58:25 GMT):
well, transfer is the setup in this case :)

rjones (Thu, 03 Jun 2021 17:58:42 GMT):
@lehors if you could vote for your own proposal to archive that fabric lab I'd appreciate it. that or I can use `force majeure`

lehors (Thu, 03 Jun 2021 17:59:04 GMT):
lol, I was just looking at it

lehors (Thu, 03 Jun 2021 17:59:08 GMT):
give me a chance!

rjones (Thu, 03 Jun 2021 17:59:17 GMT):
tick tock

lehors (Thu, 03 Jun 2021 17:59:29 GMT):
I was chairing another LF meeting...

lehors (Thu, 03 Jun 2021 17:59:43 GMT):
isn't that a valid excuse for not having responded yet?

lehors (Thu, 03 Jun 2021 18:02:06 GMT):
so that other repo was setup for that same lab but never used?

lehors (Thu, 03 Jun 2021 18:02:22 GMT):
if so, then, yes, nuke it

rjones (Thu, 03 Jun 2021 18:02:59 GMT):
OK

tkuhrt (Thu, 03 Jun 2021 19:52:23 GMT):
Pretty sure you cannot approve a PR that you created. Might need to use the `foruce majeure` Ry

tkuhrt (Thu, 03 Jun 2021 19:52:23 GMT):
Pretty sure you cannot approve a PR that you created. Might need to use the `foruce majeure` @rjones cc:@lehors

tkuhrt (Thu, 03 Jun 2021 19:52:23 GMT):
Pretty sure you cannot approve a PR that you created. Might need to use the `foruce majeure` @rjones cc: @lehors

tkuhrt (Thu, 03 Jun 2021 19:52:23 GMT):
Pretty sure you cannot approve a PR that you created. Might need to use the `force majeure` @rjones cc: @lehors

rjones (Thu, 03 Jun 2021 19:55:41 GMT):
ah of course, you're right

rjones (Thu, 03 Jun 2021 19:56:17 GMT):
@tkuhrt done.

rjones (Thu, 03 Jun 2021 19:57:17 GMT):
@tkuhrt @lehors @VipinB @trbs you may have noticed that I moved all of the archived labs from the `hyperledger-labs-archives` to the main org. This will make `archiving` much easier to do, and reverse.

tkuhrt (Thu, 03 Jun 2021 19:58:06 GMT):
So no more hyperledger-labs-archives organization?

rjones (Thu, 03 Jun 2021 19:58:10 GMT):
right.

rjones (Thu, 03 Jun 2021 19:58:24 GMT):
well, it exists, but it is empty

tkuhrt (Thu, 03 Jun 2021 19:58:27 GMT):
I was wondering why I was removed from the organization. Now it all makes sense.

rjones (Thu, 03 Jun 2021 19:59:16 GMT):
I was noodling on one of Vipin's questions, and I realized that really didn't make sense for labs - archiving and unarchiving should be much easier, instead of the multi-step pain in the behind

rjones (Thu, 03 Jun 2021 20:00:06 GMT):
Also - lots of labs still using `master` branch. https://github.com/ryjones/repolister/blob/main/hyperledger-labs-repos-master-branch-default.json

tkuhrt (Thu, 03 Jun 2021 20:00:10 GMT):
Archived flag is nice

rjones (Thu, 03 Jun 2021 20:00:30 GMT):
Yup, and I can delegate that, unlike repo transfers which is a pain

tkuhrt (Thu, 03 Jun 2021 20:00:57 GMT):
Should we create issues for all the labs that still have master branch?

rjones (Thu, 03 Jun 2021 20:02:04 GMT):
maybe?

rjones (Thu, 03 Jun 2021 20:02:37 GMT):
Let me see if there is an easy way to do it via the API

lehors (Fri, 04 Jun 2021 05:16:43 GMT):
I suspect this is something people don't even know about given that we recently discovered some didn't know we expected them to use the Apache 2 license

lehors (Fri, 04 Jun 2021 05:17:24 GMT):
so this is something we should add to the documentation and yes, creating issues is a good idea

BrunoVavala (Fri, 04 Jun 2021 20:32:04 GMT):
@rjones I have created the main branch for Private Data Objects (https://github.com/hyperledger-labs/private-data-objects/tree/main) but I can't switch the default branch. Would you please do that?

rjones (Fri, 04 Jun 2021 21:32:24 GMT):
@BrunoVavala done

BrunoVavala (Fri, 04 Jun 2021 21:37:29 GMT):
thanks Ry!

rjones (Mon, 07 Jun 2021 16:13:54 GMT):
@tkuhrt @lehors I undid the removal of the `Sponsor` stanza; apologies for the turbulence

lehors (Mon, 07 Jun 2021 16:14:26 GMT):
no worries, thanks

lehors (Mon, 07 Jun 2021 16:14:46 GMT):
only those who do nothing make no mistakes :)

barankilic (Sat, 12 Jun 2021 15:29:59 GMT):
Has joined the channel.

toddinpal (Sat, 12 Jun 2021 17:54:55 GMT):
Has joined the channel.

toddinpal (Sat, 12 Jun 2021 17:54:56 GMT):
@adc any timeframe for when the Fabric Token SDK design or architecture documentation will be made available?

adc (Sat, 12 Jun 2021 17:54:56 GMT):
Has joined the channel.

tkuhrt (Mon, 14 Jun 2021 15:07:19 GMT):
Hi, @HritikGupta : Moving your DM to this channel so that we can ensure visibility. > I was a hyperledger mentorship program mentee for the last year (2020) and worked on this project https://labs.hyperledger.org/labs/citizens-pulse.html, that was accepted in Hyperledger Labs > We are maintaining this code in a public repo that's owned by my mentor and would like to move it to hyperledger-labs repo to invite more contributors > Could you help me with an initial commit of creating a repo for the project so that I can push the code there? If the public repo has DCO sign-offs and an Apache 2.0 license, we could have your mentor transfer the lab to @rjones (Github user : ryjones) so that he can then transfer into the hyperledger-labs organization. (I do not remember if I still have this access).

HritikGupta (Mon, 14 Jun 2021 15:07:19 GMT):
Has joined the channel.

rjones (Mon, 14 Jun 2021 15:34:53 GMT):
@tkuhrt thanks! I created a blank repo as a target, which I hope works

swati25 (Tue, 15 Jun 2021 11:15:46 GMT):
Has joined the channel.

swati25 (Tue, 15 Jun 2021 11:15:50 GMT):
Hi .. i am trying to do a dev environment setup for fabric block archiving but none of the specified links in readme is working.. any leads will be highly appreciated

rjones (Tue, 15 Jun 2021 14:42:59 GMT):
@swati25 it looks like that repo hasn't had a commit in over a year

toddinpal (Tue, 15 Jun 2021 17:43:10 GMT):
adc any timeframe for when the Fabric Token SDK design or architecture documentation will be made available? It's really hard to follow the code without a bit more context.

toddinpal (Tue, 15 Jun 2021 17:43:10 GMT):
@adc any timeframe for when the Fabric Token SDK design or architecture documentation will be made available? It's really hard to follow the code without a bit more context.

rjones (Tue, 15 Jun 2021 20:32:52 GMT):
@frank-bee I added that app, but you might need to log in to make it work? they wanted me to click through and do a bunch of stuff and I'm not willing to do that

rjones (Tue, 15 Jun 2021 20:32:52 GMT):
@frank-bee I added [GitPod](https://www.gitpod.io), but you might need to log in to make it work? they wanted me to click through and do a bunch of stuff and I'm not willing to do that

frank-bee (Wed, 16 Jun 2021 06:51:40 GMT):
Cool thanks! Gitpod works even without this app. A developer can just use the badge in our readme.md to work with it. The github app just allows some extra features , it works like a bot and add some comments /links to PRs

rjones (Wed, 16 Jun 2021 15:27:22 GMT):
I approved that, but it wanted additional configuration. I think you can do that configuration via a file in github directly

frank-bee (Sat, 19 Jun 2021 08:03:24 GMT):
sure..that worked. I have configured a setup for gitpod now, quite nice. Could be interesting for other projects as well

HritikGupta (Sat, 19 Jun 2021 11:38:45 GMT):
Thanks @rjones @tkuhrt for helping out, I have added the code to the repo. If we need to add ci/cd to the commits, should we simply write a workflows yaml ?

rjones (Sat, 19 Jun 2021 15:35:10 GMT):
@HritikGupta yes, use GitHub actions for ci/cd. as far as a chat channel, please use this channel

HritikGupta (Sat, 19 Jun 2021 15:38:13 GMT):
Got it, thanks!

msarres (Tue, 22 Jun 2021 17:35:14 GMT):
Has joined the channel.

nguyer (Fri, 02 Jul 2021 12:19:36 GMT):
Has joined the channel.

shemnon (Fri, 02 Jul 2021 22:21:49 GMT):
Has joined the channel.

lohan.spies (Wed, 07 Jul 2021 13:25:21 GMT):
Has joined the channel.

VadimInshakov (Wed, 14 Jul 2021 08:56:30 GMT):
Has joined the channel.

VadimInshakov (Wed, 14 Jul 2021 08:56:30 GMT):
@rjones Hi! I'm maintainer of FabEx project in Hyperledger Labs and I was deleted from hyperledger-labs org on Github automatically, because I was recovering access to my account after losing it (problems with 2FA). Can you add me again?

tkuhrt (Wed, 14 Jul 2021 15:19:14 GMT):
What is your Github ID?

VadimInshakov (Wed, 14 Jul 2021 15:52:17 GMT):
@tkuhrt `vadiminshakov`

tkuhrt (Wed, 14 Jul 2021 15:54:19 GMT):
Sent you an invite that will add you to the fabex-committers team

maddocche (Thu, 22 Jul 2021 09:16:22 GMT):
Has joined the channel.

maddocche (Thu, 22 Jul 2021 09:16:23 GMT):
Hi everyone! Just heard about YUI, the new project added to labs with the goal of inter-chain communication. I'd like to know more about this project but I can't find other info except the ones in labs pages. It seems it still doesn't have its rocketchat channel. Is there a place where I can find more info about this project? I'd like to know things like current state, next milestones, planned roadmap, etc etc... Thank you!

rjones (Thu, 22 Jul 2021 12:21:21 GMT):
@maddocche this is the place

rjones (Wed, 28 Jul 2021 15:40:04 GMT):
@adlrocha @mtng I noticed the TrustID has a couple questions about how to use it. [Issue 43](https://github.com/hyperledger-labs/TrustID/issues/43) [issue 44](https://github.com/hyperledger-labs/TrustID/issues/44)

rjones (Wed, 28 Jul 2021 15:40:04 GMT):
@adlrocha @mtng I noticed the TrustID lab has a couple questions about how to use it. [Issue 43](https://github.com/hyperledger-labs/TrustID/issues/43) [issue 44](https://github.com/hyperledger-labs/TrustID/issues/44)

mtng (Wed, 28 Jul 2021 15:40:04 GMT):
Has joined the channel.

unnati (Mon, 02 Aug 2021 17:32:29 GMT):
Has joined the channel.

unnati (Mon, 02 Aug 2021 17:34:58 GMT):
Hey everyone! I am Unnati a prefinal year student from India! I will be applying for LFX Mentorship this time. Could anyone let me know about the issues like when it will be live? Thank you

rjones (Mon, 02 Aug 2021 17:54:38 GMT):
Hi - the current mentorships for 2021 have all been awarded and are in progress. Dates for 2022 will be similar

Bobbijn (Mon, 02 Aug 2021 21:58:49 GMT):
Hello, The Giving Chain mentorship project is looking to move into a Lab, anyone interested in Sponsoring us? Bobbi and Hardik

rjones (Mon, 02 Aug 2021 22:06:09 GMT):
I think the sponsorship requirement turned into a nice-to-have

rjones (Mon, 02 Aug 2021 22:15:08 GMT):
@Bobbijn [It was earlier this year](https://wiki.hyperledger.org/display/TSC/Eliminate+Lab+Sponsor+requirement)

unnati (Tue, 03 Aug 2021 07:39:36 GMT):
[ ](https://chat.hyperledger.org/channel/labs?msg=Ww96K3kGeAXArCrXF) but i can see one project listed on lfx site and applications are open for fall 2021

unnati (Tue, 03 Aug 2021 07:40:22 GMT):

Clipboard - August 3, 2021 1:10 PM

unnati (Tue, 03 Aug 2021 07:42:27 GMT):
could you please tell me which communication channel i should join for this?

rjones (Tue, 03 Aug 2021 16:00:25 GMT):
@myu ?

myu (Tue, 03 Aug 2021 16:00:25 GMT):
Has joined the channel.

myu (Tue, 03 Aug 2021 16:05:22 GMT):
@unnati You're correct that we have one Hyperledger mentorship project currently accepting application. The plan is to identify one mentee toward the end of August and the mentee/mentor working session will be September through November.

myu (Tue, 03 Aug 2021 16:07:08 GMT):
If you have any questions about this project, I encourage you to check out details of the project here https://wiki.hyperledger.org/display/INTERN/Automated+Testing+for+Climate+Emissions+Ledger and reach out to the mentors directly.

rjones (Tue, 03 Aug 2021 16:17:35 GMT):
thank you @myu - @unnati , I was wrong. Sorry for the misinformation!

unnati (Wed, 04 Aug 2021 02:31:07 GMT):
ok thank you so much

unnati (Wed, 04 Aug 2021 06:22:21 GMT):
From where i can contact mentors? through mail?

knagware9 (Fri, 06 Aug 2021 04:37:49 GMT):
@unnati you can contact me kamlesh.nagware@snapperfuturetech.com, I am on of mentor this project along with Robin & Si chen

Gavimat (Thu, 26 Aug 2021 12:38:40 GMT):
Has joined the channel.

seanyoung (Fri, 05 Nov 2021 11:59:18 GMT):
I'm writing a npm module for solang. Would it be possible to publish this as `@hyperledger-labs/solang` ?

rjones (Fri, 05 Nov 2021 16:05:55 GMT):
yes

seanyoung (Fri, 05 Nov 2021 16:38:01 GMT):
@rjones thanks! I'll be in touch once it is finished

barankilic (Tue, 16 Nov 2021 09:46:27 GMT):
Hi! The message is about https://github.com/hyperledger-labs/pluggable-hcs . I created a Hedera testnet account and followed this tutorial https://docs.hedera.com/guides/resources/tutorials/getting-started-with-the-hedera-consensus-service-fabric-plugin . The dev branch gives the following error at network launch step (./byfn.sh up -t 20): ``` ========= Chaincode is packaged on peer0.org1 =========== Installing chaincode on peer0.org1... + peer lifecycle chaincode install mycc.tar.gz + res=1 + set +x Error: chaincode install failed with status: 500 - failed to invoke backing implementation of 'InstallChaincode': could not build chaincode: docker build failed: docker image inspection failed: Get "http://unix.sock/images/dev-peer0.org1.example.com-mycc_1-499c930c033864d90e4fcac68113bd10748065b33295ba12d0a8b39b764d8bd4-41b9dcbab025e3161b78c8ec45c0fabdc30e0485238473ec8567c79a0ba37727/json": dial unix /host/var/run/docker.sock: connect: no such file or directory !!!!!!!!!!!!!!! Chaincode installation on peer0.org1 has failed !!!!!!!!!!!!!!!! ========= ERROR !!! FAILED to execute End-2-End Scenario =========== ERROR !!!! Test failed ``` The main branch gives the following error: ``` Channel name : mychannel Creating channel... Signing the channel create transaction... 2021-11-16 09:03:11.440 UTC [channelCmd] InitCmdFactory -> INFO 001 Endorser and orderer connections initialized 2021-11-16 09:03:11.577 UTC [channelCmd] InitCmdFactory -> INFO 001 Endorser and orderer connections initialized + peer channel create -o orderer.example.com:7050 -c mychannel -f ./channel-artifacts/channel.tx --tls true --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem -t 30s + res=1 + set +x 2021-11-16 09:03:11.722 UTC [channelCmd] InitCmdFactory -> INFO 001 Endorser and orderer connections initialized Error: rpc error: code = Unavailable desc = transport is closing !!!!!!!!!!!!!!! Channel creation failed !!!!!!!!!!!!!!!! ========= ERROR !!! FAILED to execute End-2-End Scenario =========== ERROR !!!! Test failed ```

xlswirlds (Tue, 16 Nov 2021 15:55:38 GMT):
Has joined the channel.

xlswirlds (Tue, 16 Nov 2021 15:55:38 GMT):
@barankilic did you run it on a linux box? If not, can you try it again on a linux system for example ubuntu? btw, testnet node 3 is unhealthy atm, you can remove it from first-network/hedera_env.json, otherwise hcscli may get stuck on creating HCS topics fro the demo

barankilic (Wed, 17 Nov 2021 10:22:08 GMT):
@xlswirlds Thank you for your answer. I did run it on Macos. I will try it with linux.

barankilic (Tue, 23 Nov 2021 07:24:38 GMT):
@xlswirlds Thanks. Running it on Linux and removing testnet node 3 solved the problem.

seanyoung (Thu, 25 Nov 2021 19:13:14 GMT):
@rjones is possible to upgrade rust on the mac arm runner please? 1.56.1 would be great. I've tried upgrading using `arch -arm64 rustup default 1.56.1`, but I get `arch: posix_spawnp: rustup: Bad CPU type in executable`. Without `arch -arm64` rust get updated to x86 binaries. Enjoy thanksgiving.

rjones (Thu, 25 Nov 2021 19:27:02 GMT):
@seanyoung I think you were over-thinking it - I ran rustup, and look at the host triple

rjones (Thu, 25 Nov 2021 19:27:06 GMT):
```rustup default 1.56.1 info: syncing channel updates for '1.56.1-aarch64-apple-darwin' info: latest update on 2021-11-01, rust version 1.56.1 (59eed8a2a 2021-11-01) info: downloading component 'cargo' info: downloading component 'clippy' info: downloading component 'rust-std' 21.6 MiB / 21.6 MiB (100 %) 10.2 MiB/s in 2s ETA: 0s info: downloading component 'rustc' 58.7 MiB / 58.7 MiB (100 %) 10.3 MiB/s in 5s ETA: 0s info: downloading component 'rustfmt' info: installing component 'cargo' info: installing component 'clippy' info: installing component 'rust-std' 21.6 MiB / 21.6 MiB (100 %) 19.1 MiB/s in 1s ETA: 0s info: installing component 'rustc' 58.7 MiB / 58.7 MiB (100 %) 21.6 MiB/s in 2s ETA: 0s info: installing component 'rustfmt' info: default toolchain set to '1.56.1-aarch64-apple-darwin' 1.56.1-aarch64-apple-darwin installed - rustc 1.56.1 (59eed8a2a 2021-11-01)```

rjones (Thu, 25 Nov 2021 19:27:28 GMT):
@seanyoung if doing that didn't work, let me know

seanyoung (Thu, 25 Nov 2021 20:33:46 GMT):
@rjones that worked, thank you!

seanyoung (Thu, 02 Dec 2021 09:56:41 GMT):
@rjones I've been trying to build docker images on the mac arm runner, but I'm running into strange issues. gcc seems to crash https://github.com/hyperledger-labs/solang/runs/4382032789?check_suite_focus=true#step:3:9291 and https://github.com/hyperledger-labs/solang/runs/4385189296?check_suite_focus=true#step:3:6215 I have not seen this issue before. Is it possible that the docker or macos software needs an update? I know I'm clutching at straws here.

rjones (Thu, 02 Dec 2021 15:39:14 GMT):
@seanyoung I could upgrade to Monterey, if you like. Docker did have a pending update, so I installed it. I also did a brew upgrade for: ```hyp@hyp-ci-arm ~ % brew outdated automake (1.16.4) < 1.16.5 ccache (4.4) < 4.5.1 cmake (3.21.2) < 3.22.0 coreutils (8.32) < 9.0 gdbm (1.20) < 1.22 git (2.33.0) < 2.34.1 go (1.16.6) < 1.17.3 hiredis (1.0.0) < 1.0.2 htop (3.0.5) < 3.1.2 ncurses (6.2) < 6.3 ninja (1.10.2) < 1.10.2_1 openssl@1.1 (1.1.1k) < 1.1.1l_1 pcre2 (10.37_1) < 10.39 python@3.9 (3.9.6) < 3.9.9 readline (8.1) < 8.1.1 wget (1.21.1_1) < 1.21.2 ```

seanyoung (Thu, 02 Dec 2021 15:39:48 GMT):
@rjones thank you! I'll give it another go.

rjones (Thu, 02 Dec 2021 15:41:51 GMT):
I also bumped the CPU, swap, and RAM up in case it was running into limits there.

rjones (Thu, 02 Dec 2021 15:42:39 GMT):
If you want me to upgrade to Monterey, I will, since you're _basically_ the only user of this machine. I usually don't upgrade the OS on machines in a CI stack

seanyoung (Thu, 02 Dec 2021 15:51:51 GMT):
hopefully this works and there is no need to upgrade.

rjones (Thu, 02 Dec 2021 15:59:57 GMT):
I wonder if it is an issue of crossing the p/e core boundary or something

rjones (Thu, 02 Dec 2021 16:00:26 GMT):
this box has 4p, 4e. When I look, the build is only using 100% of 1 P core.

rjones (Thu, 02 Dec 2021 16:00:35 GMT):
so, it's single-threaded

seanyoung (Thu, 02 Dec 2021 18:03:00 GMT):
The docker build got a little further this time, and failed on a different file. It does seem like a resource limitation. I thought the mac was fast, *before* I knew it was doing everything in a single thread.

rjones (Thu, 02 Dec 2021 18:19:25 GMT):
I was shocked to see that as well. Parts of the build are multi-threaded, but it looks like a lot of it isn't.

rjones (Thu, 02 Dec 2021 18:24:14 GMT):
@tkuhrt @sownak - now that the name is decided, do you want me to rename BAF and move it from labs to the main org?

sownak (Thu, 02 Dec 2021 18:24:14 GMT):
Has joined the channel.

sownak (Fri, 03 Dec 2021 07:12:32 GMT):
@rjones Yes please. We will then update the images and name with the logo once it is final.

rjones (Fri, 03 Dec 2021 17:03:33 GMT):
@sownak https://github.com/hyperledger/bevel

jcarpenter (Wed, 12 Jan 2022 17:46:33 GMT):
Has joined the channel.

jcarpenter (Wed, 12 Jan 2022 17:51:28 GMT):
Happy 2022 everyone! If you are interested in learning about MirBFT and it successor ISS coming out of the Hyperledger Labs, please join us for this session on January 13th at 10:00am MT (12:00 noon ET). https://www.meetup.com/Hyperledger-Denver/events/283055089/

sbohanlf (Tue, 25 Jan 2022 15:23:44 GMT):
Has joined the channel.

rjones (Wed, 23 Mar 2022 17:35:42 GMT):