You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 17 Next »

Overview

The main goal of the project is to create a documented Iroha (1.x) package for the Cactus project, which demonstrates the interoperability between Iroha and Cactus. The project also includes 3 documented examples of integration between Iroha and Cactus, and 2 documented examples of integration between Iroha and Fabric. The documentation will benefit the community so that people can understand this project.

Mentor and Mentee

MentorMentorMentee

Peter

PDT (UTC-7)

peter.somogyvari@accenture.com

Robin Klemens

CEST (UTC+2)

g.bazior@yodiss.pl

Han Xu

EST (UTC-5)

hongkexuhan@gmail.com

Communication channel: Telegram/ RocketChat/ Public Channels/ Emails/ Microsoft Teams

Project repo: 

https://github.com/hyperledger/cactus

https://github.com/hyperledger/iroha

Project Plan

ScheduleTaskDeliverable

Week 1 - Week 3

Jun 1 - Jun 18

Jun 18: 1st Quarter Evaluation

  • Install Ubuntu 20.04 LTS and set up environment.
  • Build Cactus.
  • Build Iroha.
  • Understand existing source code.
  • Start the Iroha and Cactus integration.
  • Project Plan.
  • Skeleton for Iroha and Cactus integration.

Week 3 - Week 6

Jun 19 - July 9

July 9: 2nd Quarter Evaluation

  • Implement the Iroha and Cactus integration.
  • Write tests for the Iroha and Cactus integration.
  • Write comments.
  • Near-complete package for Iroha and Cactus integration.
  • Technical documentation for the package.

Week 6 - Week 10

July 10 - July 30

July 30: 3rd Quarter Evaluation

  • (2 and more) Examples of Iroha and Cactus integration.
  • Examples of Iroha and Fabric integration.
  • Write tests for Iroha and Cactus integration.
  • Write tests for Iroha and Fabric integration.
  • Write comments.
  • Completed package for Iroha and Cactus integration.
  • 3 examples of Iroha and Cactus integration.
  • 2 examples of Iroha and Fabric integration.

Week 10

July 31 - Aug 10

Aug 20-31: Final Evaluation

  • Wrap up comments.
  • Final report of the project.
  • Final presentation of the project
  • Code for unit tests and integration tests. *
  • Technical documentation for the whole project.
  • Final report.
  • Final presentation.

* Will wrap up all codes-relevant stuff by Aug 5.

Process

  • Communication and updates:
    • Telegram/ RocketChat/ Public Channels/ Emails/ Microsoft Teams are used as tools.
    • Weekly check-in meetings between the mentors and mentee.
  • Quarterly review according to Summer Full-Time Mentee Schedule.
  • No labels