Hidev Hiqdev Laravel Package

Product Decisions This Supports

• Standardizing open-source contributions: Adopting this package enables teams to align with HiQDev’s vendor configuration standards (e.g., BSD-3-Clause licensing, author profiles, and contact details), reducing friction in collaborative projects.
• Accelerating project scaffolding: Ideal for teams using HiDev to streamline boilerplate setup (e.g., goals.yml defaults, PHPCS configurations) and maintain consistency across repositories.
• Build vs. Buy Decision:
  • Buy if your team is already invested in the HiDev/HiQDev ecosystem and needs standardized vendor configurations.
  • Build if you require custom vendor configurations outside this framework (e.g., unique licensing, CI/CD integrations, or Laravel-specific tooling).
• Use Cases:
  • Open-source maintainers standardizing metadata across packages.
  • Internal teams adopting HiDev for PHP/Laravel projects to enforce coding conventions (e.g., PHPCS rules, license headers).
  • Organizations templating vendor configurations for multiple teams or products.

When to Consider This Package

• Adopt if:

  • Your team uses HiDev or plans to integrate it for PHP/Laravel automation.
  • You need a pre-configured vendor template (e.g., for open-source projects or internal tooling) with BSD-3-Clause licensing.
  • You prioritize consistent metadata (authors, contacts, GitHub links) across repositories.
  • Your workflow relies on PHPCS, Travis CI, or Scrutinizer integrations (this package bundles HiQDev’s configurations for these tools).
  • You are part of the HiQDev ecosystem and want to maintain alignment with their standards.

• Look elsewhere if:

  • You’re not using HiDev (this is HiDev-specific; alternatives like custom Composer scripts or Laravel-specific packages may fit better).
  • Your team requires non-BSD-3-Clause licenses (e.g., MIT, GPL) or custom CI/CD pipelines.
  • You need modern Laravel-specific tooling (e.g., Laravel Forge/Portfolio integrations, Laravel-specific scaffolding).
  • Maintenance is a concern: Last release in 2017 with no recent activity (evaluate risk vs. forkability).
  • You are not aligned with HiQDev’s conventions and prefer Laravel-native solutions.

How to Pitch It (Stakeholders)

For Executives: "This package standardizes how we package and distribute PHP/Laravel code, acting like a ‘brand kit’ for our repositories. It automates metadata (licenses, author details) and coding standards (PHPCS rules) using HiQDev’s proven configurations, saving development time and ensuring consistency across projects. It’s a low-risk solution (BSD-3-Clause license) with high ROI for teams already using HiDev or looking to adopt it. Think of it as a default profile for our team’s open-source or internal projects."

For Engineering: *"If we’re using HiDev for scaffolding or CI/CD, this plugin provides a ready-made vendor configuration to avoid reinventing the wheel. Key benefits include:

• One-click setup for HiQDev’s PHPCS, Travis, and Scrutinizer rules.
• Consistent licensing and author metadata across repositories (no manual composer.json edits).
• Template for custom configurations if we need to adapt it for our organization. Tradeoffs: Last updated in 2017, but the core YAML structure remains stable. We could fork it if needed. Recommended for teams already in the HiDev ecosystem or those looking to adopt it for standardization purposes."*

For Developers: *"This package helps maintain consistency in our project configurations by providing standardized settings for HiQDev packages. It’s particularly useful if:

• You’re working on open-source projects and want to keep metadata (authors, licenses) uniform.
• You’re using HiDev and want to leverage its built-in configurations for PHPCS, Travis CI, and Scrutinizer.
• You want to avoid manually configuring repetitive settings across multiple projects. Note: It’s not Laravel-specific, so it won’t replace Laravel’s native tools but can complement them for metadata and coding standards."*