(or a couple of others we use!)
This is clear when you skim the repos on our org page - only some are shown are having a licence.
Research
In 2016, Github said they use Licensee for this.
Licensee says that they rely on the choosealicense.com database.
Choosealicense.com does include the EUPL in their database.
Solution
Unless we have custom versions of the licenses that Github doesn't recognize, then I suggest we update our license files to the versions of the text used by choosealicense.com.
This will help people coming to our org page and our repos for the first time more quickly and easily understand the licences we use.
(or a couple of others we use!) This is clear when you skim the repos on our org page - only some are shown are having a licence.
Research
In 2016, Github said they use Licensee for this. Licensee says that they rely on the choosealicense.com database. Choosealicense.com does include the EUPL in their database.
Solution
Unless we have custom versions of the licenses that Github doesn't recognize, then I suggest we update our license files to the versions of the text used by choosealicense.com.
This will help people coming to our org page and our repos for the first time more quickly and easily understand the licences we use.