6th June 25
Meeting Recording:
https://studio.youtube.com/video/nvYKwgzdfP0/edit
Attendance:
Matt
Davis
Intersect - Tech Ops Lead
N
Adam
Dean
TSC Vice Chair
Y
Markus
Gufler
TSC Member (Cardano Foundation)
Y
Kevin
Hammond
TSC Chair
Y
Benjamin
Hart
TSC Member (MLabs)
Y
Alexander
Moser
TSC Member (Cardano Foundation)
Y
Sebastian
Nagel
TSC Member (IOG)
Y
Ricky
Rand IOHK
IOE General Manager - Observer
N
Duncan
Soutar
TSC Secretary
N
Christian
Taylor
Intersect - Opensource Head
N
Pedro
Lucas
Observer
N
Minutes:
1. Apologies
Apologies: Johnny Kelly, Nicholas Biri, Neil Davies
2. Actions from last week
KES Agent: Action Adam & Dunan C on write up of KES Agent Migration Memory Limit Report: Awaiting final information ahead of publication
Action: This topic to be raised in SPO call
3. L Parameter
L Parameter: Proposers met with Parameter committee last week. Only query was on Civil Protection. May have an economic impact on SPOs, which may need to be addressed. CIP50 has been revived and is place for community discussion. RR: Expects that this does fall under the scope of IOE’s work to implement change if it is agreed. Noted that this will need a hard/soft fork. AD: No quorum, therefore no quorum therefore make sure comms is opinion neutral. Is there a plan for how community sentiment can be judged in the future beyond those that comment on the CIP. Important due to the economic and monitory impact, this needs a process to ensure that this has wide community support. KH: May be good to put this through as an info-action AD: Need to set new precedent on how major changes are decided to be implemented KH: Either put forward individual changes or when a hardfork is being enacted then the functionality within that HF needs to be collated.
Action: Duncan to put out comms on this CIP. Action: Kevin & Seb to go to SPO call to raise this issue Action: Christian to share ecosystem diagram on what is 'core'
4. Core Budget Proposals Review
Review of the projects that were approved as part of the budget process KH: Not clear if core or not in many instance. Not clear if tooling falls under TSC or not.
KH: Listed examples of things he did and did not believe were core AD: Why approach this in this way? To what end? DS: Agreed with Adam, would prefer to focus on TSC role rather that definition of core CT: Core was defined by the Repos AD: Challenges the concept that anything not Haskell or DS: Anything that needs a HardFork needs to be within TSC AD: Discussion on Star Steam CT: Use ecosystem Diagram to determine what is “Core” Some tooling is important for supporting essential core development, should this fall under the TSC? OSC still working out how payments are made for tooling OSC will support building things on top of core. Lucid evolution could also apply to tooling.
5. TSC Remit
DS: Shared a RACI template to help shape and formalise the TSC's role DS: Requested TSC members input their views of TSC's role across several key areas KH: Explained Key Steps in Hard Fork Coordination
Action: All TSC members to input their views on TSC's role
Last updated