Technical Design Committee Meeting Notes: January 22

(Apologies in the delay of publishing these notes)

The Technical Design Committee (TDC) helps guide the overall technical direction of ROOST's projects (read more about ROOST project governance). The inaugural TDC members bring deep expertise across large-scale systems, complex child safety issues, information security, open source development, and a variety of safety issues ranging from violent extremism to fraud and scams.

Notes

• Welcome to the TDC and setting expectations

  • Public meetings and notes going forward

  • Future notes will be posted on Github

• Roadmap feedback: https://github.com/roostorg/community/blob/main/roadmap.md

  • Update on Coop
  • 3 adopters of Osprey so far, have there been any issues or feedback from them?
    • Druid is an issue - replacing with Clickhouse may be better for 3rd party maintainers
    • Kafka is not preferred by a potential adopter, right now Osprey needs Kafka to work

• We will need to be opinionated or overengineer things to be overly flexible, which is in itself a problem

  • Important and common in open source projects! Be clear in first documentation that we chose things for a reason, that can go a long way in making people feel more included. As we get more collaborators we will solve those issues as people make changes themselves
  • Our goal is at minimum, Apache 2 software license
  • Before starting a new project, it’s important to define our principles. If our goal is adoption and companies don’t have the resources to configure things then focus our efforts on out-of-box adoption and not building it for customization.
    OR we can focus on providing foundational blocks that require heavy customization.
  • Vinay: We must build for at least 1M events per day, otherwise we are competing with super simple tools like a Google Sheet.

• How can ROOST make its projects easier to consume and explore?

  • Hosted demo? Single command? Right now we are a bit complicated to check out and explore

• Ongoing meeting cadence