Bug 33695 - Better distinction between UCS apps and external apps
Better distinction between UCS apps and external apps
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: UMC - App-Center
UCS 4.1
Other Linux
: P5 enhancement (vote)
: ---
Assigned To: UMC maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-12-10 10:07 CET by Moritz Muehlenhoff
Modified: 2019-01-03 07:18 CET (History)
3 users (show)

See Also:
What kind of report is it?: Feature Request
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional): Usability
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Moritz Muehlenhoff univentionstaff 2013-12-10 10:07:45 CET
It was criticised during a technical training that it's too difficult to distinguish between apps provided by Univention and external ones. Suggestion: Add a little Univention 'u' to the lower right corner of the icons of UCS apps.
Comment 1 Alexander Kläser univentionstaff 2013-12-10 10:26:46 CET
Good idea.
Comment 2 Dirk Wiesenthal univentionstaff 2013-12-10 10:46:59 CET
Why? Are Apps from external sources not trustworthy? Or do customers try to avoid anything from Univention after using UMC?

All apps, once in the official App Center, meet certain requirements, passed several tests, etc. I do not see why we should distinguish between good/bad apps. Or what is the use case here?

The category "UCS components" (which is part of the standard installation and thus part of the maintenance) can be used to find out-of-the-box-supported apps.
Comment 3 Moritz Muehlenhoff univentionstaff 2013-12-10 11:19:03 CET
(In reply to Dirk Wiesenthal from comment #2)
> Why? Are Apps from external sources not trustworthy? Or do customers try to
> avoid anything from Univention after using UMC?
> 
> All apps, once in the official App Center, meet certain requirements, passed
> several tests, etc. I do not see why we should distinguish between good/bad
> apps. Or what is the use case here?

For every UCS component app there's a maintenance provided by Univention with is part of the UCS maintenance. If I install e.g. Squid I can use that component for the full 5+ years lifetime of a UCS major release with guaranteed updates and support. For the apps no such guarantees exist. For almost all apps the license status isn't even specified anywhere.
 
> The category "UCS components" (which is part of the standard installation
> and thus part of the maintenance) can be used to find
> out-of-the-box-supported apps.

Obviously. But if I click on any of the further categories I cannot see which ones are provided by Univention unless I study the details page.
Comment 4 Dirk Wiesenthal univentionstaff 2013-12-10 11:52:16 CET
(In reply to Moritz Muehlenhoff from comment #3)
> For every UCS component app there's a maintenance provided by Univention
> with is part of the UCS maintenance. If I install e.g. Squid I can use that
> component for the full 5+ years lifetime of a UCS major release with
> guaranteed updates and support. For the apps no such guarantees exist. For
> almost all apps the license status isn't even specified anywhere.

Some apps provide a license file, basically all saying: This is a test license with no warranty whatsoever. Please contact sales@vendor.com if you want to use it in production environments.

Granted, in many cases information about support is missing. I would not add a Univention 'u', though. Maybe a "Supported 's'" (better something more clever)?

Then it could be incorporated into the App Center generically and we may, some day, show this flag on third-party apps, too. E.g. when the App Center handles all the license stuff for the apps.
Comment 5 Stefan Gohmann univentionstaff 2019-01-03 07:18:09 CET
This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018.

Customers still on UCS 4.1 are encouraged to update to UCS 4.3. Please contact
your partner or Univention for any questions.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.