This repository has been archived by the owner on Jul 23, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 66
Further merge the Launcher and OSIO project creation wizard #1317
Labels
Milestone
Comments
joshuawilson
changed the title
[EPIC] Further merge the Launcher and OSIO project creation wizard
Further merge the Launcher and OSIO project creation wizard
Nov 9, 2017
I created fabric8-launcher/launcher-planning#69 and we (cc @quintesse) are working on fabric8-launcher/launcher-planning#66 |
@slemeur can you add #1499 as a new merge task checkbox? That is the only missing task extracted from fabric8-launcher/launcher-planning#66 |
Done. Thanks @gastaldi |
It looks like the checkboxes are out-of-date relative to the child issues. Can someone update, please? |
3 tasks
Moved to OpenShift.io: https://openshift.io/openshiftio/openshiftio/plan/detail/2059 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
Goal
Further merge fabric8 launcher and OSIO wizard so they share a code base and the user experience is fluid from launcher to OSIO.
Description
We have two separate codebases between Launcher and project creation wizard in OSIO. This came from historical reasons while Launcher needed to be released while OSIO was not ready. The goal of the epic is mainly to reduce the technical debt between the two components and allow to use a single codebase.
The user experience will remain consistent, but Launcher, would allow to display the specific pages that are used and needed inside of OSIO
Launcher (on redhat.developers.com/launch) will allow to point the user to OSIO, so that it will open OSIO with the create project wizard displayed in OSIO
Identified steps and items to reduce the technical debt
Moving component to ngx-forge:
Merge Tasks:
Bugs:
Nice to have improvements:
User Experience
We need to better align the create project wizard from OSIO with the flow in Launcher. UXD will need to work on how we can make the wizard consistent between the two platform.
Parent Scenario
#2083
The text was updated successfully, but these errors were encountered: