Below I list the jetpack "feature" for enabling modules that "don't require a WordPress.com" connection. And rule number 6 that says "you cannot "cripple" functionality in the plugin and then ask for payment or provide a code to unlock the functionality."
So I'm confused, is requiring a wordpress.com login not the same things as requiring a code?
Does jetpack not violate the spirit of the rules of the repo by requiring wordpress.com login?
So what does this suggest that a person should be able to do if there is not a double standard here.
You should be able to provide a plugin who's functionality is only enabled by logging into a third party service.
So clearly there are components of jetpack that are services. But other components "modules" are not.
So is the answer that you have to have at least one service component and then you can gate the functionality of the rest of the your plugins by just bundling theme alongside the plugin that requires a service.
Can someone explain to me why this is not a double standard? Can I make a jetpack style plugin bundle and require that someone has an account with me to use it, and host that on the repo, or not?
Enhancement: Development Mode: Define the JETPACK_DEV_DEBUG constant to true to enable an offline mode for localhost development. Only modules that don't require a WordPress.com connection can be enabled in this mode.
6. Trialware is not allowed in the repository. It's perfectly fine to attempt to upsell the user on other products and features, but a) not in an annoying manner and b) not by disabling functionality after some time period. Similarly, you cannot "cripple" functionality in the plugin and then ask for payment or provide a code to unlock the functionality. All code hosted by WordPress.org servers must be free and fully-functional. If you want to sell advanced features for a plugin (such as a "pro" version), then you must sell and serve that code from your own site, we will not host it on our servers.