193 lines
18 KiB
Markdown
193 lines
18 KiB
Markdown
# Weekly Evidence Pack
|
||
|
||
---
|
||
|
||
**# Major Developments**
|
||
- Version 3 of Boukili is finalized; testing is about to start.
|
||
- The “set‑focus” trigger feature in Storyline is ready but its compatibility with JAWS screen readers is still unknown; the feature will remain on standby.
|
||
- ONFR live‑feed implementation: Haywire feed will be used for tests; a second Chorus URL is not being pursued pending cost clarification.
|
||
- A supervision solution for background jobs (cron checks with URL health, notifications on critical state changes) has been approved for phased rollout, starting with ONFR.
|
||
- OTT search‑result ranking changes have been made; final sign‑off is pending completion of device testing (including Apple TV zoom).
|
||
- Boukili will run on a dedicated VM long‑term; the planned API integration is postponed.
|
||
|
||
**# Risks / Blockers**
|
||
- Unclear compatibility of Storyline “set‑focus” with JAWS may delay its future product inclusion.
|
||
- CRTC report request lacks clarity on retroactivity, required content, and publication location; the exact response already sent is not known to all stakeholders.
|
||
- Variable episode lengths (30 min first, 20‑28 min thereafter) risk incorrect automatic stop of JWP recording; manual intervention may be required.
|
||
- Subtitles for test videos are not displaying, likely due to missing collection association.
|
||
- JWP ingest point behavior, possible fees for the secondary feed, and overall documentation are not confirmed.
|
||
- No identified staging server for supervision‑solution testing; reliance on simulation could hide production issues.
|
||
- Access to Boukili’s production database and Contentful API configuration remain unresolved, blocking full integration.
|
||
- Podcast automation still depends on connecting to the Jira API.
|
||
|
||
**# Decisions Made**
|
||
- Do not retro‑fit existing work to immediately include the Storyline feature; keep it on standby until screen‑reader compatibility is verified.
|
||
- Use the Haywire feed for ONFR testing; defer a second Chorus URL.
|
||
- Deploy the job‑supervision checks first on ONFR, then later on Idéllo and TFO after successful tests.
|
||
- Keep the JWP 24/7 feed unchanged; manage the secondary test feed manually via Wirecast.
|
||
- Maintain manual activation/deactivation of the test feed for now (no full automation).
|
||
- Preserve Boukili on a VM; postpone API development.
|
||
- Use engaged‑view metrics for YouTube performance reporting to retain historical comparability.
|
||
|
||
**# Decisions Needed**
|
||
- Clarify with Pierre‑Olivier and the CRTC exactly what modifications (retroactivity, location, inclusion of response) are required for the CRTC report.
|
||
- Confirm JWP’s ingest‑point behavior and any associated billing for the secondary feed.
|
||
- Determine whether a second Chorus URL will ever be purchased for live feed use.
|
||
- Decide the final content handling after ONFR live events (retain JWP stream vs. replace with main version in Louise/Magador).
|
||
- Approve the Jira‑form design for automated podcast‑chain requests after feasibility confirmation with Marc.
|
||
|
||
**# Project Changes**
|
||
- Boukili version 3 testing schedule initiated; OTT and other dossiers to be followed up.
|
||
- ONFR episode preparation shifted to “prepare Wednesday, publish Thursday” cadence; three initial episodes to follow this pattern.
|
||
- Supervision solution rollout timeline: ONFR → Idéllo → TFO, with testing checkpoints.
|
||
- OTT testing expanded to include multiple devices and Apple TV zoom verification before sign‑off.
|
||
|
||
**# Vendor Issues**
|
||
- Potential surfacturation of the secondary JWP feed (active for at least four months) pending verification with JWP.
|
||
- Need clarification from JWP on ingest‑point operation, fee structure, and stream handling.
|
||
|
||
**# Team / Coaching / Recognition**
|
||
- No explicit coaching or recognition items recorded in the notes.
|
||
|
||
**# Next‑Week Commitments**
|
||
- Send email to CRTC and follow up with Pierre‑Olivier on the report clarification.
|
||
- Begin version 3 Boukili testing.
|
||
- Conduct end‑to‑end test with broadcast studio (start 10 h, live at 10:10 h, 10‑min video).
|
||
- Implement cron checks on ONFR and add supervision entries.
|
||
- Create a test collection in JWP and verify subtitle display.
|
||
- Verify JWP secondary‑feed billing and ingest‑point details.
|
||
- Complete mapping of Boukili production‑DB fields after migration.
|
||
- Obtain “is original” product indicator data from Louise team for reporting.
|
||
|
||
**# Sources**
|
||
- **Work/Team/Valery/Valery 1‑1/2026‑09‑08 - Valery - Amadou.md** — Storyline feature, CRTC issue, Boukili v3 status.
|
||
- **Work/Projects/2026/ONFR/2026‑09‑08 - Ai Rei et Moi.md** — Haywire feed decision, episode duration handling, subtitle issue.
|
||
- **Work/Projects/2026/ONFR/2026‑09‑08 - Direct ONFR - Point du feed pour le Live Event.md** — JWP feed strategy, ingest/fee clarification, subtitle collection test.
|
||
- **Work/Team/Slimane/Slimane 1‑1/2026‑09‑08 - Mohammed Slimane- Amadou.md** — Job supervision solution approval and rollout plan.
|
||
- **Work/Team/Jean‑Claude/Jean‑Claude 1‑1/2026‑09‑08 - Jean‑Claude - Amadou.md** — JWP feed details, OTT testing, Contentful API, podcast automation.
|
||
- **Work/Team/Habiba/Habiba 1‑1/2026‑09‑08 - Habiba 1‑1.md** — Boukili VM decision, production DB access, YouTube engaged‑view metric, ONFR live‑ON OTT data tracking.
|
||
|
||
---
|
||
|
||
**# Major Developments**
|
||
- Decision to keep WordPress on the current site and retain WP Engine as the hosting provider. (Source: *Mohammed B 1‑1/2026‑09‑08 – Amadou - Mohammed.md*)
|
||
- Established process for publishing course ZIP files to Idéllo: a ticket must be created, the ZIP prepared, and then handed to Hélène for injection into Louise; implementation cannot start before 12 Oct. (Source: *2026‑09‑10 – Flux Zip pour les maleos qui vont sur Idello.md*)
|
||
- Approval from the CTO to present a potential collaboration with Lunii to the CEO, with a view to opening an exploratory discussion. (Source: *2026‑09‑11 – Présenter Luuni à Xavier.md*)
|
||
- Planned dedicated meeting on 16 Sept afternoon to discuss the Mogador project’s synchronization evolution and possible removal. (Source: *Mohammed B 1‑1/2026‑09‑08 – Amadou - Mohammed.md*)
|
||
|
||
**# Risks / Blockers**
|
||
- Geo‑blocking of TFO and Idéllo cannot be temporarily removed without a production release; raises legal issues for international distribution. (Source: *Mohammed B 1‑1/2026‑09‑08 – Amadou - Mohammed.md*)
|
||
- CRTC accessibility remarks lack detail; need clarification of confidentiality vs. anonymity before the 5 Oct deadline. (Source: *Mohammed B 1‑1/2026‑09‑08 – Amadou - Mohammed.md*)
|
||
- Mogador synchronization complexity, potential removal, and lack of a clear “source of truth” for data. (Source: *Mohammed B 1‑1/2026‑09‑08 – Amadou - Mohammed.md*)
|
||
- Dependency on US‑based vendors (JWP, WP Engine, Algolia) poses compliance risk under current policy. (Source: *Mohammed B 1‑1/2026‑09‑08 – Amadou - Mohammed.md*)
|
||
- Applications built with Gemini or via vibe coding could be deployed without sufficient visibility on design, security, or maintenance. (Source: *Mohammed B 1‑1/2026‑09‑08 – Amadou - Mohammed.md*)
|
||
- OTT test completion is required before any store publication; delay could impact launch schedule. (Source: *Mohammed B 1‑1/2026‑09‑08 – Amadou - Mohammed.md*)
|
||
- Limited time (≈1.5 days) to implement and validate four technical items for the Boukili build; risk of P3/P4 bugs remaining unresolved. (Source: *Daily Meeting TFO vs Zemind.md*)
|
||
|
||
**# Decisions Made**
|
||
- Remain on WordPress for the site and keep WP Engine as the host. (Source: *Mohammed B 1‑1/2026‑09‑08 – Amadou - Mohammed.md*)
|
||
- ZIP‑to‑Idéllo workflow: ticket → ZIP preparation → hand‑off to Hélène; start no earlier than 12 Oct. (Source: *2026‑09‑10 – Flux Zip pour les maleos qui vont sur Idello.md*)
|
||
- Unblock Trings invoice now that the deliverable has been provided. (Source: *Mohammed B 1‑1/2026‑09‑08 – Amadou - Mohammed.md*)
|
||
- Organize dedicated meetings for complex topics rather than bundling many items in a single session. (Source: *Mohammed B 1‑1/2026‑09‑08 – Amadou - Mohammed.md*)
|
||
|
||
**# Decisions Needed**
|
||
- Confirmation of 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 build for Boukili. (Source: *Daily Meeting TFO vs Zemind.md*)
|
||
- Final determination on Mogador’s synchronization approach and whether the project will be removed. (Source: *Mohammed B 1‑1/2026‑09‑08 – Amadou - Mohammed.md*)
|
||
- Clarification of CRTC accessibility requirements and confidentiality handling before 5 Oct. (Source: *Mohammed B 1‑1/2026‑09‑08 – Amadou - Mohammed.md*)
|
||
- Decision on proceeding with the Lunii exploratory contact after CEO review. (Source: *2026‑09‑11 – Présenter Luuni à Xavier.md*)
|
||
|
||
**# Project Changes**
|
||
- Scheduled dedicated Mogador discussion on Wednesday 16 Sept afternoon. (Source: *Mohammed B 1‑1/2026‑09‑08 – Amadou - Mohammed.md*)
|
||
- Planned presentation of projects with Francis and team for the following week. (Source: *Mohammed B 1‑1/2026‑09‑08 – Amadou - Mohammed.md*)
|
||
- Production build for Boukili to be released as a release candidate the day after the QA‑validated build. (Source: *Daily Meeting TFO vs Zemind.md*)
|
||
|
||
**# Vendor Issues**
|
||
- Ongoing compliance review of US‑based vendors (JWP, WP Engine, Algolia) due to policy constraints. (Source: *Mohammed B 1‑1/2026‑09‑08 – Amadou - Mohammed.md*)
|
||
- Trings regression requires review of Algolia logic; pending email from JC. (Source: *2026‑09‑10 Journal.md* and *2026‑09‑11 Journal.md*)
|
||
|
||
**# Team / Coaching / Recognition**
|
||
- No explicit coaching or recognition entries meet the extraction criteria. (No applicable source content.)
|
||
|
||
**# Next‑Week Commitments**
|
||
- Prepare and deliver the ZIP‑to‑Idéllo workflow ticket (start 12 Oct). (Source: *2026‑09‑10 – Flux Zip pour les maleos qui vont sur Idello.md*)
|
||
- Conduct the dedicated Mogador meeting (Wed 16 Sept afternoon). (Source: *Mohammed B 1‑1/2026‑09‑08 – Amadou - Mohammed.md*)
|
||
- Present project overview with Francis to the teams (next week). (Source: *Mohammed B 1‑1/2026‑09‑08 – Amadou - Mohammed.md*)
|
||
- Validate and deploy the production build for Boukili, including password‑reset testing. (Source: *Daily Meeting TFO vs Zemind.md*)
|
||
|
||
**# Sources**
|
||
- *Mohammed B 1‑1/2026‑09‑08 – Amadou - Mohammed.md* — major project decisions, risks, actions, and upcoming meetings.
|
||
- *2026‑09‑10 – Flux Zip pour les maleos qui vont sur Idello.md* — ZIP publishing decision and timeline.
|
||
- *2026‑09‑11 – Présenter Luuni à Xavier.md* — CTO‑approved Lunii collaboration proposal.
|
||
- *Daily Meeting TFO vs Zemind.md* — Boukili build schedule, technical blockers, and pending decisions.
|
||
- *2026‑09‑10 Journal.md* — notes on OTT testing and Trings/Algolia issues.
|
||
- *2026‑09‑11 Journal.md* — additional Trings regression details.
|
||
|
||
---
|
||
|
||
**# Major Developments**
|
||
- The planned production release for the Firebase‑to‑AWS migration (Boukili) scheduled for Monday was cancelled; no new release date will be set until blockers are clarified and reliable estimates obtained. (Source: *20 Work/Projects/2026/Boukili/2026-09-10 - Boukili.md*)
|
||
- A “freeze” of code will occur once the currently identified issues are fixed and validated; phase‑2 work will be kept on a separate branch and not merged into phase‑1 during validation. (Source: *20 Work/Meetings/TFO/Produits Numériques (Transversal)/2026-09-11 - Produit Numérique.md*)
|
||
- The OTT delivery is at risk of missing the live‑event deadline (Sept 14) due to regressions; a weekend release may be required to meet the Sept 17 live broadcast. (Source: *20 Work/Meetings/Team Meetings/2026/2026-09-10 - Reunion equipe.md*)
|
||
|
||
**# Risks / Blockers**
|
||
- Potential loss or non‑synchronisation of user data for multi‑device users during the Firebase‑to‑AWS migration; risk heightened if devices remain on different back‑ends. (Source: *Boukili.md*)
|
||
- Ongoing Salesforce regression investigation with no resolution at time of meeting; impacts data migration reliability. (Source: *Boukili.md*)
|
||
- Uncertainty about the reliability of the data migration itself; current suggested solutions (accepting data loss or reduced reliability) are not acceptable. (Source: *Boukili.md*)
|
||
- Insufficient testing time to guarantee a solid version before submission; migration works on test/staging but fails on UAT. (Source: *Produit Numérique.md*)
|
||
- “Last activity” field reliability issues, especially under network failure conditions. (Source: *Produit Numérique.md*)
|
||
- Undefined strategy for forced migration of multi‑device users; critical for submission. (Source: *Produit Numérique.md*)
|
||
- QA capacity bottleneck: only one QA resource covering four sites; risk of delayed testing. (Source: *Reunion equipe.md*)
|
||
- JW Player billing ambiguity: unclear whether fees apply to active address or actual stream usage. (Source: *Direct ONFR - Réponse sur le feed de JWP.md*)
|
||
|
||
**# Decisions Made**
|
||
- Cancelled Monday production release for Boukili migration; defer new date pending clarification. (Source: *Boukili.md*)
|
||
- Code freeze to be applied after fixing and validating identified issues; phase‑2 work isolated on separate branch. (Source: *Produit Numérique.md*)
|
||
- Use the second Corus feed for a test send to JW Player; keep existing feed unchanged; retain both ingest points and request JW Player to delete those that cannot be removed directly. (Source: *Direct ONFR - Réponse sur le feed de JWP.md*)
|
||
- Documentation departmental will be presented under “platform” section; data governance treated as continuous practice; project renamed “projet Données FMC”. (Source: *Reunion equipe.md*)
|
||
- For Idéllo ZIP files, each course/ZIP must have its own Jira ticket; processing will not start before 12 Oct. (Source: *Reunion equipe.md*)
|
||
|
||
**# Decisions Needed**
|
||
- Confirmation of the migration‑forced strategy for multi‑device users and associated user communication plan. (Source: *Produit Numérique.md*)
|
||
- Final delivery date and freeze trigger confirmation for the upcoming release (window 18 Sept – 23 Sept). (Source: *Produit Numérique.md*)
|
||
- Clarification of JW Player billing conditions (address active vs. stream usage). (Source: *Direct ONFR - Réponse sur le feed de JWP.md*)
|
||
- Approval of additional QA resources or temporary reinforcement to address capacity bottleneck. (Source: *Reunion equipe.md*)
|
||
|
||
**# Project Changes**
|
||
- Production schedule for Boukili migration postponed; new schedule pending resolution of data‑migration blockers. (Source: *Boukili.md*)
|
||
- OTT delivery timeline now uncertain; may require weekend release to meet live event on 17 Sept. (Source: *Reunion equipe.md*)
|
||
- Phase‑2 development work will be isolated on a separate branch, not merged into phase‑1 during validation. (Source: *Produit Numérique.md*)
|
||
|
||
**# Vendor Issues**
|
||
- JW Player billing details remain contradictory; need clarification from vendor. (Source: *Direct ONFR - Réponse sur le feed de JWP.md*)
|
||
- Coordination with Corus (contact Chris Sandinot) required to modify second stream address for test. (Source: *Direct ONFR - Réponse sur le feed de JWP.md*)
|
||
|
||
**# Team / Coaching / Recognition**
|
||
- No explicit coaching or recognition items identified in the notes.
|
||
|
||
**# Next‑Week Commitments**
|
||
- Technical point with Abiba to clarify data‑migration issues (deadline: tomorrow morning). (Source: *Boukili.md*)
|
||
- Prepare and circulate email detailing critical blockers for team validation. (Source: *Boukili.md*)
|
||
- Evaluate feasibility, cost, and timeline of IBO intervention on migration with The Mind (starting after tomorrow’s point). (Source: *Boukili.md*)
|
||
- Inform Mohamed of the release postponement after clarification with Abiba. (Source: *Boukili.md*)
|
||
- Obtain duration estimates for resolving remaining problems (responsible: The Mind). (Source: *Boukili.md*)
|
||
- Investigate UAT migration issue and deliver a stable version after a new test cycle (development team). (Source: *Produit Numérique.md*)
|
||
- Implement retry mechanism for “last activity” field and set up visibility indicator for tests (development team). (Source: *Produit Numérique.md*)
|
||
- Exchange with Habiba to define robust solution for validating last activity (responsible: relevant teams). (Source: *Produit Numérique.md*)
|
||
- Study with current agency the possibility of forcing all users to update via Contentful message (Amadou & team). (Source: *Produit Numérique.md*)
|
||
- Verify Salesforce test progress with Nicolas and Mark; communicate update (responsible: relevant team). (Source: *Produit Numérique.md*)
|
||
- Confirm realistic delivery dates by email (development team, due afternoon). (Source: *Produit Numérique.md*)
|
||
- Prepare project presentation for meeting with Francis (due Tuesday 15 Sept). (Source: *Reunion equipe.md*)
|
||
- Continue Umami tracker implementation (Jean‑Claude). (Source: *Reunion equipe.md*)
|
||
- Analyze Mogador sync flows and set up failure alerts (Mohamed Slimane). (Source: *Reunion equipe.md*)
|
||
- Create Jira tickets for each Idéllo ZIP file/course starting 12 Oct (Jason & requestors). (Source: *Reunion equipe.md*)
|
||
- Perform targeted regression tests on TFO live/carousel delivery before 16‑17 Sept (Ajar). (Source: *Reunion equipe.md*)
|
||
- Conduct exchange on service‑tracking recommendations for MAMI (Rabiba & Amandou). (Source: *Reunion equipe.md*)
|
||
- Test second Corus feed to JW Player and report results (responsible not specified). (Source: *Direct ONFR - Réponse sur le feed de JWP.md*)
|
||
|
||
**# Sources**
|
||
- 20 Work/Projects/2026/Boukili/2026-09-10 - Boukili.md — production release cancellation, blockers, actions.
|
||
- 20 Work/Meetings/TFO/Produits Numériques (Transversal)/2026-09-11 - Produit Numérique.md — code freeze, delivery window, risks.
|
||
- 20 Work/Meetings/Team Meetings/2026/2026-09-10 - Reunion equipe.md — OTT delivery risk, Boukili migration complexity, QA capacity, project naming, Idéllo ZIP process.
|
||
- 20 Work/Projects/2026/OTT/2026-09-10 - Direct ONFR - Réponse sur le feed de JWP.md — JW Player feed test, billing ambiguity.
|
||
|