| >>I propose something like this You don't need to propose it. If its your code you can just do it. I would recommend that you clearly document (for yourself, if not publically) what your goals are. Is it money? Fame? Github stars? Users? Contributers? Something else? In order to determine if the license is a success you need to set goals, and then measure the results. Frankly, while this topic comes up frequently on HN, it's getting somewhat boring. I'm starting to come around to the viewpoint that you can either give your work away for free, or make a living, [1], but fundamentally those two goals are against each other. Sure you can make a living tangential to the work (docs, support et al), but of course that's taking time away from the code (so kinda just like a day job.) [1] as with lots of fields, like authors and music, there is a tiny sliver of people who manage it, and are held up as examples that it can be done. But I do applaud your creativity here, and i encourage you to experiment. My first thought is why bother to go Open at all? Presumably to meet some goal and it will be interesting to see if it meets that goal. I suspect you are looking for contributers (but I'm putting words in your mouth here) and I would suggest that the vast majority of projects get no contributers, regardless of license. |