Kim Ebert: Today's meeting cancelled.
Charles Lanahan: I was wondering that myself.
Jakub Koci: yeah, I'm just writing them almost like, if if it's happening today. So let's see.
Timo Glastra: good afternoon, everyone.
Timo Glastra: Can you hear me?
Warren Gallagher: Yes, I can. Hello!
Timo Glastra: Hello!
Timo Glastra: I'm sorry.
Timo Glastra: Forgot about the time completely.
Timo Glastra: I was working on the afgh, and very deep, deeply focused.
Timo Glastra: We could be making an agenda, and then we can get started right away.
Timo Glastra: All right.
Timo Glastra: That's good. Start. long number on today are some Javascript for group call of July 20 need to remind you to remember the hypothesis of Connect and the trust policy.
Timo Glastra: if you would like to add yourself to the tennis list. Feel free to do so. but it's like in the chat. so
Timo Glastra: yeah, any status updates from the we had a called 2 weeks ago.
any status updates you would like to share?
Warren Gallagher: There was a an Aries working group call yesterday and
Warren Gallagher: the discussion mostly focused around. some work that's been done on marketing copy
Warren Gallagher: and the results of a survey that we're informing that marketing copy So when there were links in the
Warren Gallagher: in the meeting notes to the survey results and to that marketing copy proposal. So if anybody wants to go and look at those
Warren Gallagher: they're available. I think the intent is to make apply
Warren Gallagher: the changes to the main wiki sooner rather than later, and then iterate on it as necessary to try and get some of the benefit of the rework. That's been done.
Warren Gallagher: That's number one. And there was also a presentation given
Warren Gallagher: on Aries Vcx.
Warren Gallagher: which is a a library written in rust that uses a whole bunch of the other rust libraries to provide a bunch of the areas functionality?
Warren Gallagher: the intent is not to provide a a complete batteries included agent, but rather all of the stuff that you would need to construct one, or a wallet or something else.
Warren Gallagher: Looks like they've made good progress. And there's work underway at the moment to integrate support for Mozilla's Fi project to
Warren Gallagher: export or describe all of the rest bindings to their primary api, so that they can be made available in other languages.
Timo Glastra: And that's using unify or
Warren Gallagher: yes, I believe so.
Timo Glastra: Okay. cool. Thank you.
Timo Glastra: Any other updates.
Kim Ebert: the low testing framework.
Kim Ebert: with, on, that's under the Aries Mediator Service.
Kim Ebert: we recently use that to test over 12,000 users simultaneously.
Timo Glastra: Cool.
Timo Glastra: That's the soccer talk, right?
Kim Ebert: No, that's the load testing underneath the area's we need your service. I'll drop a link in the chat.
Timo Glastra: Okay.
Timo Glastra: okay? And this is a a test you have run to to test mediator load, and you had 12,000 concurrent open sessions. Or.
Kim Ebert: yeah, so this is it can be used more than just a testing mediation. that has some other tests inside of it, such as issuance.
Kim Ebert: we're also working on adding verification workflow to it as well
Timo Glastra: cool.
Kim Ebert: it uses Aj as the client uses a logist as the orchestrator
Timo Glastra: cool. And so the difference with like the
Timo Glastra: the era slow generator is that this is, one is fully focused on mediation.
Kim Ebert: No?
Timo Glastra: Oh.
Kim Ebert: it started off with just mediation. we've added issuance into it. We're working on verification flow right now.
Timo Glastra: Okay? And and do you know how it's comparison to the eras load generator?
Kim Ebert: the Aries load generator. My understanding is that it starts up all of the services the concept here with the area's mediator services, it's focused on
Kim Ebert: that being a client to an existing infrastructure.
Kim Ebert: right now the issuance and verification flows focused on an act by Api end. But I'm sure it could be modified to use
Kim Ebert: any other issue or or verifier as long as the endpoints updated.
Kim Ebert: because it will contact the issuer and verifier Api endpoints to
Kim Ebert: request the connection and request the issue. Answer verification.
Warren Gallagher: So so this is intended to be able to point at some areas infrastructure to be able to determine what its own characteristics are as opposed to
Warren Gallagher: the load generator which sparks up its own infrastructure. And it's primarily, I guess, to test
Warren Gallagher: that things don't tip over.
Warren Gallagher: I guess that would be the primary difference in the approach.
Kim Ebert: Yeah, the goals to test the structure. That's a existing
Warren Gallagher: good
Timo Glastra: sounds interesting.
Timo Glastra: Cool any other set of updates.
Timo Glastra: All right, I think we can get to that general
Timo Glastra: are there specific topics? People would like to discuss on the agenda today. last time we went through. a lot of the pull requests.
Timo Glastra: and
Timo Glastra: so yeah, are some of the topics people would like to discuss. Otherwise we could maybe do also a quick, quick tour around to the 2 requests again. yeah.
Timo Glastra: all right.
Timo Glastra: let's do that. I'm not sure if there's a lot of progress being made in a lot of people. Also.
Warren Gallagher: maybe it's covered in the in the pull requests, chemo. But I would be interested in knowing where
Warren Gallagher: the work is in terms of supporting the
Warren Gallagher: newest versions of like expo and react native and dependencies in the like.
Timo Glastra: Yeah. And so
Timo Glastra: it was. Do you mean expo 49 then, or
Timo Glastra: Warren. Do you mean like the latest like expo 49, or what are its meaning? Specifically.
Warren Gallagher: I believe so. I think there was work intended to be done to get
Warren Gallagher: like beyond react native 68 or 69. And
Warren Gallagher: and the related expo versions I don't recall the exact version numbers. But
Timo Glastra: okay, yeah. So that work is is completed. and
Timo Glastra: So we haven't tested with the the latest expo version. But that came out like, I think, 2 weeks ago, or something. but I don't expect too many issues. but we have tested it with like we got it working with the latest versions, and Barrett did some very complex
Timo Glastra: stuff to make If we go to the. for example, the adequate for us. repo
Timo Glastra: so react native.
Timo Glastra: It was mostly with android, I think. Yeah. So as you can see, there is now a custom logic for different direct native versions. and as you can see, it works like we have tested it up to 0
Timo Glastra: top 71 we haven't tested it with
Timo Glastra: with 0 72. But that's also just came out. So I think it it. It should all just work out of the box and and everything with auto-linking and with an export project. So if you would like to have an example, is the
Timo Glastra: paradigm wallet repo, which has an
Timo Glastra: exco app in here, and that uses Let me see.
Timo Glastra: it uses react native 0 dot 71. It uses the latest areas as far release. And it uses a for 0 without like native code. So I think this this you can use this as an example. If you're looking for how to set that up.
Timo Glastra: Does that answer your question? Or
Warren Gallagher: yes, that's great. Thank you.
Timo Glastra: Perfect. Yeah. So, and we need to.
Timo Glastra: Yeah, add some more documentation exactly on how to set it up. But it it should all work
Timo Glastra: cool.
Timo Glastra: so any Pr people would like to discuss. I haven't had a lot of time to to look at. Pr. So we discussed last time. There are some reviews I need to
Timo Glastra: me to leave
Timo Glastra: any Pr people would like to discuss.
Timo Glastra: All right.
Timo Glastra: maybe. Then there are some issues we can maybe get some consensus on one is that started in another pr, for some updating of the samples. But it's currently like with the
Timo Glastra: the rappers that only work in
Timo Glastra: we have native or like only a note 80. But we also support. Note 16, and it ups a lot of complexity. Is that we
Timo Glastra: make the rappers only support. Note 18. Because they basically already do we? add to pets? Pipes. Rep not be to those wrapper. So you don't have to do the custom resolutions anymore. And we update A of J to only support. Note 18. And we drop support for note 16, which is a bit ahead of the end of life, which is in September. But I think it would make the setup a lot easier and and improve performance. So
Timo Glastra: I'm curious if people are.
Timo Glastra: if someone is like against dropping support for node 16. So this will be
Timo Glastra: in 0 point 5 because like, it would be a break and change. So 0 point 4 will
Timo Glastra: keep support for note 60,
Timo Glastra: then for
Denver Naicker: item, I was only successful in launching the Aries Workshop, Demo and A, as well as running through the tutorials of hyper ledger areas. Javascript.
Denver Naicker: By using Node 16 on Linux and Wwsl to windows. Linux. I tried Node 18, and it gave me a lot of errors.
Denver Naicker: so I'm not for doing away support for node 16,
Denver Naicker: partly because of a lot of troubleshooting and blockages that are experienced.
Timo Glastra: Okay, so
Timo Glastra: did. Have you opened an issue for that? Or
Denver Naicker: I have not, because I was successful with getting it running on. Note 16. I can't log in issues for no to 18. Then.
Timo Glastra: Yeah, if you could do that, because usually what we do is when a note version reaches end of life, we will remove support for it.
Timo Glastra: either way, so that would be in September, which is like not that much in the future. So if we can get that addressed that would be great. There are like. There may be some issues with the the Linux sub shell on windows where it's not working. Are you running it with in the SDK, or with
Denver Naicker: So I just Npm installed based on the tutorials based on the documentation.
Denver Naicker: And that didn't work.
Denver Naicker: So it it was just using the. There is Javascript online documentation. there was no mention for Indiosk or prerequisite.
Timo Glastra: Okay, so are you still on 0 dot 3.
Denver Naicker: I'm I'm I I downloaded the 0 point 4 0 Repository, and I the workshop Demo, the one that was hosted last week, and I ran that successfully.
Denver Naicker: but I think the older tutorials might be 0 point 3.
Denver Naicker: I don't think it's 0 it. It was the latest, actually, because
Denver Naicker: it's based on the documentation online.
Timo Glastra: Okay? Yeah. n, then I think you're you're using the latest, especially if you also followed it from the workshop. So yeah, then please open an issue, and then we'll take a look, and then we'll make sure that that is resolved before we remove support for
Timo Glastra: before we drop support for node. 16
Timo Glastra: it's called windows sub shell for Linux, or something. Right?
Denver Naicker: Yeah, that was Wsl to.
Denver Naicker: Yes, it's
Timo Glastra: okay.
Timo Glastra: what's your use? Name on Github
Denver Naicker: Dnaiker. 86. DNA, I. C
Denver Naicker: DNA, it's
Timo Glastra: Can you post in chat?
Denver Naicker: Yes. Okay.
Timo Glastra: Okay. Any other concerns with dropping support for node. 16.
Timo Glastra: Okay.
Timo Glastra: okay.
Timo Glastra: perfect.
Timo Glastra: okay.
Timo Glastra: There was.
Warren Gallagher: So I just have one other comment, I guess, which is
Warren Gallagher: Do we know whether this will create a problem for
Warren Gallagher: the bifold for folks who are
Warren Gallagher: primary cause, all actually, they, they're not using the node version. Anyways, right? They're using react native. So I guess it doesn't apply.
Timo Glastra: no, so it doesn't apply. I think
Timo Glastra: we no, we I think we just. We need to make sure that we set the engine version on on the the at our framework. Slash notes package, and then it shouldn't be an issue.
Warren Gallagher: Perfect.
Timo Glastra: all right. There was also a discussion on
Timo Glastra: breaking out to Demo.
Timo Glastra: I think.
Timo Glastra: yeah, this I I just need to comment on like something. But I think it's not controversial.
Timo Glastra: are there
Timo Glastra: any other issues people would like to discuss, or would like to work on address that we need to discuss?
Timo Glastra: I see there is
Timo Glastra: a didn't qualify. Did migration update? This is something that's being discussed in the
Timo Glastra: the errors working group calls to be able to migrate from legacy dates to
Timo Glastra: qualified dates. we already have a customer implementation that goes from
Timo Glastra: didn't qualify to get pier one days.
Timo Glastra: and I think with this, with this we just have to update all the in
Timo Glastra: all the did pier. One dits. We have migrated from the unqualified D to now get pier 2, and this pier 3 ditch We did store all the Still the legacy did did the commence, so would be a migration
Timo Glastra: a script that we have to write. I think we can get that into
Timo Glastra: 0 5 0. that does raise the question on whether we should change the default, it bare. No, I go. That is used for creating connections. So currently.
Timo Glastra: we
Timo Glastra: in the data exchange protocol, we use this pair one because for data exchange, you need to attach the date documents to
Timo Glastra: to the did exchange message and then sign that a problem is with the pair. To do that you don't necessarily have a did document because you resolved it based on the
Timo Glastra: You resolve it based on the the date itself. So and I think we had race started this discussion in the As working group call. But we never came to a very concrete
Timo Glastra: decision.
Timo Glastra: how do you handle it? If you don't have to do documents, you you attach the did document either way, so like just to resolve the document and and sign that So
Timo Glastra: yeah,
Timo Glastra: should we
Timo Glastra: change the default? That pair methods? If you add this? Or are we going to use? Did pier one for did exchange and
Timo Glastra: migrate all the legacy? dates to? Did pair to slash 3? Does anyone have no being on this.
Warren Gallagher: I guess there would be a need to have agreement across the Aries projects.
Warren Gallagher: in terms of did it? You know the
Warren Gallagher: did exchange right.
Warren Gallagher: I don't know. It's a a decision we can make in isolation. So
Warren Gallagher: I'm not sure that I have an opinion on it. But it is still on the agenda within the areas working group. And so if we need like, it sounds like it's
Warren Gallagher: getting time to get serious about finalizing that stuff. So maybe you can raise it higher
Warren Gallagher: priority on the agenda for the next meeting.
Timo Glastra: Yeah. So I I think the one thing
Timo Glastra: that isn't currently talked about, and that's the like. The the did exchange protocol. not having very clearly defined how to use non.
Timo Glastra: did pier one date. So whether it's public dates or like dates that you can't move based on the or they documents that you can resolve based on the debt.
Timo Glastra: I think there is maybe
Timo Glastra: an issue open in ours. Rfc, and there is the let me see.
Timo Glastra: yeah, there is a
Timo Glastra: legacy that this one? Yeah.
Timo Glastra: so this repo is there. I think the idea is now to migrate this
Timo Glastra: transformation script.
Timo Glastra: to go from like a legacy date to a did pair 2. And I think, Steve, and added support for it. Pair 3 so I think with that
Timo Glastra: we are
Timo Glastra: mostly there in having the yeah, the the
Timo Glastra: the process to find.
Warren Gallagher: So I guess that then comes down to
Warren Gallagher: Do we want to go with the most recent stack?
Warren Gallagher: Or
Warren Gallagher: do we want to go with something that might achieve wider compatibility with folks who haven't gone there yet?
Warren Gallagher: I don't know.
Timo Glastra: Yeah,
Timo Glastra: so I think what they are suggesting. Also in the committee coordinated updates,
Timo Glastra: is that
Timo Glastra: you need to support?
Timo Glastra: Let me see. Yeah, I think, because it's a community recorded update, there will be quite a long period.
Timo Glastra: the process where.
Timo Glastra: let me see, you work to step in one step. One is.
Timo Glastra: So I think, what is Step one here? I think it's to support.
Timo Glastra: Huh?
Timo Glastra: this is, here's the
Timo Glastra: okay. So we need to
Timo Glastra: Agent Bill must update all agent code bases and deployments to accept in all in qualified and new forms.
Timo Glastra: during this step
it must continue to be in qualified
Timo Glastra: it's in all cases.
Timo Glastra: Yeah. So what I'm
Timo Glastra: uncertain about
Timo Glastra: is
Timo Glastra: that it says it should that
Timo Glastra: 18 builders must update all agent code base in deployment to use only fully qualified dates. Now, communication. And does that also include the connection protocol? Because in that case,
Timo Glastra: it probably gonna be very complex, because, like it has been implemented a few years ago, like, it's fairly, it's using old
Timo Glastra: way of structuring. And they documents. Well, that pair 2 uses a new one. So currently, how we implemented in A Ofj is we use just to unqualified exchange, and then internally, we translate it into a qualified identifier and use that
Timo Glastra: Well, I think this is just in
Timo Glastra: to
Timo Glastra: oh, use the pair to, or did your tree everywhere, even in creating a connection. For example,
Timo Glastra: do. Is anyone involved in in the discussion share and know more about this? Or
Warren Gallagher: I've only been peripherally involved? And so I don't feel equipped to
Warren Gallagher: like, make any definitive statements about this. this seems to have been driven more by Stephen Kerr and Sam.
Timo Glastra: Okay.
Timo Glastra: I'll leave a comment on this pr, with these questions, then but then, yeah, it should be quite easy for us to to
Timo Glastra: follow whatever is is described here. and and get that implemented while still supporting the
Timo Glastra: The old ways of doing things without breaking backwards compatibility.
Timo Glastra: because I don't think we should. It's like.
Timo Glastra: I don't think it's
Timo Glastra: like, if we do this like updating everything to use. Only fully qualified. D, it means we're gonna break so much backwards compatibility with all implementations that have been made over the years and maybe are not gonna adopt this So it would be good if we can have a bit more of a like
Timo Glastra: gradual. if you
Timo Glastra: to support qualified, let's do that. Otherwise. we'll keep using the the and qualified ones. directly.
Timo Glastra: Okay.
Timo Glastra: are there any other
Timo Glastra: future issues people would like to to discuss here? Or
Timo Glastra: right?
Timo Glastra: Okay, then I think we can just
Timo Glastra: got the meeting short for today. and we can.
Timo Glastra: yeah, continue with work on the Prs and and issues.
Timo Glastra: one thing. I do want to. Highlight is.
Timo Glastra: I see your unmute yako, do you want to say something? Or.
Jakub Koci: Yeah, yeah, yeah, a good catch. I just wanted to rise. My hand, not the yeah, yeah, you you are. First. yeah. I have a question.
Jakub Koci: We don't have to discuss it now. But about it, it's it's about the migration to the Afj, like like 2 new libraries Afskar or media, or an ongrad.
Jakub Koci: Is there any any documentation about that and a ma
Jakub Koci: any description about about some pain points, or or like a tricky part which we should be aware of.
Timo Glastra: So there is the migrating from 0 to 3 to 0 4
Timo Glastra: which introduced to break and change this. And there.
Timo Glastra: Listen. It's migrating from India to gay wallet to
Timo Glastra: so
Timo Glastra: That's there. One thing that we haven't documented very well is the migration from
Timo Glastra: in the SDK to in the vdr or in the SDK to an of credits or s, so like the changes in the Api are
Timo Glastra: covert here, so like that you now have to register on them credits module, but they should see. This still uses the in the SDK module here. But there is
Timo Glastra: in the agent setup. It does define like, okay, how do you use the the In the Cdr module and configure it with different lectures?
Timo Glastra: so that's the documentation, there is
Timo Glastra: but no specific like these are pain points or something, to be aware of
Jakub Koci: okay, yeah, sounds good sounds good
Jakub Koci: I'm just thinking, I I I I know that the actually I asked the Oh, Baron, the or like Ariel on the on their presentation about Aj for version 0 for 0 point 4
Jakub Koci: about this. And
Jakub Koci: my question was, Will.
Jakub Koci: If like. if if we should migrate everything at once, or if there is a specific process.
Jakub Koci: if if there is better, if there is some some process which might be better.
Jakub Koci: And what I mean is that we we have like 0 point 3 right now with in the SDK, right? So now it's a question like
Jakub Koci: I. I remember that
Jakub Koci: it should be maybe better to do everything at once. but
Jakub Koci: I think that he also mentioned some, that there were some issues, probably with some part. But I'm I don't remember that the that? What? What exactly I mentioned? Do you have a do you have an a do you know anything about that? Or
Timo Glastra: I think, we have done mostly everything at once. Also what we did in the by fault and some other projects. We are just doing it all at once, because we would like to get rid of the in the SDK as soon as possible.
Timo Glastra: But you can do it in 2 steps like you could do first upgrade 204 and use the in the SDK still. And then at another point, you could do the upgrade to Eras Offscar, for example, when 0 5 releases, or whenever you're ready for it. So it are 2 separate migrations you can do. We have just chosen to do it at once. if you don't have
Timo Glastra: in the SDK wallet to migrate Jet, so haven't released your wallet to the stores. For example, I would definitely recommend to do it all at once, because then you don't have to do the Indians K to Oscar migration, because that does require like we have do this in the
Timo Glastra: in the Bible products. And it does require you to have like an custom package you need to on every agent started. Basically, you need to do a check like, okay, while I previously, and in the SDK wallet? If so, I now need to migrate it and and do that to an Oscar structure, because, like the database is completely different. So we really have like to
Timo Glastra: make a connection to the postcres. Database create new tables, move to structure, decrypt everything, re-encrypt. So like, if you can get away with not having this package.
Jakub Koci: Yeah, I would say, sure to it all at once. Yeah, in our case, we have it already out there. So it's it's already in. We we already. We already did the migration from the Vcx. like library to have, just as you know. But there was also not only it was also not only about like frameworks, but also our data. So we are in this migration to in the SDK,
Jakub Koci: yeah. And now it seems that we will have to do this migration with with those libraries. But I I think it's great that there, if there is some
Jakub Koci: let's call it script right to to do this migration. yeah, that's that's definitely great. So I I hope that it should be fine.
Timo Glastra: Yeah, it's not that complex. I can send you the
Timo Glastra: I think it's the the implementation from the by folks.
Timo Glastra: let me see. yeah. So
Timo Glastra: basically, this
Timo Glastra: is it. where it checks, is it? migrated to ascar? And if not, there is a custom
Timo Glastra: method implementation here. That's
Timo Glastra: calls this in the SDK to ask our migration update.
Jakub Koci: Okay, cool. Cool. That's great. Thanks.
Timo Glastra: Marvin.
Warren Gallagher: Yeah, I I seem to recall so so 2 things. One. Another thing that came up in the Aries call yesterday is that Steven current is pushing towards officially deprecating in the SDK.
Warren Gallagher: and they'd like to do it sooner rather than later, and so is is trying to rally everybody to to do that. So just as a point of interest is that he wants to move, and the SDK to
Warren Gallagher: archived state as soon as possible. so I don't know whether that goes into your decision about your migration path and the and the like. Just so, you know that's
Warren Gallagher: happening. And if you have concerns with that. Then you should chime in and get in touch with Steven, and you know, let him know what your concerns are.
Warren Gallagher: And the other thing. The only thing I seem to recall as being an issue, and it may have been resolved, but with the migration was, if with Afj, and as far as if you were using multi tenant.
Warren Gallagher: I think there was that that's not supported in the current migration. But I might be incorrect about that. So I just wanted to bring that up as a question in case that's something that is German in here.
Timo Glastra: Yeah, it it.
Timo Glastra: It isn't in command of jets like we need to do proper migrations for multi. Tennessee needs to be implemented. Still, anyway, it is something we are going to implement because we are using multi-tenancy with a in 0 for 0. we haven't written the migration for multi tenancy, and no just completely yet, for Uscar is because we don't know anyone that is using
Timo Glastra: it's a multi-tenancy in production. And so
Timo Glastra: I added, to like the
Timo Glastra: the dogs and everything. There are some warnings in like, Hey, multi, tenancy is not supported. if you need it, please open an issue. But I don't. Didn't want to go through all the trouble and complexity if nobody is ever going to need it.
Timo Glastra: yeah. So if you are using multi, Tennessee are on 0 3 within the SDK, and you are in prediction and need to migrate it to
Timo Glastra: us guard, and please open an issue, and then we can look at getting that implemented But, for example, we have mediators running with in the SDK in 0 3, and we have successfully migrated those to 0 for and updating indie to uscar so for that use case yeah, it. It works fine. But yeah, you're right. That that is
Timo Glastra: not implemented that.
Timo Glastra: okay?
Timo Glastra: Or the deprecating the in the Fk, yeah, it might be a good one to discuss. also.
Timo Glastra: I'm in favor of it. I think it adds complexity to this project to also have to support it.
Timo Glastra: And the installation is like very cumbersome. also for newcomers.
Timo Glastra: so
Timo Glastra: yeah, I'm I'm totally on board with deprecating the in the SDK. Maybe what we
Timo Glastra: to do is already start adding notes to like we have for we have in the like experimental modules. We have warnings like, Hey, this is experimental. Maybe we could also start adding, like, Hey, this is going to be deprecated. looks warning looks, and then maybe
Timo Glastra: we say we remove support, for
Timo Glastra: in the SDK in either
Timo Glastra: zero-five. But maybe we should set it for 0 6 release, so people can still do one more upgrade within the SDK to 0 5. But then in zeros dot 6, we will remove support for the in the SDK and
Timo Glastra: if people are really interested in keeping support for it, then that would still be possible, because, like, it's currently there's no logic in core to support in the SDK. But I would then suggest that from 0 6 onwards we remove it out of the the, the errors from a Javascript repository, and there could be, like a custom maintained implementation outside of it, if you really need in the sk But then yeah, I think that would provide the
Timo Glastra: clear migration that I can.
Kim Ebert: Yeah, If you have a clear migration path here, it'd be good to let Steven know kind of the timeline.
Kim Ebert: because one of the things that came up was removing some of the build artifacts from the repositories to encourage no longer using in the SDK, and so having a timeline on that would be helpful for
Kim Ebert: Steven to know what a good time would be to remove those build artifacts from various repositories.
Timo Glastra: Yeah. And so built artifacts. Because I think we're moving built out of fox can mean that current deployments can break. Is that something we want?
Timo Glastra: I think my my
Timo Glastra: prefer to approach would more likely be to like not update it anymore. So if you have, like an older
Timo Glastra: deployment, it doesn't suddenly
Timo Glastra: break
Kim Ebert: the concern there is
Kim Ebert: deploying artifacts that aren't maintained anymore.
Kim Ebert: so if there's security holds or things like that. And so at some point. having the
Kim Ebert: artifacts deployed out, there can be more of a liability than they are a benefit to anyone.
Timo Glastra: Yeah, that makes sense.
Warren Gallagher: I think the the the thing that would require some communication with Steven, then, is
Warren Gallagher: about a a prospective plan. for you know you you mentioned, perhaps you know, deprecated putting in deprecation warnings and removing support in 0 5 0, or maybe in 0 6 0. And so if we have an idea of
Warren Gallagher: you know what
Warren Gallagher: what you would desire to do there, and what the timelines are, you know, at at best, guess at that point for this release, then, that could inform
Warren Gallagher: some of the other stuff that that Steven and others are doing to try and wrangle the in the SDK to the ground. Just make sure we're coordinated on that stuff.
Timo Glastra: Yeah.
Timo Glastra: yeah, it makes sense.
Timo Glastra: Are people, any people here that are using any sk and don't intend to upgrade to
Timo Glastra: Iscar and related libraries for 0 5 or even 0 6.
Timo Glastra: Okay, well, that's a positive, at least.
Timo Glastra: okay.
Timo Glastra: cool Then, final note is, I think I also mentioned this last time. already, I'm not 100% sure, because it's 2 weeks ago already, and notification in between. So I but all my memory from before
Timo Glastra: but that we wanted to switch hosting the A Ofj call to being bi weekly because there is like with current things that are happening. I think having a by weekly call would be good enough.
Timo Glastra: And if there well. in the
Timo Glastra: so much to discuss that we can do it in in the the buy would be called, and we can always go back to having weekly calls. But I think a lot of this stuff can also be picked up in issues and full requests.
Timo Glastra: any people
Timo Glastra: against that here today that's that would like to keep it at a weekly call. People that are
Timo Glastra: agreeing of the bi-weekly call or have any opinions notes on this?
Jakub Koci: I I think it definitely makes sense during the summer occasions. Right? maybe. Let's see again on
Jakub Koci: in September or in autumn and the the so does it mean that we would skip next week and do it in a 2 weeks again.
Jakub Koci: another call would be like, in 2 weeks from now.
Timo Glastra: Yeah, exactly.
Jakub Koci: Okay. Good.
Timo Glastra: Okay. I I think. oh, yeah, correct.
Denver Naicker: Sorry, Tim, I I I just. This is my first meeting.
Denver Naicker: and I thoroughly enjoyed it. There's a lot of insights.
Denver Naicker: and I'll I'm a bit sad, and if it goes to sort of
Denver Naicker: further away, further away from, you know the consistency by weekly, is it? Every 2 2 times a week, or then twice every second week.
Timo Glastra: Yeah. So it would be once every 2 weeks, 2 times a month. Basically.
Denver Naicker: Okay. cause I I've been away. I haven't. I also desperately looking to be more involved in the community. And this is my first meeting, and I, you know, thoroughly enjoyed it. So
Denver Naicker: it'll be with T on my clock.
Timo Glastra: Okay.
Timo Glastra: no, that's good to know. I think. Yeah.
Timo Glastra: I we have done it like for weekly, I think for really long time already. I think it at first was bi weekly. I just think with the conversations we have lately. maybe it's something for the summer months. And then we can always reconsider it after the summer months. or if there are enough topics to do it weekly.
Timo Glastra: That would also be fine by me. But I think
Timo Glastra: we can also. yeah, we should have probably some more like we have in the past that that's a bit like doing alternating weeks of having a maintainer and a
Timo Glastra: users call, basically where one week will be really focused on in-depth. discussions on the implementation. The other one would be more focused on.
Timo Glastra: the on the user side of things having people give presentations.
Timo Glastra: what have they built with Asj? What can you do with it? And more from a user perspective? and I notes that I haven't had a lot of time
Timo Glastra: lately to prepare well for the working group calls. And I think that's also one of the reasons why I would like to move it more to a by weekly call.
Timo Glastra: Because, yeah, having people to present on these things with presentations and everything. I think that helps in making it more.
Timo Glastra: So a a better working group call I have also discussed a bit with
Timo Glastra: yeah, Koop and Aliel and cream and parent and asks to maybe do it a bit more in alternating fashion where we host the working group calls I think that that could maybe also help a bit.
Timo Glastra: but yeah, I'll definitely take it into account.
Timo Glastra: I would like to propose for now to at least for the summer. Do it by weekly. And then, as Jack upset after the summer, we can reconsider to to see like, okay, what's the interest? And do we want to make it
Timo Glastra: weekly or by weekly.
Timo Glastra: yeah. And so if you have topics, you would like to
Timo Glastra: present and or talk about on on the desk call presentation or something like that. also, please
Timo Glastra: raise that to us. and then we can have those on the working group calls
Timo Glastra: for a you unmute it.
Warren Gallagher: Yeah, I just wanted to say, I I think that the you know that
Warren Gallagher: the cadence of the calls doesn't matter personally to me as as much one way or the one way or the other.
Warren Gallagher: but I will say that I think the last few months have been
Warren Gallagher: very
Warren Gallagher: busy for the project, because there's been so much both refactoring of the framework
Warren Gallagher: as well as a lot of rework due to moving to shared components, and those 2 things have taken a lot of coordination, and I think have needed the the cadence of the calls
Warren Gallagher: to to maintain the velocity and coordinate those complex activities. And so I'd like to pass on some congratulations, I think, to the group to for managing that like, there's a very complicated set of things to to get to and deliver, and I think it was done pretty well.
Warren Gallagher: and so if for the next little while it. You know, people need a a break from that. And there's a lot more, you know, independent work that can happen. That doesn't require as much coordination. Then, you know, perhaps
Warren Gallagher: you know less.
Warren Gallagher: regular calls might be might be appropriate, and you know community will take that into account. But I I I certainly do appreciate the amount of work that's been ha! You know, and the amount of coordination that's happened to have had to happen over the last few months it's been pretty
Warren Gallagher: intense
Timo Glastra: cool. Thanks. Yeah, I I think what you may. What you say makes sense like. There's been less activity in in in the last weeks. And so after the a lot of the refect rings, and that makes up so that we have less to discuss. Yes.
Timo Glastra: okay, then, let's just keep it my weekly for now, but always keep it open like we can have it more often when needed. I'll
Timo Glastra: communicate this with why.
Timo Glastra: Then we're out of time
Timo Glastra: filter hour nicely. thanks, everyone, and then we won't have to meeting next week, but we will have it the one
Timo Glastra: after.
Timo Glastra: yeah, I need to think, yeah, I'll I'll be
Timo Glastra: still. Yeah, I'm going on vacation. But the week after that. So in 2 weeks I will be here with you.
Timo Glastra: thanks for
Alexander Shenshin: thank you.
Jakub Koci: Bye
Denver Naicker: me too great.