Pulp UI: Phase 2 Working Group

Announcements
#1

Hey folks,

The initial proof-of-concept for a Pulp UI is now available in the oci-env and, shortly, will be part of the nightly OCI images for Pulp! Time to consider what our next steps/priorities should be.

To that end, we’re organizing a “Phase 2” working group around the UI work. If you’re interested in contributing, or even just helping us set priorities for this effort, please chime in here. We will meet sometime next week to organize and discuss timelines and such.

Thanks to @himdel, @ZitaNemeckova and @gerrod for all the work so far - excited to continue!

Thanks,
G

5 Likes
#2

I’m in :slight_smile:

#3

Hey :slight_smile: Let’s set a date before Christmas and get the roadmap out. I heard from few people that they may use the holidays to catch up on learning React and this could be a project they’ll contribute to :slight_smile:

2 Likes
#4

Concur - right now it’s just you and me (and Martin, I assume :slight_smile: ). Will bring it up at next team mtg, and shoot for a mtg late next week/early the following.

G

#5

mdellweg has expressed an interest as well

#6

I’ll jump in

#7

Organizational mtg scheduled for 16-DEC 0930 ET - see y’all there!

#8

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 “hgow 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
    • Next meeting: 16-JAN 1030 ET (1530 UTC)

Action Items:

1 Like
#9

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!
  • 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: