* style-guide: use the new note syntax
* MAINTAINERS: use the new note syntax, use full month names
* CONTRIBUTING: use the new note syntax
* maintainers-guide: use the new note syntax
* CLIENT-SPECIFICATION: use the new note syntax
* COMMUNITY-ROLES: use the new note syntax
* git-terminal: use the new note syntax
---------
Co-authored-by: K.B.Dharun Krishna <kbdharunkrishna@gmail.com>
* Add notes about placeholders and some examples
* Apply suggestions from code review
Co-authored-by: CleanMachine1 <78213164+CleanMachine1@users.noreply.github.com>
* Use `tokens` instead of `things`
Co-authored-by: Muhammad Falak R Wani <falakreyaz@gmail.com>
Co-authored-by: CleanMachine1 <78213164+CleanMachine1@users.noreply.github.com>
Co-authored-by: Muhammad Falak R Wani <falakreyaz@gmail.com>
I have fixed a grammatical mistake (specifically, a lack of number agreement). Previously, the sentence in question did not, construed strictly, make sense. Also, I'm doing this to practice doing pull requests!
Cleaned up translation guidelines:
- Reworded and simplified the first paragraph.
- Do not require the optional BCP47 region code for language tags.
- Do not require the existence of the relative English page before
adding a new page in a different language.
- Fix spelling and wording.
the cla-assistant link leads to a page requesting the user to sign it, which may not be as friendly
since prospective contributors may want to simply read the CLA without a prompt to sign it.
- moved one entry from the general guidelines, since now there's a specific section for tokens;
- reordered and numbered the entries, for clarity and ease of reference
- rewrote some passages for clarity and conciseness.
- adjust whitespace & line breaks to make the markdown source more readable and consistent
- remove "we"/"our", to avoid reinforcing the "us vs. them" paradigm
- clarify a couple passages
- remove obsolete license agreement notice, now covered by the CLA
- remove redundant (and oddly specific) plea for contributions and the end of the document,
since there's already one at the beginning
- remove a redundant example of commit message format
* add subsections to "submit a PR" section
this allows the reader to visually separate the instructions and makes the longer git-command section less prone to trigger a TLDR (heh) when reading this part.
also, line wrapping tweaks, split a paragraph into two, and reword a couple passages for clarity
* compact the list of git commands
* CONTRIBUTING: greatly simplify the PR instructions
plus some wording tweaks here and there
* improve instructions to use tldrl
* brace expansion is not as common in the wild
removing it keeps the examples of unix features to a manageable/readable 3
* use actual commands in the git section
* use only one-liners on the git section
* add subsection header for commit message
* slight reword of licensing note
Lena
K.B.Dharun Krishna
dz-at-tc
Cornelius Roemer
Emily Grace Seville
Muhammad Falak R Wani
Sherman Hui
9tykeshav
marchersimon
Miles Glapa-Grossklag
bl-ue
Owen Voke
FantasyCookie17
Lucas Gabriel Schneider
Quinn Vissak
Jacob Hrbek
Waldir Pimenta
fejx
Zlatan Vasović
LinuxOnTheDesktop
Agniva De Sarker
Marco Bonelli
Marco Bonelli
Amy Martin
Yash Sharma
Igor Shubovych
Ruben Vereecken