Larks, I’ve noticed that your comments on this post focus on criticizing the specific rules in the CC donor policy document that I shared as an example for other EA organizations to consider. You rightly point out that some of these rules might be impractical for EA orgs to follow. However, I feel frustrated because I think your responses have missed the point of my original post, which was to highlight the value of having a written donor screening policy, and to offer the CC document as a resource that other orgs can legally copy and adapt to their own needs (under the CC-BY license), rather than to recommend that others adopt the policy verbatim.
I would appreciate it if we could keep the conversation focused on discussing the broader idea of implementing donor screening policies or processes for EA orgs, rather than getting bogged down in the specifics of this document tearing down this specific policy without suggesting alternatives. By focusing on the bigger picture, we can ensure that EA organizations develop systems that promote transparency and trust, especially in light of past controversies such as FTX. I think this approach would help build more confidence in the community, while still allowing for flexibility in implementation.
If you have thoughts on how these policies or processes could be better adapted to fit the needs of EA organizations, I’d be glad to discuss them here. I hope we can continue this conversation in a collaborative and constructive way.
Using a very simple cntrl-f methodology, I estimated that over 95% of this post is the CC Guidelines. In contrast you spend less than one sentence arguing for having such a policy, and zero words whatsoever considering tradeoffs. If you want engagement on something you need to provide some material to engage with, and if you thought the CC Guidelines were inappropriate for EA orgs and require significant modification you should say so in the post! I don’t think you can share a lengthy post and then declare, post hoc, that almost the entire post is off-limits, running the risk that orgs might copy-paste it without understanding the issues, and that comments should be restricted to a topic which was barely mentioned in the post.
Indeed, as far as I can see even you agree with this, since one paragraph after chastising me for getting “bogged down in the specifics of the document” you ask for advice on how to adapt these policies, which necessarily involves engagement with the specifics.
Larks, I’ve noticed that your comments on this post focus on criticizing the specific rules in the CC donor policy document that I shared as an example for other EA organizations to consider. You rightly point out that some of these rules might be impractical for EA orgs to follow. However, I feel frustrated because I think your responses have missed the point of my original post, which was to highlight the value of having a written donor screening policy, and to offer the CC document as a resource that other orgs can legally copy and adapt to their own needs (under the CC-BY license), rather than to recommend that others adopt the policy verbatim.
I would appreciate it if we could keep the conversation focused on discussing the broader idea of implementing donor screening policies or processes for EA orgs, rather than
getting bogged down in the specifics of this documenttearing down this specific policy without suggesting alternatives. By focusing on the bigger picture, we can ensure that EA organizations develop systems that promote transparency and trust, especially in light of past controversies such as FTX. I think this approach would help build more confidence in the community, while still allowing for flexibility in implementation.If you have thoughts on how these policies or processes could be better adapted to fit the needs of EA organizations, I’d be glad to discuss them here. I hope we can continue this conversation in a collaborative and constructive way.
Using a very simple cntrl-f methodology, I estimated that over 95% of this post is the CC Guidelines. In contrast you spend less than one sentence arguing for having such a policy, and zero words whatsoever considering tradeoffs. If you want engagement on something you need to provide some material to engage with, and if you thought the CC Guidelines were inappropriate for EA orgs and require significant modification you should say so in the post! I don’t think you can share a lengthy post and then declare, post hoc, that almost the entire post is off-limits, running the risk that orgs might copy-paste it without understanding the issues, and that comments should be restricted to a topic which was barely mentioned in the post.
Indeed, as far as I can see even you agree with this, since one paragraph after chastising me for getting “bogged down in the specifics of the document” you ask for advice on how to adapt these policies, which necessarily involves engagement with the specifics.