Remix clone Hacker News

new | show | ask | jobs Github

	▲	em-bee 4 hours ago
		when you commit code to a project you are warranting that you have the legal right to do so. the bigger projects will not even accept your contribution done at work without an explicit permission from your employer. this is not just about you and your risk, but also about the risk for the project.
	▲	__MatrixMan__ an hour ago \| parent \| next [-]
		What does that rejection look like? Do they refuse to merge the PR until you send them a document or something? As far as I'm aware these legal dark corners are uninhabited. If you say: `> I was blocked, so I fixed a bug, and rather than wasting time maintaining an internal fork in violation of the OSS project's license, I complied with that license by contributing my fix upstream.` I've never met a manager or a maintainer who would suggest that you open the can of worms by contacting a lawyer about it. We all know that intellectual property is a bit of a farce, especially as applied to software that was written jointly by an employee and model that was likely trained on the OSS project in the first place. But it's not a problem unless it's a Problem, so as long as no party is injured, why make it one?
	▲	vinckr 3 hours ago \| parent \| prev [-]
		in most cases you dont need explicit permission but you need to sign a CLA (Individual Contributor License Agreement) - which kind of includes permission