Bug 58531 - Need clear link to T's and C's
Need clear link to T's and C's
Product: Red Hat Network
Classification: Red Hat
Component: RHN/Web Site (Show other bugs)
RHN Stable
All Linux
medium Severity medium
: ---
: ---
Assigned To: Greg DeKoenigsberg
Jay Turner
Depends On:
Blocks: 64484
  Show dependency treegraph
Reported: 2002-01-18 16:14 EST by Lisa Justice
Modified: 2015-01-07 18:54 EST (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-05-20 11:30:00 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Lisa Justice 2002-01-18 16:14:55 EST
Request from Legal for us to have a separate tab on the left navigation bar
titled "Legal" (or something along those lines).  The page for this tab would
include a link to the T's and C's and the Security and Privacy stuff.  Basically
- just put all the legal mumbo jumbo in one place.  Right now - customer has to
know to go to Help Desk in order to read T's and C's.
Comment 1 Josef Komenda 2002-03-21 19:04:16 EST

 'Legal statement : Privacy statement' in the footer to:

 'Terms & Conditions : Legal : Privacy'

Would probably cover this.
Comment 2 Josef Komenda 2002-05-20 11:29:53 EDT
Also need to make the following changes: 

* On this page: https://rhn.redhat.com/help/index.pxt
Change Name of T's and C's from "License and Limited Product Warranty" to "Red
Hat Network Services Use and Subscription Agreement"
* Change name of "Security and Privacy" link on navigation bar to "Legal  and
* Under new "Legal and Privacy" section - add "Terms and Conditions" link in Nav Bar
* Under new "Legal and Privacy" section - add "Security and Privacy" link in Nav Bar
* Under "Purchase Info" section on Nav Bar - add link for "Terms and Conditions"
Comment 3 Josef Komenda 2002-05-23 15:56:22 EDT
Everything looks good on QA. Closing.

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