WP Tavern › Forums › Create Topic
George Stephanis So you’re telling me I can submit a plugin or theme that “phones home” as long as I use the same process Jetpack uses for connecting users to Automattics servers? That is considered asking permission according to the guidelines? Yes. Informed Consent. Did you even read the linked guidelines? If I could have had a button to connect them to my server then I would have built this two years ago, but again everyone told me I couldn’t so I didn’t. So either you’re wrong, or the .org admins and core contributors I spoke to were incorrect which is a problem in and of its self. I’m not wrong, and the .org admins and core contribs aren’t wrong either. It is prohibited, just not under the rule I’d been referring to — that’s actually prohibited under Rule 8 — https://wordpress.org/plugins/about/guidelines/ No sending executable code via third-party systems. Use of third-party systems is acceptable in a service-client type of model, but sending actual PHP or other executable code over the network is considered a security risk. Executing outside code like this is not allowed except for specific and very carefully considered cases (such as during upgrades, for example). So you can’t use code in the repository to install code that is not in the repository — be it from GitHub or a private commercial server. It’s a security precaution. RE: theme wranglers — it’s clear you’re confused. So perhaps get things straight in your own head before making accusations. If you’re going to spend the money to assemble a theme dream team, then why aren’t they developing a new generation theme framework for all future WordPress themes? Because there is already a theme framework — it’s called the WordPress Theme API. Or did you mean a base theme framework more akin to Underscores? Or you know, improving how themes, and child themes are handled by WordPress? I’m pretty sure some of our folks are regular core contributors and work on that sort of thing. How about a CSS framework for the entire WordPress project? Are you just throwing out buzzwords now? At the very least why aren’t they regularly producing ThemeForrest quality designs and staying on top of design trends? I’d put the code quality of any Automattic theme up against any ThemeForest theme, any day of the week. And I think we’re doing okay design wise. Finally, regarding the featured themes on .org, again you seem to be conflicted. You’re arguing both that what you’re reading as ‘pay to play’ was bad, and then in the same breath that taking it away was bad and killed your business. Honestly, wtf^^? Which way do you want it?
George Stephanis
So you’re telling me I can submit a plugin or theme that “phones home” as long as I use the same process Jetpack uses for connecting users to Automattics servers? That is considered asking permission according to the guidelines?
Yes. Informed Consent. Did you even read the linked guidelines?
If I could have had a button to connect them to my server then I would have built this two years ago, but again everyone told me I couldn’t so I didn’t. So either you’re wrong, or the .org admins and core contributors I spoke to were incorrect which is a problem in and of its self.
I’m not wrong, and the .org admins and core contribs aren’t wrong either. It is prohibited, just not under the rule I’d been referring to — that’s actually prohibited under Rule 8 — https://wordpress.org/plugins/about/guidelines/
No sending executable code via third-party systems. Use of third-party systems is acceptable in a service-client type of model, but sending actual PHP or other executable code over the network is considered a security risk. Executing outside code like this is not allowed except for specific and very carefully considered cases (such as during upgrades, for example).
So you can’t use code in the repository to install code that is not in the repository — be it from GitHub or a private commercial server. It’s a security precaution.
RE: theme wranglers — it’s clear you’re confused. So perhaps get things straight in your own head before making accusations.
If you’re going to spend the money to assemble a theme dream team, then why aren’t they developing a new generation theme framework for all future WordPress themes?
Because there is already a theme framework — it’s called the WordPress Theme API. Or did you mean a base theme framework more akin to Underscores?
Or you know, improving how themes, and child themes are handled by WordPress?
I’m pretty sure some of our folks are regular core contributors and work on that sort of thing.
How about a CSS framework for the entire WordPress project?
Are you just throwing out buzzwords now?
At the very least why aren’t they regularly producing ThemeForrest quality designs and staying on top of design trends?
I’d put the code quality of any Automattic theme up against any ThemeForest theme, any day of the week. And I think we’re doing okay design wise.
Finally, regarding the featured themes on .org, again you seem to be conflicted. You’re arguing both that what you’re reading as ‘pay to play’ was bad, and then in the same breath that taking it away was bad and killed your business. Honestly, wtf^^? Which way do you want it?
Name *
Email *
Website:
Topic Title (Maximum Length: 80):
Forum: — No forum —AI and WordPress Articles Blocks Showcase Discussions Events Introductions Jobs and Working in WordPress Podcast Episodes Site and Block Editor
Enter your email address to subscribe to this blog and receive notifications of new posts by email.
Email Address
Submit
Enter the destination URL
Or link to existing content
