Okay, so I think we can start with portfolio management because that's a lot easier because that's like literally you know at for now one front-end developer right and then and as I mentioned front-end team is the bottleneck so I might like if we have time at the end I might want to talk to you about that like about future and plans like that but for now let's just get this part done so I already went through this a little bit with the team with the portfolio management team but if you look at what you see on my screen here let me zoom in a bit so if you look at everything until the end of the year you can see it's like really obvious stuff that people would have asked that why don't you have that right so like closing an epic we're trying to do make a lot of progress this iteration and then try to wrap it up in like one or two iterations so you see like system nodes and stuff like that that we're not doing now but like system those notifications stuff like that will will wrap up in future iterations but that's that's what this is make epics easier to use that's like promoting epics oh from other places yeah promoting an issue to an epic so that's like something making it really easy to do creating an issue from an epic so when you click plus here right now you can paste an issue but you can't create an issue right away so that would be super helpful and so and things like that just to make it easy and so the quick action to add issue to it so we already have these two but these are like like tying it up in a nice bow right so we're releasing like we're releasing this version and 11.2 and then this is to make it like even more spiffy so again these are like small well they're not they're not new features I don't think they're small but I think they will require time to do so that's why if you look at it it's it's to the end of the year right so there's nothing new except for like close epics which I just mentioned and even this one we're like quote-unquote done already this one is the one that implements this feature here right so it looks done but then there is still like this for example there's there's some back-end stuff that that the folks wanted to do so right now says 11.6 here they wanted to show the actual milestone so there's some like making it perfect sort of deal here so that's why if you look at this I'm trying to tell you that I'm being very conservative right so you can see like I'm saying it's a lot of stuff there yeah there's a lot but I'm saying that there's like another PM might say oh we have like a whole quarter let's do something new and awesome right so I'm being super conservative I'm saying the new and awesome quote-unquote new and awesome is not really new it's like I mean it's new in the sense as a new functionality but it's pretty obvious it's like just closing so basically you're closing gaps so the experience yeah exactly exactly yeah that's that's smart I'm gonna say that smart yeah well I mean I don't know if it's smart but it's we wanted to do a lot a lot of this but like my current plan which you know you can say like you don't want to do this or whatever but is just to do the closing and then you know notification stuff that we've started and we wanted to finish and then sorting as well like sorting here this type of thing making a shirt I'd say sit a back end and stuff like that so there's like one or two more issues I think right so if you look at that so sort direction to the back end back and in roadmaps so yeah so this one for example it's implemented oops like start data end date and then we want it to be consistent so that this these two would be merged right and then created date and last updated you can sort in both directions as well and then so there was an issue if you notice in the issues of merger quest that was going on for a lot and there's like a lot of chatter so basically once that settles down I expect we can bring that exact same design and implementation yeah I'm following that now because a fat is out so I'm gonna be monitoring that to review and I just assigned myself to that issue so yeah yeah like yeah I'm fine if we can't get it like I know it got delayed to 11.4 and then if we can't get it that sucks but it looks like it will be okay awesome so other than that the new things I can go through this really quickly I'm going to slow so let me go a little bit faster because we have like the rest well maybe not not too bad because the portfolio management is like new functionality maybe it deserves me a little bit of explanation and the rest of the functionality and plan is more obvious like they're not super new-ish stuff but this one move forward backward in time in the roadmap is just scrolling horizontally and vertically and then you can see see more things so I can scroll down and scroll up left and right so on and so forth vertically is already possible is that what I'm saying yes and so that's just vertically is definitely possible but I wanted to include it just for designers and developers just to see like if there's any leftover work we need to do for example when you score horizontally I expect new epics to appear on the screen right yeah but when you scroll vertically right now I don't think you need that because we load everything on the screen all at once so we might want to change that existing functionality to to be more like pagination or infinite scrolling so if we're doing the left right horizontal maybe there's a good reason that we can we should adjust up down as well yes it makes sense that it's visible yeah so you don't know like like right now if you for example if you do this I think it loads everything right so it takes a while hello yeah you can see it loads literally everything right so this that's not scalable right so right so so that's that's that I wanted to put like a placeholder there and so you can see I just put like that's starting in December and goes for a whole quarter so again being somewhat yeah but it's good to know it's it's one of those things about laying down the bricks to allow us to get well actually now that I'm thinking it's a good thing we're having this call today because the people from from back in our pinging me regarding using GraphQL and what I'm thinking is that we're gonna have to have a proof-of-concept first just to kick the tires around but I think it should be ready to get started on this part and maybe this is a good candidate for us to try it out like a feature you mean to as a feature like fully fledged because the point you're familiar with GraphQL right why I mean I've heard about it people saying about it I think you're not so basically the big the big the big aspect of it is that front and we'll be able to do calls to the back end that the back end didn't necessarily specify a specific endpoint for that interesting okay that makes the next front end easier to develop because it's just like you're working on the for instance you're working on the epics right you want to have an epic resource exposed we can ask anything there is to know about the epics anything okay regardless of whether they have specified a specific endpoint okay sometimes you have these issues that oh we're gonna have to add a field to the back end API right with GraphQL that is no longer needed oh so you just need to define the model the resource exactly that you just suppose and everything oh okay interesting okay then we just ask we send the request like I need a B and C and it comes back with a B and C fields that's that sounds like a pretty interesting it's pretty good yeah well yeah it might be good good good to have this call by the way yeah yeah I mean that's exactly what your point but what are the points this thing here yeah there was a lot of conversation about like just getting the dates you know how it says 11.5 right now but in Pedro's original design he wanted the dates as well for the hover which makes sense so you can see both dates so I don't know if GraphQL would help with that but that's like one of those small things that like oh we had to cut scope because it's another sexual workflow yeah if it's not available the API then that wouldn't be a problem because it's always available exactly yeah yeah that was exactly that was exactly it we have to transform it on the front end right right right yeah it's cool so okay so that's this one and then like I said I'm being super conservative in that another reason I'm being I want to be conservative here is we're still I don't know what the future of Gillab is in terms of process but you can see there's a lot of issues not represented on this roadmap meaning these are like the big initiatives but like the small bug fixes the small features I'm trying my best to get off features major features like to be in the roadmap so that this type of conversation is not unrealistic that's the idea there so I mean isn't that like always hard because apart if unless you have cases like we have the merge request refactor that I was like spitting a lot of regressions I that's not really a way for us to bundle everything in one topic usually there's like random regressions here and there bugs right well I mean that one topic they might be able to put it on the roadmap as long as yeah as long as there's a feature I will try to put it in an epic and expose it here like bugs yeah there might be even like big tech that things are UX polish things that we can put here yeah I know you're totally right those things are like how do we represent those to me if that's more like working with you and Sean and saying like oh you know approximately every epic we spend like you know 50% of the time doing non-major things or so so that's why again I don't want to be too prescriptive here and then again like nobody's holding us super accountable right now that these are not slipping but these are just you know approximate plans but you know thank you much and yeah so that's what this is so this one is the a bunch of these are work breakdown structure so a big area when we're in talking with customers is doing sub-ethics essentially so when talking with Sean and Annabelle they said like a better way to talk about his epic relationships instead of sub-ethics so basically parents basically parent children relationship yeah so if you look at the idea here is that if you take this concept here as you see so that's like sort of what but obviously it would look like do you have an epic yeah children epics and you can go on forever depending on the final design but just getting that structure is super critical for customers are super useful and a lot of competitors have it but once you have that it will take a long time just to get the rest of epics and roadmaps if not issues and merger costs consistent with that paradigm and so that's like that that's like at the current rate that's gonna take us like all of 2019 or most of it right so so you can see for example this is just the basics so the back-end API on the epic page itself to do all those things that you expect right and then on the roadmap itself I think I have a picture here doing be able to do this right I group it yeah exactly so you click one one here and epic and then it expands out yeah so so basically once you have that structure like it just becomes it's not really a designing a new thing it's a design problem in the sense like what do you design to account for all those specific cases and that's pretty much the rest of 2019 so okay can I can I ask you this word this work breakdown really go down all the way to the issues and emerge requests so epic like just like you have epic relationships having relationships and issues and merge requests like having parents that's right so right now with so everything that I just said is just epic with relationship to themselves and epic relationship to issue we already have obviously which is right now when you have yeah exactly so I think your question is issues themselves so this is a this is an issue issue yeah issue to issue we have one thing which is related issues which we already have here exactly and then this epic here which I linked to from one of these ethics is a two additional relationships which is blocking issues which a lot people has asked for and it hasn't really elevated to like super high priority yet but you know I've at least documented here and then you can see approximate timeline here right and then some issues which is like parent child yeah and then so this would be immediately applicable to the what you and Sean want to do right like up the weights product thing in the weights so that structure I see being useful and solving those use cases I purposely left it out of like this view of portfolio management even though we could probably get the same team to work on it but right now I wanted to focus just on ethics and cleaning that out and then and then maybe roll in that sub issue stuff because we can definitely go to a customer and say oh we don't have some issues that you know you can sort of as a workaround still use sub ethics yeah yeah there is a workaround it makes sense to do the epics first I'm just wondering because it's such a powerful concept because if you think about it once you have that relationship you can start revealing that those interdependencies like just like the one you were mentioning if I change the milestone of an issue of a merge request updating the issue the same thing would be automatic for and actually expected for parent issues that sort of thing so a lot of things can be worked there and make things a little bit more integrated and I definitely see the value in that so good that that that's totally the idea and then so the rest of these are filling in the gaps I guess it's so like yeah once you have that then you can inherit children started end dates which are just one issue for now but I expect this to be expanded so that's why oh it's one issue you can do it in a month like no that's not gonna happen right so that's why you can see like yeah two of these two iterations I've scoped it yeah sure once I'll come back to this one but then maybe there's one there's one one concern I have sure that is that you if you attack the inheritance is of each property one by one you gonna be a little while until you have like everything covered I'm wondering if we shouldn't have a discovery phase to see can we have a generic approach to inheritance like all fields are inherited except they are explicitly overridden but that needs a UI that needs a UI work right just say this is from the parents then a button to override it and then you just do that so so let me let me as a comment right yeah I'm gonna put in the description because I don't animal still working on work breakdown it's basically just to one participant it's you right right and nobody else would be notified as discussed nobody I know I'm gonna put it here so when we come like when I like asked the designers to start thinking about this yeah so the idea is just to consider considers evaluating a generic approach of inheritance that every field gets inherited from the parents except overriding just for example so like like labels labels labels assigned needs etc. when these are applied to a child level does it make sense to somehow exactly those are the one of the questions so it's just to have designers think about that problem and then they will come up with yeah I know that's that's a really good like perfect perfect yeah yeah we should definitely design that because like yeah I always don't like how issues and merge request are like out of split yeah that that's a that's a great point okay that's that's inheritance and auto close is again sort of obvious if like all the issues are closed and you want to close epic searching in epic so that's mostly back hold on hold on a little bit the auto close epic you have like what two cycles one two three I have June to August so that's around two cycles okay I'm trying to think what sort of complexity you expect there that one is all an epic should be auto close of these yeah and immediate like it's just triggered so if anything I would think this is more back-end ish oh it is it is I'm just wondering to have three cycles and sign to it it's kind of like meaning that you might have some complexity but I would I would expect a little bit less that's fine let's just be conservative yeah no no exactly so yeah that comes from the conservatives it's also more of a Sean department so I don't have visibility on that yeah I was just wondering but that leave it be for now yeah I was thinking a lot yeah yeah yeah yeah no no problem most of these are like around three cycles anyways and I just having sort of like staggered here yeah and then so Paul I'm just jumping around polish epic relationships are like system nodes quick actions and creating a child epic from an epic so that's that's wrapping up the the work we've done structured there right but if you look at I don't know I don't know if this goes further out I don't think so and then the rest are a little bit weirder so this one is just showing weight information so this is less about work breakdown structure so but this is weight information yep on the epic itself so I'm on an epic and I want to like but what it's like we already we already have the design for boards right like so we could we might want to just inherit that design the weight there yeah exactly I don't know if the designers want like a percentage complete and stuff like that so and then we also want this information on that might have a market yeah yeah so something this right I made it like a long time ago so and then this one is getting the I don't know if you know that we have a like bug that's been there forever it's annoying but this is getting the actual milestone on the roadmap right pager has some designed I don't really like them yet one of the things I don't like so far is I don't think he's been able to indicate start and end date yet of a milestone and then so this is my rendition which looks hella ugly right so but I think we but why I added this is to indicate the information I think we should add to the roadmap which is start date and end date of the milestone and also the weight of the milestone so the meaning the reason is that I haven't solved like back in the front end yet oh no I think this might solve it right you can just filter by back in front end but then some ethics at both so it's weird but the idea here is the exact problem where we're experiencing right now the problem is that I'm saying oh just look at this roadmap and just like tell me if this is reasonable right and then let's like it's sort of a really hard ask for like the engineer manager right hopefully this is a little bit more reasonable in that you can actually see the milestone there and you can see those some weight already so then you there's a little bit more truth to this well it still depends on the issues having weights right exactly these are the ones are going to determine the weight of an epic although yeah if you heavily if you're doing like pre-planning for like three releases ahead we can do like a broad scope weight right on a bundle of issues so it is definitely useful to have that yeah but yeah so to me this isn't this just needs a lot of work in terms of design not just visual design like just this concept yeah what I wanted to illustrate here is that right now when we're looking at a roadmap view we're losing milestone and some weights per information and so for example one thing that's this and then with this design or it doesn't make sense a hundred percent is that this milestone say 11.2 even though it's already filtered by this label you might have some issues that are not in any of the epics on this screen so it doesn't really make sense right so if we take this vertical slice it doesn't really represent even if this is like you're saying like oh I'm gonna do like if this is uniform distribution and I'm gonna do a little bit of like none of this is like perfect so I don't think it needs to be perfect in a sense like everything is chopped exactly precisely but at the same time I think it might be a needs to needs a little bit more realistic than this so but in any case this is like scoped here for work to consider that right we need to somehow incorporate I'm pretty convinced like milestone information but is it just literally just gonna be just vertical bar storing milestone information and we don't show like a capacity weight information or does it include it so I'm not sure right I'll live that for design but I'm a big fan of progressive disclosure so you have like a small tip then you click on it and it'll expand right that sort of thing so I'll be in sync with Pedro as well to yeah I mean this is like all the way way and might even be different people but doesn't matter yeah exactly so okay but that's pretty much it so portfolio management yeah so I don't know if you were sort of staring at the dates I have been taking a look at that so what I'm what I'm thinking already is that there is some preparation of work that we might do especially regarding or at least making sure that we have GraphQL as soon as possible sorted because a lot of these things could benefit from that and and then in terms of front-end from what I see let me see yeah I was thinking if there's anything that needs to be rewritten or refactored to have any of these things in place so I don't think it needs to but there are some places that might benefit from because I know that Kushal mentioned some refactors that could be done it's a real quick one sorry I was on mute I think you wanted to do refactor for the sidebar if not the entire epic I think sidewalk me the entire epic I forget there was one issue yeah I have to go back and look at my notes issue boards now I have to go back I don't have it right now but I know that he mentioned something so I will go back to my notes later and see what what what could be potentially required to have a big rewrite and what it means just like we just have to account for it which might have to adjust or not the dates but it's definitely good to know more or less what's coming and then on my next one or one with him I'm gonna be like thinking in specifically go ahead and push him to to get that like somewhere like just go play it does detail but like at least get some issues going sure exactly exactly I have one more a pixel okay yeah so it does bleed off to the edge so I have one that goes on that starts in October and then goes to 2020 so that's swim lanes got it and so if you want to click if you want to click on this issue actually have like this really awesome flow that I shared with folks that shows you like from a use case perspective like if you want to plan something at a high level and then track it over time estimate and stuff like that and you're really focused on ethics what are the like what are the steps set by like a product manager does this and then you talk with stakeholders and engineering design you collaborate and then you do high level planning and then you create sub-epics to scope it out and then you do weights and then you use you do assignments in the boards and then you do this thing in roadmap and like and then becomes bottoms-up planning later on so this is like a flow of everything and then so all these all the all the work required to make this flow work is mostly portfolio management yeah that's where it came from but that's why a similar swim lanes come so late right well or could we have some sort of MVC of a swim lane before all that well I mean this this flow is not intended to say like we build in the order of the floor in order right it's not to do that right but it's it to mention the gaps and and I you can people can disagree including yourself but I think what like this particular feature is a lot harder I don't think it's super critical just yet and then so that's why I put this further out in the in the in the roadmap and so the roadmap is really focused on whoever it is work breakdown structure first and then looking back to adding swim lanes on boards and then what's sort of interesting here is that it's the reverse of what I just talked about so if so I'll show you this so this is a roadmap view and then you see milestones right and so map view is sort of the base visualization here the timeline is time in this roadmap view is is like time as in like calendar time right right step-by-step it's linear in that each unit of centimeters is corresponds to linear yeah a milestone Rome milestone board yeah board is sort of different because people could have different size milestones yeah and then you again you see work but you see issues instead of epics but now what you do is you introduce the epics into the milestone view via swim lanes and so you can see how it's like sort of the the yin and yang of this view where one thing doesn't have the other and then now you're introducing it to it so like my vision is when you combine these two it should help with design or maybe you can somehow merge these I don't know yet but yeah that's my preliminary maybe I'm not get maybe I'm not getting swim lanes concepts because my my problem right now with boards or at least one of the things that I've been hearing Tim struggle with is when we jump to the boards it's not like there's no way of seeing progress on the issues like we have them on the lists of assignees or something but some of them are already in review some of them haven't even haven't even been started and that's not exposed so I thought swim lanes would help that but maybe it's not so what is it well this is also a problem that Pedro highlighted like our boards are so powerful and flexible that it's not prescriptive which I like exactly yeah but this is one version of like in my crazy world yeah you can create a swim lane for everything you can have a milestone swim lane and assignee swim lane a label and then an epic swim like so it will be possible it will be right right right interview yeah exactly so my point is that like a list is just a dimension and then now we have three things that we can put on this list and you can have like an epic on the list too like nobody's stopping us from doing that exactly and then so my crazy ideas like I haven't told this to like Pedro I don't even have an issue is that a swim link could have the same four dimensions I mean this would like make Pedro really annoyed and angry and whatever so and then like I don't think we need to have that conversation right now so that's why I didn't bring it up but like to me that's how I think of boards it can be super like flexible style yeah exactly yeah right so I don't know if that's the future boards like Pedro I don't Pedro I think this agrees with that so I could be convinced either way so right now at least it's flexible enough to have three types of lists right and he's doing he's doing discovery there exactly exactly okay so that that makes sense I let me explain why I raise this is just because I feel like that's such an important like improvement so that they are two major improvements that I feel the words kind of like need before 2020 now you're thinking like me like two years and yeah because that sounds really far ahead right away and what so one of the things that I've been struggling with is the logic like not having a knot for example operator like exclude certain labels so imagine all issues that don't have deliverable right that's not possible and that and that thing of the status which I would say that it's some of the most things that I'm feeling but I'm fine with following the roadmap of course that's not the point I'm just saying raising that for you for as yeah no no no no you can definitely influence the road right right so but in terms of that epic actually reworking everything following the discovery it makes sense to have it after all this so okay okay I think for portfolio management we're kind of sorry you're like are you okay like do like again I know it takes a lot actually put accurate effort estimate like is this like radically ridiculous no the only thing the only thing that kind of popped right away into my head my eye was the autoclose being free cycles the rest I I do think we should plan for that because there's always like some lingering small improvements that we can do in the third one right but and again we'll as we get closer we'll get more accurate yeah so but for now I don't necessarily see any things what I will do as a homework or after this call is check that that need for any refactor in this sort of benefit that's great I'll get back to you I'll be back to you once I have that information sure and we can reassess yep yep and then we'll just like my plan is that we would just insert it and then we just shift everything yep yeah we would need a feature for that right and then as I said like this is the type of thing I want to keep sharing with yoga and other stakeholders and say like we need more capacity if we want to if you guys think this is like a really awesome vision if you like senior leadership of Gillab think this is an awesome vision of plan if you think it's strategic to do it sooner then you know let's get more people working on these things so yeah for sure that's the idea so if I if I close if I remove this becomes a lot crazier so now you would want to remove portfolio management yes we don't have I don't exactly the future but that's actually one of that that's actually one of the ethics so that's exactly what you said the logic right yeah yeah but let me just go through this really quickly or maybe this is the part where you can say like no we'll never do that like a lot longer so so this is you sort of have to just filter about filter away portfolio management which I know is really hard yeah so if you look at so this is these are wrapping up the performance is back in we talked about this we talked about this we talked about this this is the one that I'm almost like not caring anymore I mean I do care about it but like the gray area I guess yeah and then on the front end side you're managing it and then on back inside it's it's one it's Mario so it's not it's not like yeah so there there's it's not a huge impact on the capacity burn down charts so there's a couple of crazy ones here so let me scroll right sure so burn down chart in boards is I have it scoped to the end of the year which is again pretty conservative and then now gets becomes hard because then you're supposed to look at everything at the same time but it's fine basically the idea here is to put the burn down chart inside issue board because you can do it here let me that's this is the design as you can see right but the idea is that once you click the edit button you already have the scope of the issues and then if you've if you've chosen a scope that uses a milestone then the burn down chart is well-defined right yeah so so that's the design here and there's the idea is that then you can use a burner check directly on your board and you can use it like like agile whatever and then you don't have and then it's actually useful like for us because we are we don't care about the rest of other people's or like for you you would like one of at least two burn down charts yeah I don't like yeah well I mean I mean both between teams and then between boot back and in front of you might four burn down charts right so but that that's the idea for that makes sense okay got it so again shouldn't be that radically different extra effort it's nothing new but you know it takes some finite work so that's still do we have that feature now no no okay we have burn down charts just burn on charts but we do not have it in board at all we have it we do not have it in the board no but you have it elsewhere oh the burn down chart is at the milestone level oh yeah sorry I know a lot of people don't use milestones so I don't burn use on burn on trust so that's why even at gilab people don't know about it so that's totally fair so we do have this feature and it's here so this has been implemented like a while back like I think late 10.x we implemented this okay so just wondering I'm just wondering because I wasn't aware of it so if it had to be implemented from scratch there might be a bit of a problem but if we can reuse it then it's less of a problem so yeah so the current thinking is to reuse the code obviously there's some work that I will hopefully scope out in the next couple weeks so if you saw the slack conversation we want to do charting in general and so I wanted to clean up burn down charts because that's a pay chart implant and we don't have too many charts in plan so it's not that bad which is like monitoring team has a crap load of charts so if they wanted to redo charts it sucks and that's what their plan is but basically the current thinking that in talking with Josh PM who's PM like for like five different areas which is crazy I think at least three I don't know five scenes I think he's like meltono monitoring this whatever so but then so meltono is this crazy data science project that I sort of know what's going on but not really but according to Jacob Schatz a really cool idea which is the working plan is that we will take some libraries inside front end libraries from meltono that he's working on and make them dependencies in GitLab the product and so that we will be able to leverage that in creating charts in GitLab and we'll have a consistent way of creating charts in terms of front end logic right and then that's the conversation we're going to have in that chat in that scope see what is the best way I don't necessarily have an opinion right now but we need to learn more about it exactly exactly so so there's some discussion there ongoing but so that that might imply this where so so I totally expect like these will change but that you know that's fine right but for now we can look at burn downs is just like exposing them on words exactly exactly that's actually cool feature that's yeah yeah no no I mean the fact that you don't know about it is a failure of us building this and it's being useless so like I'm recently focusing on the plan side as a manager right no no I'm not I'm talking about you as a manager not using this tool exactly a problem right it is so when I joined GitLab in late 2016 this was this EE feature was like in the double digits of EE like our EE issue numbers I think are four digits now or three digits double digits so this is true the people want to burn down charts forever yeah and then when I joined I think that issue was like one or two years old and then we finally did it but like I wasn't really a good I don't claim to be an amazing private manager now but I was definitely a worse one before because we like I really wasn't doing the like thinking really hardly hard about like like plan is the plan and create are like the best product areas because you will be forced to use them so I didn't think of a way to like how we develop it and use it ourselves right and so this has been lingering forever and it's a finally like over a year later we have a plan to be able to use it ourselves so that's cool yeah just I had an issue that had four digits and I was excited that's how new I am that's amazing yeah this has been been yeah people have been asking for so we finally did it Pedro did the design way back and then so we have this I mean we want to bring it to board okay let's let's maybe rush a little bit so that we can have time yeah it's fine we don't have to finish it but so to burn on channel board there's import your issues to get that issues which is yeah I will go faster but it's basically a quick CSV import so that's idea it's more of a back-end effort it should be a back-end effort minimum front-end in that UI to just upload a CSV and then this is milestone parody of project mouse this is sorry this is literally one issue right now which is oh no no no it's not sorry it's this is the existing cleanup so there's two more issues so so this is pretty much done this is scope for this issue a milestone or 11.5 and this should be a back-end issue mostly I think and then this dynamic milestone pages do you know what I'm talking about there not really so I heard about it on C on me on meetings but not really clear right so this is that's why it's like really confusing that's why we wanted to get it so this is just really quickly so this is no this is fine if we go over this is a good use of time yeah I actually have a meeting after that's what I'm saying okay yeah yeah no no we'll end right on time so there there are a bunch of milestones on this page I like if you look at the my bottom left-hand screen you will see that when you do this you notice how it's it's searching for the milestone yeah right so when you click on this this is a dynamic milestone page I pretty sure in that a group milestone is like a native group milestone object but this one is actually there's two projects inside GitLab that are called these things yeah both of these projects if you click on them and you click on to their milestone their milestone is called v1 0 and v1 0 8 so these are two separate milestones in the database right one is to the get a lead project yep one is to the give up runner project but if you look at this view this is a quote-unquote dynamic because when you click on it it creates this dynamic page which sucks in these two milestones which then sucks in all the issues from all of our so so this is like like somebody invented this before there was group milestones and you can see how that makes sense right yeah because you just want something to group multiple projects together is it matched matched by the name matched by the name okay it may sense then it doesn't make sense yeah and then so it's really messy if you think about it and it's matching name and then if you want to use re-use the name then you screwed when you open this I was thought oh but they're related no yeah yeah so that's why it's confusing right so got it perfect so that's why we wanted to get rid of this and so I know so it's removal of code removal of stuff exactly the the functionality so redirects that sort of thing exactly so hopefully that's not too bad managing multiple boards that the starring thing yeah that's the starting thing I'm pushing Pedro to help design about so not a lot there yet so this will probably push it out in the future analytics chart dashboards that's that's the board stuff I was the stuff I was talking about so I actually don't worry about the dates because this will probably change so that's not much of that award emoji cleanup there's a lot here so I'm just trying to put one or two every single iteration yeah but these are all small right so emoji I think extending that standard order emoji tabs so nothing huge there yeah this one's a big one move default description templates out of project settings so if you go to a project such as this one if you go to a any project then the this I don't know if you know this the description template is here right you have this description template here right yeah and you have the same one here the the non-default one is source control the default one is not source control and you like why the hell is that the reason that happened is that we if you look at the history of good this is like before my time this is like like seven dots something already got some is like a long time ago we created this feature I think in star before it wasn't called starter because we just had enterprise back then and then and then later on we added the source control version so but people because we move so fast again that we never cleaned that up right it's obvious so the the scope of this work is to get that into source control out of the project settings into the source control so there's a lot back and work well I think it's mostly back and work right if you think about it but is it like just removing it from the settings and asking people if they want to do that do it through source control exactly and then if you go through source control we'll have like some default it'll be like default and like it will be default MD will be the one that reads from automatically but the reason there's like four issues for this is that we're doing like a migration path and we want to put like a lot of messaging and make sure that people know what's going on because we are changing existing data so that's that's idea so in terms of actual work I don't think it's it's a lot especially for front-end but there there is some some finite work there version issues issues versioned issues and merge requests is right now has only one thing but already this is like in the future right so this is pretty this is pretty it'll take a while I don't know if it's this should be one issue but basically it's just doing this like you see the comments yeah basically on the system notes just having an expanded I've seen this before yeah yeah so I'm actually maybe this isn't that bad me again a lot of front-end to do this one yep right right right now yeah yeah yeah so this is just system notes not not description yet but isn't this like versioned versioned issues and merge request description because it sounds like you'd have like a version one of an issue version two of an issue which is not what oh oh I mean it's a bad yeah maybe I'll just change it right now so this is this is the description and not the comment sorry so why don't I just change this issue and merge request description yeah yeah yeah so so that's what that is again that's one issue yeah that we talked about this is this is the one that we just said or you wanted right so all these are now in 2019 as you can see right I can live with that I can live that nice nice it's just literally just these two right so I anticipate the developers will say like there's a lot more than just this but right now we we when I joined like maybe a month or two after I joined we implemented this UI this thing here yeah we implemented this on the issues and it was like really terrible in that there was like so many bugs factor that I was you we just saw the discussion on the whip thing oh that one I'm like why is that taking so long but I'm like I'm not gonna add more like yeah but there's I don't want to I don't want to annoy people by like intruding into that issue that's a great right right but we want to we want to so that's basically we've already learned that we need to reflect to that part and maybe that before we get to do this but not in the logic right yeah yeah otherwise just gonna keep adding to the technical debt right and that's what like when we whoever designed this like it was like maybe they designed it like a summer before I joined in 2016 yeah I'm pretty sure they had like not like this logic thing it was there forever and then like that was one of the reason we have like this thing here because it's like it's a really good design to add the logic operators if you think about it right so that's been and people have been asking that for like two years or more right so yeah okay we're getting close is there any like last thing that I should be aware maybe we can do another session or wait for Sean but I'll let you read read through the rest I know I'm really happy I got through the portfolio management ones because that's like I can focus on that especially with you know but yeah why don't I let you just what we can have another session next week because this this week I'm gonna check with kushalini and you have a touch base next week again just let's do that let's do that let's do that okay cool and then yeah so I'll let you read through the rest of these or they're actually most of them are portfolio management because the rest of these go to the end of 2019 and then there's other crazy like custom fields and don't like you see this thing like it goes on forever like page with this arrow right or this thing that means it never ends right this is what that means there's no end date so it means infinity right so it seems like the reason the elastic search never ends the reason to me it never ends or I don't have confidence in it because it's so technical that I don't know what the hell Sean is talking about like like it's him and Nick and Valerie and then they're like these things and issues like and then they ask me questions that I'm like can you like explain to me what this means and then like I'm on calls in English exactly so when it's so technical it's really hard for me to get a grasp of like when and what and I keep asking Sean and like he does like a decent job of like doing estimate of then and stuff but but there's like so much work and then it's not just development work I think there's a lot of like system like other teams has to get to work on that thing hey Demetri we're just wrapping up the call so okay but yeah so okay thank you Andre I will thank you very much Victor I'll talk to you later this is really useful okay okay right see you have a good day Demetri I'm recording this call so I'm gonna stop this call and come back in


