黑客守则_论守则与社区

黑客守则

People often ask me “Why Sass?” Why choose Sass over another preprocessor? Why is it so much more popular than its competitors?

人们经常问我“为什么要萨斯？” 为什么选择Sass而不是另一个预处理器？ 为什么它比竞争对手那么受欢迎？

That’s a great question, and aside from all of the technical conversations about similarities and differences between preprocessors that can follow, the real answer is: the community. With a thriving, benevolent, and encouraging community of designers and developers, Sass has grown to be the irrefutably most popular and mature CSS preprocessor out there.

这是一个很好的问题，除了所有关于后续处理器之间的异同的技术性讨论外，真正的答案是： 社区 。 凭借着一个蓬勃发展，仁慈而又令人鼓舞的设计师和开发人员社区，Sass已经成长为在那里毫无争议地最受欢迎和最成熟CSS预处理程序。

Let’s take a look at what happens in a large, healthy development community:

让我们看看在一个大型，健康的开发社区中发生了什么：

1. More people look at the source code, which means more people are there to triage issues, log bugs, and help develop the source.
   越来越多的人关注源代码，这意味着有更多的人来分类问题，记录错误并帮助开发源代码。
2. More people try out the product because it’s improving more rapidly.
   越来越多的人尝试该产品，因为它的改进速度越来越快。
3. More people write about using the product and develop new ideas on workflows.
   越来越多的人撰写有关使用该产品的文章，并在工作流程方面提出新的想法。
4. More people help contribute to the documentation.
   更多的人帮助撰写文档。
5. More people develop 3rd party applications and toolkits to improve upon the product.
   越来越多的人开发第三方应用程序和工具包来改进产品。
6. More people talk about using the product and its tools at meetups and conferences.
   在聚会和会议上，越来越多的人谈论使用该产品及其工具。
7. More people switch to using the product in the workplace.
   越来越多的人开始在工作场所使用该产品。
8. More people are introduced to the product, from development teams to interns to designers to project managers.
   从开发团队到实习生再到设计师再到项目经理，更多的人被介绍给该产品。

From development teams, to interns, to designers, to project managers, this is cyclical.

从开发团队到实习生，再到设计师，再到项目经理，这都是周期性的。

Eventually there are meetup groups, books, videocasts, and a conference devoted to the product. Community is essential in the life line of any piece of software because without people to use your product, what’s the point? This is something that the Slack Chat Product Team understands very clearly, and if you read the story of their journey, you’ll see how user-centric their development approach was. The founder of the company recalls “when key users told us something wasn’t working, we fixed it — immediately.”

最终会有聚会小组，书籍，视频广播和专门针对该产品的会议 。 社区对于任何软件的生命线都是必不可少的，因为如果没有人使用您的产品，那有什么意义呢？ Slack聊天产品团队非常清楚地理解了这一点，如果您阅读了他们的旅程的故事，您将看到他们的开发方法以用户为中心。 该公司的创始人回忆说：“当关键用户告诉我们某些问题不起作用时，我们会立即予以修复。”

人就是一切 (People are Everything)

Word of mouth is the number one contributor to product adoption than anything else. I learned about Sass and Compass at a Refresh Meetup in Washington, DC. To me, it was a new tool — a simple idea that I started tinkering with until I found so much value in it that I passed it along eagerly to everyone I knew.

口口相传是产品采用率的第一大贡献者。 我在华盛顿特区的一次聚会上了解了Sass和Compass。 对我来说，这是一个新工具，一个简单的主意，我开始修改，直到发现其中的价值，以至于将它热切地传递给了我认识的每个人。

Studies show that 92% of consumers believe recommendations from friends and family over any and all forms of advertising.

研究表明，有92％的消费者相信朋友和家人对任何形式的广告都推荐。

This is so important for developers, who often think product-first and not people-first to understand. Your audience is largely influenced by its community. Once you have a basis, this grows exponentially. I can’t even begin to name how many grid frameworks, style guide generators, blog posts, and other tools there are out there that have branched off of Sass, and which introduce new developers into the mix continuously.

