For the record, I believe you did the right thing. It's your work so you should use whichever license you like, and have users use your product on your own terms. It's just that passing non-OSI approved licenses as "Open Source" does tend to trigger strong responses.
OSS flies faster because people love the ability to use and reuse source code. But not everything must be OSS especially if the source code itself must be the source of income (thinking here of a mantra that's been repeated in HN several times, and which is very correct IMO: "Open Source is not a business model")
And yes you're right that it's better to go from restricted to open. The opposite direction has always been received with harsh criticism. Also you open yourself to the risk of a community forming around forking the project from the last commit that was OSS, and departing with their own thing form there. Unlikely, but technically possible.
OSS flies faster because people love the ability to use and reuse source code. But not everything must be OSS especially if the source code itself must be the source of income (thinking here of a mantra that's been repeated in HN several times, and which is very correct IMO: "Open Source is not a business model")
And yes you're right that it's better to go from restricted to open. The opposite direction has always been received with harsh criticism. Also you open yourself to the risk of a community forming around forking the project from the last commit that was OSS, and departing with their own thing form there. Unlikely, but technically possible.