I've checked couple dozens popular boilerplates (react, react-native, nodejs) and neither of them are forks from other boilerplates.
Am i missing something? why are people writing them from scratch instead of forking?
Say, i want to create own boilerplate, because other are not specialized enough for needs of my company. This boilerplate will be maintained by my employees only (or "almost only"). This boilerplate will remain open-sourced. Do i have to start from scratch reinventing this wheel, or i can just fork existing repo and build on top of it? are there any sort of limitations in such approach?
i don't like "Forked from" sign, because in vast majority of cases it means "forked, added couple of commits and that's all", which is not the case for me - it will be modified quite a lot. So, is it ok, if i'll
git clone, change repo address and put it to own repo?
may be i can remove the whole
.git, delete all references to original developers along with the part of this code that doesn't suit my needs and publish the result as my own boilerplate? That doesn't sound fair though. Anyways, is this allowed for MIT-licensed repos? i'm confused, because this is the explicitly suggested "way to go" to start build on top of many repos.