 Hello everyone. Thank you for having us here today. We appreciate the opportunity to present one of our project. We're going to talk about bridging the knowledge gap, connecting a global network of nonprofits with Drupal. Let's start with introducing ourselves. We are from Brainsome, a Drupal-focused agency. Our mission is to create value for our clients, but also to make a greater good via impactful projects and open source, of course. We deliver full projects from UX, Discovery to implementation, and continuous support on the long run. We believe in open source and this approach enables us working even with the largest organizations. My name is Jofia Alfaldi. I'm a project manager at Brainsome, a certified professional scrum master and a certified associate in project management. I've collaborated on 12-plus NGO-related projects, both as a scrum master and the project manager. I'm Peter Ponja. I'm the CTO and co-founder of Brainsome, and part of my job is to find the right technologies for our clients. And guess what? I usually find Drupal the right one. We used to say Drupal is a CMS framework, but I believe it's much better to show by example why Drupal is much more than a CMS. We've built and delivered all kinds of web applications from this list. Drupal is great for e-learning, digital asset management. It can power microsite builder platforms and much more. Now we tend to say Drupal is great for content-heavy web applications. In this case, we created a social knowledge sharing and collaboration platform, and we will give you insights about this ambitious project. Rofi, please introduce the client and the objectives. The International Federation of Red Cross and Red Crescent Societies is the world's largest humanitarian network. And the other key stakeholder was the Financial Development Competency Network, which brings together RCRC financial management practitioners throughout the world. Our objectives were to strengthen the community of a finance expert to design and develop a platform which is in harmonization with the financial management standards, tools and resources that are made available to the RCRC movement at large through a collaborative community of practice. During the selection process, we faced competition from some of the largest players. First of all, there was SharePoint and Teams, the standard tools of the Red Cross. Then came Microsoft's Yammer, Microsoft's social internet tool and workplace from Facebook. At the end, the lack of certain customization options and due to some special feature requirements, for example, the hybrid single sign-on letting in outsiders had helped us meaning the standard with an open source solution. Let's move on and explain our general approach and what was specific to this project. Rofi, please. The most important part in our approach was to understand the project, to develop a website with the ability to maintain the stability as well as to continuously improve. Although ideas were existing as to the network and its online platform, the real user needs are at the core of this development. From our UX perspective, this project became special as the client has done their research beforehand. They worked together with a designer and created the user needs study and the UI UX design. While they worked together with a designer, they weren't really sure of the outcome. The first idea was to have a custom build web application, but during the initial meetings, it became clear that the open source approach will be the best fit for their needs. This meant that our standard UX processes were overwritten and we quickly found ourselves in a rather precarious situation as we feared that there might be some misunderstanding regarding the main objectives and the user's real needs. To avoid this misunderstanding, the user personas have been created by us. With the workshops organized, we could analyze, review and validate these personas so the picture became more clear. Six personas have been created which covered the main pain points and the target features for the future users. These are extremely important as we aim to create a website where each individual can find a way to connect, share knowledge and get help. All in all, we decided to grab the famous open-social-drupal distribution and tailored it and extended it with custom features. We added or altered the following features. We added a custom main page. We enhanced the community feed. We made it possible to upload images and documents directly to posts. We extended the member directory with filters. We added feature topics, blogs and touch the all topics feature as well. We extended how the sub-community support works and we added a fully custom-built community resource module. We also added an events calendar. Jofi will guide you through each one of these. After login, the home page instantly supports networking and connecting. The featured posts section displays the most recent posts or the ones that get the most interactions likes on it or the ones that are deemed important by the site managers. We get several other important information straight away such as the available sub-communities to join the upcoming events, the featured resources, topics and so on. The community feed has many perks such as the image and the file uploading. Interesting info is that each of the uploaded items are being scanned by an antivirus system to avoid malicious file spreading. Interrupting with the posts are encouraged with the comment section. Here the file and image uploading is available as well. We can see here the members directory enhanced with filters so the people can easily find user based on their expertise, organization or date of registration. From the list, a private message can be sent straight away or we can view the person's activity on their profile page. Topics are great conversation starters and come in many forms, blogs, news or discussion. This section helps the site managers to highlight the most relevant topics of FDCN. Of course, there is an all topics page created with filters as well so the users can easily sort through and find the relevant content. We can find here the create topic button so a new content can be easily added. Sub-communities are the heart of the platform to make connecting with each other smoother and the users can join to sub-communities that are relevant to their expertise. These sub-communities are managed by the community managers and have different visibility settings. Some are free to join, others require a request to join or only available after invitation. The community resources are the core of sharing knowledge. Templates, reports, guidance and toolkits are some of the available types. Two status have been separated when uploading a document. Community resources uploaded by the community members or the validated resources through the IofRSE quality assurance process. While at first glance we could see the task of finding a relevant document mission impossible, the available sorting options, tags and filters help us greatly in solving this issue. And last but not least, events will promote the engagement of the members and help the community spread the world while continuously growing. We can view the upcoming events or the past events in a calendar or on a Lister page and each of the events can be saved to our own calendar, for example Google, Yahoo or Outlook. These are the main functionalities without the need for completeness as the time is limited today. Okay, so very nice, we added all these features but was it worth it? Did they really work? We are obsessed with clear measurable results and the KPI analytics section provided a great spectrum of visualized data and we even tailored it. So on this graph we can see the steady growth of the numbers of users in the system, especially after it was introduced to a... Oops, it's frozen. You guys just have to believe us. Okay, so believe us there is a steady growth in the number of active users. Yeah, here it is. On the other side, the contributions should also grow higher over time but the expertise is not distributed equally in this network. And the other reason behind this is that, as you all know from the Drupal community, it's kind of hard to turn content consumers to content contributors. Okay, if we take a look at this other dimension, we can see that a wide variety dozens of expertise are represented by the users and this makes the platform very useful for its members seeking advice. This map shows how truly global this platform is. The numbers on this slide are not the numbers of users but the numbers of organizations from various geographic regions. We know, for example, that the financial practitioners working on a small island for the Red Cross, the local Red Cross, was able to reach out and get advice from an expert in Norway. We can also track the ratio between likes and comments on topics, and on top of likes and topics, the very important number, the actual enrollments to events over time. Okay, let's move on and check how it was actually working with OpenSocial from a developer's perspective. Let's be honest and start with the difficulties. So, although OpenSocial is a well-maintained software distribution, it requires a little bit different approach than working with Drupal because many Drupal module versions and patches are basically set to certain versions in its composite JSON. This, at the end, led us working with custom patches a lot. So, for example, there is a custom patch added to OpenSocial, but we need a newer one. We cannot just add it because we cannot remove the old one, so we had to create a new one combining the old patch and the new one and add it this way. So it's kind of a little bit tricky, but it works. Sometimes we also had to use to the situation that sometimes we have to wait, obviously, for the security updates because the OpenSocial maintainers require some time also to release them. And, for example, as per my latest knowledge, there is still no stable release for Drupal 10, but it's almost there and we also contributed with two small patches. So altering the existing functionality can be also tricky. We had to take really carefully the way, the ordering, the order precedence of how these altars are running to get the behavior we wanted. Okay, let's move back to the bright side. What went really well? Oops. No, again. Okay. Okay, so I will talk about some positive aspects as well while we still see these difficulties. So the KPI analytics, that's not only powerful on the UI, but also it was great working with it as a developer. We had to extend it. We had to tailor it and it was kind of easy and flexible. And then the notification system. There's a powerful notification system in OpenSocial. Also on the web UI, the interface, but also there is a way to get email updates on topics or anything user follows. We even altered a little bit. We had another weekly digest option to it and it worked pretty well. It's kind of, it's a pity. Sorry. I will try. Okay. I can remember. It's someone here from Google Gorilla, the OpenSocial team, because sorry for this slide. I know that this is some critics. Okay, so I will just continue. The teaming was also, it went well with OpenSocial. We had to adhere to the look and feel. Something's there. Sorry. It's not even, no, it's not responding. It's dead. It's not about the computer. Okay. Anyway, so teaming was went well, but we have to admit that we agreed with the client that the main layouts for the community feed and these kind of main parts of OpenSocial will remain intact. And we customized mostly the custom features. And of course, we generally added the brand book. And let's recap the conclusions. So overall OpenSocial, we totally recommend it. It's out of the box, a full blown solution. You can even demo it to your clients and start to manage expectations early. It's also customizable, while sometimes it can be tricky, but so far everything was possible. And last key takeaways. So OpenSource won again this time against Microsoft and Facebook. We are really proud of it. And there was no need for software as a service solution or any license software. And it took six months for four developers until the initial silent launch in December 2021. And another six months until the official announcement and the opening for a wider audience in June 2020. Thank you for your attention and sorry for the problem. And if you have any questions, feel free to ask. What would you say the percentages of the OpenSocial distribution, additional country modules and ideas? What would be the percentages? Okay, so I will repeat the question. So what were the percentages between OpenSocial features and additional contributed modules and custom features? Well, unfortunately, I don't have these numbers. I just know that we touched on almost every part of OpenSocial. And I cannot tell that what would be the percentage in lines of code or what. But I would say, I don't know, maybe if we exchange our contacts, I will be able to give you. So actually it was like one year or four developers to get there, to get this platform customized and tailored to the client's needs. And then the starting point was the pure OpenSocial. So maybe that's something. Any other questions? Okay. Well, then thanks for your attention.