You can also find me on IRC. My nickname there is, not surprisingly,
dafrito. I frequent many of the various Fedora channels on
irc.freenode.net, such as:
- User:Dafrito/Draft_proventesters_instructions lots of editing. Thanks to User:Adamwill for his draft and feedback.
- Policy for nonresponsive package maintainers needs some love
- Shouldn't Fedora link to an article on Fedora, rather than infrastructure?
- It'd also be cool to have pages for all versions of Fedora, with a template used to describe each.
- "updates-testing" and "Test Updates" are used interchangeably, which I don't believe should be the case. "Test Updates" is a natural name which succinctly describes its purpose. "updates-testing" is the technical name that is used by machines. This dual-naming scheme is familiar to the common and scientific names given to animals, like Canis lupus referring to a wolf, and I think the expectations for which to use for animal names should apply here.
State of the Fedora wiki
Wiki's are excellent for housing lots of content, they are easy for people to edit and use, and they are well-understood. People have learned how Wikipedia.org is organized, and I believe they have come to expect Wikipedia-like behavior from similar looking sites. I humbly believe that the Fedora wiki deviates too often from this expectation, and I think an effort should be made to reorganize it, safely and carefully, to adhere more with common conventions.
I understand that the Fedora Wiki has a different purpose than the Wikipedia itself. Along with housing purely encyclopedic articles, it houses drafts, proposals, how-to's, meeting logs, project homepages, and so on. I think this is an excellent use of the wiki, as it can tolerate a vast amount of information without overloading users. The Fedora wiki should not deviate from user's expectations unless there is a great benefit from the deviation. Things like unusual article names, unconventional article formats, and unexpected uses of features are sadly the norm in the wiki. I believe these inconsistencies cause confusion amongst visitors and discouragement amongst contributors. Let me address a few of the pressing concerns, and some of their potential solutions.
Article prefixes are pseudo-categories that mangle article names, such as the
QA/ in QA/Updates Testing. While prefixes can sometimes appear natural, such as Releases/Rawhide, they are usually unnecessary and distracting. For the most part, articles that have prefixes would be better served by either being in a category, by having a more descriptive name, or not having a prefix whatsoever. Article prefixes are harmful to the Wiki in many ways:
- Article prefixes are ambiguous. Article prefixes are usually too terse to indicate their purpose, or too generic to be useful. For example, the QA prefix does not indicate whether articles relate to the QA project, quality assurance in general, or articles that are merely relevant to QA. In reality, the prefix is used for all three of these purposes.
- Article prefixes miscategorize content. Since prefixes are ambiguous, editors typically are unable to find a single prefix that wholly fits their article. Content gets spread over many different prefixes, and is not predictable or easily accessible. For example, Fedora Release Criteria discusses the criteria for Fedora releases. Releases discusses releases in a broad sense. ReleaseEngineering/Overview also discusses releases, but from a releng point of view. These articles should be merged or reorganized to complement each other, rather than compete.
- Article prefixes are inconvenient. Article prefixes make it difficult for editors to link with existing articles. For a sad example, see F12, Fedora 12, Releases/12
A contributor cannot guess at the name of an article, and A contributor must type out the name, and then pipe it for easy readability. For example, to cleanly refer to updates-testing, an editor must write "
These problems combine to create a confusing experience for users and editors. Contributors miss opportunities to network with existing content, and visitors are left confused and frustrated.
The majority of article prefixes should be deprecated and phased out. Redirects should remain to preserve backwards-compatibility, but the prefixed articles should not be directly reachable. The specific fix for a prefixed article depends on the original reason for the prefix and the article's content.
Since prefixes imply a strong, mutually exclusive separation of purpose, they should be used when articles have special editing rules or unconventional origins. Here's a few examples:
Log/for meeting logs. Since these logs are not intended to be edited and have only one author, they're ideal candidates for a special prefix.
Proposal/for FESCo and other proposals. Proposals usually are much more fluid than regular articles. They typically have a strict format, are "owned" by an individual user, and document a "current" event rather than a concept or component in Fedora. This special nature deserves a prefix of its own.
Tutorial. These describe a process in exact detail. They are linear and highly instructional.
Prefixes are sometimes used to imply a categorical relationship. These should be fixed by removing the prefix and adding the appropriate category. Prefixed articles like the many under the Ambassadors prefix are ideal candidates.
Prefixes sometimes indicate a collection of subtopics. Releases, Fedora Release Criteria, and the content of ReleaseEngineering/Overview are all discussing one major concept: releases. These articles should be merged and renamed accordingly to indicate this topic/subtopic relationship. The following outline is a possibility:
- Release types
- Release criteria
- Release process
- Release types
These subtopics could be sections in the "Release" article, or they could be separate articles referred to by the main article. This choice depends on the amount of content. Once again, the Wikipedia provides good examples for how this separation may be gracefully accomplished.