diff --git a/work/zoom-transcripts/2026-10-15 Dominik Kapusta's Personal Meeting Room 2026-10-15 16 05(GMT+6 00) nzWOuhyzSdCjNqMRh6X13w/transcript.json b/work/zoom-transcripts/2026-10-15 Dominik Kapusta's Personal Meeting Room 2026-10-15 16 05(GMT+6 00) nzWOuhyzSdCjNqMRh6X13w/transcript.json index 1240d8f3..681692f1 100644 --- a/work/zoom-transcripts/2026-10-15 Dominik Kapusta's Personal Meeting Room 2026-10-15 16 05(GMT+6 00) nzWOuhyzSdCjNqMRh6X13w/transcript.json +++ b/work/zoom-transcripts/2026-10-15 Dominik Kapusta's Personal Meeting Room 2026-10-15 16 05(GMT+6 00) nzWOuhyzSdCjNqMRh6X13w/transcript.json @@ -23,1651 +23,6 @@ "time": "16:05:25", "speaker": "Dominik Kapusta", "text": "Отгод. Гуд. Туф. Ера." - }, - { - "time": "16:05:27", - "speaker": "Alex Martemyanov", - "text": "Eventful week. Let's see. A lot of things happening in parallel. And yeah, for today, I kinda… Already tired. Probably still not 100% recovered. But, yeah, anyways, I tried to update our agenda." - }, - { - "time": "16:05:45", - "speaker": "Alex Martemyanov", - "text": "Бад. Я. Энивэйс?" - }, - { - "time": "16:05:46", - "speaker": "Dominik Kapusta", - "text": "Я?" - }, - { - "time": "16:05:53", - "speaker": "Alex Martemyanov", - "text": "And, uh… Yeah, so basically… From the last update, from the last Friday's update on my top priority, there is… Not much of actual update happened since I spent most of the Monday. And… with the… It abuse the incident thing. The other stuff, and just get to the…" - }, - { - "time": "16:06:21", - "speaker": "Dominik Kapusta", - "text": "Ням?" - }, - { - "time": "16:06:24", - "speaker": "Alex Martemyanov", - "text": "Do the actual priority thing, and uh… Today, I'm… trying to get through it, and first of all, it's blocked with this, uh, domain name called Crash. The time kinda keep iterating. Miss Claude." - }, - { - "time": "16:06:40", - "speaker": "Dominik Kapusta", - "text": "Вот краш вот. Краш. Свои?" - }, - { - "time": "16:06:42", - "speaker": "Alex Martemyanov", - "text": "The domain and the domain and code, the WebKit proxy error thing." - }, - { - "time": "16:06:46", - "speaker": "Dominik Kapusta", - "text": "А. Аа, Окей?" - }, - { - "time": "16:06:49", - "speaker": "Alex Martemyanov", - "text": "Yeah, I'm just, uh… I'm just about to open it, and just final validation of the bills passing. I'm just basically ready, and I'll ping you if you can. Uh, it goes to a normal… normal release, since it's not… Not high occurrences are normally on the 86 machines, but anyways, it's naturally preceding the telemetry fix and all the other stuff. Yeah, and on the top priority, I got several stages. I think there is, um… Three, four. Even… Yeah, at least three VRs. Stacked PRs pending. So first of all, we need adjusting the attribution because currently it misses some identified points. And, uh, we need some proofs of it, actually. of the events actually happening. So basically, I've identified it to… The background issue is lock screen or unloading browser and the network process crash that may also. I don't know. We affected the CPM error and basically those like 80% of the telemetry." - }, - { - "time": "16:08:18", - "speaker": "Dominik Kapusta", - "text": "Окей?" - }, - { - "time": "16:08:25", - "speaker": "Alex Martemyanov", - "text": "It got reproduced in the. Best homeless setup. That was made for evaluating the theories. So, if it goes well, we should… We should probably cover like 80% of those and hopefully receive some extra data to cover the rest. Um, so… That's moving, although I'm kind of feeling a little… Bring the trade. and all of this. Uh, but yeah, I was hoping to open everything today so we could review it tomorrow, but realistically… It's probably gonna be only the attribution fix, so request for today and the crash fix. And for tomorrow, yeah. I'll try to… Uh, to discuss it with Michal, if we can… We can get it through." - }, - { - "time": "16:09:30", - "speaker": "Dominik Kapusta", - "text": "All right. Uh, okay." - }, - { - "time": "16:09:32", - "speaker": "Alex Martemyanov", - "text": "So, yeah, later today, I'll give an update on the project, uh, when I… when I have the request open." - }, - { - "time": "16:09:35", - "speaker": "Dominik Kapusta", - "text": "Mm-hmm. Yeah, sure." - }, - { - "time": "16:09:40", - "speaker": "Alex Martemyanov", - "text": "So, it may be…" - }, - { - "time": "16:09:43", - "speaker": "Dominik Kapusta", - "text": "Yeah, uh, I'm looking at these fixed CPM breakage issues. Breakage. WebKit issues, I guess. Uh, and there are four subtasks, which…" - }, - { - "time": "16:09:51", - "speaker": "Alex Martemyanov", - "text": "Yep." - }, - { - "time": "16:09:56", - "speaker": "Dominik Kapusta", - "text": "So there will be four pull requests?" - }, - { - "time": "16:09:57", - "speaker": "Alex Martemyanov", - "text": "All of them have contacts." - }, - { - "time": "16:10:00", - "speaker": "Dominik Kapusta", - "text": "Double." - }, - { - "time": "16:10:00", - "speaker": "Alex Martemyanov", - "text": "Yes, I guess so." - }, - { - "time": "16:10:01", - "speaker": "Dominik Kapusta", - "text": "Mmhm. Okay." - }, - { - "time": "16:10:03", - "speaker": "Alex Martemyanov", - "text": "I'm planning to… to give it some… details in the research and in the tasks themselves. on, uh… kind of describing the approaches, but yeah, it comes a bit later. So, yeah, it's to be updated. They'll post in a project a bit later today." - }, - { - "time": "16:10:27", - "speaker": "Dominik Kapusta", - "text": "Sounds good." - }, - { - "time": "16:10:28", - "speaker": "Alex Martemyanov", - "text": "So, yeah, last week. Last week after. All of that kind of got some toxication. Uh, which… Luckily gave me like a couple of days. To just get relaxed a little bit. Yeah, but meanwhile, yesterday, I got some… Oh, I… Got some time… like lazy white coding on the extra project projects. And I got some results you may have seen. So, basically, there is the tech design for the VS Code integration updated. Yeah, basically, I've posted the update. Thanks for all the input." - }, - { - "time": "16:11:14", - "speaker": "Dominik Kapusta", - "text": "Mm-hmm." - }, - { - "time": "16:11:18", - "speaker": "Alex Martemyanov", - "text": "And, uh, having all of that, I actually found a way that will work and, uh, that doesn't touch the current." - }, - { - "time": "16:11:19", - "speaker": "Dominik Kapusta", - "text": "Yeah." - }, - { - "time": "16:11:28", - "speaker": "Alex Martemyanov", - "text": "I mean, current project structure, it's, uh… It's a little… it's a small wrapper over the Xcode language." - }, - { - "time": "16:11:38", - "speaker": "Dominik Kapusta", - "text": "Ahem." - }, - { - "time": "16:11:38", - "speaker": "Alex Martemyanov", - "text": "The server, which uses the same architecture. Uh, as Xcode does for…" - }, - { - "time": "16:11:45", - "speaker": "Dominik Kapusta", - "text": "Mmhm." - }, - { - "time": "16:11:46", - "speaker": "Alex Martemyanov", - "text": "sources indexing, and it used the same Swift build system. that Xcode27 is using under the hood now, so we should be pretty much aligned on this. Even though the repo or the project itself is pretty young, I think we could easily fork it since it's released." - }, - { - "time": "16:11:57", - "speaker": "Dominik Kapusta", - "text": "Mmhm." - }, - { - "time": "16:12:07", - "speaker": "Alex Martemyanov", - "text": "Really small rubber, and uh… And keep…" - }, - { - "time": "16:12:14", - "speaker": "Dominik Kapusta", - "text": "Okay." - }, - { - "time": "16:12:16", - "speaker": "Alex Martemyanov", - "text": "And coupons, that's… for me." - }, - { - "time": "16:12:20", - "speaker": "Dominik Kapusta", - "text": "Um…" - }, - { - "time": "16:12:20", - "speaker": "Alex Martemyanov", - "text": "Because of, kind of, security and privacy concerns, and uh…" - }, - { - "time": "16:12:24", - "speaker": "Dominik Kapusta", - "text": "Fine, yeah, yeah, I think it would require… Something like a vendor triage… dependency… Triage, or tool triage, whatever it's called, but it's essentially, like, a tool that we want to use, and… And because of that, we might want to perform some checks on it." - }, - { - "time": "16:12:50", - "speaker": "Alex Martemyanov", - "text": "Yeah, there is a related question in the tech design, so basically I've assigned it to you if you can. And you may leave the comments on it." - }, - { - "time": "16:12:58", - "speaker": "Dominik Kapusta", - "text": "Mmhm." - }, - { - "time": "16:13:03", - "speaker": "Alex Martemyanov", - "text": "Yeah, so basically that should work, and… Keeping things moving and finally resolve the project. Maybe maybe a good thing to the. Career review thing. Like, moving the team forward and finishing the effort. And with the following… With the following tests update. I actually got it locally, so basically it's a buildable folder and unlinking the AppDelegate dependency. it just waits for, uh, for the tech design to be approved. Yeah, basically, it only depends on the main… main branch, it's not related to VS Code. But it works, iOS works with simulator." - }, - { - "time": "16:13:52", - "speaker": "Dominik Kapusta", - "text": "Mmhm." - }, - { - "time": "16:13:53", - "speaker": "Alex Martemyanov", - "text": "macOS network, everything just works. Oh…" - }, - { - "time": "16:13:57", - "speaker": "Dominik Kapusta", - "text": "That's good, that's good." - }, - { - "time": "16:14:00", - "speaker": "Alex Martemyanov", - "text": "And yeah, there is only one issue about export build, and it's a package resolution thing that I was trying to get rid of, but maybe I'll get through it with some local fork. Just for myself or for anybody who's interested, if… if it would be the use case. Basically, I expect a couple of… team members to adopt it, or at least take a look, maybe it works for somebody. Especially having the next things, which are in my, uh… Stick in the artwork. So basically, I. Uh, pretty much completed the, uh, virtual machine manager thing that I mentioned, kind of, half a year ago. Started work on it, so it's migrated to… Another build system… It supports remote machines like old MacBook that just works. You can see it. Sorry. It just works directly from MCP, and even if I can crash machines, but I won't advertise on the team, but anyways, I have one. And be used for virtual machines testing as well. Uh, it just works. So, um, Claude and ChatGPT, when I ask to…" - }, - { - "time": "16:15:20", - "speaker": "Dominik Kapusta", - "text": "Okay." - }, - { - "time": "16:15:25", - "speaker": "Alex Martemyanov", - "text": "validate the tests on macOS 27 or macOS 12, it just says, okay, I will set up the virtual machine, I'm getting the lease, I've run the tests, the bug is reproduced, it's fixed. Uh… So that's another part of the… AR work and developers help, and there is integration for VS Code as well, so you could just run the virtual machine and run the build. from VS Code, and there is no hanging at launch, it just works natively, and you can run UI tests in it, not blocking your main working machine. So, basically, the project is moving really, really well." - }, - { - "time": "16:16:06", - "speaker": "Dominik Kapusta", - "text": "Mm, mm-hmm." - }, - { - "time": "16:16:07", - "speaker": "Alex Martemyanov", - "text": "And I expected to have some to make some contribution to the team when I when I finish. Approving this." - }, - { - "time": "16:16:18", - "speaker": "Dominik Kapusta", - "text": "Yeah, that's good. I mean, it's a lot. It is a lot. So allow me to digest it." - }, - { - "time": "16:16:20", - "speaker": "Alex Martemyanov", - "text": "Great, thank you." - }, - { - "time": "16:16:26", - "speaker": "Dominik Kapusta", - "text": "Piece by piece. But, uh… Um… Can maybe talk about the tech design later. VS Code and Xcode preferably server. Fine. The other thing you've just mentioned, it's what's on that diagram." - }, - { - "time": "16:16:55", - "speaker": "Alex Martemyanov", - "text": "Uh, the diagram, yeah, that's just another quick, uh, quick call of yesterday's date." - }, - { - "time": "16:16:56", - "speaker": "Dominik Kapusta", - "text": "In the agenda?" - }, - { - "time": "16:17:02", - "speaker": "Alex Martemyanov", - "text": "From my bed. Oh… It's, uh, basically… Agent setup analysis for automatic bug and crash fix workflow. I just… had its one short run, and asked to summarize everything we've had for a century, and what Android and Windows teams have. Uh, so this is kind of first one-shot diagram that it came with, analyzing the signals. So we have, uh… manual trigger from Asana, like tagging or mentioning a bot. Uh, we have a new crash events, or we have a CI failure, uh, that, uh, first runs. a cloud agent or Linux with Sentry and Asana access, analyzes the code, the task, and. everything, and then runs an isolated runner on Bitrise. that reproduces UI tests or unit tests, collects the evidence, tries to fix, iterates, and proceeds opening pull requests with a fix or no hope. With automated MetaMoose and Basana comment. Not sent by a bot because of the incident one, and, but, posted by by the automation." - }, - { - "time": "16:18:30", - "speaker": "Dominik Kapusta", - "text": "Hmm, yeah." - }, - { - "time": "16:18:35", - "speaker": "Alex Martemyanov", - "text": "And then the last step, yeah, the bottleneck of the human review, the approval. Which, if in case of the test runs, the test runs… By the way, I just got another test run that just passed, and I'm probably gonna use the Fernando proposal to just merge it. Um, there's one self-review." - }, - { - "time": "16:18:55", - "speaker": "Dominik Kapusta", - "text": "Amanda proposal." - }, - { - "time": "16:18:58", - "speaker": "Alex Martemyanov", - "text": "Uh, they self-review for test fixes." - }, - { - "time": "16:19:02", - "speaker": "Dominik Kapusta", - "text": "Ah, yeah, yeah, sure." - }, - { - "time": "16:19:04", - "speaker": "Alex Martemyanov", - "text": "Yeah, so yeah, it's basically an automated run. fixing the… my local automators around fixing the Discover, DUI tests issues. Uh… So… It should run the same thing, but online using agent runners. And, uh… So yeah, basically we have a first. First AI iteration of it, so I could… Choose from what to move next when I have some time." - }, - { - "time": "16:19:40", - "speaker": "Dominik Kapusta", - "text": "All right. What you're doing is… It's great in terms that… It's… These are great ideas for the team, for sure. Uh, the thing is, it is being worked on already in a few places, and it would be great to coordinate that work, or maybe join that work. Uh, we are currently… figuring out… Bitrise… well, not Bitrise, but, uh, essentially infrastructure for… Running Agentic workflows on… for Apple team. And… I said Bitrise because I'm involved in a Bitrise task, which is about Bitrise remote development environments, which is their new feature that they… where they just…" - }, - { - "time": "16:20:32", - "speaker": "Alex Martemyanov", - "text": "Okay." - }, - { - "time": "16:20:41", - "speaker": "Dominik Kapusta", - "text": "just provide macOS virtual machines that you can use for that. They come with Xcode and Claude pre-installed, and… Yeah. Okay. What I was doing is I was trying to get the build to pass on these machines, like, set everything up… as close to our CI setup as possible. And I think it worked in the end, I need to… Uh, leave for a moment today, but… Yeah, I think it works." - }, - { - "time": "16:21:17", - "speaker": "Alex Martemyanov", - "text": "Yeah, you mean the… the runner automation thing? Yeah, again, I, uh, haven't spent…" - }, - { - "time": "16:21:20", - "speaker": "Dominik Kapusta", - "text": "Yeah, we…" - }, - { - "time": "16:21:24", - "speaker": "Alex Martemyanov", - "text": "Actually, a minute on it. And just… it's just a one-shot research." - }, - { - "time": "16:21:30", - "speaker": "Dominik Kapusta", - "text": "Just the discussion topic. Okay, okay, fine. Yeah." - }, - { - "time": "16:21:33", - "speaker": "Alex Martemyanov", - "text": "Yeah, so basically a discussion topic to probably involve me into these flows and, yeah, start the coordination." - }, - { - "time": "16:21:37", - "speaker": "Dominik Kapusta", - "text": "Mm-hmm, sure, sure, so I can tell you, I can tell you where we are, I can tell you where we are. We are considering… Actually, one thing that is happening is… Um, enabling… Simple Agentic workflows, like one shot. essentially workflows on GitHub Actions. And, uh, so the idea is you have a workflow where you… Or the prompt? is the input. And the. A workflow just runs, and whatever… whatever the output needs to be, it is. Is it, like, a pull request, or some artifact, whatever. But essentially, like, think of, I don't know, fix this crash, and then it ends up with a pull request. Yeah, um… There is a small problem. We aren't allowed to use… Anthropic. API keys in public repositories. So. To work around that, we are setting up a private repository that will be empty. And just have that token? And the workflows. And the workflow would clone the monorepo." - }, - { - "time": "16:23:04", - "speaker": "Alex Martemyanov", - "text": "Mmhm." - }, - { - "time": "16:23:04", - "speaker": "Dominik Kapusta", - "text": "But it would run in a private repository otherwise. But it would clone the monorepo, and work on the monorepo, and open the pull request in the monorepo. Uh, so the only… the only complication here is that it can't be the monorepo, can't live in the monorepo, but it lives in a private repository that essentially has write access to the monorepo, and that's it. So this is for a single… Like, single-shot, uh… tasks? Where you just… Essentially, you give a task to the agent, and… you don't want to talk to it in the meantime, you don't need to talk to it in the meantime, and then it comes with the result. For longer. Workflows, where you would like to… Intervene. In the meantime, or would you expect to be pinged by the agent? Uh, we can't do it in GitHub Actions, because you can't… stop the… stop the GitHub action workflow, or… essentially take over the control of it. So for that, we just need a remote machine. With… with a cloud session. And you could like SSH into that machine for instance or VNC into it and… And take over if needed. And that is being figured out. One possibility is AWS. The problem with AWS is it's $1400 per month per machine. So, we're also evaluating Bitrise on that, and Bitrise would be definitely cheaper, and it comes with… Well, the VM images are prepared for Apple development. They have Xcode, they have plenty of other tools. installed Ruby and so on and so on. So that's what we're… dealing with now, going through security triages and so on and so on. Um, oh." - }, - { - "time": "16:25:17", - "speaker": "Alex Martemyanov", - "text": "What's the problem with the… With it. Why do we have to SSH to another machine?" - }, - { - "time": "16:25:28", - "speaker": "Dominik Kapusta", - "text": "Well, we don't have to, but… If we want to… we wouldn't be able to in a GitHub Action workflow. I'm." - }, - { - "time": "16:25:40", - "speaker": "Alex Martemyanov", - "text": "Okay." - }, - { - "time": "16:25:41", - "speaker": "Dominik Kapusta", - "text": "And, yeah, well, whatever, you don't need to SSH into it, but you might want to… Connect to a cloud session on such machine. to see… what's going on there, and I don't know, to… to provide further instructions to the agent, and so on and so on. Uh, I also… to be completely fair, I don't… fully follow that use case yet. I'm… I clearly understand the need for, uh, simple workflows, like, please fix this, please do this, and so on and so on. Make no mistakes. But these interactive sessions, they are a bit… A bit strange to me, but… Yeah, people that have more experience than me suggested that we would need this. Uh, I guess it may… it may be about, um… Just doing work on a remote machine, rather than a local machine. Just like this, right? So you can do it locally, but you can also do it remotely. I'm not entirely sure how much it would, uh… we would benefit from it. Umm. Let's see." - }, - { - "time": "16:27:04", - "speaker": "Alex Martemyanov", - "text": "Yeah, like having a… remote testing machine with BNC, and uh… Agent runs, and even remote building from… from the VS Code. Uh, it may be a good option, since not everybody has, like, as new of machine as I… of machines as I do. And ability to run those. So probably we could." - }, - { - "time": "16:27:25", - "speaker": "Dominik Kapusta", - "text": "Mm-hmm." - }, - { - "time": "16:27:29", - "speaker": "Alex Martemyanov", - "text": "Integrate. And that point as well, somehow. So just maybe ping me in the related tasks and." - }, - { - "time": "16:27:34", - "speaker": "Dominik Kapusta", - "text": "Yeah, yeah." - }, - { - "time": "16:27:38", - "speaker": "Alex Martemyanov", - "text": "I'll see where can we… Integrate. and distribute the work. Okay." - }, - { - "time": "16:27:55", - "speaker": "Dominik Kapusta", - "text": "Yeah, I can try to involve you here and there or just give you links. Because, because, because, because one of them is this one. This is one of them. That's for the simple workflows and the other one is… this. And this Bitrise thingy is a subtask of. of a full project called \"Find an alternative to Cursor Cloud Agents to safely run autonomous workflows\"." - }, - { - "time": "16:28:48", - "speaker": "Alex Martemyanov", - "text": "Mm-hmm." - }, - { - "time": "16:28:53", - "speaker": "Dominik Kapusta", - "text": "One other limitation of GitHub Actions is that. Any workflow can only run for 6 hours, so in case we have some long, long jobs… It would just stop after six hours. and be deleted and forgotten." - }, - { - "time": "16:29:12", - "speaker": "Alex Martemyanov", - "text": "Yeah, generally, the ramps should not… List for cigarette rollers." - }, - { - "time": "16:29:17", - "speaker": "Dominik Kapusta", - "text": "Yeah, they shouldn't. I agree. Oh, all right." - }, - { - "time": "16:29:29", - "speaker": "Alex Martemyanov", - "text": "Yeah." - }, - { - "time": "16:29:31", - "speaker": "Dominik Kapusta", - "text": "All right, so that's this. For the tech design. I will have a look later. I saw there are some comments already, and overall the reception is… is better. Probably because… It's opt-in, and it doesn't change anything that we have. Um… Yeah, some of the requirements of your previous design were… hard to… Hard to just, you know… agree on without, without, uh…" - }, - { - "time": "16:30:06", - "speaker": "Alex Martemyanov", - "text": "Accept." - }, - { - "time": "16:30:10", - "speaker": "Dominik Kapusta", - "text": "No. Like… It was just, essentially it was just refactoring, refactoring a lot of code in order to maybe have some benefits, but also there were, like, a significant part of these benefits would be achievable without all these changes, so… I'm glad that we're gonna be switching to buildable folders, which will simplify the project file drastically. And then there's this other thing. that I have forgotten in the meantime. Oh, yeah, uh, removing the host application from tests." - }, - { - "time": "16:30:48", - "speaker": "Alex Martemyanov", - "text": "Uh, I think it's not removing, but uh… Because since we run it in Xcode and not as a package, we cannot remove the host application." - }, - { - "time": "16:31:01", - "speaker": "Dominik Kapusta", - "text": "But you don't launch it in UI tests, in unit tests." - }, - { - "time": "16:31:04", - "speaker": "Alex Martemyanov", - "text": "Relaunch it." - }, - { - "time": "16:31:06", - "speaker": "Dominik Kapusta", - "text": "But if you set it to none, do you still launch it?" - }, - { - "time": "16:31:06", - "speaker": "Alex Martemyanov", - "text": "But, uh… You cannot launch it if you don't have it. Because it's run against the host application from Xcode. And if you want to run to remove the host application, you have to convert it to the library as it was in the initial design." - }, - { - "time": "16:31:26", - "speaker": "Dominik Kapusta", - "text": "So what happens? If I go here… and here and do this. What does this really change?" - }, - { - "time": "16:31:38", - "speaker": "Alex Martemyanov", - "text": "Mmhm. I suppose it won't. Build the tests." - }, - { - "time": "16:31:51", - "speaker": "Dominik Kapusta", - "text": "It works. It's what I wrote in the comment on your initial tech design. I set it to none, and it works. The only tests that are failing were the CBR…" - }, - { - "time": "16:31:52", - "speaker": "Alex Martemyanov", - "text": "Or maybe, uh… Excuse me." - }, - { - "time": "16:32:03", - "speaker": "Dominik Kapusta", - "text": "Tests. No." - }, - { - "time": "16:32:09", - "speaker": "Alex Martemyanov", - "text": "Okay, good. I'll reiterate about it." - }, - { - "time": "16:32:12", - "speaker": "Dominik Kapusta", - "text": "Okay." - }, - { - "time": "16:32:12", - "speaker": "Alex Martemyanov", - "text": "Anyways, uh… anyways, it's ready without… even without it. And, uh… The fix there was just to… To inject the… An empty app delegate." - }, - { - "time": "16:32:26", - "speaker": "Dominik Kapusta", - "text": "Yeah, yeah, that was… that was the thing that came to my mind initially. We can… we can have another app that I get, and then…" - }, - { - "time": "16:32:26", - "speaker": "Alex Martemyanov", - "text": "Instead of the apps that I'm gonna get." - }, - { - "time": "16:32:36", - "speaker": "Dominik Kapusta", - "text": "I think it's a build setting, the app delegate is also a build setting somewhere, or the… yeah." - }, - { - "time": "16:32:39", - "speaker": "Alex Martemyanov", - "text": "Yeah, so anyways, I'm getting to it, and it's independent from VS Code or anything else, and when I…" - }, - { - "time": "16:32:44", - "speaker": "Dominik Kapusta", - "text": "Yeah, yeah. Mm-hmm." - }, - { - "time": "16:32:47", - "speaker": "Alex Martemyanov", - "text": "Wipe, wipe out the current priority work." - }, - { - "time": "16:32:53", - "speaker": "Dominik Kapusta", - "text": "Mm-hmm." - }, - { - "time": "16:32:53", - "speaker": "Alex Martemyanov", - "text": "On my table, and uh… I'll come back to it and. And, uh… and modularization items as well." - }, - { - "time": "16:33:05", - "speaker": "Dominik Kapusta", - "text": "Mmhm." - }, - { - "time": "16:33:05", - "speaker": "Alex Martemyanov", - "text": "So, maybe when, uh… when we have the browser modularized, like, finalized, we could reiterate over the SPM package, as it would be a logical next step, or maybe we didn't change. Uh, with the next, next code release. Uh, like, Apple providing several…" - }, - { - "time": "16:33:23", - "speaker": "Dominik Kapusta", - "text": "Hmm." - }, - { - "time": "16:33:25", - "speaker": "Alex Martemyanov", - "text": "Steps further." - }, - { - "time": "16:33:26", - "speaker": "Dominik Kapusta", - "text": "Mm-hmm." - }, - { - "time": "16:33:27", - "speaker": "Alex Martemyanov", - "text": "to the SPM compilation, as it seems. Uh, so… yeah, we'll get there." - }, - { - "time": "16:33:35", - "speaker": "Dominik Kapusta", - "text": "Okay. Okay, nice. One other thing that we need to do today. which is slightly overdue, is the… Continuous development check-in. Which means we should talk about growth areas and shoutouts as well, actually, of course. They are here. Yeah, it's a private task, but you have access. um… So we… We talked about… uh, the communication overall. And… um… For this… Like then, what was the next steps was that you're moving again from ON to OE into a new… Environment, new people… And there was just this reminder to use your project advisor, to bring questions, to… to provide updates in the project and so on and so on. And… What do you think about… About this growth area, about the other growth area perhaps as well, because we can keep it, we can… Call it done. We can create a new one. My. Personal feeling is that. It still needs some work. But curious about your perspective." - }, - { - "time": "16:35:40", - "speaker": "Alex Martemyanov", - "text": "So, I don't know… Very good question. So generally, we… It's the last… iteration. We've had several projects, like. And… The most complicated one is probably the current one, and uh…" - }, - { - "time": "16:35:58", - "speaker": "Dominik Kapusta", - "text": "Mmhm." - }, - { - "time": "16:36:01", - "speaker": "Alex Martemyanov", - "text": "So general directions there were initial communications over the project structure. I will proceed and." - }, - { - "time": "16:36:11", - "speaker": "Dominik Kapusta", - "text": "Mmhm." - }, - { - "time": "16:36:12", - "speaker": "Alex Martemyanov", - "text": "Several need more time suggesting the roadmap. Oh. Otherwise, there were just regular project updates on the current state and expectations with some corrections as required. And… So about bringing question and doubts. I'm not sure here, because I think there were a couple of. question and doubts that I brought to the project advisor on what. What's better to do, or how to iterate over it, or should we apply this, or have a bigger iteration on the better solution?" - }, - { - "time": "16:36:49", - "speaker": "Dominik Kapusta", - "text": "Mm-hmm. Mmhm." - }, - { - "time": "16:36:56", - "speaker": "Alex Martemyanov", - "text": "Or, uh… Aligning on the… on the roadmap, I mean, on schedule, like on reviews and… our release dates. So… Generally, from my perspective, I… Try to keep it. Up to date and keep people updated when it's… when something happens, or like, nothing happens if I…" - }, - { - "time": "16:37:25", - "speaker": "Dominik Kapusta", - "text": "Yeah, okay." - }, - { - "time": "16:37:28", - "speaker": "Alex Martemyanov", - "text": "Um, if there is… if there is a slowdown, for example, for some reason." - }, - { - "time": "16:37:29", - "speaker": "Dominik Kapusta", - "text": "Right. Yeah, yeah, and that's good. If you… So when you reach out to the project advisor, do you do it on Inasana or Mattermost?" - }, - { - "time": "16:37:48", - "speaker": "Alex Martemyanov", - "text": "Mmm…" - }, - { - "time": "16:37:48", - "speaker": "Dominik Kapusta", - "text": "Is it in the comms task or some other tasks?" - }, - { - "time": "16:37:53", - "speaker": "Alex Martemyanov", - "text": "I think it's mostly in MetaMOST, but sometimes there is some… So basically, project update iteration, if there was some…" - }, - { - "time": "16:37:56", - "speaker": "Dominik Kapusta", - "text": "Mmhm. Mmhm." - }, - { - "time": "16:38:02", - "speaker": "Alex Martemyanov", - "text": "If there was some decision." - }, - { - "time": "16:38:04", - "speaker": "Dominik Kapusta", - "text": "Mm-hmm. Good. What I can… suggest, maybe, is… because, like, at least looking at, uh, at this task…" - }, - { - "time": "16:38:18", - "speaker": "Alex Martemyanov", - "text": "Yeah, there is not much of the communication happening on the top." - }, - { - "time": "16:38:18", - "speaker": "Dominik Kapusta", - "text": "for… You know, there is not much communication, but there are also two instances of, uh… career advisor asking… I mean, sorry, project advisor asking you for… for the status?" - }, - { - "time": "16:38:34", - "speaker": "Alex Martemyanov", - "text": "Uh, and actually, I was just writing the project update, and in the moment, he was asking." - }, - { - "time": "16:38:34", - "speaker": "Dominik Kapusta", - "text": "And." - }, - { - "time": "16:38:40", - "speaker": "Alex Martemyanov", - "text": "Uh, about the status…" - }, - { - "time": "16:38:41", - "speaker": "Dominik Kapusta", - "text": "Mmhm." - }, - { - "time": "16:38:43", - "speaker": "Alex Martemyanov", - "text": "And…" - }, - { - "time": "16:38:43", - "speaker": "Dominik Kapusta", - "text": "And." - }, - { - "time": "16:38:46", - "speaker": "Alex Martemyanov", - "text": "And yeah, you mean making the communication more visible and go through the communication tasks?" - }, - { - "time": "16:38:50", - "speaker": "Dominik Kapusta", - "text": "Making the… if the communication happens, making it visible would be great. what I noticed, uh… Diego did on a couple of occasions. We were on a Zoom call, and he would put a summary of a Zoom call in the communication task. Just, you know, just some bullet points, just to…" - }, - { - "time": "16:39:14", - "speaker": "Alex Martemyanov", - "text": "Mm-hmm." - }, - { - "time": "16:39:17", - "speaker": "Dominik Kapusta", - "text": "to make it clear that the communication happens. And it's also valuable… of course, it's valuable to everyone who reads the task, but it's also valuable to yourself and to the project advisor, because project advisor. I mean, more to the project advisor, of course, because you… this is your top priority, but this is not project advisor's top priority, and they may have more work, and they may be forgetting things, so it's great to… To just… Note down. Oh. whatever is happening, right? If you… even if you chat on Mattermost, and you have, like, a… some exchange of messages in Matrimos that is valuable, and where you learn something. It's a great… Um, great, uh, habit to… to just, you know… put it in Asana as well. Just as a documentation that things are happening. When it comes to project updates. It's… It's probably… I wanted to say that, well, I can see you're posting frequent updates when needed. There's an update from 7th of October and then the update from 9th of October. Because some people get fixed on that. rows weekly… I mean, write weekly updates, and then they put one update a week, and they're fine with that. But it's not… always enough to just write one update a week. So that's good. But… What I would like to see… And this CPM project is not looking… I mean, it's looking fine, right? People seem to be… okay with your communication there, but then there is… like, the communication does not end on your project, your top priorities. We had an example with this VS Code initiative where… Well, some comments started popping up on your project task. And you remember, like, I was pinging you to put a comment there, uh, like. Calm them down, because the situation was that some people wrote some comments and… The last one was from Juan. The last one was from Juan, and um… And he just… asked you explicitly, could you talk more about the benefits of the project structure, cleanup, and coding standards we'll get from these changes? And… I know that. you… your idea was to write a tech design, and that's also what we agreed on on Apple Weekly. Another weekly meeting, I think it went well overall, where you calmed people down, essentially. But not everyone was on the call. And then if you come back to that project, you see that project in Asana, and you still see Juan's comment there, which is unanswered. It would be great to respond to it. Could you talk more about the benefits of the project structure cleanup? I mean, yes… I'm about to write everything down in a tech design. So we'll see, and… yeah, I saw your comment, I read your comment, and I will address it. Sometimes this is… Fine. Um, there were actually some… some agreements on the Apple Weekly Call that you could put in writing over there, like, yeah, you'll write the tech design, and then we'll talk about it, and it's not… what was very important to me, I think, at least, was that… it's not strictly about VS Code integration, but also it's… It's a way of speeding up builds, cleaning up project structure, and so on and so on. So… This could have been put there in a comment. Otherwise, people were… a bit lost in all of this, and they were… Actually, I have to say they were afraid." - }, - { - "time": "16:44:17", - "speaker": "Dominik Kapusta", - "text": "about what's happening, because it's a lot of changes, and… Of course, we don't like changes, no one likes big changes, especially if they are not clearly backed by some proper reasoning. Um, so… So that was that. And then when I… then when I… kept pinging you for a couple of days, you told me, oh, I'm writing a tech design, I'll update later, I'll say, fine. And then you only wrote the comment that the tech design is ready, so please go read a tech design. Go and retake design. Which, yeah, it was a bit… a bit late as well, but uh… What I… what I suggested you on our Mattermost chat, it's essentially, you know, just put, like, two, three sentences there to calm people down, and you should be fine. Mmm. No. So… So that's something that… That would be great to see going forward. I think. Because… Let me… put it this way. It's clearer than when projects are going… The right way, or… Or not, but as long as it's… On the technical side, good or bad, whatever, you're handling it perfectly. You're just, okay, this is my project, this is the plan, these are the tasks I'm working on, when I'm done with this, I'm gonna do this, and so on and so on. And you're giving proper updates, you're keeping everyone… Well informed. And then… when sometimes something happens, and also, you're fine, like, calling me mid-mortems to decide on technical stuff, and so on, and so on. But if there is this… This, how to say, um, well, someone raising something, uh, having doubts. Then it gets tricky. Essentially it gets tricky and you may be. A bit lost, I don't know. I'm just still trying to…" - }, - { - "time": "16:47:08", - "speaker": "Alex Martemyanov", - "text": "Yeah, I just tried to go through the actual comment to reason about it and to." - }, - { - "time": "16:47:15", - "speaker": "Dominik Kapusta", - "text": "Yeah." - }, - { - "time": "16:47:16", - "speaker": "Alex Martemyanov", - "text": "Basically, to iterate over it so it gets to my… Incoming queue, and uh…" - }, - { - "time": "16:47:21", - "speaker": "Dominik Kapusta", - "text": "Mm-hmm." - }, - { - "time": "16:47:23", - "speaker": "Alex Martemyanov", - "text": "When I reach to it, I, yeah, answer, basically." - }, - { - "time": "16:47:26", - "speaker": "Dominik Kapusta", - "text": "Mm-hmm, mm-hmm, mm." - }, - { - "time": "16:47:30", - "speaker": "Alex Martemyanov", - "text": "And some comments do require some extra checks." - }, - { - "time": "16:47:34", - "speaker": "Dominik Kapusta", - "text": "Mmhm." - }, - { - "time": "16:47:35", - "speaker": "Alex Martemyanov", - "text": "Uh, switching contexts and, uh, especially having those run as a parallel project." - }, - { - "time": "16:47:37", - "speaker": "Dominik Kapusta", - "text": "No." - }, - { - "time": "16:47:42", - "speaker": "Alex Martemyanov", - "text": "or background projects to the priority. And it may be, yeah, it may require some extra efforts. To marry those." - }, - { - "time": "16:47:54", - "speaker": "Dominik Kapusta", - "text": "You know." - }, - { - "time": "16:47:56", - "speaker": "Alex Martemyanov", - "text": "There's really the incoming, um… Incoming backlog." - }, - { - "time": "16:48:05", - "speaker": "Dominik Kapusta", - "text": "I'm thinking how to… What to do? to also avoid… Being pinged. for updating your project status. I understand that there was a coincidence, like, Michal commented, okay, so how is it going, what are the next steps, and you were just writing an update. But. Yeah, maybe…" - }, - { - "time": "16:48:37", - "speaker": "Alex Martemyanov", - "text": "Yeah, so basically there is a milestone at the end of the week and my evening of Fridays and there is some events like mid-mortems or some plan changes or some re-evaluations." - }, - { - "time": "16:48:41", - "speaker": "Dominik Kapusta", - "text": "Mmhm. Mmhm." - }, - { - "time": "16:48:52", - "speaker": "Alex Martemyanov", - "text": "That I'll post midweek. And, uh…" - }, - { - "time": "16:48:54", - "speaker": "Dominik Kapusta", - "text": "Hmm." - }, - { - "time": "16:48:55", - "speaker": "Alex Martemyanov", - "text": "Generally, otherwise, when, uh… it feels natural for me to post an update, like, when I finish my work on Friday, just to hand over to the, uh…" - }, - { - "time": "16:49:02", - "speaker": "Dominik Kapusta", - "text": "No." - }, - { - "time": "16:49:06", - "speaker": "Alex Martemyanov", - "text": "Uh, to the ones from the US side that are usually running the objectives, and uh…" - }, - { - "time": "16:49:09", - "speaker": "Dominik Kapusta", - "text": "Mm-hmm. Mmhm." - }, - { - "time": "16:49:11", - "speaker": "Alex Martemyanov", - "text": "it feels kinda fine, posting an update in the morning when I didn't finish, and I don't see the outcome yet, and… It's kind of. It may get tricky." - }, - { - "time": "16:49:25", - "speaker": "Dominik Kapusta", - "text": "Okay. Yeah, uh… Oh, okay, okay. All right. Fine, but I will… I would still keep that growth area here, because I think this is the most important thing for you right now. It's to… to be…" - }, - { - "time": "16:49:57", - "speaker": "Alex Martemyanov", - "text": "I'm trying to… To work with it from the different perspective and having some. Yeah, basically, I've also added to the agenda, like, the, uh, the personal OS setup that. And that keeps growing in parallel. I already had some. Local agents analyzing my past work and. current work and just prepare the workflow for the. current status analysis and comparing it to the local work that is being done and tracing the communication requiring my reactions. Just to keep things in focus and maybe post some notifications as… as is required. So to get myself like pinged that. Okay, you already like hyper focus to this task like for 6 h, you should stop for today. Post an update and answer for these 3 comments. So this is the." - }, - { - "time": "16:50:51", - "speaker": "Dominik Kapusta", - "text": "Mm-hmm, mm-hmm. Yeah. Yes." - }, - { - "time": "16:51:03", - "speaker": "Alex Martemyanov", - "text": "should be the case and it's… It's already starts to show something. Building up from it." - }, - { - "time": "16:51:11", - "speaker": "Dominik Kapusta", - "text": "Did you say you put it in the agenda?" - }, - { - "time": "16:51:12", - "speaker": "Alex Martemyanov", - "text": "Oh. No, uh, yes. Uh, yes, I put it to the, uh… The agenda." - }, - { - "time": "16:51:24", - "speaker": "Dominik Kapusta", - "text": "Can't find it." - }, - { - "time": "16:51:24", - "speaker": "Alex Martemyanov", - "text": "Right. Hmm. Where is it?" - }, - { - "time": "16:51:33", - "speaker": "Dominik Kapusta", - "text": "I don't know." - }, - { - "time": "16:51:35", - "speaker": "Alex Martemyanov", - "text": "Sure, it was there. It was in the… Good. Not here. Okay, let's put it here. It was the update that was, uh… the old content, basically, I updated it. Maybe… maybe you just got something from it." - }, - { - "time": "16:51:56", - "speaker": "Dominik Kapusta", - "text": "Oh. Okay, in the old path. Mmhm." - }, - { - "time": "16:52:46", - "speaker": "Alex Martemyanov", - "text": "And… Yeah. So basically what's, it's done there, it's, monitors the activity watch, active window, of course, locally, related to the local work trees, to Asana tasks, loads, the Asana task." - }, - { - "time": "16:53:27", - "speaker": "Dominik Kapusta", - "text": "Mm-hmm." - }, - { - "time": "16:53:29", - "speaker": "Alex Martemyanov", - "text": "full listing and summarizes it to the short project status and key decisions. And, uh, when the new events arrive, uh, they are updated. Um, so… In the perfect world, it should, like… Group up, analyze my current day workflow, analyze the…" - }, - { - "time": "16:53:49", - "speaker": "Dominik Kapusta", - "text": "Mm-hmm." - }, - { - "time": "16:53:51", - "speaker": "Alex Martemyanov", - "text": "week, weekly, uh… weekly plans and career plans and mix it in a balanced set of. Oh. plans and nudges like notifications to react on something or to. Minish Lee. Focus on context switching. It starts getting some shape, so it's currently on the state of current local agent output. Of course, it should be gone through manually in my free time, and I should see the actual project status and what I got from it. And how it understands it, so there's no… Mmhm. Doubling source of truth. And yeah, after it, I'll build something on top of it. Meanwhile, it led some consequences with the token solar usage." - }, - { - "time": "16:54:58", - "speaker": "Dominik Kapusta", - "text": "Thank you." - }, - { - "time": "16:54:58", - "speaker": "Alex Martemyanov", - "text": "So I got commented from Kane. Uh, asking me to share the actual results I've got from spending. the quarters. the first week of October." - }, - { - "time": "16:55:13", - "speaker": "Dominik Kapusta", - "text": "Wow." - }, - { - "time": "16:55:15", - "speaker": "Alex Martemyanov", - "text": "Yeah, um… I'm gonna share it later. Probably." - }, - { - "time": "16:55:23", - "speaker": "Dominik Kapusta", - "text": "Interesting." - }, - { - "time": "16:55:25", - "speaker": "Alex Martemyanov", - "text": "And…" - }, - { - "time": "16:55:25", - "speaker": "Dominik Kapusta", - "text": "So, what was it? You exhausted the quota, or you have higher quota already?" - }, - { - "time": "16:55:29", - "speaker": "Alex Martemyanov", - "text": "Yeah, basically, I've adjusted the quota, and I've requested a quota raise for Claude, and I got raised the quota." - }, - { - "time": "16:55:35", - "speaker": "Dominik Kapusta", - "text": "Yeah, and then they are asking for what you've done with it." - }, - { - "time": "16:55:39", - "speaker": "Alex Martemyanov", - "text": "Yeah, unboxing what was happening and what was going wrong. So basically, it's just the default Opus that I have set here again. Let's just, especially on the high level." - }, - { - "time": "16:55:51", - "speaker": "Dominik Kapusta", - "text": "Was was it? Was it 5.5?" - }, - { - "time": "16:55:54", - "speaker": "Alex Martemyanov", - "text": "Yep. Yeah, Opus 5.5, the org default, set for high, it's uh…" - }, - { - "time": "16:55:56", - "speaker": "Dominik Kapusta", - "text": "Oh." - }, - { - "time": "16:56:01", - "speaker": "Alex Martemyanov", - "text": "It just burned another 200 of bucks yesterday for the test iteration work, because I…" - }, - { - "time": "16:56:04", - "speaker": "Dominik Kapusta", - "text": "Hmm. Mm-hmm." - }, - { - "time": "16:56:08", - "speaker": "Alex Martemyanov", - "text": "Started it that way and forgot to switch it back." - }, - { - "time": "16:56:11", - "speaker": "Dominik Kapusta", - "text": "Hmmm." - }, - { - "time": "16:56:11", - "speaker": "Alex Martemyanov", - "text": "So and it's really easy to to burn 200 there. So 5 days of work, and you have the 1,000 out." - }, - { - "time": "16:56:12", - "speaker": "Dominik Kapusta", - "text": "Okay. Yeah, sure." - }, - { - "time": "16:56:18", - "speaker": "Alex Martemyanov", - "text": "So nothing special, actually." - }, - { - "time": "16:56:21", - "speaker": "Dominik Kapusta", - "text": "Yeah. Okay." - }, - { - "time": "16:56:21", - "speaker": "Alex Martemyanov", - "text": "Um… So I'll probably try to mention it, that we should set the default model. to another one, because it says Opus by default, because it's set as ORG default. But yeah, otherwise there were some outputs from it." - }, - { - "time": "16:56:36", - "speaker": "Dominik Kapusta", - "text": "Hmm…" - }, - { - "time": "16:56:41", - "speaker": "Alex Martemyanov", - "text": "like the UI test, the CPM web extension. 3 pull requests, and… Countless iteration of a revolution with virtual machines and all this setup. Actually, run with it, and… So it got the job done, but… The burning is still…" - }, - { - "time": "16:57:04", - "speaker": "Dominik Kapusta", - "text": "Interesting, interesting. I just saw, I just checked and it looks like I'm on medium effort because I had the medium effort set for Fable. I was using Fable on medium effort." - }, - { - "time": "16:57:04", - "speaker": "Alex Martemyanov", - "text": "I've looked at my leggings." - }, - { - "time": "16:57:19", - "speaker": "Dominik Kapusta", - "text": "And I switched back to Opus 5.5, and I kept medium effort. I didn't mean to keep medium effort, but I have very, very, very, very low usage this month." - }, - { - "time": "16:57:30", - "speaker": "Alex Martemyanov", - "text": "Actually, Sonnet is using a reasonable amount of token, I say, and high effort, because I usually use high effort for some larger topics, especially." - }, - { - "time": "16:57:37", - "speaker": "Dominik Kapusta", - "text": "Okay." - }, - { - "time": "16:57:45", - "speaker": "Alex Martemyanov", - "text": "when I just run it, okay, evaluate this bug from Asana, run the test, fix it, and then come up with a PR, so I can check the final result and not iterate on every stage. And if I set medium effort, it just loses context, compacts it, and starts doing some…" - }, - { - "time": "16:57:50", - "speaker": "Dominik Kapusta", - "text": "Mm-hmm. Mm-hmm." - }, - { - "time": "16:58:01", - "speaker": "Alex Martemyanov", - "text": "Some bullshit, usually." - }, - { - "time": "16:58:04", - "speaker": "Dominik Kapusta", - "text": "Right." - }, - { - "time": "16:58:06", - "speaker": "Alex Martemyanov", - "text": "But yeah, Sonnet is, uh, Sonnet or Fable is pretty good at it, and I just should not forget to switch it back from Opus." - }, - { - "time": "16:58:15", - "speaker": "Dominik Kapusta", - "text": "Yeah. Uh, alright…" - }, - { - "time": "16:58:22", - "speaker": "Alex Martemyanov", - "text": "So yeah, coming back to the updates." - }, - { - "time": "16:58:22", - "speaker": "Dominik Kapusta", - "text": "Override." - }, - { - "time": "16:58:28", - "speaker": "Alex Martemyanov", - "text": "I'm… I'm working on that." - }, - { - "time": "16:58:31", - "speaker": "Dominik Kapusta", - "text": "Mmhm." - }, - { - "time": "16:58:31", - "speaker": "Alex Martemyanov", - "text": "So I have that that points to. To provide some updates and try to. To catch it if it requires some more attention and post updates. Earlier, for example, I have one pending from Kirby and some pixel not being reported. Mmm… I'll probably just pause it. I have to manage my top priority and answer later this week. This weekend's tomorrow. Okay. Uh, yeah, I'm working on it. And, uh… And, uh, and, and… Anything else on the, uh… On the growth areas." - }, - { - "time": "16:59:23", - "speaker": "Dominik Kapusta", - "text": "Only growth areas… I think we should also keep the other one for… About. Essentially growing others. So that's for team leadership, which means reviewing stuff, which you… have done a nice job for Andre. I'll try to get feedback from him." - }, - { - "time": "16:59:50", - "speaker": "Alex Martemyanov", - "text": "And it was…" - }, - { - "time": "16:59:53", - "speaker": "Dominik Kapusta", - "text": "Umm." - }, - { - "time": "16:59:53", - "speaker": "Alex Martemyanov", - "text": "It was, uh… yeah, I tried… I mean, it was a lot of, uh… a lot of work, actually, spent on the reviews and back and forth and all of that, and…" - }, - { - "time": "17:00:03", - "speaker": "Dominik Kapusta", - "text": "Yeah, and it may be overwhelming, it may be annoying, but I also…" - }, - { - "time": "17:00:04", - "speaker": "Alex Martemyanov", - "text": "that… Goes like an." - }, - { - "time": "17:00:11", - "speaker": "Dominik Kapusta", - "text": "I also heard from Andre that. Does your good reviewer? I'm going to send him a feedback request for that." - }, - { - "time": "17:00:19", - "speaker": "Alex Martemyanov", - "text": "Yeah, training every day on Claude and Codex." - }, - { - "time": "17:00:22", - "speaker": "Dominik Kapusta", - "text": "Yeah, so that was fine. We got feedback. Have you seen feedback from Max?" - }, - { - "time": "17:00:32", - "speaker": "Alex Martemyanov", - "text": "No." - }, - { - "time": "17:00:33", - "speaker": "Dominik Kapusta", - "text": "It arrived yesterday. Uh, let me share… It's here." - }, - { - "time": "17:01:04", - "speaker": "Alex Martemyanov", - "text": "And… Thanks. And…" - }, - { - "time": "17:01:18", - "speaker": "Dominik Kapusta", - "text": "which also…" - }, - { - "time": "17:01:18", - "speaker": "Alex Martemyanov", - "text": "Okay, 100." - }, - { - "time": "17:01:21", - "speaker": "Dominik Kapusta", - "text": "What was that, sorry?" - }, - { - "time": "17:01:21", - "speaker": "Alex Martemyanov", - "text": "Yes, here we are. Oh, for months." - }, - { - "time": "17:01:25", - "speaker": "Dominik Kapusta", - "text": "Yes. Have you read it?" - }, - { - "time": "17:01:28", - "speaker": "Alex Martemyanov", - "text": "Hmm… Okay. Mm-hmm." - }, - { - "time": "17:01:50", - "speaker": "Dominik Kapusta", - "text": "Yeah, so, um…" - }, - { - "time": "17:01:53", - "speaker": "Alex Martemyanov", - "text": "Again, this is the career advisor task." - }, - { - "time": "17:01:54", - "speaker": "Dominik Kapusta", - "text": "This is… This is also… I, sorry, what was that?" - }, - { - "time": "17:01:58", - "speaker": "Alex Martemyanov", - "text": "It's a visibility question." - }, - { - "time": "17:02:00", - "speaker": "Dominik Kapusta", - "text": "I don't understand." - }, - { - "time": "17:02:00", - "speaker": "Alex Martemyanov", - "text": "The career advisor task communication thing that." - }, - { - "time": "17:02:04", - "speaker": "Dominik Kapusta", - "text": "The project advisor task." - }, - { - "time": "17:02:07", - "speaker": "Alex Martemyanov", - "text": "Project advisor cost, right?" - }, - { - "time": "17:02:07", - "speaker": "Dominik Kapusta", - "text": "Yes, yes, yes. Yeah, yeah, so that's that. I don't know what to say, just remember about that, because the previous feedback from Alessandro was really, really good. And I was like, ah, that's amazing." - }, - { - "time": "17:02:27", - "speaker": "Alex Martemyanov", - "text": "Yeah, generally we kept in touch with Alessandro, and probably he was the… Only one, and the, uh, ODRIs were updated during the meeting… during the meetings, the stand-ups." - }, - { - "time": "17:02:38", - "speaker": "Dominik Kapusta", - "text": "Uh-huh, yeah." - }, - { - "time": "17:02:38", - "speaker": "Alex Martemyanov", - "text": "Uh, so there was no… nobody else, uh, involved there. Here in the status, it may look like." - }, - { - "time": "17:02:44", - "speaker": "Dominik Kapusta", - "text": "Mm-hmm." - }, - { - "time": "17:02:47", - "speaker": "Alex Martemyanov", - "text": "Because, uh, the project advisor communications in the summer look pretty much the same, actually, and I just…" - }, - { - "time": "17:02:53", - "speaker": "Dominik Kapusta", - "text": "Mmhm. Mmhm." - }, - { - "time": "17:02:56", - "speaker": "Alex Martemyanov", - "text": "reached out to him directly on Mattermost, most of the times, and posting the project update in the… in the main desk." - }, - { - "time": "17:02:59", - "speaker": "Dominik Kapusta", - "text": "Mm-mm. I see. Yeah, yeah." - }, - { - "time": "17:03:03", - "speaker": "Alex Martemyanov", - "text": "So having no real discussions happening in the project advisor tasks." - }, - { - "time": "17:03:08", - "speaker": "Dominik Kapusta", - "text": "Right, right." - }, - { - "time": "17:03:09", - "speaker": "Alex Martemyanov", - "text": "That probably should come up with some kind of discussions to be put in there." - }, - { - "time": "17:03:11", - "speaker": "Dominik Kapusta", - "text": "Oh. Yeah, probably, you know, don't do anything for the sake of doing it, but just… Documenting and the chats in that async task is a good habit to have. Yeah, um… We're also waiting for feedback from Michal. So we'll see. And I'll send one out to Andre. For now, I think let's keep your… let's keep your growth areas. So, yeah, focus on… I mean, keep communication in mind. And not only into priorities." - }, - { - "time": "17:04:03", - "speaker": "Alex Martemyanov", - "text": "Okay, I'll just post an update today, probably that we discussed today about the project, and we're not getting up with all the PRs today." - }, - { - "time": "17:04:14", - "speaker": "Dominik Kapusta", - "text": "Hmm, hmm. Fine. Uh, yeah, and the other one is leverage your functional skills to ensure that your peers keep a high quality bar. And I'm going to document the progress and the progresses that you've worked with Andra. Have you also commented on… Yeah, you have. You have commented on the ship review. So that's great." - }, - { - "time": "17:04:37", - "speaker": "Alex Martemyanov", - "text": "On the ship review, on tech design." - }, - { - "time": "17:04:39", - "speaker": "Dominik Kapusta", - "text": "Mmhm." - }, - { - "time": "17:04:41", - "speaker": "Alex Martemyanov", - "text": "There was and the. And the VS Code tech design discussion and iterations." - }, - { - "time": "17:04:46", - "speaker": "Dominik Kapusta", - "text": "Yeah, yeah, yeah, yeah, sure, sure. For tech designs here, for tech designs, we're looking for examples when you were the reviewer." - }, - { - "time": "17:04:48", - "speaker": "Alex Martemyanov", - "text": "I guess." - }, - { - "time": "17:04:56", - "speaker": "Dominik Kapusta", - "text": "So. Next time. Uh, and yeah, if there's something, uh, something, uh. that I spot that you could be a reviewer for, I will… I will arrange it. So that you could do it for a tech design. Good." - }, - { - "time": "17:05:18", - "speaker": "Alex Martemyanov", - "text": "Okay…" - }, - { - "time": "17:05:22", - "speaker": "Dominik Kapusta", - "text": "I'm going to update it soon. Not many updates, anyway, in the Grove Areas. The Grove Areas stay. I'm gonna add a new shoutout, and slightly rework the Grove Areas, and that's it. For the… for the… this VS Code work… I think we're done. Your last comment was really good, like acknowledging everything and closing it and opening a new one. The new one, it is a little bit of a surprise, it comes so quick, so fast. That, yeah, people may be wondering… what are you doing in your free time? Which is… I know what you're doing, but it may be strange." - }, - { - "time": "17:06:06", - "speaker": "Alex Martemyanov", - "text": "Yeah, basically it was… In my bed yesterday, just with clothes." - }, - { - "time": "17:06:10", - "speaker": "Dominik Kapusta", - "text": "Mmhm. No." - }, - { - "time": "17:06:12", - "speaker": "Alex Martemyanov", - "text": "Just to iterate over it." - }, - { - "time": "17:06:15", - "speaker": "Dominik Kapusta", - "text": "Mmhm." - }, - { - "time": "17:06:15", - "speaker": "Alex Martemyanov", - "text": "So…" - }, - { - "time": "17:06:19", - "speaker": "Dominik Kapusta", - "text": "Fine." - }, - { - "time": "17:06:21", - "speaker": "Alex Martemyanov", - "text": "Yes, that's in the technical leadership and the…" - }, - { - "time": "17:06:21", - "speaker": "Dominik Kapusta", - "text": "Good. I'll…" - }, - { - "time": "17:06:25", - "speaker": "Alex Martemyanov", - "text": "We integrate the agenda task. Uh, ship review, the comment on tech design…" - }, - { - "time": "17:06:32", - "speaker": "Dominik Kapusta", - "text": "Mmhm." - }, - { - "time": "17:06:35", - "speaker": "Alex Martemyanov", - "text": "And the VS Code tech design moving forward and giving Apple weekly updates about it. And… Bye." - }, - { - "time": "17:06:56", - "speaker": "Dominik Kapusta", - "text": "I will respond to the tech design later today, hopefully today." - }, - { - "time": "17:07:00", - "speaker": "Alex Martemyanov", - "text": "Okay, so I hope it makes sense, I'll just… Ah, that's true." - }, - { - "time": "17:07:06", - "speaker": "Dominik Kapusta", - "text": "There are some comments from Diego already and Federico. If this sounds like…" - }, - { - "time": "17:07:11", - "speaker": "Alex Martemyanov", - "text": "Thank you. I feel like I cannot finish it today." - }, - { - "time": "17:07:16", - "speaker": "Dominik Kapusta", - "text": "If this sounds like something that will need a few extra files in the repository, which is what I think…" - }, - { - "time": "17:07:23", - "speaker": "Alex Martemyanov", - "text": "Yeah, basically, there is one script, or six script files in Scripts, VS Code directory, and a code workspace file that loads it." - }, - { - "time": "17:07:30", - "speaker": "Dominik Kapusta", - "text": "Mm-hmm." - }, - { - "time": "17:07:36", - "speaker": "Alex Martemyanov", - "text": "Other, uh, other stuff it does by itself." - }, - { - "time": "17:07:38", - "speaker": "Dominik Kapusta", - "text": "Oh, okay." - }, - { - "time": "17:07:40", - "speaker": "Alex Martemyanov", - "text": "So it basically loads, generates the build server, generates the tasks and launch JSON." - }, - { - "time": "17:07:44", - "speaker": "Dominik Kapusta", - "text": "Mm-hmm." - }, - { - "time": "17:07:46", - "speaker": "Alex Martemyanov", - "text": "Uh, to keep it not in the repository, and everything happens in the script." - }, - { - "time": "17:07:49", - "speaker": "Dominik Kapusta", - "text": "Mmhm." - }, - { - "time": "17:07:54", - "speaker": "Alex Martemyanov", - "text": "And removed by removing those three files if needed." - }, - { - "time": "17:07:54", - "speaker": "Dominik Kapusta", - "text": "So overall, yeah, overall the ask of this tech design is… Just adding these files really, because nothing changes. Mm-Hmm." - }, - { - "time": "17:08:03", - "speaker": "Alex Martemyanov", - "text": "Yeah." - }, - { - "time": "17:08:05", - "speaker": "Dominik Kapusta", - "text": "with the rest. That sounds good. Yeah. Okay, okay, okay, um… Good. Great. Thanks for that, um… yeah, I think we're… I think we're good, I think we're… Clear. If we're not, we'll iterate next month, next Tuesday. Uh, good." - }, - { - "time": "17:08:26", - "speaker": "Alex Martemyanov", - "text": "Yeah, on that one, the PR is basically ready, and uh… Confirmed working with some. Extensive tests. And I think… Even the VS Code remote debugging should be up soon as well. But the bottleneck is my review. attention that I have. Still have to complete the top priority and just… Iterate over all the stuff happening, including the communications." - }, - { - "time": "17:08:59", - "speaker": "Dominik Kapusta", - "text": "Sure." - }, - { - "time": "17:09:02", - "speaker": "Alex Martemyanov", - "text": "Quickly." - }, - { - "time": "17:09:02", - "speaker": "Dominik Kapusta", - "text": "Right, yeah. If you have a pull request sort of ready, or a draft pull request up, you can just link it there." - }, - { - "time": "17:09:07", - "speaker": "Alex Martemyanov", - "text": "Yeah, I have one… I have one here in search. And that window, this window, it's the crash. I hope it makes sense. Should be pretty clear, but, uh, just touch as many places in the code, and use a swift linter to prevent the…" - }, - { - "time": "17:09:27", - "speaker": "Dominik Kapusta", - "text": "Whoa." - }, - { - "time": "17:09:35", - "speaker": "Alex Martemyanov", - "text": "failures… possible failures in the future. And has, uh, Swiss law for…" - }, - { - "time": "17:09:39", - "speaker": "Dominik Kapusta", - "text": "Okay." - }, - { - "time": "17:09:41", - "speaker": "Alex Martemyanov", - "text": "to wrap the errors that we got, that we may extract from other places." - }, - { - "time": "17:09:46", - "speaker": "Dominik Kapusta", - "text": "Mm-hmm, mm-hmm, m." - }, - { - "time": "17:09:47", - "speaker": "Alex Martemyanov", - "text": "Um… yeah, it has tests, and… validation steps to to prove the clauses happening on on Rosetta. 86 architectures and to prove it does not. Let me just get this fixed." - }, - { - "time": "17:10:03", - "speaker": "Dominik Kapusta", - "text": "Nice. Okay, fine." - }, - { - "time": "17:10:07", - "speaker": "Alex Martemyanov", - "text": "And after that, I could switch to… Give it to priority telemetry, and I'll give an update in the project advisor's task at the time. Not getting everything ready by today, and uh…" - }, - { - "time": "17:10:20", - "speaker": "Dominik Kapusta", - "text": "Uh-huh." - }, - { - "time": "17:10:21", - "speaker": "Alex Martemyanov", - "text": "Because… Because of this work and. The crash and the. And the amount of tasks to be filled, including the plans and attribution data analysis." - }, - { - "time": "17:10:38", - "speaker": "Dominik Kapusta", - "text": "Good, sounds good. Alright." - }, - { - "time": "17:10:38", - "speaker": "Alex Martemyanov", - "text": "Smooth." - }, - { - "time": "17:10:42", - "speaker": "Dominik Kapusta", - "text": "Fine. Thank you very much. Have." - }, - { - "time": "17:10:45", - "speaker": "Alex Martemyanov", - "text": "Yep. Thank you, Drew, for…" - }, - { - "time": "17:10:47", - "speaker": "Dominik Kapusta", - "text": "Have a great rest of the day. See ya. Bye bye." - }, - { - "time": "17:10:49", - "speaker": "Alex Martemyanov", - "text": "I'm sounding this loud and everything. Yep, I'll…" - }, - { - "time": "17:10:53", - "speaker": "Dominik Kapusta", - "text": "No, don't worry. That's great." - }, - { - "time": "17:10:54", - "speaker": "Alex Martemyanov", - "text": "I'll get back to you on the…" } ] } diff --git a/work/zoom-transcripts/2026-10-15 Dominik Kapusta's Personal Meeting Room 2026-10-15 16 05(GMT+6 00) nzWOuhyzSdCjNqMRh6X13w/transcript.md b/work/zoom-transcripts/2026-10-15 Dominik Kapusta's Personal Meeting Room 2026-10-15 16 05(GMT+6 00) nzWOuhyzSdCjNqMRh6X13w/transcript.md index 056c6c62..79560ccd 100644 --- a/work/zoom-transcripts/2026-10-15 Dominik Kapusta's Personal Meeting Room 2026-10-15 16 05(GMT+6 00) nzWOuhyzSdCjNqMRh6X13w/transcript.md +++ b/work/zoom-transcripts/2026-10-15 Dominik Kapusta's Personal Meeting Room 2026-10-15 16 05(GMT+6 00) nzWOuhyzSdCjNqMRh6X13w/transcript.md @@ -15,332 +15,3 @@ source: "https://us01mynotes.zoom.us/nzWOuhyzSdCjNqMRh6X13w" - **16:05:14 · Dominik Kapusta:** Ай Горю? - **16:05:15 · Alex Martemyanov:** Oh. Still commuting, yeah. Much better, I think. And yeah, reaching you. - **16:05:25 · Dominik Kapusta:** Отгод. Гуд. Туф. Ера. -- **16:05:27 · Alex Martemyanov:** Eventful week. Let's see. A lot of things happening in parallel. And yeah, for today, I kinda… Already tired. Probably still not 100% recovered. But, yeah, anyways, I tried to update our agenda. -- **16:05:45 · Alex Martemyanov:** Бад. Я. Энивэйс? -- **16:05:46 · Dominik Kapusta:** Я? -- **16:05:53 · Alex Martemyanov:** And, uh… Yeah, so basically… From the last update, from the last Friday's update on my top priority, there is… Not much of actual update happened since I spent most of the Monday. And… with the… It abuse the incident thing. The other stuff, and just get to the… -- **16:06:21 · Dominik Kapusta:** Ням? -- **16:06:24 · Alex Martemyanov:** Do the actual priority thing, and uh… Today, I'm… trying to get through it, and first of all, it's blocked with this, uh, domain name called Crash. The time kinda keep iterating. Miss Claude. -- **16:06:40 · Dominik Kapusta:** Вот краш вот. Краш. Свои? -- **16:06:42 · Alex Martemyanov:** The domain and the domain and code, the WebKit proxy error thing. -- **16:06:46 · Dominik Kapusta:** А. Аа, Окей? -- **16:06:49 · Alex Martemyanov:** Yeah, I'm just, uh… I'm just about to open it, and just final validation of the bills passing. I'm just basically ready, and I'll ping you if you can. Uh, it goes to a normal… normal release, since it's not… Not high occurrences are normally on the 86 machines, but anyways, it's naturally preceding the telemetry fix and all the other stuff. Yeah, and on the top priority, I got several stages. I think there is, um… Three, four. Even… Yeah, at least three VRs. Stacked PRs pending. So first of all, we need adjusting the attribution because currently it misses some identified points. And, uh, we need some proofs of it, actually. of the events actually happening. So basically, I've identified it to… The background issue is lock screen or unloading browser and the network process crash that may also. I don't know. We affected the CPM error and basically those like 80% of the telemetry. -- **16:08:18 · Dominik Kapusta:** Окей? -- **16:08:25 · Alex Martemyanov:** It got reproduced in the. Best homeless setup. That was made for evaluating the theories. So, if it goes well, we should… We should probably cover like 80% of those and hopefully receive some extra data to cover the rest. Um, so… That's moving, although I'm kind of feeling a little… Bring the trade. and all of this. Uh, but yeah, I was hoping to open everything today so we could review it tomorrow, but realistically… It's probably gonna be only the attribution fix, so request for today and the crash fix. And for tomorrow, yeah. I'll try to… Uh, to discuss it with Michal, if we can… We can get it through. -- **16:09:30 · Dominik Kapusta:** All right. Uh, okay. -- **16:09:32 · Alex Martemyanov:** So, yeah, later today, I'll give an update on the project, uh, when I… when I have the request open. -- **16:09:35 · Dominik Kapusta:** Mm-hmm. Yeah, sure. -- **16:09:40 · Alex Martemyanov:** So, it may be… -- **16:09:43 · Dominik Kapusta:** Yeah, uh, I'm looking at these fixed CPM breakage issues. Breakage. WebKit issues, I guess. Uh, and there are four subtasks, which… -- **16:09:51 · Alex Martemyanov:** Yep. -- **16:09:56 · Dominik Kapusta:** So there will be four pull requests? -- **16:09:57 · Alex Martemyanov:** All of them have contacts. -- **16:10:00 · Dominik Kapusta:** Double. -- **16:10:00 · Alex Martemyanov:** Yes, I guess so. -- **16:10:01 · Dominik Kapusta:** Mmhm. Okay. -- **16:10:03 · Alex Martemyanov:** I'm planning to… to give it some… details in the research and in the tasks themselves. on, uh… kind of describing the approaches, but yeah, it comes a bit later. So, yeah, it's to be updated. They'll post in a project a bit later today. -- **16:10:27 · Dominik Kapusta:** Sounds good. -- **16:10:28 · Alex Martemyanov:** So, yeah, last week. Last week after. All of that kind of got some toxication. Uh, which… Luckily gave me like a couple of days. To just get relaxed a little bit. Yeah, but meanwhile, yesterday, I got some… Oh, I… Got some time… like lazy white coding on the extra project projects. And I got some results you may have seen. So, basically, there is the tech design for the VS Code integration updated. Yeah, basically, I've posted the update. Thanks for all the input. -- **16:11:14 · Dominik Kapusta:** Mm-hmm. -- **16:11:18 · Alex Martemyanov:** And, uh, having all of that, I actually found a way that will work and, uh, that doesn't touch the current. -- **16:11:19 · Dominik Kapusta:** Yeah. -- **16:11:28 · Alex Martemyanov:** I mean, current project structure, it's, uh… It's a little… it's a small wrapper over the Xcode language. -- **16:11:38 · Dominik Kapusta:** Ahem. -- **16:11:38 · Alex Martemyanov:** The server, which uses the same architecture. Uh, as Xcode does for… -- **16:11:45 · Dominik Kapusta:** Mmhm. -- **16:11:46 · Alex Martemyanov:** sources indexing, and it used the same Swift build system. that Xcode27 is using under the hood now, so we should be pretty much aligned on this. Even though the repo or the project itself is pretty young, I think we could easily fork it since it's released. -- **16:11:57 · Dominik Kapusta:** Mmhm. -- **16:12:07 · Alex Martemyanov:** Really small rubber, and uh… And keep… -- **16:12:14 · Dominik Kapusta:** Okay. -- **16:12:16 · Alex Martemyanov:** And coupons, that's… for me. -- **16:12:20 · Dominik Kapusta:** Um… -- **16:12:20 · Alex Martemyanov:** Because of, kind of, security and privacy concerns, and uh… -- **16:12:24 · Dominik Kapusta:** Fine, yeah, yeah, I think it would require… Something like a vendor triage… dependency… Triage, or tool triage, whatever it's called, but it's essentially, like, a tool that we want to use, and… And because of that, we might want to perform some checks on it. -- **16:12:50 · Alex Martemyanov:** Yeah, there is a related question in the tech design, so basically I've assigned it to you if you can. And you may leave the comments on it. -- **16:12:58 · Dominik Kapusta:** Mmhm. -- **16:13:03 · Alex Martemyanov:** Yeah, so basically that should work, and… Keeping things moving and finally resolve the project. Maybe maybe a good thing to the. Career review thing. Like, moving the team forward and finishing the effort. And with the following… With the following tests update. I actually got it locally, so basically it's a buildable folder and unlinking the AppDelegate dependency. it just waits for, uh, for the tech design to be approved. Yeah, basically, it only depends on the main… main branch, it's not related to VS Code. But it works, iOS works with simulator. -- **16:13:52 · Dominik Kapusta:** Mmhm. -- **16:13:53 · Alex Martemyanov:** macOS network, everything just works. Oh… -- **16:13:57 · Dominik Kapusta:** That's good, that's good. -- **16:14:00 · Alex Martemyanov:** And yeah, there is only one issue about export build, and it's a package resolution thing that I was trying to get rid of, but maybe I'll get through it with some local fork. Just for myself or for anybody who's interested, if… if it would be the use case. Basically, I expect a couple of… team members to adopt it, or at least take a look, maybe it works for somebody. Especially having the next things, which are in my, uh… Stick in the artwork. So basically, I. Uh, pretty much completed the, uh, virtual machine manager thing that I mentioned, kind of, half a year ago. Started work on it, so it's migrated to… Another build system… It supports remote machines like old MacBook that just works. You can see it. Sorry. It just works directly from MCP, and even if I can crash machines, but I won't advertise on the team, but anyways, I have one. And be used for virtual machines testing as well. Uh, it just works. So, um, Claude and ChatGPT, when I ask to… -- **16:15:20 · Dominik Kapusta:** Okay. -- **16:15:25 · Alex Martemyanov:** validate the tests on macOS 27 or macOS 12, it just says, okay, I will set up the virtual machine, I'm getting the lease, I've run the tests, the bug is reproduced, it's fixed. Uh… So that's another part of the… AR work and developers help, and there is integration for VS Code as well, so you could just run the virtual machine and run the build. from VS Code, and there is no hanging at launch, it just works natively, and you can run UI tests in it, not blocking your main working machine. So, basically, the project is moving really, really well. -- **16:16:06 · Dominik Kapusta:** Mm, mm-hmm. -- **16:16:07 · Alex Martemyanov:** And I expected to have some to make some contribution to the team when I when I finish. Approving this. -- **16:16:18 · Dominik Kapusta:** Yeah, that's good. I mean, it's a lot. It is a lot. So allow me to digest it. -- **16:16:20 · Alex Martemyanov:** Great, thank you. -- **16:16:26 · Dominik Kapusta:** Piece by piece. But, uh… Um… Can maybe talk about the tech design later. VS Code and Xcode preferably server. Fine. The other thing you've just mentioned, it's what's on that diagram. -- **16:16:55 · Alex Martemyanov:** Uh, the diagram, yeah, that's just another quick, uh, quick call of yesterday's date. -- **16:16:56 · Dominik Kapusta:** In the agenda? -- **16:17:02 · Alex Martemyanov:** From my bed. Oh… It's, uh, basically… Agent setup analysis for automatic bug and crash fix workflow. I just… had its one short run, and asked to summarize everything we've had for a century, and what Android and Windows teams have. Uh, so this is kind of first one-shot diagram that it came with, analyzing the signals. So we have, uh… manual trigger from Asana, like tagging or mentioning a bot. Uh, we have a new crash events, or we have a CI failure, uh, that, uh, first runs. a cloud agent or Linux with Sentry and Asana access, analyzes the code, the task, and. everything, and then runs an isolated runner on Bitrise. that reproduces UI tests or unit tests, collects the evidence, tries to fix, iterates, and proceeds opening pull requests with a fix or no hope. With automated MetaMoose and Basana comment. Not sent by a bot because of the incident one, and, but, posted by by the automation. -- **16:18:30 · Dominik Kapusta:** Hmm, yeah. -- **16:18:35 · Alex Martemyanov:** And then the last step, yeah, the bottleneck of the human review, the approval. Which, if in case of the test runs, the test runs… By the way, I just got another test run that just passed, and I'm probably gonna use the Fernando proposal to just merge it. Um, there's one self-review. -- **16:18:55 · Dominik Kapusta:** Amanda proposal. -- **16:18:58 · Alex Martemyanov:** Uh, they self-review for test fixes. -- **16:19:02 · Dominik Kapusta:** Ah, yeah, yeah, sure. -- **16:19:04 · Alex Martemyanov:** Yeah, so yeah, it's basically an automated run. fixing the… my local automators around fixing the Discover, DUI tests issues. Uh… So… It should run the same thing, but online using agent runners. And, uh… So yeah, basically we have a first. First AI iteration of it, so I could… Choose from what to move next when I have some time. -- **16:19:40 · Dominik Kapusta:** All right. What you're doing is… It's great in terms that… It's… These are great ideas for the team, for sure. Uh, the thing is, it is being worked on already in a few places, and it would be great to coordinate that work, or maybe join that work. Uh, we are currently… figuring out… Bitrise… well, not Bitrise, but, uh, essentially infrastructure for… Running Agentic workflows on… for Apple team. And… I said Bitrise because I'm involved in a Bitrise task, which is about Bitrise remote development environments, which is their new feature that they… where they just… -- **16:20:32 · Alex Martemyanov:** Okay. -- **16:20:41 · Dominik Kapusta:** just provide macOS virtual machines that you can use for that. They come with Xcode and Claude pre-installed, and… Yeah. Okay. What I was doing is I was trying to get the build to pass on these machines, like, set everything up… as close to our CI setup as possible. And I think it worked in the end, I need to… Uh, leave for a moment today, but… Yeah, I think it works. -- **16:21:17 · Alex Martemyanov:** Yeah, you mean the… the runner automation thing? Yeah, again, I, uh, haven't spent… -- **16:21:20 · Dominik Kapusta:** Yeah, we… -- **16:21:24 · Alex Martemyanov:** Actually, a minute on it. And just… it's just a one-shot research. -- **16:21:30 · Dominik Kapusta:** Just the discussion topic. Okay, okay, fine. Yeah. -- **16:21:33 · Alex Martemyanov:** Yeah, so basically a discussion topic to probably involve me into these flows and, yeah, start the coordination. -- **16:21:37 · Dominik Kapusta:** Mm-hmm, sure, sure, so I can tell you, I can tell you where we are, I can tell you where we are. We are considering… Actually, one thing that is happening is… Um, enabling… Simple Agentic workflows, like one shot. essentially workflows on GitHub Actions. And, uh, so the idea is you have a workflow where you… Or the prompt? is the input. And the. A workflow just runs, and whatever… whatever the output needs to be, it is. Is it, like, a pull request, or some artifact, whatever. But essentially, like, think of, I don't know, fix this crash, and then it ends up with a pull request. Yeah, um… There is a small problem. We aren't allowed to use… Anthropic. API keys in public repositories. So. To work around that, we are setting up a private repository that will be empty. And just have that token? And the workflows. And the workflow would clone the monorepo. -- **16:23:04 · Alex Martemyanov:** Mmhm. -- **16:23:04 · Dominik Kapusta:** But it would run in a private repository otherwise. But it would clone the monorepo, and work on the monorepo, and open the pull request in the monorepo. Uh, so the only… the only complication here is that it can't be the monorepo, can't live in the monorepo, but it lives in a private repository that essentially has write access to the monorepo, and that's it. So this is for a single… Like, single-shot, uh… tasks? Where you just… Essentially, you give a task to the agent, and… you don't want to talk to it in the meantime, you don't need to talk to it in the meantime, and then it comes with the result. For longer. Workflows, where you would like to… Intervene. In the meantime, or would you expect to be pinged by the agent? Uh, we can't do it in GitHub Actions, because you can't… stop the… stop the GitHub action workflow, or… essentially take over the control of it. So for that, we just need a remote machine. With… with a cloud session. And you could like SSH into that machine for instance or VNC into it and… And take over if needed. And that is being figured out. One possibility is AWS. The problem with AWS is it's $1400 per month per machine. So, we're also evaluating Bitrise on that, and Bitrise would be definitely cheaper, and it comes with… Well, the VM images are prepared for Apple development. They have Xcode, they have plenty of other tools. installed Ruby and so on and so on. So that's what we're… dealing with now, going through security triages and so on and so on. Um, oh. -- **16:25:17 · Alex Martemyanov:** What's the problem with the… With it. Why do we have to SSH to another machine? -- **16:25:28 · Dominik Kapusta:** Well, we don't have to, but… If we want to… we wouldn't be able to in a GitHub Action workflow. I'm. -- **16:25:40 · Alex Martemyanov:** Okay. -- **16:25:41 · Dominik Kapusta:** And, yeah, well, whatever, you don't need to SSH into it, but you might want to… Connect to a cloud session on such machine. to see… what's going on there, and I don't know, to… to provide further instructions to the agent, and so on and so on. Uh, I also… to be completely fair, I don't… fully follow that use case yet. I'm… I clearly understand the need for, uh, simple workflows, like, please fix this, please do this, and so on and so on. Make no mistakes. But these interactive sessions, they are a bit… A bit strange to me, but… Yeah, people that have more experience than me suggested that we would need this. Uh, I guess it may… it may be about, um… Just doing work on a remote machine, rather than a local machine. Just like this, right? So you can do it locally, but you can also do it remotely. I'm not entirely sure how much it would, uh… we would benefit from it. Umm. Let's see. -- **16:27:04 · Alex Martemyanov:** Yeah, like having a… remote testing machine with BNC, and uh… Agent runs, and even remote building from… from the VS Code. Uh, it may be a good option, since not everybody has, like, as new of machine as I… of machines as I do. And ability to run those. So probably we could. -- **16:27:25 · Dominik Kapusta:** Mm-hmm. -- **16:27:29 · Alex Martemyanov:** Integrate. And that point as well, somehow. So just maybe ping me in the related tasks and. -- **16:27:34 · Dominik Kapusta:** Yeah, yeah. -- **16:27:38 · Alex Martemyanov:** I'll see where can we… Integrate. and distribute the work. Okay. -- **16:27:55 · Dominik Kapusta:** Yeah, I can try to involve you here and there or just give you links. Because, because, because, because one of them is this one. This is one of them. That's for the simple workflows and the other one is… this. And this Bitrise thingy is a subtask of. of a full project called "Find an alternative to Cursor Cloud Agents to safely run autonomous workflows". -- **16:28:48 · Alex Martemyanov:** Mm-hmm. -- **16:28:53 · Dominik Kapusta:** One other limitation of GitHub Actions is that. Any workflow can only run for 6 hours, so in case we have some long, long jobs… It would just stop after six hours. and be deleted and forgotten. -- **16:29:12 · Alex Martemyanov:** Yeah, generally, the ramps should not… List for cigarette rollers. -- **16:29:17 · Dominik Kapusta:** Yeah, they shouldn't. I agree. Oh, all right. -- **16:29:29 · Alex Martemyanov:** Yeah. -- **16:29:31 · Dominik Kapusta:** All right, so that's this. For the tech design. I will have a look later. I saw there are some comments already, and overall the reception is… is better. Probably because… It's opt-in, and it doesn't change anything that we have. Um… Yeah, some of the requirements of your previous design were… hard to… Hard to just, you know… agree on without, without, uh… -- **16:30:06 · Alex Martemyanov:** Accept. -- **16:30:10 · Dominik Kapusta:** No. Like… It was just, essentially it was just refactoring, refactoring a lot of code in order to maybe have some benefits, but also there were, like, a significant part of these benefits would be achievable without all these changes, so… I'm glad that we're gonna be switching to buildable folders, which will simplify the project file drastically. And then there's this other thing. that I have forgotten in the meantime. Oh, yeah, uh, removing the host application from tests. -- **16:30:48 · Alex Martemyanov:** Uh, I think it's not removing, but uh… Because since we run it in Xcode and not as a package, we cannot remove the host application. -- **16:31:01 · Dominik Kapusta:** But you don't launch it in UI tests, in unit tests. -- **16:31:04 · Alex Martemyanov:** Relaunch it. -- **16:31:06 · Dominik Kapusta:** But if you set it to none, do you still launch it? -- **16:31:06 · Alex Martemyanov:** But, uh… You cannot launch it if you don't have it. Because it's run against the host application from Xcode. And if you want to run to remove the host application, you have to convert it to the library as it was in the initial design. -- **16:31:26 · Dominik Kapusta:** So what happens? If I go here… and here and do this. What does this really change? -- **16:31:38 · Alex Martemyanov:** Mmhm. I suppose it won't. Build the tests. -- **16:31:51 · Dominik Kapusta:** It works. It's what I wrote in the comment on your initial tech design. I set it to none, and it works. The only tests that are failing were the CBR… -- **16:31:52 · Alex Martemyanov:** Or maybe, uh… Excuse me. -- **16:32:03 · Dominik Kapusta:** Tests. No. -- **16:32:09 · Alex Martemyanov:** Okay, good. I'll reiterate about it. -- **16:32:12 · Dominik Kapusta:** Okay. -- **16:32:12 · Alex Martemyanov:** Anyways, uh… anyways, it's ready without… even without it. And, uh… The fix there was just to… To inject the… An empty app delegate. -- **16:32:26 · Dominik Kapusta:** Yeah, yeah, that was… that was the thing that came to my mind initially. We can… we can have another app that I get, and then… -- **16:32:26 · Alex Martemyanov:** Instead of the apps that I'm gonna get. -- **16:32:36 · Dominik Kapusta:** I think it's a build setting, the app delegate is also a build setting somewhere, or the… yeah. -- **16:32:39 · Alex Martemyanov:** Yeah, so anyways, I'm getting to it, and it's independent from VS Code or anything else, and when I… -- **16:32:44 · Dominik Kapusta:** Yeah, yeah. Mm-hmm. -- **16:32:47 · Alex Martemyanov:** Wipe, wipe out the current priority work. -- **16:32:53 · Dominik Kapusta:** Mm-hmm. -- **16:32:53 · Alex Martemyanov:** On my table, and uh… I'll come back to it and. And, uh… and modularization items as well. -- **16:33:05 · Dominik Kapusta:** Mmhm. -- **16:33:05 · Alex Martemyanov:** So, maybe when, uh… when we have the browser modularized, like, finalized, we could reiterate over the SPM package, as it would be a logical next step, or maybe we didn't change. Uh, with the next, next code release. Uh, like, Apple providing several… -- **16:33:23 · Dominik Kapusta:** Hmm. -- **16:33:25 · Alex Martemyanov:** Steps further. -- **16:33:26 · Dominik Kapusta:** Mm-hmm. -- **16:33:27 · Alex Martemyanov:** to the SPM compilation, as it seems. Uh, so… yeah, we'll get there. -- **16:33:35 · Dominik Kapusta:** Okay. Okay, nice. One other thing that we need to do today. which is slightly overdue, is the… Continuous development check-in. Which means we should talk about growth areas and shoutouts as well, actually, of course. They are here. Yeah, it's a private task, but you have access. um… So we… We talked about… uh, the communication overall. And… um… For this… Like then, what was the next steps was that you're moving again from ON to OE into a new… Environment, new people… And there was just this reminder to use your project advisor, to bring questions, to… to provide updates in the project and so on and so on. And… What do you think about… About this growth area, about the other growth area perhaps as well, because we can keep it, we can… Call it done. We can create a new one. My. Personal feeling is that. It still needs some work. But curious about your perspective. -- **16:35:40 · Alex Martemyanov:** So, I don't know… Very good question. So generally, we… It's the last… iteration. We've had several projects, like. And… The most complicated one is probably the current one, and uh… -- **16:35:58 · Dominik Kapusta:** Mmhm. -- **16:36:01 · Alex Martemyanov:** So general directions there were initial communications over the project structure. I will proceed and. -- **16:36:11 · Dominik Kapusta:** Mmhm. -- **16:36:12 · Alex Martemyanov:** Several need more time suggesting the roadmap. Oh. Otherwise, there were just regular project updates on the current state and expectations with some corrections as required. And… So about bringing question and doubts. I'm not sure here, because I think there were a couple of. question and doubts that I brought to the project advisor on what. What's better to do, or how to iterate over it, or should we apply this, or have a bigger iteration on the better solution? -- **16:36:49 · Dominik Kapusta:** Mm-hmm. Mmhm. -- **16:36:56 · Alex Martemyanov:** Or, uh… Aligning on the… on the roadmap, I mean, on schedule, like on reviews and… our release dates. So… Generally, from my perspective, I… Try to keep it. Up to date and keep people updated when it's… when something happens, or like, nothing happens if I… -- **16:37:25 · Dominik Kapusta:** Yeah, okay. -- **16:37:28 · Alex Martemyanov:** Um, if there is… if there is a slowdown, for example, for some reason. -- **16:37:29 · Dominik Kapusta:** Right. Yeah, yeah, and that's good. If you… So when you reach out to the project advisor, do you do it on Inasana or Mattermost? -- **16:37:48 · Alex Martemyanov:** Mmm… -- **16:37:48 · Dominik Kapusta:** Is it in the comms task or some other tasks? -- **16:37:53 · Alex Martemyanov:** I think it's mostly in MetaMOST, but sometimes there is some… So basically, project update iteration, if there was some… -- **16:37:56 · Dominik Kapusta:** Mmhm. Mmhm. -- **16:38:02 · Alex Martemyanov:** If there was some decision. -- **16:38:04 · Dominik Kapusta:** Mm-hmm. Good. What I can… suggest, maybe, is… because, like, at least looking at, uh, at this task… -- **16:38:18 · Alex Martemyanov:** Yeah, there is not much of the communication happening on the top. -- **16:38:18 · Dominik Kapusta:** for… You know, there is not much communication, but there are also two instances of, uh… career advisor asking… I mean, sorry, project advisor asking you for… for the status? -- **16:38:34 · Alex Martemyanov:** Uh, and actually, I was just writing the project update, and in the moment, he was asking. -- **16:38:34 · Dominik Kapusta:** And. -- **16:38:40 · Alex Martemyanov:** Uh, about the status… -- **16:38:41 · Dominik Kapusta:** Mmhm. -- **16:38:43 · Alex Martemyanov:** And… -- **16:38:43 · Dominik Kapusta:** And. -- **16:38:46 · Alex Martemyanov:** And yeah, you mean making the communication more visible and go through the communication tasks? -- **16:38:50 · Dominik Kapusta:** Making the… if the communication happens, making it visible would be great. what I noticed, uh… Diego did on a couple of occasions. We were on a Zoom call, and he would put a summary of a Zoom call in the communication task. Just, you know, just some bullet points, just to… -- **16:39:14 · Alex Martemyanov:** Mm-hmm. -- **16:39:17 · Dominik Kapusta:** to make it clear that the communication happens. And it's also valuable… of course, it's valuable to everyone who reads the task, but it's also valuable to yourself and to the project advisor, because project advisor. I mean, more to the project advisor, of course, because you… this is your top priority, but this is not project advisor's top priority, and they may have more work, and they may be forgetting things, so it's great to… To just… Note down. Oh. whatever is happening, right? If you… even if you chat on Mattermost, and you have, like, a… some exchange of messages in Matrimos that is valuable, and where you learn something. It's a great… Um, great, uh, habit to… to just, you know… put it in Asana as well. Just as a documentation that things are happening. When it comes to project updates. It's… It's probably… I wanted to say that, well, I can see you're posting frequent updates when needed. There's an update from 7th of October and then the update from 9th of October. Because some people get fixed on that. rows weekly… I mean, write weekly updates, and then they put one update a week, and they're fine with that. But it's not… always enough to just write one update a week. So that's good. But… What I would like to see… And this CPM project is not looking… I mean, it's looking fine, right? People seem to be… okay with your communication there, but then there is… like, the communication does not end on your project, your top priorities. We had an example with this VS Code initiative where… Well, some comments started popping up on your project task. And you remember, like, I was pinging you to put a comment there, uh, like. Calm them down, because the situation was that some people wrote some comments and… The last one was from Juan. The last one was from Juan, and um… And he just… asked you explicitly, could you talk more about the benefits of the project structure, cleanup, and coding standards we'll get from these changes? And… I know that. you… your idea was to write a tech design, and that's also what we agreed on on Apple Weekly. Another weekly meeting, I think it went well overall, where you calmed people down, essentially. But not everyone was on the call. And then if you come back to that project, you see that project in Asana, and you still see Juan's comment there, which is unanswered. It would be great to respond to it. Could you talk more about the benefits of the project structure cleanup? I mean, yes… I'm about to write everything down in a tech design. So we'll see, and… yeah, I saw your comment, I read your comment, and I will address it. Sometimes this is… Fine. Um, there were actually some… some agreements on the Apple Weekly Call that you could put in writing over there, like, yeah, you'll write the tech design, and then we'll talk about it, and it's not… what was very important to me, I think, at least, was that… it's not strictly about VS Code integration, but also it's… It's a way of speeding up builds, cleaning up project structure, and so on and so on. So… This could have been put there in a comment. Otherwise, people were… a bit lost in all of this, and they were… Actually, I have to say they were afraid. -- **16:44:17 · Dominik Kapusta:** about what's happening, because it's a lot of changes, and… Of course, we don't like changes, no one likes big changes, especially if they are not clearly backed by some proper reasoning. Um, so… So that was that. And then when I… then when I… kept pinging you for a couple of days, you told me, oh, I'm writing a tech design, I'll update later, I'll say, fine. And then you only wrote the comment that the tech design is ready, so please go read a tech design. Go and retake design. Which, yeah, it was a bit… a bit late as well, but uh… What I… what I suggested you on our Mattermost chat, it's essentially, you know, just put, like, two, three sentences there to calm people down, and you should be fine. Mmm. No. So… So that's something that… That would be great to see going forward. I think. Because… Let me… put it this way. It's clearer than when projects are going… The right way, or… Or not, but as long as it's… On the technical side, good or bad, whatever, you're handling it perfectly. You're just, okay, this is my project, this is the plan, these are the tasks I'm working on, when I'm done with this, I'm gonna do this, and so on and so on. And you're giving proper updates, you're keeping everyone… Well informed. And then… when sometimes something happens, and also, you're fine, like, calling me mid-mortems to decide on technical stuff, and so on, and so on. But if there is this… This, how to say, um, well, someone raising something, uh, having doubts. Then it gets tricky. Essentially it gets tricky and you may be. A bit lost, I don't know. I'm just still trying to… -- **16:47:08 · Alex Martemyanov:** Yeah, I just tried to go through the actual comment to reason about it and to. -- **16:47:15 · Dominik Kapusta:** Yeah. -- **16:47:16 · Alex Martemyanov:** Basically, to iterate over it so it gets to my… Incoming queue, and uh… -- **16:47:21 · Dominik Kapusta:** Mm-hmm. -- **16:47:23 · Alex Martemyanov:** When I reach to it, I, yeah, answer, basically. -- **16:47:26 · Dominik Kapusta:** Mm-hmm, mm-hmm, mm. -- **16:47:30 · Alex Martemyanov:** And some comments do require some extra checks. -- **16:47:34 · Dominik Kapusta:** Mmhm. -- **16:47:35 · Alex Martemyanov:** Uh, switching contexts and, uh, especially having those run as a parallel project. -- **16:47:37 · Dominik Kapusta:** No. -- **16:47:42 · Alex Martemyanov:** or background projects to the priority. And it may be, yeah, it may require some extra efforts. To marry those. -- **16:47:54 · Dominik Kapusta:** You know. -- **16:47:56 · Alex Martemyanov:** There's really the incoming, um… Incoming backlog. -- **16:48:05 · Dominik Kapusta:** I'm thinking how to… What to do? to also avoid… Being pinged. for updating your project status. I understand that there was a coincidence, like, Michal commented, okay, so how is it going, what are the next steps, and you were just writing an update. But. Yeah, maybe… -- **16:48:37 · Alex Martemyanov:** Yeah, so basically there is a milestone at the end of the week and my evening of Fridays and there is some events like mid-mortems or some plan changes or some re-evaluations. -- **16:48:41 · Dominik Kapusta:** Mmhm. Mmhm. -- **16:48:52 · Alex Martemyanov:** That I'll post midweek. And, uh… -- **16:48:54 · Dominik Kapusta:** Hmm. -- **16:48:55 · Alex Martemyanov:** Generally, otherwise, when, uh… it feels natural for me to post an update, like, when I finish my work on Friday, just to hand over to the, uh… -- **16:49:02 · Dominik Kapusta:** No. -- **16:49:06 · Alex Martemyanov:** Uh, to the ones from the US side that are usually running the objectives, and uh… -- **16:49:09 · Dominik Kapusta:** Mm-hmm. Mmhm. -- **16:49:11 · Alex Martemyanov:** it feels kinda fine, posting an update in the morning when I didn't finish, and I don't see the outcome yet, and… It's kind of. It may get tricky. -- **16:49:25 · Dominik Kapusta:** Okay. Yeah, uh… Oh, okay, okay. All right. Fine, but I will… I would still keep that growth area here, because I think this is the most important thing for you right now. It's to… to be… -- **16:49:57 · Alex Martemyanov:** I'm trying to… To work with it from the different perspective and having some. Yeah, basically, I've also added to the agenda, like, the, uh, the personal OS setup that. And that keeps growing in parallel. I already had some. Local agents analyzing my past work and. current work and just prepare the workflow for the. current status analysis and comparing it to the local work that is being done and tracing the communication requiring my reactions. Just to keep things in focus and maybe post some notifications as… as is required. So to get myself like pinged that. Okay, you already like hyper focus to this task like for 6 h, you should stop for today. Post an update and answer for these 3 comments. So this is the. -- **16:50:51 · Dominik Kapusta:** Mm-hmm, mm-hmm. Yeah. Yes. -- **16:51:03 · Alex Martemyanov:** should be the case and it's… It's already starts to show something. Building up from it. -- **16:51:11 · Dominik Kapusta:** Did you say you put it in the agenda? -- **16:51:12 · Alex Martemyanov:** Oh. No, uh, yes. Uh, yes, I put it to the, uh… The agenda. -- **16:51:24 · Dominik Kapusta:** Can't find it. -- **16:51:24 · Alex Martemyanov:** Right. Hmm. Where is it? -- **16:51:33 · Dominik Kapusta:** I don't know. -- **16:51:35 · Alex Martemyanov:** Sure, it was there. It was in the… Good. Not here. Okay, let's put it here. It was the update that was, uh… the old content, basically, I updated it. Maybe… maybe you just got something from it. -- **16:51:56 · Dominik Kapusta:** Oh. Okay, in the old path. Mmhm. -- **16:52:46 · Alex Martemyanov:** And… Yeah. So basically what's, it's done there, it's, monitors the activity watch, active window, of course, locally, related to the local work trees, to Asana tasks, loads, the Asana task. -- **16:53:27 · Dominik Kapusta:** Mm-hmm. -- **16:53:29 · Alex Martemyanov:** full listing and summarizes it to the short project status and key decisions. And, uh, when the new events arrive, uh, they are updated. Um, so… In the perfect world, it should, like… Group up, analyze my current day workflow, analyze the… -- **16:53:49 · Dominik Kapusta:** Mm-hmm. -- **16:53:51 · Alex Martemyanov:** week, weekly, uh… weekly plans and career plans and mix it in a balanced set of. Oh. plans and nudges like notifications to react on something or to. Minish Lee. Focus on context switching. It starts getting some shape, so it's currently on the state of current local agent output. Of course, it should be gone through manually in my free time, and I should see the actual project status and what I got from it. And how it understands it, so there's no… Mmhm. Doubling source of truth. And yeah, after it, I'll build something on top of it. Meanwhile, it led some consequences with the token solar usage. -- **16:54:58 · Dominik Kapusta:** Thank you. -- **16:54:58 · Alex Martemyanov:** So I got commented from Kane. Uh, asking me to share the actual results I've got from spending. the quarters. the first week of October. -- **16:55:13 · Dominik Kapusta:** Wow. -- **16:55:15 · Alex Martemyanov:** Yeah, um… I'm gonna share it later. Probably. -- **16:55:23 · Dominik Kapusta:** Interesting. -- **16:55:25 · Alex Martemyanov:** And… -- **16:55:25 · Dominik Kapusta:** So, what was it? You exhausted the quota, or you have higher quota already? -- **16:55:29 · Alex Martemyanov:** Yeah, basically, I've adjusted the quota, and I've requested a quota raise for Claude, and I got raised the quota. -- **16:55:35 · Dominik Kapusta:** Yeah, and then they are asking for what you've done with it. -- **16:55:39 · Alex Martemyanov:** Yeah, unboxing what was happening and what was going wrong. So basically, it's just the default Opus that I have set here again. Let's just, especially on the high level. -- **16:55:51 · Dominik Kapusta:** Was was it? Was it 5.5? -- **16:55:54 · Alex Martemyanov:** Yep. Yeah, Opus 5.5, the org default, set for high, it's uh… -- **16:55:56 · Dominik Kapusta:** Oh. -- **16:56:01 · Alex Martemyanov:** It just burned another 200 of bucks yesterday for the test iteration work, because I… -- **16:56:04 · Dominik Kapusta:** Hmm. Mm-hmm. -- **16:56:08 · Alex Martemyanov:** Started it that way and forgot to switch it back. -- **16:56:11 · Dominik Kapusta:** Hmmm. -- **16:56:11 · Alex Martemyanov:** So and it's really easy to to burn 200 there. So 5 days of work, and you have the 1,000 out. -- **16:56:12 · Dominik Kapusta:** Okay. Yeah, sure. -- **16:56:18 · Alex Martemyanov:** So nothing special, actually. -- **16:56:21 · Dominik Kapusta:** Yeah. Okay. -- **16:56:21 · Alex Martemyanov:** Um… So I'll probably try to mention it, that we should set the default model. to another one, because it says Opus by default, because it's set as ORG default. But yeah, otherwise there were some outputs from it. -- **16:56:36 · Dominik Kapusta:** Hmm… -- **16:56:41 · Alex Martemyanov:** like the UI test, the CPM web extension. 3 pull requests, and… Countless iteration of a revolution with virtual machines and all this setup. Actually, run with it, and… So it got the job done, but… The burning is still… -- **16:57:04 · Dominik Kapusta:** Interesting, interesting. I just saw, I just checked and it looks like I'm on medium effort because I had the medium effort set for Fable. I was using Fable on medium effort. -- **16:57:04 · Alex Martemyanov:** I've looked at my leggings. -- **16:57:19 · Dominik Kapusta:** And I switched back to Opus 5.5, and I kept medium effort. I didn't mean to keep medium effort, but I have very, very, very, very low usage this month. -- **16:57:30 · Alex Martemyanov:** Actually, Sonnet is using a reasonable amount of token, I say, and high effort, because I usually use high effort for some larger topics, especially. -- **16:57:37 · Dominik Kapusta:** Okay. -- **16:57:45 · Alex Martemyanov:** when I just run it, okay, evaluate this bug from Asana, run the test, fix it, and then come up with a PR, so I can check the final result and not iterate on every stage. And if I set medium effort, it just loses context, compacts it, and starts doing some… -- **16:57:50 · Dominik Kapusta:** Mm-hmm. Mm-hmm. -- **16:58:01 · Alex Martemyanov:** Some bullshit, usually. -- **16:58:04 · Dominik Kapusta:** Right. -- **16:58:06 · Alex Martemyanov:** But yeah, Sonnet is, uh, Sonnet or Fable is pretty good at it, and I just should not forget to switch it back from Opus. -- **16:58:15 · Dominik Kapusta:** Yeah. Uh, alright… -- **16:58:22 · Alex Martemyanov:** So yeah, coming back to the updates. -- **16:58:22 · Dominik Kapusta:** Override. -- **16:58:28 · Alex Martemyanov:** I'm… I'm working on that. -- **16:58:31 · Dominik Kapusta:** Mmhm. -- **16:58:31 · Alex Martemyanov:** So I have that that points to. To provide some updates and try to. To catch it if it requires some more attention and post updates. Earlier, for example, I have one pending from Kirby and some pixel not being reported. Mmm… I'll probably just pause it. I have to manage my top priority and answer later this week. This weekend's tomorrow. Okay. Uh, yeah, I'm working on it. And, uh… And, uh, and, and… Anything else on the, uh… On the growth areas. -- **16:59:23 · Dominik Kapusta:** Only growth areas… I think we should also keep the other one for… About. Essentially growing others. So that's for team leadership, which means reviewing stuff, which you… have done a nice job for Andre. I'll try to get feedback from him. -- **16:59:50 · Alex Martemyanov:** And it was… -- **16:59:53 · Dominik Kapusta:** Umm. -- **16:59:53 · Alex Martemyanov:** It was, uh… yeah, I tried… I mean, it was a lot of, uh… a lot of work, actually, spent on the reviews and back and forth and all of that, and… -- **17:00:03 · Dominik Kapusta:** Yeah, and it may be overwhelming, it may be annoying, but I also… -- **17:00:04 · Alex Martemyanov:** that… Goes like an. -- **17:00:11 · Dominik Kapusta:** I also heard from Andre that. Does your good reviewer? I'm going to send him a feedback request for that. -- **17:00:19 · Alex Martemyanov:** Yeah, training every day on Claude and Codex. -- **17:00:22 · Dominik Kapusta:** Yeah, so that was fine. We got feedback. Have you seen feedback from Max? -- **17:00:32 · Alex Martemyanov:** No. -- **17:00:33 · Dominik Kapusta:** It arrived yesterday. Uh, let me share… It's here. -- **17:01:04 · Alex Martemyanov:** And… Thanks. And… -- **17:01:18 · Dominik Kapusta:** which also… -- **17:01:18 · Alex Martemyanov:** Okay, 100. -- **17:01:21 · Dominik Kapusta:** What was that, sorry? -- **17:01:21 · Alex Martemyanov:** Yes, here we are. Oh, for months. -- **17:01:25 · Dominik Kapusta:** Yes. Have you read it? -- **17:01:28 · Alex Martemyanov:** Hmm… Okay. Mm-hmm. -- **17:01:50 · Dominik Kapusta:** Yeah, so, um… -- **17:01:53 · Alex Martemyanov:** Again, this is the career advisor task. -- **17:01:54 · Dominik Kapusta:** This is… This is also… I, sorry, what was that? -- **17:01:58 · Alex Martemyanov:** It's a visibility question. -- **17:02:00 · Dominik Kapusta:** I don't understand. -- **17:02:00 · Alex Martemyanov:** The career advisor task communication thing that. -- **17:02:04 · Dominik Kapusta:** The project advisor task. -- **17:02:07 · Alex Martemyanov:** Project advisor cost, right? -- **17:02:07 · Dominik Kapusta:** Yes, yes, yes. Yeah, yeah, so that's that. I don't know what to say, just remember about that, because the previous feedback from Alessandro was really, really good. And I was like, ah, that's amazing. -- **17:02:27 · Alex Martemyanov:** Yeah, generally we kept in touch with Alessandro, and probably he was the… Only one, and the, uh, ODRIs were updated during the meeting… during the meetings, the stand-ups. -- **17:02:38 · Dominik Kapusta:** Uh-huh, yeah. -- **17:02:38 · Alex Martemyanov:** Uh, so there was no… nobody else, uh, involved there. Here in the status, it may look like. -- **17:02:44 · Dominik Kapusta:** Mm-hmm. -- **17:02:47 · Alex Martemyanov:** Because, uh, the project advisor communications in the summer look pretty much the same, actually, and I just… -- **17:02:53 · Dominik Kapusta:** Mmhm. Mmhm. -- **17:02:56 · Alex Martemyanov:** reached out to him directly on Mattermost, most of the times, and posting the project update in the… in the main desk. -- **17:02:59 · Dominik Kapusta:** Mm-mm. I see. Yeah, yeah. -- **17:03:03 · Alex Martemyanov:** So having no real discussions happening in the project advisor tasks. -- **17:03:08 · Dominik Kapusta:** Right, right. -- **17:03:09 · Alex Martemyanov:** That probably should come up with some kind of discussions to be put in there. -- **17:03:11 · Dominik Kapusta:** Oh. Yeah, probably, you know, don't do anything for the sake of doing it, but just… Documenting and the chats in that async task is a good habit to have. Yeah, um… We're also waiting for feedback from Michal. So we'll see. And I'll send one out to Andre. For now, I think let's keep your… let's keep your growth areas. So, yeah, focus on… I mean, keep communication in mind. And not only into priorities. -- **17:04:03 · Alex Martemyanov:** Okay, I'll just post an update today, probably that we discussed today about the project, and we're not getting up with all the PRs today. -- **17:04:14 · Dominik Kapusta:** Hmm, hmm. Fine. Uh, yeah, and the other one is leverage your functional skills to ensure that your peers keep a high quality bar. And I'm going to document the progress and the progresses that you've worked with Andra. Have you also commented on… Yeah, you have. You have commented on the ship review. So that's great. -- **17:04:37 · Alex Martemyanov:** On the ship review, on tech design. -- **17:04:39 · Dominik Kapusta:** Mmhm. -- **17:04:41 · Alex Martemyanov:** There was and the. And the VS Code tech design discussion and iterations. -- **17:04:46 · Dominik Kapusta:** Yeah, yeah, yeah, yeah, sure, sure. For tech designs here, for tech designs, we're looking for examples when you were the reviewer. -- **17:04:48 · Alex Martemyanov:** I guess. -- **17:04:56 · Dominik Kapusta:** So. Next time. Uh, and yeah, if there's something, uh, something, uh. that I spot that you could be a reviewer for, I will… I will arrange it. So that you could do it for a tech design. Good. -- **17:05:18 · Alex Martemyanov:** Okay… -- **17:05:22 · Dominik Kapusta:** I'm going to update it soon. Not many updates, anyway, in the Grove Areas. The Grove Areas stay. I'm gonna add a new shoutout, and slightly rework the Grove Areas, and that's it. For the… for the… this VS Code work… I think we're done. Your last comment was really good, like acknowledging everything and closing it and opening a new one. The new one, it is a little bit of a surprise, it comes so quick, so fast. That, yeah, people may be wondering… what are you doing in your free time? Which is… I know what you're doing, but it may be strange. -- **17:06:06 · Alex Martemyanov:** Yeah, basically it was… In my bed yesterday, just with clothes. -- **17:06:10 · Dominik Kapusta:** Mmhm. No. -- **17:06:12 · Alex Martemyanov:** Just to iterate over it. -- **17:06:15 · Dominik Kapusta:** Mmhm. -- **17:06:15 · Alex Martemyanov:** So… -- **17:06:19 · Dominik Kapusta:** Fine. -- **17:06:21 · Alex Martemyanov:** Yes, that's in the technical leadership and the… -- **17:06:21 · Dominik Kapusta:** Good. I'll… -- **17:06:25 · Alex Martemyanov:** We integrate the agenda task. Uh, ship review, the comment on tech design… -- **17:06:32 · Dominik Kapusta:** Mmhm. -- **17:06:35 · Alex Martemyanov:** And the VS Code tech design moving forward and giving Apple weekly updates about it. And… Bye. -- **17:06:56 · Dominik Kapusta:** I will respond to the tech design later today, hopefully today. -- **17:07:00 · Alex Martemyanov:** Okay, so I hope it makes sense, I'll just… Ah, that's true. -- **17:07:06 · Dominik Kapusta:** There are some comments from Diego already and Federico. If this sounds like… -- **17:07:11 · Alex Martemyanov:** Thank you. I feel like I cannot finish it today. -- **17:07:16 · Dominik Kapusta:** If this sounds like something that will need a few extra files in the repository, which is what I think… -- **17:07:23 · Alex Martemyanov:** Yeah, basically, there is one script, or six script files in Scripts, VS Code directory, and a code workspace file that loads it. -- **17:07:30 · Dominik Kapusta:** Mm-hmm. -- **17:07:36 · Alex Martemyanov:** Other, uh, other stuff it does by itself. -- **17:07:38 · Dominik Kapusta:** Oh, okay. -- **17:07:40 · Alex Martemyanov:** So it basically loads, generates the build server, generates the tasks and launch JSON. -- **17:07:44 · Dominik Kapusta:** Mm-hmm. -- **17:07:46 · Alex Martemyanov:** Uh, to keep it not in the repository, and everything happens in the script. -- **17:07:49 · Dominik Kapusta:** Mmhm. -- **17:07:54 · Alex Martemyanov:** And removed by removing those three files if needed. -- **17:07:54 · Dominik Kapusta:** So overall, yeah, overall the ask of this tech design is… Just adding these files really, because nothing changes. Mm-Hmm. -- **17:08:03 · Alex Martemyanov:** Yeah. -- **17:08:05 · Dominik Kapusta:** with the rest. That sounds good. Yeah. Okay, okay, okay, um… Good. Great. Thanks for that, um… yeah, I think we're… I think we're good, I think we're… Clear. If we're not, we'll iterate next month, next Tuesday. Uh, good. -- **17:08:26 · Alex Martemyanov:** Yeah, on that one, the PR is basically ready, and uh… Confirmed working with some. Extensive tests. And I think… Even the VS Code remote debugging should be up soon as well. But the bottleneck is my review. attention that I have. Still have to complete the top priority and just… Iterate over all the stuff happening, including the communications. -- **17:08:59 · Dominik Kapusta:** Sure. -- **17:09:02 · Alex Martemyanov:** Quickly. -- **17:09:02 · Dominik Kapusta:** Right, yeah. If you have a pull request sort of ready, or a draft pull request up, you can just link it there. -- **17:09:07 · Alex Martemyanov:** Yeah, I have one… I have one here in search. And that window, this window, it's the crash. I hope it makes sense. Should be pretty clear, but, uh, just touch as many places in the code, and use a swift linter to prevent the… -- **17:09:27 · Dominik Kapusta:** Whoa. -- **17:09:35 · Alex Martemyanov:** failures… possible failures in the future. And has, uh, Swiss law for… -- **17:09:39 · Dominik Kapusta:** Okay. -- **17:09:41 · Alex Martemyanov:** to wrap the errors that we got, that we may extract from other places. -- **17:09:46 · Dominik Kapusta:** Mm-hmm, mm-hmm, m. -- **17:09:47 · Alex Martemyanov:** Um… yeah, it has tests, and… validation steps to to prove the clauses happening on on Rosetta. 86 architectures and to prove it does not. Let me just get this fixed. -- **17:10:03 · Dominik Kapusta:** Nice. Okay, fine. -- **17:10:07 · Alex Martemyanov:** And after that, I could switch to… Give it to priority telemetry, and I'll give an update in the project advisor's task at the time. Not getting everything ready by today, and uh… -- **17:10:20 · Dominik Kapusta:** Uh-huh. -- **17:10:21 · Alex Martemyanov:** Because… Because of this work and. The crash and the. And the amount of tasks to be filled, including the plans and attribution data analysis. -- **17:10:38 · Dominik Kapusta:** Good, sounds good. Alright. -- **17:10:38 · Alex Martemyanov:** Smooth. -- **17:10:42 · Dominik Kapusta:** Fine. Thank you very much. Have. -- **17:10:45 · Alex Martemyanov:** Yep. Thank you, Drew, for… -- **17:10:47 · Dominik Kapusta:** Have a great rest of the day. See ya. Bye bye. -- **17:10:49 · Alex Martemyanov:** I'm sounding this loud and everything. Yep, I'll… -- **17:10:53 · Dominik Kapusta:** No, don't worry. That's great. -- **17:10:54 · Alex Martemyanov:** I'll get back to you on the… diff --git a/work/zoom-transcripts/2026-10-19 Michal Smaga's Personal Meeting Room QvxllpCuTTSLGEZp-R6jQw/transcript.json b/work/zoom-transcripts/2026-10-19 Michal Smaga's Personal Meeting Room QvxllpCuTTSLGEZp-R6jQw/transcript.json index c0c0cfd7..56825536 100644 --- a/work/zoom-transcripts/2026-10-19 Michal Smaga's Personal Meeting Room QvxllpCuTTSLGEZp-R6jQw/transcript.json +++ b/work/zoom-transcripts/2026-10-19 Michal Smaga's Personal Meeting Room QvxllpCuTTSLGEZp-R6jQw/transcript.json @@ -23,656 +23,6 @@ "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." } ] } diff --git a/work/zoom-transcripts/2026-10-19 Michal Smaga's Personal Meeting Room QvxllpCuTTSLGEZp-R6jQw/transcript.md b/work/zoom-transcripts/2026-10-19 Michal Smaga's Personal Meeting Room QvxllpCuTTSLGEZp-R6jQw/transcript.md index 72165174..331d24b5 100644 --- a/work/zoom-transcripts/2026-10-19 Michal Smaga's Personal Meeting Room QvxllpCuTTSLGEZp-R6jQw/transcript.md +++ b/work/zoom-transcripts/2026-10-19 Michal Smaga's Personal Meeting Room QvxllpCuTTSLGEZp-R6jQw/transcript.md @@ -15,133 +15,3 @@ 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. diff --git a/work/zoom-transcripts/2026-11-03 Dominik Kapusta's Personal Meeting Room kOfTt34CRsG3dquIpsIzYA/transcript.json b/work/zoom-transcripts/2026-11-03 Dominik Kapusta's Personal Meeting Room kOfTt34CRsG3dquIpsIzYA/transcript.json index fefbf37b..5aa89c6d 100644 --- a/work/zoom-transcripts/2026-11-03 Dominik Kapusta's Personal Meeting Room kOfTt34CRsG3dquIpsIzYA/transcript.json +++ b/work/zoom-transcripts/2026-11-03 Dominik Kapusta's Personal Meeting Room kOfTt34CRsG3dquIpsIzYA/transcript.json @@ -23,831 +23,6 @@ "time": "16:04:21", "speaker": "Dominik Kapusta", "text": "on the CPM." - }, - { - "time": "16:04:24", - "speaker": "Alex Martemyanov", - "text": "Uh, yeah. So, where were we? I think we missed the last one, and there was the performance review, and there was… They have days. With the demo that I made. And the last week I spent on CPM, and they updated. The updated plan of it. Oh, yeah. So, currently, from the top priority, uh… That is kinda… I'd say we've reached the… We've exhausted all the hypotheses that we've got so far. There is still a couple of fixes we're expecting to get publicly released next week, but still the metrics we defined, we call it acceptable." - }, - { - "time": "16:05:12", - "speaker": "Dominik Kapusta", - "text": "Uh-huh." - }, - { - "time": "16:05:25", - "speaker": "Alex Martemyanov", - "text": "They are probably not going to be reached. And the breakage is somewhere, somewhere else, not reproduced. And the data we've got does not show it. So I just had a call with Michal on the further movements. So probably we'll gonna discuss it on today's weekly call. Oh. Whether to wrap it up in this stage or. Thanks. some other… some other things. But anyways, I think we should have some… we should introduce some permanent metrics, just to keep it, uh… To indicate any breakages in the future." - }, - { - "time": "16:06:12", - "speaker": "Dominik Kapusta", - "text": "No." - }, - { - "time": "16:06:13", - "speaker": "Alex Martemyanov", - "text": "And there is some cleanup to be done, like removing the temporary feature flags and hypotheses that were rejected. Um, so… So that's the plan for this week, I guess. I'm gonna update a bit later today. On the top priority. Bye." - }, - { - "time": "16:06:33", - "speaker": "Dominik Kapusta", - "text": "So the issue is still there." - }, - { - "time": "16:06:35", - "speaker": "Alex Martemyanov", - "text": "Yep." - }, - { - "time": "16:06:36", - "speaker": "Dominik Kapusta", - "text": "But you… You were able to… Lower the numbers, at least for iOS, right? For both platforms?" - }, - { - "time": "16:06:43", - "speaker": "Alex Martemyanov", - "text": "Uh, yes, so there were some number pollution, uh, fixed last week, uh, so actually each. error pages… each error page, uh, like regular tab loading problem, was reported because CPM is not loading on this, uh…" - }, - { - "time": "16:07:01", - "speaker": "Dominik Kapusta", - "text": "Oh, yeah, okay." - }, - { - "time": "16:07:02", - "speaker": "Alex Martemyanov", - "text": "HTML content replacement and uh but yeah it uh it gave some expected uh. drop Marques numbers, like, from 3% to 1.9." - }, - { - "time": "16:07:17", - "speaker": "Dominik Kapusta", - "text": "Mmhm." - }, - { - "time": "16:07:18", - "speaker": "Alex Martemyanov", - "text": "Of the affected users, but it's still above the threshold we defined, like, below 1%." - }, - { - "time": "16:07:25", - "speaker": "Dominik Kapusta", - "text": "Yeah, yeah." - }, - { - "time": "16:07:26", - "speaker": "Alex Martemyanov", - "text": "While iOS is below 1%, it's like 0.9. Not. Not not much, but still." - }, - { - "time": "16:07:36", - "speaker": "Dominik Kapusta", - "text": "All right, yeah." - }, - { - "time": "16:07:37", - "speaker": "Alex Martemyanov", - "text": "So there were actual fixes. There were actual bugs or corner cases discovered. Some of those corner cases are not the case and not giving the meaningful amount of breakage. So we won't proceed with them. But some of them, like pin tabs issues or… Some pre-loading, pre-warm-up are something to keep, because they…" - }, - { - "time": "16:08:04", - "speaker": "Dominik Kapusta", - "text": "Mm-hmm." - }, - { - "time": "16:08:05", - "speaker": "Alex Martemyanov", - "text": "They affect something, but not the main portion of it, basically. There is 35% of the breakage reports. Or… or even 40%, that… Just actually show… just show the normal… Lodge. And, uh… The unit failure." - }, - { - "time": "16:08:30", - "speaker": "Dominik Kapusta", - "text": "You know." - }, - { - "time": "16:08:32", - "speaker": "Alex Martemyanov", - "text": "So… There is no obvious points in code pointing to anything. Like, it looks like everything is okay, but it just won't work. Oh. So, yeah, it's probably up to the… objective to decide whether to go further with it. So I'll try to give a plan for, first of all, for a cleanup, whether to keep it inside the project or do it as a follow-up outside of the project, although it won't change much." - }, - { - "time": "16:09:06", - "speaker": "Dominik Kapusta", - "text": "No." - }, - { - "time": "16:09:11", - "speaker": "Alex Martemyanov", - "text": "Because there is, uh…" - }, - { - "time": "16:09:11", - "speaker": "Dominik Kapusta", - "text": "Twice." - }, - { - "time": "16:09:13", - "speaker": "Alex Martemyanov", - "text": "There is actually much a lot of things to to clean up because we've added a bunch of feature flags, pixels, metrics and." - }, - { - "time": "16:09:19", - "speaker": "Dominik Kapusta", - "text": "Yeah, I suppose so." - }, - { - "time": "16:09:21", - "speaker": "Alex Martemyanov", - "text": "Yeah, it's not just one feature flag to remove outside of the project." - }, - { - "time": "16:09:24", - "speaker": "Dominik Kapusta", - "text": "Cheers." - }, - { - "time": "16:09:26", - "speaker": "Alex Martemyanov", - "text": "And, uh, yeah, adding some permanent metrics is also a thing, too. to have. But otherwise, we're probably gonna at least put it on hold. Or post-mortem leads, and uh… Decide what to do with the data updated." - }, - { - "time": "16:09:47", - "speaker": "Dominik Kapusta", - "text": "So I saw, I saw, yeah, I saw Russell commenting on the…" - }, - { - "time": "16:09:47", - "speaker": "Alex Martemyanov", - "text": "If we choose." - }, - { - "time": "16:09:52", - "speaker": "Dominik Kapusta", - "text": "DRI advisor task to… Make a decision." - }, - { - "time": "16:09:56", - "speaker": "Alex Martemyanov", - "text": "Yeah, basically, what would be the…" - }, - { - "time": "16:10:00", - "speaker": "Dominik Kapusta", - "text": "No." - }, - { - "time": "16:10:01", - "speaker": "Alex Martemyanov", - "text": "the completion of the project. Yeah. So I'm at the moment I'm preparing this." - }, - { - "time": "16:10:03", - "speaker": "Dominik Kapusta", - "text": "Mmhm." - }, - { - "time": "16:10:08", - "speaker": "Alex Martemyanov", - "text": "Plan. We've discussed it with Michal. Go on with it, and uh… yeah. By the, by the meeting, I'm planning to update the data first, uh, to have the numbers, and uh…" - }, - { - "time": "16:10:19", - "speaker": "Dominik Kapusta", - "text": "Okay, awesome." - }, - { - "time": "16:10:23", - "speaker": "Alex Martemyanov", - "text": "That's the plan for cleanup and extended metrics or changed metrics that they're saying." - }, - { - "time": "16:10:28", - "speaker": "Dominik Kapusta", - "text": "So, I think… Just a general advice. This is not very official, not a very official communication thread. If you have something in progress, I think it's… Better than you… I mean, it's better when you post a comment that, yes, we will be wrapping up and then working on the plan, rather than keeping them waiting until you have the plan in place." - }, - { - "time": "16:10:54", - "speaker": "Alex Martemyanov", - "text": "You know." - }, - { - "time": "16:10:55", - "speaker": "Dominik Kapusta", - "text": "So, I would just comment quickly there that, yeah…" - }, - { - "time": "16:10:58", - "speaker": "Alex Martemyanov", - "text": "Yeah, makes sense." - }, - { - "time": "16:10:58", - "speaker": "Dominik Kapusta", - "text": "working on the plan, and then, yeah, post… and I will post an update later today, before the meeting." - }, - { - "time": "16:11:06", - "speaker": "Alex Martemyanov", - "text": "Okay, yeah. Um… For the AOR, there were a couple of things. So, first of all…" - }, - { - "time": "16:11:11", - "speaker": "Dominik Kapusta", - "text": "Awesome. Uh-huh." - }, - { - "time": "16:11:17", - "speaker": "Alex Martemyanov", - "text": "the holidays stuff that's…" - }, - { - "time": "16:11:20", - "speaker": "Dominik Kapusta", - "text": "Yes. Amazing." - }, - { - "time": "16:11:20", - "speaker": "Alex Martemyanov", - "text": "Uh, that waits for my input." - }, - { - "time": "16:11:24", - "speaker": "Dominik Kapusta", - "text": "Mm-hmm." - }, - { - "time": "16:11:24", - "speaker": "Alex Martemyanov", - "text": "Um… So yeah, I think it's some good changes, I hope. And so one is ready, the tooltip one, the link preview, ship preview." - }, - { - "time": "16:11:33", - "speaker": "Dominik Kapusta", - "text": "Julie, mm-hmm. Is the ship review already done or open?" - }, - { - "time": "16:11:39", - "speaker": "Alex Martemyanov", - "text": "The ship review is up. It's on Stephen for today. I think it's mostly up to Stephen to decide whether the design fits. And if it works, I think we'll move on." - }, - { - "time": "16:11:40", - "speaker": "Dominik Kapusta", - "text": "Okay. Yeah. Sure." - }, - { - "time": "16:11:51", - "speaker": "Alex Martemyanov", - "text": "Another one with the fire window as there were some inconsistencies. And… It's generally an important thing. I should just. Go through it carefully and review it myself first. And, I just didn't have time yet." - }, - { - "time": "16:12:11", - "speaker": "Dominik Kapusta", - "text": "Mmhm." - }, - { - "time": "16:12:11", - "speaker": "Alex Martemyanov", - "text": "For it. Another one is the top preview getting stuck. I also got some. Kind of AI feeds for it, but looking at it more closely, it changed some. Responder chain events and it's probably causing some over reporting the state. Maybe it's not too bad. But still, yeah, I also want to check to go through it one more time and… Just make sure. Maybe change something." - }, - { - "time": "16:12:49", - "speaker": "Dominik Kapusta", - "text": "Mm-hmm." - }, - { - "time": "16:12:50", - "speaker": "Alex Martemyanov", - "text": "Okay, um… And there were some tests work, some —. And… Measurement that we are… That we keep communication with Bartek, and… Changing the pixel. That seems stabilized. Yeah, with the CPM breakage, uh, fix, you've got the, um…" - }, - { - "time": "16:13:11", - "speaker": "Dominik Kapusta", - "text": "And… Thank you." - }, - { - "time": "16:13:21", - "speaker": "Alex Martemyanov", - "text": "the content blocking data polluted, the logging time, because now it happens after the CPM warm-up, and. It does not indicate the actual… Mm, time till interaction." - }, - { - "time": "16:13:39", - "speaker": "Dominik Kapusta", - "text": "Okay. Yes." - }, - { - "time": "16:13:41", - "speaker": "Alex Martemyanov", - "text": "And… So yeah, we are gonna merge the metrics together and have some buckets to indicate actual timings inside of it. And, uh, yeah, Patrick suggested to change the name, so it… so it's not, uh… misleading, because it's… currently, it's about the compile… compilation of the rule timing, and uh… if it's a common metric, it should be a different one, I guess." - }, - { - "time": "16:14:04", - "speaker": "Dominik Kapusta", - "text": "Uh-huh. You know." - }, - { - "time": "16:14:11", - "speaker": "Alex Martemyanov", - "text": "And… And the last thing… is the… Older runners, virtual machines, and all that stuff, but… No progress since last week on that. And, uh, yeah, I'm… Since one is AFK, I'm also nevertheless maintenance this week." - }, - { - "time": "16:14:45", - "speaker": "Dominik Kapusta", - "text": "Yeah, yeah, I saw that. Thanks for… stepping in. I couldn't do it because I was off yesterday, but thanks for your help. All right, I'm, uh… I'm behind things because of the performance review last week, and this is finally wrapping up. We've. Supposedly the last day, today. Uh, the last day of… Reviewing the reviews, and then the next 3 days will be the calibration, company-wide calibration, that… shouldn't affect. my reviews, at least, so I hope I'll be free. But, yeah. Last week was… tricky, and also… Jonathan was late to… to the reviews, so he was working on the weekend and was asking questions, so I was responding to him on the weekend. Yeah, it is what it is. Uh… Right, so that's that. What do you think about the CPMN? Sorry, I keep saying CPMN because of… the OL metric, but… well, the CPM project… next steps? I mean, you… you told me that we'll be wrapping up, but is it this week, or rather next week? I'm just thinking about when you will be freeing up for the next… project." - }, - { - "time": "16:16:28", - "speaker": "Alex Martemyanov", - "text": "I guess this week is for the cleanup and metrics." - }, - { - "time": "16:16:32", - "speaker": "Dominik Kapusta", - "text": "Yeah, yeah." - }, - { - "time": "16:16:34", - "speaker": "Alex Martemyanov", - "text": "And… But, yeah, I'm not sure whether it would be up to me to proceed with it, or we just wrap it up." - }, - { - "time": "16:16:47", - "speaker": "Dominik Kapusta", - "text": "Well, you'll have a meeting today, right?" - }, - { - "time": "16:16:48", - "speaker": "Alex Martemyanov", - "text": "It's, uh… Yep." - }, - { - "time": "16:16:50", - "speaker": "Dominik Kapusta", - "text": "Yeah, so we'll probably discuss there." - }, - { - "time": "16:16:53", - "speaker": "Alex Martemyanov", - "text": "Yeah, because currently I am kind of stuck. There is no further plans except for wrapping up and cleaning up." - }, - { - "time": "16:17:01", - "speaker": "Dominik Kapusta", - "text": "Yeah, so it's a good thing to suggest that explicitly." - }, - { - "time": "16:17:02", - "speaker": "Alex Martemyanov", - "text": "Uh, it…" - }, - { - "time": "16:17:09", - "speaker": "Dominik Kapusta", - "text": "And yeah, discuss it on the meeting, and… It's probably do it, so close the project." - }, - { - "time": "16:17:18", - "speaker": "Alex Martemyanov", - "text": "Because all the previous fixes were based on the data we've had." - }, - { - "time": "16:17:24", - "speaker": "Dominik Kapusta", - "text": "Uh-huh." - }, - { - "time": "16:17:24", - "speaker": "Alex Martemyanov", - "text": "or some… WebKit open issues, for example. But yeah, currently we will run out of data, and it just seems regular usage, and I… So it's not still produced locally and. There is no ideas on how to." - }, - { - "time": "16:17:42", - "speaker": "Dominik Kapusta", - "text": "Mm-hmm." - }, - { - "time": "16:17:43", - "speaker": "Alex Martemyanov", - "text": "How to approach to it, except for change something in the data itself. and how we measure things. It may give some… Some glimpse into what's actually happening. Maybe it's something obvious, for example, there is an issue with the… there is a possible issue with config loading from the web extension, so if it hangs, everything would hang. But, uh… Again, if it hangs, the water should reload it and it should be restored, but it's not getting restored. So maybe it's something inside of the extension, maybe not. And you've got no data and. It may turn in some endless cycle, getting some, measuring something, evaluating, fixing something." - }, - { - "time": "16:18:31", - "speaker": "Dominik Kapusta", - "text": "You know. No." - }, - { - "time": "16:18:36", - "speaker": "Alex Martemyanov", - "text": "Then re-measuring something and re-evaluating. Since we cannot, you know, strike actual user behavior and scenarios, it's mostly guessing here." - }, - { - "time": "16:18:46", - "speaker": "Dominik Kapusta", - "text": "Yeah, yeah, yeah." - }, - { - "time": "16:18:47", - "speaker": "Alex Martemyanov", - "text": "And…" - }, - { - "time": "16:18:48", - "speaker": "Dominik Kapusta", - "text": "Absolutely." - }, - { - "time": "16:18:49", - "speaker": "Alex Martemyanov", - "text": "So why I'm totally not sure how it proceeds and. Like, I got no… defined steps of it, except for wrapping up." - }, - { - "time": "16:19:07", - "speaker": "Dominik Kapusta", - "text": "Yeah, sounds good. All right." - }, - { - "time": "16:19:26", - "speaker": "Alex Martemyanov", - "text": "But yeah, uh, on your point on, uh, when… Could we possibly finish it? So the next week we have the fixes released, and uh… We need to analyze the data outcomes from it. If it changes anything." - }, - { - "time": "16:19:42", - "speaker": "Dominik Kapusta", - "text": "Mm-hmm." - }, - { - "time": "16:19:44", - "speaker": "Alex Martemyanov", - "text": "And. And… probably these. The cleanup and metrics will proceed into that week. I guess, but… There is a chance that it would be done as, like, a follow-up task, just to have the data analyzed. So…" - }, - { - "time": "16:20:07", - "speaker": "Dominik Kapusta", - "text": "Oh." - }, - { - "time": "16:20:08", - "speaker": "Alex Martemyanov", - "text": "There is a chance, uh, that in a week or two. I'll be available for another project and leave this. as a… general… backlog investigation, basically." - }, - { - "time": "16:20:27", - "speaker": "Dominik Kapusta", - "text": "Mm-hmm. Cool. Also, let's see what… What is the next step when it comes to your top priority? I mean, what's your next top priority? That's what I wanted to say, because I don't know now. I don't know what our objective needs. We are having an OL assessment. This week, but it sounds like… It sounds like they are not. Willing to request more people. Unless we, like, need them desperately? I suppose it's related to all being tier 2, essentially. So we… We just have what we have, and… And that's it. Um… We even have Jorge on a project right now. But he's not listed in the team for the next roadmap, so he will just wrap up his project and, I don't know, move somewhere else. Uh, that is weird to me." - }, - { - "time": "16:21:40", - "speaker": "Alex Martemyanov", - "text": "Okay, that's fine, and uh…" - }, - { - "time": "16:21:41", - "speaker": "Dominik Kapusta", - "text": "But let's see." - }, - { - "time": "16:21:44", - "speaker": "Alex Martemyanov", - "text": "And how is the Chrome migration doing?" - }, - { - "time": "16:21:50", - "speaker": "Dominik Kapusta", - "text": "The Chromium migration, uh…" - }, - { - "time": "16:21:50", - "speaker": "Alex Martemyanov", - "text": "I heard it's." - }, - { - "time": "16:21:53", - "speaker": "Dominik Kapusta", - "text": "On the Windows side." - }, - { - "time": "16:21:55", - "speaker": "Alex Martemyanov", - "text": "Yeah." - }, - { - "time": "16:21:56", - "speaker": "Dominik Kapusta", - "text": "It's going forward, I'm not very close to it. It's actually, it has been moved from OL to OQ." - }, - { - "time": "16:22:03", - "speaker": "Alex Martemyanov", - "text": "Hmm." - }, - { - "time": "16:22:04", - "speaker": "Dominik Kapusta", - "text": "So, I'm not really following it very closely, but they are working on it, and they are just doing, you know, feature by feature. I don't also know the… The roadmap, as in when, uh, when will they be ready? Um…" - }, - { - "time": "16:22:24", - "speaker": "Alex Martemyanov", - "text": "But it's not public yet, right?" - }, - { - "time": "16:22:26", - "speaker": "Dominik Kapusta", - "text": "It is not public, not… no, it… It's not. Um… but they are working on keeping the feature parity between… I mean, the feature parity. Whatever… I think whatever is added to… Uh, to… The public release is. adapted to Chrome. It's being adopted, like, on whatever we're adding. We're essentially adding new features on both." - }, - { - "time": "16:22:51", - "speaker": "Alex Martemyanov", - "text": "Okay." - }, - { - "time": "16:22:58", - "speaker": "Dominik Kapusta", - "text": "Browsers." - }, - { - "time": "16:23:00", - "speaker": "Alex Martemyanov", - "text": "Well, I was just thinking if… If it lands, if it reaches the public state. Would the desktop… my browser also be replaced with Chrome? It's like…" - }, - { - "time": "16:23:13", - "speaker": "Dominik Kapusta", - "text": "Yeah, it's…" - }, - { - "time": "16:23:15", - "speaker": "Alex Martemyanov", - "text": "Seems logical." - }, - { - "time": "16:23:16", - "speaker": "Dominik Kapusta", - "text": "Seems logical. It's not a given yet, because it would have consequences in… macOS browser… for App Store. having to stay on WebKit, essentially." - }, - { - "time": "16:23:30", - "speaker": "Alex Martemyanov", - "text": "Mm-hmm." - }, - { - "time": "16:23:30", - "speaker": "Dominik Kapusta", - "text": "Because we could ship a browser with… I actually don't know. What I wanted to say is… On iOS App Store, you can't have a browser that's not WebKit-based. with an entitlement to be able to become the system default browser. So if you want your browser to be able to be a system default browser, it needs to be WebKit-based, essentially. So we couldn't… And there are no plans to migrate iOS to Chromium, but for macOS App Store, I don't know. I don't know if it would work. If it's possible. That's something to be…" - }, - { - "time": "16:24:11", - "speaker": "Alex Martemyanov", - "text": "Whoa." - }, - { - "time": "16:24:12", - "speaker": "Dominik Kapusta", - "text": "Verified." - }, - { - "time": "16:24:14", - "speaker": "Alex Martemyanov", - "text": "Judging from macOS App Store not having actual Chrome." - }, - { - "time": "16:24:18", - "speaker": "Dominik Kapusta", - "text": "Yes!" - }, - { - "time": "16:24:18", - "speaker": "Alex Martemyanov", - "text": "Probably not. Yeah. Good point." - }, - { - "time": "16:24:20", - "speaker": "Dominik Kapusta", - "text": "Yeah, yeah." - }, - { - "time": "16:24:22", - "speaker": "Alex Martemyanov", - "text": "Yeah, that's all. Such a couple." - }, - { - "time": "16:24:26", - "speaker": "Dominik Kapusta", - "text": "Because it's not… it's definitely not related to Chrome… Chromium itself, because there are Electron apps in…" - }, - { - "time": "16:24:26", - "speaker": "Alex Martemyanov", - "text": "Okay." - }, - { - "time": "16:24:35", - "speaker": "Dominik Kapusta", - "text": "App Store, so there are apps that… compile JavaScript, run JavaScript code, uh… In, uh, in App Store." - }, - { - "time": "16:24:46", - "speaker": "Alex Martemyanov", - "text": "Yeah." - }, - { - "time": "16:24:47", - "speaker": "Dominik Kapusta", - "text": "Um, so you can ship an engine, yeah, yeah, but for some reason there are no chromium-based browsers there, yeah." - }, - { - "time": "16:24:48", - "speaker": "Alex Martemyanov", - "text": "Just a browser." - }, - { - "time": "16:24:57", - "speaker": "Dominik Kapusta", - "text": "Mmhm." - }, - { - "time": "16:24:58", - "speaker": "Alex Martemyanov", - "text": "Okay." - }, - { - "time": "16:25:06", - "speaker": "Dominik Kapusta", - "text": "Yeah, but we'll see. It's not for now, like, macOS for now is…" - }, - { - "time": "16:25:07", - "speaker": "Alex Martemyanov", - "text": "Well…" - }, - { - "time": "16:25:12", - "speaker": "Dominik Kapusta", - "text": "focused on extensions. We are going to ship extensions by the end of the year. Technically, the due date is end of November, but I'm not sure if we'll meet it. But, yeah, November, December, anyway. And then we'll see. So we'll probably keep…" - }, - { - "time": "16:25:33", - "speaker": "Alex Martemyanov", - "text": "Okay." - }, - { - "time": "16:25:33", - "speaker": "Dominik Kapusta", - "text": "doing some things until the Chromium… Fork is out. And then we'll… start thinking about macOS Chromium fork. So, still a few months to go. Yeah." - }, - { - "time": "16:25:50", - "speaker": "Alex Martemyanov", - "text": "Okay. What the hell does that mean?" - }, - { - "time": "16:26:05", - "speaker": "Dominik Kapusta", - "text": "So, what's the status of your hack days, besides that one tooltip thingy? What about the fire animation?" - }, - { - "time": "16:26:13", - "speaker": "Alex Martemyanov", - "text": "Uh… The fire animation is still there, yes. As I told, it touches the burning logics because it's related to windows opening and closing. There were some issues found." - }, - { - "time": "16:26:27", - "speaker": "Dominik Kapusta", - "text": "Yeah. Yeah, I commented… I commented about full screen." - }, - { - "time": "16:26:31", - "speaker": "Alex Martemyanov", - "text": "In the original code, so…" - }, - { - "time": "16:26:35", - "speaker": "Dominik Kapusta", - "text": "I remember that." - }, - { - "time": "16:26:35", - "speaker": "Alex Martemyanov", - "text": "Uh, I guess full screen is, uh, the smallest of the problems, because I think it's not look it looks nice when this there is full screen during revealing the desktop under." - }, - { - "time": "16:26:40", - "speaker": "Dominik Kapusta", - "text": "Okay." - }, - { - "time": "16:26:49", - "speaker": "Alex Martemyanov", - "text": "But, uh… I'm more talking about the data clearing itself that's happening and tied to the window closing, window reopening process. So I I need to come come back to it. Basically, I didn't. Since they have this." - }, - { - "time": "16:27:09", - "speaker": "Dominik Kapusta", - "text": "Mm-hmm." - }, - { - "time": "16:27:11", - "speaker": "Alex Martemyanov", - "text": "So it's somewhere in my plan." - }, - { - "time": "16:27:15", - "speaker": "Dominik Kapusta", - "text": "Sure, sure, sure. All right. All right, that's fine. Yeah." - }, - { - "time": "16:27:20", - "speaker": "Alex Martemyanov", - "text": "It's a top priority." - }, - { - "time": "16:27:24", - "speaker": "Dominik Kapusta", - "text": "Yeah, if you could keep pushing it forward on the side, that would be great." - }, - { - "time": "16:27:26", - "speaker": "Alex Martemyanov", - "text": "Hello? Yeah, there was also this app-wide theming support with the buttons backgrounds and title bar backgrounds. Like this Windows 95 thing." - }, - { - "time": "16:27:41", - "speaker": "Dominik Kapusta", - "text": "Mmhm." - }, - { - "time": "16:27:43", - "speaker": "Alex Martemyanov", - "text": "Uh, thank you. I also keep it somewhere, maybe for the next five days to make it more production ready, so we can support a wider amount of themable." - }, - { - "time": "16:27:50", - "speaker": "Dominik Kapusta", - "text": "Yeah, yeah. Mm-hmm." - }, - { - "time": "16:27:56", - "speaker": "Alex Martemyanov", - "text": "Areas like changing icons. For the buttons, for backgrounds and titles." - }, - { - "time": "16:28:07", - "speaker": "Dominik Kapusta", - "text": "Mmm. Hmm. Right. Hmm. So, uh… So, it looks like… Everything is clear, at least with regards to your top priority, it will become more clear after today's call, in a way. And the rest is… Just you following up on your… Like this work. And… Roughly, that's it." - }, - { - "time": "16:28:56", - "speaker": "Alex Martemyanov", - "text": "Yeah, the good news, I'm… Cleaned up most of my backlog. There are still a lot of like feature flags to be removed and." - }, - { - "time": "16:29:07", - "speaker": "Dominik Kapusta", - "text": "Yeah, I also have some." - }, - { - "time": "16:29:08", - "speaker": "Alex Martemyanov", - "text": "It's supposed to be cleaned up. related to CPM mostly. But, yeah, otherwise, uh, the tests… work. So there's 5 tasks in my FTQ." - }, - { - "time": "16:29:24", - "speaker": "Dominik Kapusta", - "text": "No." - }, - { - "time": "16:29:24", - "speaker": "Alex Martemyanov", - "text": "Otherwise, it's much better than before." - }, - { - "time": "16:29:28", - "speaker": "Dominik Kapusta", - "text": "That sounds great. Alright, if nothing more, then we can wrap it up here, because I also don't have much, because last week was… What it was." - }, - { - "time": "16:29:37", - "speaker": "Alex Martemyanov", - "text": "Yeah, so waiting for the performance review and results." - }, - { - "time": "16:29:40", - "speaker": "Dominik Kapusta", - "text": "Yeah, the performance review will be back next Tuesday, so we'll talk about it. And that's it for now." - }, - { - "time": "16:29:52", - "speaker": "Alex Martemyanov", - "text": "Okay, okay." - }, - { - "time": "16:29:52", - "speaker": "Dominik Kapusta", - "text": "All right, if you need anything, just ping me on Mattermost, happy to chat. And other than that, thank you very much, and see you at the Apple Weekly." - }, - { - "time": "16:30:04", - "speaker": "Alex Martemyanov", - "text": "Yep. Okay. See you." } ] } diff --git a/work/zoom-transcripts/2026-11-03 Dominik Kapusta's Personal Meeting Room kOfTt34CRsG3dquIpsIzYA/transcript.md b/work/zoom-transcripts/2026-11-03 Dominik Kapusta's Personal Meeting Room kOfTt34CRsG3dquIpsIzYA/transcript.md index 2abc5321..31cca581 100644 --- a/work/zoom-transcripts/2026-11-03 Dominik Kapusta's Personal Meeting Room kOfTt34CRsG3dquIpsIzYA/transcript.md +++ b/work/zoom-transcripts/2026-11-03 Dominik Kapusta's Personal Meeting Room kOfTt34CRsG3dquIpsIzYA/transcript.md @@ -15,168 +15,3 @@ source: "https://us01mynotes.zoom.us/kOfTt34CRsG3dquIpsIzYA" - **16:04:06 · Dominik Kapusta:** How's. Going. - **16:04:09 · Alex Martemyanov:** Um, yeah, no worries. Forward. Uh, still there… Still there, I guess, and not much changed. - **16:04:21 · Dominik Kapusta:** on the CPM. -- **16:04:24 · Alex Martemyanov:** Uh, yeah. So, where were we? I think we missed the last one, and there was the performance review, and there was… They have days. With the demo that I made. And the last week I spent on CPM, and they updated. The updated plan of it. Oh, yeah. So, currently, from the top priority, uh… That is kinda… I'd say we've reached the… We've exhausted all the hypotheses that we've got so far. There is still a couple of fixes we're expecting to get publicly released next week, but still the metrics we defined, we call it acceptable. -- **16:05:12 · Dominik Kapusta:** Uh-huh. -- **16:05:25 · Alex Martemyanov:** They are probably not going to be reached. And the breakage is somewhere, somewhere else, not reproduced. And the data we've got does not show it. So I just had a call with Michal on the further movements. So probably we'll gonna discuss it on today's weekly call. Oh. Whether to wrap it up in this stage or. Thanks. some other… some other things. But anyways, I think we should have some… we should introduce some permanent metrics, just to keep it, uh… To indicate any breakages in the future. -- **16:06:12 · Dominik Kapusta:** No. -- **16:06:13 · Alex Martemyanov:** And there is some cleanup to be done, like removing the temporary feature flags and hypotheses that were rejected. Um, so… So that's the plan for this week, I guess. I'm gonna update a bit later today. On the top priority. Bye. -- **16:06:33 · Dominik Kapusta:** So the issue is still there. -- **16:06:35 · Alex Martemyanov:** Yep. -- **16:06:36 · Dominik Kapusta:** But you… You were able to… Lower the numbers, at least for iOS, right? For both platforms? -- **16:06:43 · Alex Martemyanov:** Uh, yes, so there were some number pollution, uh, fixed last week, uh, so actually each. error pages… each error page, uh, like regular tab loading problem, was reported because CPM is not loading on this, uh… -- **16:07:01 · Dominik Kapusta:** Oh, yeah, okay. -- **16:07:02 · Alex Martemyanov:** HTML content replacement and uh but yeah it uh it gave some expected uh. drop Marques numbers, like, from 3% to 1.9. -- **16:07:17 · Dominik Kapusta:** Mmhm. -- **16:07:18 · Alex Martemyanov:** Of the affected users, but it's still above the threshold we defined, like, below 1%. -- **16:07:25 · Dominik Kapusta:** Yeah, yeah. -- **16:07:26 · Alex Martemyanov:** While iOS is below 1%, it's like 0.9. Not. Not not much, but still. -- **16:07:36 · Dominik Kapusta:** All right, yeah. -- **16:07:37 · Alex Martemyanov:** So there were actual fixes. There were actual bugs or corner cases discovered. Some of those corner cases are not the case and not giving the meaningful amount of breakage. So we won't proceed with them. But some of them, like pin tabs issues or… Some pre-loading, pre-warm-up are something to keep, because they… -- **16:08:04 · Dominik Kapusta:** Mm-hmm. -- **16:08:05 · Alex Martemyanov:** They affect something, but not the main portion of it, basically. There is 35% of the breakage reports. Or… or even 40%, that… Just actually show… just show the normal… Lodge. And, uh… The unit failure. -- **16:08:30 · Dominik Kapusta:** You know. -- **16:08:32 · Alex Martemyanov:** So… There is no obvious points in code pointing to anything. Like, it looks like everything is okay, but it just won't work. Oh. So, yeah, it's probably up to the… objective to decide whether to go further with it. So I'll try to give a plan for, first of all, for a cleanup, whether to keep it inside the project or do it as a follow-up outside of the project, although it won't change much. -- **16:09:06 · Dominik Kapusta:** No. -- **16:09:11 · Alex Martemyanov:** Because there is, uh… -- **16:09:11 · Dominik Kapusta:** Twice. -- **16:09:13 · Alex Martemyanov:** There is actually much a lot of things to to clean up because we've added a bunch of feature flags, pixels, metrics and. -- **16:09:19 · Dominik Kapusta:** Yeah, I suppose so. -- **16:09:21 · Alex Martemyanov:** Yeah, it's not just one feature flag to remove outside of the project. -- **16:09:24 · Dominik Kapusta:** Cheers. -- **16:09:26 · Alex Martemyanov:** And, uh, yeah, adding some permanent metrics is also a thing, too. to have. But otherwise, we're probably gonna at least put it on hold. Or post-mortem leads, and uh… Decide what to do with the data updated. -- **16:09:47 · Dominik Kapusta:** So I saw, I saw, yeah, I saw Russell commenting on the… -- **16:09:47 · Alex Martemyanov:** If we choose. -- **16:09:52 · Dominik Kapusta:** DRI advisor task to… Make a decision. -- **16:09:56 · Alex Martemyanov:** Yeah, basically, what would be the… -- **16:10:00 · Dominik Kapusta:** No. -- **16:10:01 · Alex Martemyanov:** the completion of the project. Yeah. So I'm at the moment I'm preparing this. -- **16:10:03 · Dominik Kapusta:** Mmhm. -- **16:10:08 · Alex Martemyanov:** Plan. We've discussed it with Michal. Go on with it, and uh… yeah. By the, by the meeting, I'm planning to update the data first, uh, to have the numbers, and uh… -- **16:10:19 · Dominik Kapusta:** Okay, awesome. -- **16:10:23 · Alex Martemyanov:** That's the plan for cleanup and extended metrics or changed metrics that they're saying. -- **16:10:28 · Dominik Kapusta:** So, I think… Just a general advice. This is not very official, not a very official communication thread. If you have something in progress, I think it's… Better than you… I mean, it's better when you post a comment that, yes, we will be wrapping up and then working on the plan, rather than keeping them waiting until you have the plan in place. -- **16:10:54 · Alex Martemyanov:** You know. -- **16:10:55 · Dominik Kapusta:** So, I would just comment quickly there that, yeah… -- **16:10:58 · Alex Martemyanov:** Yeah, makes sense. -- **16:10:58 · Dominik Kapusta:** working on the plan, and then, yeah, post… and I will post an update later today, before the meeting. -- **16:11:06 · Alex Martemyanov:** Okay, yeah. Um… For the AOR, there were a couple of things. So, first of all… -- **16:11:11 · Dominik Kapusta:** Awesome. Uh-huh. -- **16:11:17 · Alex Martemyanov:** the holidays stuff that's… -- **16:11:20 · Dominik Kapusta:** Yes. Amazing. -- **16:11:20 · Alex Martemyanov:** Uh, that waits for my input. -- **16:11:24 · Dominik Kapusta:** Mm-hmm. -- **16:11:24 · Alex Martemyanov:** Um… So yeah, I think it's some good changes, I hope. And so one is ready, the tooltip one, the link preview, ship preview. -- **16:11:33 · Dominik Kapusta:** Julie, mm-hmm. Is the ship review already done or open? -- **16:11:39 · Alex Martemyanov:** The ship review is up. It's on Stephen for today. I think it's mostly up to Stephen to decide whether the design fits. And if it works, I think we'll move on. -- **16:11:40 · Dominik Kapusta:** Okay. Yeah. Sure. -- **16:11:51 · Alex Martemyanov:** Another one with the fire window as there were some inconsistencies. And… It's generally an important thing. I should just. Go through it carefully and review it myself first. And, I just didn't have time yet. -- **16:12:11 · Dominik Kapusta:** Mmhm. -- **16:12:11 · Alex Martemyanov:** For it. Another one is the top preview getting stuck. I also got some. Kind of AI feeds for it, but looking at it more closely, it changed some. Responder chain events and it's probably causing some over reporting the state. Maybe it's not too bad. But still, yeah, I also want to check to go through it one more time and… Just make sure. Maybe change something. -- **16:12:49 · Dominik Kapusta:** Mm-hmm. -- **16:12:50 · Alex Martemyanov:** Okay, um… And there were some tests work, some —. And… Measurement that we are… That we keep communication with Bartek, and… Changing the pixel. That seems stabilized. Yeah, with the CPM breakage, uh, fix, you've got the, um… -- **16:13:11 · Dominik Kapusta:** And… Thank you. -- **16:13:21 · Alex Martemyanov:** the content blocking data polluted, the logging time, because now it happens after the CPM warm-up, and. It does not indicate the actual… Mm, time till interaction. -- **16:13:39 · Dominik Kapusta:** Okay. Yes. -- **16:13:41 · Alex Martemyanov:** And… So yeah, we are gonna merge the metrics together and have some buckets to indicate actual timings inside of it. And, uh, yeah, Patrick suggested to change the name, so it… so it's not, uh… misleading, because it's… currently, it's about the compile… compilation of the rule timing, and uh… if it's a common metric, it should be a different one, I guess. -- **16:14:04 · Dominik Kapusta:** Uh-huh. You know. -- **16:14:11 · Alex Martemyanov:** And… And the last thing… is the… Older runners, virtual machines, and all that stuff, but… No progress since last week on that. And, uh, yeah, I'm… Since one is AFK, I'm also nevertheless maintenance this week. -- **16:14:45 · Dominik Kapusta:** Yeah, yeah, I saw that. Thanks for… stepping in. I couldn't do it because I was off yesterday, but thanks for your help. All right, I'm, uh… I'm behind things because of the performance review last week, and this is finally wrapping up. We've. Supposedly the last day, today. Uh, the last day of… Reviewing the reviews, and then the next 3 days will be the calibration, company-wide calibration, that… shouldn't affect. my reviews, at least, so I hope I'll be free. But, yeah. Last week was… tricky, and also… Jonathan was late to… to the reviews, so he was working on the weekend and was asking questions, so I was responding to him on the weekend. Yeah, it is what it is. Uh… Right, so that's that. What do you think about the CPMN? Sorry, I keep saying CPMN because of… the OL metric, but… well, the CPM project… next steps? I mean, you… you told me that we'll be wrapping up, but is it this week, or rather next week? I'm just thinking about when you will be freeing up for the next… project. -- **16:16:28 · Alex Martemyanov:** I guess this week is for the cleanup and metrics. -- **16:16:32 · Dominik Kapusta:** Yeah, yeah. -- **16:16:34 · Alex Martemyanov:** And… But, yeah, I'm not sure whether it would be up to me to proceed with it, or we just wrap it up. -- **16:16:47 · Dominik Kapusta:** Well, you'll have a meeting today, right? -- **16:16:48 · Alex Martemyanov:** It's, uh… Yep. -- **16:16:50 · Dominik Kapusta:** Yeah, so we'll probably discuss there. -- **16:16:53 · Alex Martemyanov:** Yeah, because currently I am kind of stuck. There is no further plans except for wrapping up and cleaning up. -- **16:17:01 · Dominik Kapusta:** Yeah, so it's a good thing to suggest that explicitly. -- **16:17:02 · Alex Martemyanov:** Uh, it… -- **16:17:09 · Dominik Kapusta:** And yeah, discuss it on the meeting, and… It's probably do it, so close the project. -- **16:17:18 · Alex Martemyanov:** Because all the previous fixes were based on the data we've had. -- **16:17:24 · Dominik Kapusta:** Uh-huh. -- **16:17:24 · Alex Martemyanov:** or some… WebKit open issues, for example. But yeah, currently we will run out of data, and it just seems regular usage, and I… So it's not still produced locally and. There is no ideas on how to. -- **16:17:42 · Dominik Kapusta:** Mm-hmm. -- **16:17:43 · Alex Martemyanov:** How to approach to it, except for change something in the data itself. and how we measure things. It may give some… Some glimpse into what's actually happening. Maybe it's something obvious, for example, there is an issue with the… there is a possible issue with config loading from the web extension, so if it hangs, everything would hang. But, uh… Again, if it hangs, the water should reload it and it should be restored, but it's not getting restored. So maybe it's something inside of the extension, maybe not. And you've got no data and. It may turn in some endless cycle, getting some, measuring something, evaluating, fixing something. -- **16:18:31 · Dominik Kapusta:** You know. No. -- **16:18:36 · Alex Martemyanov:** Then re-measuring something and re-evaluating. Since we cannot, you know, strike actual user behavior and scenarios, it's mostly guessing here. -- **16:18:46 · Dominik Kapusta:** Yeah, yeah, yeah. -- **16:18:47 · Alex Martemyanov:** And… -- **16:18:48 · Dominik Kapusta:** Absolutely. -- **16:18:49 · Alex Martemyanov:** So why I'm totally not sure how it proceeds and. Like, I got no… defined steps of it, except for wrapping up. -- **16:19:07 · Dominik Kapusta:** Yeah, sounds good. All right. -- **16:19:26 · Alex Martemyanov:** But yeah, uh, on your point on, uh, when… Could we possibly finish it? So the next week we have the fixes released, and uh… We need to analyze the data outcomes from it. If it changes anything. -- **16:19:42 · Dominik Kapusta:** Mm-hmm. -- **16:19:44 · Alex Martemyanov:** And. And… probably these. The cleanup and metrics will proceed into that week. I guess, but… There is a chance that it would be done as, like, a follow-up task, just to have the data analyzed. So… -- **16:20:07 · Dominik Kapusta:** Oh. -- **16:20:08 · Alex Martemyanov:** There is a chance, uh, that in a week or two. I'll be available for another project and leave this. as a… general… backlog investigation, basically. -- **16:20:27 · Dominik Kapusta:** Mm-hmm. Cool. Also, let's see what… What is the next step when it comes to your top priority? I mean, what's your next top priority? That's what I wanted to say, because I don't know now. I don't know what our objective needs. We are having an OL assessment. This week, but it sounds like… It sounds like they are not. Willing to request more people. Unless we, like, need them desperately? I suppose it's related to all being tier 2, essentially. So we… We just have what we have, and… And that's it. Um… We even have Jorge on a project right now. But he's not listed in the team for the next roadmap, so he will just wrap up his project and, I don't know, move somewhere else. Uh, that is weird to me. -- **16:21:40 · Alex Martemyanov:** Okay, that's fine, and uh… -- **16:21:41 · Dominik Kapusta:** But let's see. -- **16:21:44 · Alex Martemyanov:** And how is the Chrome migration doing? -- **16:21:50 · Dominik Kapusta:** The Chromium migration, uh… -- **16:21:50 · Alex Martemyanov:** I heard it's. -- **16:21:53 · Dominik Kapusta:** On the Windows side. -- **16:21:55 · Alex Martemyanov:** Yeah. -- **16:21:56 · Dominik Kapusta:** It's going forward, I'm not very close to it. It's actually, it has been moved from OL to OQ. -- **16:22:03 · Alex Martemyanov:** Hmm. -- **16:22:04 · Dominik Kapusta:** So, I'm not really following it very closely, but they are working on it, and they are just doing, you know, feature by feature. I don't also know the… The roadmap, as in when, uh, when will they be ready? Um… -- **16:22:24 · Alex Martemyanov:** But it's not public yet, right? -- **16:22:26 · Dominik Kapusta:** It is not public, not… no, it… It's not. Um… but they are working on keeping the feature parity between… I mean, the feature parity. Whatever… I think whatever is added to… Uh, to… The public release is. adapted to Chrome. It's being adopted, like, on whatever we're adding. We're essentially adding new features on both. -- **16:22:51 · Alex Martemyanov:** Okay. -- **16:22:58 · Dominik Kapusta:** Browsers. -- **16:23:00 · Alex Martemyanov:** Well, I was just thinking if… If it lands, if it reaches the public state. Would the desktop… my browser also be replaced with Chrome? It's like… -- **16:23:13 · Dominik Kapusta:** Yeah, it's… -- **16:23:15 · Alex Martemyanov:** Seems logical. -- **16:23:16 · Dominik Kapusta:** Seems logical. It's not a given yet, because it would have consequences in… macOS browser… for App Store. having to stay on WebKit, essentially. -- **16:23:30 · Alex Martemyanov:** Mm-hmm. -- **16:23:30 · Dominik Kapusta:** Because we could ship a browser with… I actually don't know. What I wanted to say is… On iOS App Store, you can't have a browser that's not WebKit-based. with an entitlement to be able to become the system default browser. So if you want your browser to be able to be a system default browser, it needs to be WebKit-based, essentially. So we couldn't… And there are no plans to migrate iOS to Chromium, but for macOS App Store, I don't know. I don't know if it would work. If it's possible. That's something to be… -- **16:24:11 · Alex Martemyanov:** Whoa. -- **16:24:12 · Dominik Kapusta:** Verified. -- **16:24:14 · Alex Martemyanov:** Judging from macOS App Store not having actual Chrome. -- **16:24:18 · Dominik Kapusta:** Yes! -- **16:24:18 · Alex Martemyanov:** Probably not. Yeah. Good point. -- **16:24:20 · Dominik Kapusta:** Yeah, yeah. -- **16:24:22 · Alex Martemyanov:** Yeah, that's all. Such a couple. -- **16:24:26 · Dominik Kapusta:** Because it's not… it's definitely not related to Chrome… Chromium itself, because there are Electron apps in… -- **16:24:26 · Alex Martemyanov:** Okay. -- **16:24:35 · Dominik Kapusta:** App Store, so there are apps that… compile JavaScript, run JavaScript code, uh… In, uh, in App Store. -- **16:24:46 · Alex Martemyanov:** Yeah. -- **16:24:47 · Dominik Kapusta:** Um, so you can ship an engine, yeah, yeah, but for some reason there are no chromium-based browsers there, yeah. -- **16:24:48 · Alex Martemyanov:** Just a browser. -- **16:24:57 · Dominik Kapusta:** Mmhm. -- **16:24:58 · Alex Martemyanov:** Okay. -- **16:25:06 · Dominik Kapusta:** Yeah, but we'll see. It's not for now, like, macOS for now is… -- **16:25:07 · Alex Martemyanov:** Well… -- **16:25:12 · Dominik Kapusta:** focused on extensions. We are going to ship extensions by the end of the year. Technically, the due date is end of November, but I'm not sure if we'll meet it. But, yeah, November, December, anyway. And then we'll see. So we'll probably keep… -- **16:25:33 · Alex Martemyanov:** Okay. -- **16:25:33 · Dominik Kapusta:** doing some things until the Chromium… Fork is out. And then we'll… start thinking about macOS Chromium fork. So, still a few months to go. Yeah. -- **16:25:50 · Alex Martemyanov:** Okay. What the hell does that mean? -- **16:26:05 · Dominik Kapusta:** So, what's the status of your hack days, besides that one tooltip thingy? What about the fire animation? -- **16:26:13 · Alex Martemyanov:** Uh… The fire animation is still there, yes. As I told, it touches the burning logics because it's related to windows opening and closing. There were some issues found. -- **16:26:27 · Dominik Kapusta:** Yeah. Yeah, I commented… I commented about full screen. -- **16:26:31 · Alex Martemyanov:** In the original code, so… -- **16:26:35 · Dominik Kapusta:** I remember that. -- **16:26:35 · Alex Martemyanov:** Uh, I guess full screen is, uh, the smallest of the problems, because I think it's not look it looks nice when this there is full screen during revealing the desktop under. -- **16:26:40 · Dominik Kapusta:** Okay. -- **16:26:49 · Alex Martemyanov:** But, uh… I'm more talking about the data clearing itself that's happening and tied to the window closing, window reopening process. So I I need to come come back to it. Basically, I didn't. Since they have this. -- **16:27:09 · Dominik Kapusta:** Mm-hmm. -- **16:27:11 · Alex Martemyanov:** So it's somewhere in my plan. -- **16:27:15 · Dominik Kapusta:** Sure, sure, sure. All right. All right, that's fine. Yeah. -- **16:27:20 · Alex Martemyanov:** It's a top priority. -- **16:27:24 · Dominik Kapusta:** Yeah, if you could keep pushing it forward on the side, that would be great. -- **16:27:26 · Alex Martemyanov:** Hello? Yeah, there was also this app-wide theming support with the buttons backgrounds and title bar backgrounds. Like this Windows 95 thing. -- **16:27:41 · Dominik Kapusta:** Mmhm. -- **16:27:43 · Alex Martemyanov:** Uh, thank you. I also keep it somewhere, maybe for the next five days to make it more production ready, so we can support a wider amount of themable. -- **16:27:50 · Dominik Kapusta:** Yeah, yeah. Mm-hmm. -- **16:27:56 · Alex Martemyanov:** Areas like changing icons. For the buttons, for backgrounds and titles. -- **16:28:07 · Dominik Kapusta:** Mmm. Hmm. Right. Hmm. So, uh… So, it looks like… Everything is clear, at least with regards to your top priority, it will become more clear after today's call, in a way. And the rest is… Just you following up on your… Like this work. And… Roughly, that's it. -- **16:28:56 · Alex Martemyanov:** Yeah, the good news, I'm… Cleaned up most of my backlog. There are still a lot of like feature flags to be removed and. -- **16:29:07 · Dominik Kapusta:** Yeah, I also have some. -- **16:29:08 · Alex Martemyanov:** It's supposed to be cleaned up. related to CPM mostly. But, yeah, otherwise, uh, the tests… work. So there's 5 tasks in my FTQ. -- **16:29:24 · Dominik Kapusta:** No. -- **16:29:24 · Alex Martemyanov:** Otherwise, it's much better than before. -- **16:29:28 · Dominik Kapusta:** That sounds great. Alright, if nothing more, then we can wrap it up here, because I also don't have much, because last week was… What it was. -- **16:29:37 · Alex Martemyanov:** Yeah, so waiting for the performance review and results. -- **16:29:40 · Dominik Kapusta:** Yeah, the performance review will be back next Tuesday, so we'll talk about it. And that's it for now. -- **16:29:52 · Alex Martemyanov:** Okay, okay. -- **16:29:52 · Dominik Kapusta:** All right, if you need anything, just ping me on Mattermost, happy to chat. And other than that, thank you very much, and see you at the Apple Weekly. -- **16:30:04 · Alex Martemyanov:** Yep. Okay. See you. diff --git a/work/zoom-transcripts/2026-11-03 Michal Smaga's Personal Meeting Room qQ2bzU5KTiCGluiBYA-ROA/transcript.json b/work/zoom-transcripts/2026-11-03 Michal Smaga's Personal Meeting Room qQ2bzU5KTiCGluiBYA-ROA/transcript.json index 25d631bf..c6c5819d 100644 --- a/work/zoom-transcripts/2026-11-03 Michal Smaga's Personal Meeting Room qQ2bzU5KTiCGluiBYA-ROA/transcript.json +++ b/work/zoom-transcripts/2026-11-03 Michal Smaga's Personal Meeting Room qQ2bzU5KTiCGluiBYA-ROA/transcript.json @@ -23,286 +23,6 @@ "time": "15:28:24", "speaker": "Michal Smaga", "text": "Оф, Ол, Юзерс, Райт?" - }, - { - "time": "15:28:26", - "speaker": "Alex Martemyanov", - "text": "Uh, yes, from daily users. So it's still higher than the 1% threshold. And, uh… We've got two fixes more to be released next week. The RR6 reload. which can. Probably cover up to 30% of every 6 total reports. Uh, because it's not… It's not proof that… So usually LR6, when it's happening, it should be recovered normally by the kit. And we are handling some kind of case when it's not recovering. And, uh… The other one is, uh, braid, which may… affect… Yes. The upgrade failures, some hacks caused by it. So speculating on it another like 20 or 30%." - }, - { - "time": "15:29:25", - "speaker": "Michal Smaga", - "text": "So, those two errors are… On my like, in this week's internal. Yeah. So they will be public next week." - }, - { - "time": "15:29:33", - "speaker": "Alex Martemyanov", - "text": "Yes, and those are not the main part of the failures we are getting. So they are expected to have some effect." - }, - { - "time": "15:29:45", - "speaker": "Michal Smaga", - "text": "But not that big, yeah." - }, - { - "time": "15:29:47", - "speaker": "Alex Martemyanov", - "text": "But it won't cross the one-person gap still, I think. Thank you." - }, - { - "time": "15:29:55", - "speaker": "Michal Smaga", - "text": "Yeah, I think, like, probably the main reason is that we have exhausted the options, as you mentioned, like that, like the… The the the idle like thing was not we are not able to reproduce that one. So basically, probably, like…" - }, - { - "time": "15:30:10", - "speaker": "Alex Martemyanov", - "text": "Yeah, so…" - }, - { - "time": "15:30:12", - "speaker": "Michal Smaga", - "text": "Yeah. Okay. My gut feeling would be to just, like, probably provide a summary of the current state of the, like." - }, - { - "time": "15:30:19", - "speaker": "Michal Smaga", - "text": "the reporting have maybe some kind of, like, a dashboard and and probably, like, revisit it next week when we have the numbers for the the last part of the fixes." - }, - { - "time": "15:30:26", - "speaker": "Alex Martemyanov", - "text": "Okay." - }, - { - "time": "15:30:32", - "speaker": "Michal Smaga", - "text": "But probably I wouldn't hold the project any longer, like, for the next week." - }, - { - "time": "15:30:39", - "speaker": "Alex Martemyanov", - "text": "Um… So my suggestion, my thinking of the project for this week. So, first of all, we have this… A lot of feature flags introduced, and the pixels, metrics, and so on, and all of them are basically marked as temporary, and some of them are not, uh… Not even being reported. So there is some cleanup, I guess, to be done. For example, this graveyard fix, we are catching some… percent, lower than one percent, probably, of all the reported events that can match it, but I would not activate it, looking at it, looking at the numbers, so it's… Certainly not the main issue. And there is another one. Um, yeah, anyways, uh, so I was thinking to clean it up. To see… to check the… Safe fixes and remove the picture flags for them. To leave the more controversial, dangerous things behind the feature flags. that we are living. And, uh… Maybe should we remove the recorder thing and episode diagnostics? Maybe not this week, but the week after. Because we are generally… We've collected all the data that it could provide, I guess. And the main portion of it that remains, the neat quake. I think it's generally not covered by it in any sense. And that's…" - }, - { - "time": "15:32:36", - "speaker": "Michal Smaga", - "text": "Yeah…" - }, - { - "time": "15:32:37", - "speaker": "Alex Martemyanov", - "text": "Certainly the main cause." - }, - { - "time": "15:32:38", - "speaker": "Michal Smaga", - "text": "And… And apart from the episodes, the diagnostics, we… We have other pixels to measure the hangs, right? Or they are, like…" - }, - { - "time": "15:32:55", - "speaker": "Alex Martemyanov", - "text": "Currently, there is only this episode thing. We have, uh, the pixels for reports, for user reports, that is separating. And yeah, currently this episode metric only includes like background events, the state of things and. initiating, basically, event." - }, - { - "time": "15:33:17", - "speaker": "Michal Smaga", - "text": "So we would also, like, lose the visibility into the the the, like, the permanent hangs. Right?" - }, - { - "time": "15:33:25", - "speaker": "Alex Martemyanov", - "text": "I'm sorry." - }, - { - "time": "15:33:25", - "speaker": "Michal Smaga", - "text": "Like, the absolute…" - }, - { - "time": "15:33:27", - "speaker": "Alex Martemyanov", - "text": "Actually, I was thinking, maybe not finished planning yet, but I was thinking about redoing the whole reporting thing. Centering it in the gray zone, like, uncovered. Places. So, we have… We have a sequence, like, the content script being injected. sending INIT, WebKit receiving the INIT. In the ground, receiving and handling the event. The config fetching. And… And the website fetching, that may also indicate some kind of… So there is a… Uh, corner case, when the config cannot be fetched. For whatever reason, if it hangs, it would give this kind of symptoms. But… Normally it should not hang. So I would… I'm hesitating to fix it. Um, before we have any data on this. And… Generally, they should not cause permanent headaches. We're done, right? But yeah, currently we are not, uh, tied to the… Extension lifecycle, but we are tied to the page loading lifecycle. And, uh… Also, we don't… we don't have a baseline for the navigations, so we can't tell of which percent of navigation actually have the extension radar, but we are… Diminishing it instead against, like, daily users or installs metrics. So, uh… Still maybe has not. the correct numbers. We don't understand, like, the… the whole picture of it, like how many navigations do actually succeed. And, uh, where exactly… You've got this, uh… Meaning, like, failure, for example. Maybe it is the init, maybe it's somewhere in the WebKit internals, or maybe it's on our side, like waiting for the config fetch or whatever. And that would include the extension modification itself already, the measurement points. And probably some… Thank you. Not episodes, but a summary of, uh… The hung state, so whenever we catch it, when any chain of this, any part of the chain fails, we could report where it has failed." - }, - { - "time": "15:36:18", - "speaker": "Michal Smaga", - "text": "Thanks." - }, - { - "time": "15:36:23", - "speaker": "Alex Martemyanov", - "text": "So I'm thinking, well, maybe we should just, uh… Check this week to implement this metrics. redoing… And uh… then put it on hold, basically, before we receive. I mean, data related." - }, - { - "time": "15:36:41", - "speaker": "Michal Smaga", - "text": "So you suggest, like, doing it for roughly a week, probably, more? Do the cleanup." - }, - { - "time": "15:36:46", - "speaker": "Alex Martemyanov", - "text": "Yeah, so…" - }, - { - "time": "15:36:48", - "speaker": "Michal Smaga", - "text": "Do the cleanup and implement those, like, long term metrics to have some kind of observability in this gray zone." - }, - { - "time": "15:36:55", - "speaker": "Alex Martemyanov", - "text": "Yeah. So, first of all, it should have… some permanent part, I guess, just so we keep it for… For catching the spikes or future breaks. And have some temporary metrics as well, but measuring the inside of the extension. because currently we have the okay. Everything seems fine. Background is loaded in less than 1 s. And then nothing. So and we don't have any idea and anything suspect that can be suspected for causing it." - }, - { - "time": "15:37:25", - "speaker": "Michal Smaga", - "text": "Yeah. Mmhm." - }, - { - "time": "15:37:36", - "speaker": "Alex Martemyanov", - "text": "So yeah, no hypothesis on that. What is actually breaking there? Except for a couple of issues inside the GS, but they are also… Kind of. Hmm. Do not seem so severe and causing this problems. So, that would be my point for today. Otherwise, I have no ideas for you." - }, - { - "time": "15:38:04", - "speaker": "Michal Smaga", - "text": "Yeah, so… Yeah, so I think, like, the point that Russell is having is probably he wants to, like… have a clear understanding where the project will end, yeah, because we can, like, just probably, like, move it, move it, like, chase the, chase the, the, the, the finish line, like, forever." - }, - { - "time": "15:38:20", - "speaker": "Alex Martemyanov", - "text": "Okay." - }, - { - "time": "15:38:27", - "speaker": "Michal Smaga", - "text": "That's going away." - }, - { - "time": "15:38:29", - "speaker": "Alex Martemyanov", - "text": "Well… I would highlight that we certainly have some improvement. We've found some actual bugs. Some of them are not even the case because they are really corner cases, but those are a real issue reproduced." - }, - { - "time": "15:38:44", - "speaker": "Michal Smaga", - "text": "Yeah, I understand, yeah, yeah, so probably no one is questioning that, yeah, but just, like, to have, like, a more… like, condensed or, like, focused, uh, wrap-up for the project, yeah, so I would suggest, like, yeah, I like the plan, and I think it makes sense, yeah, so I would… I would bring the… Uh, yeah, so I think… Two things need to be done, like, one is to do a project update and, like, recap the current data, and summarize, like, where we landed at. And probably, I would start with, uh… with the DRI task, and, like, respond to Russell, and, like… Present the plan that, like, we have those, like, we have those fixes, the updates, and link to the project update, that you have the, like. Two more fixes, like, that will come up in the next version, and you propose the plan to, uh. Uh, have the final week of the project to, like, clean up the, like, all… Unnecessary things and clean up the diagnostics that we set up in place for, like, nailing down the issues. And suggest like to to metrics to like keep track of like where we're at with the permanent hangs and maybe better visibility in what's happening." - }, - { - "time": "15:39:58", - "speaker": "Alex Martemyanov", - "text": "Introduce some permanent. Yep." - }, - { - "time": "15:40:09", - "speaker": "Michal Smaga", - "text": "Yeah, and probably, like, we can see, like, what happens. Yeah, I… probably you want, like, if there's, like, a concrete plan that, like, this is the final week, and we just need to clean up the stuff, I don't think that there should be an issue. That's my feelings." - }, - { - "time": "15:40:27", - "speaker": "Alex Martemyanov", - "text": "Okay, yeah, I'll do it today, then, before the… before the meeting, hopefully." - }, - { - "time": "15:40:36", - "speaker": "Michal Smaga", - "text": "Yeah, and the meetings today are, like, the regular time, yeah." - }, - { - "time": "15:40:40", - "speaker": "Alex Martemyanov", - "text": "I think it's one hour later shifted due to some times on things." - }, - { - "time": "15:40:46", - "speaker": "Michal Smaga", - "text": "Yeah, but I think that…" - }, - { - "time": "15:40:46", - "speaker": "Alex Martemyanov", - "text": "All the meetings, actually." - }, - { - "time": "15:40:52", - "speaker": "Michal Smaga", - "text": "Oh, didn't you have the time zone change for the winter time?" - }, - { - "time": "15:40:55", - "speaker": "Alex Martemyanov", - "text": "No, luckily I don't have time zone change, but unfortunately I do have the Easter." - }, - { - "time": "15:40:57", - "speaker": "Michal Smaga", - "text": "Okay." - }, - { - "time": "15:41:03", - "speaker": "Alex Martemyanov", - "text": "And the western time zones changing and shifting my schedules up to the late night." - }, - { - "time": "15:41:08", - "speaker": "Michal Smaga", - "text": "the… Okay. Uh, yeah, so sounds good. Uh, like, I would ask you to, to, like, do the project update, and, like, provide the, the, the data analysis in some, some task, and, like, respond to us also." - }, - { - "time": "15:41:19", - "speaker": "Alex Martemyanov", - "text": "Mm-hmm." - }, - { - "time": "15:41:24", - "speaker": "Michal Smaga", - "text": "So we have the clear understanding, and we can discuss it on the meeting if he has any." - }, - { - "time": "15:41:28", - "speaker": "Alex Martemyanov", - "text": "Okay, so…" - }, - { - "time": "15:41:29", - "speaker": "Michal Smaga", - "text": "Further questions, but it sounds good to me." - }, - { - "time": "15:41:30", - "speaker": "Alex Martemyanov", - "text": "Probably. Probably the cleanup is, uh… I think, to be done anyways, whether it comes into the project or just as a follow-up, but it would be necessary to do it anyways, and it's not…" - }, - { - "time": "15:41:40", - "speaker": "Michal Smaga", - "text": "Yeah, yeah." - }, - { - "time": "15:41:47", - "speaker": "Alex Martemyanov", - "text": "And it's not small, because there's multiple things in it, and it should be…" - }, - { - "time": "15:41:49", - "speaker": "Michal Smaga", - "text": "Yeah. Yeah, okay." - }, - { - "time": "15:41:53", - "speaker": "Alex Martemyanov", - "text": "Some considerations whether things should be kept or cleaned up or enabled for everybody. So it seems like a natural part for a natural completion part of the project. But yeah, for the metrics. It also seems pretty natural to have some permanent metrics just in case we could detect if anything becomes worse. at some point. Okay, that would be it then. Thanks." - }, - { - "time": "15:42:32", - "speaker": "Michal Smaga", - "text": "Cool. Yeah, that sounds good. Yeah, thank you for the chat." - }, - { - "time": "15:42:40", - "speaker": "Alex Martemyanov", - "text": "Okay, see you, see you later." } ] } diff --git a/work/zoom-transcripts/2026-11-03 Michal Smaga's Personal Meeting Room qQ2bzU5KTiCGluiBYA-ROA/transcript.md b/work/zoom-transcripts/2026-11-03 Michal Smaga's Personal Meeting Room qQ2bzU5KTiCGluiBYA-ROA/transcript.md index fe961a8b..27cf157a 100644 --- a/work/zoom-transcripts/2026-11-03 Michal Smaga's Personal Meeting Room qQ2bzU5KTiCGluiBYA-ROA/transcript.md +++ b/work/zoom-transcripts/2026-11-03 Michal Smaga's Personal Meeting Room qQ2bzU5KTiCGluiBYA-ROA/transcript.md @@ -15,59 +15,3 @@ source: "https://us01mynotes.zoom.us/qQ2bzU5KTiCGluiBYA-ROA" - **15:26:12 · Alex Martemyanov:** So yeah, I wanted to have a sync up on the project. And regarding the Russell's questioning. In the Advisor Sync thread. So whether do we do we wrap up or. Continuing something. Um… So, yeah, basically, at the current state, it seems, from my perspective, that we are. exhausted all the… - **15:26:44 · Alex Martemyanov:** hypothesis that we've got so far. And so there's been some fixes that are genuine and they are working. And, uh, according to the first day data I got today, there is a 30% drop of macOS over-reporting, so that was expected from the. Error page fix the data pollution. So. Currently, they are comparable with iOS and macOS. Uh, yes, locally, not yet in the… The data. So basically, I think we are matching iOS. Uh, roughly. And, uh… So the main numbers are… So for any failure, there is a drop in my voice from around thirty percent to around twenty percent. And, oh, sorry, from 20% to around 15%, so it's a 30% drop. And, uh, so otherwise it's pretty much steady. Uh, since there was no actual fixes, and uh… In permanent hang numbers, macOS had around. 2 to 3%. And now it's around steady. 1.9%. - **15:28:24 · Michal Smaga:** Оф, Ол, Юзерс, Райт? -- **15:28:26 · Alex Martemyanov:** Uh, yes, from daily users. So it's still higher than the 1% threshold. And, uh… We've got two fixes more to be released next week. The RR6 reload. which can. Probably cover up to 30% of every 6 total reports. Uh, because it's not… It's not proof that… So usually LR6, when it's happening, it should be recovered normally by the kit. And we are handling some kind of case when it's not recovering. And, uh… The other one is, uh, braid, which may… affect… Yes. The upgrade failures, some hacks caused by it. So speculating on it another like 20 or 30%. -- **15:29:25 · Michal Smaga:** So, those two errors are… On my like, in this week's internal. Yeah. So they will be public next week. -- **15:29:33 · Alex Martemyanov:** Yes, and those are not the main part of the failures we are getting. So they are expected to have some effect. -- **15:29:45 · Michal Smaga:** But not that big, yeah. -- **15:29:47 · Alex Martemyanov:** But it won't cross the one-person gap still, I think. Thank you. -- **15:29:55 · Michal Smaga:** Yeah, I think, like, probably the main reason is that we have exhausted the options, as you mentioned, like that, like the… The the the idle like thing was not we are not able to reproduce that one. So basically, probably, like… -- **15:30:10 · Alex Martemyanov:** Yeah, so… -- **15:30:12 · Michal Smaga:** Yeah. Okay. My gut feeling would be to just, like, probably provide a summary of the current state of the, like. -- **15:30:19 · Michal Smaga:** the reporting have maybe some kind of, like, a dashboard and and probably, like, revisit it next week when we have the numbers for the the last part of the fixes. -- **15:30:26 · Alex Martemyanov:** Okay. -- **15:30:32 · Michal Smaga:** But probably I wouldn't hold the project any longer, like, for the next week. -- **15:30:39 · Alex Martemyanov:** Um… So my suggestion, my thinking of the project for this week. So, first of all, we have this… A lot of feature flags introduced, and the pixels, metrics, and so on, and all of them are basically marked as temporary, and some of them are not, uh… Not even being reported. So there is some cleanup, I guess, to be done. For example, this graveyard fix, we are catching some… percent, lower than one percent, probably, of all the reported events that can match it, but I would not activate it, looking at it, looking at the numbers, so it's… Certainly not the main issue. And there is another one. Um, yeah, anyways, uh, so I was thinking to clean it up. To see… to check the… Safe fixes and remove the picture flags for them. To leave the more controversial, dangerous things behind the feature flags. that we are living. And, uh… Maybe should we remove the recorder thing and episode diagnostics? Maybe not this week, but the week after. Because we are generally… We've collected all the data that it could provide, I guess. And the main portion of it that remains, the neat quake. I think it's generally not covered by it in any sense. And that's… -- **15:32:36 · Michal Smaga:** Yeah… -- **15:32:37 · Alex Martemyanov:** Certainly the main cause. -- **15:32:38 · Michal Smaga:** And… And apart from the episodes, the diagnostics, we… We have other pixels to measure the hangs, right? Or they are, like… -- **15:32:55 · Alex Martemyanov:** Currently, there is only this episode thing. We have, uh, the pixels for reports, for user reports, that is separating. And yeah, currently this episode metric only includes like background events, the state of things and. initiating, basically, event. -- **15:33:17 · Michal Smaga:** So we would also, like, lose the visibility into the the the, like, the permanent hangs. Right? -- **15:33:25 · Alex Martemyanov:** I'm sorry. -- **15:33:25 · Michal Smaga:** Like, the absolute… -- **15:33:27 · Alex Martemyanov:** Actually, I was thinking, maybe not finished planning yet, but I was thinking about redoing the whole reporting thing. Centering it in the gray zone, like, uncovered. Places. So, we have… We have a sequence, like, the content script being injected. sending INIT, WebKit receiving the INIT. In the ground, receiving and handling the event. The config fetching. And… And the website fetching, that may also indicate some kind of… So there is a… Uh, corner case, when the config cannot be fetched. For whatever reason, if it hangs, it would give this kind of symptoms. But… Normally it should not hang. So I would… I'm hesitating to fix it. Um, before we have any data on this. And… Generally, they should not cause permanent headaches. We're done, right? But yeah, currently we are not, uh, tied to the… Extension lifecycle, but we are tied to the page loading lifecycle. And, uh… Also, we don't… we don't have a baseline for the navigations, so we can't tell of which percent of navigation actually have the extension radar, but we are… Diminishing it instead against, like, daily users or installs metrics. So, uh… Still maybe has not. the correct numbers. We don't understand, like, the… the whole picture of it, like how many navigations do actually succeed. And, uh, where exactly… You've got this, uh… Meaning, like, failure, for example. Maybe it is the init, maybe it's somewhere in the WebKit internals, or maybe it's on our side, like waiting for the config fetch or whatever. And that would include the extension modification itself already, the measurement points. And probably some… Thank you. Not episodes, but a summary of, uh… The hung state, so whenever we catch it, when any chain of this, any part of the chain fails, we could report where it has failed. -- **15:36:18 · Michal Smaga:** Thanks. -- **15:36:23 · Alex Martemyanov:** So I'm thinking, well, maybe we should just, uh… Check this week to implement this metrics. redoing… And uh… then put it on hold, basically, before we receive. I mean, data related. -- **15:36:41 · Michal Smaga:** So you suggest, like, doing it for roughly a week, probably, more? Do the cleanup. -- **15:36:46 · Alex Martemyanov:** Yeah, so… -- **15:36:48 · Michal Smaga:** Do the cleanup and implement those, like, long term metrics to have some kind of observability in this gray zone. -- **15:36:55 · Alex Martemyanov:** Yeah. So, first of all, it should have… some permanent part, I guess, just so we keep it for… For catching the spikes or future breaks. And have some temporary metrics as well, but measuring the inside of the extension. because currently we have the okay. Everything seems fine. Background is loaded in less than 1 s. And then nothing. So and we don't have any idea and anything suspect that can be suspected for causing it. -- **15:37:25 · Michal Smaga:** Yeah. Mmhm. -- **15:37:36 · Alex Martemyanov:** So yeah, no hypothesis on that. What is actually breaking there? Except for a couple of issues inside the GS, but they are also… Kind of. Hmm. Do not seem so severe and causing this problems. So, that would be my point for today. Otherwise, I have no ideas for you. -- **15:38:04 · Michal Smaga:** Yeah, so… Yeah, so I think, like, the point that Russell is having is probably he wants to, like… have a clear understanding where the project will end, yeah, because we can, like, just probably, like, move it, move it, like, chase the, chase the, the, the, the finish line, like, forever. -- **15:38:20 · Alex Martemyanov:** Okay. -- **15:38:27 · Michal Smaga:** That's going away. -- **15:38:29 · Alex Martemyanov:** Well… I would highlight that we certainly have some improvement. We've found some actual bugs. Some of them are not even the case because they are really corner cases, but those are a real issue reproduced. -- **15:38:44 · Michal Smaga:** Yeah, I understand, yeah, yeah, so probably no one is questioning that, yeah, but just, like, to have, like, a more… like, condensed or, like, focused, uh, wrap-up for the project, yeah, so I would suggest, like, yeah, I like the plan, and I think it makes sense, yeah, so I would… I would bring the… Uh, yeah, so I think… Two things need to be done, like, one is to do a project update and, like, recap the current data, and summarize, like, where we landed at. And probably, I would start with, uh… with the DRI task, and, like, respond to Russell, and, like… Present the plan that, like, we have those, like, we have those fixes, the updates, and link to the project update, that you have the, like. Two more fixes, like, that will come up in the next version, and you propose the plan to, uh. Uh, have the final week of the project to, like, clean up the, like, all… Unnecessary things and clean up the diagnostics that we set up in place for, like, nailing down the issues. And suggest like to to metrics to like keep track of like where we're at with the permanent hangs and maybe better visibility in what's happening. -- **15:39:58 · Alex Martemyanov:** Introduce some permanent. Yep. -- **15:40:09 · Michal Smaga:** Yeah, and probably, like, we can see, like, what happens. Yeah, I… probably you want, like, if there's, like, a concrete plan that, like, this is the final week, and we just need to clean up the stuff, I don't think that there should be an issue. That's my feelings. -- **15:40:27 · Alex Martemyanov:** Okay, yeah, I'll do it today, then, before the… before the meeting, hopefully. -- **15:40:36 · Michal Smaga:** Yeah, and the meetings today are, like, the regular time, yeah. -- **15:40:40 · Alex Martemyanov:** I think it's one hour later shifted due to some times on things. -- **15:40:46 · Michal Smaga:** Yeah, but I think that… -- **15:40:46 · Alex Martemyanov:** All the meetings, actually. -- **15:40:52 · Michal Smaga:** Oh, didn't you have the time zone change for the winter time? -- **15:40:55 · Alex Martemyanov:** No, luckily I don't have time zone change, but unfortunately I do have the Easter. -- **15:40:57 · Michal Smaga:** Okay. -- **15:41:03 · Alex Martemyanov:** And the western time zones changing and shifting my schedules up to the late night. -- **15:41:08 · Michal Smaga:** the… Okay. Uh, yeah, so sounds good. Uh, like, I would ask you to, to, like, do the project update, and, like, provide the, the, the data analysis in some, some task, and, like, respond to us also. -- **15:41:19 · Alex Martemyanov:** Mm-hmm. -- **15:41:24 · Michal Smaga:** So we have the clear understanding, and we can discuss it on the meeting if he has any. -- **15:41:28 · Alex Martemyanov:** Okay, so… -- **15:41:29 · Michal Smaga:** Further questions, but it sounds good to me. -- **15:41:30 · Alex Martemyanov:** Probably. Probably the cleanup is, uh… I think, to be done anyways, whether it comes into the project or just as a follow-up, but it would be necessary to do it anyways, and it's not… -- **15:41:40 · Michal Smaga:** Yeah, yeah. -- **15:41:47 · Alex Martemyanov:** And it's not small, because there's multiple things in it, and it should be… -- **15:41:49 · Michal Smaga:** Yeah. Yeah, okay. -- **15:41:53 · Alex Martemyanov:** Some considerations whether things should be kept or cleaned up or enabled for everybody. So it seems like a natural part for a natural completion part of the project. But yeah, for the metrics. It also seems pretty natural to have some permanent metrics just in case we could detect if anything becomes worse. at some point. Okay, that would be it then. Thanks. -- **15:42:32 · Michal Smaga:** Cool. Yeah, that sounds good. Yeah, thank you for the chat. -- **15:42:40 · Alex Martemyanov:** Okay, see you, see you later. 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 27046917..87102478 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,231 +23,6 @@ "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 9022f094..9ff5c167 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,48 +15,3 @@ 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/2026-11-17 Dominik Kapusta's Personal Meeting Room KcmYOq5_SQGPxdkdbhRx9A/transcript.json b/work/zoom-transcripts/2026-11-17 Dominik Kapusta's Personal Meeting Room KcmYOq5_SQGPxdkdbhRx9A/transcript.json index 5cb1a4fe..34670af0 100644 --- a/work/zoom-transcripts/2026-11-17 Dominik Kapusta's Personal Meeting Room KcmYOq5_SQGPxdkdbhRx9A/transcript.json +++ b/work/zoom-transcripts/2026-11-17 Dominik Kapusta's Personal Meeting Room KcmYOq5_SQGPxdkdbhRx9A/transcript.json @@ -23,1251 +23,6 @@ "time": "16:09:31", "speaker": "Alex Martemyanov", "text": "Okay. So for the past week, uh, what was there?" - }, - { - "time": "16:09:38", - "speaker": "Dominik Kapusta", - "text": "To priority." - }, - { - "time": "16:09:40", - "speaker": "Alex Martemyanov", - "text": "Yes, uh, there is, uh, current priorities, uh…" - }, - { - "time": "16:09:41", - "speaker": "Dominik Kapusta", - "text": "Jest." - }, - { - "time": "16:09:45", - "speaker": "Alex Martemyanov", - "text": "to be postmortemed on Thursday, since today's slot is taken. Which is a good thing, I guess, not to go to the late night. There is still some. some discussion going on the extra extension lifecycle matrix to be added as a follow-up to analyze some NGS code. Whether we receive this in it or not. Is it almost before? Probably it's not before, but we need to understand. Exactly where. Anyways, I'm gonna… comment to the project later today. Postmortem is planned for, uh, Thursday slots. And, uh, there was, uh, the metric… I was discussing with Bartek a couple of weeks ago, and I just pushed it forward today, and uh… I've got a scalpel of four. Couple of feature flags removed. Couple of tasks still in this step. One crush, and let… Hopefully to be reviewed today and. And the neutral priority, yes. So I started kinda looking into it. Again, it doesn't seem like something… Precise. To be done, some measurements. Okay, hopefully it won't take too long, just some time-boxed experiments, I guess, and some defined experiments like splitting the CSAs into… Zero parts. Mm-hmm. Yeah, and really hoping the next top priority won't be of… these claims. If you can just… Speak up to… somebody in the objectives that, yeah, I'm seeking for something closer to the browser. Probably… If it can work, because, uh, yeah, the last top priority, I can't say that it was. Great, and I feel great about it. Hmmm." - }, - { - "time": "16:12:25", - "speaker": "Dominik Kapusta", - "text": "Feel great about what exactly? Sorry." - }, - { - "time": "16:12:27", - "speaker": "Alex Martemyanov", - "text": "Yeah, I'm not feeling great about the last top priority I got, the CPM." - }, - { - "time": "16:12:31", - "speaker": "Dominik Kapusta", - "text": "You are not feeling good. Yeah." - }, - { - "time": "16:12:33", - "speaker": "Alex Martemyanov", - "text": "Yeah, I'm really tired of it, and uh… Of life." - }, - { - "time": "16:12:40", - "speaker": "Dominik Kapusta", - "text": "Yeah, I can tell. I can tell, of course. It's not an obvious win, right? This project, which sucks." - }, - { - "time": "16:12:50", - "speaker": "Alex Martemyanov", - "text": "Yeah. Yeah." - }, - { - "time": "16:12:53", - "speaker": "Dominik Kapusta", - "text": "But the… The most important question is, or maybe you have the answer already, or maybe someone gave that answer to you, whether that work you spent on it was… Uh, useful or not useful." - }, - { - "time": "16:13:13", - "speaker": "Alex Martemyanov", - "text": "So, so, I'm sure there's a lot." - }, - { - "time": "16:13:15", - "speaker": "Dominik Kapusta", - "text": "Yeah." - }, - { - "time": "16:13:15", - "speaker": "Alex Martemyanov", - "text": "So there were some bugs fixed, but the main metric." - }, - { - "time": "16:13:17", - "speaker": "Dominik Kapusta", - "text": "Um, okay." - }, - { - "time": "16:13:19", - "speaker": "Alex Martemyanov", - "text": "was not, it didn't reach the target basically defined to lower the numbers below one percent. At least on macOS, it's still above one percent." - }, - { - "time": "16:13:26", - "speaker": "Dominik Kapusta", - "text": "Oh, yeah. Mm-mm. So I guess one other question could be… Could this work be stopped earlier? Just for the post-mortem, because, of course, it happened already, so just for the future… Could you? Could someone, because it's not only you, it's plenty, like, many people in OE, right? being fine with this project running for… As long as it run. So, it looked like… There was hope all the time, or… yeah, we had…" - }, - { - "time": "16:14:07", - "speaker": "Alex Martemyanov", - "text": "Okay. I… for sure it could, uh, probably finish earlier, maybe couple of weeks." - }, - { - "time": "16:14:09", - "speaker": "Dominik Kapusta", - "text": "Some more ideas." - }, - { - "time": "16:14:16", - "speaker": "Alex Martemyanov", - "text": "But I don't know. Not in the fall. Since we got several iterations, like first naive approach, several bugs found, measured, two weeks to the next release, measured again. And, uh… Measurement showing the debugs did not affect, and another iteration of adding metrics. To find something else. So, uh… Of course we could just drop it at some point defining like. Like a trailer or partial. But, uh… Probably the research was kind of genuine, I guess. heading… several hypotheses tested, tried, measured, and. There is still some progress done over the bug fixes. Only maybe just not enough. to to call it successful." - }, - { - "time": "16:15:24", - "speaker": "Dominik Kapusta", - "text": "Right. Um… Is the postmortem happening today?" - }, - { - "time": "16:15:38", - "speaker": "Alex Martemyanov", - "text": "Meeting Thursday." - }, - { - "time": "16:15:39", - "speaker": "Dominik Kapusta", - "text": "Thursday." - }, - { - "time": "16:15:42", - "speaker": "Alex Martemyanov", - "text": "Yeah. Yes. Today, today is Thursday." - }, - { - "time": "16:15:48", - "speaker": "Dominik Kapusta", - "text": "Oh, yeah, yeah, yeah." - }, - { - "time": "16:15:48", - "speaker": "Alex Martemyanov", - "text": "During the slot system." - }, - { - "time": "16:15:51", - "speaker": "Dominik Kapusta", - "text": "Okay, sure, sure, sure. Cool. Yeah, but anyway, and you're moving to OB right now. Which… is great. I think, what do you think about this project?" - }, - { - "time": "16:16:10", - "speaker": "Alex Martemyanov", - "text": "Hmm. Okay. I hope. I'll be still alive when it ends. There will be New Year holidays close. So that should add on it. But, uh, yeah, I can't say that I'm happy about it." - }, - { - "time": "16:16:32", - "speaker": "Dominik Kapusta", - "text": "You're not happy about it." - }, - { - "time": "16:16:33", - "speaker": "Alex Martemyanov", - "text": "Not really." - }, - { - "time": "16:16:36", - "speaker": "Dominik Kapusta", - "text": "Yeah, from my perspective, it's just that it's… It's an important project." - }, - { - "time": "16:16:46", - "speaker": "Alex Martemyanov", - "text": "For sure, for sure, yeah." - }, - { - "time": "16:16:46", - "speaker": "Dominik Kapusta", - "text": "It's something that has many eyes on it right now. So. I'm glad you're working on it. It's not…" - }, - { - "time": "16:16:58", - "speaker": "Alex Martemyanov", - "text": "like… Unfortunately, my, uh…" - }, - { - "time": "16:16:59", - "speaker": "Dominik Kapusta", - "text": "It's…" - }, - { - "time": "16:17:02", - "speaker": "Alex Martemyanov", - "text": "Mm, feeling on it, and, uh, my motivation… is not driven by the importance of the project. Oh, okay." - }, - { - "time": "16:17:11", - "speaker": "Dominik Kapusta", - "text": "Yeah, and that's…" - }, - { - "time": "16:17:14", - "speaker": "Alex Martemyanov", - "text": "It's a pity, but… yeah." - }, - { - "time": "16:17:15", - "speaker": "Dominik Kapusta", - "text": "That's, I mean, that's fair, that's fair, of course. I'm just saying it for context. Because… I know it's hard. Because you have to… You have to endure that. But my hope is that in the long run you could. Even, perhaps… Stay in OB." - }, - { - "time": "16:17:45", - "speaker": "Alex Martemyanov", - "text": "And let's see… let's see how it goes. So, I…" - }, - { - "time": "16:17:47", - "speaker": "Dominik Kapusta", - "text": "I'm… I'm… No." - }, - { - "time": "16:17:51", - "speaker": "Alex Martemyanov", - "text": "Yeah, looking to the project, looking at the project, it's split to some parts, tasks for one or two days. Uh, so hopefully it won't take, uh, too much of… of my energy. to complete it." - }, - { - "time": "16:18:08", - "speaker": "Dominik Kapusta", - "text": "Oh. No." - }, - { - "time": "16:18:09", - "speaker": "Alex Martemyanov", - "text": "At least in the scope to define it right now. So, the kickoff goes to the next week, I guess?" - }, - { - "time": "16:18:23", - "speaker": "Dominik Kapusta", - "text": "Bring the apple slices back." - }, - { - "time": "16:18:28", - "speaker": "Alex Martemyanov", - "text": "Or… When the will be quickly happening." - }, - { - "time": "16:18:32", - "speaker": "Dominik Kapusta", - "text": "I don't know. I don't know." - }, - { - "time": "16:18:35", - "speaker": "Alex Martemyanov", - "text": "November 16 yesterday, on Monday, yeah, so…" - }, - { - "time": "16:18:38", - "speaker": "Dominik Kapusta", - "text": "Okay, Mondays. Mm-hmm." - }, - { - "time": "16:18:43", - "speaker": "Alex Martemyanov", - "text": "Okay, fine. I guess it naturally goes to the next Monday." - }, - { - "time": "16:18:56", - "speaker": "Dominik Kapusta", - "text": "at least… At least this is… kind of… work, where you can… Clearly see the result, at least in the numbers of… The size of, of, of… JavaScript bundle that's loaded into the binary, into the, well, WebView." - }, - { - "time": "16:19:20", - "speaker": "Alex Martemyanov", - "text": "Yeah, I can't say that I'm really good at JavaScript bundles. And all this stuff and how it should work, but yeah, having… probably having LLMs and some good judgment. We can just make a testing strategy and experiment on the memory footprint, and whether the testing website." - }, - { - "time": "16:19:36", - "speaker": "Dominik Kapusta", - "text": "Um… Bye." - }, - { - "time": "16:19:45", - "speaker": "Alex Martemyanov", - "text": "websites work, although I didn't find the exact websites when it fails. But we have the privacy test pages done by Bartosz, so… Hopefully it just works and should be pretty straightforward looking from." - }, - { - "time": "16:19:59", - "speaker": "Dominik Kapusta", - "text": "Yeah." - }, - { - "time": "16:20:04", - "speaker": "Alex Martemyanov", - "text": "from today. But we'll see how it goes." - }, - { - "time": "16:20:07", - "speaker": "Dominik Kapusta", - "text": "So they had some previous work on that, apparently. from… Uh, config, pruning, and uh… Passing config as a JSON string. What is that? Probably not using JSON serialization." - }, - { - "time": "16:20:29", - "speaker": "Alex Martemyanov", - "text": "I guess…" - }, - { - "time": "16:20:33", - "speaker": "Dominik Kapusta", - "text": "Anyway, they were doing some optimizations, and they had some…" - }, - { - "time": "16:20:33", - "speaker": "Alex Martemyanov", - "text": "And then…" - }, - { - "time": "16:20:40", - "speaker": "Dominik Kapusta", - "text": "Some test websites. Some websites to test it on, so that part should be…" - }, - { - "time": "16:20:43", - "speaker": "Alex Martemyanov", - "text": "Mm-hmm." - }, - { - "time": "16:20:48", - "speaker": "Dominik Kapusta", - "text": "resolved, but now I'm wondering… I'm essentially wondering why do they need a native engineer for that, because it sounds like JavaScript work. If they want to have separate bundles for iOS and macOS, they could do it in CSE, just like that, and then just… Rename the files in the native code." - }, - { - "time": "16:21:12", - "speaker": "Alex Martemyanov", - "text": "Well, who cares nowadays?" - }, - { - "time": "16:21:16", - "speaker": "Dominik Kapusta", - "text": "Yeah, of course, I mean, whatever. You could get a project advisor, speak to Dave, I guess, and get a project advisor from the front-end team, maybe? Maybe?" - }, - { - "time": "16:21:17", - "speaker": "Alex Martemyanov", - "text": "Okay. Mmhm." - }, - { - "time": "16:21:27", - "speaker": "Dominik Kapusta", - "text": "Someone who is experienced with CS." - }, - { - "time": "16:21:29", - "speaker": "Alex Martemyanov", - "text": "Yep." - }, - { - "time": "16:21:32", - "speaker": "Dominik Kapusta", - "text": "But also, an alternative is to have someone from the Apple team, and then LLM help, and just reach out, being able to reach out to a front-end person. If needed." - }, - { - "time": "16:21:45", - "speaker": "Alex Martemyanov", - "text": "Okay, I'll just ping Dave, probably, who could…" - }, - { - "time": "16:21:47", - "speaker": "Dominik Kapusta", - "text": "Yeah, I mean…" - }, - { - "time": "16:21:48", - "speaker": "Alex Martemyanov", - "text": "You suggest for… Advising the project." - }, - { - "time": "16:21:57", - "speaker": "Dominik Kapusta", - "text": "Yeah, that's a good idea. Dave would probably be able to." - }, - { - "time": "16:21:59", - "speaker": "Alex Martemyanov", - "text": "Mm-hmm, I'll be back in. Luke." - }, - { - "time": "16:22:02", - "speaker": "Dominik Kapusta", - "text": "So just someone." - }, - { - "time": "16:22:03", - "speaker": "Alex Martemyanov", - "text": "Or is it Thanksgiving?" - }, - { - "time": "16:22:07", - "speaker": "Dominik Kapusta", - "text": "Not yet. Not yet." - }, - { - "time": "16:22:10", - "speaker": "Alex Martemyanov", - "text": "Where is it?" - }, - { - "time": "16:22:12", - "speaker": "Dominik Kapusta", - "text": "I think it's…" - }, - { - "time": "16:22:13", - "speaker": "Alex Martemyanov", - "text": "I'm leaving 2026." - }, - { - "time": "16:22:14", - "speaker": "Dominik Kapusta", - "text": "Beginning… or, yeah, last week of November or first week of December. 26." - }, - { - "time": "16:22:20", - "speaker": "Alex Martemyanov", - "text": "Uh, 26." - }, - { - "time": "16:22:22", - "speaker": "Dominik Kapusta", - "text": "Okay." - }, - { - "time": "16:22:23", - "speaker": "Alex Martemyanov", - "text": "Yeah, okay, it's Thursday. Mmhm." - }, - { - "time": "16:22:34", - "speaker": "Dominik Kapusta", - "text": "Split the iOS bundle from macOS. Make the isolated world mainframe only on Apple." - }, - { - "time": "16:22:50", - "speaker": "Alex Martemyanov", - "text": "Okay, I think Dave in the advisor's task." - }, - { - "time": "16:23:00", - "speaker": "Dominik Kapusta", - "text": "Okay. And drop the unused tracker." - }, - { - "time": "16:23:05", - "speaker": "Alex Martemyanov", - "text": "Yes." - }, - { - "time": "16:23:07", - "speaker": "Dominik Kapusta", - "text": "Try from Apple bundles. Okay. Nice. Sounds… Easy? I don't want to… I don't want to say easy, but… Uh…" - }, - { - "time": "16:23:24", - "speaker": "Alex Martemyanov", - "text": "Yeah, I hope so." - }, - { - "time": "16:23:25", - "speaker": "Dominik Kapusta", - "text": "You'll have a hack phase, and you'll figure out most of the things in the hack phase, hopefully." - }, - { - "time": "16:23:26", - "speaker": "Alex Martemyanov", - "text": "Because…" - }, - { - "time": "16:23:32", - "speaker": "Dominik Kapusta", - "text": "And also, if you're… if everything goes smoothly. You probably will have the entire project implemented during the hack phase. Who knows?" - }, - { - "time": "16:23:42", - "speaker": "Alex Martemyanov", - "text": "Mm-hmm." - }, - { - "time": "16:23:42", - "speaker": "Dominik Kapusta", - "text": "But if there are obstacles, then of course you'll have to… go through them during the project." - }, - { - "time": "16:23:48", - "speaker": "Alex Martemyanov", - "text": "Anyways, there's probably some triages. Reviews, front end team, back and forth and so on." - }, - { - "time": "16:23:53", - "speaker": "Dominik Kapusta", - "text": "Yeah, yeah, yeah. Totally. Maybe tech designs." - }, - { - "time": "16:23:57", - "speaker": "Alex Martemyanov", - "text": "Yeah. For sure." - }, - { - "time": "16:24:01", - "speaker": "Dominik Kapusta", - "text": "Sounds good. It's a bit unclear to me whether we should, um… Whether we should, uh… Have it as… or run… Involve more Apple people or front-end people here. But let's see. Let's see what Dave suggests, first of all." - }, - { - "time": "16:24:24", - "speaker": "Alex Martemyanov", - "text": "Mm-hmm." - }, - { - "time": "16:24:25", - "speaker": "Dominik Kapusta", - "text": "Mm-hmm. And, uh… When do you think you would start working on it? Thursday?" - }, - { - "time": "16:24:34", - "speaker": "Alex Martemyanov", - "text": "Uh, yes, uh, I think tomorrow." - }, - { - "time": "16:24:37", - "speaker": "Dominik Kapusta", - "text": "Tomorrow. Oh, that's cool. Nice." - }, - { - "time": "16:24:38", - "speaker": "Alex Martemyanov", - "text": "Wednesday. Should work, I guess, if nothing strikes." - }, - { - "time": "16:24:52", - "speaker": "Dominik Kapusta", - "text": "Nice, nice. Awesome." - }, - { - "time": "16:24:52", - "speaker": "Alex Martemyanov", - "text": "So there is still one follow up for the current project to analyze metrics. So, I just need… Max and Mihal to you. Uh, to check. Basically, it seems, uh… Hmm… It is in the middle, I guess. And should not be… Too big. So, the pull requests are basically ready, and we should just agree on what we measure, and… Added Grafana board, probably. So it's not… It's not too much." - }, - { - "time": "16:25:29", - "speaker": "Dominik Kapusta", - "text": "Yeah, uh, I see that this task is not added to technical designs?" - }, - { - "time": "16:25:29", - "speaker": "Alex Martemyanov", - "text": "Okay." - }, - { - "time": "16:25:35", - "speaker": "Dominik Kapusta", - "text": "I'm not sure if it's an omission or you meant it that way." - }, - { - "time": "16:25:35", - "speaker": "Alex Martemyanov", - "text": "Hmm… Oh, shit. You're right. per year. Review your remarks. Yeah." - }, - { - "time": "16:25:54", - "speaker": "Dominik Kapusta", - "text": "Awesome." - }, - { - "time": "16:25:56", - "speaker": "Alex Martemyanov", - "text": "Indeed, the extensions. Mm-hmm." - }, - { - "time": "16:26:21", - "speaker": "Dominik Kapusta", - "text": "So setting this project aside and setting your new top priority aside. What are the kinds of things you would like to work on right now?" - }, - { - "time": "16:26:32", - "speaker": "Alex Martemyanov", - "text": "I guess it's mostly, uh… Around my profile, and… I told, uh… Basically, the browser and… There is still some, uh… Things not finished, never finished, like bookmarks, history, and so on. Mm-hmm." - }, - { - "time": "16:26:57", - "speaker": "Dominik Kapusta", - "text": "Okay." - }, - { - "time": "16:26:59", - "speaker": "Alex Martemyanov", - "text": "So…" - }, - { - "time": "16:27:00", - "speaker": "Dominik Kapusta", - "text": "So, essentially, OL…" - }, - { - "time": "16:27:02", - "speaker": "Alex Martemyanov", - "text": "Extension to oil, yeah." - }, - { - "time": "16:27:03", - "speaker": "Dominik Kapusta", - "text": "Type of work. Uh… Got it. That would be great. But the problem with OL right now is that it's tier two, whatever that means. I mean, it means that it's not the greatest impact on the company top priority, but okay. And, uh…" - }, - { - "time": "16:27:25", - "speaker": "Alex Martemyanov", - "text": "I mean, there's alternative options if to consider if we have, for example, if we have, if we ever plan to deliver, like, a browser, Chromium-based browser to Linux, and I could switch to it, for example." - }, - { - "time": "16:27:32", - "speaker": "Dominik Kapusta", - "text": "Mm-hmm. Mm-hmm. Yeah. Yeah." - }, - { - "time": "16:27:40", - "speaker": "Alex Martemyanov", - "text": "Yeah. Just just not to Windows." - }, - { - "time": "16:27:41", - "speaker": "Dominik Kapusta", - "text": "Yeah, yeah, yeah. Of course, yes, yes, yes. It's still a couple months ahead. So let's see, but… it seems to me that there will be push to having… to having a Chromium. Based browser on macOS. and that will be a big project. Of course, Mac OS, yes, and then we will have to migrate everything essentially the entire app to chromium, which is what windows is working on right now." - }, - { - "time": "16:28:06", - "speaker": "Alex Martemyanov", - "text": "Mm-hmm. Marcus? Mmhm. Right, sir." - }, - { - "time": "16:28:17", - "speaker": "Dominik Kapusta", - "text": "And, uh… Yeah, and for that we will need many people. But let's see if it happens in the first place. On Windows, it's happening because Windows browser is shitty. As hell, it's just…" - }, - { - "time": "16:28:33", - "speaker": "Alex Martemyanov", - "text": "Mmhm." - }, - { - "time": "16:28:35", - "speaker": "Dominik Kapusta", - "text": "Crap. So, they are fixing it by… Forking Chromium. Then once they have Chromium, they could… a Chromium fork… We could work on… a Linux client, and macOS client as well. The added value of a Chromium fork… is that suddenly you get all the core browser features for free. Things like tab groups." - }, - { - "time": "16:29:04", - "speaker": "Alex Martemyanov", - "text": "Yeah, basically this was, that's what I was suggesting during my, when I was just hiring, I mean employed." - }, - { - "time": "16:29:05", - "speaker": "Dominik Kapusta", - "text": "Profiles." - }, - { - "time": "16:29:16", - "speaker": "Alex Martemyanov", - "text": "Oh. And, uh, yeah. I do understand since I did some research back then and I was basically proving that the browser needs to be Chromium based. But back then. It was… About policy mostly. But I guess it's a good news. And it's a bit pity that there is some work done that's being trashed." - }, - { - "time": "16:29:54", - "speaker": "Dominik Kapusta", - "text": "Yeah, yeah." - }, - { - "time": "16:29:55", - "speaker": "Alex Martemyanov", - "text": "But anyways." - }, - { - "time": "16:29:56", - "speaker": "Dominik Kapusta", - "text": "I mean, let's see, because I… That's something that we'll need to probably calculate, try to estimate, uh, but… in the long run, I think this sounds good, because otherwise, we have to… we would have to implement. Everything ourselves. And then there's a question of whether to go that way. or not, whether to invest time and people in. Implementing… Tab multi-select, things like that, right? Or…" - }, - { - "time": "16:30:31", - "speaker": "Alex Martemyanov", - "text": "Yeah, I'm…" - }, - { - "time": "16:30:35", - "speaker": "Dominik Kapusta", - "text": "For Chromium, spend… Half a year or more. And have it… just for free, in a sense. So… We'll get there, probably not earlier than spring next year. And, uh, in the mean… because what I'm… Observing right now is… It's looking harder and harder to get buy-in for implementing features. I wanted to add reader mode. and I run a Hackface for the reader mode, and, uh, well, it works. It just needs some more… Integration with whatever we have in the browser right now, like adding these two settings." - }, - { - "time": "16:31:26", - "speaker": "Alex Martemyanov", - "text": "Mm-hmm." - }, - { - "time": "16:31:30", - "speaker": "Dominik Kapusta", - "text": "And I wanted to push it through in the assessment, and I was like, okay, we can have a hack phase. Just 3 days! To use an agent and, like. embed. Reader mode settings in permissions mechanism, because it's… Similar. Uh, and they were like, okay, hug face maybe, and then someone said. that's fine, I understand it's a hack phase, it's just 3 days, but blah blah blah, there's something more important, and let's only do it if we run out of tasks for that. For the assessment, I mean, for the roadmap. So it's still waiting. And it was like it was a couple of days. it's not even… Any kind of a long project. Uh, so if it's going to look like this going forward for everything else, then… Are we even needed here for anything, or what? So, yeah. Let's see." - }, - { - "time": "16:32:36", - "speaker": "Alex Martemyanov", - "text": "Okay, anyways, I think it's a wide move to Chromium. There is, like, WebRTC, there is all the browser site issues solved, basically, for free, because I got my tax payments have to be done in Chrome, because they don't work in LambdaGo." - }, - { - "time": "16:32:37", - "speaker": "Dominik Kapusta", - "text": "Yeah, we… You know. Yeah, yeah, yeah. Yeah, yeah." - }, - { - "time": "16:32:54", - "speaker": "Alex Martemyanov", - "text": "And, yeah, a lot of things, basically." - }, - { - "time": "16:32:59", - "speaker": "Dominik Kapusta", - "text": "Um… Nothing will happen in that area this year, for sure. Probably not in January, but I'll keep monitoring it. The next assessment in OL is in January. shouldn't be… this shouldn't be a topic in January either. Because Windows is not shipped yet. But yeah, let's… I'll keep an eye on that, for sure." - }, - { - "time": "16:33:27", - "speaker": "Alex Martemyanov", - "text": "Yeah." - }, - { - "time": "16:33:28", - "speaker": "Dominik Kapusta", - "text": "And if we get to rewriting the app in Chromium, we will definitely get a bigger team. And we'll have plenty of work, of course." - }, - { - "time": "16:33:37", - "speaker": "Alex Martemyanov", - "text": "Yeah, and that is basically the chance to get to Linux platform, or…" - }, - { - "time": "16:33:38", - "speaker": "Dominik Kapusta", - "text": "So…" - }, - { - "time": "16:33:43", - "speaker": "Alex Martemyanov", - "text": "Almost free, I guess." - }, - { - "time": "16:33:44", - "speaker": "Dominik Kapusta", - "text": "Yeah, yeah." - }, - { - "time": "16:33:45", - "speaker": "Alex Martemyanov", - "text": "And I've seen there was some planning around it being done in Asana somewhere." - }, - { - "time": "16:33:52", - "speaker": "Dominik Kapusta", - "text": "Mm-hmm." - }, - { - "time": "16:33:54", - "speaker": "Alex Martemyanov", - "text": "Mm-hmm. Who knows, maybe I could upgrade my MacBook to the Framework MacBook. Next slide." - }, - { - "time": "16:34:01", - "speaker": "Dominik Kapusta", - "text": "Yeah. Uh… Ah, ah, ah. All right, that's it. On… In other… topics. There was… Oh, but this is not really a macOS thing, but anyway, there was this Bitrise incident over the weekend. They haven't… they…" - }, - { - "time": "16:34:25", - "speaker": "Alex Martemyanov", - "text": "Yeah, I know." - }, - { - "time": "16:34:27", - "speaker": "Dominik Kapusta", - "text": "It's ongoing, it's actually ongoing, Jackie." - }, - { - "time": "16:34:28", - "speaker": "Alex Martemyanov", - "text": "I tried to merge on Saturday to get to the release, because there was late approval on Friday, and yeah." - }, - { - "time": "16:34:32", - "speaker": "Dominik Kapusta", - "text": "Right… And, uh…" - }, - { - "time": "16:34:38", - "speaker": "Alex Martemyanov", - "text": "Been there. There is bankings. Incident, as promised, on 17th of November." - }, - { - "time": "16:34:44", - "speaker": "Dominik Kapusta", - "text": "Mm-hmm. Oh, yeah. Oh." - }, - { - "time": "16:34:48", - "speaker": "Alex Martemyanov", - "text": "So, yeah, should get some cash from base." - }, - { - "time": "16:34:52", - "speaker": "Dominik Kapusta", - "text": "Ha ha ha." - }, - { - "time": "16:34:53", - "speaker": "Alex Martemyanov", - "text": "While I could." - }, - { - "time": "16:34:56", - "speaker": "Dominik Kapusta", - "text": "Interesting." - }, - { - "time": "16:34:57", - "speaker": "Alex Martemyanov", - "text": "And…" - }, - { - "time": "16:34:59", - "speaker": "Dominik Kapusta", - "text": "Yeah. But they had, uh… One, two, three. 3… almost 3 days… 60 something hours of downtime. Or some sort of uses." - }, - { - "time": "16:35:13", - "speaker": "Alex Martemyanov", - "text": "Oh, right, about the priorities and interests. So, basically, I've got some… not some, maybe a lot of plans being done around testing infrastructure, all this stuff that should. That looks mostly like a top priority project, I guess, to set up some older OS runners and prepare this. I guess it would be something I would be interested in, too. If there is some possibility, but since it's kind of objective work." - }, - { - "time": "16:35:46", - "speaker": "Dominik Kapusta", - "text": "Yeah. Okay. Mmhm." - }, - { - "time": "16:35:51", - "speaker": "Alex Martemyanov", - "text": "And… I'm not sure if it could be chosen chosen as a top priority." - }, - { - "time": "16:35:52", - "speaker": "Dominik Kapusta", - "text": "This will have to… Yeah, well, uh… well, yes, if it's scored appropriately." - }, - { - "time": "16:35:57", - "speaker": "Alex Martemyanov", - "text": "Okay." - }, - { - "time": "16:36:01", - "speaker": "Dominik Kapusta", - "text": "and scores highly in the Apple Projects rubric. So, if you have a… If you have some… project-sized work to… to do… The best thing would be to… Scope a project for it. Added to Apple Projects, and… And, uh… And Scott is there. And let's see. If it can be picked up. And then keep linking it in your next TP tasks." - }, - { - "time": "16:36:37", - "speaker": "Alex Martemyanov", - "text": "Mm-hmm. Okay." - }, - { - "time": "16:36:37", - "speaker": "Dominik Kapusta", - "text": "Apart from these, we were talking about a separate Xcode project for UI tests." - }, - { - "time": "16:36:45", - "speaker": "Alex Martemyanov", - "text": "Yes, but, uh… But it didn't move on since then. So basically, um… No worries. What was there? It was not needed. Yeah, I should have commented it. And, uh, so I had some experiments what was needed and what I, uh… What I tried and had some success is basically building all the…" - }, - { - "time": "16:37:16", - "speaker": "Dominik Kapusta", - "text": "Oh, okay." - }, - { - "time": "16:37:20", - "speaker": "Alex Martemyanov", - "text": "all the corners in one run from the project, including the app and the runners, and then just distributing to the tester, to the runners." - }, - { - "time": "16:37:23", - "speaker": "Dominik Kapusta", - "text": "Mm-hmm." - }, - { - "time": "16:37:33", - "speaker": "Alex Martemyanov", - "text": "So there will be only some extra work needed to build the macOS 12 compatibility layer. It's also defined and sitting somewhere in my work trees. So basically, the project can stay as it is, and we don't need since… but we can build all together and just distribute it to every other macOS, and it works." - }, - { - "time": "16:37:55", - "speaker": "Dominik Kapusta", - "text": "But… Is it? Okay. Interesting. But you're build… so what are you building? What would the…" - }, - { - "time": "16:38:06", - "speaker": "Alex Martemyanov", - "text": "the app and the runner, the UI test runner." - }, - { - "time": "16:38:06", - "speaker": "Dominik Kapusta", - "text": "What do we build there? The app and the test run… okay, but the test runner would be a debug build. Like, ad hoc, signed, or unsigned?" - }, - { - "time": "16:38:16", - "speaker": "Alex Martemyanov", - "text": "Maybe. But I think…" - }, - { - "time": "16:38:19", - "speaker": "Dominik Kapusta", - "text": "I'm wondering about code signing and the ability to run this on a different machine." - }, - { - "time": "16:38:23", - "speaker": "Alex Martemyanov", - "text": "I… I remember it did… it used to work, it just worked, but I didn't push it forward since then, so…" - }, - { - "time": "16:38:29", - "speaker": "Dominik Kapusta", - "text": "Okay, I mean, yeah, if it works for you, then that's great. I tried doing something like that some time ago. It was probably different. It was probably different. But it was, ah, it was a different thing. It was a different thing. It was copying derived data to runners." - }, - { - "time": "16:38:58", - "speaker": "Alex Martemyanov", - "text": "Mm-hmm." - }, - { - "time": "16:38:58", - "speaker": "Dominik Kapusta", - "text": "so that it could be reused. But that didn't work." - }, - { - "time": "16:39:02", - "speaker": "Alex Martemyanov", - "text": "Okay." - }, - { - "time": "16:39:08", - "speaker": "Dominik Kapusta", - "text": "Cool. Uh…" - }, - { - "time": "16:39:08", - "speaker": "Alex Martemyanov", - "text": "Sure. Do you have it by your hand, the task?" - }, - { - "time": "16:39:15", - "speaker": "Dominik Kapusta", - "text": "Oh, no, no, no, that was a long time ago, and I didn't have a task for that. That's when I was breaking down UI tests." - }, - { - "time": "16:39:21", - "speaker": "Alex Martemyanov", - "text": "Mm-hmm. No, I mean… The, uh, the one about splitting the project." - }, - { - "time": "16:39:25", - "speaker": "Dominik Kapusta", - "text": "What do you mean?" - }, - { - "time": "16:39:32", - "speaker": "Alex Martemyanov", - "text": "I'm just trying to find it." - }, - { - "time": "16:39:32", - "speaker": "Dominik Kapusta", - "text": "No, I don't think… Well, let's see." - }, - { - "time": "16:39:40", - "speaker": "Alex Martemyanov", - "text": "Thank you. Move, yeah, on it. I'll just probably post an update on it, that it's currently on pause, and uh…" - }, - { - "time": "16:39:50", - "speaker": "Dominik Kapusta", - "text": "Okay. Okay, okay, good." - }, - { - "time": "16:39:53", - "speaker": "Alex Martemyanov", - "text": "And. I don't see her. If it's reasonable to move on with it." - }, - { - "time": "16:40:11", - "speaker": "Dominik Kapusta", - "text": "The next thing we should talk about is the Apple Meetup. We don't have any…" - }, - { - "time": "16:40:15", - "speaker": "Alex Martemyanov", - "text": "Which is not gonna happen in Japan, as I understand." - }, - { - "time": "16:40:19", - "speaker": "Dominik Kapusta", - "text": "Yeah, very unlikely. Well, I don't know anything. I haven't spoken to Jonathan." - }, - { - "time": "16:40:22", - "speaker": "Alex Martemyanov", - "text": "Here." - }, - { - "time": "16:40:27", - "speaker": "Dominik Kapusta", - "text": "And I expect Jonathan to say something about it in today's Apple Weekly. But… Yeah, it's unlikely to be Japan, or… Well, let's see, let's actually see, because… There's this discussion here, if you missed it." - }, - { - "time": "16:40:49", - "speaker": "Alex Martemyanov", - "text": "Yeah, it's, you know, it's…" - }, - { - "time": "16:40:52", - "speaker": "Dominik Kapusta", - "text": "Meetup location guide. Hmm. Places that would work for you. I like Chile, Costa Rica again, Mexico." - }, - { - "time": "16:41:16", - "speaker": "Alex Martemyanov", - "text": "It's Chris Harbour, I guess." - }, - { - "time": "16:41:19", - "speaker": "Dominik Kapusta", - "text": "Mexico is what? Sorry, higher. Mm." - }, - { - "time": "16:41:19", - "speaker": "Alex Martemyanov", - "text": "I've got this. Mexico is maybe problematic." - }, - { - "time": "16:41:24", - "speaker": "Dominik Kapusta", - "text": "Ah, okay." - }, - { - "time": "16:41:26", - "speaker": "Alex Martemyanov", - "text": "Um, not sure. They kinda have, uh… easier visa rules, seemingly easy visa rules, but I've heard there's a lot of rejections just in the airport that they just said, you're not going because of no explanations. So they are." - }, - { - "time": "16:41:41", - "speaker": "Dominik Kapusta", - "text": "Oh, shit. Oh, that sucks." - }, - { - "time": "16:41:46", - "speaker": "Alex Martemyanov", - "text": "experienced some problems with crimes, probably, or some Russia-related stuff, I don't know, but…" - }, - { - "time": "16:41:51", - "speaker": "Dominik Kapusta", - "text": "Mm-hmm." - }, - { - "time": "16:41:56", - "speaker": "Alex Martemyanov", - "text": "There were some issues I've heard of." - }, - { - "time": "16:41:56", - "speaker": "Dominik Kapusta", - "text": "No. Yeah, I am." - }, - { - "time": "16:42:10", - "speaker": "Alex Martemyanov", - "text": "Yeah, it's done, yeah. Still not considered, although it's a really great place from my perspective. Mmm. Broadcasting… Uruguay, probably… And. And, uh… Ireland, Australia, UK, generally. So that's kind of there. But Canada, I don't know, maybe it may work. Speeds. Also may work, but they require extra… Extra movements to…" - }, - { - "time": "16:43:01", - "speaker": "Dominik Kapusta", - "text": "Okay." - }, - { - "time": "16:43:02", - "speaker": "Alex Martemyanov", - "text": "Probably bizarre. And for… yeah, Egypt. Why not?" - }, - { - "time": "16:43:09", - "speaker": "Dominik Kapusta", - "text": "Egypt would be interesting." - }, - { - "time": "16:43:12", - "speaker": "Alex Martemyanov", - "text": "Ah, it's not, it's not, it's not the place. It's the places where…" - }, - { - "time": "16:43:12", - "speaker": "Dominik Kapusta", - "text": "I haven't been there. Not on the list. Ah, okay. Yeah." - }, - { - "time": "16:43:17", - "speaker": "Alex Martemyanov", - "text": "Yeah, our team leaves. Wrong location. Rome, Paris, London, Barcelona, Vienna… Europe, basically." - }, - { - "time": "16:43:30", - "speaker": "Dominik Kapusta", - "text": "Mm-hmm, yeah, yeah." - }, - { - "time": "16:43:32", - "speaker": "Alex Martemyanov", - "text": "I can give it another try, maybe. Who knows? Maybe because… Maybe France. So I've heard people are getting visas to France." - }, - { - "time": "16:43:48", - "speaker": "Dominik Kapusta", - "text": "Yeah, yeah." - }, - { - "time": "16:43:49", - "speaker": "Alex Martemyanov", - "text": "And anyways, you can get a visa for France, and then go to some other… country, or just have a flight to France first, and then move further." - }, - { - "time": "16:43:55", - "speaker": "Dominik Kapusta", - "text": "That's right. That's right." - }, - { - "time": "16:44:03", - "speaker": "Alex Martemyanov", - "text": "Correct, yeah, Spain, Sweden, Belgium, Portugal… It's basically all the… European cities." - }, - { - "time": "16:44:14", - "speaker": "Dominik Kapusta", - "text": "Yeah, I think the first… The first that's not European is, well, New York City and then Playa del Carmen in Mexico." - }, - { - "time": "16:44:26", - "speaker": "Alex Martemyanov", - "text": "Yeah, I guess, uh… New York could work better. But it's harder for me to… to fulfill all the paper paperwork for it." - }, - { - "time": "16:44:37", - "speaker": "Dominik Kapusta", - "text": "Okay, I see. Well." - }, - { - "time": "16:44:39", - "speaker": "Alex Martemyanov", - "text": "So, for Europe, it's just an easy application. I just have to go and apply for… get some bank statements and apply, but it's…" - }, - { - "time": "16:44:45", - "speaker": "Dominik Kapusta", - "text": "Yeah…" - }, - { - "time": "16:44:47", - "speaker": "Alex Martemyanov", - "text": "Would be a third reject in a row, maybe or maybe not." - }, - { - "time": "16:44:50", - "speaker": "Dominik Kapusta", - "text": "Mm-hmm. Oh." - }, - { - "time": "16:44:53", - "speaker": "Alex Martemyanov", - "text": "That's, you know, for New York, it's kind of more complicated. Including the flight." - }, - { - "time": "16:45:01", - "speaker": "Dominik Kapusta", - "text": "You know. I'm really curious what will… come out of it because, yeah, it's interesting. It's just… Sounds… sounds bad that we have to sort of rule you out of every meetup every year, unless we go… To Costa Rica, like, 3 years ago, 2 years ago, uh…" - }, - { - "time": "16:45:35", - "speaker": "Alex Martemyanov", - "text": "Yeah, why not?" - }, - { - "time": "16:45:36", - "speaker": "Dominik Kapusta", - "text": "Why not? Yeah, I mean, we should do it. Let's see. Yeah, let's see, maybe we'll talk about it in the Apple Weekly, hopefully. All right, other than that, so to recap the call, perhaps… Unless… do you have anything else to talk about?" - }, - { - "time": "16:46:06", - "speaker": "Alex Martemyanov", - "text": "And… Well, I guess not." - }, - { - "time": "16:46:09", - "speaker": "Dominik Kapusta", - "text": "Mm-hmm." - }, - { - "time": "16:46:10", - "speaker": "Alex Martemyanov", - "text": "Should be…" - }, - { - "time": "16:46:12", - "speaker": "Dominik Kapusta", - "text": "Yeah, sure, sure, sure. Alright, uh… So… Yeah, so you're moving to OB, but you'll have to… Go through. Uh… And it looks like you have another project scheduled after this one." - }, - { - "time": "16:46:33", - "speaker": "Alex Martemyanov", - "text": "Yeah, the, uh… It seems it's…" - }, - { - "time": "16:46:37", - "speaker": "Dominik Kapusta", - "text": "Stop. Stop." - }, - { - "time": "16:46:37", - "speaker": "Alex Martemyanov", - "text": "consequent projects." - }, - { - "time": "16:46:39", - "speaker": "Dominik Kapusta", - "text": "Stop iOS reload loops after tab memory kills. Which may be interesting… I mean, interesting, as in, uh, maybe straightforward, because we have the… Uh, we have that in macOS. To some extent, in some shape. It's, of course, different, but… At least there's a precedent. But it looks like you'll stick with OB until the end of the year, at least. And, uh… That's that, essentially. Umm. Fine. So if you could update the UI tests thingy, that would be great as well. And that's it, you're wrapping up your project, so…" - }, - { - "time": "16:47:37", - "speaker": "Alex Martemyanov", - "text": "Mmhm." - }, - { - "time": "16:47:38", - "speaker": "Dominik Kapusta", - "text": "Probably not much time to work on AORs. But also, there's nothing burning over there. I mean, there is a burning thing in the CIA UR, and I'll have to rotate all GitHub Action secrets. Should be funny! Okay. Uh, yeah, so we can just… Wrap it up here, let's catch up again next week. And see how OB work is going." - }, - { - "time": "16:48:06", - "speaker": "Alex Martemyanov", - "text": "Okay. Noted. Cool." - }, - { - "time": "16:48:09", - "speaker": "Dominik Kapusta", - "text": "Cool. Yeah, I'll see you at the Apple Weekly. Thanks a lot, Alex. Have a great rest of the day." } ] } diff --git a/work/zoom-transcripts/2026-11-17 Dominik Kapusta's Personal Meeting Room KcmYOq5_SQGPxdkdbhRx9A/transcript.md b/work/zoom-transcripts/2026-11-17 Dominik Kapusta's Personal Meeting Room KcmYOq5_SQGPxdkdbhRx9A/transcript.md index 855079d7..68f2285b 100644 --- a/work/zoom-transcripts/2026-11-17 Dominik Kapusta's Personal Meeting Room KcmYOq5_SQGPxdkdbhRx9A/transcript.md +++ b/work/zoom-transcripts/2026-11-17 Dominik Kapusta's Personal Meeting Room KcmYOq5_SQGPxdkdbhRx9A/transcript.md @@ -15,252 +15,3 @@ source: "https://us01mynotes.zoom.us/KcmYOq5_SQGPxdkdbhRx9A" - **16:09:03 · Alex Martemyanov:** Pretty good. How's it going? That's… that's great. Yeah, probably I'm gonna take one day off next week too, or Monday, or extended weekend. Uh, yeah, just to have some rest from the… Project I'm doing. - **16:09:28 · Dominik Kapusta:** Nie. - **16:09:31 · Alex Martemyanov:** Okay. So for the past week, uh, what was there? -- **16:09:38 · Dominik Kapusta:** To priority. -- **16:09:40 · Alex Martemyanov:** Yes, uh, there is, uh, current priorities, uh… -- **16:09:41 · Dominik Kapusta:** Jest. -- **16:09:45 · Alex Martemyanov:** to be postmortemed on Thursday, since today's slot is taken. Which is a good thing, I guess, not to go to the late night. There is still some. some discussion going on the extra extension lifecycle matrix to be added as a follow-up to analyze some NGS code. Whether we receive this in it or not. Is it almost before? Probably it's not before, but we need to understand. Exactly where. Anyways, I'm gonna… comment to the project later today. Postmortem is planned for, uh, Thursday slots. And, uh, there was, uh, the metric… I was discussing with Bartek a couple of weeks ago, and I just pushed it forward today, and uh… I've got a scalpel of four. Couple of feature flags removed. Couple of tasks still in this step. One crush, and let… Hopefully to be reviewed today and. And the neutral priority, yes. So I started kinda looking into it. Again, it doesn't seem like something… Precise. To be done, some measurements. Okay, hopefully it won't take too long, just some time-boxed experiments, I guess, and some defined experiments like splitting the CSAs into… Zero parts. Mm-hmm. Yeah, and really hoping the next top priority won't be of… these claims. If you can just… Speak up to… somebody in the objectives that, yeah, I'm seeking for something closer to the browser. Probably… If it can work, because, uh, yeah, the last top priority, I can't say that it was. Great, and I feel great about it. Hmmm. -- **16:12:25 · Dominik Kapusta:** Feel great about what exactly? Sorry. -- **16:12:27 · Alex Martemyanov:** Yeah, I'm not feeling great about the last top priority I got, the CPM. -- **16:12:31 · Dominik Kapusta:** You are not feeling good. Yeah. -- **16:12:33 · Alex Martemyanov:** Yeah, I'm really tired of it, and uh… Of life. -- **16:12:40 · Dominik Kapusta:** Yeah, I can tell. I can tell, of course. It's not an obvious win, right? This project, which sucks. -- **16:12:50 · Alex Martemyanov:** Yeah. Yeah. -- **16:12:53 · Dominik Kapusta:** But the… The most important question is, or maybe you have the answer already, or maybe someone gave that answer to you, whether that work you spent on it was… Uh, useful or not useful. -- **16:13:13 · Alex Martemyanov:** So, so, I'm sure there's a lot. -- **16:13:15 · Dominik Kapusta:** Yeah. -- **16:13:15 · Alex Martemyanov:** So there were some bugs fixed, but the main metric. -- **16:13:17 · Dominik Kapusta:** Um, okay. -- **16:13:19 · Alex Martemyanov:** was not, it didn't reach the target basically defined to lower the numbers below one percent. At least on macOS, it's still above one percent. -- **16:13:26 · Dominik Kapusta:** Oh, yeah. Mm-mm. So I guess one other question could be… Could this work be stopped earlier? Just for the post-mortem, because, of course, it happened already, so just for the future… Could you? Could someone, because it's not only you, it's plenty, like, many people in OE, right? being fine with this project running for… As long as it run. So, it looked like… There was hope all the time, or… yeah, we had… -- **16:14:07 · Alex Martemyanov:** Okay. I… for sure it could, uh, probably finish earlier, maybe couple of weeks. -- **16:14:09 · Dominik Kapusta:** Some more ideas. -- **16:14:16 · Alex Martemyanov:** But I don't know. Not in the fall. Since we got several iterations, like first naive approach, several bugs found, measured, two weeks to the next release, measured again. And, uh… Measurement showing the debugs did not affect, and another iteration of adding metrics. To find something else. So, uh… Of course we could just drop it at some point defining like. Like a trailer or partial. But, uh… Probably the research was kind of genuine, I guess. heading… several hypotheses tested, tried, measured, and. There is still some progress done over the bug fixes. Only maybe just not enough. to to call it successful. -- **16:15:24 · Dominik Kapusta:** Right. Um… Is the postmortem happening today? -- **16:15:38 · Alex Martemyanov:** Meeting Thursday. -- **16:15:39 · Dominik Kapusta:** Thursday. -- **16:15:42 · Alex Martemyanov:** Yeah. Yes. Today, today is Thursday. -- **16:15:48 · Dominik Kapusta:** Oh, yeah, yeah, yeah. -- **16:15:48 · Alex Martemyanov:** During the slot system. -- **16:15:51 · Dominik Kapusta:** Okay, sure, sure, sure. Cool. Yeah, but anyway, and you're moving to OB right now. Which… is great. I think, what do you think about this project? -- **16:16:10 · Alex Martemyanov:** Hmm. Okay. I hope. I'll be still alive when it ends. There will be New Year holidays close. So that should add on it. But, uh, yeah, I can't say that I'm happy about it. -- **16:16:32 · Dominik Kapusta:** You're not happy about it. -- **16:16:33 · Alex Martemyanov:** Not really. -- **16:16:36 · Dominik Kapusta:** Yeah, from my perspective, it's just that it's… It's an important project. -- **16:16:46 · Alex Martemyanov:** For sure, for sure, yeah. -- **16:16:46 · Dominik Kapusta:** It's something that has many eyes on it right now. So. I'm glad you're working on it. It's not… -- **16:16:58 · Alex Martemyanov:** like… Unfortunately, my, uh… -- **16:16:59 · Dominik Kapusta:** It's… -- **16:17:02 · Alex Martemyanov:** Mm, feeling on it, and, uh, my motivation… is not driven by the importance of the project. Oh, okay. -- **16:17:11 · Dominik Kapusta:** Yeah, and that's… -- **16:17:14 · Alex Martemyanov:** It's a pity, but… yeah. -- **16:17:15 · Dominik Kapusta:** That's, I mean, that's fair, that's fair, of course. I'm just saying it for context. Because… I know it's hard. Because you have to… You have to endure that. But my hope is that in the long run you could. Even, perhaps… Stay in OB. -- **16:17:45 · Alex Martemyanov:** And let's see… let's see how it goes. So, I… -- **16:17:47 · Dominik Kapusta:** I'm… I'm… No. -- **16:17:51 · Alex Martemyanov:** Yeah, looking to the project, looking at the project, it's split to some parts, tasks for one or two days. Uh, so hopefully it won't take, uh, too much of… of my energy. to complete it. -- **16:18:08 · Dominik Kapusta:** Oh. No. -- **16:18:09 · Alex Martemyanov:** At least in the scope to define it right now. So, the kickoff goes to the next week, I guess? -- **16:18:23 · Dominik Kapusta:** Bring the apple slices back. -- **16:18:28 · Alex Martemyanov:** Or… When the will be quickly happening. -- **16:18:32 · Dominik Kapusta:** I don't know. I don't know. -- **16:18:35 · Alex Martemyanov:** November 16 yesterday, on Monday, yeah, so… -- **16:18:38 · Dominik Kapusta:** Okay, Mondays. Mm-hmm. -- **16:18:43 · Alex Martemyanov:** Okay, fine. I guess it naturally goes to the next Monday. -- **16:18:56 · Dominik Kapusta:** at least… At least this is… kind of… work, where you can… Clearly see the result, at least in the numbers of… The size of, of, of… JavaScript bundle that's loaded into the binary, into the, well, WebView. -- **16:19:20 · Alex Martemyanov:** Yeah, I can't say that I'm really good at JavaScript bundles. And all this stuff and how it should work, but yeah, having… probably having LLMs and some good judgment. We can just make a testing strategy and experiment on the memory footprint, and whether the testing website. -- **16:19:36 · Dominik Kapusta:** Um… Bye. -- **16:19:45 · Alex Martemyanov:** websites work, although I didn't find the exact websites when it fails. But we have the privacy test pages done by Bartosz, so… Hopefully it just works and should be pretty straightforward looking from. -- **16:19:59 · Dominik Kapusta:** Yeah. -- **16:20:04 · Alex Martemyanov:** from today. But we'll see how it goes. -- **16:20:07 · Dominik Kapusta:** So they had some previous work on that, apparently. from… Uh, config, pruning, and uh… Passing config as a JSON string. What is that? Probably not using JSON serialization. -- **16:20:29 · Alex Martemyanov:** I guess… -- **16:20:33 · Dominik Kapusta:** Anyway, they were doing some optimizations, and they had some… -- **16:20:33 · Alex Martemyanov:** And then… -- **16:20:40 · Dominik Kapusta:** Some test websites. Some websites to test it on, so that part should be… -- **16:20:43 · Alex Martemyanov:** Mm-hmm. -- **16:20:48 · Dominik Kapusta:** resolved, but now I'm wondering… I'm essentially wondering why do they need a native engineer for that, because it sounds like JavaScript work. If they want to have separate bundles for iOS and macOS, they could do it in CSE, just like that, and then just… Rename the files in the native code. -- **16:21:12 · Alex Martemyanov:** Well, who cares nowadays? -- **16:21:16 · Dominik Kapusta:** Yeah, of course, I mean, whatever. You could get a project advisor, speak to Dave, I guess, and get a project advisor from the front-end team, maybe? Maybe? -- **16:21:17 · Alex Martemyanov:** Okay. Mmhm. -- **16:21:27 · Dominik Kapusta:** Someone who is experienced with CS. -- **16:21:29 · Alex Martemyanov:** Yep. -- **16:21:32 · Dominik Kapusta:** But also, an alternative is to have someone from the Apple team, and then LLM help, and just reach out, being able to reach out to a front-end person. If needed. -- **16:21:45 · Alex Martemyanov:** Okay, I'll just ping Dave, probably, who could… -- **16:21:47 · Dominik Kapusta:** Yeah, I mean… -- **16:21:48 · Alex Martemyanov:** You suggest for… Advising the project. -- **16:21:57 · Dominik Kapusta:** Yeah, that's a good idea. Dave would probably be able to. -- **16:21:59 · Alex Martemyanov:** Mm-hmm, I'll be back in. Luke. -- **16:22:02 · Dominik Kapusta:** So just someone. -- **16:22:03 · Alex Martemyanov:** Or is it Thanksgiving? -- **16:22:07 · Dominik Kapusta:** Not yet. Not yet. -- **16:22:10 · Alex Martemyanov:** Where is it? -- **16:22:12 · Dominik Kapusta:** I think it's… -- **16:22:13 · Alex Martemyanov:** I'm leaving 2026. -- **16:22:14 · Dominik Kapusta:** Beginning… or, yeah, last week of November or first week of December. 26. -- **16:22:20 · Alex Martemyanov:** Uh, 26. -- **16:22:22 · Dominik Kapusta:** Okay. -- **16:22:23 · Alex Martemyanov:** Yeah, okay, it's Thursday. Mmhm. -- **16:22:34 · Dominik Kapusta:** Split the iOS bundle from macOS. Make the isolated world mainframe only on Apple. -- **16:22:50 · Alex Martemyanov:** Okay, I think Dave in the advisor's task. -- **16:23:00 · Dominik Kapusta:** Okay. And drop the unused tracker. -- **16:23:05 · Alex Martemyanov:** Yes. -- **16:23:07 · Dominik Kapusta:** Try from Apple bundles. Okay. Nice. Sounds… Easy? I don't want to… I don't want to say easy, but… Uh… -- **16:23:24 · Alex Martemyanov:** Yeah, I hope so. -- **16:23:25 · Dominik Kapusta:** You'll have a hack phase, and you'll figure out most of the things in the hack phase, hopefully. -- **16:23:26 · Alex Martemyanov:** Because… -- **16:23:32 · Dominik Kapusta:** And also, if you're… if everything goes smoothly. You probably will have the entire project implemented during the hack phase. Who knows? -- **16:23:42 · Alex Martemyanov:** Mm-hmm. -- **16:23:42 · Dominik Kapusta:** But if there are obstacles, then of course you'll have to… go through them during the project. -- **16:23:48 · Alex Martemyanov:** Anyways, there's probably some triages. Reviews, front end team, back and forth and so on. -- **16:23:53 · Dominik Kapusta:** Yeah, yeah, yeah. Totally. Maybe tech designs. -- **16:23:57 · Alex Martemyanov:** Yeah. For sure. -- **16:24:01 · Dominik Kapusta:** Sounds good. It's a bit unclear to me whether we should, um… Whether we should, uh… Have it as… or run… Involve more Apple people or front-end people here. But let's see. Let's see what Dave suggests, first of all. -- **16:24:24 · Alex Martemyanov:** Mm-hmm. -- **16:24:25 · Dominik Kapusta:** Mm-hmm. And, uh… When do you think you would start working on it? Thursday? -- **16:24:34 · Alex Martemyanov:** Uh, yes, uh, I think tomorrow. -- **16:24:37 · Dominik Kapusta:** Tomorrow. Oh, that's cool. Nice. -- **16:24:38 · Alex Martemyanov:** Wednesday. Should work, I guess, if nothing strikes. -- **16:24:52 · Dominik Kapusta:** Nice, nice. Awesome. -- **16:24:52 · Alex Martemyanov:** So there is still one follow up for the current project to analyze metrics. So, I just need… Max and Mihal to you. Uh, to check. Basically, it seems, uh… Hmm… It is in the middle, I guess. And should not be… Too big. So, the pull requests are basically ready, and we should just agree on what we measure, and… Added Grafana board, probably. So it's not… It's not too much. -- **16:25:29 · Dominik Kapusta:** Yeah, uh, I see that this task is not added to technical designs? -- **16:25:29 · Alex Martemyanov:** Okay. -- **16:25:35 · Dominik Kapusta:** I'm not sure if it's an omission or you meant it that way. -- **16:25:35 · Alex Martemyanov:** Hmm… Oh, shit. You're right. per year. Review your remarks. Yeah. -- **16:25:54 · Dominik Kapusta:** Awesome. -- **16:25:56 · Alex Martemyanov:** Indeed, the extensions. Mm-hmm. -- **16:26:21 · Dominik Kapusta:** So setting this project aside and setting your new top priority aside. What are the kinds of things you would like to work on right now? -- **16:26:32 · Alex Martemyanov:** I guess it's mostly, uh… Around my profile, and… I told, uh… Basically, the browser and… There is still some, uh… Things not finished, never finished, like bookmarks, history, and so on. Mm-hmm. -- **16:26:57 · Dominik Kapusta:** Okay. -- **16:26:59 · Alex Martemyanov:** So… -- **16:27:00 · Dominik Kapusta:** So, essentially, OL… -- **16:27:02 · Alex Martemyanov:** Extension to oil, yeah. -- **16:27:03 · Dominik Kapusta:** Type of work. Uh… Got it. That would be great. But the problem with OL right now is that it's tier two, whatever that means. I mean, it means that it's not the greatest impact on the company top priority, but okay. And, uh… -- **16:27:25 · Alex Martemyanov:** I mean, there's alternative options if to consider if we have, for example, if we have, if we ever plan to deliver, like, a browser, Chromium-based browser to Linux, and I could switch to it, for example. -- **16:27:32 · Dominik Kapusta:** Mm-hmm. Mm-hmm. Yeah. Yeah. -- **16:27:40 · Alex Martemyanov:** Yeah. Just just not to Windows. -- **16:27:41 · Dominik Kapusta:** Yeah, yeah, yeah. Of course, yes, yes, yes. It's still a couple months ahead. So let's see, but… it seems to me that there will be push to having… to having a Chromium. Based browser on macOS. and that will be a big project. Of course, Mac OS, yes, and then we will have to migrate everything essentially the entire app to chromium, which is what windows is working on right now. -- **16:28:06 · Alex Martemyanov:** Mm-hmm. Marcus? Mmhm. Right, sir. -- **16:28:17 · Dominik Kapusta:** And, uh… Yeah, and for that we will need many people. But let's see if it happens in the first place. On Windows, it's happening because Windows browser is shitty. As hell, it's just… -- **16:28:33 · Alex Martemyanov:** Mmhm. -- **16:28:35 · Dominik Kapusta:** Crap. So, they are fixing it by… Forking Chromium. Then once they have Chromium, they could… a Chromium fork… We could work on… a Linux client, and macOS client as well. The added value of a Chromium fork… is that suddenly you get all the core browser features for free. Things like tab groups. -- **16:29:04 · Alex Martemyanov:** Yeah, basically this was, that's what I was suggesting during my, when I was just hiring, I mean employed. -- **16:29:05 · Dominik Kapusta:** Profiles. -- **16:29:16 · Alex Martemyanov:** Oh. And, uh, yeah. I do understand since I did some research back then and I was basically proving that the browser needs to be Chromium based. But back then. It was… About policy mostly. But I guess it's a good news. And it's a bit pity that there is some work done that's being trashed. -- **16:29:54 · Dominik Kapusta:** Yeah, yeah. -- **16:29:55 · Alex Martemyanov:** But anyways. -- **16:29:56 · Dominik Kapusta:** I mean, let's see, because I… That's something that we'll need to probably calculate, try to estimate, uh, but… in the long run, I think this sounds good, because otherwise, we have to… we would have to implement. Everything ourselves. And then there's a question of whether to go that way. or not, whether to invest time and people in. Implementing… Tab multi-select, things like that, right? Or… -- **16:30:31 · Alex Martemyanov:** Yeah, I'm… -- **16:30:35 · Dominik Kapusta:** For Chromium, spend… Half a year or more. And have it… just for free, in a sense. So… We'll get there, probably not earlier than spring next year. And, uh, in the mean… because what I'm… Observing right now is… It's looking harder and harder to get buy-in for implementing features. I wanted to add reader mode. and I run a Hackface for the reader mode, and, uh, well, it works. It just needs some more… Integration with whatever we have in the browser right now, like adding these two settings. -- **16:31:26 · Alex Martemyanov:** Mm-hmm. -- **16:31:30 · Dominik Kapusta:** And I wanted to push it through in the assessment, and I was like, okay, we can have a hack phase. Just 3 days! To use an agent and, like. embed. Reader mode settings in permissions mechanism, because it's… Similar. Uh, and they were like, okay, hug face maybe, and then someone said. that's fine, I understand it's a hack phase, it's just 3 days, but blah blah blah, there's something more important, and let's only do it if we run out of tasks for that. For the assessment, I mean, for the roadmap. So it's still waiting. And it was like it was a couple of days. it's not even… Any kind of a long project. Uh, so if it's going to look like this going forward for everything else, then… Are we even needed here for anything, or what? So, yeah. Let's see. -- **16:32:36 · Alex Martemyanov:** Okay, anyways, I think it's a wide move to Chromium. There is, like, WebRTC, there is all the browser site issues solved, basically, for free, because I got my tax payments have to be done in Chrome, because they don't work in LambdaGo. -- **16:32:37 · Dominik Kapusta:** Yeah, we… You know. Yeah, yeah, yeah. Yeah, yeah. -- **16:32:54 · Alex Martemyanov:** And, yeah, a lot of things, basically. -- **16:32:59 · Dominik Kapusta:** Um… Nothing will happen in that area this year, for sure. Probably not in January, but I'll keep monitoring it. The next assessment in OL is in January. shouldn't be… this shouldn't be a topic in January either. Because Windows is not shipped yet. But yeah, let's… I'll keep an eye on that, for sure. -- **16:33:27 · Alex Martemyanov:** Yeah. -- **16:33:28 · Dominik Kapusta:** And if we get to rewriting the app in Chromium, we will definitely get a bigger team. And we'll have plenty of work, of course. -- **16:33:37 · Alex Martemyanov:** Yeah, and that is basically the chance to get to Linux platform, or… -- **16:33:38 · Dominik Kapusta:** So… -- **16:33:43 · Alex Martemyanov:** Almost free, I guess. -- **16:33:44 · Dominik Kapusta:** Yeah, yeah. -- **16:33:45 · Alex Martemyanov:** And I've seen there was some planning around it being done in Asana somewhere. -- **16:33:52 · Dominik Kapusta:** Mm-hmm. -- **16:33:54 · Alex Martemyanov:** Mm-hmm. Who knows, maybe I could upgrade my MacBook to the Framework MacBook. Next slide. -- **16:34:01 · Dominik Kapusta:** Yeah. Uh… Ah, ah, ah. All right, that's it. On… In other… topics. There was… Oh, but this is not really a macOS thing, but anyway, there was this Bitrise incident over the weekend. They haven't… they… -- **16:34:25 · Alex Martemyanov:** Yeah, I know. -- **16:34:27 · Dominik Kapusta:** It's ongoing, it's actually ongoing, Jackie. -- **16:34:28 · Alex Martemyanov:** I tried to merge on Saturday to get to the release, because there was late approval on Friday, and yeah. -- **16:34:32 · Dominik Kapusta:** Right… And, uh… -- **16:34:38 · Alex Martemyanov:** Been there. There is bankings. Incident, as promised, on 17th of November. -- **16:34:44 · Dominik Kapusta:** Mm-hmm. Oh, yeah. Oh. -- **16:34:48 · Alex Martemyanov:** So, yeah, should get some cash from base. -- **16:34:52 · Dominik Kapusta:** Ha ha ha. -- **16:34:53 · Alex Martemyanov:** While I could. -- **16:34:56 · Dominik Kapusta:** Interesting. -- **16:34:57 · Alex Martemyanov:** And… -- **16:34:59 · Dominik Kapusta:** Yeah. But they had, uh… One, two, three. 3… almost 3 days… 60 something hours of downtime. Or some sort of uses. -- **16:35:13 · Alex Martemyanov:** Oh, right, about the priorities and interests. So, basically, I've got some… not some, maybe a lot of plans being done around testing infrastructure, all this stuff that should. That looks mostly like a top priority project, I guess, to set up some older OS runners and prepare this. I guess it would be something I would be interested in, too. If there is some possibility, but since it's kind of objective work. -- **16:35:46 · Dominik Kapusta:** Yeah. Okay. Mmhm. -- **16:35:51 · Alex Martemyanov:** And… I'm not sure if it could be chosen chosen as a top priority. -- **16:35:52 · Dominik Kapusta:** This will have to… Yeah, well, uh… well, yes, if it's scored appropriately. -- **16:35:57 · Alex Martemyanov:** Okay. -- **16:36:01 · Dominik Kapusta:** and scores highly in the Apple Projects rubric. So, if you have a… If you have some… project-sized work to… to do… The best thing would be to… Scope a project for it. Added to Apple Projects, and… And, uh… And Scott is there. And let's see. If it can be picked up. And then keep linking it in your next TP tasks. -- **16:36:37 · Alex Martemyanov:** Mm-hmm. Okay. -- **16:36:37 · Dominik Kapusta:** Apart from these, we were talking about a separate Xcode project for UI tests. -- **16:36:45 · Alex Martemyanov:** Yes, but, uh… But it didn't move on since then. So basically, um… No worries. What was there? It was not needed. Yeah, I should have commented it. And, uh, so I had some experiments what was needed and what I, uh… What I tried and had some success is basically building all the… -- **16:37:16 · Dominik Kapusta:** Oh, okay. -- **16:37:20 · Alex Martemyanov:** all the corners in one run from the project, including the app and the runners, and then just distributing to the tester, to the runners. -- **16:37:23 · Dominik Kapusta:** Mm-hmm. -- **16:37:33 · Alex Martemyanov:** So there will be only some extra work needed to build the macOS 12 compatibility layer. It's also defined and sitting somewhere in my work trees. So basically, the project can stay as it is, and we don't need since… but we can build all together and just distribute it to every other macOS, and it works. -- **16:37:55 · Dominik Kapusta:** But… Is it? Okay. Interesting. But you're build… so what are you building? What would the… -- **16:38:06 · Alex Martemyanov:** the app and the runner, the UI test runner. -- **16:38:06 · Dominik Kapusta:** What do we build there? The app and the test run… okay, but the test runner would be a debug build. Like, ad hoc, signed, or unsigned? -- **16:38:16 · Alex Martemyanov:** Maybe. But I think… -- **16:38:19 · Dominik Kapusta:** I'm wondering about code signing and the ability to run this on a different machine. -- **16:38:23 · Alex Martemyanov:** I… I remember it did… it used to work, it just worked, but I didn't push it forward since then, so… -- **16:38:29 · Dominik Kapusta:** Okay, I mean, yeah, if it works for you, then that's great. I tried doing something like that some time ago. It was probably different. It was probably different. But it was, ah, it was a different thing. It was a different thing. It was copying derived data to runners. -- **16:38:58 · Alex Martemyanov:** Mm-hmm. -- **16:38:58 · Dominik Kapusta:** so that it could be reused. But that didn't work. -- **16:39:02 · Alex Martemyanov:** Okay. -- **16:39:08 · Dominik Kapusta:** Cool. Uh… -- **16:39:08 · Alex Martemyanov:** Sure. Do you have it by your hand, the task? -- **16:39:15 · Dominik Kapusta:** Oh, no, no, no, that was a long time ago, and I didn't have a task for that. That's when I was breaking down UI tests. -- **16:39:21 · Alex Martemyanov:** Mm-hmm. No, I mean… The, uh, the one about splitting the project. -- **16:39:25 · Dominik Kapusta:** What do you mean? -- **16:39:32 · Alex Martemyanov:** I'm just trying to find it. -- **16:39:32 · Dominik Kapusta:** No, I don't think… Well, let's see. -- **16:39:40 · Alex Martemyanov:** Thank you. Move, yeah, on it. I'll just probably post an update on it, that it's currently on pause, and uh… -- **16:39:50 · Dominik Kapusta:** Okay. Okay, okay, good. -- **16:39:53 · Alex Martemyanov:** And. I don't see her. If it's reasonable to move on with it. -- **16:40:11 · Dominik Kapusta:** The next thing we should talk about is the Apple Meetup. We don't have any… -- **16:40:15 · Alex Martemyanov:** Which is not gonna happen in Japan, as I understand. -- **16:40:19 · Dominik Kapusta:** Yeah, very unlikely. Well, I don't know anything. I haven't spoken to Jonathan. -- **16:40:22 · Alex Martemyanov:** Here. -- **16:40:27 · Dominik Kapusta:** And I expect Jonathan to say something about it in today's Apple Weekly. But… Yeah, it's unlikely to be Japan, or… Well, let's see, let's actually see, because… There's this discussion here, if you missed it. -- **16:40:49 · Alex Martemyanov:** Yeah, it's, you know, it's… -- **16:40:52 · Dominik Kapusta:** Meetup location guide. Hmm. Places that would work for you. I like Chile, Costa Rica again, Mexico. -- **16:41:16 · Alex Martemyanov:** It's Chris Harbour, I guess. -- **16:41:19 · Dominik Kapusta:** Mexico is what? Sorry, higher. Mm. -- **16:41:19 · Alex Martemyanov:** I've got this. Mexico is maybe problematic. -- **16:41:24 · Dominik Kapusta:** Ah, okay. -- **16:41:26 · Alex Martemyanov:** Um, not sure. They kinda have, uh… easier visa rules, seemingly easy visa rules, but I've heard there's a lot of rejections just in the airport that they just said, you're not going because of no explanations. So they are. -- **16:41:41 · Dominik Kapusta:** Oh, shit. Oh, that sucks. -- **16:41:46 · Alex Martemyanov:** experienced some problems with crimes, probably, or some Russia-related stuff, I don't know, but… -- **16:41:51 · Dominik Kapusta:** Mm-hmm. -- **16:41:56 · Alex Martemyanov:** There were some issues I've heard of. -- **16:41:56 · Dominik Kapusta:** No. Yeah, I am. -- **16:42:10 · Alex Martemyanov:** Yeah, it's done, yeah. Still not considered, although it's a really great place from my perspective. Mmm. Broadcasting… Uruguay, probably… And. And, uh… Ireland, Australia, UK, generally. So that's kind of there. But Canada, I don't know, maybe it may work. Speeds. Also may work, but they require extra… Extra movements to… -- **16:43:01 · Dominik Kapusta:** Okay. -- **16:43:02 · Alex Martemyanov:** Probably bizarre. And for… yeah, Egypt. Why not? -- **16:43:09 · Dominik Kapusta:** Egypt would be interesting. -- **16:43:12 · Alex Martemyanov:** Ah, it's not, it's not, it's not the place. It's the places where… -- **16:43:12 · Dominik Kapusta:** I haven't been there. Not on the list. Ah, okay. Yeah. -- **16:43:17 · Alex Martemyanov:** Yeah, our team leaves. Wrong location. Rome, Paris, London, Barcelona, Vienna… Europe, basically. -- **16:43:30 · Dominik Kapusta:** Mm-hmm, yeah, yeah. -- **16:43:32 · Alex Martemyanov:** I can give it another try, maybe. Who knows? Maybe because… Maybe France. So I've heard people are getting visas to France. -- **16:43:48 · Dominik Kapusta:** Yeah, yeah. -- **16:43:49 · Alex Martemyanov:** And anyways, you can get a visa for France, and then go to some other… country, or just have a flight to France first, and then move further. -- **16:43:55 · Dominik Kapusta:** That's right. That's right. -- **16:44:03 · Alex Martemyanov:** Correct, yeah, Spain, Sweden, Belgium, Portugal… It's basically all the… European cities. -- **16:44:14 · Dominik Kapusta:** Yeah, I think the first… The first that's not European is, well, New York City and then Playa del Carmen in Mexico. -- **16:44:26 · Alex Martemyanov:** Yeah, I guess, uh… New York could work better. But it's harder for me to… to fulfill all the paper paperwork for it. -- **16:44:37 · Dominik Kapusta:** Okay, I see. Well. -- **16:44:39 · Alex Martemyanov:** So, for Europe, it's just an easy application. I just have to go and apply for… get some bank statements and apply, but it's… -- **16:44:45 · Dominik Kapusta:** Yeah… -- **16:44:47 · Alex Martemyanov:** Would be a third reject in a row, maybe or maybe not. -- **16:44:50 · Dominik Kapusta:** Mm-hmm. Oh. -- **16:44:53 · Alex Martemyanov:** That's, you know, for New York, it's kind of more complicated. Including the flight. -- **16:45:01 · Dominik Kapusta:** You know. I'm really curious what will… come out of it because, yeah, it's interesting. It's just… Sounds… sounds bad that we have to sort of rule you out of every meetup every year, unless we go… To Costa Rica, like, 3 years ago, 2 years ago, uh… -- **16:45:35 · Alex Martemyanov:** Yeah, why not? -- **16:45:36 · Dominik Kapusta:** Why not? Yeah, I mean, we should do it. Let's see. Yeah, let's see, maybe we'll talk about it in the Apple Weekly, hopefully. All right, other than that, so to recap the call, perhaps… Unless… do you have anything else to talk about? -- **16:46:06 · Alex Martemyanov:** And… Well, I guess not. -- **16:46:09 · Dominik Kapusta:** Mm-hmm. -- **16:46:10 · Alex Martemyanov:** Should be… -- **16:46:12 · Dominik Kapusta:** Yeah, sure, sure, sure. Alright, uh… So… Yeah, so you're moving to OB, but you'll have to… Go through. Uh… And it looks like you have another project scheduled after this one. -- **16:46:33 · Alex Martemyanov:** Yeah, the, uh… It seems it's… -- **16:46:37 · Dominik Kapusta:** Stop. Stop. -- **16:46:37 · Alex Martemyanov:** consequent projects. -- **16:46:39 · Dominik Kapusta:** Stop iOS reload loops after tab memory kills. Which may be interesting… I mean, interesting, as in, uh, maybe straightforward, because we have the… Uh, we have that in macOS. To some extent, in some shape. It's, of course, different, but… At least there's a precedent. But it looks like you'll stick with OB until the end of the year, at least. And, uh… That's that, essentially. Umm. Fine. So if you could update the UI tests thingy, that would be great as well. And that's it, you're wrapping up your project, so… -- **16:47:37 · Alex Martemyanov:** Mmhm. -- **16:47:38 · Dominik Kapusta:** Probably not much time to work on AORs. But also, there's nothing burning over there. I mean, there is a burning thing in the CIA UR, and I'll have to rotate all GitHub Action secrets. Should be funny! Okay. Uh, yeah, so we can just… Wrap it up here, let's catch up again next week. And see how OB work is going. -- **16:48:06 · Alex Martemyanov:** Okay. Noted. Cool. -- **16:48:09 · Dominik Kapusta:** Cool. Yeah, I'll see you at the Apple Weekly. Thanks a lot, Alex. Have a great rest of the day. diff --git a/work/zoom-transcripts/index.json b/work/zoom-transcripts/index.json index 2683c8ec..ba78226f 100644 --- a/work/zoom-transcripts/index.json +++ b/work/zoom-transcripts/index.json @@ -110,8 +110,8 @@ "note_modified_at": "2026-10-15T11:12:31.812Z", "source_url": "https://us01mynotes.zoom.us/nzWOuhyzSdCjNqMRh6X13w", "folder": "2026-10-15 Dominik Kapusta's Personal Meeting Room 2026-10-15 16 05(GMT+6 00) nzWOuhyzSdCjNqMRh6X13w", - "sha256": "34921cf2862c6a7286a849ee41af52d2f309fc087caf0dfcc940956843506e1d", - "cues": 332 + "sha256": "e3643f57bd7da45c00a31c3b14ffd85ea17b16ff56bdbea3c50d825d81236ddf", + "cues": 3 }, "rJFn9D3lRJmnlCMSomhPsw": { "title": "Michal Smaga's Personal Meeting Room", @@ -134,8 +134,8 @@ "note_modified_at": "2026-11-12T09:53:25.042Z", "source_url": "https://us01mynotes.zoom.us/DLwAbUQ_RZ6X_D63xiX_Ww", "folder": "undated Max Tsoy's Personal Meeting Room DLwAbUQ_RZ6X_D63xiX_Ww", - "sha256": "a3436342699e9bdbbbf1071cd8c4e9189e3be8feb502df39b34ae20812cd2142", - "cues": 115 + "sha256": "db809c761f4db97fd8b6f58235b80d896f8b4ac7886f3c495a4f396f3f875879", + "cues": 3 }, "VSuzeqZCR5O2z5KtmaQt3g": { "title": "Apple Weekly Team Meeting - Zoom ID", @@ -146,8 +146,8 @@ "note_modified_at": "2026-11-10T15:01:11.107Z", "source_url": "https://us01mynotes.zoom.us/VSuzeqZCR5O2z5KtmaQt3g", "folder": "undated Apple Weekly Team Meeting - Zoom ID VSuzeqZCR5O2z5KtmaQt3g", - "sha256": "89cbb44cc7924bd9624a000cbe485052b215901139b318b32edca2b1fb3ed7ae", - "cues": 38 + "sha256": "9b60eff9386c690f0136b636129fee6489d0e7aa6c0a62230a8500c3520999e9", + "cues": 3 }, "p5FdcX9WT-afBpWjRgaW0w": { "title": "Dominik Kapusta's Personal Meeting Room", @@ -158,8 +158,8 @@ "note_modified_at": "2026-11-10T10:01:44.278Z", "source_url": "https://us01mynotes.zoom.us/p5FdcX9WT-afBpWjRgaW0w", "folder": "undated Dominik Kapusta's Personal Meeting Room p5FdcX9WT-afBpWjRgaW0w", - "sha256": "21d3c3d8f4c7fea11976f5cb54b98a121c895c7aabcb1b541c6d3f6f1167460a", - "cues": 130 + "sha256": "5d3aeb038b4212d9cdd785c7b1683d37ea04faf0816463ce4e37873af9bb8dbb", + "cues": 3 }, "e5TYWRytRz2WwWSe68BSWQ": { "title": "O-E 2026", @@ -242,8 +242,8 @@ "note_modified_at": "2026-11-03T10:04:07.74Z", "source_url": "https://us01mynotes.zoom.us/kOfTt34CRsG3dquIpsIzYA", "folder": "2026-11-03 Dominik Kapusta's Personal Meeting Room kOfTt34CRsG3dquIpsIzYA", - "sha256": "e44b551f39b5f1d02366d4be6518383190d6af1ee64986cc5a987caa3ed666d4", - "cues": 168 + "sha256": "d262e4ea477617170afc6f348871c57f1bac0ee0b7a19cdef4c4ffd593776e2b", + "cues": 3 }, "qQ2bzU5KTiCGluiBYA-ROA": { "title": "Michal Smaga's Personal Meeting Room", @@ -254,8 +254,8 @@ "note_modified_at": "2026-11-03T09:26:09.911Z", "source_url": "https://us01mynotes.zoom.us/qQ2bzU5KTiCGluiBYA-ROA", "folder": "2026-11-03 Michal Smaga's Personal Meeting Room qQ2bzU5KTiCGluiBYA-ROA", - "sha256": "dafb593da5838d0c82fa22918d30cd0e58dbe5d9a592b8a8c2c997d083a80638", - "cues": 59 + "sha256": "646f7d0a50c8ad5f3297b8d28175a5649505ae798ba57fca5340d26536f0dd14", + "cues": 3 }, "FZA-Gp3ATxiQ7cQaU5u5tg": { "title": "O-E 2026", @@ -362,8 +362,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": "a4b3c5ce7fafb99496019591da19f9a103e35cf5f37ec42aa8f154021fdebcae", - "cues": 133 + "sha256": "5cf16938df6ebe0110bec8e8b4311fcbe55a764bd2bb72f64faa049ba1777d9e", + "cues": 3 }, "KcmYOq5_SQGPxdkdbhRx9A": { "title": "Dominik Kapusta's Personal Meeting Room", @@ -374,8 +374,8 @@ "note_modified_at": "2026-11-17T10:09:04.028Z", "source_url": "https://us01mynotes.zoom.us/KcmYOq5_SQGPxdkdbhRx9A", "folder": "2026-11-17 Dominik Kapusta's Personal Meeting Room KcmYOq5_SQGPxdkdbhRx9A", - "sha256": "5c109ab406cc31416901fa0074d845e38f8600045da5ba76945e879eea975b92", - "cues": 252 + "sha256": "cdce4f852b434945d53f44b1f66ab533243bcda2c06687c7b3935661ab786a56", + "cues": 3 }, "GJhjFoDDRY6PkqEUdM-YFg": { "title": "Apple Weekly Team Meeting - Zoom ID", @@ -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": "cd06af7a61ede6d4cd5d78b6ed94d9c6650c99a66d637cdf0e2eba0fef6390c5", - "cues": 48 + "sha256": "22c2c60c7a01fe8692c3e347c12beaa43102161292c468734320db978739bb11", + "cues": 3 } } } diff --git a/work/zoom-transcripts/sync-status.json b/work/zoom-transcripts/sync-status.json index d16470bb..edcd66d7 100644 --- a/work/zoom-transcripts/sync-status.json +++ b/work/zoom-transcripts/sync-status.json @@ -1 +1 @@ -{"observed_at":"2026-11-18T07:08:09.397Z","scanned":31,"imported":0,"skipped":31,"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-18T07:40:41.239Z","scanned":31,"imported":9,"skipped":22,"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 diff --git a/work/zoom-transcripts/undated Apple Weekly Team Meeting - Zoom ID VSuzeqZCR5O2z5KtmaQt3g/transcript.json b/work/zoom-transcripts/undated Apple Weekly Team Meeting - Zoom ID VSuzeqZCR5O2z5KtmaQt3g/transcript.json index bc9f2e92..0d87c512 100644 --- a/work/zoom-transcripts/undated Apple Weekly Team Meeting - Zoom ID VSuzeqZCR5O2z5KtmaQt3g/transcript.json +++ b/work/zoom-transcripts/undated Apple Weekly Team Meeting - Zoom ID VSuzeqZCR5O2z5KtmaQt3g/transcript.json @@ -23,181 +23,6 @@ "time": "21:03:03", "speaker": "SS", "text": "Hey, yes, um… I was recently doing some bug finding and fixing in the iOS app, uh, and had an opportunity to use the verify skill that Pete had put together for iOS. So the back… the background here is that, um. This is a skill that is used with PStack, if you remember Potato Mode. Who amongst us could forget? Uh, that is built around the concept of these verify skills, and Peter's made one for iOS that captures, like. recording of the screen, it captures, like, the pixels that were sent, like, everything you need to, like, prove that, you know, the agent has done the thing that it said it was going to do. Uh, so I used this for fixing a cr. evidence before the crash happening, after of it being fixed. It was super useful, worked great, so. Thank you, Pete." - }, - { - "time": "21:03:50", - "speaker": "Jonathan Jackson", - "text": "Awesome. Thank you. Quick reminder that our next team retro is about four weeks from now. Just keep that in mind. It's coming up. It's going to come quickly, I think, for everybody this time of year. Um… we'll go through a quick round of rotation check-ins. Uh, this week for iOS Triage is Hasan, uh, followed by PCOR and then Yasek. Mac OS triage is Alessandro this week, followed by Ann and then Sabrina. For iOS release, it looks like whoever's on this week has closed the task by accident, but I hope you know who you are and you can bring it back for us. Next week will be Pao and then Hanyu. And for macOS…" - }, - { - "time": "21:04:37", - "speaker": "Pete Smith", - "text": "Is that… sorry, Jonathan, was that iOS this week, was it?" - }, - { - "time": "21:04:39", - "speaker": "Jonathan Jackson", - "text": "Yep. iOS release this week? Yeah, is that you?" - }, - { - "time": "21:04:43", - "speaker": "Pete Smith", - "text": "Yeah, yeah, I closed it. It wasn't by accident, though. I just closed it because I have the other release tasks. But if you need it open, I can reopen." - }, - { - "time": "21:04:47", - "speaker": "Jonathan Jackson", - "text": "Oh, okay. I mean, if we don't… no, we don't necessarily need it open. If it's done, it's done, but usually they've set open for the." - }, - { - "time": "21:04:54", - "speaker": "Pete Smith", - "text": "Cool." - }, - { - "time": "21:04:54", - "speaker": "Jonathan Jackson", - "text": "Doesn't matter. Uh, the important part is that you know you're doing it, you've dealt with it, which clearly you have. Uh, and then macOS release, uh, is Joseph this week, followed by Federico, and then Juan. Also, a reminder that we're starting to coordinate the winter holiday rotations. There's a task link in the meeting notes here, and I sent that out late last week. Maybe it was even early this week, early last week. We definitely need some folks to be able to cover for others who are out. A lot of those rotations land on people's out of office time. take a peek. If you can cover one of those, even if you're not normally on that rotation, and you're… but you're willing to, that would be lovely. It would help other people have the time off that they are looking for. If we get stuck, I'll get a little more involved once it sort of has run its course on basic conversation and then see what we can do to make sure this works for everybody. Um, but for now, start with if there's something that you're… either if you're on a rotation that you can't cover, mark yourself as unavailable. Most folks have already done that, but there's a few that still need to. Or if there's one you're willing to cover through the holiday, whether you're just around during that time or you're going to be out of office, but you're still willing to cover it, mark yourself as green, and then we'll go from there about other coverage. I see a couple of folks have already volunteered to cover a couple of weeks. I appreciate that. Time sensitive topics. Andre. An update on SmartLink from you. Thank you." - }, - { - "time": "21:06:30", - "speaker": "Andre Martingo", - "text": "Yeah, just a quick follow-up on the previous update that we had. So, um, we have been running for, I think it's a second release now. Um, it showed up more mature, this one, so basically, uh, we had a lot of strings that were, uh. merge into master, so the PR for iOS and macOS are already merged. In fact, iOS, we went through already a specific flow because everything was not ready when we forked the release. So basically, we saw during this night. That was able to understand if the job was not completed and then wait for the job to be completed and pull all the strings. So we disable the danger rule in main. So basically now you can start merging untranslated stuff. and everything should work. Me and Pao, we are gonna still keep an eye to understand if something goes wrong. Uh, but for example, we already saw with Reedy, uh, another, uh, feature that we introduced, which is if you create a… If you merge into main and that job that got triggered on your commit will have some question from someone from SmartLink, it will create a task for you. So you don't need to always check if the job has any issues. proactively will create a task for you, if there is any issue. Um, so we expect everything to be much smoother, um, and basically, yeah, you can start merging, uh, English strings into mine." - }, - { - "time": "21:08:05", - "speaker": "Jonathan Jackson", - "text": "Amazing. Thank you. And the automated task creation, if it has a question, is really excellent too because it closes that loop. Very cool. Dominic. Bitrise update. We're spending seven grand a month on UI tests." - }, - { - "time": "21:08:25", - "speaker": "Dominik Kapusta", - "text": "Yes, thank you. On UI test on macOS 15 and 26 and 14. Which is now deleted. Um… That's what I learned. Oh. After switching to Bitrise, I kept asking Kiran about the costs of GitHub, expecting them to go down, and they went down to $7,000 a month. So I started digging, and I found out that this… Sort of… almost ideally matches the number of minutes we used on macOS 14, 15 and 26xlarge GitHub runners in October. And then, I also recalled that Bitrise rolled out an update to BuildHub pools, that they allow… when they allow to… scaling down pools to zero, essentially, so… You can create a pool of… Some machines, and if none of them is used. there are just zero machines in the pool, and it doesn't contribute to the overall capacity. So I thought, okay, I'm just gonna create pools for macOS 15 and macOS 26, and let's run UI tests in Bitrise, and it's live. As of now, it's in main, so all macOS UI tests now run on Bitrise machines, and we're aiming to remove that $7,000 a month from GitHub bill. Um, and in place of that, I'm proposing that we increase our Bitrise fleet, because we will need some more machines. in some time, especially when we start using Bitrise machines for Agentic workflows. But also, some queuing is happening already. So, I put together a very small, um… Um, proposal with a calculation. I only pinged Jonathan and Laura over there, for what it's worth. You can reach that proposal by going to that task and in a subtask. But it's essentially to just agree that we should pursue that at the very moment, because we are about to update the Bitrise deal. Jeff from Partnerships suggested that if we're… if we wanted to… if we are updating the deal at the moment, that's really to build cash, a separate thing, completely. Uh, if we're doing an amendment, we'll need legal review, we'll need some other reviews, probably, so… If we want to change something else, let's do it right now. To… to speed up the process and also save. Time and money of the legal team. So, that's that. The change for… for Apple team members is that UI tests will be… oh, there's actually one more change I forgot about. So the UI tests run on bitrise. And also… from now on, by default, UI tests will only run on macOS 27. If you want to run macOS… if you want to run macOS UI tests on older OS versions, you have to check the box. That's called all OS versions. It was previously on by default, now it's off by default. That's the change. But also, there's another news item I want to share. Alessandro is working on… an overhaul of how we trigger UI tests. So, we removed some triggers for UI tests workflows on pull requests, and in place of that, we'll be putting. UI test workflows triggered by a label on a pull request. Ale is working on that. We'll have more next week. Thank you." - }, - { - "time": "21:12:21", - "speaker": "Jonathan Jackson", - "text": "One question on the UI test side. You talked about this for macOS only. Should we think about it for iOS as well, or is there a different story there already?" - }, - { - "time": "21:12:29", - "speaker": "Dominik Kapusta", - "text": "It's a different story, because iOS doesn't need old OS versions, because it has simulators." - }, - { - "time": "21:12:36", - "speaker": "Jonathan Jackson", - "text": "So those are already running in the rows." - }, - { - "time": "21:12:36", - "speaker": "Dominik Kapusta", - "text": "It will be… Yeah, yeah." - }, - { - "time": "21:12:40", - "speaker": "Jonathan Jackson", - "text": "Okay, awesome." - }, - { - "time": "21:12:41", - "speaker": "Dominik Kapusta", - "text": "Thank you." - }, - { - "time": "21:12:44", - "speaker": "Jonathan Jackson", - "text": "James, you're up next." - }, - { - "time": "21:12:48", - "speaker": "JF", - "text": "Hey, um, this is just an update on something I started during the last hack days, which was… To look at automating our, uh… the pixel anomaly triage stage of our rotations, uh, initially starting with macOS, just because that's what I'm used to looking at on the rotation. I got it working reasonably well over half days, and then… When Jorge was on maintenance a few weeks ago, I manually ran it each day, um, kind of alongside him, just to see how it was going. Tuned it, made it less verbose over time. I think it's in a good place now. It's built on… There's a new GitHub Agentic workflow system that's been put in place by Lucas, which. Um, is now approved and ready to go, and it can… run on a GitHub workflow and access Asano, ClickHouse, um, you know, GitHub. info. So, basically, I feel like it's in a good place, so I'm going to enable it to run each day. Automatically, once the Pixel triage tasks are created for macOS, basically it annotates the existing description that gets put in the triage tasks. If it thinks anything needs further review, it will create a subtask and assign it to that person. Just like any of us would do if we were reviewing these things. So I'm going to enable it. We can see how it goes. I've dropped a link. In the, uh… chart both. dropped a document in the AI enablement, um… project with kind of how it works. I'll keep an eye on it as well as it runs and keep in touch with the people who are on rotations just to see what they think of it. And we can, you know, we can dial it in. But if anyone's got any, you know, questions or issues or. improvements they can suggest, then let me know. But I will turn that on shortly." - }, - { - "time": "21:14:54", - "speaker": "Jonathan Jackson", - "text": "Very cool. Thank you. I'm going to ask you the same question I asked Dominic. What about iOS?" - }, - { - "time": "21:14:59", - "speaker": "JF", - "text": "Yeah, I don't see why that should. should be an issue. It's the same kind of thing, but I just thought I'd start with one." - }, - { - "time": "21:15:03", - "speaker": "Jonathan Jackson", - "text": "Yeah, I figured. Great. Yeah, yeah, sure. I just want to make sure that you're thinking ahead, as I imagine you are." - }, - { - "time": "21:15:10", - "speaker": "JF", - "text": "Yeah." - }, - { - "time": "21:15:11", - "speaker": "Jonathan Jackson", - "text": "Um, I guess I would say when you're, you know, once you're happy with it on macOS, you could turn it on for iOS. If you need more signal, you could turn it on for both even sooner, and you'd." - }, - { - "time": "21:15:17", - "speaker": "JF", - "text": "Yeah. Sure." - }, - { - "time": "21:15:21", - "speaker": "Jonathan Jackson", - "text": "But I'll leave that up to you to decide, obviously." - }, - { - "time": "21:15:23", - "speaker": "JF", - "text": "Cool." - }, - { - "time": "21:15:24", - "speaker": "Jonathan Jackson", - "text": "Thank you. Awesome. Okay. Miha, you're next." - }, - { - "time": "21:15:33", - "speaker": "Michal Smaga", - "text": "Yeah, I wanted to do a short demo, like, to give you a privilege of, like, pre-release showcase of the feature we are working on. So, as you probably know, we have already ad blocking for YouTube, and now we are working on something called, like, sponsor blocking, or skipping sponsor segments, so… Uh, there may be, uh, like, some of the videos can have the… the parts where the creator, like, advertises some kind of, like, sponsored product, and sometimes you may want to skip those, and there's no easy way, unless you use some third-party, like, web extensions. And we are trying to leverage one of the solutions, which is SponsorBlock. So this is, like, both API and both web extension, and we try to, like, integrate it into our browsers, so… Uh, in the linked task, there's, like, a step-by-step, uh, description. So, uh, the current state is that we have the MVP, which is, like, very, like, uh, bare-bones, that, uh, there's no design, there's no copy, so there are no translations, so basically this is, like, a very bare-bones version. Of the future to validate if it works and if it, like, lives up to to our expectations. And this is like for internal use only, so it won't be shipped in that form. Definitely. So, you may already have it because it's enabled by the behind the internal user feature flag in this week's internal releases. So if you go into the task. There's, uh… There's a short description of the feature. There's the required version, which is, like, this week's internal. So either you need to use TestFlight for the apps versions, or if you have the direct download on macOS, it should be already on your desktop. And basically, the future works like that, that if you open, uh… video that contains a sponsored segment. I think this one does. You will see that there's, like, a highlight in the SIG bar, which is the sponsored segment, and… If you open the settings in ad blocking, you have the additional section here for the sponsored segments, where you can toggle between the manual and the automatic mode. So the default one is the manual one, so if you go into the section here, you can see there's, like, a button. You can click it, and it goes to the end of the section, and, it plays back. In the automatic, it automatically, like, skips the segment when it's being encountered. Uh, yeah, and this is basically it, and should just work for everyone, so the goal is to have it for internal users, for the employees, be enabled by default. there will be wider announcement, uh, for… for it, uh, and probably we'll have some kind of, like, channel to gather the feedback, so keep an eye on… on that, and yeah, if you want, like, sponsored segment-free YouTube experience, you'll… Feel free to, like, use it and enjoy it. If you have any open questions, I'm… Sure. Thank you." - }, - { - "time": "21:18:56", - "speaker": "Jonathan Jackson", - "text": "Very cool, thank you. I'm definitely gonna check that one out." - }, - { - "time": "21:18:59", - "speaker": "Michal Smaga", - "text": "I see there was like a question in the chat. Yeah, Brindy asked about if the YouTubers are getting paid. Yeah, so this is like not the ads that are served by YouTube. So this is like part of the video, which is the tricky part. And, uh, like, from all the information that we were able to gather, uh, they are, like, probably paid upfront, so there's, like, external contract that they are, and there's no indication on. the video, or, like, specific segment, I'm not sure if there are, like, analytics for that, uh, that if given, like, sponsored segment was being, uh, watched. Uh, and, uh, yeah, so I don't think so, and basically the data is not extracted from YouTube, it's basically, like, from a third party, so the sponsor block is, like, the API, where… which is, like, open source, and, like. community-driven, so, like, people, like, submit the segments, uh, for the data, and yeah, we can use that." - }, - { - "time": "21:20:03", - "speaker": "Jonathan Jackson", - "text": "Cool. Thank you. Yeah, that was a good question. Uh, Brenda, your revenue stream sounds like it's safe. Um… Does anybody have anything else to add? Any questions, demos, other things you want to talk about today?" - }, - { - "time": "21:20:18", - "speaker": "Jorge Leandro Perez", - "text": "Question, do we have a meetup location defined yet, or not yet?" - }, - { - "time": "21:20:23", - "speaker": "Jonathan Jackson", - "text": "Uh, location is not defined the way… there are… the process is a little different this year, um, and John B. has taken over the… the week questionnaire, and sort of getting those weeks figured out. I think you probably have seen that. Um… I need to check back in with him now that that's happened, and figure out what next steps are in terms of location planning. He's been in touch with us a little bit, um, but that'll be, I think, probably the next step, so stay tuned." - }, - { - "time": "21:20:50", - "speaker": "Jorge Leandro Perez", - "text": "Thank you." - }, - { - "time": "21:20:58", - "speaker": "Jonathan Jackson", - "text": "Thank you. Anything else? Anybody? OK. Thank you all. It's good to see you. Have a great day." } ] } diff --git a/work/zoom-transcripts/undated Apple Weekly Team Meeting - Zoom ID VSuzeqZCR5O2z5KtmaQt3g/transcript.md b/work/zoom-transcripts/undated Apple Weekly Team Meeting - Zoom ID VSuzeqZCR5O2z5KtmaQt3g/transcript.md index 504cd9aa..159da775 100644 --- a/work/zoom-transcripts/undated Apple Weekly Team Meeting - Zoom ID VSuzeqZCR5O2z5KtmaQt3g/transcript.md +++ b/work/zoom-transcripts/undated Apple Weekly Team Meeting - Zoom ID VSuzeqZCR5O2z5KtmaQt3g/transcript.md @@ -15,38 +15,3 @@ source: "https://us01mynotes.zoom.us/VSuzeqZCR5O2z5KtmaQt3g" - **21:01:48 · Jorge Leandro Perez:** I'm usually the one who can't stand the silence in elevators, so I start talking. - **21:01:55 · Jonathan Jackson:** I appreciate that you haven't decided to bite Muzak into our meeting, sir, so… All right. Why don't we go ahead and get started? Sam, you want to kick us off with your appreciation? - **21:03:03 · SS:** Hey, yes, um… I was recently doing some bug finding and fixing in the iOS app, uh, and had an opportunity to use the verify skill that Pete had put together for iOS. So the back… the background here is that, um. This is a skill that is used with PStack, if you remember Potato Mode. Who amongst us could forget? Uh, that is built around the concept of these verify skills, and Peter's made one for iOS that captures, like. recording of the screen, it captures, like, the pixels that were sent, like, everything you need to, like, prove that, you know, the agent has done the thing that it said it was going to do. Uh, so I used this for fixing a cr. evidence before the crash happening, after of it being fixed. It was super useful, worked great, so. Thank you, Pete. -- **21:03:50 · Jonathan Jackson:** Awesome. Thank you. Quick reminder that our next team retro is about four weeks from now. Just keep that in mind. It's coming up. It's going to come quickly, I think, for everybody this time of year. Um… we'll go through a quick round of rotation check-ins. Uh, this week for iOS Triage is Hasan, uh, followed by PCOR and then Yasek. Mac OS triage is Alessandro this week, followed by Ann and then Sabrina. For iOS release, it looks like whoever's on this week has closed the task by accident, but I hope you know who you are and you can bring it back for us. Next week will be Pao and then Hanyu. And for macOS… -- **21:04:37 · Pete Smith:** Is that… sorry, Jonathan, was that iOS this week, was it? -- **21:04:39 · Jonathan Jackson:** Yep. iOS release this week? Yeah, is that you? -- **21:04:43 · Pete Smith:** Yeah, yeah, I closed it. It wasn't by accident, though. I just closed it because I have the other release tasks. But if you need it open, I can reopen. -- **21:04:47 · Jonathan Jackson:** Oh, okay. I mean, if we don't… no, we don't necessarily need it open. If it's done, it's done, but usually they've set open for the. -- **21:04:54 · Pete Smith:** Cool. -- **21:04:54 · Jonathan Jackson:** Doesn't matter. Uh, the important part is that you know you're doing it, you've dealt with it, which clearly you have. Uh, and then macOS release, uh, is Joseph this week, followed by Federico, and then Juan. Also, a reminder that we're starting to coordinate the winter holiday rotations. There's a task link in the meeting notes here, and I sent that out late last week. Maybe it was even early this week, early last week. We definitely need some folks to be able to cover for others who are out. A lot of those rotations land on people's out of office time. take a peek. If you can cover one of those, even if you're not normally on that rotation, and you're… but you're willing to, that would be lovely. It would help other people have the time off that they are looking for. If we get stuck, I'll get a little more involved once it sort of has run its course on basic conversation and then see what we can do to make sure this works for everybody. Um, but for now, start with if there's something that you're… either if you're on a rotation that you can't cover, mark yourself as unavailable. Most folks have already done that, but there's a few that still need to. Or if there's one you're willing to cover through the holiday, whether you're just around during that time or you're going to be out of office, but you're still willing to cover it, mark yourself as green, and then we'll go from there about other coverage. I see a couple of folks have already volunteered to cover a couple of weeks. I appreciate that. Time sensitive topics. Andre. An update on SmartLink from you. Thank you. -- **21:06:30 · Andre Martingo:** Yeah, just a quick follow-up on the previous update that we had. So, um, we have been running for, I think it's a second release now. Um, it showed up more mature, this one, so basically, uh, we had a lot of strings that were, uh. merge into master, so the PR for iOS and macOS are already merged. In fact, iOS, we went through already a specific flow because everything was not ready when we forked the release. So basically, we saw during this night. That was able to understand if the job was not completed and then wait for the job to be completed and pull all the strings. So we disable the danger rule in main. So basically now you can start merging untranslated stuff. and everything should work. Me and Pao, we are gonna still keep an eye to understand if something goes wrong. Uh, but for example, we already saw with Reedy, uh, another, uh, feature that we introduced, which is if you create a… If you merge into main and that job that got triggered on your commit will have some question from someone from SmartLink, it will create a task for you. So you don't need to always check if the job has any issues. proactively will create a task for you, if there is any issue. Um, so we expect everything to be much smoother, um, and basically, yeah, you can start merging, uh, English strings into mine. -- **21:08:05 · Jonathan Jackson:** Amazing. Thank you. And the automated task creation, if it has a question, is really excellent too because it closes that loop. Very cool. Dominic. Bitrise update. We're spending seven grand a month on UI tests. -- **21:08:25 · Dominik Kapusta:** Yes, thank you. On UI test on macOS 15 and 26 and 14. Which is now deleted. Um… That's what I learned. Oh. After switching to Bitrise, I kept asking Kiran about the costs of GitHub, expecting them to go down, and they went down to $7,000 a month. So I started digging, and I found out that this… Sort of… almost ideally matches the number of minutes we used on macOS 14, 15 and 26xlarge GitHub runners in October. And then, I also recalled that Bitrise rolled out an update to BuildHub pools, that they allow… when they allow to… scaling down pools to zero, essentially, so… You can create a pool of… Some machines, and if none of them is used. there are just zero machines in the pool, and it doesn't contribute to the overall capacity. So I thought, okay, I'm just gonna create pools for macOS 15 and macOS 26, and let's run UI tests in Bitrise, and it's live. As of now, it's in main, so all macOS UI tests now run on Bitrise machines, and we're aiming to remove that $7,000 a month from GitHub bill. Um, and in place of that, I'm proposing that we increase our Bitrise fleet, because we will need some more machines. in some time, especially when we start using Bitrise machines for Agentic workflows. But also, some queuing is happening already. So, I put together a very small, um… Um, proposal with a calculation. I only pinged Jonathan and Laura over there, for what it's worth. You can reach that proposal by going to that task and in a subtask. But it's essentially to just agree that we should pursue that at the very moment, because we are about to update the Bitrise deal. Jeff from Partnerships suggested that if we're… if we wanted to… if we are updating the deal at the moment, that's really to build cash, a separate thing, completely. Uh, if we're doing an amendment, we'll need legal review, we'll need some other reviews, probably, so… If we want to change something else, let's do it right now. To… to speed up the process and also save. Time and money of the legal team. So, that's that. The change for… for Apple team members is that UI tests will be… oh, there's actually one more change I forgot about. So the UI tests run on bitrise. And also… from now on, by default, UI tests will only run on macOS 27. If you want to run macOS… if you want to run macOS UI tests on older OS versions, you have to check the box. That's called all OS versions. It was previously on by default, now it's off by default. That's the change. But also, there's another news item I want to share. Alessandro is working on… an overhaul of how we trigger UI tests. So, we removed some triggers for UI tests workflows on pull requests, and in place of that, we'll be putting. UI test workflows triggered by a label on a pull request. Ale is working on that. We'll have more next week. Thank you. -- **21:12:21 · Jonathan Jackson:** One question on the UI test side. You talked about this for macOS only. Should we think about it for iOS as well, or is there a different story there already? -- **21:12:29 · Dominik Kapusta:** It's a different story, because iOS doesn't need old OS versions, because it has simulators. -- **21:12:36 · Jonathan Jackson:** So those are already running in the rows. -- **21:12:36 · Dominik Kapusta:** It will be… Yeah, yeah. -- **21:12:40 · Jonathan Jackson:** Okay, awesome. -- **21:12:41 · Dominik Kapusta:** Thank you. -- **21:12:44 · Jonathan Jackson:** James, you're up next. -- **21:12:48 · JF:** Hey, um, this is just an update on something I started during the last hack days, which was… To look at automating our, uh… the pixel anomaly triage stage of our rotations, uh, initially starting with macOS, just because that's what I'm used to looking at on the rotation. I got it working reasonably well over half days, and then… When Jorge was on maintenance a few weeks ago, I manually ran it each day, um, kind of alongside him, just to see how it was going. Tuned it, made it less verbose over time. I think it's in a good place now. It's built on… There's a new GitHub Agentic workflow system that's been put in place by Lucas, which. Um, is now approved and ready to go, and it can… run on a GitHub workflow and access Asano, ClickHouse, um, you know, GitHub. info. So, basically, I feel like it's in a good place, so I'm going to enable it to run each day. Automatically, once the Pixel triage tasks are created for macOS, basically it annotates the existing description that gets put in the triage tasks. If it thinks anything needs further review, it will create a subtask and assign it to that person. Just like any of us would do if we were reviewing these things. So I'm going to enable it. We can see how it goes. I've dropped a link. In the, uh… chart both. dropped a document in the AI enablement, um… project with kind of how it works. I'll keep an eye on it as well as it runs and keep in touch with the people who are on rotations just to see what they think of it. And we can, you know, we can dial it in. But if anyone's got any, you know, questions or issues or. improvements they can suggest, then let me know. But I will turn that on shortly. -- **21:14:54 · Jonathan Jackson:** Very cool. Thank you. I'm going to ask you the same question I asked Dominic. What about iOS? -- **21:14:59 · JF:** Yeah, I don't see why that should. should be an issue. It's the same kind of thing, but I just thought I'd start with one. -- **21:15:03 · Jonathan Jackson:** Yeah, I figured. Great. Yeah, yeah, sure. I just want to make sure that you're thinking ahead, as I imagine you are. -- **21:15:10 · JF:** Yeah. -- **21:15:11 · Jonathan Jackson:** Um, I guess I would say when you're, you know, once you're happy with it on macOS, you could turn it on for iOS. If you need more signal, you could turn it on for both even sooner, and you'd. -- **21:15:17 · JF:** Yeah. Sure. -- **21:15:21 · Jonathan Jackson:** But I'll leave that up to you to decide, obviously. -- **21:15:23 · JF:** Cool. -- **21:15:24 · Jonathan Jackson:** Thank you. Awesome. Okay. Miha, you're next. -- **21:15:33 · Michal Smaga:** Yeah, I wanted to do a short demo, like, to give you a privilege of, like, pre-release showcase of the feature we are working on. So, as you probably know, we have already ad blocking for YouTube, and now we are working on something called, like, sponsor blocking, or skipping sponsor segments, so… Uh, there may be, uh, like, some of the videos can have the… the parts where the creator, like, advertises some kind of, like, sponsored product, and sometimes you may want to skip those, and there's no easy way, unless you use some third-party, like, web extensions. And we are trying to leverage one of the solutions, which is SponsorBlock. So this is, like, both API and both web extension, and we try to, like, integrate it into our browsers, so… Uh, in the linked task, there's, like, a step-by-step, uh, description. So, uh, the current state is that we have the MVP, which is, like, very, like, uh, bare-bones, that, uh, there's no design, there's no copy, so there are no translations, so basically this is, like, a very bare-bones version. Of the future to validate if it works and if it, like, lives up to to our expectations. And this is like for internal use only, so it won't be shipped in that form. Definitely. So, you may already have it because it's enabled by the behind the internal user feature flag in this week's internal releases. So if you go into the task. There's, uh… There's a short description of the feature. There's the required version, which is, like, this week's internal. So either you need to use TestFlight for the apps versions, or if you have the direct download on macOS, it should be already on your desktop. And basically, the future works like that, that if you open, uh… video that contains a sponsored segment. I think this one does. You will see that there's, like, a highlight in the SIG bar, which is the sponsored segment, and… If you open the settings in ad blocking, you have the additional section here for the sponsored segments, where you can toggle between the manual and the automatic mode. So the default one is the manual one, so if you go into the section here, you can see there's, like, a button. You can click it, and it goes to the end of the section, and, it plays back. In the automatic, it automatically, like, skips the segment when it's being encountered. Uh, yeah, and this is basically it, and should just work for everyone, so the goal is to have it for internal users, for the employees, be enabled by default. there will be wider announcement, uh, for… for it, uh, and probably we'll have some kind of, like, channel to gather the feedback, so keep an eye on… on that, and yeah, if you want, like, sponsored segment-free YouTube experience, you'll… Feel free to, like, use it and enjoy it. If you have any open questions, I'm… Sure. Thank you. -- **21:18:56 · Jonathan Jackson:** Very cool, thank you. I'm definitely gonna check that one out. -- **21:18:59 · Michal Smaga:** I see there was like a question in the chat. Yeah, Brindy asked about if the YouTubers are getting paid. Yeah, so this is like not the ads that are served by YouTube. So this is like part of the video, which is the tricky part. And, uh, like, from all the information that we were able to gather, uh, they are, like, probably paid upfront, so there's, like, external contract that they are, and there's no indication on. the video, or, like, specific segment, I'm not sure if there are, like, analytics for that, uh, that if given, like, sponsored segment was being, uh, watched. Uh, and, uh, yeah, so I don't think so, and basically the data is not extracted from YouTube, it's basically, like, from a third party, so the sponsor block is, like, the API, where… which is, like, open source, and, like. community-driven, so, like, people, like, submit the segments, uh, for the data, and yeah, we can use that. -- **21:20:03 · Jonathan Jackson:** Cool. Thank you. Yeah, that was a good question. Uh, Brenda, your revenue stream sounds like it's safe. Um… Does anybody have anything else to add? Any questions, demos, other things you want to talk about today? -- **21:20:18 · Jorge Leandro Perez:** Question, do we have a meetup location defined yet, or not yet? -- **21:20:23 · Jonathan Jackson:** Uh, location is not defined the way… there are… the process is a little different this year, um, and John B. has taken over the… the week questionnaire, and sort of getting those weeks figured out. I think you probably have seen that. Um… I need to check back in with him now that that's happened, and figure out what next steps are in terms of location planning. He's been in touch with us a little bit, um, but that'll be, I think, probably the next step, so stay tuned. -- **21:20:50 · Jorge Leandro Perez:** Thank you. -- **21:20:58 · Jonathan Jackson:** Thank you. Anything else? Anybody? OK. Thank you all. It's good to see you. Have a great day. diff --git a/work/zoom-transcripts/undated Dominik Kapusta's Personal Meeting Room p5FdcX9WT-afBpWjRgaW0w/transcript.json b/work/zoom-transcripts/undated Dominik Kapusta's Personal Meeting Room p5FdcX9WT-afBpWjRgaW0w/transcript.json index c90c29e4..d53103a2 100644 --- a/work/zoom-transcripts/undated Dominik Kapusta's Personal Meeting Room p5FdcX9WT-afBpWjRgaW0w/transcript.json +++ b/work/zoom-transcripts/undated Dominik Kapusta's Personal Meeting Room p5FdcX9WT-afBpWjRgaW0w/transcript.json @@ -23,641 +23,6 @@ "time": "16:02:10", "speaker": "Dominik Kapusta", "text": "Jest." - }, - { - "time": "16:02:13", - "speaker": "Alex Martemyanov", - "text": "And basically no progress on other stuff yet." - }, - { - "time": "16:02:19", - "speaker": "Alex Martemyanov", - "text": "I need to finish the priority cleanup. So basically last week we've discussed it during the OE that we should. Basically wrap up the project with the. No visible outcomes. There was a slight decline in the numbers and several genuine bugs fixed, but they were not representing the main feature breakage." - }, - { - "time": "16:02:45", - "speaker": "Dominik Kapusta", - "text": "Nie. Drop, Ios." - }, - { - "time": "16:02:50", - "speaker": "Alex Martemyanov", - "text": "I know." - }, - { - "time": "16:02:57", - "speaker": "Dominik Kapusta", - "text": "Łazać." - }, - { - "time": "16:03:00", - "speaker": "Alex Martemyanov", - "text": "There was some decline, maybe a third. So there was a decline in some part. of the numbers, but there is still around 40%. of the event sequence of the received events that so basically most of it is. The data we received for most of the breakage pixels represents just regular normal flow and nothing obviously." - }, - { - "time": "16:03:34", - "speaker": "Dominik Kapusta", - "text": "Bardzo." - }, - { - "time": "16:03:34", - "speaker": "Alex Martemyanov", - "text": "pointing to anything. So the discussion during the OE was to basically clean up the inefficient fixes that we've got. The feature flags for the features that are removed and some. Um, like the pinned tabs management fix, uh, that are, um, staying without the feature flag. And, uh… Yeah, clean up the data that's being collected, because we've collected enough of it, and, uh, implement some permanent data collection that stays there for, uh. for diagnostics for the future possible breakages. And try to add some in. inside of the extension, some metrics inside of the extension to, um, to track the loading progress, basically. Where we… where do we stop, and where the messaging." - }, - { - "time": "16:04:23", - "speaker": "Dominik Kapusta", - "text": "Ok." - }, - { - "time": "16:04:31", - "speaker": "Alex Martemyanov", - "text": "Stops. and try to reason about it from from that perspective." - }, - { - "time": "16:04:37", - "speaker": "Dominik Kapusta", - "text": "Misji." - }, - { - "time": "16:04:39", - "speaker": "Alex Martemyanov", - "text": "So, uh… So yeah, probably today I'm going to open the featured slugs and clean up PR. And. later this week will complete. So I've updated the project, moving on the post-mortem to the next week, since last week I had no time to. completed due to some circumstances. And, uh… That's mostly it. I still got some. PRs requiring my attention, like the crash reporting fix. So, yeah, no updates since last week. On it. So, basically, my concern about it is, uh, we may, uh, we may break the existing macOS collection while fixing iOS collection, so I need to… reproduce it, reproduce the crash and. this slowdown condition and normal conditions and see how it if it still works and nothing breaks and then I'll proceed with it." - }, - { - "time": "16:05:49", - "speaker": "Dominik Kapusta", - "text": "Collection as in…" - }, - { - "time": "16:05:52", - "speaker": "Alex Martemyanov", - "text": "The App Store reports." - }, - { - "time": "16:05:53", - "speaker": "Dominik Kapusta", - "text": "Crosscode? Yeah, cross-collection, mhm." - }, - { - "time": "16:05:57", - "speaker": "Alex Martemyanov", - "text": "Yeah, so matching against process identifier or by date." - }, - { - "time": "16:06:02", - "speaker": "Dominik Kapusta", - "text": "Yeah. Yeah, yeah, yeah, yeah." - }, - { - "time": "16:06:05", - "speaker": "Alex Martemyanov", - "text": "Mmm." - }, - { - "time": "16:06:05", - "speaker": "Dominik Kapusta", - "text": "Oh. Right." - }, - { - "time": "16:06:14", - "speaker": "Alex Martemyanov", - "text": "And… That is it, I guess, so… I'm. I'm not top performing for the last week. So just… Just completing the TP stuff." - }, - { - "time": "16:06:35", - "speaker": "Dominik Kapusta", - "text": "Yeah, which is…" - }, - { - "time": "16:06:36", - "speaker": "Alex Martemyanov", - "text": "And yeah, there was…" - }, - { - "time": "16:06:38", - "speaker": "Dominik Kapusta", - "text": "Expected." - }, - { - "time": "16:06:39", - "speaker": "Alex Martemyanov", - "text": "And there was the maintenance, the release maintenance. Luckily, it was growing weak." - }, - { - "time": "16:06:46", - "speaker": "Dominik Kapusta", - "text": "Mm-hmm." - }, - { - "time": "16:06:47", - "speaker": "Alex Martemyanov", - "text": "So nothing else ended from it." - }, - { - "time": "16:06:48", - "speaker": "Dominik Kapusta", - "text": "I saw that, yeah, that's good, that's good. All right. Nice. That's fine. So you're going to wrap up your project. Will you run the postmortem this week or next week?" - }, - { - "time": "16:07:05", - "speaker": "Alex Martemyanov", - "text": "Next week, next week." - }, - { - "time": "16:07:06", - "speaker": "Dominik Kapusta", - "text": "Next week. Mm-hmm. Okay." - }, - { - "time": "16:07:07", - "speaker": "Alex Martemyanov", - "text": "So this week, I'm, uh… Completing the cleanup. And the next week is time for the postmortem." - }, - { - "time": "16:07:18", - "speaker": "Dominik Kapusta", - "text": "Sounds good. Alright, and then… Do you have… Do you know anything about… You're next. Top priority?" - }, - { - "time": "16:07:32", - "speaker": "Alex Martemyanov", - "text": "Uh, nope." - }, - { - "time": "16:07:35", - "speaker": "Dominik Kapusta", - "text": "Yeah, because there won't be any follow-up… there won't be any follow-up in OE for…" - }, - { - "time": "16:07:35", - "speaker": "Alex Martemyanov", - "text": "I guess I should make one." - }, - { - "time": "16:07:41", - "speaker": "Dominik Kapusta", - "text": "For this. I mean…" - }, - { - "time": "16:07:44", - "speaker": "Alex Martemyanov", - "text": "Well, I guess not, at least for the moment." - }, - { - "time": "16:07:45", - "speaker": "Dominik Kapusta", - "text": "Immediate follow up at least. Yeah, yeah, yeah." - }, - { - "time": "16:07:49", - "speaker": "Alex Martemyanov", - "text": "And, uh… So if we are shifting the diagnostics into the JavaScript part, it's probably… due to some someone else to. Keep up with it." - }, - { - "time": "16:08:05", - "speaker": "Dominik Kapusta", - "text": "No." - }, - { - "time": "16:08:05", - "speaker": "Alex Martemyanov", - "text": "So maybe there will be a follow-up task to perform the data analysis next week." - }, - { - "time": "16:08:12", - "speaker": "Dominik Kapusta", - "text": "Mm-hmm." - }, - { - "time": "16:08:12", - "speaker": "Alex Martemyanov", - "text": "So just one, one cloud shot. To fetch the data, to perform the analysis, to see the trends, and if… Anything new is highlighted from it. So I could person. Wrap up up a date. And that's it. And it goes after." - }, - { - "time": "16:08:29", - "speaker": "Dominik Kapusta", - "text": "Yeah, yeah." - }, - { - "time": "16:08:31", - "speaker": "Alex Martemyanov", - "text": "Two weeks from now, I guess, when the release is out." - }, - { - "time": "16:08:39", - "speaker": "Dominik Kapusta", - "text": "All right, fine, we'll need to learn what's next for you. When would you be opening? When would you be opening a top priority, Fred?" - }, - { - "time": "16:08:47", - "speaker": "Alex Martemyanov", - "text": "Gosh. Probably now." - }, - { - "time": "16:08:53", - "speaker": "Dominik Kapusta", - "text": "Yep." - }, - { - "time": "16:08:55", - "speaker": "Alex Martemyanov", - "text": "It's really, it's a good time." - }, - { - "time": "16:08:55", - "speaker": "Dominik Kapusta", - "text": "Okay. Okay, this is interesting then. There will be some work. shaping up in OB. If you're up for it, that may be interesting. I'm not sure how much native support they need, but… It is… considered a big problem these days, and that's the fact that all the JavaScript code injected into our websites causes performance issues. And side breakage. But… Yeah, well, both of them, essentially. And I'm, like I said, I'm not sure… If… A native engineer would be needed immediately. But if so, then… that… That would be very important. So this is very important. And… Let me see… So the assessment is this Thursday. And the projects… Okay. Let's see. Let's see. I see there is a… So this is the assessment task. And there is a subtask for the… staffing for the Apple team, so it sounds like they will need… they will need someone from the Apple team. This is not finalized yet, but… But, uh… Should probably be… should probably be… filled out today, I hope. I'll have the proposed critical path and Gantt chart ready for review on Tuesday. I'm proposing OB focus on performance this cycle, specifically the cost of the JS and config we inject into every frame." - }, - { - "time": "16:11:21", - "speaker": "Alex Martemyanov", - "text": "Thank you." - }, - { - "time": "16:11:21", - "speaker": "Dominik Kapusta", - "text": "They may at least need someone on the native side to, I don't know, implement some. measurements. I suppose. If this is something that… would be of interest to you, then that's great, because if not, I think you will still be mentioned there. What do you think?" - }, - { - "time": "16:11:58", - "speaker": "Alex Martemyanov", - "text": "Visibility. What is this discussion? That you mentioned." - }, - { - "time": "16:12:04", - "speaker": "Dominik Kapusta", - "text": "I was just reading the last comment in the thread." - }, - { - "time": "16:12:07", - "speaker": "Alex Martemyanov", - "text": "Okay." - }, - { - "time": "16:12:08", - "speaker": "Dominik Kapusta", - "text": "From Dave." - }, - { - "time": "16:12:22", - "speaker": "Alex Martemyanov", - "text": "Mmm… Well, looking at my current TP, if it can be reproduced, it would be more of a… something that I would be interested in, if… And if it's something like we got some breakage to fix it. Not so exciting, I'd say." - }, - { - "time": "16:12:52", - "speaker": "Dominik Kapusta", - "text": "Yeah, yeah, yeah, I can tell. I can tell. This, however, should be easier. On the functional side, on the technical side, it should be easier. at least from…" - }, - { - "time": "16:13:10", - "speaker": "Alex Martemyanov", - "text": "Yeah, at least if there is exact cases reported on or some exact websites." - }, - { - "time": "16:13:13", - "speaker": "Dominik Kapusta", - "text": "Yeah, I know. Uh, it may be… it may be about… it may be about just measuring things." - }, - { - "time": "16:13:17", - "speaker": "Alex Martemyanov", - "text": "It should be easier." - }, - { - "time": "16:13:22", - "speaker": "Dominik Kapusta", - "text": "So that front-end engineers can… Do changes, make changes. But I don't know. I don't know the details. Let's see. Trim the Apple Cs. Bundle and isolated world." - }, - { - "time": "16:13:37", - "speaker": "Alex Martemyanov", - "text": "Okay, I'm fine to get mentioned on the thread, and so for the next TP, I'll probably open it on Thursday, I guess." - }, - { - "time": "16:13:38", - "speaker": "Dominik Kapusta", - "text": "Interesting. Mmhm." - }, - { - "time": "16:13:47", - "speaker": "Alex Martemyanov", - "text": "Makes sense." - }, - { - "time": "16:13:49", - "speaker": "Dominik Kapusta", - "text": "Yeah, probably. I think it makes a lot of sense. I will be AFK for the rest of the week. Um, Bob…" - }, - { - "time": "16:13:57", - "speaker": "Alex Martemyanov", - "text": "Mm-hmm." - }, - { - "time": "16:13:59", - "speaker": "Dominik Kapusta", - "text": "It's not a problem, of course. Um… I will try to… Try to reach out to Jonathan to ask. If he knows anything about OB plans for a pool. Or if he knows anything about anything else. Any other objective that might need Apple people and I'll let you know. Do you want to talk about your performance review?" - }, - { - "time": "16:14:31", - "speaker": "Alex Martemyanov", - "text": "Uh, yes, I guess so." - }, - { - "time": "16:14:35", - "speaker": "Dominik Kapusta", - "text": "Why not? Right. All right. I linked it in the agenda, updated the link to the latest review. So, congrats on the promotion!" - }, - { - "time": "16:14:52", - "speaker": "Alex Martemyanov", - "text": "Thanks." - }, - { - "time": "16:14:52", - "speaker": "Dominik Kapusta", - "text": "Amazing, you made it." - }, - { - "time": "16:14:53", - "speaker": "Alex Martemyanov", - "text": "I guess it was a lot of your efforts." - }, - { - "time": "16:14:55", - "speaker": "Dominik Kapusta", - "text": "uh…" - }, - { - "time": "16:15:00", - "speaker": "Alex Martemyanov", - "text": "Involved to make it go through." - }, - { - "time": "16:15:06", - "speaker": "Dominik Kapusta", - "text": "Just a bit, really. It's, you know, this… this performance review time is overall great. I mean, I like it. I like… I like working on it, because it's, uh…" - }, - { - "time": "16:15:17", - "speaker": "Alex Martemyanov", - "text": "Bye." - }, - { - "time": "16:15:19", - "speaker": "Dominik Kapusta", - "text": "Um… okay. It's a great time. When you can appreciate people you work with and be able to do something for them. uh… make them… make their efforts visible and recognized. So, if that works, then that's great. This time it worked, so that's amazing. Uh, but… At the end of the day, it's just your work. put into the project. Uh, and, uh, and that got you… a bump in project management, which is amazing, which is… it's essentially hard facts, especially this year. If you look at the… if you look at the review… Format. It's… Like, dry facts. Nothing else, no pros, no…" - }, - { - "time": "16:16:13", - "speaker": "Alex Martemyanov", - "text": "Mm-hmm." - }, - { - "time": "16:16:15", - "speaker": "Dominik Kapusta", - "text": "Did a great job! everyone likes you, and so on and so on, like it used to be in the previous years. This time, it's, like, super, super concrete. With dates, with complexity assessments, with… The amount of direction needed." - }, - { - "time": "16:16:32", - "speaker": "Alex Martemyanov", - "text": "Mmhm." - }, - { - "time": "16:16:33", - "speaker": "Dominik Kapusta", - "text": "with clear impact stated in each bullet point. So it's just your work. distilled into a few sentences. So… Yeah, great job and keep doing that. I have to say… I have to say, I didn't ask for a promotion, because… I learned that these are the rules. The rules are, you have to have a star in all… in 4 out of 5 dimensions. So you would have to have a star in project management, and in… Team leadership. So I was like, okay, I would like to bump Alexa's project management. But I'm keeping the level at D, because… That's what the rules are, and the rules are in Asana. Um… These are the rules. Alex. There is a task about it. So I read through that task to be 100% sure that I'm doing the right thing, and I said. We have four stars in total, but not… in four dimensions, so it remains D. And everyone agreed with me. And then the calibration committee visited the review just on… it's actually last Friday afternoon. And they said, well, we decided to promote Alex based on that, because… Because we… that's what they thought would be the right thing, and also they are working on updating these rules here. to allow promotions in more, like, spiky profiles, when you have two stars somewhere, and no stars elsewhere. Uh, so…" - }, - { - "time": "16:18:26", - "speaker": "Alex Martemyanov", - "text": "Mm-hmm. No, I see." - }, - { - "time": "16:18:31", - "speaker": "Dominik Kapusta", - "text": "Yeah, that… that happened. Oh, actually…" - }, - { - "time": "16:18:31", - "speaker": "Alex Martemyanov", - "text": "Thank you." - }, - { - "time": "16:18:35", - "speaker": "Dominik Kapusta", - "text": "Oh, actually, there is a change in that. If you see… The latest edit in that task. there is a sentence added. In exceptional cases, someone may have spiky dimensions performing more than one level above the next level. these can balance out dimensions that are not yet at the next level and will be reviewed case by case. So, in your case, that warranted a promotion, so that's great. Um…" - }, - { - "time": "16:19:00", - "speaker": "Alex Martemyanov", - "text": "I see." - }, - { - "time": "16:19:01", - "speaker": "Dominik Kapusta", - "text": "All right, so we have this. Um, and… Well, you proved that you're… operating on the D-star level when it comes to project management. Um, and uh… Where is your review again? Yes. So we have this, we… I didn't have the… evidence to… ask… bump Team Leadership to the star, but this is something we should… focus on… In the coming year." - }, - { - "time": "16:19:48", - "speaker": "Alex Martemyanov", - "text": "Okay." - }, - { - "time": "16:19:48", - "speaker": "Dominik Kapusta", - "text": "And it will be… Tricky. Because you're not a project advisor. And it will be… Even trickier, because you may… In your current… Work. setting. It may be tricky for you to become a project advisor, but… Let's do whatever we can to try and push that. So, in short, to become a project advisor, you should probably be able to stay in a single objective for some time. On a positive side, we have 12 months. Or six months, let's say, until you're able to operate. to work as a project advisor and make impact, right? And also, I wanted to… Clarify that it's not required. It's not required that you grow to D-star in team leadership by next cycle. It would just be great, it would be the right thing. It's just what's missing in the distal level, so… So we should focus on that specifically. Uh, team leadership… is… Essentially about accelerating the work that is being done. And it's a quote from the Professional Levels PDF. Organizational leadership is accelerating how we work. overall, like, overall, and team leadership is accelerating the work that is currently being done. So, organizational leadership is figuring out new processes, or improving existing processes, and team leadership is finding people that. Struggle at a given time and helping them move forward." - }, - { - "time": "16:21:49", - "speaker": "Alex Martemyanov", - "text": "Mmhm." - }, - { - "time": "16:21:51", - "speaker": "Dominik Kapusta", - "text": "And, uh… the project advisor role fits here very, very well. So it's very easy, if you're a project advisor, if you're advising projects, then you can just help move projects forward. If you're not a project advisor, you can still do it. You can still do it, but it requires you to proactively go. Go through projects and see if there's something you can help somewhere. And I imagine… It can be very hard if… You're just starting out on that? So… and I'm also… You know, we have plenty of time. But, uh, it would be great to have. Some evidence of you doing things like that. In a year from now." - }, - { - "time": "16:22:44", - "speaker": "Alex Martemyanov", - "text": "Mm-hmm." - }, - { - "time": "16:22:47", - "speaker": "Dominik Kapusta", - "text": "Let's see, I'll try to… I'll be trying to… let you know about opportunities to do that." - }, - { - "time": "16:22:58", - "speaker": "Alex Martemyanov", - "text": "Okay, so…" - }, - { - "time": "16:22:58", - "speaker": "Dominik Kapusta", - "text": "You could also, if you have… Yeah, you could also, like… Look at some projects here and there. OL seems… straightforward, the most straightforward here. However, OL these days is about web extensions, mostly. And we seem to be covered there, but if there's anything… coming up in OL that I think would benefit from your help. Then the easiest is to just add yourself to the project and keep following whatever is happening there. Look at the subtasks. I don't know, help? help the DRI essentially move forward, um… And let's see how it goes. We'll… We will revisit growth areas, and also… Try to formulate something that… Not really, like, describes… What needs to happen? So that's team leadership, and that should be the main focus for next cycle. Uh, apart from that, just keep up your project management, and also getting to this start in project management, showing that you can… run projects smoothly and keep stakeholders up to date and essentially. yeah, do a good job as a… as a project DRI is… is something that will help you become a project advisor, I believe, uh, I'm sure. But the process… the process is that the ODRI selects new project advisors, and this is the main blocker now." - }, - { - "time": "16:24:36", - "speaker": "Alex Martemyanov", - "text": "Okay, yeah." - }, - { - "time": "16:24:44", - "speaker": "Dominik Kapusta", - "text": "So, just to end my speech… Even if you're… bored with… Uh, analyzing site breakage, or various types of breakage. Maybe if it's something that you have actually… Uh, you have a lot of experience in… maybe it would be… easier, helpful to… To stay in this area. If that's possible, if… You know, if staffing allows for that. Uh, and gain a little bit more depth. which would allow you to grow others, perhaps advise projects at some point. But let's see. For now… Take it easy. Take it easy. It's not that you have to start smashing it first week after the review. So yeah, wrap up your project. Let's see what comes next. If the next thing for you is OB, then I think it will be good. If not, we'll rearrange things and see how can we grow in." - }, - { - "time": "16:25:55", - "speaker": "Alex Martemyanov", - "text": "Mm-hmm." - }, - { - "time": "16:26:03", - "speaker": "Dominik Kapusta", - "text": "In a different setting, but yeah. That's what I wanted to say overall. What do you think about it?" - }, - { - "time": "16:26:10", - "speaker": "Alex Martemyanov", - "text": "Yeah, sounds wise, uh… I guess so. There is. some… opportunities to be looked for in the tech designs and. Some other projects that are ongoing, related to my expertise, and uh…" - }, - { - "time": "16:26:28", - "speaker": "Dominik Kapusta", - "text": "Yeah, totally." - }, - { - "time": "16:26:31", - "speaker": "Alex Martemyanov", - "text": "And… Yeah, let's look for… for the OB, uh… Next project." - }, - { - "time": "16:26:39", - "speaker": "Dominik Kapusta", - "text": "Mmhm." - }, - { - "time": "16:26:40", - "speaker": "Alex Martemyanov", - "text": "Maybe there's something that could be done." - }, - { - "time": "16:26:46", - "speaker": "Dominik Kapusta", - "text": "Cool. Cool, cool, cool. That's, that sounds good. All right, and with that, like I said, for now, let's just see what happens. Let's see where you land next next week. Mmhm. And I think that's all I had. Can I help you with anything? Is there anything you wanted to… Raise. talk about." - }, - { - "time": "16:27:22", - "speaker": "Alex Martemyanov", - "text": "Okay. I… I don't know. Not really, not anything. In this tech, um…" - }, - { - "time": "16:27:48", - "speaker": "Dominik Kapusta", - "text": "That's fine. That's fine." - }, - { - "time": "16:27:52", - "speaker": "Alex Martemyanov", - "text": "So, yeah, there was, uh, some work, like, kinda planned for, uh, the UI test runners and, uh, all this stuff, but, uh… I'm… At the moment, I'm not doing anything related to it, just completing the TPM." - }, - { - "time": "16:28:09", - "speaker": "Dominik Kapusta", - "text": "Mm-hmm." - }, - { - "time": "16:28:10", - "speaker": "Alex Martemyanov", - "text": "Um, the open… They opened, they already closed pull requests that I need to complete and. That's… that's all that's on my plate. At the moment, so I'm planning to move forward with this." - }, - { - "time": "16:28:28", - "speaker": "Dominik Kapusta", - "text": "Mmhm." - }, - { - "time": "16:28:28", - "speaker": "Alex Martemyanov", - "text": "organizational leadership stuff." - }, - { - "time": "16:28:32", - "speaker": "Dominik Kapusta", - "text": "Okay." - }, - { - "time": "16:28:32", - "speaker": "Alex Martemyanov", - "text": "But not… not right now." - }, - { - "time": "16:28:37", - "speaker": "Dominik Kapusta", - "text": "Sure, sure. I mean, that's fine. Totally fine to… Like I said, to take it easy for now. Um, alright, uh…" - }, - { - "time": "16:28:52", - "speaker": "Alex Martemyanov", - "text": "I mean, for sure, I… I will need to, uh, sync up with you, and… On that area, when I get my hands on it." - }, - { - "time": "16:29:00", - "speaker": "Dominik Kapusta", - "text": "Mm-hmm. Yeah, yeah, we can do it next." - }, - { - "time": "16:29:03", - "speaker": "Alex Martemyanov", - "text": "But yeah, just not ready." - }, - { - "time": "16:29:05", - "speaker": "Dominik Kapusta", - "text": "next week, um… Later. Should be fine. All right, all right." - }, - { - "time": "16:29:15", - "speaker": "Alex Martemyanov", - "text": "Thank you." - }, - { - "time": "16:29:20", - "speaker": "Dominik Kapusta", - "text": "Good. So if nothing else, we can wrap it up here. I don't have any other announcements, any other important info. I'm also… deep down in my project, trying to open a ship review today, so let's see. And then I'm taking 3 days off, finally. So I'll be back next week." - }, - { - "time": "16:29:43", - "speaker": "Alex Martemyanov", - "text": "Okay." - }, - { - "time": "16:29:43", - "speaker": "Dominik Kapusta", - "text": "But we'll see each other weekly. If I know anything from Jonathan, I'll let you know. Because I'm curious myself. So let's see. Good. If that's it, we can wrap it up here. Congrats again. You're doing a great job. It's a pleasure to be working with you, and yeah, we'll keep smashing it, hopefully, starting next week." - }, - { - "time": "16:30:05", - "speaker": "Alex Martemyanov", - "text": "Thanks." - }, - { - "time": "16:30:12", - "speaker": "Dominik Kapusta", - "text": "Awesome." - }, - { - "time": "16:30:13", - "speaker": "Alex Martemyanov", - "text": "Okay." - }, - { - "time": "16:30:14", - "speaker": "Dominik Kapusta", - "text": "Thank you. Thanks and have a great rest of the day. See ya." } ] } diff --git a/work/zoom-transcripts/undated Dominik Kapusta's Personal Meeting Room p5FdcX9WT-afBpWjRgaW0w/transcript.md b/work/zoom-transcripts/undated Dominik Kapusta's Personal Meeting Room p5FdcX9WT-afBpWjRgaW0w/transcript.md index 3a5780f0..3f35b848 100644 --- a/work/zoom-transcripts/undated Dominik Kapusta's Personal Meeting Room p5FdcX9WT-afBpWjRgaW0w/transcript.md +++ b/work/zoom-transcripts/undated Dominik Kapusta's Personal Meeting Room p5FdcX9WT-afBpWjRgaW0w/transcript.md @@ -15,130 +15,3 @@ source: "https://us01mynotes.zoom.us/p5FdcX9WT-afBpWjRgaW0w" - **16:01:44 · Dominik Kapusta:** Is it going. - **16:01:46 · Alex Martemyanov:** And then… I'm pretty good. Thank you. After you… after last week's, uh… I was… So all this RKAFK, so I'm… Wrapping up the top priority project. Mostly, mostly it finally merged the link tooltip thing from the Hug days. - **16:02:10 · Dominik Kapusta:** Jest. -- **16:02:13 · Alex Martemyanov:** And basically no progress on other stuff yet. -- **16:02:19 · Alex Martemyanov:** I need to finish the priority cleanup. So basically last week we've discussed it during the OE that we should. Basically wrap up the project with the. No visible outcomes. There was a slight decline in the numbers and several genuine bugs fixed, but they were not representing the main feature breakage. -- **16:02:45 · Dominik Kapusta:** Nie. Drop, Ios. -- **16:02:50 · Alex Martemyanov:** I know. -- **16:02:57 · Dominik Kapusta:** Łazać. -- **16:03:00 · Alex Martemyanov:** There was some decline, maybe a third. So there was a decline in some part. of the numbers, but there is still around 40%. of the event sequence of the received events that so basically most of it is. The data we received for most of the breakage pixels represents just regular normal flow and nothing obviously. -- **16:03:34 · Dominik Kapusta:** Bardzo. -- **16:03:34 · Alex Martemyanov:** pointing to anything. So the discussion during the OE was to basically clean up the inefficient fixes that we've got. The feature flags for the features that are removed and some. Um, like the pinned tabs management fix, uh, that are, um, staying without the feature flag. And, uh… Yeah, clean up the data that's being collected, because we've collected enough of it, and, uh, implement some permanent data collection that stays there for, uh. for diagnostics for the future possible breakages. And try to add some in. inside of the extension, some metrics inside of the extension to, um, to track the loading progress, basically. Where we… where do we stop, and where the messaging. -- **16:04:23 · Dominik Kapusta:** Ok. -- **16:04:31 · Alex Martemyanov:** Stops. and try to reason about it from from that perspective. -- **16:04:37 · Dominik Kapusta:** Misji. -- **16:04:39 · Alex Martemyanov:** So, uh… So yeah, probably today I'm going to open the featured slugs and clean up PR. And. later this week will complete. So I've updated the project, moving on the post-mortem to the next week, since last week I had no time to. completed due to some circumstances. And, uh… That's mostly it. I still got some. PRs requiring my attention, like the crash reporting fix. So, yeah, no updates since last week. On it. So, basically, my concern about it is, uh, we may, uh, we may break the existing macOS collection while fixing iOS collection, so I need to… reproduce it, reproduce the crash and. this slowdown condition and normal conditions and see how it if it still works and nothing breaks and then I'll proceed with it. -- **16:05:49 · Dominik Kapusta:** Collection as in… -- **16:05:52 · Alex Martemyanov:** The App Store reports. -- **16:05:53 · Dominik Kapusta:** Crosscode? Yeah, cross-collection, mhm. -- **16:05:57 · Alex Martemyanov:** Yeah, so matching against process identifier or by date. -- **16:06:02 · Dominik Kapusta:** Yeah. Yeah, yeah, yeah, yeah. -- **16:06:05 · Alex Martemyanov:** Mmm. -- **16:06:05 · Dominik Kapusta:** Oh. Right. -- **16:06:14 · Alex Martemyanov:** And… That is it, I guess, so… I'm. I'm not top performing for the last week. So just… Just completing the TP stuff. -- **16:06:35 · Dominik Kapusta:** Yeah, which is… -- **16:06:36 · Alex Martemyanov:** And yeah, there was… -- **16:06:38 · Dominik Kapusta:** Expected. -- **16:06:39 · Alex Martemyanov:** And there was the maintenance, the release maintenance. Luckily, it was growing weak. -- **16:06:46 · Dominik Kapusta:** Mm-hmm. -- **16:06:47 · Alex Martemyanov:** So nothing else ended from it. -- **16:06:48 · Dominik Kapusta:** I saw that, yeah, that's good, that's good. All right. Nice. That's fine. So you're going to wrap up your project. Will you run the postmortem this week or next week? -- **16:07:05 · Alex Martemyanov:** Next week, next week. -- **16:07:06 · Dominik Kapusta:** Next week. Mm-hmm. Okay. -- **16:07:07 · Alex Martemyanov:** So this week, I'm, uh… Completing the cleanup. And the next week is time for the postmortem. -- **16:07:18 · Dominik Kapusta:** Sounds good. Alright, and then… Do you have… Do you know anything about… You're next. Top priority? -- **16:07:32 · Alex Martemyanov:** Uh, nope. -- **16:07:35 · Dominik Kapusta:** Yeah, because there won't be any follow-up… there won't be any follow-up in OE for… -- **16:07:35 · Alex Martemyanov:** I guess I should make one. -- **16:07:41 · Dominik Kapusta:** For this. I mean… -- **16:07:44 · Alex Martemyanov:** Well, I guess not, at least for the moment. -- **16:07:45 · Dominik Kapusta:** Immediate follow up at least. Yeah, yeah, yeah. -- **16:07:49 · Alex Martemyanov:** And, uh… So if we are shifting the diagnostics into the JavaScript part, it's probably… due to some someone else to. Keep up with it. -- **16:08:05 · Dominik Kapusta:** No. -- **16:08:05 · Alex Martemyanov:** So maybe there will be a follow-up task to perform the data analysis next week. -- **16:08:12 · Dominik Kapusta:** Mm-hmm. -- **16:08:12 · Alex Martemyanov:** So just one, one cloud shot. To fetch the data, to perform the analysis, to see the trends, and if… Anything new is highlighted from it. So I could person. Wrap up up a date. And that's it. And it goes after. -- **16:08:29 · Dominik Kapusta:** Yeah, yeah. -- **16:08:31 · Alex Martemyanov:** Two weeks from now, I guess, when the release is out. -- **16:08:39 · Dominik Kapusta:** All right, fine, we'll need to learn what's next for you. When would you be opening? When would you be opening a top priority, Fred? -- **16:08:47 · Alex Martemyanov:** Gosh. Probably now. -- **16:08:53 · Dominik Kapusta:** Yep. -- **16:08:55 · Alex Martemyanov:** It's really, it's a good time. -- **16:08:55 · Dominik Kapusta:** Okay. Okay, this is interesting then. There will be some work. shaping up in OB. If you're up for it, that may be interesting. I'm not sure how much native support they need, but… It is… considered a big problem these days, and that's the fact that all the JavaScript code injected into our websites causes performance issues. And side breakage. But… Yeah, well, both of them, essentially. And I'm, like I said, I'm not sure… If… A native engineer would be needed immediately. But if so, then… that… That would be very important. So this is very important. And… Let me see… So the assessment is this Thursday. And the projects… Okay. Let's see. Let's see. I see there is a… So this is the assessment task. And there is a subtask for the… staffing for the Apple team, so it sounds like they will need… they will need someone from the Apple team. This is not finalized yet, but… But, uh… Should probably be… should probably be… filled out today, I hope. I'll have the proposed critical path and Gantt chart ready for review on Tuesday. I'm proposing OB focus on performance this cycle, specifically the cost of the JS and config we inject into every frame. -- **16:11:21 · Alex Martemyanov:** Thank you. -- **16:11:21 · Dominik Kapusta:** They may at least need someone on the native side to, I don't know, implement some. measurements. I suppose. If this is something that… would be of interest to you, then that's great, because if not, I think you will still be mentioned there. What do you think? -- **16:11:58 · Alex Martemyanov:** Visibility. What is this discussion? That you mentioned. -- **16:12:04 · Dominik Kapusta:** I was just reading the last comment in the thread. -- **16:12:07 · Alex Martemyanov:** Okay. -- **16:12:08 · Dominik Kapusta:** From Dave. -- **16:12:22 · Alex Martemyanov:** Mmm… Well, looking at my current TP, if it can be reproduced, it would be more of a… something that I would be interested in, if… And if it's something like we got some breakage to fix it. Not so exciting, I'd say. -- **16:12:52 · Dominik Kapusta:** Yeah, yeah, yeah, I can tell. I can tell. This, however, should be easier. On the functional side, on the technical side, it should be easier. at least from… -- **16:13:10 · Alex Martemyanov:** Yeah, at least if there is exact cases reported on or some exact websites. -- **16:13:13 · Dominik Kapusta:** Yeah, I know. Uh, it may be… it may be about… it may be about just measuring things. -- **16:13:17 · Alex Martemyanov:** It should be easier. -- **16:13:22 · Dominik Kapusta:** So that front-end engineers can… Do changes, make changes. But I don't know. I don't know the details. Let's see. Trim the Apple Cs. Bundle and isolated world. -- **16:13:37 · Alex Martemyanov:** Okay, I'm fine to get mentioned on the thread, and so for the next TP, I'll probably open it on Thursday, I guess. -- **16:13:38 · Dominik Kapusta:** Interesting. Mmhm. -- **16:13:47 · Alex Martemyanov:** Makes sense. -- **16:13:49 · Dominik Kapusta:** Yeah, probably. I think it makes a lot of sense. I will be AFK for the rest of the week. Um, Bob… -- **16:13:57 · Alex Martemyanov:** Mm-hmm. -- **16:13:59 · Dominik Kapusta:** It's not a problem, of course. Um… I will try to… Try to reach out to Jonathan to ask. If he knows anything about OB plans for a pool. Or if he knows anything about anything else. Any other objective that might need Apple people and I'll let you know. Do you want to talk about your performance review? -- **16:14:31 · Alex Martemyanov:** Uh, yes, I guess so. -- **16:14:35 · Dominik Kapusta:** Why not? Right. All right. I linked it in the agenda, updated the link to the latest review. So, congrats on the promotion! -- **16:14:52 · Alex Martemyanov:** Thanks. -- **16:14:52 · Dominik Kapusta:** Amazing, you made it. -- **16:14:53 · Alex Martemyanov:** I guess it was a lot of your efforts. -- **16:14:55 · Dominik Kapusta:** uh… -- **16:15:00 · Alex Martemyanov:** Involved to make it go through. -- **16:15:06 · Dominik Kapusta:** Just a bit, really. It's, you know, this… this performance review time is overall great. I mean, I like it. I like… I like working on it, because it's, uh… -- **16:15:17 · Alex Martemyanov:** Bye. -- **16:15:19 · Dominik Kapusta:** Um… okay. It's a great time. When you can appreciate people you work with and be able to do something for them. uh… make them… make their efforts visible and recognized. So, if that works, then that's great. This time it worked, so that's amazing. Uh, but… At the end of the day, it's just your work. put into the project. Uh, and, uh, and that got you… a bump in project management, which is amazing, which is… it's essentially hard facts, especially this year. If you look at the… if you look at the review… Format. It's… Like, dry facts. Nothing else, no pros, no… -- **16:16:13 · Alex Martemyanov:** Mm-hmm. -- **16:16:15 · Dominik Kapusta:** Did a great job! everyone likes you, and so on and so on, like it used to be in the previous years. This time, it's, like, super, super concrete. With dates, with complexity assessments, with… The amount of direction needed. -- **16:16:32 · Alex Martemyanov:** Mmhm. -- **16:16:33 · Dominik Kapusta:** with clear impact stated in each bullet point. So it's just your work. distilled into a few sentences. So… Yeah, great job and keep doing that. I have to say… I have to say, I didn't ask for a promotion, because… I learned that these are the rules. The rules are, you have to have a star in all… in 4 out of 5 dimensions. So you would have to have a star in project management, and in… Team leadership. So I was like, okay, I would like to bump Alexa's project management. But I'm keeping the level at D, because… That's what the rules are, and the rules are in Asana. Um… These are the rules. Alex. There is a task about it. So I read through that task to be 100% sure that I'm doing the right thing, and I said. We have four stars in total, but not… in four dimensions, so it remains D. And everyone agreed with me. And then the calibration committee visited the review just on… it's actually last Friday afternoon. And they said, well, we decided to promote Alex based on that, because… Because we… that's what they thought would be the right thing, and also they are working on updating these rules here. to allow promotions in more, like, spiky profiles, when you have two stars somewhere, and no stars elsewhere. Uh, so… -- **16:18:26 · Alex Martemyanov:** Mm-hmm. No, I see. -- **16:18:31 · Dominik Kapusta:** Yeah, that… that happened. Oh, actually… -- **16:18:31 · Alex Martemyanov:** Thank you. -- **16:18:35 · Dominik Kapusta:** Oh, actually, there is a change in that. If you see… The latest edit in that task. there is a sentence added. In exceptional cases, someone may have spiky dimensions performing more than one level above the next level. these can balance out dimensions that are not yet at the next level and will be reviewed case by case. So, in your case, that warranted a promotion, so that's great. Um… -- **16:19:00 · Alex Martemyanov:** I see. -- **16:19:01 · Dominik Kapusta:** All right, so we have this. Um, and… Well, you proved that you're… operating on the D-star level when it comes to project management. Um, and uh… Where is your review again? Yes. So we have this, we… I didn't have the… evidence to… ask… bump Team Leadership to the star, but this is something we should… focus on… In the coming year. -- **16:19:48 · Alex Martemyanov:** Okay. -- **16:19:48 · Dominik Kapusta:** And it will be… Tricky. Because you're not a project advisor. And it will be… Even trickier, because you may… In your current… Work. setting. It may be tricky for you to become a project advisor, but… Let's do whatever we can to try and push that. So, in short, to become a project advisor, you should probably be able to stay in a single objective for some time. On a positive side, we have 12 months. Or six months, let's say, until you're able to operate. to work as a project advisor and make impact, right? And also, I wanted to… Clarify that it's not required. It's not required that you grow to D-star in team leadership by next cycle. It would just be great, it would be the right thing. It's just what's missing in the distal level, so… So we should focus on that specifically. Uh, team leadership… is… Essentially about accelerating the work that is being done. And it's a quote from the Professional Levels PDF. Organizational leadership is accelerating how we work. overall, like, overall, and team leadership is accelerating the work that is currently being done. So, organizational leadership is figuring out new processes, or improving existing processes, and team leadership is finding people that. Struggle at a given time and helping them move forward. -- **16:21:49 · Alex Martemyanov:** Mmhm. -- **16:21:51 · Dominik Kapusta:** And, uh… the project advisor role fits here very, very well. So it's very easy, if you're a project advisor, if you're advising projects, then you can just help move projects forward. If you're not a project advisor, you can still do it. You can still do it, but it requires you to proactively go. Go through projects and see if there's something you can help somewhere. And I imagine… It can be very hard if… You're just starting out on that? So… and I'm also… You know, we have plenty of time. But, uh, it would be great to have. Some evidence of you doing things like that. In a year from now. -- **16:22:44 · Alex Martemyanov:** Mm-hmm. -- **16:22:47 · Dominik Kapusta:** Let's see, I'll try to… I'll be trying to… let you know about opportunities to do that. -- **16:22:58 · Alex Martemyanov:** Okay, so… -- **16:22:58 · Dominik Kapusta:** You could also, if you have… Yeah, you could also, like… Look at some projects here and there. OL seems… straightforward, the most straightforward here. However, OL these days is about web extensions, mostly. And we seem to be covered there, but if there's anything… coming up in OL that I think would benefit from your help. Then the easiest is to just add yourself to the project and keep following whatever is happening there. Look at the subtasks. I don't know, help? help the DRI essentially move forward, um… And let's see how it goes. We'll… We will revisit growth areas, and also… Try to formulate something that… Not really, like, describes… What needs to happen? So that's team leadership, and that should be the main focus for next cycle. Uh, apart from that, just keep up your project management, and also getting to this start in project management, showing that you can… run projects smoothly and keep stakeholders up to date and essentially. yeah, do a good job as a… as a project DRI is… is something that will help you become a project advisor, I believe, uh, I'm sure. But the process… the process is that the ODRI selects new project advisors, and this is the main blocker now. -- **16:24:36 · Alex Martemyanov:** Okay, yeah. -- **16:24:44 · Dominik Kapusta:** So, just to end my speech… Even if you're… bored with… Uh, analyzing site breakage, or various types of breakage. Maybe if it's something that you have actually… Uh, you have a lot of experience in… maybe it would be… easier, helpful to… To stay in this area. If that's possible, if… You know, if staffing allows for that. Uh, and gain a little bit more depth. which would allow you to grow others, perhaps advise projects at some point. But let's see. For now… Take it easy. Take it easy. It's not that you have to start smashing it first week after the review. So yeah, wrap up your project. Let's see what comes next. If the next thing for you is OB, then I think it will be good. If not, we'll rearrange things and see how can we grow in. -- **16:25:55 · Alex Martemyanov:** Mm-hmm. -- **16:26:03 · Dominik Kapusta:** In a different setting, but yeah. That's what I wanted to say overall. What do you think about it? -- **16:26:10 · Alex Martemyanov:** Yeah, sounds wise, uh… I guess so. There is. some… opportunities to be looked for in the tech designs and. Some other projects that are ongoing, related to my expertise, and uh… -- **16:26:28 · Dominik Kapusta:** Yeah, totally. -- **16:26:31 · Alex Martemyanov:** And… Yeah, let's look for… for the OB, uh… Next project. -- **16:26:39 · Dominik Kapusta:** Mmhm. -- **16:26:40 · Alex Martemyanov:** Maybe there's something that could be done. -- **16:26:46 · Dominik Kapusta:** Cool. Cool, cool, cool. That's, that sounds good. All right, and with that, like I said, for now, let's just see what happens. Let's see where you land next next week. Mmhm. And I think that's all I had. Can I help you with anything? Is there anything you wanted to… Raise. talk about. -- **16:27:22 · Alex Martemyanov:** Okay. I… I don't know. Not really, not anything. In this tech, um… -- **16:27:48 · Dominik Kapusta:** That's fine. That's fine. -- **16:27:52 · Alex Martemyanov:** So, yeah, there was, uh, some work, like, kinda planned for, uh, the UI test runners and, uh, all this stuff, but, uh… I'm… At the moment, I'm not doing anything related to it, just completing the TPM. -- **16:28:09 · Dominik Kapusta:** Mm-hmm. -- **16:28:10 · Alex Martemyanov:** Um, the open… They opened, they already closed pull requests that I need to complete and. That's… that's all that's on my plate. At the moment, so I'm planning to move forward with this. -- **16:28:28 · Dominik Kapusta:** Mmhm. -- **16:28:28 · Alex Martemyanov:** organizational leadership stuff. -- **16:28:32 · Dominik Kapusta:** Okay. -- **16:28:32 · Alex Martemyanov:** But not… not right now. -- **16:28:37 · Dominik Kapusta:** Sure, sure. I mean, that's fine. Totally fine to… Like I said, to take it easy for now. Um, alright, uh… -- **16:28:52 · Alex Martemyanov:** I mean, for sure, I… I will need to, uh, sync up with you, and… On that area, when I get my hands on it. -- **16:29:00 · Dominik Kapusta:** Mm-hmm. Yeah, yeah, we can do it next. -- **16:29:03 · Alex Martemyanov:** But yeah, just not ready. -- **16:29:05 · Dominik Kapusta:** next week, um… Later. Should be fine. All right, all right. -- **16:29:15 · Alex Martemyanov:** Thank you. -- **16:29:20 · Dominik Kapusta:** Good. So if nothing else, we can wrap it up here. I don't have any other announcements, any other important info. I'm also… deep down in my project, trying to open a ship review today, so let's see. And then I'm taking 3 days off, finally. So I'll be back next week. -- **16:29:43 · Alex Martemyanov:** Okay. -- **16:29:43 · Dominik Kapusta:** But we'll see each other weekly. If I know anything from Jonathan, I'll let you know. Because I'm curious myself. So let's see. Good. If that's it, we can wrap it up here. Congrats again. You're doing a great job. It's a pleasure to be working with you, and yeah, we'll keep smashing it, hopefully, starting next week. -- **16:30:05 · Alex Martemyanov:** Thanks. -- **16:30:12 · Dominik Kapusta:** Awesome. -- **16:30:13 · Alex Martemyanov:** Okay. -- **16:30:14 · Dominik Kapusta:** Thank you. Thanks and have a great rest of the day. See ya. diff --git a/work/zoom-transcripts/undated Max Tsoy's Personal Meeting Room DLwAbUQ_RZ6X_D63xiX_Ww/transcript.json b/work/zoom-transcripts/undated Max Tsoy's Personal Meeting Room DLwAbUQ_RZ6X_D63xiX_Ww/transcript.json index 80874e3b..38585322 100644 --- a/work/zoom-transcripts/undated Max Tsoy's Personal Meeting Room DLwAbUQ_RZ6X_D63xiX_Ww/transcript.json +++ b/work/zoom-transcripts/undated Max Tsoy's Personal Meeting Room DLwAbUQ_RZ6X_D63xiX_Ww/transcript.json @@ -23,566 +23,6 @@ "time": "15:55:00", "speaker": "Max Tsoy", "text": "Yes, but still, like, I would expect… it's… it's not… it's all breakage reports, right? So… Yes, it is filtered by people who report something, but it's still a signal and it's not related to what kind of breakage report it is." - }, - { - "time": "15:55:21", - "speaker": "Michal Smaga", - "text": "And you filter by the macOS version as well, right?" - }, - { - "time": "15:55:24", - "speaker": "Max Tsoy", - "text": "Um… I think so. Yes, it's a stacked thing. It's in the same… in the same… Dashboards. Uh, this one. Right, so, uh, it's hidden under CPM diagnostics. Role." - }, - { - "time": "15:55:51", - "speaker": "Alex Martemyanov", - "text": "Yeah, and just answered in your removed breakage diagnostic thread. And yeah, I basically asked Claude to check the breakages and related reports." - }, - { - "time": "15:55:51", - "speaker": "Max Tsoy", - "text": "That's what I… Mm-hmm. Oh. Okay. Good." - }, - { - "time": "15:56:06", - "speaker": "Alex Martemyanov", - "text": "So, it highlighted that, uh… The baseline is basically the same with the waiting signal, but there is a new report categories. Uh, that may be affecting, uh. that weighting metric and." - }, - { - "time": "15:56:24", - "speaker": "Max Tsoy", - "text": "Okay, so…" - }, - { - "time": "15:56:27", - "speaker": "Alex Martemyanov", - "text": "So…" - }, - { - "time": "15:56:27", - "speaker": "Max Tsoy", - "text": "So we… we got more reports?" - }, - { - "time": "15:56:29", - "speaker": "Alex Martemyanov", - "text": "if there is a report flow on the error page, uh, which basically has no, uh, CPM running on it, and we've been affected, uh, with it with the, uh, CPM breakage pixels as well, uh, because, uh, they're not run on determination and there are pages on macOS." - }, - { - "time": "15:56:37", - "speaker": "Max Tsoy", - "text": "Okay." - }, - { - "time": "15:56:47", - "speaker": "Alex Martemyanov", - "text": "And if we exclude the report flow for the error page, it stays steady basically. And answering your treatment effect question, yeah, basically it was not…" - }, - { - "time": "15:56:53", - "speaker": "Max Tsoy", - "text": "Okay, okay." - }, - { - "time": "15:57:02", - "speaker": "Alex Martemyanov", - "text": "lowering much, not affecting much the overall breakage signal magic." - }, - { - "time": "15:57:08", - "speaker": "Max Tsoy", - "text": "Mm-hmm. Okay, so…" - }, - { - "time": "15:57:10", - "speaker": "Alex Martemyanov", - "text": "Because the main signal still stays in the seemingly normal flow as the metrics shown." - }, - { - "time": "15:57:17", - "speaker": "Max Tsoy", - "text": "Right. Okay, so basically, the increase is probably driven by something else, but there was no decrease either. Um…" - }, - { - "time": "15:57:30", - "speaker": "Alex Martemyanov", - "text": "There was a… Probably less than a percent decrease and there's still fluctuation depending on a week measured, so we can tell for sure." - }, - { - "time": "15:57:34", - "speaker": "Max Tsoy", - "text": "Yeah, yeah. Okay. Got it. Okay, so, uh, uh, alright, now, uh, I'm looking at your tech design, and my main question there is, do we… Do we not already have this? Because… so the tech design is basically proposing to send more, like, status reports from the extension." - }, - { - "time": "15:58:04", - "speaker": "Alex Martemyanov", - "text": "Yep." - }, - { - "time": "15:58:05", - "speaker": "Max Tsoy", - "text": "But we already have one signal, which is exactly the same thing, actually. So, if you look at this old… that design. that introduced that… other signal. So, the CPM dashboard state… Uh, specifically. Um… So basically, immediately after navigation, we set the CPM dashboard state to waiting in native code. And then… The first thing that… The extension does. After it gets… after it injects the content script. it's… initializes, and then… Almost immediately sends back the refresh CPM dashboard state. So… The problem is that. In the error state, this message is not received. So… Like, what you're proposing there… I think you will just not receive. Most of these messages. And that's the whole point of problem, right? So, like. Um… I don't think it's a problem of the granularity. It's basically that in this error state, we don't get. Any response?" - }, - { - "time": "15:59:37", - "speaker": "Alex Martemyanov", - "text": "Mmhm." - }, - { - "time": "15:59:37", - "speaker": "Max Tsoy", - "text": "So, it kind of looks like the messaging is broken. And that's the whole reason, right? Like, we don't know what's happening. Is the extension stuck? Is it just the messaging that doesn't get through, or is it the… You know, the whole… Thing doesn't work." - }, - { - "time": "15:59:55", - "speaker": "Alex Martemyanov", - "text": "I think it was mainly based on the, um… In the state that may be pending before we send the… The repair is unmarked state. Like, uh, for example, the config, uh, the config update state." - }, - { - "time": "16:00:09", - "speaker": "Max Tsoy", - "text": "Right." - }, - { - "time": "16:00:14", - "speaker": "Alex Martemyanov", - "text": "or. And. What else was there? Let me just open it." - }, - { - "time": "16:00:21", - "speaker": "Max Tsoy", - "text": "Right, so basically you're suggesting that within that initialization, maybe it gets stuck. In between these first… so, what we could do…" - }, - { - "time": "16:00:28", - "speaker": "Alex Martemyanov", - "text": "Yes, yes." - }, - { - "time": "16:00:32", - "speaker": "Max Tsoy", - "text": "We could just send one message. Immediately, like, on… On wake up. And I think we actually already do. Uh, don't we, like, there is some… I don't know, um, I don't remember exactly, but the… I think there was… so… What I'm saying is that I don't know if the, uh, all these other stages are… Um… useful, because I think it… the problem is that we… I suspect we won't get the first message, even." - }, - { - "time": "16:01:07", - "speaker": "Alex Martemyanov", - "text": "Maybe, but… Probably we don't know." - }, - { - "time": "16:01:15", - "speaker": "Max Tsoy", - "text": "So we have this… the first…" - }, - { - "time": "16:01:15", - "speaker": "Alex Martemyanov", - "text": "So here we kind of add no wait, so there is no await, it's kind of asynchronously as soon as we…" - }, - { - "time": "16:01:24", - "speaker": "Max Tsoy", - "text": "Mm-hmm." - }, - { - "time": "16:01:26", - "speaker": "Alex Martemyanov", - "text": "Wake of the script wakes. Unless so first. Yeah, so there is the stage for, like, no, nothing was received, then, uh… H script in it. There may be possible hang on the config read, and if it hangs for whatever reason, it won't get through and won't get to the dashboard update state. Uh, so the suggestion is, like, sending, uh… And… log messages to… To set the list. Received state. that we could report in the main CPM breakage pixel." - }, - { - "time": "16:02:15", - "speaker": "Max Tsoy", - "text": "Yeah, um…" - }, - { - "time": "16:02:16", - "speaker": "Alex Martemyanov", - "text": "I see." - }, - { - "time": "16:02:18", - "speaker": "Max Tsoy", - "text": "Well, then I would… I would suggest just to trim it down to, like, the very first. signal, because… Um, I think for the rest, we actually… we have some… We have the CPM stage thing, right? Which is kind of… the same. Um… So, the last tech design that they shared? Um, there is this, yeah." - }, - { - "time": "16:02:48", - "speaker": "Michal Smaga", - "text": "Yeah, Max, just to clarify, I'm not up to date because, like, I'm still catching up after yesterday, so I haven't read the new tech design." - }, - { - "time": "16:02:53", - "speaker": "Max Tsoy", - "text": "Yeah." - }, - { - "time": "16:02:55", - "speaker": "Michal Smaga", - "text": "But, the goal is to, like, remove the old metrics like that, that were, like, very detailed and, like, very precise. Get rid of that just because of privacy reasons and, like, to implement the new ones." - }, - { - "time": "16:03:01", - "speaker": "Max Tsoy", - "text": "Mm-hmm, mm-hmm." - }, - { - "time": "16:03:04", - "speaker": "Alex Martemyanov", - "text": "Sweet. We may be not at the same page because I've just opened another tech design I wanted to discuss. And, uh, yes, so basically, uh, I suggest to remove, uh, all the old metrics and, uh, this recorder thing, and, uh, delegate, uh, proxy." - }, - { - "time": "16:03:24", - "speaker": "Max Tsoy", - "text": "Okay." - }, - { - "time": "16:03:28", - "speaker": "Alex Martemyanov", - "text": "And basically the only basic metric that would relate page committed state to the dashboard update." - }, - { - "time": "16:03:37", - "speaker": "Max Tsoy", - "text": "Mm-hmm, mm-h." - }, - { - "time": "16:03:38", - "speaker": "Alex Martemyanov", - "text": "Uh, message. So if we don't receive it within, uh, 30 seconds, uh, we…" - }, - { - "time": "16:03:45", - "speaker": "Michal Smaga", - "text": "Record the stacks that you want." - }, - { - "time": "16:03:45", - "speaker": "Alex Martemyanov", - "text": "So we expect to receive it. Yeah, but… before we navigate to another page, or before we close this tab. And if the page was alive for longer than 30 seconds, so basically it was measured, there were some cases when the dashboard update received after 30 seconds." - }, - { - "time": "16:04:01", - "speaker": "Max Tsoy", - "text": "Mm-hmm." - }, - { - "time": "16:04:06", - "speaker": "Alex Martemyanov", - "text": "It's for loading, because of, um… getting load, or whatever. And, uh, so if we navigate from the page, and, uh, it never received, uh, anything, and the page was active more than 30 seconds, we send a metric of the page of CPM hand. And if it was, uh, caught on another job." - }, - { - "time": "16:04:22", - "speaker": "Max Tsoy", - "text": "Mm-hmm." - }, - { - "time": "16:04:27", - "speaker": "Alex Martemyanov", - "text": "After it, we send the permanent breakage." - }, - { - "time": "16:04:28", - "speaker": "Max Tsoy", - "text": "Right." - }, - { - "time": "16:04:31", - "speaker": "Alex Martemyanov", - "text": "There was another issue of matching tab against actual… web extension tab against actual tab that we are measuring, because if we open the same page in two tabs, it basically can match both. Ahm. there is the tab index, and there is window ID that we cannot access from the app itself, but there is, like, a heuristics that allow us match it if we send all the window IDs. Um, so WebKit gives the window an ID in, uh… Consequently, it's not zero-based. It may be like 44, 72, and so on, but they are always ordered consequently as they are received from the app itself. And if we send these IDs from the script, we can match exact window and exact tab that the message is meant for." - }, - { - "time": "16:05:32", - "speaker": "Max Tsoy", - "text": "Wait, wait, sorry, are you saying, uh… Are you saying we can match… we can map the extension tab ID to the native tab ID?" - }, - { - "time": "16:05:39", - "speaker": "Alex Martemyanov", - "text": "Yes. Yes. Yes." - }, - { - "time": "16:05:43", - "speaker": "Max Tsoy", - "text": "Oh, that's a, that's a great thing. I, uh, I." - }, - { - "time": "16:05:45", - "speaker": "Alex Martemyanov", - "text": "So I was breaking my head the last three days on how could we actually match it to…" - }, - { - "time": "16:05:45", - "speaker": "Michal Smaga", - "text": "Yeah, we…" - }, - { - "time": "16:05:52", - "speaker": "Alex Martemyanov", - "text": "To avoid, uh, false positives." - }, - { - "time": "16:05:52", - "speaker": "Max Tsoy", - "text": "We have a separate, like. Separate tests somewhere we have that, uh… But how would it work in a nutshell again?" - }, - { - "time": "16:06:00", - "speaker": "Alex Martemyanov", - "text": "Yeah, basically we have a tab index that we set for the tab in the window." - }, - { - "time": "16:06:07", - "speaker": "Max Tsoy", - "text": "Yes." - }, - { - "time": "16:06:08", - "speaker": "Alex Martemyanov", - "text": "Oh, it's, uh…" - }, - { - "time": "16:06:09", - "speaker": "Max Tsoy", - "text": "Huh?" - }, - { - "time": "16:06:11", - "speaker": "Michal Smaga", - "text": "A native one." - }, - { - "time": "16:06:13", - "speaker": "Alex Martemyanov", - "text": "the tab collection index. So it's not tab ID, but tab index. And we can send… we also have this tab index in the extension." - }, - { - "time": "16:06:19", - "speaker": "Max Tsoy", - "text": "Okay." - }, - { - "time": "16:06:25", - "speaker": "Alex Martemyanov", - "text": "And we don't need tab ID in that case. And it would just work on iOS, because we only have one window on iOS. But on macOS, there is another complication. If we open exact two windows with exact the same tab URLs in the same order." - }, - { - "time": "16:06:33", - "speaker": "Max Tsoy", - "text": "Right, right." - }, - { - "time": "16:06:41", - "speaker": "Alex Martemyanov", - "text": "There is a corner case that we cannot match it. But the window enumeration goes with the groan counter in the webkit. So it's not zero based, so it's not consequent. But it is growing." - }, - { - "time": "16:07:01", - "speaker": "Max Tsoy", - "text": "Okay, uh, can you…" - }, - { - "time": "16:07:02", - "speaker": "Alex Martemyanov", - "text": "So, a web extension window ID could be…" - }, - { - "time": "16:07:04", - "speaker": "Max Tsoy", - "text": "Can you drop some message in this stack design, then? Because this is the…" - }, - { - "time": "16:07:09", - "speaker": "Alex Martemyanov", - "text": "Both." - }, - { - "time": "16:07:09", - "speaker": "Max Tsoy", - "text": "I think we considered this to… There, um…" - }, - { - "time": "16:07:14", - "speaker": "Alex Martemyanov", - "text": "So basically the idea is to have another growing counter from the native side. And whenever we return a window, an extension window from the app, we grow the counter. So we will have window IDs starting like this. 1, 2, 3, and so on. And from WebKit, we would have IDs like 44, 72, 99, and so on. But there will be always two arrays of the matching size, and the sequence would match. So here we can match exactly window ID. from web extension and window ID that we gave it." - }, - { - "time": "16:07:47", - "speaker": "Max Tsoy", - "text": "Okay. Um… Yes, I mean, I'm not, like, following 100%, but I think it… I mean, if there is a way, I would like, uh, if you can read that, uh, that tech design." - }, - { - "time": "16:08:06", - "speaker": "Alex Martemyanov", - "text": "Okay, I will post an update there." - }, - { - "time": "16:08:06", - "speaker": "Max Tsoy", - "text": "just see if… because I know we… I see we actually did consider, like, the indexes and stuff, but. Um, uh, yeah, just like consider if as long as all of these are also, um, considered, I think whatever. We can do to map it, it will really help, because it's also… it's a problem for other reasons as well, right? Because now we're just matched by this, like, domains, and it's just messy. Um…" - }, - { - "time": "16:08:32", - "speaker": "Alex Martemyanov", - "text": "Yep." - }, - { - "time": "16:08:38", - "speaker": "Max Tsoy", - "text": "Anyways, okay, so, but to the, um… Uh, do this, uh, metrics thing, right? So, I… I will look at it later. Right now. It sounds like the, uh, tech design from, uh, your tech design sounds, like, very similar to what we already have, the CPM stage parameter. Which is already there, and we didn't plan to remove it. Uh, so I will need to check that. Um, and the second… Uh, one is… so this other… tasks, the… remove temporary CPM breakage diagnostics. So it's assigned to me now. I don't know if it makes sense for you to cover that too. Or, uh, I should do, because some of it is an extension. Um… Because if your goal is to clean up the old metrics and make permanent ones. Maybe that's also… but it's okay, I mean, if… I can also do that. That's no problem." - }, - { - "time": "16:09:49", - "speaker": "Alex Martemyanov", - "text": "I mean, I only wanted to validate the direction. There is one tech design for you for the need stage. I will check what you suggested. Another one is mostly for Michal, I guess." - }, - { - "time": "16:09:55", - "speaker": "Max Tsoy", - "text": "Yeah." - }, - { - "time": "16:10:05", - "speaker": "Alex Martemyanov", - "text": "But I just wanted to sync up with you both, so we have… Okay. the shared understanding of, uh, the remaining stages. So what I'll suggest is basically removing, uh, the fixes that didn't work out." - }, - { - "time": "16:10:21", - "speaker": "Max Tsoy", - "text": "Mm-hmm." - }, - { - "time": "16:10:21", - "speaker": "Alex Martemyanov", - "text": "We will keep updates on launch, base, stable base URLs restart after error six. But the ones that didn't appear in the metrics are just removed. I think it's kind of an obvious decision." - }, - { - "time": "16:10:37", - "speaker": "Max Tsoy", - "text": "Mm-hmm. Mm-hmm." - }, - { - "time": "16:10:40", - "speaker": "Alex Martemyanov", - "text": "And, uh, the next pull request, it just cleans up. all the metrics, so mostly on all the metrics that, uh, were added. And, uh, the next one would be re-adding based on some stabilized, uh, algorithms. So basically, we… rely on the sub or web page lifecycle, and if it didn't receive a CPM signal, we will report the breakage. So it should be that easy and nothing else gets connected." - }, - { - "time": "16:11:10", - "speaker": "Max Tsoy", - "text": "Yes." - }, - { - "time": "16:11:16", - "speaker": "Alex Martemyanov", - "text": "And it would be just a permanent metric that could give us understanding of where the trend going, but no reason." - }, - { - "time": "16:11:16", - "speaker": "Max Tsoy", - "text": "Okay. Yep. Okay, so, so, so far, basically, what I'm hearing is that. Um… you want to implement the same thing as we have this CPM stage, but it will be a metric for all page loads, not just for, um, uh, breakage reports. Which is… good." - }, - { - "time": "16:11:41", - "speaker": "Alex Martemyanov", - "text": "Uh, yes, uh, for all page loads, like a permanent metric, and uh…" - }, - { - "time": "16:11:44", - "speaker": "Max Tsoy", - "text": "Yep." - }, - { - "time": "16:11:46", - "speaker": "Alex Martemyanov", - "text": "So the init stage, it's kind of an extra mile for this effort just to. get an understanding of where it breaks. So it's not related, it's like another…" - }, - { - "time": "16:11:56", - "speaker": "Max Tsoy", - "text": "Okay." - }, - { - "time": "16:12:00", - "speaker": "Alex Martemyanov", - "text": "Extra magic." - }, - { - "time": "16:12:01", - "speaker": "Max Tsoy", - "text": "Okay, so basically it's optional, this step design for the web extension lifecycle metrics." - }, - { - "time": "16:12:02", - "speaker": "Alex Martemyanov", - "text": "Temporary. Yes." - }, - { - "time": "16:12:08", - "speaker": "Max Tsoy", - "text": "Okay. Um… my first… my first reaction is that, like, why do we reinvent and, like, why don't we just reuse the same? thing, because the extension already sends the CPM stage, and we could just wire it up. So it doesn't just… so it's reported. also outside breakage reports. Um, but I haven't seen… haven't looked into the actual values, like… on the first glance, it looks the same. To me. Um, and then…" - }, - { - "time": "16:12:42", - "speaker": "Alex Martemyanov", - "text": "Okay, I'll check and let you know." - }, - { - "time": "16:12:44", - "speaker": "Max Tsoy", - "text": "Yeah, you can check that. Uh, and… Yeah, I will try to get back to you today. I'm a little tied up because we have the, uh, assessment today, and I need to… Sorry for that, but, um… I hope it's not blocking you too much." - }, - { - "time": "16:13:04", - "speaker": "Alex Martemyanov", - "text": "Okay, no problem. I hope we can… get through it before Tuesday or Thursday." - }, - { - "time": "16:13:14", - "speaker": "Max Tsoy", - "text": "Uh, no, but definitely before, before Tuesday, uh, I, uh, it's, like, today or tomorrow, we can resolve it, I'm sure." - }, - { - "time": "16:13:22", - "speaker": "Alex Martemyanov", - "text": "Yep. That works." - }, - { - "time": "16:13:25", - "speaker": "Max Tsoy", - "text": "Mm-hmm." - }, - { - "time": "16:13:26", - "speaker": "Alex Martemyanov", - "text": "Okay, thanks. Then I'll give you an update async." - }, - { - "time": "16:13:28", - "speaker": "Max Tsoy", - "text": "Right. Good route." - }, - { - "time": "16:13:30", - "speaker": "Michal Smaga", - "text": "Alex, can you stay for a moment?" - }, - { - "time": "16:13:32", - "speaker": "Alex Martemyanov", - "text": "Yep." - }, - { - "time": "16:13:34", - "speaker": "Max Tsoy", - "text": "Uh, let's see if I can leave without…" - }, - { - "time": "16:13:37", - "speaker": "Michal Smaga", - "text": "Okay, so we can…" - }, - { - "time": "16:13:39", - "speaker": "Max Tsoy", - "text": "No, I can, I can, I can…" } ] } diff --git a/work/zoom-transcripts/undated Max Tsoy's Personal Meeting Room DLwAbUQ_RZ6X_D63xiX_Ww/transcript.md b/work/zoom-transcripts/undated Max Tsoy's Personal Meeting Room DLwAbUQ_RZ6X_D63xiX_Ww/transcript.md index a1d8b507..87629411 100644 --- a/work/zoom-transcripts/undated Max Tsoy's Personal Meeting Room DLwAbUQ_RZ6X_D63xiX_Ww/transcript.md +++ b/work/zoom-transcripts/undated Max Tsoy's Personal Meeting Room DLwAbUQ_RZ6X_D63xiX_Ww/transcript.md @@ -15,115 +15,3 @@ source: "https://us01mynotes.zoom.us/DLwAbUQ_RZ6X_D63xiX_Ww" - **15:53:25 · Max Tsoy:** Yeah, so I only have a few minutes, but, like, I have this question I asked about this dashboard yesterday. So, I don't understand… So, basically… We, uh, before this project, right, I made this, uh, this, uh, dashboard. With the… which was tracking this, uh, side effect. That kind of correlated with the error rate. And, uh, so we have this signal that shows. That at least one message was received from the extension, basically. Right. And it turned out that, like, I think it was, like, 10% of macOS breakage reports. Did not receive any message from the extension. So, which kind of meant that the… something was stuck. And I think that… that was the… Before this project, that was the best indicator of the problem. Right now, I'm looking at that dashboard, and I see that this… that signal only went up. on macOS. Uh, so… I don't understand, is it still relevant, or… do we, uh… I know we didn't look at it, but, like… Um… I'm not sure what it tells us. Does it actually mean that we didn't move anything, or… - **15:54:54 · Michal Smaga:** Yeah. But the question is, like, the the signal is only for the braggage reports. Right? - **15:55:00 · Max Tsoy:** Yes, but still, like, I would expect… it's… it's not… it's all breakage reports, right? So… Yes, it is filtered by people who report something, but it's still a signal and it's not related to what kind of breakage report it is. -- **15:55:21 · Michal Smaga:** And you filter by the macOS version as well, right? -- **15:55:24 · Max Tsoy:** Um… I think so. Yes, it's a stacked thing. It's in the same… in the same… Dashboards. Uh, this one. Right, so, uh, it's hidden under CPM diagnostics. Role. -- **15:55:51 · Alex Martemyanov:** Yeah, and just answered in your removed breakage diagnostic thread. And yeah, I basically asked Claude to check the breakages and related reports. -- **15:55:51 · Max Tsoy:** That's what I… Mm-hmm. Oh. Okay. Good. -- **15:56:06 · Alex Martemyanov:** So, it highlighted that, uh… The baseline is basically the same with the waiting signal, but there is a new report categories. Uh, that may be affecting, uh. that weighting metric and. -- **15:56:24 · Max Tsoy:** Okay, so… -- **15:56:27 · Alex Martemyanov:** So… -- **15:56:27 · Max Tsoy:** So we… we got more reports? -- **15:56:29 · Alex Martemyanov:** if there is a report flow on the error page, uh, which basically has no, uh, CPM running on it, and we've been affected, uh, with it with the, uh, CPM breakage pixels as well, uh, because, uh, they're not run on determination and there are pages on macOS. -- **15:56:37 · Max Tsoy:** Okay. -- **15:56:47 · Alex Martemyanov:** And if we exclude the report flow for the error page, it stays steady basically. And answering your treatment effect question, yeah, basically it was not… -- **15:56:53 · Max Tsoy:** Okay, okay. -- **15:57:02 · Alex Martemyanov:** lowering much, not affecting much the overall breakage signal magic. -- **15:57:08 · Max Tsoy:** Mm-hmm. Okay, so… -- **15:57:10 · Alex Martemyanov:** Because the main signal still stays in the seemingly normal flow as the metrics shown. -- **15:57:17 · Max Tsoy:** Right. Okay, so basically, the increase is probably driven by something else, but there was no decrease either. Um… -- **15:57:30 · Alex Martemyanov:** There was a… Probably less than a percent decrease and there's still fluctuation depending on a week measured, so we can tell for sure. -- **15:57:34 · Max Tsoy:** Yeah, yeah. Okay. Got it. Okay, so, uh, uh, alright, now, uh, I'm looking at your tech design, and my main question there is, do we… Do we not already have this? Because… so the tech design is basically proposing to send more, like, status reports from the extension. -- **15:58:04 · Alex Martemyanov:** Yep. -- **15:58:05 · Max Tsoy:** But we already have one signal, which is exactly the same thing, actually. So, if you look at this old… that design. that introduced that… other signal. So, the CPM dashboard state… Uh, specifically. Um… So basically, immediately after navigation, we set the CPM dashboard state to waiting in native code. And then… The first thing that… The extension does. After it gets… after it injects the content script. it's… initializes, and then… Almost immediately sends back the refresh CPM dashboard state. So… The problem is that. In the error state, this message is not received. So… Like, what you're proposing there… I think you will just not receive. Most of these messages. And that's the whole point of problem, right? So, like. Um… I don't think it's a problem of the granularity. It's basically that in this error state, we don't get. Any response? -- **15:59:37 · Alex Martemyanov:** Mmhm. -- **15:59:37 · Max Tsoy:** So, it kind of looks like the messaging is broken. And that's the whole reason, right? Like, we don't know what's happening. Is the extension stuck? Is it just the messaging that doesn't get through, or is it the… You know, the whole… Thing doesn't work. -- **15:59:55 · Alex Martemyanov:** I think it was mainly based on the, um… In the state that may be pending before we send the… The repair is unmarked state. Like, uh, for example, the config, uh, the config update state. -- **16:00:09 · Max Tsoy:** Right. -- **16:00:14 · Alex Martemyanov:** or. And. What else was there? Let me just open it. -- **16:00:21 · Max Tsoy:** Right, so basically you're suggesting that within that initialization, maybe it gets stuck. In between these first… so, what we could do… -- **16:00:28 · Alex Martemyanov:** Yes, yes. -- **16:00:32 · Max Tsoy:** We could just send one message. Immediately, like, on… On wake up. And I think we actually already do. Uh, don't we, like, there is some… I don't know, um, I don't remember exactly, but the… I think there was… so… What I'm saying is that I don't know if the, uh, all these other stages are… Um… useful, because I think it… the problem is that we… I suspect we won't get the first message, even. -- **16:01:07 · Alex Martemyanov:** Maybe, but… Probably we don't know. -- **16:01:15 · Max Tsoy:** So we have this… the first… -- **16:01:15 · Alex Martemyanov:** So here we kind of add no wait, so there is no await, it's kind of asynchronously as soon as we… -- **16:01:24 · Max Tsoy:** Mm-hmm. -- **16:01:26 · Alex Martemyanov:** Wake of the script wakes. Unless so first. Yeah, so there is the stage for, like, no, nothing was received, then, uh… H script in it. There may be possible hang on the config read, and if it hangs for whatever reason, it won't get through and won't get to the dashboard update state. Uh, so the suggestion is, like, sending, uh… And… log messages to… To set the list. Received state. that we could report in the main CPM breakage pixel. -- **16:02:15 · Max Tsoy:** Yeah, um… -- **16:02:16 · Alex Martemyanov:** I see. -- **16:02:18 · Max Tsoy:** Well, then I would… I would suggest just to trim it down to, like, the very first. signal, because… Um, I think for the rest, we actually… we have some… We have the CPM stage thing, right? Which is kind of… the same. Um… So, the last tech design that they shared? Um, there is this, yeah. -- **16:02:48 · Michal Smaga:** Yeah, Max, just to clarify, I'm not up to date because, like, I'm still catching up after yesterday, so I haven't read the new tech design. -- **16:02:53 · Max Tsoy:** Yeah. -- **16:02:55 · Michal Smaga:** But, the goal is to, like, remove the old metrics like that, that were, like, very detailed and, like, very precise. Get rid of that just because of privacy reasons and, like, to implement the new ones. -- **16:03:01 · Max Tsoy:** Mm-hmm, mm-hmm. -- **16:03:04 · Alex Martemyanov:** Sweet. We may be not at the same page because I've just opened another tech design I wanted to discuss. And, uh, yes, so basically, uh, I suggest to remove, uh, all the old metrics and, uh, this recorder thing, and, uh, delegate, uh, proxy. -- **16:03:24 · Max Tsoy:** Okay. -- **16:03:28 · Alex Martemyanov:** And basically the only basic metric that would relate page committed state to the dashboard update. -- **16:03:37 · Max Tsoy:** Mm-hmm, mm-h. -- **16:03:38 · Alex Martemyanov:** Uh, message. So if we don't receive it within, uh, 30 seconds, uh, we… -- **16:03:45 · Michal Smaga:** Record the stacks that you want. -- **16:03:45 · Alex Martemyanov:** So we expect to receive it. Yeah, but… before we navigate to another page, or before we close this tab. And if the page was alive for longer than 30 seconds, so basically it was measured, there were some cases when the dashboard update received after 30 seconds. -- **16:04:01 · Max Tsoy:** Mm-hmm. -- **16:04:06 · Alex Martemyanov:** It's for loading, because of, um… getting load, or whatever. And, uh, so if we navigate from the page, and, uh, it never received, uh, anything, and the page was active more than 30 seconds, we send a metric of the page of CPM hand. And if it was, uh, caught on another job. -- **16:04:22 · Max Tsoy:** Mm-hmm. -- **16:04:27 · Alex Martemyanov:** After it, we send the permanent breakage. -- **16:04:28 · Max Tsoy:** Right. -- **16:04:31 · Alex Martemyanov:** There was another issue of matching tab against actual… web extension tab against actual tab that we are measuring, because if we open the same page in two tabs, it basically can match both. Ahm. there is the tab index, and there is window ID that we cannot access from the app itself, but there is, like, a heuristics that allow us match it if we send all the window IDs. Um, so WebKit gives the window an ID in, uh… Consequently, it's not zero-based. It may be like 44, 72, and so on, but they are always ordered consequently as they are received from the app itself. And if we send these IDs from the script, we can match exact window and exact tab that the message is meant for. -- **16:05:32 · Max Tsoy:** Wait, wait, sorry, are you saying, uh… Are you saying we can match… we can map the extension tab ID to the native tab ID? -- **16:05:39 · Alex Martemyanov:** Yes. Yes. Yes. -- **16:05:43 · Max Tsoy:** Oh, that's a, that's a great thing. I, uh, I. -- **16:05:45 · Alex Martemyanov:** So I was breaking my head the last three days on how could we actually match it to… -- **16:05:45 · Michal Smaga:** Yeah, we… -- **16:05:52 · Alex Martemyanov:** To avoid, uh, false positives. -- **16:05:52 · Max Tsoy:** We have a separate, like. Separate tests somewhere we have that, uh… But how would it work in a nutshell again? -- **16:06:00 · Alex Martemyanov:** Yeah, basically we have a tab index that we set for the tab in the window. -- **16:06:07 · Max Tsoy:** Yes. -- **16:06:08 · Alex Martemyanov:** Oh, it's, uh… -- **16:06:09 · Max Tsoy:** Huh? -- **16:06:11 · Michal Smaga:** A native one. -- **16:06:13 · Alex Martemyanov:** the tab collection index. So it's not tab ID, but tab index. And we can send… we also have this tab index in the extension. -- **16:06:19 · Max Tsoy:** Okay. -- **16:06:25 · Alex Martemyanov:** And we don't need tab ID in that case. And it would just work on iOS, because we only have one window on iOS. But on macOS, there is another complication. If we open exact two windows with exact the same tab URLs in the same order. -- **16:06:33 · Max Tsoy:** Right, right. -- **16:06:41 · Alex Martemyanov:** There is a corner case that we cannot match it. But the window enumeration goes with the groan counter in the webkit. So it's not zero based, so it's not consequent. But it is growing. -- **16:07:01 · Max Tsoy:** Okay, uh, can you… -- **16:07:02 · Alex Martemyanov:** So, a web extension window ID could be… -- **16:07:04 · Max Tsoy:** Can you drop some message in this stack design, then? Because this is the… -- **16:07:09 · Alex Martemyanov:** Both. -- **16:07:09 · Max Tsoy:** I think we considered this to… There, um… -- **16:07:14 · Alex Martemyanov:** So basically the idea is to have another growing counter from the native side. And whenever we return a window, an extension window from the app, we grow the counter. So we will have window IDs starting like this. 1, 2, 3, and so on. And from WebKit, we would have IDs like 44, 72, 99, and so on. But there will be always two arrays of the matching size, and the sequence would match. So here we can match exactly window ID. from web extension and window ID that we gave it. -- **16:07:47 · Max Tsoy:** Okay. Um… Yes, I mean, I'm not, like, following 100%, but I think it… I mean, if there is a way, I would like, uh, if you can read that, uh, that tech design. -- **16:08:06 · Alex Martemyanov:** Okay, I will post an update there. -- **16:08:06 · Max Tsoy:** just see if… because I know we… I see we actually did consider, like, the indexes and stuff, but. Um, uh, yeah, just like consider if as long as all of these are also, um, considered, I think whatever. We can do to map it, it will really help, because it's also… it's a problem for other reasons as well, right? Because now we're just matched by this, like, domains, and it's just messy. Um… -- **16:08:32 · Alex Martemyanov:** Yep. -- **16:08:38 · Max Tsoy:** Anyways, okay, so, but to the, um… Uh, do this, uh, metrics thing, right? So, I… I will look at it later. Right now. It sounds like the, uh, tech design from, uh, your tech design sounds, like, very similar to what we already have, the CPM stage parameter. Which is already there, and we didn't plan to remove it. Uh, so I will need to check that. Um, and the second… Uh, one is… so this other… tasks, the… remove temporary CPM breakage diagnostics. So it's assigned to me now. I don't know if it makes sense for you to cover that too. Or, uh, I should do, because some of it is an extension. Um… Because if your goal is to clean up the old metrics and make permanent ones. Maybe that's also… but it's okay, I mean, if… I can also do that. That's no problem. -- **16:09:49 · Alex Martemyanov:** I mean, I only wanted to validate the direction. There is one tech design for you for the need stage. I will check what you suggested. Another one is mostly for Michal, I guess. -- **16:09:55 · Max Tsoy:** Yeah. -- **16:10:05 · Alex Martemyanov:** But I just wanted to sync up with you both, so we have… Okay. the shared understanding of, uh, the remaining stages. So what I'll suggest is basically removing, uh, the fixes that didn't work out. -- **16:10:21 · Max Tsoy:** Mm-hmm. -- **16:10:21 · Alex Martemyanov:** We will keep updates on launch, base, stable base URLs restart after error six. But the ones that didn't appear in the metrics are just removed. I think it's kind of an obvious decision. -- **16:10:37 · Max Tsoy:** Mm-hmm. Mm-hmm. -- **16:10:40 · Alex Martemyanov:** And, uh, the next pull request, it just cleans up. all the metrics, so mostly on all the metrics that, uh, were added. And, uh, the next one would be re-adding based on some stabilized, uh, algorithms. So basically, we… rely on the sub or web page lifecycle, and if it didn't receive a CPM signal, we will report the breakage. So it should be that easy and nothing else gets connected. -- **16:11:10 · Max Tsoy:** Yes. -- **16:11:16 · Alex Martemyanov:** And it would be just a permanent metric that could give us understanding of where the trend going, but no reason. -- **16:11:16 · Max Tsoy:** Okay. Yep. Okay, so, so, so far, basically, what I'm hearing is that. Um… you want to implement the same thing as we have this CPM stage, but it will be a metric for all page loads, not just for, um, uh, breakage reports. Which is… good. -- **16:11:41 · Alex Martemyanov:** Uh, yes, uh, for all page loads, like a permanent metric, and uh… -- **16:11:44 · Max Tsoy:** Yep. -- **16:11:46 · Alex Martemyanov:** So the init stage, it's kind of an extra mile for this effort just to. get an understanding of where it breaks. So it's not related, it's like another… -- **16:11:56 · Max Tsoy:** Okay. -- **16:12:00 · Alex Martemyanov:** Extra magic. -- **16:12:01 · Max Tsoy:** Okay, so basically it's optional, this step design for the web extension lifecycle metrics. -- **16:12:02 · Alex Martemyanov:** Temporary. Yes. -- **16:12:08 · Max Tsoy:** Okay. Um… my first… my first reaction is that, like, why do we reinvent and, like, why don't we just reuse the same? thing, because the extension already sends the CPM stage, and we could just wire it up. So it doesn't just… so it's reported. also outside breakage reports. Um, but I haven't seen… haven't looked into the actual values, like… on the first glance, it looks the same. To me. Um, and then… -- **16:12:42 · Alex Martemyanov:** Okay, I'll check and let you know. -- **16:12:44 · Max Tsoy:** Yeah, you can check that. Uh, and… Yeah, I will try to get back to you today. I'm a little tied up because we have the, uh, assessment today, and I need to… Sorry for that, but, um… I hope it's not blocking you too much. -- **16:13:04 · Alex Martemyanov:** Okay, no problem. I hope we can… get through it before Tuesday or Thursday. -- **16:13:14 · Max Tsoy:** Uh, no, but definitely before, before Tuesday, uh, I, uh, it's, like, today or tomorrow, we can resolve it, I'm sure. -- **16:13:22 · Alex Martemyanov:** Yep. That works. -- **16:13:25 · Max Tsoy:** Mm-hmm. -- **16:13:26 · Alex Martemyanov:** Okay, thanks. Then I'll give you an update async. -- **16:13:28 · Max Tsoy:** Right. Good route. -- **16:13:30 · Michal Smaga:** Alex, can you stay for a moment? -- **16:13:32 · Alex Martemyanov:** Yep. -- **16:13:34 · Max Tsoy:** Uh, let's see if I can leave without… -- **16:13:37 · Michal Smaga:** Okay, so we can… -- **16:13:39 · Max Tsoy:** No, I can, I can, I can…