Layer5 Websites, 18 Sep 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Websites Weekly Meeting (September 18th, 2022)

Description

Layer5 Websites Meeting - September 18th, 2022

Agenda:

Service-mesh-patterns
- Final Design review
- Navbar
1. Mobile Responsive ✅
2. Layer5 Logo increased size ✅
3. Button component reused ✅
- Open for assignment: Authors, Chapters.

layer5.io
- New repo for handling subscriptions
- Hacktoberfest 2022

Docs.meshery.io
- Designs of the compatibility matrix [Link]
- Document Meshery Catalog in Meshery Docs
- Catalog responsiveness #787

Join the community at https://layer5.io/community

Find Layer5 on:
GitHub: https://github.com/layer5io
Twitter: https://twitter.com/layer5
LinkedIn: https://www.linkedin.com/company/layer5
Docker Hub: https://hub.docker.com/u/layer5/

A

So hi everyone welcome to the website's call. uh We always begin this call with the introduction of our newest members. So if there's anyone in the call who's attending the website for the first time uh feel free to introduce yourself to everyone in the community, tell us what brings you here? What do you want to work with what you work with anything you like so I'll, just wait for a couple of minutes for you to volunteer. Otherwise, I see one newcomer on the call today uh you can go ahead with the introduction.

B

Hello, sheikh vari sophomore at netherlands.

C

And uh I'm new to this community and open source. Actually I was looking uh at linux foundation and then I found about all this layer, 5 and now.

B

I joined it thanks.

A

Welcome to the community of the sheikh, uh I don't think we have any other newcomer today. We can circle back to introductions later on. If we have anyone joining us uh I'll again, once again share the meeting minutes link on chat. So if you guys have any agenda items to discuss today, you can add them in and if you're on the call make sure you have your names listed down in the attendees list.

A

All right, so, let's begin with the agenda items. So first up is common commonly want to share your screen.

B

Now you can share it.

A

This is the latest review, including.

B

A

A

So there's still some responsiveness issue you see over here.

A

The text is invisible here.

A

Thing coming here as well and.

A

It might be a lag on myself.

A

Also shouldn't these two be aligned together, like was it like this in the design.

B

You mean that layer, 5 logo should be a little above.

A

Alexis, which is the final design, the one which we are following.

B

B

A

I think we can break this into two lines and have them aligned not sure what do you guys think.

B

Yeah I was saying that I followed the earlier design in which the authors and above layer pipe was separate.

A

I couldn't get.

B

uh If my voice working oh, I will just write it in the chat.

A

You know avi, are we following a line break over your patterns in action? I think that was what was there in the design and in that case, about an a5 shouldn't be centered aligned like this. I think it was left aligned, I'm not sure.

A

But other than that that can be fixed later on, uh there's still some responsiveness issues which you have to fix. After that, I think we can at least merge it and have the other changes done later on.

A

Come on is taking something.

B

B

Design we have like many designs, so maybe we could add a tag like these are the final ones.

B

For the navbar we have.

A

I think this is the final design.

A

Okay, okay and you're- also looking into the about section right, I just reviewed it. So the dark background is gone. We need some more space over here and.

A

There's still some responsiveness issues like basically what's happening before. The sign is just that this book, like it should be the front view it was going behind this section, uh but this is not what is desirable. What is happening right now.

A

And I think this is uh left aligned as well uh yeah. This is left align the heading, and this is how we want the overlap to look like.

B

A

uh Cool, please get this done by this week because uh technically the deadline was last week and I think javia is not on the call today. I'm not sure.

A

Yeah fabia is not on the ball pit and last time I checked, I think the pr was also not updated from last week.

A

So I think we can open that up for assignment now, since there's been no activity and the issue with the background image, I think that was fixed. Last time we killed shared the background image link over here. It can be downloaded and I think any other contributor can take it up, pick up the office section because there's been no activity from vr since last week.

A

So anyone in the call is interested to take this up.

A

Now, to give context, I'm talking about uh one second, this section right here.

A

We need this page to be created and I think there's an open pr, but that had a couple of responsiveness, issues that background image had to be changed.

