The Zend Developer Zone has a new post with information about some updates from the WordPress project about what plugin authors must do to be compliant with the rules of the WordPress Plugin Directory.

After five years, the WordPress plugin team has updated the Plugin Guidelines. These are the guidelines that WordPress plugin authors must comply with to be included in the WordPress Plugin Directory.

The guidelines were soft-launched last month so that they could be vetted by the larger plugin developer community community. On November 1st, 2017, they were officially announced “Revised Guidelines Are Live” by Mika Epstein.

Overall, these guidelines are good. They are solid, well communicated and clear to anyone who reads them.

The ZDZ post focuses in on just two of the guidelines that were updated with a few brief thoughts in each:

• #4. Keep your code (mostly) human readable
• #9, The plugin and its developers must not do anything illegal, dishonest, or morally offensive

They point out that, while the intent is good for #9, the term "morally offensive" is very broad and could be interpreted in many ways by many different groups.

In a new post to his site Volker Dusch shares his thoughts about warnings in coding style checks (and how they differ from real errors).

When it comes to coding standards there is one rule that always makes me cringe when I stumble upon it: "Lines SHOULD be less than 120 chars long. If not a warning will be issued." Let me try to make a point why I consider WARNINGS in coding guideline checks hurtful.

He defines a warning first, so there's no confusion (something that should be done, but doesn't have to) and why he thinks there's not much of a place for them in the code guidelines. He suggests that, by having them, they take away time from the real issues, the errors. He notes that "should" rules on formatting shouldn't be added to your QA tools right away. Adding too many of these that spit out too many warnings (not errors) could just muddy the waters and make the developers more confused.

In a new article today on PHPMaster.com Robert Mariotti takes a look at standards and how important they can be when developing applications (both in following them and defining them correctly). It's not specifically targeted at PHP developers, but it does give some good food for thought.

As a long-time programmer, often with a staff of other programmers to watch over, I learned early in my career how important enforcing programming standards is in contributing to the overall success of a project. Not only do standards affect an individual’s production of code, but they ensure that anyone else who may contribute code later can do so with a reasonable expectation of consistency.

He defines the abstract concept of "coding standards" as rules or guidelines that should be followed based on the application. Sure, there's more global standards for things (PSR-0 anyone?) but your needs will always be different and more fine-grained than those can get. He recommends standardizing everything, possibly using one of the standards popular open source projects have already laid out as a base.

On the PHP-GTK Community site today, there's a call for speakers that's been issued for the upcoming Forum PHP 2007 happening in Paris (September 21st and 22nd).

They [the organizers of the conference] are looking for French speaking experts, who want to share their know-how and enthusiasm. This two day conference features one technical day, with the most advanced PHP techniques and a business day, with case studies and examples of successful projects..

The theme for the conference focuses on the latest generation of clients and databases in PHP. Those interested in submitting a talk should check out the guidelines the groups given including the deadline and what kinds of "perks" speakers get for presenting.

On the PHP-GTK Community site today, there's a call for speakers that's been issued for the upcoming Forum PHP 2007 happening in Paris (September 21st and 22nd).

They [the organizers of the conference] are looking for French speaking experts, who want to share their know-how and enthusiasm. This two day conference features one technical day, with the most advanced PHP techniques and a business day, with case studies and examples of successful projects..

The theme for the conference focuses on the latest generation of clients and databases in PHP. Those interested in submitting a talk should check out the guidelines the groups given including the deadline and what kinds of "perks" speakers get for presenting.

Zend has officially announced their Call for Papers for this year's Zend/PHP Conference and Expo (2007):

2007 marks the third anniversary of the Zend/PHP Conference and Expo. Focused on the PHP, the world's fastest growing web development language, this year’s conference is guaranteed to again be bigger and better than ever.

The 2007 conference will bring together PHP practitioners and business managers from around the world for three days of exceptional presentations and outstanding networking.

If you're thinking about presenting this year, check out the Guidelines which includes the different areas they're looking for submissions in (including "How has PHP impacted your business – Revenue Growth, Customer Satisfaction, Time", "PHP/Java/.NET mixing, matching or choosing", "Business Intelligence and PHP applications" and much more.

The conference this year will be happening from October 8th-11th at the Hyatt Regency San Francisco Airport out in Burlinggame, CA.

Zend has officially announced their Call for Papers for this year's Zend/PHP Conference and Expo (2007):

2007 marks the third anniversary of the Zend/PHP Conference and Expo. Focused on the PHP, the world's fastest growing web development language, this year’s conference is guaranteed to again be bigger and better than ever.

The 2007 conference will bring together PHP practitioners and business managers from around the world for three days of exceptional presentations and outstanding networking.

If you're thinking about presenting this year, check out the Guidelines which includes the different areas they're looking for submissions in (including "How has PHP impacted your business – Revenue Growth, Customer Satisfaction, Time", "PHP/Java/.NET mixing, matching or choosing", "Business Intelligence and PHP applications" and much more.

The conference this year will be happening from October 8th-11th at the Hyatt Regency San Francisco Airport out in Burlinggame, CA.