-
Epic
-
Resolution: Unresolved
-
Undefined
-
None
-
Developer Lightspeed - Notebooks Spike
-
False
-
-
False
-
To Do
-
RHDHPLAN-245 - [Lightspeed] Spike of Personal AI Notebooks Feature
-
QE Needed, Docs Needed, TE Needed, Customer Facing, PX Needed
-
-
EPIC Goal
This EPIC focuses on the UI work required for the https://issues.redhat.com/browse/RHDHPLAN-245 feature of DevAI team.
What are we trying to solve here?
The goal is to capture the work required into a PoC for the frontend part of a Lightspeed feature that's similar to the Google Notebooks functionality.
Conduct user research on the UI approach for the Personal Notebooks AI flavor.
Refer to RHDHPLAN-36 for explicit goals and scope.
Some questions to consider:
- This AI "notebooks" feature should be considered an "add-on" of the current Developer Lightspeed. Is this a toggle on? Is this a new page/tab from the Developer Lightspeed page?
- How does the user upload their documents? Are they drag & dropping? Are they choosing from the folder one by one?
- How can users find their previous session?
Background/Feature Origin
As RHDHPLAN-245 describes the main idea is to explore options on NotebookLM and see if taking a similar approach is possible for lightspeed.
Refer to RHDHPLAN-36 for explicit goals and scope.
The devAI part of the work focuses on the backend component, but as this features is something that the end user will be able to use, we have also created a UI Epic.
Why is this important?
As discussed in various meetings this is an interesting feature that will allow the user to dive deeper on specific topics from the documents they bring in using lightspeed.
Dependencies (internal and external)
Acceptance Criteria
Release Enablement/Demo - Provide necessary release enablement details
and documents
DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
Issue>
DEV - Upstream documentation merged: <link to meaningful PR or GitHub
Issue>
DEV - Downstream build attached to advisory: <link to errata>
QE - Test plans in Playwright: <link or reference to playwright>
QE - Automated tests merged: <link or reference to automated tests>
DOC - Downstream documentation merged: <link to meaningful PR>