Perhaps you are a relatively new backyard poultry owner, or maybe you have years of experience. Either way, at some point you may find yourself with a surplus of eggs. Wouldn't it be wonderful if there was a way to preserve some of your farm fresh eggs for use later in the year when laying may decrease or stop altogether for a short period of time? We have good news for you. Freezing eggs is an easy and inexpensive way to preserve your eggs for use later in the year. We are going to discuss freezing mixed whole eggs in this presentation. First, break each whole, clean egg separately into a clean container. As you can see in the picture, I used a clean jelly jar for this demonstration. Examine the egg to ensure that it is in good condition and free of shell fragments. Then you can pour the eggs into a large container. The next step is to mix the eggs. The goal is to mix thoroughly while incorporating as little air as possible. The National Center for Home Food Preservation suggests adding salt, sugar, or corn syrup to the mixture to help improve the texture of the yolks in the final product. If you choose to include one of the additions, make sure and consider the future use of the eggs. For example, I use salt when I put up eggs for scrambled eggs. The amount shown are for each cup of egg mixture. The next step is to pour the eggs into a freezer bag and freeze. Make sure you label the bag with the number of eggs, the date, and any additives that you may have included. The eggs will need to be placed in the refrigerator to thaw the night before you are ready to use them. Frozen eggs should be used in dishes that will be cooked thoroughly. Again, you should consider how the eggs will be used. In the picture, I have a freezer bag with eight eggs. I chose eight because that is the number of eggs that my family typically consumes for a meal. You may want to package your eggs so that you have more control over the amount that you thaw at any given time. A good way to do this is to portion the egg into an ice cube mold.  Each cube in my ice mold holds about one and a half tablespoons of egg mixture. Most instructions say that one egg is about three tablespoons. Therefore, I know that two of my egg cubes are equivalent to about one egg. It can be difficult to remove the cubes from the tray after freezing. Running just enough warm water over the bottom of the tray to facilitate removal makes this process easier. However, the outer surface melts during this process. In order to prevent the cubes from freezing together in a solid mass, I place them individually on a baking sheet covered with wax paper or parchment paper, and place them back in the freezer until they are thoroughly frozen. Then, peel them off of the paper and put them into a freezer bag. Again, the egg should be thawed in the refrigerator and used in dishes that are cooked thoroughly. Enjoy! This presentation was narrated by Danny Reems, ACES Food Safety and Quality Agent. It was created with work done by the National Center for Home Food Preservation. For more information, please contact me at ACR 0087 at aces.edu or you can call me at<PHONE_NUMBER>. You can also visit our website at www.aces.edu.


