keptn User Groups, 28 Sep 2022

Previous Meeting

Next Meeting

⏯

youtube image

►

From YouTube: New Docs Engine for Keptn - GSoC Project

Description

Google Summer of Code (GSoC) is a global, online program focused on bringing new contributors into open source software development. GSoC contributors work with an open source organization on a summer programming project under the guidance of mentors. GSoC contributors accepted into the program work on projects to improve or enhance the Keptn project and its ecosystem.

New documentation Site Engine, by Rajiv Singh. This project is about a New Documentation Site Engine for Keptn which can handle a large number of documentation projects of Keptn. The new Documentation Site engine will be based on Docusaurus. Two major things which are needed in the documentation engine are the ability to build the documentation from the source located in multiple repositories and support for document versioning.

More about Keptn in GSoC and the projects: https://github.com/keptn/community/tree/main/mentorship/gsoc

A

And finally, we are live.

A

Yeah do some delay but um yeah well.

B

A

On the screen, but it should be key.

A

Yeah I'm not sure, what's happening, but yeah. There is delay, maybe of 20 seconds on YouTube uh what okay but yeah. Otherwise we should be ready to go yeah. So thanks a lot uh Raju for your time today, um I will also start a separate recording um yeah. Today we are doing uh final Google summer of cool Demas, so we had four projects uh um this year.

A

Three of them are considered Successful by mentors and we will have presentations today for two of the projects so pleasure for the present the new documentation engine and then into our genome. We will present the k6 integration service. uh Some of the third project demand will be published later. That's the plan for today and yeah I think that we can just start the presentation.

C

D

Okay, thank you Oleg. uh So let me say the screen.

C

D

The screen is visible, so, okay, so hello, everyone. uh This is Rajiv and I'm, going to demo my uh project on new documentation, site engine uh which I worked in this Google summer of code 2092.

D

So okay, so um this is uh so.

D

um Let me tell me let tell me about myself so I graduated uh in August 2022 from jss college Bangalore and I'm working as sv1 at lumo, so this new documentation site engine is uh like what uh so I'm going to go over, give an overview like what uh what things uh so we are solving and and how we have uh gone through other other Alternatives, how we tackle this problem and all so um so.

D

uh Okay, so this is this- is the agenda of the today demonstration, so I will be giving overview of the project and how we tackle problems and all uh then I will give you an overview of the starting phase of my work. The the second phase of my walk, uh the G-Shock, is divided by in two phases and at last, I'm going to give an overview of work done uh like what work is left uh challenges, I face and those stuff.

D

So uh so, okay, so uh first I will give an overview like uh What uh doc. A new Dockside engine is so we we know that we Captain has a dark side which is based on Hugo, and we are facing uh problem in that and to solve those problems. We wanted a a new Doc site for kptn and uh it's like the problems.

D

What we are talking is like uh seo's problem virtual link, support, multi-doc support, um uh not not well structured, uh like uh it's very hard to structure the docs like a lot of manual work ways to do what we have currently. So we wanted to overcome those things and we decided uh we going through that other libraries and all like we uh at the starting of the G-Shock.

D

We had uh uh make a difference between we choose to uh uh tool, one was and Torah and one was Dr sodas and we one who decides uh one. So we differentiate between those and we have a docs for that. You can find in the report, and so we uh we we thought like docosaurus is something we should go for so so what the docosaurus is like Docker source is a tool by Facebook it's open source. We can say a tool which makes uh websites uh for documentations like it's very easy to use.

D

It has a markdown MDX support like markdown plus JavaScript. You mean that we can render the JavaScript code inside the markdowns on on a lot of features it has, and for that reason we move with Docker service. So this is the uh a simple uh outline of work. I did in Phase One and phase two uh I'm going to give a demo on all the points and so yeah.

D

So so, if we go to okay, so the first step was to initialize the docuser site uh from scratch, like uh simple skeletal of a docosaurus site and adding so it is um so when we initialize the docuser site, we uh it comes with by default, templates and components, and we want to refactor it according to the kptn and so that I did it. uh The some uiu exchanges here, the uiu exchanges is not uh is, uh is not according to the uh feedback given by the community or something it is like.

D

