[2026-11-20] eagle: work/zoom-transcripts/2026-10-16 All-Company Meeting 2026-10-16 21 31(GMT+6 00) klekRLtLSEuMv0PCCPCjtA/transcript.json work/zoom-transcripts/2026-10-16 All-Company Meeting 2026-10-16 21 31(GMT+6 00) klekRLtLSEuMv0PCCPCjtA/transcript.md work/zoom-transcripts/2026-10-19 Michal Smaga's Personal Meeting Room QvxllpCuTTSLGEZp-R6jQw/transcript.json work/zoom-transcripts/2026-10-19 Michal Smaga's Personal Meeting Room QvxllpCuTTSLGEZp-R6jQw/transcript.md work/zoom-transcripts/2026-10-20 Apple Weekly Team Meeting - Zoom ID 2026-10-20 20 01(GMT+6 00) gBBa-iiUQLycw55WRV1tnw/transcript.json work/zoom-transcripts/2026-10-20 Apple Weekly Team Meeting - Zoom ID 2026-10-20 20 01(GMT+6 00) gBBa-iiUQLycw55WRV1tnw/transcript.md work/zoom-transcripts/2026-10-20 Dominik Kapusta's Personal Meeting Room Mg62hl1GSI2gw4XeGvHAsg/transcript.json work/zoom-transcripts/2026-10-20 Dominik Kapusta's Personal Meeting Room Mg62hl1GSI2gw4XeGvHAsg/transcript.md work/zoom-transcripts/index.json work/zoom-transcripts/undated Dominik Kapusta's Personal Meeting Room p5FdcX9WT-afBpWjRgaW0w/transcript.json

This commit is contained in:
Alexey Martemyanov committed 2026-11-20 14:34:48 +06:00
1 parent 5990a5c740
commit b77a533ecf
11 files changed
+2806 -1576

No files matched your search

