 Okay. Hi everyone. My name is Mario. I'm one of the admins of the First Asia program with Google Summer of Gold. And next to me is Ricky. Hi guys. Ricky is also one of the mentors. We will have a short intro round of the mentors. I think we could also have like another meeting one time where all the mentors introduced themselves. Today is a general onboarding meeting for students of Google Summer of Gold who are contributing to an open event and related projects. So there are different components and projects here. And yeah, we didn't get like 25 people into the chat yet. I read recently that Google actually allows 25 people to get in. I see there are only 10, but we are actually streaming live on YouTube. So we also take questions of the students involved and of course chat and everything. I think it's a learning and we will then see how things go and yeah. Next time we can have more meetings, different people inside and we can check out how it's done. Okay. So there is an agenda here. I will, I shared the agenda here with you guys on the different channels. Please check your chat channels. I can also share the agenda here on the Jitter channel. So you can like help with it. So let me quickly make a screen share. They're saying your voice is echoing. Is it because of you? My voice is echoing. Why? My volume is up. I'm not in the channel. Let's try a moment to pop out this chat. Okay. So I hope it is better now. Nope. Good for me. Isurus says it's working for him. Okay. So yeah, we just try guys check out and collect like any issues that we might have this time. So we can improve on the next time. But I see like a lot of people here already in the chat. So this is great. So I'm sharing the agenda here for a moment on the screen. I hope you can see it. So we have a welcome to GSOC with false Asia, intro of students and mentors and status of deployments of back end and front end apps. Make it bigger. Okay. Yeah. Reminders of responsibilities during GSOC. Wow. That's super big now. Distribution of project areas called for upcoming weeks and basis of server. So the server as a basis and questions and issues with ERD. Yeah. That was something we talked about yesterday already Ricky and me and the next steps. So welcome to the first Asia Google summer of code to everyone. We're really thrilled to have you here on board. And yeah, it's it's really exciting time because now with open event we're using it already for two years at the first Asia summit. We also see a few other users. Next cloud conference has used it and there are a number of small events that have used it. We have regular users of the happy lap hacker space, for example, in Berlin. And we have a lot of people who are interested in using it, but they need a few things to get done. And they need us to move to version number two. So this is the big goal of the next few weeks and months. And of course, like a lot of people have come up with like awesome ideas for features that we want to get in. So we see how far we go and how far we get. And yeah, so it's an exciting time to be in Google summer of code with first Asia. Okay, so welcome. And we're really glad that you're on board. We couldn't get everyone on board this time. I mean slots are always limited. But we also run an internship program. And generally I have to say, you don't need actually a program to contribute to first Asia's projects. You can just like participate in any way you like. So by the way, we are here in the hacker space in Singapore. So it's also a really good hacking atmosphere here. Right. Yes, it is. Okay. Hard work. Yes. Excellent. So let's get to the introduction of students. I think we have like 10 students here in the chat and I propose that we like have a short introduction round of the students in the chat. And I would like to do another meetup soon where we then have the second round of the students that are not in the chat here today, but following us on YouTube. So yeah, we can go step by step. Don't need to have everyone on board now. But let's start here. Maybe you guys can just like unmute your microphone and get started right away. Where are you from? What is your university? Where are you based? And which project do you plan to work on here? Maybe a few things. Hi, Mario. Hi, everyone. I am from India. I'm currently pursuing my final year of engineering studies from College of Technology. And right now my G-SOM project is on the back end of Open Event Support. Okay. Thank you. How's Seema? This is Seema. I am from National Institute of Technology Surat. My project is based on Open Event Android. I've been contributing to it since the last few months. Okay. Thank you. Then we have Christal here. I think real name Juan, right? Yes. That's correct. I'm Juan. I'm in Berlin. I'm from the Technical University of Berlin. And I plan to solve many issues for Open Event. I think I can really make it. I know there are some issues, but I don't think I will solve them. Okay. Thank you. And the next one, Max. I think Max is also based in Germany. Max, are you there? Can you hear us? We can't hear you. Okay. Let's give Max some time and move further to Nikit. Nikit, are you there? Hello. Hello, everyone. My name is Nikit Bandari. And I'm a second year computer science student at University School of Information and Communication Technology. And I'm working on the Open Event Android app. And I'm based in New Delhi. Okay. Thank you. And then we have Pradeep. Hi. My name is Pradeep. And I am from Trappolati, Allahabad. And I will be working on Open Event front-end during Magi Swap period. Okay. Great. And the next one is Saurav. Hello, everyone. Can you hear me? Yes, we can hear you. Yeah. I'm Saurav. I'm a second year undergraduate at Indian Institute of Technology, Patna. I'll be mainly working on the front-end server as well as the organizer app. Okay. Thank you. And the next one is Sridhar. Hello. Hello. Am I audible? Yes, you're audible. Thank you. Hello, everyone. I'm Sridhar Jhaju. And I'm studying in Delhi Technological University. I'm currently in my third year. And I'll be contributing to the Open Event Organizers app. Thank you. Okay. Great. And Vaibhav. Hello, everyone. I am Vaibhav. I'm currently studying in SGS ITS Indore. And I was previously mainly contributing to the organizer app. But I wish to contribute to the server and the front-end as well. I look forward to working on it. Am I audible? Hello. Hello. Hello. Yes. Yes, we heard you. Thank you very much. Okay. Thanks for the introduction. And Max, are you there now or is there an issue with your sound? Max. Max, can we hear you? Okay. So I don't hear Max at the moment. So we just like move on. And so we have a short introduction. Anyone who couldn't be here today in the live chat and following us on YouTube can introduce themselves next time. And we also like go into more detail with the mentors. But I would like Ricky, maybe as you are here, you could introduce a bit like how could you help students? What's your background as a mentor, as one of the mentors? So we obviously have a lot of mentors. Many mentors are former GSOC students. And Ricky here, we have worked together with him here in the hacker space. He has also like supported the meetups here in the hacker space for Asian meetups and participate in the wider open source community already for a long time. Yeah. So my name is Ricky. I was based for the last eight years in Shanghai. And before that I was working at Google in Mountain View. So this is my first experience as a GSOC mentor. Now that I'm outside of Google, so it's quite interesting to see. I've been involved in a couple of startups, different companies in China since I've been there. I co-founded the hacker space in Shanghai. And recently I started a new community called Coderbunker, which is actually like a software development community. So I look forward to welcoming you guys to that community too. So my main interests, I think, like I'm happy that we're using PostgreSQL in this project. And we, personally, we need these kinds of services because we organize a lot of meetups and events for Coderbunker. So this has a personal interest. I have a personal interest in this project to make it work, to see version two come and be delivered and be put in production and use it. So I'll be focusing on that aspect. So that's it. Yeah. Okay, great. Thank you. And I think this is very important that actually like this year the project is already advanced. And as you know, like we're all planning meetups and get together, get together as doing the Asia GSorg. So please use your project yourself, set up events on Eventier, and that's the best way to learn. Okay, so what's our next point on the list here? Reminders of responsibility. So reminders of responsibility. So we can't go too much into detail now, but like we already sent out an email with the best practices. Please check out the best practices like basic things like matching a pull request with an issue. Yeah. Things like this are very important and we will come back to this. Also like we have this idea of a daily scrum. And sometimes we see that people like communicate on different repositories. There's a server repository. There's an Android repository and you say, oh yeah, I have a blocker. I can't solve this issue because I'm waiting for something that I'm working on or I'm working collaborating with somebody on the server side. So I don't know that if I look at your issue in the Android repository, but I can see that much faster and easier if I look at your scrum and there's some information about this. So it helps us all to stay involved. So please also read the daily scrum mails of other people and please send out your scrum before 10 a.m. in the morning. The reason is we actually want to see what other different people do. Like people should be able to align with each other. So if you send it out in the evening and the day is over, I can't see what you're doing today. I can't work together with you on a specific issue because I don't even know that you're working maybe on something that overlaps with my work. So please take this serious, send out your scrum every morning at 10 a.m. So we usually expect people to send out a scrum five days a week. People have different ways to work. Some people say, oh yeah, I'm rather working six days a week because this is how we do it in India. Other people say, okay, I'm not working on Fridays because it's a holiday in my country, but I'm working on Saturday and Sunday. So it really depends up to you. Just keep your contributions regular and just stay involved. So it's also okay if you have more time one day and less time another day, but usually it's very unlikely that it works out if you just work Saturday and Sunday, 24 hours is just not possible. So make it reasonable and let's work together to bring this project forward. We have a lot of communities asking us. So it was just like in Brussels, there's the GNOME Foundation there, always have their annual GNOME event. There's the LibreOffice conference every year. They all want to use it. They all are looking at us, what we do. But like as I said, a few things are missing and we know basically what is missing and there are open issues and so on. So let's make this work. So this much for the reminders. Just to tell you, please post your questions here in the chat that we have directly here in our Hangout or on the YouTube. And I see already, okay, hello, I'm Sorop. Okay, that's great. You're also communicating here. So you can also like put up your questions that you have at this point in the channel. Okay, so I'm moving on to the next point. These were a few reminders of your responsibilities, so please also like check out the links that we sent to you in the email and best practices and guidelines for the GSOC program of our community. So we're moving on to the distribution of projects. So we already heard some of the students who introduced themselves here and I have a list here with the students of their areas of expertise and work and that I will add to the onboarding meeting notes. So yeah, I quickly want to go through this. So we have open event Android. We have open event front end. We have the organizer app, which is also an Android project. And we have the web app and the web app is basically a project to generate static websites that you can upload on FTP or on GitHub pages or GitLab pages anywhere where you like. So we have people working on that and we have the server. So I already tried to talk with you or some of you before GSOC already, many of you contributed a lot already to this project. But we see often that people are like sticking to one thing. Like let's say they stick to the Android app. But we actually, so actually like the Android app is great, but if we don't have the server, so without the server, the Android app cannot work. We need actually, so nobody can set up an event. We have an awesome app, but the server cannot work and many people are interested in front end in Android development or even iOS development. So we need to progress a bit on the server side and as we're using our APIs version 2, we need everyone to understand this. In all of you, the best way to understand this and to move ahead is actually by being able to set up the server, the API server and setting up the front end then you understand how things work together. So please everyone, upload your or install your server on the on the web. So I want to go to github.forceasia no, github.com github.com slash forceasia and I will go to the open event server on GitHub. So we have a wiki here. I'm going to share this with you. So I'm screen sharing that. So you are seeing here the website of the API server and there's a code issues wiki tab. Please go to the wiki tab and there you see student Kubernetes deployment. So we hope that you'll deploy that on Kubernetes. How do I say it correctly? I don't know. I only read it. Okay. So the Kubernetes deployment and there is a table that you see here. It's like contributor backend server front end server. So please add your GitHub username here and the links to your servers which you set up. I think this is important for all the projects that we have because you can only verify if things are working even like offline on your own so if you can connect to the server. So if you build your Android app you should be able to connect to the own server that you set up. So there are some guides here. There are some links that you can follow and also you can have others on the channel who can help you. Generally, please communicate with the public channel of the project because if you have an issue or a problem or something then others might have the same challenge and if you get an answer this answer might also help others. So it's very important. So we have different channels here I would say the server channel would be helpful. So I see like a comment here of Sorab I think the app front end contributors by agreeing on a common API endpoint absolutely. So we have API endpoints here and this is something we all can collaborate. Krestal is asking how many mentors do we have? How many mentors do we have? So basically we have a lot of mentors but the role of mentors is like different mentors have different styles of working and different roles. Let's say some mentors they will not be available every day but they are available maybe for the evaluations to look into details and give feedback on other things. Other mentors like me or like Ricky we are there rather regularly so every project has at least two or three mentors and you can communicate with them but again also here communication with mentors we prefer in public channels. Often other community members already have the answer so for example if we have different time zones for example one mentor in Germany or Singapore and like it's going for breakfast and you're just getting up and have the question and you know all these time differences and you wait a long time and this time maybe your questions could already have been answered in the public channel. So now you know please upload or add your links here to the deployments that you have and yeah I'm going to the next question that we have here which is next point goals for upcoming weeks and the server as a basis. Ricky do you want to talk a bit about that? We had a discussion about this already it would be great if you can say what would be the goals here for the next few weeks how do you see the work that we can get done in the Google Summer of Code project? Yeah so I in the discussion I saw that most of you guys have independent projects that are quite exciting and interesting but in my opinion right now we want to resolve as a team all the issues that are related to production so that we can use it right now the system as it is deployed is not usable I think I can't get past the login so that's definitely something to solve make sure that we have a strong basis especially in the data model to move forward and the API so that we can then work independently on the features. So I think that's really that aspect I think the discussion should really be around reinforcing what we already have make sure that we have a good deployment process and that we we can immediately put the version 2 to work on actual events, maybe small scale events as practice both here and Shanghai and we have so we have this question now you mainly talking about the server but also the front end so how is the role of people who like contributed let's say the Android apps and so on, how can we move forward with this also like we need to decide where we want to go with the Android apps I see some students have overlapping proposals but you guys really like we are very convincing, many of you have contributed a lot already so we still wanted to get you on board but we need to define a bit like how people actually work on stuff so not everyone can solve the same issue and also what's our priority I think maybe we can't go into detail with everything but I saw for example some like put a strong focus on moving to Kotlin but like like from Java to Kotlin but I don't know like if it's like the main goal right now because basically our goal is to get something working right? So for Android personally let me answer my question myself but like for Android maybe we can actually consider that we are moving or we are making an Android project that is actually like a more generic app right now the Android project is mainly like a generator same as the web app you generate an Android app for every event however like a few things have changed during the last few years I think not everyone installs an app all the time people don't install that many apps but for example people have the Eventbrite app and then when there's a new event they use this app for something to store their tickets or something like that because they don't find it on their phone so they just use the app okay so I think that would be a direction we want to go so the Android app should be a more generic app maybe keep the Android app generator but for now maybe it shouldn't be a focus so we use what we have in the Android app and build a more generic app so we would have two generic apps same as Eventbrite which would be a generic app for organizers so any event can scan in participants see some analytics metrics and so on and another app for users where they can just see their tickets download data check in basically and this all becomes possible because of our API approach before it was more difficult to do this because how can we plug in but now we have an API centric approach so is that something where you would agree we should go in this direction yeah sounds good I mean I'm still because obviously I have my own taste for technology we use in our own projects so most of our project right now use the React Native to make cross-platform application to be closer to the web technologies and then we also use the PostGraph file to generate a GraphQL API from the PostgreSQL database so I think the trend to me has moved a little bit from where we're seeing now to so this is something I want to discuss and I want to see and I want to compare with what's happening in the project so definitely it's going to be interesting for me to see what Kotlin and the other bring to the table so okay so I want to ask you now like so maybe should we have like a dedicated meeting or some wrap up for this with the students who contribute to the server because let me move to the next point which was actually talking about the EDR ERD I always say wrong we never use this MPT relationship diagram so we haven't used this we haven't looked into this in detail previously a lot of people rather come from front end but like I got some feedback from you so about technology you actually said we're using an IPI centric system but we could have even used maybe GraphQL which makes things easier for us possibly I think that's something to discuss with the team and I think there's already quite a bit of commitment to the current infrastructure so we have to see if it's even something to consider I think my end concern still remains that since we have a nice PostgreSQL database we also have to think about in terms of how we can do reporting directly in the database so the model is not just something that you create and maintain and insert data using Python but it's also something that the DBA should be able to create views and reports in the backend as aggregates and maybe expose those functionalities so we could also have in parallel a GraphQL API to return some aggregate reporting data while the transactional system remains with Python IPI so we could maybe add that on so I think maybe my next step would be to present a little bit how at Coderbunker we're building system now using that and see if there's any interest or I mean I would welcome also like criticism in terms of like how this wouldn't work in this particular case or would not be a good gain on this project so it could be an interesting discussion to have so I see like Bhavish you are signed up also for work on the server do you have any feedback about this at this point actually currently I'm going through the code base so earlier provided the ER diagram was very much it was very helpful for me and in coming days I will keep focusing on to make the even version V2 version of the app so currently the code base is going through programming so who else like let's go around a bit like who else is Saurab Chaturvedi are you here in the call I think we have different Saurabs Saurab Saurab and Saurab Saurab is not in the call right now but is there anyone else who has feedback on this like does this kind of idea help you in ERD do you understand what it is do you already have some knowledge Saurab you are also like into the server partly what's your idea Saurab Tivari so they just also question the group about the sperm reporting how we use them and how we create them let's get back to this later okay so Saurab Chaturvedi can you join the call I think like one spot is left now can you join the call what are your thoughts on that okay so I see here some I will be reading this out Saurab I'll be mainly working on the server side but I've mentioned in my proposal few tasks which require work on front end good so Saurab then writes there are some functionalities that can push from Python code to Postgres store procedures what's your opinion on that Tricky okay so the thing is I'm an old fart right so I'm pretty old relative to you guys and I've been using SQL for 20 years plus years and so for me the database site is quite important and the whole history is that I think like the dot com in 2000 basically brought in like really bad practices where we abandoned smart database and just push everything in the name of horizontal scalability and I think that the disadvantages like really were tied into doing a lot of stuff that processing and reporting and in the Python in this case in the API side when it could be more easily done in the database directly on reporting and with the innovation like post graph file which I can send a link later which generates a web API a GraphQL API that's very flexible based on automatically generated from the database model it kinds of makes the API unnecessary actually so but the downside is like you have to deal with this SQL which is very old you know it's older than me and that makes people uncomfortable because they'd rather do Python so there's kind of like this this two sides to it but yeah we can talk more about it I can try like I have very strong belief on that side but I mean we also have the reality that we have running projects that has been that you guys have been working very hard on for a long time and so there's quite a bit of investment in the business logic in the API right so it's quite difficult to change these things but we can maybe use that in parallel and just my message is like focus really on the data because long term for like it's a really a data centric application right so data how it's normalized how it's normalized it's really going to decide like if it's gets really messy or if it becomes more and more valuable right so that's our message okay so then I have a question so what are the next steps like we can't talk about like every detail here in the chat but like the goal is that we align with each other so what are the next steps for students how can they go on I see that you open an issue on this topic on the server yeah so there's a question having discussion where we point out things that are less desirable in the the database model and for now we can definitely just have that reflected in the Python code to fix some of those things that I think is kind of limiting us as we for the future right and yeah so I think it's just a conversation we can have on the GitHub issue and in the chat that we've already started so everybody's welcome to join that but yeah really the key thing as we know is the data is the most important right more than anything else so it's quite important to manage it correctly good so and I would like to also talk about the Android apps and the mobile apps what I would like to see from you guys now as the next step is like start working together so we already said that like we have a lot of overlapping topics and please start working together let's make a like some mockups for the Android app next version like let's say where we have a generic app besides the Android generator and I would like to focus everyone on the generic app at this point and also of course on the org app for the organizers so that would mean like we can even like start by looking at the Eventbrite app and how do they organize things and then see later how we can do things even much better than them so that would be my wish for you please communicate on the channels yeah keep up your scrum I saw like a question from Izuru about this Izuru was your question answered it's better if we can talk about the scrum reports and the use of scrum reports I tried to make it clear already so use of scrum reports basically I can just say again that we want people to read the scrum reports of others yeah so there is a paragraph or like even like a whole section on how to write scrum reports in the first Asia guidelines for the program and you can look at this there's also an example so please always provide links yeah just if you tell me like I read about something yeah I read about a certain topic and that might be important for others too so they would ask where did you read that, where did you find out about that you say on the internet well that's not helpful enough it's good that you find things but please provide links provide links to issues, provide links to your pull requests so people can also see like in the project you're contributing continuously we also would like you to make daily code commits it doesn't mean that you have to like solve like tons of issues in one day and rather like you can also commit code as work in progress like sometimes people work on larger issues and or even like issues with sub issues and maybe somebody else is also working on something related and they would like to see what are you doing so please you can label code as work in progress WIP and then make a pull request already and people can see how are you progressing so this is very helpful to understand what you are doing in the past like years ago we sometimes had people said yes I was working on this for two weeks and then it turned out it wasn't actually something that fit in well into the project at that time so that would be a shame so we want everyone also to have a good experience in the way that they do something that's useful for everyone and that's aligned with everyone's work okay so are there any questions at the moment about how we can work together do you guys have any questions so I see that Sora up here has questions specifically about linking Python objects to multiple tables in DB what about that if we normalize table in the DB the ORM will become more complex or not yeah so that's I mean I think that's a challenge right like I said the way we build system now on our site is actually not have an API server and just use GraphQL as the generic API so I am not too sure about how we could build working the Python API code and the ORM which I also strongly dislike but okay because I've worked a lot with ORMs in the past and actually I'm more troubled than there worked in my opinion but anyway that's more yeah open to discussion but I think we can bring some value by looking at not just what so we can use Python to create the model and have the ORM and stuff like that but also see okay on the database side if I want to do a report across all the events and aggregate reports it's not something that I should be doing in the Python side I should be doing in the database side because that's where the data is and that's where SQL is very good at this doing reporting on a large mass of data right so maybe like just having both working together yeah and I think definitely continue this like I was encouraged people to rather focus on the details in the issue tracker sometimes in the chat people also discuss but like you know if I see 80 messages and like I scroll back and something news happening I might miss something so keep like the central decision making in in the issue tracker so we can refer to it later I can say here look at this issue and look at this discussion whereas like if I say like two weeks ago there was a discussion on the chat channel wow like hard to find right like where was the discussion exactly I scroll through it takes me a long time so chat is good like to solve like some hands-on issues right now and some like basic discussion and if you really get into decision making into deeper questions and please try to move to the issue tracker even though it feels sometimes slightly slower but people can also like respond very fast yes that's something that goes together with your experience yeah yeah okay great good guys so I think we are now at the end of this session so like reminder of a few action items read through again the the programs guidelines check out the best practices again and install the back and in front end for each one of you and for the android team and like the I IOS we also had some people interested in IOS also in the internship program and for the android so check out like to to make like mock-ups and or basic screenshots it can be very simple at this moment like we can follow the Eventbrite app so to have a generic app and basically in the web app in front end there also a lot of issues so I think it's pretty obvious what we need to do and so we'll follow up on this and then the discussion about ERDs I mean the database yeah ERD is just the schematics of what the database looks like so I think it's helpful to look at it and figure out like okay maybe this is not how we want our database to look like so we want to make it better and so next time the plan for next time would be that we have a session with mentors we're joining like we still like have to assign some mentors in the dashboard of the GSOC program but I think you know our people like Shupam Saptar, Khashid, Ayush we have a lot of people who are active in this project for a long time so these are also our mentors and they are active and can support you generally please also refer to the former Hangouts on YouTube that we had for example with Sudeesh and with Niranjan who explained a lot about how to contribute and what is the role of mentors so the role of mentors basically they can help you but the code should be written by you guys and yeah we go forward step by step so it's good seeing you seeing you guys here and I wonder like who has some final remarks and words here at this Hangout here today so maybe we start with Babish and just go around Babish any final remarks here for today is it Babish or Babish? yeah it's Babish okay so it was a nice chat with you and I came across many of the program guidelines which were not earlier I know because I was contributing from last from September in South Asia so it was good to talk to you and I came across many of the series many of the steps from which I can follow along and this was the main part and I am looking forward to contribute as much as I can and hopefully it's over okay thank you moving on to Hassi Ma please increase the volume of it Gita channel Hassi Ma we can't hear you so well but I heard you are on the Jitter channel so that's good I think we just move on to Nikit then so good to see you Hassi regarding that Q but when I was reporting in the some reporting in the Jitter channel so Nikit okay hello so I guess he was trying to tell you that there were some problems in the deployment of the Kubernetes like there was some error I don't remember like the deployment was done correctly but still the end point wasn't reaching like 5 or 6 of us were trying to deploy it but everybody was getting the same error so I guess we can have a discussion how what the error is like like if previously somebody has deployed it so you can tell us like I tried to contact some people that they were also like we deployed it a long time back so we don't remember so we can have a discussion on what the error is the deployment issue is with the front end that doesn't reach kind of like that it's in the deployment of the server there are some errors in the project in the console you can see the errors the deployment is done correctly so I'm guessing some I mean the staging site on Eroku is not working right so there's something broken like for everybody so that needs to get fixed so it's not just like I don't take instructions or deployment step it's actually there's a discrepancy between the front end and the API that we need to fix so we can all another issue that happened in the last was that and some people like just directed the front end to work with the back end that was set up on the FOSSAsia Eroku whereas I think everyone should have like a front end that works with their own back end as well otherwise you always depend on the back end of FOSSAsia environments are important so please make sure that you set actually the front end to work with your own back end yeah and I know that like a number of people also to set this up locally because we want like that people can actually install the project on their own laptop and walk around and go somewhere maybe where they don't have such a good internet so these are issues that we need to solve here as soon as possible so everyone can work with it and also for example you can use your Android app and connect the Android app with the server that you set up on your own laptop right and generally if you do that with Kubernetes or another way that you have to check that out what's good for you in which case Kubernetes is very important for us in order to scale up the project then as soon as we go really into production okay right so the other thing I think Mario you had the week right on the repo where you were asking people to list out their front end and back end so that's kind of the old work right now is to get to a point where the front end and back end has been deployed by everybody and it's actually linked so that we can validate that it is actually happening yeah does this make sense to understand that Nikit? yeah yeah so let's work together on this and it's good that we have people with different backgrounds so I hope we're able to solve that as soon as possible on the team yeah so I guess we follow up on this and I would go to Vaibhav then who's the last one here in the chat Vaibhav any final words from your side yeah Mario the Kubernetes I'm actually exploring the Kubernetes so I haven't really deployed it yet and I planned to deploy it today and another question about the design and mock-ups that you brought up was like recently I tried out the Adobe experience design software so about for prototyping so would that be okay if we try a mock-up on that or what design software should we use should we really use some design software or just we need some basic mock-ups do we need a prototype type of thing well no we don't need a prototype like so the first step I want to understand your logic like for example like Eventbrite already has some logic I mean there are some open source projects they say oh yeah we have to do everything different technology different colors, different design everything different I think I don't have this kind of view I mean like the established players already invested a lot of time and designers and effort we don't have like the designers who have 20 years of experience in the community unfortunately we could okay follow that however if there is big traffic with you in the background so if there is any other idea for example we also have are you not audible there is something wrong with the voice I don't know I think it's the feedback and maybe background noise at your home instead of the microphone so so basically yes that we can follow them but we also have some features that for example Eventbrite doesn't have how do we integrate them how do we make it work so maybe first like a very basic version maybe also using some of the features that we already have in the Android App Generator and then move on I hope this is okay with you guys because I tried to talk with you before things keep changing a bit but we don't want anyone really to feel like they now have to do something completely different so the basic idea is that we work together and bring the expertise and the projects of the different people together now and see how it goes so we really need you guys to work together but I think to come back to the point of using a sketch or either be in design or things like that I think it's a good idea to spend time thinking about the user flows because my experience actually with Event EA so far was that all the functionality is there it's kind of hard to navigate the UI so I think spending some and I think that's one going to be one big weakness in the team we have a lot of good engineers good developers but we don't have so much of a designer to drive this so I think it's something that we need to pay attention to individually and maybe reach out to other people to help us if you guys know designers that could pitch in or review or give us some suggestions and I think it's if you guys are very very good at front end then step up and do the mockups and make suggestions on the design is a good thing yeah so generally of course we prefer free and open source tools but we're not in this black and white world so try something that works for you one thing that I haven't pushed yet for a lot this year is usually like we request people to work on Linux in the first Asia GSOC it's like mentioned in the guideline mentioned at many different points so I think I want to mention that again and so there are many reasons for this one thing is of course we are free and open source but we actually did have issues where people then like develop something on windows and even though it's like all the same then suddenly like there's one small thing so one thing that we encountered for example last year where we already ask everyone to develop actually on Linux one thing that problem that we had is like capitals and non-capitals for example so there was this one issue that we had a really hard time finding out a few months ago and case sensitivity so that was something and like we didn't know why is it working on this machine on this machine and why is it working here so there are differences and we want to keep like a consistent development environment for everyone and we want that it works for everyone and we don't want to spend time to figure out why it doesn't work on this machine and it works on this machine look guys online we will always be deploying on the Linux machine we will hardly ever deploy on a Windows machine so please make sure that you use Linux for your deployment use it for your daily work so we can work together more easily so I think we already like at an hour now of the conversation and there are lots of points to follow up in detail but the important thing is also get started solve issues contribute code we could like obviously discuss forever what technology what endpoint how to make this button or that button what we actually need very urgently is more users we need the users we need to see how users use the system what they do on the system and so on so if you have an idea that kind of works then go ahead if it helps us to get onto the stage where we can actually deploy version 2 and get the users also like it really motivates us if we have users so there is not always like one perfect way there are often many ways and like something turns out even perfect later on we can't even imagine it so like contribute code get started set up the systems and we do and have a fun summer and something that we can show to the world at the end and already doing the summer so that would be fun thanks for joining so we'll soon come back with another video cast here with mentors which we plan we will have more video cast with the other GSOC projects good luck and looking forward to see you guys again any final words from you no I think I'm really looking forward like I said like it's going to be a very useful system it's quite exciting to be part of this development and such a large team so it's a great opportunity for everybody to learn including myself so looking forward to it thanks guys and follow up on the channel see you soon bye bye bye bye