8000 Define MVP for Packit console.redhat.com integration · Issue #180 · packit/research · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Define MVP for Packit console.redhat.com integration #180

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicki 8000 ng “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
5 tasks
Tracked by #175
lachmanfrantisek opened this issue Apr 26, 2023 · 1 comment
Closed
5 tasks
Tracked by #175

Define MVP for Packit console.redhat.com integration #180

lachmanfrantisek opened this issue Apr 26, 2023 · 1 comment
Labels
area/rhel-ecosystem Related to RHEL, CentOS Stream, etc. complexity/single-task Regular task; should be done within days gain/high Brings a lot of value to users impact/high Affects a lot of users kind/internal Task that doesn't affect users directly

Comments

@lachmanfrantisek
Copy link
Member

The goal of this task is to use findings from #178 and design an MVP for the Packit integration into console.redhat.com ( #175). Specifically:

  • Go through the output of Research architecture of console.redhat.com #178
  • Prepare the ideas for the UX of Packit's integration. (You can get inspired by the demo made by @TomasTomecek in packit/private#16)
  • Discuss within a team.
  • Define a new epic issue where the user-story is clearly described.
    • Include a diagram of how people will interact with the workflow.

The work will be planned in the follow-up card: #179

This issue is part of the #175 epic.
@lachmanfrantisek lachmanfrantisek added area/rhel-ecosystem Related to RHEL, CentOS Stream, etc. complexity/single-task Regular task; should be done within days gain/high Brings a lot of value to users impact/high Affects a lot of users kind/internal Task that doesn't affect users directly labels Apr 26, 2023
This was referenced Apr 26, 2023
Closed
Open
@lachmanfrantisek lachmanfrantisek moved this from new to backlog in Packit Kanban Board Apr 26, 2023
@lachmanfrantisek lachmanfrantisek moved this from backlog to priority-backlog in Packit Kanban Board Jan 25, 2024
@lachmanfrantisek
Copy link
Member Author

This is not up-to-date... Let's open a new card when/if needed.

@lachmanfrantisek lachmanfrantisek closed this as not planned Won't fix, can't repro, duplicate, stale Feb 27, 2024
@github-project-automation github-project-automation bot moved this from priority-backlog to done in Packit Kanban Board Feb 27, 2024
@lachmanfrantisek lachmanfrantisek moved this from done to backlog in Packit Kanban Board Feb 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/rhel-ecosystem Related to RHEL, CentOS Stream, etc. complexity/single-task Regular task; should be done within days gain/high Brings a lot of value to users impact/high Affects a lot of users kind/internal Task that doesn't affect users directly
Projects
Packit Kanban Board
Archived in project
Milestone
No milestone
Development

No branches or pull requests
1 2CB0 participant
@lachmanfrantisek
0