From c110209d0e658fd4eeb0c87038b08820e7cf69ea Mon Sep 17 00:00:00 2001 From: Alexey Martemyanov Date: Thu, 19 Nov 2026 19:11:23 +0600 Subject: [PATCH] [2026-11-19] 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-remediation-plan-2026-11-18.md work/zoom-transcripts/2026-11-17 Apple Weekly Team Meeting - Zoom ID GJhjFoDDRY6PkqEUdM-YFg/transcript.json work/zoom-transcripts/2026-11-17 Apple Weekly Team Meeting - Zoom ID GJhjFoDDRY6PkqEUdM-YFg/transcript.md work/zoom-transcripts/index.json work/zoom-transcripts/sync-status.json --- .../2026-11-19/follow-up-live-acceptance.md | 6 + .../personal-os-production-acceptance.md | 2 + ...personal-os-remediation-plan-2026-11-18.md | 4 + .../transcript.json | 225 ++++++++++++++++++ .../transcript.md | 45 ++++ work/zoom-transcripts/index.json | 4 +- work/zoom-transcripts/sync-status.json | 2 +- 7 files changed, 285 insertions(+), 3 deletions(-) diff --git a/personal/projects/personal-os/personal-os-evidence/2026-11-19/follow-up-live-acceptance.md b/personal/projects/personal-os/personal-os-evidence/2026-11-19/follow-up-live-acceptance.md index d1a1f080..c83ad163 100644 --- a/personal/projects/personal-os/personal-os-evidence/2026-11-19/follow-up-live-acceptance.md +++ b/personal/projects/personal-os/personal-os-evidence/2026-11-19/follow-up-live-acceptance.md @@ -179,3 +179,9 @@ - На изолированной копии «Сегодня» открыл форму после рабочей границы. Открытие формы сохранило состояние источника. После явного сохранения текст совпал с записью `work-end:<дата>` в `local-signals.json`, сохранился после перезагрузки и открылся в истории исходной даты. С контрольным временем следующего утра та же запись появилась на «Сегодня» со ссылкой на историю. - В отдельном изолированном проходе карточка обязательства сохранила причину и дату следующей проверки. Повторный сбор сохранил статус «Отложено» и запись в истории. До исправления снимок обсуждений вычислял срок проверки по фактическим часам, хотя план считался на следующее утро. В двух повторных проходах вечерняя очередь была пуста, в 09:00 по Бишкеку в очереди ревью появилось ровно это обязательство с исходной репликой и ссылкой. Фактические решения пользователя в рабочих данных не создавались. - В 19:02 штатный сбор довёл журнал ActivityWatch до 19:00, записал сигнал `work-end:2026-11-19` с новым адресом и оставил его открытым. Система отметила готовность итогового наблюдения в 19:02:18. Рабочий Windmill E5 `01a1f3d6-c135-cde0-deb1-b7194d714f62` завершился успешно. Его план закрыл рабочее окно, сохранил Asana-календарь и вернул ноль действий и ревью. +- Повторное вечернее наблюдение `01a1f3e6-76aa-733a-b72f-5f18f3e50c57` стартовало в 19:07:00 и завершилось успешно за 2,24 секунды. Срез ActivityWatch остался ограничен 19:00, время итогового наблюдения осталось 19:02:18, в источнике сохранился один открытый сигнал без личной записи. + +## Загрузка результатов по датам + +- Повторные открытия «Недели» на рабочем портале в 19:04–19:05 вернули HTTP 200 за 1,13–1,15 секунды. Более ранний тайм-аут недельного API не воспроизвёлся. Скриншоты живой страницы показали пустые строки под четырьмя датами, пока шли независимые запросы итогов. На мобильном экране был виден только один уже загруженный день. +- После правки в окнах 1280 px и 390 px «Неделя» показала один статус загрузки на четыре даты, «История работы» — один статус на семь дат. Все даты открывались сразу, после завершения загрузки статус исчез, каждая строка содержала результат или текст о состоянии данных. Первый переход в каждом из четырёх проходов открыл датированную сводку. [Недельный обзор](http://127.0.0.1:4317/#/weekly-review) · [История работы](http://127.0.0.1:4317/#/work-history) diff --git a/personal/projects/personal-os/personal-os-production-acceptance.md b/personal/projects/personal-os/personal-os-production-acceptance.md index c9433ffc..7c9af0f9 100644 --- a/personal/projects/personal-os/personal-os-production-acceptance.md +++ b/personal/projects/personal-os/personal-os-production-acceptance.md @@ -20,6 +20,8 @@ - **Перенос работы на следующий день.** 19 ноября в 19:00 на живом «Сегодня» в двух открытых окнах появилась форма переноса и исчезли оставшиеся предложения. Открытие формы и истории сохранило состояние личной записи. На стенде сохранённая запись видна в истории исходной даты и на «Сегодня» следующим утром. Два прохода через карточку обязательства подтвердили отдельный перенос с причиной и датой ревью, сохранение при повторном сборе и появление в очереди в назначенное время. Утренние проверки выполнены на контрольных часах. [Доказательства](personal-os-evidence/2026-11-19/follow-up-live-acceptance.md) +- **Результаты по датам.** В «Неделе» и «Истории работы» на широком и мобильном экранах проверены единый статус загрузки, появление результата либо статуса для каждой даты и переход к сводке выбранного дня. Повторные запросы недельного обзора в 19:04–19:05 вернули HTTP 200 за 1,13–1,15 секунды. [Доказательства](personal-os-evidence/2026-11-19/follow-up-live-acceptance.md) + - **План и приоритет.** E4 и недельный отбор принимают проверенную связь с действующим Top Priority и подтверждённые личные запросы. Production E5 сохранял текущий день, а рабочий браузер подтвердил совпадение действий, source run и ревизии дня/недели. Показанный объём действий не является постоянным лимитом рабочего дня. [Проверка приоритета](personal-os-evidence/2026-11-18/source-priority-validation.json) · [Проверка шести процессов](personal-os-evidence/2026-11-18/windmill-six-workflows.json) - **Asana.** Действует непрерывный worker с очередью и продолжением. Текущие назначения имеют преимущество перед завершённой историей. Частичный охват не объявляется полным; зависимости перепроверяются при допуске действия. [Зависимости](personal-os-evidence/2026-11-18/asana-dependencies-validation.json) - **Личная область GitHub.** Штатный проход проверил отбор из 78 PR: 48 сверены с источником, 30 merged использованы из ограниченного суточного кэша. Общие родители Asana не добавляют все соседние PR. Это квитанция конкретного среза, не постоянное число работ пользователя. [Сквозной результат](personal-os-evidence/2026-11-18/windmill-six-workflows.json) diff --git a/personal/projects/personal-os/personal-os-remediation-plan-2026-11-18.md b/personal/projects/personal-os/personal-os-remediation-plan-2026-11-18.md index 1ceaa409..955f93df 100644 --- a/personal/projects/personal-os/personal-os-remediation-plan-2026-11-18.md +++ b/personal/projects/personal-os/personal-os-remediation-plan-2026-11-18.md @@ -365,3 +365,7 @@ Zoom используется для транскриптов состоявши - Ссылка на завершение дня открывала самочувствие, а форма находилась в очереди локальных сигналов. Форма теперь доступна на «Сегодня» с конца рабочего окна. Сохранённая запись видна в истории той же даты и в начале следующего дня. Запись создаётся явным сохранением. [Проверка](personal-os-evidence/2026-11-19/follow-up-live-acceptance.md) - Для переноса конкретного обязательства карточка сохраняет дату следующей проверки и основание. Повторный сбор сохраняет решение. Очередь ревью теперь использует тот же момент расчёта, что и дневной план. На стенде обязательство отсутствовало в вечернем плане и появилось к назначенному утреннему ревью. [Проверка](personal-os-evidence/2026-11-19/follow-up-live-acceptance.md) + +### D18-56 · Загрузка результатов по датам + +- В недельном обзоре и общем списке истории появлялись даты с пустыми строками, пока запрашивались результаты. Теперь один статус показывает загрузку всего списка. Даты доступны сразу, а после загрузки рядом с каждой видны результаты или статус источника. [Проверка](personal-os-evidence/2026-11-19/follow-up-live-acceptance.md) diff --git a/work/zoom-transcripts/2026-11-17 Apple Weekly Team Meeting - Zoom ID GJhjFoDDRY6PkqEUdM-YFg/transcript.json b/work/zoom-transcripts/2026-11-17 Apple Weekly Team Meeting - Zoom ID GJhjFoDDRY6PkqEUdM-YFg/transcript.json index 87102478..27046917 100644 --- a/work/zoom-transcripts/2026-11-17 Apple Weekly Team Meeting - Zoom ID GJhjFoDDRY6PkqEUdM-YFg/transcript.json +++ b/work/zoom-transcripts/2026-11-17 Apple Weekly Team Meeting - Zoom ID GJhjFoDDRY6PkqEUdM-YFg/transcript.json @@ -23,6 +23,231 @@ "time": "21:01:11", "speaker": "Pikor", "text": "Yep. Sorry, but I just realized that if you tap on that green camera icon on the status bar, then you have this recenter button within your preview and then there is the zoom. So you can zoom yourself like crazy." + }, + { + "time": "21:01:29", + "speaker": "Jonathan Jackson", + "text": "Yeah, that's the effect." + }, + { + "time": "21:01:32", + "speaker": "Pikor", + "text": "So this is fun. Yeah, Jorge likes it as well, as I see." + }, + { + "time": "21:01:36", + "speaker": "Andre Martingo", + "text": "Hello!" + }, + { + "time": "21:01:39", + "speaker": "Jonathan Jackson", + "text": "Hey, folks." + }, + { + "time": "21:01:40", + "speaker": "Pete Smith", + "text": "Igor, please do that at appropriate moments when you're giving your reaction to an inappropriate comment." + }, + { + "time": "21:01:45", + "speaker": "Pikor", + "text": "Okay." + }, + { + "time": "21:01:45", + "speaker": "Jonathan Jackson", + "text": "Yeah, right. All right, looks like we got a pretty good crew when we get started. Quick cruise through the rotations as usual. iOS Triage, Pico, you're on this week. Cue the Zooming. Jacek, you're up next week. Followed by L the week after that. There it is. Mac OS triage is on this week, followed by Sabrina and then Fernando. For iOS release, Pao is handling this week, followed by Hanyu and then Sam. And then macOS release, I actually don't know who's on because the task is closed this week already, but I hope that means that they know. Juan will be covering next week and then Dominic the week after that. As usual, any collisions, please let me know. Yep." + }, + { + "time": "21:02:58", + "speaker": "Fernando Bunn", + "text": "Pardon? Yeah, I'm out for two weeks, starting next week, so… No. Yep." + }, + { + "time": "21:03:08", + "speaker": "Jonathan Jackson", + "text": "Okay, we should find you a replacement for that week." + }, + { + "time": "21:03:12", + "speaker": "Fernando Bunn", + "text": "All right." + }, + { + "time": "21:03:13", + "speaker": "Jonathan Jackson", + "text": "Okay. See if you can trade with somebody nearby as a starting place." + }, + { + "time": "21:03:15", + "speaker": "Pete Smith", + "text": "Equip." + }, + { + "time": "21:03:19", + "speaker": "Jonathan Jackson", + "text": "Cool. Thanks." + }, + { + "time": "21:03:19", + "speaker": "Pete Smith", + "text": "Sorry to interrupt. Jonathan, a quick question about the…" + }, + { + "time": "21:03:21", + "speaker": "Jonathan Jackson", + "text": "Yep." + }, + { + "time": "21:03:23", + "speaker": "Pete Smith", + "text": "the holiday rotation, so I just… I'm one of the people with a big X beside my name, so I definitely won't be there, but just to make sure I understand, because I read the task, but there's no ask from, uh, the people who are actually on rotation at the moment, right? I mean, you are…" + }, + { + "time": "21:03:25", + "speaker": "Jonathan Jackson", + "text": "Yeah. Yep." + }, + { + "time": "21:03:38", + "speaker": "Pete Smith", + "text": "As far as I understand, you're taking care of finding…" + }, + { + "time": "21:03:41", + "speaker": "Jonathan Jackson", + "text": "I'm gonna start some conversations next. I was gonna do that yesterday when I was out. Um, but yeah, I think the task is settled enough that the next step is to… to try to get those conversations rolling, and I'll do that piece. Um, I'll probably need your help to think about which other week you would take to swap in, but…" + }, + { + "time": "21:03:41", + "speaker": "Pete Smith", + "text": "Or you're taking care of something." + }, + { + "time": "21:03:56", + "speaker": "Jonathan Jackson", + "text": "Yeah, I'm gonna get those rolling soon. And Pete, you are up first on the agenda." + }, + { + "time": "21:04:11", + "speaker": "Pete Smith", + "text": "Yeah, thanks. I forget what I wrote. Oh, yeah. OJ will begin — this is just an announcement or an FYI, an early announcement because we're just thinking about this now. So OJ is going to begin testing auto. So the auto deductor go harness, as it's also known, we're going to start testing that in OJ. And what that practically means is, so, uh, within OJ, we'll identify projects or tasks on the critical path that we think are low risk, so, like, low risk, maybe, you know, meaning limited blast radius or well-defined requirements, and then the. uh, project DRI, so, like, an engineer, one of the engineers in OJ will hand that work to Otto, so not that different to what everybody's doing at the moment in terms of just using agents to build. Uh, Otto would implement and open the PR, and then the project DRI, so the same person that handed the work to Otto. They will review the pull request and they will leave any comments which Auto or the agent will then deal with and will iterate until the PRO is ready and the project DRA will then merge the PRO. So that's the current plan. So I guess the difference there is that, you know, rather than the current state, where we work with agents to build it, and we ask another person to review it. it's the project DRI, the person who gave the prompt to Otto, and let it work completely on its own. They'll review the PR. So that's where we're going to start testing. This is happening in some other objectives, it's already happened in some other objectives, or started, but it's a way to test. um… I guess, auto." + }, + { + "time": "21:05:56", + "speaker": "Jonathan Jackson", + "text": "All right, thanks for the heads up." + }, + { + "time": "21:05:57", + "speaker": "Pete Smith", + "text": "That's the thought that. Yeah." + }, + { + "time": "21:06:00", + "speaker": "Jonathan Jackson", + "text": "I'll look forward to hearing how it goes, for sure. Uh, yeah, Sick, your topic is next." + }, + { + "time": "21:06:12", + "speaker": "JŁ", + "text": "Okay, so I had an idea for how to better present apple release strain. So we still have it in like a static form on Asana and we know how it works, but often people outside of our team don't. And I decided to use an artifact for that. It's still a work in progress, so I will expect some feedback. Let me share. Is it this one? Okay, I think it's this one. So I created this artifact that, like, you can share with anyone. Eh… And basically what it shows you is what version is currently in the store. What version is, like, reaching users, like, on the given day, and what version is in internal testing? You can tap on any version, and you can see, like, all the info that was in Asana, so, like, release notes, when it was cut from main, how it's rolling out, when it is going to be released to any person. You can see what flags depend on that version, and you can see all the changes here as well. Everything is, like, clickable, including, like, pull requests, so you can reach that. Mm-hmm. And… Then you have a schedule in a list, so you can show it to someone, so they know when each thing is going to be released. You can. change the view to the timeline, and on hover see when anything is released. And it includes the holiday break, too. On the calendar, you can also see it in this form, so you see when every version is going to be released. like each month. And then there are feature flags. So you see what feature flags are. On what percentage? And… So again, you, you know, if something is released to people or not, and you can also search. So for instance, I know that Bartosz was doing some background task thing, and if you like, search for it either by URL or link. It will show the thing, it will show you in which version it was released, what's the current running out status. And also you will see feature flags that were included. So you see this feature flag is only like released to 1% for this feature. So, uh, you can quickly see what is going on. And it also supports macOS, so, uh… yeah, like, probably still some things to polish. let me know if it's going to work for you or not. Thank you." + }, + { + "time": "21:08:55", + "speaker": "Jonathan Jackson", + "text": "I think it's probably going to work for pretty much everybody. That's amazing. Well done. Um, I think you might want to, you know, maybe have us spend a couple of weeks with it to make sure it's not…" + }, + { + "time": "21:08:59", + "speaker": "Andre Martingo", + "text": "Thank you." + }, + { + "time": "21:09:06", + "speaker": "Jonathan Jackson", + "text": "lying to people, you know, they're not… they're not using it, but yeah, I totally agree. People are suggesting sharing it at all hands, adding it to go.go.com, like, I think you should take it to a point where it's… where we're confident in it, and then definitely share it." + }, + { + "time": "21:09:07", + "speaker": "JŁ", + "text": "Yeah, yeah, sure." + }, + { + "time": "21:09:19", + "speaker": "Jonathan Jackson", + "text": "And think about connecting to Android and Windows as well once you're ready." + }, + { + "time": "21:09:25", + "speaker": "JŁ", + "text": "Sure, sure." + }, + { + "time": "21:09:26", + "speaker": "Jonathan Jackson", + "text": "Bartek, if you want to create an incident for us, you're welcome to." + }, + { + "time": "21:09:26", + "speaker": "Andre Martingo", + "text": "Good. Just a comment. Super nice. It's interesting because I was checking as well. I don't know if you saw the Windows release what they call a comment center. They have kind of an internal website. that contains… like, I think what you built plus more steps, um, and it was something that I was looking at once I finished Smartling, so I will get in touch with you. I don't know… at this point, what's the difference between an artifact or a web page itself, uh, inside of DuckDuckGo, but it's something, uh, that maybe we can… we can chat afterwards. Uh, but it's quite nice as well. Nice." + }, + { + "time": "21:10:18", + "speaker": "Jonathan Jackson", + "text": "Cool. Thank you. Jacek, when you're ready, it'd be great if you could share that with the team as a starting place, obviously." + }, + { + "time": "21:10:24", + "speaker": "JŁ", + "text": "Sure, sure." + }, + { + "time": "21:10:25", + "speaker": "Jonathan Jackson", + "text": "Cool. Uh, Andre, your SmartLink update is up next." + }, + { + "time": "21:10:31", + "speaker": "Andre Martingo", + "text": "So yeah, just a quick update. So everything should be done. I made a post. Me and Pao, we already kind of enabled or kind of disabled the Avenger warning. So I hope you'll start merging into main your untranslated strings. I have here as well an artifact since it's the new cool thing to do. Um… So basically, it was just an exploration about… how much we were spending per release in SmartLink, so maybe this will help us to move to AI, but other than that, it was to track. when are we starting using, kind of, the new flow. So, basically, here you have a graph of spending per release in terms of dollars, and the blue bars are, kind of, our new automatic flow. Um, so we are spending an average of, like, 500, 400, depending on the release. Um, and basically, here in this artifact, you can see, like. Which ones are the jobs that got merged automatically, or which ones are manual, so we can still… we can track, like, the usage of our new flow. And hopefully, maybe with some data, we can start thinking if it would be possible to move to AI, compare the prices, or maybe just A/B test for one language. It's something for the future we can maybe try to push for. But for now, it's just to collect… some stats so we can have better discussions over it." + }, + { + "time": "21:12:10", + "speaker": "Jonathan Jackson", + "text": "That's cool. Thank you. Yeah, if you want to share that somewhere so that people can find it on a regular basis, that'd be great. How have you seen, I know it's early, but on the nightly untranslated pieces, how quickly have those jobs from SmartLine been coming back?" + }, + { + "time": "21:12:31", + "speaker": "Andre Martingo", + "text": "Sorry, which ones?" + }, + { + "time": "21:12:33", + "speaker": "Jonathan Jackson", + "text": "You're basically doing a job every night with whatever was untranslated, right?" + }, + { + "time": "21:12:39", + "speaker": "Andre Martingo", + "text": "Also, but we do every merge commit as well. So basically, once you merge, we trigger a job, and the nightly will… if something goes wrong, it will pick up as well. So the blue bars are kind of the new flow, yeah." + }, + { + "time": "21:12:48", + "speaker": "Jonathan Jackson", + "text": "Oh, okay. Well, either one. Yeah. Presumably, those are usually smaller jobs for SmartLink. I was wondering how quickly they'd been turning those around recently." + }, + { + "time": "21:13:00", + "speaker": "Andre Martingo", + "text": "Yeah, actually, we have another one where we have the kind of turnover of PRs for Smartling, but I will share afterwards once we have more data. We didn't have much, no." + }, + { + "time": "21:13:07", + "speaker": "Jonathan Jackson", + "text": "Mm-hmm. Okay. Yeah, I know it's early still. All right, cool. Thank you. Um… That's our planned agenda for the day. Any other thoughts, questions, comments, things to share, demos? All right. A quick meeting today, but some good stuff. Thank you, everyone. Good to see you, and I hope you have a good day." } ] } diff --git a/work/zoom-transcripts/2026-11-17 Apple Weekly Team Meeting - Zoom ID GJhjFoDDRY6PkqEUdM-YFg/transcript.md b/work/zoom-transcripts/2026-11-17 Apple Weekly Team Meeting - Zoom ID GJhjFoDDRY6PkqEUdM-YFg/transcript.md index 9ff5c167..9022f094 100644 --- a/work/zoom-transcripts/2026-11-17 Apple Weekly Team Meeting - Zoom ID GJhjFoDDRY6PkqEUdM-YFg/transcript.md +++ b/work/zoom-transcripts/2026-11-17 Apple Weekly Team Meeting - Zoom ID GJhjFoDDRY6PkqEUdM-YFg/transcript.md @@ -15,3 +15,48 @@ source: "https://us01mynotes.zoom.us/GJhjFoDDRY6PkqEUdM-YFg" - **21:01:06 · Jonathan Jackson:** Pico, you're uh… Camera Zoom is doing, I don't know, it's like an old 1950s horror movie. - **21:01:10 · Pete Smith:** And you… - **21:01:11 · Pikor:** Yep. Sorry, but I just realized that if you tap on that green camera icon on the status bar, then you have this recenter button within your preview and then there is the zoom. So you can zoom yourself like crazy. +- **21:01:29 · Jonathan Jackson:** Yeah, that's the effect. +- **21:01:32 · Pikor:** So this is fun. Yeah, Jorge likes it as well, as I see. +- **21:01:36 · Andre Martingo:** Hello! +- **21:01:39 · Jonathan Jackson:** Hey, folks. +- **21:01:40 · Pete Smith:** Igor, please do that at appropriate moments when you're giving your reaction to an inappropriate comment. +- **21:01:45 · Pikor:** Okay. +- **21:01:45 · Jonathan Jackson:** Yeah, right. All right, looks like we got a pretty good crew when we get started. Quick cruise through the rotations as usual. iOS Triage, Pico, you're on this week. Cue the Zooming. Jacek, you're up next week. Followed by L the week after that. There it is. Mac OS triage is on this week, followed by Sabrina and then Fernando. For iOS release, Pao is handling this week, followed by Hanyu and then Sam. And then macOS release, I actually don't know who's on because the task is closed this week already, but I hope that means that they know. Juan will be covering next week and then Dominic the week after that. As usual, any collisions, please let me know. Yep. +- **21:02:58 · Fernando Bunn:** Pardon? Yeah, I'm out for two weeks, starting next week, so… No. Yep. +- **21:03:08 · Jonathan Jackson:** Okay, we should find you a replacement for that week. +- **21:03:12 · Fernando Bunn:** All right. +- **21:03:13 · Jonathan Jackson:** Okay. See if you can trade with somebody nearby as a starting place. +- **21:03:15 · Pete Smith:** Equip. +- **21:03:19 · Jonathan Jackson:** Cool. Thanks. +- **21:03:19 · Pete Smith:** Sorry to interrupt. Jonathan, a quick question about the… +- **21:03:21 · Jonathan Jackson:** Yep. +- **21:03:23 · Pete Smith:** the holiday rotation, so I just… I'm one of the people with a big X beside my name, so I definitely won't be there, but just to make sure I understand, because I read the task, but there's no ask from, uh, the people who are actually on rotation at the moment, right? I mean, you are… +- **21:03:25 · Jonathan Jackson:** Yeah. Yep. +- **21:03:38 · Pete Smith:** As far as I understand, you're taking care of finding… +- **21:03:41 · Jonathan Jackson:** I'm gonna start some conversations next. I was gonna do that yesterday when I was out. Um, but yeah, I think the task is settled enough that the next step is to… to try to get those conversations rolling, and I'll do that piece. Um, I'll probably need your help to think about which other week you would take to swap in, but… +- **21:03:41 · Pete Smith:** Or you're taking care of something. +- **21:03:56 · Jonathan Jackson:** Yeah, I'm gonna get those rolling soon. And Pete, you are up first on the agenda. +- **21:04:11 · Pete Smith:** Yeah, thanks. I forget what I wrote. Oh, yeah. OJ will begin — this is just an announcement or an FYI, an early announcement because we're just thinking about this now. So OJ is going to begin testing auto. So the auto deductor go harness, as it's also known, we're going to start testing that in OJ. And what that practically means is, so, uh, within OJ, we'll identify projects or tasks on the critical path that we think are low risk, so, like, low risk, maybe, you know, meaning limited blast radius or well-defined requirements, and then the. uh, project DRI, so, like, an engineer, one of the engineers in OJ will hand that work to Otto, so not that different to what everybody's doing at the moment in terms of just using agents to build. Uh, Otto would implement and open the PR, and then the project DRI, so the same person that handed the work to Otto. They will review the pull request and they will leave any comments which Auto or the agent will then deal with and will iterate until the PRO is ready and the project DRA will then merge the PRO. So that's the current plan. So I guess the difference there is that, you know, rather than the current state, where we work with agents to build it, and we ask another person to review it. it's the project DRI, the person who gave the prompt to Otto, and let it work completely on its own. They'll review the PR. So that's where we're going to start testing. This is happening in some other objectives, it's already happened in some other objectives, or started, but it's a way to test. um… I guess, auto. +- **21:05:56 · Jonathan Jackson:** All right, thanks for the heads up. +- **21:05:57 · Pete Smith:** That's the thought that. Yeah. +- **21:06:00 · Jonathan Jackson:** I'll look forward to hearing how it goes, for sure. Uh, yeah, Sick, your topic is next. +- **21:06:12 · JŁ:** Okay, so I had an idea for how to better present apple release strain. So we still have it in like a static form on Asana and we know how it works, but often people outside of our team don't. And I decided to use an artifact for that. It's still a work in progress, so I will expect some feedback. Let me share. Is it this one? Okay, I think it's this one. So I created this artifact that, like, you can share with anyone. Eh… And basically what it shows you is what version is currently in the store. What version is, like, reaching users, like, on the given day, and what version is in internal testing? You can tap on any version, and you can see, like, all the info that was in Asana, so, like, release notes, when it was cut from main, how it's rolling out, when it is going to be released to any person. You can see what flags depend on that version, and you can see all the changes here as well. Everything is, like, clickable, including, like, pull requests, so you can reach that. Mm-hmm. And… Then you have a schedule in a list, so you can show it to someone, so they know when each thing is going to be released. You can. change the view to the timeline, and on hover see when anything is released. And it includes the holiday break, too. On the calendar, you can also see it in this form, so you see when every version is going to be released. like each month. And then there are feature flags. So you see what feature flags are. On what percentage? And… So again, you, you know, if something is released to people or not, and you can also search. So for instance, I know that Bartosz was doing some background task thing, and if you like, search for it either by URL or link. It will show the thing, it will show you in which version it was released, what's the current running out status. And also you will see feature flags that were included. So you see this feature flag is only like released to 1% for this feature. So, uh, you can quickly see what is going on. And it also supports macOS, so, uh… yeah, like, probably still some things to polish. let me know if it's going to work for you or not. Thank you. +- **21:08:55 · Jonathan Jackson:** I think it's probably going to work for pretty much everybody. That's amazing. Well done. Um, I think you might want to, you know, maybe have us spend a couple of weeks with it to make sure it's not… +- **21:08:59 · Andre Martingo:** Thank you. +- **21:09:06 · Jonathan Jackson:** lying to people, you know, they're not… they're not using it, but yeah, I totally agree. People are suggesting sharing it at all hands, adding it to go.go.com, like, I think you should take it to a point where it's… where we're confident in it, and then definitely share it. +- **21:09:07 · JŁ:** Yeah, yeah, sure. +- **21:09:19 · Jonathan Jackson:** And think about connecting to Android and Windows as well once you're ready. +- **21:09:25 · JŁ:** Sure, sure. +- **21:09:26 · Jonathan Jackson:** Bartek, if you want to create an incident for us, you're welcome to. +- **21:09:26 · Andre Martingo:** Good. Just a comment. Super nice. It's interesting because I was checking as well. I don't know if you saw the Windows release what they call a comment center. They have kind of an internal website. that contains… like, I think what you built plus more steps, um, and it was something that I was looking at once I finished Smartling, so I will get in touch with you. I don't know… at this point, what's the difference between an artifact or a web page itself, uh, inside of DuckDuckGo, but it's something, uh, that maybe we can… we can chat afterwards. Uh, but it's quite nice as well. Nice. +- **21:10:18 · Jonathan Jackson:** Cool. Thank you. Jacek, when you're ready, it'd be great if you could share that with the team as a starting place, obviously. +- **21:10:24 · JŁ:** Sure, sure. +- **21:10:25 · Jonathan Jackson:** Cool. Uh, Andre, your SmartLink update is up next. +- **21:10:31 · Andre Martingo:** So yeah, just a quick update. So everything should be done. I made a post. Me and Pao, we already kind of enabled or kind of disabled the Avenger warning. So I hope you'll start merging into main your untranslated strings. I have here as well an artifact since it's the new cool thing to do. Um… So basically, it was just an exploration about… how much we were spending per release in SmartLink, so maybe this will help us to move to AI, but other than that, it was to track. when are we starting using, kind of, the new flow. So, basically, here you have a graph of spending per release in terms of dollars, and the blue bars are, kind of, our new automatic flow. Um, so we are spending an average of, like, 500, 400, depending on the release. Um, and basically, here in this artifact, you can see, like. Which ones are the jobs that got merged automatically, or which ones are manual, so we can still… we can track, like, the usage of our new flow. And hopefully, maybe with some data, we can start thinking if it would be possible to move to AI, compare the prices, or maybe just A/B test for one language. It's something for the future we can maybe try to push for. But for now, it's just to collect… some stats so we can have better discussions over it. +- **21:12:10 · Jonathan Jackson:** That's cool. Thank you. Yeah, if you want to share that somewhere so that people can find it on a regular basis, that'd be great. How have you seen, I know it's early, but on the nightly untranslated pieces, how quickly have those jobs from SmartLine been coming back? +- **21:12:31 · Andre Martingo:** Sorry, which ones? +- **21:12:33 · Jonathan Jackson:** You're basically doing a job every night with whatever was untranslated, right? +- **21:12:39 · Andre Martingo:** Also, but we do every merge commit as well. So basically, once you merge, we trigger a job, and the nightly will… if something goes wrong, it will pick up as well. So the blue bars are kind of the new flow, yeah. +- **21:12:48 · Jonathan Jackson:** Oh, okay. Well, either one. Yeah. Presumably, those are usually smaller jobs for SmartLink. I was wondering how quickly they'd been turning those around recently. +- **21:13:00 · Andre Martingo:** Yeah, actually, we have another one where we have the kind of turnover of PRs for Smartling, but I will share afterwards once we have more data. We didn't have much, no. +- **21:13:07 · Jonathan Jackson:** Mm-hmm. Okay. Yeah, I know it's early still. All right, cool. Thank you. Um… That's our planned agenda for the day. Any other thoughts, questions, comments, things to share, demos? All right. A quick meeting today, but some good stuff. Thank you, everyone. Good to see you, and I hope you have a good day. diff --git a/work/zoom-transcripts/index.json b/work/zoom-transcripts/index.json index 9fe58d26..2683c8ec 100644 --- a/work/zoom-transcripts/index.json +++ b/work/zoom-transcripts/index.json @@ -386,8 +386,8 @@ "note_modified_at": "2026-11-17T15:00:56.296Z", "source_url": "https://us01mynotes.zoom.us/GJhjFoDDRY6PkqEUdM-YFg", "folder": "2026-11-17 Apple Weekly Team Meeting - Zoom ID GJhjFoDDRY6PkqEUdM-YFg", - "sha256": "22c2c60c7a01fe8692c3e347c12beaa43102161292c468734320db978739bb11", - "cues": 3 + "sha256": "cd06af7a61ede6d4cd5d78b6ed94d9c6650c99a66d637cdf0e2eba0fef6390c5", + "cues": 48 } } } diff --git a/work/zoom-transcripts/sync-status.json b/work/zoom-transcripts/sync-status.json index 99a5fb79..9beae870 100644 --- a/work/zoom-transcripts/sync-status.json +++ b/work/zoom-transcripts/sync-status.json @@ -1 +1 @@ -{"observed_at":"2026-11-19T12:38:10.672Z","scanned":31,"imported":3,"skipped":28,"withoutTranscript":0,"coverage":"complete","sections":[{"name":"Owned by me","pages":5,"notes":86,"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":86,"gaps":[],"recovered_transcripts":0,"policy":"reread_all_owned_shared_and_starred_notes_since_cutoff","since":"2026-09-30"} \ No newline at end of file +{"observed_at":"2026-11-19T13:09:32.170Z","scanned":31,"imported":1,"skipped":30,"withoutTranscript":0,"coverage":"complete","sections":[{"name":"Owned by me","pages":5,"notes":86,"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":86,"gaps":[],"recovered_transcripts":0,"policy":"reread_all_owned_shared_and_starred_notes_since_cutoff","since":"2026-09-30"} \ No newline at end of file