Suggestion, to be taken into consideration for next generation NRP
The following is just a general idea, to get the creative juices flowing...
Possibility to merge projects in the NRP. A project merger is triggered by affiliates, based on a decision making process involving all the participants in all projects that are merged. The operation is automated. It takes the input from this decision making process, which unlocks the merge operation. This can be implemented as a multisig smart contract (respecting the decision making process - number of votes, or % of affiliates) that unlocks the merger function. The merger puts all the past events under the new project entity (create a parent child relation between the new project and the ones that have been merged and closing/blocking further activity in the context of these merged projects?), and informs any benefit redistribution algorithm that will be executed in the future for pulling data from all the past individual projects that have been merged. Also, a new benefit redistribution is to be created for the newly created project. Moreover, a new project governance should be enacted for the new project. Agreements on the new benefit redistribution algorithm and the new governance doc are required prior to the agreement to merge projects.
Precedent: In Sensorica we had a proliferation of agriculture-related projects. At some time, this proliferation created duplicates, a lot of confusion, not very beneficial to the entire network. A Synthesis of past work is beneficial, making it easy for people to navigate past work and decide where to go next.
Suggestion, to be taken into consideration for next generation NRP
The following is just a general idea, to get the creative juices flowing...
Possibility to merge projects in the NRP. A project merger is triggered by affiliates, based on a decision making process involving all the participants in all projects that are merged. The operation is automated. It takes the input from this decision making process, which unlocks the merge operation. This can be implemented as a multisig smart contract (respecting the decision making process - number of votes, or % of affiliates) that unlocks the merger function. The merger puts all the past events under the new project entity (create a parent child relation between the new project and the ones that have been merged and closing/blocking further activity in the context of these merged projects?), and informs any benefit redistribution algorithm that will be executed in the future for pulling data from all the past individual projects that have been merged. Also, a new benefit redistribution is to be created for the newly created project. Moreover, a new project governance should be enacted for the new project. Agreements on the new benefit redistribution algorithm and the new governance doc are required prior to the agreement to merge projects.
Precedent: In Sensorica we had a proliferation of agriculture-related projects. At some time, this proliferation created duplicates, a lot of confusion, not very beneficial to the entire network. A Synthesis of past work is beneficial, making it easy for people to navigate past work and decide where to go next.