 So I'm Paul, I'm from the promo team and I'm going to talk about why sometimes you don't get all the love you deserve for your project. This is kind of a trailer to what I will be talking about on Monday at quarter past 12, where I'll do a workshop explaining where we will see how to improve the text on your website. Here's the thing, very often, 90% of the time, when I go to a website of one of your projects, the first thing I see is a text that tells me what that project is. This is a top down way of looking at things. I'll tell you what it is and then we may work our way down to how it is useful to you. But there is a problem with that. Very often, the people who come to your websites don't have the knowledge to understand what that thing is. So I suggest that you do it the other way round, that we have a bottom up explanation. So you start by saying how it is useful to the reader. Let me give you an example with Kirigami. Anybody is the person who wrote that here? No? Good for him or her or whatever. I was going to suggest that maybe he should leave. This is another thing. When you come on Monday, you're going to have to check your egos at the door because we're going to destroy everything you have written. Then build it up again. No problem. Let's have a look at this one. We have here Kirigami is a lightweight user interface framework for mobile and convergent applications. I think that everybody here probably understands that. But everybody who is not here doesn't. I can guarantee that. You think it's intelligible, but it's not. You are reading it through the filter of your knowledge, right? Let me give you an example of, maybe some of you will get what I'm going to say, but I'm going to give you an example from another website, from another project that is not a KDE, but it's also gobbledygook. The XYZ is the first notarized cryptocurrency P2P exchange for server blockchain entirely owned by its clients. Okay, who can tell me what is it? No, it's not Bitcoin. You're cheating. You have blockchain and you said Bitcoin. No? It's not even a cryptocurrency. It is something else entirely, right? Now, let's break, but let's get back to this, right? Let's break that down. Let's see how it is really gobbledygook. So let's take that first sentence, right? KDE is an acronym. Lightweight is a buzzword. User interface is jargon and a buzzword. Framework is jargon. Mobile is jargon. Convergent is jargon and a buzzword. Application is jargon. So you have eight words. If we take out is for and and, which I think everybody can understand. We have eight words. Seven are jargon or buzzwords, and one is the name of the project. So, you know, what can we do with this? This is something that nobody outside this room can understand. You are writing for your peers. You're writing for your colleagues. You're not writing for the world. Okay. And this has, okay, we've, oh, we don't. It's back. It's back. It's back. So there are two problems with that first sentence. One is that it is full of words that only you understand or only you understand in that context. What I mean is that, sure, application is a word that you can use in everyday language, but it doesn't mean outside this room what it means inside this room. Okay. That's why it's jargon. And the rest are just terrible. I look at that and I want to cry. Yes. And then we get on to the second sentence, which is better, much better, because it explains what it does. What it does for the user. It says, allows QT developers to easily create applications that run on most major mobile and desktop platforms without modification. It is much better. That should probably be the first sentence, right? Because it says what it does. Then we can get to what it is, right? The problem with something like that is that in the first sentence you're going to use most, you're going to lose most of the readers. Now, you may think, but why should I care? Because this is only interesting for developers, right? True or not? Yes. Why do you care? Exactly. Why? Why should you care? Well, it's very simple. You don't know who is going to be interested in Keregami. For example, if somebody came along and said, okay, I have money to spend on a free software project. Keregami sounds interesting, goes here, doesn't understand it and leaves without leaving his money, right? That's one. The other thing is, you know, not everybody is an already hardened developer like you a lot, right? Some of them are new and they don't have the vocabulary, right? And you want to introduce them to KD and its technologies. So you have to write for everybody. You have to write for the world. You don't know who you're going to need to understand this, right? I suggest, for example, an alternative to this. I haven't written it down for a slide or anything like this. But if I were to write that, I mean, I do this all the time. I do it for KDE and I do it for companies and things like that. They send me their press releases and it's always tech companies I work for. They send me their press releases. They send me their white papers, etc. And my job is to convert it into something that everybody can understand, a journalist, a boss, right? Or any reader, okay? So after dedicating a long five minutes to this, I thought that maybe this would be a good alternative, right? I'm trying to keep all the meaning here, right? So bear with me. If you want to create apps that work the same on mobile phones and desktop computers and you don't want to have to program everything twice or three times, KDE Gavme gives you all the tools you need and that's it. Okay, what would the problems be with that? Who objects to that? Say, who objects to that text, that one? Yes, buzzword? What buzzwords are they in here? If you want to create apps, apps is a buzzword, maybe. Okay, that work the same on mobile phones. Mobile phones is a buzzword, not really. And desktop computers, buzzword, not really. And you don't want to have to program everything twice, no buzzwords there, or three times? One second, one second, one second. Okay, first of all, first of all, as I said, written in five minutes. It's not necessarily the final draft. It sounds like a sales speech, but that is exactly what your website is. It's a sales mechanism. That is what you want to do. You want people to be interested in your... Because otherwise, why bother? Yes. I didn't say it was awesome. I think KDE Gavme is awesome, by the way, if anybody here is developers of KDE Gavme, I do think it is awesome. I didn't say it was awesome. I just said what it was. Yeah, I have a... Oh, sorry, sorry. Sorry, man. Here you go. I do have it in Haiku form also. You want to hear it? Develop for phones for desktop computers to KDE Gavme rules. I think that summarizes in what KDE Gavme is quite nicely. Okay, it's a bit obscure, but I wouldn't probably use it. But there are many ways of saying what you want to say. Okay, mine may sound very salesmanship, but you know why it sounds like that to you? Because you fucking... You can understand it, because it's for everybody. It sounds like some guy on television selling you detergent. Because he has to go to the lowest denominator, but you too, because that's why you have a website. Tell me. Yeah, but it's public, but wait one second. Yeah, one second, one second, but you put KDE Gavme, KDE in Google, that's the first thing that comes up. So the problem is that it's the first result on Google. So people who are interested in this, I mean, yesterday I wrote an article for a general tech blog. It's for people that like things like iPhones and PS3s and stuff like that. But I said, okay, I'm going to stick KDE Gavme in there, right? And I did, okay, and I explained it like I just said. This is this thing that computer programmers can use to program for all sorts of platforms, right? And they don't have to write things twice or three times, etc. Basically that was it. And I said, and with this, the KDE community is going to take over the world, the mobile phone world, okay? Because, you know, you have to finish with something like that. The thing is that people would read that and go click on KDE Gavme and then be, I mean, don't you guys want people to like your, do you want to put them off? Really? Is that the end game? Say, I don't know. Absolutely. Yes, yes. Okay. Yes, but yes and no, yes and no. I cheated a bit. I cheated a bit. I cheated a bit by picking KDE Gavme. I cheated, obviously. But that said, that's it. There's nothing wrong in this webpage and this, even in the top it says tech base. What is wrong is the fact that we don't have the counterpart, the commercial counterpart that you want. So this actually, the fault is that you don't have the other part. But this is not wrong. This is for developers. Yeah, that's the problem. The problem is that this is the only thing. This is the only thing, right? This is, so as I say, if we, if, if there was an alternative to this, if there was another first result in Google and this was the second result, okay, no problem. But this is the first result. And below that, there's nothing else. Okay. Yes. Sorry. Yes. Fine. But so the state of the discussion in the room right now is that his version is less well targeted as developers. And that's been accepted as a factor. I totally disagree with that because this text that's on the wiki right now doesn't speak to anything that I would actually do as a developer. Like his version says you write it once and it runs across devices, right? Which is how I would actually make an application using Kirigami. So his version tells me what my process of using Kirigami as a developer would be. Whereas the version on the wiki page, the only word that hints at this right at once and it runs across devices is convergent. And convergent is not how I develop. Like I'm not a convergent developer. The problem is. It's not a verb, right? Yeah. Sorry. I'm sorry. Go ahead. Convergence is a word that became so like popular two, three years ago tops, right? Convergence outside this room also doesn't mean what it means in this room. Okay. It doesn't even mean the same in develop in communities that develop for things that are not mobile. Okay. So, you know, I'll tell you what, what, what is happening here. My job here is to get the most, the biggest number of quality members into your community as possible. Right. And one way that I want to achieve this is by having you make your message more accessible to a larger audience. Is that, does that make sense? Does that make sense to you? So, yes? Right. So, the problem I have with these things is that, and sorry, I don't know your name, but Dennis. Dennis said, I cheated because I picked Karygami, but that doesn't only happen in Karygami. I have tons of examples that we will see on Monday if you don't bring your own where you will see that end user applications are the explanation on their website. Their first paragraph is chock-a-block with jargon, and it doesn't say what it does. This thing, yeah? I mean, if now most of you go home and look at your, your websites and start thinking of, oh, mission accomplished for me? Yes. I can't hear you very well, sorry. Sorry. Developers? This is what you get, yeah. But there are, there are, there are tricks, which, which is what, sorry. Yeah, sure. Developers writing documentation. Writing things. Yeah, okay. I agree that the, that the wording is very, is boring, basically. So, it could be a bit lighter, like a lighter style. On the other hand, it's probably due to the fact that whoever wrote this was trying to start a page for developers and so on. So, yeah, I see the problem. The problem is that it's not even, it's not even more precise than what I said. Yeah, okay. I agree. Your part, your first expression was, was first, it was actually better than what was written there. On the other hand, this one is a wiki, so. Yeah. The thing is, the thing is that, that you say developers writing documentation. Well, I'm going to tell you something. You were not born this way, okay? You learned this shit, right? And you learned this shit by reading too much documentation. You like, you're like Don Quixote, right? Who went mad because he read too many books about knights and cavalry and shit like that. You guys have been contaminated. The thing is also that the version on the wiki page, whoever wrote the text didn't do it with the mission on mind of respecting developers. They tried to pretend to be PR people and picked words that they thought said a lot and said very little like lightweight and conversion. Like it's trying to emulate something without really knowing what you're doing. Yeah. And that usually doesn't work. So the point that this version is somehow more respectful of the developer audience is not true at all to me. There is one interesting, sorry. Yeah. Just so one thing. There is an interesting point. When I write press releases for companies, you know, there is nothing that annoys me more. I mean, I get my red pen out and there's nothing that annoys me more than when they start with, we are excited to announce. We are market leaders and blah, blah, blah, blah, blah. All that goes out. Then I send my version back and they say, oh, but this is not like a press release at all. I mean, we go to, you go to press release sent out by IBM and by, one second, we're having an interesting conversation here. All right. We're getting kicked out. Sure. So please stop. I see you all are having a lot of fun with this, but the bus leaves in exactly 15 minutes. So we should probably try to wrap this up. So you can attack me in the, in the passage or whatever. Thank you.