Drew Jaynes

I would not consider this to be a relevant concern to this project or WordPress. It's every author's own responsibility to ensure they aren't infringing copyrights in content they publish....

@danielbachhuber Feel free to get a legal opinion. I would argue that if it hasn't been a problem up to now that it probably wouldn't be going forward.

I agree with @krogsgard. Sideload the full-size image, sure, but then only insert the 'large' image size. We'd probably have to make that image size filterable though.

I'd say the ideal situation would be to persist anything that's in the editor and/or title field while still enabling the ability to scan URL(s)/import content.

FWIW, if you follow the WP core [inline documentation standards for PHP](https://make.wordpress.org/core/handbook/best-practices/inline-documentation-standards/php/), you can use the official [phpdoc-parser](https://github.com/WordPress/phpdoc-parser) plugin to parse your hook docs into a WordPress site.

Welp, I'm not sure how I unassigned @oherman since I'm not a collaborator here ... but, whoops!

Just hit this too. Probably could get away with keeping it by just wrapping it in a `function_exists()` call: ```php function wpsc_serialize_shopping_cart() { global $wpsc_cart; if ( is_admin() && !...

PR: #2316

@GaryJones Which part specifically are you seeking an opinion on? I can get on board with adding file headers to the empty indexes purely for standardization sake if that's what...

@GaryJones Also, I disagree with your [assertion](https://github.com/WordPress-Coding-Standards/WordPress-Coding-Standards/issues/451#issuecomment-139911834) that we aren't in fact talking about average users. The whole point of the indexes is to prevent listing on poorly configured user...