The PHP Rountable podcast, hosted by PHP community member Sammy K Powers, has posted their latest episode focusing on GDPR for developers. In it he's joined by guests Michelangelo van Dam and Wim Godden.

The first major piece of legislation that we've seen attempt to regulate how our personal information is handled on the web is the General Data Protection Regulation (GDPR).

Today we chat with some panelist who have gone down the GDPR-compliance road and they are going to help us PHP devs understand how the GDPR affects us and what we can do to make sure our technology stack is as GDPR-compliant as possible.

You can catch this latest episode in a few different ways: either using the in-page audio/video player, watching the video directly on YouTube or grabbing the audio file directly. If you enjoy the show, be sure to follow them on Twitter and subscribe to their feed to get updates on when future shows are released.

That Podcast, with hosts and PHP community members Beau Simensen and Dave Marshall, has posted their latest episode: Episode #50 - Episode 50: The One Where We Talk to Shawn about Event Sourcery, CQRS, Event Sourcing and GDPR

In this episode, Dave and Beau talk to Shawn McCool about his experiences with CQRS and Event Sourcing, the GDPR, and his recently revealed open source project event sourcery.

Event sourcery is a PHP CQRS/ES library with a core principle of keeping it simple, while providing some more advanced technical capabilities, like keeping personal data out of the immutable event streams.

You can listen to this latest episode either through the in-page audio player or by downloading the mp3 of the show directly. If you enjoy the show be sure to subscribe to their feed and follow them on Twitter for updates on when new shows are released.

With the GDPR (General Data Protection Regulation) deadline looming on the horizon, there's no better time to make your applications compliant. Christoph Rumpel, a development lead on the Laravel-based Botman chatbot software, as posted a guide to help you ensure your chatbots are compliant.

Only one month left until the GDPR will take effect and people are already freaking out. If you haven't made yourself familiar with this topic, you need to do it now! This article will give you a summary of what you need to know and provide you with steps to make your chatbots GDPR compliant.

His article starts with a brief definition of what GDPR is and what it impacts. He then goes through and lists out some of the key changes that will have to be made to be in compliance including:

• Increased Territorial Scope
• Consent
• Process Personal Data
• Documentation

With those basics out of the way, he gets into the application of them in chatbot software. To make it easier he's come up with a listing of eleven questions to ask or steps to take to get you closer to compliance. For each he briefly describes it and provides some screenshots of the output from the bot that would be compliant.

On the Evozon blog there's a post that provides "a brief reality check to developers about GDPR" and how it effects them and their applications. GDPR (General Data Protection Regulation) is a regulation passed in Europe that enforces certain requirements about personal data and how it should be handled.

If you`re reading this, it means you`ve already heard about it or you`re about to receive some flash-news: there`s a new all-encompassing data privacy regulation in the EU. Ready or not, 25th of May 2018, the date when the General Data Protection Regulation (GDPR) becomes effective, will wait for nobody. If there’s any buzz around it, it`s because of a good reason: businesses will have to comply, software will have to evolve.

While there is still some uncertainty around certain parts, the article goes through some things you can do to help you prepare and make your application compliant including:

• discovering and documenting the purpose of the data that is being collected
• providing clear notification of data collection for the user
• define retention periods and deletion policies
• tracing any changes that happen with the data

The article does a good job providing a "checklist" of sorts you can use to ensure you're compliant. Of course, it's by no means an actual method of compliance but it does provide a good list to guide you in the right direction.