docs: skredytuj z nazwiska ludzi, ktorych to praca - #271
Merged
Merged
Conversation
…uilt The owner asked about forks. Four, and two of the people behind them have merged work here that names them nowhere. @Mohitingale13 contributed the HP, Lexmark, Sharp, Toshiba and Synology compatibility entries - five vendors in two days, each with the vendor's own published page as evidence. @slegarraga contributed the Elixir, Lua and Dart examples back on 2026-08-06 and I did not know those existed until today. The only contributor named anywhere was @kevinbytnar, on the Canon certificate case study. That page is also the only page on this site that ranks first for anything - "isrg root x1", position 1. Not a coincidence worth ignoring: a named contributor has a reason to send the link on, and a reader can see a real person stood behind the row rather than a scrape. Credit for device entries goes in data/devices.json and renders through the generator, so a future entry carries it without anybody remembering. The code examples are credited in place, next to a note that every example is run in CI - which is what makes contributing one worth somebody's evening, since a language nobody here writes daily stays correct rather than rotting. community-lead.md already said contributions get "credited by GitHub username when added". It was written down and not done.
Contributor
|
Thanks for including contributor attribution. I appreciate it and am glad to see the contributors being credited explicitly. |
Contributor
|
Thank you so much, @Mohitingale13! Contributor attribution felt like the right thing to do here, and I appreciate you taking the time to confirm it. Happy to help with follow-ups whenever useful. |
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
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.
Właściciel zapytał o forki. Cztery — a dwie osoby za nimi mają tu wmergowaną pracę, która nigdzie ich nie wymienia.
Jedynym skredytowanym gdziekolwiek był @kevinbytnar, w studium przypadku certyfikatu Canona.
I to nie jest przypadek wart zignorowania
Ta strona jest jedyną na tym serwisie, która rankuje na pozycji 1 —
isrg root x1.Skredytowany kontrybutor ma powód, żeby podać link dalej, a czytelnik widzi, że za wierszem stał prawdziwy człowiek, a nie scrape.
Jak to jest zrobione
Kredyt dla wpisów urządzeń idzie do
data/devices.jsoni renderuje się przez generator — więc przyszły wpis poniesie go bez niczyjej pamięci.Przykłady kodu skredytowane na miejscu, obok informacji, że każdy przykład jest uruchamiany w CI. To jest to, co czyni wniesienie przykładu wartym czyjegoś wieczoru: język, którego nikt tu nie pisze na co dzień, pozostaje poprawny zamiast po cichu gnić.
community-lead.mdjuż mówił, że kontrybucje są „credited by GitHub username when added". Było zapisane i niezrobione.