Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin


Anti-trust Policy Notice & Code of Conduct

  • Linux Foundation meetings involve participation by industry competitors, and it is the intention of the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in, any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws.
  • Examples of types of actions that are prohibited at Linux Foundation meetings and in connection with Linux Foundation activities are described in the Linux Foundation Antitrust Policy available at http://www.linuxfoundation.org/antitrust-policy. If you have questions about these matters, please contact your company counsel, or if you are a member of the Linux Foundation, feel free to contact Andrew Updegrove of the firm of Gesmer Updegrove LLP, which provides legal counsel to the Linux Foundation.
  • Hyperledger is committed to creating a safe and welcoming community for all. For more information, please visit our  Hyperledger Code of Conduct

18/12/23

Attendees:

  • Bobbi Muscara
  • Gianluca 
  • Arunima

...

Arunima


MkDocs introduction to Mentees PPT - https://gamma.app/docs/Discover-the-Power-of-MkDocs-vzi1068ioocgmnz

8/28



Hyperledger Mentee Checkin and Bonding Session Tuesday, August 22 7:30 – 8:30 pm IST

https://zoom-lfx.platform.linuxfoundation.org/meeting/95778285783?password=84e0bbe5-e2be-4fb8-b382-58d041c8f6a7

 Blog Format Guest blogs

Link to  Presentation

Widget Connector
urlhttps://docs.google.com/presentation/d/1iFc-aQVHuJJ0IKxvqfL9TVFRIwB4zoAb/edit?usp=sharing&ouid=105225806016454599738&rtpof=true&sd=true

https://www.canva.com/design/DAFlKRYU5Wg/jbIyWSl5lXIpOI4LwB5SLg/edit  REBRANDING 


Join us for a check-in meeting to get to know your fellow mentees better, to talk about the progress you've made and challenges you've encountered and overcome since the start of the program. We also have some fun activities planned for the session.

8/21

Attendees

Tripur

Arunima

...

  1.  Hyperledger AnonCreds v2.0 Working Group Meetings

    When:
    Monday, August 21, 2023
    7:00am to 8:00am
    (UTC-07:00) America/Los Angeles

    Where:
    https://zoom.us/j/98881501347?pwd=WURjV3BJYkhtUjg5STVwNHYvakdyZz09

    Organizer: Stephen Curran swcurran@cloudcompass.ca

    View Event

    Description:
    A bi-weekly meeting to discuss AnonCreds v2.0.  The focus of these meetings is to decide what features are needed in a breaking change implementation of AnonCreds. The goal of AnonCreds v2.0 is to retain and extend the privacy-preserving features of AnonCreds v1.0, while improving capabilities, performance, extensibility, and security. Specifically, we are looking at:

    - Enabling the use of additional kinds of ZKPs -- range proofs, set membership/non-membership, blinded encryption, and equality of attributes across credentials, etc.

    - Enabling the use of different underlying cryptographic signatures -- BBS+, PS (with the potential for a PQ version), CL.

    - A new revocation scheme.

    - Formatting the credential and presentation in a way that matches the W3C Verifiable Credentials Data Model Standard

    Progress on the specification has moved forward, and we're beginning work on the documentation -- evolving the AnonCreds v1.0 specification to the v2.0 version.

...

https://youtube.com/live/ewvYeuHDoa4

Presentation Slides: Image Modified Presentation

...

Join Zoom Meeting
https://us02web.zoom.us/j/89749129443?pwd=dmVBU3VpRDd1elBMOUZQU012M01pZz09


View file
nameaudio1490634732.m4adummyfile.txt
pageDocumentation Task Force
spaceTF
height250
View file
namevideo1490634732.mp4dummyfile.txt
pageDocumentation Task Force
spaceTF
height250

7/25

Link to today's AI Meeting 9am edt

https://us02web.zoom.us/j/81802627105?pwd=bkRwazArQmNiVTV6TkFyZDUvWUxPUT09


** 

View file
nameaudio1144310512.m4adummyfile.txt
pageDocumentation Task Force
spaceTF
height250
View file
namevideo1144310512.mp4dummyfile.txt
pageDocumentation Task Force
spaceTF
height250


7/24


Introduction to people on the call

...

View file
nameHyperledger_CBDCs_ebook_2022 (V4) .pdf
pageDocumentation Task Force
spaceTF
height250

