Project Harbor Community, 9 Mar 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: CNCF Harbor's Community Zoom Meeting - March 9, 2022

Description

CNCF Harbor's Community Zoom Meeting

A

Hello, everyone welcome to harvard community meeting today is march, the 9th and that's official cncf meeting. So please follow the code of conduct for cncf with that I've pasted in the chat the link to the howard community meetings uh notes. So if you have any anything to add to to it like the topics that you want to discuss today feel free to do that. My name is louis vasilev, as it's written on my video stream without I'm gonna share the the meeting notes from today for today give me a sec.

A

I hope everyone can see that we have few topics for today started already, so the first one is from nintendo. Are you on the call.

B

Well, there may be some mistake, it's not turn. Do I think.

A

Okay, uh I'm not sure who added this one.

B

C

Sorry, all right, let me let me rewrite revise it. Sorry for the typo.

B

It's not me, it's.

D

A

Right, I think everyone can edit that so please do so.

D

Yes, okay, so I show my screen.

A

Yeah I'll stop clearing them. If you're gonna clear your screen.

D

A

A

You can sure now.

D

Okay, I sat in authenticate.

E

D

Okay, hello, I'm eva from tencent and I'm glad to representation our proposed here and we propose to adapt multiple type of database for harbor, and the first step is to support my circle in mariadb and there is an abstract door. Layer in harbor and different databases can help their drivers to implement the interface and we want to add my circuit driver and, let's see the background.

D

As previous discussion shown, there are certain amount of users, especially in china, like the experience of maintaining pg for high availability, disaster recovery and meanwhile they're more familiar with other databases such as my circle and meredith b, and they prefer to use my real db and my circle instead of pg to keep production environments stable and as we all know, that harvard used med circle before and that scanner clear, use, pgs database.

D

So in order to keep consistency with clear and reduced maintenance difficulties, harbor unified database using pg and since hubble version, 2 used trivia as default scanner instead of clear. So there is no strongly requirement to use pg anymore. Therefore, it is possible to adapt different kinds of database now and our goals are as follows.

D

First, keep using pg as default database and our implementation will become, will be compatible with current version of hardware and abstract layer for different type of databases here remaining id in the implementation of my circle and and next support, mariadb and my circle by implementing corresponding drivers and the resolving circle compatibility and our verified version is very db.

D

10.5.9 and my circle is point: zero at last, provide migration to or get for users to migrate data from pg to mirror db and my circle. So it's our goals and our goals do not include the following.

D

First support other type of database such as and oracle, and this time we mainly focus on my circle and mario db.

D

Also, if others interesting it's it's good to support other data in the future and second implement mario db and my circle of operator for internal database case. At present, we expected to support support external database usage and if internal database user usage is supported depending on the future requirements, if need.

D

And the implementation of our goals and to support multiple database, we use the doll layer here and originally only pg was supported, and now we want to add the mathematical driver to support my circle and mirror db, and we provide a migration tool to migrate data from pg to my circle and there are four components uh interact with the database.

D

So the main modifications focus on these four core exporter and notary job service.

D

D

Initialize, the component car and exporter and notary the get db, config farm, config file and job service get config from hybrid call and after getting the database config, they do the certain initial operation, if postgres the init database and connect with pg and migrate databases with postgrad circle file and also, if it's measurable, on rdb the image database with it and connect with my circle or mario db and migrate database.

D

With my circle, superfile.

D

And I'll show the migrations directory architecture later then they need to success and when their work they need to provide service need to interact with the database and job service. Core exporter will use the certain driver type to access the database, as for notary itself originally supports my circle usage. We only need to modify the configs to provide the right database config.

D

So let's see some details at first.

D

Add the master config settings to metadata list include db type and some my circle configs and add a db tab to config pattern files. It will be used while applying the db configs to components.

D

And this is the struct of my circle, including some db configs.

D

And one in each database get the certain db configs if fpg using new pg circle and if mirror db, are my circle using new circle to know the database and as default. If you don't set the type you will use the pg by default.

D

And migrate db with certain circle file, pg circle file, founder poster brass and my circle circle file on the db underneath under my circle and here's, the directory architecture of migrations file names are the same under my circle and the postgres that falcon 10 may be different because of different grammars. Some some grammars are different.

D

And dollar make different databases compatible, and we can extend database support by implementing implementing my circle driver, and this is an example of doll, layer, door, interface,.

D

