-
Notifications
You must be signed in to change notification settings - Fork 13
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
Building #85
base: master
Are you sure you want to change the base?
Building #85
Conversation
|
||
Which features to build next? How does it look like? How do we make sure that technical power users like it without confusing noobs? Who gets to make a decision on that? How often? | ||
|
||
Recent conversations have happened around potential redesigns for product features, such as the coinjoin status “music” box or unearthing buried features such as coin control. This pushed the team to think about the reasoning behind it and discuss how features are prioritized in Wasabi 2.0. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this should be worded more generally, we'll forget what this specific case was about soon.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ACK. Will share an update. Thanks!
Co-authored-by: Max Hillebrand <[email protected]>
Scream whenever you feel like it's ready to merge! |
Co-authored-by: nopara73 <[email protected]>
We propose a system to help prioritize the product development without a static hierarchy, allowing the number of contributors to scale, limiting inefficiencies or formal authority.