 you're learning the magic yeah so hi everyone today it's my first meeting for the gsoc uh building jankens.io with alternative tools project and we welcome our contributor servant hi everyone would you like to introduce yourself uh yeah wait a minute okay yeah hi everyone hello so vandi tell us something about yourself introduction is not enough just to say hi yeah we want to hear more about i shouldn't yeah i should introduce myself hello everyone my name is vandit singh i'm based off deli india uh i'm really interested in many technologies and there's a lot to learn but there's a little bit of time for everyone when you're in college so uh i've been contributing to jankens since i guess july i start i tried i tried contributing since july but i got my first pair much around august i think so yeah hi that's for me all right so um that's our agenda so let me share my screen let's see so i should choose um okay okay i see my screen yes okay cool so we're going to talk about some action items first because we have been assigning all these items to complete before the end of the bounding period for the project so first contributor bio any questions about this vandit to know where i guess i i have already like i have created my file there already when i was i was updating some documentation i guess it was uh at that place okay cool so uh i'll leave it updated yeah but better than a photo as well because i um i i think you like some okay so no no issues about that right it's okay yeah it's all clear yeah so next we have uh to to write a project page with details so this is um i think this is a page i think uh if you want an example i think you know where to go but so if you want an example you can go and check out the get that plugin modernization project because they have already done so but for that for that one i think we've discussed some items about that before as well because like um hang on let me share my entire screen so that's all this content just but anyways so as i i think for this page here because like uh we had some discussion about before about that one here because for for you can see on the right hand side here right so on this page we have abstract rationale implementation of this ours so for and also we have at the bottom here links with gitter meetings or your gsoc project idea giant gsoc page but uh for some reason there's there's like um the links here if you play around with it i'm not sure if it has been fixed probably not but thing is uh for meetings i think this just goes back to the same page but we don't want that for this so we want that to be linked up to say the document we have like here for example okay so like going circular so that's one thing uh the original gsoc project idea i think i think it should link up to yeah the original project idea page which we used for like for for the the application phase seriously so that's what you've seen before like for your projects probably let me go back to this project so for this project it's probably this one so we can see the details here okay we should have a link to this page so that's that's what we should have for our project so let's see what else we have to pay attention to so i think let me go back to gsoc this like right now like you have remember when you after you have done your like file link it up here as well because like right now it goes to your uh github page but we want it to be kind of like this oh not yet oh hang on yeah because like i think we forgot to tell harsh to the update this just um this can be changed uh afterwards uh i meant this one because like it's just linked up to page and save a github page but either one is fine so depending on what you want so which one do you prefer so for this one yeah um an author page on jinkensio is is needed uh as soon as blog posts are published so we should update this one yeah okay and so this did the general page and there we can either point to the github profile but normally there it should point to the Jenkins profile uh we can have or for that one we we can also have a link to the github yeah voila and maybe show also the sources of the pages otherwise people are going to to be lost okay okay good okay just a tip yeah i shouldn't fill my fountain pens while talking to spill everything on my desk so right now where the page is blank but we rather have like um the mantras links here so that's taken care of the only thing we need to change is contributed like here we have to add details to it which includes abstract rationale implementation uh office hours we should state always do Chris what will be added in that rationale section uh which is rationale section so i think van deet was asking what should be added in the rationale section and i would think there it's the that's a that's an opportunity to describe why and and the motivation or the inspiration for it and if you look at the original project idea that's a good source or your project proposal that you submitted that we reviewed and that those for me would be the ideal things to to just copy and paste in there yep yeah okay okay so we should it should be kind of like uh lastly this one so for the gith lab plug-in monetization the rationale would be the plug-in be more nice because like we're using some outdated software called rest easy but for for for like the um because let me think because there should be a link to you know choose to go back here and we do this if i go back to here i think the rationale is here too because like it should be somewhere like for this project i think it's in the background section so it's like uh the first paragraph i think we tell you why we have to update the product the product version bound line i got it yeah you can just like paraphrase this paragraph as a motive rationale or the motivation so let's see what else we have so so you can just i think for for um we're having too many of these so for uh let me go back to here so for i think that's one section that's we done on here which is links so we can we remove this what you do uh because like uh for uh by default we already have a length section at the bottom so it's like if you go to yeah you'll see you'll see what i mean later once we start working on that but um i think that's so you have to you have to work on four sections in total abstract rational implementations and almost ours mean god okay so that's the project page in details so also we have to uh this year we're introducing a new feature to add to the Jenkins.io website which is the contributor blog post to to present the project at the beginning as well as to present yourself so wait some paragraphs to explain your background why why you chose this project what do you hope to gain from it um what are you planning to to do in regard to the project for the project for for Jenkins so that might be some so uh in the blog post do i have to add some technical details as well right so again like what what in in the blog post do i have to add some technical details like what will what will i'll be doing uh in like next two weeks yeah are you good you're good yeah yeah yeah it depends on what you want but the basic idea is that you have to like its actuals so basics would be to um let me see who you are yeah okay so we need to say something about project description or motivation it's one thing so um some a short um a short file to introduce yourself to introduce contributor and also maybe um like you said plans for new future or maybe um maybe first two weeks maybe uh first few weeks or first okay Chris would it be would it be useful to include by the time that that Vandit creates this blog post i think the author page will already be there and the project page with details so link to the project page that that Vandit may allow you to put more technical details in the project page and just link to it but it's up to you it's your blog post but but the the project page details will already have some technical details in it and they may be enough already to just link to it up to you maybe we can just add some some maybe two or three lines about the preparation i'll be doing and technical details will have like in more the what will i'll be doing for the first week if that sounds right yeah i like that that sounds very good you're you're talking to the to the community and they don't know you and so well you can also share what your feelings are starting this this adventure but they would like to know who you are what you intend to do what is this project about so just share that yeah that will it would be nice if i add i'll add non-technical i'll write the blog post in like in a non-technical sense so so that the community who does not know the project will like understand what i'll be doing yeah and i am feeling nervous so i'll write that but yeah but it's it's it's a good call for them to bear with you to help you and another tip about blog post but mark will probably guide you also with that is don't make it too long the temptation is to put many details so write your first draft and then try to condense it yeah i'll i'll get i'll yeah i'll get interviewed by mark and chris great okay and the other things like uh maybe what jiff and you may want to end uh yeah so like this blog post is starting blog post right i mean let me see right at the end of this forum so are you planning are you planning to have a blog post blog post like weekly or bi weekly uh no it's just just for for the bugging period yeah it's just for the bugging period and maybe another one for for wrapping up but wait yeah it's to start yeah we we can have yeah we can have a weekly one but it depends on what um or if any ones and also like it depends on like yeah yeah we could do that too yeah because like for some projects they do require that yeah yeah i don't like i mean i think so for this because i don't think we need any between the blog post because not so many maybe we can have a bi weekly or maybe midterm uh big blog posts that meet them in the past yeah like what we did but maybe one day if one day is doing the personal blog posting like many people like we focus on seeing like uh on a personal level like doing the blog post like whatever the work they did i'm i'm a little hesitant to sign up for more frequent writing in the blog i'd rather focus bandit's efforts on creating the software but but i know objections if bandit is passionate about writing great but i think for me the time is is more precious to spend on on doing the changes and there are a lot of changes needed in this particular project proposal so i i i as a mentor i would hesitate i would not like be willing to say oh you must do that it's up to you bandit if you choose to but as a mentor no way would i apply the requirement that you must what i have seen in other organizations is that g-stalkers normally uh write three blog posts one during community bonding uh second after the first evaluation and third after for wrapping up everything so i think i'll go with that format that it will it won't put much pressure on me to write weekly what i'll be doing like we are already documenting things so putting the link to the document would be nice if someone wants to dig deeper into the project details that sounds very good to me thank you you mean do you want to have anything you want to add nothing new from my side i like the details currently okay cool so next thing we want to talk about is a project plan at least it's going to check it because like for the jenkins website we already have uh i think we already have um no you're not this one because i really have a ripple say oh we should why this one yeah this one so i was thinking about like maybe uh like doing something with the project here because they already have some items here but i'm not sure it's appropriate even though i have to i have to invite to do that i may need to ask first for i add a project here maybe here so i could do that but um the thing is i think if if i'm going to do that i would be the only person who is able to change its update details but not mandated or we could alternatively we could set up like uh say private ripple and uh no not a ripple but um a ripple uh in our own um yeah i can't let's say let's see so for my project trees i could probably like i start like i say uh a new one say so i can i can do say uh i can say jenkins io um two or maybe jenkins io but i'm not going to do it right now because like um i'm just saying like i'm just proposing an idea i can say like um i'm told no yeah so i i'll make it public do like if if you want to do it this way do make it public and uh i think it will begin i did forget indeed to do it so you can you can like in your own like um i can't open the new repository with the names in between this one let's say and make it public uh so and the next thing to do is to like start building from your new repository that would be easier for us to wait later but do it right yeah then later we can like uh we can like make a branch on the main jenkins dot io uh pushing a master bank because like they're using master yeah like it would this would this would be very i will work for like till the midterm evaluation and after that if things are rolling good we can like create a branch on the main master branch uh yeah master yeah on the main master okay yeah i that would be all right i guess because um i yeah yeah we remember to invite all of us to like i mean the mentors team to join your iphone and to have like access right to it so we could monitor it and make changes to it if we see anything like um we we would like travel changing maybe not all the arguments but at least all the mentors so it's like um mark uh yiming which if and me yeah yeah we can do that yeah so uh project so then we can uh in in that case we can use a wiki so uh let me see so let me back up first okay so we can use test features so we can use a that's like as much wiki pages using wiki so this is um i think manage quick okay so we could we could use wikis for for setting up your project plan project plan uh do you have any like do you do do you have any concern about this i have never used them but i think i i i'll work on that and i'll inform you how i feel currently i don't know i have never worked with wikis yeah because i can show you like what i mean because like you have to be um yeah yeah an example would be nice yeah because like we have we do have like the gate lock plug in or it's like right now it's open to the public so we can just see wiki here so the thing is you can add things to it the home is just like nothing is here yet it's just as welcome to the gate lock fucking wiki but someone else has already done like some documentation in it so it's using mark down so wiki will wiki will contain the uh information about entoren gets me right uh yep that's that depends on what you do is like this is just an example to show you what you can do with it but thing is for for like for for this one so i would like you to like in case you're setting up settings go to features we strike adding to users and teams if they can do so that'd be great so we check this box after if invited us to a team yeah so we will be more private but at first we don't have to do it but in in case like you feel more secure that way you should do that that way too yeah we can we can we can start working like that if i just i just wanted to clear one thing the wiki will be used to host the document the documentation the documenting i'll be doing uh about using entoren gets me right uh the wiki is for the project plan or not oh the only the god only a project plan at first if if we finally use for we can we can use it for other things as well for the documentation too but um um i think uh we should keep everything to the project plan yeah yeah then it's yeah that's that sounds right then okay okay cool so mark raises and oh sorry i didn't say mark yeah go ahead i was just trying to trying to understand the the a piece you had described earlier so initially your idea is that vandit will create a separate private repository for sort of rapid experimentation that isn't based on jenkins.io right is that it's it's so later on we will push a branch from this repo to jenkins.io repo that's that's the idea but first we want to have our own repo first so we have we can like set things up more easily and test things out first right okay so so this is a this is a safe space for vandit to do rapid rapid experimentation rapid evaluation and then then there comes there's comes some time when the project team agrees it's now ready enough to get close to jenkins.io by starting shifting to being on the actual jenkins.io repository is that is that what you're describing um yeah okay thank you i just needed to be sure i understood it so it's it's somewhat similar to what what uh basal crow did when he created his prototype of anthora he created a disposable prototype knowing that it was intentionally fully disposable and and when we get to to real production it will go on to the official location that sounds good to me yep okay so let's let me let me like write down so um we set up a new private repo for oh sorry finally pushing the bench maybe i think the bench can be called anything but master so you can call it manually you can call it um because like we don't want to force push into the main or master bench that's like because normally that's protected push the bench and now now you used the word private repo but i thought that you were okay if it was a public repo there's no reason for vandit to new oh got it i see okay yeah you're right it was a typo okay so vandit i assume you're comfortable with that but this this methodology works for you i saw you shaking your head i i like that that's great okay yeah because i i knew i i have written that this is my proposal about the branching part but i was kind of nervous that it couldn't because i have tried doing that on a personal project before handwriting it there so it was kind of difficult you can say to start a new branch completely from a project start a new branch with content different different from all the other branches completely different from all the other branches so it would be uh difficult to handle so this repository thing will be easy to maintain and easy to use it will be like a playground for me so i can work faster great yeah that that thank you that you've you've confirmed you understood the concept i needed to ask some questions to be sure i understood it thank you okay good so next is to engage you sorry what was that vandit it was a the last thing i think there is a connection problem yeah so it's like a pros and cons can you hear us do yes now and date and date oh i think i think it's like it does some connection issues can you guys hear me yes i can hear you just great yes yes and indeed froze yeah yeah i can't need you good okay good okay good so next stage will be to like get the community involved the most important thing is like how are we going to set up the the whole website with the new tools but to and wise we for like for most parts we have discussed but for the west so would you like to say something about it and date oh awesome it has a connection problem yeah i think it's on this side if i can follow him hi guys i'm back uh i my router he started i guess congratulations and and welcome to the internet come on think about what we're doing here right we have two people in china two people in india a person in belgium and a person in the united states talking together in real time okay occasionally there will be a bump yeah okay yeah what did i miss uh i i didn't hear anything about that initial email part if that has been discussed is it discussed we were installing it but you you just you disappeared so the thing is like we have to talk about like which part to do which with entour and gasp so uh for the user documentation entour for the developer documentation entour block gasp and i think for like one two three and that's the west yeah so any suggestions entour or gasp so my my preference we will use entour for everything except the block that's my preference so is is that isn't that something we want vandit to explore because we can't lose security information we can't lose the the non-versioned components right the the documentation will be a versioned component and the non-versioned components we can't regress so vandit's challenge will be okay how do we how do we retain the changelog and the upgrade guide and the the security pages and the google summer of code pages yeah i have i have i have seen that uh entour out of the box does not provide anything regarding dot yml files and the changelogs and roadmaps are generated from dot yml files so i would i but gats gatsby provides plugins for these things so i think it would be correct or like it would be a great starting point if we start if we use everything from entour and the components like the changelogs and the roadmap that are the only thing that entour does not like generates we can generate them with using gatsby and the block part okay okay that's what you mean now so you have in here how they generate the changelogs yml roadmap yeah yeah they generate dot yml files use gatsby generates dot yml files using plugins that reads dot yml files and uh create an html site uh page html page from it so i my preference would be everything would be from entoura expect the blog and the dot yml files okay so accept the changelogs accept the roadmap everything else accept the block too like everything else should be in entour i i i love plans and i'm always surprised at how plans get reshaped as we learn more old military saying okay so um bandit would it be okay for you for you to write like a brief motivation for like what we have just discussed so i can relay that to the community in an email i'll send the email but i want you to contribute to the yeah uh so it will be like a blog post for the community or why we'll be using uh shifting shifting to entour and what parts will be uh generated from gatsby yep yeah is that what you're saying yep yeah that's what i can write that okay so i can write that you can like you can send it to me before next Friday we'd like you leave that be okay yeah wait let me just write it somewhere so i don't forget okay i'll run you too okay i'll i'll send it to you by by Friday okay cool so i'll send it after i've seen what you've written and i'll add some details to it to introduce you to the community too so uh what else do we need to do so on the agenda we have so uh interaction gone through action items so any other questions you have about like what you need to do for next week no uh i'll i'll just sum up i'll have to create a blog post a project page description all the things uh and the project plan would be on wiki i'll explore that how to use wikis uh and a blog post for the motivation why we why we'll use entour for the most part most parts of the site and road maps change logs and blogs using gatsby okay yeah i also buy the most important thing is like to begin with the first thing you should have it before you can like update is a bio then project yeah i'll update it after this meeting yep then blog post is not urgent so blog posts you can do anytime before the bonding period ends okay but uh the contribute but the contributor blog post should be before the blog post about the motivation why i will be using entour for the most parts right um for that it's just to to expect to the community so you can you can you should have it ready say uh well because i don't want to put time pressure on you i don't want to rush you to complete it but you can complete it next week if you want to so we can share it with community earlier yeah then i i'll i'll complete the contributor blog post by like by the by friday and the motivation motivation blog can be like on monday and or tuesday like i can write that on the weekend uh and project planning can be after but it has to be done before the bonding period is over so last yeah project plan can be done last yep for the community bonding period yeah that's yeah we had so the thing is i think i need to set up the set of um set up perfect okay this one i should have started to uh to do it later okay very good any other questions no uh i don't have any questions i'm totally one two three four five things for you to do this week and next yeah okay so so we go okay go ahead oh vandi in terms of exams and other things that may be of importance in your personal life that we need to be aware of if you can just be sure that that we know when those are so that we don't make heavy demands on you that no one makes heavy demands on you at the time when you're doing school work uh i don't i uh my exams maybe we will start from 26 or 27 and the community bonding periods ends on 28 so i think it won't be much of much hindrance for me like i i'll be able to do most of the work before that i have i have i have planned my studies so i think i'll be free thank you so you don't need to prepare your exams i have considering that considering that uh i'll do most of the work before my exams okay good cool so why won't we be away for exams my exams will be one week maximum one week uh and during that i'll i'll join the meetings and i won't i won't be able to do like code work or setting up things so yeah any any other thing i should we should be aware of not that can i and not that i can now recall or i have anything planned okay so uh no vacation plan right excuse me uh no family vacation plan no no no family vacation okay cool yeah good so it's time next time we're gonna meet it's on Friday it's next Friday yeah okay cool yeah next Friday seven PM IST then IST okay so um anyone any any other mentors or anything that they want to add like which evening no thanks just sincere thanks Vandit looking forward to this we are going to have fun we're going to watch and observe you're going to do a great job thanks very much for your already existing contributions and looking forward to the contributions you'll make as part of google summer of code yep thank you my friend that was nice to hear i was i'm so nervous are you yes i am but we'll fake it until we make it yeah so if you have any questions feel free to ask us ask the questions in the channel yeah on guitar yeah i think that well so yiming went through the same thing last year so you can share experiences do a part of us too yeah okay look again next week so thanks everyone for coming and uh stop recording now