Notes on distribution, possible name fixer

Author: fileformat

docs/_drafts/fix.md

@@ -0,0 +1,21 @@
+---
+title: Fixing file names
+h1: Fixing file names that are found
+---
+
+I think this should be a separate program (`fnfix`, `namefix`, etc) but still part of this project.
+
+Several levels of fixing:
+
+- basic: just nulls and UTF-8
+- portable: anything that causes cross-platform issues
+- ascii: convert every character to ASCII
+- posix: convert everything to POSIX-safe
+- shellsafe?
+
+Code:
+
+- each rule should have an optional `fixlevel` and `replace`
+- program takes a directory name and fixes all files in it
+- optional `recursion` flag to go into subdirectories
+- optional `dryrun` flag to show what it would do

docs/_drafts/where-to-find.md

@@ -0,0 +1,35 @@
+---
+title: Where to find namelint
+---
+
+Places where to find and use namelint:
+
+- [ ] Download binary from Github
+- [ ] Download `.deb` and install
+- [ ] Run Docker image from DockerHub (and GHCR, etc)
+- [ ] [npm](https://www.npmjs.com/)
+- [ ] [Homebrew](https://docs.brew.sh/)
+- [ ] [Github Actions Marketplace](https://github.com/marketplace?type=actions)
+- [ ] [Gitlab CI/CD Catalog](https://gitlab.com/explore/catalog)
+
+## Eventually
+
+- [ ] `.deb` bundled with Debian-based Linux distributions
+- [ ] RPM and bundled with RedHat-based Linux distributions
+- [ ] Other CI runners
+  - Argo
+  - Azure DevOps
+  - Bitrise
+  - CircleCI
+  - Google Cloud Build
+  - Spinnaker
+  - TeamCity
+  - Travis
+  - [List at Awesome CI](https://github.com/ligurio/awesome-ci)
+- [ ] Other npm packagers: [Github Packages](https://docs.github.com/en/packages/working-with-a-github-packages-registry/working-with-the-npm-registry), [jsr.io](https://jsr.io/)...
+- [ ] [Mac App Store](https://www.apple.com/app-store/)
+- [ ] [Microsoft Store](https://apps.microsoft.com/home)
+- [ ] [Chocolatey](https://chocolatey.org/)
+- [ ] FreeBSD: [ports](https://ports.freebsd.org/cgi/ports.cgi)
+- [ ] NetBSD: [pkgsrc](https://www.pkgsrc.org/)
+- [ ] SUSE: [packagehub](https://packagehub.suse.com/)

docs/_posts/2024-08-17-prior-art.md

@@ -8,7 +8,9 @@ IMHO, anything that isn't in Rust or C/C++ is going to be too high level and not
 
 - [**notox**](https://github.com/Its-Just-Nans/notox) - Rust, a command line utility that reports (and optionally fixes) toxic file names
 
-- [**ls-lint**](https://ls-lint.org/) - Go, focused on file name conventions ([source](https://github.com/loeffel-io/ls-lint))
+- [**ls-lint**](https://ls-lint.org/) - Go, focused on file name conventions ([source](https://github.com/loeffel-io/ls-lint)).  It has a [Github Action](https://github.com/ls-lint/action) and an [npm package](https://www.npmjs.com/package/@ls-lint/ls-lint).
+
+- [pre-commit-hooks](https://github.com/pre-commit/pre-commit-hooks) - Python, includes some file name checks ([check-case-conflict](https://github.com/pre-commit/pre-commit-hooks/blob/main/pre_commit_hooks/check_case_conflict.py) is especially interesting).  The overall [pre-commit framework](https://pre-commit.com/) should be supported by namelint.
 
 - [detox](https://github.com/dharple/detox) - C, renames files to make them easier to work with under Linux and other Unix-like
 operating systems