On Thu, Jan 13, 2022 at 6:00 PM Jilayne Lovejoy <jlovejoy(a)redhat.com> wrote:
well, as Miroslav began this thread asking about the scenario of
having
a Good or Bad license (and didn't seem to indicate it was specifically
the Perl example - I assumed Fedora packagers are coming across such
scenarios.
I guess I don't really know for sure. My intuition is that it's not
going to be common because while disjunctive dual (and triple, etc.)
licenses are common in FOSS projects usually all the licenses are
clearly FOSS. In the Fedora context I don't think I know of a good|bad
example other than the GPL/Artistic cases. A team at Red Hat has been
using ScanCode to scan RHEL packages and I see the results of these; I
think there may have been one or two "good|bad" cases outside the Perl
module cases. So I think it's probably really rare.
(Conjunctive multiple licenses -- "Good AND Bad" -- is going to be a
much more common situation.)
> However, I don't see why we should go to all this trouble if
it is
> reasonably likely that in the one case where this problem is known to
> occur it might go away by revisiting Fedora's classification of the
> Artistic License 1.0 (in its various forms) as "bad".
It was a question on this mailing list that started this thread and
there was some support to documenting the answer to the question.
At a minimum, stating explicitly that where one has a "Good or Good" -
the License: field should capture that and if it's "Good or Bad" the
License field should include only the Good license. That seemed to be
common practice by all I could deduce from the entire thread. I can't
see how at least capturing that is controversial?
I totally agree with the suggestion that "Good or Bad" should be
represented in the license tag as just "Good". Sorry if it seemed I
was saying otherwise. The only thing I'm really objecting to is
imposing a new commenting requirement that didn't exist before (I
think especially if the triggering event is going to be really
uncommon).
Richard
-