John Kellerman

I actually think this error belongs more in this repo. I've closed https://github.com/EclipseFdn/open-vsx.org/issues/2322.

Well, not sure what happened with my previous attempts, but working with @filiptronicek we are not able to reproduce this now. I'm concluding some kind of operator error.

Maybe leave this open for now to see if it reappears

@filiptronicek We're taking a different approach from VS Marketplace. What was the thinking?

@amvanbaren This could represent a pretty substantial visible change to our users/adopters. Is there an easy way to determine how may extensions would have what shows for their license change?

@amvanbaren @filiptronicek I've just about finished running `licensee` on all the extensions. I'm having to do it in batches because it makes enough GH API calls that I run into...

I tried a number of different permutations of license files and `license` entries in `package.json` to see how our system behaved. By and large, with one exception, it behaved as...

The above said, I think at a minimum, if an author specifies `license` in `package.json`, that's the text we should display and link to the provided license file. It's up...

Thinking about this some more, I think this is what open-vsx should do: - If no `license` in `package.json`, error on publishing. This happens today. - If no `license` in...

@amvanbaren No, I think the current behavior is fine. To wit, just a message that indicates either `No README available` or `No changelog available`.