[2026-11-19] eagle: personal/projects/personal-os/personal-os-evidence/2026-11-19/follow-up-live-acceptance.md personal/projects/personal-os/personal-os-production-acceptance.md personal/projects/personal-os/personal-os-remediation-plan-2026-11-18.md work/zoom-transcripts/index.json work/zoom-transcripts/undated Apple Weekly Team Meeting - Zoom ID VSuzeqZCR5O2z5KtmaQt3g/transcript.json work/zoom-transcripts/undated Apple Weekly Team Meeting - Zoom ID VSuzeqZCR5O2z5KtmaQt3g/transcript.md
This commit is contained in:
1 parent
e173d071ac
commit
004c626d89
6 files changed
+14
-214
No files matched your search
@@ -146,8 +146,8 @@
|
||||
"note_modified_at": "2026-11-10T15:01:11.107Z",
|
||||
"source_url": "https://us01mynotes.zoom.us/VSuzeqZCR5O2z5KtmaQt3g",
|
||||
"folder": "undated Apple Weekly Team Meeting - Zoom ID VSuzeqZCR5O2z5KtmaQt3g",
|
||||
"sha256": "89cbb44cc7924bd9624a000cbe485052b215901139b318b32edca2b1fb3ed7ae",
|
||||
"cues": 38
|
||||
"sha256": "9b60eff9386c690f0136b636129fee6489d0e7aa6c0a62230a8500c3520999e9",
|
||||
"cues": 3
|
||||
},
|
||||
"p5FdcX9WT-afBpWjRgaW0w": {
|
||||
"title": "Dominik Kapusta's Personal Meeting Room",
|
||||
|
||||
-175
@@ -23,181 +23,6 @@
|
||||
"time": "21:03:03",
|
||||
"speaker": "SS",
|
||||
"text": "Hey, yes, um… I was recently doing some bug finding and fixing in the iOS app, uh, and had an opportunity to use the verify skill that Pete had put together for iOS. So the back… the background here is that, um. This is a skill that is used with PStack, if you remember Potato Mode. Who amongst us could forget? Uh, that is built around the concept of these verify skills, and Peter's made one for iOS that captures, like. recording of the screen, it captures, like, the pixels that were sent, like, everything you need to, like, prove that, you know, the agent has done the thing that it said it was going to do. Uh, so I used this for fixing a cr. evidence before the crash happening, after of it being fixed. It was super useful, worked great, so. Thank you, Pete."
|
||||
},
|
||||
{
|
||||
"time": "21:03:50",
|
||||
"speaker": "Jonathan Jackson",
|
||||
"text": "Awesome. Thank you. Quick reminder that our next team retro is about four weeks from now. Just keep that in mind. It's coming up. It's going to come quickly, I think, for everybody this time of year. Um… we'll go through a quick round of rotation check-ins. Uh, this week for iOS Triage is Hasan, uh, followed by PCOR and then Yasek. Mac OS triage is Alessandro this week, followed by Ann and then Sabrina. For iOS release, it looks like whoever's on this week has closed the task by accident, but I hope you know who you are and you can bring it back for us. Next week will be Pao and then Hanyu. And for macOS…"
|
||||
},
|
||||
{
|
||||
"time": "21:04:37",
|
||||
"speaker": "Pete Smith",
|
||||
"text": "Is that… sorry, Jonathan, was that iOS this week, was it?"
|
||||
},
|
||||
{
|
||||
"time": "21:04:39",
|
||||
"speaker": "Jonathan Jackson",
|
||||
"text": "Yep. iOS release this week? Yeah, is that you?"
|
||||
},
|
||||
{
|
||||
"time": "21:04:43",
|
||||
"speaker": "Pete Smith",
|
||||
"text": "Yeah, yeah, I closed it. It wasn't by accident, though. I just closed it because I have the other release tasks. But if you need it open, I can reopen."
|
||||
},
|
||||
{
|
||||
"time": "21:04:47",
|
||||
"speaker": "Jonathan Jackson",
|
||||
"text": "Oh, okay. I mean, if we don't… no, we don't necessarily need it open. If it's done, it's done, but usually they've set open for the."
|
||||
},
|
||||
{
|
||||
"time": "21:04:54",
|
||||
"speaker": "Pete Smith",
|
||||
"text": "Cool."
|
||||
},
|
||||
{
|
||||
"time": "21:04:54",
|
||||
"speaker": "Jonathan Jackson",
|
||||
"text": "Doesn't matter. Uh, the important part is that you know you're doing it, you've dealt with it, which clearly you have. Uh, and then macOS release, uh, is Joseph this week, followed by Federico, and then Juan. Also, a reminder that we're starting to coordinate the winter holiday rotations. There's a task link in the meeting notes here, and I sent that out late last week. Maybe it was even early this week, early last week. We definitely need some folks to be able to cover for others who are out. A lot of those rotations land on people's out of office time. take a peek. If you can cover one of those, even if you're not normally on that rotation, and you're… but you're willing to, that would be lovely. It would help other people have the time off that they are looking for. If we get stuck, I'll get a little more involved once it sort of has run its course on basic conversation and then see what we can do to make sure this works for everybody. Um, but for now, start with if there's something that you're… either if you're on a rotation that you can't cover, mark yourself as unavailable. Most folks have already done that, but there's a few that still need to. Or if there's one you're willing to cover through the holiday, whether you're just around during that time or you're going to be out of office, but you're still willing to cover it, mark yourself as green, and then we'll go from there about other coverage. I see a couple of folks have already volunteered to cover a couple of weeks. I appreciate that. Time sensitive topics. Andre. An update on SmartLink from you. Thank you."
|
||||
},
|
||||
{
|
||||
"time": "21:06:30",
|
||||
"speaker": "Andre Martingo",
|
||||
"text": "Yeah, just a quick follow-up on the previous update that we had. So, um, we have been running for, I think it's a second release now. Um, it showed up more mature, this one, so basically, uh, we had a lot of strings that were, uh. merge into master, so the PR for iOS and macOS are already merged. In fact, iOS, we went through already a specific flow because everything was not ready when we forked the release. So basically, we saw during this night. That was able to understand if the job was not completed and then wait for the job to be completed and pull all the strings. So we disable the danger rule in main. So basically now you can start merging untranslated stuff. and everything should work. Me and Pao, we are gonna still keep an eye to understand if something goes wrong. Uh, but for example, we already saw with Reedy, uh, another, uh, feature that we introduced, which is if you create a… If you merge into main and that job that got triggered on your commit will have some question from someone from SmartLink, it will create a task for you. So you don't need to always check if the job has any issues. proactively will create a task for you, if there is any issue. Um, so we expect everything to be much smoother, um, and basically, yeah, you can start merging, uh, English strings into mine."
|
||||
},
|
||||
{
|
||||
"time": "21:08:05",
|
||||
"speaker": "Jonathan Jackson",
|
||||
"text": "Amazing. Thank you. And the automated task creation, if it has a question, is really excellent too because it closes that loop. Very cool. Dominic. Bitrise update. We're spending seven grand a month on UI tests."
|
||||
},
|
||||
{
|
||||
"time": "21:08:25",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "Yes, thank you. On UI test on macOS 15 and 26 and 14. Which is now deleted. Um… That's what I learned. Oh. After switching to Bitrise, I kept asking Kiran about the costs of GitHub, expecting them to go down, and they went down to $7,000 a month. So I started digging, and I found out that this… Sort of… almost ideally matches the number of minutes we used on macOS 14, 15 and 26xlarge GitHub runners in October. And then, I also recalled that Bitrise rolled out an update to BuildHub pools, that they allow… when they allow to… scaling down pools to zero, essentially, so… You can create a pool of… Some machines, and if none of them is used. there are just zero machines in the pool, and it doesn't contribute to the overall capacity. So I thought, okay, I'm just gonna create pools for macOS 15 and macOS 26, and let's run UI tests in Bitrise, and it's live. As of now, it's in main, so all macOS UI tests now run on Bitrise machines, and we're aiming to remove that $7,000 a month from GitHub bill. Um, and in place of that, I'm proposing that we increase our Bitrise fleet, because we will need some more machines. in some time, especially when we start using Bitrise machines for Agentic workflows. But also, some queuing is happening already. So, I put together a very small, um… Um, proposal with a calculation. I only pinged Jonathan and Laura over there, for what it's worth. You can reach that proposal by going to that task and in a subtask. But it's essentially to just agree that we should pursue that at the very moment, because we are about to update the Bitrise deal. Jeff from Partnerships suggested that if we're… if we wanted to… if we are updating the deal at the moment, that's really to build cash, a separate thing, completely. Uh, if we're doing an amendment, we'll need legal review, we'll need some other reviews, probably, so… If we want to change something else, let's do it right now. To… to speed up the process and also save. Time and money of the legal team. So, that's that. The change for… for Apple team members is that UI tests will be… oh, there's actually one more change I forgot about. So the UI tests run on bitrise. And also… from now on, by default, UI tests will only run on macOS 27. If you want to run macOS… if you want to run macOS UI tests on older OS versions, you have to check the box. That's called all OS versions. It was previously on by default, now it's off by default. That's the change. But also, there's another news item I want to share. Alessandro is working on… an overhaul of how we trigger UI tests. So, we removed some triggers for UI tests workflows on pull requests, and in place of that, we'll be putting. UI test workflows triggered by a label on a pull request. Ale is working on that. We'll have more next week. Thank you."
|
||||
},
|
||||
{
|
||||
"time": "21:12:21",
|
||||
"speaker": "Jonathan Jackson",
|
||||
"text": "One question on the UI test side. You talked about this for macOS only. Should we think about it for iOS as well, or is there a different story there already?"
|
||||
},
|
||||
{
|
||||
"time": "21:12:29",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "It's a different story, because iOS doesn't need old OS versions, because it has simulators."
|
||||
},
|
||||
{
|
||||
"time": "21:12:36",
|
||||
"speaker": "Jonathan Jackson",
|
||||
"text": "So those are already running in the rows."
|
||||
},
|
||||
{
|
||||
"time": "21:12:36",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "It will be… Yeah, yeah."
|
||||
},
|
||||
{
|
||||
"time": "21:12:40",
|
||||
"speaker": "Jonathan Jackson",
|
||||
"text": "Okay, awesome."
|
||||
},
|
||||
{
|
||||
"time": "21:12:41",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "Thank you."
|
||||
},
|
||||
{
|
||||
"time": "21:12:44",
|
||||
"speaker": "Jonathan Jackson",
|
||||
"text": "James, you're up next."
|
||||
},
|
||||
{
|
||||
"time": "21:12:48",
|
||||
"speaker": "JF",
|
||||
"text": "Hey, um, this is just an update on something I started during the last hack days, which was… To look at automating our, uh… the pixel anomaly triage stage of our rotations, uh, initially starting with macOS, just because that's what I'm used to looking at on the rotation. I got it working reasonably well over half days, and then… When Jorge was on maintenance a few weeks ago, I manually ran it each day, um, kind of alongside him, just to see how it was going. Tuned it, made it less verbose over time. I think it's in a good place now. It's built on… There's a new GitHub Agentic workflow system that's been put in place by Lucas, which. Um, is now approved and ready to go, and it can… run on a GitHub workflow and access Asano, ClickHouse, um, you know, GitHub. info. So, basically, I feel like it's in a good place, so I'm going to enable it to run each day. Automatically, once the Pixel triage tasks are created for macOS, basically it annotates the existing description that gets put in the triage tasks. If it thinks anything needs further review, it will create a subtask and assign it to that person. Just like any of us would do if we were reviewing these things. So I'm going to enable it. We can see how it goes. I've dropped a link. In the, uh… chart both. dropped a document in the AI enablement, um… project with kind of how it works. I'll keep an eye on it as well as it runs and keep in touch with the people who are on rotations just to see what they think of it. And we can, you know, we can dial it in. But if anyone's got any, you know, questions or issues or. improvements they can suggest, then let me know. But I will turn that on shortly."
|
||||
},
|
||||
{
|
||||
"time": "21:14:54",
|
||||
"speaker": "Jonathan Jackson",
|
||||
"text": "Very cool. Thank you. I'm going to ask you the same question I asked Dominic. What about iOS?"
|
||||
},
|
||||
{
|
||||
"time": "21:14:59",
|
||||
"speaker": "JF",
|
||||
"text": "Yeah, I don't see why that should. should be an issue. It's the same kind of thing, but I just thought I'd start with one."
|
||||
},
|
||||
{
|
||||
"time": "21:15:03",
|
||||
"speaker": "Jonathan Jackson",
|
||||
"text": "Yeah, I figured. Great. Yeah, yeah, sure. I just want to make sure that you're thinking ahead, as I imagine you are."
|
||||
},
|
||||
{
|
||||
"time": "21:15:10",
|
||||
"speaker": "JF",
|
||||
"text": "Yeah."
|
||||
},
|
||||
{
|
||||
"time": "21:15:11",
|
||||
"speaker": "Jonathan Jackson",
|
||||
"text": "Um, I guess I would say when you're, you know, once you're happy with it on macOS, you could turn it on for iOS. If you need more signal, you could turn it on for both even sooner, and you'd."
|
||||
},
|
||||
{
|
||||
"time": "21:15:17",
|
||||
"speaker": "JF",
|
||||
"text": "Yeah. Sure."
|
||||
},
|
||||
{
|
||||
"time": "21:15:21",
|
||||
"speaker": "Jonathan Jackson",
|
||||
"text": "But I'll leave that up to you to decide, obviously."
|
||||
},
|
||||
{
|
||||
"time": "21:15:23",
|
||||
"speaker": "JF",
|
||||
"text": "Cool."
|
||||
},
|
||||
{
|
||||
"time": "21:15:24",
|
||||
"speaker": "Jonathan Jackson",
|
||||
"text": "Thank you. Awesome. Okay. Miha, you're next."
|
||||
},
|
||||
{
|
||||
"time": "21:15:33",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Yeah, I wanted to do a short demo, like, to give you a privilege of, like, pre-release showcase of the feature we are working on. So, as you probably know, we have already ad blocking for YouTube, and now we are working on something called, like, sponsor blocking, or skipping sponsor segments, so… Uh, there may be, uh, like, some of the videos can have the… the parts where the creator, like, advertises some kind of, like, sponsored product, and sometimes you may want to skip those, and there's no easy way, unless you use some third-party, like, web extensions. And we are trying to leverage one of the solutions, which is SponsorBlock. So this is, like, both API and both web extension, and we try to, like, integrate it into our browsers, so… Uh, in the linked task, there's, like, a step-by-step, uh, description. So, uh, the current state is that we have the MVP, which is, like, very, like, uh, bare-bones, that, uh, there's no design, there's no copy, so there are no translations, so basically this is, like, a very bare-bones version. Of the future to validate if it works and if it, like, lives up to to our expectations. And this is like for internal use only, so it won't be shipped in that form. Definitely. So, you may already have it because it's enabled by the behind the internal user feature flag in this week's internal releases. So if you go into the task. There's, uh… There's a short description of the feature. There's the required version, which is, like, this week's internal. So either you need to use TestFlight for the apps versions, or if you have the direct download on macOS, it should be already on your desktop. And basically, the future works like that, that if you open, uh… video that contains a sponsored segment. I think this one does. You will see that there's, like, a highlight in the SIG bar, which is the sponsored segment, and… If you open the settings in ad blocking, you have the additional section here for the sponsored segments, where you can toggle between the manual and the automatic mode. So the default one is the manual one, so if you go into the section here, you can see there's, like, a button. You can click it, and it goes to the end of the section, and, it plays back. In the automatic, it automatically, like, skips the segment when it's being encountered. Uh, yeah, and this is basically it, and should just work for everyone, so the goal is to have it for internal users, for the employees, be enabled by default. there will be wider announcement, uh, for… for it, uh, and probably we'll have some kind of, like, channel to gather the feedback, so keep an eye on… on that, and yeah, if you want, like, sponsored segment-free YouTube experience, you'll… Feel free to, like, use it and enjoy it. If you have any open questions, I'm… Sure. Thank you."
|
||||
},
|
||||
{
|
||||
"time": "21:18:56",
|
||||
"speaker": "Jonathan Jackson",
|
||||
"text": "Very cool, thank you. I'm definitely gonna check that one out."
|
||||
},
|
||||
{
|
||||
"time": "21:18:59",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "I see there was like a question in the chat. Yeah, Brindy asked about if the YouTubers are getting paid. Yeah, so this is like not the ads that are served by YouTube. So this is like part of the video, which is the tricky part. And, uh, like, from all the information that we were able to gather, uh, they are, like, probably paid upfront, so there's, like, external contract that they are, and there's no indication on. the video, or, like, specific segment, I'm not sure if there are, like, analytics for that, uh, that if given, like, sponsored segment was being, uh, watched. Uh, and, uh, yeah, so I don't think so, and basically the data is not extracted from YouTube, it's basically, like, from a third party, so the sponsor block is, like, the API, where… which is, like, open source, and, like. community-driven, so, like, people, like, submit the segments, uh, for the data, and yeah, we can use that."
|
||||
},
|
||||
{
|
||||
"time": "21:20:03",
|
||||
"speaker": "Jonathan Jackson",
|
||||
"text": "Cool. Thank you. Yeah, that was a good question. Uh, Brenda, your revenue stream sounds like it's safe. Um… Does anybody have anything else to add? Any questions, demos, other things you want to talk about today?"
|
||||
},
|
||||
{
|
||||
"time": "21:20:18",
|
||||
"speaker": "Jorge Leandro Perez",
|
||||
"text": "Question, do we have a meetup location defined yet, or not yet?"
|
||||
},
|
||||
{
|
||||
"time": "21:20:23",
|
||||
"speaker": "Jonathan Jackson",
|
||||
"text": "Uh, location is not defined the way… there are… the process is a little different this year, um, and John B. has taken over the… the week questionnaire, and sort of getting those weeks figured out. I think you probably have seen that. Um… I need to check back in with him now that that's happened, and figure out what next steps are in terms of location planning. He's been in touch with us a little bit, um, but that'll be, I think, probably the next step, so stay tuned."
|
||||
},
|
||||
{
|
||||
"time": "21:20:50",
|
||||
"speaker": "Jorge Leandro Perez",
|
||||
"text": "Thank you."
|
||||
},
|
||||
{
|
||||
"time": "21:20:58",
|
||||
"speaker": "Jonathan Jackson",
|
||||
"text": "Thank you. Anything else? Anybody? OK. Thank you all. It's good to see you. Have a great day."
|
||||
}
|
||||
]
|
||||
}
|
||||
-35
@@ -15,38 +15,3 @@ source: "https://us01mynotes.zoom.us/VSuzeqZCR5O2z5KtmaQt3g"
|
||||
- **21:01:48 · Jorge Leandro Perez:** I'm usually the one who can't stand the silence in elevators, so I start talking.
|
||||
- **21:01:55 · Jonathan Jackson:** I appreciate that you haven't decided to bite Muzak into our meeting, sir, so… All right. Why don't we go ahead and get started? Sam, you want to kick us off with your appreciation?
|
||||
- **21:03:03 · SS:** Hey, yes, um… I was recently doing some bug finding and fixing in the iOS app, uh, and had an opportunity to use the verify skill that Pete had put together for iOS. So the back… the background here is that, um. This is a skill that is used with PStack, if you remember Potato Mode. Who amongst us could forget? Uh, that is built around the concept of these verify skills, and Peter's made one for iOS that captures, like. recording of the screen, it captures, like, the pixels that were sent, like, everything you need to, like, prove that, you know, the agent has done the thing that it said it was going to do. Uh, so I used this for fixing a cr. evidence before the crash happening, after of it being fixed. It was super useful, worked great, so. Thank you, Pete.
|
||||
- **21:03:50 · Jonathan Jackson:** Awesome. Thank you. Quick reminder that our next team retro is about four weeks from now. Just keep that in mind. It's coming up. It's going to come quickly, I think, for everybody this time of year. Um… we'll go through a quick round of rotation check-ins. Uh, this week for iOS Triage is Hasan, uh, followed by PCOR and then Yasek. Mac OS triage is Alessandro this week, followed by Ann and then Sabrina. For iOS release, it looks like whoever's on this week has closed the task by accident, but I hope you know who you are and you can bring it back for us. Next week will be Pao and then Hanyu. And for macOS…
|
||||
- **21:04:37 · Pete Smith:** Is that… sorry, Jonathan, was that iOS this week, was it?
|
||||
- **21:04:39 · Jonathan Jackson:** Yep. iOS release this week? Yeah, is that you?
|
||||
- **21:04:43 · Pete Smith:** Yeah, yeah, I closed it. It wasn't by accident, though. I just closed it because I have the other release tasks. But if you need it open, I can reopen.
|
||||
- **21:04:47 · Jonathan Jackson:** Oh, okay. I mean, if we don't… no, we don't necessarily need it open. If it's done, it's done, but usually they've set open for the.
|
||||
- **21:04:54 · Pete Smith:** Cool.
|
||||
- **21:04:54 · Jonathan Jackson:** Doesn't matter. Uh, the important part is that you know you're doing it, you've dealt with it, which clearly you have. Uh, and then macOS release, uh, is Joseph this week, followed by Federico, and then Juan. Also, a reminder that we're starting to coordinate the winter holiday rotations. There's a task link in the meeting notes here, and I sent that out late last week. Maybe it was even early this week, early last week. We definitely need some folks to be able to cover for others who are out. A lot of those rotations land on people's out of office time. take a peek. If you can cover one of those, even if you're not normally on that rotation, and you're… but you're willing to, that would be lovely. It would help other people have the time off that they are looking for. If we get stuck, I'll get a little more involved once it sort of has run its course on basic conversation and then see what we can do to make sure this works for everybody. Um, but for now, start with if there's something that you're… either if you're on a rotation that you can't cover, mark yourself as unavailable. Most folks have already done that, but there's a few that still need to. Or if there's one you're willing to cover through the holiday, whether you're just around during that time or you're going to be out of office, but you're still willing to cover it, mark yourself as green, and then we'll go from there about other coverage. I see a couple of folks have already volunteered to cover a couple of weeks. I appreciate that. Time sensitive topics. Andre. An update on SmartLink from you. Thank you.
|
||||
- **21:06:30 · Andre Martingo:** Yeah, just a quick follow-up on the previous update that we had. So, um, we have been running for, I think it's a second release now. Um, it showed up more mature, this one, so basically, uh, we had a lot of strings that were, uh. merge into master, so the PR for iOS and macOS are already merged. In fact, iOS, we went through already a specific flow because everything was not ready when we forked the release. So basically, we saw during this night. That was able to understand if the job was not completed and then wait for the job to be completed and pull all the strings. So we disable the danger rule in main. So basically now you can start merging untranslated stuff. and everything should work. Me and Pao, we are gonna still keep an eye to understand if something goes wrong. Uh, but for example, we already saw with Reedy, uh, another, uh, feature that we introduced, which is if you create a… If you merge into main and that job that got triggered on your commit will have some question from someone from SmartLink, it will create a task for you. So you don't need to always check if the job has any issues. proactively will create a task for you, if there is any issue. Um, so we expect everything to be much smoother, um, and basically, yeah, you can start merging, uh, English strings into mine.
|
||||
- **21:08:05 · Jonathan Jackson:** Amazing. Thank you. And the automated task creation, if it has a question, is really excellent too because it closes that loop. Very cool. Dominic. Bitrise update. We're spending seven grand a month on UI tests.
|
||||
- **21:08:25 · Dominik Kapusta:** Yes, thank you. On UI test on macOS 15 and 26 and 14. Which is now deleted. Um… That's what I learned. Oh. After switching to Bitrise, I kept asking Kiran about the costs of GitHub, expecting them to go down, and they went down to $7,000 a month. So I started digging, and I found out that this… Sort of… almost ideally matches the number of minutes we used on macOS 14, 15 and 26xlarge GitHub runners in October. And then, I also recalled that Bitrise rolled out an update to BuildHub pools, that they allow… when they allow to… scaling down pools to zero, essentially, so… You can create a pool of… Some machines, and if none of them is used. there are just zero machines in the pool, and it doesn't contribute to the overall capacity. So I thought, okay, I'm just gonna create pools for macOS 15 and macOS 26, and let's run UI tests in Bitrise, and it's live. As of now, it's in main, so all macOS UI tests now run on Bitrise machines, and we're aiming to remove that $7,000 a month from GitHub bill. Um, and in place of that, I'm proposing that we increase our Bitrise fleet, because we will need some more machines. in some time, especially when we start using Bitrise machines for Agentic workflows. But also, some queuing is happening already. So, I put together a very small, um… Um, proposal with a calculation. I only pinged Jonathan and Laura over there, for what it's worth. You can reach that proposal by going to that task and in a subtask. But it's essentially to just agree that we should pursue that at the very moment, because we are about to update the Bitrise deal. Jeff from Partnerships suggested that if we're… if we wanted to… if we are updating the deal at the moment, that's really to build cash, a separate thing, completely. Uh, if we're doing an amendment, we'll need legal review, we'll need some other reviews, probably, so… If we want to change something else, let's do it right now. To… to speed up the process and also save. Time and money of the legal team. So, that's that. The change for… for Apple team members is that UI tests will be… oh, there's actually one more change I forgot about. So the UI tests run on bitrise. And also… from now on, by default, UI tests will only run on macOS 27. If you want to run macOS… if you want to run macOS UI tests on older OS versions, you have to check the box. That's called all OS versions. It was previously on by default, now it's off by default. That's the change. But also, there's another news item I want to share. Alessandro is working on… an overhaul of how we trigger UI tests. So, we removed some triggers for UI tests workflows on pull requests, and in place of that, we'll be putting. UI test workflows triggered by a label on a pull request. Ale is working on that. We'll have more next week. Thank you.
|
||||
- **21:12:21 · Jonathan Jackson:** One question on the UI test side. You talked about this for macOS only. Should we think about it for iOS as well, or is there a different story there already?
|
||||
- **21:12:29 · Dominik Kapusta:** It's a different story, because iOS doesn't need old OS versions, because it has simulators.
|
||||
- **21:12:36 · Jonathan Jackson:** So those are already running in the rows.
|
||||
- **21:12:36 · Dominik Kapusta:** It will be… Yeah, yeah.
|
||||
- **21:12:40 · Jonathan Jackson:** Okay, awesome.
|
||||
- **21:12:41 · Dominik Kapusta:** Thank you.
|
||||
- **21:12:44 · Jonathan Jackson:** James, you're up next.
|
||||
- **21:12:48 · JF:** Hey, um, this is just an update on something I started during the last hack days, which was… To look at automating our, uh… the pixel anomaly triage stage of our rotations, uh, initially starting with macOS, just because that's what I'm used to looking at on the rotation. I got it working reasonably well over half days, and then… When Jorge was on maintenance a few weeks ago, I manually ran it each day, um, kind of alongside him, just to see how it was going. Tuned it, made it less verbose over time. I think it's in a good place now. It's built on… There's a new GitHub Agentic workflow system that's been put in place by Lucas, which. Um, is now approved and ready to go, and it can… run on a GitHub workflow and access Asano, ClickHouse, um, you know, GitHub. info. So, basically, I feel like it's in a good place, so I'm going to enable it to run each day. Automatically, once the Pixel triage tasks are created for macOS, basically it annotates the existing description that gets put in the triage tasks. If it thinks anything needs further review, it will create a subtask and assign it to that person. Just like any of us would do if we were reviewing these things. So I'm going to enable it. We can see how it goes. I've dropped a link. In the, uh… chart both. dropped a document in the AI enablement, um… project with kind of how it works. I'll keep an eye on it as well as it runs and keep in touch with the people who are on rotations just to see what they think of it. And we can, you know, we can dial it in. But if anyone's got any, you know, questions or issues or. improvements they can suggest, then let me know. But I will turn that on shortly.
|
||||
- **21:14:54 · Jonathan Jackson:** Very cool. Thank you. I'm going to ask you the same question I asked Dominic. What about iOS?
|
||||
- **21:14:59 · JF:** Yeah, I don't see why that should. should be an issue. It's the same kind of thing, but I just thought I'd start with one.
|
||||
- **21:15:03 · Jonathan Jackson:** Yeah, I figured. Great. Yeah, yeah, sure. I just want to make sure that you're thinking ahead, as I imagine you are.
|
||||
- **21:15:10 · JF:** Yeah.
|
||||
- **21:15:11 · Jonathan Jackson:** Um, I guess I would say when you're, you know, once you're happy with it on macOS, you could turn it on for iOS. If you need more signal, you could turn it on for both even sooner, and you'd.
|
||||
- **21:15:17 · JF:** Yeah. Sure.
|
||||
- **21:15:21 · Jonathan Jackson:** But I'll leave that up to you to decide, obviously.
|
||||
- **21:15:23 · JF:** Cool.
|
||||
- **21:15:24 · Jonathan Jackson:** Thank you. Awesome. Okay. Miha, you're next.
|
||||
- **21:15:33 · Michal Smaga:** Yeah, I wanted to do a short demo, like, to give you a privilege of, like, pre-release showcase of the feature we are working on. So, as you probably know, we have already ad blocking for YouTube, and now we are working on something called, like, sponsor blocking, or skipping sponsor segments, so… Uh, there may be, uh, like, some of the videos can have the… the parts where the creator, like, advertises some kind of, like, sponsored product, and sometimes you may want to skip those, and there's no easy way, unless you use some third-party, like, web extensions. And we are trying to leverage one of the solutions, which is SponsorBlock. So this is, like, both API and both web extension, and we try to, like, integrate it into our browsers, so… Uh, in the linked task, there's, like, a step-by-step, uh, description. So, uh, the current state is that we have the MVP, which is, like, very, like, uh, bare-bones, that, uh, there's no design, there's no copy, so there are no translations, so basically this is, like, a very bare-bones version. Of the future to validate if it works and if it, like, lives up to to our expectations. And this is like for internal use only, so it won't be shipped in that form. Definitely. So, you may already have it because it's enabled by the behind the internal user feature flag in this week's internal releases. So if you go into the task. There's, uh… There's a short description of the feature. There's the required version, which is, like, this week's internal. So either you need to use TestFlight for the apps versions, or if you have the direct download on macOS, it should be already on your desktop. And basically, the future works like that, that if you open, uh… video that contains a sponsored segment. I think this one does. You will see that there's, like, a highlight in the SIG bar, which is the sponsored segment, and… If you open the settings in ad blocking, you have the additional section here for the sponsored segments, where you can toggle between the manual and the automatic mode. So the default one is the manual one, so if you go into the section here, you can see there's, like, a button. You can click it, and it goes to the end of the section, and, it plays back. In the automatic, it automatically, like, skips the segment when it's being encountered. Uh, yeah, and this is basically it, and should just work for everyone, so the goal is to have it for internal users, for the employees, be enabled by default. there will be wider announcement, uh, for… for it, uh, and probably we'll have some kind of, like, channel to gather the feedback, so keep an eye on… on that, and yeah, if you want, like, sponsored segment-free YouTube experience, you'll… Feel free to, like, use it and enjoy it. If you have any open questions, I'm… Sure. Thank you.
|
||||
- **21:18:56 · Jonathan Jackson:** Very cool, thank you. I'm definitely gonna check that one out.
|
||||
- **21:18:59 · Michal Smaga:** I see there was like a question in the chat. Yeah, Brindy asked about if the YouTubers are getting paid. Yeah, so this is like not the ads that are served by YouTube. So this is like part of the video, which is the tricky part. And, uh, like, from all the information that we were able to gather, uh, they are, like, probably paid upfront, so there's, like, external contract that they are, and there's no indication on. the video, or, like, specific segment, I'm not sure if there are, like, analytics for that, uh, that if given, like, sponsored segment was being, uh, watched. Uh, and, uh, yeah, so I don't think so, and basically the data is not extracted from YouTube, it's basically, like, from a third party, so the sponsor block is, like, the API, where… which is, like, open source, and, like. community-driven, so, like, people, like, submit the segments, uh, for the data, and yeah, we can use that.
|
||||
- **21:20:03 · Jonathan Jackson:** Cool. Thank you. Yeah, that was a good question. Uh, Brenda, your revenue stream sounds like it's safe. Um… Does anybody have anything else to add? Any questions, demos, other things you want to talk about today?
|
||||
- **21:20:18 · Jorge Leandro Perez:** Question, do we have a meetup location defined yet, or not yet?
|
||||
- **21:20:23 · Jonathan Jackson:** Uh, location is not defined the way… there are… the process is a little different this year, um, and John B. has taken over the… the week questionnaire, and sort of getting those weeks figured out. I think you probably have seen that. Um… I need to check back in with him now that that's happened, and figure out what next steps are in terms of location planning. He's been in touch with us a little bit, um, but that'll be, I think, probably the next step, so stay tuned.
|
||||
- **21:20:50 · Jorge Leandro Perez:** Thank you.
|
||||
- **21:20:58 · Jonathan Jackson:** Thank you. Anything else? Anybody? OK. Thank you all. It's good to see you. Have a great day.
|
||||
Reference in new issue
Block a user