 Hello everyone. Hey, welcome. Hello, so myself, Anupam and my colleague got up today. We are going to present to you evolving phosology ecosystem. So in today's agenda, we'll see what is this phosology project and how it's getting benefited from programs like GSOC. So what is this phosology project is all about. So let's take a brief look into this project. Phosology is an open source license compliance software system toolkit. As a toolkit, you can use phosology for license copyright and ECC scan from command line. And as a system, you have a database and UI where you can perform your compliance activities. Phosology is published almost a decade ago in 2008 and licensed under GPL 2.0. In 2015, it becomes a Linux Foundation collaboration project. It's a multi-user, multi-tenant. It provides you a multi-user, multi-tenant web UI for review and organizing your clearing jobs. So that's more about phosology project. And in phosology development stack, it's used CC++ PHP. And in the back end, you have PostgreSQL. That's all legacy code base or legacy software that we use for phosology. So what's phosology does? So phosology has multiple agents. So if you have any archive for a software, you can upload it to phosology. And it runs its agents through your archive to find out different interesting things. So when you upload your archive to phosology, it first unpack your archive. Once this archive is unpacked, it starts running multiple agents. For example, in phosology, we have Nomos and Monk for your license scanning. And we have copyright for your copyright scanning, ECC for ECC scanning. So here, you can see typically an example of an unarchived file where you have a license text in the file header. The phosology will find you what license text is that. So it finds the license text, reference to licenses, and written text that explains the licensing and license relevant statement. So it can give you what kind of license is that. It may be difficult from reading the license, what license sees. Also, you will be able to find copyright ECC using copyright ECC scanning. You will find the copyright statement that's there in this file. For example, at the beginning of this, beginning of this file, you have a copyright Siemensage 2013-2015. That can be found by phosology. And it will give you a consolidated view of all the licenses and copyrights that found. So here, you can see an example of such a consolidated view. We call it a histogram view. So here, we have a very popular software library called Thrift, which is licensed under aperture. But typically when you scan this software with phosology, you will find multiple other licenses inside Thrift. For example, though Thrift is licensed under aperture 2, it will be your interest that you will find GPL version 2, GPL 3 licenses inside this aperture 3 package. This happens actually because we use multiple ways to build ways as tools. So it's important that we thoroughly scan those ways as tool and phosology is important here. It's it sells you to check. What license is your software has or what's going actually inside the software and like what license actually going inside your software. So that's where it's important. So here you can see phosology is a very specialized tool that mainly used by companies. Those who want to check what kind of licenses goes inside your software. But why it should attract students, how they are benefited. Okay, so introduction. So there it comes the introduction to Google Summer of Code. So how Google Summer of Code is helping us building a community around phosology. How we are mentoring this community, how the how students are getting connected with us. This is beside the companies that already are connected with phosology. So so we have tried with multiple other programs. Those who help students to get connected with the way says projects and Google Summer of Code is one such program that fit fits as the best. And let's see why this Google Summer of Code is so special with us and why this help how the why and how this helped us a lot in our way says development. So Google Summer of Code is mainly organized by Google. It's under one. It's under the Google umbrella. And it's a global program focused on bringing more student developer into open source software development. So this is a well known program, international program. It's almost there for 16 plus DCL 16 tier. So it's there since 16 year Google give stipend to students. So the students are handsomely stipend for the for coding for the way says projects. And for the mentoring organizations, which is the open source organization organization. So this year the program is a bit shortened. It's now a 10 weeks program earlier it used to be 1213 weeks program. So but it's between mentor and students how the students are focused and how mentors are connected with the students. So you can do a lot of things with this 10 week time. So probably when God will do through the journey, then you will see how much we can do in 10 weeks and how the students have contributed for this 10 weeks. So how the program as we as I said the students are handsomely stipend to collect the way says project experience. They work for the way says project, not for the organization. However, organization invest effort for mentoring. So mentors need to come on board and they should be dedicated with the students to mentor them whenever they request to answer their queries and all other stuff they may need during the project. So one thing you should be aware of that this project is funded by Google. So if the students are not interested and students can just join the project and then don't do anything. So it's it's not expectation from the students. Students need to be focused on what they want to do for the project. They should be focused on. And also the mentors, they should be very much involved in the project guiding the students and answering students queries. So that mentor and student they work together in the whole project. It's very important. So every person participating in this project, they should be focused. And organization organ the org admin should take care of this that nothing is slipped. So everyone is doing the best they can do for the project. So why this is a project? So what are the achievements that students and the mentors get from here? The students, they mainly get experience for writing code. As we know, the open source code pretty much follow a good standard because its code is visible to all. So and the student get an experience to work on the WSS project and to get connected with the community. They also come to know about this distributed working environment. They get an internship experience. This is coding exercise. They get positive visibility. Positive visibility in the sense they get this visibility in the community as well as to anyone they want to share. So means after student, most of the students go in for some kind of placement. So there also they can showcase that what they did for the WSS and it's approved by multiple mentors. So we owe us reason that the code quality will be properly followed and it will be quite good. So mentor and the org admin get new contacts. Contact in the sense the students that are working with the project, they will continue with the project. That's the expectation or if if you are good to the student, they probably will continue. They become a very good contributor for your student. They may come back next year as an mentor again. So what's there for the mentors? Mentors are great. They are contributing to WSS. Mentors are from the WSS ecosystem and now they get new persons to know how this ecosystem works. How the person can come and get the knowledge of the WSS project and can work with that person so that they can contribute very good coding. They can contribute a very good. It can be code or it can be a feature or they can contribute to something for the WSS project. They can also extend this extend the community of your project because the multiple mentors can. For example, if you're working on a new project area, probably on a new topic, then probably your mentor can get some other person who knows that topic pretty well. So they can other people, other mentor can get connected with your project. And the best part I think that mentor gets is attending G-Sog Mentor Summit. So every organization can send two people for the G-Sog Mentor Summit and there they can attend various talks from the other WSS or other. As well as other WSS open source organizations. So that's a pretty good part of this program for mentors. So what's the timeline? So as mentioned before, this is a 10 week program now. So the 10 week program is only for the coding period. So it starts pretty early and then it starts with organizations making applications for the Google Summer Up Code. So once the organizations selected the student applications to the organizations and G-Sog. Then once the students are selected, they start the coding period and the final revolutions student get to evaluate the mentor and both mentors get to the student and finally they submitted to Google. So let's look at detail of this timeline a bit in detail so that we come to know what's happening here. So this is a timeline for this year. The G-Sog started with the organization when the applications open for the organizations. Organizations can apply. The mentor organization can apply for G-Sog. This was all started on 29 January this year and the deadline was till 19 February when the G-Sog application end. Then the organizations were announced. These are the selected organizations that Google has announced. I think this year around 700 organizations participated and around 200 organizations got 200 plus organizations got selected for the G-Sog program. Now once the organizations get announced, the students have a chance to go through the organizations and find out what kind of project the organizations is interested in. So now the organization interest and student interest both get involved. So students go through the organizations, find out the project and if the project suits their interest, they can apply for those projects. Now once the students find out the suitable project, they start digging into those projects. So to reach out to student what we do here, we do a reach out program and where if we start to reach out program or not program but weekly call where students can come on board or they can discuss if they have any query about the project. Now then the student filed their applications for the suitable project. They have chosen with the organizations and then the organizations get a chance to review those projects application. Once the project applications get to use the students, then the organizations submit to the selected student, submit the selected student to Google and Google announce who are the students participating for that organization. Then it start the most interesting part that is the coding part and now here the maintenance students are completely involved with the project. So students start to know about the WSS project. They start digging more into it and here the mentor should come and help them out. So as a mentor we help them out whenever they require they have any queries or anywhere they are blocked in the project. So typically after a month we get the first evolution. So students get to do the first sorry mentor gets to do the first evolution of the work. Then the second phase after the evolutions hopefully all the students get passed and then they start the second phase of this coding work. And then finally they submit the evolution means it's a next month. It's a two months program now. So the students submit their final level students submit their code and everything for the final pro evolutions. And then again evaluated by the mentors and the result is announced finally. So this year we have around seven students and all got successfully completed the GSOC project. So this is more about our GSOC journey this year. We have received 15 proposals. We had 10 mentors. The mentors are from different organizations like HP Orange. So we got seven slot allocated by Google. We are thankful for that. And so we are able to complete this whole project in time. As I mentioned earlier and all our students completed the final evolution successfully. So this is a journey for the GSOC. We started this in 2018 where actually we tried to as I mentioned earlier. Fossilogy is a very special project and getting to the students is getting interested group to create interested developer group is pretty challenging here. So GSOC was one such program that give us this opportunity where we created the interested group. In 2018 we started this journey. We received three proposals. Two students were selected and in consecutive years the number of slots that we have received has increased along with the proposals. So one good thing we are able to do here. We are able to retain our mentors or the students those who have participated earlier years. They came back as a mentor. That's one good thing for us. And they successfully mentor the next year student batch and also sometimes one more interesting point probably I would like to share. They not only mentor sometimes they also like to run some POC to see how they can do more to the project. So that's how our community getting increased. So here is an this time this time in Google Summer of Code final call. All the students and mentor decided that they want to see each other. So we switched to a video call though and that's a snapshot from that video call. I think it's pretty good and yeah. We are thankful to all students and mentors and definitely the org admin who control the whole thing. So this is from my side and next my colleague Gaurav is going to take you to the GSOG journey. How this helped us more about it and over to Gaurav now. Thank you. Thanks Anupam. So let me take you guys to our achievements by achievements. I mean the amazing projects which are done by the amazing students throughout this GSOG since 2018 with our organization. So let's have a look. So in the first year in 2018 when we were new to this Google Summer of Code. We got three applications and from there we sorted out to two students. But due to some reason one of the students failed to update the progress from his end. So we decided to drop him off like mark him as fail on the Google dashboard. And we ended up with one amazing student Amanjan. So as you already know for Solji is a decade old project. So we thought like we can have a new license which can take you take help of multiple new text statistics algorithms. And use them to the benefit of finding out the licenses rather than relying on the rule based. It's kind of what we already have. So he did the initial contribution for the Akarachi agent which gave us a very nice and strong base for coming projects. So this same project is still active and still continuing. I'll talk about it later. But yeah, so he did a great work over there. And he also decided to be a mentor with us for the next year. Since he was already in the final year in 2018 so he could not participate as a student in 2019. So yeah, he decided to be a mentor with us and guide our next student who was going to work on in Akarachi. So in 2019 we received five proposals, five very good proposals. But unfortunately we had to reduce it down to C and we ended up with Vivek Sandip and Ayush working with us. That year we got two new integrations to Fosalji. So that is like the big picture you imagine as an open source organization is collaborating with other open source organizations. So these two projects handle them very nicely. So first of the project integration with Microsoft clearly defined and is called as its first in Fosalji. And then by Vivek so clearly defined is another portal to store this license clearing information centrally and share it with other members in the community. So this brings us a very good value to our project as well for Solji like anyone who is using it to do their own license clearing. As well provided a good base where someone can do their contribution to clearly defined as well. So if I saw a new package today I did the clearing and then I can contribute it back there so others can benefit from it. So that you know the bigger aim of having a different source. Then coming to next project from Sandip is the integration with the software heritage which is a global archive of all the available source code. So they support like GitHub, GitLab, BigBucket, any popular repository where you know people can post their public post. So this again helps give Fosalji another advantage to identify whether source file is public or is it modified or is it private. You know it helps identify that so even though this integration does not directly affect how the license clearing is done. But it provide additional information on top of it. So there are various aspects of any software so that came out clearly over here with this integration of software heritage. Then we had Ayush continuing the work on Atarashi agent and bringing them in some new algorithms. So here he was mentored by Aman in 2019 that again bought many new things to Atarashi. This was the first time we attempted integrating it back to Fosalji because it can also work as a standalone tool. So in 2019 we decided to do an integration and the Atarashi already had some algorithms integrated in it but we did not have any way to do an evaluation. So he also added the test cases for the same. So that again is an enhancement for the project. It also helps us to introduce the CI to it. We can now do automated build and automated testing in the project. Then moving on to next year in 2020. Ayush decided to participate again with us like for the second term since he was in the final year and we had Poshlendra participating for the first time and also Darshan. So in 2020 also we received five proposals and we analyzed it to see. So this year Ayush and Poshlendra decided to collaborate on two projects. So one was the code comment extraction script we call it NIRGES and also some enhancement on the Atarashi site. So this NIRGES we designed so that additional information from the source code can be reduced and the task of identifying the licenses can be improved. So there was a very good collaboration between these two in 2020 to bring NIRGES to state what it is as of now. And also integrated with Atarashi and even further enhance the accuracy level. So yeah, then Darshan, he worked on Grafana base dashboard for Poshlendra. So this helped to have additional monitoring rather than just doing a license clearing. You can now also collect various statistics like how is the inflow of the packages for your company, how much hours maybe someone's putting in or how much of the resource consumption is there. So also for IT, this is helpful. So that was again a great contribution from Darshan. And he was also in the final year in 2020. And once he finished the GSOC, he also got an offer from Apple and he finally joined the company. That one good story we face or we rather saw from Apple in this report. And then coming to this year in 2021, we received the highest number of proposals so far that was heading. And we managed to get seven of them on board with us. So this year Poshlendra continued with us and from previous years Vivek and Aman also I used, they decided to be a mentor with our organization. One good thing also happened. So last year, we could not select one of the proposals due to limited number of slots. So the student was so grateful to us or rather we are grateful to him that he decided to mentor us in 2021. So these things happen like you cannot get everything what you want. So we have managed to get him again in 2021 and he mentored along with us for the GSOC. So we are coming to the students, seven of them. So first we had Aman and Shrutu, which worked on creating a new GUI for Cosology which is based on in technology React. And that was just an amazing collaboration between two students which have not even seen them, seen each other. So also this was during the pandemic so they cannot physically meet at all. All the interactions whatever happened were virtual. So we had this amazing thing, the collaboration there. They also created a new project in our Cosology so it's in future. React.js is a new trending framework. We see many students also approaching us already who want to do a contribution to the React project and help us get better UI. And yeah, Kaushalendra this year helped us to develop a new agent or a new integration for copyright false positive detection. So as a concept for Solgy also do the copyright scanning and not the lesson. So sometimes we end up having more number of copyrights which are not particularly valid. So that is a manual effort to clear all of them through the clearing. So yeah, he's this year developed new algorithms to reduce that additional effort and also do some clearing on the copyright library and other stuff like that. And also we had a winner with the new. We make so for Solgy was relying on makefile for like 10 12 years. But yeah, we saw that makefile was a bit lengthy whenever there is a new agent you have to multiple files at a time. And the way the makefile were designed initially, we like multi processing so we cannot compile multiple targets at the same. So yeah, he helped us to bring the make to the mix and also increase this build performance like by reducing the build time doing this parallel builds. And maybe in future who knows we can also run for Solgy on new. Then we had Omar Sarita and Shreya. So Omar Omar starts was very much different. So also he is not from the computer science background. He is into electronic. So, but here the contribution he did it for itself. So he tried to migrate existing for Solgy, which is more of a monolithic kind of architecture into Kubernetes. So yes, that was a great learning for him as well as also for our mentors because only few of them are very familiar with the Kubernetes. So along with Omar, we also learned many things about the Kubernetes and other stuff. For example, how containers interact with each other, how their volumes can be mounted here. And Sarita again brought a new integration. So again, a new community got connected with for Solgy, which is a scan code tool kit, which again is a very prominent license scanner, very well known license. So that integration is the even enhance the capabilities of for Solgy and making it a better tool overall. So Sarita and also Avinal, they did a great collaboration. Even though they are in the same school, but due to pandemic they have never met each other in person. So yes, in this virtual world, these great collaborations we have seen how we have witnessed this particularly so consecutive. Then finally we had Shreya with us. So she is also from chemical background actually, not from computer science or anything related to computer science. But still she delivered a project or machine learning what she did is taking various licenses. So speaking broad terms, you will find that max 500 license out there which are commonly used and those 500 license will give you 500 license. So if you want to train or any machine learning or test the statistics and it becomes very difficult because 500 is not a very vast data set and for each license it has just one text to compare it. So her contribution helped us create multiple, you know, multiple variations of the same license set. And we ended up getting more than 3000 license on those 500 we started with. So this again will serve as a base for Solgy as well as our Akarashi agent. And also anyone in the same space, you know, this project is open source, the data generated is open source. So anyone can come and use the data and generate a new algorithm and you can even better scan it. So such amazing things come out when you collaborate with different people. And DSOC has helped us to provide that platform to be required. So ending this thing with the reporting. So I have provided some links here that we can add them to the description of the talk. So you can go through, have a look and feel how the reporting is done. And so all these fields are particularly not mandatory. But yeah, we recommend our students to have them, which includes the project goal. Like what was the aim of the particular project we were doing and various steps to decide, you know, this approach is good or that approach is good. Then we have weekly progress support. So it also includes all the weekly calls we have. So we, for all our students, we open the call channel. So whenever it is required, you can, or they can contact us or even we had weekly once called with them. So yeah, they also reported whatever happened in the meeting. So if anyone, you know, want to go and have a look, they just need to know which particular meeting. So they will be presented with a concrete report. And then in GSOC we have two evaluation times this year. So also milestone whatever milestones they have achieved for that particular evaluation, whether it is aligned to their progress, what they propose or not. Yeah, so such reporting is there. So everything is not just, you know, in code. It's also well documented. So yeah, you can have a look on these links and maybe use them as a guide as well for maybe your students, which will be contributing to your particular project. So for our community, we gathered some of the statistics. So since we started participating in the software 2018, how it has affected our community. So with all this, we've got six new projects in the community for new integration. That, you know, it's simply a multiple. Then we should then combined have given their 3000 plus hours doing all this activity and generated more than 150,000 lines of code, which is a huge thing to achieve. And we really appreciate all the students have taken care. And overall, we got like more than 180 policers just concerning the code in our community. We have 18 new features. So all these things are not just restricted to the code what they have done during the summer period. And they also, you know, collaborated with us before this off and sometimes even after this off, there were few open issues. They also fit that. So we thought what issues fit as well. And overall, we had been, you know, contacted to 35 new contributors. That is a big number for any community. Especially in for Solji. This is a big achievement for us. Then I will end with other programs apart from Google for more of code which are there. And I would encourage everyone, you know, to either if you are a community maintainer, or if you know your maintainer, if you know your admin, please, please, please do reach out to them. Other than to participate in any of the program. I listed here, I will give you a brief about all of them. So for example, outreach is similar to Google summer of code is a paid internship for female. Then we have Google season of talk that again is from Google, but it concentrates more on the documentation aspect of the topic. I believe would be very interesting for all of you. And it is for six months. So it is based on, you know, there will be a stipend, but it's more based on the grant rather than directly. Then we have Anita, both organizations, which promote women impact. Yeah, so, again, the participants like the students need to be on like me to be a female, but the mentoring, mentoring organization can be anything. Then again, from the Linux community, we have various mentorship programs going on. So there is mentorship in CLCS, there is mentorship in kernel. Yeah, so if you are part of the next foundation, like possibly you can also participate there. And we recently have a new project in India called the script summer of code. It was started in 2018 is also three months long like. And is I believe also a paid internship for the students. Yeah, so I highly recommend you do like highly recommend you to go out and see what programs suits your organization best and improve your collaboration. So if you have any questions, please do reach out to us. Mail anytime or even go to our community. In our weekly, we also have a slack channel. You can join that. There are, there is also a YouTube channel we have, where we uploaded some training videos and also some technical videos also in the GSoC, we have some preparation. They are also. Yes, thanks for listening and have a nice day.