fig-tlo

Many thanks to Andrew Carter, Younes Rafie, and Scott Molinari for peer reviewing this post!

非常感谢Andrew Carter ， Younes Rafie和Scott Molinari同行评审了这篇文章！

The Polish writer, Henryk Sienkiewicz, was awarded the 1905 Nobel prize for Literature for his epic novel Quo Vadis, which is a Latin phrase meaning “Where are you going?”. In the face of any dilemma, a brief pause and redefinition of one’s goals may be therapeutic.

波兰作家亨里克·西恩凯维奇(Henryk Sienkiewicz)因其史诗小说《 Quo Vadis》而获得1905年诺贝尔文学奖。 面对任何困境，短暂的停顿和重新定义自己的目标可能会有所帮助。

The PHP Framework Interoperability Group (PHP-FIG) has come of age. With the acceptance of more PHP Standards Recommendations (PSRs), PHP has attracted further positive attention and admiration of the programming community. PSRs governing coding standards, coding style guides, autoloading, logging, caching and HTTP messages have been accepted.

PHP框架互操作性组 (PHP-FIG)已经成熟。 随着越来越多的PHP标准建议书 (PSR)的接受，PHP引起了编程社区的进一步积极关注和赞赏。 管理编码标准，编码样式指南， 自动加载 ， 日志记录 ，缓存和HTTP消息的PSR已被接受。

Other proposals at different stages of draft and review cover hypermedia links, PHPDoc standard, event management, caching and security issues. There’s even one on Huggable Interfaces (PSR-8) which, among other things, talks about huggable objects and mutually-assured hugging!

在起草和审核的不同阶段的其他建议包括超媒体链接，PHPDoc标准，事件管理，缓存和安全性问题。 Huggable Interfaces(PSR-8)上甚至还有一个，其中涉及可拥抱对象和相互确保的拥抱！

However, the future isn’t as bright as painted, as a recent ruckus within the organization has thrown its continuing existence under doubt.

但是，未来并不像所描绘的那样光明，因为该组织内部最近的动荡使它的持续生存受到质疑。

起源 (Origin)

The seed of PHP-FIG was sown at php|tek in 2009 when some developers got together to share ideas. This was out of concern over the fragmentation within the PHP community that has congregated on different islands of frameworks and applications. FIG should be the PHP equivalent of the Java Community Process, a platform for the development of standard technical specifications for Java.

PHP-FIG的种子是在2009年php | tek播种的，当时一些开发人员聚在一起分享想法。 出于对PHP社区内部分散的担忧，这种分散聚集在不同的框架和应用程序孤岛上。 图应该等同于Java Community Process，它是用于开发Java标准技术规范的平台。

Their intention was the creation of a forum for discussing common issues faced by PHP projects and by working together, find ways of cooperation and interoperability. They wanted to make it easier to share the work done between different projects.

他们的意图是创建一个论坛来讨论PHP项目面临的常见问题，并通过共同努力找到合作与互操作性的方式。 他们希望简化在不同项目之间共享的工作。

组织 (Organization)

Participating is as simple as subscribing to the Google group mailing list or joining the IRC channel. The ability to vote on deliberations requires a voting membership.

参与就像订阅Google 网上邮件列表或加入IRC频道一样简单。 对审议进行表决的能力需要有表决权的成员。

The general administrative duties are performed by a triumvirate of secretaries elected at different months of the year for a two-year term. Details of the day-to-day running of the organization are available on the Bylaws section of the PHP-FIG website.

一般行政职责由在一年中不同月份选举产生的三任秘书执行，任期两年。 有关组织日常运行的详细信息，请访问PHP-FIG 网站的“ 章程”部分。

成功案例 (Successes)

As noted above, PSR-4 (Autoloading Standard) describes a specification for autoloading classes from file paths. It’s designed to be fully interoperable, and can be used to supplement any existing autoloading specification, including PSR-0 (the deprecated Autoloading Standard). This PSR also describes the location of files that are to be auto-loaded in accordance with the specification.

如上所述，PSR-4(自动加载标准)描述了一种从文件路径自动加载类的规范。 它设计为完全可互操作的，并且可用于补充任何现有的自动加载规范，包括PSR-0(不推荐使用的自动加载标准)。 此PSR还描述了根据规范要自动加载的文件的位置。

With Composer (a voting member of PHP-FIG), installing and using a PSR-4 compliant package is seamless. A framework-agnostic package such as Carbon can be dropped into any PSR-4 compliant application without any problems.

