GitLab CI/CD UX Team, 24 Aug 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: CI/CD UX Meeting (August 24, 2022)

Description

The CI/CD UX Team meeting (bi-weekly) for August 24th. Product design management, product design, and UX research get together to discuss what everyone is working on and ask/provide feedback where necessary.

A

Okay, hello, it's uh august, 24th, almost september, which is crazy. um This is the cicd ux meeting and there's a just one announcement that we have friends and family day on the 29th, which is monday and then hayana had also asked for us to just give progress on. Oh, I think this was supposed to be for q3 okrs, but it says q2.

A

um Does anybody have anything that's like blocked or at risk.

B

A

Right any other announcements or general stuff.

A

Okay, all right I'll uh I'll move into the items for pipeline insights and runner, then the the for runner we're running a category maturity scorecard for the first time ever for runner fleet. It's been going really well, where I've done four sessions. I have one more uh scheduled for next week. I think and we're shooting to be scored at complete. So right now we have that we've for those four participants, we've gotten to that score, so we'll just see if we stay there um and then for pipeline insights.

A

This was something I wanted to share with the group, because.

A

There is a lot of overlap with our group, so I'm just gonna share my screen.

A

Okay, um so we in a test report for a pipeline. If there are child pipelines that are included, then the tests from that child pipeline will be aggregated into this single report at the parent pipeline level and the problem is the jobs aka, the tests that are in those jobs that are listed here.

A

We don't like tell you, if they're from this pipeline or if they're from the child pipeline- and there can be many children, so um what I wanted to do was indicate which jobs are from which pipeline basically- and I uh I added this child badge here- because it looks like we were doing- that within the pipeline- visualization I'll zoom in a bit here. We use this like child badge.

A

um I thought it would be a good way to reuse that pattern, but what I did differently was added the pipeline id, because I assume that there can be many children and I wanted there to be a difference, and then I was thinking that you could just click on the that badge and it would bring you to that child's test report.

A

So it would be like a similar page to this, but it would just be for that pipeline. um Is there any feedback that you have? Anyone has on this.

C

I have a lot of questions which I think you, both you and nadia could answer. um So when I come to this tab on the pipeline overview page, I expect the experience to be like very similar to what I would see on the jobs page on the jobs tab right uh the list. Now um I have added a link here in the agenda. That's for one of the pipelines that's running currently uh for gitlab when I navigate through the multi-project and the child pipe pipeline like upstream downstream.

C

So what I see is uh the list and the jobs it doesn't change until I go ahead and select the pipeline in the graph like, for example, if I'm in the parent pipeline, the job list is not going to have the items which are in the child pipeline until I go and select the child pipeline.

A

A

We don't show the jobs for child pipelines, basically at the parent level,.

C

That's what I uh felt when I checked this in the morning: okay,.

D

I'm not, uh I wasn't aware of this actually, so I had no idea that we have some kind of um connection there so uh just to confirm when you expand the child pipeline in the pipeline graph. Only then we show the jobs from the pipeline in the job steps.

C

uh If you like, just look at the badge and see when uh gina like clicks on the on expanding the downstream, it doesn't change like the number of jobs inside the tab. It doesn't change at all, it doesn't expand and it doesn't give a new list until you click on the uh pipeline, like child pipeline numbers to explicitly.

C

But now I'm looking at the details for the child pipeline.

A

Oh, like that,.

C

D

Yeah, oh yeah makes sense um yeah I mean it sounds like um an issue, something that we have to consider separately. I have never heard this come up um yeah. It seems reasonable to update it. If you expand the graph.

C

C

I think what gina is doing is uh the experience that's expected, uh but the overall experience for the jobs tab. uh It needs to be updated as well.

A

D

um So I have a comment um around the around the usage of the badge for this. So currently, the badges on the child pipelines are not clickable. They're just meant to show you the type of the item that it is and um oftentimes the badges in the ui are not clickable, so they don't have a strong visual affordance that you can. Click on them and users are not necessarily used to that. So my concern would be that this link would not be discoverable um and also placing the id inside.

D

The badge makes it kind of more difficult to read in a way because it's together with the chat the world child and makes it more difficult to copy and paste it if you need to if you need to search for the pipeline, for example. So these are just like my thoughts on uh using the badge here.

D