We want something to show, uh so we want to remove the default templates and all the so it the doc site. Look like some this so.

D

Yeah, so this is the dark side: uh I'm previewing, the yeah yeah. So this is the structure of a Dockside how it looked like uh we have our dark mode and it by default, supported by the Dark Souls, and we have the uh down like neighbor and all like uh stuff. So this is the UI ux.

D

um What I did like the sidebar and all? And so so the new, the the next next was uh adding um like the uh so. This is the UI exchanges and removing the by default templates and all so so next uh was to add a search functionality. So when we go to the current doc site so.

D

uh Kptn, so we don't have uh any any search for functionality. We can't search the docs yeah so that uh I've added in the new Dockside engine, so we have a search. uh It will work only when it is lived. So let me uh go through that. um Maybe installation and I want to search some like kptn instance. So.

C

C

Okay, let me search them. Oh okay,.

C

D

Yeah, so uh if I start something like.

D

Like some, it's anything you search, it will come to the the nearest uh whatever is found in the docs uh and it it's giving us the latest docs. So uh this is all I didn't updated it. So it is the 17 and now it's 19 so, but we have um like okay, so it just gives the latest it gives the content from the latest docs not from the older and all. So that's how the search uh works.

D

Dada was like the adding the burdening support, so uh the current docs we used to add manually like uh the it is going like it's. uh We are we used to put in the docs uh all the real in the religious section, different dogs, it's very hard to manage uh for a large number of dogs. So what what docosaurus gives is like? We can version the dogs, so we have a 19 version, so what we have to do is like just run a command yarn run and the version thing.

D

So basically, it worked like yarn run.

D

Yeah I'm done and uh just create an version of that what new version we want to create. So we have a 19 version and you want to create a 28th version, 0.20 point x. So what it does is like when we run the command you just copy all the current 19 versions and duplicate it. uh Something like this.

D

So we have this 19, so it will create one more folder, uh 0.20, point x and equal to get all the docs, so we don't have and then, according to us, we can edit the docs.

D

So that feature is to uh provided by Doc sorters, and so this is the latest version, 19 version, and we have a next version like if you want to showcase like in next um what what really is we are going to do next, iteration and all so, if you click on the next, it's going to say like this is the latest. It's an X version and latest is this so also it gives uh we are giving uh a lot like.

D

Okay, we are, you are in the not you are not in the latest version or you. You are like, if I go to 17 version, you are in the older version and not it's not maintained or something. So. This is all about the gardening support for the docker service, um okay, so the main. So these two features the adding the versioning support and multi-doc support by the two critical issues you want to solve via new Dockside in them, so so adding a multiple dock support. So this feature is uh we even we are.

D

We are not sure we are not able to do uh Pro fully like not like I'm, not telling you inaudible rule, but a partially. According to me, we want more automation on that, so I'll showcase. What uh we did so.

D

So, okay, so uh first I will go, give a whatever we like what a multi-doc support is, so we wanted uh other documentation to be uh more resist um to be rendered in this site engine. So if you, if you want like developer docs, we wanted to add the docs for here docs for that um in the this side. Is this only so we wanted to pull docs and organize it in the news offset engine. So uh so, to achieve this, we went through different different approaches. You can find those all the approaches.

D

We've tried in the report so so, but the starting was to writing a GitHub action which can pull the docs from the repo and structure it. uh We we uh like. We write a digital action, but like we are we that GitHub action was not uh structured. One like it can pull it off, but we wanted not to pull but also to organize and receive different sections. So that was not I didn't work out. Then we tried um tried using the captain, generate docs command.

D

So this this command is like uh like what we are using now it it pulled a captain, Clyde ox and put it in a Hugo side. So we went through the code the go code, how it does, but that was not um sufficient because the go code. uh What we have in here is like, according to Hugo, so when we see the so we can't use in Docker service, because the front matter is generated is not according to the docosaurus side so uh like these are not supported in our customers.

D

So we wanted something to change this and anyway, we have to like run this in batches, because this will generate only docs for Captain CLI, not like overall, like we wanted some more of generic approach, so that that is also like something we didn't. uh It doesn't work out like nicely so we uh then, then we tried a plugin called Dockers remote content, so what he does it like? It pulls docs so from the other repository.

