 First of all, thank you guys for coming. I'm Mr. Jang Yurle. I'm a PhD student at Marmor University in Turkey. I'm a GSOC student in the Devian community, and I'm working on the development of web-artistic plugins. I'm really happy to be here. This is my first step comes, and I'm really happy to meet the community. I'm from India and it's great to meet all of you. Thank you for coming. We'll be talking about the work we've done and the work we hope to complete in our GSOC project. Our main project is improving voice, video, and chat for free and open-source software, and we hope you'll enjoy it a lot. Thank you. We both are working on the development of web-artistic plugins. So far, we have developed a WordPress one, and media wiki plugin is about to arrive. It's almost finished, and we will give you some details about what we have done and what's the progress. First, why we choose WordPress? WordPress powers more than 24 percent of the web. It's really huge, and the number is rising all the time. It started to be a simple blogging system, but now it's a complex portal. You can build enterprise websites. It's a fully CMS, and you can build applications. It's really what you want. Just to WordPress, because I'm sure a lot of people here even have WordPress blogs, even if you're not sitting here, people watching you through the live stream or the video, if you're seeing me, I'm sure you can relate or you've seen a WordPress blog, because WordPress is that common, and we urgently needed a plugin, and that's what Mesut has done. So he'll be talking to us about his plugin. I would like to talk a little bit about web-artistic, and web-artistic brings audio and video chat to our web applications, to browsers, and we don't need to install any plugins to use it, and it also gives us opportunity to transfer data between peers, and there is no complex code, no expensive infrastructure behind it, and the browsers are fully supported. All the modern browsers are already support web-artistic, and most of the browsers that you are using already supports web-artistic now, and it has really a huge potential to reach billions of devices already. I'm excited, so we have something level the playing field with all these proprietary software. Our goal was the allow users to video and audio chat on WordPress. At first, we can allow users to exchange files, but at first we decide to allow users to video and audio chat first, and we write plugins to support that. I would like to go a little bit deeper in WordPress. It started at 2003. It's a fully open source project. It has lots of thousands of plugins, widgets, themes, and has evolved to be a full content management system. WordPress has started to be a just simple block webpage, and now it's a, you can really build complex applications and you can do whatever you want with WordPress, and it's the same under GPI version two. It's a fresh software, but it's roots and development go back to 2001. It's major and stable. And it gives, it's really simple to create some pages, and it's really flexible, and you can easily publish your document, publish your writings, and it has really huge publishing tools, support, and WordPress has already built in user management, media management, and it's already full standard compliance, and you can extend WordPress using plugins, it has already built in commands, and it's already search engine optimized, and it supports over 70 languages. Easy installation, easy upgrades, and you can own your data, and it's free, and there is a huge community supporting WordPress, and it has really low requirements. You can just use PHP version 5.6 and MySQL version 5.6 or MariaDB version 10 or higher, but it supports lower than that, but the lower versions are end-of-life, so at least you need to use these versions, and you just only need a modern browser to that supports WebRTC, and the software architecture is just like this. We hold a web server that hosts WordPress, and we use JS communicator to communicate with each other. The user first HTTP get request server and loads the WordPress page. There's a built-in plugin that supports WebRTC. For seniorly mechanism, we use CIP over web sockets, and we sign up each other, and then the RTP media can flow through peer between peers, and we can use a turn server if we are behind an app. So if you had seen, there is a part called JS communicator over there. If somebody is not here, JS communicator is the user end code that you have to integrate into your website. So when you're using the WP call plugin, JS communicator will obviously be inside the plugin, but you can also host WebRTC directly from your HTML page or your website by using JS communicator. So JS communicator is this beautiful piece of very elegant and very simple code. It's written with HTML, CSS, and JavaScript, and you can just integrate it into your web page. Now our plugin is called WP call. You can just see WP call inside under the plugins tab. You can install or activate it easily. We already have an options page. It's under settings. It's really hard to read from here, but it's under settings. You can change the settings. And on the front end, we have this size of widget. It shows that the WebSocket link is connected. SIP registration is registered. If both situations are in this place, so we can easily call any destination we want, we enter a SIP address here and we can prefer to use audio or video call. During calling, the screen goes into this form. This is the test time address we can call now. We can enter the call or we can enter a number. Yeah, so we'll be moving on from WordPress to MediaViki. MediaViki is the part that I've been working on. It's not complete yet, but it's working progress. And something, if you could go back one slide into the architecture. Yeah. So if people are confused, the SIP over there is session initiation protocol. We use an SIP proxy in this network so that the SIP proxy is the address to which you give inside, you change it again to the front end. So you have to enter your SIP proxy and that is how the calling functions. So that is the thing that makes the whole system works. So I'll come back to my MediaViki. So I've been creating this form to input data and all that. My front end has been done. I'm still working on transferring the data in between from this to the back end. And this is basically work in progress. I think Mesoots is almost complete. I'm pretty sure I checked it and I found out. So you'll have to wait at least a week or more for my work to be done. And this is basically how it will look like once it's done. There are some options here. You can have a video call. You can have an audio call. And this is all the things that you can find in a Skype call or in a Google Hangout. So we are just building that for FOS. So this is a prototype model. The end product may vary. So that's what we have. That's what we've been doing. And what's happening next is we are... We are happy to announce that when we complete the video we pick all. We are straight to go to the Jumla, RedMind and Django plugins. We are not just going to develop these plugins to use inside that CMS. We are gonna connect each CMS system to connect to each other. And we can use RTC.dev.org. You can be using RTC.dev.org or any website. You can use any CMS system to use our plugin. So our plugin all connects to each other. You can talk to any of them. So something I'd like to add was that our mentor had already created a plugin for Drupal called Drupal. Unfortunately, we forgot to list it. But that is already functional. It's a module in Drupal. And that is one of the sources that we had. So that was the model that we are basing it on. And if anybody uses Drupal, you can go check out that module as well. And we are really grateful for them because they are advising us and they're telling us how to do this. And so that's basically it. Please do contact us. My MediaWiki plugin is not completely done. And I do have some issues in the back end because I'm very unfamiliar with the MediaWiki formatting and all that. So we're working through that. And so we'd love to hear from you. We'd love your feedback if you try using one of our plugins because they're all very new. These are all beta, you know, new releases. And so we thank the Debian community for your support and everything. So any questions? We'll take questions back. Thank you. Sorry, so the talk of the title mentioned free RTC. How does that fit into this? How does that relate to web RTC? Free RTC, we are using the community. We all came together into RTC, web RTC technologies as free RTC. We call them all as free RTC. Free RTC is just the name because web RTC I think was called proprietary to Google or something. So free RTC is, it's basically does the same job but it is free and open source. So that is our project is for free RTC. Have you tried approaching WordPress to get this integrated because WordPress has two as far as I understand it. One is the WordPress.com where many people have their public blogs and then there's WordPress.org which basically people have their own servers and then they set it up as you share. I think what would be more nicer if you can get this integrated in WP.com then people will be able to access that service. Any movement in that? I would like to inform all the users about WordPress.com and what WordPress.org is. WordPress.org is the community website. It's developing the WordPress software and you can reach the community to get help. We get WordPress version from that website. WordPress.com is the, allow users to create some WordPress sites and manage their websites. It's a really nice idea to support WordPress.com but we couldn't, it's not that mature yet. We have just finished the WordPress plugin and it will be really a good idea. So I'd like to add to that. So the plugin creation was done maybe two weeks ago, I believe, so it's very new. We'd like to have more feedback, more testing done and make sure that there are no bugs and everything works just fine before we approach them but it's a great suggestion, we'd like to note that out. Thank you. Yeah, have you applied for the plugin repository access? No, we haven't applied with yet. Okay. So actually, this is the, vpcall.org is the website for the plugin. So we are really open to any support, any help. Okay. We much appreciate it. I'll surely try to. I'll surely try to. All right, it's good. We have this website just created to create some new plugins easily using GS Communicator. And thanks for our mentors, Mr. Daniel and Mr. Bruno for supporting us. Okay. And just for that question that a series had about WordPress.com. So WordPress.org is the community website for downloading the CMS software and running it on your servers. And WordPress.com is a multi-site installation that is already available publicly. So you can go and go and run your, get a site for yourself. That is what the product is. Anyways that, I think WordPress.com is their own proprietary thing of something. But it's just an instance of that WordPress.org CMS. Anyways, thank you. WordPress.com, anybody can access easily but WordPress.org, you have to download the software. And one name you forgot to mention, we'd also like to thank our mentors, Juliana Lubek if she's listening. I'm sorry we left out your name in between. So integration.md, that link that you had given. And it's basically about how to integrate all these plugins, JS Communicator and all that. So whichever website or whichever CMS that you're hosting, if you can get in touch with us, if it's not there in the integration.md file, we'll try to help you out and see how you can use what the software that we are building for your site, even if it needs an extra plugin creation. We are very open, this is very new. So we'd like the community to know about it. So anything else? Any questions? Yeah, sir. Thank you so much. Thank you. Thank you. It's been great.