Difference between revisions of "Promo's Long Term Goals"

Jump to: navigation, search
m (Remove duplicate word.)
(Remove superfluous mention of "KDE", specify "Others" as user adoption/usage share, for the sake of clarity)
Line 25: Line 25:
 
* '''Some popular apps are not associated with our brand''', despite being fostered within our community.
 
* '''Some popular apps are not associated with our brand''', despite being fostered within our community.
  
== Others ==
+
== User adoption/usage share ==
  
 
* '''Domestic usage is probably lower than 1%''': if we take the figures that say that users of the Linux desktop make up little more than 2% of the market, and taking into account that by most measures, Gnome is the most pervasive of the Linux desktops, it stands to reason that KDE's Plasma desktop is used by less than 1% of the desktop users worldwide.
 
* '''Domestic usage is probably lower than 1%''': if we take the figures that say that users of the Linux desktop make up little more than 2% of the market, and taking into account that by most measures, Gnome is the most pervasive of the Linux desktops, it stands to reason that KDE's Plasma desktop is used by less than 1% of the desktop users worldwide.
Line 33: Line 33:
 
= Long Term Goals =
 
= Long Term Goals =
  
== For the KDE technology ==
+
== For the technology ==
  
 
The main aim in this section is to increase project sustainability be adding more developers and acquiring better and more stable financing.  One way of doing this would be to increase the usage of the KDE Frameworks, Plasma, and Applications in general in companies.
 
The main aim in this section is to increase project sustainability be adding more developers and acquiring better and more stable financing.  One way of doing this would be to increase the usage of the KDE Frameworks, Plasma, and Applications in general in companies.
Line 43: Line 43:
 
* '''Help establish durable and stable working relationships with large, long-standing, FLOSS-friendly organisations, such as Mozilla, Wikipedia, Apache, Blender, the Document Foundation, etc. Over the next 5 years we want to help increase by ten the number of organisations that we work closely with and, preferably have them join the advisory board.''' This will help us have an even better integration of popular software (such as Firefox, Blender 3D, LibreOffice, etc.) with Plasma and KDE Applications, and increment the number of developers supporting Plasma and KDE-related applications and technologies outside our community. This will not only help increase the number of contributors to our project, but also offer a better and more coherent experience to our users. We will carry out this goal by leveraging our connections, talking directly to people we already know within each project, inviting them to joint activities (events and sprints), inviting them to become part of the Advisory Board, and in general listening and solving their concerns they have with regard to working upstream with us.
 
* '''Help establish durable and stable working relationships with large, long-standing, FLOSS-friendly organisations, such as Mozilla, Wikipedia, Apache, Blender, the Document Foundation, etc. Over the next 5 years we want to help increase by ten the number of organisations that we work closely with and, preferably have them join the advisory board.''' This will help us have an even better integration of popular software (such as Firefox, Blender 3D, LibreOffice, etc.) with Plasma and KDE Applications, and increment the number of developers supporting Plasma and KDE-related applications and technologies outside our community. This will not only help increase the number of contributors to our project, but also offer a better and more coherent experience to our users. We will carry out this goal by leveraging our connections, talking directly to people we already know within each project, inviting them to joint activities (events and sprints), inviting them to become part of the Advisory Board, and in general listening and solving their concerns they have with regard to working upstream with us.
  
== For the KDE community ==
+
== For the community ==
  
 
* '''Help increase diversity''': Over the next 5 years help promote diversity and collaborate in attracting contributors in order to get close to having the same proportion of men, women, and other genders as there are in the real world. Likewise promote KDE as a community all over the world to contribute to recruiting contributors so as to achieve a balanced representation of the largest number of ethnicities and nationalities as possible among contributors. At the moment, the community is composed mainly by white male Europeans. The goal is to add 5 percentile of minority contributors to the community every year over the next 5 years, without decreasing the number of contributors KDE already has.  We can do this by carrying out actions that target under-represented genders, ethnicities and people with disabilities, so that we can tap undiscovered talent, receive input and help from a larger slice of the population, and better adapt KDE's software to the needs of wider selection of the population. We can take a page from Wikimedia's playbook on how to encourage under-represented groups to participate in KDE's community. Implement and enforce a strict CoC both for the community and each event against discrimination and harassment. Also, move main event (Akademy) away from Europe and encourage sprints and events in other places, like Asia, South America and Africa, as well as activities devise activities which will appeal to minorities.
 
