Discussion in 'Bukkit Discussion' started by spirroouu, Nov 4, 2011.
This is a very good idea
Because when you ask for a dev to do a project it takes away from their time and they might not be interested in the plugin. But usually i make plugins because its very fun and i like to make people happy with my work.
A few notes:
-A developer should get paid. Even for a free project, he should get paid in appreciation. Why else would we do this? We aren't robots
-The community consists of both developers and users. These 2 are essential to make this work.
-Paid plugins would give a number of effects. My guess if 3/4 of the plugins would become paid:
The number of programmers working on plugins would double.
The number of users would shrink depending on the price of paid plugins and availability of free alternatives.
If for example Spout would become paid, pirated versions would be all over the internet.
Anti-piracy would be build in, cracked and improved again. This is not what bukkit is about, we would be wasting valuable time.
The quality of top plugins would probably improve some.
Java plugins can still be decompiled.
Personally, I think paid plugins aren't a solution. However, it wouldn't hurt if a system would be implemented in bukkitdev that allowed users to show appreciation to a dev with 1 click of a button. Right now, I mostly hear the bugs, request and questions. When I hear a "Great plugin" or something like that, it keeps me motivated.
Replace paypal with thumbs up and make a Plugin Of The Day section.
That's a subjective PoV. There are three ways to price goods: cost-based pricing, price-based costing, and competitive pricing.
1. Cost based pricing: Price the good according to how much it costs for you to make (fixed costs + variable costs) and add a profit margin to be defined by the firm.
2. Price-based costing: Price the good according to how much consumers are willing to pay.
3. Competitive pricing: Price the good according to what your competition is charging.
While all true, that doesn't make my 2 cents obsolete. I was talking about the concept that the dev should be compensated for the work that was put in his/her plugin, I didn't say anything about the price
If you read #2 a bit closer, that's your key focus for considering charging for your efforts. Do you really believe the majority of Bukkit freeloaders will pay for your plugin?
Your previous post indicates a donation system. This is already a status-quo. But if you are considering offering paid plugins, then I will state with full confidence that your user base will fall significantly.
I probably misworded that sentence. What I ment was: "A developer should get something in return. Even for a free project, he should get paid in appreciation. Why else would we do this? We aren't robots "
AKA: I wasn't specificly talking about money.
Also: I should note that I ain't a proponent of money-paid plugins, as suggested by the last sentence in my original post
If you are to push for a compensation system, you will open a Pandora's box in that developers, especially ones who writes plugin with duplicate features or spin-offs of popular plugins, will demand recognition that they obviously don't deserve and complain when they don't get such recognition. They spent perhaps just as much time and effort to complete mediocre things, why don't they get any attention?
At the same time, such a recognition system might instigate a very hostile work environment between developers and developers and whoever grades their work's worthiness.
The App Store and the Android Market run on ratings, I don't see any problem there. (Although that could just be me)
Everything depends on how you implement the system.
For example= A plugin with 10 "Good plugin" votes could be rewarded the same as a plugin that has 100 "Good plugin" votes.
And that's something that's been suggested to the staff before. Haven't seen any changes though.
Lets hope they had good arguments to not implement it.
Separate names with a comma.