D

But the thing is that we have to specify all the file name like, uh but we can't do that, like a lot of. If you want to pull a lot of documentation like a tutorial tutorial or something, we can't say all the names and all so for to overcome, this I have written uh uh like Javascript file, which uh for uh which, in which we don't have to specify file name yeah. We just have to put filters so filters. You mean the.

D

If you want to pull all MD dogs, so just have to put the star MD or something. So what I'm doing is that uh so I'm using a GitHub API, like uh so I'm, using a GitHub API which can list a document like three three API.

D

So uh when my when I call uh so when I call that API uh it is going to pull uh all the it's going to uh give a list of all the documents uh of the repository and Report repository I'm, specifying here like uh the repo name and all so it's going to pull all the list of documents and in in that code, only I'm applying some filters, so we have include uh include filters, exclude folder that these things I'm passing in the docker config file.

D

So so this is the main code where all the logic is written and so okay I'll show you how it works on so first we have to obviously import the file and try, then uh to specify the repo name from where I want to uh pull uh docs which repo so uh like, uh like we I, have already uh so okay, so here so I am for demo purpose. I have used this two repo and one enhanced with proposal and one and Captain developer tops.

D

This is also not a repo like this is inside a captain. So even we can pull us uh some folder also not whole repo, or we can pull a whole repo. Also, so I can so I specify here at the repo uh repo organization name, then I have to give a repo name and then the branch which you want to pull. So we can. We can customize this more like uh to have or like. Maybe we want to pull from some other branches or some to having have some all edge cases covered.

D

So I just give three parameters. So these three things we have to specify now uh now we have to give uh the filters. So how is structured like that to give the include filters and exclude filters? So these are the files uh or filters which we want to pull so I want to pull all the MD files, all the MDX and PNG files and I don't want to pull the dot GitHub, because if I pull dot MD file, it's going to pull the pull request templates too and I don't want that.

D

So we can exclude all the folders which we don't want to. So let me uh so when we run the yarn command, it's going to pull all the docs. Let me delete some docs here, so it's just full docs slash developer from Capitan. Let me delete this and we'll run that and.

C

D

Empty, uh let me delete this too. Now the captain doc Captain developer this. This is empty uh thing, so, when I run.

D

Is going to populate all the files, so these are the files which is inside the captain, which is inside this captain.

C

Let's get done.

D

I think this is inside docs developer. You just pull all the docs in here, so you can see in docks.

D

Even the assets also is pulled because I have specified PNG files so that so it's just pull all the docs according to we I didn't display any name on our all of like if I want to pull like um even same with the same with the in enhancements proposal too. So if I go to.

C

C

Let me see uh yeah.

C

D

B

So uh so you just pull.

D

All the docs, let me like remove this exclude filter for your management profile. So now we have in uh do do this to redmi MD files see automatically just I I removed. Actually, it's worked dynamically, so I removed the exclude filter. It's just pull other docs into dot GitHub, also so I, it's just because uh how it dynamically pulled, because it's still running right.

D

So just pull all the docks. uh These two earlier I was just trying it. So so it's so this how how this uh we have achieved a multi-doc support, but uh we wanted more automation like um we wanted some Chrome job or something or even one, uh some issues with what the issues are. So the thing is that that API, what I'm calling here uh in the this file, it has a rate limit, so we can't do again again um like uh here now: I have a specified token!

D

That's why, uh like rate limit me like six times, four I, don't know what is the stats of that? How many times we can call it, but now I can call anytime, because I have providing a token so um break so uh via token. I can do as much time. So that we can, we can improve it by maybe caching the files like if I am again running the yarn command it's going to pull, but we already have a docs.

D

Why to pull again so to we can have a one more function we can, which checks, uh whether the docs are there or not, but even for that all so we have to check it. We wanted to pull fast to get a list of it, so there is a rate limit for that dates, API, so that we can work on. uh It is soluble, it is soluble. So so now so we are pulling the so it just pull the docks here.

D

So so that's how this multi-doc support, uh Works um and so, but still manual work- has to be done now. I'm I can pull the all the docs MD's file on, uh but uh we don't have anything here like we have. We have two ads from front matter and all according to docosaurus, because how.

