Symfony2 Coding Standard Laravel Package

Product Decisions This Supports

• Code Quality & Consistency: Enables alignment with Symfony2 coding standards, reducing onboarding friction for teams familiar with Symfony.
• Legacy System Modernization: Useful for maintaining or migrating older Symfony2-based applications where adherence to historical standards is critical.
• Developer Tooling Roadmap: Justifies investment in static analysis tools (e.g., PHP_CodeSniffer) to enforce best practices, even if this specific package is deprecated.
• Build vs. Buy: Avoids reinventing a coding standard wheel; leverages existing, battle-tested rules (though deprecated, the underlying principles remain relevant).
• Use Cases:
  • Onboarding new developers to legacy Symfony2 projects.
  • Auditing existing codebases for compliance with historical standards.
  • Integrating with CI/CD pipelines to gate code merges based on style/quality.

When to Consider This Package

• Adopt if:

  • Your team maintains a Symfony2 codebase and needs to enforce its native coding standards.
  • You’re working with legacy systems where Symfony2 is entrenched, and migration to newer versions isn’t imminent.
  • You lack the resources to custom-build or maintain a coding standard from scratch.
  • Your team prioritizes consistency over cutting-edge tooling (e.g., Symfony 6+ standards).

• Look elsewhere if:

  • You’re using Symfony 3+ or later (modern alternatives like symfony/flex or php-cs-fixer with Symfony bundles exist).
  • Your project is greenfield or PHP framework-agnostic (consider PHP_CodeSniffer with generic rules like PSR-12).
  • You need active maintenance or modern features (e.g., autofix capabilities, Symfony 5/6+ support).
  • Your team prefers customizable or framework-agnostic standards (e.g., rector, pint).

How to Pitch It (Stakeholders)

For Executives: "This deprecated but historically relevant package lets us enforce Symfony2’s coding standards—critical for maintaining legacy systems with minimal developer friction. While not actively maintained, it’s a lightweight, zero-cost way to ensure consistency in our existing codebase, reducing technical debt during onboarding or audits. We’d pair it with modern tooling (e.g., PHP_CodeSniffer) to future-proof our workflows."

For Engineering: *"The m6web/symfony2-coding-standard package provides Symfony2’s official coding rules via PHP_CodeSniffer, which we can integrate into our CI pipeline. It’s a drop-in solution for legacy projects, but we should:

1. Audit its rules against our needs (some may be outdated).
2. Combine it with php-cs-fixer for autofix capabilities.
3. Plan a migration path to Symfony 5/6+ standards post-deprecation. This avoids reinventing the wheel while keeping our legacy codebase aligned."*