🎯 Executive Summary

Overall health:
Traffic light: 🟡

This week's headline:
Multiple critical releases (Boukili v3, ONFR live‑feed, supervision solution) were finalized or approved, while several high‑impact risks (screen‑reader compatibility, CRTC report clarity, JW Player billing, OTT test completion, Boukili migration blockers) require immediate attention.

Wins 🏆

Version 3 of Boukili finalized; testing to start.
“Set‑focus” trigger delivered in Storyline (on standby pending compatibility).
ONFR live‑feed implementation using Haywire feed selected; first three episodes prepared for Thursday release.
Supervision solution (cron checks, status URLs, notifications) approved; rollout planned for ONFR → Idéllo → TFO.
JWP feed architecture clarified; 24/7 feed unchanged, test feed managed manually via Wirecast.
Boukili to run on a dedicated VM long‑term; API integration postponed.
Weekly ONFR live on OTT scheduled to start 17 Sept; engaged‑views adopted as primary YouTube metric.
Decision to keep WordPress on current site with WP Engine hosting.
Established ZIP‑to‑Idéllo publishing process (ticket → ZIP → hand‑off to Hélène).
CTO approved exploratory collaboration with Lunii.
Code freeze applied after issue fixes; phase‑2 work isolated on separate branch.
Second Corus feed test configured for JW Player without altering existing feed.

Risks ⚠️

Storyline “set‑focus” trigger compatibility with JAWS screen reader not verified.
CRTC report requirements (retroactivity, location, prior response inclusion) remain unclear.
Variable ONFR episode lengths may cause JWP recording mismatches; manual intervention needed.
Subtitles for deaf‑hearing test file not displaying; cause uncertain.
Unclear JW Player ingest‑point behavior and potential fees for second feed (risk of surfacturation).
No staging server for supervision checks; tests rely on simulation.
Access to Boukili PROD database pending migration; field‑mapping blocked.
OTT test results (device behavior, Apple TV zoom) incomplete; sign‑off pending.
Podcast automation missing Jira API connection.
Geo‑blocking of TFO and Idéllo cannot be removed without production release (legal risk).
Compliance risk from reliance on US‑based vendors (JWP, WP Engine, Algolia).
Boukili Firebase‑to‑AWS migration faces data‑loss risk, Salesforce regression, and insufficient testing time.
QA capacity bottleneck (single QA resource for four sites).
Upcoming absences of key staff (Ajar, Jean‑Claude, Joël) may slow progress.
OTT live‑event deadline (Sept 14) at risk; may require weekend release.

Team 👥

Team health

Overall morale: Not assessed.

Coaching / Recognition

No explicit coaching or recognition items recorded.

Projects 📁

Project	Status	Next Milestone	Blocker
Boukili migration (Firebase → AWS)	Production release cancelled; code freeze applied	Validate issues & set new release date	PROD DB access, data‑loss risk, Salesforce regression
ONFR live‑feed & OTT	Haywire feed selected; episodes prepared	OTT live on 17 Sept; finalize subtitle & JWP ingest verification	JWP billing clarity, subtitle display issue
Supervision solution (cron checks)	Approved, rollout plan defined	Deploy on ONFR, then Idéllo & TFO	No staging server for tests
JWP feed management	24/7 feed unchanged; test feed manual	Confirm ingest‑point behavior & billing	Unclear fee structure
WordPress site hosting	Decision to stay on WP Engine	Ongoing maintenance	–
Idéllo ZIP publishing workflow	Process defined, start after 12 Oct	Create first ZIP ticket	–
Lunii collaboration exploration	Approved for presentation to CEO	Schedule exploratory discussion	–
Mogador synchronization	Dedicated meeting scheduled 16 Sept	Decide on removal or evolution	Complexity, lack of source‑of‑truth
OTT delivery (live event)	At risk, testing ongoing	Final OTT test sign‑off	Incomplete device testing, deadline pressure
Contentful version control & other technical subjects for Boukili	Pending decision which to include in next build	Decision needed	–

Vendors 🤝

JW Player: Billing model for ingest points unclear; risk of surfacturation.
WP Engine: Hosting decision retained; no immediate issues.
Algolia: Compliance review ongoing due to US‑based vendor policy.
The Mind / IBO: Potential assistance for Boukili migration being evaluated (cost, feasibility).

Decisions Made

Keep Storyline “set‑focus” trigger on standby until screen‑reader compatibility is confirmed.
Use Haywire feed for ONFR tests; defer second Chorus URL.
Prepare first three ONFR episodes on Wednesday for Thursday publishing.
Deploy supervision checks first on ONFR, then Idéllo and TFO.
Maintain JWP 24/7 feed unchanged; manage test feed manually via Wirecast.
Keep Boukili on a dedicated VM; postpone API integration.
Use engaged‑views as primary YouTube performance metric.
Remain on WordPress with WP Engine hosting.
Implement ZIP‑to‑Idéllo workflow (ticket → ZIP → Hélène) starting 12 Oct.
Approve presentation of Lunii collaboration to CEO.
Cancel Monday production release for Boukili; apply code freeze after issue fixes.
Use second Corus feed for JW Player test without altering existing feed.

Decisions Needed

Clarify CRTC report requirements (retroactivity, location, prior response inclusion).
Confirm JW Player ingest‑point behavior, billing model, and any fees for the second feed.
Determine if a second Chorus URL will ever be required and justify cost.
Approve Jira form design for automated podcast/balado requests (subject to feasibility).
Validate OTT test outcomes (device compatibility, Apple TV zoom) for final sign‑off.
Confirm data availability and tracking format for ONFR live OTT event in JWP/CDN.
Decide which of the four technical subjects (retry of last‑activity tracking, Firebase auth lockout, update‑message migration, Contentful version control) will be included in the next Boukili build.
Final determination on Mogador synchronization approach and possible project removal.
Approval of additional/temporary QA resources to mitigate capacity bottleneck.

Top Priorities Next Week

Clarify CRTC report requirements with Pierre‑Olivier and send follow‑up email.
Verify JW Player ingest‑point behavior and billing; request deletion of unused ingest points.
Complete OTT device testing (including Apple TV zoom) and obtain sign‑off.
Obtain access to Boukili PROD database and proceed with field‑mapping.
Implement and test subtitle display for ONFR test file.
Deploy supervision cron checks on ONFR and validate workflow.

CTO Development

Leadership:

Approved strategic decisions on Storyline feature standby, ONFR feed strategy, supervision rollout, and vendor compliance reviews.
Organized dedicated meetings for complex topics (Mogador sync, Lunii collaboration).

Technology:

Oversaw code freeze after issue resolution and isolation of phase‑2 work.
Directed cancellation of Boukili production release pending risk clarification.

Business:

Selected engaged‑views as primary metric for YouTube reporting.
Maintained WordPress hosting decision aligning with business continuity.

Finance:

Communication:

Initiated CRTC clarification email.
Presented Lunii collaboration proposal to CEO.

One thing I did this week that made me more like a CTO:
Approved and communicated high‑level strategic decisions (e.g., supervision solution rollout, vendor compliance reviews) that shape multiple product lines.

One thing I did this week that kept me acting like an individual contributor:
Wrote the JWP stop‑recording script for the 28‑minute episode limit.

8.1 KiB Raw Blame History Unescape Escape