* '''Help increase diversity''': Over the next 5 years help promote diversity and collaborate in attracting contributors in order to get close to having the same proportion of men, women, and other genders as there are in the real world. Likewise promote KDE as a community all over the world to contribute to recruiting contributors so as to achieve a balanced representation of the largest number of ethnicities and nationalities as possible among contributors. At the moment, the community is composed mainly by white male Europeans. The goal is to add 5 percentile of minority contributors to the community every year over the next 5 years, without decreasing the number of contributors KDE already has.  We can do this by carrying out actions that target under-represented genders, ethnicities and people with disabilities, so that we can tap undiscovered talent, receive input and help from a larger slice of the population, and better adapt KDE's software to the needs of wider selection of the population. We can take a page from Wikimedia's playbook on how to encourage under-represented groups to participate in KDE's community. Implement and enforce a strict CoC both for the community and each event against discrimination and harassment. Also, move main event (Akademy) away from Europe and encourage sprints and events in other places, like Asia, South America and Africa, as well as activities devise activities which will appeal to minorities.
Line 53: Line 53:
 
* '''Contribute to acquiring more sponsors by helping increase at least by 25% every year the amount contributed by sponsors to the community over the next 5 years.''' A bigger community means more expenses. We would need to guarantee that KDE remains operational by, among other things attracting stable sponsorships. Also, by increasing the number of sponsors, KDE does not have a a two big dependence on any one sponsor in particular, which helps the community maintain its independence. We would need to determine what reasonable increment of sponsors we want to achieve. Apart from working with companies as mentioned in the *For Technology* section above, we can also jump start interest in sponsoring KDE projects by attending events which management from corporations also attend. We want to deliver talks to CTOs and have booths to showcase KDE's solutions. In part, this strategy is already being implemented.
 
* '''Contribute to acquiring more sponsors by helping increase at least by 25% every year the amount contributed by sponsors to the community over the next 5 years.''' A bigger community means more expenses. We would need to guarantee that KDE remains operational by, among other things attracting stable sponsorships. Also, by increasing the number of sponsors, KDE does not have a a two big dependence on any one sponsor in particular, which helps the community maintain its independence. We would need to determine what reasonable increment of sponsors we want to achieve. Apart from working with companies as mentioned in the *For Technology* section above, we can also jump start interest in sponsoring KDE projects by attending events which management from corporations also attend. We want to deliver talks to CTOs and have booths to showcase KDE's solutions. In part, this strategy is already being implemented.
  
== For the KDE brand ==
+
== For the brand ==
  
 
We want to increase brand awareness across the board.
 
We want to increase brand awareness across the board.
Line 63: Line 63:
 
* '''Help reinforce KDE's brand through popular applications.''' Over the next 5 years, convince all KDE's standalone applications (i.e. applications that can be run outside of Plasma, even on different platforms, such as Windows, Android, or macOS and that have their own website) to include the "Made by KDE" branding badge into their sites and on splash screens. We will want to ask application project leaders to push the KDE brand front and centre to increase brand awareness in users. We are in the stages of discussing this at [https://phabricator.kde.org/T9122 T9122].
 
* '''Help reinforce KDE's brand through popular applications.''' Over the next 5 years, convince all KDE's standalone applications (i.e. applications that can be run outside of Plasma, even on different platforms, such as Windows, Android, or macOS and that have their own website) to include the "Made by KDE" branding badge into their sites and on splash screens. We will want to ask application project leaders to push the KDE brand front and centre to increase brand awareness in users. We are in the stages of discussing this at [https://phabricator.kde.org/T9122 T9122].
  
== For Others ==
+
== For increasing user adoption/usage share ==
  
 
Increase number of end-users by
 