A

uh It was not ready, so you might have to do it from scratch or you can take inspiration from that pr as well, but we need a new contributor to take this up.

B

A

You want to contribute to this.

B

A

Okay, uh cool and I'll note your name down I'll, be sure.

B

Can I start contributing after this week because currently my.

C

Medicine exams are going on.

A

We're moving slow with this, so you're gonna be inactive for this week. We might have someone else. Take this up. You can come back and take up any other issue whenever you're free, that's not a problem.

A

If it's fine with you, there'll be a couple of other good first issues, or even this if by next week, it's but anyone who can look into this this week,.

D

Hello yeah, I said bubba is almost done with the pr. I don't know why she's not here for the call today, but uh as far as I know, she's almost done.

B

Last week,.

D

I talked with her.

B

E

She has done with the pr, then ask her to join the column, share and update. Otherwise we are moving on with the other person like it's already been two and more than two weeks sure.

D

I'll just text her and.

E

Because I haven't seen even the first set of reviews being resolved, so I'm not sure what the connection is.

A

uh All right, so no other updates from service match pattern site right. uh Kamal. You have two components, so I think you should pick up your base a little bit there have you addressed a couple of uh reviews and everything, but let's get this merged by this week, because we are moving very slow with the service mesh part inside.

B

Yeah yeah it will. I will be committed to this right today.

A

All right uh and.

B

A

B

A

B

I was saying that we can have a volunteer also for the chapters of the page.

A

B

For chapters uh chapters in the book section.

A

Yes, the last time I think you mentioned that.

B

I had but, but I was talking the navbar and about so I couldn't get time for the chapters in the booklet, so maybe we can have a volunteer for that.

A

uh Do you guys remember who was okay? It must be mentioned here, love push.

A

Now, love kush was assigned to the later part of the author's page right, but he's not on the call either so I'll. Think on the website's channel, we'll look for fresh assignments for both these sections chapters and, in the meantime, alexis I think, you're working on patterns and actions, page the design right.

B

A

So no updates on that today.

B

A

So let's have these assignments I'll ping on these slack channel uh cool anything else from you come on or uh there's no one else in the calls.

E

Now I will update both the sections by today. That is the update for my site.

A

All right cool so moving on, uh let's cover ishan's topic; first I'll bring this up after that. You want to share yourself.

B

D

Hello, can you hear me.

A

D

So yeah, I think, last week uh lee told us to file an issue or something I mean uh me and deborah are working for it, but uh and we are not sure what exactly he had told us to do. I think he told us to file an issue. I mean there's one part of the october 2022, which is updating the layer 5 site, uh which is clear, but the second part is not clear, which is about the opening of an issue.

A

uh Can you go to the recording, which was which I think will come out this week?

A

I I just published it a couple of minutes back. It should be available on youtube. Can you go to the recording which we asked you to do because it's last week.

A

So about this, so I think uh yeah a couple of days back lee and I were talking and we thought that we need needed a new domain basically measurey.dev to handle subscriptions like it would be something similar to this, but mostly to unsubscribe people like a form to unsubscribe people, but we wanted a separate domain. So uh I created a new reboot for this one problem that I'm facing is we want the domain name to be measuring there, but I think currently it's redirected to the measuring page.

A

I it might be a stupid question, but I couldn't find out uh where this redirect is mentioned like. That is why the cname, the custom domain is facing, like I'm facing an issue with defining the custom domain. So I don't think nikhil. Do you have any idea where I can change this? Redirect.

E

It's happening in the layer, 5 site itself right or it's happening in the measure.website, so I've been the machine on the website.

E

You, if you navigate to message.dev, then only it's navigating you to like redirecting you to layer, five dot, io cloud native last mission, yeah and what's the rapper for this site.

A

So the wrapper for this is the subscription repo which I just recently created, so the redirect was happening from before. I just want to prevent the redirect so that I can add that to the github pages, for this.

E

It's a regular html site or checklist. Sorry, it's a normal html site or is using jk.

A

uh It's a normal html.

