From Fedora Project Wiki

Revision as of 19:09, 21 June 2010 by Dafrito (talk | contribs) (Article prefixes: Some cleanup for readability)

My name is Aaron Faanes. I am a Fedora 13 user, occasional Wiki contributor, and frequent hacker. See my homepage.



You can also find me on IRC. My nickname there is, not surprisingly, dafrito. I frequent many of the various Fedora channels on, such as:

  • #fedora
  • #fedora-qa
  • #fedora-devel
  • #fedora-bugzappers

Notable pages


  • 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 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

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. QA/Updates Testing is an ambiguous, and probably inappropriate name. The implication is that the article provides QA-specific information on updates-testing, or that updates-testing is something that is owned/managed/created by QA.
  • Article prefixes are arbitrary. Fedora Release Criteria discusses the criteria for Fedora releases. Releases discusses releases in a broad sense. ReleaseEngineering/Overview is a very good article that also discusses releases. All are good, but which is definitive? There should be a natural starting point to these articles, with specific content in specifically named articles.
  • Article prefixes create walled gardens. The QA/ prefix appears to "own" many disparate articles. Editors must decide whether their article is related to the QA group enough to place their article under that prefix. If they do, then they likely add more vagueness to the meaning of the QA prefix. If they don't, then visitors may not understand why one article merits a prefix and a related one did not.
  • Article prefixes are frustrating for editors. A contributor must type out the name, and then pipe it for easy readability. For example, to refer to updates-testing, an editor must write "[[QA/Updates Testing|updates-testing]]". Their alternative is not piping and instead having the unsightly QA/Updates Testing.

These problems combine to create a confusing experience for both users and contributors. Visitors do not understand why a prefix is used, and contributors create redundant articles and neglect networking with articles of similar content. This severely hinders usability, since effort and articles are fragmented across arbitrary divisions.


Article prefixes should be deprecated and phased out. In fact, many, many articles that have article prefixes already redirect to unprefixed names, so it seems like their phase-out is happening regardless of whether it is official or not. They should, however, be phased out in an orderly fashion. Redirects should remain to preserve backwards-compatibility, but these redirects should not be directly reachable. The fix for the prefixed article depends on the original reason for the prefix, and the article's content.

Function-related articles

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.
  • HowTo/ or 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
    • Release types
      • Branched
      • Rawhide
    • Release criteria
    • Release process

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.