 So I'll start and I'm going to talk about how to get designers involved in your project. So a bit, a bit even more basic than we've talked before. So, yeah, I also work on next cloud and the design team since a long time already. And yeah, so the short story of how to get designers involved is basically go to open-source-design.net slash jobs and post what you need on the job board, on our job board of the open-source design collective. But the long story is a bit longer and I'm going to use examples that we learned from working on next cloud and that I also learned from working in other communities. And it's, yeah, very, very basic things which have a lot of impact. So can I have a show of hands? How many people work on an open-source project? Okay. How many of you do not have any designer involved in that project? Okay. Or somewhat maybe also. So this will be very useful for you but this will also be very useful for people who are designers who work on a project and who want to improve. So even though it's kind of, or I consider them very basic things or I keep repeating them in projects, I think a lot of people or a lot of projects still don't do them. So yeah, you'll see then. Just a small word about next cloud. You might have heard about the whole on-cloud, next-cloud fork. So short story, next-cloud is a community fork of on-cloud because we were unhappy with some things, for example, that not everything was open-source and a bunch of other things. So yeah, you can ask me later about it. But anyway, this next cloud is like an open-source alternative to Dropbox and Google products for files and contacts, calendar, email, video chat, stuff like that. So yeah, it's quite an extensive project. You already heard about Ragu that he maintains the calendar or co-maintains the calendar as designer. So yeah, we have a bunch of components and there's lots of things that we learned during the years. So first thing of four basic things is to establish a culture of design. So I was back when it was still on-cloud. I was like the fourth or fifth contributor and I was the first designer in the project. And yeah, it was very few people and there wasn't even a company yet and yeah, it was just like a few people hacking at a table and stuff. So the first thing, very first thing I did, because I come from a design background and not from like a programmer or open-source background, very first thing I did was look at this and say, what the fuck is this? So you can even see like I have trouble fitting it on the slide because there's so much stuff on it and so misaligned and yeah, that's the own cloud one installation. So yeah, it's pretty... I mean I could point out like what's wrong with it, like alignment of the field labels to the left, the password, you need to retype the passwords. It's pretty much a drag. You need to choose the data directory or you can change it, which I don't even care about. Force SSL, just do it. All this stuff like date format, what does g even mean? I have no clue. Probably you can tell me, but I don't even care. And then one of my biggest problems with the whole thing is the database. Like I remember horror nightmares of copying and finding database credentials somewhere in some weird other subfolder or asking my web host for that and even with like a bit of nerdy skill that was difficult. There is also like a technical choice to usability and some sort and that being how it looks like now, that's the installation now, you see there is no database field by default because we use SQLite by default. It's not 100% advised to use it for big installations, but that allows us because SQLite, if you know it or not know it, it's just a single file and you don't need to create any username, password, credentials or whatever, it can all be done by the web server. So it's a technical decision that allows us to actually make it so simple. You just need to choose an admin username and password. We could just also like directly log you in and give you the credentials or have default credentials, but that would result in a lot of insecure installations. So we don't do that. But yeah, we make it, I'd like to think even simpler than the WordPress five minute install and yeah, this, but you can still change storage database so you can still modify two things. One is the database, so you can change it to MySQL or PostgreSQL or whatever you want, whatever you implement and then also to, you can change the storage path so that you can store it somewhere else and all the rest is just done automatically. So the, yeah, so it's just username and password. It's basically, this is very similar to just the login screen actually and that's very simple. That still though leaves you with, you need to download it, you need to set the permissions and stuff like that. So you always need to know that in open source we have this additional problem. We don't have a sign in button on the page. We have a download button, right? So that's a very, very different thing. So yeah, but that gets easier and some sort also technical reason with PHP seven, I think at least because you don't need to mess around with permission so much anymore or on certain servers. So a lot of technical things interweave with the design decisions or with how the UX is at the end. And in this case, UX is of course the user experience of admins installing the software. Okay, so that's the first thing and I think I've been talking so long about it now because I think it's so important that the setup process is easy because that's the first reason that people turn around and don't use your project like website and installation process, I would say. Next thing is you have to care about details. So for example, here we have a colleague of mine. He's actually more of a developer but does a bit of front end and yeah, he opens that issue or we basically did it together. At every meetup we now do, we have four meetups during the year. They're like planning meetups or working meetups for the next version and they're open so everyone can actually attend and what we established during these meetups is that we sit in a meeting room and we install the newest version or the current development version and we just click through it as if we were like people new to the project and we just point out every single small thing. So you see like, there's like wrong capitalization for example or white space issues or some icon errors like it's white instead of black and stuff like that. It's very, very detailed things. So that establishes a general culture of design, a general culture of the, you probably heard about the no broken windows policy. So if you don't see anything wrong then you're also less inclined to do wrong choices or you encourage people to do similarly nice looking things. So that's very important to do that with everyone and everyone is in that room like all the developers or the other people working on it. So yeah, it just brings everyone together on this design or experience base. Second thing is be informative. So what does that mean? It's basically something such as simple as just putting screenshots in your readme, in your repository readme. A lot of projects I look at, I go to their GitHub or to their GitLab or to their repository anywhere and they don't even have any screenshots even though it is an app which probably has an interface and there's like a ton of explanation and it's like oh we use PostgreSQL and some blah blah blah cluster with some AngularJS and I don't even care about that when I want to use it. So basic thing, just a short explanation like even those tags are a bit nerdy but that's okay. So just short explanation and just a nice screenshot so people can understand what they're actually looking at. So that's very important. That's one very small thing. So the people who raise their hands if you don't do that yet, please do that now and because this is also similar to the website so if you don't have a website you just have a repository, do this. So make sure your website has short explanation and a screenshot but most projects don't have a website yet so just do this. Next we scroll down in the readme and then we need some kind of a concise feature list explaining what the hell this actually does. So we have some funny emojis, also part of design and we just list some features or some important functionality of the app to explain what it does and then we even have some more nerdy info like we say if you want to send a script to the email just use this browser extension and which libraries we use for example just for developers who also want to get involved and also what we have planned for the coming versions so it's kind of like being informative and being open about your process. Then we scroll down even more and the problem is always like oftentimes people or projects don't even have any setup info like how the hell do I make this thing run? I just download it and then what? You just clone the git repository which is already pretty difficult for many people and then I'm just left there and I see an install.sah and I see a grant file or some shit like that and I'm just utterly confused about what I need to do next and so one important thing is do not assume that everyone knows what they need to do with a make file or what they need to do if they see a make file or something like that just write it out and make sure that it's very few commands so I'm actually still complaining about this like about two commands so if it can be like just make it make or I mean nothing at all would be best but if it actually needs to be just make it one command because this I always forget like what I actually need to type and so yeah that's also another important thing like for people who actually want to contribute and who are a bit more technical maybe or less technical but would like to learn just spell it out like just write it out and those are the three important things in the read me actually I would say then third part I would also mention it same thing be welcoming and I like to repeat it because it's super important and I'd like to think that this is one of the big reasons why the next cloud design team is so successful the first thing for example is tying into the whole make or grand file or whatever thing is that you need to remove barriers to entry for example we have this issue or we have this thought forever like oh should we have some CSS preprocessor CSS in this case also regarding design right so we could talk about like I don't know using using composer for PHP which we also do in some parts but this specifically is about the CSS so it also concerns front-end designers and so one thought was yeah do we use SCSS and we were discussing about it in the past already and we're saying ah no we didn't really want to use it because like then people need to compile it and then this one contributor said well there is this PHP library which directly compiles it and next cloud being a PHP app you don't need to do anything else right so actually it's seamless so and I said okay if you can do it like that like if you can if you provide a pull request and if you make it if you rewrite it and if you make it so that it just works then that's okay but otherwise it's a barrier to entry and that's not okay so yeah we're on a good way like this issue is still partly open but most of it actually is moved already and yeah it's it's very cool with the yeah with the additional bonus of not making it any more difficult except you know the SCSS syntax is like I mean it's almost the same as CSS but it's it's very easy very easy to learn it's like not an entirely new technology so you can have some optimizations or you can have some cool tools but you still need to keep in mind that it needs to be simple then second thing what I will also mention I'm very happy that it's successful or that it works is two tags that we use or yeah we use many tags but these I think are one of the most important ones or two of the most important ones for open source projects in general one is the design tag it's just like an umbrella tag for everything regarding interface design and UX design any kind of design we just chose the tag design I actually got it from Mozilla where they use 13 different tags I think like UX feedback so if there's missing feedback or if there's a spinner showing too long then UX wording I think when the language is too technical or not understandable so we just grouped it to one design tag because that makes stuff much simpler and then also the starter issue or junior job label which is just for issues which are very good for people new to the project and as you can filter with two tags so you can combine these tags and you can just see what can I do as a designer new to the project so it's simple stuff like some logo or icon is misaligned or there needs to be some CSS fixes or something is broken in Safari and yeah some of the time of course we need to fix these things but often times we also just leave them open for a bit longer intentionally to get more people involved and this is also perfect for events for like small hackathons for example where for new people to get involved that we have like a list of issues that need to be done so that's very I would recommend that a lot raise their hand again if you don't have a design tag if you don't have a starter issue tag please create them now and add issues to it and open issues if you don't have them yet like if you know of design issues in your project just open them and communicate them openly so yeah I'm very happy that our design team is actually the biggest team in the entire organization and I would say like it's a pretty big team for any open source project and I mean of course some people are more active some people are less active but in general it gives like a great feeling that you can always just mention like Github has this at mention functionality that you can just at Next Cloud Designers review please or what do you think of this and as there are so many aspects like Android app, calendar app desktop and stuff like that it's very cool that people get designers involved some of these designers are in individual teams of the apps for example so yeah thanks to all these folks contributing so first thing last thing is talk about design like make it an actual topic this is similar to the culture of design actually say it in I don't know in tweets or in communication don't just say hey we do a developer meetup just say either we do a contributor meetup or we do a developer designer meetup or we do a contributor meetup developers and designers are very welcome just basic stuff like that for example also publish updates which are specifically about design unfortunately blogging is always something which is neglected of the feeling and we are guilty of that too but yeah sometimes we have design team updates and it's like when we had a discussion at the conference we have a bunch of info how to get involved some feedback what was good and then also we had three good questions that we discussed for example how was the design decided on how to approach a new feature and where is design help needed or how do I ask for it as an app developer so if it's discussed in this way at a developer meeting or developer designer contributor meeting then it's good to notice like how you lack things and how to improve things and coming back to the first point also yeah by the way next start conference will be in Berlin in August and one thing that we say specifically there in the text focus will be on coding design front end work and testing so we actually mention it it's just a small thing right we could just not mention that sentence or we could just say hey every developer interested just come around specifically mention design front end work so people of that area designers will feel welcome and that's often all it takes for designers to contribute so to recap have a culture of design establish a culture of design of simple design preferably to make it user centered be informative explain what your project does in easy terms on your website or in your readme very welcoming to new people in general like this also this doesn't only apply to projects who need designers this applies to any project and then also talk about design make it a topic and raise the profile of design so yeah thank you come contribute and please leave feedback for the talks and you can talk to me here or on twitter or github or whatever we'll see you next time bye bye