Takeaways
- Problems are:
- Core teams don’t feel responsible for collaboration
- Core teams don’t have personnel with expertise to contribute back
- We don’t have a north star / principles / cross-project coordination strategy
- How do we coordinate priorities together?
- sync meetings between Core Teams?
- KPIs solve this in Web2 — what are a better KPI/OKR strategy for a DAO?
- How can we design an emergent product vision strategy
- How can we coordiante product priorities cooperatively?
Notes
- What is supposed to be unified? What remains autonomous in Core Teams?
- What is the benefit of unifying vs. benefit of autonomy?
- We’re lacking a set of system/protocol values
- Lacking coordination around infrastructure. What is our protocol-market fit?
- Why isn’t cross-team project contributing?
- engineering speciality issues - not everyone is an expert
- but there are common sets of features (e.g. key management, patches)
- not being communicated now (e.g. why is nobody using collaborative objects)
- multiple infrastructure teams - how do we create more cohesion between alt-clients and link?
- from link side: SLA was present to the mailing list/roadmap
- did alt-clients review? do they contribute to roadmap?
- core teams need support with engineering hiring
- can link and alt-clients sync?
- What core teams sync together?