Pertains to the wiki, moving from f-docs-l to here.

----- Forwarded message from Toshio Kuratomi a.badger@gmail.com -----

Delivered-To: ianweller@gmail.com Date: Fri, 12 Dec 2008 09:50:22 -0800 From: Toshio Kuratomi a.badger@gmail.com User-Agent: Thunderbird 2.0.0.18 (X11/20081119) To: fedora-docs-list@redhat.com Cc: Tom spot Callaway tcallawa@redhat.com Subject: Packaging Guidelines Organization Precedence: junk Reply-To: For participants of the Documentation Project fedora-docs-list@redhat.com Errors-To: fedora-docs-list-bounces@redhat.com

Howdy folks,

I'm on the Fedora Packaging Committee and we are in desperate need of some docs help.

We manage the Packaging Guidelines which help packagers and reviewers create quality packages for Fedora. Unfortunately, as time has progressed the Guidelines have grown larger and larger in an "organic" fashion. In order to keep the policies managable for people new to Fedora we need to organize them somehow. There's several threads in this:

1) We want something that helps the packager and reviewer find all the Guidelines that apply to the package that they are working on but not to the ones they are not. So we need some sort of navigation based on questions the packager and reviewer can answer about the packages:

General Review Items

What programming languages is this written in?

Is this a library or an application?

2) We want to have a checklist of items to look at with more in-depth information about why a Guideline exists available to those who want to know more.

3) Some of our extra information is more HOWTO-oriented. For instance, the section on Package Naming talks about how to choose a name for a package and how to structure the version strings so that they are always upgradable.

If we could get someone to help us work out this restructuring I'm here to work on these things from the FPC side. Feel free to contact me via this list, email, fedora-packaging-list, or on IRC: abadger1999 (#fedora-devel, #fedora-admin).

-Toshio