Symfony2 Timeline Bundle Fork & Integration
Overview
The author’s working fork of the Spy/TimelineBundle activity-timeline engine for Symfony2, consumed via VCS by the social-network application. Closely related to SnTimelineBundle; this is the upstream-tracking copy that was adapted and integrated rather than written from scratch.
Why It Exists
The social-network product needed a battle-tested timeline/wall engine. Forking the established Spy TimelineBundle allowed it to be customised, pinned and pulled in through Composer’s VCS repositories while keeping the option to track upstream fixes.
What We Built
A maintained fork of the stephpy/timeline-bundle (Spy\TimelineBundle) providing entity walls, activity spreads and an unread-notification system, with Doctrine ORM, MongoDB ODM and Redis drivers, timeline filters, Twig helpers and console commands for spreading/deploying timelines. Includes Travis CI configuration and atoum unit tests.
Technologies & Approach
PHP/Symfony2 bundle built on stephpy/timeline, integrated into the host application via a Composer VCS repository so the fork could be customised and version-pinned independently of Packagist.
Outcome / Impact
Served as the integrated timeline dependency for the social-network platform, showing comfort with evaluating, forking and integrating third-party open-source bundles into a production application.
Capabilities Demonstrated
- Evaluating and forking open-source Symfony bundles
- Integrating external libraries via Composer VCS repositories
- Operating activity-feed engines across multiple persistence backends
- Customising and version-pinning dependencies for a host product