2020-10-13 Meeting notes

Date

13 Oct 2020

1. Release planning towards v1.0

Shingo proposed a refinement of the release planning, including a purpose of each point release
Details of the proposal are included in the Agenda page https://lf-hyperledger.atlassian.net/wiki/display/cactus/2020-10-13+Cactus+Contributors+Meeting+Agenda
Point in time proposal below; maintainers aligned on high-level objectives and will begin maintaining on the Github milestones https://github.com/hyperledger/cactus/milestones?direction=asc&sort=title&state=open
Shingo raised about how to best setup containers
Peter highlighted about how to avoid conflicts on filesystem and ports. The examples are in https://github.com/hyperledger/cactus/tree/master/tools/docker and include information about expected behavior
As we build out more examples this can eventually become a type of template for future contributors

2. Academic paper discussion

Rafael has proposed some considerations but will be discussed with him live during the session on the Western Contributors call on Thursday
Rather than proposing a security model, Hart would like the community to provide inputs on potential security solutions
For those on Eastern time zones they could also connect with Raphael during the fortnightly Eastern Contributors call
There could be a white paper after the fact that documents the developer level priorities from the academic paper

3. Discussion on how we can more aggressively work towards merging codebases and working on the same code.

This was covered in the first topic. Maintainers will be working on an aligned roadmap with detailed issues per point release

4. Ad-hoc items

Clive raised that he linked a presentation to PR #253, which includes information about how to secure plugins, which beyond the consideration for PR 253 could have a direct application onto the security aspect of the academic paper

5. Pull request loop

281 - skipped for today
298 - discussed Peter's feedback, open question on how tradeID works. Takuma will provide sample code on how this will work
308 - very large draft PR submitted for review, initial question from Shingo on structure. Moving discussion to mailing list / PR