I do like using badge for the child just to show that it's the child pipeline, because it's exactly the same. What we show in the pipeline graph, but maybe the id, could be a separate link or yeah something that the user will immediately see as a navigation item, because we do use linked ids a lot in the ui to navigate between pipelines and jobs.

A

Okay, yeah, I can play around with separating it out. I I agree. I I like the reuse of the badge just because it's already something that we use- um and I was thinking of maybe doing a full other like column that includes the pipeline id um I'll I'll. Think about that. More though.

E

This might be unrelated, but we were actually finding the opposite where we had a success badge on the deployment, uh the environment, page and people thought it was clickable.

E

Even though it wasn't because it was a badge, so I think I know why.

C

Because other badges on the pipeline page, they are clickable.

E

Yeah, so I'm wondering if you could style the badge a little bit differently where it looks like it's clickable. um I don't know what options for badges there are, but I feel like if they there is like a badge version that looks like it's clickable um and when we made it not clickable people were confused.

F

Is there any guidance from pajamas about whether or not these should be interactive elements.

D

I think they can be both okay cool, but.

A

Yeah I'm trying to think of like like issue labels. I guess those are technically labels, not badges, but those are clickable and sometimes not clickable.

A

One other question I had was um just thinking about like the idea of having the sophisticated simplicity.

A

Like thing that's going on right now, I was wondering if it made sense to maybe keep this like the child pipeline tests collapse by default, because we do that in the pipeline too, like you have to expand it to show the child pipeline. So I'm wondering if it would be worth exploring.

A

I don't know a show, hide like toggle to show and hide them. It was just a thought.

D

You mean in the pipeline craft.

A

um I mean like in this jobs list yeah, adding like a toggle here.

D

It sounds like something that could be also a filter like a drop down, because you would filter by a type of job, a sorting mechanism of sort.

C

Or the bridge or trigger job can be expanded.

C

Like the job, that's calling the downstream or the child pipeline, uh that can be a little that can be treated differently visually and there can be an option to expand it and collapse. It.

A

It might just be something that I need to like validate a little bit too, because yeah, I feel like. I don't feel confident enough to be like. Let's complicate this by adding filters.

B

Just yet, and I think gina what you can do too is come up with just two or three key tasks and then look at the impact on the flow. But I'm thinking that we want to optimize for when they're debugging.

A

So, okay yeah, that's a good idea, too! Okay and stop sharing. Thank you for the feedback that was really great, so.

B

Friends of everybody in the on the call like live. Brainstorming, okay, I know it's very useful.

A

My my last thing: I'm we can take this async if we wanted to, but I just feel like I'm taking forever creating issues with the feature that feature detailed template. um I feel like there's a lot of different sections. I need to fill out labels to add, and I was wondering if people had best practices around making it more efficient.

D

uh Yeah, I just wanted to say that I can relate and I don't have any specific tips because my process manual, but I see that physical mention templates, and I can also second, that it's very important to use templates yeah, but it doesn't really solve. I mean it applies some labels, actually some basic labels, so.

C

Yeah, so mostly, you have to delete what that implies.

C

But uh I've been talking in terms of efficiency, because you highlighted that gina, I would say uh it makes you efficient, but in a very different way. For example, it really makes people think about the problem statement when they're filling out this detailed template, so in pipe and execution when we started to get to the like very heavy backlog.

C

That was therefore there were about 3.5 000 issues, so we started to be very careful uh about like what exists there and what we need to close us duplicates and what is not valid anymore, but we started to notice that people open issues with just two lines like this is what I want. This is how it should be done like with proposal, so we started to like discourage that and every issue when it used to come to me for tragic, uh especially through that uh what issue that's created over the weekend.

C

I always used to make it a point. I still do to like request people to like apply the template and fill up the questions, and that has really made everyone think about the proposals that they're trying to put across like what is it that they're trying to solve? Who is it for? Is it just for that one person?

C

So even it feels very heavy to do that at that particular time in pipeline execution. That has like really helped us.

F

I just had a comment that I don't currently use templates. I totally get what you're saying, though vitica. I guess um I don't know if it's required to use the template, um but maybe for me the reason why I don't is sometimes we'll just have like a small bug or something that needs to be addressed, and I never want to be a barrier to document that in an issue and it can always be refined later, but maybe I'm a bit lucky that um when my team is creating issues, they usually have a strong.

