Recording:
...
Cactus Maintainers 200810.mp4
Date
Attendees
...
- Make a decision about the meeting agendas and go through PRs.
Discussion items
| Time | Item | Who | Notes |
|---|
| Introductions | Everyone | - Note: No one wanted to be introduced.
|
| 15 min | Pull-request about Karma+Webpack based browser tests (PR#245) | Peter | - Abstract: Peter prepared a plan of browser tests of the common package.
- Discussion point: Questions about Cactus's role happened. Cactus is a server-side application, not client-side.
|
30 | 20 min | Manual consortium plugin (PR#242) | Peter | - Abstract: Peter prepared a plan of manual consortium plugin
- Discussion point: Who is the consortium members of consortium plugin?
- Note: Shingo
|
Fujimoto- proposed the following material (The conclusion is discussed with this topic)
|
10 | 20 min | Federation on blockchain integrated service related to the topic (PR#242) | Shingo | - Abstract: Shingo prepared a plan of federation of blockchain integrated service.
| View file |
|---|
| name | Cactus_FederationDiscussion_Shingo20200810.pdf |
|---|
| height | 250 |
|---|
|
- Discussion point: The function (registry for trustworthy validators) is almost similar to consortium plugin
|
as Somogyvari- proposed. The difference is where is the trust point. The registry should not be admin's one.
- Consensus: The discussion continues to the next week.
|
| 5 min | Academic paper: current contributors, initial ideas | Many | - Consensus: We should design the Cactus architecture at first. After this, we will summarize the output to academic paper.
|
| PR Discussion | Peter/Many | - Note: Meeting time is over then this is postponed to the next week.
|
Action items