License file not recognized by package website

[idleberg]

I've already created an issue for package-generator, but this is probably the more appropriate place for this issue:

The package generator creates a Markdown file as license (LICENSE.md), but that incompatible to the Atom package website, which expects a LICENSE file without extension. If a Markdown file is for the license, the License-button on the website will remain greyed out.

Ideally, the website would work with LICENSE, LICENSE.md and maybe LICENSE.txt.

[winstliu]

All three should work, but I believe there's currently a problem with the backend where it's not recognizing any license files.

/cc @lee-dohm

[lee-dohm]

We know about the problem and I have a manual process that can go through and clean things up as a workaround for now. It's not a 100% thing, kind of intermittent. The website supports all three versions and even will do its best to detect if you only specify the license by name in the package.json.

[danielbayley]

+1. I noticed this recently too.

[mattstratton]

+1 This is occurring on https://atom.io/packages/linter-cookstyle as well. I have tried renaming LICENSE to LICENSE.md and that didn't seem to matter.

[lee-dohm]

As I stated above, this isn't an issue with the name of the file, it is an intermittent website issue.

[ce3a]

Same issues here https://atom.io/packages/language-dts

[lee-dohm]

Ran the batch process to update all the packages. Everyone's license should be there now.

[JustParsa]

hi there! My package likewise seems to be having this issue https://atom.io/packages/atom-ember-component

[JustParsa]

@lee-dohm ^

[pixxx]

Can't this intermittent website issue get fixed?

[felipecrp]

Same problem here. Package.json with license, github repository with license, but atom package page is missing license. Check https://atom.io/packages/highlight-cursor-line

[felipecrp]

Problem solved today. I think atom package site have a delay to update license.

[jasonrudolph]

I believe there's currently a problem with the backend where it's not recognizing any license files.

We've deployed some updates that should resolve the problem. As you publish a new package (or a new version of an existing package), atom.io should correctly display your package's license. We've also backfilled the license info on atom.io for all previously published packages. If you continue to observe this problem, please let us know. 🙇