F

Why um and like a you know like maybe I'm just a bit fortunate in that regard in terms of um expediting, I set up a keyboard shortcut in system preferences that will apply the kind of like 10, most common labels that I use so then I just literally just have two two keystrokes and then I have like a uh the labels and then I could just edit them from there. That has helped a bit.

A

That's really cool. I didn't even know that that was a thing I.

F

Can make a like a like a one minute, video of how to do it and um I'll post it on our channel or on ux or something yeah.

D

F

E

C

E

That would be awesome because I remember um when I had my co-working session with leviticus. I was asking about like how do you copy and paste labels, or is there a more efficient way to add label the same labels to issues.

A

E

Creating ux themes, all of them had the same labels, but I had to manually add them. So if there's any way to speed up that process,.

C

I use a very manual method, so I keep like the shortcuts to create those labels that I have based on the issues uh handy on my notepad. So I just copy paste.

E

A

Cool okay, um thank you for all the conversation. Emily, do you want to go through your items.

E

Yeah, so my first item is release held office hours last week, which was actually a huge success. It was surprising how many people we got to attend the first one um and during this office hours we really walked through like how community contributors can contribute like uh open the floor, to ask them questions one of the engineers kind of went through how to find issues that are available to take on um and then tips and tricks on how to get help. On mrs, like how to tag us in those.

E

So it was like a very helpful uh thing to do and we're planning to hold another one in september around ux front end, which hopefully, will increase the amount of like community contributions we get. um Since I know that's a big thing right now,.

C

Yeah, that's the exact thing I uh pointed out to my product manager. I guess in the meeting that release had an officer. I looked at the agenda. They like really. um They highlighted the opportunity for contribution so well and um like I'm, not sure if we have the bandwidth to do this at this moment, but yeah, I'm really happy to like learn from like how that went.

E

Yeah, I noticed uh some of the like main questions. We had were just how to get feedback, so people who wanted to contribute or curious about like when they should like create vmr.

E

Can they do it when they're still working on something, if it's still a draft and how to tag people to get feedback on things, um tips on how to find issues in like the languages, they're comfortable working on um and all of that- and we also had some questions too- that were a little off topic about how to look for open jobs at get lab. So I think just be aware that some people might be coming in because they are also interested in working at get lab and having answers to that as well.

E

Yeah, that's right!.

F

um I just I'm sorry, oh.

C

And I I'm just saying, like a closing statement like I hope, more teams are able to do something similar.

F

I'm I I put the question what our office hours in this context, but I'm I'm gathering that you, you had kind of an open conversation with users of git lab, is. Is that what it was yeah.

E

So what we did was we created a. I think it was on meetup.com, just like a release, office hours added in an agenda and then the release team kind of uh advertised on linkedin we kind of went to our older community contributors and told them that they could come to this. So we like advertised it out a little bit to just the broader community who would be interested in seeing how a release worked um to come with questions and yeah. It's like open to absolutely anyone who's interested.

E

The only thing we did learn is that it's important to have this through like meet up or another site and not just have an open, zoom link, because apparently zoom bombing is like a big thing. If you just randomly put a zoom link out there, so having uh kind of like stricter access into the meeting was important.

F

That's awesome: that's such a good idea I'll have a closer look into it.

C

E

Well um and then the only other thing is on release we're planning an onboarded onboarding focused improvement to our empty state pages, because we realized kind of across the board. The empty state pages um they're not very, like they're, all slightly different design wise. um They could have more helpful, like ctas for people just landing on them. um So this is like an idea we're doing, but just wanted to share it out, because I think it's helpful, like across all stage groups at gitlab.

E

Well and that's it unless there's any questions.

D

uh I have a quick suggestion for the empty states, uh just like a quick thought that they have. I don't know if there's there's, probably reasons why you did it this way, but um it would be interesting to see the buttons placed underneath the empty state, ui copy and the illustrations.

D

I think this is how we usually deal with those empty states, um but I I guess, there's gonna be like a table here or like a list of items and then the buttons will be at the top, but I think usually what we do is we have the action buttons inside the empty state and then once there are items to show, then the buttons are placed above the uh items list.

E

Yeah, I think, right now, all three of the empty states and deployments are look different. So I think this is kind of like getting that cta. The cdi is to be consistent across the three of them, getting like a good cta finessing, some of like the copies. So I think there's some really simple things. We can do to fix it up, but yeah.