We can extend implemented and my circle driver to implement these functions.

D

And here have a call: crossconfig applies a certain circuit file according to the db type, if you're using my circle on my db, we will set is enforced to my circle over variables and by default. We also use pg.

D

And its project is the same with car, because exporters configure variables didn't contain the pg keywords, so it can be reused directly only add and db tab to show the type of database.

D

And if it's pg, this infos are all pg database infos and if type is my circle, and these are the master called infos importance.

D

Next job service job service gets config from call and then init database will db, dbconfig obtained also admin, add mirrordb and my circle support.

D

And yes, database enforce it get.

D

And next migration, as described above, will provide a migration to to migrate data from pg to my circle and ready b. Firstly, there's an official migration tool from my circle: community we haven't, tested it in depth yet in and still need further tests.

D

And, secondly, we could write a scrap the script to migrate data. First, define data models for pg and mirror db or my circle and read the data from pg and map to data model, then transfer pg data model to mirror db or my circle, data mode and draw data to mirror db or my circle database.

D

So and our compatibility testing.

D

We have done some tests for circle, compact compatibility and he released some support in incompatible points. First, pg use trigger to update the files of update time and instead of 3 trigger my circle, use default and update use. This way, it's okay- and this is the one point and next serial type in my circle is big inch on lined and this type is not supported to be a foreign key.

D

So if a column reference other column with tab 0, it needs to be defined. As speaking to enzymes,.

D

And next outer table column type in my circle must use, modify which use out mpg. So it's a small point and loop keyword is different between my circle and postgres.

D

The grammar is quite different, so it's a big difference. It modified a lot and last create index, not supportive, not exist usage and in my circle, maybe delete these keywords.

D

And now our 22 circle files are compatible with my circle and later we will demo it demo it with my circle version 8.

D

And also mirror db, where db, there's.

D

There's no something different with my circle, but at last they will be the same with use the same circle file and the same code logic with with my circle. So it is have some more works to do.

D

And at last all these tasks finished. We can use with my circle on the db in this way and config db infos under extend external database and add the database type.

D

If my circle and there's some db infos.

D

And notary we we haven't finished yet so this demo we didn't demo notary, but the basics basic component. We can demo, we can have a demo.

D

So now, let's see the demo.

D

Let's see the harper yama and matrix reset it and to use the exporter and external database.

D

So external database, we use my circle and set the infos below.

D

I start my circle in advance.

D

So we can use it directly and we test to install it.

D

Okay, the component all apps, and we can look at the block.

D

D

Okay, we registered database with my circle, and the info is my: I filled in the hyper yama.

D

And also the job service.

D

Yes, it's my circle.

D

D

Also, my circle and the host.

D

So then we can see the portal.

D

D

So we can create a new project.

D

F

D

And push an image.

G

E

D

Oh, I forgot. I started logging before so I didn't stop logging.

D

D

Up the three already.

D

D

D

Copy art effect.

D

D

D

The basic functions looks okay, delete, project, delete and the time will be only modified as a necessary code and to verify that my circle is available and we'll refine the code later, and this proposal still have many works to do so. If you are interested in this proposal, welcome to join our work groups- okay, all right, please. I finished my presentation thanks.

D

So is there any problems.

C

We have several um a question about your proposal assessed for the presentation. um I didn't see a very clear um part in the this proposal to support uh natalie um uh all of things. Naturally,.

E

C

Yeah, so um we have to add this part to this proposal to support. uh How do we support notary to support other kind of um database?

C

um Okay, uh oh yeah, the other one is the yes so um and as you list here, um there are several other cq are not passed um in this table right. So.

C

We use the several specific features that build in with poster quest like just, for example, json operation. So um how do we and how? How can we handle this part in this proposal? I I haven't seen that.

D

Okay, first notary yeah, I I saw the notary confused because we this time mainly focused on my circle and major db. I saw that notary itself support the my circle. Ways to start up notary and yes, I think we we need to do is to add the my circle configs to notary, and I yeah this time is uh um to.

C

D

C

And me have introduced some uh make fireworks and you have to add some. My secret.

C

We have to add this part and for the compatibility test, um since we use some specific feature for uh um in the cq files, so we how to handle this part we we should add this in in your proposal. um This is my.

H

C

Comment: uh yeah, the next one is the um for the migration tool, uh since this proposal is targeted to support multiple kind of uh database. But uh in this proposal you just mentioned: how um can we migrate data from post request to my secure.

