web标准以及w3c标准
It took months to land a tiny change, but it finally went public, and I’d like to help you out with all the details so that maybe, next time, it’ll take less time, or it’ll require less iterations between parts.
花了几个月的时间进行了微小的更改，但最终还是公开了，我想为您提供所有详细信息，以便下次可能会花费更少的时间，或者在两次更新之间需要更少的迭代部分。
If we’re not willing to sign this agreement, which is pretty common for any Open Source contribution when the project is driven by organizations, we can just keep ranting about standards on twitter and skip reading here.
如果我们不愿意签署该协议，这在组织推动项目的情况下对于任何开源贡献来说都是很普遍的，那么我们可以继续在Twitter上抱怨标准，而在此处跳过阅读。
Moreover, if the company we work for deals with, or uses, Web technologies, be sure such company is OK in letting us signing that agreement on behalf of such company, but there are also other steps needed:
此外，如果我们工作的公司与Web技术打交道或使用Web技术，请确保该公司可以让我们代表该公司签署该协议是可以的，但还需要其他步骤：
the company should have a GitHub organization
公司应该有一个GitHub组织
our GitHub account should be part of such organization, and we have to be sure its visibility is public (it’s private by default)
我们的GitHub帐户应该是该组织的一部分，并且我们必须确保其可见性是公开的(默认情况下为私有)
Without these premises, even if we’re contributing in our free-time or over a weekend, and even if the proposed change, or fix, has nothing to do with what our company does, there’s no way to help out in any way.
没有这些前提，即使我们在业余时间或周末做出贡献，即使提议的更改或修复与公司的工作无关，也无法以任何方式提供帮助。
This is the part that baffled me the most: if we work on GitLab instead, there’s apparently no way to help contributing with standard bodies.
这是令我最困惑的部分：如果我们改为在GitLab上工作，显然没有办法帮助标准机构。
I think this is a bit unfair for GitLab users, but I’m sure it’s not a meant limitation, it’s just easier, more convenient, to use GitHub’s popularity.
我认为这对GitLab用户来说有点不公平，但是我敢肯定这不是一个有限制的事情，使用GitHub的普及程度更容易，更方便。
Could this be any better? Well, my quick and rushed hint here:
会更好吗？ 好吧，我的快速而匆忙的提示在这里：
演示地址
There is an already made template that helps us filing issues, and the more details we’ll put in our proposal, the more chances we have it’ll get noticed, and vendors’ engineers will show their interest.
有一个已经制作好的模板可以帮助我们提交问题，并且我们在提案中提供的详细信息越多，被注意到的机会就越多，供应商的工程师将表现出他们的兴趣。
Mine is just an example on how to start a conversation, and it’s within such conversation that we should understand if there’s interest or not in implementing such proposal.
我的只是一个关于如何开始对话的例子，在这种对话中，我们应该了解是否有兴趣实施这样的建议。
an engineer agreed on moving forward with the proposal 一位工程师同意继续推进该提案Ideally, we should convince at least two implementers from two different browsers, because that’s required to accept any Merge Request.
理想情况下，我们应该说服来自两个不同浏览器的至少两个实现者，因为这是接受任何合并请求所必需的。
As suggested by the template itself, these are the condition to land the MR:
正如模板本身所建议的，这是登陆MR的条件：
At least two implementers are interested (and none opposed) 至少有两个实现者对此感兴趣(并且没有反对者) Tests are written and can be reviewed and commented upon 测试是书面的，可以进行审查和评论 Chrome, Firefox, and Safari implementations bugs are filedChrome，Firefox和Safari实施错误已提交I cannot stop thanking people involved in the MR, because I couldn’t have landed anything without their help.
我不能停止感谢参与MR的人们，因为没有他们的帮助我什么也登陆不了。
As tiny as my change was, I didn’t know the whole living standards document was based on a single monolith which is also pretty hard to edit, as everything has to be written by hands.
尽管变化很小，但我不知道整个生活水平文件都基于一个整体，也很难编辑，因为所有内容都必须用手写。
Thankfully, that’s just a huge HTML file, and I assume if we’d like to contribute to Web standards, we know at least the basics here, but there are various things to consider, as inner document links, wording, parts that need extra care, and so on … so that to propose this change:
值得庆幸的是，这只是一个巨大的HTML文件，我假设如果我们想为Web标准做贡献，我们至少知道这里的基础知识，但是作为内部文档链接，措辞和其他需要考虑的部分，还有很多事情需要考虑护理，等等……以便提出此更改：
// previous implementation, whenDefined resolves with nothingcustomElements.whenDefined(name).then(() => {});// proposed change: resolve with the class// instead of requiring customElements.get(name) aftercustomElements.whenDefined(name).then(Class => {});I had to modify some content that spanned over 300 lines, within a document that contains a more than 120K lines of specifications.
我必须在包含超过12万行规格的文档中修改跨越300行的某些内容。
Yes, we can contribute to Web standards without being employed by Apple, Google, or Mozilla, as long as we keep these points in mind:
是的，只要牢记以下几点，我们就可以为Web标准做出贡献，而无需被Apple，Google或Mozilla聘用：
we gotta be patient, because there are hundreds of proposal and moving parts daily in there 我们要有耐心，因为那里每天有数百个提案和活动部件 the better we formulate the proposal, the sooner it will move into implementation and the related Merge Request can be pushed我们制定提案的能力越强，越早将其付诸实施，相关的合并请求就可以被推送we can ask help to people doing this on daily basis ♥我们可以每天向这样做的人寻求帮助♥as we all live in a different timezone, the least amount of back-and-forward bureaucratic iterations we need, the better (i.e. the agreement bit, which delayed in my case the landing by more than a week) 因为我们每个人都生活在不同的时区，所以我们所需的来回官僚机构迭代次数越少越好(即协议位，在我的情况下将着陆时间推迟了一周以上)I hope this post will encourage those potential contributors that never dared to help out for real; there are few things that need to be done in a specific way, but after all, it’s been a pretty awesome experience 👍
我希望这篇文章会鼓励那些从未敢为现实提供帮助的潜在贡献者； 很少有一些事情需要以特定的方式完成，但是毕竟，这是一个很棒的体验experience
翻译自: https://medium.com/@WebReflection/a-journey-to-web-standards-contribution-8027bb874908
web标准以及w3c标准
相关资源：四史答题软件安装包exe