4 Commits

Include renames

Author	SHA1	Message	Date
jcoffey-dev	966241070e	Name Coffey Labs LLC as the copyright holder ... Coffey Labs is now Coffey Labs LLC, an Arizona limited liability company. Copyright lines and SPDX-FileCopyrightText headers naming Coffey Labs or John Coffey now name Coffey Labs LLC. Upstream copyright notices are unchanged.	2026-10-05 23:33:00 -07:00
jcoffey-dev	8ffdeea85d	Write down how a change reaches main, now that it is enforced ... main has a ruleset as of today: no force-push, no deletion, and a pull request with a green build to merge. CONTRIBUTING said nothing about any of it, and a contributor's first clue would have been a rejected push. No approving review is required. A review gate nobody can pass is not a gate, and this is a project with one maintainer; the build is the part that has to hold. The section also says why the rule exists rather than only what it is. The weekly release cuts from main on a Monday and ships whatever is there, so main is expected to be releasable continuously -- which makes "not finished" a thing that belongs behind a default-off switch or off main altogether, not a state main passes through on a Thursday. Administrators can bypass. That is written down as being for correcting the tree, not for skipping the path, because an undocumented bypass becomes the normal route.	2026-09-20 16:32:43 -07:00
jcoffey-dev	a63839f6b0	The repository's own .github, now that it is public ... SPEC 2.2a says INBUXA writes its own when the repository is first published, and it is. Until now the public repository carried Stalwart's: a security policy telling people to report vulnerabilities to Stalwart Labs, and a contributing guide whose policy is that pull requests from anyone not on upstream's vouched list are closed automatically. Neither is this project's, and both were being offered to anyone who looked. So: a security policy that says where to send a report, and what happens if it turns out to be upstream's bug rather than ours; a contributing guide that says what a fork of someone else's code needs from a contributor, including the clean-room question, since the record has to stay true; the Contributor Covenant; and a sponsor link. Upstream's two security documents move to .github-upstream/ beside its workflows -- kept, not used, not presented as ours. CI builds the server and compiles every test target, and deliberately runs no suite. The unit tests only build with the integration crate in the graph, and the integration suites want a STORE, fixed ports and a container apiece, so running them here would mean a tick that skipped everything or a cross that means "the runner has no Redis". The workflow says as much, so nobody has to rediscover it. Also ignores /artifact: two hand-built binaries, ~190 MB, one `git add -A` away from a public repository.	2026-09-20 00:00:05 -07:00
jcoffey-dev	7dae9b29fd	Import upstream v0.16.22, stripped ... Upstream commit: 474dd0229cb20cf513036619781ed97bd8073c3f Enterprise-only files removed or emptied: 63 Enterprise-only snippets removed: 117 in 50 files Dangling module declarations removed: 5 Cargo edits turning enterprise off: 14 Verification: clean Enterprise feature gates left for rebuilt features: 19 in 18 files Produced by tools/fork/strip.py. The full report is in docs/fork/strip-reports/ on main.	2026-09-18 10:21:56 -07:00