C

But in my opinion, we have to provide a framework to have user to add some new implementation to support other kind of migration like if I um implement another uh kind of driver to support uh like my mongodb yeah.

C

How can we, uh how can I migrate my data from post requests to mongodb and how can I implement a new adapter such as our plugin in your migration tool? So for the part it should be a framework, I think um not just uh simply already.

D

Yes, yeah this time we yeah, we mainly focus on this type of db, and if future, we need to add other databases. Maybe it should be a certain way should it provide another migrate to provide data, translate we we may need to migrate data from pg to and use another migration too. I think yeah.

E

G

Be generous, uh I I I understand uh what you said. uh You mean uh we need to uh uh write this migration tool, uh uh abs, uh abstractly. uh We need to uh support other database in the future. We will. uh We will add this part in the proposal.

D

Okay, okay, I I know we are only focus number eight and we should focus on more databases right.

C

Now we should uh have more details on the uh migration partner. How can they use.

H

C

And when should I use it? Yeah.

E

C

H

One yes yeah just related to the migration part, so I I also had a thought that we should be a little uh like since we use uh a database driver abstraction which is gobigo. uh I think it's a bigo framework that is used. We need to be aware, like uh we, we need to benchmark. What will be is the behavior of bigo, uh like whatever apis we use of bigo? Are they? Are they like?

H

You know it may not be uh sent to send similar, but there should be some level of similarity, because it should not happen that bigo implementation creates a performance problem when you start migrating the data from postgre to mysql, because we do not know if the implementation has used something specific to postgrade, to speed up some executions and we are just invited. We are just using that feature without knowing it.

H

So, in my opinion, in addition to the migration abstraction, as yan mentioned, which is which is really important, we also should make sure that uh the the sdk that we are using to interact with the database right now is going to perform comparably across both the databases and it does not induce some, uh like you know, lags or performance penalties which are hard to track. So I think that's important.

H

I guess, uh since uh we are moving across databases- and it's not like a general driver like bigo, will definitely use some hints to optimize some types of some types of executions or other. So we need to check that out too. I guess.

G

You mean we use big uh or have some uh performance issue right. Yes,.

H

That's right uh like like it may be. Speed like the same. The same functionality will be speedy will be executing very well on postgre, but the moment you migrate to your moment you migrate to mysql or mario db, uh possibly like you know, you may see a performance hit and it could simply be because the underlying big implementation is doing something wrong, and- and I call this out because I have done some database migration projects- I have seen this happen in the java world.

H

I'm not sure if it happens in a google world, but yeah we need to. We need to be careful over there. Oh okay! Thank you. Thank you. I I understand.

E

D

E

D

Last question: jason: okay, okay, you see.

C

Oh sorry, I may have some further uh questions about regarding to the dl interface.

C

Do we have to implement the all the dl interfaces in harbor I mean for each manager um like uh repository type label and etc,.

D

And most most jaw interviews are compatible with pg and my circle. Only little circle statement are not support between pg and my circle.

C

D

I, in my opinion, it should be a architecture that we should give a certain database, uh the the implementation, and that we can take a reference to the default interface. So we we can reuse the function, reduce the implementation, but we should have a driver to reference to the default function.

D

Maybe the implementation of them are the same, but they have the.

D

B

I have a suggestion, uh I think uh it's better for your tools to discuss uh offline.

H

You can use chinese.

B

I think it's much easier for us because yeah about uh implementation details, I think, is a bad choice.

C

Yes uh feel free to schedule meeting, but uh we I like to discuss some details in this meeting so that the other um users from the community can understand uh the proposal, details and what's going on on in the pearl harbor community. So um but okay, we can uh we. I can just add some comments in this proposal and- and we can have discuss on that so that uh others can see the communication um based on our conversations. Yeah.

B

I think it's a good idea.

C

Okay, um so um my last question is that we should provide some guidance for the developer from community to tell them. How can they implement a new database driver? What should I do? What should I follow and so that the others can follow this guide to implement their own database driver and contribute back to harbor like I want implement one mongodb driver and just follow your gut and then send me my pr on back to contribute to harvard.

C

So we should provide the guidance in your proposal.

B

Yes, I agree uh about this. uh I have I want to discuss some common things about this proposal for databases. Shall we extend the scope to too wide? We will we need. We need to support different kinds of databases that others want. I think, if we support too many databases, uh it will be a big burden for hubble. To maintain one of the things is your progress mentioned the migration tool. I think it will be difficult for hubble to maintain too many databases, tools and the logics.

