We don’t allow questions seeking recommendations for software libraries, tutorials, tools, books, or other off-site resources. You can edit the question so it can be answered with facts and citations.
Closed 9 years ago.
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
接受
或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
发布评论
评论(2)
如果您确实足够大,这是一个问题(而且,我怀疑,如果您在美国),您可能会发现 软件自由法律中心的软件自由保护组织可以帮助...
If you really are big enough that this is a problem (and, I suspect, if you're in the US), you might find that the Software Freedom Conservancy from the Software Freedom Law Center can help...
一个简单的死人开关即可完成此操作。任命社区中的长期/有价值的成员作为继任者,以防最坏的情况发生,并安排将钥匙转移给他们。
你也可以很容易地建立自己的基金会,它不需要是非营利的,也不需要支付任何员工的工资。
根据我的经验,伞式组织可能没有足够的资源来与社区保持一致,以达到在发生情况时迅速采取行动所需的程度。这就是为什么 SPI 除了充当支付工具之外,很少参与其所服务的组织代理人。
您最好只是与其他开发者协调意愿,或者建立一些您社区固有的小东西。
A simple dead man's switch accomplishes this. Appoint long term / valued members of your community as successors in case the worst happens, make arrangements for the keys to be transferred to them.
You can also form your own foundation very easily, it need not be non-profit, nor is it required to pay any of its employees.
In my experience, umbrella organizations may not have the resources to stay in tune with the community to the degree needed to act quickly in case something happens. This is why SPI has very little involvement with the organizations it serves, other than acting as a payment proxy.
You would do better to simply coordinate wills with the other developer, or set up something small that is intrinsic to your community.