使用Composer(PHP-FIG的投票成员)，可以无缝安装和使用符合PSR-4的软件包。 无需与框架无关的软件包(例如Carbon)可以放入任何符合PSR-4的应用程序中，而不会出现任何问题。

In the same way, PSR-7 (HTTP Messages) has opened the door for interoperability wider by proposing a specification for the description of HTTP requests and responses. PSR-13 (HTTP Middleware) will build on PSR-7 and further push back the frontiers of interoperability between compliant frameworks and applications.

同样，PSR-7(HTTP消息)通过提出描述HTTP请求和响应的规范，为互操作性打开了更广阔的大门。 PSR-13(HTTP中间件)将建立在PSR-7之上，并进一步推动兼容框架与应用程序之间互操作性的前沿。

The laudable goals of the pending PSRs may not be realized, as the very foundation of the organization is under threat.

待定的PSR值得称赞的目标可能无法实现，因为组织的基础已经受到威胁。

纠纷 (Disputes)

The current situation can be summarized in this post to the mailing list: “The increase in legalistic bureaucracy has taken front stage, and is impeding the good work that this group was set up to do. Put more bluntly, the FIG has become increasingly toxic in recent months, making effective participation nearly impossible.”. Bureaucracy. Toxicity.

当前的情况可以在邮件列表的这篇文章中进行总结：“法治官僚主义的增加已经走上了前列，并阻碍了该小组的成立。 坦率地说，无花果在最近几个月变得越来越有毒，几乎不可能进行有效参与。” 官僚。 毒性。

The mailing list receives lots of messages outside the scope of technical discussion of interoperability. Here’s a sample of topics: “Secretary conflict of interest”, “Harmony between secretaries”, “Bylaw Amendment for Expulsion Votes”, “How can you tolerate this guy?!”, “Expulsion Bylaw Change”, “Request a vote to expel xxxxxx”, “Nullification of xxxx membership” etc.

邮件列表接收了很多互操作性技术讨论范围之外的消息。 这是一个主题示例：“秘书之间的利益冲突”，“秘书之间的和谐”，“驱逐投票的法律修正案”，“您如何容忍这个人？！”，“驱逐章程变更”，“要求开除驱逐票” xxxxxx”，“取消xxxx成员资格”等。

There’s even a recent thread – Alternative to FIG 3.0 – Is it time to call FIG complete?. The premise is, FIG has completed its work, no need for FIG 3.0, so let’s disband PHP-FIG. The FIG 3.0 proposal is a rewrite of the complicated bylaws, structure and processes of the organization. Some, including the author of the post on disbanding the group, would argue that FIG 3.0 is trying to replace a bureaucracy with more complex bureaucracy.

甚至还有一个最新的线程– 替代FIG 3.0 –是时候调用FIG完整了吗？ 。 前提是，FIG已完成其工作，不需要FIG 3.0，因此让我们解散PHP-FIG。 图3.0的提案是对组织的复杂章程，结构和流程的重写。 一些人，包括解散该组织的帖子的作者，会认为图3.0试图用更复杂的官僚机构代替官僚机构。

The departures of high-profile projects and individuals such as Laravel, Doctrine, Propel, Guzzle, PHP League and Assetic haven’t helped matters. An attempt to expel one of the three secretaries fell at the voting hurdle. Perhaps in protest, the PHP Community-driven Standards (PHP-CDS) was formed with a very loose structure and lower-entry level for proposals.

备受瞩目的项目以及Laravel，Doctrine，Propel，Guzzle，PHP League和Assetic等个人的离职并没有帮助。 试图开除三名秘书之一的努力落在了投票的障碍上。 也许是为了抗议， PHP社区驱动的标准 (PHP-CDS)的形成具有非常宽松的结构和较低的投标水平。

According to them: “PHP CDS is not a group or organization, it’s a concept. Its core idea is for the community to create RFCs, discuss them, then hold a vote on their acceptance as a community standard.” The term PHP Community Standard (PCS) echoes the Java Community Process (JCP) but setting up the organization in the first place, might prove to be just a protest against the discord in FIG.

根据他们的说法：“ PHP CDS不是一个团体或组织，而是一个概念。 它的核心思想是让社区创建RFC，进行讨论，然后对它们被接受为社区标准进行投票。” 术语PHP社区标准(PCS)与Java社区过程(JCP)相呼应，但是首先建立该组织可能证明仅是对图11中的矛盾提出的抗议。

甜蜜和谐 (Sweet harmony)

