 Recording is on. Good afternoon, good evening, good morning everybody around the world. Welcome to this first office hour of hours for Google Summer of Code 2023. Big news is the Jenkins project has been accepted as a mentoring organization for this year's Google Summer of Code. So we're very excited to start this new season with a lot of people interested, mentors, a full team of people that want to start working together on this great adventure. First a little presentation. So my name is Jean-Marc Messen. I'm located in Brussels, Belgium. I speak normally French and I can speak a couple of other languages and I still want to know more about Indian culture. So I need to visit India one of these days because we have a lot of people from the eastern hemisphere. So we have also round the table, Elissa Tong. So Elissa, if you can present yourself trying desperately to unmute. Sorry, I was trying that unmute button. Hi everybody, welcome to Jenkins in GSOC. So I'm a a long time Jenkins contributor. I've been with the project for during its Hudson day. So it's been a while for me and I love the community that we are in, that we are building. So and I love and enjoy being part of the GSOC as one of the mentoring orgs and org admin. So welcome, glad to have you and hope you'll stick around. And you're on the U.S. West Coast. Yes, I am in California. Early morning for you. Yeah, eight o'clock now, eight a.m. Great. Then we have another key player as admin role as org admin. We have Chris Stern located. Where are you located? Where are you doing? Who are you? Okay, so my name is Chris. I'm from Hong Kong. I can speak Cantonese, some Mandarin and English. Not much French, exactly. And I do software development at a consultancy and I mostly deal with web development these days. So in my spare time I'll code. That's it. And I'm going to give a few. So Chris was participated to Google Summer of Code some time ago. Yeah, in 2019 and 2020 with Open Astronomy. Right. And he joined Jenkins project and got involved for mentoring. And he was a mentor last year as well as an org admin and quite active. And then we also have Bruno who joined the org admin team. So go ahead. Yes, I'm an org admin team wannabe. I'm just looking at what's happening for this. I'm not doing much. Just observing. So I can talk French somehow because I live in France. I'll talk just a little bit of English and I'm not far from Jean-Marc, something like 200 miles from Jean-Marc's home. So we're almost neighbors when it comes to the world. I've been a recent, I am a recent Jenkins contributor. Earlier I was working for another organization. But I do like our community and I'm pretty happy to be a relation developer for Jenkins project. And yeah, I'm happy to see what you're going to build for Jenkins this year. So as Jean-Marc said, I'm an org admin wannabe, but I'm also a potential mentor for one of our projects. We'll see that later on. Great. Thank you, Bruno. Just a little word. I will retire because I'm older than I look. And I will start a new page of my career in caring for other projects. And so we're preparing that the program. So I will hand over a lot of my duties and I'll stay behind the curtain to make it work. In 2024, Bruno is probably going to get involved together with Chris. And so we'll have a strong team for next week. This said, I'm not looking forward to retirement. I'm looking forward to a great Google Summer of Code 2023 episode. I see a lot of interested people. We're now 25 on this call. Thank you for joining. I know it's late, even very late in the Eastern atmosphere. Thank you for the effort and very happy to see you, meet you, or see you on the call. I see mentors. I see people whose name I've seen on the Gitter channel. So welcome, welcome everybody here. And we'll try to work together to make it enjoyable adventure, a fun one, and especially one where everybody will learn something. Google Summer of Codes is a program that is competitive. So I want to say the things as they are. A lot of people are interested. It's a demanding program and we have only a limited capacity of mentoring. So we'll have to choose and as difficult and painful that it can be, we'll have to make decisions. The choices will be made on a ranking based on the proposals that will work now in the coming couple of weeks. So you will work on a proposal for a project. You will submit it and the mentor team will rank that. Frateriors are basically who has the highest likelihood to achieve the goals of the project and to bring it to a successful completion in September. We can explain that later. So there is work involved. You will have to work to get a strong proposal, trying to be the best in there. And when you select it, if you select it, then the other part of the fun will start. So it's, as I said earlier, this is like climbing a mountain, a great adventure. You're going to see great things. But there's effort and sometimes you're going to say, why did I volunteer for that adventure? But you will be very happy once you achieve that. So we're there to help you. We want to make you as successful and even if you're not selected, that you'll learn something from the experience that you can reuse afterwards. So this is why one of the things that we put in place is we're going to hold this meeting every week. It will be an open meeting. If there are no subjects, we can discuss football or cricket or whatever. Indian attendees can try to explain me the cricket rules. I'll be more than happy to learn to learn that. But here we're mostly here to discuss any question doubts related to Google Summer of Code with Jenkins with the projects. We'll try to cover as much as we can. Some of the questions will be pushed to ad hoc meetings that probably at a certain point there will be dedicated meetings to discuss topics around these projects. This will always be there. So if you're lost, you don't know where to go, where to ask your questions, at least every Thursday at that time will be together. Deadline. So as in life, you need deadlines to keep them in mind and live with them. For this phase, your deadline, talking now to the contributors, students, you will have to hand over to the latest for April 4th your proposal, a document. So there is a template that's available, that you need to fill in, improve. That document will show that you're understood the project, that you understand the subject matter, that you come with novel solutions or something that's stand out. Pratam, I've seen your question. We're going to share that in the meeting notes, the link. So the question for Pratam was to where is the link to that document? So going back, you need to show in that document that you understood the project, that you know, that you know what you're talking about. Well, yeah, I don't laugh. There are sometimes surprises that you come with novel ideas and that you show and demonstrate us why you have better chances to succeed than your colleagues, because you have already program experience, because you already contributed to the Jenkins project and so on. We can help you and guide you for that. Second important point is that based on our experience and based on the ways of open source, the main purpose of this whole exercise, beside having a nice line in somebody's resume, is that we learn together how does open source work, how you contribute, what is the culture in these kinds of things. And can be also helpful for your professional career. So the first important step that you're going to learn and will be quite frightening is that we will ask to make your proposals and your work documents available to everybody. One of the principles of open source is that everything is open. You share what you do, you ask for opinion of others, we're working in public. That means that we'll ask you to make your work document public, submit it to the Jenkins community and they will take the time to guide you, answer questions, clarify things that are not obvious and make you build a strong proposal and will help everybody equally. We don't want to, how do you say that in English, but we don't want to favorize, how do you say that in English, to give an unfair advantage to one or the other person. I'm sorry, I don't find the exact English word for that. So we want to really help equally. That means that all our answers can be seen and read by everybody. As I said already before, I will not answer to direct questions and mentors should not do that. If there's no use to ping privately a mentor or an org admin for having advice or things like that. Ask it publicly, everybody can hear it, everybody can give his opinion. Cheating, now you probably, if I remember well, my university time, we were told so you may not cheat, you may not to look on what your neighbor is writing. This is called cheating. In open source, it's not called cheating. This is called cooperation. That means that you can get inspired by ideas of somebody else, but then you give the attribution so you don't steal the work of somebody else. You build on it and you respect the work that somebody else has done. So somebody who just copies work done by somebody else will get me or us upset and because it's seen. So we can see it. If you say this idea comes from that person and this is what I add or build or change to that idea. This is an important culture and this is the first step to learn that. So working there. We'll work together. You're going to see how this evolves. It seems a little bit confusing. Here my advice, I have gray hair so I've seen other things. Do that step early. It's frightening because I know the feeling that most of you have and say, well, people are going to laugh me out. People are going to say, who am I to dare write something like that? No, to the contrary. This humility and showing will help you to grow and will help people or will allow other people to start helping you and to make the things better. Is that working together? So try to make the step. If you have difficulties with that or you don't know how to proceed, just mention it. We can discuss it either in these meetings here. Today is a little bit difficult, but we can discuss that in one of the office hours and maybe later around the glass of beer or a cup of coffee. Discuss that. But this is a very important recommendation I want to make you start early working on your proposal. Ask for guidance and the best guidance can be given on material. So start the document and then ask people, can you review it? Did I understand it correctly? How can I improve? We'll stop there for a second. Are there questions? I don't have time to read the chat. Are there questions? I don't see any questions in the chat, John Mark. But if any of our attendees, if you have questions, feel free to unmute yourself and ask your question too. Leave a couple of seconds. Just raise your hand or interrupt. So a lot of guidance, a lot of documentation is available on the Jenkins Google Summer of Code page. We're going to add the links to the meeting notes. If something is unclear, just ask here on the Gitter channel or on somebody wanted to ask something. Yeah. Guys, can you hear him? Yes, I can hear you. It's Pratham, right? Yeah. Hello. Hello. I am Pratham and I am from India. And I have a question that honestly, I'm really late in this project, but can you guys like, are you okay? And I am a newbie into the open source. Can you guys guide me like how to, is the optimal way to approach right now from start to day? Okay. So I'm going to rephrase your question is, where do I start if I start today? Yes. Yeah, exactly. Yeah. Yeah. Okay. So there's a lot of documentation available on the side because this is a question that has been asked several times. And people have been preparing since December. And I recommend that you listen to a recording that was done. We're going to repeat the link to these recordings. So all meetings that we do are recorded because it's night somewhere on the earth. So we want to give a chance to everybody to listen to what we say. So in this meeting, we explained how to get prepared. Now at this stage, two things that I recommend. Well, you're already a little late, but here we have one big month. Two things. You need to clearly understand what is the project idea, what is the problem it tries to solve and start to understand it. This is the first thing. But the prerequisite for that to understand it correctly is that you have an idea what the complete ecosystem is about. What is Jenkins? What does it do? Where is the where is the snout? And where is the tail of this beat? And that you know. So we give several tips. The biggest tip I can give and do it as quickly as you can is start your own Jenkins instance on your laptop or on a virtual machine you have somewhere. Use Jenkins before a couple of times. Okay, good. So that you need to know enough. Okay, this is very good that you have an idea. What is an agent? What is a pipeline? What is the administrative console? How does it work? What is the purpose of it? Okay, and so that you can then dig in more precisely in the functional domain of the project that interests you. The third point once you have that is that you need to understand how you're going to solve the problem. So the technical side of it. So what is the internal? How what are the libraries involved? How's the code? Best way to do that is what we recommend is that you submit some pull requests so that you have a good feeling how the process works. How does the community work? Who's doing what? So these are the principles. Hearing you, it gives you a good start. Okay, thank you. So read the documentation. Get acquainted and listen to the various previous recording. Learn the basics of Jenkins. Run your own. If you have already experienced, that's okay. Or it's even better. Start digging into the functional aspect of the project that you're interested in. Fourth point is you don't see my fingers. I'm counting here lower. The fourth is start to understand how to contribute. Okay. So what is the code? Other questions? Hello sir, where I can get the meeting links? What links? To the recordings? Yeah, yeah, recordings. I'm going to put them in the meeting notes. So are you already registered to the Gitter channel? Yes, I am there. Okay, so there at least we'll drop a note with the link to the meeting notes and to the various things. And I'm going also to do it on the community server because they're sticky. You can search it. Okay, that's good. Okay. So we covered the purpose of the office hours. Answer any questions you have. Just checking the time. Okay, talked a little bit too much here. Some explanation about the program. Timeline, very important. We have time. We don't have excessive time. You'll need to concentrate. So you need to get work done and go ahead because the fourth of April is the last deadline. So it will be April 4th at about this time of the day. So it will be end of the day in India and you can start submitting a March 20. Making your proposal available for review March 20 is already very late. April 3rd or April 2nd, this is too late. So make your document available for review internal as soon as possible and people will be kind to you and will help because we want everybody to learn something from this experience. Okay, with all the notes that taking my notes are scrolling above the... Am I audible? Yes, I'm hearing you. Go ahead. Yes, I'm Netra and I'm also from India. So I wanted to just ask, I'm also a newbie actually into this open source contribution and I started the contribution in the start of February. So my doubt was, does the criteria of maximum contribution come into play while selecting the contributors? It's a good question. It's not a hard criteria in the sense we're going to count how many contributions are there. Oh, he's missing one or she's missing one. No. What we want to see and we're going to compare people is that first, does the candidate have experience? Does he know how it works? What's the principle? Did he already make proposal changes in code? What did he show or she show about her knowledge? I have problems with so I'm sorry if I say he instead of she, Netra. That's not a problem. So that's not a problem. I apologize. So we want to have to see how proficient or knowledgeable the person is. Now with one or two PRs, well, okay, he knows the principle, he knows how to do a review, he knows how to do a rebase or, you know, the vocabulary of how that works. Now if you have had only time to do one, but it doesn't mean that you're out of the game or at all and you don't need to do 10 in order to start to be looked at. It's a complete set of criteria that will be used. Does that answer your question? So for suppose if I choose a project and should I know all the skills required for the project mentioned in the project details. So the question is do you need to have them beforehand? Yes, yeah, beforehand. No, just show us or demonstrate that you either have them because you already did them or that you're able to learn them quickly because you already did this or that. It's a conversation you're going to do that. It's like an interview to be hired. So you need to convince us and we're going to compare. So if you say, well, okay, I've done my thesis on that subject or I did that as a hobby project and here you can see the details, say that and we're saying, well, okay, this lady or this person knows what they're talking about. But on the other side, you can also come with a little experience and say, I want to learn. But I understood what needs to be done. I come with novel ideas. I come with my heart and that's perfectly okay. Yes. Or did I completely confuse you? No, it's okay, I understood. Okay, right. Thank you. But we're not counting the number of contributions or pull requests or accepted one. No, but it's important. Show what you have done. We have two people entering. I think Alyssa was first. So there's a question in the chat window that says I'm a college student with some academic commitments too. If I'm inactive for some time, does it hamper any chance or my chance? No, I wanted to do a stupid joke. No, I refrain doing stupid joke. Let's be serious. No, it does not hamper. What is very important is that you say it clearly. When I now have experience, when you read a proposal, you get that feeling very well. So things that are described expressed clearly. For instance, saying, and there is a chapter that covers that in the proposal. These are, I don't remember how it's called, but you say, obviously I can spend or I'm able to spend as much time per week on the project and during this period and this period I will not be available for, and you can disclose the reason or not. But disclosing it is also always better and there can be reasons. I need to go visit my family or I'm taking vacations. Mentors have the same kind of problems or I need to get married or whatever. I need to go to somebody else's marriage. They're good reasons. Say it upfront. The contract is that you're going to get committed to 175 hours of work. And the better you show us, how are you going to use these hours and how are you going to cooperate with the mentors, the better it is. And we want to say it upfront and we want to hear it upfront. Did I answer that question correctly? I don't know who asked that. Hi, John Mark. I'm Shreya. I'm from India. I asked that question. Thank you so much for answering. What I really wanted to ask was like during the contribution period, if I'm not able to actively contribute for some small amount of time because I've got my exams coming on. So does that in any way hamper my chances? No. A clear no. Say it upfront. Say it during your application and this is part, if you're selected, this will be part of the way you organize the project with your mentors. It's perfectly okay. There are three months foreseen for the old project and if necessary, we can foresee, we can go up to November if necessary. But it needs to be well organized. And a word is, I'm sorry if I sound fatherly, there. Exams go first. Okay. Your future life is more important than open source or Google Summer of Code in the keep life work balance correct and will be my task to be careful that this is done. It's an exciting adventure. It's one in a lifetime opportunity. I know it, but don't get killed or don't get in in troubles because of that. So exams are important. Okay. Thank you. Thank you so much. Are there other questions? They're good questions. I'm unable, sir. Hi. So I'm sorry. I can try and say your name, but it goes too fast. But sure, your name. I apologize for that. So go ahead with your question. Good evening, sir. I'm Harsh from India. I have looked into the Jenkins projects repositories in the GitHub. I know the technologies, but I'm unable to understand the large code basis. So can you guide me? How can I understand that? I don't understand it either. So you're looking at 10 years worth of work done by a huge number of people and somewhere very, very strong. So it's normal, completely normal. I use the analogy of climbing a mountain and how do you climb a mountain step after step and you explore and you understand a piece of what you're looking at. Now I go into detail, but this is a methodology to learn Harsh. And this is an important skill to learn because for open source, but also professionally, you will have to do that very often. Now to go one step further and then I will leave the words to people that are more on the technical side. One of the techniques to understand how a piece of code works is first compile it, make it run. And then you start doing the ugly thing. You add print codes. I was here. I was there. I did that. Try to use the debugger. Follow the flow of the program. Oh, then it does that. Okay. Did that check. Then it does that. And so you observe like a scientist. What does it do? And so you understand the flow. Then you start changing it. Just I do a little change. Oh yeah. Okay. I understood this is the piece that controls this behavior. The third tip I would give is read the unit tests. Every piece of code, I hope that you have been taught that at school or so, but every piece of code that you provide has a set of tests to validate that it continues working as it's supposed to do. There's a lot of knowledge in these tests and try to understand. So, and I would even start looking at the test, altering it or adding the print screens or not the print screen. Sorry about that. The println or whatever in the tests. If I do this, I set up the tests. This is the result. Show me the result that I have and doing that one. I'm going already in details. I don't know if the more technical people have things to add. So first, is that a good start to answer you? And if somebody wants to add to that tip, he's welcome. I think it was harsh to ask the question. Do you have answers? Yes. Yes. Okay. Well, at least I managed to say something useful to you. Is there somebody who wants to add something to this very interesting question? Okay. Well, okay. I was going to ask. Let's take a few couple of questions. And then at a certain point, I'm going to stop the questions and push them for next week because I'd like to give opportunity to start presenting a project in detail. So I had somebody on the left side of my screen. Doesn't help you, but somebody wanted to ask a question. Said hello. Go ahead. Yes, sir. Good afternoon, sir. I had some questions. First of all, for the question of the large code basis. So I would also recommend that you start with a small code basis. And as you gradually gain experience, you then move on to larger code basis. So that's what I have experienced. That's a very good tip. Yeah. The next question that I wanted to ask is that do I have to submit my proposal directly on the Gitter channel so that it could be reviewed? Here. There are two policies. They're not policies, two recommendations. Here. My choice for mentioning, so how does it work? I just, it's detailed in the document, but you create a Google Doc document because it's easy, can be easily shared, and Google Summer of Code is sponsored by Google. Okay. Let's use that as well. Okay. It works very well. So you create a document in the cloud and just give everybody the commenters rights so that people can add comments and review. And this technique is used tremendously all over open source. And so you get, and this you control in sharing, explore that sharing the knob on the right. I didn't prepare it. I could have shown you how it works. Well, okay. Taking a little bit of balance there, but there is a button on the right that says share. This is where you control who has access. And there you have also the possibility to get the link to the document. Well, format it. So you copy that link, and you make that link available either on community.jenkins.io. There is the GSOC channel available for that. That's where all the GSOC messages are. And you say, please, GSOC proposal, please help me to review this. And you post the link there. You can also do it in Gitter. Now, why do I recommend doing it in community is this is more a bulletin board or a forum format, which is much better than just a chat. Chat tends to scroll out. And honestly, I don't go, I go maybe twice a day on Gitter. And there are so many messages that already flowed through. It gets very easily lost on Gitter. So recommendation is do it on community.jenkins.io in the GSOC channel and put the link there. And people can either create a thread around the document and can find the link to your document there. Does that answer your question? Yes, sir. May I ask some more questions? Go ahead. Yeah, you're welcome. Yeah, so if we run out of time, I'm just for everybody, I'm going to stop the meeting in 15 minutes just to respect everybody's time. And I think in India and other countries over there, it's already very, very late for you. We'll be back next week. And you can ask your questions on the two discussion. But I'm happy that there are questions. So go ahead. Sartak, is that the way your name is pronounced? Yes. So I was wondering that, can I submit three separate proposals for three different projects with the organization? Good question. Yes. As long as there are good proposals, not junk proposals, spam, but I don't believe that people around the table here do that. But you can propose any number of proposals. Remember, it's a competition. We'll take only the best because we have only limited mentoring. And you can, even if you're very strong, propose a new idea. But this is a steep, a steep mountain to climb. But there's no objection for that. Just convince us that you're the right person to achieve this project and to bring it to successful end. So did I answer your questions, Sartak? Yes, sir. And one more thing. I'm going to stop you here. Stop calling me, sir. You give me 10 years more. So you make me older than I am. You can call me John Mark. Okay? Okay. Sure. Go ahead. My question was that I have been posting all my progress, like all my contributions and all the things which I have learned on Twitter and LinkedIn. So can I add that to my proposal? Yes, why not? Just be aware that some of the mentors that are going to review, it might be lazy and might not always follow the link to your LinkedIn. So if you feel a contribution is particularly important in the scope of your proposal, copy the experience in your proposal or try to make it substantial. But don't assume that the people will go on your LinkedIn profile to read this particular thing. Is that clear what I'm saying? Did you understand that suggestion? Yes, sir. I partially understood it. Okay. So I'm going to rephrase it to be 100% sure. You can use links and material that's available either on Twitter or on LinkedIn. But don't assume that people will read it. They will read your application document. This is what they're going to read. So be wise in the way you do it. But if you propose a document for review, the people are going to tell it to you. Okay? Yes. One more thing. Can I directly add the code changes in my proposal? Like, for example, if I have already made the changes locally, so can I just put it in the proposal? So the concern mentor? I have a problem to understand or see what is the case. Normally, a Google Summer of Code project is 175 hours work. So are you going to put the equivalent of that much work in your application document? But you could add code as an example of what you did. So I cannot answer to that question directly. Can you clarify it? Yes. So I just wanted to ask that. Can I submit a related code which I have made for that so that I can give a gist of what I'm trying to do? Here, show me. Create a document and ask to the people that are going to review, is this a good way to do it? Will this be a good proposal or not? I cannot give you advice without seeing precisely. I feel that there are good reasons and that are good cases where that would be strong. But on the other side, I fear that we're going off road. Yes, definitely. I'll post about it on the community and wait for the response. Another question I had is that you're going to be the winner of the most asked questions. Go ahead. Yeah, so I just checked out the issues section, the issues.jenkins.io webpage. So basically the issues I'm seeing here, I haven't dealt with such an interface before. So how can I find the repositories for which I have to make the changes? For example, there are some links which I am able to follow. But in some issues, there are no links attached. So that's what I wanted to ask. Yeah. I will, unless somebody else wants to jump on that question here, will not be able to answer that in this session. Ask this particular question eventually with examples of the issue you want to solve or get acquainted with. Ask that either in the GitterChat or on the community. Ask these specific questions there. Okay. And my last question is that I have been contributing to different organizations. So before this, I was contributing to the Jaeger repository. And unfortunately, it wasn't selected for Google summer of course. So I have to make a last minute switch for that. So as soon as I finish my contributions over there, I'll be jumping on here. So I also don't have much progress in the Jenkins repository, but I do have some progress in other repositories. So can I add links for the other contributions which I have made outside the organization? Good question. Here, what you're going to show with that is that you have already experience of the way, especially if it's a Java project or in the technology that. So if you feel this is something that you want to share with the reviewers, so the mentors that are going to rank the proposal, please add that. And every experience is useful. You're the judge to know if it's interesting or not. Now, don't forget that people here are focusing on Jenkins. There's a world they have little knowledge of, oh, I'm simplifying, but they have little knowledge of what's happening outside because we are convinced that the Earth is rotating around Jenkins, as everybody knows. No, I'm joking, I'm exaggerating. But having contribution on another project is interesting, but will not be a decisive criteria to be selected. Okay? Yes, thank you very much. So you're today's winner of the number of questions. We do that every office hours to say who asks the most questions. So definitely, thank you. You're the winner of this session. We had a question from on the slack. Can I just ask a small question? Go ahead, Natra. Yeah, so I just wanted to ask what is the expected number of contributors around like, how many are expected to be selected, the number? Ah, as many as we can, doesn't answer your question. Based on experience and based on the mentorship capacity, we have been dealing with between four contributors being selected to a maximum of six. So this gives you an idea. It will really depend, but I don't want to commit to any number, but between three and six, six being really here, I want to be sure, or we want as an organization to be sure that if somebody's selected that he gets or she gets all the help and mentorship that this effort deserves, we really want it to be a success. So we're not going to accept the students if we're not able to help them. Yes, okay. Now it gets scary, right? Yeah. Don't worry. Two things. Just by participating to the competition, you will learn a lot. And you're welcome to propose again next year. So especially as there is no requirement that you're still studying, that you're a student, young professionals can also contribute. So you can try again. But even just participating to this month and a half of effort, you will already learn a lot about open source, about the community. And this will help you in your professional career. So it's worth doing it. Yes, of course. A lot of people that were selected said, how come I have been selected? Who am I to be? No, it's worth competing. It's worth competing. I just want to make clear that it's not a walk in the park. There's work involved. There is an effort involved for that. Okay. Yes. Great. The camera is a little bit low, so you don't see my hand signals and my nonverbal communication. Great. Adrienne, I'm awfully sorry. I believe that presenting your project in the three minutes that are left will not work. Yeah, no, I'm not that good. Yeah, it won't work. So let's schedule that for our next week. Right. Okay. Good. We'll do it during the office hours. And if there is interest, I will suggest to the lead mentors that eventually we organize separate meetings per project to dig into. What do you think of that idea, Adrienne? I feel it's a very good idea. I'm respectful for every one time, because other mentors might want to have a dedicated time for their own project. So yeah, definitely just having a small introduction of the project ideas during office hours, and then we can move on to a different meeting on a different schedule for more specific questions. Yeah, I think we'll do that. I will talk to the different mentors and see how we can make it more respectful for everybody's time. But we'll keep this meeting. Next week, we'll have a one-hour meeting again, because as many questions will have a couple of other mentors, I hope you will be able to join Adrienne and the others that were there. But we can answer and discuss the general questions, doubts you have. I'll be here the whole summer, so not maybe in this place, because I may be traveling at certain times, but this meeting will be held every week. It's a watering hole and just to be together. Hi, can I ask a small question? Go ahead. Do you have one minute? Right. So I was wondering whether it's a good idea to mention that, for example, some project uses a text type that I'm not very familiar with. For example, somebody mentioned Antora. So is it a good idea to write in a proposal that I'll be dedicating this much time to learn and get used to that text type and then work on the project? Sure, it's a good idea. And here, the people that are going to review your proposals are going to guide you or give you hints and say, oh, you mentioned that. Maybe explain that better or more in details, what you mean with that and how that can bring more color to your proposal and make it a strong proposal. Does that answer your question? Right. Thank you so much. Okay, good. Here, I'm sorry, I will not take any other questions. We can meet on the Gitter channel and on not conference, on community. People are available there in different time zones, so continue asking questions. Questions were great. There were super, super questions. I see a lot of enthusiasm, a lot of very interesting people, interesting and interested people. I'm super happy to have met you all, directly or indirectly. So welcome aboard and we'll start a great journey together. So I'll send out the recording to this meeting soon, as soon as the recording is available, so probably in a couple hours. And then I'll also add the notes. So next week's office hours, same bat channel, same day, same time. Great. Thank you for helping me, Alyssa, and covering me with all these great teams. Okay, thank you with that. Thank you for everybody joining. I've been doing most of the talk. I'm sorry about that. It's boring. But here, we'll make it better in another time. Thank you all. Have a nice rest of the day or the night. Thank you for joining and see you next week. Bye-bye, everybody. Thank you. Thank you, Alyssa. Bye.