B

Maybe we can just focus on a 203 database kind. I think it's most.

C

I think, from a perspective of harbor, we just only maintain post requests, but uh if someone from community they want to maintain my secure mongodb marine db is good for us, so by default, hardware supports post awards and all the maintainers will provide support help on that, but for the other kind of database.

C

We should uh leverage the effort from community to support that, but um for just like what we did for the replication like the tencent adapter, I think you guys could provide some help on that adapter to support hardware replication from hardware to tencent network right um yeah. That's my answer for.

B

For your question from our from us, we we only want to focus the marine db and message for the moment and yes, I will. We agree that we should provide a framework to have others to implement their own in java, for layer uh prefer the databases but it's difficult to, for uh I suggest by stephen we we maybe we will make a database whole group, but I think it's. uh If we didn't control the scope it will.

B

It will be very difficult for the work groups to work if we cover too many kind of databases- and we didn't have uh that- that's effort to uh do the work.

C

We won't do. I think you can just uh provide uh effort to support mysql on my rdb yeah.

C

For other kind of database, I think if someone from community have interest on that, um they can just contribute that part.

B

Okay, I got it uh and uh I have another uh another things to say about this proposal is maybe, if we uh choose to provide one kind, a kind of databases, but it it may not work work for all of the hubble component, for example the notary.

B

If we, if one customer wants to use hubble with cassandra, for example, but notary didn't didn't, doesn't support cassandra, I think it also can be a choice. Just if we make our choice to use the cassandra, we must give up the notary use component just to use the basic hardware functions. Do you think it is reasonable.

C

So my opinion is not: um we have to provide uh uh all the functionality for a new kind of database, but the notary is is a special case, and since we we have some discussion or not with application, but uh anyway I I my suggestion is that we should provide full functionality on new kind of database.

B

So, if, if we want to uh provide four functions of hubble none, if we want to support one database, we need to adapt to the hardware or clear such candle for solar parts component right.

C

Yes, but there are not so many third-party components that need to be accessed database just another so far and there were not some additional uh third party not to be introduced into harvard to have access to database.

B

Okay, I see, I don't know how many databases, notably support for the moment.

C

My real post request, um I don't know others, sorry.

B

Okay, so uh considering for this, I think for the moment we can only support uh the previously mentioned databases for, for now,.

C

uh Yes, yes, but uh if we uh duplicate the notary I mean the without notary uh um integration. um We can introduce um some other kind of advice. I think.

B

Yes, that's. My second question to you: is this legal to support owning the basic function of hubble without the notary.

B

We want to provide the full functionality of the hubble. Maybe uh the choice of database is very limited.

C

My personal uh opinion is that we have to provide function, full functionality to support new kind of database, but uh I'm not sure others of any or not.

D

Yeah, maybe it's a choice.

C

So we can, you can just put this item um into your proposal and then anyone who reviews the proposal can give our answer on that is that, okay, for you.

B

Yes, I think it is a good choice. We will make it the statement in the proposal. First.

A

Great, um I I'm sorry, we have to run fast. We have uh less than 15 minutes. Okay, I'm sorry! uh I don't want to put you off, but uh I don't want to crawl the hour. So uh we agreed that I can see the pr put the proposal in so you're gonna.

A

You don't want you're gonna put your commands in, I can see already tianon commented steven wren commented so there's ongoing discussion about that happening in the in the pr for that proposal. So please do that.

A

Thank you a lot for your demo and presentation very useful. um So with that, I think we can continue with few more topics on the agenda. I'm sorry again to get you all, but we don't have to um across the hour. um So uh I have two topics: kind of h3.

A

uh Our maintainer truck was accepted for the kypcon eu 2022., um please uh I think young one you you've submitted it. um Please start preparing. If you need my help, uh just drop a line, and I can I can help out with the with the preparation for the uh for the session.

A

um Second topic is: are we going to release in two days.

I

Oh only that's that's not true, and the original plan is we target to release around uh may march 11 right yeah. uh I remember in last community meeting, maybe have checked me to check the date. At that time I updated in the stack channel I it targeted to maybe uh march 21 since uh yeah. That's a monday right, but currently we have some new. uh I mean new uh new sense.

I

