In a new post to his blog Pádraic Brady gives his take on the PHP-FIG (Framework Interoperability Group) and some of the decisions they've been making on PHP coding standards.
Anthony, whose views always make good reading, raises concerns about the way in which this group generates standards. He contrasts the current approach to RFC 2026 which defines the IETF's Internet Standards Process. [...] Where Anthony's arguments seemingly fall flat is that the FIG is not the IETF. The Framework Interoperability Group was founded to allow cooperating members to develop shared standards. It does not claim to be PHP's standards body and so there is no obligation for any PHP programmer to adopt their standards (unless they work on a member project obviously!).
He points out that the standards group's process has been slowly opening more and more ("by inches") and that the group, while made of up individuals, is more than just a collection of people - it's representatives for well-known Open Source projects.
In other words, the FIG is actually something really really good for PHP. PHP needs standards so we can make interoperability between various frameworks and applications a true reality. The hodgepodge of APIs and standards we've relied on to this point only serve to reinforce PHP's NIH obsession. [...] What the FIG should do, in my opinion, is clearly define its purpose and better document its bylaws/processes. [...] It really all comes down to better communication and pushing the community engage with the FIG.
没有评论:
发表评论