Skip to content

User Group Code of Conduct

Introduction

As you may know, I'm co-organizing two user groups, PHP User Group Rheinhessen and RheinMainJS, and although we've fortunately never had any complaints about or problems with abusive behavior or harassment, I would like to establish a Code of Conduct for these user groups.

Others have done this before: AmsterdamPHP has a Code of Conduct (CoC). phpMiNDS in Nottingham has one. Several user groups in Berlin support a CoC. A lot of conferences both in the PHP and JS communities have a Code of Conduct, e.g. phpDay and JSConf Europe among many others.

A painting of two men. The man at the center is looking off to his right while drawing a symbol with his right hand. His left hand is resting on a page in a book. He is wearing a robe with a hood. The man on the right is looking towards the front and is wearing a long-sleeve red shirt with a black jacket. Several writing utensils and books are on a table with a green tablecloth in the front of the image.

"User Group Code of Conduct" vollständig lesen

Craft Beer in Kosovo

A couple of months ago, I had the chance to spend some days in Europe's youngest country: Kosovo. Depending on whom you ask, of course, it is or isn't a sovereign state. But since Germany recognizes it as independent state, I will treat it as such. It's complicated.

Unfortunately, I did not have as much time to travel the country as I would have liked, but I was keen to learn about local food and drinks, among a million other things (another blog post might follow). Also, as it happens so often, I caught a cold on my first day of travelling. Therefore I could not dive into as many activities as I had planned to.

Nevertheless, upon arriving in Pristina, Kosovo's capital, I was craving good food - and good beer. For I had searched the Internets before I left and I knew there was lots to discover. I even found the website of a craft brewery, yet was unsure how easy it would be to find their beer.

"Craft Beer in Kosovo" vollständig lesen

The most frequently used PHP functions on GitHub

While preparing the April meetup of the PHP User Group Rheinhessen, Christian came up with an idea: Let's take a look at one of the least used and most "exotic" internal functions of PHP and discuss them. Soon, the question arose, "which functions are only infrequently used?" - A: "Let's take a look at PHP repos on Github!"

After studying Github's Search API, it soon became clear that it's not possible to search all PHP repositories for functions this way. What I had to do was to write a simple crawler that POSTed search queries to the search form on the Github website (while respecting the rate limit, of course).

The results were parsed and saved to a JSON file, and I built a bar chart that visualizes the collected data:

Screenshot of http://mattsches.github.io/php-funcs-frequency/ where the findings are presented

"The most frequently used PHP functions on GitHub" vollständig lesen

VulnerabilitiesBundle for Symfony2

Only two days after I pushed the first version of my VersionEyeBundle for Symfony2 to GitHub, Fabien Potencier announced SensioLab's new Security Advisories Checker. This service work quite similar to VersionEye, but instead of uploading your composer.json file your composer.lock file is required to figure out which dependencies are really installed - and if there are any known security issues.

VulnerabilitiesBundle for Symfony2 in Web Debug Toolbar
This is what it looks like in the toolbar

SensioLabs have an upload form in the browser, but conveniently offer an API, too. And, of course, the code of their security-checker is on GitHub. So what could be more natural than to add the results of the security check to the Web Profiler Toolbar right next to all the other useful information? Right. I wrote a second bundle, called VulnerabilitiesBundle, that displays security advisories in the toolbar and the profiler view.

VulnerabilitiesBundle for Symfony2 in Profiler
And this is the Profiler page.

Please keep in mind that this is an early development version that is only intended for use in DEV environments (even if it will be stable someday). It just doesn't make sense on production servers. Feel free to fork, test, and report any issues you encounter. Of course, contributions in the form of pull requests, are more than welcome :-)

VersionEyeBundle for Symfony2

At last week's Webmontag Frankfurt (?), Robert Reiz talked about continuous updating of dependencies with VersionEye. VersionEye, in its own words, is a

cross-platform search engine and crowdsourcing app for open source software libraries.

Essentially, the service tracks more than 170.000 libraries in languages like Java, Ruby, PHP, Python, and many more, and monitors any updates to those libs. Registered users can keep track of their projects and the libraries used in these projects. If any updates occur upstream, VersionEye sends out a mail. As a developer, you don't have to manually check on all the GitHub repositories anymore, VersionEye does that for you.

VersionEye also allows you to create beautiful graphs like this one here on the right. It also lists all the licenses of all the libraries used in your project, an let's you see which libraries you use most often.

Using it with PHP

Adding a PHP project to the service couldn't be simpler (if you use Composer, which you should!): Just upload your composer.json to VersionEye, and you're all set up. The same goes for project files like package.json (node.js), requirement.txt (Python Package Index), pom.xml (Maven) or Ruby Gemfiles. You can also connect VersionEye to your GitHub account, and it will notify you of outdated dependencies in your repositories.

Robert also said that there already is a VersionEye module for ZF2 and the ZendDeveloperTools that calls the VersionEye JSON API to track dependencies. However, I could not find a Symfony2 bundle with this functionality. So I wrote one.

"VersionEyeBundle for Symfony2" vollständig lesen