 Well, all right. Well, thanks Jeremy for joining us. Jeremy's our product manager for For the manage team so Jeremy without further ado, I'll turn things over to you and let you talk a little bit about the GitLab manage and and other things you're interested in discussing with the community members. Yeah, sounds great. Thanks a lot Ray I really appreciate it. So I'm Jeremy Watson. I'm the product manager for manager at GitLab I'm going to share my screen and chat through manage at a high level in terms of what the stage at GitLab tries to accomplish Talk through kind of the the stage itself some of our goals and priorities for this for the for the core team And then I can talk through kind of how you can help contribute in some issues that I kind of like to highlight So without further ado, I'll go ahead and share my screen So manage is interesting because it's one of the few stages here at GitLab that spans across the entire DevOps lifecycle so right now I'm looking at Inside the GitLab handbook the categories page and our part in the product section of our handbook I'm just looking at this diagram here, which kind of outlines how we think about DevOps here at GitLab So whereas you see that there's very specific stages like plan create release and configure that deal with like very specific areas Of the DevOps lifecycle, we have several stages which manages one of one of which that span the across the entire lifecycle And and that's what manages all about like manage is kind of the the foundational piece to GitLab that covers all the common components that like We that instances need to be successful as well as like the kind of high-level analytics about how your instance is performing Giving you like powerful configuration that enables you to set up your instance kind of how you want with powerful controls and analytics So I can know what's going on So that's really what manages all about it's about the Managing your instance And this is something that is that we think about in kind of two high-level goals With the team which is helping organizations really prosper and do well with the configuration analytics that they really need As well as like removing barriers to finding value and helping users really find solutions to problems like GitLab helps solve So, you know, like I mentioned manage covers like a lot of different areas it covers analytics covers configuration in the form of authentication authorization And it covers a lot of those common components that you can see here on the back to the categories page That's in this other functionality and manage and that's user management permissions projects groups profiles navigation management area so Again, you know manage covers this this wide kind of area inside the product And I want to kind of try to help that break that down for the community in terms of you know What is it that this team is working on what are our priorities and kind of how you can really help Kind of be a part of that So i'm going to flip back to the the product vision for manage So the page here that i'm looking at is the direction page that's specific to manage And i'll continue talking through this a little bit So You know the themes that we really work on and you can kind of take a look at this video here on our direction page To get a little deeper look in terms of like what we're working on Over the next, you know, three months or so Is really like helping instances operated scale Providing instances with powerful analytics security and also increasing the lovability of our product as a whole So when it comes to operating at scale, we want to try to Take and solve those problems that instances typically run into when they you know reach large large You know scale when they're dealing with hundreds and thousands of members on their instance Where things become harder to manage where you need Better coverage on our apis where automation becomes a greater need and where my annual tasks just simply start to break down So, you know, this this definitely involves better authentication better about Evolution of our apis and how we handle things like personal access tokens and application scoping And then how for ee how they managed how instances managed spending with our with our licensing model You know, we also want to really improve the way the analytics work at get lab We see that cycle analytics is an opportunity for instances to really understand kind of how their instances is operating And how faster shipping software and which is something it's tremendously relevant for core We really want to get you know Like take large steps forward in our in our analytics and the insights that we're able to deliver there As well as increase the you know the security of instances by giving them like not only better levers for Being able to enforce powerful security for their users But also being able to enforce strong access controls like at the group level So they're only able to kind of give access to specific users and entities that they want to their instance And then kind of lastly We're just interested in building on you know the overall loveability to product We don't want something that is just merely functionally complete with you know, lots of configuration that is like challenging to manage but ultimately very But like has high utility value We want to agree an unbeatable experience that ultimately like customers and users really really love So this is all you know a particular area that i'm excited about And looking to the community's help not only for their feedback in terms of like what it is that we can do to To make get lots of something that you you you really really love to stand off the rough edges and You know in the areas of territory that tend to frustrate users But also the highlights and areas in which that we can That we would love love the community's help guidance on so In terms of like what the team itself is working on The current focus That we're kind of like thinking about is really helping authentication right now get better The team the managed team Which is a team of about five back end developers and four front end developers currently working on improving authentication, especially in the form of sso We'll also start working on inactive user management and being able to manage the users on your instance and understand their activity levels better We'll also work on A better comprehensive audit logs. You understand what's going on your instance more Better access controls and then analytics improvements that I that I kind of talked to a little bit earlier Also relevance to kind of like this loveability theme is going to be our work on new onboarding Which we're excited to kind of we're starting to explore right now So how can we help users going to get started faster? on a git lab instance How can we create like a relevant smart dashboard for you so that when you hit like your instance's home page You're immediately seeing relevant information in terms of like what it is that you need to do and You know what relevant activity has taken place on the instance. It's important for you to be aware of And then and then redesigning core Experiences at git lab like the project overview page and the group in the group overview page So a lot of exciting stuff that the team is working on and we clearly have our hands full So I think that you know the priorities that we have are definitely relevant to both c e and e users and customers And I really wanted to highlight some areas that we wanted to that we think are really really important for us to Focus on in the future, but thus far. We just it's been a real challenge for us to make time for So the first one I'll kind of mention in the highlight is One thing that that's that's been a challenge for me as a product manager and for the team to kind of make time for Has been again like iterating on some of those core experiences that customers You know typically struggle with and typically affects like the use the core user experience and livability of the product And the first one I'll talk to is kind of being able to share private projects And this is like something that that customers will and users will typically struggle with because They will have a prior project on git lab.com And in order to share that with someone who's an external party They think that customer that person needs to first register for the but at git lab instance for git lab.com And then at that point the The private project can be shared with that member, but this is kind of a clumsy You know awkward workflow and generally what people want to do is they just want to be able to Generate a url Share it with different people and then have those individuals be able to use that url to view their code So we want to we want to introduce this by leveraging our existing invite flow Where you can invite an existing member of the instance to go ahead and pull them into the project But at the moment you can't do that for the users that aren't Existing members and we want to be able to extend that here. So this issue here Which I would love either feedback or contribution for Is extending that existing invite flow so that now you can invite That it that invite url is now Utilizable by any kind of by any member who is not already on the git lab instance So a project or group owner should be able to generate an invite url from the members page They should then be able to go ahead and share that with others And even if that user is not already like an existing member on that instance They should be able to use that invite url Join through a sign through our sign up flow and then immediately be added to that project or group at like a defined Membership level so this is something that like the community has been really excited about This is something we would love to get to get into git lab And we consider this like a big step forward for from being able to to make private projects more widely shareable and usable by Members so we're excited. We're excited to this one. This is one. I definitely wanted a highlight From there, there's a couple others that I'm really excited to talk about and one is pin projects One we've had a design Ready for some time that iterated on the on the profile page for users The moment like what people want to you really want to do with their profile page is they also want to use it to highlight particular projects and areas they're really excited about And the the problem is is that you can't do that right now like an external Someone who is an external viewer like clicks on your profile and you know, they see the profiles Your your profile and the projects that are in your profile Kind of sorted by by last activity, which isn't always like how we want to be able to to highlight them so We want to give users the ability to to pin certain projects by highlighting this By servicing this kind of pin object on mouse over and being able to click on that and being able to pin that That particular project to your profile so that when anyone sees clicks on your profile, they're able to see those those projects Immediately and be able to understand which projects are most important to you and which you want to highlight in your personal timeline So, um, this is one that we're very excited about Again, one of those that you know Community is excited about we think this would be a great addition to get lab But we thus far haven't been able to get to it and right now it's sitting with a with a q2 milestone And uh, and uh, you know, it's one that we're still struggling to find time for Additionally, we want to add pins to both the projects To the group's overview page So one of our designers and manager Matei has created a really really compelling future Vision for where we would like the the group's overview page to go So you can see here This is kind of the final kind of version our vision of where we'd like it to go We see as kind of the seven days overview of like what is happening in the group Like a little spark line of like the last seven days of activity on in the group And then we also have this this container here which kind of highlights some of the top projects that we want to highlight within that group These this is another area where pins really help So these are actually just pins where you can pin certain projects and certain subgroups To the overview page or to highlight their significance So, you know when a newcomer who's coming into your Organization your open source project or your or your company clicks on the group They can immediately see what what projects and which subgroups are most relevant to to whatever that group is trying to accomplish So, you know, this is something that's not always clear right now The group overview page is kind of sort of by last graded or last activity and we are it's not really clear in terms of like What the group is trying to accomplish? So we want to make that very clear And we want to be able to add pin groups and subgroups to the to the group overview page in order to make that clear in order to give a the group owner a Clear and an obvious way to kind of customize what people kind of what where you want to where you want to direct folks Whenever they are clicking and viewing on your your group overview page So adding this this is a this is a completed design. That's kind of things kind of ready and once again, you know It it it's something that we struggle to make time for and manage. So So those are the three issues that I wanted to highlight the the share private project by a url Pin projects and user overview page and then finally pins and projects and subgroups within the group overview page Really excited about all these. We really think this is going to make a great admission to get lab And we love either your contributions or your feedback in terms of how we can execute on these features and make them successful Lastly what I'm going to leave you with is kind of my favorite Is a couple two kind of words on community contributions The first is one thing that I like to do is I like to be able to sort to keep priority labels on high value and Contributions that like are very important for manage is like a stage and a team But stuff that we just haven't been able to get to and so the the query that I really love to use is is is sorting the Sorting ce by accepting merge requests p2 and manage So p2 is a label that we use at it lab to be able to signify High importance issues where p1 is like critical We have to drop everything and do it immediately down to p4, which is you know, it's a very it's a nice to have So p2 is our you know issues that are very significant Ones that we may be not having had a chance to get to yet and sorting by milestone due date So these are issues that like are open for community contributions and accepting merge requests But the milestone is kind of distant They're either in the in a future quarter or they're in the backlog or they don't have a specific milestone And these are the ones that we would either Love to focus the community's effort on in terms of feedback and how we can make you successful for you or We would welcome a community contribution to see how we can how we can get those in the get lab The second issue that I'll talk about is if you see an issue that you're excited about and that you are You know, you're excited to move forward with Feel free to signal on the issue that you're interested in it Even if the issue isn't necessarily complete or there are still open issues in the description Um, you know, I or someone else from the from the get lab team are more than happy to start moving the Answer some of those unanswered questions and move the design forward if one is needed If someone from the community is really excited about picking it up. So Um, so those are the kind of the two two two takeaways I wanted to leave you with as I uh as I shut up for here for now Which is number one, you know, this is a great way to kind of find high value community contributions to get out That we're that we'd be welcoming and then number two is, you know, even if you see an issue Regardless of the of the labels if it has accepting word requests on it Even if there are open questions, you know, feel free to to add mention me Into the issue and we can kind of discuss how we answer this question. So I'll leave it there for now, but uh, you know, I'm excited to kick the hackathon off and uh, I hope, uh, you know, you can direct any future questions about managed to me Either in get lab or by email and my contact information here On the direction page here at the top of this page. So Excited to excited to work with y'all Well, thanks, Jeremy. That was perfect you Uh, I think you like, uh, I was about to ask you a question about how people should find issues But you already addressed that so definitely appreciate that and and the first issue regarding share private project via url I think that's one of the issues that we highlighted for the hackathon. Uh, that's um, so people tackle that issue People will be eligible for the extra prize and it looked like there was some discussion this far There's even a couple of days ago So there are definitely interests from the community members, but it's still waiting for it to be picked up and hopefully somebody will be able to Tackle that and yeah, definitely appreciate your insight and not not only in terms of what What manages but what your priorities for for the rest of the year. So I'm sure yeah. Yeah. Yeah the I'm excited about the share private project issues 157 of votes Which is which is a ton. So there's clearly a lot of interest in the community and a lot of people who are really excited about this Um, and uh on the information that I just shared in this video. I think the best Uh single source of truth is going to be the managed direction page. So, um, you know all the information that I just shared in this video including the You know the the two takeaways at the end on in terms of like how to find issues And also, you know, how to kind of direct your interest if you're interested in an issue with some financial questions I'll be adding that to the to the direction page in a merge request Um, so continue to keep an eye on that page and uh, you know open a merge request If you feel like there's there's unanswered questions. We can be doing a better job at so, uh, anyone can contribute awesome, uh Yeah, so I don't think I have any questions that david. Were you was there anything else that you wanted to ask or you wanted to point out Yeah, I have a couple of questions for for jeremy. Um related to um priorities and um and um community needs as well um, so you've mentioned that uh, sometimes, uh, one of the things that you um that you use for measuring um Not measuring but having a better idea of what uh, what features are popular feature requests are popular are the thumbs up for instance so, um In the I'm asking this question in the context of um, of a couple of open source projects What I've been working with they are uh, intending to migrate to a big lab There are a few issues that are interesting to to them And they're generally on the on they are generally using githlap ce So with this context, um, if they um feel that They can contribute in raising the priority to to a particular issue What's the best way for them to do it to do it? Is it just a thumbs up or it is the matter of exposing their case on the on the issue How does it work best for you for your team to to to manage those requests and priorities? Yeah, no, I think that's a great question. So, you know, as you as you kind of Previewed it's it's a combination of everything. So thumbs up for definitely, you know, a really clear quantitative Input in terms of like how important something is to the community But I think in those cases where you you have like a large open source project that it like needs Like a couple of issues in order for it to make it to make it live a viable solution for them You know, it has to be both. It has to be both, you know, ideally a thumbs up but also a comment in the issue Specifically so that you know, the relevant product manager is aware of like their needs You know, again, you know, that doesn't mean that we're that we'll have to have the bandwidth the ability to get to things right away But I think that you know, if there is maybe two or three issues for a large open source project To make githlap viable like we we should at least be aware of it So I think the best way that I've seen is just to have, you know, someone from that project Comment on the issue, you know, at ideally at mention the relevant product manager So myself for issues that are really that have a managed label on them And then be able to You know, articulate all the issues that are that are relevant to that to the open source or You know, the the the the issue is not is not only being aware of like the issues But also the importance to that particular organization so that we have like, you know If we decide to ship one thing, you know, that's not the the end all solution We also have to ship, you know, issues these bc and b as well So, um, so, you know, in order to answer your question, it's it's both it's both the upvotes help But also I think that additional context in terms of like what the organization needs and making sure the product manager is aware And can prioritize accordingly. I think that's the key Excellent makes sense. Thank you. Um, I have another one related or somehow related And again with the same content context An open source project Requesting a feature, but this is a feature that's already implemented and it's it's on it's on e Generally, uh, when I talk to these projects, I said the expectations that we have this process for for stewardship Where it is it is possible to request a feature to be backported, but um, it's something that That requires a careful discussion as well because it implies as well that we might be losing value as as well um, what would your feedback be for such open source projects to start such a discussion to uh, to uh, to backport prior to sorry back for the feature from e to c I think it's a good question. So I think that the best Uh, I think the my recommendation will be to start an issue. Um, specifically requesting that feature be backported down to cd Um, you know, I'm like there is a some I'm just taking a quick look through our products. Um The product section of our handbook to try to find the section where we talk about moving issues to core But um, what we do In the background is You know, um, so David, like as you said, it's something that we have to be very careful about Like ultimately like moving if you like features to core is generally a one-way door We generally will you know move features down, but we will never move features up in git lab So, you know, it's very typical for us to move a feature from starter or premium or ultimately down to core But I don't recall ever in git lab us moving a feature from core to a paid tier So with that in mind it is kind of a one-way door So we want to make sure that we're doing that In a very mindful way that's that advances the stewardship of the product But also is something that that that that we're aware of at least the business value of that feature So, um, when when so again, I recommend that users can start by creating an issue in ce and trying to I'm trying to start the conversation there and making sure the relevant product manager is aware of the need And why specifically this this should be kind of in core and what problem it solves for that user And the best the best issues that I've seen kind of really articulate like this is why it's important to us Here's our workflow without it and here's what it enables us to do when we have it And that allows us to have a really clear conversation In terms of like, you know, you know allows us to see the value very easily So what we then do is, you know, it's up to the product manager to gather information internally Talk to sales to try to talk to the rest to to to git lab internally to understand like the importance of this feature To the business of ee And then, you know, we we have a we we ultimately like make a call on it as a product organization and whether or not we want to do that I mean, then we scheduled the work and then and then proceed from there But um, but that's kind of the the overall process and kind of what I recommend users do If that's something that they think is important to them in their organization and their efforts Go ahead and create an issue. We'll have a discussion about it And it helps to really understand like the why behind that request to make that a little bit of an easier process Awesome. That makes sense. I mean, I like the fact that That you included guidelines as well. I think the why as you're saying and articulating the workflows Why do they need this feature as well? It's something that I can I can Essentially happen with Awesome And I'll just share the screen because I found this So this is articulated in our handbook under this section bringing features to lower tiers So, you know in full transparency, this is kind of the what what we do behind the scenes You know, we will take look evaluate the issue. We'll evaluate it, you know at our at our 18 level we'll create an issue describing the plan and then we'll get this We'll just gather feedback with the rest of the team and get lab, you know from the sales perspective And then we'll we'll make a decision and update the the non-continental issue Unlike why we're moving forward to the decision or not Awesome. Perfect. Thank you. All right Anything else David or Yeah, I saw that co-com just joined as well, but not sure if there are any other questions or comments Don't see anything on the chat Uh, well, Jeremy, thank you very much for your time. This recording will Be on the hackathon channel and hopefully in the next couple of hours, but thanks again for your time And uh, yeah, I look forward to community the contributions to the managed team Yeah, thanks a lot for organizing this. I'm really excited and thanks to everyone for their contributions All right. Thank you. Thanks. See you. Bye