<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en_US"><generator uri="https://jekyllrb.com/" version="3.9.0">Jekyll</generator><link href="https://phpqa.io/feed.xml" rel="self" type="application/atom+xml" /><link href="https://phpqa.io/" rel="alternate" type="text/html" hreflang="en_US" /><updated>2020-08-12T15:29:55+00:00</updated><id>https://phpqa.io/feed.xml</id><title type="html">PHP Quality Assurance</title><subtitle>A community managed website about PHP Quality Assurance</subtitle><author><name>Bart Reunes</name></author><entry><title type="html">What is the internet for?</title><link href="https://phpqa.io/posts/2018/06/30/what-is-the-internet-for.html" rel="alternate" type="text/html" title="What is the internet for?" /><published>2018-06-30T00:00:00+00:00</published><updated>2018-06-30T00:00:00+00:00</updated><id>https://phpqa.io/posts/2018/06/30/what-is-the-internet-for</id><content type="html" xml:base="https://phpqa.io/posts/2018/06/30/what-is-the-internet-for.html">&lt;p&gt;Recently I noticed a change on the old PHP QA Tools domain &quot;phpqatools.org&quot;.&lt;/p&gt;

&lt;!--more--&gt;

&lt;p&gt;Where before was a simple page for PHP QA tools, now it is telling you to use virtual reality… for porn.
So I took down all the links to the old page. And if you still have a link to it,
you might want to update it to &lt;a href=&quot;&quot;&gt;https://phpqa.io&lt;/a&gt;. But then again, that's totally up to you!&lt;/p&gt;

&lt;p&gt;After all, I guess that &lt;a href=&quot;https://www.youtube.com/watch?v=TcN5CxO86qI&quot;&gt;Avenue Q song&lt;/a&gt; was right all along.&lt;/p&gt;</content><author><name>MetalArend</name></author><summary type="html">Recently I noticed a change on the old PHP QA Tools domain &quot;phpqatools.org&quot;.</summary></entry><entry><title type="html">About Composer and PHARs</title><link href="https://phpqa.io/posts/2017/06/18/about-composer-and-phars.html" rel="alternate" type="text/html" title="About Composer and PHARs" /><published>2017-06-18T00:00:00+00:00</published><updated>2017-06-18T00:00:00+00:00</updated><id>https://phpqa.io/posts/2017/06/18/about-composer-and-phars</id><content type="html" xml:base="https://phpqa.io/posts/2017/06/18/about-composer-and-phars.html">&lt;p&gt;All projects have an installation section now.&lt;/p&gt;

&lt;!--more--&gt;

&lt;p&gt;For now, however, only the official instructions are visible, as close as possible as they are mentioned
on all the websites, repositories, wikis and readme files, and only in the three most common ways:
using &lt;a href=&quot;https://getcomposer.org/&quot;&gt;Composer&lt;/a&gt;, &lt;a href=&quot;https://git-scm.com/&quot;&gt;git&lt;/a&gt; and/or &lt;a href=&quot;https://phar.io/&quot;&gt;PHAR&lt;/a&gt;s.
There are more obscure ways mentioned now and then, and they will be added soon, for completeness sake,
but after today, I certainly am hoping at least one of the PHAR tools will make it through.&lt;/p&gt;

&lt;p&gt;Cause yes, as &lt;a href=&quot;https://twitter.com/shochdoerfer&quot;&gt;Stephan Hochdörfer&lt;/a&gt; mentioned,
we &lt;a href=&quot;https://blog.bitexpert.de/blog/solving-the-require-dev-problem/&quot;&gt;do have a problem&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;I certainly would love to add more secure instructions on how to download PHARs and packages in a verifiable way.&lt;/p&gt;

&lt;p&gt;Let the era of a lovechild between &lt;a href=&quot;https://getcomposer.org/&quot;&gt;Composer&lt;/a&gt; and &lt;a href=&quot;https://phar.io/&quot;&gt;PHIVE&lt;/a&gt; begin!&lt;/p&gt;

&lt;p&gt;Sincerely,
your buzzard.&lt;/p&gt;</content><author><name>MetalArend</name></author><summary type="html">All projects have an installation section now.</summary></entry><entry><title type="html">Welcome</title><link href="https://phpqa.io/posts/2017/06/03/welcome.html" rel="alternate" type="text/html" title="Welcome" /><published>2017-06-03T00:00:00+00:00</published><updated>2017-06-03T00:00:00+00:00</updated><id>https://phpqa.io/posts/2017/06/03/welcome</id><content type="html" xml:base="https://phpqa.io/posts/2017/06/03/welcome.html">&lt;p&gt;Welcome to the new PHP Quality Assurance website.&lt;/p&gt;

&lt;!--more--&gt;

&lt;p&gt;A few weeks ago I noticed that the &lt;a href=&quot;https://web.archive.org/web/20161107075017/http://phpqatools.org:80/&quot;&gt;PHP QA Tools website&lt;/a&gt;,
curated by &lt;a href=&quot;https://sebastian-bergmann.de/&quot;&gt;Sebastian Bergmann&lt;/a&gt;, closed down somewhere late 2016.
However simple the setup of the onepager was, I felt like I lost something.
For years, it was one of those pages I kept mentioning to new and upcoming PHP developers.
Every time I saw people writing PHP code that could use a little magic touch, there were two pages I mentioned:
&lt;a href=&quot;http://www.phptherightway.com/&quot;&gt;PHP The Right Way&lt;/a&gt;, and the QA Tools page.&lt;/p&gt;