C

D

Increase the seos and all so.

C

I will give a.

D

Demo also like.

C

D

Except- and this is already pulled- so no- not this one- uh Captain developer doc. So this is the docs, oh lord, it's not that it will work, because we, though I didn't, provide a front moderation. It will work like how doctors work it takes any MD file and it does render it yeah. We have to see manually like if anything is breaking Snippets or like see. Something is like um I think we are trying some icon or something so that we have to see.

D

So this is like pulled uh like uh from a full request, so um that is. uh This is like the deployed version, so I didn't put any docs on automatically pulls uh docs and whenever, when we run the command, so this is all I wanted to multi-doc support how we achieve it.

D

um We can improve a lot uh by updating this file uh because I just added a demo like I've, just added like some basic like getting a list of document and then adding uh inside the document passing exclude include filters. We can improve a lot on the recalling the inconfig so yeah, so this is all about the multi-doc support and all that all the things we have tried and all are in the report, and maybe those we didn't. This Captain generate docs.

D

We, it doesn't work out accordingly, but we can integrate that or maybe we can write us a general go file for all, um not for the captain CLI, but for all dogs and yeah. That was something uh we had. We had worked on uh one more thing like uh so um also we have improved the seos of uh site so earlier we don't have uh how we improve seos like so when we go to the roadmap, and so we can specify tax and all so when we see the docs thing uh we have a.

D

uh We can specify tax here to this. These things are very helpful when we want to search like find all the time all the docs will do. The roadmaps which will list all there provides.

D

um Even uh even uh we can specify the meta image so uh when we copy this thing and go to meta tags, so earlier docs we have, we are not able to get any description of any page or something. Now we we, we can have a description. We can have a meta image. These all things are comes in the improving seos.

D

So these all things you can exercise in the front matter, and we can, we can add a lot of stuff like in front matter, keyword like I just added for demo for first also, also also when we go to the site. We won't find so much uh content here, because uh content migration is something we still working on, because we are not decided what content should comes in the new dioxide and structuring of it is something we wanted more discussion on that uh okay.

D

So this is the work of uh phase one phase two is more related to about adding tools to the new Doc site, so we have integrated the lighthouse CI. So, first of all this is this. Lighthouse is not is a captain Lighthouse thing it is the like web. uh So we have a lighthouse. Is a tool which gives report about the websites uh how much it is optimized how much JavaScript is used and all so? uh So what is this like when you make a PR here uh like I, need a PR this?

D

So it's going to give a lighter score. Okay, this PR, whatever the changes we are doing here, is how much is affecting the current uh status of the site. So it's going to give a performance of this. It's going to I know this is approximate, uh but it's going to give a Insight of it. How much we are changing stock and when you click on the report, it give our overall report of it like. Okay, this is a SEO g90, and this performance is like very less, so we can improve more.

D

So we can get a. This. Is the just an GitHub action right, so this is the we can give a get an insight about the site site, uh the page uh using the lighthouse um okay.

D

So the next is like available.

D

Syntax and all Pros, uh so we have integrated this uh uh wheel uh like we didn't go through directly like we had a uh it's. You can find in report like how we went through well instead of Roseland and why Avail is was good and all so. This is also like how a whale boxes like uh whenever the anything syntax uh so yeah and as of now we are following the Google style guide and anything uh which doesn't follow this Google style guide is going to give a you know: okay, you are not following that.

D

It's rule or something uh Google style guide, I followed, because that is more popular and we are not decided as of now what we are going to follow for kptn. That is still discuss. Different discussion like uh should we go for a Google style guide with customize, or we can write our own rules for well desktop and all so so Vale is something we used to uh linter, syntax pros and all for just improve the quality of Docs.

D

We have a prettier GitHub action, so obviously, okay, so we are using Docker service and most of things are in my we play with markdown, MDX and all and we wanted something which can like. We can't make sure every time we uh like, like I, have like automatic flow. It automatically format, every other prettiest organized format stuff, but not all people see like if some highlights are left or something so to make sure it.

D

So what PTR does is this like it just format the docs automatically, when above you make a PR uh still that that is, that is stuff. uh We are still doing, merge it like uh still no no. So that is much so that is still we have wanted to improve because that is auto commit.