Presentation: Learning Tokens @ Hyperledger Besu - Mentorship Project Alfonso Govela

...

 DELIVERABLE- Welcome Mentee Presentation Wednesday , June 14th, 10:00-11:00 EDT 

Recordings

...

  1. Welcome
    1. Anti Trust
    2. Introductions
        1. Yash Pimple
        2. Akanksha Rani
        3. Devesh Meena
        4. Elena Treshcheva
        5. Osama Tahir
        6. Yash Kataria
        7. Arunima Chaudhuri
        8. Pratyay Banerjee
        9. John Carpenter
        10. Bobbi Muscara
  2. Presentation to the Task Force
    1. Summary and Time Frame

    2.  Presentation Details


      Names 
      AreaResource

      Bobbi

      Akanksha Rani

      Arunima Chaudhuri
      Tripur Joshi

      Ezra Okenda


      Introduction

      Elena

      Arunima Chaudhuri

      Yash Pimple

      Kajal Kumari

      Pratyay Banerjee

      Ezra Okenda

      Report on GitHubDirectory update
      Next Steps

      https://github.com/hyperledger/toc/pull/112#discussion_r1201109442

      https://github.com/hyperledger-labs/documentation-template

      1. https://github.com/hyperledger/cacti/blob/10746c3e65891dfa38658d9ecae631222b92fddd/.readthedocs.yaml urllib released which broke previous configs.
      2. https://github.com/readthedocs/readthedocs.org/issues/10290

      Yash Kataria,

      Akanksha Rani

      Arunima Chaudhuri

      Kajal Kumari

      Pratyay Banerjee

      Template

      Suggestion 

      Next Step

      Best Practices Badges / Templates



      Pratyay Banerjee

      Arunima Chaudhuri

      Kajal Kumari

      Ezra Okenda

      Best PracticesSuggestion
      Next Step

      Best Practices Badges / Templates

      https://github.com/hyperledger/toc/pull/111/files#diff-3c3bc5881181f0ebddf231ef31ffb92c747479dd5fad615357c2c1e6f60765da


      Arunima Chaudhuri

      Akanksha Rani

      Pratyay Banerjee

      Onboard Suggestion
      Next Step
      Onboarding Task Force - Task Forces - Hyperledger Foundation

      Akanksha RaniEnd of Task Force Month 


    3.  4 areas of deliverables
      1. Work on Github Repo
        https://github.com/hyperledger-labs/documentation-template

      2. Template / New Brand: Get link from Ben

      3. User Docs

      4. Work with other Task forces

    4.  Result : Where to put information moving forward
  3. Mentorship Program:
  4. Comments

Recording: https://youtu.be/2MYGWIypaKw

5/15/23

Anti-trust Policy Notice & Code of Conduct

  • Linux Foundation meetings involve participation by industry competitors, and it is the intention of the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in, any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws.
  • Examples of types of actions that are prohibited at Linux Foundation meetings and in connection with Linux Foundation activities are described in the Linux Foundation Antitrust Policy available at http://www.linuxfoundation.org/antitrust-policy. If you have questions about these matters, please contact your company counsel, or if you are a member of the Linux Foundation, feel free to contact Andrew Updegrove of the firm of Gesmer Updegrove LLP, which provides legal counsel to the Linux Foundation.
  • Hyperledger is committed to creating a safe and welcoming community for all. For more information, please visit our  Hyperledger Code of Conduct

Attendees 

David Boswell dboswell@linuxfoundation.org

Bobbi Muscara bobbi@LedgerAcademy.com

Arunima Chaudhuri arunimachaudhuri2020@gmail.com

Maurice Magorane magorane@gmail.com

Akanksha Rani akankshar8800@gmail.com

...

Ayush Kumar Singh ayushk4549@gmail.com

Aswin Shailajan aswins2108@gmail.com

Pranit Patil patilpranit3112@gmail.com

...

TaskNameTasks
Work on Github Repo

Bobbi (bobbi@ledgeracademy.com)

Akanksha Rani

akankshar8800@gmail.com

Yash Kataria
yashkataria1993@gmail.com

Arunima Chaudhuri
( arunimachaudhuri2020@gmail.com )

Yash Pimple (yashpimple22@gmail.com)

