建立在线社区：Node-Pixel。

by Gitter

通过吉特

建立在线社区：Node-Pixel。 (Building Online Communities: Node-Pixel.)

Andrew Fisher works on a project merging hardware and software to create beautiful lighting effects. He told us about his way of fostering and managing the open source community around his project. Find out what he says & check out the Node-Pixel Gitter channel.

安德鲁·费舍尔(Andrew Fisher)从事一个项目，将硬件和软件合并在一起，以创建漂亮的照明效果 。 他向我们介绍了围绕他的项目培育和管理开源社区的方式。 找出他所说的话，并查看Node-Pixel Gitter频道 。

Tell us about a little bit about yourself and the Node-Pixel community. What is Node-Pixel? How did it all begin?

告诉我们一些关于您自己和Node-Pixel社区的信息。 什么是Node-Pixel？ 这一切是怎么开始的？

I’m a career web developer of 20 years and now the CTO of LUXE City Guides. I’ve always been involved in the open source community in various forms and over the last few years been deeply involved in the JavaScript Robotics (nodebots) community.

我是20年的职业网站开发人员，现在是LUXE City Guides的CTO。 我一直以各种形式参与开源社区，并且在过去的几年中，我深入参与了JavaScript Robotics(nodebots)社区。

Node-Pixel grew out of that, with the project very specifically merging hardware and software (JavaScript) together to create beautiful lighting effects. It began because historically there hadn’t been an easy way to do that in the JS Hardware world and I’m a sucker for pretty lights so decided to build something that would do it.

Node-Pixel就是从此发展而来的，该项目非常专门地将硬件和软件(JavaScript)合并在一起以创建漂亮的照明效果。 之所以开始，是因为从历史上看，在JS硬件世界中没有一个简单的方法可以做到这一点，而我是吸引美丽的灯光的人，因此决定构建可以做到这一点的东西。

The community is definitely a subset of the Johnny-Five and NodeBots communities with those who are specifically interested in hardware lighting being part of it (other groups are more interested in traditional robotics or home automation etc.). The project has seen commits from some amazingly talented developers from around the world who have helped realise the goal of a straightforward way to control hardware lighting from JavaScript.

该社区绝对是Johnny-Five和NodeBots社区的一个子集，对硬件照明特别感兴趣的人也属于该社区(其他群体对传统机器人技术或家庭自动化等也更感兴趣)。 该项目吸引了来自世界各地的一些才华横溢的开发人员的承诺，他们帮助实现了通过JavaScript控制硬件照明的简单方法的目标。

What common goals do you have as a community ?

作为社区，您有哪些共同目标？

Pretty much as explained above, really a desire to see people use hardware with JavaScript and in particular be able to work with very sophisticated hardware using a straightforward way to do this.

就像上面所解释的那样，确实希望看到人们使用带有JavaScript的硬件，尤其是能够使用简单的方法来处理非常复杂的硬件。

What issues related to the Node Pixel project are you most excited about these days?

这些天，您对与Node Pixel项目相关的哪些问题最感兴趣？

Definitely the wider integration into Interchange, which is a project I’m also involved in. Interchange solves for hardware firmwares what pip and npm solve for python and javascript modules — that is, package management for specific targets. The Node Pixel project illustrated the need for this within the JS hardware world and caused Interchange to happen, so making it fully compatible with Interchange is a big goal.

绝对是与Interchange的更广泛集成，这也是我参与的一个项目。Interchange解决了pip和npm解决python和javascript模块问题的硬件固件，即针对特定目标的程序包管理。 Node Pixel项目说明了JS硬件世界中对此的需求，并导致了Interchange的发生，因此使其与Interchange完全兼容是一个很大的目标。

Beyond that the next big push is in making the library more capable of things like animation and what not, to create really sophisticated lighting effects and have them all triggered from NodeJS or potentially from the browser directly.

除此以外，下一个大推动力是使库更具有动画等功能，以创建真正复杂的照明效果并将其全部从NodeJS或直接从浏览器触发。

What are the most important factors that you have taken into account while creating and maintaining the community? What factors contribute to the success of your community?

在创建和维护社区时，要考虑哪些最重要的因素？ 哪些因素有助于您社区的成功？

The biggest things really I think have been transparency — we use Gitter and GitHub issues as a big part of this to foster collaboration between people that are geographically separated. Having logs of our discussions etc. makes it easy to go back to the community to explain the rationale behind something, especially if they are a user of the project but may not contribute to it.

我真正认为最大的事情就是透明度-我们将Gitter和GitHub问题作为其中的重要组成部分，以促进地理位置分散的人们之间的协作。 拥有我们讨论的日志等，可以轻松地返回社区解释某些背后的原因，尤其是如果他们是该项目的用户，但可能对此没有贡献。

Related to this is that we abide by a Code of Conduct for contribution to the project and since the outset we’ve always endeavoured to foster an open, trusting, safe and responsible community. I think when people set that out as just “the way things are” then it helps people adopt that set of standards when they engage. Node Pixel has been good in that respect but really owes a great deal to the wider work being done in the JS Hardware world by Johnny-Five and javaScript in general to ensure safe places.

与此相关的是，我们遵守《行为准则》为项目做出贡献，从一开始就一直致力于建立一个开放，信任，安全和负责任的社区。 我认为，当人们以“事物的现状”来阐述这一点时，它将帮助人们在参与时采用这套标准。 Node Pixel在这方面一直很出色，但实际上，很大程度上要归功于Johnny-Five和javaScript在JS硬件世界中为确保安全场所所做的更广泛的工作。

