Bug 1282008

Summary:	Clarify language when referring to non-RH packages
Product:	Red Hat Enterprise Linux 6	Reporter:	Alois Mahdal <amahdal>
Component:	preupgrade-assistant-el6toel7	Assignee:	Petr Stodulka <pstodulk>
Status:	CLOSED WONTFIX	QA Contact:	Alois Mahdal <amahdal>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.7	CC:	ovasik, phracek, pstodulk, ttomecek
Target Milestone:	rc	Keywords:	Extras
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-07-01 15:30:51 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Alois Mahdal 2015-11-14 06:46:56 UTC

Description of problem
======================

Use of "Non-RH signed" term when referring to "user's packages" may
be confusing.

In particular, "Non-RH signed" may be understood as referring to packages
that are signed, but not by Red Hat.   But in fact, we don't make any
distinction between packages signed by other authorities or not signed
at all; this term may create impression that there is such distinction.


Version-Release number of selected component
============================================

preupgrade-assistant-contents-0.6.41-1.el6


Additional info
===============

Other term that has been mentioned and is sometimes used in same context
is are "3rd party packages".  IMHO this is better, but still may sound a
bit awkward in some situations, in particular if the packages are owned
solely by customer: there is no 3rd party (just us and them).

My suggestion is to use very simple language here, such as "foreign" or
"non-RH" packages.  The important distinction here is that the packages
are not already "covered" by Red Hat so someone should take a look.

Comment 3 Petr Stodulka 2019-07-01 15:30:51 UTC

Closing this bugzilla as the component is under a maintenance mode in which the maintainers are going to fix only critical bugs. If you consider the bugzilla critical, feel free to reopen the bug with an explanation.