D

So autocom is not good, uh it's just autocommitted and whenever we find anything indentation and all so pretty that's what this so um then we have uh adding GitHub action to check broken links, so so, okay, so xrf's uh broken links, is something we want. uh We have uh in the Hugo, but we want it more like more robust uh stuff, so I will give a like.

D

So what a new uh broker link Checker does is like when you, so whenever there is a broken link or any price left missing or something it just create an issues, and is this tag uh so I will overview here so like failing link check. So whenever there is a broken link is going to make an issue, and it's just going to assign it. We can as uh like. How is assigning me is like, like I, can specify any anyone in the GitHub action like if you go to GitHub action, uh Style.

D

uh uh We're gonna try. The sign is also like group or something and he's going to assign a b and we're going to specify the tax okay. So these like label, sorry uh which level should put in this issue, so just make an issues and just call the person who can see okay. So when I click on the and to see the where the it's broken or something you can see the workflow logs and when you click here just for a demo purpose, I have uh I created earlier, so it just gives okay.

D

Here the link is not there or something. This is not working, uh so we can go manually and check it. So this is uh the new markdown Checker uh link check, check.

C

String we have like here.

D

Yeah so also the lighthouse accent okay, so this is the Patriot action. This is the whale enter and Lighthouse uh report uh style, guide and all are here. So this is uh this is the uh the Google server they're following and.

E

D

The uh well it might, uh it might false false checks also, so we can specify the acceptance like maybe kep and kptns. Something is like if Google can make say. Okay, this is the wrong spelling, but we wanted that. So we can try desktop in the cap, slash capital and this this in these files.

D

So so, okay, so so this is all about the phase two work, and so this is the whole overall uh overview of what we did and some some more topics are there like, uh like which we wanted to focus on, like the main was the making uh automating more the multi-talk support, uh it's working, fine I think, but we wanted more like okay, so you can see here the API that New Media exceeded because it's called a lot of times, and so so, okay, so so future work to be done.

D

So this is the work which is I think this is very important and uh there are other suggestions too, which you can find it here in these links. uh So first was the enhancing the multi multi-departistic Rock support feature having a UI ux uh proper structure. Ui works I mean that as of now, we have uh this website. It's look good according to me, but other people might have a different feedback on it. Okay, we wanted this. This all uh down thing to be here this side or something.

D

So that's that that structure, UI ux rule should be. We can have migrating dogs. So still the current docks, so Meg has written a list note on the structuring of dogs so that we can follow and remove the contents uh to the older doctor to the new Dockside and uh like a okay. So even uh in the installation page uh earlier in the in the dark side, we have a box box thing here, so we used to used to leave the main.

D

So when we go to here so we when we go to installation, so we have uh we people try to like they don't know we have a Content down and they used to see this and they move. So these things and all these two tackle manually so I have removed here an installation that box thing. We don't need, because anyhow, that will come in sidebar.

D

Now it's not coming because I didn't added content uh to why to why to see again again here and again in the sidebar, it's just based, and so so that's things and all uh we can tackle the while navigating the docs. uh The second. This is the second or third point, and this is the fourth was writing your own custom role. I'm, not sure we have to write or not because.

D

And also the one more uh which is uh I got suggestion in Captain doc, Channel like having a component which can render Shipyard files. So when we see this slack block. So what is what I'm talking is like about like something like this.

C

D

So we can like just uh just render uh like we can specify some payload and it is going to uh render uh uh something like a block uh uh like something like this. So we can provide a payload uh I'll show.

C

D

uh Yeah, so we are providing a payload and you just generate this uh UI, so that uh so we will provide a CPI files and it will going to generate something render it so that component it is achievable because Docker support uh JavaScript, so we can create a components, JavaScript other box and suggestion, which is uh by Meg me and um so that and all are in the here. You can find it, but these are the main crucial thing which can be the future work to be done yeah. So it's a challenges face.

D

So the main challenge was to the multi-top support, which is still I I feel like is, we can automate it more and we are not able to do it. Yeah I teach all one of the learning. We learn a lot of ways we cannot achieve that, but now we think that we can. We might get help like um I said you, like Captain, CL, I, think earlier it was not working, but I now I think we can use uh in our current a JavaScript code.

