GNOME Community Guide

The purpose of this guide is to provide all GNOME community members with a foundational understanding on how to approach interactions within the community.

This guide is separated into two major segments: one for GNOME developers and maintainers, and one for non-developer community members. While each section is written for a specific audience, all members are encouraged to read the entire guide.

For Everyone

Brief: Paraphrase Allan's "The GNOME Way"?

For Developers

Brief: Summarize "what it feels like to be a user".

• While developers see requests "all the time", sometimes for a user, this is their first time talking to a developer. The user could be nervous (it's kind of like talking to a celebrity), so be kind and respectful. If you're drained, say so, and bow out of the conversation.
• Always approach a conversation with an open mind. You never know when a user might have a clever solution that you never considered before.
• Be open to new ideas. Give the user time to fully state their case, and give the idea a fair chance before "shooting it down".
• Give constructive feedback, and be able to cogently and politely explain why an idea is not good. Have reference links to back up your points (maybe links to GNOME HIG sections, or parts of this document or The GNOME Way).

• Don't respond to an insult with more insults.

For Users

Brief: Summarize "what it feels like to be a developer". This should include some points Allan brings up in The GNOME Way. Additionally:

• Developers consider the ecosystem-wide impact a change could have.

• Developers love to discuss the pros and cons of a change; "it's how we debate".

• Always approach a conversation with an open mind.
• Be open to criticism and feedback, and be able to cogently state your case.

• Don't respond to an insult with more insults.

• Don't take criticism personally; "developers are not PR people"