对于开发人员来说，这是如此重要，他们通常认为首先了解产品而不是首先了解人。 您的受众群体很大程度上受到其社区的影响。 一旦有了基础，它就会成倍增长 。 我什至无法开始列举从Sass分支出来的有多少个网格框架，样式指南生成器，博客文章和其他工具，这些工具不断地将新的开发人员引入其中。

建立美丽的开发社区 (Building a Beautiful Dev Community)

One of the most amazing things about the Sass community is its brilliant diversity and dedication to embracing inclusivity. This is a community where the code of conduct is taken very seriously and where any form of intimidation is really looked down upon. All opinions are welcome, encouraged, and embraced.

Sass社区最令人惊奇的事情之一是其辉煌的多样性和对包容性的奉献精神。 这是一个非常认真对待行为准则并真正轻视任何形式的恐吓的社区。 欢迎，鼓励和接受所有意见。

What happens when you take inclusivity seriously is that it decreases barriers to entry. Developers feel more comfortable, therefore unafraid to ask questions and report bugs. This increases participation and introduces new opinions into the mix. New participants are excited to be a part of something, as they introduce zeal and experimentation, and are likely to pass along the project to their friends and colleagues. And it grows, and grows, and grows.

当您认真对待包容性时，会减少进入的障碍。 开发人员感到更自在，因此不怕问问题和报告错误。 这增加了参与度，并在组合中引入了新的观点。 新参与者很高兴能参与其中，因为他们会介绍热情和实验，并有可能将项目传递给他们的朋友和同事。 它在成长，在成长，在成长。

伸出手 (Reaching Out)

But Sass isn’t the only example of a burgeoning development community. I want to talk to you all for a moment about Craft. If you aren’t familiar, Craft is a Custom CMS, created by ExpressionEngine developers, Pixel and Tonic. Let me tell you a little story about this growing community.

但是Sass并不是蓬勃发展的开发社区的唯一例子。 我想和大家聊一会关于Craft的话题。 如果您不熟悉， Craft是一个自定义CMS，由ExpressionEngine开发人员Pixel和Tonic创建。 让我告诉您有关这个不断发展的社区的小故事。

Craft version 1.0 came out in June of 2013. At the time, I was interning at a Development Shop called Viget, who was pretty involved in the ExpressionEngine community at the time and curious about this new product. I had the opportunity to try it out first, having the opportunity to start a brand new project with no clients to convince. Despite being a junior in college studying graphic design and struggling to learn about ARIA roles and the <figure> element, the kind of treatment and support I received from the (then tiny) Craft community was inspiring.

Craft版本1.0于2013年6月问世。当时，我在一家名为Viget的开发商店实习，当时他非常参与ExpressionEngine社区，并对这个新产品感到好奇。 我有机会先尝试一下，有机会启动一个没有客户说服的全新项目。 尽管我是一名大三的学生，学习平面设计并且努力学习ARIA的角色和<figure>元素，但是从(当时很小的)Craft社区获得的那种待遇和支持令人鼓舞。

The two developers, Brad and Brandon, held (and still hold) an open chat every Friday at 1:30 PM PST where they asked people to log in and talk about their issues, their successes, and the projects they were working on with Craft. When I was having difficulty with the system, they took time out of their day to remotely connect to my computer and fix the bugs that I was having issues with (twice actually — I’m really good at breaking things). It was very clear that the developers sincerely cared about the people using their product and it was clear.

布拉德(Brad)和布兰登(Brandon)这两个开发人员在太平洋标准时间每个星期五下午1:30举行(并且仍然举行)公开聊天，他们要求人们登录并谈论他们的问题，他们的成功以及他们正在与Craft合作的项目。 当我在使用系统时遇到困难时，他们花了很多时间来远程连接到我的计算机并修复我遇到问题的错误(实际上是两次，我非常擅长解决问题)。 很明显，开发人员真诚地关心使用他们产品的人们，这很明显。