The Open Source community has epitomized goodwill and harmony over the years and the model has won the admiration of corporations that peddle proprietary solutions that are often closed-source.

多年来，开放源代码社区体现了良好的信誉和和谐，并且该模型赢得了兜售通常是封闭源代码的专有解决方案的公司的赞赏。

The Apache Software Foundation that supports a wide range of projects including the extremely popular Apache HTTP Server remains strong. The Linux Foundation provides a home for the Linux kernel project which is probably the world’s largest and most important open source project. Then there are strong communities that congregate around excellent software such as Symfony, Drupal, Composer, Guzzle, etc.

支持广泛项目的Apache软件基金会(包括非常受欢迎的Apache HTTP Server)仍然很强大。 Linux基金会为Linux内核项目提供了一个家，它可能是世界上最大，最重要的开源项目。 然后，有强大的社区聚集在优秀的软件周围，例如Symfony，Drupal，Composer，Guzzle等。

Perhaps it is projects that develop around or which are supported by corporate entities that do well. Maybe it’s projects started and led by a personality that commands respect and admiration.

可能是围绕着项目开展的项目，或者得到表现良好的公司实体的支持。 也许它的项目是由一个受到尊重和钦佩的个性开始并领导的。

苦涩不和谐 (Bitter discord)

If the open source community has seen the best of humanity it has also seen its fair share of verbally-brutal attacks and civil strife. People often disagree – neighbors don’t always see eye-to-eye. Motorists on the motorway find a way to express their displeasure at each other. That’s a fact of life as social animals.

如果开源社区看到了人类最好的一面，那么它也应该看到口头上的残酷攻击和内乱。 人们经常不同意–邻居并不总是见得很对。 高速公路上的驾车者找到了一种表达彼此不满的方法。 作为社会动物，这是生活的事实。

Linus Torvalds is undoubtedly a genius but you wouldn’t want to put him at the top of the list for a diplomat position. Surely not someone who apparently wrote to a mailing list, “Can we please get rid of the brain-damaged stupid networking comment syntax style, PLEASE?”. Or, in another message, “nice” comments like, “I’m a bastard. I have absolutely no clue why people can ever think otherwise. Yet they do. People think I’m a nice guy, and the fact is that I’m a scheming, conniving bastard who doesn’t care for any hurt feelings or lost hours of work, if it just results in what I consider to be a better system. And I’m not just saying that. I’m really not a very nice person. I can say ‘I don’t care’ with a straight face, and really mean it.” Well, nobody has been so annoyed by such words or his comments on pull requests to have gone ahead to fork the Linux kernel.

莱纳斯·托瓦尔兹(Linus Torvalds)无疑是一个天才，但您不想将他放在外交官职位的榜首。 当然不是显然写过邮件列表的人 ：“我们能摆脱脑筋急转弯的愚蠢的网络注释语法风格，请吗？”。 或者，在另一条消息中 ，“不错”的评论如“我是个混蛋。 我绝对不知道人们为什么会另外考虑。 但是他们做到了。 人们以为我是一个好人，事实是我是一个狡猾的，自以为是的混蛋，即使我认为这是一个更好的系统，也不会在意任何受伤的感觉或工作时间的减少。 我不只是这么说。 我真的不是一个好人。 我可以直说“我不在乎”，这是真的。” 好吧，没有人对这样的话或他对拉取请求的评论感到厌烦，因为他们继续派遣Linux内核。

Github was hit by its own earthquake around 2014 when a female employee made some claims of sexism, harassment and intimidation at the office. The story had several dimensions, not least of which involved some ladies hula-hooping to music during office hours while the male geeks were multi-tasking – coding away and at the same time gawking at the dancers. Beyond the frivolity, she claimed: “I had a really hard time getting used to the culture, the aggressive communication on pull requests and how little the men I worked with respected and valued my opinion.” She was alarmed when her “character started being discussed in inappropriate places like on pull requests and issues.”

Github在2014年左右遭受了自己的地震袭击，当时一名女雇员在办公室声称性别歧视，骚扰和恐吓 。 这个故事涉及多个方面，其中最重要的是涉及一些女士在办公时间内呼呼呼呼音乐，而男性怪胎则是多任务处理–编码离开，同时凝视舞者。 除了轻描淡写之外，她声称：“我很难适应这种文化，在要求要求方面进行积极的交流，以及我工作的人很少尊重和重视我的意见。” 当她的“角色开始在不适当的地方，例如请求请求和问题上进行讨论”时，她感到震惊。