E

E

Can you share the repo link with us.

A

A

Okay, so we'll come back to this later, uh let's take up aditya's topic or divine's topic designs of the compatibility matrix. Do you guys want to say this? Okay.

C

Yeah yeah divine on the call yeah, isn't it uh hi divine? uh Would you like to share or should I share this.

C

Yeah I I'll share the screen and diving in pidgin, so uh what we are currently working on now is that uh so in the docs hello. Can I hear me.

B

C

Yeah yeah yeah you're already good.

B

Oh okay, okay,.

C

So I'll just describe the issue what we're working on then you can continue from the divine all right right. So what we are currently working on is that we have a compatibility matrix which shows all the uh since we run integration test on each of the repository like hto, linked e comma, and we report it here back in the docs. So we have made from these integration test a compatibility matrix in which we show the uh which measuring component is compatible, how much with what mesh kubernetes version.

C

So we have this compatible matrix, but currently it's a bit of a hidden like it's not uplifted in a way in which we can easily see the users can easily see it. So our plan was, to you know uh uplift the comparative matrix and combine it with the you know, consolidated with the platform compatibility matrix that we have here in supported platforms, page so working on with the designs with divine. We came up with some designs and we pushed it. For you know.

C

We also posted in the website channel to look for suggestions and all, and we did post one iteration first, uh which was this, but this was not uh like. We expanded the platform compatible matrix and put the comparatively matrix below, but that was not the required one. Since we wanted to. You know, combine this platform coverage magic as well as the compatible metric, so we so divine made up a new design for it, uh and this is the one in which uh okay, sorry yeah this design.

C

uh What it does is that uh it lists all the platforms in the heading and once a user clicks on a platform it opens, it opens a field for that platform like it opens a table for that specific platform. Only and in the left side we display all the uh all the platforms that this parent platform supports and the in the middle of the table. We show the platform like compatibility matrix, so if we click a docker, we so similarly all the platform that we're having and compatible matrix so yeah. That was it.

C

That was looking good, but uh lee pointed out one issue in this that uh earlier, uh like we used to, you, know, show the version of the platform itself, like suppose, aks right, as you can see, we are showing eks it's 1.1 to x and above so, this 1.12 x is particularly showing giving us the version of eks itself like it's compatible with eks itself, but uh currently in the integration test. We are not testing that at all, like the version of eks is not.

C

We are not testing at all, but only the version of kubernetes. We are testing, so we thought of removing those uh in a consolidated platform comparative matrix and which is done, but they come like they occur another issue regarding the same with dockers, because when docker we, we are not particularly storing anything in e to a test in dockers, but we still have uh like. uh We still want to show what version we are compatible with docker.

C

So yeah, that's a bit of uh like stopping point that we are stuck at right now, like how should we, you know, show like docker is uh compatible with measuring components like uh we don't want to show the version right here, but we want to show something that uh in the compatible matrix, not available thing for docker, so yeah, that's what least suggestion I could not. You know uh I'm stuck like how should we do that.

C

Divine, you want to add something else.

A

uh Divine, do you have any others? Any suggestions to add here.

A

You're on mute, if you're speaking, we cannot show you.

B

Hello, can you hear me hello? Can you hear me yep, my network is hot, so I might not be talking much.

C

Hello, I said I have a pretty bad man's work, so I can't oh okay uh yeah. I basically discussed like all the problems and solutions come up to come for it. uh We are just stuck on this thing like how should we display the dockers compatibility thing and what I was?

C

uh What like, what I thought was that, since uh docker, desktop and docker actions are like separate application of itself, so we don't uh like we can forgo these versions that we list here like 2.0 and two point x, but uh please correct me if I'm wrong, but does this to uh run on docker engine like if so then we can. We can uh like clearly show here like uh yeah. It's it is. The machine components are supported with docker engine uh this 1.1 x and other like.

C

If docker engine is the main like driving factor from for working docker.

A

I think uh three of them work differently, like docker engine docker desktop docker extension. They are separate, so I don't think there's a nesting involved in the world.

C

