This page describes one of the characteristics of the broad range of users for whom we should target our distribution.
In the unlikely event of broken software or user experience, we expect a user to be willing to remedy the problem. However, the steps they take to find a remedy are not those of an experienced contributor. A user isn't expected to automatically understand our software building, testing, and shipping processes. It's our responsibility to put tools in the user's hands that allow them to effectively begin the collaboration process. Prior to beginning that collaboration, we don't expect users to:
- Monitor Fedora communication channels such as IRC and mailing lists
- Understand how to effectively search bug trackers such as Bugzilla
- Know where to find software for testing
- Understand how to select or install testing software
A user can be expected to:
- Perform a search on the Web to find similar problems and resolution
- Send email to ask about a problem
- Consult a web-based forum to seek answers
To encourage collaboration and contribution, we should make tools and information available to users that allow them to accurately describe their problem and relay data as needed. If we provide this information, we can reasonably expect the user to:
- Post information about the issue
- Deliver additional information if asked and given directions
- Iteratively try solutions and give feedback
A user should be afforded broad opportunities to help solve any problem. We can't force users who choose not to participate. Fedora leadership and contributors should consistently seek out ways to expand these opportunities even if not everyone makes use of them.
- The user may not know technical terms, however, to perform an effective search.