# Motivation and Perceptions for a UI for Pulp

###### tags: `PulpCon 2020`

## Motivations for a UI

* Having no UI and no CLI, users must
* Read/Learn the API
* Do some form of programming
* Having a CLI but no UI, requires users to
* Read/Learn the CLI
* Do some form of scripting
* Requiring either scripting or programming to use Pulp is a large barrier to it's usage
* The largest competitors to Pulp both have UIs
* Artifactory: https://www.jfrog.com/confluence/display/JFROG/Repository+Management
* Nexus Repository Manager 3: https://help.sonatype.com/repomanager3/user-interface
* No matter how great Pulp 3 is, without a UI it cannot be a relavent competitor
* Natural place to surface RBAC and perms (even if in a read only sense at first)

## UI collaboration project overview

We're hoping to work with students from UMass Lowell to develop a Web UI.

#### Outline

https://hackmd.io/Dp-kVIjnTVeQVse2w2eC-w

## Discussion
* Another benefit to UI is exposing and demonstrating the semi-large set of resources and actions in a slightly friendly mechanism than browsing API specs and schema
* And a natural place to join resources definitions and user centric documentation and examples.
* Strong parallel between needs of cli and a semi-generic UI. ie, exposing resources and ops and expressive and explicit ops (CRUD-ish) as well as providing some higher level workflows
* Automation hub RBAC and content sync demo: https://redhat.bluejeans.com/playback/s/5U1ie62rXnAomu1hg0ghpD9DCusNDGWOt74FJVWfzWQC4CwOoPsjuOcMhwoJTIGP
* This project was mentioned in chat: https://github.com/af6140/pulpman

###### tags: `PulpCon 2020`