This community provides a space to suggest and discuss ideas for improvements to the Decentralized Hive Fund (DHF). These can be ideas for changing how the DHF operates, how we use it, or anything else related.
The community aims to maintain a well-organized space where there is more clarity about how to propose an idea for discussion by the wider Hive userbase, collect feedback and get a sense of level of support for the idea.
By adding a bit of structure, the community hopes to aid the process of starting with an initial idea, fleshing it out, gathering feedback from multiple groups (marketers, devs, business owners, blogging users, etc.) and maturing it into a well-rounded, concrete and viable proposed improvement.
To be effective at making change, the community is looking to involve large numbers of stakeholders. This can not only provide a lot of input but also can give an idea traction and show its level of support. As a first step in this direction, the community owner account itself will hopefully soon be a multisig controlled by multiple people (looking to go to 20+).
When needed, if an idea has traction, a formal DHF proposal could be made (that doesn't ask for any funding) to gauge total stake support, before deciding whether to move with implementation. With that said, many ideas may not need any change to the code but simply some behavioral changes, or other.
Suggested guideline for posting
To keep things organized, it is suggested that we have one post per idea. This allows to discuss the merits of each idea in its own dedicated post. Before making a new post, first check if a similar idea has been suggested already and participate in its dedicated post if so.
Tweaks to the idea can be made by editing the post. Very substantial changes probably warrant creating a new post for the new idea.
Aim for a descriptive title that will allow your post to be easily searched and referenced.
Avoid posting an idea that already exists, and avoid spamming in general as this will reduce overall participation.
Suggested guideline for commenting
It can be helpful to discuss pros and cons in the idea’s post. For each pro that you identify, consider making a separate comment that starts with Pro:, for example:
Pro: This will likely increase stakeholder participation in DHF voting.
And for each con that you identify, consider making a separate comment that starts with Con:, for example:
Con: This requires the creation of a separate legal entity.
This will enable stakeholders to comment under each pro and con, and to vote on those they consider important. This will give some aggregated sense of where stakeholders stand on an idea’s pros and cons.
Suggested guideline for ideas for improvements to the community itself
If you have an idea for the DHF Improvements community itself, first check if a similar idea has been suggested already. If not, make a dedicated post with the title starting with [META], for example:
[META] Make declined post rewards mandatory for posting in the community
The [META] helps identify ideas related to the community’s own organization.
Ideas for changing the community’s technical functioning are up to the community multisig holders to approve, whereas ideas beyond that are up to everyone participating to embrace and make use of.