Skip to content

Instantly share code, notes, and snippets.

@rynowak
Last active April 13, 2024 00:33
Show Gist options
  • Save rynowak/32988b6f4574c0dbb0e5b0086fcf1b18 to your computer and use it in GitHub Desktop.
Save rynowak/32988b6f4574c0dbb0e5b0086fcf1b18 to your computer and use it in GitHub Desktop.
Radius Maintainer's Day Notes

Radius Maintainers' Day 2024

Agenda

10:00: welcome and coffee
10:15->11:00: First session: Governance and CNCF process
11:00->11: 45: Second session: Radius OSS project retro + direction setting 
11:45->12:00: Break
12:00->12:30: Third session: Technical Strategy and Roadmap + Dapr
12:30 ->13:30: OFF CAMPUS LUNCH
13:30->14:15: Fourth Session: Defining Production Readiness pt1
14:15->14:30: Break
14:30->15:15: Fifth session: Defining Production Readiness pt2 or Roadmap Review
15:15->16:00 Wrap up (overflow for other topics)

Sessions

Welcome

  • This is a zone of trust and honesty. We all want best for the project.
  • As maintainers we have the most input.
  • I'm trusting all of you. We'll be having high-clarity + low-certainty discussions.
  • Chances for collaboration with peers are rare, so recognize and embrace the opportunity.

Icebreaker

  • Tell us about a wierd or funny experience at work.
  • Proudest technical achievement.
  • An interesting hobby, skill or activity, past or present.

Governance and CNCF Process

Open Source vs Open Governance

CNCF process

Ryan's involvement:

  • TAG App Delivery
  • Tag App Developer
  • Partnerships with small companies (Syntasso, Threeport)

Notes:

  • Revisiting current maintainers/approvers?
    • What do the roles mean?
      • Member -> Contributing
      • Approver -> Judgement
      • Maintainer -> Leading
    • Action items:
      • Define the technical areas of the product
      • Align maintainers to technical areas and evaluate
      • Future: split Radius repo when the timing is right
      • Provide clear feedback to team members on how to become approvers
        • Sylvain to drive
      • No regrets on making some of more active community members into project members
        • Reshma to drive engagement plan

Radius Project Retro

  • List categories (community support, code reviews, eng systems, design process, code quality, testing coverage/practices)
  • Give a letter grade (can't be all "A"s). Compare to other teams and other projects.
    • A = world class
    • B = excellent
    • C = ok
    • D = below average
    • F = awful
  • Everyone explain your grade (no interrupting, need a time cop)
    • Come up with a consensus range
  • Where do you want to be? Let's assume we can only go up 3 letter grades total for the project.
    • What would it take to get there?

Radius Technical Roadmap

  • Radius adopts Dapr
  • Radius can move outside the cluster, can work with multiple clusters
  • Simplified RP contract + Reconciler
  • Recipe all the things!
  • Complete the app model
  • DE is replatted on Dapr
  • DE is multi-format
  • DE has stacks

Notes:

  • As an exercise, let's scope out the additional feature we need like stacks and ev2 integration.

Radius Production Readiness

Categories of investment:

  • Completeness: User-facing functionality and capabilities of Radius for application and resource management.
  • Operations & Security: Functionality for the production operations and security of the Radius control-plane itself.
  • Fundamentals: Internal team processes to verify the quality of Radius towards pillars like reliability and performance.
  • Guidance: User-facing content to assist organizations in adopting Radius in production.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment