Bug 152942 - Add a section talking about repositories.
Summary: Add a section talking about repositories.
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora Documentation
Classification: Retired
Component: release-notes
Version: devel
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Karsten Wade
QA Contact: Tammy Fox
URL: http://fedoraproject.org/wiki/FedoraD...
Whiteboard:
Depends On:
Blocks: fc-relnotes-traqr
TreeView+ depends on / blocked
 
Reported: 2005-03-31 03:57 UTC by Phil Schaffner
Modified: 2007-04-18 17:22 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2006-08-20 10:44:10 UTC
Embargoed:


Attachments (Terms of Use)
Information on add-on repositories. (1.89 KB, text/plain)
2005-03-31 03:57 UTC, Phil Schaffner
no flags Details

Description Phil Schaffner 2005-03-31 03:57:33 UTC
Description of problem, bug, incorrect information, or enhancement request:

Add a section with links, about additional repositories.

Version of release notes this bug refers to:

FC4test1

URL of bug/enhancement (change if different):

http://fedoraproject.org/wiki/FedoraDocs_2fRelNotes_2fCore4Test1RelNotes

Comment 1 Phil Schaffner 2005-03-31 03:57:34 UTC
Created attachment 112500 [details]
Information on add-on repositories.

Comment 2 Karsten Wade 2005-04-06 21:06:55 UTC
This is probably not possible as written.  If the repositories contain packages
that have questionable or problematic legal concerns, Fedora cannot be
associated with them.

In the docs project the method we hit upon was to suggest search terms to use on
a favorite search engine.  Again, specific package names should not be mentioned.

I have to look around more and see how this is being handled.  I do have a
fairly clear idea of how Red Hat's legal team wanted it handled, at least in
terms of direct mentions in documentation about where to get e.g. mp3 plug-ins
for XMMS.

Comment 3 Phil Schaffner 2006-08-20 10:44:10 UTC
This has been hanging around long enough - probably obsoleted by the WiKi.


Note You need to log in before you can comment on or make changes to this bug.