ddev / ddev-ui

A not-currently-maintained user Interface that provides a graphical way of interacting with DDEV Local
https://www.ddev.com/
Apache License 2.0
20 stars 5 forks source link

Redefine the updated Roadmap #100

Closed alkymst closed 6 years ago

alkymst commented 6 years ago

What happened (or feature request):

With the most recent on-site, and Q3 objectives we need to redefine the roadmap to release and WPCampus.

What you expected to happen:

We have a clear path we are working against.

Anything else do we need to know:

WpCampus is a priority for July 11th - 14th

Related source links or issues:

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

alkymst commented 6 years ago

@rickmanelius this has been updated, let me know what you think? I should have just posted it here first.

This is the official development roadmap for DRUD ddev UI.

Planned Releases

v0.3.0 (Style Guide and Designs)

The intention of this milestone is to change, disseminate, and practice our new workflow around design related asset creation, review, approval, and usage. We've moved towards the use of a global ddev style guide but these efforts are currently at different levels of completion and out of sync. By the end of this milestone, we intend to have the following issues addressed:

v0.4.0 (Stability / Demobility)

The intention of this milestone is to provide a solid application for users to demo. Areas of focus here are as follows:

v0.4.1alpha (Alpha Release - TBD)

The intention of this milestone is to provide a demo for user to provide feedback. Areas of focus here are as follows:

v0.5.0 (Workflow Improvements)

The intention here is to make it easier for developers to save/restore from a local backup as well as create a cloned copy. Areas of focus here are as follows:

v0.6.0 (Notifications)

The intention of this milestone is to allow end-users to receive notifications when long standing tasks (downloads, imports, etc) are complete. Areas of focus here are as follows:

v0.7.0 (App Search)

The intention of this milestone is to help users manage multiple apps (dozens or more) by providing the ability to search, sort, and filter the app dashboard. Areas of focus here are as follows:

v0.8.0 (Hooks and Containers)

The intention of this milestone is to help surface more advanced features and functionality, including the ability to view configurations related to services and pre/post hooks as well as pull from a library of pre-existing solutions for each. Areas of focus here are as follows:

v0.9.0 (Support)

The intention of this milestone is to ensure the application is providing proper instructions, helper text, and access to additional resources if/when they are blocked. Areas of focus here are as follows:

v0.10.0 (Performance, Security, & Bugs)

While we plan on addressing these themes along the way, it's important that we have a 1st class focus on this as we end the first leg of the roadmap. Areas of focus here are as follows:

v1.0.0 (Official Release)

The intention of this release is to ensure we finalize all the non-development related items that are necessary to support our project, including landing pages, tutorials, branding, etc.

Future Releases

v1.1.0 (Wishlist: Short-term)

These are items that are out of scope from 1.0, but likely to make it in on the longer roadmap.

(3rd Party Hosting)

The intention of this milestone is to add apps directly from a supported 3rd party integration and begin importing databases and files. Areas of focus here are as follows:

v1.2.0 (Wishlist: Long-term)

These are items that are out of scope from v1.0 but are much more speculative in nature because there are many unknowns, it could take a lot of effort, or it's unclear if this fits within the goals of our project and its end-users.

Previous Releases

rickmanelius commented 6 years ago

@alkymst Just noting this ahead of time before I respond in more detail. I'm going to focus purely on the first 3 milestones (v0.3.0 through v0.4.1) because they directly relate to the current definition of the OKR and its goals. Milestones v0.5.0 and beyond, while important, can be updated later or simply left alone for now and updated once we get to v0.4.1 and determine if changes are necessary.

rickmanelius commented 6 years ago

In my worldview, milestone v0.3.0 as proposed relates to the first target WP Campus and the remaining two of v0.4.0 and v0.4.1 would be necessary prior to a full release to the community.

alkymst commented 6 years ago

That’s how I’m seeing it as well. And what I was trying to do with issue organization.

rickmanelius commented 6 years ago

Google docs is easier to collaborate/modify the three milestones. Moving here and then once we're good let's pullback into the wiki. Ty https://docs.google.com/document/d/1JMqRbA3oNPzmvysXM-yRS0crE9awEcz50563mu3_Mtg/edit#

rickmanelius commented 6 years ago

I feel good with the above edits. Feel free to respond/modify. I basically updated the description of the v0.3.0 milestone to be more accurate. Only a few bullets are questionable. Otherwise this is G2G and we can get this updated and then modify the KR to reflect the milestone parity (I'll take on that step).

alkymst commented 6 years ago

Roadmap has been updated.

rickmanelius commented 6 years ago

@alkymst Much appreciated!