Files
cal-diy-oidc/agents/rules/culture-accountability.md
T
Benny Joo ab21c7f805 refactor: Cal.diy (#28903)
* feat: Cal.diy — community-driven MIT-licensed fork of Cal.com

This squashed commit contains all Cal.diy changes applied on top of calcom/cal.com main:

- Rebrand Cal.com to Cal.diy across the entire codebase
- Remove Enterprise Edition (EE) features, license checks, and AGPL restrictions
- Switch license from AGPL-3.0 to MIT
- Remove docs/ directory (migrated to Nextra at cal.diy)
- Remove dead code: org tests, EE tips, platform nav, premium username, SAML/SSO, etc.
- Clean up .env.example for self-hosted Cal.diy
- Update Docker image references to calcom/cal.diy
- Update README, CONTRIBUTING.md, and issue templates for Cal.diy community fork
- Add PR welcome bot for Cal.diy contributors
- Fix API v2 breaking changes oasdiff ignore entries
- Replace Blacksmith CI runners with default GitHub Actions

3893 files changed, 20789 insertions(+), 411020 deletions(-)

Co-Authored-By: benny@cal.com <sldisek783@gmail.com>

* refactor: remove org-specific /organizations/:orgId endpoints from API v2 atoms controllers (#1701)

Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>

* fix: revert Cal.diy Inc to Cal.com, Inc. in license files, copyright notices, and package metadata (#1702)

Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>

* rip out org related comments in api v2

---------

Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
2026-04-15 09:52:36 -03:00

1.8 KiB

title, impact, impactDescription, tags
title impact impactDescription tags
Hold Each Other Accountable for Quality MEDIUM Builds collective ownership and prevents technical debt culture, accountability, quality, teamwork

Hold Each Other Accountable for Quality

Impact: MEDIUM

We hold each other accountable for quality. Cutting corners might feel faster in the moment, but it creates problems that slow everyone down later. When you see a teammate about to merge a PR with obvious issues, speak up.

This isn't about being difficult or slowing people down. It's about collective ownership of our codebase and our reputation. Every shortcut one person takes becomes everyone's problem. Every corner cut today means more debugging sessions, more hotfixes, and more frustrated customers tomorrow.

Make it normal to challenge poor decisions, respectfully:

// When someone says:
"Let's just hard-code this for now"

// The expected response:
"What would it take to do it the proper way the first time?"
// When someone wants to commit untested code:
"Can we add tests for this before merging? I can help if needed."
// When someone suggests copy-paste instead of abstraction:
"This looks like it could be a shared utility. Should we extract it?"

We're building something that needs to almost never fail. That level of reliability doesn't happen by accident. It happens when every engineer feels responsible for quality - not just their own code but the entire system. We succeed as a team or we fail as a team.

Key behaviors:

  • Push back when you see shortcuts being taken
  • Offer to help when suggesting improvements
  • Accept feedback gracefully when others challenge your decisions
  • Focus on the code, not the person
  • Remember that quality standards protect everyone

Reference: Cal.diy Engineering Blog