D

Something maybe run that thing in patches, not a single time or uh yeah. So uh but I was. uh The second was like a little bit didn't understand the proper uh multi-doc support thing because, like um uh okay, so we wanted a multi-doc support, but uh we might also in what sense like uh we wanted to pull only dogs or uh or what type of dogs we want to pull or txt file or a markdown file or anything we have to specify or all the dogs whether we wanted.

D

But that was a thing and the third one was like. Sometimes we used to find little bit, not it's not a serious problem, binding with scheduling the meetings and all like uh at some different time zone hmm yeah. So so learning is our learning like first of all like this, whatever I've listed here is like it's just over just some points, which I think is important, but I learned a lot of stuff which I can't I didn't mention here.

D

uh The one was like having a POC is very important and we even after having a POC, we are not sure we are able to achieve because things changes as we move and the so that is one of learnings and the other one. If you talk about textile, learn a lot about doctors and GitHub actions linking and all structuring and planning of projects like uh how we document it and working with the team like sharing the thoughts and getting a feedback and then start walking, yeah so yeah. So thank you uh for the yeah.

D

So thank you. Everyone, like you, can find all the stuff and in this reproductory all the reports, all the meetings and all you can find like uh everything is I've organized here.

B

D

The community repository of the Capitan and yeah. Thank you. Everyone.

A

Thanks for the presentation and yeah good overview of the project, um so I would give some time to mentors uh to share their feedback and opinion about what needs to be done next, so max Suresh. Who would you like to share.

B

You want to go first.

E

I was going to say the same to you.

E

uh No issues um I think.

E

Well, he put me in a spot. Let me think um I'll first go over the future that that needs to be done. um I think we need to migrate a lot of our old documentation to the new documentation site um that, and there are some use cases around, putting talks from multi multiple repositories which still need to be covered like um pulling the auto generated docs from the from the captain Commander the dogs that Captain Comanche.

E

Is that something you need to do um that and I think migrating docs is probably the biggest thing that we need to do styling, and all of that um that is what I can think of when it comes to future work, and um the other thing would be to start migrating some of our talks to the new dox engine and see how it works.

E

We would like to receive more feedback from the community in general before we start using it uh across the board for all of our talks as for feedback for Rajiv or the overall project, I think the project will add a lot of value for us.

E

um We initially faced some makeup speakers of multiple time zones. It was mostly around us finding the right time for everyone and uh eventually we we found the right time and uh we were able to work it out.

E

um Overall I think Raji was very consistent with the work um I think one of the uh things I mean I, think Raji mentioned it also as managing their priority um making, which which I tend to pick up next, basically based on the priority, that's something we could have done better in the project, but overall I think it would be a great value addition to that I mean that's. All I have.

B

Yeah I agree: we need to um I think we probably messed up. We should have gotten more of the content over there. Just because you see things, you know it's one thing when it's in the abstract and when you start seeing your own docs in there, you start seeing issues um another point that I think I think we messed up a little bit, not getting um a full understanding of what we needed early on uh The Moldy doc. Support especially is, as I see it. There are sort of three phases of that.

B

One is the the CLI reference Pages, which are already being pulled in from another repo, um not the most elegant implementation, but it works and that we I think we should have. You know understood that what I think happened was Rajiv, knew um that docosaurus had this multi repo support and we said multi repost the board. He went towards entered the tooling without sitting back and saying. What exactly do you mean for that um and I think you know, we all thought we all.

B

We all had our understanding of that and I'm, not sure we were as good as we should have been up front, making sure we were all clear about it um and again with priorities: I'm I'm, not sure when you had a we had.

B

You know we start out with a very ambitious project list and the most some of the most critical things that we were doing first when they, when he ran into trouble with those we just moved on, and it made it meant, though he got more of the other features in, but it means the key features didn't get done, but it was a real pleasure working with you Rajiv.

B

um You did a lot of work, I think we're going to be able to take good use from this and hymo. It's good to see you joining us.

B

uh Do you have anything to say about this at the end of the project.

C

Nothing more to say really: um it looks pretty good I look forward to actually using it, of course, and then improving it a little bit, especially with the multi Rebel stuff, but generally awesome, work, great stuff.