B

E

Sure makes sense, the main thing is yeah, like you said, I think the cta on the release page is up in the top right corner, um which is kind of missing. So I think just getting the ctas in the empty state would be an interesting one to do.

E

um If that's it, I can pass over to vitica.

C

Okay um yeah, so I wanted to update about the insights that I've known through a very recent validation exercise that I ran. It was unmoderated on user testing and uh it kind of gave some good like people to how users are using their username space today and uh what kind of projects they host under there. uh How many projects they host.

C

So it turns out that users usually put just like small personal projects directly under under their namespace, and those are not the kind that are very uh engagement, heavy like it's something that they only interact with by themselves and um that's the reason like they also don't have much concerns around. What's the cicd minutes consumption because there might not even be a pipeline for those projects- um and there is no contribution related concerns for sure for these projects, and that implies that there is little or no need to control the merit consumption.

C

Then user name space related settings. I mean uh we did provide them with certain tasks in the test, but it was really difficult for them to go to those setting options which are existing today. It was not even something that I had added on the top. It was something that had been there since long.

C

For example, we are still able to see the usage quota for the uh projects which are directly under your namespace uh through the user settings usage quota page, but the way we land on the user setting is kind of here, because today, if you click on your profile picture and you go to preferences, that takes you to user settings preferences and for me that has been my gateway into the settings and that's how like I always land there.

C

I don't know if there's any other way that someone else uses- and that gives everybody an idea that maybe it's just something that's used for customizing like how the club looks for you and like not do anything deeper than that.

C

So some resonated with this uh that and the others expected the quota to be controlled through the existing usage quota tab, because it was pretty clear for them that this size coder and I'm getting to like control microrise. It has to be through this tab, but the interesting part is we never do that like so far, we have never done that. It only kind of shows you like what a consumption is like, but uh that page has never historically been used for allowing users to kind of set any configurations.

C

As far as I remember it's mostly just to view and like consume the information about the consumption. Now apart from that, um what else yeah. So this feature, uh as we had already expected, uh users mentioned that it would be more useful for uh groups and subgroups now I'll, give a little background about like why we had started with user namespace.

C

So this feature is like. Currently, we only allow users to control their minutes. Consumption minutes is uh the resource, that's required to run the pipelines.

C

We only allow them to control this through the admin view, and all that is done today is the admins are able to add, like a standard cap to the usage, so they can define like all. The groups can only use 2000 minutes like they cannot exceed that, but at a more granular level like when it comes to projects, because a group can have a lot many projects, it can have subgroups and subgroups under that and under that many projects.

C

So it gets pretty complex now at project level maintainers who are working on those projects, they would want some like some sort of control, because not all the projects inside a group or a sub group has the same amount of importance.

C

So they would want to make sure that this particular one that sees a lot of contribution from our users and is very critical to our business should always be able to run its pipeline, and it shouldn't happen that this other project that's lying parallel to it, which is not as uh much of a priority to us. It ends up consuming all the cicd minutes. That's allotted to the screw.

C

So to avoid that situation, we started working on this feature, but right like while we were having the discussion around like how we would make this happen. We realized that the moment we like touch upon groups and subgroups. This is going to get so much complicated, because then we have to uh take into account like um how there will be the subdivisions of the minutes, and uh how would we surface the quota like this much out of this much is used by this group.

C

This is what you're left with this is what you can do with it. So we started with the easiest path available so that we can also validate it. We started with username space because that's like flat, that's just one level like the projects which are directly under your username space, and uh once that happens uh once we get good insights from those we decided that we'll create issues and we'll make improvements and then we'll move to groups of groups.

C

uh I see that we are very close to time and nadia also has to go. So I'm happy to take questions on slack as well and I'll pass it on to nadia.

D

Thanks vedica um yeah, so this milestone I'm participating in beautifying ui. There is an issue where um I'm gathering all of the ideas that I want to work on: brainstorming, some solutions, so I'm trying to keep. I keep it like one thread for one improvement. So if there's anything that you would like to work on, but maybe your team doesn't have capacity or anything like that feel free to drop your ideas into that issue, and I can't promise that it will get picked up because also the engineer I'm working with, he has limited capacity.

D

