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

Select Feature Goals for Blossom #3682

Closed
nathan-at-least opened this issue Nov 15, 2018 · 2 comments

Comments

Projects
None yet
3 participants
@nathan-at-least
Copy link
Contributor

commented Nov 15, 2018

This ticket is for tracking the need to integrate and select the target features for Blossom. Here's the process.

Early Research / Brainstorm Phase:

a. Brainstorm ideas and track them with the Blossom wishlist label.
b. @nathan-at-least may select some of those to promote to Blossom Goal + Feature Requirements labels status. This change signals that the company is moving beyond the brainstorm/wishlist stage to putting the goal through a "feature selection" process, namely the following steps.
c. Issues that aren't promoted may be transferred to the wishlist for future upgrades, or we may choose to close them to signal that we plan to not aim for that proposal for the foreseeable future.

Feature Selection Process:

d. When brainstorms become explicit goals, the first step is to define "feature requirements" which translates a broad high-level goal into precise technical requirements. (Note: this is not design or implementation, which comes later.) @nathan-at-least will delegate some of this feature requirements work.
e. While feature requirements are being sorted, @nathan-at-least will be coordinating a "product validation" process, which involves getting targetted feedback from the ecosystem, and also doing internal user modeling and market analysis. We want to know who a feature helps, how it helps them, which strategic goal this advances, and what those user's best alternative to a given feature might be. If all those those don't line up sufficiently, we may decide to nix a feature goal.
f. In concert with product validation, we also need a requirements integration process, to ensure all of the feature requirements are coherent together.
g. For the features which have well specified requirements and which pass our validation, we'll then commit to them, which will begin a subsequent specification & implementation phase.

We'll announce our transition into the specification and implementation phase as we approach it.

Edit: Formatting / markup after initial post.

@mms710

This comment has been minimized.

Copy link

commented Nov 15, 2018

Hi! Just wanted to make a note that we're aiming for the end of November to have all items from the brainstorming list either rejected or promoted to the Blossom Goal + Feature Requirements labels status by the end of November.

@mms710

This comment has been minimized.

Copy link

commented Dec 27, 2018

Closing this ticket as we think we have the goals defined for Blossom, as follows:
Harmony Mining - #3672
Shorter Blocktimes - #3690
Split Founder's Reward - #3673
Allow transaction version 4 through Blossom upgrade - #3739

@mms710 mms710 closed this Dec 27, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.