Increase number of end-users by

Revision as of 13:25, 8 March 2019

Current Situation

This is how KDE as a project and brand is currently perceived in the IT market. This information is gleaned from a lot of anecdotal data, so please take everything with a grain of salt.

Technology

Despite being quite mature in many aspects, KDE's frameworks and libraries do not seem to be used or, indeed, known much outside of the KDE community. We have had several anecdotal experiences in which organisations and companies that we thought would've known better were completely ignorant of what KDE had to offer.

  • Frameworks are surprisingly underused outside the KDE community. Even many FLOSS projects are ignorant of what we do.
  • The Plasma desktop has a low penetration, but is generally regarded as a high quality product. Very high ratio of developers to users.
  • Many Applications are well known (e.g. Krita, Kdenlive), but users do not associate them with KDE (see #Brand later). Others - while excellent - dwell in total obscurity.

Community

According to many accounts, the community is not what it used to be. This is true about activism in the FLOSS world in general; people grow older, find time-absorbing jobs, have families and have less time to give away. Also FLOSS is not perceived as an exciting, pioneering, revolutionary thing like it used to be, so a younger generation is not as interested.

  • The KDE community is shrinking. According to testimonies of old-timers and numbers of attendees at events, there is a decline of active community members from a peak that was reached in 2013. Despite a peak in 2010, and sharp drop off immediately after, there has not been radical shrinkage, but there has been a slow gradual one.
  • The community is largely homogeneous with regard to gender, race, class and geographical extraction, being made up mainly by white male middle class European engineers.
  • There is a large ratio of developers to users. This comes about in part from the philosophy of "scratch your own itch" which is pervasive in FLOSS development: Developers are often the consumers of their own development. In KDE, however, this is a bit more diluted and can attributed to the fact that KDE technologies are not that well-known outside our community.

Brand

  • The KDE brand is recognised within the FLOSS community, even though many of the products are not. That said, KDE is still being used as a synonym of "Plasma desktop" by most FLOSS community members not associated with KDE.
  • Anecdotal (but not unique) evidence collected at external conferences seems to indicate that the KDE brand is not known outside the FLOSS community.
  • Some popular apps are not associated with our brand, despite being fostered within our community.

User adoption/usage share

  • Domestic usage is probably lower than 1%: if we take the figures that say that users of the Linux desktop make up little more than 2% of the market, and taking into account that by most measures, Gnome is the most pervasive of the Linux desktops, it stands to reason that KDE's Plasma desktop is used by less than 1% of the desktop users worldwide.
  • Professional usages is probably also very low: "Professional" as in use in offices, hospitals, schools, public administrations, etc. If we have learnt anything from things like Wannacry and other virus crisis is that the most public institutions and big companies use proprietary tools that are also outdated.
  • Progress in getting KDE tech on devices: That said, we have made progress in getting KDE software (especially Plasma) preinstalled onto devices. The KDE Slimbook I and II, the Pinebook (although not as a default) and our ongoing work to get Plasma Mobile onto the Librem 5 and other devices, are examples of the headway we are making.

Long Term Goals

For the technology

The main aim in this section is to increase project sustainability be adding more developers and acquiring better and more stable financing. One way of doing this would be to increase the usage of the KDE Frameworks, Plasma, and Applications in general in companies.

  • Contribute to help increase by 5 the number of software companies that use KDE frameworks as the basis for their UI-based applications over the next 5 years. Among these companies there must be at least one multinational global player, like Samsung, Lenovo, LG, etc. The ultimate goal is to create a sustainable businesses ecosystem in which it makes sense for companies to develop, sell and maintain KDE-based software or develop software fo their own products, both for users and for other businesses. We can do this by (1) visiting events and engaging attending representatives of target companies, (2) pushing news about developments of KDE frameworks on B2B social media networks and to tech-business press; and (3) increasing the userbase and the use of KDE software in non-techie organisations, which will lead to and increase in interest on behalf of third party companies to ramp up the use of our frameworks to develop their own software.
  • Help establish durable and stable working relationships relationships with Linux/BSD/etc. distribution maintainers. Over the next 5 years increase by ten the number of distros that offer "KDE" as the default environment for end users. This will help us avoid distributions dropping our software, help make thinks like Plasma become the default desktop for more distributions, increment the number of maintainers/developers, and keep the packages distributed with distros more up to date. All of the above will help increase the number of users and contributors to our project. We will carry out this goal by leveraging out connections, talking directly to people we already know within each project and listening and solving their concerns they have with regard to working upstream with us.
  • Help establish durable and stable working relationships with large, long-standing, FLOSS-friendly organisations, such as Mozilla, Wikipedia, Apache, Blender, the Document Foundation, etc. Over the next 5 years we want to help increase by ten the number of organisations that we work closely with and, preferably have them join the advisory board. This will help us have an even better integration of popular software (such as Firefox, Blender 3D, LibreOffice, etc.) with Plasma and KDE Applications, and increment the number of developers supporting Plasma and KDE-related applications and technologies outside our community. This will not only help increase the number of contributors to our project, but also offer a better and more coherent experience to our users. We will carry out this goal by leveraging our connections, talking directly to people we already know within each project, inviting them to joint activities (events and sprints), inviting them to become part of the Advisory Board, and in general listening and solving their concerns they have with regard to working upstream with us.

For the community

  • Help increase diversity: Over the next 5 years help promote diversity and collaborate in attracting contributors in order to get close to having the same proportion of men, women, and other genders as there are in the real world. Likewise promote KDE as a community all over the world to contribute to recruiting contributors so as to achieve a balanced representation of the largest number of ethnicities and nationalities as possible among contributors. At the moment, the community is composed mainly by white male Europeans. The goal is to add 5 percentile of minority contributors to the community every year over the next 5 years, without decreasing the number of contributors KDE already has. We can do this by carrying out actions that target under-represented genders, ethnicities and people with disabilities, so that we can tap undiscovered talent, receive input and help from a larger slice of the population, and better adapt KDE's software to the needs of wider selection of the population. We can take a page from Wikimedia's playbook on how to encourage under-represented groups to participate in KDE's community. Implement and enforce a strict CoC both for the community and each event against discrimination and harassment. Also, move main event (Akademy) away from Europe and encourage sprints and events in other places, like Asia, South America and Africa, as well as activities devise activities which will appeal to minorities.
  • Contribute to achieving a sustained growth of the number contributors, helping increase by 25% the number of active contributors and volunteers every year over the next 5 years. To stop the community from shrinking further and, if possible, reverse that trend, we can again use the effort to push for diversity. While activism of FLOSS in the Europe and North America has decreased, in developing countries FLOSS is very much a nascent movement, akin to what it was like in Europe and the US in the early 2000s. This is a demographic KDE can cater to and, in the process, bring new blood with new perspectives into the community. We would achieve this be ramping up activities in these regions, attending and organising events and recruiting students for SoK, GSoC and so on. This will (hopefully) have a snowball effect and students will in turn become mentors and help grow the communities organically.
  • Help attract existing FLOSS software projects to KDE and incorporate their members into our community. We would want to increase the number of projects by 5 every year over the next 5 year. This would help KDE increase its portfolio and app catalogue, making our platform more attractive to users and contributors (= a larger variety of projects to chose from). The community would grow with members of already active projects, thus increasing our reach with every project added. One would expect it would make KDE more attractive to a wider variety of sponsors. The projects that joined us would be able to increase number of contributors (developers, artists, translators) working on their product, increasing the bus factor. They would be able to take advantage of KDE's infrastructure and services (like Promo), while at the same time increasing the probability of obtaining sponsorship and funding. Finally they would be working with like-minded colleagues. We will approach the project leaders and to ensure we can accommodate the project, we will work with the onboarding project members so we are ready to accept mature projects into the fold.
  • Contribute to acquiring more sponsors by helping increase at least by 25% every year the amount contributed by sponsors to the community over the next 5 years. A bigger community means more expenses. We would need to guarantee that KDE remains operational by, among other things attracting stable sponsorships. Also, by increasing the number of sponsors, KDE does not have a a two big dependence on any one sponsor in particular, which helps the community maintain its independence. We would need to determine what reasonable increment of sponsors we want to achieve. Apart from working with companies as mentioned in the *For Technology* section above, we can also jump start interest in sponsoring KDE projects by attending events which management from corporations also attend. We want to deliver talks to CTOs and have booths to showcase KDE's solutions. In part, this strategy is already being implemented.

For the brand

We want to increase brand awareness across the board.

  • Contribute to making KDE a household name** and we can start be trying to **make KDE, Plasma and some of KDE's more popular applications recognisable for at least 5% of the population over the next 5 years. Tech-literate users should be able to identify KDE applications, Plasma, Plasma Mobile the same way the can differentiate Android, iOS, Windows and macOS. Companies developing software with GUIs should consider KDE technologies, like Kirigami for their products. Users should become more familiar with some of the more mainstreamable (?) applications (Krita, GCompris, Kdenlive, etc.). It is unlikely that KDE will become recognised on its software merits alone. There are several ways this can be achieved: we can use standard advertising, ad stunts, and broadcasting to mainstream media (exploiting contacts in publications); attending events beyond the sphere of FLOSS and with attendees that are not only developers; engaging online personalities and influencers so they review and test our products.
  • Help KDE become recognised as a provider of quality software and improve consumers' and businesses' awareness and positive perception of KDE products. We would need to make sure QA is carried out on all projects associated with our brand and they abide by KDE's core vision. Carry out surveys every year to monitor progress. Each yearly survey must show significant improvements (?) in the perception of KDE's products over the one carried out the year before. We also aim to achieve larger proportion of positive reviews and articles on bloggers, vloggers and podcasters sites, as well as in professional publications.
  • Help reinforce KDE's brand through popular applications. Over the next 5 years, convince all KDE's standalone applications (i.e. applications that can be run outside of Plasma, even on different platforms, such as Windows, Android, or macOS and that have their own website) to include the "Made by KDE" branding badge into their sites and on splash screens. We will want to ask application project leaders to push the KDE brand front and centre to increase brand awareness in users. We are in the stages of discussing this at T9122.

For increasing user adoption/usage share

Increase number of end-users by

  • Helping take over niches, like education, science & research, art, etc. Promo's aim is to contribute to turning KDE applications into the most used applications within at least two niches within the next 5 years. For example, making GCompris the most used application for by primary teachers for education, or Krita the most used painting program for art students. We plan to do this by seeking out events, associations or organisations that cater to each niche and working with them on training and awareness programs. Collecting feedback so developers can adapt their applications to specific real world (TM) needs.
  • Helping get manufacturers preinstall KDE software on devices by adding at least two new hardware manufacturers a year to the list of hardware vendors consistently pre-installing KDE-based technologies onto their devices. We want to establish ties with manufacturers and help them and support them to get Plasma, Plasma Mobile, and the rest of KDE's ecosystem working on their devices. An even longer term aim would be to have major device manufacturers (HP, Asus, Dell, Acer, LG, Samsung...) ship devices with Plasma and KDE applications pre-installed, whether laptops, tablets, phones or smart appliances (TVs, fridges, etc.). Again, the way to achieve this is engaging manufacturers at events and via contacts we already have in our network.
  • Helping increase the presence of KDE software in companies by marketing at events and directly to businesses that could benefit from adopting KDE software and need technical corporate backing. Promo aims to contribute to increasing the number of companies using KDE environments, applications and technologies by two every year over the next five years. This may be achieved again by a combination of leveraging our network, cold-door calling, engaging decision-makers at events, and so on.
  • Contributing to the increment of the number of domestic users, to be precise, Promo intends to help increase the number of desktop end users by 2% over the next 5 years. This may be achieved by striking deals with hardware providers to supply OEM versions of KDE-based distributions, increasing guerrilla and conventional promotion, and by working with online publications, bloggers and influencers.

Content is available under Creative Commons License SA 4.0 unless otherwise noted.