Hacker News new | past | comments | ask | show | jobs | submit login

He covers this in TFA:

> And FYI for the actual innocent bystanders who aren't troll farm accounts - the "various compliance requirements" are not just a US thing.




It'd be nice to list what those "various compliance requirements" are on a public open source project.


Not open source specific, but:

> Treasury, in consultation with the Department of State, has issued a new determination under Executive Order (E.O.) 14071, which prohibits the supply to any person in the Russian Federation of (1) IT consultancy and design services; and (2) IT support services and cloud-based services for enterprise management software and design and manufacturing software. The determination will take effect on September 12, 2024.

https://home.treasury.gov/news/press-releases/jy2404#:~:text....


At least part of that might very well be illegal.


Then it sounds like public open source projects are now illegal in the US. We should act accordingly.


Alternatively we can continue like normal because not much of value will be lost. Git is inherently decentralized. If A requires work by C they can pull it directly or B can pull from C and A from B.

There is no inherent issue with C's contributions coming in by way of B especially if B vetted and examined said contributions personally.


Please see the legal reason in the sibling comment.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: