I would put adequate documentation as part of clarity and discoverability, both because they serve the same end and because the inherent clarity and discoverability can increase or decrease the amount of documentation needed to effectively use the API. So maybe I should have said "clarity, discoverability, and documentation".
In fact one can earn revenue from the sites using your work if you have released under GPL, but they must licence their work in GPL. If you release your work in MIT Licence the developer need not licence his work in MIT he may keep it has closed source.
Does Yipit allows commericial usage????
I believe Yipit does allow commercial usage. Since they allow you to save your affiliate-id's for many of the deals sites they aggregate and they build those into the links their API returns to you. The python-twitter uses the Apache license I believe. Where does that lay in the spectrum?
I guess u can choose MIT Licence, if u want allow developers to include your work in their commercial software. You can choose GPL if you want developers to include work only if they are building open source software.:)??
I think GPL sounds good... but at the same time... people who use Yipit's API may be trying to create cool sites that generate a bit of revenue. Does that mean MIT is the way to go? Or is there some middle grounds...
its useful for developer who want create plugin, themes for wp. Localhost is very fast for end user than web server. so having wp installed in local machine has a gr8 advantage
thnk u :)