docs: overhaul contributing and maintenance docs for end-of-year 2023

[JoshuaKGoldberg]

Overview

Applies what I've personally found to be reasonable and usable contributing and maintenance processes as an iteration to the existing docs. Includes:

• General docs:
  • Splitting a new .github/DEVELOPMENT.md out of .github/CONTRIBUTING.md
  • Renaming "JS Foundation" to "OpenJS Foundation", per the foundation's rename
  • Split sentences to one per line (as if https://github.com/JoshuaKGoldberg/sentences-per-line were enabled)
• Issues:
  • Added two new issue types: documentation and repository tooling
  • Disabled filing a new blank issue
  • Streamlined the contents of the issue templates a bit, and added some emojis
  • Used the new GitHub Issue Forms instead of .md templates
• Pull requests:
  • Streamlined the template
• Labels:
  • Renaming labels to include area: or type: prefixes
  • Switching from needing an explicit unconfirmed-bug to opting into status: ... labels after triage
• Switching from the old Gitter to a new Discord
• Switching from requiring rebasing to merging

Does not include likely followups:

• Renaming the master branch to main
• Enforcing any formatting/spellchecking/style with any new tooling
• Set up commit/PR linting to enforce PR titles and nothing else, per squash merging

Fixes #5036. Fixes #5037.

[JoshuaKGoldberg]

A nitpick on my end: unnecessary trailing / slashes at the end of URLs irritate me. 😄

[plroebuck]

Web server always assumes it's serving a file, unless the URL ends in a directory separator.

If the URL is to a directory, the server will append the directory index file (typically 'index.html') to the URL before it tries. If the server fails to return a file, it appends the directory separator to the path and retries as a directory.

Thus doing it this way causes twice the number of network calls needed for every directory URL without a trailing directory separator.

Apache: Mapping URLs to Filesystem Locations #DocumentRoot

[voxpelli]

@plroebuck Thats something that eg Apache does internally – it’s not something done through multiple requests – and eg plain Node.js doesn’t do anything like that at all

@JoshuaKGoldberg Not sure I like this though, the one with the slash in the end is the more “correct” one 😜

[JoshuaKGoldberg]

Haha how do we define "correct" here... per some specs the trailing slash is more correct. But end-users are generally told to visit URLs without saying the slash.

[coveralls]

coverage: 94.337%. remained the same
when pulling 7142832 on JoshuaKGoldberg:overhaul-contributing-and-maintenance-docs
into b41e985 on mochajs:master.

[voxpelli]

Looking good overall, will give it a proper review once I’m at a computer again (my bus was late so I’m reviewing from my phone in the winter cityscape 🥶)

[voxpelli]

@JoshuaKGoldberg We should maybe investigate adding eg https://github.com/JoshuaKGoldberg/sentences-per-line later? To document / enforce such stylistic choices and making it easier for contributors to follow them?

[Uzlopak]

Didnt we want a "Checkbox I want to provide a PR"

[JoshuaKGoldberg]

We're discussing this now. Our consensus is:

1. We don't believe the benefits of a pristine Git history to be worth the cost of asking everyone to maintain that history
2. Squash merging PRs using their title + description preserves a relatively clean history
3. We'll switch to squash merging always, and only enforcing conventions on the PR title
4. We can therefore remove commit linting for anything other than file formatting

[Uzlopak]

LGTM

[JoshuaKGoldberg]

💡 shorter name good!

Suggested change

	name: 📝 Documentation
	title: "📝 Documentation: <short description of the request>"
	name: 📝 Docs
	title: "📝 Docs: <short description of the request>"