2024-01-06
Basic Info
Time: 18:00 Every Friday PST (UTC-7)
Please download and import the following iCalendar (.ics) files to your calendar: https://zoom.us/meeting/tJwkc-2oqDgsE9RLmd0AwOltrBhSKjG3jEnp/ics?icsToken=98tyKuCgpz8uGtKWthCHRow-HY-gLPTwpnZdj_pvsBLhUwFETQ_iJMBKAZl1N4vaMeeting links:
Project Wiki Page https://lf-hyperledger.atlassian.net/wiki/display/cello/
In Process issues https://github.com/hyperledger/cello/projects/1#column-6892634
User dashboard API: ;
API-engine API docs: Cello API-Engine API
Agent API:
Add wikipage: https://github.com/hyperledger/cello/wiki/Debug-cello-by-container
Start service workflow is up to date: https://github.com/hyperledger/cello#quick-start
Attendee
Please input your name before the meeting
@Baohua Yang: yangbaohua@gmail.com
@DuPeng: dupeng@h3c.com
@Dixing Xu: dixingxu@gmail.com
@xie ruitao: rtxie@h3c.com
@qiang xu : xq-310@163.com
@prince Gao: prince.zxgao@gmail.com
@Yuanmao Zhu
@Tong Li (Deactivated): litong01@us.ibm.com
@hightall: hightallyht@gmail.com
@Luke Chan: jiahaochen1993@gmail.com
@Xichen Pan: xichen.pan@gmail.com
@panhaowen789: panhaowen789@gmail.com
@Xiao Ran : xiaor2@illinois.edu
@Yun Gu :nerokucn@gmail.com
Agenda&Minutes
PR this week
Release 1.0.0
QA:@feng yangis the QA manager, need to cut 1.0.0 from https://github.com/hyperledger/cello/tree/release-v1.0.0 branch.
Release plan 1.1.0 Q4 of 2023
chaincode (wait till channel can add org): @feng yang will draft a design spec first
UI behavior design of chaincode lifecycle: @Xichen Pan @feng yang
Chaincode frontend design: Chaincode Frontend Design: Approved.
@Xichen Pan lead the backend API discussion.
Backend API Design: @Yuanmao Zhu
FE Implementation: ETA 4 PW
@feng yang @Xichen Pan will lead. @Xiao Ran will continue to work on the OSS project in 2024
@Xichen Pan has done the dashboard page, split based on operations to let interns join the work. https://github.com/umijs/umi
BE Implementation: ETA 4 PW
@Yuanmao Zhu @Xichen Pan will lead. @Yun Gu @panhaowen789
@Yuanmao Zhu will have one API work as a sample, split the work based on APIs to let interns join the work.
package, install, approve, commit, invoke/query
Intern Students Updates (everyone should join hyperledger org at github first): https://yeasy.gitbook.io/blockchain_guide/.
Haowen Pan: Reading django and fabric. Improve docker compose with depends_on and healthcheck: https://docs.docker.com/compose/compose-file/05-services/#healthcheck; Improve docker-compose file.
Continue on the Test Chaincode v2 API Spec
On leave today (on trip)
Xiao Ran: Reading hlf docs first and run some local chaincode, reading django and build up a sample website. https://github.com/yeasy/docker-compose-files/tree/master/hyperledger_fabric
Reading FE code and almost understand the framework, will start to contribute code. Potentially start from Approve, Commit.
Confirm with @Yuanmao Zhu on the list channel API: Channel
Working on the commit FE part: Chaincode v2 API Spec: 6. Query an organization's approved chaincode definition on a channel.
Yun Gu: Run hlf testnet, reading django, watch youtube video. https://github.com/yeasy/docker-compose-files/tree/master/hyperledger_fabric. Need advisor from backend. @Xichen Pan will help, @Yuanmao Zhu as backup.
Potentially start from Approve, Commit.
work with @Xichen Pan on BE APIs.
@feng yang suggest revise the creating peer node API:
Only create one peer with the specified name
@Yuanmao Zhu will help fix the issue
@feng yang suggests:
When downloading channel config, remove the hint of downloading succeed
When creating channel, no need to edit orderer nodes
When updating the channel (add an org), why need to input the msp_id? Need to update the steps into docs.
Others
TODO: update HLF version from 2.2 LTS → 2.5 LTS
HLF 2.5.0 is released.
TODO: integrate hlf-operator into Cello as the k8s agent.
@feng yang mentioned that the release-0.9.0-h3c branch may contain some k8s APIs and code