Pulp UI : Phase II Working Group

• Meeting time: 1030 GMT-5
• Members: mhradil, znemecko, ggainey, pbrochado, mdellweg
• pulp-ui repo
  • non-draft open PRs
• pulp-ui oci-env profile

Template

## YYYY-MM-DD
### Attendees:
*
### Previous Action Items:
* 
### Agenda:
* 
### Action Items:
* ggainey: add notes to [discourse thread](https://discourse.pulpproject.org/t/pulp-ui-phase-2-working-group/1795/7)

Upcoming

• GH details:
  • Do we want to use auto-merge?
  • How about branch rules (requiring review and wf success)?
    • already in place
  • Meaning of "draft".

2025-02-13

Attendees:

• ggainey, mdellweg

Previous Action Items:

Agenda:

• PRs closed since last meeting
• issues opened since last meeting

Action Items:

• ggainey: add notes to discourse thread

2025-01-16

Attendees:

• ggainey, mdellweg, zita, vishali, mhradil, pbrochado

Previous Action Items:

• ggainey: schedule 3 mtgs (DONE)

Agenda:

• status of Draft PRs?
  • react-router: mhradil waiting to comment til not-draft
    • AI: mdellweg to undraft
  • session/cookie-auth:
    • requires react-router PR in its current state
    • PR works but on top of core/3.70
    • needs fixes
    • FF presents login-window when it sees basic-auth-header
      • but NOT if you use FETCH?
      • BUT - session-cookie requries presenting auth-header
    • should work once core/3.70 is released
    • wait until core/3.70 Ecosystem (esp incl pulp_rpm) is released
  • rpm-search:
    • mhradil to refresh his memory
• tests exist! yay!
  • how can we learn to do that?
  • https://docs.cypress.io/app/end-to-end-testing/writing-your-first-end-to-end-test
  • also look at the PR that adds the basic smoketest
  • warning: UI Testing is Chaotic - "be paranoid about checking exactly where the app actually is"
  • component tests?
    • Yes Please!
• finding issues with existing - best way to open?
  • suggestion: open an issue for a page, list the set of problems noticed as bullets
• discussion: tell us about alert-popups
  • sometimes per-page, sometimes global?
  • if in context, they don't auto-close when move to new screen
  • if move into context - make sure to address how they get closed
• pulp-file repo/remote "works"
  • but still suboptimal
  • could use some refactoring
  • still -serves as a useable "how to" for other plugins who want to duplicate that much at least
• Meeting cadence:
  • every-other week, 2 more, then reasses
  • Phase 2 WG *ends at end of Q1

Action Items:

• ggainey: add notes to discourse thread

2024-12-16

Attendees:

• ggainey

Previous Action Items:

• N/A

Agenda:

• Discuss priorities
  • Discuss proposals for priorities
    • mhradil: rewriting/refactoring important technical-debt
      • will make future work MUCH easier
    • mhradil: patternfly-6?
      • some of the switch is "easy"
      • some amount, is not
      • navigation, select-components (deprecated from 4)
    • mhradil: some amount of "content"
      • not just repos/remotes
    • ggainey: having a firm foundation/examples for "how to do it" will help keep the project healthy/get commmunity contribution more easily
    • mhradil: tests would be Very Nice
      • small set to start
    • mdellweg: react-router
      • username/pwd in browser-storage - we def need to Do Something About That
      • drf-api knows how to do this? maybe?
      • mdellweg has an experiment in progress
        • login w/ basic-auth and then rely on session-cookie-auth
    • mhradil: "storybook" for "components available for reuse in this project"
      • less "reinventing wheels"
    • zita: decide what to do with ansible/galaxy code remaining
      • keep what makes sense in "bare" Pulp installation, and remove everything else
• Meeting format
  • 30 min?
  • every-other-week? monthly?
  • how long will Phase 2 go?
  • proposal:
    • meet every-other-week
    • revisit schedule after 6 weeks
    • ggainey to schedule 3 mtgs then reconsider
    • mhradil/zita's cals prob not up-to-date "yet"
      • drop info to ggainey to consider
    • let's not do Fridays

Action Items:

• ggainey: schedule mtgs
• ggainey: add notes to discourse thread