Skip to content
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.

By clicking “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

Add Stacks page under Che's Dashboard #2206

Closed
slemeur opened this issue Aug 25, 2016 · 4 comments
Closed

Add Stacks page under Che's Dashboard #2206

slemeur opened this issue Aug 25, 2016 · 4 comments
Labels
kind/enhancement A feature request - must adhere to the feature request template.
Milestone

Comments

@slemeur
Copy link
Contributor

slemeur commented Aug 25, 2016

Add Stacks list under Che's Administration page

We will add a new tab under the Che's Administration page on the User Dashboard: "Stacks"
In this page we will display the list of all the Stacks that are registered on Che. (ie stacks.json)

6 - stacks - actions - option2

@TylerJewell
Copy link

Maybe this should be a primary left nav item called Stacks? If we are going to do a lot more with stacks sharing and notification among shares users then that would not be an administration issue - it would just be stacks.

@slemeur slemeur changed the title Add Stacks list under Che's Administration page Add Stacks page under Che's Dashboard Aug 25, 2016
@slemeur
Copy link
Contributor Author

slemeur commented Aug 25, 2016

OK +1

Updated design:
6 - stacks - actions - option3

@ashumilova ashumilova added kind/enhancement A feature request - must adhere to the feature request template. status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it. sprint/next team/plugin labels Aug 26, 2016
@TylerJewell
Copy link

+1 on the location - definitely want this as a primary object. @slemeur - lets also think about some of the onboarding workflows for new users into the Che product once stack editing is available.

If you are a new user in Che, today we push you to create your first workspace. We want to get them with a private repository that they can make a commit with. Should we be thinking a bit more about pushing people into creating their first custom stack?

1: Browsing existing stacks for their contents. I noticed that many of the stacks have descriptions and component lists that could be updated (version numbers and more complete items).

2: Browsing the different stacks by operating system. I noticed that we do not have a filter component on the ready-to-go stacks, but we do on the stack library. We should be consistent.

3: How will changes to stacks have notifications to users? This is a super tricky issue as we can track changes to the meta information, but we will not necessarily be able to track changes to internal images.

4: When users create new stacks, creating from an existing one or a new from a template will be a big deal. We will want to make it really fun for people to create new stacks over time.

Ok to start breaking these issues into different issues - just starting the discussion.

@ashumilova ashumilova added sprint/current status/in-progress This issue has been taken by an engineer and is under active development. and removed sprint/next status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it. labels Sep 6, 2016
@slemeur
Copy link
Contributor Author

slemeur commented Sep 8, 2016

Cross link with #2316

@ashumilova ashumilova removed sprint/current status/in-progress This issue has been taken by an engineer and is under active development. labels Sep 19, 2016
@ashumilova ashumilova added this to the 5.0.0-M2 milestone Sep 19, 2016
@riuvshin riuvshin modified the milestones: 5.0.0-M3, 5.0.0-M2 Sep 20, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement A feature request - must adhere to the feature request template.
Projects
None yet
Development

No branches or pull requests

4 participants