uh It is. I have seen you listed in the topic five right. There is a notice related to cve issue which is currently block or release. So we should uh have some.

I

I mean information from northwest that when they can reduce the patch to fix gstv, so we can uh consume the upstream patch in our harbor side, so that will also impact our 2.5 release. I think so.

A

Right so I can put the really date again, tentative.

I

Yeah is that it is your attendant you, I think, if it's no notary cv issue, I think we can say maybe the target daily around march 21, but due to the cve it is, it is the temptation. Okay.

A

Okay, cool about that, I'm trying to um to find a way through the cstf governance with the notary folks if they can touch that yeah. Thank you, but for how how much it will take at the time but um yeah, okay, uh abby you! You have a topic for the sick dogs.

F

Yes, hello. I just wanted to um plug our uh our next meeting, um the sig docs group, which will be next wednesday, which I think is the 16th. I might have have the wrong date, but it'll be next wednesday and it should be at the same time as this meeting.

F

um We are having daylight savings time change this weekend in the u.s, so I might have put out the wrong time so I'll double check the date and the time, um but it will be next wednesday, so folks are interested in joining um and and helping us with the docs or learning more about our docs um for the harper project, uh we'll be having a meeting, and I hope to see you all there.

A

Right, uh do you need any help from my site to like do the I don't know, uh announcement in channel or tweet or something that we're gonna meet, and that will be the first official sickbox meeting.

F

um Yeah, maybe we can put, we could talk um a little bit about where to post other messages in the channel and such.

A

I

Cool thanks, that's great! Thank you. Baby.

A

And one again to refer back to the cvs, uh those came out from the app check things that we run right: yeah yeah and we okay. How should I put this one if notary are not like cooperative enough in in some time? uh What are our options? Do we have any any other options? I mean to like at least close our eyes for this one and release like this. I don't like this one, but.

C

Actually, I have a same question.

A

Yeah personally, we don't have roger on the call. uh Maybe he can put more this one, but I mean a part of the procedural. Like closing our eyes. Do we have some technical um solutions for this one? uh I think we discuss once to fork notary and fix it on our own, which is, I think we should go for this one as a the last possible solution.

C

Yes, that's right, so if we cannot get any response from notary community, the the worst case is that we there repository and ship not really in the we're part of it.

A

And in did you already uh submitted a pr to the notary with the fix or we're just waiting for them to fix it on their own.

C

They already have someone on risk pr to fix that, but they have to merge them and then raise another pr based on that, so to fix the uh another pcbe. um But uh I I have already mounted them, I mean uh not for community or a maintainer. They have no idea about the eda.

C

They just said to me that they they will provide patch but no guarantee on when they can do that.

A

I'm just trying to figure out how I can change them properly, uh so I can see we don't have an open pr for this one, at least from our side. It's like yeah.

C

um Yes, yes, um um the third one is up from offside to fix the program, um yes, and that one is from a stronger cr to fix the form of dependency uh and another one. The.

C

Return is the other one. uh Can you switch back to the the pianist yeah.

A

C

The sec, the six, the sixth one, um this one.

A

Or no, this one.

C

No yeah this one, let's go, they have to merge this pr first day and then I can raise another pr too. Okay, first, they have. They actually have already approved this pr, but no one take further action.

C

I I'm just very.

A

So um I'm gonna, I'm gonna talk with justin. I know him and um I'm gonna ask him if he can provide some some info on this one.

C

Okay, thank you. uh um So when shall we make a decision for very part, uh do we have a uh uh enough day for for this.

A

You mean to take the decision, what we should do next.

C

Yeah, whether we should or or just uh wait for their response and eventually we we should have a decision on that yeah. So I mean. When, should we have that decision.

A

Okay, that that depends how much time we need after we make that decision. uh If we're gonna meet the 21st of march release date,.

C

But regarding to 2.4.2, I heard several customers are waiting for that release, but that one is also blocked by this cve.

C

So um we have already deleted the lab patch release for several weeks and yeah.

A

Have you addressed that to alex chu or roger.

C

I think we need roger's comment on that. Yeah.

A

I can help out with this one, but I I cannot take that decision. It's uh it's not in my field at all, but also relatively new uh cvs right.

A

C

A

Okay but yeah, but taking into account that notary hasn't been released, uh there's no new release for for notary for almost a year, or maybe two.

A