This milestone, which is unfortunate because I dedicated half of my time to this- and I think he dedicated like 20 of his time to this, um but we're going to choose like the top impact, maybe also easiest, to do kinds of improvements and run with that. So drop your comments. There um yeah. I see that you have a lot of suggestions, but let's keep read only for the sake of time, uh and um another thing I wanted to share is our results from the secrets management jobs to be done research.

D

So it was meta-analysis of existing research that we have around secrets and there's lots of great insights that came out of it that you can check out uh in this issue that I linked. I summarized everything in the issue description, so you can just skim through that. If you want- and um I wanted to point out- that secrets is uh our top priority right now for pipeline authoring uh generally.

D

As far as new features are concerned, our main focus is secret management and uh the cicd catalog work that we're doing um and there's nmr for updated secret jobs to be done and um there's a lot of overlap there that we're finding with compliance and security. So we will be collaborating with those teams to make sure that we connect the secrets management workflow to management of your security policies and compliance policies, and so on, yeah and now on to katie.

F

Cool um my first one is just an fyi in case people. Don't know we have a dedicated product analyst named nicole, who we can make ux data requests to. um She can help with structuring the kind of the right questions to ask to remove bias and implementation in the code for tracking things and then also sisense dashboards.

F

She is across all of opps, so she she also works with many pms. So she's got quite a lot of competing priorities, so she did requests that when we are creating issues to kind of indicate the the urgency and the priority.

F

um But I just didn't know that uh we had this relationship so in case anyone else didn't and not much else to report for package, I'm still covering uh ecosystem uh until like november, um but we're working on some process improvements in package about how we refine and how issues come into the milestone, and I've also gotten the opportunity to speak to a number of enterprise customers, because our pm is on parental leave um and you might have seen eric and I discussing in slack yesterday now that I have those relationships with those enterprise, customers and tams.

F

I would love to recruit them, um but erica wisely pointed out that you know we should be really strategic. These are very valuable and hard to find research participants. So I just wanted to have a group discussion in terms of like. Does anyone have any ideas about any light process that we could use to make sure that we're um utilizing these to the most high value, research amongst us or maybe amongst gitlab in general,.

G

um I mean one thing that I can add is um that I've mainly worked for tams or worked with tams to like get access to large enterprise customers.

G

I think we maybe have some within like our first look panel, but I'm not entirely sure I think it's relatively low.

G

um I think it's important whenever scheduling these research sessions with large enterprise customers is since there's not a whole lot of them um trying to not overuse- and you know over leverage that group, um because you know they are so hard to access- and you know we're essentially talking to like the same handful of people uh over and over again, so that can influence the design, even if we do see them as like. Well they're, you know they're representing a large company that has a lot of users.

G

We tend to just talk to the same individuals from those companies they're representing their set of users.

F

Yeah, that makes total sense. I wonder if like um if we have some kind of process that we can also track, who spoke to which enterprise customer at which time so that we can kind of uh avoid what you are mentioning will in terms of biasing for free customers or something like this.

B

And and that's why we have kind of set up this in part. One of the reasons why we've set up the enterprise company profiles and personas is that we kind of just want to cobble together all of those interviews and touch points and then like abstract them away almost if we can um so that we can really do the like small business enterprise uh comparison.

B

um So just advertising that we have that. So if we can get consent through that form, um that's linkedin slack to record and then put those in the dovetail that's linked there. um I have it in q4 plans to begin to like put those together um and when we start on that, like in a more full-fledged manner, which isn't cobbling I'll, be like really asking for help on recruit for that, but it won't be in tokyo.

F

Oh, that's all good, I'm just wondering um you know, because I have these relationships now and I would love to just speak to these customers anyway. But I'm wondering if uh yeah should we even just have informal conversations amongst ourselves to make sure that those customers aren't needed or they haven't been kind of overused, as as will was mentioning, or should there be a more formal process or does anyone have any thoughts on this.

B

We could start in that dovetail issue, just a table where we mark who we've talked to and bring them in. I have an intention to bring in the one company that I won't name so we can share this out, but that will and hayana- and I think gina has also also met with um so maybe there's just like an informal table. But if it's in dovetail maybe it's like accessible and we can cross-reference it with the videos we have.

F

Okay cool, so I'm happy to uh create that table. Did you say you wanted that on the gitlab issue? That's about that enterprise, or do you want it in dovetail itself? I think.