Okay, uh uh I thought like docker engine is the like engine that makes every all the docker components work. If not, then yeah we just need to figure out like how how do we, you know, display this, because if we, uh if we still want to maintain similarity like we, don't want to display their individual version here.

C

So maybe we can.

A

We have like a collapsible table like uh you have docker as the main uh table and when you click on it as a sub list, you have the three variations.

C

Yeah, that's what it does like if we click docker, we we see this page like docker gets selected and all the platform for the docker and the compatible matrix like we want to show something here. Maybe yeah.

A

uh Any other suggestions, anyone.

E

I'm still missing some context. What exactly do you want to achieve over here.

B

C

Okay, so during the first initial uh like when divine, we made up the platform compared this this matrix, we were showing uh these versions here, like uh eks, 1.12, x and other 1.1, for example, up here right. But these are the version of eks and jk itself, which we are not tracking at all like. We are just concerned about the kubernetes version, so we thought that, let's remove that, because we are just increasing complexity and making user confused, so we removed it from the kubernetes one.

C

But now when we talk about docker, we we did show that it is compatible with docker like a driver engine 1.19x above 2.0x and above. But these are again the same platform like docker engine version, docker desktop version which, if you want to you, know, uh maintain the similarity as we did in kubernetes.

C

We would want them to be removed like you should. We should not be showing them here but like in the integration test. There are no no docker talker configuration that I'll uh that are shown so like what should be show uh here that makes like that makes the user educated that yes, uh doctor works with compatible mat. Like machinery is compatible with docker this and above like what is that factor.

B

F

Can we still add the versions for the docker extension and just remove for only the kubernetes.

B

Or include for only the pages with um local extensions and the ones I need to show the.

B

C

uh I also kind of thought that but yeah that that still has some problems. Regarding the like, uh it's still a bit of confusing, I guess for the user like it's not here, and it's here, that kind of thing.

E

So if we are using like do, we still want to show the platform site all the three platforms that we have: docker engine docker desktop and docker extension.

C

I think uh docker extension is like now. You know merge with docker desktop so yeah. You can merge it. So.

E

We only want to show docker engine and docker, for example, yeah.

C

E

But it will have all the different versions just like this, so we can show it. Similarly, as we are showing it for the kubernetes tab itself, like the first column, should be the versions called the rest should highlight the compatible versions. uh If, of course, if uh like there might be a difference that it might not have be all the five columns altogether, but it could have only two columns.

C

So I think we should work on. You know exposing the docker version, these integration textile running.

E

C

Okay, that's that seems kind of like I I'll I'll, raise this issue in the ci channel and you know, let's see where it goes,.

B

C

Yeah, thank you.

A

uh So next up we have kanika's topic right now, hello.

G

um Am I horrible yeah? Okay, so um I've been assigned the issue of the catalog one like um the okay? Let me just share my screen. uh The document messaging catalog in mystery docs, so um I have to like make a a separate page like a separate uh documentation for the meshley catalog. um I just wanted some of the clearance on like how how to do it, because there's so many components on the mesh documentation, so just a clearance about where the catalog topic will be there and stuff like that.

G

So I just wanted to know um so. If, um if anyone can guide me a little bit, I will be just.

C

Sharing the.

G

G

So this is the um this is the measuring documentation um so where the catalog thing will actually go like which of the uh in which of the headings and stuff like that. So uh I wanted to know about that.

A

Well, he is not on the call, but as far as my understanding goes, the catalogue is an extension right. Aditya you've been working on it. Do we consider the catalogue to go under measuring extensions.

C

uh I'm also not perfectly sure but yeah in the measuring ui. We go it. We put it on the extensions.

G

And one more thing, I think um I think um I don't remember, but someone was actually working on the um uh these filters. This was was one, so I just also also wanted to know that, should I like start working on the catalog, or should I wait for these to, like you know, uh finish up.

G

Yeah go ahead. Yes,.

A

D

No, I said it was me, I am sean okay, okay,.

D

