Future of HL Explorer


Chinoy, Vinita M. <vchinoy@...>
 

Hello,

 

As you may know so far folks from DTCC and one person from Fujitsu have been maintainers for the Hyperledger blockchain explorer for the past few years. With members from both organizations being pulled into other work, it has become hard for us to continue being in the maintainers role without support from the community. Last year with David Boswell’s help we presented to the community both on US and APAC side to try and get more contributors. It generated interest alright but we did not get any commitment. This year David reached out to me again and we were looking for options when Varad from IBM and us found synergies in creating a combined app that would service a fabric network from both angles, administration side with adding new nodes, deploying chaincode etc. and consumer side to view the nodes information, transactions and chaincode. We were really excited about the opportunity to combine IBM operations console with HL Explorer and source help from the community to make this happen but unfortunately IBM pulled out.

So now we are back where started, still looking for new maintainers/contributors. Since we see Explorer is being used and definitely helps the larger community we would like to keep it alive in others’ capable hands. Wanted to bring this to TSC to see if you can help us find the right folks to handover to.

If we could add this to TSC call Agenda for next week, I would be happy to elaborate on this.

 

Thanks.

 

Vinita Chinoy

Director, Software Engineering

Technology Research & Innovation

DTCC Tampa

+1 813-470-2662 | vchinoy@...

 

Visit us at www.dtcc.com or connect with us on LinkedIn, Twitter, Facebook and YouTube.

To learn about career opportunities at DTCC, please visit careers.dtcc.com.

 


DTCC Internal (Green)

DTCC DISCLAIMER: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error, please notify us immediately and delete the email and any attachments from your system. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. Message content created by DTCC is automatically secured using Transport Layer Security (TLS) encryption and will be encrypted and sent through a secure transmission connection if the recipient's system is configured to support TLS on the incoming email gateway. If there is no TLS configured or the encryption certificate is invalid on the recipient's system, the email communication will be sent through an unencrypted channel. Organizations communicating with DTCC should be using TLS v1.2 or newer to ensure continuation of encrypted communications. DTCC will not be responsible for any disclosure of private information or any related security incident resulting from an organization's inability to receive secure electronic communications through the current version of TLS.


Somogyvari, Peter
 

Hi Vinita,

I'm very sorry to hear about the recent difficulties regarding the maintenance of Hyperledger Explorer.
Since we see Explorer is being used and definitely helps the larger community we would like to keep it alive in others’ capable hands.
​Is there a list of these users somewhere by any chance? Better yet, could I talk to them?
What I'm interested to know is what parts (or if it's the whole) of Explorer are they most interested in using and why.

