All the talks of the @PHPers Summit are up on joind.in now!
So if you've been at the Summit, please take a moment and give the speakers some constructive feedback.
I have already linked the slides of my talk "Watch the Clock" there. So if you want to see the slides, hop over to https://joind.in/talk/cd546 and feel free to also leave some feedback so that I can improve for the next instalment. Thank you!
Hey #php folks of Frankurt and surrounding area: The #neos community is doing a code sprint this weekend at @decix (Hanauer Landstraße in Frankfurt). The main goal is preparation of the next release.
@heiglandreas@sarah I made this mistake once when I addressed a lawyer as Ms Surname in an email because I assumed their name was feminine, when it was literally the common Welsh version of unambiguously masculine John. I used Ms to avoid assuming martial status, but it never occurred to me they were Mr. Ever since, I only refer to people by the name they give me. 😂
The Bulgaria #PHP Usergroup (not on Mastodon) has an english online meetup on the 13th of March 19:15 Sofia Time (EET/UTC+2).
They will have Mateusz Charytoniuk with a talk aboit "The good the bad and the ugly parts of asynchronois PHP in the context of Swoole and Resonamce Framework"
Once you are happy with the content of the RFC in the wiki you'd then announce the RFC on the mailinglist and then discussion starts. And after at least 2 weeks of discussion voting can start and then after 2 weeks of voting you will know whether the idea found friends in the PHP-Ecosystem or not. 😁
Good luck and feel free to reach out when I can provide help!
@heiglandreas That's explains why the phrasing felt a little odd. But explaining the process to the general public certainly doesn't hurt either. There appears to be so much confusion about it.
@heiglandreas@wouterj@jaapio I know what a number of the concerns are that prompt things like this. That said, having been an author of several components where this happened, I can also say that it's hugely dispiriting when your work is essentially forked and modified only slightly, just so it can comply with the Symfony release lifecycle or its preferred API. You end up losing users and contributors, and any fixes or improvements on the symfony version never make it back to the original. 😐
@wouterj@heiglandreas@jaapio so perhaps we should implement a new flow. One where collaboration and communication is more central. To promote reuse and interoperability for libraries and frameworks.
Perhaps we should create a group, let's call is the Library Interoperability Group, LIG for short, where these things can be discussed.