论文标题
首先看一个社区组织的新兴模型，用于长期维护生态系统的包装
A first look at an emerging model of community organizations for the long-term maintenance of ecosystems' packages
论文作者
论文摘要
许多现代编程语言中最大的优势之一是他们丰富的开源包生态系统。确实，现代语言特定的软件包经理使共享可重复使用的代码并取决于其他人（通常是陌生人）所写的组件变得更加容易。但是，尽管他们使程序员提高了生产力，但这种做法在生态系统的水平上产生了新的健康风险：当使用大量使用的软件包停止维护时，所有依赖于该计划的项目都受到威胁。在本文中，我问三个问题。 RQ1：这种威胁有多普遍？特别是，一个人维护了多少个依赖软件包（谁可以随时辍学）？我表明，很大一部分此类包裹就是这种情况。 RQ2：依赖软件包的项目作者如何反应其维护者变得不可用？我列出了一些选项，并且特别关注叉子的概念。 RQ3：生态系统的程序员如何共同对这些事件做出反应，或为它们做准备？我首先研究了一个新兴的社区组织模型，以长期维护包裹，这些模型出现在几个生态系统中。
One of the biggest strength of many modern programming languages is their rich open source package ecosystem. Indeed, modern language-specific package managers have made it much easier to share reusable code and depend on components written by someone else (often by total strangers). However, while they make programmers more productive, such practices create new health risks at the level of the ecosystem: when a heavily-used package stops being maintained, all the projects that depend on it are threatened. In this paper, I ask three questions. RQ1: How prevalent is this threat? In particular, how many depended-upon packages are maintained by a single person (who can drop out at any time)? I show that this is the case for a significant proportion of such packages. RQ2: How can project authors that depend on a package react to its maintainer becoming unavailable? I list a few options, and I focus in particular on the notion of fork. RQ3: How can the programmers of an ecosystem react collectively to such events, or prepare for them? I give a first look at an emerging model of community organizations for the long-term maintenance of packages, that appeared in several ecosystems.
