Removing the PHP 5.4 plugin directory linting The…

Removing the PHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. http://php.net/manual/en/intro-whatis.php. 5.4 pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party directory linting

The plugin directory has linting against PHP 5.4 for quite some time now. It used to be a feature to prevent accidental bad commits, but today it’s now regarded by many as a bug.

We need to do one or more of the following:

  1. Upgrade the PHP linting to PHP-latest-stable (7.0)
  2. Upgrade the PHP linting to PHP 5.6 with a plan to move to PHP 7.0 (latest stable) and keep up with future releases
  3. Switch PHP linting to being a warning instead of a blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience.
  4. Remove the linting all together

Simply upgrading the linting to PHP 5.6 only kicks the can down the road, and still blocks people from using PHP 7 syntaxes in plugins (which is totally okay, if the plugin specifies that as a requirement).
Removing the linting seems like a bad idea, as I believe authors should still be notified they’re committing code that may not be compatible (Unfortunately we currently don’t do php fatal error prevention checks on plugin upgrades, so I’d like to retain it to prevent an unexpected WSOD).

So, I personally feel we should leave the linting at PHP 5.4 (which is what the majority of WordPress sites run today) and make it a warning, not a block.

In order to warn instead of outright blocking, the linting needs to be moved from the pre-commit hook to the post-commit hook and the script exiting with a error-level code, STDERR will then be sent to the client after the commit is made.

#plugins-svn, #svn

Hi could I have commit access to https…

Hi, could I have commit access to https://meta.trac.wordpress.org/browser/sites/trunk/wordpress.org/public_html/wp-content/themes/pub for #475-meta?
Thanks!

#meta, #svn

Could I please have commit access to http…

Could I please have commit access to https://meta.svn.wordpress.org/sites/trunk/wordpress.org/public_html/style in order to fix #555-meta?

#permissions, #svn

Can we turn off gitolite on svn1 Trying…

Can we turn off gitolite on svn1? Trying to clone anything on *.git.wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ over the HTTPHTTP HTTP is an acronym for Hyper Text Transfer Protocol. HTTP is the underlying protocol used by the World Wide Web and this protocol defines how messages are formatted and transmitted, and what actions Web servers and browsers should take in response to various commands. protocol (instead of the git protocol) ends up checking out the dead/never used WordPress for Android gitolite project.

I don’t see anything listening on *.git.wordpress.org, just android.git.wordpress.org, so I’m not sure what’s going on and it’s why I’m not doing it myself.

#git, #svn, #svn1

Could I please get commit access to https…

Could I please get commit access to https://meta.svn.wordpress.org/sites/trunk/profiles.wordpress.org/public_html/wp-content/ in order to fix #485-meta?

#permissions, #svn

Can I please get me commit access to…

Can I please get me commit access to https://meta.svn.wordpress.org/sites/trunk/global.wordpress.org/public_html/wp-content/ (for #471-meta and #472-meta)?

#global-wordpress-org, #meta, #permissions, #rosetta, #svn

Can I please have commit access granted to…

Can I please have commit access granted to bbpress.svn.wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ for the username ‘netweb’?

We’ve had the Uncle Ben talk, and @matt‘s looped in and given his nod of approval.

#bbpress, #commit, #svn

The SVN server appears to run PHP 5.4…

The SVNSVN Apache Subversion (often abbreviated SVN, after its command name svn) is a software versioning and revision control system. Software developers use Subversion to maintain current and historical versions of files such as source code, web pages, and documentation. Its goal is to be a mostly compatible successor to the widely used Concurrent Versions System (CVS). WordPress core and the wordpress.org released code are all centrally managed through SVN. https://subversion.apache.org/. server appears to run PHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. http://php.net/manual/en/intro-whatis.php. 5.4 now. For most repositories (notably coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.), we strongly benefit from pre-commit syntax checking to be PHP 5.2.

I think we need to install PHP 5.2 (old, I know) on this server. Then, a pre-commit hook can use php52 -l as needed.

There are a select few files (in our unit tests) that use 5.3 syntax, but I can patch around that in core’s pre-commit hook.

There are other options for verifying that files can be parsed (like a continuous integration procedure), but nothing beats an immediate commit rejection.

#php, #svn

Please give DrewAPicture rw for develop svn

Please give DrewAPicture rw for develop.svn.

#request, #svn

Could I please have write access to http…

Could I please have write access to https://meta.svn.wordpress.org/sites/trunk/wordcamp.org/public_html/wp-content/plugins/wc-post-types ?

I need to commit some changes to the [schedule] shortcodeShortcode A shortcode is a placeholder used within a WordPress post, page, or widget to insert a form or function generated by a plugin in a specific location on your site. for WCSF. They’d like it to go live today if possible.


ian@macenzie wc-post-types: svn ci
Authentication realm: Use your WordPress.org login
Password for 'iandunn':
svn: Commit failed (details follow):
svn: access to '[redacted]' forbidden
svn: Your commit message was left in a temporary file:
svn: '[redacted]/wp-content/plugins/wc-post-types/svn-commit.tmp'

#meta, #svn, #wc-post-types, #wordcamp-org