Hey everyone! For the many of you that don't know me, I'm Michael Heap and I'm based just outside of London in England. Thus far I've had very little direct involvement in the FIG, but have been watching from the sidelines for many years. After the vote for FIG 3.0 passed, my desire to get involved grew as it showed that the majority of projects wanted to focus on solving problems rather than arguing amongst themselves.
I've been involved in the PHP community since 2009 when I had the opportunity to present my first conference talk at PHPNW09 in Manchester. Since then I've been hooked - travelling around to various usergroups and conferences as both an attendee and a speaker. As far as open source goes, my contributions have been smaller than I'd have liked. Instead, I've spent my spare time writing books[1] and preparing conference talks[2]. There have been a few contributions to projects such as Joind.in and PHPDocumentor, as well as Silex service providers but nothing as significant as other candidates. *Why I'm a good candidate for the CC:* I'm not deeply involved in various open source projects, and I've not been a vocal contributor to the FIG thus far. I'm not your typical FIG member. Instead,I've spent time working with companies that want to standardize and adopt new technology, but don't know where to start. By joining the core committee, I believe that I can help by providing practical input that will help everyday companies adopt new PSRs. If you ask those that I've worked with to describe my working style, they'd tell you that it's "strong beliefs, loosely held". For me, the end result isn't important. Ensuring that all of the relevant questions have been asked and answered is. This makes sure that we arrive at solutions that are robust and applicable for all. *What I'd like to accomplish in the CC:* Contributing to the core committee is one of the ways I'd like to contribute back to the community. A lot of my day to day work is with companies that want to adopt the standards recommended by the FIG, but are working with internal frameworks that are almost a decade old. Ensuring that the recommendations proposed are suitable for slow moving companies with a desire to progress is a big part of my drive to join the core committee. The majority of developers aren't a part of the community, they don't attend conferences and have never heard of the FIG. Making sure their requirements are represented in a way that makes it easier for them to start integrating the FIG recommendations into their day to day work is something I feel strongly about. [1] https://www.amazon.co.uk/dp/1484216601 [2] http://michaelheap.com/talks -- You received this message because you are subscribed to the Google Groups "PHP Framework Interoperability Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/0f256f8c-6dd3-4257-b51d-ab123915828e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
