・ Please note that it may not be possible to convey the correct expression because it is via a translator.
・ This issue is very biased because I will talk from the perspective of the creator who is listing the project. Not everything is right for me, and not everything needs to be what I want. This is a reference opinion.
・I won’t list individual project names in this topic, and I don’t know the background why that project is in that situation right now. So far, I have no complaints about the support gathered for my project.
Currently, I feel that the amount of support for listed projects lacks fairness.
Let me give you an example. More than tens of thousands of DEVs of support will be gathered for products that have never been committed and development has stopped since the beginning of this year. Even if they have hardly committed since the listing, a large amount of support has been gathered through public relations activities. The creators who launched valuable projects for these are not very gathered because they are new and have low communication power.
The usefulness of open source brought about by the project (the amount of pull requests and the number of people who use the product purely), and the degree of contribution in the sense that the product is increasing the number of participants in the DEV economic zone through public relations activities. I will ignore it here.
In my opinion, what Stakes.social wanted to achieve was to create continuity for open source projects.
I believe that products that are not under development, have no further progress using developed products, have no progress in activities, and have no contribution to the DEV economic zone should be considered finished or completed. Recall that projects that went public after development could be completed without the need for Stakes.social.
The introduction has become long, but based on the above, I will summarize the problem and propose improvements to it.
(Issue and countermeasures
(1) It is difficult to understand if you do not look at github whether you are developing.
→ Add a function to visualize the development progress on the project list page and project details page. Commit line graph, commit history, new commits, etc.
(2) The hypothesis that investors are not interested in the future of the project because the APY does not change no matter which project they support.
→ Make APY fluctuate depending on the activity of the community in the development or project page (although it is very difficult to create logic and algorithms that everyone can be satisfied with …)
The above is an opinion that ignores the cost of implementation. Please forgive me.
Thank you for your cooperation.