Last call for Feedback on the Open Mithril Development Framework!
Shortly we will be editing/adjusting the proposal (we already are), to include some of the feedback we have received that can still be changed. In the past 8 days (!!!) we have received tremendous feedback, a lot of it positive, and continued to connect with leaders and builders around the chain.
And I don't want to be glib, I love all the positive feedback I am getting - it helps validate us and our 35+ years of experience working with open source (depending on how you count) - and of course makes the energetic cost to do this part of the roadmap a little more bearable with each positive validation.
But I want and need the negative. So one more time, I have indexed the list. If you have anything to add - do it now.
All the things someone didn't like:
Too vague
Responded: Simple as it gets: Redhat for HIVE
Too Wide
Responded: Specific as it gets: 4 Champion Modules
Module 1: yourFrontend / yourBackend
Feedback: We already have frontends? - INVALID
Module 2: Auto-Badger
Feedback: only positive
Module 3: HAF app - Mithril's FiscalForge
Feedback: Repeat work for Keychain Store, Distriator, HiveDebit, SpendHBD - INVALID
Response: from this post
Module 4: Beem Hive-Nectar
Feedback: We don't need Beem
Response: We are doing it anyway
Response: Use our work with dhive library
Too quick (voting)
Response: Impossible to change now
Too tight (payout)
Response: Impossible to change now
Remove Travel
Response: Budget under consideration
Remove hive power
Response: Budget under consideration
This is all the feedback I have gotten. I feel like there might be a few more hiding out there, but this is what you have given me to work with.
I am giving you ~24 more hours!
Hit me with your best shot!
7M+ HP and 99 users agree with us, and that is just in 8 days!! Pretty good for a "dead chain" amirite?
So shoot your shot, gimmee what you got, I can take it, I want it, I need it - THIS IS WHAT WE ARE DOING
Is it worth money?
Vote Yes HERE peakd
Vote Yes HERE ecency