There were other facets to the Github story but it goes to show that where two or three developers are, disagreement is there in their midst. Discord is a part of human experience. How we deal with perceived obnoxiousness in people around us reveal a lot about us.

Github故事还有其他方面，但它表明在两三个开发人员所在的地方，他们之间存在分歧。 不和谐是人类经验的一部分。 我们如何处理周围人的令人讨厌的烦恼，这揭示了很多关于我们的事情。

前进的道路 (Way forward)

PHP-FIG is on the delicate path of implosion. The good that we have witnessed since its emergence is the strongest argument for its continued existence. However, the thought of replacing a so-called broken bureaucracy with some neo-bureaucracy in the guise of FIG 3.0 is based on the premise that there is good bureaucracy. The bylaws page on the FIG website and voting process are way too complicated. How about simplifying the running of FIG? How about only focusing on interoperability and not implementation details?

PHP-FIG处于内爆的微妙道路上。 自从它出现以来，我们所看到的好处是它继续存在的最有力论据。 然而，以图3.0为幌子，用一些新官僚机构代替所谓的破碎官僚机构的想法是基于存在良好官僚机构的前提。 FIG网站上的章程页面和投票过程太复杂了。 如何简化图的运行？ 只关注互操作性而不关注实现细节怎么样？

Perhaps the way forward is in less bureaucracy and more concentration on how to improve communication and discussion of PSRs. Maybe it should be easier for “non-experts” to be able to chip into the process in order to facilitate inclusiveness? Some PSRs were in the pipeline for 5 years of more. Does it really have to take so long?

也许未来的方法是减少官僚主义，而将更多精力集中在如何改善PSR的沟通和讨论上。 也许“非专家”能够更轻松地介入流程以促进包容性？ 一些PSR即将发布5年以上。 真的需要这么长时间吗？

Admire Linus Torvalds as a human being or not, let’s pause and listen. He’s been quoted as saying: “I think it’s been part of what’s been great about Linux, the fact that I haven’t had a vision, and very few people had a vision. I take that back. Lots of people had visions, but they’re completely different. People know where they want to drive Linux, but there’s no coherent plan, and it’s actually, I think, what made Linux be a fairly well balanced system, because there was nobody who said, ‘This is the direction, and we’re going that direction, whether it’s right or wrong.’ We just spread out and did a little bit of everything.”

不管您是不是喜欢佩服莱纳斯·托瓦尔兹，让我们停下来倾听。 有人引用他的话说：“我认为这是Linux杰出之处的一部分，这一事实我没有愿景，很少有人有愿景。 我收回之前说过的话。 许多人都有异象，但它们是完全不同的。 人们知道他们想在哪里驱动Linux，但是没有一致的计划，实际上，我认为，是什么使Linux成为一个相当平衡的系统，因为没有人说：“这是方向，我们将无论是对还是错。 我们只是散布了一下，做了所有的事情。”

结论 (Conclusion)

PHP-FIG need to pause and consider the question, “Quo Vadis?”. If the answer is anything other than the original goal of interoperability, its continuing existence may be in doubt. It’s interesting to note that the “toxic” secretary still believes in open source and won’t jump even though he survived being pushed through the expulsion vote. Everybody’s opinion counts. Not every opinion can be accepted but they all deserve attention. Let’s focus less on things like governance, operations, bylaws and administration.

PHP-FIG需要暂停并考虑问题“ Quo Vadis？”。 如果答案不是互操作性的最初目标，那么它的持续存在可能会令人怀疑。 有趣的是，这位“有毒”的秘书仍然坚信开源，即使他被驱逐出选而幸免，也不会跳槽。 每个人的意见都很重要。 并非所有观点都可以接受，但是它们都值得关注。 让我们较少关注诸如治理，运营，章程和管理之类的事情。

We are programmers. Here’s one more Linus’ quote: “Talk is cheap. Show me the code.” And another one – “Those that can, do. Those that can’t, complain.” I can’t, but I won’t complain. The less talking in FIG and more code that interoperates, despite different implementations of a concept, the better the future.

我们是程序员。 这是Linus的另一句话 ：“谈话很便宜。 给我看代码。” 还有一个-“可以做到的。 那些不能的人，抱怨。” 我不能，但我不会抱怨。 尽管概念的实现方式不同，但图中的讨论越少，可进行交互操作的代码越多，未来就越好。

翻译自: https://www.sitepoint.com/php-fig-quo-vadis/

fig-tlo