From Fedora Project Wiki

Revision as of 10:47, 26 November 2009 by Quaid (talk | contribs) (adding a few ideas)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Make a Fedora feature for F13

As a suggestion, consider making a feature page for 'Fedora-tour', and do it soonest to get on the Fedora 13 schedule. Details on how to make a feature page are at Features.

Reasons for doing this soonest:

  • The Features page is commonly the central node for collaborating with other Fedora Project members, such as Marketing and the Docs Project.
  • Being a formal feature for a specific release helps draw attention to the feature, which means additional testing, help, users, and so forth.
  • The feature process is tracked by project manager within the Fedora release schedule. Having this attention and additional rigorous practice helps the feature be ready by a release.

A formal feature is not required for this idea to work. For example, you could skip the feature tracking and just write the application, package it up, then work on convincing the first-boot maintainer to offer 'Fedora-tour', get it linked from the default desktop, etc. Being a feature may make all of that easier, it gets more attention from other sub-projects, and increases the chance that 'Fedora-tour' is discussed in Fedora marketing/press release materials.

--Quaid 10:47, 26 November 2009 (UTC)

Make it easy for Fedora Marketing and Docs and others to contribute updated content

Even though you may not want the content to change very much between releases, it is likely that a small portion will change. If you want the help of, for example, the Fedora Docs and Marketing teams, you want to consider how to make it easy for them to edit and even update the content for the application.

For example, a specifically structured set of wiki pages could be created. When the pages were finished being edited by other Fedora sub-projects, they would be exported to XML or XHTML for pulling in to the application. (Probably best to handle translation files, PO/POT, from within the 'Fedora-tour' application build environment.)

Another idea is to use the CMS platform that Docs/Marketing is preparing to use, with an export to XML or XHTML.

--Quaid 10:47, 26 November 2009 (UTC)