Open KOLANICH opened 4 years ago
I believe the second approach is the best one here, for a number of reasons;
Then we need a way to achieve consensus on distinguishing essential goals from non-essential.
Binary voting essential goals are met
/essential goals are not met
. A voting can be started after one or more of the declared features added to the project.
Voting on the list of essential goals during issue discussion. For each goal a message is created, for which votes are counted.
Idea creator must specify the list of goals, stating the criteria he considers right. Every community member can propose an own criteria during discussion in a form of a binary function, where operands are the minimal features. The community then votes on proposals by community members. After the criteria is accepted, it is used to determine the completion status. Criteria can be changed using voting, if the circumstances change.
Proposed change
Motivation
What is considered a project to be
complete
?Proposed implementation
Common for all approaches:
Approach 1
All the goals stated in the top post are met. Cons:
Pros:
Approach 2
Essential goals stated in the top post are met. The project is already usable for its users and the rest of goals can be achieved by adding the features to the existing project feature-by feature.
Pros:
Cons:
Approach 3
Differentiate between fully implemented and minimum viable. Have separate halls of fame for them.
Pros:
Cons:
So IMHO we should stick to
Approach 2
.