Dave Verwer

In some ways, we're already rating packages with our score. Yes, that score isn't being published right now but we have plans to expose that in some way, at some...

Alright, I just did some more investigation into this and here's what it'd look like. Our top score is currently 87 points, but there are very few packages that make...

I also just renamed this issue. The more I've thought about this today the more I'm convinced that this is our "Package Quality Score" that we've been talking about. Yes,...

Just an extra bit of context, they tagged me the other day to ask about the included plugin. https://github.com/onevcat/Kingfisher/discussions/1952 It's still our problem as I'd not expect it to raise...

Yes, this has been on my mind for a while too. What we really need is to replace the FAQ, and especially the build FAQ which is so hidden even...

I’ll let @finestructure handle the Linux case as he knows far more about that side of things, but I can chime in on the iOS/watchOS/tvOS issue. I added your package...

> It's probably not a typical result in the sense that the ci bot is in there but I think it hints at another potential issue and one where stats...

> We'll probably have to spam proof the metadata file at some point... Almost certainly, but the fact that it's a file in a git repository makes it immune to...

> Should we push towards populating the author field via metadata entirely instead of trying to parse it from git? That's a good idea, but we should have all other...

There's a part of me that wants to still parse out author information from the git repository. One problem with relying completely on the metadata file is that when it...