> Oh, and the confusing name. Why is it called "Commons Clause"? Exactly. What is in effect crossing the boundary between open source and shared source (as Mic

> Oh, and the confusing name. Why is it called "Commons Clause"? Exactly. What is in effect crossing the boundary between open source and shared source (as Microsoft called the first source release of the .Netruntime) is made to sound like an afterthought. So, instead of AGPL (widely recognized as off-limits for corporate users), you could claim it's "Apache plus Commons Clause" which sounds nice as long as you squint really hard. It's ok to put software under a BSD-inspired or Apache-inspired noncommercial-only license - in fact plenty of people are doing this already - but it's disingenuous to use the name of the open source license you took inspiration from in the hope to profit from the open source halo for non-open-source software.