 Hello everyone. So today is May 27th and this is our third meeting for the building Jenkins.io with alternative tools project for Jenkins. Okay, so first, I think let's go over. Let's go over. See the document we have for this project. Okay, you guys see. Yeah, we can. Yep. So same project plan with, like, like I said, it's, it's, it's still, like, not completed yet. But, um, okay. And I think I should put also the structure here. And the project should include. I do include. Not good. So we should have goals and objectives through these two are your guiding principles. Success metrics, which can be just combined with mind stones and developers. So if we have rich as I'm targeted within a certain time frame, and it's considered success. So stakeholders and roles. This is simple for a project because we just have you and the mentors and maybe all come in as well and the community, the Jenkins community. So scope and resources available. So this one is supposed to be like something like. To be used for budgeting, but we don't have my consideration since it's open to us. And we use only mostly free. We saw since. So scope. Do you have any questions about scope? I have questions about success metrics. So should we go from there? Yeah, sure. Yeah. So the success metric will be according to the evaluations, the midterm and the final evaluation, right? Yeah, or weekly. Yep. So we turn. Okay. We can have incremental metrics if you want, but those may not be as well. So just meet them and find out. By. So the success metrics will depend on the midterm and final evaluation and what would that be midterm? I guess it will be the documentation that has to be built has to build with and Dora would be completed by then. And final would be the rest of the site. Yep. Awesome. Okay. Is it okay to dispute that? Sure. I think the project will have succeeded if docs dot Jenkins dot IO has version documentation, even if nothing else changed. Oh, okay. Yeah, you said that before, but I kept like, not giving a lot of emphasis. So dog dogs or dog. Docs, plural dogs. Jenkins. Yeah, so for me, the, the, the crucial thing here is versioned documentation, right? That is a key feature and getting that all the way to users is, is a great victory. If nothing else happened, if the blog stayed on Jenkins dot IO with with Ostrich that still versioned documentation with Antora would be a significant victory for the project. So for me, I, I think we should, we should, it would be great if we also got the other things transitioned to Gatsby that would really be wonderful. But I don't think I would call this project a failure in any way if it succeeded in delivering docs dot Jenkins dot IO with versioned documentation. What you're saying Mark is that we should the docs dot Jenkins IO should be the first milestone. Yeah, is that is that what you're trying to convey. No, no, no, I'm saying that I'm saying that if the project achieves that because I think that's large, I think if the project achieves that I would love for that to be the first milestone. But if there are surprises or things that derail us, I will not have felt a failure if we only achieved the first milestone. Okay, so this, this is kind of like a first milestone, but I got a question about the structure of new website. So I don't see it like, it's not supposed to be dogs don't you think I know right now right. This is just a structure we're going to migrate into because I didn't pay attention to it. Okay, I'm not sure I understood your comment Chris could you. It is not and that's why I like the, that's why I'm so attracted by the idea of creating that sub domain, or that that that host name that entry is that it doesn't exist now so we will disrupt no one by creating it there. And if it's created there, it, it leaves the old site undisturbed until we're ready to disturb it ourselves. Very cool yeah but I wish we talked to you about this because the hosting team is in for. Yes, so the, the Jenkins info team knows how to do that. We do it already with plugins dot Jenkins.io and stories dot Jenkins.io, and with, I think maybe one or two others. So the complete site will live on docs dot Jenkins.io after this project. Right. Oh well so no so so for me I would, I think that it would be just fine if the versioned documentation were on docs dot Jenkins.io and everything else could either be on docs, or on on the www dot Jenkins.io either is fine. For me the transition from version non version to version documentation is such a significantly valuable transition I think we should do it there now. Again, I'm not, I'm not lead mentor so it's perfectly okay for Van Deet and Chris to say no mark you're wrong. Don't, don't be shy and saying that no I'm just. I think I think it's a good idea. Yeah, because I never seen docs dot Jenkins.io before that's why I was like, it could be, it could be workable but we need to coordinate with like the info team to do it. Correct. Let's see so credit tokens, or the adults, or the adults. Right and likewise stories. And accounts too. Yes, yes, that's right to I hadn't even thought of accounts is a very different thing plugins and stories are both static sites accounts is is a is is really a different site because it's a non static site it's got a database behind it and is yeah. Okay, so I'm also success metrics that goes okay and our questions about success metrics or grows and project objectives. Because like it's like for some people they define goals and project objectives a bit differently so well they can be the same depends on like how I like it. I wouldn't like I wouldn't we straight you to define it in a particular way but you could like you could have just oneself objectives. And on top of that goals, we can just have like goals or just objectives. The project objective the project objective is to migrate to Gatsby now like the major part will be on Gatsby and to version documentation. So the. So these are the goals we have right now because everything will be like most of the things will be on Gatsby. So we can say like, for example, like, let's let's do it here. So goals would be to migrate to. Documentation I guess. And the objectives would be so meet your numbers. Subjectives would be to migrate. Documentation. I think the most important part, as Mark said, is this point. Gatsby is no less important. Okay, have like, I think, I think like if we use this convention. We can also have a mushroom is done this right now we can also have blocks. Yeah, we're like, we'll actually get version docs done with and after that, like that gets like you said Gatsby is not that important. It's for the rest of the site and like, we can make maybe we can like, if, if things are going well with Gatsby and we have completed more than in a more than half of the Gatsby site, maybe we can like file in for extended time period. Okay. If we if we have if we like get things done on Gatsby in part. Yeah, sounds good. Okay, so stakeholders. The stakeholders are community and the Jenkins infrared team because they currently Jenkins and fra host the Jenkins site. So the infra team. Yeah, agree. So, these are the main steps. Yeah. Are there two is, is there, is there a way to, is it worth it for us to differentiate or to make, make it clear that there are authors who are certainly one set of stakeholders roles good okay so they're authors people are content contributors right. And then there are readers. And, and those, those I think are both interesting stakeholders right the Jenkins community is sort of a reader, but Chris Stern, Mark Wait, Kevin Martins, Alex Brandis where we tend to be authors gsoc gsoc contributors writing blog posts tend to be authors. It will be better to like call it developers. Yeah, that would be vague. Yeah, whatever word helps us that I have no problem with I certainly when I write I'm doing development that people. Other people tend to get confused they think they, there may be times when they think development is creating the scripts and the tools that build the site. And that's distinct from writing about pipelines and writing about why you should do things this way or that way. Yeah, we can we can yeah it's like Chris wrote, we can replace the readers with users, because users read the documentation most most of the time. Right. Okay. So, how about this. Kind of for those of us readers co contributors. I mean, there is. Yep. Okay. So scope and resources available scope. Because it's kind of a scope would be, um, well depends depends on depends on progress. Initially it is a version of documentation right. Okay. I'm a bit confused about the resources available like what does that what is it trying to say what are the resources like the tools we are using. And Torrent Gatsby are these the resources. Yep. That was our example. They're like, they're like, they can be but resources. So it can be like, um, and so on. So it's ready. It can be Gatsby. So, um, domain by input, which is like, which is not, not free, but we have, we can, we can open a ticket for it. Can open a ticket for this. Okay. Subdomains. Okay. Also, I think other things that are like resources that are available. Could be, could be anything that's like, I'll just put exactly for now. Those are not as important. I'm trying to get hub good. These are the main, main resources we have and will be extensively used. Yeah, but are you on Mac or Windows? I'm on Linux right now. Oh, Linux. That's cool. That's easy. It's kind of like a Mac. It's like, my Berkeley, my Berkeley roots would be terribly offended at that. Okay, that's great. Okay, next milestones, deliverables and project dependencies. So, um, I think we should, we should grip it as such. So milestones and diverse. So you have to work on this, which is similar to what you have in your proposal. Because you have the days, but you may need to revise them. So should be a Yeah, I like the dates will be revised, but the main milestones will, I will be same. The duration will be revised. Mainly to, yeah, mainly to revise. So, okay, next project dependencies. I don't think that's much like, well, I can only think of one hosting. The new sub domain will be dependent on us having a drop in the site. That's it. Anything else you guys can think of? I can't think of anything that will be a dependency right now. It's, it's, it's more like a fun and project. So it's like, there are not much dependencies. Yeah, not like a bad importer. So my schedule should be Chris, I just realized there is one more dependency and maybe it's it's related to the hosting of the new sub domain. So we will certainly want preview sites to be available. While working through iterations, right, so CI Jenkins that I owe today does preview sites of of changes to Jenkins that I owe and they're very, very helpful for to evaluate. It's just a natural flow out of the Jenkins CI, CI project process on the current site. We may need Gavin Mogan's or someone else's help to set it up for the for the docs that Jenkins that I owe sub domain. But I can ask Gavin about this later. So Vandit, were you comfortable with my phrasing there I think you've already used the preview sites. Yeah, it was discussed it was extensively discussed in the main ticket about the migration that we would haven't had help because he handles the previous stuff. Yeah, we can talk to him. So communication time I think it like for timeline schedule should be it's just it should be like something to come to mind. We have four milestones and three verbose. So should be same. I can like I can put them in a table with milestones and timeline like weekly milestones and main milestones. We can use a do have you heard of this before, like a game chart. Yeah, I can do yeah we can work with that but they could. Yeah, I'll have to create an image for that because the keys don't like really support Gantt charts. Yeah, by default. Yeah, I can try. We could use which is free, or maybe what we have, like, talk about before. Okay, I think it might have like a game chart feature, but you're not sure how to test it. I haven't used it in a while. I think like for some software like Monday, they do have a game charts. So if you have a like a camp and boy, they would often make a giant job for you. Yeah, there are there are many tools for Gantt chart, but I might have a difficult time like actually inputting the data because once I have created a Gantt chart and all the data was messed up after inputting it. I'll see what will work best. Okay. Okay. So communication plan. So we have four mentors and you, the contributor. So we should establish a most for which kind of channel for what type of communication. So first, maybe get in. Next would be an email. Next would be a certain calls. Okay. It's obvious. Because it's used for weekly. How about guitar. So for. Conversation for day to day updates. Okay. So for day to day. Maybe it's a method. For. So email. So it keeps for time and for exhibition for maybe time. Managing. I think it's next space and. Weekly. For zoom is like weekly games. So anything I've missed. Or this. No, we got a month. Okay. Good. So it's one day good enough for you. Do you want more days? No, I'll do most of the stuff by tomorrow and I'll like, I will, I will like inform you to give it a read if everything is there. And we can like build it, build it, build it from there. The wiki. Yeah. And. So maybe make it. Okay. Yeah. So we've done, we've done that. So it's just detailed milestones and deliverables. Maybe, maybe. Look, should we do it now or do we have the time we do have a little bit more time. So do I have your. Where's your, do you still have your personal somewhere. Yeah, it should be there. Yeah, in the link. I'll send it, I'll send the link to the guitar channel. Wait. Okay. Do you want editor access. Do you want to like change things? Yeah, maybe just dress right now, not for public, not for viewers. Yeah, I've sent it there. Okay. Okay, so for, I think it's in some way, so proposed timeline. That includes all the project developers. Okay. Too bad. I don't have a link to it. Okay, good project developers. Maybe you should make these more incremental. Is it possible. Because like for the website, if we go back to Jenkins IO. We can see like, it just just for just for documentation, maybe just for user guy. There's so many sections here. Like version pages, tutorials, developer guy, and even for developer guy, it's not trivial. Yeah, we just have to like move it there. We don't have to make it worse and change anything in it. Yeah, but I'm thinking like for for your deliverables, you should like have smaller tasks and more detailed planning. I'll, I'll be, I'll be dividing the larger tasks into small ones in my timeline. So like, you can track the progress if like on a weekly or a bi weekly basis that this will be done by this week. This will be done by this week. And this large goal will be done by after these after this, this number of weeks. Yeah, go ahead. I just, this will be sorry, but I'm thinking that for this project, we can do weekly and so by weekly, because I am expecting you to work on this pretty quickly. Yeah, so because like the concepts are quite simple, but the work, the final work may not be. Yeah, the work is simple too, until we get we get hit with the roadblock. So, so we can plan up to maybe by the end up to August. Yeah. Yeah, and we're looking forward to how whether to change it later to apply for extension. I have like, how when can we like when can when can be when can we submit for timeline for extended time period extensions like maybe August for if you want to extend it to September. I think it's by, I don't remember exactly how it's done but it could be weekly or bi weekly. So we can, we can, we can like discuss about that on week 11, like that will be appropriate amount of time. Yeah, by then the program. Yeah, by then we can, we can decide on the basis of the progress by then. Yeah. Yeah, cool. Yeah, so also let's say efficient improvements. So I think I'm going to have a timeline was not very detailed, but it was sufficient to get the glimpse. So we have to check whether you have everything here. So first thing you I bundle so have you ever done this step already. I just I have to yeah I have done that I just have to start working on the UI bundle. It's relatively easy because I'll have to implement the table of contents the sidebar to match the current Jenkins layout and the colors. Because yeah, go ahead. Yeah, because in the inversion documentation there's not many men like there's not many components that need editing like there are not very. There's not much components that need to be redesigned there and we have table of content sidebar and maybe I'm forgetting the word that arrow thingie that we haven't been concerned I have for for switching to the pages. Yeah, you mean navigation. Yeah, yeah. pagination pagination. Oh, passionation. Yeah, we sweet sweet items up top. Yeah, yeah, so we'll be like so that will be done. It will take less time, but I'll have to check that it is working on each in on every page and like that at the time that will I the more time that I will like use will be on checking things to because there are lots of pages on in the documentation. Yeah, so you have a bundle will take around like, I guess one week, one week. Yeah, it will take it will take around one week. Okay, one to one to two weeks. Yeah, like one to two weeks just just to be on the safer side. You're just in case you have you got stuck in anything. Okay, so let's just focus on weeks one and two weeks. While working on the your bundle like I while working on the other things will be like, I, they will be done while working on the like they are related to it, like the navigation structure and that Okay, some part of all these is completed. Okay, okay, so I just knew track a repo right for component. Yeah, yeah. So partially completed subject people according to the project. So this is like after you've completed the work on the restructure right. Yeah, the playbook project with the playbook project like I'll have to see I'll have to update it once everything is done in the UI bundle so like it fetches the new UI changes. Oh, that's easy. Yeah, that's like, yeah, that won't take much time. Yeah, because like, I'm trying to learn toys. I quite accept the UI is quite a bit of hassle. Yeah, yeah. I think we can remove the fifth checkbox because like, we won't be using the existing fifth, fifth, fifth, yeah. Take the existing modules. We can remove the take the existing modules checkbox because like, we won't be converting the existing modules. Yeah, yeah. Okay. So this is the things that I'll have to do for the first two weeks. Okay, good. Okay, so what do you mean like for like I like I explained in the last meeting you for the site for the sidebar navigation on the pages, the table of content you'll you have to manually write in and giving the X ref links. Yeah. So that is what I'm trying to say, set up a new navigation structure. Is there a way to automate this, like if we add a new, or do we have to manually do this every single time. I can, I can check with check in with the entire community for that if they have a plugin for that. I don't currently know if they have something like that but what I have seen in the documentation there is not like explicitly stated that you can use this or that. Sounds good. Yeah. And then we'll leave weeks to info until next time. Yeah. Okay, so it's this one that's done. Check for four weeks. So it's arrangements for cool use my mentors. So I think I expect all four of us will be using a code, but maybe I must. So Mark will definitely do that. And we're different. You mean we do that, like, if, and when they have time. But the thing is that only, I think, currently only mark and I have to have to merge accents. So you need to ping with Jeff and you mean on every PR submit. But I think we're not hang on. We're using your report right. And we're not on it so every time so for for for for that case. How do you handle that we've been caught that way because they will you were using your private account repo. And isn't it that Vandeep adds Rajiv and yimming as as collaborators collaborators that's the word. Yeah, I have already, I've already sent them the invite. How does it work for PR reviews? Can we open PR that way? And once it opens, how do we have where I haven't tried to do that way yet? Maybe we can, I can, I can like send send the link to the guitar channel every time I raise a PR and bring everyone there. Yeah, because I checked it. It works a bit differently from like, Yeah. Yeah, the like most everyone will have to own will only have to check the getter for new updates. Okay, sure works for me. How about what you've been you mean any concerns about this? No, no, it's okay. Yeah, it works for me. Okay. I think we could open PRs. If PRs. Let's try that way. Okay, so any other issues you talk about today? Nope. Everything is all right. Okay, so let me see. So I think for me, I'll have to start and okay. This one should be okay. Okay, so any other questions from other mentors? So Mark, do you have any questions? Okay, what do you have? I don't know my thing. Okay, you mean any questions? Any concerns? No questions. Okay, so let's stop here. And that's, so I decided it's time. Okay, for everyone. So just want to check because like, some people may have things to do weekend. Okay. Cool. Okay. So we'll see you guys next week. Thanks for coming. Thanks. Thanks. Bye everyone. Bye. Thank you Rajiv. Thank you. Thank you Chris for your time.