Event Bundle Laravel Package

Product Decisions This Supports

• Legacy platform sustainment vs. migration: This bundle is a targeted fix for a custom eZ Publish 5 (eZ5) datatype (ezpublishevent). It supports the decision of whether to keep patching an aging eZ5 estate or fund a migration to a supported platform (Ibexa DXP / modern Symfony).
• Build vs. buy vs. vendor patch: Given zero stars and zero dependents, the realistic options are (a) adopt this vendor-maintained fix, (b) write a minimal in-house patch, or (c) contract xrow directly. A PM should frame this as a sourcing decision for a narrow, vendor-specific component—not a strategic platform choice.
• Feature roadmap for event publishing: If event content types and publishing workflows are on the roadmap, this bundle indicates the capability exists only as a custom eZ5 datatype. That constrains how events can be modeled, scheduled, and displayed, and should inform whether event functionality belongs in the current platform or the next one.
• Use cases: Content editors publishing events through the eZ5 content model; event listings/calendars on legacy sites; maintaining parity for existing xrow-based installations.
• Risk register input: No community validation (no stars, no dependents), vendor lock-in, and end-of-life platform risk are all decision-relevant signals that should be logged alongside any adoption.

When to Consider This Package

Consider it when:

• You are already running eZ Publish 5 and depend on xrow custom datatypes, specifically ezpublishevent.
• You need a narrow, tactical bug fix rather than new capability.
• You have an existing vendor relationship with xrow and can confirm support, licensing, and PHP/eZ5 version compatibility.
• The alternative—an in-house patch or a fork—would cost more than the vendor fix.

Look elsewhere when:

• You are building on Laravel or any modern PHP framework—this is a Symfony/eZ Publish bundle, not Laravel, and is not a fit.
• You are on eZ Platform / Ibexa DXP or planning to migrate; invest in the target platform instead.
• You need community support, active maintenance, or ecosystem validation—zero stars and zero dependents mean no signal of adoption and a high bus factor.
• Event publishing is a core, differentiating capability; a single-vendor legacy datatype is the wrong foundation for it.

How to Pitch It (Stakeholders)

For executives: This is a small, vendor-specific maintenance patch for a legacy eZ Publish 5 component, not a strategic dependency. Adoption signals are effectively zero—no stars, no dependent projects—so treat it as a tactical, time-boxed fix with a clear exit path, and avoid letting it anchor the event-publishing roadmap. If event capability matters commercially, budget for migration rather than accumulating legacy patches.

For engineering: Note that this is an eZ Publish 5 / Symfony bundle, not a Laravel package. Scope is narrow: it repairs the xrow ezpublishevent datatype. Before adoption, verify PHP and eZ5 version compatibility, license terms, and whether the vendor will support it going forward. Expect to own the code if the vendor relationship lapses.

Recommendation: Adopt only if you are already on eZ5 with xrow datatypes and need the fix now. Otherwise, do not introduce this dependency—fund the migration or implement a minimal in-house patch with a documented deprecation date.