So yeah we are still to uh I mean we are still lacking some information, but, as we said last time, we can merge, whatever information has been built. So I'll do that, if we can do that, we can merge whatever information I've actually raised appear on it. I'll just comment on it today, so that the maintenance can get an idea.

D

B

A

And as for kanika, I think the first page that will go in is just an overview for the catalog right, nothing in detail just what the catalog is. How does it integrate measuring stuff like that right.

G

A

uh Okay, it was a question, but.

G

Yeah, yes, yes, surely the first stage would uh would be necessarily the introduction part like just an overview of catalogs.

C

Yes, I kind of mentioned in the issue itself, like the first part of it.

G

Yes, uh what's catalog, and um so I just wanted to know that where, where it would be fitted like the in the overview, one or the concepts, one of the functionality, one like, uh because I'm first time working with uh jekyll. uh So this documentation is built on that. So just a clearance.

A

One second.

A

I think it will go under extensibility. That is, but uh have you started working in the draft you're writing that as well? Right, uh sorry, can you repeat uh you're the one who's writing the draft right. You're, like your part of the issue, is not just publishing it on the docs. You have to write it as well.

G

Draft, I think draft is not mentioned here. I I think I have to like contribute to the talks uh directly yeah.

A

C

No yeah, I was saying that only like you have to write uh like you can write up a draft like you need to create curator content like what goes in that and then after that, maybe you can think about. Where should be putting it in the docks.

G

A

Yeah so uh add that dock to the community drive, uh let's have the content up first and then uh I'll confirm I'll confirm for you. We need to put it it'll mostly be inside extensibility, but if there's any change I'll, let you know, but let's have the const.

A

uh You're still not audible, can you write in on chat.

A

uh Okay, so I'll be good to go from here, I'll I'll.

B

A

All right so next up, uh rohit, catalog, okay, just before we move on kanika, was your design for mesh mark on the smp page approved.

G

uh For the mesh mark yeah, um there were two. uh There were two changes that uh nikhil wanted to uh like he wanted to do so, um I'm just working on the changes um it would be. It would be ready uh like this uh this evening.

A

Okay, then, please share the link or ask for review on any of these live channels once it's up for review, okay, okay, good! So yeah do it! You can share your screen.

B

H

Yeah am I audible.

B

H

Yeah, so um so, yeah. uh Last last time, my last meeting, I had a feedback that the button didn't really look like a drop down, so I uh okay yeah. So I made that uh I made a few changes that now uh it looks kind of like a button.

C

Yeah I just when you are editing that you change the order of the menu. Also resources should be at the.

B

B

H

Okay, uh can someone else share the screen? My internet is acting like this.

H

Is that fine then, like.

A

Is the link on that.

H

A

You have the pi, sir I'll answer.

H

Yeah, I could just scroll up and then open the deployment.

H

um Reduce it to mobile screen.

H

uh Yeah, so that button was there so that I added that.

H

So I could uh um just to just for improvement. I could uh just round the corners if, uh if that would look good and then uh somebody also pointed out another issue where there was alignment issues during in the full screen, I saw that also so uh for now. uh I think everything is good if there are no other, no other improvements or not.

A

uh Do you guys think we should just have the button first instead of showing this.

A

Does that make sense.

E

Like probably yeah like yeah, instead of yeah like instead of just having the filter button at one corner, we could span out the complete width, but it shouldn't be a complete button, like the complete screen, which shouldn't be a button, the text could be separated out and we could just use an icon on the right side, since we will be hiding the view just having a button on the right side. Won't look that good, or maybe it look good like we might need to check it out.

E

I can't do it right away.

A

We just show like the drop down first, instead of showing categories as well like only when a person clicks on it should be defaulted to all, but only if the person wants to filter uh you can go here and filter as per whatever category they want to. So.

G

A

Can show the button and if we remove this, uh what nikhil suggested is just having a button over here might not look good.

H

A

You might span it out or have like text and a small drop down over here. So what is it over here? We also use just a button.

A

It doesn't have to be similar, but I think having it just on this corner might not look good, but it could be centered aligned.

A

uh Maybe once you open it, you could have a transition effect over here across or upward arrow. Something like that.

