[2026-11-20] eagle: personal/projects/personal-os/personal-os-evidence/2026-11-19/follow-up-live-acceptance.md personal/projects/personal-os/personal-os-production-acceptance.md personal/projects/personal-os/personal-os-project-management.md personal/projects/personal-os/personal-os-remediation-plan-2026-11-18.md personal/projects/personal-os/personal-os-user-scenarios.md personal/projects/personal-os/project-management-rules.json work/zoom-transcripts/2026-10-16 All-Company Meeting 2026-10-16 21 31(GMT+6 00) klekRLtLSEuMv0PCCPCjtA/transcript.json work/zoom-transcripts/2026-10-16 All-Company Meeting 2026-10-16 21 31(GMT+6 00) klekRLtLSEuMv0PCCPCjtA/transcript.md work/zoom-transcripts/2026-10-19 Michal Smaga's Personal Meeting Room QvxllpCuTTSLGEZp-R6jQw/transcript.json work/zoom-transcripts/2026-10-19 Michal Smaga's Personal Meeting Room QvxllpCuTTSLGEZp-R6jQw/transcript.md
This commit is contained in:
1 parent
d4d2e4dc52
commit
78718d2e8a
12 files changed
+916
-10
No files matched your search
+6
@@ -1292,3 +1292,9 @@
|
||||
- GitHub для PR #8374 на `991fa98f790d` вернул два текущих обсуждения и пять устаревших незакрытых нитей. Ранее счётчик показывал семь. В новом расчёте совпадают число, коммит и ссылки. Детали прикрепляются только после полного чтения нитей на том же HEAD. [Растеризация](https://github.com/duckduckgo/apple-browsers/pull/8374#discussion_r4643674203) · [Тестовые случаи](https://github.com/duckduckgo/apple-browsers/pull/8374#discussion_r4643674224)
|
||||
- GitHub отдельно подтвердил завершение Test (Non-Sandbox) с ошибкой на том же коммите. В очереди виден следующий шаг со ссылкой на точный job. Причина сбоя остаётся открытой. Рабочий E5 `aff3ecaf-61ae-4b4a-81c8-f701776a2c45` завершился за 68,281 секунды. При 1280 и 390 px после открытия и перезагрузки разобраны оба замечания, их файлы, автор и лог. Карточка осталась удержанной. [Тестовый лог](https://github.com/duckduckgo/apple-browsers/actions/runs/44772225144/job/136412644616) · [Очередь](http://127.0.0.1:4317/#/task-queue?action=github-work%3Aduckduckgo%2Fapple-browsers%238374)
|
||||
- Отдельные проходы D18-201 и D18-202 вновь подтвердили ожидание CPM до возобновления DNR и две задачи в датированной встрече CPM. В истории сохранены реплики в 22:15:01 и срок анализа 4 декабря. Asana подтвердила открытый анализ и паузу DNR. [Ожидание](http://127.0.0.1:4317/#/task-queue?action=project-management%3Acloseout-cleanup%3A1216761517055116%3A1216262985473637%3Ablocker) · [История CPM](http://127.0.0.1:4317/#/work-history?date=2026-11-19&episode=zoom%3AnExkucRLSESP9SkgIBfCyg)
|
||||
|
||||
## Подготовка назначенного Midmortem
|
||||
|
||||
- Asana подтвердила три завершённых Midmortem CPM. В Mid-mortem 2 от 6 октября сохранены связь с проектом и точная повестка O‑E Weekly. В карточке нет точного времени и членства в реестре Midmortem. В исходной повестке пусты Risks / blockers и Path forward. Действующий шаблон отделяет Recap, который заполняется на созвоне. [Mid-mortem 2](https://app.asana.com/0/0/1219230836268250) · [Повестка](https://app.asana.com/0/0/1219009129735524) · [Шаблон](https://app.asana.com/0/0/1203886245376707)
|
||||
- На копии этой карточки с открытой стадией и временем наблюдения до встречи обычный путь показал два пустых раздела, нужный реестр и уточнение времени. Прямые ссылки проверены при 1280 и 390 px после открытия и перезагрузки. После контрольного заполнения и подтверждения слота карточка скрылась. Завершённый проект, пауза и прошедший слот исключили подготовку. В графике Asana отдельно проверен заголовок Mid-mortem с дефисом. Исходные карточки Asana сохранены.
|
||||
- Рабочий E5 `a5ea209b-e47f-4e18-a21c-3392a9b03171` опубликовал версию 7 за 78,232 секунды. На живом портале правило и точный шаблон открыты после первой загрузки и перезагрузки при обеих ширинах. У действующего Top Priority отсутствует открытый назначенный Midmortem, ложных карточек нет. C-S-S на паузе, Kick-off без даты. Автоматический выбор нового Midmortem и сверка приглашённых остаются открытыми.
|
||||
@@ -211,7 +211,7 @@
|
||||
|
||||
102. В «Неделе» видны последние сохранённые решения, время и состояние обзора. При смене источника пояснение доступно рядом с прежней записью. Сохранение, чтение файла решения и отказ устаревшей попытки проверены на отдельном наборе. В рабочем портале проверен исходный пустой раздел и два повтора с контрольным ответом для 1280 и 390 px. Реальная запись владельца отсутствовала. [Доказательства](personal-os-evidence/2026-11-19/follow-up-live-acceptance.md#решения-недельного-обзора-после-сохранения)
|
||||
103. D18-200 открыт. В живой очереди проверены фильтры, переход из «Недели», пять продолжений CPM, три реестра Asana и десять источников GitHub. На копии реальной карточки бенчмарков проверены явный результат, попадание в оба плана, исключение дубля и отзыв решения. Незакрытые TD, Ship Review и PR прошли оба плана на контрольных копиях из первоисточников. Поздний ответ владельца исключает конкретный отвеченный вопрос. Нумерованный ответ владельца по HTML-списку исключил три старых вопроса TD. Штатная модель выбрала открытый запрос по запуску iOS. В Ship Review проверено имя из первичного комментария. Полный проход свежего Current Objectives завершён для всех 393 записей. На копиях проверены применение и фильтр O‑B и O‑5. Первый разбор общего каталога завершился на 356 записях, расширение на 383. Живой каталог включает 13 репозиториев, в трёх новых источниках первично сверены 27 открытых PR. Первое открытие охвата показывает ход фоновой сверки менее чем за секунду. После исправления обработки ответов GitHub к 21:28 по Бишкеку разобраны все 379 записей нового снимка, 349 результатов переиспользованы. В предпросмотре 31 совпадение, 344 исключения, четыре неопределённых. Ошибочное предложение PR #44 исключено. Свежие обсуждения Asana обнаружили два предложения без открытого вопроса. Исправление исключает их и сохраняет свежий вопрос в конце длинного комментария. Оба пути проверены на копии. Начат повторный разбор подтверждённых 51 ревью Asana с сохранением 328 результатов GitHub. К 22:08 в нём обработано 379 из 379. Сверка четырёх Asana-совпадений выявила ответ в строке шаблона и общую просьбу о замечаниях. Оба источника исключены в контрольном повторе, конкретный вопрос сохранён. Повторный разбор к 22:36 завершил все 378 карточек снимка. Проверены 50 Asana и 328 GitHub. Отдельный прогон с новой проверкой удержал TD уведомлений, а по вопросу о пикселях дал иной вердикт. Стабильность отбора по свободной форме открыта. В журнале удержаны оба ложных предложения из шаблона и общей просьбы. Найдено третье устаревшее предложение в TD уведомлений. На копии прежняя карточка исчезает при обновлении, конкретное позднее возражение отображается с прямой ссылкой после применения контрольного ответа. Отдельный тайм-аут Node устранён. На копии проверены сохранение локальной отметки и повтор только по оставшейся карточке с вопросом. Решения владельца и ответы свободной формы без однозначной связи остаются открытыми. [План](personal-os-tasks.md) · [Доказательства](personal-os-evidence/2026-11-19/follow-up-live-acceptance.md#подтверждение-предложения-из-общего-каталога)
|
||||
104. D18-201 открыт. В живой очереди сверены Kick-off C-S-S с результатом Hack Phase, зависимость замеров, вопрос о скрытых страницах macOS и запрос Advisor. Для текущего Kick-off по iOS проверены дата, слот O‑B Weekly, общий тест с FE и форма подтверждения. На копии действующего частично заполненного Kick-off появляется только черновик Next steps. После штатного пересчёта живой iOS Kick-off сохранил четыре раздела для исходной заготовки. Два итога iOS без оставшихся действий сверены с Asana. На копии незакреплённый итог даёт ссылку на опубликованный комментарий. Рабочий CPM сохранил подтверждение закрепления без повторного действия. При паузе DNR открытый вопрос о блокировке CPM сохранил прежний идентификатор и обе ссылки. Живой портал показывает ожидание возобновления без срока. Допуск того же шага в оба плана, смена версии и снятие решения прошли на изолированной копии. Реального решения в рабочем журнале пока нет. На копии CPM проверена настройка интервала DRI ↔ PA и ссылка на последнее обновление. Рабочий интервал пока не задан. Открыты адресное уведомление, рабочий календарь Outlook, пересечения без общей ссылки, Running и теги AoR. Точное членство в macOS App Development устанавливает AoR Work по действующему руководству. Рабочий E5 и оба прохода в портале подтвердили категорию, точные ссылки и прежнее удержание двух задач. [Проверка AoR Work](personal-os-evidence/2026-11-19/follow-up-live-acceptance.md#категория-aor-по-рабочей-доске) Назначение Advisor сохраняется после контрольного закрытия Kick-off для iOS и C-S-S. Закрытие самого проекта снимает шаг. В 23:09 повторно подтверждены пауза DNR и ожидание в очереди. Для встреч используются рабочий календарь и Asana. Чтение писем исключено. На «Сегодня» и в Weekly Review повторно сверены ссылки O‑B Weekly, Career Advisor и Apple Weekly с первичными датами Asana. [Доказательства и этапы](personal-os-project-management.md)
|
||||
104. D18-201 открыт. В живой очереди сверены Kick-off C-S-S с результатом Hack Phase, зависимость замеров, вопрос о скрытых страницах macOS и запрос Advisor. Для текущего Kick-off по iOS проверены дата, слот O‑B Weekly, общий тест с FE и форма подтверждения. На копии действующего частично заполненного Kick-off появляется только черновик Next steps. После штатного пересчёта живой iOS Kick-off сохранил четыре раздела для исходной заготовки. Два итога iOS без оставшихся действий сверены с Asana. На копии незакреплённый итог даёт ссылку на опубликованный комментарий. Рабочий CPM сохранил подтверждение закрепления без повторного действия. При паузе DNR открытый вопрос о блокировке CPM сохранил прежний идентификатор и обе ссылки. Живой портал показывает ожидание возобновления без срока. Допуск того же шага в оба плана, смена версии и снятие решения прошли на изолированной копии. Реального решения в рабочем журнале пока нет. На копии CPM проверена настройка интервала DRI ↔ PA и ссылка на последнее обновление. Рабочий интервал пока не задан. Назначенный Midmortem проверяет повестку, время и реестр. Правило версии 7 открыто в рабочем портале, положительный сценарий пройден на копии CPM. Открыты адресное уведомление, рабочий календарь Outlook, предложение нового Midmortem, пересечения без общей ссылки, Running и теги AoR. Точное членство в macOS App Development устанавливает AoR Work по действующему руководству. Рабочий E5 и оба прохода в портале подтвердили категорию, точные ссылки и прежнее удержание двух задач. [Проверка AoR Work](personal-os-evidence/2026-11-19/follow-up-live-acceptance.md#категория-aor-по-рабочей-доске) Назначение Advisor сохраняется после контрольного закрытия Kick-off для iOS и C-S-S. Закрытие самого проекта снимает шаг. В 23:09 повторно подтверждены пауза DNR и ожидание в очереди. Для встреч используются рабочий календарь и Asana. Чтение писем исключено. На «Сегодня» и в Weekly Review повторно сверены ссылки O‑B Weekly, Career Advisor и Apple Weekly с первичными датами Asana. [Доказательства и этапы](personal-os-project-management.md)
|
||||
105. D18-202 открыт. В живой хронологии при 1280 и 390 px сверены время Zoom, слот Asana, интервал ActivityWatch, ревью GitHub #8188, черновик статуса из коммита, две созданные задачи и итоговый комментарий CPM. Два PR одного Tech Design различимы по заголовку и номеру, поиск по номеру работает. В раскрытии трёх замечаний GitHub сверены цитаты, точные ссылки и исходный SHA. Ревью с одним LGTM не показывает пустой блок замечаний. Реплики об обновлении TD видны внутри встречи 12 ноября с авторами и точным временем. Карточки плана по ним отсутствуют, пока цель не установлена. На встрече CPM 19 ноября сверены две существующие задачи, точные реплики, сроки и ссылки. После перезапуска ссылки однажды появились только после повторного чтения Asana. На рабочем портале перепроверен прямой путь. На отдельном сервере при контрольном HTTP 503 реальные сохранённые карточки показали обе ссылки и время снимка. Отказ в доступе и непригодная копия исключены. Контрольный перенос и снятие срока анализа сохраняют дату договорённости и исходную ссылку. Прямой путь со сроком 4 декабря повторно подтверждён на живом портале в 23:09 при 1280 и 390 px после перезагрузки. На копии проверена поздняя локальная квитанция, на рабочем портале открыт существующий черновик. Записей создания из Personal OS в рабочем журнале нет. Остаются рабочее создание новой задачи из решения встречи или черновика Personal OS и черновики из результатов без Git-коммита. Единственная связанная локальная заметка имеет одну версию и семь рабочих связей. Поручение Exact tab/window matching сохраняется в истории 13 ноября и очереди после закрытия исходной нити. Снятие при публикации текста или закрытии цели проверено на копии. [План](personal-os-day-history.md) · [Доказательства](personal-os-evidence/2026-11-19/follow-up-live-acceptance.md#два-pr-одного-tech-design-в-хронологии)
|
||||
106. Вопрос к Juan Pereira снят из рабочей очереди и требований личной карточки FaviconStore. Назначение, исходное обсуждение и фильтр AoR Work сохранились. Рабочий пересчёт и повтор при 1280 и 390 px подтвердили исправление. [Доказательства](personal-os-evidence/2026-11-19/follow-up-live-acceptance.md#запрос-с-другим-адресатом-в-личной-задаче)
|
||||
107. В рабочем PR FaviconStore показаны два актуальных замечания, точный коммит и лог Test (Non-Sandbox). Пять устаревших нитей отделены от активных. Удержание сохранено. [Доказательства](personal-os-evidence/2026-11-19/follow-up-live-acceptance.md#два-текущих-замечания-pr-faviconstore)
|
||||
|
||||
@@ -26,6 +26,7 @@ Milestone **D18-201** добавляет в «Рабочую очередь» о
|
||||
- Сверять регулярные обновления проекта и отдельный DRI ↔ Project Advisor thread. Учитывать комментарий по существу, принятое решение и уточнение от Advisor. Реакции, пустые комментарии и старые нити не закрывают текущую потребность. Частота хранится в правиле проекта или категории. При отсутствии подтверждённой частоты агент предлагает её установить; просрочка сама по себе не объявляется.
|
||||
- Сопоставлять Task Timeline с реально принятыми изменениями скоупа, новыми findings, зависимостями, переносами, открытыми блокерами и влиянием параллельной работы. Предлагать конкретные изменения очередности или сроков, с основаниями и указанием кого потребуется уведомить.
|
||||
- При существенном расширении скоупа, риске для критериев успеха, явном конфликте сроков или решении Advisor предложить Midmortem. Условие и время проверки задаются правилом. Подготовить сравнение с целью и планом, риски, варианты продолжения и требуемые решения по шаблону. При принятом решении сверить Asana, общий слот или Outlook и заинтересованных участников.
|
||||
- У существующего Midmortem действующего Top Priority проверяются будущая дата, точное время или слот Asana, регистрация и пустые части повестки. Пункт Recap ожидает созвона. У завершённого или приостановленного проекта подготовка не выводится. [Проверка CPM](personal-os-evidence/2026-11-19/follow-up-live-acceptance.md#подготовка-назначенного-midmortem)
|
||||
|
||||
### Закрыть проект
|
||||
|
||||
@@ -62,9 +63,9 @@ Milestone **D18-201** добавляет в «Рабочую очередь» о
|
||||
|
||||
Проверены [Kick-off Call Template](https://app.asana.com/0/0/332886249861503), [Pre-Kick-off Questions](https://app.asana.com/0/0/1207268731049843), [правило о Project Advisor и стейкхолдерах](https://app.asana.com/0/0/1207268731049844), [Mid-mortem Template](https://app.asana.com/0/0/1203886245376707) и [Postmortem Template](https://app.asana.com/0/0/479969710297425). Asana вернула HTTP 404 для отдельной страницы с условиями Midmortem, указанной в шаблоне. Частота проверок, подборка остальных пересечений, приглашения Outlook и настройки Running остаются открытыми. [Условия Midmortem](https://app.asana.com/0/0/1206092209398857) · [Шаблон нити DRI ↔ PA](https://app.asana.com/0/0/1209365089275750)
|
||||
|
||||
В [«Рабочей очереди»](http://127.0.0.1:4317/#/task-queue?category=project-management) доступны 15 исходных правил и редактор. Можно добавить правило, выбрать стадию и категории, указать условие, инструкцию, период и критерий закрытия, а также приостановить или восстановить исходное правило. Текущий расчёт сохраняет версию правил. Изменение настроек запускает новый расчёт. При конфликте двух вкладок сохраняется уже записанная версия.
|
||||
В [«Рабочей очереди»](http://127.0.0.1:4317/#/task-queue?category=project-management) доступны 16 исходных правил и редактор. Можно добавить правило, выбрать стадию и категории, указать условие, инструкцию, период и критерий закрытия, а также приостановить или восстановить исходное правило. Текущий расчёт сохраняет версию правил. Изменение настроек запускает новый расчёт. При конфликте двух вкладок сохраняется уже записанная версия.
|
||||
|
||||
Восемь проверок используют правила из активной версии. Сценарий на отдельном наборе подтвердил, что пауза убирает соответствующее предложение, восстановление возвращает его, а старый запрос отклоняется. Остальные правила можно настраивать и читать. В портале явно отмечено, для каких ещё требуется подключить автоматическую проверку. Открыты автоматический допуск предложений в планы и проверка остальных стадий.
|
||||
Девять проверок используют правила из активной версии. Сценарий на отдельном наборе подтвердил, что пауза убирает соответствующее предложение, восстановление возвращает его, а старый запрос отклоняется. Остальные правила можно настраивать и читать. В портале явно отмечено, для каких ещё требуется подключить автоматическую проверку. Открыты автоматический допуск предложений в планы и проверка остальных стадий.
|
||||
|
||||
20 ноября штатный расчёт в 13:56 связал карточку C-S-S с точной повесткой O-B Weekly. На живом экране при 1280 и 390 px после первого открытия и перезагрузки проверены действие, ссылка на повестку, открытие редактора и отмена. Отдельное приглашение остаётся неподтверждённым. Установленный Outlook через локальный интерфейс чтения вернул один календарь без рабочего аккаунта и ни одного аккаунта Exchange.
|
||||
|
||||
|
||||
@@ -985,7 +985,7 @@ Zoom используется для транскриптов состоявши
|
||||
- Добавить самостоятельный milestone «Сопровождение работ» и одноимённую категорию «Рабочей очереди». После чтения источников проверять требования на конкретной стадии по редактируемому набору для Top Priority, AoR и пользовательских категорий. Правила доступны в портале и агенту списком с условиями и критерием закрытия.
|
||||
- Для AoR Work брать точное членство в доске из действующего руководства роли и свежей задачи Asana. Сохранять связь и доказательство в очереди при удержании задачи. Применимость Running и тегов требует собственного подтверждённого правила. [Проверка](personal-os-evidence/2026-11-19/follow-up-live-acceptance.md#категория-aor-по-рабочей-доске)
|
||||
- Покрыть подготовку проекта, применимую Hack Phase, параллельные проекты и открытые вопросы, Kick-off и приглашения, регулярные обновления, DRI ↔ PA, Task Timeline, findings, блокеры, Midmortem, cleanup, Postmortem и итоговое оповещение. Для AoR сверять рабочие секции, включая применимый Running, и теги по действующим правилам.
|
||||
- Начальный список из 15 правил и редактор доступны на портале. Восемь проверок используют сохранённую версию. Опубликованы черновик Kick-off, регистрация Current Objectives, зависимость C-S-S, ожидание ответа по Advisor и два решения после закрытия CPM. Слот сверяется по задаче и оценке времени в Weekly. Для встреч достаточно повесток и календаря. Чтение писем исключено. Подключение остальных стадий, рабочего календаря Outlook и допуск предложений в оба плана открыты. [Этапы и первоначальное наполнение](personal-os-project-management.md) · [Правила для агента](project-management-rules.json) · [Сценарии U24](personal-os-user-scenarios.md#u24--сопровождение-работ)
|
||||
- Список из 16 правил и редактор доступны на портале. Девять проверок используют сохранённую версию. Опубликованы черновик Kick-off, регистрация Current Objectives, зависимость C-S-S, ожидание ответа по Advisor и два решения после закрытия CPM. Слот сверяется по задаче и оценке времени в Weekly. Для встреч достаточно повесток и календаря. Чтение писем исключено. Подключение остальных стадий, рабочего календаря Outlook и допуск предложений в оба плана открыты. [Этапы и первоначальное наполнение](personal-os-project-management.md) · [Правила для агента](project-management-rules.json) · [Сценарии U24](personal-os-user-scenarios.md#u24--сопровождение-работ)
|
||||
|
||||
- Черновик C-S-S использует результат существующей Hack Phase и уточняет, какое решение нужно для Task Timeline. В пересечениях отдельно показан связанный вопрос по скрытым страницам macOS с точной ссылкой Asana. [Доказательства](personal-os-evidence/2026-11-19/follow-up-live-acceptance.md#результат-hack-phase-и-решение-по-скоупу-c-s-s)
|
||||
- Подготовка начинается с подтверждённой карточки Kick-off, включая карточку без даты. Для текущего проекта по iOS в очереди есть предложение согласовать слот O‑B Weekly или отдельный созвон, черновик по описанию проекта, регистрация и проверка Advisor. Общий совет о пересечениях исключён. Для отдельной карточки требуется конкретная открытая работа. [Доказательства](personal-os-evidence/2026-11-19/follow-up-live-acceptance.md#kick-off-без-даты-для-нового-top-priority)
|
||||
@@ -999,6 +999,7 @@ Zoom используется для транскриптов состоявши
|
||||
- Правила Kick-off и Postmortem используют рабочий календарь для отдельных встреч, повестку Asana для Weekly и Asana для оповещений. Доступ к почте исключён. [Доказательства](personal-os-evidence/2026-11-19/follow-up-live-acceptance.md#источники-для-проверки-встреч-проекта)
|
||||
- Проверка пустого Project Advisor использует открытую нить и стадию самого проекта. Контрольное закрытие Kick-off сохраняет предложение, закрытие проекта снимает его. [Доказательства](personal-os-evidence/2026-11-19/follow-up-live-acceptance.md#project-advisor-после-закрытия-kick-off)
|
||||
- Если в правиле DRI ↔ PA задан интервал, проверять последнее подтверждённое обновление DRI. На копии CPM проверены пороги 6 и 7 дней и ссылка на исходное обновление. У рабочих правил значение не выставлялось. [Доказательства](personal-os-evidence/2026-11-19/follow-up-live-acceptance.md#настраиваемый-интервал-dri--pa)
|
||||
- Для уже назначенного Midmortem действует правило подготовки повестки, времени и регистрации. График Asana распознаёт названия Mid-mortem и Midmortem и требует точного слота. Автоматическое предложение нового Midmortem и проверка приглашённых остаются отдельными этапами. [Доказательства](personal-os-evidence/2026-11-19/follow-up-live-acceptance.md#подготовка-назначенного-midmortem)
|
||||
|
||||
### D18-202 · Графическая хронология работы и возникших задач
|
||||
|
||||
|
||||
@@ -776,6 +776,8 @@
|
||||
|
||||
### U24.6 — Task Timeline, findings, блокер и Midmortem
|
||||
|
||||
- На копии Mid-mortem 2 из CPM открыть существующую карточку с будущей датой. Сверить пустые разделы повестки, реестр и точное время. После заполнения, записи реестра и подтверждения слота предложение исчезает. Приостановка, завершение и прошедший слот исключают подготовку. На рабочем портале проверить доступность правила и его стадию.
|
||||
|
||||
- Прочитать принятый рост скоупа, отдельную гипотезу и реальный блокер. Сверить предложение изменений по Task Timeline и Midmortem с нужной стадией и условиями. Незначительное уточнение и прежняя гипотеза без решения не образуют новые встречи. После принятого решения читаются повестка, участники и итог.
|
||||
|
||||
### U24.7 — Cleanup и Postmortem после завершения
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
{
|
||||
"version": 6,
|
||||
"version": 7,
|
||||
"rules": [
|
||||
{
|
||||
"id": "project-registration",
|
||||
@@ -149,6 +149,20 @@
|
||||
"https://app.asana.com/0/0/1206092209398857"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "midmortem-readiness",
|
||||
"categories": [
|
||||
"top-priority"
|
||||
],
|
||||
"stage": "active",
|
||||
"title": "Подготовить назначенный Midmortem",
|
||||
"condition": "Действующий Top Priority не приостановлен. В Asana заведён открытый Midmortem с ещё не прошедшей датой.",
|
||||
"agent": "Сверь пустые части повестки, точное время или слот Asana и членство в реестре Midmortem. Предложи только подтверждённые пробелы в существующей карточке. Приглашение и список участников сверяются по календарной записи.",
|
||||
"completion": "Проверенные пропуски устранены в существующей карточке Midmortem.",
|
||||
"sources": [
|
||||
"https://app.asana.com/0/0/1203886245376707"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "closeout-cleanup",
|
||||
"categories": [
|
||||
|
||||
+85
@@ -25,6 +25,91 @@
|
||||
"time": "21:31:26",
|
||||
"speaker": "Gabriel Weinberg",
|
||||
"text": "Yeah."
|
||||
},
|
||||
{
|
||||
"time": "21:31:34",
|
||||
"speaker": "Anne Hildebrand",
|
||||
"text": "And also, uh, we want to make sure you get your questions answered around anything you want to discuss there, so submit a PeopleOps form, that's one way to do it. Um, if you do submit it without your name on the form, remember that the responses go to the project I've dropped in the channel there, so make sure not to miss those. That's it for me."
|
||||
},
|
||||
{
|
||||
"time": "21:31:58",
|
||||
"speaker": "Viktor Jansson",
|
||||
"text": "Alright, objective update from 05 Search Revenue. Last week, we held an assessment and switched the focus to evaluate ad experience and optimizations for search revenue. We will do this by evaluating if we can show ads from other providers for commercial queries, where Microsoft doesn't give us any ads, and how we can improve our overall shopping and product experience. For the optimizations, we have a few products in the pipeline, mainly for optimizing product ads, which we expect a potential $4 million a year revenue increase for. And the Duckbill Award goes to Renato, who ran a product during Quick Win Days to highlight prices for products on sale, which added half a million dollars a year, while at the same time helping our users to find discounted products. Great example of time well spent during Quick Win Days with a large impact to the objective KPIs. Over to Kirby for more million dollar updates."
|
||||
},
|
||||
{
|
||||
"time": "21:32:56",
|
||||
"speaker": "Kirby (she/they)",
|
||||
"text": "Hey, thanks Victor. So we built a lot this past cycle. We hit 150,000 active subscribers. We're tracking toward 180,000 by the end of this year, which is the stretch goal that we set out in our last cycle. And it's not official yet, but tentatively, we're working toward 300,000 as the goal for the end of next year, end of 2027. So more exciting updates to come. This slide is mostly about one A/B test that we did, and I want to take a minute to explain it, because it's really interesting. So we, in rough numbers, about 800 people start a subscription every day. Some of them are going direct into a paid subscription. Some of them are starting a free trial. Also, every day we have between 4 and 500 people canceling their subscription. So more than half. And the difference between those numbers is net subscriber additions. That's OO's KPI. So we're not just trying to get more people to start a subscription. We're also trying to get fewer people to cancel. And one way we're doing that is by giving people a better day zero experience as soon as they subscribe, creating subscriber onboarding. But another way we're doing it is by shifting people over to yearly plans. So we've got monthly, we've got yearly. Monthly plans have a 14% churn rate. That's the likelihood that someone will cancel every month. Yearly plans, it's only 2%, because you only have one opportunity to churn. every year. So to try to shift people toward yearly, we tested removing the free trial option from monthly plans to make yearly a little more appealing. And we did this first on Android, and we saw what we expected or what we hoped for. which is that fewer people are getting a subscription, because some people will see that there's no free trial on monthly, they don't want yearly, they bounce. But of the people who do stick around, more of them are on yearly, and we modeled it out so that we'd catch up with where. our growth would have been within a few months. Then we also did it on iOS, and we saw something surprising, which is that iOS users will just buy the monthly subscription with no free trial, and more of them are going yearly also. So the number of extra people we got on iOS. cancels out the people we lost on Android. So there's no cost. It's not going to take any time to catch up with where our growth would have been. We're just getting the extra lifetime value of each of these users by shifting more people over to yearly. And we're going to reduce the churn rate from where it is now, 9.5%, which is pretty good compared to the industry standard for VPNs. We want it to be at 7% and we want it to stay there. And a year from now, just from this one experiment. we're going to get down to 7.2% churn from having more people coming in on yearly plans. So if you're close to OO, you know that we work really hard to get one experiment out right after the last one. And this is why we never know. when we're gonna have one that's even more valuable than we'd anticipated. In lifetime value, which is different from revenue, but it's the projected amount of revenue we expect to get per user, we're adding 5 million in lifetime value per. year just from this one experiment. So the next time we're moving quickly to get something out for an experiment, out of the way, because these are really valuable and interesting. And congratulations to the team for all the work that got done. Super congratulations to Bartek, who's come on in a tech lead role. And as soon as he got to the objective, he got up to speed really quickly. and is our Duckbill winner because he has been accelerating the timelines in project after project by just thinking of something we didn't think of, coming up with a simpler way to solve something, and he connected the dots between incidents that we've been seeing across platforms where users are getting logged out and we don't know why. And he'd figured out a path forward, turned it into an SLO, and owned it, and is getting it fixed. Congratulations, Bartek. And next, on to Russell, I think."
|
||||
},
|
||||
{
|
||||
"time": "21:37:23",
|
||||
"speaker": "russell holt",
|
||||
"text": "Thanks, Gary. Hi, yeah, Russell here with an update for OE, where we are working on cookie prompt management and ad blocking. Um, for CPM, we've been, uh, improving the automated pipeline, which processes. uh, fixes and unhandled sites. And at this point, about 50% of these changes, uh, to our data set are fully automated, meaning no human involvement, which is pretty exciting. And right now we're at about overall 73% coverage, uh, in the US. Right now. So, one thing that we did this cycle is we finally got a reasonable opt-in rate. um, of 65% on Android, similar to iOS for CPM. Uh, which is a flow we've been struggling with for a bit, because we have a lot of cases where we need user consent. to automatically do something for them for legal reasons. And in this case, it was we need to accept cookies under certain circumstances to raise that coverage to improve the experience. And it's been a little bit of trouble, but that was great. So, on this cycle, we're really doubling down on the CPM automation, making the agent faster, more accurate, improving heuristic pop-up detection, doing regression testing, and this is really the key. to the long-term maintenance mode for CPM, which is finally in sight again, which we're pretty excited about. Um, and on the ad blocking side, uh, we're moving forward with two of the main feature requests. that we got from our analysis after the big YouTube ad blocking launch. Um, which will be… One, expanding ad blocking to a selection of top sites, starting with adult sites. And then two, on YouTube specifically, giving users the ability to skip sponsored segments. sponsored content segments, which look like ads to people. Uh, through YouTube. So, the goal there is to give people more control. and make a better default experience, even for YouTube Premium. where people see these sponsored segments as ads, so better not block. All right, that's it for OE. I guess on to Emmanuelle."
|
||||
},
|
||||
{
|
||||
"time": "21:39:42",
|
||||
"speaker": "Emanuele Feliziani",
|
||||
"text": "Yes, Russell, thanks. Exciting updates on the CDM and unblocking stuff. We had OI assessment last week. We will keep the focus on ChatSync. We will have a hopefully final push to stabilize the ChatSync system. So this will be more of a milestone focus. And we'll focus, yes, on stabilization. What we've done in the sparse cycle, we've optimized. the Syncflow on several platforms, both mobile and, uh, like, native and, um, and third-party, and we also shipped, uh, promos for ChatSync. For third parties, we've seen a significant inflow of users from those promos. We've doubled the daily activations and the daily active users for third parties specifically is up almost 5x. And it's 30% across all platforms. So really nice bump in users there. We're still not happy with the adoption. We want more. We are also not happy with the conversion rates. So we will keep iterating. in the… in future cycles, so after this one. Uh, in the meantime, we are also running, uh, user research to try and understand the drop of… the drop of points, the points of confusion. For users during the sync setup flow and see where we can be more helpful towards our users, making sure that they are able to set up sync. um… across multiple devices especially. We'll also look into ways to make the sync entry point more prominent. We've already seen that people struggle to find it in the settings, it's kind of buried, so we try to make it more prominent, lift it up a little bit, make it more intuitive how to use it. Um, and yeah. That's it for ROI. The duck bill goes to Pablo Serrano, the pub RR. designer, Serrano, uh, designer Pablo, we also have a Pablo on the back end. Uh, and yeah, he's, he's been great. Uh, he's been great for a long time and this cycle we are happy to congratulate him, uh, with, with the award. And, uh, yeah, he's been, uh, he's been great, uh, on the project advisory side, very quick and tidy on the design front. And he's been, diving into the metrics with, with Gusto. So, really happy to see Pablo grow in this role. Thanks, Pablo, and congrats. Uh, next up, I think, is, uh, team member, uh, updates with John Russell."
|
||||
},
|
||||
{
|
||||
"time": "21:42:36",
|
||||
"speaker": "Jon Russo",
|
||||
"text": "Hi. Didn't realize I was coming up this soon. But, hi, everybody. I'm John from the CloudOps team. I guess I'm Matt. Two different angles here. One from the work side. Recently, I started working on some of our Kubernetes stuff, which is really exciting and a little intimidating for me. I've been wanting to kind of dip my toes into this technology for a while, and it's nice to be able to finally do it. I got a lot of people on the team helping me in that, and kind of designing a new deployment spec for some of our new Kubernetes clusters. So that's fun and exciting in the infra velocity kind of project there. On a personal side, two pretty exciting things coming up. One tomorrow, I've been doing a lot of trail running this past year, and I have a half marathon coming up at a place called Von Trapp Mountain. Um, it's just outside of Stowe, Vermont, if anybody knows the area. Uh, the Von Trapp family is famous from The Sound of Music, uh, movies way back in the day, and it's an absolutely beautiful property up there. Um, so it's gonna be a fun race, um… there that has about 2,000 feet of elevation gain in it. I think that's roughly like 600 meters for the Europeans. The weather is looking pretty terrible, actually, so it might be a bit of a slop fest. We're expected to get an inch of rain today, and then it's going to be 33 degrees Fahrenheit at the start of the race, about 1 degree Celsius, so pretty dang cold. Um, and then the other side is that, uh, about a couple weeks ago, I booked a trip to Japan for end of January. Uh, this is something I've always wanted to do. It's been a bucket list trip for me to go skiing there. Um, so me and a couple friends are going to Hokkaido for two weeks. And, uh, traveling around in a van, and kind of exploring all the resorts there, and doing some backcountry skiing, uh, maybe even backcountry skiing into a volcano. Um, so that should be fun. Yeah, that's it for me. Thanks."
|
||||
},
|
||||
{
|
||||
"time": "21:44:56",
|
||||
"speaker": "Stephen",
|
||||
"text": "Oh, I think this is me. Hi, so we've been working on a refreshed new tab page for iOS for a while, and we're finally getting ready for the first internal release. It should be next week. I think there's a link in there if you want to enable it early. I tried to make a video. So this would work out well, but that didn't work. So we're gonna do it live demo real quick. So hopefully this does work out. I'm gonna try to. share this via… My phone. So if it doesn't work, someone please yell at me. Okay. Hopefully you can see my phone."
|
||||
},
|
||||
{
|
||||
"time": "21:45:37",
|
||||
"speaker": "Spencer",
|
||||
"text": "Yes."
|
||||
},
|
||||
{
|
||||
"time": "21:45:38",
|
||||
"speaker": "Stephen",
|
||||
"text": "Okay, awesome. Thank you. So… So here's the new tab — the new, new tab page. Kind of a weird phrasing. But you can see it's more brand forward. We have Dax there. He's got some Dax greetings. We have a nice background illustration there in the background. And the greetings will update. Probably not this frequently, but you can kind of see there's a few in there and we're going to update them based on time of day and some other stuff. The toggle's right there so you can switch between chat and search pretty easily. And you can see we have. Placeholder favorites now. So these are not hidden by default. So this is kind of inviting people to add more favorites. I could add one. Maybe. Yep, and there's that one, so that goes there. But we don't show the, uh… icon until you go there once. And then we also have… The return to hatch there. So you can get back to that. You can swipe it away if you want. Also get to your new tabs easier. And… I think I lost my window. I have too many DuckDuckGo's going here. You can also… Have a lot of favorites. So they scroll and expand and contract. And you can use the customization right on the page now, so you can toggle them on and off. From here, change some settings, we're gonna add some more there as well, and it also has… Dark mode, so if you want a cool fancy dark mode, you can have that as well, and everything should look… Nice there as well. So if you want to try that out, you can wait till next week, or you can follow the link and turn it on for yourself now."
|
||||
},
|
||||
{
|
||||
"time": "21:47:35",
|
||||
"speaker": "Julia Abreu",
|
||||
"text": "We had one more demo added to the agenda, but there is no name there. So, how to enable Redesign NTP? Does anyone…"
|
||||
},
|
||||
{
|
||||
"time": "21:47:45",
|
||||
"speaker": "Gabriel Weinberg",
|
||||
"text": "I think that's Brett Stevens."
|
||||
},
|
||||
{
|
||||
"time": "21:47:46",
|
||||
"speaker": "Stephen",
|
||||
"text": "Oh, yeah, that was part of mine, sorry."
|
||||
},
|
||||
{
|
||||
"time": "21:47:48",
|
||||
"speaker": "Gabriel Weinberg",
|
||||
"text": "Yeah."
|
||||
},
|
||||
{
|
||||
"time": "21:47:48",
|
||||
"speaker": "Julia Abreu",
|
||||
"text": "Oh, okay, cool. Just wanted to make sure that there was no extra in there. Uh, okay, before we wrap up, I just wanted to say or remind everybody that next day we have Hack Days. Um, it's the last Hack Days of the year. We will have a quick win in, uh, December. If you want to check the dates, you can see the AOR for special days. I am just drafting the calendar for next year, so I'll get Gabriel to take a look, and then I will post it as well under the AOR. I am working on some ideas on how to make the meeting for the demos a little shorter. I don't want to make it. every demo shorter than 2 minutes, because, um, I know you all wouldn't like that, but I'm trying to figure out, um, some ways that maybe we can split demos in different days, or, like, so if you have any ideas, or if you would like to help in any way. please go ahead and ping me. And otherwise, I just have one personal update that is special for Elle. Um, this is Maple. This is our third Dash Hound. Um, I am completely out of control now that I have a garden, so, um, I might be just sharing a new Dutch hound every week. Uh, and if I get her to not bark at everyone, I will bring her to our next meetup, uh, because the other two are not. very well trained. Um, so that's it for me. I hope you all have a great weekend, and uh… we'll roll out GPT for next week."
|
||||
},
|
||||
{
|
||||
"time": "21:49:17",
|
||||
"speaker": "Gabriel Weinberg",
|
||||
"text": "Yeah, one idea for you, Julia, for everyone here, is that to make less demos, you can collaborate with each other on projects, so… I'm not sure our best process for that at the moment, but there's the Hack Days project. You can say what you're gonna work on in there and try to recruit people. There's, we have a Mattermost channel too, don't we? Do you? Or if not, maybe we should."
|
||||
},
|
||||
{
|
||||
"time": "21:49:37",
|
||||
"speaker": "Julia Abreu",
|
||||
"text": "We do have, yes, specialties."
|
||||
},
|
||||
{
|
||||
"time": "21:49:40",
|
||||
"speaker": "Gabriel Weinberg",
|
||||
"text": "Maybe that's the place to go. Go to the Mattermost channel. Um, okay, hope everyone's gonna be good."
|
||||
}
|
||||
]
|
||||
}
|
||||
+17
@@ -15,3 +15,20 @@ source: "https://us01mynotes.zoom.us/klekRLtLSEuMv0PCCPCjtA"
|
||||
- **21:31:08 · Gabriel Weinberg:** Hello? That was a nice fade out. Um… Okay… No new team members, no AOR updates. Um, we had one company update, there's no name by it.
|
||||
- **21:31:23 · Anne Hildebrand:** Sorry, that was me. Um, yes, this is Anne. Uh, just a reminder to check your inboxes for the outcome of the compensation review.
|
||||
- **21:31:26 · Gabriel Weinberg:** Yeah.
|
||||
- **21:31:34 · Anne Hildebrand:** And also, uh, we want to make sure you get your questions answered around anything you want to discuss there, so submit a PeopleOps form, that's one way to do it. Um, if you do submit it without your name on the form, remember that the responses go to the project I've dropped in the channel there, so make sure not to miss those. That's it for me.
|
||||
- **21:31:58 · Viktor Jansson:** Alright, objective update from 05 Search Revenue. Last week, we held an assessment and switched the focus to evaluate ad experience and optimizations for search revenue. We will do this by evaluating if we can show ads from other providers for commercial queries, where Microsoft doesn't give us any ads, and how we can improve our overall shopping and product experience. For the optimizations, we have a few products in the pipeline, mainly for optimizing product ads, which we expect a potential $4 million a year revenue increase for. And the Duckbill Award goes to Renato, who ran a product during Quick Win Days to highlight prices for products on sale, which added half a million dollars a year, while at the same time helping our users to find discounted products. Great example of time well spent during Quick Win Days with a large impact to the objective KPIs. Over to Kirby for more million dollar updates.
|
||||
- **21:32:56 · Kirby (she/they):** Hey, thanks Victor. So we built a lot this past cycle. We hit 150,000 active subscribers. We're tracking toward 180,000 by the end of this year, which is the stretch goal that we set out in our last cycle. And it's not official yet, but tentatively, we're working toward 300,000 as the goal for the end of next year, end of 2027. So more exciting updates to come. This slide is mostly about one A/B test that we did, and I want to take a minute to explain it, because it's really interesting. So we, in rough numbers, about 800 people start a subscription every day. Some of them are going direct into a paid subscription. Some of them are starting a free trial. Also, every day we have between 4 and 500 people canceling their subscription. So more than half. And the difference between those numbers is net subscriber additions. That's OO's KPI. So we're not just trying to get more people to start a subscription. We're also trying to get fewer people to cancel. And one way we're doing that is by giving people a better day zero experience as soon as they subscribe, creating subscriber onboarding. But another way we're doing it is by shifting people over to yearly plans. So we've got monthly, we've got yearly. Monthly plans have a 14% churn rate. That's the likelihood that someone will cancel every month. Yearly plans, it's only 2%, because you only have one opportunity to churn. every year. So to try to shift people toward yearly, we tested removing the free trial option from monthly plans to make yearly a little more appealing. And we did this first on Android, and we saw what we expected or what we hoped for. which is that fewer people are getting a subscription, because some people will see that there's no free trial on monthly, they don't want yearly, they bounce. But of the people who do stick around, more of them are on yearly, and we modeled it out so that we'd catch up with where. our growth would have been within a few months. Then we also did it on iOS, and we saw something surprising, which is that iOS users will just buy the monthly subscription with no free trial, and more of them are going yearly also. So the number of extra people we got on iOS. cancels out the people we lost on Android. So there's no cost. It's not going to take any time to catch up with where our growth would have been. We're just getting the extra lifetime value of each of these users by shifting more people over to yearly. And we're going to reduce the churn rate from where it is now, 9.5%, which is pretty good compared to the industry standard for VPNs. We want it to be at 7% and we want it to stay there. And a year from now, just from this one experiment. we're going to get down to 7.2% churn from having more people coming in on yearly plans. So if you're close to OO, you know that we work really hard to get one experiment out right after the last one. And this is why we never know. when we're gonna have one that's even more valuable than we'd anticipated. In lifetime value, which is different from revenue, but it's the projected amount of revenue we expect to get per user, we're adding 5 million in lifetime value per. year just from this one experiment. So the next time we're moving quickly to get something out for an experiment, out of the way, because these are really valuable and interesting. And congratulations to the team for all the work that got done. Super congratulations to Bartek, who's come on in a tech lead role. And as soon as he got to the objective, he got up to speed really quickly. and is our Duckbill winner because he has been accelerating the timelines in project after project by just thinking of something we didn't think of, coming up with a simpler way to solve something, and he connected the dots between incidents that we've been seeing across platforms where users are getting logged out and we don't know why. And he'd figured out a path forward, turned it into an SLO, and owned it, and is getting it fixed. Congratulations, Bartek. And next, on to Russell, I think.
|
||||
- **21:37:23 · russell holt:** Thanks, Gary. Hi, yeah, Russell here with an update for OE, where we are working on cookie prompt management and ad blocking. Um, for CPM, we've been, uh, improving the automated pipeline, which processes. uh, fixes and unhandled sites. And at this point, about 50% of these changes, uh, to our data set are fully automated, meaning no human involvement, which is pretty exciting. And right now we're at about overall 73% coverage, uh, in the US. Right now. So, one thing that we did this cycle is we finally got a reasonable opt-in rate. um, of 65% on Android, similar to iOS for CPM. Uh, which is a flow we've been struggling with for a bit, because we have a lot of cases where we need user consent. to automatically do something for them for legal reasons. And in this case, it was we need to accept cookies under certain circumstances to raise that coverage to improve the experience. And it's been a little bit of trouble, but that was great. So, on this cycle, we're really doubling down on the CPM automation, making the agent faster, more accurate, improving heuristic pop-up detection, doing regression testing, and this is really the key. to the long-term maintenance mode for CPM, which is finally in sight again, which we're pretty excited about. Um, and on the ad blocking side, uh, we're moving forward with two of the main feature requests. that we got from our analysis after the big YouTube ad blocking launch. Um, which will be… One, expanding ad blocking to a selection of top sites, starting with adult sites. And then two, on YouTube specifically, giving users the ability to skip sponsored segments. sponsored content segments, which look like ads to people. Uh, through YouTube. So, the goal there is to give people more control. and make a better default experience, even for YouTube Premium. where people see these sponsored segments as ads, so better not block. All right, that's it for OE. I guess on to Emmanuelle.
|
||||
- **21:39:42 · Emanuele Feliziani:** Yes, Russell, thanks. Exciting updates on the CDM and unblocking stuff. We had OI assessment last week. We will keep the focus on ChatSync. We will have a hopefully final push to stabilize the ChatSync system. So this will be more of a milestone focus. And we'll focus, yes, on stabilization. What we've done in the sparse cycle, we've optimized. the Syncflow on several platforms, both mobile and, uh, like, native and, um, and third-party, and we also shipped, uh, promos for ChatSync. For third parties, we've seen a significant inflow of users from those promos. We've doubled the daily activations and the daily active users for third parties specifically is up almost 5x. And it's 30% across all platforms. So really nice bump in users there. We're still not happy with the adoption. We want more. We are also not happy with the conversion rates. So we will keep iterating. in the… in future cycles, so after this one. Uh, in the meantime, we are also running, uh, user research to try and understand the drop of… the drop of points, the points of confusion. For users during the sync setup flow and see where we can be more helpful towards our users, making sure that they are able to set up sync. um… across multiple devices especially. We'll also look into ways to make the sync entry point more prominent. We've already seen that people struggle to find it in the settings, it's kind of buried, so we try to make it more prominent, lift it up a little bit, make it more intuitive how to use it. Um, and yeah. That's it for ROI. The duck bill goes to Pablo Serrano, the pub RR. designer, Serrano, uh, designer Pablo, we also have a Pablo on the back end. Uh, and yeah, he's, he's been great. Uh, he's been great for a long time and this cycle we are happy to congratulate him, uh, with, with the award. And, uh, yeah, he's been, uh, he's been great, uh, on the project advisory side, very quick and tidy on the design front. And he's been, diving into the metrics with, with Gusto. So, really happy to see Pablo grow in this role. Thanks, Pablo, and congrats. Uh, next up, I think, is, uh, team member, uh, updates with John Russell.
|
||||
- **21:42:36 · Jon Russo:** Hi. Didn't realize I was coming up this soon. But, hi, everybody. I'm John from the CloudOps team. I guess I'm Matt. Two different angles here. One from the work side. Recently, I started working on some of our Kubernetes stuff, which is really exciting and a little intimidating for me. I've been wanting to kind of dip my toes into this technology for a while, and it's nice to be able to finally do it. I got a lot of people on the team helping me in that, and kind of designing a new deployment spec for some of our new Kubernetes clusters. So that's fun and exciting in the infra velocity kind of project there. On a personal side, two pretty exciting things coming up. One tomorrow, I've been doing a lot of trail running this past year, and I have a half marathon coming up at a place called Von Trapp Mountain. Um, it's just outside of Stowe, Vermont, if anybody knows the area. Uh, the Von Trapp family is famous from The Sound of Music, uh, movies way back in the day, and it's an absolutely beautiful property up there. Um, so it's gonna be a fun race, um… there that has about 2,000 feet of elevation gain in it. I think that's roughly like 600 meters for the Europeans. The weather is looking pretty terrible, actually, so it might be a bit of a slop fest. We're expected to get an inch of rain today, and then it's going to be 33 degrees Fahrenheit at the start of the race, about 1 degree Celsius, so pretty dang cold. Um, and then the other side is that, uh, about a couple weeks ago, I booked a trip to Japan for end of January. Uh, this is something I've always wanted to do. It's been a bucket list trip for me to go skiing there. Um, so me and a couple friends are going to Hokkaido for two weeks. And, uh, traveling around in a van, and kind of exploring all the resorts there, and doing some backcountry skiing, uh, maybe even backcountry skiing into a volcano. Um, so that should be fun. Yeah, that's it for me. Thanks.
|
||||
- **21:44:56 · Stephen:** Oh, I think this is me. Hi, so we've been working on a refreshed new tab page for iOS for a while, and we're finally getting ready for the first internal release. It should be next week. I think there's a link in there if you want to enable it early. I tried to make a video. So this would work out well, but that didn't work. So we're gonna do it live demo real quick. So hopefully this does work out. I'm gonna try to. share this via… My phone. So if it doesn't work, someone please yell at me. Okay. Hopefully you can see my phone.
|
||||
- **21:45:37 · Spencer:** Yes.
|
||||
- **21:45:38 · Stephen:** Okay, awesome. Thank you. So… So here's the new tab — the new, new tab page. Kind of a weird phrasing. But you can see it's more brand forward. We have Dax there. He's got some Dax greetings. We have a nice background illustration there in the background. And the greetings will update. Probably not this frequently, but you can kind of see there's a few in there and we're going to update them based on time of day and some other stuff. The toggle's right there so you can switch between chat and search pretty easily. And you can see we have. Placeholder favorites now. So these are not hidden by default. So this is kind of inviting people to add more favorites. I could add one. Maybe. Yep, and there's that one, so that goes there. But we don't show the, uh… icon until you go there once. And then we also have… The return to hatch there. So you can get back to that. You can swipe it away if you want. Also get to your new tabs easier. And… I think I lost my window. I have too many DuckDuckGo's going here. You can also… Have a lot of favorites. So they scroll and expand and contract. And you can use the customization right on the page now, so you can toggle them on and off. From here, change some settings, we're gonna add some more there as well, and it also has… Dark mode, so if you want a cool fancy dark mode, you can have that as well, and everything should look… Nice there as well. So if you want to try that out, you can wait till next week, or you can follow the link and turn it on for yourself now.
|
||||
- **21:47:35 · Julia Abreu:** We had one more demo added to the agenda, but there is no name there. So, how to enable Redesign NTP? Does anyone…
|
||||
- **21:47:45 · Gabriel Weinberg:** I think that's Brett Stevens.
|
||||
- **21:47:46 · Stephen:** Oh, yeah, that was part of mine, sorry.
|
||||
- **21:47:48 · Gabriel Weinberg:** Yeah.
|
||||
- **21:47:48 · Julia Abreu:** Oh, okay, cool. Just wanted to make sure that there was no extra in there. Uh, okay, before we wrap up, I just wanted to say or remind everybody that next day we have Hack Days. Um, it's the last Hack Days of the year. We will have a quick win in, uh, December. If you want to check the dates, you can see the AOR for special days. I am just drafting the calendar for next year, so I'll get Gabriel to take a look, and then I will post it as well under the AOR. I am working on some ideas on how to make the meeting for the demos a little shorter. I don't want to make it. every demo shorter than 2 minutes, because, um, I know you all wouldn't like that, but I'm trying to figure out, um, some ways that maybe we can split demos in different days, or, like, so if you have any ideas, or if you would like to help in any way. please go ahead and ping me. And otherwise, I just have one personal update that is special for Elle. Um, this is Maple. This is our third Dash Hound. Um, I am completely out of control now that I have a garden, so, um, I might be just sharing a new Dutch hound every week. Uh, and if I get her to not bark at everyone, I will bring her to our next meetup, uh, because the other two are not. very well trained. Um, so that's it for me. I hope you all have a great weekend, and uh… we'll roll out GPT for next week.
|
||||
- **21:49:17 · Gabriel Weinberg:** Yeah, one idea for you, Julia, for everyone here, is that to make less demos, you can collaborate with each other on projects, so… I'm not sure our best process for that at the moment, but there's the Hack Days project. You can say what you're gonna work on in there and try to recruit people. There's, we have a Mattermost channel too, don't we? Do you? Or if not, maybe we should.
|
||||
- **21:49:37 · Julia Abreu:** We do have, yes, specialties.
|
||||
- **21:49:40 · Gabriel Weinberg:** Maybe that's the place to go. Go to the Mattermost channel. Um, okay, hope everyone's gonna be good.
|
||||
+650
@@ -25,6 +25,656 @@
|
||||
"time": "18:10:09",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Uh, I think I'm, I'm like… done reviewing the first one about the pixel. I had the issue that I wasn't able to reproduce it, like, I was trying to kill the WebKit process."
|
||||
},
|
||||
{
|
||||
"time": "18:10:22",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Mm-hmm."
|
||||
},
|
||||
{
|
||||
"time": "18:10:23",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Do you have any, like, extra steps?"
|
||||
},
|
||||
{
|
||||
"time": "18:10:27",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Uh, so generally it fails from the second try on this exact test page that is attached there."
|
||||
},
|
||||
{
|
||||
"time": "18:10:37",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "So after, after I, I killed the, the, the…"
|
||||
},
|
||||
{
|
||||
"time": "18:10:37",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Okay."
|
||||
},
|
||||
{
|
||||
"time": "18:10:41",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Web extension, web process. I should reload the page?"
|
||||
},
|
||||
{
|
||||
"time": "18:10:47",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Yes, in general."
|
||||
},
|
||||
{
|
||||
"time": "18:10:49",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Do I need to do it, like, quickly, or do I need to, like…"
|
||||
},
|
||||
{
|
||||
"time": "18:10:53",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Um…"
|
||||
},
|
||||
{
|
||||
"time": "18:10:53",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Wait a bit."
|
||||
},
|
||||
{
|
||||
"time": "18:10:55",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Usually… yeah. I don't know, within one second, just kill the process, then reload the page."
|
||||
},
|
||||
{
|
||||
"time": "18:11:02",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Yeah."
|
||||
},
|
||||
{
|
||||
"time": "18:11:03",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "If it doesn't work from the first try, you just give it and reload again, and usually from second attempt, it does, uh… Uh, hang the… the extension. So it's not… it's not the genuine issue, so it's the…"
|
||||
},
|
||||
{
|
||||
"time": "18:11:20",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Yeah, artificial."
|
||||
},
|
||||
{
|
||||
"time": "18:11:22",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "artificial reproducing step that we didn't enable with the feature flag of the fix that went before, but it should be still here, and we… and allow to… To produce it. Uh, that's… So generally, yeah, I think you've seen the comment I posted to… to the… Project communication task. And the data, the data analysis."
|
||||
},
|
||||
{
|
||||
"time": "18:11:52",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Yeah, yeah, yeah."
|
||||
},
|
||||
{
|
||||
"time": "18:11:52",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "So… so generally there is, uh… yeah, it's kind of heavy codecs and cloud work, and, um… I cannot… Oh. I cannot tell that I understand, like, 100% what is happening beneath, uh, under the hood, and… Um… Generally, we have reproduced most of the… of the stall issues, uh, with some… Thank you. my display on black. Wow. I just need to switch off something, I guess."
|
||||
},
|
||||
{
|
||||
"time": "18:12:35",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "I can hear you, I cannot see you."
|
||||
},
|
||||
{
|
||||
"time": "18:12:36",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Hello? Yeah, I cannot see you, because… Give it a minute. Yeah. No. Fuck. And… Good morning, Mark. Sorry. One moment, Amy. I need to burn off something."
|
||||
},
|
||||
{
|
||||
"time": "18:13:10",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Did your laptop display died?"
|
||||
},
|
||||
{
|
||||
"time": "18:13:13",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Not yet, I guess. I hope. Uh, here… Here we are. Uh-huh. So, we do. Yeah. All right, I'm back. And… Oh, yeah, I just got some. Testing. Fairness around here. Uh, where was I? Yeah, the issues. Uh, so generally, there's four issues in the work, and uh… One is behind the disabled feature flag. Because it reloads the page, and I don't think it's optimal. And probably a couple of more go next, and we'll leave. the smallest groups for the next iteration, I guess. So here we have to, uh… To expand the diagnostics. So generally, to fulfill the privacy triage, uh, I was requested to… To reduce what we… actually submit, and the decision was to merge the events into a single event. It should not generally harm our, uh… our data. We can lose something in case the browser crashes, or if it's reloaded. But I guess it's acceptable at this point, since we get these isolated groups already. And we just need some proofs. for the remaining and the pixels. Prior to this."
|
||||
},
|
||||
{
|
||||
"time": "18:15:02",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Yes. So, so the first…"
|
||||
},
|
||||
{
|
||||
"time": "18:15:04",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Pixel fire for the pixel, yeah."
|
||||
},
|
||||
{
|
||||
"time": "18:15:06",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "First PR is the pixels, yeah? So the one from the PR."
|
||||
},
|
||||
{
|
||||
"time": "18:15:09",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Yes, so the suggestion is to improve the diagnostics first, and then the stacked ones go onto it."
|
||||
},
|
||||
{
|
||||
"time": "18:15:18",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Yeah, and what is the status of the other, like, PRs, the follow-up ones, with the fixes?"
|
||||
},
|
||||
{
|
||||
"time": "18:15:24",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Uh, so we have the… the recovery. And… First one is InitLoss. And InitLoss includes P1 and P2 as inputs. As I remember. Yeah, and P4, that's not enabled at the moment. It's, uh, 7379. It should be… Should be generated already. For review. And another one is 7459. It's also open. And… Well, generally, should also be pretty much ready, so the… There is integration tests, integration test harness that's supposed to only be run once to reproduce the issue."
|
||||
},
|
||||
{
|
||||
"time": "18:16:38",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Mm-hmm."
|
||||
},
|
||||
{
|
||||
"time": "18:16:39",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "In, like, lab condition."
|
||||
},
|
||||
{
|
||||
"time": "18:16:40",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Can you say. Which one was the last PR?"
|
||||
},
|
||||
{
|
||||
"time": "18:16:45",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "The last one, uh, 7459. This one."
|
||||
},
|
||||
{
|
||||
"time": "18:17:00",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Yeah, yeah, yeah, I got it, yeah, the network one, yeah."
|
||||
},
|
||||
{
|
||||
"time": "18:17:11",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "So the first, that is 7379, it should… So basically, we guess that it may be not an issue. And it's maybe an issue of slow. Slow loading and the fix itself is triggering the background will be load with the navigation itself. Because, uh, the initial… initial startup, or return from background, maybe not, uh, warming up the web view. Or, um… Or our extension. And, uh… The situation with P4 is that we may need to reload the page after, you know, after the extension is loaded, so it is applied to the page. And, uh, I was planning to investigate it further. Is there a way to run the… Plug in after the page is already loaded, maybe send another page load event. And see if it… if it just works. Uh, but the reload is there. And the feature flag."
|
||||
},
|
||||
{
|
||||
"time": "18:18:36",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "And do you think, like, uh… Are we able to detect the fourth one without the feature flag? Just to get the pixels about, like, how…"
|
||||
},
|
||||
{
|
||||
"time": "18:18:48",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Just to get the pixels… yeah, I guess so. I guess so we can make the pixel."
|
||||
},
|
||||
{
|
||||
"time": "18:18:59",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Yeah, because it would be get, like. It's good to get the signal, like, how many of those cases they potentially would be fixed by the future flag."
|
||||
},
|
||||
{
|
||||
"time": "18:19:11",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Yeah, I agree."
|
||||
},
|
||||
{
|
||||
"time": "18:19:12",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Yeah, but I mean, like, reloading the page is kind of, like, a risky thing, yeah, it can be disruptive, and… The question is, like, how frequently it would be."
|
||||
},
|
||||
{
|
||||
"time": "18:19:22",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Mm-hmm."
|
||||
},
|
||||
{
|
||||
"time": "18:19:23",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Yeah, and probably we would also have, like, the question is, like, how much confidence that they are actually, like, experiencing the problem. Just not to do the the, like, the reload. When there's no… not an issue for that."
|
||||
},
|
||||
{
|
||||
"time": "18:19:57",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Okay, and the next one is the network. Network process crash. Uh, it's a bit trickier. I… I didn't finish going through it. Actually… But, uh… So general state of it, it's kind of reproduced on the integration test harness. And the fix… Seems… to fix it. So, again, it's kinda… not… non-proved concepts and kind of speculative fixes. And we are hoping to… So first of all, those should be feature flagged, just in case anything goes wrong with it. You can private selectors or whatever are disturbing. The overall extension flow, so we could disable it remotely, and uh… Yeah, so again, I'm… Oh… Not 100% sure on those, but how it is reproduced in the test harness and by the automation. It seems we could use those fixes. Another one pending, it's not opened yet, is the base URL thing. And, uh… And the speculative steps to reproduce is, uh, if we reload the, um… if we update the web extension. it changes the base URL. Because we don't have this table base irrelevant. Those… It was flagged in the early research phase. Uh, what I'm not sure with it, uh, does it harm any… Can it bring any privacy or security concerns with it if we…"
|
||||
},
|
||||
{
|
||||
"time": "18:22:09",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "But which base? I, I don't, I don't get it, like, fully, like, with me."
|
||||
},
|
||||
{
|
||||
"time": "18:22:13",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "The extension was 0. So it's UUID that's generated for the extension every time it's launched. And when it changes, it brings some… Disturbance into the web extension."
|
||||
},
|
||||
{
|
||||
"time": "18:22:28",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Okay."
|
||||
},
|
||||
{
|
||||
"time": "18:22:29",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "And if we set it fixed as a fixed UID. For our web extension, it generally follows the WebKit rules as I understand it and may fix another part of the failures."
|
||||
},
|
||||
{
|
||||
"time": "18:22:44",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Mhmm. But it's only only on update, like, when we uninstall and install again, right?"
|
||||
},
|
||||
{
|
||||
"time": "18:22:45",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "And, uh… Yeah, but I, uh… I can guess it may be some significant portion of users that receive the service related to the app updates. As, uh, as it was, uh, as it was… described and issued initially."
|
||||
},
|
||||
{
|
||||
"time": "18:23:14",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Okay, so it's like, uh… 3… Three PRs with fixes. and potentially four."
|
||||
},
|
||||
{
|
||||
"time": "18:23:24",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Mmhm. network, the P1 one, uh, base URL. One for the loading. And, uh, yeah, potentially the fifth one. So, yeah, currently there is four, uh, four fixes in… in my… On my… work."
|
||||
},
|
||||
{
|
||||
"time": "18:23:53",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "So, do you have any, like, doubts, like, that, like, some of the fixes are, like, too risky, and, like, for example, the reload one? you would be not too sure about, like, shipping that one? Because I'm just, like, thinking…"
|
||||
},
|
||||
{
|
||||
"time": "18:24:05",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Uh, Zip?"
|
||||
},
|
||||
{
|
||||
"time": "18:24:07",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "thinking about, like, probably we can have the questions from Russell or someone, like. How much more time we can spend here, like, just to, like, focus on the, like, bare minimum, because probably, like, just to, like… better calculate the effort that we want to put into it."
|
||||
},
|
||||
{
|
||||
"time": "18:24:27",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Yeah, generally, we already had this question by Russell, as I mentioned, and I tried to answer it today."
|
||||
},
|
||||
{
|
||||
"time": "18:24:30",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Yeah, yeah, yeah."
|
||||
},
|
||||
{
|
||||
"time": "18:24:37",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "No, we've seen it. Uh, so the issue here is, uh, that we cannot distribute. the failures. You cannot tell there is one main… ah, yeah, there is another. Another one… And… Great deeds. Yeah, another genuine one that is kind of proved is window git close. So the original. Window and tab merging management, uh, fix it, uh… It didn't cover every… Every issue with the pin tab, and there is still one more remaining, uh, for the window closing, and, uh, yeah, should be a short one. Uh, it should cover the genuine issue of closing in tab using the web extension."
|
||||
},
|
||||
{
|
||||
"time": "18:25:31",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "But it's only McCoy, right?"
|
||||
},
|
||||
{
|
||||
"time": "18:25:32",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "I don't know. Yeah, my question. So, yeah, that is, uh, for… Four, one, two, three, one, two, three, four main groups that are targeted here, one requiring the page reload. And the P3 that, uh, without… Context without view, it may be the pin tab. And we have one iOS of 0.03%. macOS at around 6%, but it may be wrong. And we have the other group that cannot be considered at the moment. Maybe it gets fixed with the four fixes, or maybe we receive some more data. So I try to express this point in the conversation task. But if the hypothesis are correct, we should cover most of the cases."
|
||||
},
|
||||
{
|
||||
"time": "18:26:37",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "So, do you estimate to get them done this week?"
|
||||
},
|
||||
{
|
||||
"time": "18:26:37",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "So, yeah. Yeah, so the point here is to timebox it to…"
|
||||
},
|
||||
{
|
||||
"time": "18:26:45",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "To merge it this week, and so we can, like, get it internally next week, right?"
|
||||
},
|
||||
{
|
||||
"time": "18:26:45",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Two currents. Yeah. Yeah, so if we… if we get it to the release… I mean, the data analysis, the data attribution extension, and those fixes, if we get it to internal. Today and tomorrow. Uh, we can reason about it on… Next week."
|
||||
},
|
||||
{
|
||||
"time": "18:27:11",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Okay, so you would mean to merge it to… Release branches."
|
||||
},
|
||||
{
|
||||
"time": "18:27:17",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Yes, if it's possible."
|
||||
},
|
||||
{
|
||||
"time": "18:27:22",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "So, the two first PRs, like, one for the telemetry for the pixels, and the second with the P1 and P2, right?"
|
||||
},
|
||||
{
|
||||
"time": "18:27:31",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Um… It depends, I guess, if we can do it, if it's possible, I would give a go for all of them. Again, behind the feature flags."
|
||||
},
|
||||
{
|
||||
"time": "18:27:43",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Yeah, let's try. So, like, I'm… I'm… I'm… I'm done, like… reading and commenting for the first PRs, there are a couple of, like. leftovers for the dead code, so please check the comments. I'll try to, like, try forcing to reproduce it."
|
||||
},
|
||||
{
|
||||
"time": "18:27:55",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Mmhm."
|
||||
},
|
||||
{
|
||||
"time": "18:28:01",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "So so I get it and then I can move to the next PR. I can focus today on that. So we have the the the chart."
|
||||
},
|
||||
{
|
||||
"time": "18:28:08",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Okay, good. And when we have those reviewed, we can open the exception and try to push it to the internal."
|
||||
},
|
||||
{
|
||||
"time": "18:28:18",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "I mean, like, if it's, like, Monday, Tuesday, you can do it probably, like, for free."
|
||||
},
|
||||
{
|
||||
"time": "18:28:24",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Mm-hmm, okay."
|
||||
},
|
||||
{
|
||||
"time": "18:28:24",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "If it's later than tomorrow. Yeah. Okay. Okay, so let's try to do that."
|
||||
},
|
||||
{
|
||||
"time": "18:28:30",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Okay, I'll… I'll keep you pinged, yeah."
|
||||
},
|
||||
{
|
||||
"time": "18:28:31",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "And… Please ping me when you have the following one, because I want to, like…"
|
||||
},
|
||||
{
|
||||
"time": "18:28:37",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Mm-hmm."
|
||||
},
|
||||
{
|
||||
"time": "18:28:38",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Schedule the time for them, uh, like, in between my, my work, just to, just to not, like… Delay you. Uh, yeah."
|
||||
},
|
||||
{
|
||||
"time": "18:28:47",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Yeah, I guess it's… I guess it may take some time, maybe the rest of your day today, and those two PRs. Could feel it."
|
||||
},
|
||||
{
|
||||
"time": "18:28:58",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Yeah, so I'll focus on that, not to block you, so let's push for the first two ones, and yeah."
|
||||
},
|
||||
{
|
||||
"time": "18:29:04",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Mmhm."
|
||||
},
|
||||
{
|
||||
"time": "18:29:04",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "And the others, like, later in the week."
|
||||
},
|
||||
{
|
||||
"time": "18:29:07",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Mm-hmm."
|
||||
},
|
||||
{
|
||||
"time": "18:29:08",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Yeah, I agree."
|
||||
},
|
||||
{
|
||||
"time": "18:29:09",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "So, and yeah."
|
||||
},
|
||||
{
|
||||
"time": "18:29:10",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Just to try to get them out as soon as possible to get some results."
|
||||
},
|
||||
{
|
||||
"time": "18:29:16",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "And yes, since it's highly speculative, I would give it another mid-mortem. So yeah, time box it to this week. I'd say to the first half of this week. Because there is not much work really to be done about it. Just, uh… Just so you know, I have, like, a huge testing harness work tree, and I'm trying to split the parts from it that reproduce one another issue and make it into…"
|
||||
},
|
||||
{
|
||||
"time": "18:29:48",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "No doubt."
|
||||
},
|
||||
{
|
||||
"time": "18:29:53",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "into digestible pull requests. But generally, most of them are kind of reproduced in the lab. But we have no any proofs that they actually match the production issues because they are based on the event sequence that we get."
|
||||
},
|
||||
{
|
||||
"time": "18:30:08",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Yeah."
|
||||
},
|
||||
{
|
||||
"time": "18:30:14",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "We got to produce the event sequence that we are receiving, but we still cannot reason about the real issues leading to those. So, yeah, that's the state. All right, thank you. I won't take more of your time."
|
||||
},
|
||||
{
|
||||
"time": "18:30:31",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "So, after this week, you would put the, like, you would have the mid-mortem this week, or, like, next week after the…"
|
||||
},
|
||||
{
|
||||
"time": "18:30:41",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Next week, so let's try to get it out and have some data. The meeting is on Tuesday, right? So we could have the data analyzed and, uh, have a mid-mortem. and decide on the next steps whether we need. Keep on going, or we are satisfied with those, or we just give up and…"
|
||||
},
|
||||
{
|
||||
"time": "18:31:06",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Yeah. But do you think, like, on Tuesday, you will have, like, any meaningful data? It will be, like, just out for two days. Right?"
|
||||
},
|
||||
{
|
||||
"time": "18:31:13",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Uh, yes, we should, uh, since we… we received most of the current data by Tuesday. And it didn't change significantly throughout the week. I think there is a lot of issues are reported."
|
||||
},
|
||||
{
|
||||
"time": "18:31:36",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Okay."
|
||||
},
|
||||
{
|
||||
"time": "18:31:37",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "And there's more than enough data to analyze. So, yeah, Tuesday should be should be fine to have a big more time. I'll probably update the comments. Highlighting this."
|
||||
},
|
||||
{
|
||||
"time": "18:31:51",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Okay, sounds good. Okay, so I'm back to reviewing it, and, like, let's… Probably tomorrow you can, like, will you be on the OE weekly?"
|
||||
},
|
||||
{
|
||||
"time": "18:32:05",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Yes, tomorrow, tomorrow, tomorrow, tomorrow is Tuesday, yes, I think so."
|
||||
},
|
||||
{
|
||||
"time": "18:32:11",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Yeah, so we can recap the plan and see. So this is, like, your top priority, right? You're focusing on…"
|
||||
},
|
||||
{
|
||||
"time": "18:32:20",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Yeah, yeah. So, I mean, there is, uh, there is enough work for me outside of the top priority. Like where you are and pushing other stuff forward. But, yeah."
|
||||
},
|
||||
{
|
||||
"time": "18:32:39",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Makes sense. Cool. Are you blocked by anything, or just, like, this is, like… The general, like, work is enough for you."
|
||||
},
|
||||
{
|
||||
"time": "18:32:49",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Alright. Blocked with the data missing. And, uh, so… Only the pull requests are on the plate. Bottle making it. And, uh, yeah, the gaps between the releases, so we… keep perceiving it and. Analyzing how it goes."
|
||||
},
|
||||
{
|
||||
"time": "18:33:11",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Have you assigned me to all of the PRs? Because, uh, I see them…"
|
||||
},
|
||||
{
|
||||
"time": "18:33:15",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Not yet, I guess. Let me assign the network process. I didn't go through it myself yet, but yeah, I've assigned it to you."
|
||||
},
|
||||
{
|
||||
"time": "18:33:29",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Yeah, I think, like, something is broken with the…"
|
||||
},
|
||||
{
|
||||
"time": "18:33:33",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Yeah, yeah, I'll… I'm on it."
|
||||
},
|
||||
{
|
||||
"time": "18:33:36",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "No, no, like, I mean, like, uh, I'm browsing through the, the, this PR, these are the PRs, and, like, I'm filtering by the assigned to me. And I only picked it up."
|
||||
},
|
||||
{
|
||||
"time": "18:33:47",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Ah, assignees. I need to assign them. We generally don't assign the PRs, just set a reviewer."
|
||||
},
|
||||
{
|
||||
"time": "18:33:54",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "I don't know, like, you have the filter, like, review requested."
|
||||
},
|
||||
{
|
||||
"time": "18:34:00",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Mm-hmm."
|
||||
},
|
||||
{
|
||||
"time": "18:34:01",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "They can…"
|
||||
},
|
||||
{
|
||||
"time": "18:34:01",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Yeah, let me just send. Yes, I need. and requests. Yeah, so there is three pull requests."
|
||||
},
|
||||
{
|
||||
"time": "18:34:07",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Can you… can you see? So those are, like, open PRs from you all, but you have the filter for review, and it's, like, awaiting review from…"
|
||||
},
|
||||
{
|
||||
"time": "18:34:14",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Yep."
|
||||
},
|
||||
{
|
||||
"time": "18:34:18",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Me? I only get two of them."
|
||||
},
|
||||
{
|
||||
"time": "18:34:24",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Okay. 7, 4, 5, 5, 7."
|
||||
},
|
||||
{
|
||||
"time": "18:34:26",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Which is weird."
|
||||
},
|
||||
{
|
||||
"time": "18:34:29",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Oh, 7376 is missing for some reason. Probably you gave a review for it already. And it's waiting for…"
|
||||
},
|
||||
{
|
||||
"time": "18:34:38",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Okay."
|
||||
},
|
||||
{
|
||||
"time": "18:34:40",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "For the resolutions. Angus."
|
||||
},
|
||||
{
|
||||
"time": "18:34:43",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Okay, so maybe it's like, yeah."
|
||||
},
|
||||
{
|
||||
"time": "18:34:46",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Yeah, so currently two more in stock."
|
||||
},
|
||||
{
|
||||
"time": "18:34:50",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Okay. So it's it's in the stack, so I can get them from from the list. Right?"
|
||||
},
|
||||
{
|
||||
"time": "18:34:55",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Yep."
|
||||
},
|
||||
{
|
||||
"time": "18:34:56",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Okay, cool. Can I help you in any other way?"
|
||||
},
|
||||
{
|
||||
"time": "18:34:59",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Review stuck. Yes, stuck, stuck, stuck. Create stuck. Create stuck. And now those are in the stacks. Okay, good."
|
||||
},
|
||||
{
|
||||
"time": "18:35:15",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Do you need any other help?"
|
||||
},
|
||||
{
|
||||
"time": "18:35:18",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Not at the moment. I'm going to update the first one, telemetry one. And give you a ping, and uh… And when I complete the third one, I'll ping you as well, and probably… Probably the window did close, should be an easy one for today. As well. If it sounds good."
|
||||
},
|
||||
{
|
||||
"time": "18:35:46",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Okay. Okay, so I'm on the PRs. Please check the comments for the first one. I'm all moving for the second one."
|
||||
},
|
||||
{
|
||||
"time": "18:35:58",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Sure. Okay, thank you."
|
||||
},
|
||||
{
|
||||
"time": "18:36:03",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Thank you."
|
||||
}
|
||||
]
|
||||
}
|
||||
+130
@@ -15,3 +15,133 @@ source: "https://us01mynotes.zoom.us/QvxllpCuTTSLGEZp-R6jQw"
|
||||
- **18:10:01 · Michal Smaga:** Good.
|
||||
- **18:10:01 · Alex Martemyanov:** I'm pretty good. Jumping between windows. Yes.
|
||||
- **18:10:09 · Michal Smaga:** Uh, I think I'm, I'm like… done reviewing the first one about the pixel. I had the issue that I wasn't able to reproduce it, like, I was trying to kill the WebKit process.
|
||||
- **18:10:22 · Alex Martemyanov:** Mm-hmm.
|
||||
- **18:10:23 · Michal Smaga:** Do you have any, like, extra steps?
|
||||
- **18:10:27 · Alex Martemyanov:** Uh, so generally it fails from the second try on this exact test page that is attached there.
|
||||
- **18:10:37 · Michal Smaga:** So after, after I, I killed the, the, the…
|
||||
- **18:10:37 · Alex Martemyanov:** Okay.
|
||||
- **18:10:41 · Michal Smaga:** Web extension, web process. I should reload the page?
|
||||
- **18:10:47 · Alex Martemyanov:** Yes, in general.
|
||||
- **18:10:49 · Michal Smaga:** Do I need to do it, like, quickly, or do I need to, like…
|
||||
- **18:10:53 · Alex Martemyanov:** Um…
|
||||
- **18:10:53 · Michal Smaga:** Wait a bit.
|
||||
- **18:10:55 · Alex Martemyanov:** Usually… yeah. I don't know, within one second, just kill the process, then reload the page.
|
||||
- **18:11:02 · Michal Smaga:** Yeah.
|
||||
- **18:11:03 · Alex Martemyanov:** If it doesn't work from the first try, you just give it and reload again, and usually from second attempt, it does, uh… Uh, hang the… the extension. So it's not… it's not the genuine issue, so it's the…
|
||||
- **18:11:20 · Michal Smaga:** Yeah, artificial.
|
||||
- **18:11:22 · Alex Martemyanov:** artificial reproducing step that we didn't enable with the feature flag of the fix that went before, but it should be still here, and we… and allow to… To produce it. Uh, that's… So generally, yeah, I think you've seen the comment I posted to… to the… Project communication task. And the data, the data analysis.
|
||||
- **18:11:52 · Michal Smaga:** Yeah, yeah, yeah.
|
||||
- **18:11:52 · Alex Martemyanov:** So… so generally there is, uh… yeah, it's kind of heavy codecs and cloud work, and, um… I cannot… Oh. I cannot tell that I understand, like, 100% what is happening beneath, uh, under the hood, and… Um… Generally, we have reproduced most of the… of the stall issues, uh, with some… Thank you. my display on black. Wow. I just need to switch off something, I guess.
|
||||
- **18:12:35 · Michal Smaga:** I can hear you, I cannot see you.
|
||||
- **18:12:36 · Alex Martemyanov:** Hello? Yeah, I cannot see you, because… Give it a minute. Yeah. No. Fuck. And… Good morning, Mark. Sorry. One moment, Amy. I need to burn off something.
|
||||
- **18:13:10 · Michal Smaga:** Did your laptop display died?
|
||||
- **18:13:13 · Alex Martemyanov:** Not yet, I guess. I hope. Uh, here… Here we are. Uh-huh. So, we do. Yeah. All right, I'm back. And… Oh, yeah, I just got some. Testing. Fairness around here. Uh, where was I? Yeah, the issues. Uh, so generally, there's four issues in the work, and uh… One is behind the disabled feature flag. Because it reloads the page, and I don't think it's optimal. And probably a couple of more go next, and we'll leave. the smallest groups for the next iteration, I guess. So here we have to, uh… To expand the diagnostics. So generally, to fulfill the privacy triage, uh, I was requested to… To reduce what we… actually submit, and the decision was to merge the events into a single event. It should not generally harm our, uh… our data. We can lose something in case the browser crashes, or if it's reloaded. But I guess it's acceptable at this point, since we get these isolated groups already. And we just need some proofs. for the remaining and the pixels. Prior to this.
|
||||
- **18:15:02 · Michal Smaga:** Yes. So, so the first…
|
||||
- **18:15:04 · Alex Martemyanov:** Pixel fire for the pixel, yeah.
|
||||
- **18:15:06 · Michal Smaga:** First PR is the pixels, yeah? So the one from the PR.
|
||||
- **18:15:09 · Alex Martemyanov:** Yes, so the suggestion is to improve the diagnostics first, and then the stacked ones go onto it.
|
||||
- **18:15:18 · Michal Smaga:** Yeah, and what is the status of the other, like, PRs, the follow-up ones, with the fixes?
|
||||
- **18:15:24 · Alex Martemyanov:** Uh, so we have the… the recovery. And… First one is InitLoss. And InitLoss includes P1 and P2 as inputs. As I remember. Yeah, and P4, that's not enabled at the moment. It's, uh, 7379. It should be… Should be generated already. For review. And another one is 7459. It's also open. And… Well, generally, should also be pretty much ready, so the… There is integration tests, integration test harness that's supposed to only be run once to reproduce the issue.
|
||||
- **18:16:38 · Michal Smaga:** Mm-hmm.
|
||||
- **18:16:39 · Alex Martemyanov:** In, like, lab condition.
|
||||
- **18:16:40 · Michal Smaga:** Can you say. Which one was the last PR?
|
||||
- **18:16:45 · Alex Martemyanov:** The last one, uh, 7459. This one.
|
||||
- **18:17:00 · Michal Smaga:** Yeah, yeah, yeah, I got it, yeah, the network one, yeah.
|
||||
- **18:17:11 · Alex Martemyanov:** So the first, that is 7379, it should… So basically, we guess that it may be not an issue. And it's maybe an issue of slow. Slow loading and the fix itself is triggering the background will be load with the navigation itself. Because, uh, the initial… initial startup, or return from background, maybe not, uh, warming up the web view. Or, um… Or our extension. And, uh… The situation with P4 is that we may need to reload the page after, you know, after the extension is loaded, so it is applied to the page. And, uh, I was planning to investigate it further. Is there a way to run the… Plug in after the page is already loaded, maybe send another page load event. And see if it… if it just works. Uh, but the reload is there. And the feature flag.
|
||||
- **18:18:36 · Michal Smaga:** And do you think, like, uh… Are we able to detect the fourth one without the feature flag? Just to get the pixels about, like, how…
|
||||
- **18:18:48 · Alex Martemyanov:** Just to get the pixels… yeah, I guess so. I guess so we can make the pixel.
|
||||
- **18:18:59 · Michal Smaga:** Yeah, because it would be get, like. It's good to get the signal, like, how many of those cases they potentially would be fixed by the future flag.
|
||||
- **18:19:11 · Alex Martemyanov:** Yeah, I agree.
|
||||
- **18:19:12 · Michal Smaga:** Yeah, but I mean, like, reloading the page is kind of, like, a risky thing, yeah, it can be disruptive, and… The question is, like, how frequently it would be.
|
||||
- **18:19:22 · Alex Martemyanov:** Mm-hmm.
|
||||
- **18:19:23 · Michal Smaga:** Yeah, and probably we would also have, like, the question is, like, how much confidence that they are actually, like, experiencing the problem. Just not to do the the, like, the reload. When there's no… not an issue for that.
|
||||
- **18:19:57 · Alex Martemyanov:** Okay, and the next one is the network. Network process crash. Uh, it's a bit trickier. I… I didn't finish going through it. Actually… But, uh… So general state of it, it's kind of reproduced on the integration test harness. And the fix… Seems… to fix it. So, again, it's kinda… not… non-proved concepts and kind of speculative fixes. And we are hoping to… So first of all, those should be feature flagged, just in case anything goes wrong with it. You can private selectors or whatever are disturbing. The overall extension flow, so we could disable it remotely, and uh… Yeah, so again, I'm… Oh… Not 100% sure on those, but how it is reproduced in the test harness and by the automation. It seems we could use those fixes. Another one pending, it's not opened yet, is the base URL thing. And, uh… And the speculative steps to reproduce is, uh, if we reload the, um… if we update the web extension. it changes the base URL. Because we don't have this table base irrelevant. Those… It was flagged in the early research phase. Uh, what I'm not sure with it, uh, does it harm any… Can it bring any privacy or security concerns with it if we…
|
||||
- **18:22:09 · Michal Smaga:** But which base? I, I don't, I don't get it, like, fully, like, with me.
|
||||
- **18:22:13 · Alex Martemyanov:** The extension was 0. So it's UUID that's generated for the extension every time it's launched. And when it changes, it brings some… Disturbance into the web extension.
|
||||
- **18:22:28 · Michal Smaga:** Okay.
|
||||
- **18:22:29 · Alex Martemyanov:** And if we set it fixed as a fixed UID. For our web extension, it generally follows the WebKit rules as I understand it and may fix another part of the failures.
|
||||
- **18:22:44 · Michal Smaga:** Mhmm. But it's only only on update, like, when we uninstall and install again, right?
|
||||
- **18:22:45 · Alex Martemyanov:** And, uh… Yeah, but I, uh… I can guess it may be some significant portion of users that receive the service related to the app updates. As, uh, as it was, uh, as it was… described and issued initially.
|
||||
- **18:23:14 · Michal Smaga:** Okay, so it's like, uh… 3… Three PRs with fixes. and potentially four.
|
||||
- **18:23:24 · Alex Martemyanov:** Mmhm. network, the P1 one, uh, base URL. One for the loading. And, uh, yeah, potentially the fifth one. So, yeah, currently there is four, uh, four fixes in… in my… On my… work.
|
||||
- **18:23:53 · Michal Smaga:** So, do you have any, like, doubts, like, that, like, some of the fixes are, like, too risky, and, like, for example, the reload one? you would be not too sure about, like, shipping that one? Because I'm just, like, thinking…
|
||||
- **18:24:05 · Alex Martemyanov:** Uh, Zip?
|
||||
- **18:24:07 · Michal Smaga:** thinking about, like, probably we can have the questions from Russell or someone, like. How much more time we can spend here, like, just to, like, focus on the, like, bare minimum, because probably, like, just to, like… better calculate the effort that we want to put into it.
|
||||
- **18:24:27 · Alex Martemyanov:** Yeah, generally, we already had this question by Russell, as I mentioned, and I tried to answer it today.
|
||||
- **18:24:30 · Michal Smaga:** Yeah, yeah, yeah.
|
||||
- **18:24:37 · Alex Martemyanov:** No, we've seen it. Uh, so the issue here is, uh, that we cannot distribute. the failures. You cannot tell there is one main… ah, yeah, there is another. Another one… And… Great deeds. Yeah, another genuine one that is kind of proved is window git close. So the original. Window and tab merging management, uh, fix it, uh… It didn't cover every… Every issue with the pin tab, and there is still one more remaining, uh, for the window closing, and, uh, yeah, should be a short one. Uh, it should cover the genuine issue of closing in tab using the web extension.
|
||||
- **18:25:31 · Michal Smaga:** But it's only McCoy, right?
|
||||
- **18:25:32 · Alex Martemyanov:** I don't know. Yeah, my question. So, yeah, that is, uh, for… Four, one, two, three, one, two, three, four main groups that are targeted here, one requiring the page reload. And the P3 that, uh, without… Context without view, it may be the pin tab. And we have one iOS of 0.03%. macOS at around 6%, but it may be wrong. And we have the other group that cannot be considered at the moment. Maybe it gets fixed with the four fixes, or maybe we receive some more data. So I try to express this point in the conversation task. But if the hypothesis are correct, we should cover most of the cases.
|
||||
- **18:26:37 · Michal Smaga:** So, do you estimate to get them done this week?
|
||||
- **18:26:37 · Alex Martemyanov:** So, yeah. Yeah, so the point here is to timebox it to…
|
||||
- **18:26:45 · Michal Smaga:** To merge it this week, and so we can, like, get it internally next week, right?
|
||||
- **18:26:45 · Alex Martemyanov:** Two currents. Yeah. Yeah, so if we… if we get it to the release… I mean, the data analysis, the data attribution extension, and those fixes, if we get it to internal. Today and tomorrow. Uh, we can reason about it on… Next week.
|
||||
- **18:27:11 · Michal Smaga:** Okay, so you would mean to merge it to… Release branches.
|
||||
- **18:27:17 · Alex Martemyanov:** Yes, if it's possible.
|
||||
- **18:27:22 · Michal Smaga:** So, the two first PRs, like, one for the telemetry for the pixels, and the second with the P1 and P2, right?
|
||||
- **18:27:31 · Alex Martemyanov:** Um… It depends, I guess, if we can do it, if it's possible, I would give a go for all of them. Again, behind the feature flags.
|
||||
- **18:27:43 · Michal Smaga:** Yeah, let's try. So, like, I'm… I'm… I'm… I'm done, like… reading and commenting for the first PRs, there are a couple of, like. leftovers for the dead code, so please check the comments. I'll try to, like, try forcing to reproduce it.
|
||||
- **18:27:55 · Alex Martemyanov:** Mmhm.
|
||||
- **18:28:01 · Michal Smaga:** So so I get it and then I can move to the next PR. I can focus today on that. So we have the the the chart.
|
||||
- **18:28:08 · Alex Martemyanov:** Okay, good. And when we have those reviewed, we can open the exception and try to push it to the internal.
|
||||
- **18:28:18 · Michal Smaga:** I mean, like, if it's, like, Monday, Tuesday, you can do it probably, like, for free.
|
||||
- **18:28:24 · Alex Martemyanov:** Mm-hmm, okay.
|
||||
- **18:28:24 · Michal Smaga:** If it's later than tomorrow. Yeah. Okay. Okay, so let's try to do that.
|
||||
- **18:28:30 · Alex Martemyanov:** Okay, I'll… I'll keep you pinged, yeah.
|
||||
- **18:28:31 · Michal Smaga:** And… Please ping me when you have the following one, because I want to, like…
|
||||
- **18:28:37 · Alex Martemyanov:** Mm-hmm.
|
||||
- **18:28:38 · Michal Smaga:** Schedule the time for them, uh, like, in between my, my work, just to, just to not, like… Delay you. Uh, yeah.
|
||||
- **18:28:47 · Alex Martemyanov:** Yeah, I guess it's… I guess it may take some time, maybe the rest of your day today, and those two PRs. Could feel it.
|
||||
- **18:28:58 · Michal Smaga:** Yeah, so I'll focus on that, not to block you, so let's push for the first two ones, and yeah.
|
||||
- **18:29:04 · Alex Martemyanov:** Mmhm.
|
||||
- **18:29:04 · Michal Smaga:** And the others, like, later in the week.
|
||||
- **18:29:07 · Alex Martemyanov:** Mm-hmm.
|
||||
- **18:29:08 · Michal Smaga:** Yeah, I agree.
|
||||
- **18:29:09 · Alex Martemyanov:** So, and yeah.
|
||||
- **18:29:10 · Michal Smaga:** Just to try to get them out as soon as possible to get some results.
|
||||
- **18:29:16 · Alex Martemyanov:** And yes, since it's highly speculative, I would give it another mid-mortem. So yeah, time box it to this week. I'd say to the first half of this week. Because there is not much work really to be done about it. Just, uh… Just so you know, I have, like, a huge testing harness work tree, and I'm trying to split the parts from it that reproduce one another issue and make it into…
|
||||
- **18:29:48 · Michal Smaga:** No doubt.
|
||||
- **18:29:53 · Alex Martemyanov:** into digestible pull requests. But generally, most of them are kind of reproduced in the lab. But we have no any proofs that they actually match the production issues because they are based on the event sequence that we get.
|
||||
- **18:30:08 · Michal Smaga:** Yeah.
|
||||
- **18:30:14 · Alex Martemyanov:** We got to produce the event sequence that we are receiving, but we still cannot reason about the real issues leading to those. So, yeah, that's the state. All right, thank you. I won't take more of your time.
|
||||
- **18:30:31 · Michal Smaga:** So, after this week, you would put the, like, you would have the mid-mortem this week, or, like, next week after the…
|
||||
- **18:30:41 · Alex Martemyanov:** Next week, so let's try to get it out and have some data. The meeting is on Tuesday, right? So we could have the data analyzed and, uh, have a mid-mortem. and decide on the next steps whether we need. Keep on going, or we are satisfied with those, or we just give up and…
|
||||
- **18:31:06 · Michal Smaga:** Yeah. But do you think, like, on Tuesday, you will have, like, any meaningful data? It will be, like, just out for two days. Right?
|
||||
- **18:31:13 · Alex Martemyanov:** Uh, yes, we should, uh, since we… we received most of the current data by Tuesday. And it didn't change significantly throughout the week. I think there is a lot of issues are reported.
|
||||
- **18:31:36 · Michal Smaga:** Okay.
|
||||
- **18:31:37 · Alex Martemyanov:** And there's more than enough data to analyze. So, yeah, Tuesday should be should be fine to have a big more time. I'll probably update the comments. Highlighting this.
|
||||
- **18:31:51 · Michal Smaga:** Okay, sounds good. Okay, so I'm back to reviewing it, and, like, let's… Probably tomorrow you can, like, will you be on the OE weekly?
|
||||
- **18:32:05 · Alex Martemyanov:** Yes, tomorrow, tomorrow, tomorrow, tomorrow is Tuesday, yes, I think so.
|
||||
- **18:32:11 · Michal Smaga:** Yeah, so we can recap the plan and see. So this is, like, your top priority, right? You're focusing on…
|
||||
- **18:32:20 · Alex Martemyanov:** Yeah, yeah. So, I mean, there is, uh, there is enough work for me outside of the top priority. Like where you are and pushing other stuff forward. But, yeah.
|
||||
- **18:32:39 · Michal Smaga:** Makes sense. Cool. Are you blocked by anything, or just, like, this is, like… The general, like, work is enough for you.
|
||||
- **18:32:49 · Alex Martemyanov:** Alright. Blocked with the data missing. And, uh, so… Only the pull requests are on the plate. Bottle making it. And, uh, yeah, the gaps between the releases, so we… keep perceiving it and. Analyzing how it goes.
|
||||
- **18:33:11 · Michal Smaga:** Have you assigned me to all of the PRs? Because, uh, I see them…
|
||||
- **18:33:15 · Alex Martemyanov:** Not yet, I guess. Let me assign the network process. I didn't go through it myself yet, but yeah, I've assigned it to you.
|
||||
- **18:33:29 · Michal Smaga:** Yeah, I think, like, something is broken with the…
|
||||
- **18:33:33 · Alex Martemyanov:** Yeah, yeah, I'll… I'm on it.
|
||||
- **18:33:36 · Michal Smaga:** No, no, like, I mean, like, uh, I'm browsing through the, the, this PR, these are the PRs, and, like, I'm filtering by the assigned to me. And I only picked it up.
|
||||
- **18:33:47 · Alex Martemyanov:** Ah, assignees. I need to assign them. We generally don't assign the PRs, just set a reviewer.
|
||||
- **18:33:54 · Michal Smaga:** I don't know, like, you have the filter, like, review requested.
|
||||
- **18:34:00 · Alex Martemyanov:** Mm-hmm.
|
||||
- **18:34:01 · Michal Smaga:** They can…
|
||||
- **18:34:01 · Alex Martemyanov:** Yeah, let me just send. Yes, I need. and requests. Yeah, so there is three pull requests.
|
||||
- **18:34:07 · Michal Smaga:** Can you… can you see? So those are, like, open PRs from you all, but you have the filter for review, and it's, like, awaiting review from…
|
||||
- **18:34:14 · Alex Martemyanov:** Yep.
|
||||
- **18:34:18 · Michal Smaga:** Me? I only get two of them.
|
||||
- **18:34:24 · Alex Martemyanov:** Okay. 7, 4, 5, 5, 7.
|
||||
- **18:34:26 · Michal Smaga:** Which is weird.
|
||||
- **18:34:29 · Alex Martemyanov:** Oh, 7376 is missing for some reason. Probably you gave a review for it already. And it's waiting for…
|
||||
- **18:34:38 · Michal Smaga:** Okay.
|
||||
- **18:34:40 · Alex Martemyanov:** For the resolutions. Angus.
|
||||
- **18:34:43 · Michal Smaga:** Okay, so maybe it's like, yeah.
|
||||
- **18:34:46 · Alex Martemyanov:** Yeah, so currently two more in stock.
|
||||
- **18:34:50 · Michal Smaga:** Okay. So it's it's in the stack, so I can get them from from the list. Right?
|
||||
- **18:34:55 · Alex Martemyanov:** Yep.
|
||||
- **18:34:56 · Michal Smaga:** Okay, cool. Can I help you in any other way?
|
||||
- **18:34:59 · Alex Martemyanov:** Review stuck. Yes, stuck, stuck, stuck. Create stuck. Create stuck. And now those are in the stacks. Okay, good.
|
||||
- **18:35:15 · Michal Smaga:** Do you need any other help?
|
||||
- **18:35:18 · Alex Martemyanov:** Not at the moment. I'm going to update the first one, telemetry one. And give you a ping, and uh… And when I complete the third one, I'll ping you as well, and probably… Probably the window did close, should be an easy one for today. As well. If it sounds good.
|
||||
- **18:35:46 · Michal Smaga:** Okay. Okay, so I'm on the PRs. Please check the comments for the first one. I'm all moving for the second one.
|
||||
- **18:35:58 · Alex Martemyanov:** Sure. Okay, thank you.
|
||||
- **18:36:03 · Michal Smaga:** Thank you.
|
||||
@@ -98,8 +98,8 @@
|
||||
"note_modified_at": "2026-10-16T15:51:25.415Z",
|
||||
"source_url": "https://us01mynotes.zoom.us/klekRLtLSEuMv0PCCPCjtA",
|
||||
"folder": "2026-10-16 All-Company Meeting 2026-10-16 21 31(GMT+6 00) klekRLtLSEuMv0PCCPCjtA",
|
||||
"sha256": "000dc4ec158ed7f12d6fe8450f1c98f2f7b59b9df83e22a17edf91f53ccc6981",
|
||||
"cues": 3
|
||||
"sha256": "0dca61b2d18372150117b79e1a3e43ac4a0d5383397c34458a302268c48d7b0f",
|
||||
"cues": 20
|
||||
},
|
||||
"AEmGnEdJQfCMmCjwLyGtGA": {
|
||||
"title": "Зал персональной конференции Alex Martemyanov 2026-10-09 18:51(GMT+6:00)",
|
||||
@@ -420,8 +420,8 @@
|
||||
"note_modified_at": "2026-10-19T12:37:38.903Z",
|
||||
"source_url": "https://us01mynotes.zoom.us/QvxllpCuTTSLGEZp-R6jQw",
|
||||
"folder": "2026-10-19 Michal Smaga's Personal Meeting Room QvxllpCuTTSLGEZp-R6jQw",
|
||||
"sha256": "71c027dbd925614c7300ac720e4a5082fe4f712c2e6b5b607532c299bbbd890b",
|
||||
"cues": 3
|
||||
"sha256": "93a7a203db72ada9e1a4b791a72811c929f6ef88eccb9f1aa9d2bb3a9e9c7919",
|
||||
"cues": 133
|
||||
},
|
||||
"KcmYOq5_SQGPxdkdbhRx9A": {
|
||||
"title": "Dominik Kapusta's Personal Meeting Room",
|
||||
|
||||
@@ -1 +1 @@
|
||||
{"observed_at":"2026-11-20T16:51:26.769Z","scanned":33,"imported":3,"skipped":30,"withoutTranscript":0,"coverage":"complete","sections":[{"name":"Owned by me","pages":5,"notes":88,"complete":true,"terminal_cursor":true},{"name":"Shared with me","pages":1,"notes":0,"complete":true,"terminal_cursor":true},{"name":"Starred","pages":1,"notes":0,"complete":true,"terminal_cursor":true}],"discovered":88,"gaps":[],"recovered_transcripts":0,"policy":"reread_all_owned_shared_and_starred_notes_since_cutoff","since":"2026-09-30"}
|
||||
{"observed_at":"2026-11-20T17:22:46.318Z","scanned":33,"imported":2,"skipped":31,"withoutTranscript":0,"coverage":"complete","sections":[{"name":"Owned by me","pages":5,"notes":88,"complete":true,"terminal_cursor":true},{"name":"Shared with me","pages":1,"notes":0,"complete":true,"terminal_cursor":true},{"name":"Starred","pages":1,"notes":0,"complete":true,"terminal_cursor":true}],"discovered":88,"gaps":[],"recovered_transcripts":0,"policy":"reread_all_owned_shared_and_starred_notes_since_cutoff","since":"2026-09-30"}
|
||||
Reference in new issue
Block a user