I’m literally laughing over this.
I’m being one of those ignored voices, that reclaims further support on the themes side from the Ghost organization. A few of use are not deverlopers (we may be able to maintain a server, but we are not good enough to translate the default themes and keep them up-to-date with the code updates happening in the source repos.
Issue here is the theme ecosystem is too inmature out there. Yo have right know two choices: Get a theme posted on Github, and trying to support (donate) the maintainer, so you don’t end with a theme without updates, or use Envato. And their legal terms are clear. If a user is charged while using the end-product (paywall), you need to use the extended license.
From License FAQ | ThemeForest
And from WordPress Themes & Website Templates from ThemeForest
It’s hard to be the first, but paywalls are still not popular as feature on CMSs. This is why is critical that the default themes are thought to be fit for content makers, instead of focusing on developers, that have more skills to remove translation strings than the other way around. Still, the crew from Ghost is more focused on developers, than content makers. A bit weird taking into account that their main product is a CMS (?)
Seems now that if you want to use a major feature of Ghost, you need to either use a default theme (only if you and your public speak english), trust a Github repo maintainer, or be ready to pay almost a grand. That’s not great.