body: A software product (a web service) is being developed.
  
  
  In essence, I want the software code to be hosted publicly on GitHub. Anyone should be able view, download, modify, use for personal use, and contribute back with improvements as they want, meaning most of the "open source" principles - but not all, as...
  
  
  ...Only I may make commercial usage of the software code.
  
  
  But the more I search on the Internet, the more confused I get about this topic. According to me, **this situation has to be a common desire by developers or organizations**, but yet it seems hard to find a clear answer to exactly how an organization can achieve this.
  
  
  I have a hard time believing that each person or organization has to call in a lawyer that writes a custom license each time, right? In other words, reinventing the wheel all the time.
  
  
  Isn't there a straightforward, popular, or common license or license model that achieves this?
  
  
  Perhaps "dual licensing" is the only way to achieve this? If so, are there any examples of GitHub projects that do this?
  
  
  
title: What (combination of) licenses is popular for public/shared proprietary software (“Feel free to contribute, but only we can make commercial use”)?