@@ -23,6 +23,91 @@
"time": "21:31:26",
"speaker": "Gabriel Weinberg",
"text": "Yeah."
},
{
"time": "21:31:34",
"speaker": "Anne Hildebrand",
"text": "And also, uh, we want to make sure you get your questions answered around anything you want to discuss there, so submit a PeopleOps form, that's one way to do it. Um, if you do submit it without your name on the form, remember that the responses go to the project I've dropped in the channel there, so make sure not to miss those. That's it for me."
},
{
"time": "21:31:58",
"speaker": "Viktor Jansson",
"text": "Alright, objective update from 05 Search Revenue. Last week, we held an assessment and switched the focus to evaluate ad experience and optimizations for search revenue. We will do this by evaluating if we can show ads from other providers for commercial queries, where Microsoft doesn't give us any ads, and how we can improve our overall shopping and product experience. For the optimizations, we have a few products in the pipeline, mainly for optimizing product ads, which we expect a potential $4 million a year revenue increase for. And the Duckbill Award goes to Renato, who ran a product during Quick Win Days to highlight prices for products on sale, which added half a million dollars a year, while at the same time helping our users to find discounted products. Great example of time well spent during Quick Win Days with a large impact to the objective KPIs. Over to Kirby for more million dollar updates."
},
{
"time": "21:32:56",
"speaker": "Kirby (she/they)",
"text": "Hey, thanks Victor. So we built a lot this past cycle. We hit 150,000 active subscribers. We're tracking toward 180,000 by the end of this year, which is the stretch goal that we set out in our last cycle. And it's not official yet, but tentatively, we're working toward 300,000 as the goal for the end of next year, end of 2027. So more exciting updates to come. This slide is mostly about one A/B test that we did, and I want to take a minute to explain it, because it's really interesting. So we, in rough numbers, about 800 people start a subscription every day. Some of them are going direct into a paid subscription. Some of them are starting a free trial. Also, every day we have between 4 and 500 people canceling their subscription. So more than half. And the difference between those numbers is net subscriber additions. That's OO's KPI. So we're not just trying to get more people to start a subscription. We're also trying to get fewer people to cancel. And one way we're doing that is by giving people a better day zero experience as soon as they subscribe, creating subscriber onboarding. But another way we're doing it is by shifting people over to yearly plans. So we've got monthly, we've got yearly. Monthly plans have a 14% churn rate. That's the likelihood that someone will cancel every month. Yearly plans, it's only 2%, because you only have one opportunity to churn. every year. So to try to shift people toward yearly, we tested removing the free trial option from monthly plans to make yearly a little more appealing. And we did this first on Android, and we saw what we expected or what we hoped for. which is that fewer people are getting a subscription, because some people will see that there's no free trial on monthly, they don't want yearly, they bounce. But of the people who do stick around, more of them are on yearly, and we modeled it out so that we'd catch up with where. our growth would have been within a few months. Then we also did it on iOS, and we saw something surprising, which is that iOS users will just buy the monthly subscription with no free trial, and more of them are going yearly also. So the number of extra people we got on iOS. cancels out the people we lost on Android. So there's no cost. It's not going to take any time to catch up with where our growth would have been. We're just getting the extra lifetime value of each of these users by shifting more people over to yearly. And we're going to reduce the churn rate from where it is now, 9.5%, which is pretty good compared to the industry standard for VPNs. We want it to be at 7% and we want it to stay there. And a year from now, just from this one experiment. we're going to get down to 7.2% churn from having more people coming in on yearly plans. So if you're close to OO, you know that we work really hard to get one experiment out right after the last one. And this is why we never know. when we're gonna have one that's even more valuable than we'd anticipated. In lifetime value, which is different from revenue, but it's the projected amount of revenue we expect to get per user, we're adding 5 million in lifetime value per. year just from this one experiment. So the next time we're moving quickly to get something out for an experiment, out of the way, because these are really valuable and interesting. And congratulations to the team for all the work that got done. Super congratulations to Bartek, who's come on in a tech lead role. And as soon as he got to the objective, he got up to speed really quickly. and is our Duckbill winner because he has been accelerating the timelines in project after project by just thinking of something we didn't think of, coming up with a simpler way to solve something, and he connected the dots between incidents that we've been seeing across platforms where users are getting logged out and we don't know why. And he'd figured out a path forward, turned it into an SLO, and owned it, and is getting it fixed. Congratulations, Bartek. And next, on to Russell, I think."
},
{
"time": "21:37:23",
"speaker": "russell holt",
"text": "Thanks, Gary. Hi, yeah, Russell here with an update for OE, where we are working on cookie prompt management and ad blocking. Um, for CPM, we've been, uh, improving the automated pipeline, which processes. uh, fixes and unhandled sites. And at this point, about 50% of these changes, uh, to our data set are fully automated, meaning no human involvement, which is pretty exciting. And right now we're at about overall 73% coverage, uh, in the US. Right now. So, one thing that we did this cycle is we finally got a reasonable opt-in rate. um, of 65% on Android, similar to iOS for CPM. Uh, which is a flow we've been struggling with for a bit, because we have a lot of cases where we need user consent. to automatically do something for them for legal reasons. And in this case, it was we need to accept cookies under certain circumstances to raise that coverage to improve the experience. And it's been a little bit of trouble, but that was great. So, on this cycle, we're really doubling down on the CPM automation, making the agent faster, more accurate, improving heuristic pop-up detection, doing regression testing, and this is really the key. to the long-term maintenance mode for CPM, which is finally in sight again, which we're pretty excited about. Um, and on the ad blocking side, uh, we're moving forward with two of the main feature requests. that we got from our analysis after the big YouTube ad blocking launch. Um, which will be… One, expanding ad blocking to a selection of top sites, starting with adult sites. And then two, on YouTube specifically, giving users the ability to skip sponsored segments. sponsored content segments, which look like ads to people. Uh, through YouTube. So, the goal there is to give people more control. and make a better default experience, even for YouTube Premium. where people see these sponsored segments as ads, so better not block. All right, that's it for OE. I guess on to Emmanuelle."
},
{
"time": "21:39:42",
"speaker": "Emanuele Feliziani",
"text": "Yes, Russell, thanks. Exciting updates on the CDM and unblocking stuff. We had OI assessment last week. We will keep the focus on ChatSync. We will have a hopefully final push to stabilize the ChatSync system. So this will be more of a milestone focus. And we'll focus, yes, on stabilization. What we've done in the sparse cycle, we've optimized. the Syncflow on several platforms, both mobile and, uh, like, native and, um, and third-party, and we also shipped, uh, promos for ChatSync. For third parties, we've seen a significant inflow of users from those promos. We've doubled the daily activations and the daily active users for third parties specifically is up almost 5x. And it's 30% across all platforms. So really nice bump in users there. We're still not happy with the adoption. We want more. We are also not happy with the conversion rates. So we will keep iterating. in the… in future cycles, so after this one. Uh, in the meantime, we are also running, uh, user research to try and understand the drop of… the drop of points, the points of confusion. For users during the sync setup flow and see where we can be more helpful towards our users, making sure that they are able to set up sync. um… across multiple devices especially. We'll also look into ways to make the sync entry point more prominent. We've already seen that people struggle to find it in the settings, it's kind of buried, so we try to make it more prominent, lift it up a little bit, make it more intuitive how to use it. Um, and yeah. That's it for ROI. The duck bill goes to Pablo Serrano, the pub RR. designer, Serrano, uh, designer Pablo, we also have a Pablo on the back end. Uh, and yeah, he's, he's been great. Uh, he's been great for a long time and this cycle we are happy to congratulate him, uh, with, with the award. And, uh, yeah, he's been, uh, he's been great, uh, on the project advisory side, very quick and tidy on the design front. And he's been, diving into the metrics with, with Gusto. So, really happy to see Pablo grow in this role. Thanks, Pablo, and congrats. Uh, next up, I think, is, uh, team member, uh, updates with John Russell."
},
{
"time": "21:42:36",
"speaker": "Jon Russo",
"text": "Hi. Didn't realize I was coming up this soon. But, hi, everybody. I'm John from the CloudOps team. I guess I'm Matt. Two different angles here. One from the work side. Recently, I started working on some of our Kubernetes stuff, which is really exciting and a little intimidating for me. I've been wanting to kind of dip my toes into this technology for a while, and it's nice to be able to finally do it. I got a lot of people on the team helping me in that, and kind of designing a new deployment spec for some of our new Kubernetes clusters. So that's fun and exciting in the infra velocity kind of project there. On a personal side, two pretty exciting things coming up. One tomorrow, I've been doing a lot of trail running this past year, and I have a half marathon coming up at a place called Von Trapp Mountain. Um, it's just outside of Stowe, Vermont, if anybody knows the area. Uh, the Von Trapp family is famous from The Sound of Music, uh, movies way back in the day, and it's an absolutely beautiful property up there. Um, so it's gonna be a fun race, um… there that has about 2,000 feet of elevation gain in it. I think that's roughly like 600 meters for the Europeans. The weather is looking pretty terrible, actually, so it might be a bit of a slop fest. We're expected to get an inch of rain today, and then it's going to be 33 degrees Fahrenheit at the start of the race, about 1 degree Celsius, so pretty dang cold. Um, and then the other side is that, uh, about a couple weeks ago, I booked a trip to Japan for end of January. Uh, this is something I've always wanted to do. It's been a bucket list trip for me to go skiing there. Um, so me and a couple friends are going to Hokkaido for two weeks. And, uh, traveling around in a van, and kind of exploring all the resorts there, and doing some backcountry skiing, uh, maybe even backcountry skiing into a volcano. Um, so that should be fun. Yeah, that's it for me. Thanks."
},
{
"time": "21:44:56",
"speaker": "Stephen",
"text": "Oh, I think this is me. Hi, so we've been working on a refreshed new tab page for iOS for a while, and we're finally getting ready for the first internal release. It should be next week. I think there's a link in there if you want to enable it early. I tried to make a video. So this would work out well, but that didn't work. So we're gonna do it live demo real quick. So hopefully this does work out. I'm gonna try to. share this via… My phone. So if it doesn't work, someone please yell at me. Okay. Hopefully you can see my phone."
},
{
"time": "21:45:37",
"speaker": "Spencer",
"text": "Yes."
},
{
"time": "21:45:38",
"speaker": "Stephen",
"text": "Okay, awesome. Thank you. So… So here's the new tab — the new, new tab page. Kind of a weird phrasing. But you can see it's more brand forward. We have Dax there. He's got some Dax greetings. We have a nice background illustration there in the background. And the greetings will update. Probably not this frequently, but you can kind of see there's a few in there and we're going to update them based on time of day and some other stuff. The toggle's right there so you can switch between chat and search pretty easily. And you can see we have. Placeholder favorites now. So these are not hidden by default. So this is kind of inviting people to add more favorites. I could add one. Maybe. Yep, and there's that one, so that goes there. But we don't show the, uh… icon until you go there once. And then we also have… The return to hatch there. So you can get back to that. You can swipe it away if you want. Also get to your new tabs easier. And… I think I lost my window. I have too many DuckDuckGo's going here. You can also… Have a lot of favorites. So they scroll and expand and contract. And you can use the customization right on the page now, so you can toggle them on and off. From here, change some settings, we're gonna add some more there as well, and it also has… Dark mode, so if you want a cool fancy dark mode, you can have that as well, and everything should look… Nice there as well. So if you want to try that out, you can wait till next week, or you can follow the link and turn it on for yourself now."
},
{
"time": "21:47:35",
"speaker": "Julia Abreu",
"text": "We had one more demo added to the agenda, but there is no name there. So, how to enable Redesign NTP? Does anyone…"
},
{
"time": "21:47:45",
"speaker": "Gabriel Weinberg",
"text": "I think that's Brett Stevens."
},
{
"time": "21:47:46",
"speaker": "Stephen",
"text": "Oh, yeah, that was part of mine, sorry."
},
{
"time": "21:47:48",
"speaker": "Gabriel Weinberg",
"text": "Yeah."
},
{
"time": "21:47:48",
"speaker": "Julia Abreu",
"text": "Oh, okay, cool. Just wanted to make sure that there was no extra in there. Uh, okay, before we wrap up, I just wanted to say or remind everybody that next day we have Hack Days. Um, it's the last Hack Days of the year. We will have a quick win in, uh, December. If you want to check the dates, you can see the AOR for special days. I am just drafting the calendar for next year, so I'll get Gabriel to take a look, and then I will post it as well under the AOR. I am working on some ideas on how to make the meeting for the demos a little shorter. I don't want to make it. every demo shorter than 2 minutes, because, um, I know you all wouldn't like that, but I'm trying to figure out, um, some ways that maybe we can split demos in different days, or, like, so if you have any ideas, or if you would like to help in any way. please go ahead and ping me. And otherwise, I just have one personal update that is special for Elle. Um, this is Maple. This is our third Dash Hound. Um, I am completely out of control now that I have a garden, so, um, I might be just sharing a new Dutch hound every week. Uh, and if I get her to not bark at everyone, I will bring her to our next meetup, uh, because the other two are not. very well trained. Um, so that's it for me. I hope you all have a great weekend, and uh… we'll roll out GPT for next week."
},
{
"time": "21:49:17",
"speaker": "Gabriel Weinberg",
"text": "Yeah, one idea for you, Julia, for everyone here, is that to make less demos, you can collaborate with each other on projects, so… I'm not sure our best process for that at the moment, but there's the Hack Days project. You can say what you're gonna work on in there and try to recruit people. There's, we have a Mattermost channel too, don't we? Do you? Or if not, maybe we should."
},
{
"time": "21:49:37",
"speaker": "Julia Abreu",
"text": "We do have, yes, specialties."
},
{
"time": "21:49:40",
"speaker": "Gabriel Weinberg",
"text": "Maybe that's the place to go. Go to the Mattermost channel. Um, okay, hope everyone's gonna be good."
}
]
}
@@ -15,3 +15,20 @@ source: "https://us01mynotes.zoom.us/klekRLtLSEuMv0PCCPCjtA"
- **21:31:08 · Gabriel Weinberg:** Hello? That was a nice fade out. Um… Okay… No new team members, no AOR updates. Um, we had one company update, there's no name by it.
- **21:31:23 · Anne Hildebrand:** Sorry, that was me. Um, yes, this is Anne. Uh, just a reminder to check your inboxes for the outcome of the compensation review.
- **21:31:26 · Gabriel Weinberg:** Yeah.
- **21:31:34 · Anne Hildebrand:** And also, uh, we want to make sure you get your questions answered around anything you want to discuss there, so submit a PeopleOps form, that's one way to do it. Um, if you do submit it without your name on the form, remember that the responses go to the project I've dropped in the channel there, so make sure not to miss those. That's it for me.
- **21:31:58 · Viktor Jansson:** Alright, objective update from 05 Search Revenue. Last week, we held an assessment and switched the focus to evaluate ad experience and optimizations for search revenue. We will do this by evaluating if we can show ads from other providers for commercial queries, where Microsoft doesn't give us any ads, and how we can improve our overall shopping and product experience. For the optimizations, we have a few products in the pipeline, mainly for optimizing product ads, which we expect a potential $4 million a year revenue increase for. And the Duckbill Award goes to Renato, who ran a product during Quick Win Days to highlight prices for products on sale, which added half a million dollars a year, while at the same time helping our users to find discounted products. Great example of time well spent during Quick Win Days with a large impact to the objective KPIs. Over to Kirby for more million dollar updates.
- **21:32:56 · Kirby (she/they):** Hey, thanks Victor. So we built a lot this past cycle. We hit 150,000 active subscribers. We're tracking toward 180,000 by the end of this year, which is the stretch goal that we set out in our last cycle. And it's not official yet, but tentatively, we're working toward 300,000 as the goal for the end of next year, end of 2027. So more exciting updates to come. This slide is mostly about one A/B test that we did, and I want to take a minute to explain it, because it's really interesting. So we, in rough numbers, about 800 people start a subscription every day. Some of them are going direct into a paid subscription. Some of them are starting a free trial. Also, every day we have between 4 and 500 people canceling their subscription. So more than half. And the difference between those numbers is net subscriber additions. That's OO's KPI. So we're not just trying to get more people to start a subscription. We're also trying to get fewer people to cancel. And one way we're doing that is by giving people a better day zero experience as soon as they subscribe, creating subscriber onboarding. But another way we're doing it is by shifting people over to yearly plans. So we've got monthly, we've got yearly. Monthly plans have a 14% churn rate. That's the likelihood that someone will cancel every month. Yearly plans, it's only 2%, because you only have one opportunity to churn. every year. So to try to shift people toward yearly, we tested removing the free trial option from monthly plans to make yearly a little more appealing. And we did this first on Android, and we saw what we expected or what we hoped for. which is that fewer people are getting a subscription, because some people will see that there's no free trial on monthly, they don't want yearly, they bounce. But of the people who do stick around, more of them are on yearly, and we modeled it out so that we'd catch up with where. our growth would have been within a few months. Then we also did it on iOS, and we saw something surprising, which is that iOS users will just buy the monthly subscription with no free trial, and more of them are going yearly also. So the number of extra people we got on iOS. cancels out the people we lost on Android. So there's no cost. It's not going to take any time to catch up with where our growth would have been. We're just getting the extra lifetime value of each of these users by shifting more people over to yearly. And we're going to reduce the churn rate from where it is now, 9.5%, which is pretty good compared to the industry standard for VPNs. We want it to be at 7% and we want it to stay there. And a year from now, just from this one experiment. we're going to get down to 7.2% churn from having more people coming in on yearly plans. So if you're close to OO, you know that we work really hard to get one experiment out right after the last one. And this is why we never know. when we're gonna have one that's even more valuable than we'd anticipated. In lifetime value, which is different from revenue, but it's the projected amount of revenue we expect to get per user, we're adding 5 million in lifetime value per. year just from this one experiment. So the next time we're moving quickly to get something out for an experiment, out of the way, because these are really valuable and interesting. And congratulations to the team for all the work that got done. Super congratulations to Bartek, who's come on in a tech lead role. And as soon as he got to the objective, he got up to speed really quickly. and is our Duckbill winner because he has been accelerating the timelines in project after project by just thinking of something we didn't think of, coming up with a simpler way to solve something, and he connected the dots between incidents that we've been seeing across platforms where users are getting logged out and we don't know why. And he'd figured out a path forward, turned it into an SLO, and owned it, and is getting it fixed. Congratulations, Bartek. And next, on to Russell, I think.
- **21:37:23 · russell holt:** Thanks, Gary. Hi, yeah, Russell here with an update for OE, where we are working on cookie prompt management and ad blocking. Um, for CPM, we've been, uh, improving the automated pipeline, which processes. uh, fixes and unhandled sites. And at this point, about 50% of these changes, uh, to our data set are fully automated, meaning no human involvement, which is pretty exciting. And right now we're at about overall 73% coverage, uh, in the US. Right now. So, one thing that we did this cycle is we finally got a reasonable opt-in rate. um, of 65% on Android, similar to iOS for CPM. Uh, which is a flow we've been struggling with for a bit, because we have a lot of cases where we need user consent. to automatically do something for them for legal reasons. And in this case, it was we need to accept cookies under certain circumstances to raise that coverage to improve the experience. And it's been a little bit of trouble, but that was great. So, on this cycle, we're really doubling down on the CPM automation, making the agent faster, more accurate, improving heuristic pop-up detection, doing regression testing, and this is really the key. to the long-term maintenance mode for CPM, which is finally in sight again, which we're pretty excited about. Um, and on the ad blocking side, uh, we're moving forward with two of the main feature requests. that we got from our analysis after the big YouTube ad blocking launch. Um, which will be… One, expanding ad blocking to a selection of top sites, starting with adult sites. And then two, on YouTube specifically, giving users the ability to skip sponsored segments. sponsored content segments, which look like ads to people. Uh, through YouTube. So, the goal there is to give people more control. and make a better default experience, even for YouTube Premium. where people see these sponsored segments as ads, so better not block. All right, that's it for OE. I guess on to Emmanuelle.
- **21:39:42 · Emanuele Feliziani:** Yes, Russell, thanks. Exciting updates on the CDM and unblocking stuff. We had OI assessment last week. We will keep the focus on ChatSync. We will have a hopefully final push to stabilize the ChatSync system. So this will be more of a milestone focus. And we'll focus, yes, on stabilization. What we've done in the sparse cycle, we've optimized. the Syncflow on several platforms, both mobile and, uh, like, native and, um, and third-party, and we also shipped, uh, promos for ChatSync. For third parties, we've seen a significant inflow of users from those promos. We've doubled the daily activations and the daily active users for third parties specifically is up almost 5x. And it's 30% across all platforms. So really nice bump in users there. We're still not happy with the adoption. We want more. We are also not happy with the conversion rates. So we will keep iterating. in the… in future cycles, so after this one. Uh, in the meantime, we are also running, uh, user research to try and understand the drop of… the drop of points, the points of confusion. For users during the sync setup flow and see where we can be more helpful towards our users, making sure that they are able to set up sync. um… across multiple devices especially. We'll also look into ways to make the sync entry point more prominent. We've already seen that people struggle to find it in the settings, it's kind of buried, so we try to make it more prominent, lift it up a little bit, make it more intuitive how to use it. Um, and yeah. That's it for ROI. The duck bill goes to Pablo Serrano, the pub RR. designer, Serrano, uh, designer Pablo, we also have a Pablo on the back end. Uh, and yeah, he's, he's been great. Uh, he's been great for a long time and this cycle we are happy to congratulate him, uh, with, with the award. And, uh, yeah, he's been, uh, he's been great, uh, on the project advisory side, very quick and tidy on the design front. And he's been, diving into the metrics with, with Gusto. So, really happy to see Pablo grow in this role. Thanks, Pablo, and congrats. Uh, next up, I think, is, uh, team member, uh, updates with John Russell.
- **21:42:36 · Jon Russo:** Hi. Didn't realize I was coming up this soon. But, hi, everybody. I'm John from the CloudOps team. I guess I'm Matt. Two different angles here. One from the work side. Recently, I started working on some of our Kubernetes stuff, which is really exciting and a little intimidating for me. I've been wanting to kind of dip my toes into this technology for a while, and it's nice to be able to finally do it. I got a lot of people on the team helping me in that, and kind of designing a new deployment spec for some of our new Kubernetes clusters. So that's fun and exciting in the infra velocity kind of project there. On a personal side, two pretty exciting things coming up. One tomorrow, I've been doing a lot of trail running this past year, and I have a half marathon coming up at a place called Von Trapp Mountain. Um, it's just outside of Stowe, Vermont, if anybody knows the area. Uh, the Von Trapp family is famous from The Sound of Music, uh, movies way back in the day, and it's an absolutely beautiful property up there. Um, so it's gonna be a fun race, um… there that has about 2,000 feet of elevation gain in it. I think that's roughly like 600 meters for the Europeans. The weather is looking pretty terrible, actually, so it might be a bit of a slop fest. We're expected to get an inch of rain today, and then it's going to be 33 degrees Fahrenheit at the start of the race, about 1 degree Celsius, so pretty dang cold. Um, and then the other side is that, uh, about a couple weeks ago, I booked a trip to Japan for end of January. Uh, this is something I've always wanted to do. It's been a bucket list trip for me to go skiing there. Um, so me and a couple friends are going to Hokkaido for two weeks. And, uh, traveling around in a van, and kind of exploring all the resorts there, and doing some backcountry skiing, uh, maybe even backcountry skiing into a volcano. Um, so that should be fun. Yeah, that's it for me. Thanks.
- **21:44:56 · Stephen:** Oh, I think this is me. Hi, so we've been working on a refreshed new tab page for iOS for a while, and we're finally getting ready for the first internal release. It should be next week. I think there's a link in there if you want to enable it early. I tried to make a video. So this would work out well, but that didn't work. So we're gonna do it live demo real quick. So hopefully this does work out. I'm gonna try to. share this via… My phone. So if it doesn't work, someone please yell at me. Okay. Hopefully you can see my phone.
- **21:45:37 · Spencer:** Yes.
- **21:45:38 · Stephen:** Okay, awesome. Thank you. So… So here's the new tab — the new, new tab page. Kind of a weird phrasing. But you can see it's more brand forward. We have Dax there. He's got some Dax greetings. We have a nice background illustration there in the background. And the greetings will update. Probably not this frequently, but you can kind of see there's a few in there and we're going to update them based on time of day and some other stuff. The toggle's right there so you can switch between chat and search pretty easily. And you can see we have. Placeholder favorites now. So these are not hidden by default. So this is kind of inviting people to add more favorites. I could add one. Maybe. Yep, and there's that one, so that goes there. But we don't show the, uh… icon until you go there once. And then we also have… The return to hatch there. So you can get back to that. You can swipe it away if you want. Also get to your new tabs easier. And… I think I lost my window. I have too many DuckDuckGo's going here. You can also… Have a lot of favorites. So they scroll and expand and contract. And you can use the customization right on the page now, so you can toggle them on and off. From here, change some settings, we're gonna add some more there as well, and it also has… Dark mode, so if you want a cool fancy dark mode, you can have that as well, and everything should look… Nice there as well. So if you want to try that out, you can wait till next week, or you can follow the link and turn it on for yourself now.
- **21:47:35 · Julia Abreu:** We had one more demo added to the agenda, but there is no name there. So, how to enable Redesign NTP? Does anyone…
- **21:47:45 · Gabriel Weinberg:** I think that's Brett Stevens.
- **21:47:46 · Stephen:** Oh, yeah, that was part of mine, sorry.
- **21:47:48 · Gabriel Weinberg:** Yeah.
- **21:47:48 · Julia Abreu:** Oh, okay, cool. Just wanted to make sure that there was no extra in there. Uh, okay, before we wrap up, I just wanted to say or remind everybody that next day we have Hack Days. Um, it's the last Hack Days of the year. We will have a quick win in, uh, December. If you want to check the dates, you can see the AOR for special days. I am just drafting the calendar for next year, so I'll get Gabriel to take a look, and then I will post it as well under the AOR. I am working on some ideas on how to make the meeting for the demos a little shorter. I don't want to make it. every demo shorter than 2 minutes, because, um, I know you all wouldn't like that, but I'm trying to figure out, um, some ways that maybe we can split demos in different days, or, like, so if you have any ideas, or if you would like to help in any way. please go ahead and ping me. And otherwise, I just have one personal update that is special for Elle. Um, this is Maple. This is our third Dash Hound. Um, I am completely out of control now that I have a garden, so, um, I might be just sharing a new Dutch hound every week. Uh, and if I get her to not bark at everyone, I will bring her to our next meetup, uh, because the other two are not. very well trained. Um, so that's it for me. I hope you all have a great weekend, and uh… we'll roll out GPT for next week.
- **21:49:17 · Gabriel Weinberg:** Yeah, one idea for you, Julia, for everyone here, is that to make less demos, you can collaborate with each other on projects, so… I'm not sure our best process for that at the moment, but there's the Hack Days project. You can say what you're gonna work on in there and try to recruit people. There's, we have a Mattermost channel too, don't we? Do you? Or if not, maybe we should.
- **21:49:37 · Julia Abreu:** We do have, yes, specialties.
- **21:49:40 · Gabriel Weinberg:** Maybe that's the place to go. Go to the Mattermost channel. Um, okay, hope everyone's gonna be good.
@@ -23,6 +23,656 @@
"time": "18:10:09",
"speaker": "Michal Smaga",
"text": "Uh, I think I'm, I'm like… done reviewing the first one about the pixel. I had the issue that I wasn't able to reproduce it, like, I was trying to kill the WebKit process."
},
{
"time": "18:10:22",
"speaker": "Alex Martemyanov",
"text": "Mm-hmm."
},
{
"time": "18:10:23",
"speaker": "Michal Smaga",
"text": "Do you have any, like, extra steps?"
},
{
"time": "18:10:27",
"speaker": "Alex Martemyanov",
"text": "Uh, so generally it fails from the second try on this exact test page that is attached there."
},
{
"time": "18:10:37",
"speaker": "Michal Smaga",
"text": "So after, after I, I killed the, the, the…"
},
{
"time": "18:10:37",
"speaker": "Alex Martemyanov",
"text": "Okay."
},
{
"time": "18:10:41",
"speaker": "Michal Smaga",
"text": "Web extension, web process. I should reload the page?"
},
{
"time": "18:10:47",
"speaker": "Alex Martemyanov",
"text": "Yes, in general."
},
{
"time": "18:10:49",
"speaker": "Michal Smaga",
"text": "Do I need to do it, like, quickly, or do I need to, like…"
},
{
"time": "18:10:53",
"speaker": "Alex Martemyanov",
"text": "Um…"
},
{
"time": "18:10:53",
"speaker": "Michal Smaga",
"text": "Wait a bit."
},
{
"time": "18:10:55",
"speaker": "Alex Martemyanov",
"text": "Usually… yeah. I don't know, within one second, just kill the process, then reload the page."
},
{
"time": "18:11:02",
"speaker": "Michal Smaga",
"text": "Yeah."
},
{
"time": "18:11:03",
"speaker": "Alex Martemyanov",
"text": "If it doesn't work from the first try, you just give it and reload again, and usually from second attempt, it does, uh… Uh, hang the… the extension. So it's not… it's not the genuine issue, so it's the…"
},
{
"time": "18:11:20",
"speaker": "Michal Smaga",
"text": "Yeah, artificial."
},
{
"time": "18:11:22",
"speaker": "Alex Martemyanov",
"text": "artificial reproducing step that we didn't enable with the feature flag of the fix that went before, but it should be still here, and we… and allow to… To produce it. Uh, that's… So generally, yeah, I think you've seen the comment I posted to… to the… Project communication task. And the data, the data analysis."
},
{
"time": "18:11:52",
"speaker": "Michal Smaga",
"text": "Yeah, yeah, yeah."
},
{
"time": "18:11:52",
"speaker": "Alex Martemyanov",
"text": "So… so generally there is, uh… yeah, it's kind of heavy codecs and cloud work, and, um… I cannot… Oh. I cannot tell that I understand, like, 100% what is happening beneath, uh, under the hood, and… Um… Generally, we have reproduced most of the… of the stall issues, uh, with some… Thank you. my display on black. Wow. I just need to switch off something, I guess."
},
{
"time": "18:12:35",
"speaker": "Michal Smaga",
"text": "I can hear you, I cannot see you."
},
{
"time": "18:12:36",
"speaker": "Alex Martemyanov",
"text": "Hello? Yeah, I cannot see you, because… Give it a minute. Yeah. No. Fuck. And… Good morning, Mark. Sorry. One moment, Amy. I need to burn off something."
},
{
"time": "18:13:10",
"speaker": "Michal Smaga",
"text": "Did your laptop display died?"
},
{
"time": "18:13:13",
"speaker": "Alex Martemyanov",
"text": "Not yet, I guess. I hope. Uh, here… Here we are. Uh-huh. So, we do. Yeah. All right, I'm back. And… Oh, yeah, I just got some. Testing. Fairness around here. Uh, where was I? Yeah, the issues. Uh, so generally, there's four issues in the work, and uh… One is behind the disabled feature flag. Because it reloads the page, and I don't think it's optimal. And probably a couple of more go next, and we'll leave. the smallest groups for the next iteration, I guess. So here we have to, uh… To expand the diagnostics. So generally, to fulfill the privacy triage, uh, I was requested to… To reduce what we… actually submit, and the decision was to merge the events into a single event. It should not generally harm our, uh… our data. We can lose something in case the browser crashes, or if it's reloaded. But I guess it's acceptable at this point, since we get these isolated groups already. And we just need some proofs. for the remaining and the pixels. Prior to this."
},
{
"time": "18:15:02",
"speaker": "Michal Smaga",
"text": "Yes. So, so the first…"
},
{
"time": "18:15:04",
"speaker": "Alex Martemyanov",
"text": "Pixel fire for the pixel, yeah."
},
{
"time": "18:15:06",
"speaker": "Michal Smaga",
"text": "First PR is the pixels, yeah? So the one from the PR."
},
{
"time": "18:15:09",
"speaker": "Alex Martemyanov",
"text": "Yes, so the suggestion is to improve the diagnostics first, and then the stacked ones go onto it."
},
{
"time": "18:15:18",
"speaker": "Michal Smaga",
"text": "Yeah, and what is the status of the other, like, PRs, the follow-up ones, with the fixes?"
},
{
"time": "18:15:24",
"speaker": "Alex Martemyanov",
"text": "Uh, so we have the… the recovery. And… First one is InitLoss. And InitLoss includes P1 and P2 as inputs. As I remember. Yeah, and P4, that's not enabled at the moment. It's, uh, 7379. It should be… Should be generated already. For review. And another one is 7459. It's also open. And… Well, generally, should also be pretty much ready, so the… There is integration tests, integration test harness that's supposed to only be run once to reproduce the issue."
},
{
"time": "18:16:38",
"speaker": "Michal Smaga",
"text": "Mm-hmm."
},
{
"time": "18:16:39",
"speaker": "Alex Martemyanov",
"text": "In, like, lab condition."
},
{
"time": "18:16:40",
"speaker": "Michal Smaga",
"text": "Can you say. Which one was the last PR?"
},
{
"time": "18:16:45",
"speaker": "Alex Martemyanov",
"text": "The last one, uh, 7459. This one."
},
{
"time": "18:17:00",
"speaker": "Michal Smaga",
"text": "Yeah, yeah, yeah, I got it, yeah, the network one, yeah."
},
{
"time": "18:17:11",
"speaker": "Alex Martemyanov",
"text": "So the first, that is 7379, it should… So basically, we guess that it may be not an issue. And it's maybe an issue of slow. Slow loading and the fix itself is triggering the background will be load with the navigation itself. Because, uh, the initial… initial startup, or return from background, maybe not, uh, warming up the web view. Or, um… Or our extension. And, uh… The situation with P4 is that we may need to reload the page after, you know, after the extension is loaded, so it is applied to the page. And, uh, I was planning to investigate it further. Is there a way to run the… Plug in after the page is already loaded, maybe send another page load event. And see if it… if it just works. Uh, but the reload is there. And the feature flag."
},
{
"time": "18:18:36",
"speaker": "Michal Smaga",
"text": "And do you think, like, uh… Are we able to detect the fourth one without the feature flag? Just to get the pixels about, like, how…"
},
{
"time": "18:18:48",
"speaker": "Alex Martemyanov",
"text": "Just to get the pixels… yeah, I guess so. I guess so we can make the pixel."
},
{
"time": "18:18:59",
"speaker": "Michal Smaga",
"text": "Yeah, because it would be get, like. It's good to get the signal, like, how many of those cases they potentially would be fixed by the future flag."
},
{
"time": "18:19:11",
"speaker": "Alex Martemyanov",
"text": "Yeah, I agree."
},
{
"time": "18:19:12",
"speaker": "Michal Smaga",
"text": "Yeah, but I mean, like, reloading the page is kind of, like, a risky thing, yeah, it can be disruptive, and… The question is, like, how frequently it would be."
},
{
"time": "18:19:22",
"speaker": "Alex Martemyanov",
"text": "Mm-hmm."
},
{
"time": "18:19:23",
"speaker": "Michal Smaga",
"text": "Yeah, and probably we would also have, like, the question is, like, how much confidence that they are actually, like, experiencing the problem. Just not to do the the, like, the reload. When there's no… not an issue for that."
},
{
"time": "18:19:57",
"speaker": "Alex Martemyanov",
"text": "Okay, and the next one is the network. Network process crash. Uh, it's a bit trickier. I… I didn't finish going through it. Actually… But, uh… So general state of it, it's kind of reproduced on the integration test harness. And the fix… Seems… to fix it. So, again, it's kinda… not… non-proved concepts and kind of speculative fixes. And we are hoping to… So first of all, those should be feature flagged, just in case anything goes wrong with it. You can private selectors or whatever are disturbing. The overall extension flow, so we could disable it remotely, and uh… Yeah, so again, I'm… Oh… Not 100% sure on those, but how it is reproduced in the test harness and by the automation. It seems we could use those fixes. Another one pending, it's not opened yet, is the base URL thing. And, uh… And the speculative steps to reproduce is, uh, if we reload the, um… if we update the web extension. it changes the base URL. Because we don't have this table base irrelevant. Those… It was flagged in the early research phase. Uh, what I'm not sure with it, uh, does it harm any… Can it bring any privacy or security concerns with it if we…"
},
{
"time": "18:22:09",
"speaker": "Michal Smaga",
"text": "But which base? I, I don't, I don't get it, like, fully, like, with me."
},
{
"time": "18:22:13",
"speaker": "Alex Martemyanov",
"text": "The extension was 0. So it's UUID that's generated for the extension every time it's launched. And when it changes, it brings some… Disturbance into the web extension."
},
{
"time": "18:22:28",
"speaker": "Michal Smaga",
"text": "Okay."
},
{
"time": "18:22:29",
"speaker": "Alex Martemyanov",
"text": "And if we set it fixed as a fixed UID. For our web extension, it generally follows the WebKit rules as I understand it and may fix another part of the failures."
},
{
"time": "18:22:44",
"speaker": "Michal Smaga",
"text": "Mhmm. But it's only only on update, like, when we uninstall and install again, right?"
},
{
"time": "18:22:45",
"speaker": "Alex Martemyanov",
"text": "And, uh… Yeah, but I, uh… I can guess it may be some significant portion of users that receive the service related to the app updates. As, uh, as it was, uh, as it was… described and issued initially."
},
{
"time": "18:23:14",
"speaker": "Michal Smaga",
"text": "Okay, so it's like, uh… 3… Three PRs with fixes. and potentially four."
},
{
"time": "18:23:24",
"speaker": "Alex Martemyanov",
"text": "Mmhm. network, the P1 one, uh, base URL. One for the loading. And, uh, yeah, potentially the fifth one. So, yeah, currently there is four, uh, four fixes in… in my… On my… work."
},
{
"time": "18:23:53",
"speaker": "Michal Smaga",
"text": "So, do you have any, like, doubts, like, that, like, some of the fixes are, like, too risky, and, like, for example, the reload one? you would be not too sure about, like, shipping that one? Because I'm just, like, thinking…"
},
{
"time": "18:24:05",
"speaker": "Alex Martemyanov",
"text": "Uh, Zip?"
},
{
"time": "18:24:07",
"speaker": "Michal Smaga",
"text": "thinking about, like, probably we can have the questions from Russell or someone, like. How much more time we can spend here, like, just to, like, focus on the, like, bare minimum, because probably, like, just to, like… better calculate the effort that we want to put into it."
},
{
"time": "18:24:27",
"speaker": "Alex Martemyanov",
"text": "Yeah, generally, we already had this question by Russell, as I mentioned, and I tried to answer it today."
},
{
"time": "18:24:30",
"speaker": "Michal Smaga",
"text": "Yeah, yeah, yeah."
},
{
"time": "18:24:37",
"speaker": "Alex Martemyanov",
"text": "No, we've seen it. Uh, so the issue here is, uh, that we cannot distribute. the failures. You cannot tell there is one main… ah, yeah, there is another. Another one… And… Great deeds. Yeah, another genuine one that is kind of proved is window git close. So the original. Window and tab merging management, uh, fix it, uh… It didn't cover every… Every issue with the pin tab, and there is still one more remaining, uh, for the window closing, and, uh, yeah, should be a short one. Uh, it should cover the genuine issue of closing in tab using the web extension."
},
{
"time": "18:25:31",
"speaker": "Michal Smaga",
"text": "But it's only McCoy, right?"
},
{
"time": "18:25:32",
"speaker": "Alex Martemyanov",
"text": "I don't know. Yeah, my question. So, yeah, that is, uh, for… Four, one, two, three, one, two, three, four main groups that are targeted here, one requiring the page reload. And the P3 that, uh, without… Context without view, it may be the pin tab. And we have one iOS of 0.03%. macOS at around 6%, but it may be wrong. And we have the other group that cannot be considered at the moment. Maybe it gets fixed with the four fixes, or maybe we receive some more data. So I try to express this point in the conversation task. But if the hypothesis are correct, we should cover most of the cases."
},
{
"time": "18:26:37",
"speaker": "Michal Smaga",
"text": "So, do you estimate to get them done this week?"
},
{
"time": "18:26:37",
"speaker": "Alex Martemyanov",
"text": "So, yeah. Yeah, so the point here is to timebox it to…"
},
{
"time": "18:26:45",
"speaker": "Michal Smaga",
"text": "To merge it this week, and so we can, like, get it internally next week, right?"
},
{
"time": "18:26:45",
"speaker": "Alex Martemyanov",
"text": "Two currents. Yeah. Yeah, so if we… if we get it to the release… I mean, the data analysis, the data attribution extension, and those fixes, if we get it to internal. Today and tomorrow. Uh, we can reason about it on… Next week."
},
{
"time": "18:27:11",
"speaker": "Michal Smaga",
"text": "Okay, so you would mean to merge it to… Release branches."
},
{
"time": "18:27:17",
"speaker": "Alex Martemyanov",
"text": "Yes, if it's possible."
},
{
"time": "18:27:22",
"speaker": "Michal Smaga",
"text": "So, the two first PRs, like, one for the telemetry for the pixels, and the second with the P1 and P2, right?"
},
{
"time": "18:27:31",
"speaker": "Alex Martemyanov",
"text": "Um… It depends, I guess, if we can do it, if it's possible, I would give a go for all of them. Again, behind the feature flags."
},
{
"time": "18:27:43",
"speaker": "Michal Smaga",
"text": "Yeah, let's try. So, like, I'm… I'm… I'm… I'm done, like… reading and commenting for the first PRs, there are a couple of, like. leftovers for the dead code, so please check the comments. I'll try to, like, try forcing to reproduce it."
},
{
"time": "18:27:55",
"speaker": "Alex Martemyanov",
"text": "Mmhm."
},
{
"time": "18:28:01",
"speaker": "Michal Smaga",
"text": "So so I get it and then I can move to the next PR. I can focus today on that. So we have the the the chart."
},
{
"time": "18:28:08",
"speaker": "Alex Martemyanov",
"text": "Okay, good. And when we have those reviewed, we can open the exception and try to push it to the internal."
},
{
"time": "18:28:18",
"speaker": "Michal Smaga",
"text": "I mean, like, if it's, like, Monday, Tuesday, you can do it probably, like, for free."
},
{
"time": "18:28:24",
"speaker": "Alex Martemyanov",
"text": "Mm-hmm, okay."
},
{
"time": "18:28:24",
"speaker": "Michal Smaga",
"text": "If it's later than tomorrow. Yeah. Okay. Okay, so let's try to do that."
},
{
"time": "18:28:30",
"speaker": "Alex Martemyanov",
"text": "Okay, I'll… I'll keep you pinged, yeah."
},
{
"time": "18:28:31",
"speaker": "Michal Smaga",
"text": "And… Please ping me when you have the following one, because I want to, like…"
},
{
"time": "18:28:37",
"speaker": "Alex Martemyanov",
"text": "Mm-hmm."
},
{
"time": "18:28:38",
"speaker": "Michal Smaga",
"text": "Schedule the time for them, uh, like, in between my, my work, just to, just to not, like… Delay you. Uh, yeah."
},
{
"time": "18:28:47",
"speaker": "Alex Martemyanov",
"text": "Yeah, I guess it's… I guess it may take some time, maybe the rest of your day today, and those two PRs. Could feel it."
},
{
"time": "18:28:58",
"speaker": "Michal Smaga",
"text": "Yeah, so I'll focus on that, not to block you, so let's push for the first two ones, and yeah."
},
{
"time": "18:29:04",
"speaker": "Alex Martemyanov",
"text": "Mmhm."
},
{
"time": "18:29:04",
"speaker": "Michal Smaga",
"text": "And the others, like, later in the week."
},
{
"time": "18:29:07",
"speaker": "Alex Martemyanov",
"text": "Mm-hmm."
},
{
"time": "18:29:08",
"speaker": "Michal Smaga",
"text": "Yeah, I agree."
},
{
"time": "18:29:09",
"speaker": "Alex Martemyanov",
"text": "So, and yeah."
},
{
"time": "18:29:10",
"speaker": "Michal Smaga",
"text": "Just to try to get them out as soon as possible to get some results."
},
{
"time": "18:29:16",
"speaker": "Alex Martemyanov",
"text": "And yes, since it's highly speculative, I would give it another mid-mortem. So yeah, time box it to this week. I'd say to the first half of this week. Because there is not much work really to be done about it. Just, uh… Just so you know, I have, like, a huge testing harness work tree, and I'm trying to split the parts from it that reproduce one another issue and make it into…"
},
{
"time": "18:29:48",
"speaker": "Michal Smaga",
"text": "No doubt."
},
{
"time": "18:29:53",
"speaker": "Alex Martemyanov",
"text": "into digestible pull requests. But generally, most of them are kind of reproduced in the lab. But we have no any proofs that they actually match the production issues because they are based on the event sequence that we get."
},
{
"time": "18:30:08",
"speaker": "Michal Smaga",
"text": "Yeah."
},
{
"time": "18:30:14",
"speaker": "Alex Martemyanov",
"text": "We got to produce the event sequence that we are receiving, but we still cannot reason about the real issues leading to those. So, yeah, that's the state. All right, thank you. I won't take more of your time."
},
{
"time": "18:30:31",
"speaker": "Michal Smaga",
"text": "So, after this week, you would put the, like, you would have the mid-mortem this week, or, like, next week after the…"
},
{
"time": "18:30:41",
"speaker": "Alex Martemyanov",
"text": "Next week, so let's try to get it out and have some data. The meeting is on Tuesday, right? So we could have the data analyzed and, uh, have a mid-mortem. and decide on the next steps whether we need. Keep on going, or we are satisfied with those, or we just give up and…"
},
{
"time": "18:31:06",
"speaker": "Michal Smaga",
"text": "Yeah. But do you think, like, on Tuesday, you will have, like, any meaningful data? It will be, like, just out for two days. Right?"
},
{
"time": "18:31:13",
"speaker": "Alex Martemyanov",
"text": "Uh, yes, we should, uh, since we… we received most of the current data by Tuesday. And it didn't change significantly throughout the week. I think there is a lot of issues are reported."
},
{
"time": "18:31:36",
"speaker": "Michal Smaga",
"text": "Okay."
},
{
"time": "18:31:37",
"speaker": "Alex Martemyanov",
"text": "And there's more than enough data to analyze. So, yeah, Tuesday should be should be fine to have a big more time. I'll probably update the comments. Highlighting this."
},
{
"time": "18:31:51",
"speaker": "Michal Smaga",
"text": "Okay, sounds good. Okay, so I'm back to reviewing it, and, like, let's… Probably tomorrow you can, like, will you be on the OE weekly?"
},
{
"time": "18:32:05",
"speaker": "Alex Martemyanov",
"text": "Yes, tomorrow, tomorrow, tomorrow, tomorrow is Tuesday, yes, I think so."
},
{
"time": "18:32:11",
"speaker": "Michal Smaga",
"text": "Yeah, so we can recap the plan and see. So this is, like, your top priority, right? You're focusing on…"
},
{
"time": "18:32:20",
"speaker": "Alex Martemyanov",
"text": "Yeah, yeah. So, I mean, there is, uh, there is enough work for me outside of the top priority. Like where you are and pushing other stuff forward. But, yeah."
},
{
"time": "18:32:39",
"speaker": "Michal Smaga",
"text": "Makes sense. Cool. Are you blocked by anything, or just, like, this is, like… The general, like, work is enough for you."
},
{
"time": "18:32:49",
"speaker": "Alex Martemyanov",
"text": "Alright. Blocked with the data missing. And, uh, so… Only the pull requests are on the plate. Bottle making it. And, uh, yeah, the gaps between the releases, so we… keep perceiving it and. Analyzing how it goes."
},
{
"time": "18:33:11",
"speaker": "Michal Smaga",
"text": "Have you assigned me to all of the PRs? Because, uh, I see them…"
},
{
"time": "18:33:15",
"speaker": "Alex Martemyanov",
"text": "Not yet, I guess. Let me assign the network process. I didn't go through it myself yet, but yeah, I've assigned it to you."
},
{
"time": "18:33:29",
"speaker": "Michal Smaga",
"text": "Yeah, I think, like, something is broken with the…"
},
{
"time": "18:33:33",
"speaker": "Alex Martemyanov",
"text": "Yeah, yeah, I'll… I'm on it."
},
{
"time": "18:33:36",
"speaker": "Michal Smaga",
"text": "No, no, like, I mean, like, uh, I'm browsing through the, the, this PR, these are the PRs, and, like, I'm filtering by the assigned to me. And I only picked it up."
},
{
"time": "18:33:47",
"speaker": "Alex Martemyanov",
"text": "Ah, assignees. I need to assign them. We generally don't assign the PRs, just set a reviewer."
},
{
"time": "18:33:54",
"speaker": "Michal Smaga",
"text": "I don't know, like, you have the filter, like, review requested."
},
{
"time": "18:34:00",
"speaker": "Alex Martemyanov",
"text": "Mm-hmm."
},
{
"time": "18:34:01",
"speaker": "Michal Smaga",
"text": "They can…"
},
{
"time": "18:34:01",
"speaker": "Alex Martemyanov",
"text": "Yeah, let me just send. Yes, I need. and requests. Yeah, so there is three pull requests."
},
{
"time": "18:34:07",
"speaker": "Michal Smaga",
"text": "Can you… can you see? So those are, like, open PRs from you all, but you have the filter for review, and it's, like, awaiting review from…"
},
{
"time": "18:34:14",
"speaker": "Alex Martemyanov",
"text": "Yep."
},
{
"time": "18:34:18",
"speaker": "Michal Smaga",
"text": "Me? I only get two of them."
},
{
"time": "18:34:24",
"speaker": "Alex Martemyanov",
"text": "Okay. 7, 4, 5, 5, 7."
},
{
"time": "18:34:26",
"speaker": "Michal Smaga",
"text": "Which is weird."
},
{
"time": "18:34:29",
"speaker": "Alex Martemyanov",
"text": "Oh, 7376 is missing for some reason. Probably you gave a review for it already. And it's waiting for…"
},
{
"time": "18:34:38",
"speaker": "Michal Smaga",
"text": "Okay."
},
{
"time": "18:34:40",
"speaker": "Alex Martemyanov",
"text": "For the resolutions. Angus."
},
{
"time": "18:34:43",
"speaker": "Michal Smaga",
"text": "Okay, so maybe it's like, yeah."
},
{
"time": "18:34:46",
"speaker": "Alex Martemyanov",
"text": "Yeah, so currently two more in stock."
},
{
"time": "18:34:50",
"speaker": "Michal Smaga",
"text": "Okay. So it's it's in the stack, so I can get them from from the list. Right?"
},
{
"time": "18:34:55",
"speaker": "Alex Martemyanov",
"text": "Yep."
},
{
"time": "18:34:56",
"speaker": "Michal Smaga",
"text": "Okay, cool. Can I help you in any other way?"
},
{
"time": "18:34:59",
"speaker": "Alex Martemyanov",
"text": "Review stuck. Yes, stuck, stuck, stuck. Create stuck. Create stuck. And now those are in the stacks. Okay, good."
},
{
"time": "18:35:15",
"speaker": "Michal Smaga",
"text": "Do you need any other help?"
},
{
"time": "18:35:18",
"speaker": "Alex Martemyanov",
"text": "Not at the moment. I'm going to update the first one, telemetry one. And give you a ping, and uh… And when I complete the third one, I'll ping you as well, and probably… Probably the window did close, should be an easy one for today. As well. If it sounds good."
},
{
"time": "18:35:46",
"speaker": "Michal Smaga",
"text": "Okay. Okay, so I'm on the PRs. Please check the comments for the first one. I'm all moving for the second one."
},
{
"time": "18:35:58",
"speaker": "Alex Martemyanov",
"text": "Sure. Okay, thank you."
},
{
"time": "18:36:03",
"speaker": "Michal Smaga",
"text": "Thank you."
}
]
}
@@ -15,3 +15,133 @@ source: "https://us01mynotes.zoom.us/QvxllpCuTTSLGEZp-R6jQw"
- **18:10:01 · Michal Smaga:** Good.
- **18:10:01 · Alex Martemyanov:** I'm pretty good. Jumping between windows. Yes.
- **18:10:09 · Michal Smaga:** Uh, I think I'm, I'm like… done reviewing the first one about the pixel. I had the issue that I wasn't able to reproduce it, like, I was trying to kill the WebKit process.
- **18:10:22 · Alex Martemyanov:** Mm-hmm.
- **18:10:23 · Michal Smaga:** Do you have any, like, extra steps?
- **18:10:27 · Alex Martemyanov:** Uh, so generally it fails from the second try on this exact test page that is attached there.
- **18:10:37 · Michal Smaga:** So after, after I, I killed the, the, the…
- **18:10:37 · Alex Martemyanov:** Okay.
- **18:10:41 · Michal Smaga:** Web extension, web process. I should reload the page?
- **18:10:47 · Alex Martemyanov:** Yes, in general.
- **18:10:49 · Michal Smaga:** Do I need to do it, like, quickly, or do I need to, like…
- **18:10:53 · Alex Martemyanov:** Um…
- **18:10:53 · Michal Smaga:** Wait a bit.
- **18:10:55 · Alex Martemyanov:** Usually… yeah. I don't know, within one second, just kill the process, then reload the page.
- **18:11:02 · Michal Smaga:** Yeah.
- **18:11:03 · Alex Martemyanov:** If it doesn't work from the first try, you just give it and reload again, and usually from second attempt, it does, uh… Uh, hang the… the extension. So it's not… it's not the genuine issue, so it's the…
- **18:11:20 · Michal Smaga:** Yeah, artificial.
- **18:11:22 · Alex Martemyanov:** artificial reproducing step that we didn't enable with the feature flag of the fix that went before, but it should be still here, and we… and allow to… To produce it. Uh, that's… So generally, yeah, I think you've seen the comment I posted to… to the… Project communication task. And the data, the data analysis.
- **18:11:52 · Michal Smaga:** Yeah, yeah, yeah.
- **18:11:52 · Alex Martemyanov:** So… so generally there is, uh… yeah, it's kind of heavy codecs and cloud work, and, um… I cannot… Oh. I cannot tell that I understand, like, 100% what is happening beneath, uh, under the hood, and… Um… Generally, we have reproduced most of the… of the stall issues, uh, with some… Thank you. my display on black. Wow. I just need to switch off something, I guess.
- **18:12:35 · Michal Smaga:** I can hear you, I cannot see you.
- **18:12:36 · Alex Martemyanov:** Hello? Yeah, I cannot see you, because… Give it a minute. Yeah. No. Fuck. And… Good morning, Mark. Sorry. One moment, Amy. I need to burn off something.
- **18:13:10 · Michal Smaga:** Did your laptop display died?
- **18:13:13 · Alex Martemyanov:** Not yet, I guess. I hope. Uh, here… Here we are. Uh-huh. So, we do. Yeah. All right, I'm back. And… Oh, yeah, I just got some. Testing. Fairness around here. Uh, where was I? Yeah, the issues. Uh, so generally, there's four issues in the work, and uh… One is behind the disabled feature flag. Because it reloads the page, and I don't think it's optimal. And probably a couple of more go next, and we'll leave. the smallest groups for the next iteration, I guess. So here we have to, uh… To expand the diagnostics. So generally, to fulfill the privacy triage, uh, I was requested to… To reduce what we… actually submit, and the decision was to merge the events into a single event. It should not generally harm our, uh… our data. We can lose something in case the browser crashes, or if it's reloaded. But I guess it's acceptable at this point, since we get these isolated groups already. And we just need some proofs. for the remaining and the pixels. Prior to this.
- **18:15:02 · Michal Smaga:** Yes. So, so the first…
- **18:15:04 · Alex Martemyanov:** Pixel fire for the pixel, yeah.
- **18:15:06 · Michal Smaga:** First PR is the pixels, yeah? So the one from the PR.
- **18:15:09 · Alex Martemyanov:** Yes, so the suggestion is to improve the diagnostics first, and then the stacked ones go onto it.
- **18:15:18 · Michal Smaga:** Yeah, and what is the status of the other, like, PRs, the follow-up ones, with the fixes?
- **18:15:24 · Alex Martemyanov:** Uh, so we have the… the recovery. And… First one is InitLoss. And InitLoss includes P1 and P2 as inputs. As I remember. Yeah, and P4, that's not enabled at the moment. It's, uh, 7379. It should be… Should be generated already. For review. And another one is 7459. It's also open. And… Well, generally, should also be pretty much ready, so the… There is integration tests, integration test harness that's supposed to only be run once to reproduce the issue.
- **18:16:38 · Michal Smaga:** Mm-hmm.
- **18:16:39 · Alex Martemyanov:** In, like, lab condition.
- **18:16:40 · Michal Smaga:** Can you say. Which one was the last PR?
- **18:16:45 · Alex Martemyanov:** The last one, uh, 7459. This one.
- **18:17:00 · Michal Smaga:** Yeah, yeah, yeah, I got it, yeah, the network one, yeah.
- **18:17:11 · Alex Martemyanov:** So the first, that is 7379, it should… So basically, we guess that it may be not an issue. And it's maybe an issue of slow. Slow loading and the fix itself is triggering the background will be load with the navigation itself. Because, uh, the initial… initial startup, or return from background, maybe not, uh, warming up the web view. Or, um… Or our extension. And, uh… The situation with P4 is that we may need to reload the page after, you know, after the extension is loaded, so it is applied to the page. And, uh, I was planning to investigate it further. Is there a way to run the… Plug in after the page is already loaded, maybe send another page load event. And see if it… if it just works. Uh, but the reload is there. And the feature flag.
- **18:18:36 · Michal Smaga:** And do you think, like, uh… Are we able to detect the fourth one without the feature flag? Just to get the pixels about, like, how…
- **18:18:48 · Alex Martemyanov:** Just to get the pixels… yeah, I guess so. I guess so we can make the pixel.
- **18:18:59 · Michal Smaga:** Yeah, because it would be get, like. It's good to get the signal, like, how many of those cases they potentially would be fixed by the future flag.
- **18:19:11 · Alex Martemyanov:** Yeah, I agree.
- **18:19:12 · Michal Smaga:** Yeah, but I mean, like, reloading the page is kind of, like, a risky thing, yeah, it can be disruptive, and… The question is, like, how frequently it would be.
- **18:19:22 · Alex Martemyanov:** Mm-hmm.
- **18:19:23 · Michal Smaga:** Yeah, and probably we would also have, like, the question is, like, how much confidence that they are actually, like, experiencing the problem. Just not to do the the, like, the reload. When there's no… not an issue for that.
- **18:19:57 · Alex Martemyanov:** Okay, and the next one is the network. Network process crash. Uh, it's a bit trickier. I… I didn't finish going through it. Actually… But, uh… So general state of it, it's kind of reproduced on the integration test harness. And the fix… Seems… to fix it. So, again, it's kinda… not… non-proved concepts and kind of speculative fixes. And we are hoping to… So first of all, those should be feature flagged, just in case anything goes wrong with it. You can private selectors or whatever are disturbing. The overall extension flow, so we could disable it remotely, and uh… Yeah, so again, I'm… Oh… Not 100% sure on those, but how it is reproduced in the test harness and by the automation. It seems we could use those fixes. Another one pending, it's not opened yet, is the base URL thing. And, uh… And the speculative steps to reproduce is, uh, if we reload the, um… if we update the web extension. it changes the base URL. Because we don't have this table base irrelevant. Those… It was flagged in the early research phase. Uh, what I'm not sure with it, uh, does it harm any… Can it bring any privacy or security concerns with it if we…
- **18:22:09 · Michal Smaga:** But which base? I, I don't, I don't get it, like, fully, like, with me.
- **18:22:13 · Alex Martemyanov:** The extension was 0. So it's UUID that's generated for the extension every time it's launched. And when it changes, it brings some… Disturbance into the web extension.
- **18:22:28 · Michal Smaga:** Okay.
- **18:22:29 · Alex Martemyanov:** And if we set it fixed as a fixed UID. For our web extension, it generally follows the WebKit rules as I understand it and may fix another part of the failures.
- **18:22:44 · Michal Smaga:** Mhmm. But it's only only on update, like, when we uninstall and install again, right?
- **18:22:45 · Alex Martemyanov:** And, uh… Yeah, but I, uh… I can guess it may be some significant portion of users that receive the service related to the app updates. As, uh, as it was, uh, as it was… described and issued initially.
- **18:23:14 · Michal Smaga:** Okay, so it's like, uh… 3… Three PRs with fixes. and potentially four.
- **18:23:24 · Alex Martemyanov:** Mmhm. network, the P1 one, uh, base URL. One for the loading. And, uh, yeah, potentially the fifth one. So, yeah, currently there is four, uh, four fixes in… in my… On my… work.
- **18:23:53 · Michal Smaga:** So, do you have any, like, doubts, like, that, like, some of the fixes are, like, too risky, and, like, for example, the reload one? you would be not too sure about, like, shipping that one? Because I'm just, like, thinking…
- **18:24:05 · Alex Martemyanov:** Uh, Zip?
- **18:24:07 · Michal Smaga:** thinking about, like, probably we can have the questions from Russell or someone, like. How much more time we can spend here, like, just to, like, focus on the, like, bare minimum, because probably, like, just to, like… better calculate the effort that we want to put into it.
- **18:24:27 · Alex Martemyanov:** Yeah, generally, we already had this question by Russell, as I mentioned, and I tried to answer it today.
- **18:24:30 · Michal Smaga:** Yeah, yeah, yeah.
- **18:24:37 · Alex Martemyanov:** No, we've seen it. Uh, so the issue here is, uh, that we cannot distribute. the failures. You cannot tell there is one main… ah, yeah, there is another. Another one… And… Great deeds. Yeah, another genuine one that is kind of proved is window git close. So the original. Window and tab merging management, uh, fix it, uh… It didn't cover every… Every issue with the pin tab, and there is still one more remaining, uh, for the window closing, and, uh, yeah, should be a short one. Uh, it should cover the genuine issue of closing in tab using the web extension.
- **18:25:31 · Michal Smaga:** But it's only McCoy, right?
- **18:25:32 · Alex Martemyanov:** I don't know. Yeah, my question. So, yeah, that is, uh, for… Four, one, two, three, one, two, three, four main groups that are targeted here, one requiring the page reload. And the P3 that, uh, without… Context without view, it may be the pin tab. And we have one iOS of 0.03%. macOS at around 6%, but it may be wrong. And we have the other group that cannot be considered at the moment. Maybe it gets fixed with the four fixes, or maybe we receive some more data. So I try to express this point in the conversation task. But if the hypothesis are correct, we should cover most of the cases.
- **18:26:37 · Michal Smaga:** So, do you estimate to get them done this week?
- **18:26:37 · Alex Martemyanov:** So, yeah. Yeah, so the point here is to timebox it to…
- **18:26:45 · Michal Smaga:** To merge it this week, and so we can, like, get it internally next week, right?
- **18:26:45 · Alex Martemyanov:** Two currents. Yeah. Yeah, so if we… if we get it to the release… I mean, the data analysis, the data attribution extension, and those fixes, if we get it to internal. Today and tomorrow. Uh, we can reason about it on… Next week.
- **18:27:11 · Michal Smaga:** Okay, so you would mean to merge it to… Release branches.
- **18:27:17 · Alex Martemyanov:** Yes, if it's possible.
- **18:27:22 · Michal Smaga:** So, the two first PRs, like, one for the telemetry for the pixels, and the second with the P1 and P2, right?
- **18:27:31 · Alex Martemyanov:** Um… It depends, I guess, if we can do it, if it's possible, I would give a go for all of them. Again, behind the feature flags.
- **18:27:43 · Michal Smaga:** Yeah, let's try. So, like, I'm… I'm… I'm… I'm done, like… reading and commenting for the first PRs, there are a couple of, like. leftovers for the dead code, so please check the comments. I'll try to, like, try forcing to reproduce it.
- **18:27:55 · Alex Martemyanov:** Mmhm.
- **18:28:01 · Michal Smaga:** So so I get it and then I can move to the next PR. I can focus today on that. So we have the the the chart.
- **18:28:08 · Alex Martemyanov:** Okay, good. And when we have those reviewed, we can open the exception and try to push it to the internal.
- **18:28:18 · Michal Smaga:** I mean, like, if it's, like, Monday, Tuesday, you can do it probably, like, for free.
- **18:28:24 · Alex Martemyanov:** Mm-hmm, okay.
- **18:28:24 · Michal Smaga:** If it's later than tomorrow. Yeah. Okay. Okay, so let's try to do that.
- **18:28:30 · Alex Martemyanov:** Okay, I'll… I'll keep you pinged, yeah.
- **18:28:31 · Michal Smaga:** And… Please ping me when you have the following one, because I want to, like…
- **18:28:37 · Alex Martemyanov:** Mm-hmm.
- **18:28:38 · Michal Smaga:** Schedule the time for them, uh, like, in between my, my work, just to, just to not, like… Delay you. Uh, yeah.
- **18:28:47 · Alex Martemyanov:** Yeah, I guess it's… I guess it may take some time, maybe the rest of your day today, and those two PRs. Could feel it.
- **18:28:58 · Michal Smaga:** Yeah, so I'll focus on that, not to block you, so let's push for the first two ones, and yeah.
- **18:29:04 · Alex Martemyanov:** Mmhm.
- **18:29:04 · Michal Smaga:** And the others, like, later in the week.
- **18:29:07 · Alex Martemyanov:** Mm-hmm.
- **18:29:08 · Michal Smaga:** Yeah, I agree.
- **18:29:09 · Alex Martemyanov:** So, and yeah.
- **18:29:10 · Michal Smaga:** Just to try to get them out as soon as possible to get some results.
- **18:29:16 · Alex Martemyanov:** And yes, since it's highly speculative, I would give it another mid-mortem. So yeah, time box it to this week. I'd say to the first half of this week. Because there is not much work really to be done about it. Just, uh… Just so you know, I have, like, a huge testing harness work tree, and I'm trying to split the parts from it that reproduce one another issue and make it into…
- **18:29:48 · Michal Smaga:** No doubt.
- **18:29:53 · Alex Martemyanov:** into digestible pull requests. But generally, most of them are kind of reproduced in the lab. But we have no any proofs that they actually match the production issues because they are based on the event sequence that we get.
- **18:30:08 · Michal Smaga:** Yeah.
- **18:30:14 · Alex Martemyanov:** We got to produce the event sequence that we are receiving, but we still cannot reason about the real issues leading to those. So, yeah, that's the state. All right, thank you. I won't take more of your time.
- **18:30:31 · Michal Smaga:** So, after this week, you would put the, like, you would have the mid-mortem this week, or, like, next week after the…
- **18:30:41 · Alex Martemyanov:** Next week, so let's try to get it out and have some data. The meeting is on Tuesday, right? So we could have the data analyzed and, uh, have a mid-mortem. and decide on the next steps whether we need. Keep on going, or we are satisfied with those, or we just give up and…
- **18:31:06 · Michal Smaga:** Yeah. But do you think, like, on Tuesday, you will have, like, any meaningful data? It will be, like, just out for two days. Right?
- **18:31:13 · Alex Martemyanov:** Uh, yes, we should, uh, since we… we received most of the current data by Tuesday. And it didn't change significantly throughout the week. I think there is a lot of issues are reported.
- **18:31:36 · Michal Smaga:** Okay.
- **18:31:37 · Alex Martemyanov:** And there's more than enough data to analyze. So, yeah, Tuesday should be should be fine to have a big more time. I'll probably update the comments. Highlighting this.
- **18:31:51 · Michal Smaga:** Okay, sounds good. Okay, so I'm back to reviewing it, and, like, let's… Probably tomorrow you can, like, will you be on the OE weekly?
- **18:32:05 · Alex Martemyanov:** Yes, tomorrow, tomorrow, tomorrow, tomorrow is Tuesday, yes, I think so.
- **18:32:11 · Michal Smaga:** Yeah, so we can recap the plan and see. So this is, like, your top priority, right? You're focusing on…
- **18:32:20 · Alex Martemyanov:** Yeah, yeah. So, I mean, there is, uh, there is enough work for me outside of the top priority. Like where you are and pushing other stuff forward. But, yeah.
- **18:32:39 · Michal Smaga:** Makes sense. Cool. Are you blocked by anything, or just, like, this is, like… The general, like, work is enough for you.
- **18:32:49 · Alex Martemyanov:** Alright. Blocked with the data missing. And, uh, so… Only the pull requests are on the plate. Bottle making it. And, uh, yeah, the gaps between the releases, so we… keep perceiving it and. Analyzing how it goes.
- **18:33:11 · Michal Smaga:** Have you assigned me to all of the PRs? Because, uh, I see them…
- **18:33:15 · Alex Martemyanov:** Not yet, I guess. Let me assign the network process. I didn't go through it myself yet, but yeah, I've assigned it to you.
- **18:33:29 · Michal Smaga:** Yeah, I think, like, something is broken with the…
- **18:33:33 · Alex Martemyanov:** Yeah, yeah, I'll… I'm on it.
- **18:33:36 · Michal Smaga:** No, no, like, I mean, like, uh, I'm browsing through the, the, this PR, these are the PRs, and, like, I'm filtering by the assigned to me. And I only picked it up.
- **18:33:47 · Alex Martemyanov:** Ah, assignees. I need to assign them. We generally don't assign the PRs, just set a reviewer.
- **18:33:54 · Michal Smaga:** I don't know, like, you have the filter, like, review requested.
- **18:34:00 · Alex Martemyanov:** Mm-hmm.
- **18:34:01 · Michal Smaga:** They can…
- **18:34:01 · Alex Martemyanov:** Yeah, let me just send. Yes, I need. and requests. Yeah, so there is three pull requests.
- **18:34:07 · Michal Smaga:** Can you… can you see? So those are, like, open PRs from you all, but you have the filter for review, and it's, like, awaiting review from…
- **18:34:14 · Alex Martemyanov:** Yep.
- **18:34:18 · Michal Smaga:** Me? I only get two of them.
- **18:34:24 · Alex Martemyanov:** Okay. 7, 4, 5, 5, 7.
- **18:34:26 · Michal Smaga:** Which is weird.
- **18:34:29 · Alex Martemyanov:** Oh, 7376 is missing for some reason. Probably you gave a review for it already. And it's waiting for…
- **18:34:38 · Michal Smaga:** Okay.
- **18:34:40 · Alex Martemyanov:** For the resolutions. Angus.
- **18:34:43 · Michal Smaga:** Okay, so maybe it's like, yeah.
- **18:34:46 · Alex Martemyanov:** Yeah, so currently two more in stock.
- **18:34:50 · Michal Smaga:** Okay. So it's it's in the stack, so I can get them from from the list. Right?
- **18:34:55 · Alex Martemyanov:** Yep.
- **18:34:56 · Michal Smaga:** Okay, cool. Can I help you in any other way?
- **18:34:59 · Alex Martemyanov:** Review stuck. Yes, stuck, stuck, stuck. Create stuck. Create stuck. And now those are in the stacks. Okay, good.
- **18:35:15 · Michal Smaga:** Do you need any other help?
- **18:35:18 · Alex Martemyanov:** Not at the moment. I'm going to update the first one, telemetry one. And give you a ping, and uh… And when I complete the third one, I'll ping you as well, and probably… Probably the window did close, should be an easy one for today. As well. If it sounds good.
- **18:35:46 · Michal Smaga:** Okay. Okay, so I'm on the PRs. Please check the comments for the first one. I'm all moving for the second one.
- **18:35:58 · Alex Martemyanov:** Sure. Okay, thank you.
- **18:36:03 · Michal Smaga:** Thank you.
@@ -23,676 +23,6 @@
"time": "20:05:36",
"speaker": "Jonathan Jackson",
"text": "Mm, got it."
},
{
"time": "20:05:37",
"speaker": "Tom Strba",
"text": "And I think I'm next week. Because I almost got a heart attack when you said that I am…"
},
{
"time": "20:05:40",
"speaker": "Dominik Kapusta",
"text": "Yes, this week is Diego. And sorry for not closing my task."
},
{
"time": "20:05:41",
"speaker": "Jonathan Jackson",
"text": "Okay."
},
{
"time": "20:05:45",
"speaker": "Tom Strba",
"text": "that I am this week."
},
{
"time": "20:05:45",
"speaker": "Jonathan Jackson",
"text": "This week… Why is Diego… I don't see a task… this is a macOS release we're talking about, right?"
},
{
"time": "20:05:52",
"speaker": "Tom Strba",
"text": "Yeah, I think Diego maybe marked it as complete in the beginning of the week, because there's just, like, triage…"
},
{
"time": "20:05:57",
"speaker": "Jonathan Jackson",
"text": "Yes, you're right, Tom, your block is the 26th to the 30th, because that task is missing, I didn't see it, I wasn't looking at the dates, I was just reading the list."
},
{
"time": "20:06:04",
"speaker": "Tom Strba",
"text": "That's okay. Just wanted to be sure."
},
{
"time": "20:06:07",
"speaker": "Jonathan Jackson",
"text": "Okay. Diego is responsible for the release this week. It sounds like he's actually doing that. Is that right?"
},
{
"time": "20:06:08",
"speaker": "Tom Strba",
"text": "Perfect."
},
{
"time": "20:06:14",
"speaker": "Jonathan Jackson",
"text": "He knows. Okay, cool. Thank you."
},
{
"time": "20:06:14",
"speaker": "Dominik Kapusta",
"text": "That's right."
},
{
"time": "20:06:18",
"speaker": "Jonathan Jackson",
"text": "Um, no problem. Okay. Anyway, think about starting your self reviews this week. If you feel like you're gonna need more than a day to knock it out. Bartek, over to you."
},
{
"time": "20:06:31",
"speaker": "Bartek Waresiak",
"text": "Yep, I will be stepping down as IS app DRI. Jacek will take the primary role, and Brindy will take on secondary role. So, yeah, if there is IS drama, if there are IS issues, if there are any urgent things. Go to them! And thank you very much."
},
{
"time": "20:06:57",
"speaker": "Jonathan Jackson",
"text": "All right. Thank you. An, you're next on the agenda."
},
{
"time": "20:07:08",
"speaker": "Anh Do",
"text": "Oh, that was quick. Yeah, so in OK, there have been a few projects that involve native changes required as part of the front-end-led projects. Um, so the background is that they, uh, want to contribute some PR, and, uh, um… AI assisted Pi, of course, and then what have been working for us lately is like depends on the size of the task like I would be the one to like either. Dri the change that they are they want to make, or like they prepare the Pi, and I do a thorough review of that. So and now we want to kind of do this more regularly. And so there was a need for some kind of like guidelines that we can give to contributor from outside the apple team. So I was just starting like a small task to basically collect ideas from people. And if you have anything that we already have somewhere, maybe I could get put in. And so. it becomes something that we can point other people to when they want to contribute to the Apple codebase to ensure our standard and make sure that, like, everything is being done the way that we want. So that's about it. Nice."
},
{
"time": "20:08:19",
"speaker": "Jonathan Jackson",
"text": "Cool, thank you. I just took a quick peek. I see you do mention the engineering expectations. I think that's a good source. We might also want to link… to the onboarding process. Not that they would need to follow all of it, but some of… that's basically our best source of, like, how to get set up with the codebase. So there's probably a little work to do to figure out how to have a slimmed down version of that that folks could follow. And I'm sure other people have other ideas as well. So thank you. Um… Luke, we have a non-Apple person lurking in our midst. Welcome. What can we do for you?"
},
{
"time": "20:08:54",
"speaker": "Luke Andrew",
"text": "Hello. Yes, thanks for having me. Luke from SRE, for people that I haven't met before. Um, this is just a plea for generic Apple help. I don't want to, sort of, get all of your attention to focus on this task. We basically have… a looping client that seems to be sending, uh, requests once a second to us, uh, that is Apple, but not DuckDuckGo Apple, based on the user agent, and doesn't seem to be Safari either. Um… And it's cumulatively across lots of different devices, lots of different queries, sending in the region of 3 million searches a day. Which is substantial, not sort of catastrophic, but substantial enough searches that it's something that we want to deal with. Umm. And I don't really know where to go next to try and understand where it might be coming from or how we might try and reproduce it. So I don't want to solve that in this call, but I just wanted to bring your attention to the task. And if there's anyone who thinks they might be able to help, I'd really appreciate. a second pair of eyes, and pointed out that it's not even worth, with what we have at the moment, that we can, like, escalate this to Apple, because we just don't have enough, uh, information to get any help from them. So yeah, that's it. If anyone has any questions immediately or async, just pop them on the task. Yeah, that's all I have."
},
{
"time": "20:10:18",
"speaker": "BA",
"text": "Quick one, Luke."
},
{
"time": "20:10:18",
"speaker": "Jonathan Jackson",
"text": "This is not from a single client, but from a particular app version, potentially, is that right?"
},
{
"time": "20:10:24",
"speaker": "Luke Andrew",
"text": "Yeah. Yeah."
},
{
"time": "20:10:24",
"speaker": "Jonathan Jackson",
"text": "Okay. You know, be scared that it was one client going crazy. Okay, um…"
},
{
"time": "20:10:30",
"speaker": "BA",
"text": "Yeah, I was going to ask, what's the — we eliminated bots from the equation. Are we happy that it's not bots?"
},
{
"time": "20:10:36",
"speaker": "Luke Andrew",
"text": "It doesn't look like bots. The queries all look human. The rate is really low compared with bots. The moment that I put in a block for it and it immediately stopped, like redirected away."
},
{
"time": "20:10:39",
"speaker": "BA",
"text": "Okay. Right."
},
{
"time": "20:10:52",
"speaker": "Luke Andrew",
"text": "It got, like, a 302 from deep, and then just immediately stopped, so that doesn't feel like… bossy behavior either. They normally persist a little bit and then give up. Whereas this was just immediately, it broke out of whatever loop it was in and stopped."
},
{
"time": "20:11:09",
"speaker": "Jonathan Jackson",
"text": "Interesting."
},
{
"time": "20:11:10",
"speaker": "Luke Andrew",
"text": "Uh, so don't all take a look, because that would be a waste of time, but if you think you can help, um, I'd appreciate a pair of eyes. I'm gonna drop off. Thank you all for having me."
},
{
"time": "20:11:19",
"speaker": "Jonathan Jackson",
"text": "Yeah, one last quick question. It sounds like you're treating this as something that definitely needs attention, but not an incident at this point. Is that correct?"
},
{
"time": "20:11:25",
"speaker": "Luke Andrew",
"text": "Yeah, that's correct. It's been going on for… Based on… um, how we categorize queries for, um, like, ads perspectives. These get classified as a separate category based on user agents, so we don't send them to Bing and say, these are definitely good queries. Um, it's been happening for about a month. So it's, at the moment, not urgent. I'm gonna raise it with SRE, maybe, and see if we think it should be an incident that we just let run, but at the moment, that's not how we'."
},
{
"time": "20:11:55",
"speaker": "Jonathan Jackson",
"text": "Okay. Great. Thank you for the clarity there. Uh, and yeah, if anybody thinks they can help Luke out and figure out what's going on there, feel free to hop into the task. Thanks for coming. Moving on. Alex, you're first in the regular topics list."
},
{
"time": "20:12:16",
"speaker": "Alex Martemyanov",
"text": "Yeah, hey. I have several topics for today, including the VS Code integration postmortem to run later. And the first one goes with a proposal. The proposal is pretty short. And kind of related to the, uh, recent incident with Mac OS 12 crash. that we are not. Testing for macOS 12 and 13, I guess, because we are missing the infrastructure on CI runners. And the suggestion is pretty simple to extract the macOS UI tests target from the main macOS Xcode project, leaving it as a separate macOS project inside the. uh, Xcode workspace. So it will be available the same way it is now, and, uh, runnable. So only, uh, the only issue I can see for those who use, uh, the actual macOS Xcode project instead of the workspace. they would have to switch to another project to run the tests. So, I just wanted to hear if there is any concerns or objectives against it."
},
{
"time": "20:13:39",
"speaker": "Dominik Kapusta",
"text": "I think some time ago, we… someone asked… who uses or doesn't use Workspace, and people who didn't use Workspace were in a… In a minority, anyway, like, very few of them, so… I guess… I could move to the workspace."
},
{
"time": "20:14:06",
"speaker": "Jonathan Jackson",
"text": "I think it'd be good to ask that question in that proposal, at least more explicitly, and just give people a chance to chime in if they feel like that would be a hurdle. Um… Other question for me is, is there… should we think about the iOS side of this as well, and to match… structure, or is this really a macOS only question?"
},
{
"time": "20:14:26",
"speaker": "Alex Martemyanov",
"text": "Okay. Maybe, I… Didn't think about it, actually. And the main concerns here is the compatibility. So we can reach macOS 12 compatibility, at least for some local runners that I'm going to present further. And the build times, so we have package fetching and building for every macOS runner that runs the UI tests and any of the dependencies. None of the dependencies are used during the runs, so it's a 10-second step for each runner that can be easily omitted, and so, yeah. And yeah, it's not related to the main browser targets, so there's no risks. Uh, and they're both, uh, U.S. Probably to think about it in the ER."
},
{
"time": "20:15:25",
"speaker": "Dominik Kapusta",
"text": "I think iOS is not…"
},
{
"time": "20:15:25",
"speaker": "Jonathan Jackson",
"text": "I mean, I don't have a strong… sorry, I don't have a strong feeling there, I just felt like if we're gonna make this change, like, if it's gonna end up with different structures depending on the app, we should think about whether we really want that to be the case, or if we should do the other."
},
{
"time": "20:15:37",
"speaker": "Alex Martemyanov",
"text": "No, it actually shouldn't change any structure, any file structure, just the project placement."
},
{
"time": "20:15:38",
"speaker": "Jonathan Jackson",
"text": "Screwed up. Yeah, yeah, yeah. Dominic, I interrupted you. I'm sorry."
},
{
"time": "20:15:44",
"speaker": "Dominik Kapusta",
"text": "Ah, no worries, I just wanted to say that iOS is not affected by this at all, because… iOS doesn't need testing on various macOS versions."
},
{
"time": "20:15:51",
"speaker": "Jonathan Jackson",
"text": "Alright. So the limita… this is about dealing with a limitation that comes from Mac OS 12 build, particularly."
},
{
"time": "20:15:59",
"speaker": "Dominik Kapusta",
"text": "Yes."
},
{
"time": "20:16:01",
"speaker": "Alex Martemyanov",
"text": "And bill times."
},
{
"time": "20:16:01",
"speaker": "Dominik Kapusta",
"text": "I'm Bill Times."
},
{
"time": "20:16:02",
"speaker": "Jonathan Jackson",
"text": "Got it. Okay. thanks for pointing it out. Uh, like I said, I think you might want to give people a little bit more time to respond to async if they have… particularly if they feel like the… Workspace thing is gonna be a hurdle, but my guess is it's not gonna be a big issue. Uh…"
},
{
"time": "20:16:22",
"speaker": "Alex Martemyanov",
"text": "Okay."
},
{
"time": "20:16:24",
"speaker": "Jonathan Jackson",
"text": "Next topic."
},
{
"time": "20:16:24",
"speaker": "Alex Martemyanov",
"text": "We can…"
},
{
"time": "20:16:26",
"speaker": "Jonathan Jackson",
"text": "From you, also."
},
{
"time": "20:16:26",
"speaker": "Alex Martemyanov",
"text": "Perfect. To the next topic then. Yeah, so, uh, this is another iteration of, uh, the Verfield project. I've been live coding for a while already. Uh, so this is the current state of things. It's changed a little bit, some of you may remember the first, uh, first demo. Uh, so the change is it's, uh, migrated to Go language, and, uh, now it runs on TART system that's used on, uh… We tried runners, I guess. And so the system is here to show you the available images, available runners and locations. So here you see I can have it. stored on the external SSD, because I have my internal 2TB ETH. up to completely, and I have the old MacBook Pro also managed from the same environment. And, uh, you can add other machines as well. Uh, so this is, uh, a wrapper around the TART system that manages, uh, Xcode installs, uh, SIP protection, and, uh, for virtual machine and real machines. Uh, if you use older hardware and, uh. It's, uh… basically providing MCP server for AI clients to. to run these UI tests. Mostly. on the older virtual machines. It can be not older virtual machines, but actual virtual machines. New refreshable machines as well, sir. Uh, for example, I don't update to macOS 27, because, uh… I expect some issues, but I use, uh, testing on macOS 27 using this, uh… a virtual machine system. And so basically the… Again, I have a question to the team in… In the light of a recent discussion of testing on order. macOS versions, for example, whether should I try to push it forward to, like, team-wide? So the idea… the idea is to be able, uh… again, we'll… And in the post-mortem. for the VS Code integration projects. So here you can see VS Code. Basically, it's running the Google browser. It can… run iOS browser as well, in simulator, and in addition, it can also run remote debugging, unlike Xcode, which had supported remote debugging. in a long time ago, but currently lacks the ability, so… Integrating these systems together allows, like, click one button. choose the virtual machine you want to run to test on, and it builds, deploys, and debugs in real time without any lags for library symbols transfer and other stuff. So it just works like you would do on your host machine, but in the virtual machine. So I wanted to hear opinions whether should be. try to adopt this team wide."
},
{
"time": "20:20:06",
"speaker": "Dominik Kapusta",
"text": "I can offer an opinion."
},
{
"time": "20:20:09",
"speaker": "Alex Martemyanov",
"text": "Nobody wants to."
},
{
"time": "20:20:09",
"speaker": "Dominik Kapusta",
"text": "uh… No, well, I mean… No one to be the only one commenting, but anyway. This will be the topic of, uh, of, uh, of the upcoming postmortem, uh, as well, that… The Apple engineering expectation of testing on older macOS version is essentially a dead low. We are supposed to test on older macOS versions, but we rarely do it. Perhaps for new features on macOS? I'm not sure. But certainly not for… Small… tasks. I don't think… well, I don't know, but I don't think we bother to test on all the ROS versions, every small version. Change to the UI, especially. And, uh… Because of that, if we had a way, and also we can't, we are unable to test in CI. So, if… I had a way to… Ask an agent to… run UI tests on a virtual machine. on an arbitrary OS version, that would be great. I would like to see the demo of that, actually. That would be awesome. And that is why we might be interested in adopting it. Perhaps."
},
{
"time": "20:21:41",
"speaker": "Alex Martemyanov",
"text": "Yeah, again, about the UI tests, correct point. So sometimes you want to run an agent reproducing an issue, for example, and it's not always convenient to upload it to CI, wait for the UI tests to be run. Look for the results, while if you run it locally on your machine, it will be blocked for 5 minutes, and do the stuff while you take a coffee. So this thing allows you to just run directly from the agent on the same machine in background and provide you screen recording with all this and the results."
},
{
"time": "20:22:22",
"speaker": "Jonathan Jackson",
"text": "Yeah, I mean, I think… You know, your point that our expectations are that we'd be testing on all versions that we support, but in practicality, I think almost nobody actually does that. And particularly with something like as old as Mac OS 12 where we don't have the hardware, we don't have like, most people don't have access to test it to your point, L. Um… I think I'd like to understand a little bit more about how the system would work, what kind of third-party dependencies there are, what it would look like to really set up and what it would cost. I think the idea of we would be able to test. On versions that we say we actually support is pretty appealing."
},
{
"time": "20:23:00",
"speaker": "Alex Martemyanov",
"text": "Okay, so probably the resolution here would be, um… So, first of all, I do use it as my self-made tooling, and uh… if… I can reach it to the point, I can make it to the point when you click a button, install the system, click a button, and it just runs. I think it would be worth. adopting at least as a selected auditory who can. have, uh, the means to testing, like, enough of RAM or some older hardware, uh, like, choose the early adopters and, uh, see how would we… expand it. And, uh, yeah, correct question by, uh, Federico about, uh, older ores. It's another topic that I wanted to raise during the post-mortem. During the incident, actually. Both for the incident, uh, that, uh, having… Maybe one dedicated machine, older machine, maybe somewhere that would run the UI test suite at least once per week for each release would be a great addition, even if it's like a physical machine somewhere. someone's office or home space."
},
{
"time": "20:24:28",
"speaker": "Jonathan Jackson",
"text": "Yeah, that's an interesting idea, too. I think… I guess I think that a proposal here that sort of lays out what a strategy for old testing would be that used this would be maybe a useful next step. Um, because then that would be a place that people could rally around, sort of solving that higher order problem of how do we actually make good on our promise of testing on the systems that we support. And it sounds like this would be one, but maybe not the only tool to consider, or maybe even as a combination. Does that make sense?"
},
{
"time": "20:25:00",
"speaker": "Alex Martemyanov",
"text": "Yep."
},
{
"time": "20:25:01",
"speaker": "Jonathan Jackson",
"text": "Cool. Okay, thank you. Interesting stuff. Sam, you're up next."
},
{
"time": "20:25:10",
"speaker": "SS",
"text": "Yeah, recently I have been chatting with some folks about being able to put Claude workflows in our CI. I talked about this with OT and they told us that they don't want Anthropic tokens being available in public repos. I've created a private repo to host the agents, uh, which is… Pretty bare bones right now. It lives here in the Apple Team Agents repo, it has CI set up, it has the Claude, uh, action set up. I have a workflow first for testing it, uh, just so we can make sure you can actually talk to Claude and back. Um, the only thing I'm waiting for is whether or not we should get a dedicated API key, because I've been told. Two different things from OT. So I'm just waiting to —. Get that sorted out. I think we should get a dedicated one. once we've done that, yeah, we can start doing things like an automation to clean up feature flags and such, like Fernando's, uh, proposed. So, uh, I'll post to Apple Diary once that's ready, but I think you'd be… if you do want to start building automations in this now, like, feel free, uh. As long as it's, you know, not super expensive. Pete, done."
},
{
"time": "20:26:19",
"speaker": "Pete Smith",
"text": "Yeah, thanks, Sam. This, this looks really cool. Just because I've seen, um, like, there's a few different conversations. There's a conversation with this, and there's the Bitrise, you know, running, um. uh… Agentic stuff on Bitrise as well. How does it all fit together? Like, I think I understand it, but, like, say I wanna… say we wanted to, you know, uh, build our feature overnight while we're in bed, um… How could we use this to do that? Or can we?"
},
{
"time": "20:26:43",
"speaker": "SS",
"text": "This is not that. This is definitely not that. This is not like the development environment thing. Yeah, these are not like the development machines. I really just expect these to be like GitHub Actions workflows that just do helpful things with Claude. Uh, and we just need a place to put those. Like, if it weren't for the API key limitation, this would live in the monorepo."
},
{
"time": "20:26:56",
"speaker": "Pete Smith",
"text": "Yep. Yeah, yeah, I guess, I guess what I'm wondering is, so, like, yeah, exactly, we can, we can hit Claude and, um, but, you know, Claude can't, well, build for us, so, like, well, build and check that it's actually working, so where would… say, say even, like, removing feature flag, where would that. On the PR, at the PR station."
},
{
"time": "20:27:17",
"speaker": "SS",
"text": "Yeah, this is something that Fernando and I was talking about, about doing some kind of coordination between these repos where the monorepo would talk back and forth, do the things that it needs to. This can create a branch. The monorepo can then do the actual testing. Yeah. Right now, I'm just using these for, like, dependability analysis kind of problems, or planning on anyway, which I have a demo for coming up soon."
},
{
"time": "20:27:33",
"speaker": "Pete Smith",
"text": "Okay. Yep. Cool. Yeah, cool. Thanks."
},
{
"time": "20:27:44",
"speaker": "SS",
"text": "Dominic."
},
{
"time": "20:27:46",
"speaker": "Dominik Kapusta",
"text": "Mm-hmm, uh… one of the limitations here is that GitHub Actions workflows are limited to 6 hours of runtime. So…"
},
{
"time": "20:27:53",
"speaker": "SS",
"text": "Also that, yeah."
},
{
"time": "20:27:54",
"speaker": "Dominik Kapusta",
"text": "Yeah. And also, it's, of course, non-interactive. Um… Which is why we're currently trying to figure out if Bitrise… or Bitrise or not, but anyway, looking for some infrastructure provider for, uh… macOS machines that could run Agentic workflows and be… and offer. interaction with them, right? So, uh… Bitrise RDE remote. development environments is one of the options there. Um… That is in progress. For now. They also… it's also quite a fresh feature on their end, and they have some bugs there that we're trying to resolve right now. And we have a CloudOps team member on that as well. the side of… Connecting them to ClickHouse or Sentry. Yeah, so… We'll see in some time."
},
{
"time": "20:28:58",
"speaker": "SS",
"text": "Yeah, yeah, to Dominic's point, like, that problem is much bigger than what this repo is. This really is just, I want to be able to run Claude on an automation, like I currently do on my own machine, and I'm just sick of doing it on my machine. I just want to push that up to GitHub Actions. Have it run on its own, and… Show up with PRs and Asana tasks occasionally, so. Okay."
},
{
"time": "20:29:19",
"speaker": "Jonathan Jackson",
"text": "So the limitations here are that it can… It can inspect code, it can run as an agent, but it can't build and run, so it would… prospectively submit a pull request, and then CIA would tell you whether it did the thing or not."
},
{
"time": "20:29:32",
"speaker": "SS",
"text": "Yeah, the idea that I'm thinking here is that, yeah, like PRs would go over back to the monorepo. This thing would open PRs against the monorepo. And then CI would do its thing over there. Yeah."
},
{
"time": "20:29:38",
"speaker": "Jonathan Jackson",
"text": "Right. Yeah, and if we needed to inspect it from there, we could pull a branch and do whatever else we needed."
},
{
"time": "20:29:46",
"speaker": "SS",
"text": "Yeah."
},
{
"time": "20:29:47",
"speaker": "Jonathan Jackson",
"text": "Okay, cool. Definitely sounds like a good step, even if you're not trying to solve everything all at once, which is reasonable. You're the next topic as well, Sam."
},
{
"time": "20:30:00",
"speaker": "SS",
"text": "Oh, is this the demo? Probably should have just done this all at once. Yeah. So one of the things that I."
},
{
"time": "20:30:04",
"speaker": "Jonathan Jackson",
"text": "Oh, before you… sorry, if you're doing demos, before we get into demos real quick… Uh, we had a note here that we were gonna actually record demos. Um, but we haven't ever done that. Mostly people have opted out of wanting to be recorded, so I wanted to just check in since we have 3 demos here. do we want to record these? Should we rely on the… just the transcript summaries at this point, and whatever tasks people have written? I'm kind of okay either way. Um… I don't know. I don't know that we've ever recorded a demo."
},
{
"time": "20:30:35",
"speaker": "Pete Smith",
"text": "Alessandro. Alessandro is waiting for his Wednesday morning. Won't be the same if we don't record our demo."
},
{
"time": "20:30:39",
"speaker": "Jonathan Jackson",
"text": "Right. That's the question, right? I know, yeah, it's like this is sort of a hard way to do this. So, Sam, would you like me to record or not?"
},
{
"time": "20:30:51",
"speaker": "SS",
"text": "I mean, I've already shown this to Alessandro, so I don't think he cares. Yeah. Up to you. I'm good either way. I remember. Don't worry. This is a super quick one anyway, just to show the initial problem that I'm trying to solve with… with a repo like this. Let me share my screen. Um, so I have, for a while, wanted the other half of the flaky tests project. Right now, we have a flaky test project, which keeps track of, uh, you know, tests that are failing. Um… I have traditionally been more interested in the problem of what are the workflows that are failing, uh, and why, because these things were just, like… this stuff comes up a lot, like, during Xcode upgrades in particular, so… This is something that is being used by Claude to pull the monorepo, get the actions, go and look at the code, figure out what's causing a problem, and report back and give a little write-up about what's going on. Um, the idea being that eventually you could then move something into this ready-to-fix section, and the agent would then go and actually open the PR later. Um, you know, this is just moving a… moving an automation that I've had on my machine is like a daily, like, 10 AM workflow for a while. and just putting it remotely so I don't have to think about it anymore. Which is the ultimate goal. So yeah, this is the kind of thing that I'm trying to do with this repo. Um… As an aside, OT is kind of working on… something along this as well, which I learned about as I was setting up this repo. They are setting up this template, which lives on Dub, for what it's worth, for these kind of analyzing report workflows. Umm. So that might be interesting if you are needing like access from things within the system already. Uh, like, I think Lucas is currently looking at getting that thing to have sentry access and all this kind of stuff, so… Yeah. Go check that project out if you're interested. That's it."
},
{
"time": "20:32:48",
"speaker": "Jonathan Jackson",
"text": "Awesome. Thank you. Pete, you're next."
},
{
"time": "20:32:57",
"speaker": "Pete Smith",
"text": "Yeah, thanks. Yeah, this is in the demo section. It's not really a demo, I guess, but just wanted to share. I'll speak a little bit about, um. ASTAC, so I put a link in… a link into the chat there, so I'm sure people have heard… of… PSTAC, or maybe people have heard of PSTAC. I'm going to just share my screen. So if you haven't, um… Pstack is a plugin created by an engineer at Cursor or SpaceX. It's basically just a set of skills that this engineer found were very good. at, um, fixing bugs, implementing features. So they created the PSTACK plugin. What ASTACK is, is basically just a port of PSTACK. So PSTACK was. built for cursor. So it has a lot of built in you know, instructions in terms of cursor models and how they work so forth. So I just. Ported PSTAC, uh, over… To, uh, ASTAC, um… Basically replacing any of the cursor references with Cloud Code and Codex references. So what AStack is, is a plugin that you can use in Codex or Cloud Code. It's like it sounds very abstract. It's not. It's really just a. A set of skills, a set of playbooks, some defined principles. And they all work together to what I found to just to produce good output. um… So I'll just, I'll talk a little bit in a moment about how ASTAG works. So how it's set up at the moment, you can see on the left, I just have it there under my public, under my own public repo. But if anybody wants to try it out, I would encourage it. You can see like I didn't do a lot of work here. I really want to undersell this. asked an agent to port this over. So take PStack, port it, make sure it works with Cloud Code and Codex. The most work I did was creating that logo you see on the left of the screen, so that's where all my creativity went into. Um… But yeah, you can go here, you can grab the plugin, you can install it in Cloud Code. And you can try it out. I'd recommend trying it out for… for bug fixes, even like small features that are well defined. So, you know, the evidence, like any evidence I have is just anecdotal. I've just found these particular set of skills, these set of playbooks and the principles that are defined just produce very good output. Again, anecdotal. I haven't measured this. I also think it seems to do it at lower token usage. But again, I haven't measured it. So how it works, how ASTAC or PSTAC work is, you know, you install the plugin, it sets up a hook, so at the start of your sessions, the agents are aware that ASTAC is there. And if you say, hey, build this feature or fix this bug or whatever, you can explicitly say. Enter potato mode. But that's actually part of the hook. The agent will know, oh, if you give it a feature or a bug, it will enter potato mode. All that is like a top level skill, which is basically a router. And depending on the task that you give it, like fix this bug or implement this feature. You will go and find the right playbook and follow that playbook and in the playbook. That would reference what skills to use, et cetera. So. again, you know, there's nothing, like, there's nothing magical here. I mean, there's been other plugins that have been very popular. I was talking to Fernando earlier, and we talked about… was it the Superpowers one? I think was another popular plugin. So things like this will probably be, as I was speaking to Fernando about, they'll probably be, can, you know, eventually end up in the harness. Probably won't need plugins like this at some point. But at the moment, this is something I'm using daily. And I find it very beneficial. It just results in really good output. So I would encourage people to try it out. Like, what what, you know, we've seen probably saw the post from Sebastian, from OM. He's creating, like, auto, which is their version of pstack. He just took pstack. And ported that and kind of made it very specific to Duck AI. That's like the the OM version of Pete's group. So if ASTAC, if people find it useful, we could basically turn that into like the Apple version of PSTAC, Apple team version of PSTAC. and… that's something we could do. So yeah, I would just encourage people to try it out, if you're interested. There's an Asana task there that I posted, and you can give any feedback, and if people want to. People find it useful and want to contribute and make it better. We can do that. It's under AI enablement AOR. I spoke for a long time, if anybody has. Sorry, I shared that artifact. Sorry, key. I didn't go through all this artifact."
},
{
"time": "20:37:59",
"speaker": "Pete Smith",
"text": "It's linked in… The Apple Weekly Task, so you can go and look at that artifact, it explains at a very high level how it works. Again, it's not magic, it's just a skill, a ruler, lots of other skills. Sorry, my dog is barking. I don't know if you can hear my dog, but. He's over there barking at me. That's very low. That's it. If anybody has any questions, you can ask me questions, or you can ask me questions later. Jane, sorry, your hand up."
},
{
"time": "20:38:35",
"speaker": "JF",
"text": "Yeah, sorry if you said already and I missed it. What changes have you made over the original piece, Doug?"
},
{
"time": "20:38:42",
"speaker": "Pete Smith",
"text": "Yeah, so… Oh, I'm sorry, it looks like. Okay, dog went dead. Um, yeah, that's why I wanted to undersell it. Like, I didn't, I didn't, I didn't do anything. So, uh, I created that logo. What, what, what I did, or what the agent did, was just port it over, support Pstack over, um, for Cloud Code and Codex. Like, the original Pstack has references to Cursor, and how Cursor. Works. So I just ported it over, so it works in… Um, codecs and cloud code. I didn't add anything additional yet. Um… But the idea will be we can add things if we find them useful. We can add Apple-specific things. If we find them useful. So yeah, no changes really. Sorry, one more thing, James. Thanks for reminding me. I'm going to reshare. Sorry, everybody. Very annoying. I'm going to reshare. So a good question. Like, PStack is being continuously updated. So I have a scheduled task that runs every Monday, looks at the latest PStack, and consumes the latest changes, and, like, ports over the latest changes. So I keep it up to date. So I look at the upstream and keep. a stack up to date. But that's other than that, I just I just port it. I don't make any other changes. Like, you know, of course, there's a chance it's not ported well. It might not work properly, but the intention is it's just a direct port."
},
{
"time": "20:40:09",
"speaker": "Jonathan Jackson",
"text": "Cool. Thank you, Pete. Paul, I'm protesting."
},
{
"time": "20:40:16",
"speaker": "Pau Ballart",
"text": "Yes, thank you. I'm going to share my screen. This is pretty much. a demo that I owe you of the snapshot testing. So, quick reminder, this is already available on iOS, not yet on macOS, because we are waiting for macOS 27. runners on big drives on the CI. on, uh… Yeah, pretty much. It's a package that has a very nice README explaining of it, what I will show today. So you can read it or tell your favorite agent to read it. But it has like requirements, how to use it. A bunch of examples for both iOS and macOS, even though, as I said, macOS. is disabled. But let's do a bit of an example. if I find the Xcode that just crashed, apparently. Ah, it's here, yeah. So, uh, how does it work? We start with the bill. Maybe, or maybe not, you will have previews. That is the new, like, hashtag… preview macro but for a snapshot so I created this one you don't need to use previews but it's just if you use them it becomes handy so there is this new preview provider that's the system. protocol, then if you conform it like this, so pretty much. You configure the different states that you want to have in the view. In this example, it's this segmented control. So there are two previews, one for each tab, let's say. You configure it here. So that's the model or the state of the view. And then you configure it here. So it will render one of the previews for each tab in this case. That basically gives you the previews here, but what is nice about it is that then you have the snapshot test. becomes basically a one liner or yeah one four liner uh but yeah just one call because it reuses the same previews that you refine it and then uh this is just a unit test like. Any other that we have. that runs the test. And this. Basically, you can configure it in different ways, for example. Here, if you want, um… to have a preview, but you don't want to snapshot it, because it's not needed. You have different. uh parameters here in this um. Let me show you. In these configurations, so there is… a scope where you can say, I want just for previews, just for snapshots, or for all of them. And then, um… in the test, you can snapshot in a different set of, um, configurations. So, in these asset snapshots. But everything is here in this package. We have different things. We have the different strategies. If you want to snapshot, for example, iPhones, iPads, all the combinations, just a single screen or a custom. Uh, size? And then you have also. the different sizes of components that you can have in an app, right? Majority of things are the screen, but you can also test some intrinsic content size, bottom sheets, or just any big size that you want. So all of that has, like, default parameters. In this example, for example, it's just, you know, normal screen, and I want to judge a snapshot in that mode, because that screen doesn't have light mode. So, it would work like this. And this is a unit test, it runs super fast, and uh… It passes in less than a second. how it works when you change something so let's say remember we have this previous let's say now i change this uh. this view. No, there is a design change, so we have this title here. If I run the tests, now they will fail. I will show you how it looks like in Xcode. So pretty much, issue recording, blah blah blah, does not match reference. And then, you can go here in your tests. We see the test that failed, and if you double-click, there is this gallery. That basically is showing us the reference, the failure, and the difference. So you can preview it like this. That's the original one. And then the new one that got recorded is this one with hello."
},
{
"time": "20:45:21",
"speaker": "Pau Ballart",
"text": "So you can see a diff that it's generated. Basically, you see everything is moving down. Um… So here it can happen two things. It's a real failure and you need to fix your UI, or it's a design change that is… expected, and you want to re-record the test flight, because this is now the new correct design. To do it, you have different ways. Here, there is a record Boolean. You can pass it to true. But at the same time, instead of changing code. If you go to the folder of the test. In in in Git you can let me show you. in a… in another screen. You can just delete the reference image in the file system. So that's the submodule that we have. In the, um… With all the snapshots. So if you go there and delete the file, it will recreate it on top of it. Um, so yeah, basically you have these two options. If there is no original file in the file system, it will just create it right away. If there is an existing one, it will do the comparison and so on. So the easiest usually is, um, to just remove. the image and re-record it. But let's say that… This works, and you upload a PR, and it fails in the CI. So how does it look like? Pretty much the current PR checks that we have for iOS, we'll report them here with the faillet, and it generates an HTML report, which is this one. that, uh… creates the same thing that we see in Xcode, but in the CI. So if you see a PR failing, you don't need to download the artifacts and so on. You just have to open this, and it has, like, these drop-downs. with the same concept, like the reference, the failure, and the diff. Um, so that's… A bit what I wanted to show. Then, um… So the snapshots live in a submodule, as you probably know. So it's a different repo. It's these DuckDuckGo Apple browser snapshots. And it just contains the PNG files. So that is this. Orchestration, if you want to run when you create snapshots, you need to open, let's say, two PRs. But there is a script that handles everything. So what you would do is here when you record your new snapshots. Maybe I can do it really quick. Just a second. I will. Show you exactly what I mean. So we have the submodule. Snapshot references. I'm gonna remove… The, um… Tests for this one. which is the scan QR code test. So I remove it from the file system. Okay, from this folder. And then when I record it or when I run the test, it will record. So first time it fails, but now it says no reference found on disk, which is fine. And then second time it runs, it already has the references and it passes. Okay, so now we want to open the PR, uh, and we can see that the snapshot reference module has the changes. Again, old and new with a new title. So there is a script in the scripts folder. around doo doo doo scripts. called Open Snapshot Zoom Module PR. You just run this over there, runs it, and it will open the PR, so commit, push, open PR, and so on. Um, and then once in your main branch or main PR, there is a new label that you can tag. Uh, let me show you here. Merge the snapshots. So this will merge the snapshots PR and update the pointer and so on. So, it's these two extra steps. You can do it manually, but, uh, the easiest is once you record it, and you have the changes here in Git, you just run the OpenPR, uh… script, and then once your main PR is approved, you can, uh, just use this label to merge the… the snapshots PR. So you…"
},
{
"time": "20:50:21",
"speaker": "Pau Ballart",
"text": "It's a bit of extra work, but I try to minimize it and automate as much as possible, so… That's how we currently have it set up with these failures and so on. Any questions so far?"
},
{
"time": "20:50:37",
"speaker": "Dominik Kapusta",
"text": "Yes, this is amazing, and do we have a documentation for that in the Apple documentation project?"
},
{
"time": "20:50:44",
"speaker": "Pau Ballart",
"text": "For the CAI part, you mean?"
},
{
"time": "20:50:46",
"speaker": "Dominik Kapusta",
"text": "Yeah, for…"
},
{
"time": "20:50:47",
"speaker": "Pau Ballart",
"text": "Or in general."
},
{
"time": "20:50:48",
"speaker": "Dominik Kapusta",
"text": "In general. You've mentioned that there's a script that simplifies the work, and that would be great to have it as a task in the Apple Documentations project, if it's not there yet."
},
{
"time": "20:51:00",
"speaker": "Pau Ballart",
"text": "Okay, I will add it, yeah. Yeah, so the biggest documentation right now is the README, but I understand that it's not, uh…"
},
{
"time": "20:51:02",
"speaker": "Dominik Kapusta",
"text": "Awesome. Thank you so much."
},
{
"time": "20:51:09",
"speaker": "Pau Ballart",
"text": "in the best place. I mean, it's useful, but…"
},
{
"time": "20:51:10",
"speaker": "Dominik Kapusta",
"text": "Mm-hmm."
},
{
"time": "20:51:12",
"speaker": "Pau Ballart",
"text": "Yeah, I will let it also in Asana."
},
{
"time": "20:51:16",
"speaker": "Dominik Kapusta",
"text": "Thanks so much."
},
{
"time": "20:51:16",
"speaker": "Jonathan Jackson",
"text": "Very cool, thank you, Pao."
},
{
"time": "20:51:20",
"speaker": "Pau Ballart",
"text": "I have one more thing to share, which is… So two things. Why is this useful, right? Like, because, okay, we can add a snapshot test and so on. There are three things that I see that are important. First one is PR reviews. Since now the two PRs are linked, it makes it easier to review changes, right? You read UI code of SwiftUI, for example, and you see paddings, frames, blah, blah, blah. Seeing a screenshot helps a lot, so now it would be easy to compare side by side, because you will have here, um… For example, this one. The… the file changes. Directly in the… well, it's not the… This one needs a rename. And you will have the file changes on GitHub to review side by side like this. So PR reviews are better than. I think it was already mentioned we can. think about our UI tests, and if we have UI tests that are asserting. Just how things look like. It's a good candidate to replace with. with the snapshots. Um, so… I will open a proposal at some point, but the idea is… Since UI tests are flaky and snapshots and units. are less flaky and run quite fast. We might look at opportunities to move some of these tests and with a good combination of unit and snapshots. Yes, we are still missing the navigation part of I tap this button and this other screen opens. But yeah, it's up for discussion, but I think you have already a good coverage of a feature, right? And the last thing is ship reviews, because here in this other repo, it's becoming basically like an S3 bucket of data. PNG files. So when you prepare your ship review, if you have used this, you don't need, uh… to regenerate the snapshots and so on. You would just even link it from here or pick them from here. And that's just a starting point. We can improve it with future ideas, like we were talking about different languages. So how we could snapshot test different languages, different dynamic sizes for accessibility, like a large text size and so on. Even, I don't know, when the snapshots PR is open. with some automation, check the original Figma design, and compare it, and there are, there are, um… ways to improve this. So this is just a starting point. And last thing I want to mention, it was part of the tech design to track adoption of this. So far, I'm the only one contributing, which is why I'm doing this demo as well. But I created with Claude an automation that every week checks the repo. It's very easy, because we can just go to the insides of this, um… of this repo and see contributors, but also just check, uh, the asset and snapshot, uh, usages. So this is a dashboard that I shared, uh, within DuckDuckGo. It's updated every week, and basically we can see how. how it grows over time. Um… So yeah, if you fancy, please use it. And if there are any issues, let me know. I'm like the unofficial or official DRI of this. Happy to be on top of it if it's causing issues as well."
},
{
"time": "20:54:59",
"speaker": "Jonathan Jackson",
"text": "It's really cool, Pat. Thank you for sharing. Yes."
},
{
"time": "20:54:59",
"speaker": "DR",
"text": "Good work, pal."
},
{
"time": "20:55:04",
"speaker": "Jonathan Jackson",
"text": "Very cool. We are now at 5 minutes to the top of the hour. Dominic and Alex, you both have postmortems on the list. Do you want to… run those now, understanding we'll go past time, and anybody who can stay is welcome to stay or not? Or would you rather find another time for those?"
},
{
"time": "20:55:24",
"speaker": "Dominik Kapusta",
"text": "I'm fine running it. It should also be short, but not sure about Alexa's one."
},
{
"time": "20:55:33",
"speaker": "Alex Martemyanov",
"text": "Probably can wait till the next Apple Weekly."
},
{
"time": "20:55:37",
"speaker": "Jonathan Jackson",
"text": "Okay."
},
{
"time": "20:55:37",
"speaker": "Alex Martemyanov",
"text": "I think it was waiting for a year and it didn't wait another week."
},
{
"time": "20:55:41",
"speaker": "Jonathan Jackson",
"text": "All right."
},
{
"time": "20:55:42",
"speaker": "Alex Martemyanov",
"text": "Thank you."
},
{
"time": "20:55:43",
"speaker": "Jonathan Jackson",
"text": "Thank you, Alex. Um, then, Dominic, why don't you go ahead and get started? Anybody who's not interested in Dominic's incident post-mortem, obviously, is welcome to drop. If we run a little bit late and you need to be somewhere else, that's also okay to drop. And Alex, I'll keep yours on the agenda for next week. Thank you."
},
{
"time": "20:56:01",
"speaker": "Dominik Kapusta",
"text": "Thanks. I've dropped the link in the agenda as well for the incident postmortem. What happened last Monday is we released the app that was crashing on macOS 12. And, uh, the app was out… well, uh, so the app was out for, like. 3 hours before we, uh, realized that there is a crashing scenario on macOS 12, and then that was handled real quick, uh, with app store rollout stopped. And, uh, Sparkle rollout stopped, uh, as well at some point, um, and the fix was released, actually… well, it… It. Well, almost immediately on DMG, and the next day on App Store, because of the review time. Um, but, uh, how it happened? So, it happened, uh, because we had a change to, um, the save credentials pop-up, which shows up every time you're offered to… you're being offered to save a password. Um… On macOS 12, um… And that change was due to dropping a storyboard, replacing a storyboard with a code-initialized view. So what didn't go as planned? This, uh, change was not tested on old OS versions before merging, and it was strictly macOS 12 issue. Uh, like I mentioned before in this call, we had that engineering expectation in place, but we're not really enforcing it for every change. There's no way of enforcing it, uh, and there's no way of. testing, um… all those versions in CI, so… that's why it happened. Really. Uh, the other thing is, uh, we didn't know about the crash, because, uh, I overlooked it in Sentry. I was the release DRA and I overlooked it in Sentry. There was a single crash on macOS 12 there. Uh, that I treated as noise, and I went ahead and released the app. The sentry summaries weren't generated on that day, because we had another… Whoopsie. Um, the week before, when we updated, uh. Well, some updated the model version and I reviewed it and approved it. and we merged that change, and we updated the model version, but we didn't update the SDK version, and the old SDK didn't… wasn't recognizing the new model, and it failed to… collaborate, so we didn't generate summaries. Um… So that's the other… the other thing. Uh, when the… but! When the summary was generated, uh, it clearly pointed out that there is a crashing scenario on Mac OS 12, which started the incident. A week of internal testing didn't catch a relatively easy-to-reproduce crash. It was a 100% crashing scenario, which wasn't caught. Because we don't have testers on macOS 12. Well, apparently we have one, because we got this one crash at some point. I don't know who it is. I'm…"
},
{
"time": "20:59:33",
"speaker": "Alex Martemyanov",
"text": "Yeah, and by the way, there was another kind of related issue about the crash on Intel machines. It's not directly related, but yeah, it was close."
},
{
"time": "20:59:41",
"speaker": "Dominik Kapusta",
"text": "Yes, another one, exactly. We also don't have testers, or many testers, on x86. architecture. The App Store review took 15 hours, which is rather long for an expedited review, but also there's nothing we can do about it. At least it got in the queue… I mean, it got in the review pretty quickly after requesting a completed review. What went well is that the sentry summary that was eventually generated, um… Clearly identified the crash, and suggested addressing it, and the fix was simple, quick to prepare and test, it was just assigning an initial frame to a view. And the hotfix release automation workflow less at this time. It's always important to point this out, because… We only talk about CI when it's not working correctly. Despite the long review time, we only had 37 crashes in total and only 9 affected users. That's all. for action items and DRIs, we actually, uh… there was an action item to update agent's instruction prefect… essentially update prefect to ensure that Claude agent SDK version is… compatible with used models. Uh, Sam has handled it, and, uh, well, there is a code command right now to, to update the SDK version whenever you update the model version. Um… The other topic that's not actually mentioned here is what to do about testing on older OS versions, but this is something we will be handling separately through Alex's work, mentioned earlier on the call. And… That's it. Finally, I created an incident task through the form. Asana forum, and marked the incident as high, because it's a crashing scenario, we need a hotfix, and an SRE person joined the call, and we talked a little bit, and he, um… Explain to me that if it's a one-person rollout. It's not a high severity incident, and we dropped it to medium, and they dropped the call. And that's it. And, um… That's something to keep in mind for later, for next incidents, when they are only starting rolling out, we may not need SRA help there. This is all I have."
},
{
"time": "21:02:09",
"speaker": "SS",
"text": "Regarding the action item, are you happy enough with just having the code comment now that reminds about the Claude SDK?"
},
{
"time": "21:02:15",
"speaker": "Dominik Kapusta",
"text": "I think so."
},
{
"time": "21:02:16",
"speaker": "SS",
"text": "you know, it's… it's not bulletproof, like, what I… what I wanted to do was to just ask the Claude SDK, what models do you support, and check that it's in the list, but it only includes… yeah, it doesn't include all the actual supported models."
},
{
"time": "21:02:18",
"speaker": "Dominik Kapusta",
"text": "I think, yeah. I saw that, yeah."
},
{
"time": "21:02:28",
"speaker": "SS",
"text": "Eh, maybe the comment's okay for now. I tried to make it very obvious what to do and how to confirm this."
},
{
"time": "21:02:32",
"speaker": "Dominik Kapusta",
"text": "Yeah, I mean, that's okay. Also, that comment would show up, because it's just very close to the line that is changing, it will show up in the GitHub UI when reviewing the code, so it should be fine."
},
{
"time": "21:02:37",
"speaker": "SS",
"text": "It's right there. Yeah, the only way I was considering extending this was to just have a GitHub Actions check that looks for model changes and adds a comment, GitHub Actions comments. But I would want to do this for all of Prefect. Whatever. I'll look at that."
},
{
"time": "21:02:56",
"speaker": "Dominik Kapusta",
"text": "Yeah, yeah. Should be fine. Okay."
},
{
"time": "21:02:58",
"speaker": "SS",
"text": "Okay."
},
{
"time": "21:03:00",
"speaker": "Dominik Kapusta",
"text": "Thank you. Thanks for handling that, Sam. Alex?"
},
{
"time": "21:03:05",
"speaker": "Alex Martemyanov",
"text": "Yeah, I got a proposal in… I got it related to post-mortem of the VS Code, but I think it more suits here. What about adding… updating our process to require adding UI tests in addition to renting some older Mac to run older OSs, but make a requirement to the process to cover any UI change. with a UI test. Even if it's a fix or a quick addition in the uncovered region, especially having all the Agentic workflows, it may be a quick and cheap option. I mean, cheap to add. maybe not to maintain. But it adds, of course, it adds extra cost for the runners. Or maybe we could have like a test suite number two that runs weekly, for example, and not daily."
},
{
"time": "21:04:11",
"speaker": "Dominik Kapusta",
"text": "I actually think it's… Some Windows team uses something similar. whenever they change UI, they add UI tests, and they have plenty of UI tests, and that's another problem. I believe, but… Yeah, we could… We could discuss it, I guess."
},
{
"time": "21:04:31",
"speaker": "Alex Martemyanov",
"text": "Yeah, because, uh…"
},
{
"time": "21:04:31",
"speaker": "Jonathan Jackson",
"text": "I think that's what we're considering. Sorry, go ahead."
},
{
"time": "21:04:35",
"speaker": "Alex Martemyanov",
"text": "Because obvious, like, obvious… thing that could fix it is, uh, like, QA, which we are missing, for… everybody knows for… for why, for what reasons, uh, but we have a lot of, uh, supported platforms, a lot of supported macOS versions, and, uh, it's, uh… Like, uh, it's impossible to… make the requirement as in the mentioned. Uh, process, like, to test all the supported macOS versions, because not everybody even have all these machines that, like, I have the older one, but it's not DuckDuckGo, it's my personal machine. And, uh, I can test it, but it takes time. Uh, and nobody… nobody does it, frankly. And we have no QA, and it's impossible to guarantee the quality in such conditions. So, maybe it's required. It should be a required condition to… to… raise the UI test coverage, the end-to-end coverage, so we can validate we are actually producing quality UI tests. Stuff."
},
{
"time": "21:05:50",
"speaker": "Jonathan Jackson",
"text": "Yeah, I think that's worth considering alongside the virtual machine testing stuff that you were talking about earlier, right? I mean, we've known for a long time that we clearly have testing gaps, especially on older versions and older hardware. And… To this point, I think we've just accepted that as the way it is and every now and then something like this goes wrong and we deal with it. um… But we should definitely think about whether there's a promise we're making to our users there that we're not able to fulfill properly. And I think certainly that's true right now. The question is, what does it take to do better at that promise? So I'd love to see some proposals around moving some of these pieces forward."
},
{
"time": "21:06:32",
"speaker": "Dominik Kapusta",
"text": "All right, that was all for me. Thank you very much."
},
{
"time": "21:06:38",
"speaker": "Jonathan Jackson",
"text": "Alright, and thank you. Um, so, Alex, we're gonna wait till next week for your other postmortem. Thank you for your flexibility there. And thank you all who stayed to finish that out. I appreciate it. And I look forward to seeing you again soon. Bye, everyone."
},
{
"time": "21:06:54",
"speaker": "Alex Martemyanov",
"text": "Thank you. Bye."
}
]
}
@@ -15,137 +15,3 @@ source: "https://us01mynotes.zoom.us/gBBa-iiUQLycw55WRV1tnw"
- **20:03:14 · Jonathan Jackson:** Hello, everyone. Let me go ahead and get started. Quick runs through our scheduled rotations as usual. This week, iOS triage is L, followed by Bartek, and then Brindy. Mac OS triage on is on this week by Jorge and then Rachel. Uh, for iOS release, Sam, you're on duty this week, followed by Bartosh, and then Mihao. And for macOS release, Dominic was last week, hasn't closed that task yet. Tom, you're on this week, followed by Juan, and then Joseph. You all may have also seen, I published our… Uh, release schedule changes around the winter holidays, uh, last week. Um, next step there is for me to look at out-of-office stuff and start trying to coordinate and… uh, coordinate swaps and coverage during that time when a lot of us are gonna be out, so keep an eye out for that soon, I'll get that. Um… I'm also using the Zoom transcript feature on top of Zoom summaries, and I'm gonna feed the transcript to Claude and see if we get a better summary that way than we have been out of Zoom's summarization AI. Uh, so… And I'll share maybe both, or I'll see what it comes up with, and I'll share an update after this meeting about what we ended up with there. Um, and one final reminder, next week, uh, is performance review week. The process starts with self-reviews happening on Monday. And then there's a few days of CAs writing reviews, and then a few more days of calibration after that. um… But because there's really only one day in that official schedule dedicated to self-eval writing, I suggest y'all think about starting this week. If you're anything like me, I usually need to write it, and then think about it, and then come back and edit it heavily, and then think about it, and then write it again. So I would suggest giving yourself the extra time if you need to do that. to get started early. Tom, what's up?
- **20:05:23 · Tom Strba:** Just a small note, I checked the macOS release rotations. Yes, there is not finished one rotation that's Dominic's, but this week is Diego. Right? Is that true?
- **20:05:36 · Jonathan Jackson:** Mm, got it.
- **20:05:37 · Tom Strba:** And I think I'm next week. Because I almost got a heart attack when you said that I am…
- **20:05:40 · Dominik Kapusta:** Yes, this week is Diego. And sorry for not closing my task.
- **20:05:41 · Jonathan Jackson:** Okay.
- **20:05:45 · Tom Strba:** that I am this week.
- **20:05:45 · Jonathan Jackson:** This week… Why is Diego… I don't see a task… this is a macOS release we're talking about, right?
- **20:05:52 · Tom Strba:** Yeah, I think Diego maybe marked it as complete in the beginning of the week, because there's just, like, triage…
- **20:05:57 · Jonathan Jackson:** Yes, you're right, Tom, your block is the 26th to the 30th, because that task is missing, I didn't see it, I wasn't looking at the dates, I was just reading the list.
- **20:06:04 · Tom Strba:** That's okay. Just wanted to be sure.
- **20:06:07 · Jonathan Jackson:** Okay. Diego is responsible for the release this week. It sounds like he's actually doing that. Is that right?
- **20:06:08 · Tom Strba:** Perfect.
- **20:06:14 · Jonathan Jackson:** He knows. Okay, cool. Thank you.
- **20:06:14 · Dominik Kapusta:** That's right.
- **20:06:18 · Jonathan Jackson:** Um, no problem. Okay. Anyway, think about starting your self reviews this week. If you feel like you're gonna need more than a day to knock it out. Bartek, over to you.
- **20:06:31 · Bartek Waresiak:** Yep, I will be stepping down as IS app DRI. Jacek will take the primary role, and Brindy will take on secondary role. So, yeah, if there is IS drama, if there are IS issues, if there are any urgent things. Go to them! And thank you very much.
- **20:06:57 · Jonathan Jackson:** All right. Thank you. An, you're next on the agenda.
- **20:07:08 · Anh Do:** Oh, that was quick. Yeah, so in OK, there have been a few projects that involve native changes required as part of the front-end-led projects. Um, so the background is that they, uh, want to contribute some PR, and, uh, um… AI assisted Pi, of course, and then what have been working for us lately is like depends on the size of the task like I would be the one to like either. Dri the change that they are they want to make, or like they prepare the Pi, and I do a thorough review of that. So and now we want to kind of do this more regularly. And so there was a need for some kind of like guidelines that we can give to contributor from outside the apple team. So I was just starting like a small task to basically collect ideas from people. And if you have anything that we already have somewhere, maybe I could get put in. And so. it becomes something that we can point other people to when they want to contribute to the Apple codebase to ensure our standard and make sure that, like, everything is being done the way that we want. So that's about it. Nice.
- **20:08:19 · Jonathan Jackson:** Cool, thank you. I just took a quick peek. I see you do mention the engineering expectations. I think that's a good source. We might also want to link… to the onboarding process. Not that they would need to follow all of it, but some of… that's basically our best source of, like, how to get set up with the codebase. So there's probably a little work to do to figure out how to have a slimmed down version of that that folks could follow. And I'm sure other people have other ideas as well. So thank you. Um… Luke, we have a non-Apple person lurking in our midst. Welcome. What can we do for you?
- **20:08:54 · Luke Andrew:** Hello. Yes, thanks for having me. Luke from SRE, for people that I haven't met before. Um, this is just a plea for generic Apple help. I don't want to, sort of, get all of your attention to focus on this task. We basically have… a looping client that seems to be sending, uh, requests once a second to us, uh, that is Apple, but not DuckDuckGo Apple, based on the user agent, and doesn't seem to be Safari either. Um… And it's cumulatively across lots of different devices, lots of different queries, sending in the region of 3 million searches a day. Which is substantial, not sort of catastrophic, but substantial enough searches that it's something that we want to deal with. Umm. And I don't really know where to go next to try and understand where it might be coming from or how we might try and reproduce it. So I don't want to solve that in this call, but I just wanted to bring your attention to the task. And if there's anyone who thinks they might be able to help, I'd really appreciate. a second pair of eyes, and pointed out that it's not even worth, with what we have at the moment, that we can, like, escalate this to Apple, because we just don't have enough, uh, information to get any help from them. So yeah, that's it. If anyone has any questions immediately or async, just pop them on the task. Yeah, that's all I have.
- **20:10:18 · BA:** Quick one, Luke.
- **20:10:18 · Jonathan Jackson:** This is not from a single client, but from a particular app version, potentially, is that right?
- **20:10:24 · Luke Andrew:** Yeah. Yeah.
- **20:10:24 · Jonathan Jackson:** Okay. You know, be scared that it was one client going crazy. Okay, um…
- **20:10:30 · BA:** Yeah, I was going to ask, what's the — we eliminated bots from the equation. Are we happy that it's not bots?
- **20:10:36 · Luke Andrew:** It doesn't look like bots. The queries all look human. The rate is really low compared with bots. The moment that I put in a block for it and it immediately stopped, like redirected away.
- **20:10:39 · BA:** Okay. Right.
- **20:10:52 · Luke Andrew:** It got, like, a 302 from deep, and then just immediately stopped, so that doesn't feel like… bossy behavior either. They normally persist a little bit and then give up. Whereas this was just immediately, it broke out of whatever loop it was in and stopped.
- **20:11:09 · Jonathan Jackson:** Interesting.
- **20:11:10 · Luke Andrew:** Uh, so don't all take a look, because that would be a waste of time, but if you think you can help, um, I'd appreciate a pair of eyes. I'm gonna drop off. Thank you all for having me.
- **20:11:19 · Jonathan Jackson:** Yeah, one last quick question. It sounds like you're treating this as something that definitely needs attention, but not an incident at this point. Is that correct?
- **20:11:25 · Luke Andrew:** Yeah, that's correct. It's been going on for… Based on… um, how we categorize queries for, um, like, ads perspectives. These get classified as a separate category based on user agents, so we don't send them to Bing and say, these are definitely good queries. Um, it's been happening for about a month. So it's, at the moment, not urgent. I'm gonna raise it with SRE, maybe, and see if we think it should be an incident that we just let run, but at the moment, that's not how we'.
- **20:11:55 · Jonathan Jackson:** Okay. Great. Thank you for the clarity there. Uh, and yeah, if anybody thinks they can help Luke out and figure out what's going on there, feel free to hop into the task. Thanks for coming. Moving on. Alex, you're first in the regular topics list.
- **20:12:16 · Alex Martemyanov:** Yeah, hey. I have several topics for today, including the VS Code integration postmortem to run later. And the first one goes with a proposal. The proposal is pretty short. And kind of related to the, uh, recent incident with Mac OS 12 crash. that we are not. Testing for macOS 12 and 13, I guess, because we are missing the infrastructure on CI runners. And the suggestion is pretty simple to extract the macOS UI tests target from the main macOS Xcode project, leaving it as a separate macOS project inside the. uh, Xcode workspace. So it will be available the same way it is now, and, uh, runnable. So only, uh, the only issue I can see for those who use, uh, the actual macOS Xcode project instead of the workspace. they would have to switch to another project to run the tests. So, I just wanted to hear if there is any concerns or objectives against it.
- **20:13:39 · Dominik Kapusta:** I think some time ago, we… someone asked… who uses or doesn't use Workspace, and people who didn't use Workspace were in a… In a minority, anyway, like, very few of them, so… I guess… I could move to the workspace.
- **20:14:06 · Jonathan Jackson:** I think it'd be good to ask that question in that proposal, at least more explicitly, and just give people a chance to chime in if they feel like that would be a hurdle. Um… Other question for me is, is there… should we think about the iOS side of this as well, and to match… structure, or is this really a macOS only question?
- **20:14:26 · Alex Martemyanov:** Okay. Maybe, I… Didn't think about it, actually. And the main concerns here is the compatibility. So we can reach macOS 12 compatibility, at least for some local runners that I'm going to present further. And the build times, so we have package fetching and building for every macOS runner that runs the UI tests and any of the dependencies. None of the dependencies are used during the runs, so it's a 10-second step for each runner that can be easily omitted, and so, yeah. And yeah, it's not related to the main browser targets, so there's no risks. Uh, and they're both, uh, U.S. Probably to think about it in the ER.
- **20:15:25 · Dominik Kapusta:** I think iOS is not…
- **20:15:25 · Jonathan Jackson:** I mean, I don't have a strong… sorry, I don't have a strong feeling there, I just felt like if we're gonna make this change, like, if it's gonna end up with different structures depending on the app, we should think about whether we really want that to be the case, or if we should do the other.
- **20:15:37 · Alex Martemyanov:** No, it actually shouldn't change any structure, any file structure, just the project placement.
- **20:15:38 · Jonathan Jackson:** Screwed up. Yeah, yeah, yeah. Dominic, I interrupted you. I'm sorry.
- **20:15:44 · Dominik Kapusta:** Ah, no worries, I just wanted to say that iOS is not affected by this at all, because… iOS doesn't need testing on various macOS versions.
- **20:15:51 · Jonathan Jackson:** Alright. So the limita… this is about dealing with a limitation that comes from Mac OS 12 build, particularly.
- **20:15:59 · Dominik Kapusta:** Yes.
- **20:16:01 · Alex Martemyanov:** And bill times.
- **20:16:01 · Dominik Kapusta:** I'm Bill Times.
- **20:16:02 · Jonathan Jackson:** Got it. Okay. thanks for pointing it out. Uh, like I said, I think you might want to give people a little bit more time to respond to async if they have… particularly if they feel like the… Workspace thing is gonna be a hurdle, but my guess is it's not gonna be a big issue. Uh…
- **20:16:22 · Alex Martemyanov:** Okay.
- **20:16:24 · Jonathan Jackson:** Next topic.
- **20:16:24 · Alex Martemyanov:** We can…
- **20:16:26 · Jonathan Jackson:** From you, also.
- **20:16:26 · Alex Martemyanov:** Perfect. To the next topic then. Yeah, so, uh, this is another iteration of, uh, the Verfield project. I've been live coding for a while already. Uh, so this is the current state of things. It's changed a little bit, some of you may remember the first, uh, first demo. Uh, so the change is it's, uh, migrated to Go language, and, uh, now it runs on TART system that's used on, uh… We tried runners, I guess. And so the system is here to show you the available images, available runners and locations. So here you see I can have it. stored on the external SSD, because I have my internal 2TB ETH. up to completely, and I have the old MacBook Pro also managed from the same environment. And, uh, you can add other machines as well. Uh, so this is, uh, a wrapper around the TART system that manages, uh, Xcode installs, uh, SIP protection, and, uh, for virtual machine and real machines. Uh, if you use older hardware and, uh. It's, uh… basically providing MCP server for AI clients to. to run these UI tests. Mostly. on the older virtual machines. It can be not older virtual machines, but actual virtual machines. New refreshable machines as well, sir. Uh, for example, I don't update to macOS 27, because, uh… I expect some issues, but I use, uh, testing on macOS 27 using this, uh… a virtual machine system. And so basically the… Again, I have a question to the team in… In the light of a recent discussion of testing on order. macOS versions, for example, whether should I try to push it forward to, like, team-wide? So the idea… the idea is to be able, uh… again, we'll… And in the post-mortem. for the VS Code integration projects. So here you can see VS Code. Basically, it's running the Google browser. It can… run iOS browser as well, in simulator, and in addition, it can also run remote debugging, unlike Xcode, which had supported remote debugging. in a long time ago, but currently lacks the ability, so… Integrating these systems together allows, like, click one button. choose the virtual machine you want to run to test on, and it builds, deploys, and debugs in real time without any lags for library symbols transfer and other stuff. So it just works like you would do on your host machine, but in the virtual machine. So I wanted to hear opinions whether should be. try to adopt this team wide.
- **20:20:06 · Dominik Kapusta:** I can offer an opinion.
- **20:20:09 · Alex Martemyanov:** Nobody wants to.
- **20:20:09 · Dominik Kapusta:** uh… No, well, I mean… No one to be the only one commenting, but anyway. This will be the topic of, uh, of, uh, of the upcoming postmortem, uh, as well, that… The Apple engineering expectation of testing on older macOS version is essentially a dead low. We are supposed to test on older macOS versions, but we rarely do it. Perhaps for new features on macOS? I'm not sure. But certainly not for… Small… tasks. I don't think… well, I don't know, but I don't think we bother to test on all the ROS versions, every small version. Change to the UI, especially. And, uh… Because of that, if we had a way, and also we can't, we are unable to test in CI. So, if… I had a way to… Ask an agent to… run UI tests on a virtual machine. on an arbitrary OS version, that would be great. I would like to see the demo of that, actually. That would be awesome. And that is why we might be interested in adopting it. Perhaps.
- **20:21:41 · Alex Martemyanov:** Yeah, again, about the UI tests, correct point. So sometimes you want to run an agent reproducing an issue, for example, and it's not always convenient to upload it to CI, wait for the UI tests to be run. Look for the results, while if you run it locally on your machine, it will be blocked for 5 minutes, and do the stuff while you take a coffee. So this thing allows you to just run directly from the agent on the same machine in background and provide you screen recording with all this and the results.
- **20:22:22 · Jonathan Jackson:** Yeah, I mean, I think… You know, your point that our expectations are that we'd be testing on all versions that we support, but in practicality, I think almost nobody actually does that. And particularly with something like as old as Mac OS 12 where we don't have the hardware, we don't have like, most people don't have access to test it to your point, L. Um… I think I'd like to understand a little bit more about how the system would work, what kind of third-party dependencies there are, what it would look like to really set up and what it would cost. I think the idea of we would be able to test. On versions that we say we actually support is pretty appealing.
- **20:23:00 · Alex Martemyanov:** Okay, so probably the resolution here would be, um… So, first of all, I do use it as my self-made tooling, and uh… if… I can reach it to the point, I can make it to the point when you click a button, install the system, click a button, and it just runs. I think it would be worth. adopting at least as a selected auditory who can. have, uh, the means to testing, like, enough of RAM or some older hardware, uh, like, choose the early adopters and, uh, see how would we… expand it. And, uh, yeah, correct question by, uh, Federico about, uh, older ores. It's another topic that I wanted to raise during the post-mortem. During the incident, actually. Both for the incident, uh, that, uh, having… Maybe one dedicated machine, older machine, maybe somewhere that would run the UI test suite at least once per week for each release would be a great addition, even if it's like a physical machine somewhere. someone's office or home space.
- **20:24:28 · Jonathan Jackson:** Yeah, that's an interesting idea, too. I think… I guess I think that a proposal here that sort of lays out what a strategy for old testing would be that used this would be maybe a useful next step. Um, because then that would be a place that people could rally around, sort of solving that higher order problem of how do we actually make good on our promise of testing on the systems that we support. And it sounds like this would be one, but maybe not the only tool to consider, or maybe even as a combination. Does that make sense?
- **20:25:00 · Alex Martemyanov:** Yep.
- **20:25:01 · Jonathan Jackson:** Cool. Okay, thank you. Interesting stuff. Sam, you're up next.
- **20:25:10 · SS:** Yeah, recently I have been chatting with some folks about being able to put Claude workflows in our CI. I talked about this with OT and they told us that they don't want Anthropic tokens being available in public repos. I've created a private repo to host the agents, uh, which is… Pretty bare bones right now. It lives here in the Apple Team Agents repo, it has CI set up, it has the Claude, uh, action set up. I have a workflow first for testing it, uh, just so we can make sure you can actually talk to Claude and back. Um, the only thing I'm waiting for is whether or not we should get a dedicated API key, because I've been told. Two different things from OT. So I'm just waiting to —. Get that sorted out. I think we should get a dedicated one. once we've done that, yeah, we can start doing things like an automation to clean up feature flags and such, like Fernando's, uh, proposed. So, uh, I'll post to Apple Diary once that's ready, but I think you'd be… if you do want to start building automations in this now, like, feel free, uh. As long as it's, you know, not super expensive. Pete, done.
- **20:26:19 · Pete Smith:** Yeah, thanks, Sam. This, this looks really cool. Just because I've seen, um, like, there's a few different conversations. There's a conversation with this, and there's the Bitrise, you know, running, um. uh… Agentic stuff on Bitrise as well. How does it all fit together? Like, I think I understand it, but, like, say I wanna… say we wanted to, you know, uh, build our feature overnight while we're in bed, um… How could we use this to do that? Or can we?
- **20:26:43 · SS:** This is not that. This is definitely not that. This is not like the development environment thing. Yeah, these are not like the development machines. I really just expect these to be like GitHub Actions workflows that just do helpful things with Claude. Uh, and we just need a place to put those. Like, if it weren't for the API key limitation, this would live in the monorepo.
- **20:26:56 · Pete Smith:** Yep. Yeah, yeah, I guess, I guess what I'm wondering is, so, like, yeah, exactly, we can, we can hit Claude and, um, but, you know, Claude can't, well, build for us, so, like, well, build and check that it's actually working, so where would… say, say even, like, removing feature flag, where would that. On the PR, at the PR station.
- **20:27:17 · SS:** Yeah, this is something that Fernando and I was talking about, about doing some kind of coordination between these repos where the monorepo would talk back and forth, do the things that it needs to. This can create a branch. The monorepo can then do the actual testing. Yeah. Right now, I'm just using these for, like, dependability analysis kind of problems, or planning on anyway, which I have a demo for coming up soon.
- **20:27:33 · Pete Smith:** Okay. Yep. Cool. Yeah, cool. Thanks.
- **20:27:44 · SS:** Dominic.
- **20:27:46 · Dominik Kapusta:** Mm-hmm, uh… one of the limitations here is that GitHub Actions workflows are limited to 6 hours of runtime. So…
- **20:27:53 · SS:** Also that, yeah.
- **20:27:54 · Dominik Kapusta:** Yeah. And also, it's, of course, non-interactive. Um… Which is why we're currently trying to figure out if Bitrise… or Bitrise or not, but anyway, looking for some infrastructure provider for, uh… macOS machines that could run Agentic workflows and be… and offer. interaction with them, right? So, uh… Bitrise RDE remote. development environments is one of the options there. Um… That is in progress. For now. They also… it's also quite a fresh feature on their end, and they have some bugs there that we're trying to resolve right now. And we have a CloudOps team member on that as well. the side of… Connecting them to ClickHouse or Sentry. Yeah, so… We'll see in some time.
- **20:28:58 · SS:** Yeah, yeah, to Dominic's point, like, that problem is much bigger than what this repo is. This really is just, I want to be able to run Claude on an automation, like I currently do on my own machine, and I'm just sick of doing it on my machine. I just want to push that up to GitHub Actions. Have it run on its own, and… Show up with PRs and Asana tasks occasionally, so. Okay.
- **20:29:19 · Jonathan Jackson:** So the limitations here are that it can… It can inspect code, it can run as an agent, but it can't build and run, so it would… prospectively submit a pull request, and then CIA would tell you whether it did the thing or not.
- **20:29:32 · SS:** Yeah, the idea that I'm thinking here is that, yeah, like PRs would go over back to the monorepo. This thing would open PRs against the monorepo. And then CI would do its thing over there. Yeah.
- **20:29:38 · Jonathan Jackson:** Right. Yeah, and if we needed to inspect it from there, we could pull a branch and do whatever else we needed.
- **20:29:46 · SS:** Yeah.
- **20:29:47 · Jonathan Jackson:** Okay, cool. Definitely sounds like a good step, even if you're not trying to solve everything all at once, which is reasonable. You're the next topic as well, Sam.
- **20:30:00 · SS:** Oh, is this the demo? Probably should have just done this all at once. Yeah. So one of the things that I.
- **20:30:04 · Jonathan Jackson:** Oh, before you… sorry, if you're doing demos, before we get into demos real quick… Uh, we had a note here that we were gonna actually record demos. Um, but we haven't ever done that. Mostly people have opted out of wanting to be recorded, so I wanted to just check in since we have 3 demos here. do we want to record these? Should we rely on the… just the transcript summaries at this point, and whatever tasks people have written? I'm kind of okay either way. Um… I don't know. I don't know that we've ever recorded a demo.
- **20:30:35 · Pete Smith:** Alessandro. Alessandro is waiting for his Wednesday morning. Won't be the same if we don't record our demo.
- **20:30:39 · Jonathan Jackson:** Right. That's the question, right? I know, yeah, it's like this is sort of a hard way to do this. So, Sam, would you like me to record or not?
- **20:30:51 · SS:** I mean, I've already shown this to Alessandro, so I don't think he cares. Yeah. Up to you. I'm good either way. I remember. Don't worry. This is a super quick one anyway, just to show the initial problem that I'm trying to solve with… with a repo like this. Let me share my screen. Um, so I have, for a while, wanted the other half of the flaky tests project. Right now, we have a flaky test project, which keeps track of, uh, you know, tests that are failing. Um… I have traditionally been more interested in the problem of what are the workflows that are failing, uh, and why, because these things were just, like… this stuff comes up a lot, like, during Xcode upgrades in particular, so… This is something that is being used by Claude to pull the monorepo, get the actions, go and look at the code, figure out what's causing a problem, and report back and give a little write-up about what's going on. Um, the idea being that eventually you could then move something into this ready-to-fix section, and the agent would then go and actually open the PR later. Um, you know, this is just moving a… moving an automation that I've had on my machine is like a daily, like, 10 AM workflow for a while. and just putting it remotely so I don't have to think about it anymore. Which is the ultimate goal. So yeah, this is the kind of thing that I'm trying to do with this repo. Um… As an aside, OT is kind of working on… something along this as well, which I learned about as I was setting up this repo. They are setting up this template, which lives on Dub, for what it's worth, for these kind of analyzing report workflows. Umm. So that might be interesting if you are needing like access from things within the system already. Uh, like, I think Lucas is currently looking at getting that thing to have sentry access and all this kind of stuff, so… Yeah. Go check that project out if you're interested. That's it.
- **20:32:48 · Jonathan Jackson:** Awesome. Thank you. Pete, you're next.
- **20:32:57 · Pete Smith:** Yeah, thanks. Yeah, this is in the demo section. It's not really a demo, I guess, but just wanted to share. I'll speak a little bit about, um. ASTAC, so I put a link in… a link into the chat there, so I'm sure people have heard… of… PSTAC, or maybe people have heard of PSTAC. I'm going to just share my screen. So if you haven't, um… Pstack is a plugin created by an engineer at Cursor or SpaceX. It's basically just a set of skills that this engineer found were very good. at, um, fixing bugs, implementing features. So they created the PSTACK plugin. What ASTACK is, is basically just a port of PSTACK. So PSTACK was. built for cursor. So it has a lot of built in you know, instructions in terms of cursor models and how they work so forth. So I just. Ported PSTAC, uh, over… To, uh, ASTAC, um… Basically replacing any of the cursor references with Cloud Code and Codex references. So what AStack is, is a plugin that you can use in Codex or Cloud Code. It's like it sounds very abstract. It's not. It's really just a. A set of skills, a set of playbooks, some defined principles. And they all work together to what I found to just to produce good output. um… So I'll just, I'll talk a little bit in a moment about how ASTAG works. So how it's set up at the moment, you can see on the left, I just have it there under my public, under my own public repo. But if anybody wants to try it out, I would encourage it. You can see like I didn't do a lot of work here. I really want to undersell this. asked an agent to port this over. So take PStack, port it, make sure it works with Cloud Code and Codex. The most work I did was creating that logo you see on the left of the screen, so that's where all my creativity went into. Um… But yeah, you can go here, you can grab the plugin, you can install it in Cloud Code. And you can try it out. I'd recommend trying it out for… for bug fixes, even like small features that are well defined. So, you know, the evidence, like any evidence I have is just anecdotal. I've just found these particular set of skills, these set of playbooks and the principles that are defined just produce very good output. Again, anecdotal. I haven't measured this. I also think it seems to do it at lower token usage. But again, I haven't measured it. So how it works, how ASTAC or PSTAC work is, you know, you install the plugin, it sets up a hook, so at the start of your sessions, the agents are aware that ASTAC is there. And if you say, hey, build this feature or fix this bug or whatever, you can explicitly say. Enter potato mode. But that's actually part of the hook. The agent will know, oh, if you give it a feature or a bug, it will enter potato mode. All that is like a top level skill, which is basically a router. And depending on the task that you give it, like fix this bug or implement this feature. You will go and find the right playbook and follow that playbook and in the playbook. That would reference what skills to use, et cetera. So. again, you know, there's nothing, like, there's nothing magical here. I mean, there's been other plugins that have been very popular. I was talking to Fernando earlier, and we talked about… was it the Superpowers one? I think was another popular plugin. So things like this will probably be, as I was speaking to Fernando about, they'll probably be, can, you know, eventually end up in the harness. Probably won't need plugins like this at some point. But at the moment, this is something I'm using daily. And I find it very beneficial. It just results in really good output. So I would encourage people to try it out. Like, what what, you know, we've seen probably saw the post from Sebastian, from OM. He's creating, like, auto, which is their version of pstack. He just took pstack. And ported that and kind of made it very specific to Duck AI. That's like the the OM version of Pete's group. So if ASTAC, if people find it useful, we could basically turn that into like the Apple version of PSTAC, Apple team version of PSTAC. and… that's something we could do. So yeah, I would just encourage people to try it out, if you're interested. There's an Asana task there that I posted, and you can give any feedback, and if people want to. People find it useful and want to contribute and make it better. We can do that. It's under AI enablement AOR. I spoke for a long time, if anybody has. Sorry, I shared that artifact. Sorry, key. I didn't go through all this artifact.
- **20:37:59 · Pete Smith:** It's linked in… The Apple Weekly Task, so you can go and look at that artifact, it explains at a very high level how it works. Again, it's not magic, it's just a skill, a ruler, lots of other skills. Sorry, my dog is barking. I don't know if you can hear my dog, but. He's over there barking at me. That's very low. That's it. If anybody has any questions, you can ask me questions, or you can ask me questions later. Jane, sorry, your hand up.
- **20:38:35 · JF:** Yeah, sorry if you said already and I missed it. What changes have you made over the original piece, Doug?
- **20:38:42 · Pete Smith:** Yeah, so… Oh, I'm sorry, it looks like. Okay, dog went dead. Um, yeah, that's why I wanted to undersell it. Like, I didn't, I didn't, I didn't do anything. So, uh, I created that logo. What, what, what I did, or what the agent did, was just port it over, support Pstack over, um, for Cloud Code and Codex. Like, the original Pstack has references to Cursor, and how Cursor. Works. So I just ported it over, so it works in… Um, codecs and cloud code. I didn't add anything additional yet. Um… But the idea will be we can add things if we find them useful. We can add Apple-specific things. If we find them useful. So yeah, no changes really. Sorry, one more thing, James. Thanks for reminding me. I'm going to reshare. Sorry, everybody. Very annoying. I'm going to reshare. So a good question. Like, PStack is being continuously updated. So I have a scheduled task that runs every Monday, looks at the latest PStack, and consumes the latest changes, and, like, ports over the latest changes. So I keep it up to date. So I look at the upstream and keep. a stack up to date. But that's other than that, I just I just port it. I don't make any other changes. Like, you know, of course, there's a chance it's not ported well. It might not work properly, but the intention is it's just a direct port.
- **20:40:09 · Jonathan Jackson:** Cool. Thank you, Pete. Paul, I'm protesting.
- **20:40:16 · Pau Ballart:** Yes, thank you. I'm going to share my screen. This is pretty much. a demo that I owe you of the snapshot testing. So, quick reminder, this is already available on iOS, not yet on macOS, because we are waiting for macOS 27. runners on big drives on the CI. on, uh… Yeah, pretty much. It's a package that has a very nice README explaining of it, what I will show today. So you can read it or tell your favorite agent to read it. But it has like requirements, how to use it. A bunch of examples for both iOS and macOS, even though, as I said, macOS. is disabled. But let's do a bit of an example. if I find the Xcode that just crashed, apparently. Ah, it's here, yeah. So, uh, how does it work? We start with the bill. Maybe, or maybe not, you will have previews. That is the new, like, hashtag… preview macro but for a snapshot so I created this one you don't need to use previews but it's just if you use them it becomes handy so there is this new preview provider that's the system. protocol, then if you conform it like this, so pretty much. You configure the different states that you want to have in the view. In this example, it's this segmented control. So there are two previews, one for each tab, let's say. You configure it here. So that's the model or the state of the view. And then you configure it here. So it will render one of the previews for each tab in this case. That basically gives you the previews here, but what is nice about it is that then you have the snapshot test. becomes basically a one liner or yeah one four liner uh but yeah just one call because it reuses the same previews that you refine it and then uh this is just a unit test like. Any other that we have. that runs the test. And this. Basically, you can configure it in different ways, for example. Here, if you want, um… to have a preview, but you don't want to snapshot it, because it's not needed. You have different. uh parameters here in this um. Let me show you. In these configurations, so there is… a scope where you can say, I want just for previews, just for snapshots, or for all of them. And then, um… in the test, you can snapshot in a different set of, um, configurations. So, in these asset snapshots. But everything is here in this package. We have different things. We have the different strategies. If you want to snapshot, for example, iPhones, iPads, all the combinations, just a single screen or a custom. Uh, size? And then you have also. the different sizes of components that you can have in an app, right? Majority of things are the screen, but you can also test some intrinsic content size, bottom sheets, or just any big size that you want. So all of that has, like, default parameters. In this example, for example, it's just, you know, normal screen, and I want to judge a snapshot in that mode, because that screen doesn't have light mode. So, it would work like this. And this is a unit test, it runs super fast, and uh… It passes in less than a second. how it works when you change something so let's say remember we have this previous let's say now i change this uh. this view. No, there is a design change, so we have this title here. If I run the tests, now they will fail. I will show you how it looks like in Xcode. So pretty much, issue recording, blah blah blah, does not match reference. And then, you can go here in your tests. We see the test that failed, and if you double-click, there is this gallery. That basically is showing us the reference, the failure, and the difference. So you can preview it like this. That's the original one. And then the new one that got recorded is this one with hello.
- **20:45:21 · Pau Ballart:** So you can see a diff that it's generated. Basically, you see everything is moving down. Um… So here it can happen two things. It's a real failure and you need to fix your UI, or it's a design change that is… expected, and you want to re-record the test flight, because this is now the new correct design. To do it, you have different ways. Here, there is a record Boolean. You can pass it to true. But at the same time, instead of changing code. If you go to the folder of the test. In in in Git you can let me show you. in a… in another screen. You can just delete the reference image in the file system. So that's the submodule that we have. In the, um… With all the snapshots. So if you go there and delete the file, it will recreate it on top of it. Um, so yeah, basically you have these two options. If there is no original file in the file system, it will just create it right away. If there is an existing one, it will do the comparison and so on. So the easiest usually is, um, to just remove. the image and re-record it. But let's say that… This works, and you upload a PR, and it fails in the CI. So how does it look like? Pretty much the current PR checks that we have for iOS, we'll report them here with the faillet, and it generates an HTML report, which is this one. that, uh… creates the same thing that we see in Xcode, but in the CI. So if you see a PR failing, you don't need to download the artifacts and so on. You just have to open this, and it has, like, these drop-downs. with the same concept, like the reference, the failure, and the diff. Um, so that's… A bit what I wanted to show. Then, um… So the snapshots live in a submodule, as you probably know. So it's a different repo. It's these DuckDuckGo Apple browser snapshots. And it just contains the PNG files. So that is this. Orchestration, if you want to run when you create snapshots, you need to open, let's say, two PRs. But there is a script that handles everything. So what you would do is here when you record your new snapshots. Maybe I can do it really quick. Just a second. I will. Show you exactly what I mean. So we have the submodule. Snapshot references. I'm gonna remove… The, um… Tests for this one. which is the scan QR code test. So I remove it from the file system. Okay, from this folder. And then when I record it or when I run the test, it will record. So first time it fails, but now it says no reference found on disk, which is fine. And then second time it runs, it already has the references and it passes. Okay, so now we want to open the PR, uh, and we can see that the snapshot reference module has the changes. Again, old and new with a new title. So there is a script in the scripts folder. around doo doo doo scripts. called Open Snapshot Zoom Module PR. You just run this over there, runs it, and it will open the PR, so commit, push, open PR, and so on. Um, and then once in your main branch or main PR, there is a new label that you can tag. Uh, let me show you here. Merge the snapshots. So this will merge the snapshots PR and update the pointer and so on. So, it's these two extra steps. You can do it manually, but, uh, the easiest is once you record it, and you have the changes here in Git, you just run the OpenPR, uh… script, and then once your main PR is approved, you can, uh, just use this label to merge the… the snapshots PR. So you…
- **20:50:21 · Pau Ballart:** It's a bit of extra work, but I try to minimize it and automate as much as possible, so… That's how we currently have it set up with these failures and so on. Any questions so far?
- **20:50:37 · Dominik Kapusta:** Yes, this is amazing, and do we have a documentation for that in the Apple documentation project?
- **20:50:44 · Pau Ballart:** For the CAI part, you mean?
- **20:50:46 · Dominik Kapusta:** Yeah, for…
- **20:50:47 · Pau Ballart:** Or in general.
- **20:50:48 · Dominik Kapusta:** In general. You've mentioned that there's a script that simplifies the work, and that would be great to have it as a task in the Apple Documentations project, if it's not there yet.
- **20:51:00 · Pau Ballart:** Okay, I will add it, yeah. Yeah, so the biggest documentation right now is the README, but I understand that it's not, uh…
- **20:51:02 · Dominik Kapusta:** Awesome. Thank you so much.
- **20:51:09 · Pau Ballart:** in the best place. I mean, it's useful, but…
- **20:51:10 · Dominik Kapusta:** Mm-hmm.
- **20:51:12 · Pau Ballart:** Yeah, I will let it also in Asana.
- **20:51:16 · Dominik Kapusta:** Thanks so much.
- **20:51:16 · Jonathan Jackson:** Very cool, thank you, Pao.
- **20:51:20 · Pau Ballart:** I have one more thing to share, which is… So two things. Why is this useful, right? Like, because, okay, we can add a snapshot test and so on. There are three things that I see that are important. First one is PR reviews. Since now the two PRs are linked, it makes it easier to review changes, right? You read UI code of SwiftUI, for example, and you see paddings, frames, blah, blah, blah. Seeing a screenshot helps a lot, so now it would be easy to compare side by side, because you will have here, um… For example, this one. The… the file changes. Directly in the… well, it's not the… This one needs a rename. And you will have the file changes on GitHub to review side by side like this. So PR reviews are better than. I think it was already mentioned we can. think about our UI tests, and if we have UI tests that are asserting. Just how things look like. It's a good candidate to replace with. with the snapshots. Um, so… I will open a proposal at some point, but the idea is… Since UI tests are flaky and snapshots and units. are less flaky and run quite fast. We might look at opportunities to move some of these tests and with a good combination of unit and snapshots. Yes, we are still missing the navigation part of I tap this button and this other screen opens. But yeah, it's up for discussion, but I think you have already a good coverage of a feature, right? And the last thing is ship reviews, because here in this other repo, it's becoming basically like an S3 bucket of data. PNG files. So when you prepare your ship review, if you have used this, you don't need, uh… to regenerate the snapshots and so on. You would just even link it from here or pick them from here. And that's just a starting point. We can improve it with future ideas, like we were talking about different languages. So how we could snapshot test different languages, different dynamic sizes for accessibility, like a large text size and so on. Even, I don't know, when the snapshots PR is open. with some automation, check the original Figma design, and compare it, and there are, there are, um… ways to improve this. So this is just a starting point. And last thing I want to mention, it was part of the tech design to track adoption of this. So far, I'm the only one contributing, which is why I'm doing this demo as well. But I created with Claude an automation that every week checks the repo. It's very easy, because we can just go to the insides of this, um… of this repo and see contributors, but also just check, uh, the asset and snapshot, uh, usages. So this is a dashboard that I shared, uh, within DuckDuckGo. It's updated every week, and basically we can see how. how it grows over time. Um… So yeah, if you fancy, please use it. And if there are any issues, let me know. I'm like the unofficial or official DRI of this. Happy to be on top of it if it's causing issues as well.
- **20:54:59 · Jonathan Jackson:** It's really cool, Pat. Thank you for sharing. Yes.
- **20:54:59 · DR:** Good work, pal.
- **20:55:04 · Jonathan Jackson:** Very cool. We are now at 5 minutes to the top of the hour. Dominic and Alex, you both have postmortems on the list. Do you want to… run those now, understanding we'll go past time, and anybody who can stay is welcome to stay or not? Or would you rather find another time for those?
- **20:55:24 · Dominik Kapusta:** I'm fine running it. It should also be short, but not sure about Alexa's one.
- **20:55:33 · Alex Martemyanov:** Probably can wait till the next Apple Weekly.
- **20:55:37 · Jonathan Jackson:** Okay.
- **20:55:37 · Alex Martemyanov:** I think it was waiting for a year and it didn't wait another week.
- **20:55:41 · Jonathan Jackson:** All right.
- **20:55:42 · Alex Martemyanov:** Thank you.
- **20:55:43 · Jonathan Jackson:** Thank you, Alex. Um, then, Dominic, why don't you go ahead and get started? Anybody who's not interested in Dominic's incident post-mortem, obviously, is welcome to drop. If we run a little bit late and you need to be somewhere else, that's also okay to drop. And Alex, I'll keep yours on the agenda for next week. Thank you.
- **20:56:01 · Dominik Kapusta:** Thanks. I've dropped the link in the agenda as well for the incident postmortem. What happened last Monday is we released the app that was crashing on macOS 12. And, uh, the app was out… well, uh, so the app was out for, like. 3 hours before we, uh, realized that there is a crashing scenario on macOS 12, and then that was handled real quick, uh, with app store rollout stopped. And, uh, Sparkle rollout stopped, uh, as well at some point, um, and the fix was released, actually… well, it… It. Well, almost immediately on DMG, and the next day on App Store, because of the review time. Um, but, uh, how it happened? So, it happened, uh, because we had a change to, um, the save credentials pop-up, which shows up every time you're offered to… you're being offered to save a password. Um… On macOS 12, um… And that change was due to dropping a storyboard, replacing a storyboard with a code-initialized view. So what didn't go as planned? This, uh, change was not tested on old OS versions before merging, and it was strictly macOS 12 issue. Uh, like I mentioned before in this call, we had that engineering expectation in place, but we're not really enforcing it for every change. There's no way of enforcing it, uh, and there's no way of. testing, um… all those versions in CI, so… that's why it happened. Really. Uh, the other thing is, uh, we didn't know about the crash, because, uh, I overlooked it in Sentry. I was the release DRA and I overlooked it in Sentry. There was a single crash on macOS 12 there. Uh, that I treated as noise, and I went ahead and released the app. The sentry summaries weren't generated on that day, because we had another… Whoopsie. Um, the week before, when we updated, uh. Well, some updated the model version and I reviewed it and approved it. and we merged that change, and we updated the model version, but we didn't update the SDK version, and the old SDK didn't… wasn't recognizing the new model, and it failed to… collaborate, so we didn't generate summaries. Um… So that's the other… the other thing. Uh, when the… but! When the summary was generated, uh, it clearly pointed out that there is a crashing scenario on Mac OS 12, which started the incident. A week of internal testing didn't catch a relatively easy-to-reproduce crash. It was a 100% crashing scenario, which wasn't caught. Because we don't have testers on macOS 12. Well, apparently we have one, because we got this one crash at some point. I don't know who it is. I'm…
- **20:59:33 · Alex Martemyanov:** Yeah, and by the way, there was another kind of related issue about the crash on Intel machines. It's not directly related, but yeah, it was close.
- **20:59:41 · Dominik Kapusta:** Yes, another one, exactly. We also don't have testers, or many testers, on x86. architecture. The App Store review took 15 hours, which is rather long for an expedited review, but also there's nothing we can do about it. At least it got in the queue… I mean, it got in the review pretty quickly after requesting a completed review. What went well is that the sentry summary that was eventually generated, um… Clearly identified the crash, and suggested addressing it, and the fix was simple, quick to prepare and test, it was just assigning an initial frame to a view. And the hotfix release automation workflow less at this time. It's always important to point this out, because… We only talk about CI when it's not working correctly. Despite the long review time, we only had 37 crashes in total and only 9 affected users. That's all. for action items and DRIs, we actually, uh… there was an action item to update agent's instruction prefect… essentially update prefect to ensure that Claude agent SDK version is… compatible with used models. Uh, Sam has handled it, and, uh, well, there is a code command right now to, to update the SDK version whenever you update the model version. Um… The other topic that's not actually mentioned here is what to do about testing on older OS versions, but this is something we will be handling separately through Alex's work, mentioned earlier on the call. And… That's it. Finally, I created an incident task through the form. Asana forum, and marked the incident as high, because it's a crashing scenario, we need a hotfix, and an SRE person joined the call, and we talked a little bit, and he, um… Explain to me that if it's a one-person rollout. It's not a high severity incident, and we dropped it to medium, and they dropped the call. And that's it. And, um… That's something to keep in mind for later, for next incidents, when they are only starting rolling out, we may not need SRA help there. This is all I have.
- **21:02:09 · SS:** Regarding the action item, are you happy enough with just having the code comment now that reminds about the Claude SDK?
- **21:02:15 · Dominik Kapusta:** I think so.
- **21:02:16 · SS:** you know, it's… it's not bulletproof, like, what I… what I wanted to do was to just ask the Claude SDK, what models do you support, and check that it's in the list, but it only includes… yeah, it doesn't include all the actual supported models.
- **21:02:18 · Dominik Kapusta:** I think, yeah. I saw that, yeah.
- **21:02:28 · SS:** Eh, maybe the comment's okay for now. I tried to make it very obvious what to do and how to confirm this.
- **21:02:32 · Dominik Kapusta:** Yeah, I mean, that's okay. Also, that comment would show up, because it's just very close to the line that is changing, it will show up in the GitHub UI when reviewing the code, so it should be fine.
- **21:02:37 · SS:** It's right there. Yeah, the only way I was considering extending this was to just have a GitHub Actions check that looks for model changes and adds a comment, GitHub Actions comments. But I would want to do this for all of Prefect. Whatever. I'll look at that.
- **21:02:56 · Dominik Kapusta:** Yeah, yeah. Should be fine. Okay.
- **21:02:58 · SS:** Okay.
- **21:03:00 · Dominik Kapusta:** Thank you. Thanks for handling that, Sam. Alex?
- **21:03:05 · Alex Martemyanov:** Yeah, I got a proposal in… I got it related to post-mortem of the VS Code, but I think it more suits here. What about adding… updating our process to require adding UI tests in addition to renting some older Mac to run older OSs, but make a requirement to the process to cover any UI change. with a UI test. Even if it's a fix or a quick addition in the uncovered region, especially having all the Agentic workflows, it may be a quick and cheap option. I mean, cheap to add. maybe not to maintain. But it adds, of course, it adds extra cost for the runners. Or maybe we could have like a test suite number two that runs weekly, for example, and not daily.
- **21:04:11 · Dominik Kapusta:** I actually think it's… Some Windows team uses something similar. whenever they change UI, they add UI tests, and they have plenty of UI tests, and that's another problem. I believe, but… Yeah, we could… We could discuss it, I guess.
- **21:04:31 · Alex Martemyanov:** Yeah, because, uh…
- **21:04:31 · Jonathan Jackson:** I think that's what we're considering. Sorry, go ahead.
- **21:04:35 · Alex Martemyanov:** Because obvious, like, obvious… thing that could fix it is, uh, like, QA, which we are missing, for… everybody knows for… for why, for what reasons, uh, but we have a lot of, uh, supported platforms, a lot of supported macOS versions, and, uh, it's, uh… Like, uh, it's impossible to… make the requirement as in the mentioned. Uh, process, like, to test all the supported macOS versions, because not everybody even have all these machines that, like, I have the older one, but it's not DuckDuckGo, it's my personal machine. And, uh, I can test it, but it takes time. Uh, and nobody… nobody does it, frankly. And we have no QA, and it's impossible to guarantee the quality in such conditions. So, maybe it's required. It should be a required condition to… to… raise the UI test coverage, the end-to-end coverage, so we can validate we are actually producing quality UI tests. Stuff.
- **21:05:50 · Jonathan Jackson:** Yeah, I think that's worth considering alongside the virtual machine testing stuff that you were talking about earlier, right? I mean, we've known for a long time that we clearly have testing gaps, especially on older versions and older hardware. And… To this point, I think we've just accepted that as the way it is and every now and then something like this goes wrong and we deal with it. um… But we should definitely think about whether there's a promise we're making to our users there that we're not able to fulfill properly. And I think certainly that's true right now. The question is, what does it take to do better at that promise? So I'd love to see some proposals around moving some of these pieces forward.
- **21:06:32 · Dominik Kapusta:** All right, that was all for me. Thank you very much.
- **21:06:38 · Jonathan Jackson:** Alright, and thank you. Um, so, Alex, we're gonna wait till next week for your other postmortem. Thank you for your flexibility there. And thank you all who stayed to finish that out. I appreciate it. And I look forward to seeing you again soon. Bye, everyone.
- **21:06:54 · Alex Martemyanov:** Thank you. Bye.
@@ -15,3 +15,322 @@ source: "https://us01mynotes.zoom.us/Mg62hl1GSI2gw4XeGvHAsg"
- **15:04:34 · Dominik Kapusta:** How are you?
- **15:04:35 · Alex Martemyanov:** I don't know. Pretty, pretty fine, I guess. Mmhm. Still a lot, a lot of things. I'm going through my head.
- **15:04:50 · Dominik Kapusta:** Hmm.
- **15:04:51 · Alex Martemyanov:** And… That gives me some… Darn this. Um, but…
- **15:04:58 · Dominik Kapusta:** What is going on?
- **15:05:00 · Alex Martemyanov:** Yeah, overall… overall, I think it's… It's going pretty fine. There is some… Operational… issues, um, that I'm trying to get resolved. But otherwise… We should be pretty fine. So yeah, the top.
- **15:05:22 · Dominik Kapusta:** um… Is this related to… Sorry. Yeah, I mean, go on. We'll get to that.
- **15:05:24 · Alex Martemyanov:** The top priority. Yeah, so the top priority thing, uh… Basically… basically, I'm getting pinged by, uh, Russell. Like… How long the project is gonna take anymore.
- **15:05:45 · Dominik Kapusta:** Yeah, I saw that.
- **15:05:46 · Alex Martemyanov:** I'm trying to give some reasoning behind it. So basically. We have two-week spans for testing the data and releasing the fixes, and you have eight theories to… to work on, and basically nobody.
- **15:06:03 · Dominik Kapusta:** Mm-hmm.
- **15:06:07 · Alex Martemyanov:** have an idea on what actually is happening under the hood. So… I guess it should be fine. I'm trying to get the project updated and timebox the current.
- **15:06:19 · Dominik Kapusta:** Mm-hmm.
- **15:06:22 · Alex Martemyanov:** Fixes for this week, and uh… Try to get them try to merge it to the release today. So we have the data and… Fixes. the next… What are these? So, to the next… for the next OE meeting, we'll have… data to analyze and to run another mid-mortem to decide on the project life.
- **15:06:49 · Dominik Kapusta:** What day is the OE meeting on?
- **15:06:52 · Alex Martemyanov:** Tuesday, late.
- **15:06:53 · Dominik Kapusta:** Tuesday, okay. Okay, okay.
- **15:06:56 · Alex Martemyanov:** Uh, so yeah, today, uh, is gonna be… Another call. I'm gonna talk about it again. And I guess we should be fine. There is still a lot of unknowns, and I'm trying to fix it in the last minute, just… Just talking to Michal at the moment about the… Fixes, because… the telemetry update for the request is kinda approved as of yesterday, but today I started to reason about it again, and found some issues that we may have with it, that may be polluting our data, and we may need to…
- **15:07:32 · Dominik Kapusta:** Oh.
- **15:07:39 · Alex Martemyanov:** Tune it a little bit more. Uh, so it's… Could be more accurate, especially related to iOS background loading. Because it's handled another way than on macOS, and I just haven't talked about it. Uh, so… Otherwise, we have four, I guess. One is merged. Do this up. Three fixes going today, and probably one or two more. Going later. So, getting to the next release.
- **15:08:16 · Dominik Kapusta:** Mm-hmm.
- **15:08:19 · Alex Martemyanov:** Oh… It's kind of heavy from the… Mental perspective. Because, uh… Thinking of it from, uh… like, 2 years ago, without all this AI stuff. the project would really take at least half a year, or maybe even more, of such a scale, and it's comparable to the navigation refactoring, or so, just to dig inside it. And of course, I cannot.
- **15:08:42 · Dominik Kapusta:** Thank you. Yeah. Okay. Mm-hmm. Yeah, yeah.
- **15:08:53 · Alex Martemyanov:** Digest everything in the web extension stack and everything that's getting fixed and tested and everything.
- **15:08:58 · Dominik Kapusta:** Sure.
- **15:09:01 · Alex Martemyanov:** But I have to go through the pull requests, switch the chats, and uh…
- **15:09:06 · Dominik Kapusta:** No.
- **15:09:06 · Alex Martemyanov:** Get it through my head, which is kind of exhausting.
- **15:09:12 · Dominik Kapusta:** Yeah, yeah, totally.
- **15:09:12 · Alex Martemyanov:** And, uh… In the background, I'm also going through the AUR stuff. Which is some tests. As you've seen.
- **15:09:26 · Dominik Kapusta:** Mm-hmm. Oh, yes, I have… I have some, uh, code reviews. I owe you some code reviews, I guess? No, not anymore. Okay. Ah, yeah, I… yeah, yeah, yeah, that was one that I asked you to… to assign to someone through my OS, yeah.
- **15:09:26 · Alex Martemyanov:** These are some tasks. I… no, you don't. I actually… Yeah, there's one that I already sent from you, and another one was just, uh… Uh… so you were just… In the copy of it.
- **15:09:50 · Dominik Kapusta:** Mmhm.
- **15:09:51 · Alex Martemyanov:** And I applied the self-review. Uh, process, because the change is only included in the test.
- **15:09:55 · Dominik Kapusta:** True. Yes, yes, sounds good.
- **15:09:58 · Alex Martemyanov:** Ah, there is still a deck of pull requests still up. Sure. How many? In 12 years. Yeah, happening in parallel. I also… I also try to keep the wheels rolling on the unit test thing, because if it gets outdated, it would require to start the whole thing from scratch.
- **15:10:34 · Dominik Kapusta:** Yeah, yeah, right.
- **15:10:37 · Alex Martemyanov:** Okay. Okay. Probably later today or tomorrow. And looking forward for the holidays. And this was kind of another topic to discuss later today.
- **15:10:51 · Dominik Kapusta:** Alright, what's… What's on your plate for the Hug Days?
- **15:11:01 · Alex Martemyanov:** Yeah, from the good side of all this work, I kind of cleaned up my backlog, almost. There is still fire window animation, and uh… And, uh… And I'm failing Excel reports. And feature flags, basically. All the other stuff is currently inactive, and uh… pull requests are… open or about to get open. Uh, so… it should simplify my life a lot.
- **15:11:37 · Dominik Kapusta:** Nice.
- **15:11:37 · Alex Martemyanov:** I hope. From the hack days, from the hack days, I basically run AI. Yesterday's night, I just… Thank you.
- **15:11:48 · Dominik Kapusta:** Mmhm.
- **15:11:49 · Alex Martemyanov:** Get another medical phase, I guess. Burst on the ideas and evaluate it around 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11.
- **15:11:53 · Dominik Kapusta:** No.
- **15:12:05 · Alex Martemyanov:** Um… 11. It is. So… I'm thinking how to get it not wasted because some of them may be viable and some of them may need. Some. ship reviews or iteration with the design team, and I am just wondering… I think the macOS browser kinda… active development on Pose. I mean, not bug fixing, but adding new features. Mm-hmm. But still we have this 3D delight highlighted by Gabriel and.
- **15:12:47 · Dominik Kapusta:** Yeah. Oh. Yep. But the macOS development… macOS development is not on pause.
- **15:12:52 · Alex Martemyanov:** I see that I'm right. Alright. It's, uh, deprioritized, or… how's it called? So, there is… Yeah, there is, there is, there is.
- **15:13:12 · Dominik Kapusta:** I don't think I understand that. What do you mean by… But development is on hold.
- **15:13:19 · Alex Martemyanov:** I mean, is it, uh, real to get, uh… Some new features for macOS browser released. Or is it just this demo stuff and that's it?
- **15:13:31 · Dominik Kapusta:** Mmm… I… I'd like to say, I don't think it's necessarily true, but, um… Well, it depends on the feature, probably, that's demoed. Um… There are some… well, there is a backlog of. macOS… potential macOS projects. if you… if you go to… well, so, this is part of our rubric, but within this our rubric, I'm also making this… Digests. of macOS-only projects, and the latest one, which is probably from… September is… Here. And… So the list of projects in this task is taken from our rubric and they are… ordered by the score in the rubric. So, from the top… and there are… yeah, like, macOS Native, the projects in this list don't depend on each other or on design projects. Unless specified otherwise. And from the top. You have password manager extensions, which is a big deal, of course. The next one is import history from third-party browsers. This is being picked up, this is being worked on by Andre. The next one is force websites to use dark mode. We will actually be removing this… current experience, which is internal, and replacing it with the Dark Reader extension, a proper, regular Dark Reader extension that works just fine. In our browser right now. And then we… and then the actual features start. Which is tab groups. And the prerequisite to tab groups is multi-select on tabs. Selecting and dragging multiple tabs at once. And this is… I think it's very hard to do well, because there will be plenty of… Uh, quirks related with… to the… look and feel of that field, essentially. The interaction…
- **15:16:01 · Alex Martemyanov:** Metal… What do you think about me stealing some of those, like, tab groups and multi-select to my Hug Days project? And, uh… Trying to hook it and basically it gets impacted. They all have objective in such way to get to continue basically the development as an extra priority.
- **15:16:17 · Dominik Kapusta:** Thank you. Yeah. Yeah. Okay. Yeah, yeah. Uh…
- **15:16:23 · Alex Martemyanov:** I mean, just an idea.
- **15:16:26 · Dominik Kapusta:** I can't say it will work. But… You could never… you could still just… Just give it a try because it counts, like whatever you do. For Hug Days, that's… I mean, for Hug Days, you can bring your own ideas, but you can as well just accelerate existing roadmaps, and this is exactly it. I, for instance, once I teamed up with Shane, and we did the… NewTapPage prototype? Something like that. And then we turned it into a proper NewTapPage, uh… HTML NewTapPage project.
- **15:17:04 · Alex Martemyanov:** Mm-hmm.
- **15:17:05 · Dominik Kapusta:** So… so you could… if you feel like working on… selecting and dragging multiple tabs at once, that would be great, because I think everyone is afraid of that. And if you could just… just do it, then that would be an amazing addition. And I think this is also something that we could ship independently. We don't need tab groups to ship this thing. This is why it's extracted as a separate project.
- **15:17:35 · Alex Martemyanov:** Mmhm. Well, okay, then it sounds like an idea. Oh… Nice. Nice. And, uh, so virtually… Actually, the list of the experiments I've had. I may try to demo something. Uh, so… So, basically, let me share my screen, I guess. Craft recording, system settings. Sure. Okay, can you see it?
- **15:18:18 · Dominik Kapusta:** Yes.
- **15:18:19 · Alex Martemyanov:** Yeah, so, yeah, first of all, it's running VS Code.
- **15:18:23 · Dominik Kapusta:** Of course.
- **15:18:24 · Alex Martemyanov:** Yeah, and trying not to open Xcode. I just demoed Xcode to my wife yesterday evening, trying to describe what am I doing and why, showing all these glitches and tabs blinking.
- **15:18:37 · Dominik Kapusta:** And… the…
- **15:18:40 · Alex Martemyanov:** Like the best ID by Apple.
- **15:18:43 · Dominik Kapusta:** Mmhm.
- **15:18:44 · Alex Martemyanov:** She was very laughing about it. Like, yeah, Apple's really make makes an amazing stuff.
- **15:18:51 · Dominik Kapusta:** No.
- **15:18:52 · Alex Martemyanov:** And, uh, yeah, me complaining that nobody really understands it. And still prefers to use Xcode. But yeah, anyways, it's working, debugging. Yeah, I can jump to the symbols here. And something I'm going to demo in today's Apple. Apple Weekly. Uh, on the… in the post-mortem, showing the actual results and, uh, sharing the… In the repo, this can be used. So, basically, it uses, uh, Git hooks to install this extension to every, uh, every checkout I make locally.
- **15:19:23 · Dominik Kapusta:** Mm-hmm.
- **15:19:32 · Alex Martemyanov:** And it just works. Uh, I also made a helper or work trees for, uh, this, uh.
- **15:19:36 · Dominik Kapusta:** Okay.
- **15:19:41 · Alex Martemyanov:** How is it called? Raycast.
- **15:19:42 · Dominik Kapusta:** Nice. Yeah. Yeah, I like that. Mm-hmm.
- **15:19:44 · Alex Martemyanov:** Yes, so we can search any, like, fire, something, it filters the active work trees, showing the state, and I can directly open it with VS Code, or Explode, or Terminal, or even delete ones.
- **15:19:51 · Dominik Kapusta:** Hmm. Nice. Yeah, yeah. Haha, cool.
- **15:19:58 · Alex Martemyanov:** Oh. So this build succeeded. I guess it's launching. Is it launching? Very much.
- **15:20:13 · Dominik Kapusta:** I don't know.
- **15:20:14 · Alex Martemyanov:** I guess it's not launching, just building. And yeah, so this still issue of resolving packages. Basically, the benefits we would get if… Migrated to SPM, getting rid of this stage that eats like ten seconds. But otherwise, it's working. And we… what we have else for this while it's loading. No one's listening. That's fine, I guess. Yeah, it's launching. Here… here we are.
- **15:21:07 · Dominik Kapusta:** Mm-hmm.
- **15:21:08 · Alex Martemyanov:** Yeah, something that I was doing for this project is the burn animation here.
- **15:21:08 · Dominik Kapusta:** Nice.
- **15:21:16 · Alex Martemyanov:** So it's like burning the window. Uh, completely not… not going through it, but when the fire animation goes and, uh, just…
- **15:21:25 · Dominik Kapusta:** Ah, nice. You know.
- **15:21:28 · Alex Martemyanov:** clears it behind.
- **15:21:30 · Dominik Kapusta:** Oh man, that's so great!
- **15:21:32 · Alex Martemyanov:** And there is one more thing.
- **15:21:35 · Dominik Kapusta:** It's… just one thing, it's not looking… it's not looking super sharp while you're sharing the screen, so maybe worth recording an animation and just sharing. somewhere.
- **15:21:47 · Alex Martemyanov:** Yeah, maybe there is actually a choice of animation and we can do this.
- **15:21:53 · Dominik Kapusta:** Awesome.
- **15:21:54 · Alex Martemyanov:** Or we can do what? we can do… this… Okay.
- **15:22:05 · Dominik Kapusta:** Nice.
- **15:22:05 · Alex Martemyanov:** I just was thinking it would be, it could be nice to bring it to… to production, generally.
- **15:22:13 · Dominik Kapusta:** Mmhm.
- **15:22:13 · Alex Martemyanov:** And, uh, there is another fix of the… A link preview that shows the link text on the left. Bottom corner.
- **15:22:24 · Dominik Kapusta:** Mm-hmm.
- **15:22:24 · Alex Martemyanov:** And if you put the cursor in the left down corner, it's overlapping. And so adding another window, I guess it should have a small quick ship review and just go to production since we have a task for it in the backlog.
- **15:22:31 · Dominik Kapusta:** Yeah, okay.
- **15:22:42 · Alex Martemyanov:** But the fire, maybe I should talk to Stephen, I guess, just suggesting it as an improvement and show a demo.
- **15:22:43 · Dominik Kapusta:** Okay. Mm-hmm.
- **15:22:54 · Alex Martemyanov:** And we may… Mayrama project, maybe… Make it a little bit sharper. Or make some extra tuning. but, yeah. Otherwise, the principle is pretty simple. We are just… instead of all this, uh… jumping across, uh… the animation layer, tabs, tab bar, and everything, it just makes a snapshot, and… deals animation on top of it, hiding window instantaneously, doing all the job behind the scenes.
- **15:23:20 · Dominik Kapusta:** Mm-hmm, yeah, yeah. Sounds simple, now that you've said that.
- **15:23:28 · Alex Martemyanov:** Yeah, basically everything's just one shot made by AI.
- **15:23:29 · Dominik Kapusta:** It's just. Mmhm. Yeah, yeah.
- **15:23:35 · Alex Martemyanov:** Another thing I made is, uh… reviving the old projects on the browser profiles and dedicated apps for websites.
- **15:23:45 · Dominik Kapusta:** Mmhm.
- **15:23:46 · Alex Martemyanov:** and rewriting it using the web storage, or how is it called? Basically a FHIR window, but a stored FHIR window with naming profiles. It is… it was also a… feature user were asking for for a long time, I guess.
- **15:24:05 · Dominik Kapusta:** So what exactly? Like a separate storage?
- **15:24:07 · Alex Martemyanov:** Uh, profiles. Profiles, separate storage, yes. And, uh, dedicated apps, actually, that Safari does.
- **15:24:09 · Dominik Kapusta:** Profiles, okay. Yeah, yeah, yeah, yeah. Yes. Yes.
- **15:24:18 · Alex Martemyanov:** Uh, what else was there?
- **15:24:19 · Dominik Kapusta:** Profiles is a big deal, because profiles can be understood in various ways, and one of the ways is just separate instances of the app, really, with separate bookmarks, separate settings, and so on and so on. Umm. Yeah, okay.
- **15:24:37 · Alex Martemyanov:** Yeah, another one was bookmarks and history search from the menus and the bookmarks bar when you start typing, like in the help menu.
- **15:24:44 · Dominik Kapusta:** Mm-hmm. Mmhm.
- **15:24:48 · Alex Martemyanov:** And it searches… Bookmarklets. I guess that would require privacy triage or security triage.
- **15:24:58 · Dominik Kapusta:** Probably not. I'm not sure, because Windows supports it.
- **15:25:03 · Alex Martemyanov:** Hmm, okay.
- **15:25:03 · Dominik Kapusta:** I've just, I've just, I've just tested it last week, because we needed something. I don't remember why, but the topic of bookmarklets appeared, and I was testing Windows, and they just support it, so…
- **15:25:17 · Alex Martemyanov:** Thank you.
- **15:25:19 · Dominik Kapusta:** Maybe it was because they moved to Chromium, I don't know. Yeah, let me quickly check.
- **15:25:19 · Alex Martemyanov:** Okay, that should be fine then. Yeah, for sure, Chromium does support it.
- **15:25:26 · Dominik Kapusta:** Oh, my God. Yeah, yeah, yeah, of course, of course.
- **15:25:29 · Alex Martemyanov:** But from our side, it may require some extra precautions, like security or privacy.
- **15:25:38 · Dominik Kapusta:** Mm-hmm.
- **15:25:38 · Alex Martemyanov:** Because they are not Chromium, essentially.
- **15:25:40 · Dominik Kapusta:** Yeah. This is the issue that we got on Reddit. And, uh… And I had a task, I had a task to scope a project to support bookmarklets.
- **15:25:52 · Alex Martemyanov:** Mm-hmm. Okay, and uh… What else? Basically, the last thing was the tab groups, research.
- **15:26:09 · Dominik Kapusta:** Mm-hmm.
- **15:26:10 · Alex Martemyanov:** And, uh, it's… Didn't produce any. testable thing, but anyways, I think that should be more than enough for a demo, and maybe even grow to some projects like our groups, for example.
- **15:26:20 · Dominik Kapusta:** Yeah, totally. Mm-hmm. Mm-hmm. Yeah, sure.
- **15:26:27 · Alex Martemyanov:** So, yeah, that's how the late night went yesterday.
- **15:26:31 · Dominik Kapusta:** just. Just, just a thought that… We've had a couple of… Hug Days demos for type groups already, in the past Hug Days. So, just so you know, um…
- **15:26:43 · Alex Martemyanov:** Yeah, sure.
- **15:26:48 · Dominik Kapusta:** I don't know what to say. I just wanted to say that we've seen it a couple of times, nothing happened out of it. Probably because there's always more important work to do. But I think… If you would be able to add multiple selection. And drag and drop for multiple tabs at once, that would be a killer feature, that would be something that we could totally just add. to the browser right now, which… because it's more… it's much simpler than tab groups, right? Conceptually. Just a…
- **15:27:25 · Alex Martemyanov:** Yep.
- **15:27:26 · Dominik Kapusta:** a single interaction, really, yeah. So if you want to make impact quickly, then that would be simple. And the tab groups… we did tab groups a few times, so… and of course, you can do tab groups, everyone knows that. You can do tab groups.
- **15:27:26 · Alex Martemyanov:** Yeah, you're right.
- **15:27:41 · Dominik Kapusta:** Um… No.
- **15:27:43 · Alex Martemyanov:** Yeah, there is one… one more thing I tried. It's basically the raycast, and uh… Integration. Like… Tapping.
- **15:27:57 · Dominik Kapusta:** Nice.
- **15:27:57 · Alex Martemyanov:** Dr. Yai. Searching… or bookmark search. And the same, basically, for the, uh… Or, how is it called? Spotlight. Yeah, so I'm also thinking if it could be… somehow released, or… I don't know. Probably should go through the product.
- **15:28:35 · Dominik Kapusta:** Yeah, but… so that Spotlight plugin… it would be shipped with the app, and then Spotlight would… get extra functionality if DuckDuckGo is installed? Mm-hmm.
- **15:28:45 · Alex Martemyanov:** Uh, yeah, Spotlight is… Spotlight is shipped within the app, and Raycast needs an extension.
- **15:28:50 · Dominik Kapusta:** Mmhm. Okay, yeah.
- **15:28:54 · Alex Martemyanov:** distributed through the Raycast store.
- **15:28:57 · Dominik Kapusta:** Right. Yeah, that Spotlight plugin would be cool, for sure. So I guess it's just a target in the app, right? Like some… Up extension, something like that.
- **15:29:08 · Alex Martemyanov:** Uh… Probably.
- **15:29:10 · Dominik Kapusta:** Mm-hmm. Okay. Yeah, sure.
- **15:29:11 · Alex Martemyanov:** I haven't seen the code.
- **15:29:16 · Dominik Kapusta:** Oh, okay. Funny. Great.
- **15:29:22 · Alex Martemyanov:** Yeah, so… So that's the plan for the holidays, I think should be plenty.
- **15:29:27 · Dominik Kapusta:** Mm-hmm.
- **15:29:30 · Alex Martemyanov:** And, uh… And yeah, we have the upcoming… Performance review, right?
- **15:29:37 · Dominik Kapusta:** Yes, we do. And I would like you to… Spend a moment. This week. Probably. Well, if not this week, then you'll have to do it on Monday, which is… which may be tricky, I don't know, but Monday will be the due date for your self-reflection, which I think now is called self-assessment. One second.
- **15:30:05 · Alex Martemyanov:** Mm-hmm.
- **15:30:06 · Dominik Kapusta:** uh… Oh. Where is it? I don't know. Ah, I know. One second. self assessment template. Yes. Here's the link. There are also… Trainings. For on the performance review this week. I don't know the dates, but… It's happening. Performance review trainings.
- **15:30:51 · Alex Martemyanov:** Mm-hmm. And that's basically the usual stuff.
- **15:31:00 · Dominik Kapusta:** Thursday, 9am ET. That's… late for you. 7:30, 7:00, 7:00 PM, I guess.
- **15:31:15 · Alex Martemyanov:** 9 a.m. ET. ET, 9… AM. Yeah, 7, it's fine.
- **15:31:26 · Dominik Kapusta:** So… It's the usual stuff. But… But, yeah, uh… There are also recordings here. And, uh… The thing with the self-assessment thingy is that the template is new. And it's shorter, it's supposed to be shorter than the self-reflection. You have these five… Five sections, project management, which essentially map to dimensions. And then the looking ahead section, and you're supposed to fill each of them with… Well, with your assessment of the last period and keep it 150 words or shorter. Each section.
- **15:32:30 · Alex Martemyanov:** Thursday, 9 AM is… Is it Thursday?
- **15:32:37 · Dominik Kapusta:** Yes. My name is T.
- **15:32:40 · Alex Martemyanov:** Yes, but… Okay. Not to miss it as I lost time mixing the dates.
- **15:32:48 · Dominik Kapusta:** Mm-hmm. Ah, yeah, yeah, yeah. So, that's the self-assessment template, and… Umm… I will probably be working on mine this week, sometime during Hug Days, just so that on Monday I can just… Just verify that it… oh, copy it over to the official task and verify if it makes sense and just complete it. And you're supposed to complete it on Monday.
- **15:33:07 · Alex Martemyanov:** Mmhm.
- **15:33:18 · Dominik Kapusta:** And then… I'll be working on your review for the next three days. And that's… and that's roughly it. And then talking with review advisors and blah blah blah. for your career… for your growth areas. I've updated them after our discussion last time. I updated them with. A shout out. And essentially kept the previous growth areas, uh… so here's the link again. And that's that. So, essentially… I just reflected what was in the feedback. About the communication project, like…
- **15:34:10 · Alex Martemyanov:** Mmhm.
- **15:34:13 · Dominik Kapusta:** You can surely… Oh. Relay your thoughts into comments and updates on the project, but just remember to… to do it unprompted, to avoid being pinged on that, and that would be great. And then, I think it's the only thing missing, uh… Here. And then you didn't have a chance… so you did great with, um… With, uh, code reviews and the ship review, uh… contributions to Andre's project. So… have a look at more opportunities like that, and also have a look at tech designs that appear in the Apple team.
- **15:35:01 · Alex Martemyanov:** Mm-hmm.
- **15:35:03 · Dominik Kapusta:** Um, to… share your thoughts on that, and I think that's what we need to be looking for. What we're looking for, essentially, is… because the rest… the rest, you're just… you're just doing it. You're doing functional expertise. it's… it's a clear D double star, and we… uh… we also won't move it to E until you're at least D star in project management, that's what I've been told. It would be hard to bump. Functional expertise to E without at least a star in project management. So that remains at this DW star. Organization leadership, you're at this star already. Uh… I know they're doing that. You're just… just… just… just… uh… Um, focusing on, uh… improving the macOS browser in many ways, and fixing issues as they come, and fixing stability of tests, and so on and so on, and you're just actually working on it. Um… Mostly on your own. Uh, which is… Which is not bad, either. I mean, not bad anyway, but… it's just how we work here, right? You have your backlog, and you work on that, and you know what you need to do, so that's great. Some of the initiatives… are not necessarily… ideal for the team, at least. I mean, you've worked on the VS Code thingy, it appears not to be… very appealing to the entire team. So, there may be discussions of whether this was… Time well spent. But we've had that… we've had that discussion at some point. Oh, you… so, what's… undiscussable is that. As part of this effort, you did a lot of improvements to the macOS codebase, and that's great. And then we stopped at some point. Which probably was the right point, when… The rest of the team learned about everything, and they started asking questions, and you open a proposal, and tech design, and there was a longer discussion, and the…
- **15:37:26 · Alex Martemyanov:** Yeah, there was a discussion of actual effort to implement the… the actual thing was relatively low, so it was more about the refactoring itself, and…
- **15:37:26 · Dominik Kapusta:** Think was. was closed. Yeah. Mm-hmm. For…
- **15:37:37 · Alex Martemyanov:** fixes that are proceeding it.
- **15:37:39 · Dominik Kapusta:** For the future, I think you could… you could go with, uh… a proposal earlier than that, maybe, if that makes sense. I know there was that tech design a year ago, but, you know, a year is a long time, people sort of forgot about that in the meantime. Yeah, but… But overall, it was… it was… it was… I mean, a lot of it was worth it. And I wouldn't really… be connecting that incident that we had with the VS Code, uh, initiative. It just happens, right? It's… sometimes it happens. We'll talk about it in the Apple Weekly. it's not easy to test everything on macOS 12, unless we will be… we want to accept that we'll be working, like, twice… I mean, half as fast, so 50% slower.
- **15:38:38 · Alex Martemyanov:** Well, the answer would be QA, but yeah, I know.
- **15:38:39 · Dominik Kapusta:** Thank you. Yeah, yeah. And. Yeah, so that's organizational, and the one that you're… that I'm trying to push you into more is team leadership, and that means… Well, project advising. That's one thing, but it's very hard to get to project advising if you're jumping between objectives. And also, it works… better if you have proven project management skills first, but you're… I think you're almost there. Um… Next thing I wanted to say is… Yeah, project advising, but outside of project advising, it's… Growing people via code reviews, via, um… Should preview commands and take design commands.
- **15:39:37 · Alex Martemyanov:** Mm-hmm.
- **15:39:38 · Dominik Kapusta:** So, yeah, that could be a way to bump your team leadership. Uh, and also this… Cycle is short. So let's see if we can… Bump anything. But… If we can, that would be great. I was thinking about project management, but let's see what… Let's see what happens. Let's see if I'm able to defend that. The conclusion may be that, yeah, you still need more time. And then we'll have to wait until next cycle. Yeah, but let's see. Let's see. I'll do my best. And you can help me by writing yourself a section.
- **15:40:22 · Alex Martemyanov:** It's fine.
- **15:40:29 · Dominik Kapusta:** on time.
- **15:40:31 · Alex Martemyanov:** Mm-hmm.
- **15:40:34 · Dominik Kapusta:** Good. So that's the… that's the, uh, growth areas and shoutouts. Next week, I would ideally… not have a meeting, not have any meetings on Tuesday, because I'll be busy writing reviews. So, yeah, we could just skip it next week.
- **15:40:53 · Alex Martemyanov:** Good.
- **15:41:01 · Dominik Kapusta:** I had one more thing. That I don't remember. Oh, I was looking at… I was actually thinking actively about your proposal for macOS 12 testing, and I… at the end, I wrote that we'll have this post-mortem, and hopefully we'll talk more as a team.
- **15:41:11 · Alex Martemyanov:** Mm, yep.
- **15:41:21 · Dominik Kapusta:** About possible solutions for that, but… Uh, in the meantime, I noticed that Bitrise have removed macOS 13 image, so they only have macOS 14, and I think they will keep the macOS 14 for, like, a year more. while GitHub is removing macOS 14 in November. But that's macOS 14, and 13 is out already, and 12 as well, of course. So I don't know.
- **15:41:50 · Alex Martemyanov:** Uh, well, let me… Let me ask you another question, which may also need some thoughts.
- **15:42:00 · Dominik Kapusta:** Yeah.
- **15:42:01 · Alex Martemyanov:** So let me share my screen. So basically this is the… The system also was, um… Via coding in parallel, so it's the virtual machine fleet.
- **15:42:12 · Dominik Kapusta:** Mmhm. Mmhm.
- **15:42:16 · Alex Martemyanov:** Uh, controller, like, maintaining images, right, and activity, leases, uh, Xcode installs, uh… Uh, system protection, disabling, TC\CC, and all this stuff. And it's basically controlling my current Mac with the external drive, controlling older MacBook, which can be booted and also used for.
- **15:42:38 · Dominik Kapusta:** Mmhm.
- **15:42:43 · Alex Martemyanov:** Remote debugging and remote UI test and so on. And yeah, and some virtual machines extra. Uh, there is one note on the, uh… Yeah, and this is supposed to be, like, uh… orchestrator over the TART system that's used on production runners, like Detraze, I think.
- **15:43:11 · Dominik Kapusta:** Yeah, yeah, yeah, yeah.
- **15:43:13 · Alex Martemyanov:** And it provides MCP controls, which is supposed to give agents ability to run the UI tests, boot up, get a lease for virtual machine, run the tests, shut it down, perform cleanup and so on. And… Still, there is this rule about external MCP and tools that should be approved by org. Uh, highlighted in the… bug days, uh… Agenda? So…
- **15:43:51 · Dominik Kapusta:** Okay.
- **15:43:52 · Alex Martemyanov:** I'm thinking whether or should I present it to the team as a possible solution for integration and including macOS 12 and 13 tests support.
- **15:44:02 · Dominik Kapusta:** I think we can talk about it. I think we can talk about it. Ideally, we would have… A machine. Somewhere. That runs this. And that machine… so, if that machine could… run virtualization on its own. and be used for testing on macOS 12 and 14, that would be great. And we wouldn't… be doing that. On a regular basis, but… So I was talking about it a little bit with Jonathan, and he said, if we are able to run tests once a week. That would be something already. At least know if the app is crashing or not. Like the proper smoke test. If there is a smoke, then something is wrong. About, uh… We don't seem to have… a way of… Um… Setting this up as part of CI. And that would be ideal, but… But we won't be able to do it. And I wouldn't rely on local setups, because… Most likely, people… Wouldn't. Random. Essentially. Unless it's… it's really straightforward. But maybe you can make it straightforward. To some extent. So that if we had these setups and we could just say, okay, test. test on macOS 12 now, and if it all worked, that would be amazing, that would be great, actually. And that would be…
- **15:45:51 · Alex Martemyanov:** Maybe…
- **15:45:53 · Dominik Kapusta:** A big thing.
- **15:45:55 · Alex Martemyanov:** Should I… Should I raise a question?
- **15:46:00 · Dominik Kapusta:** Mm-hmm.
- **15:46:00 · Alex Martemyanov:** or… I don't know… proposal, voting… Thoughts sharing during the Apple Weekly. suggesting this kind of a solution that can be potentially used as an agent MCP for automated testing.
- **15:46:11 · Dominik Kapusta:** Mmhm.
- **15:46:19 · Alex Martemyanov:** Like, any testing, unit testing, integration testing, UI testing, essentially.
- **15:46:19 · Dominik Kapusta:** Mmhm.
- **15:46:27 · Alex Martemyanov:** Yeah, unit testing won't work because…
- **15:46:30 · Dominik Kapusta:** No, yeah, yeah, it wouldn't.
- **15:46:30 · Alex Martemyanov:** Maybe it would work with the test bundle directly moved. Yeah, there is some ways, but yeah, mostly for UI testing or agent-based screen control.
- **15:46:33 · Dominik Kapusta:** Ah, hmm. Mm-hmm. Yeah, we can limit it to UI testing, sure.
- **15:46:43 · Alex Martemyanov:** So, whether anybody is, uh, wishing to have… something similar to have, uh, this kind of local setup. It supports, uh, remote debugging from VS Code as well, by the way, so we can just…
- **15:46:57 · Dominik Kapusta:** Okay.
- **15:46:58 · Alex Martemyanov:** Select the virtual machine where you want to run the browser, and it will boot up, show the screen, and connect to it, and you will be debugging, like. And.
- **15:47:07 · Dominik Kapusta:** with… with Xcode. Uh, local?
- **15:47:11 · Alex Martemyanov:** Yes, with local export.
- **15:47:12 · Dominik Kapusta:** Install? But you have to have the lower version.
- **15:47:14 · Alex Martemyanov:** Without Xcode.
- **15:47:17 · Dominik Kapusta:** Or.
- **15:47:18 · Alex Martemyanov:** Yeah, of course, you have to install the Xcode tools in the virtual machine, which is managed automatically.
- **15:47:25 · Dominik Kapusta:** Mm-hmm.
- **15:47:26 · Alex Martemyanov:** But you just click run in VS Code, and it just runs. Like, Xcode would do, but Xcode does not support remote debugging.
- **15:47:30 · Dominik Kapusta:** Okay. Yeah. Look…
- **15:47:37 · Alex Martemyanov:** I'm not quite sure that I can demo it right now, but this feature is already baked in. I just haven't tested it directly and it even starts instantly without all this loading of symbols.
- **15:47:40 · Dominik Kapusta:** Yeah, yeah, yeah.
- **15:47:53 · Alex Martemyanov:** Because the dynamic library cache is also loaded and available from the virtual machines. So it just can be straight debugged from the host.
- **15:47:57 · Dominik Kapusta:** Mm-hmm. Yeah, to be fair, that sounds… really tempting to me. Uh… But… Only if it was… very simple to use, as in, I tell my agent, run this test on macOS 12, and it does everything, setting up the virtual machine, uh, installing an image. Copying the app and running it.
- **15:48:36 · Alex Martemyanov:** Yeah, so that's… that's… that's the question I…
- **15:48:37 · Dominik Kapusta:** Ruby.
- **15:48:41 · Alex Martemyanov:** Thinking to just bring up during the Apple Weekly, and just ask if anybody would use.
- **15:48:47 · Dominik Kapusta:** Yeah.
- **15:48:48 · Alex Martemyanov:** Something like it, if it's.
- **15:48:49 · Dominik Kapusta:** Yeah, okay.
- **15:48:50 · Alex Martemyanov:** ready available and one click from running.
- **15:48:54 · Dominik Kapusta:** Mm-hmm. Mm-hmm. Uh…
- **15:48:56 · Alex Martemyanov:** justifying the Xcode project as well.
- **15:48:59 · Dominik Kapusta:** So… So, we have that thing called Apple Engineering Expectations. And… One of the expectations is testing supported macOS versions, and we have it here. And then… It says… something about ensuring that older macOS versions are included in the testing process. This is actually… Kind of a dead lull, because no one does this. Virtually no one. You do it, right? But also not for everything, right? Not for dropping the storyboard. Fine, I mean fine, right? I wouldn't do it either, and I would just see the crash and fix it.
- **15:49:42 · Alex Martemyanov:** No, I don't.
- **15:49:54 · Dominik Kapusta:** But. So we have this, and it's like a wishful thinking. People should be doing that, but people are not doing that, because it's so much work. Um, so…
- **15:50:03 · Alex Martemyanov:** Yeah, so basically it has this use virtual body. That means you should install virtual body, you should download an image, you should manually go through the setup assistant, you should manually download Xcode.
- **15:50:12 · Dominik Kapusta:** Yeah, yes, maintain it. Yes, yes.
- **15:50:17 · Alex Martemyanov:** pass the app to it, and have NSAlert-based debugging.
- **15:50:22 · Dominik Kapusta:** Mmhm.
- **15:50:23 · Alex Martemyanov:** But I'm kind of suggesting the other way when you install this Verfil's piece of software and you just click run from VS Code and it just works.
- **15:50:26 · Dominik Kapusta:** No. No. Mm-hmm. Yeah, yeah.
- **15:50:40 · Alex Martemyanov:** So, just something to discuss.
- **15:50:44 · Dominik Kapusta:** Yeah. That sounds good to me.
- **15:50:46 · Alex Martemyanov:** I don't know, maybe you can talk about this. expectation to support the older macOS as well, and vote up for it.
- **15:50:53 · Dominik Kapusta:** Mm-hmm. Totally, totally.
- **15:50:56 · Alex Martemyanov:** And, then we can make a proposal to. To include this system as, like, an official setup, maybe?
- **15:51:05 · Dominik Kapusta:** Mmhm.
- **15:51:05 · Alex Martemyanov:** And run it under an official project in the AOR.
- **15:51:11 · Dominik Kapusta:** Sure. Sure, sounds good. Sounds good. That would be great.
- **15:51:22 · Alex Martemyanov:** Okay, then.
- **15:51:27 · Dominik Kapusta:** Nice. Is there anything else we should cover? Bye-bye.
- **15:51:33 · Alex Martemyanov:** Uh, yeah, about the separate project file… It's kind of part of…
- **15:51:38 · Dominik Kapusta:** Oh, yes. Mmhm.
- **15:51:39 · Alex Martemyanov:** This, I mean…
- **15:51:41 · Dominik Kapusta:** Yeah, I mean, that…
- **15:51:42 · Alex Martemyanov:** The bigger… the bigger picture includes it. Oh, yeah. It has some couple of talks. Introduced retrofitting some XC tests.
- **15:51:51 · Dominik Kapusta:** Oh.
- **15:51:57 · Alex Martemyanov:** thing to be supported on macOS 12. It's one file.
- **15:52:00 · Dominik Kapusta:** Okay. Okay. Okay. Bye.
- **15:52:02 · Alex Martemyanov:** Of, like, 400 lines, and uh… And using all the runner. Oh. So it's 100% doable. My agents are running those tests using this hack. Uh, without separate project, but they are building it locally, deploying, and using the hub to run it. And I'm not sure whether it's final, uh… final architecture we want, and there is a lot of mistakes. Agents are… Okay. during the process, and maybe separating this Xcode project. Would simplify things a little bit.
- **15:52:46 · Dominik Kapusta:** Mmhm. Okay, but the idea is to completely remove UI tests from the Xcode project, or just have another project for macOS 12 and older?
- **15:52:56 · Alex Martemyanov:** Not remove, but rebase. So like we have iOS project and macOS project, we'll have a third project for macOS UI tests because it's a separate project.
- **15:53:03 · Dominik Kapusta:** Mm-hmm. Okay.
- **15:53:08 · Alex Martemyanov:** It does not require any of the dependencies to resolve it every time. It will make the build faster, excluding submodels and the package resolution.
- **15:53:10 · Dominik Kapusta:** Mm-hmm. Mm-hmm. Yeah, I see. Okay.
- **15:53:19 · Alex Martemyanov:** Uh, like, currently, build takes a lot of time for… on each runner.
- **15:53:19 · Dominik Kapusta:** Uh, one… fine. One thing, sure, one thing that is. Handy today is that you can just… stay in the same Xcode project and just run UI tests.
- **15:53:36 · Alex Martemyanov:** Yeah, and we are basically not risking anything.
- **15:53:37 · Dominik Kapusta:** So…
- **15:53:40 · Alex Martemyanov:** in production. If it won't work, we will put it back.
- **15:53:45 · Dominik Kapusta:** Yeah, yeah, yeah, yeah, sure, but your plan would be to… move these UI tests from the macOS Xcode project to that separate Xcode project, so that if you want to run UI tests, if you want to run UI tests, you would have to… locally, you would have to do what?
- **15:53:57 · Alex Martemyanov:** through your iTest project, yeah.
- **15:54:04 · Dominik Kapusta:** First build the app.
- **15:54:04 · Alex Martemyanov:** Hmm, same thing.
- **15:54:06 · Dominik Kapusta:** Which is what?
- **15:54:06 · Alex Martemyanov:** Same thing. Have the dependency, choose the scheme, and run it. I guess nothing changes from… Nothing should change from it, from the current setup.
- **15:54:24 · Dominik Kapusta:** But you… Didn't you say that you want to… move these tests from one Xcode project to another.
- **15:54:33 · Alex Martemyanov:** Uh, yes, but I think… I assume the expectation is to load and work from the export workspace file.
- **15:54:42 · Dominik Kapusta:** Ah…
- **15:54:42 · Alex Martemyanov:** Isn't it?
- **15:54:43 · Dominik Kapusta:** Okay, yeah, yeah, sure.
- **15:54:44 · Alex Martemyanov:** I mean, yeah, if you run the macOS project directly, it won't be there, but if you load the whole file, it's still there.
- **15:54:48 · Dominik Kapusta:** Yeah, yeah, yeah, I'm… yeah, totally. I'm just not using the AI workspace at all, but that's just me, so…
- **15:54:55 · Alex Martemyanov:** So, yeah, that's a cone.
- **15:54:58 · Dominik Kapusta:** Huh-huh. But that's okay, I mean, I know that I'm the minority. Plenty of people use the workspace, so we should be fine.
- **15:55:10 · Alex Martemyanov:** Yeah, so that's the deal, and it should… Should just work.
- **15:55:15 · Dominik Kapusta:** All right. Uh, alright, great. Great. Let's talk more about it in the Apple Weekly, for sure. All right, all right, all right. Anything else? You mentioned some organizational issues.
- **15:55:39 · Alex Martemyanov:** Uh…
- **15:55:40 · Dominik Kapusta:** Anything I can help you with?
- **15:55:42 · Alex Martemyanov:** Some of operational issues. And, uh…
- **15:55:45 · Dominik Kapusta:** Operational, yeah.
- **15:55:47 · Alex Martemyanov:** I mean, there's all in the… Events reporting, uh… I'm talking with Michal about it.
- **15:55:54 · Dominik Kapusta:** Ah, okay, okay.
- **15:55:55 · Alex Martemyanov:** Just… just in the moment, and I hope we can get it… get it released today, just so it gets to the internal…
- **15:56:03 · Dominik Kapusta:** Mmhm.
- **15:56:03 · Alex Martemyanov:** Or can I do it tomorrow? It's too…
- **15:56:07 · Dominik Kapusta:** Um… ideally today. You can, of course, do it tomorrow with a release exception.
- **15:56:09 · Alex Martemyanov:** problematic, yeah. Yeah, okay. So, yeah, I'm trying to get it released today, and… And report it in the OEE stand-up meeting. And that's it.
- **15:56:25 · Dominik Kapusta:** Sounds good.
- **15:56:26 · Alex Martemyanov:** Otherwise, there's pretty much none of the tasks on me remaining. Except for the old Greek twins that are just hanging on me.
- **15:56:37 · Dominik Kapusta:** Now.
- **15:56:38 · Alex Martemyanov:** Thank you.
- **15:56:39 · Dominik Kapusta:** All right.
- **15:56:40 · Alex Martemyanov:** And…
- **15:56:42 · Dominik Kapusta:** Alright, cool. Uh… fine. If you need anything from me these hack days, let me know. Um… Please work on the… Yeah, going on.
- **15:56:52 · Alex Martemyanov:** Yeah, so basically… What's the expectation on the holidays? Uh, for the changes, like fire animation, or… something… like, bookmark search. Is it… should I contact Steven on it and, uh, try to… Push. Yes. Quick project.
- **15:57:14 · Dominik Kapusta:** I think… so what you've shared with me right now, I couldn't see… the animation was not looking great on the shared screen, right? I only saw a few frames at the beginning and at the end, but if you can record the video… Uh, and if it really is, like, the window is being burned, so you can see the window underneath of what was burned, and then I think it's…
- **15:57:36 · Alex Martemyanov:** Yeah. Cheers.
- **15:57:41 · Dominik Kapusta:** It would be an amazing thing to have, and if you could… I mean, you can show it to Steven at any time, because you have it, you can just record a video and send to him and say, what do you think about it? I'm… and that would probably be greatly appreciated. I'm not sure if they would want these pixel animations. Because we like the fire thingy and just because of that. But yeah, definitely send that to Steven. And, yeah, I think we could, we could… Try and move forward with it.
- **15:58:20 · Alex Martemyanov:** Okay, and I'll try to experiment with the tab grouping, dragging, whatever, maybe it will grow to the project. For me, it's called Popoyama. Right.
- **15:58:35 · Dominik Kapusta:** Right, right.
- **15:58:38 · Alex Martemyanov:** And, uh, yeah, the rest of the week for the, uh… So, reflection.
- **15:58:44 · Dominik Kapusta:** Mm-hmm. Sounds good. Awesome.
- **15:58:45 · Alex Martemyanov:** And that's it.
- **15:58:47 · Dominik Kapusta:** Cool, cool. Sounds great. All right.
- **15:58:49 · Alex Martemyanov:** And yeah, today, today about weekly, I have three demo sessions. And one postmortem.
- **15:58:58 · Dominik Kapusta:** Yeah, which is fine. Looking forward to it.
- **15:59:01 · Alex Martemyanov:** Ah, postmortem, I should fill the template, yeah.
- **15:59:01 · Dominik Kapusta:** All right. Yeah. Yeah, all right. Cool, uh, so I'll see you later, and we'll catch up later this week if needed. Thanks a lot.
- **15:59:15 · Alex Martemyanov:** Okay, sure. Yeah.
+10 -10
View File
@@ -86,8 +86,8 @@
"note_modified_at": "2026-10-16T15:51:25.415Z",
"source_url": "https://us01mynotes.zoom.us/klekRLtLSEuMv0PCCPCjtA",
"folder": "2026-10-16 All-Company Meeting 2026-10-16 21 31(GMT+6 00) klekRLtLSEuMv0PCCPCjtA",
"sha256": "86407aecffbf09effe200b26e80a01887ee197ba99d5caea70c124743fbee3fb",
"cues": 3
"sha256": "34ef73307fe86cc2d6f98caf57a719ae46937fb2d0efea3a18e03e21a42f1e00",
"cues": 20
},
"AEmGnEdJQfCMmCjwLyGtGA": {
"title": "Зал персональной конференции Alex Martemyanov 2026-10-09 18:51(GMT+6:00)",
@@ -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",
@@ -194,8 +194,8 @@
"note_modified_at": "2026-10-20T15:08:30.724Z",
"source_url": "https://us01mynotes.zoom.us/gBBa-iiUQLycw55WRV1tnw",
"folder": "2026-10-20 Apple Weekly Team Meeting - Zoom ID 2026-10-20 20 01(GMT+6 00) gBBa-iiUQLycw55WRV1tnw",
"sha256": "5757a175b493ba2bee769a1bcd33431e752ce73ed296d817ccf8946e60c6dbad",
"cues": 137
"sha256": "346d4bd302bfc92a437c43ddc0f16d64aa76fd67cdf88603598958c7c785ad2a",
"cues": 3
},
"7JZgnceAT1aZ2H75ok4dmA": {
"title": "Costas Brammer's Personal Meeting Room",
@@ -350,8 +350,8 @@
"note_modified_at": "2026-10-20T09:04:33.786Z",
"source_url": "https://us01mynotes.zoom.us/Mg62hl1GSI2gw4XeGvHAsg",
"folder": "2026-10-20 Dominik Kapusta's Personal Meeting Room Mg62hl1GSI2gw4XeGvHAsg",
"sha256": "be62837e60b31b10dcb7402a7696d655fc888703e8a91db94ee3e13df9dd4040",
"cues": 3
"sha256": "f5020ecd26269cc74c4c5e31200220dfd47607f197a79607112ecdd353785740",
"cues": 322
},
"QvxllpCuTTSLGEZp-R6jQw": {
"title": "Michal Smaga's Personal Meeting Room",
@@ -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": "5cf16938df6ebe0110bec8e8b4311fcbe55a764bd2bb72f64faa049ba1777d9e",
"cues": 3
"sha256": "a4b3c5ce7fafb99496019591da19f9a103e35cf5f37ec42aa8f154021fdebcae",
"cues": 133
},
"KcmYOq5_SQGPxdkdbhRx9A": {
"title": "Dominik Kapusta's Personal Meeting Room",
@@ -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."
}
]
}
@@ -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.