树立榜样 (Setting an Example)

And it grew slowly from there: at first Craft workshops started popping up at conferences, then they had their own Craft Summit, and now, most recently, as I was browsing meetup groups in my area, I noticed that there was a Craft meetup group. It’s been a year since I’ve built anything significant with the Craft CMS, but I am always going to recommend it when asked. Because I sincerely enjoy using it, and because the developers care about people, and developers who care about people tend to breed the kind of community of people who also care about people.

从那时开始，它开始缓慢发展：起初，Craft研讨会开始在会议上弹出，然后他们举行了自己的Craft Summit，现在，最近，当我浏览所在区域的聚会组时，我注意到有一个Craft聚会组。 自从我用Craft CMS构建了重要的东西已经有一年了，但是当有人问我时，我总是会推荐它。 因为我真诚地喜欢使用它，并且因为开发人员关心人，并且关心人员的开发人员倾向于孕育一种也关心人的社区。

The maintainers and core contributors of any product set the example.

任何产品的维护者和核心贡献者都树立了榜样。

At SassConf last year, Chris Eppstein said something along the lines of “I don’t know how this community came to be so awesome, but I’m really thankful for it.” Well the answer to that is simple. It’s because the people who built it made it that way, and made sure it stayed that way during each step of the growth process.

去年在SassConf上， 克里斯·埃普斯坦( Chris Eppstein)说了一些类似的话： “我不知道这个社区是如何变得如此出色，但是我对此感到非常感谢。” 答案很简单。 这是因为构建它的人是那样做的，并确保它在增长过程的每个步骤中都保持这种状态。

同情是关键 (Compassion is Key)

Read any dev forum and you’ll likely see people bashing each other’s code and opinions on subjects, proving their intellectual superiority as communities become increasingly fragmented. This just leads people out of the conversation, feeling intimidated and frustrated. You never know what people will make or contribute in the future.

阅读任何开发人员论坛，您可能会看到人们在主题上互相殴打对方的代码和观点，证明了随着社区变得越来越分散，他们的智力优势。 这只会使人们退出对话，感到被吓到和沮丧。 您永远都不知道人们将来会做出什么样的贡献。

If you want to foster a supportive community, try to decrease barriers to entry as much as you can. Here are a few recommendations:

如果您想建立一个支持性的社区，请尝试尽可能减少进入的障碍。 以下是一些建议：

1. Have a code of conduct. Don’t just “have” a code of conduct, but enforce it, and stand up for each other’s voices.

   制定行为准则。 不要只是“拥有”一个行为准则，而是要执行它，并站在彼此的声音中。

2. Talk to your users. Have a chat room (IRC, Gitter, Hipchat, Slack) where anybody can join and contribute opinions or ask questions.
   与您的用户交谈。 有一个聊天室(IRC，Gitter，Hipchat，Slack)，任何人都可以加入其中并发表意见或提出问题。
3. Have a Contribution Guideline. How can people participate? Guide them through setup and in areas where they can begin to help out with the project.
   有一个贡献准则。 人们如何参与？ 指导他们进行设置，并在他们可以开始为项目提供帮助的领域中提供指导。

4. Be careful about the vernacular you use when commenting on Pull Requests. I really like this guideline. Be sure to include something similar in your Contribution Guidelines or Code of Conduct.

   在对“拉取请求”进行注释时，请注意所使用的语言。 我真的很喜欢这个准则。 确保在《贡献准则》或《行为准则》中包含类似内容。

These tips don’t just relate to the FOSS (Free/Open Source Software) Community. They are even more important within a workplace. Remember: People above code. Encouragement above superiority. Those are the traits of a blossoming development community.

这些技巧不仅与FOSS(自由/开源软件)社区有关。 在工作场所中，它们甚至更为重要。 切记： 高于代码的人员。 鼓励超越优势。 这些就是蓬勃发展的社区的特征。

翻译自: https://www.sitepoint.com/on-code-and-community/

黑客守则