vault backup: 2026-09-11 21:35:10
This commit is contained in:
@@ -0,0 +1,10 @@
|
||||
|
||||
2026-07-27
|
||||
|
||||
HAB -> 7 en cours 2 en attente
|
||||
Binta -> 2 en cours 1 en attente
|
||||
JC -> 9 en cours 1 en attente
|
||||
JY -> 4 en cours 1 en attente
|
||||
VV -> n/a
|
||||
Hajar -> n/a (too many portals for her)
|
||||
MS -> 0
|
||||
@@ -0,0 +1,289 @@
|
||||
|
||||
|
||||
← [[Week 31 - Weekly Review - 2026-07-31]]
|
||||
|
||||
→ [[Week 33 - Weekly Review - 2026-08-14]]
|
||||
## 🎯 Executive Summary (2-3 sentences)
|
||||
|
||||
Overall health of the department:
|
||||
|
||||
Operations remained stable, but several strategic projects slipped due to validation findings, changing priorities, and resource constraints. This week also highlighted opportunities to strengthen project governance, documentation discipline, and the balance between operational work and project commitments.
|
||||
|
||||
Traffic light: 🟡
|
||||
|
||||
This week's headline:
|
||||
- Shifted from tracking execution to actively managing project commitments and accountability.
|
||||
|
||||
---
|
||||
|
||||
# Wins 🏆
|
||||
|
||||
Things that moved the company forward.
|
||||
|
||||
- Successfully prepared and delivered the VP project portfolio presentation.
|
||||
- Established clearer expectations around project ownership, commitments, and operational coverage.
|
||||
- Continued building my long-term management system in Obsidian to centralize decisions, employee follow-ups, meetings, and projects.
|
||||
- Wrote a lot about solutions for a better Mogador and a Sync v2 which I'll call content publication engine (CPE)
|
||||
|
||||
|
||||
---
|
||||
|
||||
# Risks ⚠️
|
||||
|
||||
What keeps me awake?
|
||||
|
||||
| Risk | Impact | Mitigation | Owner |
|
||||
| ---------------------------------------------------------------- | ------ | ------------------------------------------------------------ | ----- |
|
||||
| PBI Algolia delivery continues to slip after validation findings | High | Re-establish remaining work, validate against approved scope | Binta |
|
||||
| QA capacity reduced during Habiba's vacation | Medium | Reduce non-urgent requests and prioritize operational work | Me |
|
||||
| Operational coverage during Habiba, Valery and Joel vacation | Medium | Reduce non-urgent requests and prioritize operations | Me |
|
||||
|
||||
---
|
||||
|
||||
# Team 👥
|
||||
|
||||
## Team health
|
||||
|
||||
Overall morale:
|
||||
🟡 Normal
|
||||
|
||||
### Coaching / Recognition
|
||||
|
||||
**Who deserves recognition?**
|
||||
|
||||
- Habiba for identifying critical issues during validation instead of approving questionable results.
|
||||
- Slimane for continuing to move BetterStack monitoring forward despite shifting priorities.
|
||||
|
||||
**Who needs coaching?**
|
||||
|
||||
- Binta on estimation, ownership, testing strategy, communication, and balancing project work with operational responsibilities.
|
||||
- Slimane needs more autonomy in prioritization and technical decision-making.
|
||||
|
||||
**Any conflicts?**
|
||||
|
||||
- Ongoing concerns regarding Algolia execution and expectations around project ownership for Binta. Hasn't done the "formation" from Ai Rei's jira ticket
|
||||
|
||||
**Any hiring concerns?**
|
||||
|
||||
- None this week.
|
||||
|
||||
---
|
||||
|
||||
# Projects 📁
|
||||
|
||||
| Project | Status | Next Milestone | Blocker |
|
||||
| ---------------------- | ------ | ----------------------------------- | ------------------------------- |
|
||||
| VP Portfolio | 🟢 | September follow up | None |
|
||||
| BetterStack Heartbeats | 🟡 | Selection and implementation | Operation takeover with tickets |
|
||||
| Umami | 🟡 | Establish new timeline | Operation then vacations |
|
||||
| FMC | 🟢<br> | First draft as to what is available | None |
|
||||
| Algolia | 🔴 | Validation | Me + Habiba vacation |
|
||||
|
||||
Projects slipping:
|
||||
|
||||
- Algolia
|
||||
- Umami
|
||||
- Monitor Mogador
|
||||
|
||||
Projects completed:
|
||||
|
||||
- VP portfolio presentation
|
||||
|
||||
---
|
||||
|
||||
# Vendors 🤝
|
||||
|
||||
Any issue?
|
||||
- Important discussion regarding advertisement placement requiring follow-up Mediatonik
|
||||
- Trings is asking $3500 for tags which I'll approve
|
||||
|
||||
Renewals coming?
|
||||
- None
|
||||
|
||||
Invoices pending?
|
||||
- None handled the ones from Affranchis and Libeo
|
||||
|
||||
Contract risks?
|
||||
- None
|
||||
|
||||
---
|
||||
|
||||
# KPIs 📈
|
||||
|
||||
Important numbers this week.
|
||||
|
||||
- No formal KPI review.
|
||||
- Main focus remained project execution and delivery.
|
||||
- Executive visibility into project portfolio improved.
|
||||
|
||||
Anything unusual?
|
||||
|
||||
-
|
||||
|
||||
---
|
||||
|
||||
# Decisions Made
|
||||
|
||||
| Decision | Why |
|
||||
| ---------------------------------------------------------- | ----------------------------------------------------------------------------- |
|
||||
| Prioritize Board of Directors work over Algolia validation | Executive priority |
|
||||
| Will pay $3500 extra to trings for tags | Keeping the OTT in french see [[2026-08-07 - Pay Trings for the french tabs]] |
|
||||
|
||||
---
|
||||
|
||||
# Decisions Needed
|
||||
|
||||
What decisions must be made next week?
|
||||
|
||||
- Do we need a 2nd streams for the live on the OTT
|
||||
- Do I tell the team about CPE
|
||||
|
||||
---
|
||||
|
||||
# Meetings
|
||||
|
||||
Which meetings created value?
|
||||
|
||||
- Sprint review
|
||||
- Meeting with JC about the live POC and streamin
|
||||
|
||||
Which meetings should disappear?
|
||||
|
||||
-
|
||||
|
||||
Which meetings could become:
|
||||
|
||||
- Slack
|
||||
- Email
|
||||
- Dashboard
|
||||
- Monthly instead of weekly
|
||||
|
||||
---
|
||||
|
||||
# Delegation
|
||||
|
||||
What did I unnecessarily do myself?
|
||||
|
||||
- Anything mogador
|
||||
|
||||
What should be delegated next week?
|
||||
|
||||
- Anything Idello
|
||||
- Continue delegating technical execution while focusing on commitments, priorities, and outcomes.
|
||||
|
||||
---
|
||||
|
||||
# Learning
|
||||
|
||||
Books
|
||||
|
||||
Articles
|
||||
|
||||
Podcasts
|
||||
|
||||
Lessons learned
|
||||
|
||||
- Validation should confirm quality, not discover fundamental defects.
|
||||
- Approved project documents should not be modified without communication.
|
||||
- A manager's role is to manage commitments and decisions rather than solve technical problems.
|
||||
|
||||
---
|
||||
|
||||
# Process Improvements
|
||||
|
||||
Something that annoyed me this week.
|
||||
|
||||
- Important project documentation was modified after approval without notification.
|
||||
|
||||
How can I make sure it never happens again?
|
||||
|
||||
- Require communication whenever approved project documentation changes.
|
||||
- Continue formalizing project governance and documentation practices.
|
||||
|
||||
|
||||
|
||||
---
|
||||
|
||||
# CEO Questions
|
||||
|
||||
If the CEO walked in Monday morning, what questions might they ask?
|
||||
|
||||
- When will Algolia actually be completed?
|
||||
- What projects are currently at risk?
|
||||
- Are we properly staffed for upcoming priorities?
|
||||
|
||||
Do I already know the answers?
|
||||
Yes
|
||||
|
||||
---
|
||||
|
||||
# Top Priorities Next Week
|
||||
|
||||
1. Review Binta's tickets and delivery of the FMC project
|
||||
|
||||
2. See if Affranchis has a solution for the sync issues
|
||||
|
||||
3. Start talking about CPE.
|
||||
|
||||
---
|
||||
|
||||
# Personal Reflection
|
||||
|
||||
Energy (1-10): 8
|
||||
|
||||
Stress (1-10): 4
|
||||
|
||||
Biggest accomplishment: Mogador and preparing the presentation for the VP
|
||||
|
||||
Biggest mistake:
|
||||
- Not following closely Binta
|
||||
- Not establishing earlier expectations around documentation governance and operational/project balancing.
|
||||
|
||||
One thing to improve next week:
|
||||
- Ask better question
|
||||
- Do more follow up
|
||||
- Ask for documentation
|
||||
|
||||
---
|
||||
|
||||
# Parking Lot
|
||||
|
||||
Random ideas to revisit later.
|
||||
|
||||
-
|
||||
|
||||
-
|
||||
|
||||
|
||||
# CTO Development
|
||||
|
||||
### Leadership
|
||||
|
||||
- Improved documentation of employee performance and coaching discussions.
|
||||
- Strengthened expectations around ownership and commitments.
|
||||
|
||||
### Technology
|
||||
|
||||
- Continued refining the Obsidian knowledge system.
|
||||
- Advanced BetterStack monitoring planning.
|
||||
|
||||
### Business
|
||||
|
||||
- Improved executive project portfolio reporting.
|
||||
- Better understanding of project governance.
|
||||
|
||||
### Finance
|
||||
|
||||
- Continued discussions around vendor and project prioritization.
|
||||
|
||||
### Communication
|
||||
|
||||
- More direct conversations around expectations while remaining fact-based.
|
||||
|
||||
**One thing I did this week that made me more like a CTO:**
|
||||
|
||||
- Focused on governance, prioritization, accountability, and executive visibility rather than technical implementation.
|
||||
|
||||
**One thing I did this week that kept me acting like an individual contributor:**
|
||||
|
||||
- Spent too much time personally investigating technical details and documentation changes instead of relying on project ownership and management processes.
|
||||
@@ -0,0 +1,274 @@
|
||||
|
||||
|
||||
← [[Week 32 - Weekly Review - 2026-08-07]]
|
||||
|
||||
→ [[Week 34 - Weekly Review - 2026-08-21]]
|
||||
## 🎯 Executive Summary (2-3 sentences)
|
||||
|
||||
Overall health of the department:
|
||||
Quiet since many are on vacation
|
||||
Hajar is tired but going through.
|
||||
|
||||
Traffic light: 🟢 / 🟡 / 🔴
|
||||
|
||||
This week's headline:
|
||||
- Réponse urgente aux questions du ministère sur le rapport annuel. J'ai du clarifié les points sur le soit disant instabilité d'Idello
|
||||
- Présentation du flux live OTT qui va demander une rencontre avec Sonia et Philippe
|
||||
- Blocker avec les demandes de bug sur algolia
|
||||
|
||||
---
|
||||
|
||||
# Wins 🏆
|
||||
|
||||
Things that moved the company forward.
|
||||
|
||||
- projet OTT a bien avancé
|
||||
-
|
||||
-
|
||||
|
||||
---
|
||||
|
||||
# Risks ⚠️
|
||||
|
||||
What keeps me awake?
|
||||
|
||||
| Risk | Impact | Mitigation | Owner |
|
||||
| ----------------- | ------ | ------------------------------------ | ----------- |
|
||||
| Monitoring Sync | Majeur | Sera plus dispo au retour de Joel | Slimane |
|
||||
| Emission live ott | Moyen | A voir après la rencontre avec Sonia | Amadou / JC |
|
||||
| Hajar - fatigue | Majeur | Personne au besoin | Amadou |
|
||||
| Habiba - fatigue | Majeur | Priorité et compétence de Binta | Amadou |
|
||||
|
||||
---
|
||||
|
||||
# Team 👥
|
||||
|
||||
## Team health
|
||||
|
||||
Overall morale:
|
||||
🟡 Normal
|
||||
|
||||
|
||||
### Coaching / Recognition
|
||||
|
||||
Who deserves recognition?
|
||||
|
||||
- JC for the OTT
|
||||
- Hajar for all the test
|
||||
- Slimane pour creuser plus
|
||||
|
||||
Who needs coaching?
|
||||
|
||||
- Everyone avec les tickets
|
||||
|
||||
Any conflicts?
|
||||
|
||||
-
|
||||
|
||||
Any hiring concerns?
|
||||
|
||||
-
|
||||
|
||||
---
|
||||
|
||||
# Projects 📁
|
||||
|
||||
| Project | Status | Next Milestone | Blocker |
|
||||
| --------------- | ------ | ---------------------------- | ----------------------------------------------- |
|
||||
| OTT | 🟢 | Discussion Sonia et Philippe | |
|
||||
| Monitoring Sync | 🟡 | Choisir un outil | Opérations (tfo et ticket sur les images flous) |
|
||||
| Algolia | 🔴 | Validation | Vacances Habiba |
|
||||
|
||||
Projects slipping:
|
||||
|
||||
- Monitoring Sync
|
||||
|
||||
Projects completed:
|
||||
|
||||
-
|
||||
|
||||
---
|
||||
|
||||
# Vendors 🤝
|
||||
|
||||
Any issue?
|
||||
- Must read the contract for WP Expert
|
||||
|
||||
Renewals coming?
|
||||
|
||||
Invoices pending?
|
||||
- TVO was treated today
|
||||
- Trings I signed the amendement of $5K
|
||||
|
||||
Contract risks?
|
||||
|
||||
-
|
||||
|
||||
---
|
||||
|
||||
# KPIs 📈
|
||||
|
||||
Important numbers this week.
|
||||
|
||||
-
|
||||
|
||||
-
|
||||
|
||||
-
|
||||
|
||||
Anything unusual?
|
||||
|
||||
-
|
||||
|
||||
---
|
||||
|
||||
# Decisions Made
|
||||
|
||||
| Decision | Why |
|
||||
| --------------------------------------------------- | ----------------------------------------------------- |
|
||||
| Rencontrer Sonia et Philippe | Leur montrer le coté technique pour le live et OTT |
|
||||
| Approbation des bons de commandes de Julie | Mieux approuver que pas |
|
||||
| Faire un test en production d'un vrai live pour OTT | Voir le flux entier et s'assurer que tout marche bien |
|
||||
|
||||
---
|
||||
|
||||
# Decisions Needed
|
||||
|
||||
What decisions must be made next week?
|
||||
|
||||
- Contract Wp Expert, go ou no go?
|
||||
- Reparler des tickets Jira à l'équipe
|
||||
|
||||
---
|
||||
|
||||
# Meetings
|
||||
|
||||
Which meetings created value?
|
||||
|
||||
- Rencontre du 14 aout sur l'OTT
|
||||
|
||||
Which meetings should disappear?
|
||||
|
||||
-
|
||||
|
||||
Which meetings could become:
|
||||
|
||||
- Slack
|
||||
- Email
|
||||
- Dashboard
|
||||
- Monthly instead of weekly
|
||||
|
||||
---
|
||||
|
||||
# Delegation
|
||||
|
||||
What did I unnecessarily do myself?
|
||||
|
||||
-
|
||||
|
||||
What should be delegated next week?
|
||||
|
||||
-
|
||||
|
||||
---
|
||||
|
||||
# Learning
|
||||
|
||||
Books
|
||||
|
||||
Articles
|
||||
|
||||
Podcasts
|
||||
|
||||
Lessons learned
|
||||
|
||||
-
|
||||
|
||||
---
|
||||
|
||||
# Process Improvements
|
||||
|
||||
Something that annoyed me this week.
|
||||
|
||||
How can I make sure it never happens again?
|
||||
|
||||
-
|
||||
|
||||
---
|
||||
|
||||
# CEO Questions
|
||||
|
||||
If the CEO walked in Monday morning, what questions might they ask?
|
||||
|
||||
1.
|
||||
|
||||
2.
|
||||
|
||||
3.
|
||||
|
||||
Do I already know the answers?
|
||||
|
||||
---
|
||||
|
||||
# Top Priorities Next Week
|
||||
|
||||
1.
|
||||
|
||||
2.
|
||||
|
||||
3.
|
||||
|
||||
---
|
||||
|
||||
# Personal Reflection
|
||||
|
||||
Energy (1-10):
|
||||
|
||||
Stress (1-10):
|
||||
|
||||
Biggest accomplishment:
|
||||
|
||||
Biggest mistake:
|
||||
|
||||
One thing to improve next week:
|
||||
|
||||
---
|
||||
|
||||
# Parking Lot
|
||||
|
||||
Random ideas to revisit later.
|
||||
|
||||
-
|
||||
|
||||
-
|
||||
|
||||
|
||||
# CTO Development
|
||||
|
||||
Leadership
|
||||
|
||||
-
|
||||
|
||||
Technology
|
||||
|
||||
-
|
||||
|
||||
Business
|
||||
|
||||
-
|
||||
|
||||
Finance
|
||||
|
||||
-
|
||||
|
||||
Communication
|
||||
|
||||
-
|
||||
|
||||
One thing I did this week that made me more like a CTO:
|
||||
|
||||
-
|
||||
|
||||
One thing I did this week that kept me acting like an individual contributor:
|
||||
|
||||
-
|
||||
@@ -0,0 +1,78 @@
|
||||
# Révision des actions et blocages de l'équipe
|
||||
|
||||
## Résumé
|
||||
- **Préparation de la rencontre avec Francis** :
|
||||
- Présentation des projets (documentation départementale, gouvernance des données, projet Données FMC).
|
||||
- Gestion des livraisons OTT (migrations, calendrier).
|
||||
- Décisions : documentation rattachée à la plateforme, gouvernance des données comme pratique continue, projet nommé « Données FMC ».
|
||||
|
||||
- **Actions à executor** :
|
||||
- Préparation du dossier de présentation.
|
||||
- Correction des tickets Jira et mise en place des trackers Umami.
|
||||
- Gestion des fichiers ZIP Idéllo et traitement des demandes QA.
|
||||
|
||||
- **Blocages/Risques** :
|
||||
- Défaut de calendrier pour OTT (livraison le week-end).
|
||||
- Incompatibilité des pipelines de Boukili (Firestore/AWS).
|
||||
- Risque de perte de progression multi-device.
|
||||
- Besoin de QA supplémentaire ou renfort ponctuel.
|
||||
- Période de traitement des fichiers ZIP (12 octobre).
|
||||
|
||||
---
|
||||
|
||||
## Décisions Claires
|
||||
1. **Documentation** :
|
||||
- Rattachée à la **plateforme** (non données).
|
||||
- Gouvernance des données : **pratique continue** (source de vérité unique dans Power BI).
|
||||
- Projet nommé « **Données FMC** » (non « nouveau gabarit FMC »).
|
||||
|
||||
2. **Gestion des fichiers ZIP** :
|
||||
- **Tous les fichiers ZIP** (cours + fichiers) : tickets Jira distincts.
|
||||
- **Traitement des demandes** : commence **à partir du 12 octobre**.
|
||||
|
||||
3. **Système de tickets Jira** :
|
||||
- **Mise à jour continue** des tickets avant traitement et fermeture.
|
||||
- **Mise en œuvre systématique** depuis le 12 octobre.
|
||||
|
||||
---
|
||||
|
||||
## Actions à Faire
|
||||
- **[ ]** Préparer la présentation pour la rencontre avec Francis (responsable : équipe) – Échéance : mardi 15.
|
||||
- **[ ]** Corriger le document de présentation (responsable : non précisé) – Échéance : avant mardi 15.
|
||||
- **[ ]** Mise en place des trackers Umami (responsable : Jean-Claude) – Échéance : non précisée.
|
||||
- **[ ]** Analyser flux Mogador + alertes en cas d’échec (responsable : Mohamed Slimane) – Échéance : non précisée.
|
||||
- **[ ]** Gérer tickets Jira pour fichiers ZIP Idéllo (responsable : Jason / demandeurs) – Échéance : à partir du 12 octobre.
|
||||
- **[ ]** Récompiler fichiers ZIP reçus (responsable : équipe) – Échéance : non précisée.
|
||||
- **[ ]** Clarifier calendrier OTT (responsable : non précisé) – Échéance : non précisée.
|
||||
- **[ ]** Tests de régression TFO (responsable : Ajar) – Échéance : avant 16/17.
|
||||
- **[ ]** Échanger sur recommendations tracking (responsable : Rabiba/Amandou) – Échéance : non précisée.
|
||||
|
||||
---
|
||||
|
||||
## Blocages à Traiter
|
||||
1. **Facturation JW Player** :
|
||||
- Indétermination (adresse active = frais vs flux non écouté).
|
||||
- **Solution** : Clarifier les conditions de facturation.
|
||||
|
||||
2. **Ingest points inutilisés** :
|
||||
- Ne pas supprimer certains (ex : non modifiable directement).
|
||||
- **Solution** : Demander à JW Player de supprimer ceux-là.
|
||||
|
||||
3. **Calendrier OTT** :
|
||||
- Livraison possible le week-end (14 septembre) pour l’émission live du 17.
|
||||
- **Solution** : Ralenti les livraisons pour respecter les délais.
|
||||
|
||||
4. **QA** :
|
||||
- Capacité limitée (1 personne à 4 sites).
|
||||
- **Solution** : Renfort ponctuel ou QAs supplémentaires.
|
||||
|
||||
---
|
||||
|
||||
## À Suivre
|
||||
- **Clarifier les conditions de facturation** avec JW Player.
|
||||
- **Vérifier les résultats des tests** du second feed et sous-titrages.
|
||||
- **Suivre l’intégration de Umami** au Data Warehouse.
|
||||
- **Contrôler la mise en œuvre** des tickets Jira pour Idéllo.
|
||||
|
||||
---
|
||||
**Note** : La priorité des actions est répartie pour minimiser les blocages et optimiser le calendrier.
|
||||
@@ -0,0 +1,123 @@
|
||||
## 🎯 Executive Summary
|
||||
|
||||
**Overall health:** Not assessed.
|
||||
**Traffic light:** 🟡
|
||||
|
||||
**This week's headline:**
|
||||
Multiple critical projects (Boukili migration, ONFR live‑feed, OTT launch) face blockers and pending decisions that affect delivery schedules and vendor compliance.
|
||||
|
||||
---
|
||||
|
||||
# Wins 🏆
|
||||
- “Set‑focus” trigger in Storyline completed (on standby).
|
||||
- ONFR live‑feed testing to use Haywire feed; second Chorus URL deferred.
|
||||
- SPOF Job‑supervision solution approved; phased rollout begins with ONFR.
|
||||
- OTT search‑result ranking changes implemented; device testing underway.
|
||||
- Decision to retain WordPress on current site and keep WP Engine as host.
|
||||
- ZIP‑to‑Idéllo publishing workflow defined (ticket → ZIP → Hélène).
|
||||
- CTO approved exploratory discussion with Lunii.
|
||||
- Code freeze planned after fixing identified issues; phase‑2 isolated Boukili.
|
||||
|
||||
---
|
||||
|
||||
# Risks ⚠️
|
||||
- **Storyline “set‑focus”** compatibility with JAWS unknown → possible product delay.
|
||||
- **CRTC report** lacks clarity on retroactivity, content, and publication location; deadline 5 Oct pending.
|
||||
- Boukili v3 not ready; testing schedule launched.
|
||||
- **Variable episode lengths** may cause incorrect JWP recording stops → manual fixes needed.
|
||||
- **Subtitles** not displaying for test videos (missing collection association).
|
||||
- **JWP ingest point & billing** unclear for secondary feed; risk of unexpected fees.
|
||||
- **No staging server** for supervision‑solution testing → production issues possible.
|
||||
- **Boukili production DB & Contentful API** access unresolved, blocking full integration.
|
||||
- **Podcast automation** still depends on Jira API connection.
|
||||
- **Geo‑blocking** for TFO/Idéllo cannot be removed without release → legal compliance risk.
|
||||
- **Mogador synchronization** complexity; source‑of‑truth undefined, possible project removal.
|
||||
- **US‑based vendor compliance** (JWP, WP Engine, Algolia) under policy review.
|
||||
- **OTT delivery** at risk of missing live‑event deadline; may require weekend release.
|
||||
- **QA capacity** limited to one resource across four sites → testing delays.
|
||||
- **Firebase‑to‑AWS migration** (Boukili) blocked by data‑migration reliability and Salesforce regressions; production release cancelled.
|
||||
|
||||
---
|
||||
|
||||
# Team 👥
|
||||
|
||||
## Team health
|
||||
**Overall morale:** Not assessed.
|
||||
|
||||
### Coaching / Recognition
|
||||
- No explicit coaching or recognition items recorded.
|
||||
|
||||
---
|
||||
|
||||
# Projects 📁
|
||||
|
||||
| Project | Status | Next Milestone | Blocker |
|
||||
| --- | --- | --- | --- |
|
||||
| Boukili v3 | Testing started | Begin version 3 testing (this week) | Access to production DB & Contentful API; migration data‑validation issues |
|
||||
| Storyline “set‑focus” | Completed, on standby | Verify JAWS compatibility | Compatibility unknown |
|
||||
| ONFR live‑feed | Haywire feed selected for tests | End‑to‑end broadcast test (10 h start) | JWP ingest‑point behavior & billing clarification |
|
||||
| Job supervision solution | Approved, phased rollout | Deploy cron checks on ONFR | No staging server for testing |
|
||||
| OTT search‑result ranking | Changes applied | Complete multi‑device testing (incl. Apple TV zoom) | OTT testing timeline tight; risk to live event |
|
||||
| WordPress site | Hosting decision retained | Ongoing maintenance | None reported |
|
||||
| ZIP‑to‑Idéllo workflow | Defined | Start processing tickets after 12 Oct | None reported |
|
||||
| Lunii collaboration | Approved for exploratory talk | Present to CEO | Decision pending CEO review |
|
||||
| Mogador sync | Discussion scheduled 16 Sept | Resolve synchronization approach | Complexity & lack of source‑of‑truth |
|
||||
|
||||
---
|
||||
|
||||
# Vendors 🤝
|
||||
- **JWP**: Billing model for secondary feed unclear; ingest‑point behavior under review.
|
||||
- **WP Engine**: Hosting retained; no immediate issues.
|
||||
- **Algolia**: Regression review pending (Trings invoice unblocked).
|
||||
- **US‑based vendors** (JWP, WP Engine, Algolia) under compliance review per policy.
|
||||
|
||||
---
|
||||
|
||||
# Decisions Made
|
||||
- Keep Storyline “set‑focus” on standby until screen‑reader compatibility confirmed.
|
||||
- Use Haywire feed for ONFR testing; defer second Chorus URL.
|
||||
- Deploy supervision checks first on ONFR, then Idéllo, then TFO.
|
||||
- Maintain JWP 24/7 feed unchanged; manage secondary test feed manually.
|
||||
- Preserve Boukili on a dedicated VM; postpone API integration.
|
||||
- Retain WordPress on current site with WP Engine hosting.
|
||||
- Implement ZIP‑to‑Idéllo workflow with ticket‑based hand‑off to Hélène (start 12 Oct).
|
||||
- Approve exploratory Lunii discussion with CEO.
|
||||
- Code freeze after fixing identified issues; isolate phase‑2 work.
|
||||
|
||||
---
|
||||
|
||||
# Decisions Needed
|
||||
- Clarify CRTC report requirements (retroactivity, content, location) with Pierre‑Olivier.
|
||||
- Confirm JWP ingest‑point behavior and any secondary‑feed fees.
|
||||
- Decide if a second Corus URL will ever be purchased.
|
||||
- Determine final handling of ONFR live‑event streams (retain JWP vs. replace).
|
||||
- Approve Jira‑form design for automated podcast‑chain requests (feasibility with Marc).
|
||||
- Resolve geo‑blocking removal for TFO/Idéllo (legal compliance).
|
||||
- Finalize Mogador synchronization approach or project removal.
|
||||
- Choose which of the four technical subjects (retry, Firebase lockout, update‑message migration, Contentful version control) to include in next Boukili build.
|
||||
- Confirm migration‑forced strategy for multi‑device users and communication plan.
|
||||
- Approve additional QA resources or temporary reinforcement.
|
||||
|
||||
---
|
||||
|
||||
# Top Priorities Next Week
|
||||
1. Send clarification email to CRTC and follow up with Pierre‑Olivier.
|
||||
2. Begin Boukili v3 testing and map production‑DB fields.
|
||||
3. Execute end‑to‑end ONFR broadcast test and add supervision cron entries.
|
||||
4. Verify JWP secondary‑feed billing and ingest‑point details.
|
||||
5. Create test collection in JWP and confirm subtitle display.
|
||||
6. Conduct OTT multi‑device testing (including Apple TV zoom) for sign‑off.
|
||||
7. Prepare ZIP‑to‑Idéllo tickets (ready for 12 Oct start).
|
||||
|
||||
---
|
||||
|
||||
# CTO Development
|
||||
|
||||
**Leadership:** –
|
||||
**Technology:** –
|
||||
**Business:** –
|
||||
**Finance:** –
|
||||
**Communication:** –
|
||||
|
||||
*One thing I did this week that made me more like a CTO:* –
|
||||
*One thing I did this week that kept me acting like an individual contributor:* –
|
||||
Reference in New Issue
Block a user