certera

Why do you want more users? Are you wanting to build your own recognition in the UX space?

I hope I don't sound snarky. I just want to better understand your thoughts and motives.

What's your intention here? Just want to get more users, looking for help, trying to make money, etc.

Saw this from the early adopter thread. Looks really well build.

How much time dedicated over the decade+?

What are your thoughts on how well these kinds of tools generate html? Brings me back to Dreamweaver.

If it dies, there can be a point where the maintainer can re-license under more open terms, no? Until that point, the work and contributions are ensured to help sustain the creator.

I'm planning on releasing my project under similar terms. I'm not particularly interested in community contributions, but rather for there to be trust in ensuring privacy and security. Sometimes, there isn't a one-size-fits-all with the available OSI licenses and I appreciate what op has done to do his best to find what works well for him and the community.

I'm not sure sure it will go "badly". I believe there's a fundamental issue with a class of software applications that the current OSI licenses don't do much for. Let me clarify that statement with some examples. If you're a developer of an "open source" library or database engine, you have great OSI licenses available to use. The consumers of your work will either open source their work or purchase a license (i.e. dual-licensing). If, however, you're creating a CMS or some standalone tool (like GIMP, for example), you're left to go down the road of open core (typically). So, the alternative here is to choose a license that's conducive of being able to monetize without depending on donations or support contracts.

I think developers should pick a license that makes sense for them, not necessarily for the benefit of others. What is important though, is that some thought is taken and to try it out. You can always go more permissive later.

I'm working on something that I want to monetize, but the OSI licenses aren't helpful for the kind of application I'm working on. I'm leaning towards a similar licensing structure and have been spending a great deal of time thinking about this and I hope to have more discussions on this very topic as it's extremely helpful for everyone.

edit: typos

I love how you licensed it. I'm seeing a trend in how developers are being thoughtful about the licensing and how it will help monetize their efforts later. Excited to see how this goes.

I really enjoyed this article. It's still as applicable today as when it was written. Not everything needs to be a SaaS.

I agree. I'm developing something, and while a subscription is attractive to me, I feel it's not correctly aligned to what users deserve.

I'm burned out by all of these subscriptions and trying to go back to my "roots".