diff --git a/personal/projects/personal-os/personal-os-action-plan-2026-10-05.md b/personal/projects/personal-os/personal-os-action-plan-2026-10-05.md index 0d9e69d4..3a0fae69 100644 --- a/personal/projects/personal-os/personal-os-action-plan-2026-10-05.md +++ b/personal/projects/personal-os/personal-os-action-plan-2026-10-05.md @@ -2,7 +2,7 @@ ## 18 ноября · Рабочая публикация исправлений и продолжение приёмки -Заказчик возобновил исправления и отдельно разрешил публикацию Personal OS. В Windmill опубликован E5 v207, сверены все 12 встроенных копий и схема. Доступность на будний день рассчитывается до 19:00 по Бишкеку; снятый лимит 90 минут удалён из рабочей настройки и инструкции Codex. Штатный проход, отрицательные случаи и незакрытые сценарии записаны в [журнале приёмки](personal-os-production-acceptance.md#18-ноября--проверка-рабочей-версии-e5-v207). [План D18](personal-os-remediation-plan-2026-11-18.md) +Заказчик возобновил исправления и отдельно разрешил публикацию Personal OS. В Windmill опубликован E5 v208, сверены все 12 встроенных копий и схема. Доступность на будний день рассчитывается до 19:00 по Бишкеку; снятый лимит 90 минут удалён из рабочей настройки и инструкции Codex. Штатный проход, отрицательные случаи и незакрытые сценарии записаны в [журнале приёмки](personal-os-production-acceptance.md#18-ноября--проверка-рабочей-версии-e5-v207). [План D18](personal-os-remediation-plan-2026-11-18.md) ## 18 ноября — U10/U13/U14: текущий приоритет, контракт действия и версия проверки diff --git a/personal/projects/personal-os/personal-os-first-day.md b/personal/projects/personal-os/personal-os-first-day.md index 89d3ba04..103cd6ac 100644 --- a/personal/projects/personal-os/personal-os-first-day.md +++ b/personal/projects/personal-os/personal-os-first-day.md @@ -2,7 +2,7 @@ ## 18 ноября · Рабочая публикация исправлений и продолжение приёмки -Заказчик возобновил исправления и отдельно разрешил публикацию Personal OS. В Windmill опубликован E5 v207, сверены все 12 встроенных копий и схема. Доступность на будний день рассчитывается до 19:00 по Бишкеку; снятый лимит 90 минут удалён из рабочей настройки и инструкции Codex. Штатный проход, отрицательные случаи и незакрытые сценарии записаны в [журнале приёмки](personal-os-production-acceptance.md#18-ноября--проверка-рабочей-версии-e5-v207). [План D18](personal-os-remediation-plan-2026-11-18.md) +Заказчик возобновил исправления и отдельно разрешил публикацию Personal OS. В Windmill опубликован E5 v208, сверены все 12 встроенных копий и схема. Доступность на будний день рассчитывается до 19:00 по Бишкеку; снятый лимит 90 минут удалён из рабочей настройки и инструкции Codex. Штатный проход, отрицательные случаи и незакрытые сценарии записаны в [журнале приёмки](personal-os-production-acceptance.md#18-ноября--проверка-рабочей-версии-e5-v207). [План D18](personal-os-remediation-plan-2026-11-18.md) Откройте [Мои задачи и план дня](http://127.0.0.1:4317/#/my-tasks?plan=1) в браузере на том Mac, где работает Personal OS. Интерфейс доступен для просмотра; начало рабочего пилота требует выполнимого плана с проверенными основаниями. Базовая настройка пилота — 90 минут до 19:00 по Бишкеку. diff --git a/personal/projects/personal-os/personal-os-fixes-2026-11-13.md b/personal/projects/personal-os/personal-os-fixes-2026-11-13.md index 855277a5..b3613d36 100644 --- a/personal/projects/personal-os/personal-os-fixes-2026-11-13.md +++ b/personal/projects/personal-os/personal-os-fixes-2026-11-13.md @@ -2,7 +2,7 @@ ## 18 ноября · Рабочая публикация исправлений и продолжение приёмки -Заказчик возобновил исправления и отдельно разрешил публикацию Personal OS. В Windmill опубликован E5 v207, сверены все 12 встроенных копий и схема. Доступность на будний день рассчитывается до 19:00 по Бишкеку; снятый лимит 90 минут удалён из рабочей настройки и инструкции Codex. Штатный проход, отрицательные случаи и незакрытые сценарии записаны в [журнале приёмки](personal-os-production-acceptance.md#18-ноября--проверка-рабочей-версии-e5-v207). [План D18](personal-os-remediation-plan-2026-11-18.md) +Заказчик возобновил исправления и отдельно разрешил публикацию Personal OS. В Windmill опубликован E5 v208, сверены все 12 встроенных копий и схема. Доступность на будний день рассчитывается до 19:00 по Бишкеку; снятый лимит 90 минут удалён из рабочей настройки и инструкции Codex. Штатный проход, отрицательные случаи и незакрытые сценарии записаны в [журнале приёмки](personal-os-production-acceptance.md#18-ноября--проверка-рабочей-версии-e5-v207). [План D18](personal-os-remediation-plan-2026-11-18.md) ## 18 ноября — U10/U13/U14: текущий приоритет, контракт действия и версия проверки diff --git a/personal/projects/personal-os/personal-os-implementation-audit-2026-11-13.md b/personal/projects/personal-os/personal-os-implementation-audit-2026-11-13.md index e7898502..a10db342 100644 --- a/personal/projects/personal-os/personal-os-implementation-audit-2026-11-13.md +++ b/personal/projects/personal-os/personal-os-implementation-audit-2026-11-13.md @@ -2,7 +2,7 @@ ## 18 ноября · Рабочая публикация исправлений и продолжение приёмки -Заказчик возобновил исправления и отдельно разрешил публикацию Personal OS. В Windmill опубликован E5 v207, сверены все 12 встроенных копий и схема. Доступность на будний день рассчитывается до 19:00 по Бишкеку; снятый лимит 90 минут удалён из рабочей настройки и инструкции Codex. Штатный проход, отрицательные случаи и незакрытые сценарии записаны в [журнале приёмки](personal-os-production-acceptance.md#18-ноября--проверка-рабочей-версии-e5-v207). [План D18](personal-os-remediation-plan-2026-11-18.md) +Заказчик возобновил исправления и отдельно разрешил публикацию Personal OS. В Windmill опубликован E5 v208, сверены все 12 встроенных копий и схема. Доступность на будний день рассчитывается до 19:00 по Бишкеку; снятый лимит 90 минут удалён из рабочей настройки и инструкции Codex. Штатный проход, отрицательные случаи и незакрытые сценарии записаны в [журнале приёмки](personal-os-production-acceptance.md#18-ноября--проверка-рабочей-версии-e5-v207). [План D18](personal-os-remediation-plan-2026-11-18.md) ## 18 ноября — U10/U13/U14: текущий приоритет, контракт действия и версия проверки diff --git a/personal/projects/personal-os/personal-os-production-acceptance.md b/personal/projects/personal-os/personal-os-production-acceptance.md index a8ca39e8..59f42bc4 100644 --- a/personal/projects/personal-os/personal-os-production-acceptance.md +++ b/personal/projects/personal-os/personal-os-production-acceptance.md @@ -1,5 +1,11 @@ # Personal OS — аудит и приёмка +## 18 ноября · Контрольный повтор E5 v208 + +В E5 v208 опубликовано условие первого самостоятельного шага для очереди уточнений. Прочитана опубликованная версия, сверены 12 встроенных копий. В штатной попытке `01a1ed2c-e634-cfbf-8637-83eb66118342` Hack Phase прошёл проверку источников, но получил оценку 240 минут при максимально допустимых 180. Повтор на том же рабочем входе и реальной локальной модели выдал отдельный аудит subframes, принятый проверкой контракта. Оценка составила 180 минут; факт трудозатрат ещё не измерялся. [Квитанция и подготовленный разбор](personal-os-evidence/2026-11-18/remediation-verified-pass.md) + +Штатный E5 `c057e2bf-7d1d-4185-bfba-8b66fa33b1f1` привязал PR #3727 к точной карточке Asana по совпадению ссылки и заголовка. У нового HEAD нет формального назначения, решение по замечаниям предыдущей версии остаётся открытым. Для независимого отрицательного случая подтверждён job #6839 на том же HEAD. Из лога извлечено падение testSlideToDeleteRequiresCompletedDrag с XCTAssertTrue failed. Красный статус #7385 по-прежнему отображается отдельно как проверка правил черновика. [Реальный лог #6839](https://github.com/duckduckgo/apple-browsers/actions/runs/44160534270/job/134317341355) + ## 18 ноября · Проверка рабочей версии E5 v207 **Полная приёмка продолжается.** После отдельного разрешения опубликованы E5 v206 и v207. Изменения ограничены потоком E5. В v207 совпали 12 встроенных копий и схема; остальные модули сохранены. [Квитанция публикации и проверок](personal-os-evidence/2026-11-18/remediation-verified-pass.md) diff --git a/personal/projects/personal-os/personal-os-remediation-plan-2026-11-18.md b/personal/projects/personal-os/personal-os-remediation-plan-2026-11-18.md index ec19518c..9ed089b6 100644 --- a/personal/projects/personal-os/personal-os-remediation-plan-2026-11-18.md +++ b/personal/projects/personal-os/personal-os-remediation-plan-2026-11-18.md @@ -1,6 +1,6 @@ # Personal OS — план исправлений по замечаниям заказчика 18 ноября 2026 -Статус на 18 ноября после возобновления — **исправления применяются, полная приёмка открыта**. Заказчик возобновил работы и явно разрешил публикацию всех правок Personal OS. Опубликован рабочий E5 v207, сверены 12 встроенных копий. Расписание разработки Codex остаётся приостановленным на время текущего прохода, штатные задания Windmill продолжаются. +Статус на 18 ноября после возобновления — **исправления применяются, полная приёмка открыта**. Заказчик возобновил работы и явно разрешил публикацию всех правок Personal OS. Опубликован рабочий E5 v208, сверены 12 встроенных копий. Расписание разработки Codex остаётся приостановленным на время текущего прохода, штатные задания Windmill продолжаются. Текущие доказательства собраны в [журнале приёмки](personal-os-production-acceptance.md) и [квитанции рабочего прохода](personal-os-evidence/2026-11-18/remediation-verified-pass.md). Первоначальный снимок ниже описывает состояние до возобновления. @@ -226,7 +226,7 @@ Проверка: настоящий упавший тест со ссылкой и логом; красный process gate без упавших тестов; старый результат для другого HEAD; отменённый запуск; недоступный лог; несколько разных причин. Карточка объясняет, что именно обнаружено, чем подтверждено, что требуется изменить и сколько личной работы осталось после доступного агенту разбора. -Статус: открыт. После команды СТОП выполнено только read-only уточнение фактов и дополнение плана; исправление классификации не выполнялось. +Статус после возобновления — рабочий PR #7385 отражён как черновик с отдельной проверкой правил. Обновление прошло в E5 v207. Рабочий лог #6839 подтвердил имя упавшего UI-теста и тип assertion. Отмена, смешанные причины и чужой HEAD покрыты изолированными проверками. ### D18-28 · Критерий результата не может быть технической заглушкой @@ -238,7 +238,7 @@ Проверка: для ответа указан конкретный вопрос, адресат и факт ответа; для документа — требуемые изменения и точный документ; для проверки — конкретная причина и повторный результат для нужного HEAD. Открытие ссылки, произвольный комментарий, непустой список `done_when` и та же общая фраза не закрывают действие. Проверка должна оценивать смысл, а не только наличие поля. Связано с D18-08–D18-10 и D18-23. -Статус: открыт. Код по этому замечанию после команды СТОП не изменялся. +Статус после возобновления — общий критерий и повтор заголовка больше не допускаются в план. На рабочем Postmortem проверены конкретные шаги, ссылка на документ и наблюдаемый итог. Полное подтверждение завершения для всех видов действий остаётся открытым. ## Порядок возобновления после нового разрешения diff --git a/personal/projects/personal-os/personal-os-user-scenarios.md b/personal/projects/personal-os/personal-os-user-scenarios.md index 5bf3787d..c51bfb89 100644 --- a/personal/projects/personal-os/personal-os-user-scenarios.md +++ b/personal/projects/personal-os/personal-os-user-scenarios.md @@ -2,9 +2,19 @@ ## 18 ноября · Рабочая публикация исправлений и продолжение приёмки -Заказчик возобновил исправления и отдельно разрешил публикацию Personal OS. В Windmill опубликован E5 v207, сверены все 12 встроенных копий и схема. Доступность на будний день рассчитывается до 19:00 по Бишкеку; снятый лимит 90 минут удалён из рабочей настройки и инструкции Codex. Штатный проход, отрицательные случаи и незакрытые сценарии записаны в [журнале приёмки](personal-os-production-acceptance.md#18-ноября--проверка-рабочей-версии-e5-v207). [План D18](personal-os-remediation-plan-2026-11-18.md) +Заказчик возобновил исправления и отдельно разрешил публикацию Personal OS. В Windmill опубликован E5 v208, сверены все 12 встроенных копий и схема. Доступность на будний день рассчитывается до 19:00 по Бишкеку; снятый лимит 90 минут удалён из рабочей настройки и инструкции Codex. Штатный проход, отрицательные случаи и незакрытые сценарии записаны в [журнале приёмки](personal-os-production-acceptance.md#18-ноября--проверка-рабочей-версии-e5-v207). [План D18](personal-os-remediation-plan-2026-11-18.md) +## 18 ноября · Рабочие контрольные варианты D18 + +- **U02 · Ожидание PR и диагностика проверки.** Вход — личные PR и ссылки из текущих Asana notes. Пройти #3727 через рабочий план и исходную карточку, сверить старый SHA review и текущий HEAD. Отрицательный случай — красный process gate у черновика #7385 и настоящий красный тест в другом PR. Факты двух ожиданий и классификация лога проверены. Автоматическая подготовка исправления для всех видов результатов открыта. +- **U13/U14 · Полезный план дня из проверенной недели.** Вход — 18 ноября, доступность до 19:00, заполненный Postmortem со сроком 19 ноября. На экране «Сегодня» проверить оба merge, конкретный итог и переход в точный документ. На «Неделе» найти то же действие за 18 ноября. Отрицательный случай — нулевой план v206 при достаточной доступности и удержание свежих ревью при пробеле Zoom. Путь Postmortem до рабочего дашборда и недели повторён, подтверждение завершения и будущие часы открыты. +- **U15 · Telegram и Mac.** Вход — допущенный план v207 и уже существующее личное сообщение. Проверить короткую сводку, ссылку «Сегодня» и одну попытку отправки, после изменения проверить ID сообщения. Отрицательные случаи — длинные заголовки, неопределённая доставка и задержка нативного сигнала. Telegram подтвердил правку сообщения; фактическое чтение, входящий ответ и нативное действие остаются открытыми. +- **U16/U17 · Самочувствие и перерыв.** Вход — форма, где сохранён автоматический режим до 19:00. Отдельно проверить сохранение самочувствия и доступности. Отрицательные случаи — неизвестная энергия и неуспешное чтение. Проверены гидратация в рабочем браузере и изолированные записи; полный рабочий день с реакцией на сигналы открыт. +- **U05/U11/U20 · История, процессы и результат.** Вход — история 17 ноября, контрольные задачи и отчёт проверки полей. Открыть результат и проверить родителя и первоисточник. Отрицательные случаи — неполная активность и исправленный TD, который больше не должен выдавать отсутствие Technical Designs. Рабочие запросы и контрольные источники прочитаны; весь набор типов и прохождение непройденных сценариев остаются открытыми. + +[Квитанция](personal-os-evidence/2026-11-18/remediation-verified-pass.md) · [Разбор источников](personal-os-evidence/2026-11-18/remediation-work-preparation.md) + ## 18 ноября — U10/U13/U14: текущий приоритет, контракт действия и версия проверки **Воспроизведение и выбор.** Проверенное личное действие с точной связью с действующим Top Priority исключалось из недели как `outside_weekly_scope`, когда не было отдельного pin или срока. [Одинаковый замороженный рабочий вход](personal-os-evidence/2026-11-18/source-priority-frozen-replay.json) прошёл E4 → неделю → дневной E5: до исправления 0 минут работы, после 60 и 27 минут резерва. Общий отбор расширен только для подтверждённой связи с действующим Top Priority: источник, тип цели и её версия проверяются в E4. Поле от модели без такой связи очищается. Срок, личный pin и выполненные зависимости не придумываются; прежние сроки, бюджеты и проверки свежести сохраняются. diff --git a/work/zoom-transcripts/2026-11-17 Apple Weekly Team Meeting - Zoom ID GJhjFoDDRY6PkqEUdM-YFg/transcript.json b/work/zoom-transcripts/2026-11-17 Apple Weekly Team Meeting - Zoom ID GJhjFoDDRY6PkqEUdM-YFg/transcript.json index 87102478..27046917 100644 --- a/work/zoom-transcripts/2026-11-17 Apple Weekly Team Meeting - Zoom ID GJhjFoDDRY6PkqEUdM-YFg/transcript.json +++ b/work/zoom-transcripts/2026-11-17 Apple Weekly Team Meeting - Zoom ID GJhjFoDDRY6PkqEUdM-YFg/transcript.json @@ -23,6 +23,231 @@ "time": "21:01:11", "speaker": "Pikor", "text": "Yep. Sorry, but I just realized that if you tap on that green camera icon on the status bar, then you have this recenter button within your preview and then there is the zoom. So you can zoom yourself like crazy." + }, + { + "time": "21:01:29", + "speaker": "Jonathan Jackson", + "text": "Yeah, that's the effect." + }, + { + "time": "21:01:32", + "speaker": "Pikor", + "text": "So this is fun. Yeah, Jorge likes it as well, as I see." + }, + { + "time": "21:01:36", + "speaker": "Andre Martingo", + "text": "Hello!" + }, + { + "time": "21:01:39", + "speaker": "Jonathan Jackson", + "text": "Hey, folks." + }, + { + "time": "21:01:40", + "speaker": "Pete Smith", + "text": "Igor, please do that at appropriate moments when you're giving your reaction to an inappropriate comment." + }, + { + "time": "21:01:45", + "speaker": "Pikor", + "text": "Okay." + }, + { + "time": "21:01:45", + "speaker": "Jonathan Jackson", + "text": "Yeah, right. All right, looks like we got a pretty good crew when we get started. Quick cruise through the rotations as usual. iOS Triage, Pico, you're on this week. Cue the Zooming. Jacek, you're up next week. Followed by L the week after that. There it is. Mac OS triage is on this week, followed by Sabrina and then Fernando. For iOS release, Pao is handling this week, followed by Hanyu and then Sam. And then macOS release, I actually don't know who's on because the task is closed this week already, but I hope that means that they know. Juan will be covering next week and then Dominic the week after that. As usual, any collisions, please let me know. Yep." + }, + { + "time": "21:02:58", + "speaker": "Fernando Bunn", + "text": "Pardon? Yeah, I'm out for two weeks, starting next week, so… No. Yep." + }, + { + "time": "21:03:08", + "speaker": "Jonathan Jackson", + "text": "Okay, we should find you a replacement for that week." + }, + { + "time": "21:03:12", + "speaker": "Fernando Bunn", + "text": "All right." + }, + { + "time": "21:03:13", + "speaker": "Jonathan Jackson", + "text": "Okay. See if you can trade with somebody nearby as a starting place." + }, + { + "time": "21:03:15", + "speaker": "Pete Smith", + "text": "Equip." + }, + { + "time": "21:03:19", + "speaker": "Jonathan Jackson", + "text": "Cool. Thanks." + }, + { + "time": "21:03:19", + "speaker": "Pete Smith", + "text": "Sorry to interrupt. Jonathan, a quick question about the…" + }, + { + "time": "21:03:21", + "speaker": "Jonathan Jackson", + "text": "Yep." + }, + { + "time": "21:03:23", + "speaker": "Pete Smith", + "text": "the holiday rotation, so I just… I'm one of the people with a big X beside my name, so I definitely won't be there, but just to make sure I understand, because I read the task, but there's no ask from, uh, the people who are actually on rotation at the moment, right? I mean, you are…" + }, + { + "time": "21:03:25", + "speaker": "Jonathan Jackson", + "text": "Yeah. Yep." + }, + { + "time": "21:03:38", + "speaker": "Pete Smith", + "text": "As far as I understand, you're taking care of finding…" + }, + { + "time": "21:03:41", + "speaker": "Jonathan Jackson", + "text": "I'm gonna start some conversations next. I was gonna do that yesterday when I was out. Um, but yeah, I think the task is settled enough that the next step is to… to try to get those conversations rolling, and I'll do that piece. Um, I'll probably need your help to think about which other week you would take to swap in, but…" + }, + { + "time": "21:03:41", + "speaker": "Pete Smith", + "text": "Or you're taking care of something." + }, + { + "time": "21:03:56", + "speaker": "Jonathan Jackson", + "text": "Yeah, I'm gonna get those rolling soon. And Pete, you are up first on the agenda." + }, + { + "time": "21:04:11", + "speaker": "Pete Smith", + "text": "Yeah, thanks. I forget what I wrote. Oh, yeah. OJ will begin — this is just an announcement or an FYI, an early announcement because we're just thinking about this now. So OJ is going to begin testing auto. So the auto deductor go harness, as it's also known, we're going to start testing that in OJ. And what that practically means is, so, uh, within OJ, we'll identify projects or tasks on the critical path that we think are low risk, so, like, low risk, maybe, you know, meaning limited blast radius or well-defined requirements, and then the. uh, project DRI, so, like, an engineer, one of the engineers in OJ will hand that work to Otto, so not that different to what everybody's doing at the moment in terms of just using agents to build. Uh, Otto would implement and open the PR, and then the project DRI, so the same person that handed the work to Otto. They will review the pull request and they will leave any comments which Auto or the agent will then deal with and will iterate until the PRO is ready and the project DRA will then merge the PRO. So that's the current plan. So I guess the difference there is that, you know, rather than the current state, where we work with agents to build it, and we ask another person to review it. it's the project DRI, the person who gave the prompt to Otto, and let it work completely on its own. They'll review the PR. So that's where we're going to start testing. This is happening in some other objectives, it's already happened in some other objectives, or started, but it's a way to test. um… I guess, auto." + }, + { + "time": "21:05:56", + "speaker": "Jonathan Jackson", + "text": "All right, thanks for the heads up." + }, + { + "time": "21:05:57", + "speaker": "Pete Smith", + "text": "That's the thought that. Yeah." + }, + { + "time": "21:06:00", + "speaker": "Jonathan Jackson", + "text": "I'll look forward to hearing how it goes, for sure. Uh, yeah, Sick, your topic is next." + }, + { + "time": "21:06:12", + "speaker": "JŁ", + "text": "Okay, so I had an idea for how to better present apple release strain. So we still have it in like a static form on Asana and we know how it works, but often people outside of our team don't. And I decided to use an artifact for that. It's still a work in progress, so I will expect some feedback. Let me share. Is it this one? Okay, I think it's this one. So I created this artifact that, like, you can share with anyone. Eh… And basically what it shows you is what version is currently in the store. What version is, like, reaching users, like, on the given day, and what version is in internal testing? You can tap on any version, and you can see, like, all the info that was in Asana, so, like, release notes, when it was cut from main, how it's rolling out, when it is going to be released to any person. You can see what flags depend on that version, and you can see all the changes here as well. Everything is, like, clickable, including, like, pull requests, so you can reach that. Mm-hmm. And… Then you have a schedule in a list, so you can show it to someone, so they know when each thing is going to be released. You can. change the view to the timeline, and on hover see when anything is released. And it includes the holiday break, too. On the calendar, you can also see it in this form, so you see when every version is going to be released. like each month. And then there are feature flags. So you see what feature flags are. On what percentage? And… So again, you, you know, if something is released to people or not, and you can also search. So for instance, I know that Bartosz was doing some background task thing, and if you like, search for it either by URL or link. It will show the thing, it will show you in which version it was released, what's the current running out status. And also you will see feature flags that were included. So you see this feature flag is only like released to 1% for this feature. So, uh, you can quickly see what is going on. And it also supports macOS, so, uh… yeah, like, probably still some things to polish. let me know if it's going to work for you or not. Thank you." + }, + { + "time": "21:08:55", + "speaker": "Jonathan Jackson", + "text": "I think it's probably going to work for pretty much everybody. That's amazing. Well done. Um, I think you might want to, you know, maybe have us spend a couple of weeks with it to make sure it's not…" + }, + { + "time": "21:08:59", + "speaker": "Andre Martingo", + "text": "Thank you." + }, + { + "time": "21:09:06", + "speaker": "Jonathan Jackson", + "text": "lying to people, you know, they're not… they're not using it, but yeah, I totally agree. People are suggesting sharing it at all hands, adding it to go.go.com, like, I think you should take it to a point where it's… where we're confident in it, and then definitely share it." + }, + { + "time": "21:09:07", + "speaker": "JŁ", + "text": "Yeah, yeah, sure." + }, + { + "time": "21:09:19", + "speaker": "Jonathan Jackson", + "text": "And think about connecting to Android and Windows as well once you're ready." + }, + { + "time": "21:09:25", + "speaker": "JŁ", + "text": "Sure, sure." + }, + { + "time": "21:09:26", + "speaker": "Jonathan Jackson", + "text": "Bartek, if you want to create an incident for us, you're welcome to." + }, + { + "time": "21:09:26", + "speaker": "Andre Martingo", + "text": "Good. Just a comment. Super nice. It's interesting because I was checking as well. I don't know if you saw the Windows release what they call a comment center. They have kind of an internal website. that contains… like, I think what you built plus more steps, um, and it was something that I was looking at once I finished Smartling, so I will get in touch with you. I don't know… at this point, what's the difference between an artifact or a web page itself, uh, inside of DuckDuckGo, but it's something, uh, that maybe we can… we can chat afterwards. Uh, but it's quite nice as well. Nice." + }, + { + "time": "21:10:18", + "speaker": "Jonathan Jackson", + "text": "Cool. Thank you. Jacek, when you're ready, it'd be great if you could share that with the team as a starting place, obviously." + }, + { + "time": "21:10:24", + "speaker": "JŁ", + "text": "Sure, sure." + }, + { + "time": "21:10:25", + "speaker": "Jonathan Jackson", + "text": "Cool. Uh, Andre, your SmartLink update is up next." + }, + { + "time": "21:10:31", + "speaker": "Andre Martingo", + "text": "So yeah, just a quick update. So everything should be done. I made a post. Me and Pao, we already kind of enabled or kind of disabled the Avenger warning. So I hope you'll start merging into main your untranslated strings. I have here as well an artifact since it's the new cool thing to do. Um… So basically, it was just an exploration about… how much we were spending per release in SmartLink, so maybe this will help us to move to AI, but other than that, it was to track. when are we starting using, kind of, the new flow. So, basically, here you have a graph of spending per release in terms of dollars, and the blue bars are, kind of, our new automatic flow. Um, so we are spending an average of, like, 500, 400, depending on the release. Um, and basically, here in this artifact, you can see, like. Which ones are the jobs that got merged automatically, or which ones are manual, so we can still… we can track, like, the usage of our new flow. And hopefully, maybe with some data, we can start thinking if it would be possible to move to AI, compare the prices, or maybe just A/B test for one language. It's something for the future we can maybe try to push for. But for now, it's just to collect… some stats so we can have better discussions over it." + }, + { + "time": "21:12:10", + "speaker": "Jonathan Jackson", + "text": "That's cool. Thank you. Yeah, if you want to share that somewhere so that people can find it on a regular basis, that'd be great. How have you seen, I know it's early, but on the nightly untranslated pieces, how quickly have those jobs from SmartLine been coming back?" + }, + { + "time": "21:12:31", + "speaker": "Andre Martingo", + "text": "Sorry, which ones?" + }, + { + "time": "21:12:33", + "speaker": "Jonathan Jackson", + "text": "You're basically doing a job every night with whatever was untranslated, right?" + }, + { + "time": "21:12:39", + "speaker": "Andre Martingo", + "text": "Also, but we do every merge commit as well. So basically, once you merge, we trigger a job, and the nightly will… if something goes wrong, it will pick up as well. So the blue bars are kind of the new flow, yeah." + }, + { + "time": "21:12:48", + "speaker": "Jonathan Jackson", + "text": "Oh, okay. Well, either one. Yeah. Presumably, those are usually smaller jobs for SmartLink. I was wondering how quickly they'd been turning those around recently." + }, + { + "time": "21:13:00", + "speaker": "Andre Martingo", + "text": "Yeah, actually, we have another one where we have the kind of turnover of PRs for Smartling, but I will share afterwards once we have more data. We didn't have much, no." + }, + { + "time": "21:13:07", + "speaker": "Jonathan Jackson", + "text": "Mm-hmm. Okay. Yeah, I know it's early still. All right, cool. Thank you. Um… That's our planned agenda for the day. Any other thoughts, questions, comments, things to share, demos? All right. A quick meeting today, but some good stuff. Thank you, everyone. Good to see you, and I hope you have a good day." } ] } diff --git a/work/zoom-transcripts/2026-11-17 Apple Weekly Team Meeting - Zoom ID GJhjFoDDRY6PkqEUdM-YFg/transcript.md b/work/zoom-transcripts/2026-11-17 Apple Weekly Team Meeting - Zoom ID GJhjFoDDRY6PkqEUdM-YFg/transcript.md index 9ff5c167..9022f094 100644 --- a/work/zoom-transcripts/2026-11-17 Apple Weekly Team Meeting - Zoom ID GJhjFoDDRY6PkqEUdM-YFg/transcript.md +++ b/work/zoom-transcripts/2026-11-17 Apple Weekly Team Meeting - Zoom ID GJhjFoDDRY6PkqEUdM-YFg/transcript.md @@ -15,3 +15,48 @@ source: "https://us01mynotes.zoom.us/GJhjFoDDRY6PkqEUdM-YFg" - **21:01:06 · Jonathan Jackson:** Pico, you're uh… Camera Zoom is doing, I don't know, it's like an old 1950s horror movie. - **21:01:10 · Pete Smith:** And you… - **21:01:11 · Pikor:** Yep. Sorry, but I just realized that if you tap on that green camera icon on the status bar, then you have this recenter button within your preview and then there is the zoom. So you can zoom yourself like crazy. +- **21:01:29 · Jonathan Jackson:** Yeah, that's the effect. +- **21:01:32 · Pikor:** So this is fun. Yeah, Jorge likes it as well, as I see. +- **21:01:36 · Andre Martingo:** Hello! +- **21:01:39 · Jonathan Jackson:** Hey, folks. +- **21:01:40 · Pete Smith:** Igor, please do that at appropriate moments when you're giving your reaction to an inappropriate comment. +- **21:01:45 · Pikor:** Okay. +- **21:01:45 · Jonathan Jackson:** Yeah, right. All right, looks like we got a pretty good crew when we get started. Quick cruise through the rotations as usual. iOS Triage, Pico, you're on this week. Cue the Zooming. Jacek, you're up next week. Followed by L the week after that. There it is. Mac OS triage is on this week, followed by Sabrina and then Fernando. For iOS release, Pao is handling this week, followed by Hanyu and then Sam. And then macOS release, I actually don't know who's on because the task is closed this week already, but I hope that means that they know. Juan will be covering next week and then Dominic the week after that. As usual, any collisions, please let me know. Yep. +- **21:02:58 · Fernando Bunn:** Pardon? Yeah, I'm out for two weeks, starting next week, so… No. Yep. +- **21:03:08 · Jonathan Jackson:** Okay, we should find you a replacement for that week. +- **21:03:12 · Fernando Bunn:** All right. +- **21:03:13 · Jonathan Jackson:** Okay. See if you can trade with somebody nearby as a starting place. +- **21:03:15 · Pete Smith:** Equip. +- **21:03:19 · Jonathan Jackson:** Cool. Thanks. +- **21:03:19 · Pete Smith:** Sorry to interrupt. Jonathan, a quick question about the… +- **21:03:21 · Jonathan Jackson:** Yep. +- **21:03:23 · Pete Smith:** the holiday rotation, so I just… I'm one of the people with a big X beside my name, so I definitely won't be there, but just to make sure I understand, because I read the task, but there's no ask from, uh, the people who are actually on rotation at the moment, right? I mean, you are… +- **21:03:25 · Jonathan Jackson:** Yeah. Yep. +- **21:03:38 · Pete Smith:** As far as I understand, you're taking care of finding… +- **21:03:41 · Jonathan Jackson:** I'm gonna start some conversations next. I was gonna do that yesterday when I was out. Um, but yeah, I think the task is settled enough that the next step is to… to try to get those conversations rolling, and I'll do that piece. Um, I'll probably need your help to think about which other week you would take to swap in, but… +- **21:03:41 · Pete Smith:** Or you're taking care of something. +- **21:03:56 · Jonathan Jackson:** Yeah, I'm gonna get those rolling soon. And Pete, you are up first on the agenda. +- **21:04:11 · Pete Smith:** Yeah, thanks. I forget what I wrote. Oh, yeah. OJ will begin — this is just an announcement or an FYI, an early announcement because we're just thinking about this now. So OJ is going to begin testing auto. So the auto deductor go harness, as it's also known, we're going to start testing that in OJ. And what that practically means is, so, uh, within OJ, we'll identify projects or tasks on the critical path that we think are low risk, so, like, low risk, maybe, you know, meaning limited blast radius or well-defined requirements, and then the. uh, project DRI, so, like, an engineer, one of the engineers in OJ will hand that work to Otto, so not that different to what everybody's doing at the moment in terms of just using agents to build. Uh, Otto would implement and open the PR, and then the project DRI, so the same person that handed the work to Otto. They will review the pull request and they will leave any comments which Auto or the agent will then deal with and will iterate until the PRO is ready and the project DRA will then merge the PRO. So that's the current plan. So I guess the difference there is that, you know, rather than the current state, where we work with agents to build it, and we ask another person to review it. it's the project DRI, the person who gave the prompt to Otto, and let it work completely on its own. They'll review the PR. So that's where we're going to start testing. This is happening in some other objectives, it's already happened in some other objectives, or started, but it's a way to test. um… I guess, auto. +- **21:05:56 · Jonathan Jackson:** All right, thanks for the heads up. +- **21:05:57 · Pete Smith:** That's the thought that. Yeah. +- **21:06:00 · Jonathan Jackson:** I'll look forward to hearing how it goes, for sure. Uh, yeah, Sick, your topic is next. +- **21:06:12 · JŁ:** Okay, so I had an idea for how to better present apple release strain. So we still have it in like a static form on Asana and we know how it works, but often people outside of our team don't. And I decided to use an artifact for that. It's still a work in progress, so I will expect some feedback. Let me share. Is it this one? Okay, I think it's this one. So I created this artifact that, like, you can share with anyone. Eh… And basically what it shows you is what version is currently in the store. What version is, like, reaching users, like, on the given day, and what version is in internal testing? You can tap on any version, and you can see, like, all the info that was in Asana, so, like, release notes, when it was cut from main, how it's rolling out, when it is going to be released to any person. You can see what flags depend on that version, and you can see all the changes here as well. Everything is, like, clickable, including, like, pull requests, so you can reach that. Mm-hmm. And… Then you have a schedule in a list, so you can show it to someone, so they know when each thing is going to be released. You can. change the view to the timeline, and on hover see when anything is released. And it includes the holiday break, too. On the calendar, you can also see it in this form, so you see when every version is going to be released. like each month. And then there are feature flags. So you see what feature flags are. On what percentage? And… So again, you, you know, if something is released to people or not, and you can also search. So for instance, I know that Bartosz was doing some background task thing, and if you like, search for it either by URL or link. It will show the thing, it will show you in which version it was released, what's the current running out status. And also you will see feature flags that were included. So you see this feature flag is only like released to 1% for this feature. So, uh, you can quickly see what is going on. And it also supports macOS, so, uh… yeah, like, probably still some things to polish. let me know if it's going to work for you or not. Thank you. +- **21:08:55 · Jonathan Jackson:** I think it's probably going to work for pretty much everybody. That's amazing. Well done. Um, I think you might want to, you know, maybe have us spend a couple of weeks with it to make sure it's not… +- **21:08:59 · Andre Martingo:** Thank you. +- **21:09:06 · Jonathan Jackson:** lying to people, you know, they're not… they're not using it, but yeah, I totally agree. People are suggesting sharing it at all hands, adding it to go.go.com, like, I think you should take it to a point where it's… where we're confident in it, and then definitely share it. +- **21:09:07 · JŁ:** Yeah, yeah, sure. +- **21:09:19 · Jonathan Jackson:** And think about connecting to Android and Windows as well once you're ready. +- **21:09:25 · JŁ:** Sure, sure. +- **21:09:26 · Jonathan Jackson:** Bartek, if you want to create an incident for us, you're welcome to. +- **21:09:26 · Andre Martingo:** Good. Just a comment. Super nice. It's interesting because I was checking as well. I don't know if you saw the Windows release what they call a comment center. They have kind of an internal website. that contains… like, I think what you built plus more steps, um, and it was something that I was looking at once I finished Smartling, so I will get in touch with you. I don't know… at this point, what's the difference between an artifact or a web page itself, uh, inside of DuckDuckGo, but it's something, uh, that maybe we can… we can chat afterwards. Uh, but it's quite nice as well. Nice. +- **21:10:18 · Jonathan Jackson:** Cool. Thank you. Jacek, when you're ready, it'd be great if you could share that with the team as a starting place, obviously. +- **21:10:24 · JŁ:** Sure, sure. +- **21:10:25 · Jonathan Jackson:** Cool. Uh, Andre, your SmartLink update is up next. +- **21:10:31 · Andre Martingo:** So yeah, just a quick update. So everything should be done. I made a post. Me and Pao, we already kind of enabled or kind of disabled the Avenger warning. So I hope you'll start merging into main your untranslated strings. I have here as well an artifact since it's the new cool thing to do. Um… So basically, it was just an exploration about… how much we were spending per release in SmartLink, so maybe this will help us to move to AI, but other than that, it was to track. when are we starting using, kind of, the new flow. So, basically, here you have a graph of spending per release in terms of dollars, and the blue bars are, kind of, our new automatic flow. Um, so we are spending an average of, like, 500, 400, depending on the release. Um, and basically, here in this artifact, you can see, like. Which ones are the jobs that got merged automatically, or which ones are manual, so we can still… we can track, like, the usage of our new flow. And hopefully, maybe with some data, we can start thinking if it would be possible to move to AI, compare the prices, or maybe just A/B test for one language. It's something for the future we can maybe try to push for. But for now, it's just to collect… some stats so we can have better discussions over it. +- **21:12:10 · Jonathan Jackson:** That's cool. Thank you. Yeah, if you want to share that somewhere so that people can find it on a regular basis, that'd be great. How have you seen, I know it's early, but on the nightly untranslated pieces, how quickly have those jobs from SmartLine been coming back? +- **21:12:31 · Andre Martingo:** Sorry, which ones? +- **21:12:33 · Jonathan Jackson:** You're basically doing a job every night with whatever was untranslated, right? +- **21:12:39 · Andre Martingo:** Also, but we do every merge commit as well. So basically, once you merge, we trigger a job, and the nightly will… if something goes wrong, it will pick up as well. So the blue bars are kind of the new flow, yeah. +- **21:12:48 · Jonathan Jackson:** Oh, okay. Well, either one. Yeah. Presumably, those are usually smaller jobs for SmartLink. I was wondering how quickly they'd been turning those around recently. +- **21:13:00 · Andre Martingo:** Yeah, actually, we have another one where we have the kind of turnover of PRs for Smartling, but I will share afterwards once we have more data. We didn't have much, no. +- **21:13:07 · Jonathan Jackson:** Mm-hmm. Okay. Yeah, I know it's early still. All right, cool. Thank you. Um… That's our planned agenda for the day. Any other thoughts, questions, comments, things to share, demos? All right. A quick meeting today, but some good stuff. Thank you, everyone. Good to see you, and I hope you have a good day. diff --git a/work/zoom-transcripts/index.json b/work/zoom-transcripts/index.json index 9fe58d26..2683c8ec 100644 --- a/work/zoom-transcripts/index.json +++ b/work/zoom-transcripts/index.json @@ -386,8 +386,8 @@ "note_modified_at": "2026-11-17T15:00:56.296Z", "source_url": "https://us01mynotes.zoom.us/GJhjFoDDRY6PkqEUdM-YFg", "folder": "2026-11-17 Apple Weekly Team Meeting - Zoom ID GJhjFoDDRY6PkqEUdM-YFg", - "sha256": "22c2c60c7a01fe8692c3e347c12beaa43102161292c468734320db978739bb11", - "cues": 3 + "sha256": "cd06af7a61ede6d4cd5d78b6ed94d9c6650c99a66d637cdf0e2eba0fef6390c5", + "cues": 48 } } }