The KDE Project designation carries certain principles and requirements:

• Support the KDE Code of Conduct
• There is no mandatory Contributor License Agreement
• Technical requirements
  • The project stays true to established practices common to similar KDE projects unless special considerations force it to deviate
  • Software assets access model
    • Direct write access to the software assets is granted only to KDE contributor accounts
    • Direct write access to the software assets is granted to all KDE contributor accounts
  • Projects that choose not to host their web services on KDE infrastructure need to provide administrative access to the KDE sysadmin team; or, if such access cannot be granted, a regular backup of all the code and data used by the web services should be provided to the KDE sysadmins (except if the service is not an integral part of the project's workflow, community interactions and public image) to ensure continued availability
• Copyrights, trademarks and patents
  • KDE licensing policy should be respected
  • KDE branding guidelines should be respected
  • Trademark continuity – if the authors of the software abandon it or disappear, they agree to transfer the trademark to the next maintainer
  • Patent License - If the code is covered by patents registered by the project itself, those patents must be licensed freely