What are the key challenges that you encounter while managing the community?

您在管理社区时遇到的主要挑战是什么？

Time zones!!!!

时区！！！！

I’m in Australia and most of my collaborators are in the US and EU so getting overlaps can be really challenging when we’re working through building features etc. Need to make the Pacific or Indian oceans about half the size they are ;)

我在澳大利亚，而我的大多数合作者都在美国和欧盟，因此在进行建筑要素设计等工作时，要实现重叠可能是非常困难的。需要将太平洋或印度洋的面积扩大到原来的一半；)

What are the main issues discussed in the Node Pixel project channel on Gitter?

Gitter上的Node Pixel项目通道中讨论的主要问题是什么？

Much of the day to day stuff revolves around support for people using the project. We are very vocal about our use of Gitter as a primary support channel so encourage people to drop in and ask questions. This helps get people up and running with the project very rapidly.

每天大部分时间都围绕着对使用该项目的人员的支持。 我们非常热衷于将Gitter用作主要支持渠道，因此鼓励人们加入并提出问题。 这有助于使人们Swift启动并运行该项目。

Besides that, as we’re building features, there’s a lot of back and forth discussion about approaches, notes on code reviews etc. GitHub helps with this, however we tend to use GH as the second part of this more free-flowing chatter while we arrive at an approach then use GH to document the issues and the steps to resolution.

除此之外，在构建功能时，围绕方法，代码审查注释等进行了很多来回讨论。GitHub对此提供了帮助，但是我们倾向于将GH用作这种更为自由的聊天工具的第二部分，而我们得出一种方法，然后使用GH记录问题和解决步骤。

Based on your experience, do you feel that the open source communities have changed and evolved over the past years? If so, how?

根据您的经验，您是否觉得开源社区在过去几年中发生了变化和发展？ 如果是这样，怎么办？

Definitely. There’s some good and bad in this. On the one hand open source has more or less “won” much of the way we build software. As developers we want to be able to see, validate and change the code we’re running in our own projects. In this way I think software development has become much more open for everyone and hopefully that is helping future developers to learn and not repeat the mistakes of the past due to lack of information.

绝对是 这有好有坏。 一方面，开源在我们构建软件的过程中或多或少地“赢得了”。 作为开发人员，我们希望能够查看，验证和更改我们在自己的项目中运行的代码。 通过这种方式，我认为软件开发对每个人都变得更加开放，并希望这可以帮助未来的开发人员学习并避免由于缺乏信息而重复过去的错误。

The bad part is that there can be a lot of consumption of the “free” part of free & open source software where consumers of the projects do expect fixes to happen immediately or a new feature added just because they asked. Being able to use the tools to engage with people to soften this approach is invaluable, as you can often encourage someone to help contribute and potentially build the feature they want to see as part of the project.

糟糕的是，可能会大量消耗免费和开源软件的“免费”部分，而项目的消费者确实希望这些补丁会立即进行修复，或者只是因为要求而添加了新功能。 能够使用工具与人们互动以软化此方法是非常宝贵的，因为您通常可以鼓励某人提供帮助，并潜在地构建他们希望在项目中看到的功能。

Overall, I think the community is more of a community now and I believe the good definitely outweighs the negative aspects — but we should always be looking at what can be done to help all projects have a better experience.

总体而言，我认为社区现在更多的是社区，我相信好处绝对大于弊端，但我们应该始终在考虑可以采取哪些措施来帮助所有项目获得更好的体验。

What advice would you give to someone who wants to start an online open source community from scratch?

您对想从头开始建立在线开源社区的人有什么建议？

Talk to yourself.

自言自语。

That sounds weird but it’s often daunting when you’re the only person working on a project. You have an idea, you throw your code up there and you wait for people to nit pick it. It can be very challenging because you’re opening up yourself to potential critique.

这听起来很奇怪，但是当您是唯一从事项目工作的人时，这通常令人生畏。 您有一个主意，将代码丢到那里，然后等待其他人来挑选它。 这可能是非常具有挑战性的，因为您要公开接受潜在的批评。

One of the ways I get over this is to raise issues in my GitHub and assign them to myself. I do code reviews of my own code and make notes about it and raise tickets to fix the code. I also quite often note current statuses etc in Gitter even though I suspect no one will read it.

解决这个问题的方法之一是在GitHub上引发问题并将其分配给我自己。 我对自己的代码进行代码审查，并对其进行注释，并提出修改代码的票证。 我也经常注意到Gitter的当前状态，即使我怀疑没人会读。

However the funny thing with this approach is it helps you be more refined in the way you talk about your project to others later, and you also build up a body of documentation, rationale and “liveliness” about your project and it makes it easier for others to contribute — even if they think they are collaborating with a mad person who talks to themselves (which we all do anyway).

但是，这种方法的有趣之处在于，它可以帮助您在以后与其他人谈论项目的方式上更加完善，并且您还可以建立有关该项目的文档，基本原理和“生动性”，这使您更容易其他人也可以做出贡献-即使他们认为自己正在与一个与自己说话的疯人合作(无论如何我们都这样做)。

So my advice is talk to yourself. It helps articulate your project, makes you approachable and a community has to start with a person so *be* the person it starts from.

所以我的建议是对自己说。 它有助于阐明您的项目，使您与他人相处融洽，而社区必须从一个人开始，以便成为自己的人。

Thanks!

谢谢！

翻译自: https://www.freecodecamp.org/news/building-open-source-communities-node-pixel-afbe9fffc1b2/