B

Dovetail because then we can okay, video.

F

Okay, cool yeah: I can set that up cool.

A

Thank you katie. Can you tag I'll once you do that too, because if it's in my to-do's I'll do it okay, yeah sure.

F

Cool um I can pass over to will.

G

Yeah- and uh I guess before I talk about my section just to add on to the group discussion- I think this is something important that we could bring to the larger ux research team to talk about like longer term strategy um for how we deal with this. um But I think eric is on board with um or on point with, like how we're gonna address it. In the near term, at least.

F

G

um So the only update that I have is that I'm halfway done with my benchmarking study, so I've gotten 10 out of 20 sessions, complete I've added the videos to detail, I'm continuing to get them tagged and I have another 10 sessions over around the next week.

G

It might bleed over until at the end of next week, but hoping to have it done pretty soon and if they're not any questions I'll pass it over erica.

B

uh Yes, so I didn't make bullet points about this, but my q3 and q4 plans are kind of um set. So in a way that's good for my life, but then also just you know that I'm, if possible, like, for example, with nadia's like job to be done stuff.

B

I can sometimes fold in or like build out a research question if there's pressing needs um so just remember that we're locked, but we have some freedom within that structure and then what I'm working on is just the secrets features survey and that will help us to understand the trade-offs between the developer needs and the sre slash. Maybe security compliance depending on who we can find and we're going to field it for quite some time because to reach those two groups.

B

We know we need to go to coupon and then we need to have a long email campaign, um and so I'm sprinting towards that and then also just a yay for the team that nadia and and gina, maybe in reverse order- and I are working on a really cool participatory design activity um where we're going to kind of map out the secrets workflow. So it's still emergent, but it's exciting um and- and I think we might have a new paradigm with them so.

D

I yeah I wanted to ask about that, so I know that there's some feedback there that uh I was gonna provide- and I wanted to ask what's the latest time that you need this by, because you mentioned that you want to run the pilots next week and I'm taking the family and friends day on friday. So I'm a bit short on time this week. So maybe you can just message me.

D

Let me know, what's like the best way for us to collaborate on this or point me to an issue, comment or thread where I can jump in and help out.

B

Okay, I think you can come in after the pilots we'll use the pilot see if it stands and how it looks more.

D

Okay, okay sounds good yeah.

B

With the secret features, we might need your your feedback. I think we're actually good on that with the survey stuff and I think we'll cover okay. Okay, thank you.

D

Yeah, well, I will catch up with you on slack about that as well, too. Okay,.

A

Erica, do you want to do your? Oh, they they're read only derp. Well, did you want to voice it? We have four minutes. Okay,.

B

Yeah, so um there was a paper posted yesterday in the security research channel and um they said it wasn't a good paper which I think means it's like not. We can maybe follow it, because it's not that technically complex and good, um but I actually felt found it really helpful because it takes a few competitors and kind of talks about their different roles and access and then gives an overview, and it gives um not in a way that we should feel like concerned like.

B

I wanted to be careful like it's, not that they've found a new idea about security breaches, but they basically go through and explain how, in these different platforms, also including our competitors, secrets might be leaked um so yeah. So that's not like a pressing need, but I think it's a nice resource- um and I also did this thing where, when I first started and kind of saw that security was one of our product focuses.

B

I was watching like dev suck up conferences and taking notes. I tagged some of you early on you. I remember anyway. I turned that into a plus white papers, and so I'm like taking notes in that issue. As well,.

D

Thanks for sharing, I think this is exactly what I need to dive into.

B

Yeah and if anybody ever wonders like what do we mean by hard code secrets, it's like right there, so we can. I think this will be a good resource for us moving forward. Yeah.

A

I have one one other question for us before we wrap up. Would we um I'm just thinking about the order that we go in when we're going through this meeting?

A

Would anyone be interested in swapping maybe next time so that people near the end have more time in the beginning.

A

Seeing a lot of head knots.

D

Yeah, I think it's a good idea how.

C

About putting research first and then design and quarter change.

A

Yeah we can swap the order of design too yeah.

C

um I've been doing it exactly the opposite of what it is today so yeah. I will start.

A

Okay, cool all right I'll. Do that next time, thanks all right thanks, everyone have a good day thanks.

F