Develop a criteria of completion (or maybe diffirentiate stages of completion)

[KOLANICH]

Proposed change

Motivation

What is considered a project to be complete?

Proposed implementation

Common for all approaches:

• A project repo is created and sources are published under a FOSS license.
• The project also has an issue/bug/ticket tracker.

Approach 1

All the goals stated in the top post are met.
Cons:

• Implementer doesn't get an immediate recognition.
• Implementer is manipulated.
• We have to track a project longer even after its discussion has move into an own issue tracker.

Pros:

• No need to decide which goals are essential and which are not, so no need in getting consensus.
• Implementer is manipulated into finishing all the goals of the project.

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:

• Implementer gets immediate recognition.
• No need to track the project longer, it has an own issue, it makes more sense to track the non-essential features there.
• Implementer is not manipulated.

Cons:

• We have to have a consensus somehow on what is considered to be an essential feature. Though I don't think it will be a problem here.
• Implementer is not manipulated into finishing all the goals of the project.

Approach 3

Differentiate between fully implemented and minimum viable. Have separate halls of fame for them.

Pros:

• Implementer gets an immediate recognition.
• Implementer is manipulated into finishing all the goals of the project.

Cons:

• We have to track a project longer even after its discussion has moved into an own issue tracker.
• Implementer is manipulated.

So IMHO we should stick to Approach 2.

[FredrikAugust]

I believe the second approach is the best one here, for a number of reasons;

1. We are left with more completed projects
2. Consequentially, I believe people will be more inclined to create - at least - an MVP, as "completing" projects is easier
3. Even if the project does not make it to the "fully completed" stage, it will at least have been started, which - hopefully - leads to people forking the MVP or drawing inspiration from it, instead of starting all over

[KOLANICH]

Then we need a way to achieve consensus on distinguishing essential goals from non-essential.

Approach A

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.

Approach B

Voting on the list of essential goals during issue discussion. For each goal a message is created, for which votes are counted.

Approach C

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.