johnbillion / extended-cpts

A library which provides extended functionality to WordPress custom post types and taxonomies.
GNU General Public License v2.0
979 stars 96 forks source link

Open-source development monetization #96

Closed PatchRanger closed 6 years ago

PatchRanger commented 6 years ago

In short: this PR proposes a way to monetize open-source development of your project. The idea is similar to how free-to-play works in gamedev industry: "You are free to wait for the package download - but in case if time is money for you, please consider buying non-waiting access to the package, every cent goes to the package developer to incentive the open-source development."

For details please refer to https://github.com/Free2Wait/composer-free2wait .

According to packagist statistics of your package https://packagist.org/packages/johnbillion/extended-cpts/stats , in theory it could bring to you about 979 (installs per month) 0.03 (estimated conversion installs-to-sale) 5 (price of each non-waiting access per month) = estimated $146.85 per month.

Please give me your feedback about the idea: what do you think? Are you interested in monetizing open-source development? Do you have any suggestions? Concerns?

Would be glad to receive any feeedback. Thank you for attention.

johnbillion commented 6 years ago

While I appreciate your intent, it's difficult to know where to start with explaining what a terrible idea this is. I've read through the responses from other people in your PRs to other projects and they cover most of what I want to say about this idea.

I'd suggest that you abandon this idea completely and stop spamming projects on GitHub in order to get feedback.

PatchRanger commented 6 years ago

@johnbillion Thank you for response! I appreciate it.

While I appreciate your intent, it's difficult to know where to start with explaining what a terrible idea this is. I've read through the responses from other people in your PRs to other projects and they cover most of what I want to say about this idea.

Though I understand your point, I am not sure that we should judge in "black-or-white" manner.

I am not advocating evil - I am just trying to make this world better from what we have now) Let me accurately log all of the project's negative sides collective mind will see - while in your turn please try to see the potential positive changes it could bring. Together (I believe) we can shape it to the appropriate manner.

I'd suggest that you abandon this idea completely and stop spamming projects on GitHub in order to get feedback.

I'd like to - but the harsh reality requires me to gather statistically reasonable sample of feedback before we could ever make conscious decisions)) Almost everything in this Universe works only at big numbers.

I am sorry, John, but I am going to continue) I've already done 20 out of planned 100 - and I am going to finish the sample before making decisions. Please keep in mind that I am doing it in the most "ecological" and humanistic manner I could imagine: I've searched Github for "PHP" (https://github.com/search?l=PHP&o=desc&p=98&q=php&s=stars&type=Repositories&utf8=✓), sorted by "Most stars" - and started from the end in order to bother the least number of people possible.