Available translations

Features Hierarchy

governance.png
Summary: Each project may define Features, so that the Community may incentivize desired directions of development.
Governance->Node->Features->Definition
features.png
The Features hierarchy defines existing software features, or features in the wish list, yet to be developed. The definition of existing features exist to reward Contributors maintaining the code. Definitions of features that don’t yet exist are intended to incentivize the creation and contribution of the said features.
Governance->Node->Features->Content
Use your Weight Votes to influence the direction of development of specific Feature nodes, or sets of features represented by Feature Class nodes.
Feature Class Nodes
Governance->Node->Feature Class->Definition
feature-class.png
The Feature Class node is an organizational device used to group features in arbitrary arrangements. The node may receive Weight Votes. When it does, votes are evenly distributed among offspring nodes.
Governance->Node->Feature Class->Content
You may direct Weight Votes to a Feature Class node when you intend to support the whole class, including all features within.
Feature Nodes
Governance->Node->Feature->Definition
feature.png
A Feature is the capacity of the software to perform tasks required by a specific use case. We describe features so that users may direct Weight Votes to express which of them are the most valuable. This is how users may decide which features to incentivize, both in terms of maintenance and development.
Governance->Node->Feature->Content
You may cast Weight Votes on individual Feature nodes to incentivize the improvement, development, and maintenance of the said feature.
If you are involved in the development or maintenance of a feature, you may place a Feature Contribution Claim and rally the Community to support your claim with Feature Claim Vote nodes so that you may be rewarded for your work.
Previous
Positions Hierarchy
Next
Assets Hierarchy