Maybe you forked a library because of reasons. You can tour the original repo and explain the problems. I have at least one of those examples for each time the legal or confidentiality department stepped in.

▲

FirmwareBurner 2 years ago | parent [-]

>Maybe

The word maybe is doing a lot of heavy lifting here. What if you never had to do that? Not everyone's work is public. Inf act I'd say most people's work is not public. Sometimes even the product is not public since it's B-2-B.

▲

ttyprintk 2 years ago | parent [-]

But if you’ve worked on something mature and nontrivial, you’ve forked a dependency and are able to tour it. Looks like I’ve done it on average twice per year.

	▲	LPisGood 2 years ago \| parent \| next [-]
		I’ve worked on a piece of software you have at least heard of, probably used, and it is so far from publicly available it’s funny.
	▲	FirmwareBurner 2 years ago \| parent \| prev [-]
		I never had to for anything public.