Balveer Singh Rao (Balveer Singh Rao 5-Year IDD Electrical Engineering


Aswin Shailajan

(aswins2108@gmail.com)



Kajal Kumari
(kajalkumari130801@gmail.com)


Pratyay Banerjee
(pratyaybanerjeex@ gmail.com)

Ezra Okenda

(emanyara97@gmail.com)


  1. Review the GitHub Template and create guides. 
  2. Explore the paid tooling Available
  3. Review Discord Message :
    As a note to any @Project Maintainer using read the docs: you need to update your .readthedocs.yml to look like this: https://github.com/hyperledger/cacti/blob/10746c3e65891dfa38658d9ecae631222b92fddd/.readthedocs.yaml urllib released which broke previous configs. https://github.com/readthedocs/readthedocs.org/issues/10290 https://www.reddit.com/r/technicalwriting/comments/138rxms/readthedocs_sphinx_theme_urllib3_related_build/

Template

Akanksha Rani

akankshar8800@gmail.com

Yash Kataria yashkataria1993@gmail.com


Pranit Patil
patilpranit3112@gmail.com

Arunima Chaudhuri
( arunimachaudhuri2020@gmail.com )


Kajal Kumari
(kajalkumari130801@gmail.com)



Pratyay Banerjee
(pratyaybanerjeex@ gmail.com)


  1. Get new Branding Information from Ben 

User Docs

Balveer Singh Rao Balveer Singh Rao 5-Year IDD Electrical Engineering

Devesh Meena

nothefakedevesh@gmail.com

Arunima Chaudhuri
( arunimachaudhuri2020@gmail.com )

Yash Pimple (yashpimple22@gmail.com)

Rohit Patil

(rohitpatil1625@gmail.com)

Maurice Magorane magorane@gmail.com


Pratyay Banerjee
(pratyaybanerjeex@ gmail.com)

Ezra Okenda

(emanyara97@gmail.com)

Determine what learners need

  1. Community Contributors
  2. Maintainers: https://github.com/hyperledger-labs/documentation-template/blob/main/docs/index.md
  3. New Coders
  4. SIG Chairs
  5. TOC Members
  6. Solution Providers

Work with other Task forces




TOC call Thursday 5/11 10amEDT *Best Practices Task Force presentation
https://github.com/hyperledger/toc/pull/111#discussion_r1191202964

...

TaskNameTasks
Work on Github RepoBobbi (bobbi@ledgeracademy.com)
  1. Review the GitHub Template and create guides. 
  2. Explore the paid tooling Available
  3. Review Discord Message :
    As a note to any @Project Maintainer using read the docs: you need to update your .readthedocs.yml to look like this: https://github.com/hyperledger/cacti/blob/10746c3e65891dfa38658d9ecae631222b92fddd/.readthedocs.yaml urllib released which broke previous configs. https://github.com/readthedocs/readthedocs.org/issues/10290 https://www.reddit.com/r/technicalwriting/comments/138rxms/readthedocs_sphinx_theme_urllib3_related_build/
Template


Akanksha Rani

akankshar8800@gmail.com


Pratyay Banerjee
(pratyaybanerjeex@ gmail.com)


  1. Get new Branding Information from Ben 
User Docs

Determine what learners need

  1. Community Contributors
  2. Maintainers: https://github.com/hyperledger-labs/documentation-template/blob/main/docs/index.md
  3. New Coders
  4. SIG Chairs
  5. TOC Members
  6. Solution Providers
Work with other Task forces

Akanksha Rani

akankshar8800@gmail.com


Pratyay Banerjee
(pratyaybanerjeex@ gmail.com)


TOC call Thursday 5/11 10amEDT *Best Practices Task Force presentation

...

Mentorship Applications for Documentation

PENDING TOC REVIEWBevel: Tutorial on deploying fabric and besu on minikubeDOCUMENTATIONBevel343
23

















PENDING TOC REVIEWBevel: Documentation redesignDOCUMENTATION RESEARCHBevel354
23.5

















PENDING TOC REVIEWBiniBFT - An Optimized BFT on FabricRESEARCHCODINGDOCUMENTATIONFabric232
42.75

















PENDING TOC REVIEWCacti - DocumentationDOCUMENTATIONCacti343
33.25

















PENDING TOC REVIEWDocument, Review, and Implement Hyperledger AnonCreds ZKP Cryptographic PrimitivesDOCUMENTATIONCODINGAnonCreds, Ursa443
43.75

















PENDING TOC REVIEWHyperledger Onboarding Mentor/Mentee ProgramDOCUMENTATIONOnboarding Task Force455
54.75

















PENDING TOC REVIEWImprove Documentation for DRMan, Generate & Publish Github pages using mkdocsCODING DOCUMENTATION RESEARCHDID, Ursa, Aries342
33

















PENDING TOC REVIEWLearning Tokens @ Hyperledger BesuCODING DOCUMENTATION RESEARCHBesu, Latinoamerica Regional Chapter343
33.25

















PENDING TOC REVIEWTelecom Decentralized Identities Network (TDIDN)CODING RESEARCH DOCUMENTATIONTelecom SIG443
54

















...

ProjectDocumentationFile Type / Documentation ServiceNotesLocationWiki Page CategoriesRepos
FabricREADTHEDOCS.RST FILE and .MD FILESBuilt with  Sphinx  using a  theme  provided by  Read the Docs .https://hyperledger-fabric.readthedocs.io/en/latest/

Documentation & Resources

Repository

BesuREADTHEDOCS.MKDOC ( Material design) and .MD files

Hyperledger Besu and its documentation are licensed under Apache 2.0 license / This  Readthedocs.org  documentation is maintained with love by  Hyperledger Besu community.

Made with  Material for MkDocs 
https://besu.hyperledger.org/en/stable/

Documentation

Documentation on Hyperledger Besu can be found here: https://besu.hyperledger.org/

Repositories

https://github.com/hyperledger/besu/

https://github.com/hyperledger/besu-docs

SawtoothREADTHEDOCS

.RST FILE and .MD FILES


Sawtooth 1.2 documentation has not yet been completely converted to the new site’s format. You can find the documentation in sphinx-doc rst format at:https://sawtooth.hyperledger.org/docs/1.2/

Documentation

Repositories

IrohaREADTHEDOCS

.RST FILE and .MD FILES

Built with  Sphinx  using a  theme  provided by  Read the Docs .https://iroha.readthedocs.io/en/develop/

Documentation

Repositories

Indy READTHEDOCS.RST FILE and .MD FILES

Built with  Sphinx  using a  theme  provided by  Read the Docs .


Documentation Index

https://indy.readthedocs.io/en/latest/

Documentation

  • An index of Indy documentation can be found here.

  • The documentation of the nitty gritty of the underpinnings of the code is located in the “docs” folder of each repo.

  • Note: Indy Documentation is in the process of migrating to: indy.readthedocs.io

Repositories

AriesREADTHEDOCS.RST FILE and .MD FILESReadtheDocsRead me bring you to edx classes.

Documentation

For those new to the Aries community, Trust over IP and verifiable credentials, Linux Foundation provides two courses about the concepts and technology:

The latter is obviously more focused on Aries, with the first chapter providing a summary of the former course, and a series of hands on labs based on Aries implementations.

Repositories

Note that while the frameworks listed below are written in a specific, identified language, for the the business layer applications built on top of the frameworks can be implemented in any language.

https://github.com/hyperledger/aries

https://github.com/hyperledger/aries-rfcs

https://github.com/hyperledger/aries-cloudagent-python

https://github.com/hyperledger /aries-framework-dotnet

https://github.com/hyperledger/aries-framework-go

https://github.com/hyperledger / aries-framework-javascript

https://github.com/hyperledger/aries-vcx

https://github.com/hyperledger/aries-agent-test-harness

https://github.com/hyperledger/aries-mobile-test-harness

https://github.com/hyperledger/aries-mobile-agent-react-native

https://github.com/hyperledger/aries-mobile-agent-xamarin

All Aries repositories - https://github.com/hyperledger?utf8=%E2%9C%93&q=aries&type=&language=

BevelREADTHEDOCS.RST FILE and .MD FILES

© Copyright 2021, Hyperledger Bevel.Revision1e64937f.

Built with Sphinx using a theme provided by Read the Docs .

Image Modified

Image Modified

https://hyperledger-bevel.readthedocs.io/en/latest/introduction.html

Documentation

Repositories

CactusREADTHEDOCS

RST FILE and .MD FILES

markdown or reStructuredText files with the standard theme. 


Documentation

Repositories

https://github.com/hyperledger/cactus/blob/main/README.md

CaliperREADTHEDOCS /MKDocs

.RST FILE and .MD FILES

Note: also uses yml for Mk Docs 

powered by MkDocs and Material for MkDocs

=" Jekyll v3.9.2 " />

https://hyperledger.github.io/caliper/Documentation:  https://hyperledger.github.io/caliper/

Repositories

Source code: https://github.com/hyperledger/caliper

Documentation: https://hyperledger.github.io/caliper/

CelloREADTHEDOCS .RST FILE and .MD FILES
https://github.com/hyperledger/cello/blob/main/README.md

Documentation

Latest Docs

Repositories

Source Code: https://github.com/hyperledger/cello/

Documentation https://cello.readthedocs.io/en/latest/

FireflyJUSTThe Docs

https://just-the-docs.github.io/just-the-docs/ 


** Just the Docs is different from ReadtheDocs. Might be easier to stick to one Layout. 

This site uses  Just the Docs , a documentation theme for Jekyll.https://hyperledger.github.io/firefly/  https://hyperledger.github.io/firefly/

Repositories

Grid
  • Platform used unclear. 

** Could be JusttheDocs, but it's unclear which documentation platform or theme they are using. We know Jekyll is used but that could be any number of Documentation hosting services. 

<!-- Begin Jekyll SEO tag v2.8.0 →

Jekyll v3.8.6

The Hyperledger Grid documentation is available on the Grid website:  Hyperledger Grid Documentation

Repositories

Transact

docs.rs

http://github.com/hyperledger/transact 


** Uses a different service: Docs.rs, the documentation hosting service


docs.rs/transact/0.4.5

https://crates.io/crates/transact

https://docs.rs/about

Documentation

The Hyperledger Transact API documentation is available on crates.io (click "Documentation"):   https://crates.io/crates/transact

Repositories

Ursadocs.rs

https://github.com/hyperledger/ursa-docs


**Unclear: the documentation is on the github and on Docs.rs 


https://rust-lang.github.io/mdBook/

Documentation

Repositories

Solang



https://github.com/hyperledger/solang

https://github.com/hyperledger/homebrew-solang

Built with  Sphinx  using a  theme  provided by  Read the Docs .

https://Solang.readthedocs.io/en/latest/

How to run Solang on command line: https://Solang.readthedocs.io/en/latest/running.html

Blockchain-specific instructions for:

Solana: https://solang.readthedocs.io/en/latest/targets/solana.html

Substrate: https://solang.readthedocs.io/en/latest/targets/substrate.html

https://github.com/hyperledger/solang

https://github.com/hyperledger/homebrew-solang

...

  • The project basic documentation :This documentation must be in some media (such as text or video) that includes: how to install it, how to start it, how to use it (possibly with a tutorial using examples), and how to use it securely (e.g., what to do and what not to do) if that is an appropriate topic for the software. Users need documentation so that they can learn how to use the software. This documentation could be provided via the project website or repository, or even via hyperlink to some external information, so we do not specify exactly where this information 
  • The documentation of an external interface explains to an end-user or developer how to use it. This would include its application program interface (API) if the software has one. If it is a library, document the major classes/types and methods/functions that can be called. If it is a web application, define its URL interface (often its REST interface). If it is a command-line interface, document the parameters and options it supports. In many cases it's best if most of this documentation is automatically generated, so that this documentation stays synchronized with the software as it changes, but this isn't required. The project MAY use hypertext links to non-project material as documentation. Documentation MAY be automatically generated (where practical this is often the best way to do so). Documentation of a REST interface may be generated using Swagger/OpenAPI. Code interface documentation MAY be generated using tools such as JSDoc (JavaScript), ESDoc (JavaScript), pydoc (Python), devtools (R), pkgdown (R), and Doxygen (many). Merely having comments in implementation code is not sufficient to satisfy this criterion; there needs to be an easy way to see the information without reading through all the source code. If the project does not produce software, choose "not applicable" (N/A).

Other

David Boswell

Hart Montgomery   Arun S M   kamlesh nagware  – Thanks for your feedback and I see that you've each mentioned that having more resources at the graduated level would be helpful.  Here are some ideas to consider, although it would also be really helpful to hear from people involved in projects about what additional help they'd be interested in.

...