C

A

Maybe you would like to share something.

C

That I think a Mac and so which covered most of the stuff. But what I would like to add is that uh Rajiv did wonderful work, so we have already solved it based on which we can build the actual documentation. Afterwards, it's really wonderful and moving forward. What I really said. As early as we can move the content, we would see the changes that we really need to do.

C

For instance, there are certain syntax changes compared to the Google version and the docker source, so I think that should be the next step, that we should move content as soon as possible to the new one and then work on the changes that are required. That's the only thing that I would add.

C

A

Yeah, so for me from work admin perspective well, actually I was one of the people who was pushing for this project, because I think that it's really important to upgrade all the communication to.

C

A

New engine um now with small sub-projects happening like Captain life, cycle control or other projects, we discussed at Community meetings. um It definitely makes sense to design them for new documentation, structure right away.

A

Features would be essential to adopt the new documentation engine I hope that we would be able to finalize this feature so I see the scripts. Etc and uh yeah looks like this work is almost done and for us it would be super important to actually have the new engine when we get allowed documentation for the new projects for Captain. It's also quite useful at the moment, so we would be releasing captain captain on CS I'm, not sure whether we would move it to the new documentation engine or not right away.

A

But let's see we definitely have a lot of projects to play these legit for his work and thanks to all the mentors. So let's see how the adoption goes in the community.

A

So, of course, my expectation was a bit higher on the adoption part, because my perception that the project was not very connected uh to the community during the implementation and it's actually my main feedback to mentors and to Rajiv, because when you operate in g-soc, one of important things is to actually work in the open source community and to get direction. So when you have project in isolation it has limited value and limited contribution to the community. I'll say you don't get much feedback. So questions like uh external recommendation Etc.

A

If the requirements were clear, the main thing would be to reach out to The Wider Community right away. So there are.

E

D

A

There are other channels and I think this how it should have been done. So if you see in local Etc, the worst thing you can do in a project like gsoc is to just keep it to yourself as a team, because that is why the community, where consensus, could be built. But it's a lot of experts working its documentation, this code, this Automation and uh yeah. We could have defined the requirements here and there, and probably it would have helped the project to complete this part uh more quickly.

A

So yeah, that's the main feedback from my perception, but otherwise it's still valuable experiment for the community and I really hope that we have a lot of the documentation engine for some of the components soon.

A

Okay, so thanks everyone, any additional questions comments before we close to the Stream.

E

um I had one um around the community outreach um I think that we they.

D

E

At engaging with the community, but as a community I think we need to be more um active in general, especially I saw when we tried reaching out to the community for feedback and Captain Brock's Channel. We didn't receive as much feedback, so that is something we should be working on and for mentors as a learning I think we should have tried to make the Outreach more visible and went to more wider Channel, where we would have received much wider response. uh That is something we could have done and it's a learning for us.

B

B

Okay and special thanks to Moritz, by the way who, when we got in trouble with the CLI docs, jumped right in and provided all sorts of, help and good advice. Yeah and uh much appreciated.

A

B

When I forgot to put my camera on again shoot yeah.

A

When you present this actually.

B

Thanks for us with the camera on.

A

Yeah, especially for the stream, because otherwise the stream just shows me and Rajiv, and some of these uh taken from the background so by this quite strange in this regards how it streams to YouTube. But whatever.

E

I should have prepared more for this lately.

A

Sorry I just have a green screen because um there is no background support for baby yeah.

C

But what about the makeup that you have to do on your face? I, look like I, don't know clown.

A

Entertaining makeup this morning: yeah, okay, so yeah thanks everyone! uh So just a quick heads up um in 10 minutes we will have a community meeting I think it will be super short, um but let's see and then in one hour you have a presentation by Janam we will show k6 integration service.

A

So, if you're interested please join and yeah see you then.

B

And thanks Ken, Rajiv I hope you'll continue to participate in the community. We've enjoyed having you here, yeah.

D

B

Luck with your new job too,.

D

Yeah, thank you yeah. Thank you for everything like tremendous and Alpha, and also the kpdn community for giving Opportunity Shop.

C

Yeah thanks all again, everyone.

A

Okay, so okay, bye, everyone.