Below are lists of "Do"s and "Don't"s to reference when forming public communication pieces. These lists provide a place to gather our collected wisdom and customs around public communication.
KDE Software Compilation (SC)
The KDE SC is not a product which we promote as a single entity. It is a part of the release engineering process and marks the epochal events where KDE releases a large set of KDE software at once in a coordinated release event.
In fact, most articles discussing KDE software should not need to mention KDE SC at all but should instead focus on the workspaces, individual applications and application suites and/or the development platform. These represent the actual products which we strive to promote.
When used in an article, the phrase "KDE Software Compilation" should always be spelled out in full at least once in full. "KDE SC" is vague, insiders-jargon without that.
Consult the Branding Information for more details on how KDE SC fits into the bigger picture.
Do not use the phrase "the KDE e.V.", it is instead just "KDE e.V.". Example:
- The developer sprint was sponsored by the KDE e.V.
- The developer sprint was sponsored by KDE e.V.
When referring to the membership or other bodies, the article "the" may be used. Example:
- The KDE e.V. Board of Directors met for three days in Berlin this week.
- When it came time for a vote on the matter, the KDE e.V. membership gathered to make their collective voice heard.
Always provide a link to ev.kde.org when mentioning KDE e.V.
KDE has a wide range of social media accounts that need regular and frequent updates. Our policy is to always discuss social media posts beforehand with other members of the Promo group in the Promo IRC channel, on the Telegram group, or on the Promo mailing list, or on all three. We never post off-the-cuff messages.
To ensure your post is appropriate for our posting on KDE's social media accounts, read and apply the following guidelines to your drafts:
Upholding our Values
- First and foremost: Posts must be in line with our vision, mission, Code of Conduct, and goals. Read about all of them first before even considering posting.
- Don't encourage people to do things that are against our values.
- Cooperate with fellow organizations and support ideas that align with our values. (patrons, partners, advisory board, affiliates). Celebrate their successes.
- Think about whether a comment is worth replying to. Avoid obvious trolls. Respond to the content, not the tone.
- Do not bash people or their projects. Other FLOSS projects are not competitors.
- Own mistakes and put them into context.
The KDE promo account holders have responsibility for posting prompt, accurate, helpful and relevant content to KDE Dot News and various social media platforms. It's a self-regulating group which welcomes KDE community members. As with other restricted accounts such as Git or web or release team, access is controlled to ensure quality. Here's how we let people in:
- You must be familiar and able to communicate with the many teams in KDE
- You must want to play an active part in promoting KDE and its software
- You have a track record of 6 months contributing to KDE promo. Come and hang out in our channel and help craft our stories. This means:
- You must attend at least 1/2 the bi-weekly meetings (about 1 hour a month)
- You must take on and resolve to completion at least 1 promo task every 6 months
- You must have shown an ability to follow good practice and [follow our rules](https://community.kde.org/Promo/Guidance/DosDonts#Social_Media)
- You must have shown an ability to create high quality writing or review others work to a high standard
- You must scrupulously follow and have followed in the past [KDE's CoC](https://www.kde.org/code-of-conduct/)
- Must not disparage, offend, intend to offend, or badmouth any group, company, organisation, or individual within or without KDE from KDE's official accounts
- If you have had access to KDE's social media accounts before, you must have a clean slate with regard to the above to be eligible
- You must be able to work effectively with the rest of the promo team. This includes ALWAYS submitting your posts for revision and taking on board suggestions before posting
- Who has access will be reviewed every 6 months to ensure holders are still active
- If you post inappropriate content* your access will be removed. No second chances. No appeals.
- Account holders are listed at https://community.kde.org/Promo/People/social_media
Sysadmin has admin access to all accounts to ensure access can continue even when people move on.
- Redirect support requests to forums, bug reports to bugzilla.
- Wherever appropriate, encourage people to join the community and contribute. Show how people are contributing and make people know they can contribute easily.
Posting with Style
- For better impact, always include a colorful, busy image that's up to date.
- Always try to include a Call to Action, even if it is just "Click here to read more...".
- Try not to use "if" and "please" in a Call to Action.
"If you would like to help us, please donate here."
"You can help us by donating here."
- Use the generic "you"/"we" and avoid passives.
"The software is installed by using a Flatpak."
"You use Flatpak to install the software."
"Use Flatpak to install the software."
- Personalise, remind readers there are humans behind each project.
- Name the people and projects you're talking about and link to them.
"There is a new version of Krita out."
"The developers working on the @Krita_Painting application have just released a new version."
- "Exclamation marks draw attention to themselves" (in detriment of the message). Use them sparingly. If you think ending a tweet with a full stop is curt (.), don't sweat it -- most should end with a link anyway.
- Other things you should use sparingly: the word "awesome" and emojis.
- Make it about the reader:
"Kdenlive is awesome!!!!!!"
"Make your best movies with Kdenlive."
- Include the handle's of the projects you are talking about:
"Krita releases version 4.1"
"Developers at @Krita_Painting have released version 4.1"
- Be explicit -- say what is new in the release or what the users should expect. Don't assume the reader knows about what into the new version of the software or expect them to click the link and read through the full release announcements (most won't). You have at least 280 characters. Use them to explain why you are telling them this.