 We'd be using audio on your left to be the questions and please, you know, just speak it to the microphone so that we're recording this. So, I don't know. Okay. Thanks. Thank you. Hi, everyone. Thank you. Welcome. Good morning. This is Drupal strategies for nonprofits. If you happen to be in the wrong room, now's a good time to leave. My name is Scott Reinen, and I am lead developer at a company called Atten Design Group. Here's my email if you want to contact me after this. Morning. My name is Lydia Tupin, and I'm the studio manager at Atten Design Group. Atten Design Group is a web strategy design and development firm. We're based in Denver, Colorado in the U.S. We've been working with nonprofits and NGOs for about 12 years since we started our company. We've had some great clients and had the privilege to work with museums like the Smithsonian National Air and Space Museum, with international development organizations like the United Nations Development Program, and with journalism organizations like the Pointer Institute. So over the past 12 years, we've learned a lot about working with nonprofits and about working with Drupal, of course. So today, Scott and I are going to talk about, thanks, we're going to talk about Drupal strategies for nonprofits. Specifically, I'm going to go over some examples of Drupal sites that we've done for nonprofit clients, and then Scott's going to talk about distributions, contributions, and collaboration with the community. But first, I'd like to get an idea of who's here. So how many of you in the room work in design or development shops or are freelancers? Okay. Okay, great. And how many of you work for nonprofit organizations or agencies? Fantastic. That's wonderful. Great. Well, I am not a designer or a developer, although I work with quite a few very good ones. But I do have some nonprofit experience. I was actually raised in West Africa. I spent about 11 years there as a child with my brothers who also work for Atten. And during that time, living in the people group that we lived in, we saw some of the severe issues facing people, and I know that that goes beyond the group that I was living in to many parts of the world, issues that are threatening lives and livelihoods, political unrest, lack of education, lack of clean water, lack of health care. So at this point in my life, I'm just very grateful to be a part of a team that's helping to do this kind of good work for larger organizations who are doing large international good work as well. It's an interesting niche to be in today, but I'm just really appreciative of that opportunity. So I'd like to talk about Drupal a little bit. Drupal is, thanks. Yeah, that would be great. Can you get it? Thanks. FAST becoming a leading solution for some of these issues that are facing nonprofits, and we don't have a lot of time to get into the detail, but I want to cover a few of those points. First, we're seeing that financial partners, donors, and funders for nonprofits want to give their money to groups that are doing the most good and creating the longer-lasting impacts, and also to groups that are able to maintain a very high level of accountability about the work that they're doing. So donors want to know what's happening with their money, and they want the most out of it. This requires a level of accountability from nonprofits that depends on quick communication and the ability to quickly share information. This was not possible in years past, certainly. Much of the world it can, much of the world it can take and has taken weeks to get reports from one country to another. As an example, when I was a child, my parents kept in touch with their colleagues on a radio every morning, and as a teenager, the closest internet connection was eight hours away over dirt roads, and then once you arrived there, you could only get internet access if the phone lines were up and the power was on and they often were not. So we've come a long way in the past decade and a half. Another issue with this idea of accountability is an expectation by funders and a goal by nonprofits themselves to see the money going to the actual work that they're doing. So for example, if I'm working with a nonprofit providing for children in Africa, I don't want that money scooped up into admin overhead in Paris or D.C. I want to know that those children are actually being provided for out of the funds that we're managing. So again, the web has been changing. It continues to change, and it's being used less today as a billboard style marketplace and more of a robust tool for communication, collaboration, information sharing. There's inability to literally invite the entire world to be a part of your work. It's pretty awesome. And then to provide those partners with the tools they need to confidently continue their involvement, organizations can now keep the public and their donors up to date on their progress and on their needs. This raises awareness, which is great. It also creates more funding, which is great. And ultimately, it advances the good work that's being done. So this is where Drupal comes in. Drupal provides the tools needed by the nonprofits and the tools that partners, financial partners are looking for. And because of the large community collaboration in the Drupal community, it's very similar to that of the nonprofit community, we see that time and costs can be saved. So Scott's going to talk a little bit later about functionality and customization available in Drupal and in the distributions and how that can cut overhead for web development while still answering specific and varied needs for different clients. So like I said earlier, we've worked with many nonprofits over the years, and each of them have had very different missions, goals for their work, but we've noticed some similarities in their web development needs. It was these similarities and a lot of contribution that led to our release of the open aid distribution. And open aid is our response to some of the issues facing nonprofits and sort of how to respond to those. So I'd like to share some examples of the client work that's helped to clarify these needs and then eventually to shape the open aid distribution. Thanks. International Center for Journalists. ICFJ strives to be a catalyst for change through good journalism. They believe that independent media is crucial to improving the human condition. Their work is pretty awesome. They are partnering with the Pointer Institute, which is another journalism organization, to provide training and support for journalists around the world and specifically in countries where it is extremely difficult to tell the truth about things and often life-threatening to do so. ICFJ seeks to strengthen societies through accountable relationships with their partners like the Bill and Melinda Gates Foundation and the Knight Foundation. In addition to this providing of tools and resources, they are also trying to educate the public on what they're doing. So during our discovery process with ICFJ, we found they had some specific requirements for their web presence. And we'll just go through some of these slides. That might be a bit quick, the screenshots. An image carousel. ICFJ uses an image carousel to quickly communicate the work that they're doing and the stories that they're covering. The new section is presented in a blog style. It includes search capabilities, multi-author blogs. ICFJ has a variety of blog contributors worldwide. So this gives them the opportunity to present author information on the right and then the blogs down the middle. Profile pages provide detailed information about contributors and partners with space for related projects and social media coverage. Program pages. This section allows ICFJ to focus on their projects. So they can include video, images, information about the individuals working in those projects and event information. Mapping on ICFJ's site is worked into their program pages. So basically if you click on a point on the map, it takes you directly to the program page associated with that area. And partner profiles. This is of course extremely important to any nonprofit. It gives a place to present partner information and these of course are the groups and people making the work possible. And a resource library. ICFJ provides a lot of resources on their site and these are searchable by language. So the second client I'd like to go over is International Center for Transitional Justice. I had no idea who these people were when we started this project and this idea of transitional justice was a new one to me. ICFJ works, transitional justice refers to measures taken in the wake of massive human rights violations. So this group is coming in after things like genocide, war crimes, child slavery, gender oppression and they're partnering with government and non-government organizations to, I don't want to say clean up societies, but they're working with the criminal perpetrators and also with the victims to make sure that people who are responsible for these atrocities are being held accountable and to work with societies to make sure that there's not repeat atrocities. If you have a chance to look this side up, it's pretty amazing. So during our discovery process with ICFJ, we defined the following requirements for their website. An image carousel, like ICFJ that we saw before, they're using an image carousel here to quickly communicate their work to their audience. News section, these items are presented chronologically. There's associated topics listed on the bottom of each item for more reading. Profile pages, again, this gives a space for detailed information on ICTJ's leadership, their staff and their partners. Program pages, there's a lot of room for images here with room for news and updates on the sidebar. And mapping, this map works a little different than the first client that we saw. These, in this site, the program pages are actually the countries, so the map's been customized in Drupal to work in two separate ways for two different clients that needed two different things. ICTJ uses a lot of photographs to communicate with their users, so there are several image galleries on their site that they can use for that. And a resource library. These resources are listed by publish date. They're searchable by type, country, issue and language. And the final client I'd like to go over is Knowledge for Health. K for Health is a USAID funded organization. They manage and distribute evidence-based information and tools to provide healthcare, health services in developing countries. What that actually means is that by providing health information in audience-friendly fashion to multiple people groups around the world, they're able to help save lives and create sustainable practices, health practices in developing countries. They're run by the Johns Hopkins Bloomberg School of Public Health Center for Communication Programs. So we worked with them to improve their web products and to redesign their primary web presence. And during that process, we discovered the following items that they would need for their site. An image carousel. This space is, again, allowing them like the previous examples to quickly visually communicate to their users. A new section. This is another good example of Drupal customization. The new section here, like the previous example, is presented in a blog style chronologically, whereas the first example is searchable by categories and date range. Profile pages on K for Health site include an image, bio copy and blog post links. And program pages. This presents a zoomed in view of the map specific to that area. So we see here Ethiopia. We see Ethiopia, yeah. With the map of Ethiopia. The mapping, this one on K for Health site operates similarly to that of ICFJ. So you just click on a point on the map and it takes you directly to the program associated with that area. And finally a resource library. Much of what K for Health does is to provide resources around the world. So these are searchable by type and topic. So through the three site examples, ICFJ, ICTJ and K for Health, we see that one of them is journalism, one of them is transitional justice and one works in healthcare. So they all have different goals and missions, but they have very similar needs for their web presences. Each of these clients has specific and complex functionality that we obviously don't have time to get into. But I think it's good to just look at this idea of the commonalities and the differences and how we've been able to optimize both for the needs of the client. So during our work with K for Health, we learned that in addition to their own website, they're responsible for rolling out websites for affiliate organizations, their affiliates and USAID affiliates. So we had an opportunity to come on with that project as well and to build a platform that allows their internal developers to roll out these microsites for their affiliates. It was during that process that we started to see these similarities and thought, hey, outside of USAID and K for Health, there's probably a number of nonprofits that could benefit from this platform. So with a lot of work by our team and their team and many other people, we looked through some of the work that we had done and came up with a list of consistent needs for nonprofit sites. Can you go to the next one? Thanks. And this list is gonna look pretty familiar. This is our list of consistently utilized nonprofit and NGO features in image carousel, news, multi-author blogs, profile pages, program pages, mapping, partner profiles, image galleries and a resource library. So with a lot of intentional contribution from the K for Health team and our team at Atten and many different levels of many different organizations, we were able to release this platform as the openaid distribution on Drupal.org. We call openaid a turnkey website platform designed to help small NGOs and international development projects create cost-effective program-focused websites quickly. So Scott's gonna talk more in detail about distributions and openaid and also about collaboration and contribution. Okay, before we get too far into openaid and how that works, I wanna back up a little bit and talk about distributions. Is our people familiar with distributions in Drupal? Yep, looks like maybe half of you. So distributions are relatively new to Drupal and we've had similar things in the past that we've gone by a few different names that were kind of consolidating on how this works. And this is the documentation on Drupal.org about what a distribution is. So I just wanna read through this to give you kind of a technical overview. It says distributions are full copies of Drupal that include Drupal Core along with additional software such as themes, modules, libraries and installation profiles. That's kind of the technical definition of distributions but that doesn't really give you a great idea of why distributions are important and how they're going to change the way we work with Drupal. So I wanna talk about why you should care about this. And the first part of that is to talk about how Drupal works. This is probably familiar to many of you as well. There's an often used metaphor for Drupal that it's like a pile of Legos. So when you get a Drupal site you have a bunch of different pieces, modules that you can put together, modules and themes and other things but mostly modules that you can put together to make whatever you want with Drupal. But when you first install Drupal it doesn't actually do that much. An initial Drupal install is kind of a blank slate to build whatever you want. So Legos are cool, they're great and Drupal's great. You can make houses and spaceships and dinosaurs or whatever you want. You can make whatever you want with Drupal too. But the downside of that is it takes a lot of work to find the right pieces and put them together in the right ways. And we found that that work is especially hard for nonprofits which have limited resources and wanna put those resources as much as they can into their core work. So that's kind of a problem that we've had in the past with Drupal that especially affects nonprofits. So the alternative to this is kind of the Playmobile approach. If you're not familiar, Playmobile is a product that comes preassembled. So if you wanna make a dinosaur with Legos you buy the dinosaur set or you buy just generic Legos and put them together. But if you wanna dinosaur with Playmobile you just go to the store and buy the preassembled dinosaur and you're done. You don't have to put it together and make it work like a dinosaur. It already does that. And this is probably closer to how something like WordPress works. WordPress when you install it it's a pretty full featured blog product. You can add more to it but you don't generally have to add more to it. You can often just install it and start using it. Unfortunately the downside to that approach is that it's a little less flexible. If you buy a Playmobile dinosaur and you wanna make it green or you wanna make it bigger you can't really do that with Playmobile. And to a lesser extent that's true of WordPress as well. You can install WordPress but if you wanna make your blog have a map or have a donation system or something that's much harder to do with WordPress because it's not as flexible and it's not as modular. So this is where distributions come in and hopefully solve all of these problems. Distributions I think are like preassembled Lego sets. So you buy them, well you don't buy them but you get them and they already do something for you. You don't have to put them together to do what you wanna do but they also have the flexibility that you can take them apart and make your dinosaur bigger, make your Drupal site do something slightly different but it already does something so you get all of the advantages of both worlds which is especially good like I said before for nonprofits that have limited resources. So the idea of a distribution is the technical team can install it and administrators can immediately start using it without having to wait for any sort of custom coding. If you're doing custom coding you can start using it while you're doing that and you don't have to wait on the technical process before you can actually get some benefit out of it. So we've seen some ways that nonprofits specifically are benefiting from distributions and for smaller nonprofits the first way is kind of like what I talked about is the Playmobil approach. Smaller nonprofits distributions are really great because you can just install them and use them. You don't have to spend much time at all if any actually using a distribution in Drupal. You can like I said, customize beyond so if you find a distribution that does almost what you want it to do you can install it, turn it on, start using it but then like do the last 10% or whatever of how you want it to work. For larger nonprofits distributions are used like that but they're also used in some other ways. Larger nonprofits get a big advantage out of distributions in kind of filtering conversations around what they're doing. So if you go through the time to talk about your organization's needs and your goals and pick a distribution that you think meets those needs and goals pretty well then as you're having requests that come in for additional functionality that is desired if you pick something that meets your needs and goals and you're talking about something that isn't accomplished by that distribution that's often a good indicator that maybe you need to back up and talk about what you're trying to do and is that actually part of our organization's goals. That's kind of a non-technical advantage of distributions for larger nonprofits. Larger nonprofits also can use distributions, have the opportunity to use distributions as not so much a ready to use website but a ready to build kind of development platform. And this is actually, we're not a nonprofit but this is actually what we do at Aden with distributions primarily. We have a custom distribution that we use internally that has all of the Drupal development tools that we use to build sites pre-installed so that when we start building a site we don't have to download and enable views for example. That's already there and that saves us a lot of time at the beginning of a project. So for larger nonprofits they're rolling out a lot of different sites. This can save a lot of time building something that kind of does what you're going to do at the beginning of every project and then you don't have to do that over and over again. Like Lydia said before, this is also what we built for the K for Health team. They're rolling out a lot of sites for their affiliates so we made something that would allow them to roll out those sites a little more quickly. We identified the common needs that they had and made something that accomplishes most of what they are using on any of their sites and then they can do that end customization without having to repeat the same steps over and over again. And like Lydia said before, as we went through this process we recognized that what we were building would be useful beyond K for Health and their affiliates. We put some work into making it not just a development distribution but an actual end user distribution. And that's what we eventually released as the open aid distribution. So based on our experience working not only with K for Health but with many of the other non-profit organizations we've worked with, we're hopeful that the open aid distribution is a tool that many non-profit organizations can use to kind of solve their base needs if not all of their needs. And fortunately, talking with the K for Health team about this, they agreed that this would be a good idea to release this as a contribution on Drupal.org. So after we were done with their kind of internal project we put some additional time into generalizing this approach into a platform that would hopefully be more useful to a wider community and that's what we released as the open aid distribution. So this is the list of features that open aid has which hopefully by now looks really familiar. There's an image carousel, there's news, there's multi-authored blogs, profile pages, program pages, there's mapping, partner profiles, image galleries, resource libraries. In addition to all of that, open aid has some other capabilities beyond that kind of base level set of features including branding accommodation for logos so organizations can put their own logos in there or it comes, open aid comes with an open aid logo but we don't expect anyone to actually run an open aid site with the open aid logo or assuming they're gonna replace that with their own logos. There's customizable color schemes so everyone can kind of brand the site to go with their own look and feel. Automated translation using translate this which is especially useful for organizations working internationally so they can have content available to people speaking a variety of languages. Social media links which almost everyone is using now and a mobile friendly responsive design so that open aid sites look good not only on desktop and laptop computers but they look great on tablets and mobile devices which is increasingly important. So this is kind of what it looks like to install open aid but also what it looks like to install most distributions to kind of give you an idea of why distributions are useful. So this looks a lot like the standard Drupal install process. Normally you have a standard install option and a minimal install option and if you download a distribution you'll have at least a third option. In this case you have the open aid site option. After you choose that you go through the same language and database setup that you would with any Drupal site and then you go to the list of modules that are being enabled by default. Open aid installs a little bit more than a standard Drupal site in this initial process but it doesn't actually do a lot more than Drupal. The big difference with open aid is what happens after this. You get redirected to this page which hopefully you can see. This is a list of all of the functionality that is available in open aid and the idea with open aid is that after you install it you go through this list and decide what do you actually want to do with it. So if you want to do blogs you turn on the blog feature. If you want to list your partners you turn on the partners feature and after going through this list and deciding what do you want to do with it and checking the boxes next to the features that you want you just click save and all of that functionality is immediately available. Like I said before you have the option to customize anything you want but hopefully it comes pretty close to meeting your needs and you can immediately start entering content and that content will show up on your site where you would expect it to and your site is hopefully quickly usable right after install. So I want to talk about some sites that have been built on open aid so far to give you an idea of kind of how distributions are used in practice. The first of those is the Global Health Mini University and this site is an annual forum that brings together professionals working in global health and they do presentations somewhat like DrupalCon I guess presentations highlighting evidence-based best practices and kind of state-of-the-art information in the health industry. So open aid was designed as a web platform for organizations to kind of promote their own work and talk about what they're doing the good work that they're doing in the world but we found with the Mini University site that it works just as well for this kind of event-based site that has many of the same needs as an organization. So you can see they're using the image carousel feature not to show images of the work they're doing but to show images of the event that they did that they've done previously to kind of attract people to the next event and they're using what we're calling the hero statement feature over on the right there rather than to talk about their organization it talks about the event and gives dates and information about when the event is happening using latest updates to give updates on the event and they're using the partners feature to list the event sponsors. So we were happy to see that open aid was proving useful kind of in this context that we hadn't previously planned on it being used in. The next site I want to talk about is the mHealth working group site mHealth is a collaborative effort by 11 different organizations to promote the use of mobile technology in the health industry. So they work to build capacity, encourage collaboration and share knowledge about how mobile technology can work within a larger global health strategy. And of course one of the most important features of open aid that was useful for them is the responsive design. Of course they're trying to promote the use of mobile technology so they need a site that works well on mobile devices and open aid just does that out of the box so they don't have to do anything to get that advantage. The mHealth working group site also like I said has a lot of different organizations working together. They're doing 100 different projects in 50 different countries and they're working together with organizations like Catholic Release Services, K for Health, Save the Children. So one of the big issues that they have content-wise is how do they promote all of these different organizations and in a way that gets them all enough attention that it's worth their investment in this effort. One way open aid does that is with this partners page that is just a page that lists all of the partners with their logos and links to their sites if someone's specifically interested in who's behind this they can go here and see them. Another way open aid does this is with this partners sidebar interface and this is a scrolling interface of again all of the partners but it takes up a little less space so it allows them to put it throughout the site so if you're just looking at some other content you might notice the one of the partners and that kind of gives some increased visibility to the people who are contributing to this work. mHealth also uses open aids resource library and they're using the optional integration with Apache Solar which you can see over on the right there that gives them a listing of the different types of resources that they're sharing and like how many and that allows them to filter down and kind of in a more of a browsable interface with Apache Solar. So they're using that to share things like their meeting minutes and presentation slides as well as documents that they've specifically created to share so that that kind of gives them some increased transparency and lets people see how their work is happening not just what they're doing but like how they're doing it. Finally I want to talk about the malaria free future site. This is one of the first sites that launched on the open aid platform and I think it's a good example of how you can kind of customize a distribution like open aid to work more specifically with your organization's needs. So malaria free future is an organization seeking to improve control of malaria and they work with public and private organizations in Ghana, South Africa, Tanzania and Uganda and their goal is to scale up malaria control and kind of solve the malaria problem. And the first thing you can see here if you can see that is that they've significantly changed the navigation of open aid that you get initially for example projects what we're calling projects for the malaria free future organization those are all country specific so they're referring to those as country programs which is a little more in line with the type of language that their visitors would expect. They've also added a few items to the navigation that are specific to the focus of their organization so they have a United Against Malaria navigation item which of course doesn't come with open aid because that's not something that everyone needs but it's something that they specifically need and they're able to easily add that to the navigation and kind of work it in with the rest of what comes with open aid out of the box. Like I said before they're working in several parts of Africa specifically so they're using the mapping feature in open aid already zoomed in on the specific areas where they're working which allows rather than having a global map that only has points in a specific area they've zoomed that in on the area that they're working in so people can click on Tanzania and see the work that they're doing in Tanzania. So that's kind of like how you can change open aid and some of the ways people are using open aid we've set up a demo site at openaiddistur.org with everything that open aid does turned on so if you wanna play with that you can see everything that open aid does. And that also that's as much as possible a bare minimum install of course we had to add some like sample content so that you can see it but this is pretty close to what you get like if you just download and install open aid. Speaking of which open aid distro also has a link to where you download open aid which is just the project page on druple.org. So if you want you can download it and install it yourself and hopefully that is a quick process to see what open aid could do for you. We're of course excited about open aid and how people can use open aid and we have some flyers and buttons up here if you're also excited about it. But we recognize open aid is not the solution for everyone or even all non-profits that's not at all our goal. What we really wanna focus on is open aid as an example of using distributions because we think distributions is a great solution for a lot of organizations including a lot of non-profits and there are some other great distributions that are specifically interesting to non-profits. There are over 400 distributions on druple.org right now and here are a few that you might be interested in if you're working for with non-profits. Open outreach is a distribution specifically focused on kind of grassroots and activist organizations. So if that's the kind of work you're doing you should look at that. Open public is a distribution focused on government and public policy work. So if you're doing that kind of work that's a good thing to look at and Julio is one of the few distributions that doesn't start with the word open. Apparently they didn't get the memo that that's what we're all doing. There's no reason distributions need to start with open. I was just kidding. So Julio is focused on education and schoolwork. So if you're doing stuff in the education sector Julio is something you might wanna look at. Like I said, there's over 400 distributions on druple.org and they solve a lot of problems that many organizations have but of course they don't solve every problem. Distributions don't quite do everything yet. So that raises the question of what do you do if you look for a distribution that solves your problems and you don't find something. What I wanna encourage you to do is make your own distributions. Beyond distributions in druple one of the big things you wanna encourage is non-profit contributions back to druple and making a distribution is a great way to do that. I'll talk a little more about kind of the things you wanna look out for in doing that but I wanna be clear it's a lot of work to make a distribution and like I said before you may think you don't have the time to do that. One of the great things about the open source community and specifically the druple community is that you don't have to do that work by yourself. There's a lot of other organizations that have similar needs and probably a lot in this room. So just to like kind of demonstrate that. Who here is working with an organization that is membership focused? Like you have members of your organization. Okay so a few of you have that need and might want to work with each other. Who here is doing advocacy or like petition-based work? Couple people. So you should all look around and see who else is raising your hand. Those are the people you wanna work with. So those are just a couple general level needs of non-profits and obviously this is a relatively small sampling of the larger druple community. So the point I wanna make here is that there's other people who are trying to solve the same problems you are and we could all be working together more to solve these problems and we can get a lot out of that. That brings us to collaboration. So that's like I've hopefully indicated that's sometimes easier said than done. Collaboration in the druple community means we can save a lot of time and money and often find better solutions than we would on our own but the first part of that is finding other people to work with, who are you going to collaborate with and that can sometimes be difficult to do. There's so much opportunity in the community to find commonly needed solutions and work with each other but the first step is figuring out where to get started. Fortunately we have Drupal.org for that. Drupal.org is a great place to find other people doing similar work and to find other people who have already done work that you need to do. There's thousands of active projects on Drupal.org and there's people talking about creating new projects and people working to solve new problems with technology. The slogan on Drupal.org and kind of the slogan of Drupal is come for the software, stay for the community but you could really just come for the community. The community alone in Drupal is useful enough by itself and it's a huge community full of all sorts of awesome people which hopefully you've experienced at Drupal.com somewhat and it's also made up of a bunch of smaller communities that a lot of people working with Drupal kind of miss out on that. There's hundreds of groups on groups.drupal.org focused on kind of specific interest groups and I want to encourage you to get involved in some of these that are specifically relevant to non-profit interest. So there's a Drupal and Education group if you're doing any sort of education work I'd encourage you to get into that. There's a Drupal for Government group if you're doing anything that interacts with government work that's a good place to go. Hopefully almost everyone in this room has a reason to join the Drupal for Good group but just in case you don't if you're working for one of those rare non-profits that's focused on evil there's also a Drupal for Evil group which I think is mostly a joke but it's fun to see what kind of stuff what kind of conversations happen in that group. There's also groups for most of the distributions we've talked about talking about how they're going to move those forward. So there's an open outreach group, a Julio group and we're just starting an open aid group. Beyond groups on groups.drupal.org I'd encourage you to get involved in issue queues. If you're doing Drupal work you're using modules and if you look at the modules you're using or even modules you're thinking about using you have a ton to gain from getting to know the people who make those modules so that when you need to interact with them you have a established relationship with them. And so the first thing is to go to Drupal.org and just look through the projects and find the projects that you're actually using. And the next step is to start interacting with those projects in the issue queue. A lot of people with less technical knowledge think that they shouldn't be there they shouldn't be doing that. But even going in to an issue queue and saying something as simple as like this is what I'm trying to do I don't see a way to do this with your project. Even if it's not specifically mentioned as a feature that kind of input is incredibly useful for project maintainers to kind of get ideas of what people want to be doing and kind of start conversations about what's gonna happen next in the Drupal community. More generally I think a lot of people get into nonprofit work because of ideas like this. This is a quote from Gandhi. It's be the change you want to see in the world. And I would encourage you to apply the same sort of approach to your Drupal work. So you don't have, just like you're not waiting around to improve the world. You're actually doing something about it. You don't have to wait around for anything to happen in the Drupal community. All you have to do is say like I want to see this happen. It's not gonna like magically appear but there's no reason to wait. The Drupal community gives everyone a lot of opportunity to create change and like influence how Drupal works. So I would encourage everyone to take advantage of that. Beyond groups and issue queues and distributions, there's several other good ways to get involved in the Drupal community. One is IRC. If you're not already on IRC, you might have no idea what it is. It's kind of a simple chat system that is used pretty heavily by the Drupal community. And there's dozens of chat rooms where people are talking about the Drupal work they're doing and here's a couple that are specifically relevant to people working with nonprofits. There's a Drupal NGO channel on IRC and there's a Drupal EDU channel. And IRC allows you to do like real time chat with people all over the world who are doing similar work to you. So it's a great place to have more direct communication with people in real time. Another great place to do that is local meetups. Most larger communities have a monthly or more often Drupal meetup. And if you're working somewhere that doesn't, you should start one. Local meetups are less likely to have people who are doing the type of work you're doing but have a lot of people working in Drupal who can answer questions or give you suggestions on how you might solve problems with the work that you're doing in Drupal. And you can find local meetups again on groups.drupal.org. Another great place to get together and like start talking to people who are doing similar work is events like this like DrupalCon. We're kind of coming up to the end of DrupalCon now. But there's still this afternoon to there's still an opportunity to like create buffs, birds of a feather discussions and get together, invite people who have similar interests to work together with you. And there's also plenty of opportunity for hallway conversations. If you saw other people raise their hand with similar interests to your own, just walk up and start talking to them, find out what they're doing, talk about what you're doing and hopefully start making stuff together. However you get involved in the Drupal community, I'd encourage you to start with the most general needs possible. It's really easy to get sidetracked as soon as you find out that you have slightly different interests, but we found the best way to do this kind of work is to start with common interests, solve your common problems first, and then once you have a solution that will attract more people who have that kind of general need and then you can find people who have more specific needs and get gradually more specific and eventually find that person who is doing the exact work that you're doing. But if you look for that perfect match up front, you probably won't find it. So I'd encourage you to start general and get slowly get more specific. Don't focus on the specific stuff at first. So after you've worked with the Drupal community and made something, another great thing to do is to contribute it back. Many organizations and I think specifically nonprofits are using Drupal, but not contributing back. And the reason for that is that it takes a lot of time and effort and money to contribute back, but you also can get a lot out of that. So I wanna talk about how you can hopefully make that work. And the first part of that is to recognize that contributions won't just happen. You have to be very intentional about it. If you just, I don't know, if you kind of think that contributions would be nice, but don't take any, don't put any thought into how you're actually going to make that work, it very likely won't happen. So Open8 as an example, started as an idea on our project team, like, hey, maybe we should contribute this. But it eventually required the buy-in from a lot of different people in five different organizations. And that's a lot of communication overhead. So it's very important to kind of get your message together before you start talking about it. It can be a hard sell to say, hey, let's take this thing that we've put a lot of time and energy into making and give it away for free. That fortunately with Open8 that the organizations working with K for Health and USAID were very receptive to that. But a lot of people aren't if they're not already familiar with the idea of open source. So here's some ways, I encourage you to talk about that that can get better receptions. First, focus on the overlap between the goals of your organization or the organizations that you're working with and open source ideals. A lot of nonprofit organizations, if you look at your mission statement or the mission statement of the nonprofits you're working with, will say something about promoting the greater good and collaborating with others. And that's exactly what open source contributions are. They're collaborations towards the greater good. Second, contributions to open source are great PR. Organizations that contribute to open source kind of position themselves as innovators in their sector and kind of thought leaders. If you're putting out there something out there that other people are using, then they'll look to you to kind of drive the direction of your market. Finally, and perhaps most importantly, there's money in contributions. Like Lydia said before, a lot of grant funders are looking specifically for open source contributions and prefer giving money to organizations that are doing this kind of contribution. It's a lot better for them to give money to you to help both your organization and dozens or hundreds or thousands of other organizations rather than just only helping your organization. As an example of this, we've done some work with the Knight Foundation and are very familiar with them. They do a lot of journalism and technology funding. And this is a quote from their blog that says grants to nonprofits have an open source requirement. Any software developed with grant funds has to be open source. If a grant is made to a business, both the initial and future releases of the code need to be open source. So in this case, they're actually requiring open source contributions to get money from them. Many other grant funders are kind of happy about open source but not going as far to require it. But the money is definitely on the side of preferring open source contributions to not. So you have a lot to gain money-wise from that. So hopefully as you start talking about how you're going to contribute, you can be confident that other organizations are already doing this successfully and kind of integrating it into their overall strategy. And hopefully all of this kind of gives you an idea of some confidence that there's money available and working with Drupal with nonprofits. There's the technology is getting better and better for doing this work efficiently and quickly. And there's definitely a huge community here eager to help with this kind of work. And like Lydia said before, this like using the web effectively has never been more important and it's not likely to get less important. So Drupal's hopefully a good place for you to start thinking about and figuring out how to do that well. And we have a little time for questions now. We'd also love to hear what everyone else is doing if you're working with distributions or what your experience has been with contributions or like how you're working with Drupal with nonprofits. I think we'll not use that mic and I'll just repeat questions so that we get them recorded. Anyone? Yeah, so with OpenAid, we're displaying projects which is like the most general term we could give because everyone wants to map something slightly different but most people, so there's two main things people want to map. One is where they're working and one is where they're located. And so the more common need that we identified was where they're working. So we called that projects but I mean you could take projects and make that where you're working or where you're located. As far as the technology we're using for that, we have in the past and OpenAid comes with an open layers solution and I think the default design of that is using a map box if you're familiar with that which the specific tiles that we're using is semi-transparent so you can, that the color branding of OpenAid uses follows through to the map as well so we're using a semi-transparent background and then you just put a color behind it and that follows through, I don't know if that's clear enough but that color influences the texture of the map. Recently we've been working more with more specific mapping solutions. OpenLayers is kind of a, I don't know, it aims to solve all mapping problems and it can sometimes be a lot of code overhead. We've been working a lot with, for example, leaflet recently and that doesn't do as much but it does it more quickly. I don't know if that's, hopefully that's helpful. Oh, sorry, I said I was gonna repeat questions and I didn't so the question was, now that I answered it all, the question was what are we doing with mapping? How are we doing that, I think? Where is it? Drupal in academia meetup at 12 outside the Saint Monarchs room in this building. Really? I don't know if it might be my setting here but I don't just wanted to let you know it. It worked perfectly, perfectly, with downloading the SIFI and unpacking it and all the rest. So his comment was he installed OpenAid while we were talking, it worked well with the package download but not well with Drush. That's, so like I said, making distributions takes work and it's also new in how much work. I think that depends on what you're doing. So I said we have our own internal development distribution. That didn't take that much work because we've just kind of, as we want to add new things to it, we've just done that in bits and pieces and that's not something that we've set aside work to do. We've just slowly built that up internally. Something like OpenAid, that it's hard to say because we, that came out of, like we had an actual schedule for the work for like most of the work on that but then we did some additional work in kind of the, as we had time. Gosh, I don't, can you have any estimate on how much time we put into that? Definitely weeks of work, if not months. So, but what I was saying is, distributions are also kind of new on Drupal.org and we're still kind of working out the kinks of making distributions work. Part of which is like distributions get packaged on Drupal.org with Drush but you need a very specific setup of Drush to make that work so that might be the issue is that you might need to upgrade your Drush but I probably shouldn't be trying to do support here. Anyone else questions or want to share your experience? No? Okay. Oh. Yeah. So OpenAid has kind of a in, I don't know. OpenAid has, our designers here as well so I thought he might want to answer. It's hard to, OpenAid definitely has like, it's general enough that you can probably recognize an OpenAid site but at the same time, that's just your basis and you can definitely customize it from there if that's useful for you. The idea is just that it gives you something you can use that looks good out of the box and if heavily branding your organization visually is important to you, you're probably going to want to do some significant customization because like you said, OpenAid sites definitely have kind of a common look to them just like, I don't know, a default Drupal site out of the box. You can kind of recognize that just by looking at it. So yeah and we're definitely welcome to input on how we can make that more customizable but yeah, you're right that if you want a very specific look, you're probably gonna, you'll need to do some customizing there. Oh, sorry, I did it again. So the, the comment was that, I remember maybe the question was about customizing the look and feel. Right now it is just changing the logo and shifting the color scheme. Those are your only options with the theme that comes with OpenAid but you can change that theme if you want. Yeah, with fundraising? Yes, yes they do. So the question was about fundraising. That is not, that's definitely on our feature list for OpenAid, for future features. Fundraising is complicated because you're right that most nonprofits need to do that but there's a wide variety of ways in which they do that. Some take direct donations, some have some sort of membership or subscription system. Some are actually selling, selling some sort of product or membership product. So, and there's also a lot of nonprofits are already working with specific payment processors. So it's hard to find a solution for that that's generally useful and like I said, we're kind of focusing on the common solutions first. But yeah, we're definitely looking at ways that we can do that in a way that will be useful for a variety of organizations. I'm not sure if OpenOutreach, you might want to look at that. I'm not sure if they have some sort of way to accept donations in the OpenOutreach distribution. But yeah, that's definitely a problem that needs solving but it's also a hard problem to solve for everyone at once. So good question. I don't have a great answer. Yeah. In case anyone didn't hear that or for the recording, he said that he's working on or with a distribution that does crowd-sourced funding, I guess. Yeah, sort of like Kickstarter, which is one way to take money Yeah, so if you're interested in that, you should talk to that guy. Anything else? I think we're actually past time now. So thanks everyone and we're happy to answer more questions if you'd like to talk personally.