[bruce511]

I'm not 100% sure I understand what you mean by "owning your feature backlog."

But sure, if you dont want your staff to become your competitors then don't put tour code under a license that puts that carrot in front of them.

[growse]

> I'm not 100% sure I understand what you mean by "owning your feature backlog."

If you're stewarding the project, you have the sole authority over over which features land when. You can prioritise and drag (or even reject) PRs to suit your business case and your customers. Everyone else has to accept features when you choose to release them, or fork.

This is a massive competitive advantage, if used effectively.