The licensing policy (https://wiki.mageia.org/en/Licensing_policy) says that the short names of the Fedora license list is used: https://fedoraproject.org/wiki/Licensing:Main?rd=Licensing#SoftwareLicenses

In this list, there is "ASL 2.0" (Apache License 2.0).
But if I write a spec file with this short name, rpmlint tells me:

kytea.x86_64: W: invalid-license ASL 2.0

So there is a difference between our policy and rpmlint rules.
Unless we decided to diverge from Fedore license naming, I would say that's a bug in rpmlint rules. So either the policy has to be modified, or rpmlint rules.

Note also that in /usr/share/rpmlint/TagsCheck.py, we find:
    'Apache License',
    'Apache Software License',
in the list of valid licenses. I would say this is a bug too, and should not be accepted (still according to our license policy).

Reproduction:

- create a RPM spec with license:
License:        ASL 2.0
-`rpmbuild -ba` the spec.
- rpmlint the binary rpm or the src rpm.