@archlinux in osm all contributors needed to agree on the new license or the contribution was removed. IMHO it is not possible to change the license without a copyright holder allows it. Despite you have a contribution policy signed by your contributors that allows you doing so.
What about license compatibility of the upstream sources vs. the chosen 0BSD for the packaging?
Wouldn't it be more safe to use the same license as upstream. Esspecially if the pkg includes patches?!
We are aware of that issue. But we can't do this as we do not have a full track record of all contributions over 20 years to the distro.
This solution is a compromise and we will deal with any claims as they come. In this case there isn't realistically a lot of valid copyright claims as most of these things probably don't meet a creative work bar.
The 0BSD license is just reaffirming the public domain aspect we consider these packages to be.
@Foxboron @archlinux i like this approach. It shall be easy to implement and provides clarity for the users. I also do not expect many complains it shall be easy to handle those!