fix(radar): odrzucaj listy zamkniete w cudzym ekosystemie - #244
Merged
Merged
Conversation
The strategy seat's failing number: eight venues surfaced, three usable. 37%. Two gates already existed and both were right - a mail heading has to be a heading rather than the word in prose, and self-hosted or FOSS-only lists are rejected because a hosted service cannot qualify however the entry is worded. Neither catches a list that is simply somebody else's ecosystem. matteocrippa/awesome-swift has a mail section and will never take a Node CLI. A macOS-only app list will never take a hosted relay. Only the ecosystems this project is actually in pass: we ship a Node CLI and a hosted service, so a list named or described as belonging to another language or platform is the wrong list before the entry is written. Measured against the same eight venues the radar actually surfaced rather than argued for: it rejects awesome-swift, awesome-native-macosx-apps and awesome-n8n-templates, and keeps both of the ones that turned out usable - awesome-free-apps, which merged 51 pull requests in 90 days, and awesome-opensource-email. Three false positives removed, zero true positives lost. 37% becomes 60%. The remaining misses are a database client that is not a list at all and two FOSS lists the existing gate should have held, which is the next thing here rather than this one.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Słaba liczba stanowiska strategicznego: osiem miejsc podsuniętych, trzy użyteczne. 37%.
Dwie bramki już istniały i obie są słuszne — nagłówek pocztowy musi być nagłówkiem, a nie słowem w tekście, a listy self-hosted i FOSS-only są odrzucane, bo usługa hostowana nie zakwalifikuje się niezależnie od brzmienia wpisu.
Żadna z nich nie łapie listy, która jest po prostu cudzym ekosystemem.
matteocrippa/awesome-swiftma sekcję pocztową i nigdy nie przyjmie narzędzia w Node. Lista aplikacji tylko na macOS nigdy nie przyjmie hostowanego przekaźnika.Przechodzą wyłącznie ekosystemy, w których faktycznie jesteśmy: wysyłamy CLI w Node i usługę hostowaną.
Zmierzone na tych samych ośmiu miejscach, nie oszacowane
awesome-swift(swift),awesome-native-macosx-apps(macos),awesome-n8n-templates(n8n)awesome-free-apps— 51 mergy w 90 dniach,awesome-opensource-emailTrzy fałszywe trafienia usunięte, zero użytecznych straconych. 37% → 60%.
Reszta pudeł to klient bazodanowy, który w ogóle nie jest listą, i dwie listy FOSS, które powinna była zatrzymać istniejąca bramka — to następna rzecz tutaj, nie ta.