2025-02-15
Basic Info
Time: 18:00 Every Friday PST (UTC-7)
Meeting 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
@Xichen Pan: xichen.pan@gmail.com
@feng yang : fengyang.09186@h3c.com
@panhaowen789: panhaowen789@gmail.com
@Xiao Ran : xiaor2@illinois.edu
@Yun Gu :nerokucn@gmail.com
@Haibo Yang : haiboyang@uscb.edu
@haoyu li : haoyuli1697@gmail.com
Agenda&Minutes
PR this week
Release plan 1.1.0 GA Q1 of 2025
Channel features are done
Next Release
chaincode (wait till channel can add org):
Backend API Design: Chaincode v2 API Spec
FE Implementation: Code is done. Issue: connect to BE.
@feng yang @Xichen Pan will lead.
@Xichen Pan has done the dashboard page, split based on operations to let interns join the work. https://github.com/umijs/umi
package, install, approve, commit, invoke/query
@Xichen Pan and @Haibo Yang will work on this component together (BE and FE)
@feng yang : https://github.com/hyperledger/cello/issues/602, need to add the design spec in sep. On leave today.
Intern plan: Project Plan - Decentralized Blockchain Network Operation Dashboard
@Haibo Yang:
Proposed to let users upload code base to do package.
Anchor peer is a type of updating channel config. @Haibo Yang is working on this PR.
PR for review: https://github.com/hyperledger-cello/cello/pull/666
@haoyu li 2nd year master of UIUC, still reading the docs.
Everyone please subscribe the calendar at LFX Meetings . There will be no email notification for each meeting.
Need to import icav URL: https://webcal.prod.itx.linuxfoundation.org/lfx/a092M00001IV4ETQA1
Suggest to change meetings to bi-weekly.
Others
@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.