contributing to projects that have slop in them has legal liability. you'd have to essentially hardfork to remove the slop from git history and such.
for my part, when i do work on this, what i will do is this: re-use existing nuke.list mechanism in lbmk (used already to delete dubious files, e.g. code files with unclear licensing in u-boot) to delete the slopped files. then provide cleaned versions of the same files, with necessary patching re-written as necessary, and files that use it patched to include e.g. foo.deslop.c instead of foo.c - then git history is removed inside tarballs. filter out the changelogs for projects accordingly.
this is the most reasonable way to do it on projects with very little slop. with projects that become almost entirely slop, a hard fork becomes necessary.
for my part, when i do work on this, what i will do is this: re-use existing nuke.list mechanism in lbmk (used already to delete dubious files, e.g. code files with unclear licensing in u-boot) to delete the slopped files. then provide cleaned versions of the same files, with necessary patching re-written as necessary, and files that use it patched to include e.g. foo.deslop.c instead of foo.c - then git history is removed inside tarballs. filter out the changelogs for projects accordingly.
this is the most reasonable way to do it on projects with very little slop. with projects that become almost entirely slop, a hard fork becomes necessary.