H

A

And have the center aligned and a little bit bigger, maybe open filters, close filter, something like that.

H

Okay, so center align the button and then so for default. The default view is uh there shouldn't be nothing and those cards that you score when it's called down below. They should take up that space. What uh the uh okay that space, what it's being used right now.

A

Would move up this shouldn't be, but only suppose I click on categories. This should come up.

H

Yeah, okay got it and.

A

Maybe once you center align it, it could look like a like it uh like right now. I think these look like separate entities, they don't look like they are working together, so you edit the design in a way that it looks like this is part of the whole uh like that filter.

A

Just minor tweaks like just center align this. It shouldn't be completely to the left when the button is center link. Something like that. I think it'll make more sense, because then the user is actually filtering if they want to filter.

H

Yeah uh the problem- I actually thought of you- know centering the those lists also those idea buttons, but they don't span out properly. That's a grid right, so it won't span out. So that's why even I had to move the elements because it wouldn't span or the space won't be taken properly. So if anyone has like a solution around this or I could reduce the font size, but that wouldn't look good also.

A

We're talking about this thing.

H

Yeah this, and just generally uh generally so now, if I center line the uh this thing, that observability is there right, so that wouldn't it wouldn't that would you know, just uh go out of the view but come down because that wouldn't it will take up, you don't have space for itself.

H

H

Okay, just align.

A

Should be highlighted, something like that.

H

A

Any other suggestions.

E

One thing which should be mentioned in the comments is like: instead of using radio buttons, we could use proper square rectangular buttons, like we have on the block page for categories or tags that we have.

E

Oh yeah, probably that might help.

A

A

Okay, something like this right.

H

Yeah that that looks good.

E

Like initially the uh though it would be on the top instead of being at the bottom, and it would be collapsed initially,.

H

E

um Also an another thing like sorry for interrupting. We.

H

E

Filter using all the three of them, simon, delesi right, it should be only one of them.

H

A

E

A

Multifilters but I don't think anyone could do that yet.

E

Okay, it is possible, but it is not configured to reduce it. Yeah, okay,.

A

The plan was to have a multi-filter, but for now it's single filters because I think what happens now is, if you click on something your url changes, so that is configured now. uh Ideally, it should be multifilter, but it hasn't been achieved. Yet.

F

B

A single rule as a mobile responsive feature, so why make it good to the mobile responsiveness.

A

We can, but it becomes too long. I think that was the concern.

B

Yeah I mean you have to sacrifice something for something.

B

I think the only way to actually solve this problem is to make it um a single row where we have deployment um security, observability and scaling it comes under resiliency right.

B

I think that is the proper way to actually solve this problem, because at the end of the day, when you add more categories, we will definitely have something longer than what we're currently having, and it's still going to take up the same space. Why don't you just solve the problem at once by making it horizontal.

B

It's just a suggestion for my handling.

A

If we did not want multi-filters, then I think nikhil's idea of using the block thing is good, but if, in the future we want multi filters and we'll have to change it all over again, so um I think general suggested single line, but I think it will become too long. What do you guys think.

H

Yeah, that was the initial problem right so because that was long um we had, I had to come up with the filter.

E

H

Because another.

E

Possibility is like we can have a drop down for the filter, but it would be two volume like on the left column. It would be the main headings that would be categories, compatibility and technology and on the right side it would be the individual content for each item that would be shorter, as well as the response like. Basically, if you go to any of the ecommerce site on a mobile app, you get two options right either there is a suppose there is a brand option and there are, on the right hand, side.

E

There are options to select which brand you want to select filter. Similarly, we could do for different desires.

E

It can be taken up as a separatist, but I think that would be the best possible solution for this case, considering we might have more categories also in future.

E

If not categories, we would surely be having more compatibility options.

A

Was that clear.

H

Yeah, that was clear, but um should I implement that now or do you want? Do you want it to be a sub? I can. I can take it up after uh we can get this much and I can take it up. I can work on that, but uh you know I'm saying this because uh the the view, the mobile view right now is really bad. So we just if it looks fine enough for now, but uh you know then I could I can take it up, but yeah.

