diff --git a/metainfo.yaml b/metainfo.yaml
index 7e6e4c42e..1127ccd42 100644
--- a/metainfo.yaml
+++ b/metainfo.yaml
@@ -1,44 +1,45 @@
 name: akonadi
 description: PIM Storage Framework
 maintainer: dvratil
 group: kdepim
+type: solution
 platforms:
     - name: Linux
 public_lib: true
 libraries:
     - qmake: AkonadiCore
       cmake: KF5::AkonadiCore
 cmakename: KF5AkonadiCore
 # TODO: kapidox currently assumes: one product == one metainfo.yaml == one cmake config file
 # listing KF5AkonadiAgentBase, KF5AkonadiAgentBase, KF5AkonadiWidgets, KF5AkonadiXml as separate
 # packages in CMake's worldview needs changing kapidox first -> https://bugs.kde.org/show_bug.cgi?id=410452
 irc: akonadi
 
 group_info:
     fancyname: KDE PIM
     maintainer:
         - mlaurent
         - dvratil
     irc: kontact
     mailinglist: kde-pim
     platforms:
         - Linux
     description: KDE PIM provides set of libraries and application to access and
                  manage personal information like emails, contacts, events, etc.
     logo: docs/kontact.svg
     long_description:
         - KDE PIM provides a set of libraries and applications to access and
           manage personal information like emails, contacts, events, etc.
         - KDE PIM provides a set of libraries to parse and interact with various
           standardized PIM data formats, like RFC822 (KMime), ICAL (KCalendarCore)
           or VCARD (KContacts).
         - The backbone of the entire suite is Akonadi, the PIM storage framework.
           Akonadi provides unified API to access and manage any kind of PIM data
           regardless of the actual storage backend.
         - There are quite a few other libraries that provide PIM-specific widgets
           and utilities and can be useful for application developers who need to
           work with PIM data in their projects.
         - Please note that unless stated otherwise, none of the libraries have
           stable API or ABI as of now. We are trying to keep the changes small and
           we always announce big changes ahead on the mailing lists, but as the
           project evolves we might need to adjust some API here and there.