The preferred term nowadays is "protective". You are given some constraints, but those are intended to protect the ability of people to keep using software from

The preferred term nowadays is "protective". You are given some constraints, but those are intended to protect the ability of people to keep using software from the project in the long term for any purpose. If the net effect is to increase the overall freedom that people have for using the project, that is not necessarily more restrictive, other than in a local way. Metaphorically speaking, being able to sell yourself into slavery is not something that increases your freedom, and forbidding it isn't "more restrictive".