Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.





@Bobbi Muscara
Dear Bobbi, long time no see. Recently I try to bridge some resources among Chinese and English language, and also the community inter-visiblity.  
Since conflunce wiki is not network friendly inside mainland China from years ago, we have to fallback to Github for even documentation purpose. 
We recently migrate most of the active material into https://github.com/Hyperledger-TWGC and also learning material in https://github.com/Hyperledger-TWGC/Learning-Material

Really happy to see so many great works in this Github Resources page! And since there are too many and make here looks a little unstrcuted, I would like to let you decide where should our works be placed organized in current LMDWG framework. 
Cheers, 

David Liu


@Bobbi Muscara
Dear Bobbi, long time no see. Recently I try to bridge some resources among Chinese and English language, and also the community inter-visiblity.  
Since conflunce wiki is not network friendly inside mainland China from years ago, we have to fallback to Github for even documentation purpose. 
We recently migrate most of the active material into https://github.com/Hyperledger-TWGC and also learning material in https://github.com/Hyperledger-TWGC/Learning-Material

Really happy to see so many great works in this Github Resources page! And since there are too many and make here looks a little unstrcuted, I would like to let you decide where should our works be placed organized in current LMDWG framework. 
Cheers, 

David Liu



DEVELOPERS Select link to Get Started:   https://start-here.hyperledger.org/

Get started in a LMDWG project .

https://zoom.us/j/93304666234?pwd=OEswSmpjS2oxeWE2NmZId2hBanBnQT09 https://github.com/hyperledger/learning-materials-dev




Purpose:


Hosting content that makes sense to have in GitHub (i.e. where source control makes sense, as opposed to using the wiki) that the LMDWG members want to share for collaboration.  Ideally, this should just be a "development" area where it is being prepped for some greater purpose in the published Hyperledger documentation space.  This should not be the final destination where a contribution comes to grow old and die, since we're a development working group.

...

  • Anyone who contributes a <project> must be willing to be the maintainer of that <project>.  This means answering questions, responding to issues, keeping things up-to-date, and driving the contribution to its destination in the published Hyperledger documentation space.  They may have co-maintainers.
  • Issues should be reported using the GitHub issues mechanism.  We should come up with some guidelines to make sure people submit issues with relevant details.  We should also come up with expected response time for the maintainers to respond to issues.
  • Contributions should be submitted by GitHub Pull Request.  For anything that involves code, it must have a test suite to ensure nothing breaks and passing tests and instructions for others to run the test suite.  New contributions must also pass the test suite and, if implementing new features not covered by the test suite, new tests should also be submitted to the test suite & everything should pass.  
  • Any ACTIVE/<project> that has had no updates for a year will be moved to ARCHIVE/ and all the Issues & PRs for it will be closed as obsolete.  This can happen sooner at the request of the <project> maintainer.
  • Any other suggestions for rules?  


2. Project Plan - Build a university course on Hyperledger Fabric using Hyperledger Umbra

Hello all,
I'm building a university course on Hyperledger Technologies, with focus on Hyperledger Fabric. This course is open source and will be exposed as an Hyperledger Lab. Despite being focused on Fabric, I think it would be very valuable including a lab class on Hyperledger Besu.

I would like very much to welcome any ideas, suggestions, and contributions.
Please feel free to reach me!

Cheers,

--Rafael BelchiorPh.D. student in Computer Science and Engineering, Blockchain - Técnico Lisboa
https://rafaelapb.github.io/
https://www.linkedin.com/in/rafaelpbelchior/

...