diff --git a/.github/CODE_OF_CONDUCT.md b/.github/CODE_OF_CONDUCT.md index 6e26b3f..55a7f7f 100644 --- a/.github/CODE_OF_CONDUCT.md +++ b/.github/CODE_OF_CONDUCT.md @@ -1,42 +1,5 @@ -# Contributor Covenant Code of Conduct +# Contributor Code of Conduct -## Our Standards +_be excellent to each other_ -Examples of behavior that contributes to creating a positive environment include: - -* Using welcoming and inclusive language -* Being respectful of differing viewpoints and experiences -* Gracefully accepting constructive criticism -* Focusing on what is best for the community -* Showing empathy towards other community members - -Examples of unacceptable behavior by participants include: - -* The use of sexualized language or imagery and unwelcome sexual attention or advances -* Trolling, insulting/derogatory comments, and personal or political attacks -* Public or private harassment -* Publishing others' private information, such as a physical or electronic address, without explicit permission -* Other conduct which could reasonably be considered inappropriate in a professional setting - -## Our Responsibilities - -Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior. - -Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful. - -## Scope - -This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers. - -## Enforcement - -Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at trimstray@gmail.com. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately. - -Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership. - -## Attribution - -This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version] - -[homepage]: http://contributor-covenant.org -[version]: http://contributor-covenant.org/version/1/4/ +thank you for coming to my Ted talk diff --git a/.github/FUNDING.yml b/.github/FUNDING.yml deleted file mode 100644 index 785e504..0000000 --- a/.github/FUNDING.yml +++ /dev/null @@ -1,2 +0,0 @@ -open_collective: trimstray -github: trimstray diff --git a/TOOL-TABLE-SCHEMA.md b/TOOL-TABLE-SCHEMA.md index cad3aa1..3a00b12 100644 --- a/TOOL-TABLE-SCHEMA.md +++ b/TOOL-TABLE-SCHEMA.md @@ -19,7 +19,6 @@ Use this exact column order and formatting for all tool lists in the repository. - **Creation Date** is especially valuable for legacy / classic Unix tools, early security utilities, and projects from the 1990s–early 2000s to give historical perspective. - **Stars** provides at-a-glance community adoption signal — useful for readers new to the field who want to prioritize widely trusted tools. -- Star counts change over time → include an "as of" month/year when the value was last verified (can be updated during periodic repo maintenance sweeps). - When adding or updating entries, fetch Creation Date and Stars directly from the GitHub repo page or API if possible. - For extremely old projects without GitHub presence (e.g. original tcpdump releases, early versions of OpenSSH), prefer the initial public release year in Creation Date and leave Stars as `—`. @@ -27,6 +26,6 @@ Use this exact column order and formatting for all tool lists in the repository. | Name | Vendor/Webpage | GitHub Repo | Brief Description | Tags | Latest Commit | Creation Date | Stars | |------|----------------|-------------|-------------------|------|---------------|---------------|-------| -| Vim | — | [vim/vim](https://github.com/vim/vim) | Highly configurable text editor for efficiently creating and changing any kind of text. | editor, text, cli, sysadmin, c | 2026-03-01 (v9.1 patch) | 1991-11-02 | 35.4k as of 2026-03 | +| Vim | — | [vim/vim](https://github.com/vim/vim) | Highly configurable text editor for efficiently creating and changing any kind of text. | editor, text, cli, sysadmin, c | 2026-03-01 (v9.1 patch) | 1991-11-02 | 35.4k | This format keeps tables readable, adds meaningful context without clutter, and aligns with the goal of making the book more educational for beginners while respecting the heritage of many tools listed.