End-User Feature List

[rickmanelius]

What happened (or feature request):

• Feature Dependency

What you expected to happen:

In order to create an initial draft of a ddev UI roadmap (#6), we need to get a basic feature inventory of what we anticipate in a 1.0 version. Then we can group these by category, refine the acceptance criteria from the perspective of end-user value, etc.

Proposed acceptance criteria:

• Google spreadsheet provisioned, sharedw/ team, and stored in ddev-UI drive folder.
• Fields: category, label, short description, acceptance criteria, LOE, milestone.
• Review with team to determine any obvious gaps or potential enhancements.

Related source links or issues:

• META ddev-ui Roadmap Creation
• Define ddev Roadmap and Features Out to 2.0 (contains feature lists)
• GUI Proposal (contains feature lists)

[rickmanelius]

These two areas should serve as the initial source for generating the summarized spreadsheet. See ddev v2.0 Roadmap Scratch/DRAFT and GUI Proposal Comment.

[rickmanelius]

@andrew-c-tran and I had a good conversation regarding the high-level categories, features, and are 80-95% on the same page with respect to what they mean. Of course, more will be uncovered as we iterate and refine them.

Going to start shelling this out into a google spreadsheet here https://docs.google.com/spreadsheets/d/1oEi77sgX42BBsjHq6oOWnh3M0QNw8RnVzGCWox9scbg/edit#gid=0, and then using that to inform the roadmap ordering and next steps.

[rickmanelius]

First pass complete https://docs.google.com/spreadsheets/d/1oEi77sgX42BBsjHq6oOWnh3M0QNw8RnVzGCWox9scbg/edit#gid=1857754339

[rickmanelius]

Second pass complete w/draft milestones and roadmap.
https://docs.google.com/spreadsheets/d/1oEi77sgX42BBsjHq6oOWnh3M0QNw8RnVzGCWox9scbg/edit#gid=1857754339

[rickmanelius]

This is at a place where I recommend the following actions to get this to a completion:

• Review the combined features + milestones + roadmap spreadsheet (linked above) w/@andrew-c-tran to confirm this is tracking.
• Review with any members of the SRE team that are interested in the map ahead and identify and major gaps.
• Create the milestones in GitHub and move the roadmap information to the ddev-ui wiki.
• Break out high-level tickets for the first 3 milestones.

[rickmanelius]

Met with @andrew-c-tran and we're tracking at a high level. Moving on with the remaining items to get this to a close/completion.

[rickmanelius]

Milestones and roadmap generated. Still need to provision tickets to call this done. If anyone wants to assist, let me know :)

[rickmanelius]

https://github.com/drud/ddev-ui/wiki/roadmap

[rickmanelius]

I'm actively completing the ticket creation for the first 3 milestones. Calling this one closed!

[sgrandchamp]

@rickmanelius @andrew-c-tran As I review this doc I'm curious how we think about the GUI managing multiple users and instances of ddev within an org. I see tremendous value in being able to have Agency X log into the GUI and see everything that's in process for all deployed instances of ddev. Is that in here somewhere?

[andrew-c-tran]

@sgrandchamp I believe that would be handled when we discuss the 3rd party hosting aspect of things (v0.3). I imagine that once we have that built in, we would be able to display separate deployed accounts in different views. It's very roughly thought out right now, but that's the phase that we'd definitely start to think about how to best manage that.