Okay, yeah, actually almost yeah three years: okay, I'll, try to get into justin and see how it goes and yeah because, as I mentioned somewhere um we're not the only project that relies on notary heavily, so they have to fix that anyway and yeah yeah. The thing is that not very easy: it's uh a cnn project, yes, and they have some responsibility based on this one, so they have to do something.

A

Can I ask you if you can open an issue for our use case, because I'm not sure if I can work it properly.

A

So I can point them to the right information.

C

In terms of the cve, we usually do not file issues on github, that is, the security yeah.

I

C

We just follow their security uh um pipeline just start mile to their security work group and to notify their their cve in their project, and you have to provide fix on that, and this is the usually uh process for us reporting. A security issue.

A

C

A

Sure, if I, if I can repeat the lesson, please.

A

I

Yeah only what what I mean uh to report a security issue normally will not uh file an issue in github. uh You will follow their process to send the email to their security group. To mention that I think I already have sent an email to their security group and get a response from then so we'll patch this. But there is no ek for that.

A

Yeah but that's like it's a known, cve right, so it's out there, so whoever wants to to scan notary can get that information right. It's not like non-disclosure.

I

I mean you mean that is a normal cv already yeah publicly in the in the community right.

A

And, and my idea was to open the issue in their in their repository, so I can point them to yeah folks. We found this that right now your release, which is three years old- it's uh it's affected by these cvs. Can you estimate if you're gonna fix it and when you're gonna fix it.

I

Yeah, I'm not sure if you have pasted uh yeah. I have pasted these two cvs in the chat. Maybe you just only need to use those information and very issue to them. Maybe that easy enough, I think, but I'm in australia.

A

um Okay, can you uh young one, can you look me into that mail that you sent so I can. I can follow up from my own register. Okay, sure sure, okay,.

C

I also passed the security uh um us in there. um You can open that url to see some details.

A

Yeah but yeah, but yeah, I I know that process, but the thing is that I I think that those are like publicly available cvs already and everyone who can scan their artifact can see that those are uh valid cvs for the current release.

A

So I think I think, a simple issue. Okay, can you fix that or when you plan to fix that it will be good enough for now, but okay, I think you brought that to the security team. uh If you can forward that mail to me and I'll try to get in touch with justin, okay, great okay, with that, uh I think we are ready with the agenda. Anyone else or probably the agenda here- uh wants to say something wants to share something.

H

Hey uh jan and uh team, I just uh this has been a couple of weeks ago.

H

There are two reviews and I have responded to all the comments. uh There are some comments like getters back like I did. uh Those discussions are like I mean I think, they're rotating around the point of whether we need to show system artifacts to the user or not so yeah, and if uh baby has already responded.

H

If you could take a comment from uh our tian on respond, it will be great so that, uh because I have my implementation- and uh I want to run this uh like as soon as possible in the next couple of weeks, so just wanted to make sure that, uh like we don't we don't get back again on a decision that does something that adds some ebook.

C

Sorry, I can't hear you very clearly, but if you are talking about that your proposals, I think I have already through that regarding to the implementation, I think you can firstly to create a engineering ipad in, go harbor repository and break task breakdown.

C

You can just list the detailed tasks that you will do and then we can use that issue to track the progress.

C

uh That's okay for you!.

H

Hey, uh hey, uh hey, I'm sorry! I am lost in between because of a network glitch. uh Could you repeat like.

C

I mean I have already approved your proposal and regarding to the implementation, I think you can just firstly to create an ipad in, uh go hub repository and then do the task breakdown. You can just create some details task in the repositories. So then we can use that issues to track the implementation, progress.

H

Okay, sure sure uh sure- uh and I can do that and I'll sync up with you- if I, if I get blocked somewhere, uh creating the issue I'll come with you so yeah. Thank you.

A

Hello, can you add that thing to uh to the agenda for today? So we don't forget about it and next time, if needed, to discuss again.

H

Yeah sure uh sure I'll add it to the jitter today and I'll I'll. Just put it.

I

It was just a point.

H

That I wanted to mention so that you know the community knows that I've started. uh You know uh dabbling with the code and getting things like, but I've not done specific tasks. I will. I will maybe I'll create those tasks as young suggested, and I will so that the thing can be tracked.

A

All right thanks, yeah, no problem, anyone else anything to share.

A

No, I think, then we're done. Thank you, everyone and hope to see you next week, some of you on the sickbox meetup or the week after that on our next community meeting bye and have a nice day.