So can you hear me at all I can hear you perfectly James right? Okay, so I'm gonna I'm gonna tell the world that we are broadcasting now And also actually use my phone to check. I can find my That we are live YouTube You can do what's up to you James. Do you want to do the welcome? Yeah, I can do it. I just wanted to check. Yeah, no no go for it Since you're just you're talking first Okay, so let me double-check that get lab is streaming now And yep, it looks like so if I can see myself Okay So my phone shows us streaming. I will I will ping this to our slack to let people know that we're live I'm gonna a Sarah. We're and Daniel. We're already live by the way I'm gonna check my screen share works Yeah, just see a nice that inception You would think so this has been solved by now go ahead Sarah. Oh Quick question. This will be the first time I've been joining a kickoff in a long time And I know we've changed the format a bit. Do I need to share my screen? I'm just gonna be talking about some design system additions the benefits etc. I think it would be nice Okay, I have it ready. I just wasn't sure Yeah, usually we we share visuals Okay, great. And since you're last we're just gonna try to go as fast as we can to make time for you because we're still Have the schedule for half an hour and we usually barely make it. So so I'll talk I'll keep my short too. Absolutely. Well, you're last so you can you can use all the remaining time Yeah, we have about 40 seconds per issue as I see it, right Oh, yes, Bobby also noted your last so it has consequences. Namely, you have to you have to do the outro Sarah So what's the outro? I don't know the outro. Well, you have to say is it the best release ever? You have to you have to make a judgment on that and let the world know I Am not sure Josh will be fine because oh, this is Josh The last one I don't really think if you can shut down the live stream without Josh I Think Josh needs to jump in at the end and talk about the best release ever. I don't feel I don't feel like I'm qualified Well, Josh is here, so I'm sure you can figure it out Ask him. I'll be like Josh is this the best release ever and then he can answer me. I think that's how we should do it I'd be awesome. I Thought we are only doing that anymore though. I actually my camera is not working So I need to apparently try and change browsers or something. I'll be right back I thought we aren't doing like someone commented that like we should just like take Do our own thing or someone come like that was being a little bit contrived. I guess I don't know Yeah, have it be more of a conversation and not a pitch Yeah, I think that's fine. That's the one sentence at the end. It's not that big deal, you know Well, so James you can kick it off whenever your clock hits We're in the time zone for 12 o'clock for us. So whenever you want to start. I'll let you take it away and I'll meet myself Right, we'll do I think we got 15 seconds to top of the hour, right? I think it's top of the hour. Good morning. Good afternoon. Good evening wherever you are. Thank you for joining us on the 11.6 kickoff live stream On YouTube if you've got questions, please leave them in the the live chat and we'll do our best to keep an eye on those and answer those As we go through our items I am actually the first to share because Jeremy Unable to dial in at this time. I'll share my screen so you can take a look at some Visuals of what the managed team is going to be building this release So the first item I'd like to share is about add-on runner minutes for get lab.com on get lab.com. We provide Three minutes for using get lab CI, but some people run out and we want to make it easy for you to buy more minutes When you're using get lab CI on get lab.com. So there's gonna be a great improvement for our CI users Also for get lab.com. We're gonna be adding a new subscription table information to the billing screen It's quite hard currently to work out exactly how much you're utilizing your license And this new table will help you understand just that and make subscription decisions next up For on-premises customers who are self hosting get lab.com start a premium or ultimate edition We're simplifying the way we present the license screen information So a license will now show you in a much more easy to understand summary of the usage when it expires and who specifically the license Licensed to Moving on to some non license related features. We've got a nice improvement to add the ability to Disable admin impersonation. So we have this really handy feature where as an instance administrator when you're debugging Feedback from users or trying to help set things up. You can go to a list of users and then impersonate any of those users and see exactly how get lab is presented to them with this new option of the certain Enterprise environments where admin impersonation creates challenges understanding who's doing exactly what from an auditing perspective It can now be disabled across the whole instance This is coming to get lab community edition and core One improvement I'm really excited about is a new design for the group overview. First, let me show you what it looks like today This is what it looks like a nice flat list But we've made some really big improvements to the way projects look and we're bringing the group list in line with this So that we have the nice left alignment and a similar visual structure between projects and groups Obviously, they're distinct, but it'll just bring a more cohesive interface as you're using get lab and And even more great improvements. We're continuing to improve the profile overview With a range of improvements building on the split layout that was introduced last release We're continuing to refine that For everyone so that your profile pages look just brilliant Continuing on the theme of redesigns in the project list Where we're improving the way it looks So actually, this is this is a really great screenshot. It shows you exactly what it looks like We've got this two-row layout with a tiny little logo and information all crammed over the right and if we scroll down and take a look at What we're aiming for It's going to be a much more open layout where project logos are much more prominent So you can really distinguish Which project is which based on their logos? much clearer project title and great Information like access to the number of stars and forks so you can easily identify The popularity of projects and this is going to be really helpful when you're exploring The project lists in GitLab and also we're bringing the language stats through so you can know exactly which language the project is in Without having to open it and take a look So really trying to improve the discovery of projects and this is going to be great GitLab comm users where there's thousands and thousands of different projects that you can explore but also for larger Self-hosted customers that also have a really big number of projects and finally This is probably the feature. I'm most excited about Probably of all the features is this new tooltip So you can roll over someone's name and actually see in really great detail who they are a Bigger profile picture a description of where they are the time in the location where they are and Their status as well, so this is going to be really helpful and just knowing who you're working with and collaborating on a day-to-day basis So those are the improvements coming from manage Victor do you want to tell us what's coming for plan? I sure do so what I have on the on a list here is promote issue to epic with quick action This is an issue that we're actually wrapping up in eleven point five It didn't quite make the freeze cut off earlier this week So we we plan to finish that up very quickly a scrolling horizontally in the roadmap view So if you look at the roadmap view right now, you can scroll up and down to see different issues But you can't go further back in time or farther for out into the future You can change these date ranges, but again, that's limited So what we want to do is allow you to scroll back in time or use some UI to go back in time or forward in time Creating a good lab merge request in a Jarrah depth panel. So that's something A lot of our Jarrah users have been requesting for and it's supported in some other tools And we want you to be able to have a create a merge request directly in the development panel itself inside the Jarrah interface View board config next to search bar. What that means is that in a issue board right now? the actual board config is hidden behind a modal and so we want to expose that information so when you Navigate to the board you can see it right away. So these are just some design concepts That we are experimenting with right now and that we we plan to ship in the upcoming release Search or filter boards and navigation drop down What that means is very simple in the board switcher in GitLab you can go to different boards But if you have a large number of boards, which we do say for example in GitLab CE gilab e in the gilab group then you can search on them very quickly so you can find the board that you want This one is great epic issue list related issue list And so what this is right now if you go to this related issue list as you see here You can see you know the title you can cross it out You can see the path in the state But this future design which we're planning to work on 11.6 will also include things like The due date the mouse on the weight even who's been assigned to the issue so even confidentiality So you can see a lot more information at a glance Finally, I wanted to talk about import CSV into issues. This is something that a lot of our users have been asking about Say that they're they're working in a different Ticketing systems such as Jira red minus on and so forth and a lot of those systems support exporting to CSV So we want to take that CSV export and then import it back into GitLab So that you can continue using your data your legacy data inside GitLab So rather than trying to Support every single integration and doing it all at once We thought that we would start with the CSV support Which makes it a lot easier so some initial concepts are you know just clicking a button and uploading a CSV and then getting an email So very straightforward from your perspective, but very powerful from a future perspective James back to you Thanks Victor Very excited about those improvements We've got a number of great improvements coming in the create area of GitLab This release the first one is to do with the new merge request review feature That we launched in 11.4 and so one of the the great things about the review feature is that you can leave multiple comments and review them and then send them all as one review But you currently receive many many notifications So if I leave 10 comments, I'll still get 10 notifications even if they were submitted as one review In 11.6 what we're going to do is extend this feature and improve the notifications associated with it So that you'll receive one summary notification that describes all the discussion points that were added in the review So one review will generate one email notification. This should help keep your email inboxes less clogged with GitLab notifications so that you can better discern what's going on the next exciting improvement I'd like to share is around a really big Enhancement we're making to the way approvals work in merge requests So one of the common Challenges we have with approvals is that you can currently describe a list of say five six or ten different users and say I need at least two of this list of users to approve this merge request but as teams and projects grow larger and There's lots of different roles involved in delivering new features. You might need one senior engineer to approve it and one product manager and maybe a QA person It's not as simple as just saying I need three people any people to approve this So what we're doing is we're adding the ability to define multiple approval rules And so I think visually the easiest way to show this is what the project settings is sort of roughly going to look like We're still finalizing the designs Instead of just having a list of people who can approve it and account You'll now be able to create multiple sets of approval rules So we can say that I need one UX designer to approve the merge request I need one person from the security team to do a security review And maybe I need three different engineers to do a review These of course can be set to zero and left it essentially made as optional and so that gives you a structured way of sort of Describing who needs to approve things but this can also be used to enforce Yeah, quite powerful approval requirements And so this improvement is going to be coming to get lab premium and we're also going to be using This as a foundation for some even more great codon as improvements building on the work. We've been doing the last few releases The next really exciting change. I'd like to share is Coming to get lab CE and core which is the ability to suggest a change in a merge request if so when you're leaving a comment on Emerge request if I'll be able to click a button add a little code block and type in what the line should be and then Once I've done that there's going to be some kind of apply button So I'll be able to take this suggestion and apply it in one quick generator commit with the change Rather than having to go into my local editor and copy and paste the change in this is going to really make code reviews so much easier in terms of Addressing feedback So that's a it's a really nice improvement that I think a lot of people benefit from on a daily basis The next feature is a maybe a little less exciting for most people but Occasionally we make mistakes and we push really big files that we didn't mean to push to our repositories and one problem with that is that they kind of get stuck there and so There are a range of tools like the BFG repo cleaner that allow you to rewrite history and expunge that data from your Repository but get lab does a range of really clever things to make sure that you don't lose access to dips So if you push a commit to emerge request and leave a comment on it We create a ref to make sure that's never deleted so that your diff is always Accessible and you can always go back to the common and see what the comp was on But Because of that it means that it's almost impossible to reduce the size of the repository So what we're doing is we're adding the ability to upload the object ID mapping file from BFG And delete all those refs If you need to this is kind of a new killer option But if you've made a mistake and pushed gigabytes of data to a repository that doesn't need to be there This is going to allow you to remove it and that's it for the create team Jason over to you Thanks Right. Let me get My screen shared here. All right for the verify team we have a few great features as well The first one is that we're going to be hiding the variables in the UI by default. You'll be able to click on The reveal values button to be able to see what that value is Unless it's a protected variable in which case you won't it won't be available, of course The UI will be improved a bit, but this is where we're starting with that And this will help with making sure that things remain confidential that are supposed to We're also taking a step towards merge trains. This is a big a big change to the way that things work But we're adding the ability to be able to run a pipeline in the context of a merge request So with the way that we're going to introduce that is by having only an accept rules for merge requests that will Allow you to set behaviors in your pipeline that happen only if it's a merge request or only if it's not a merge request This will also expose some new variables to the to the pipeline as well So that you can see, you know, what the merge request ideas what the merge request Description is and and anything like that. So you this is an important first step And it'll be followed up by doing things like adding More behaviors around this and then eventually getting us to merge trains We're also introducing the ability to do triggers in a natural First-class way rather than using the corral commands or API that people use today This is another multi-part item that we'll be working on over the next few releases So we're introducing this with the ability to trigger a job then we're going to allow you to Wait for a job to succeed or just wait for a job to finish you'll have control over that and then we'll also add the ability finally to be able to set that a Pipeline it should be triggered by another pipeline running. So it's sort of triggered by instead of triggered as we have here So this will be a much better way to manage dependencies between products and those sorts of relationships We're also adding the ability to let pipelines be deleted by project owners. This is something that came up as It comes up fairly frequently as a request for people to be able to manage the data That's in their system or just to hide things that were you know Accidentally done that sort of thing. So it'll be an API call that will let you delete a pipeline ID And then finally for the verify team, we're introducing this ability To see upstream and downstream pipelines in the relationship in relationship to the running pipeline in the pipeline graph So you can see here that upstream there's an upstream dependency that ran for giddily that can be expanded And you can see what was run there and you'll be able to do the same thing on the other end And this will go very very nicely with that ability to trigger pipelines and manage them in that way So that's it for verify and I will turn things over to Josh for package Awesome, thank you very much. We got some exciting things coming here for package as well Let me go ahead and share my screen All right, hopefully that's coming through okay the first item is that we want to introduce MPM packages support within our overall package and our packs report within GitLab So to release to go we went ahead and we supported Maven packages And so now we want to go ahead and also add support for MPM as well so some really setting features there for Got no developers and some JavaScript type packages And sort of expanding our support beyond Java languages as well Also on that topic. We're improving our empty state screen And so previously if you went to the packages screen you agreed with a page that Might have a bit ended on a great of explaining what it did and so we have a new empty state screen That's warm. It's helpful links documentation and describes a little more about what it does So excited to get that in as well to improve some of the user experience And also Maven side. We're working to improve The Support we have today and so right now on Maven We have an API endpoint and essentially Maven repo per project and this can be need to kind of pull Independencies across different projects within GitLab. You're gonna have to add sort of n number of Endpoints within your Maven settings file We're now going to add a read-only instance of a Maven endpoint as a beginning place so you can have essentially one Repository you will to add for all of fraud Maven and then pull each of those in the handshakes down more easily And effectively them before and so that's a nice enhancement there for folks should improve some of the user experience of using this feature For our waving customers and so very setting there about our features for packaging and back to Jason for release Thanks, Josh So let's get this up So two things on the release side one of the big ones that's been looked for for a long time is adding pages Support for subgroups. So this is actually coming in from a community contribution. We're super super excited to be delivering this feature and Yeah, very very exciting one And the next up is we're taking a deep dive into how to do mobile development on GitLab There's a lot of a lot of things you can do using GitLab today, but some of the documentation and other Information around how how to do that in the most effective way isn't up-to-date or isn't easy to find So we're gonna take take a pass make that easy to do If anybody follows me on Twitter, you've probably seen that I've been looking for For developers of Android and mobile apps to collaborate with on this. So if you're interested to reach out to me there J4-L-E-N-N is my username on Twitter and that's it for release. So over to you, Daniel Thank you, Jason. Let me go ahead and share my screen here Okay, so on for the configure team the first thing that we're going to work on is going to be group level Kubernetes clusters This is something that we started on 11.5 didn't quite make it to the finish line So we're gonna pick it up and quickly finish it as part of 11.6 And so basically this is the ability to Configure a cluster at the group level so then the projects that are part of that group can leverage that that cluster and It's going to be very similar to what we have today where we will have a Kubernetes option And when you add the cluster itself is going to look a lot like looks today where you can add from GKE Or add it from another provider manually and basically the big things here is is that when you? Visit the cluster section on your project You're going to be able to see if there is a group cluster for for that particular project And also if there are multiple clusters defined, which one is the one that is active for that particular project So we're excited to bring this feature as part of 11.6 Next we're going to work on configuring auto DevOps deployed applications with secrets that are not in the repo So as you know when you have an application that's being deployed by auto DevOps and you need to pass a secret We don't want to store these in as part of the repo as this is not best practice So what our users are going to be able to do is leveraging the variables that we have today. They can prefix a particular variable name With something that will indicate to get lab that this is going to be passed To the application as a Kubernetes secret So let's say if you have a Rails app and you want to put your rail secret here You're going to be able to pass that to the cluster and be stored as a Secret which is then going to be best practice and it's going to be a Lot better from a security standpoint Then the next thing that we're going to work on is going to be adding API support for the Kubernetes integration So as you know right now the only way to create and manage clusters is via the GUI So basically we're bringing that same functionality to the API so programmatically you can basically bring the clusters up and manage them as you see fit and The last thing that we're going to be working on is going to be deploying cert manager to manage clusters and basically this is for the automatic issuance of SSL Certificates and what we're after here is that everything that is related to the cluster. Let's say The apps that you are deploying as part of auto DevOps or your jupyter hub instance It's going to be able to take advantage of the SSL certificate and serve the content the content via HTTPS So we're very excited to bring this this means that your auto DevOps apps are now going to be able to Support HTTPS and all the other apps that are served by the cluster and that is it for the configure team and Josh over to you for monitor Thanks, Daniel. Also some pretty awesome features in particular like can't wait for the SSL support for those applications On the monitor side. We're putting some groundwork into So just do some discovery on error tracking. This is a feature we want to add to our monitoring feature base And so we'll be looking at how we can best Sort of accomplish that here Potentially integrating a tool or perhaps building our own and so we're doing some analysis there of what that could and it should look like And that would we have a great plan that we have decided upon to go forth and execute in the next release We're also going to be working on taking our metrics dashboard And working to utilize our new Charlie library So last release you spent some time identifying a new child ever that we can use Right now the current dash was written in D3 and it's proven to be a little more work and effort to maintain and make sure We don't have bugs and things like that And so where we're moving to a new library get some additional velocity I hope they can have a little better user experience as well and so we'll be doing a kind of a sprint there to Integrate the new trying library for our metrics dashboard and again, hopefully realize those improved velocity Going forward so excited about that Fabio over to you for secure Thank You Josh. Let's see what's new for the secure team in London six So let's start with the group level Security dashboard improvements. So in level dot five We are shipping the group level security dashboard and we want to trade on top of yet in 11.6 introducing metrics and they see it means that you will not just have the list of the vulnerabilities and The counters but you can also see which is the historical data for this information So mainly it is interesting for director of security or this kind of high-level positions They want to see the trends they want to see how the team is going and which is the then which are the numbers for the different kind of security problems and this is the very first Interaction with it. So you can see there is a graph introduced into the same dashboard So you have all the information in one single look and in the future We want to improve this metric even more. There is a product discovery issue that was done in 11.6 In 11.5. So you can take a look at it if you want to see all the further iterations the second Item we want to work on 11.6 is to disallow merge if a explicit license is found So if you explicitly forbid a license to be part of your project There is almost no way Why a dependency should be allowed if the license is not matching is the license sales forbidden So in the merge request widget The merge button will be blocked in case the project has this option enabled And there is a new license. For example, you introduce a new dependency with gpld2 and the project settings Say that the gpld2 is not allowed for that specific project so there is a message and developers can Understand which is the best solution and fix it. It is very similar to the other Blockers we have on the merge request button We also have a bunch of other things a lot of backstage and database things We are iterating on if you are interested in in you can find the full list in our dashboard as usual You can find the link in the document Now James back to you Thanks Fabio Super excited to tell you about a proof of concept that we're building in 11.6 for object de-duplication in fork networks So the first phase of this is Creating when you create a fork of a public project basically making sure that we're not Copying all the same files all over again We don't need to copy all of them and we can use the git alternates feature To reduce disk usage So we're going to be building a proof of concept in this current release 11.6 That will be behind a feature flag and basically demonstrate the the forking workflow and much reduced disk usage associated with that and there's going to be a lot of things that aren't covered in the proof of concept around deletion of the upstream project and changing permissions and things like that But just to share that we're actively working towards this and we expect to have de-duplicated Forks in the near future Back to you Josh, I think Yep, thank you James. That's again really exciting We had a couple of also great items coming for our distribution team as well we have some kind of dependencies that have Fairly old and in particular a run it for example as well as the registry registry in this case It just hasn't had a release from upstream in almost a year and so what we want to do is take some time and Upgrade these the registry upgrade should be here coming soon Which is very exciting has some nice features in this new release and so looking to take advantage of that here again soon and so we'll be kind of Going from the early releases of running our industry and moving up to more recent releases in the case of the registry We'll probably pick a bit of the commit window to jump up to so we don't take the whole list of commits Which is quite large and we can reduce some risk there So we're looking to upgrade both of those in preparation to really kind of jump to latest once they're available on the case of registry We also are working on some exciting work kind of underneath the the coverage here with with GitLab to upgrade to Rails 5 And with the upgrade to Rails 5 that also unlocks some other interesting features We can take advantage of one of the most important feet or most frequently requested features that we hear on the on you Best side is that people want to really kind of separate configuration of passwords and in particular encrypt many of the passwords With the 5.x line of Rails we can now start to take advantage of that With encrypted credentials and encrypted secrets and so we'd like to do some discovery work here with Rails 5 coming So we can be prepared and understand how we will implement this and that way we can accelerate the kind of market of the actual feature itself and now we have a good plan in place and we have evaluated some of the solutions So that's very exciting there to be able to address that here in the near future with that kind of major upgrade to the Rails 5 system We're also working on some improvements to our dependencies as well So we've done some work in the past to show our dependency list for example You can see this here. We're also working to improve the how we render it to folks But you can see we have a huge list of dependencies and in many of these there's even additional dependencies underneath So you can kind of go keep going further under all of these and so the list is quite large And we want to try to up automate this process at least for reports, but also if we can upgrades as well So we're working to do that here in this release to take some of the burden and remove some manual effort That could be point errors as well And kind of again automate this process So it's an exciting work there for the team going forward. Over to you Sarah for some of the design system updates Thanks a lot. Appreciate it. Looks like I've got one minute to tell you about the awesome work We're doing on the design system, but I'll take it. So let me go ahead and share my screen real quick So the GitLab design system. We're naming it pajamas We're really excited about it and this system houses our usability patterns and guidelines for design and development Why are we talking about this at kickoff? We're committed to improving the user experience of GitLab and we're doing that using this design system They're so important that I wanted to share it with everyone So some of the benefits are speed and autonomy designers engineers and pms can work faster with established patterns and documentation to reference Consistency so established guidelines keep our user experience consistent throughout And time so having these established usability solutions gives our designers more time to devote to exploring new problems and problem spaces So I've listed some of the exciting things that we're working on adding to the design system One of the most exciting I'll skip through some of them You can go ahead and click on those links But the most exciting is component documentation inside of design.gitlab Frontend has been working really hard on this Alongside UX to make sure that it is a single source of truth for designers Engineers and pms and with that that's the end of kickoff. Thank you everyone. Have a great day