A

Yeah, let's have the filter with this normal thing merged right now, yeah.

B

A

We can you can open a separate pr.

B

A

Because yeah that'll be a good way to go with this.

H

Yeah, so for now, do I make those changes that button center.

A

Yeah, for now, uh like we discussed just add the button, remove this from the default view and on categories this can remain as it is just uh on the first view. Let's have just the button center link and the small effects. I told you, the transition over.

B

A

B

A

And the two column thing you can take, uh take it up in a different year.

H

Sure uh so you want that to uh to be uh defaultly hidden right or should it be level.

A

A

uh If you want to take notes, you can do this in the meeting minutes if it's gonna be helpful.

H

F

B

F

You hear me yeah so actually wait. Let me share my screen.

F

B

F

Okay, so actually I am working on the measuring ui restructuring and the great view for the measuring filters is completely done and whatever changes requested by the abhishek and is done by it. But the problem is right now, I'm facing whenever I'm trying to the machine. Very structuring branch, for example, make ui.

F

Actually I'm facing this error. I don't know, what's the problem, even I post the error in the slack channel, but uh someone suggested to install the node modules again, but I did it, but it's not working yet so. Can you help me so that I can show the changes.

F

If anyone can help it out.

A

This isn't the measuring uig factoring.

F

E

uh What do you get on running? Make set up your life.

F

I didn't get you can, I repeat, it.

E

uh Basically, what do you get on running permission.

F

E

What output do you get on running npm, install command.

F

Oh npm install uh it's just showing some error on uh installing husky modules.

E

How? Because uh where are you executing the npm initial command,.

F

uh In the ui folder.

E

Okay, yeah, okay, uh what's the version of ascii that is being used?

E

Is it greater than seven.

F

E

uh If you run it on this folder, then it will be an error because we don't have a package.json file outside okay.

F

What would be the section? Can I repeat so that I can just.

E

Press ctrl c and go to ui folder. I think you have posted it on the slack channel right on the mhd chat. Yes,.

F

Yes, yes, yes same thing, I have done, but uh I don't again I'm getting the error so.

F

I'm in the ui folder right now so.

E

F

Right now, okay,.

E

uh I think that's the last topic right or do we have any other topics.

B

A

That's the last one.

D

uh Hello, I actually wanted to add something uh to the fest. So, basically, okay, hello. Can you hear me.

B

D

Yeah, so just a small thing: we just need a new image for the actual first thing of 2020 to the banner or the poster or whatever so.

A

There's an open issue, so uh I, if you are not into graphic design, I think some some other contributor you are, you are ux, contributed and taken up once you have the design ready you can publish it like. I think your work was to open the issue, but I think the issue has been created already. I'm not sure.

D

Yeah I saw that I just realized.

A

Okay, never mind uh we might need like. uh Apart from this, we during hack doper fest in october. We might need to open up several other issues uh regarding the integrations thing, so uh you can help out there.

D

A

E

You can take it offline, like yeah.

A

uh Sugar, whatever you like, I think it'll take some more time, so you can share your output on slack channel. We can take it up over there. That's.

F

Not right here uh so one more thing: there is two piece and like great it's already completed just we need to submit this is after I resolve there, and another here is about the machine app bar. So uh it's for the patterns home page. I have made it like already in some response, but some no reviews are there. So I'm waiting for the review for this issue, the so two pr need to be reviewed and great, is completed. Just need to review the app bar.

A

uh This one right.

F

A

I think he will review it as soon as he gets them.

F

A

I I see that as well, so yeah yeah just uh wait for a couple.

A

You can request for review once again. If you want you missed it, uh but it will be reviewed.

F

A

Okay, uh cool, then I think we are right at time and we've covered all topics, so uh we can conclude the call right now. Thank you, everyone for joining, see you all next week and just one request, if you guys have anything to discuss, please add it during the weekends and the agenda items, because otherwise I panic a lot during ending and items before the call so yeah. uh That's all for today. Thank you for joining bye. Bye, see you all next week.