After we launch, current users will land in 2.0, and probably be confused why they don’t see their Legacy (1.0) projects on the dashboard. We need some way of communicating that they must migrate their projects for them to show up in 2.0. And, ideally we help them do that without leaving 2.0 (in other words, without making them switch back and forth between Legacy and 2.0).
This pitch is a continuation of Migrate a 1.0 Project to 2.0.
3 weeks
When I arrive in 2.0 for the first time, and land on the dashboard,
I want to understand why my Legacy projects don’t show up (it looks like I have no projects)
so that I am not confused and frustrated.
When I have to migrate a project,
I would like to stay in 2.0, and not have to switch back and forth,
because that is cumbersome.
When I am in Renku 2.0 and I click on a ‘Migrate a project from Renku Legacy’ button,
→ I see a searchable list of all of my projects I have admin (?) rights on
→ I can select 1 project
→ and this takes me to the migration form developed in the migration component of‣
(all staying inside Renku 2.0)