Further explaining my motivation here: 
If we can identify a smaller sub-set of code/components that deliver most of the value for existing users (if we are lucky and pareto's law applies, 20% of the code will deliver 80% of the value) then maybe the Cactus maintainers could consider adopting those parts thereby keeping the community engaged but in a more efficient/focused way on account of us having picked out the interesting parts.

I'm emphasizing this partial adoption angle because I do not have the resources to volunteer to maintain the entire Explorer codebase as-is. This is not just on account of the size of the codebase, but also because being the maintainer of one more GitHub repository is additional administrative overhead (separate permissions, reporting, issue tracker, meeting calendar, chat room, mailing list etc.)

You might get "better" offers, e.g. someone steps up to take the mantle as-is, and if that happens, great, but if not, we could try to initiate these conversations with the people/organizations who use Explorer in production and just see where it goes.

We have an item in the Cactus issue tracker for something similar/related: https://github.com/hyperledger/cactus/issues/1979

I'm happy to discuss it further at the TSC call tomorrow, or just keep it in email, I'm fine either way.

Kind regards,
Peter

Peter Somogyvari

Technology Architect

Accenture Products & Platforms (APP)

Office: +1 (415) 537-5541

Mobile: +1 (650) 488-1741


From: tsc@... <tsc@...> on behalf of Chinoy, Vinita M. <vchinoy@...>
Sent: Wednesday, May 4, 2022 11:19 AM
To: tsc@... <tsc@...>
Subject: [External] [Hyperledger TSC] Future of HL Explorer
 
This message is from an EXTERNAL SENDER - be CAUTIOUS, particularly with links and attachments.

Hello,

 

As you may know so far folks from DTCC and one person from Fujitsu have been maintainers for the Hyperledger blockchain explorer for the past few years. With members from both organizations being pulled into other work, it has become hard for us to continue being in the maintainers role without support from the community. Last year with David Boswell’s help we presented to the community both on US and APAC side to try and get more contributors. It generated interest alright but we did not get any commitment. This year David reached out to me again and we were looking for options when Varad from IBM and us found synergies in creating a combined app that would service a fabric network from both angles, administration side with adding new nodes, deploying chaincode etc. and consumer side to view the nodes information, transactions and chaincode. We were really excited about the opportunity to combine IBM operations console with HL Explorer and source help from the community to make this happen but unfortunately IBM pulled out.

So now we are back where started, still looking for new maintainers/contributors. Since we see Explorer is being used and definitely helps the larger community we would like to keep it alive in others’ capable hands. Wanted to bring this to TSC to see if you can help us find the right folks to handover to.

If we could add this to TSC call Agenda for next week, I would be happy to elaborate on this.

 

Thanks.

 

Vinita Chinoy

Director, Software Engineering

Technology Research & Innovation

DTCC Tampa

+1 813-470-2662 | vchinoy@...

 

Visit us at www.dtcc.com or connect with us on LinkedIn, Twitter, Facebook and YouTube.

To learn about career opportunities at DTCC, please visit careers.dtcc.com.

 


DTCC Internal (Green)

DTCC DISCLAIMER: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error, please notify us immediately and delete the email and any attachments from your system. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. Message content created by DTCC is automatically secured using Transport Layer Security (TLS) encryption and will be encrypted and sent through a secure transmission connection if the recipient's system is configured to support TLS on the incoming email gateway. If there is no TLS configured or the encryption certificate is invalid on the recipient's system, the email communication will be sent through an unencrypted channel. Organizations communicating with DTCC should be using TLS v1.2 or newer to ensure continuation of encrypted communications. DTCC will not be responsible for any disclosure of private information or any related security incident resulting from an organization's inability to receive secure electronic communications through the current version of TLS.



This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy. Your privacy is important to us. Accenture uses your personal data only in compliance with data protection laws. For further information on how Accenture processes your personal data, please see our privacy statement at https://www.accenture.com/us-en/privacy-policy.
______________________________________________________________________________________

www.accenture.com


Kuhrt, Tracy A.
 

Hi, Vinita.

 

I will add you to the May 12th TSC call.

 

Tracy

 

 

From: <tsc@...> on behalf of "Chinoy, Vinita M." <vchinoy@...>
Date: Wednesday, May 4, 2022 at 1:58 PM
To: "tsc@..." <tsc@...>
Subject: [External] [Hyperledger TSC] Future of HL Explorer

 

This message is from an EXTERNAL SENDER - be CAUTIOUS, particularly with links and attachments.


 

Hello,

 

As you may know so far folks from DTCC and one person from Fujitsu have been maintainers for the Hyperledger blockchain explorer for the past few years. With members from both organizations being pulled into other work, it has become hard for us to continue being in the maintainers role without support from the community. Last year with David Boswell’s help we presented to the community both on US and APAC side to try and get more contributors. It generated interest alright but we did not get any commitment. This year David reached out to me again and we were looking for options when Varad from IBM and us found synergies in creating a combined app that would service a fabric network from both angles, administration side with adding new nodes, deploying chaincode etc. and consumer side to view the nodes information, transactions and chaincode. We were really excited about the opportunity to combine IBM operations console with HL Explorer and source help from the community to make this happen but unfortunately IBM pulled out.

So now we are back where started, still looking for new maintainers/contributors. Since we see Explorer is being used and definitely helps the larger community we would like to keep it alive in others’ capable hands. Wanted to bring this to TSC to see if you can help us find the right folks to handover to.

If we could add this to TSC call Agenda for next week, I would be happy to elaborate on this.

 

Thanks.

 

Vinita Chinoy

Director, Software Engineering

Technology Research & Innovation

DTCC Tampa

+1 813-470-2662 | vchinoy@...

 

Visit us at www.dtcc.com or connect with us on LinkedIn, Twitter, Facebook and YouTube.

To learn about career opportunities at DTCC, please visit careers.dtcc.com.

 

 

DTCC Internal (Green)

DTCC DISCLAIMER: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error, please notify us immediately and delete the email and any attachments from your system. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. Message content created by DTCC is automatically secured using Transport Layer Security (TLS) encryption and will be encrypted and sent through a secure transmission connection if the recipient's system is configured to support TLS on the incoming email gateway. If there is no TLS configured or the encryption certificate is invalid on the recipient's system, the email communication will be sent through an unencrypted channel. Organizations communicating with DTCC should be using TLS v1.2 or newer to ensure continuation of encrypted communications. DTCC will not be responsible for any disclosure of private information or any related security incident resulting from an organization's inability to receive secure electronic communications through the current version of TLS.




This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy. Your privacy is important to us. Accenture uses your personal data only in compliance with data protection laws. For further information on how Accenture processes your personal data, please see our privacy statement at https://www.accenture.com/us-en/privacy-policy.
______________________________________________________________________________________

www.accenture.com