On Thu, Apr 21, 2022 at 03:47:34PM -0600, Jilayne Lovejoy wrote: > Let me try to get back to the core of Miroslav's original question, > which I'm simplifying to: > - when can package maintainer start using SPDX license ids in the > license field of package spec files. I think we have two possible options. One (which is my preference) would be to allow it as soon as the "what needs to happen" items you list are ready. This would be for all open Fedora Linux branches, including rawhide/F37, F36, F35, and F34 for the final month. It could also include EPEL, but EPEL could also ask for those to be conditionalized in the spec file. Two would be to start with F38, immediately when Rawhide branches on August 9th, but require all earlier branches to stay the same (or be conventionalized). This reduces the amount of potential end-user confusion for existing releases, but asks for more work from packagers (at least, from those who don't just ignore older releases!) > The other part of this is the question of how do we update all the > existing packages (efficiently) - some of which will require some > amount of "looking" at the actual license text to match it to an > SPDX license id for licenses Fedora has "categorized" (e.g., MIT, > BSD, GPLx "with exceptions") - That is a bigger task that will > (ideally) need more of a throught-through plan and will likely be > on-going for a bit. I can't see how updating all the existing > packages would be tied to a release, but more of a rolling effort > that eventually is done (hopefully) I think we'll get about 10% coverage if we just do this. I think we should plan to do a big, automated change covering the cases which are most easily handled, aimed at Rawhide either shortly after the branch (August) or the next one branch (February 2023). That should get us to 80-90% coverage. Then, sometime around the F40 timeframe, we can actively check on anything that's not updated with a hackfest or some other dedicated effort to cross the line to 100%. -- Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx> Fedora Project Leader _______________________________________________ legal mailing list -- legal@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to legal-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/legal@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
