Intersect Committees
Intersect Knowledge BaseIntersect Website
Intersect - Technical Steering Committee
Intersect - Technical Steering Committee
  • ABOUT
    • Technical Steering Committee (TSC)
    • Committee members
    • Technical Working Groups
    • Security Council
    • How to Join or Contact Us?
    • 2025 TSC Meeting Minutes
      • 2025 TSC Decision Log
      • 30th April 25
      • 23rd April 25
      • 17th April 25
      • 2nd April 25
      • 25th Mar 25
      • 19th Mar 25
      • 12th March 25
      • 26th Feb 25
      • 19th Feb 25
      • 12th Feb 25
      • 5th Feb 25
      • 22nd Jan 25
      • 15th Jan 25
      • 8th Jan 25
    • 2024 TSC Meeting Minutes
      • TSC - Decisions Log
      • 4th Dec 24
      • 27th Nov 24
      • 20th Nov 24
      • 13th Nov 24
      • 6th Nov 24
      • 30th Oct 24
      • 23rd October
      • 2nd Oct 24
      • 25th Sept 24
      • 28th August 24
      • 31st July 24
      • 17th July
      • 19th June
      • 5th June
      • 22 May 24
      • 8 May 2024
      • 24 April 24
      • 10 April 24
      • 27 Mar 24
    • Page
  • Technical Roadmap
    • How to Participate in Shaping the Technical Roadmap
    • Project Cards Explained
      • Software Readiness Level
    • Potential Roadmap Projects
    • Maintenance Items
Powered by GitBook
On this page
  1. ABOUT
  2. 2024 TSC Meeting Minutes

25th Sept 24

Previous2nd Oct 24Next28th August 24

Last updated 6 months ago

  1. TSC Elections

  • Item: There are six nominees for five open TSC positions.

  • Decision: The group agreed need for TSC candidates based with senior expertise in Cardano’s design and contributions. Candidates will be approached by TSC to discuss experience and will be asked to provide additional evidence where necessary to support their application.

  • Action: Kevin Hammond: Work with Karen Wickham (Intersect) to distribute the applications for committee review.

Committee: Each member will independently review the applications. The committee will provide a short-list of those candidates who meet the criteria.

2. 2025 Budget – Top-Down Approach

  • Item: Discussion of the 2025 budget and potential for a 35% increase in developer capacityl.

  • Decision: A 35% total budget uplift will be requested to accommodate the expected increase in capacity, and to ensure that as many work items as possible can be accommodated in 2025.

  • Action: Lewis Mayne: Capture in the minutes that the 35% uplift is an anticipation of total growth, replacing the previous 20% proposed uplift. Ensure this is clearly communicated.

  • Action: Ricky Rand and Neil Davies: Continue monitoring potential developer growth and finalize details on the expected numbers within two weeks.

I have spoken to . We should update the budget request to reflect the 35% uplift.

3. Maintenance Activities

  • Item: Discussion on allocating budget for maintenance-related activities, estimated to require around 40% of the overall budget.

  • Decision: Reserve approximately 40% of the budget for maintenance, based on industry norms (40-60% of effort). Maintain flexibility to reallocate budget based on need.

  • Action: Lewis Mayne: Continue to track the budget decisions and ensure maintenance-related costs are well documented.

  • Action: Kevin Hammond: Facilitate discussions on whether additional maintenance items should be included, and ensure transparency in reporting maintenance impacts on new development.

Update: Additional items added, discussion happening prior to the TSC meeting.

4. Updated Terms of Reference for TSC

  • Item: Review of the updated terms of reference for the Technical Steering Committee.

  • Decision: The terms of reference will be circulated for feedback, and members will have one week to comment.

  • Action: Kevin Hammond: Circulate the updated terms of reference on the channel for feedback.

  • Action: Committee: Review the ToR and provide comments within the one-week deadline.

Update: Circulated and updated the ToR.

5. Sessions for Detailed Discussion on Work Items

  • Item: Organizing structured sessions to discuss key work items such as anti-grinding, Mithril, and Peras.

  • Decision: Each session will have a champion and technical experts, with structured discussions to ensure clarity on the technical benefits and interactions between work items.

  • Action: Nicholas Clarke: Develop a formal structure for the sessions, ensuring each has the right technical expertise.

  • Action: Kevin Hammond and Neil Davies: Organize a session with Duncan Coutts to discuss interactions between the work items before diving into the facilitated sessions.

6. Search for Co-Chair of Core Infrastructure Networking Group

  • Item: The need to find a new co-chair for the Core Infrastructure Networking Group, as Leonard Hegarty (IOE) is stepping down.

  • Decision: The role will be opened to the wider community. A description of the role will be provided for clarity.

  • Action: Hwang Huongket: Draft and share a description of the co-chair role in the TSC channel to facilitate nominations. Existing infrastructure group members should be encouraged to apply, opening a member vacancy if they are selected.

Update: Initial discussion to take place on Friday. Check with about formal structure.

@Lawrence
@nclarke