| Re: [open-regulatory-compliance] CRA discussion topics and activities |
On 2024-06-14 11:29:50 +0000 (+0000), Fendt, Oliver via open-regulatory-compliance wrote: > yes I agree to you that this will impose some additional setup and > governance for some OSS projects. [...] It's not clear to me that it imposes anything mandatory on the projects themselves (in the volunteer contributor community sense). It may mean that vendors have to make some hard decisions not to distribute certain software to their customers because upstream practices aren't aligned with public policy requirements and taking on those responsibilities is cost-prohibitive for the vendor. Of course it may also mean some nonprofit steward organizations are unable to provide services to non-complying projects while retaining a tax-exempt status. This is not about fixing open source projects, it's about making sure that organizations are culpable for their poor choices and can't dodge their responsibility to their customers or dues-paying members by claiming problems were the fault of an upstream free/libre open source software community. The way we make lemonade from a CRA lemon is to ensure that it becomes an strong financial incentive for companies to provide additional support and assistance to open source communities rather, than continuing to profit off their backs while giving little in return. -- Jeremy Stanley
Attachment:
signature.asc
Description: PGP signature