&lt;p&gt;But now the &lt;a href=&quot;https://web.archive.org/web/20161107075017/http://phpqatools.org:80/&quot;&gt;distinct tiles&lt;/a&gt;
were replaced by a &lt;a href=&quot;https://web.archive.org/web/20170510161544/https://phpqatools.org&quot;&gt;sec white page with a formal RIP notice&lt;/a&gt;,
forwarding any lost souls to an extensive and mostly up-to-date list
in &lt;a href=&quot;https://github.com/exakat/php-static-analysis-tools&quot;&gt;a public Exakat repository&lt;/a&gt;.
I had encountered that list before, but however extensive and well maintained,
nobody had ever noticed that a &lt;a href=&quot;https://github.com/exakat/php-static-analysis-tools/issues/15&quot;&gt;few tools were even present multiple times&lt;/a&gt;.
It is a long list, and there are many awesome tools to be found in it,
but I was wondering if any new developer I would send there would even try to digg until they would reach the good stuff.&lt;/p&gt;

&lt;p&gt;Meanwhile, in the last few months, I had been looking into Quality Assurance tools for the projects
my colleagues and I are working on. And it was a very welcome surprise to see how many good tools are out there.
As I had been using &lt;a href=&quot;https://www.docker.com/&quot;&gt;Docker&lt;/a&gt; for development for quite some time, it was clear to me
to start using very basic &lt;a href=&quot;https://alpinelinux.org/&quot;&gt;alpine&lt;/a&gt; images to test-run many of those tools against our codebases.
It was a success.
When our team started moving our projects to &lt;a href=&quot;https://gitlab.com/&quot;&gt;GitLab&lt;/a&gt; and it's pipelines,
the images could be plugged in very easily, and since then code reports would be available for every single commit.
Even &lt;a href=&quot;https://scrutinizer-ci.com/&quot;&gt;Scrutinizer&lt;/a&gt;, however awesome, could not keep up with the insights we got
from all those amazing tools that were readily available for anyone who wanted to use them.&lt;/p&gt;

&lt;p&gt;So last week, I moved 20something Dockerfiles to a &lt;a href=&quot;https://hub.docker.com/u/phpqa/&quot;&gt;phpqa organisation&lt;/a&gt;
on &lt;a href=&quot;https://cloud.docker.com/&quot;&gt;DockerCloud&lt;/a&gt;. Those are images for several PHP related Quality Assurance tools,
ready to use. But they need documentation. Desparately.
(Not in the least because using DockerCloud will not provide any details to DockerHub.)
Since we gave a &lt;a href=&quot;https://www.slideshare.net/christophevg/git-hub-pages-69001172&quot;&gt;Jekyll and GitHub Pages workshop&lt;/a&gt;
for students with &lt;a href=&quot;https://www.meetup.com/PHP-Leuven-Web-Innovation-Group/&quot;&gt;PHP Leuven&lt;/a&gt; recently,
it was time to try it myself. After adding some &lt;a href=&quot;https://www.cloudflare.com/&quot;&gt;Cloudflare&lt;/a&gt; magic and HTTPS sprinkles,
and with a bit of dry and dusty Javascript twists, here it is.
For now, there's not even any images documentation to be found on it.
But there is a slowly growing &lt;a href=&quot;https://phpqa.io/index.html&quot;&gt;list of tools&lt;/a&gt; that you can search for and filter on,
and there are lots of plans for a lot more simple functionality.&lt;/p&gt;

&lt;p&gt;At least now, I have a new webpage to send those PHP code quality haters to. I hope you will too.&lt;/p&gt;

&lt;p&gt;Sincerely,
your buzzard.&lt;/p&gt;</content><author><name>MetalArend</name></author><summary type="html">Welcome to the new PHP Quality Assurance website.</summary></entry><entry><title type="html">Quality Assurance in PHP projects</title><link href="https://phpqa.io/posts/2010/11/11/quality-assurance-in-php-projects.html" rel="alternate" type="text/html" title="Quality Assurance in PHP projects" /><published>2010-11-11T00:00:00+00:00</published><updated>2010-11-11T00:00:00+00:00</updated><id>https://phpqa.io/posts/2010/11/11/quality-assurance-in-php-projects</id><content type="html" xml:base="https://phpqa.io/posts/2010/11/11/quality-assurance-in-php-projects.html">&lt;p&gt;Quoting from &lt;a href=&quot;https://web.archive.org/web/20101111195138/http://qualityassuranceinphpprojects.com:80/pages/tools.html&quot;&gt;the original website&lt;/a&gt;:&lt;/p&gt;

&lt;!--more--&gt;

&lt;div class=&quot;card&quot;&gt;
    &lt;div class=&quot;card-body&quot;&gt;
        &lt;h2 class=&quot;card-title&quot;&gt;The PHP Quality Assurance Toolchain&lt;/h2&gt;
        &lt;p&gt;Sebastian Bergmann's presentation on &quot;The State of QA Tools for PHP&quot; at the FrOSCon 2009 conference raised demand for an overview page of PHP quality assurance tools.&lt;/p&gt;
        &lt;p&gt;This page is a first attempt of creating such an overview.&lt;/p&gt;
    &lt;/div&gt;
&lt;/div&gt;</content><author><name>Sebastian Bergmann and Stefan Priebsch</name></author><summary type="html">Quoting from the original website:</summary></entry></feed>