Repository navigation
refactor: rename capstone → datamesh (code) / "the final project" (prose) - #15
Closed
patterncatalyst wants to merge 1 commit into
Closed
patterncatalyst wants to merge 1 commit into
patterncatalyst wants to merge 1 commit into
Conversation
…t" (prose) Remove the school-framing word "capstone" from the project. Code identifiers become `datamesh`; descriptive prose becomes "the final project". The published site is now capstone-free. Code (examples/lgtm-datamesh): - proto package capstone.inventory.v1 → datamesh.inventory.v1; proto/capstone → proto/datamesh; gRPC stubs regenerated with buf into gen/datamesh/ across all three services (old gen/capstone removed). - Helm umbrella chart charts/capstone → charts/datamesh (name, release, labels, image repo prefix, part-of). - minikube path renamed consistently: profile, namespace, Postgres cluster (datamesh-postgres, db/owner datamesh/datamesh_app), Kafka cluster (datamesh-kafka), OTel service.namespace, Grafana dashboards/PromQL. - scripts setup-capstone-profile.sh / bootstrap-capstone.sh → setup-datamesh-profile.sh / bootstrap-datamesh.sh; Avro schema namespace. - OpenShift path (already named datamesh) had stale capstone refs fixed, including a broken part-of=capstone label selector. Assets: the three 17-capstone-* figure pairs → 17-final-project-*; in-figure caption text and the capstone.inventory.v1 label updated. Site/prose: all chapters, deck sources, README/PRD/onboarding/HTML/_config and _plans updated; diagram includes rewired; root scripts audit-fedora-prereqs.sh and setup-strimzi.sh fixed (stale setup-capstone-profile.sh reference). The two cited archive decision-log files renamed to final-project-*.md with content and CAP-xxx IDs preserved. Left verbatim as historical/external audit trail (non-published): the frozen README.archive.md, external parent-repo paths, the inert site.capstone fork-compat branch in _layouts, and the _plans/archive build-diaries. Verified: buf lint clean, service imports OK, helm template clean, jekyll build clean, forbidden-syntax/cross-references/liquid-collisions all clean, zero "capstone" in the rendered _site.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Removes the school-framing word "capstone" from the project. Code identifiers become
datamesh; descriptive prose becomes "the final project". The published site is now completely capstone-free.Stacked on #14 (the chapter-template/readability PR) because it also edits
_docs. Review/merge #14 first; I'll retarget this PR's base tomainonce #14 lands.Scope (219 files originally referenced "capstone")
Code (
examples/lgtm-datamesh)capstone.inventory.v1→datamesh.inventory.v1;proto/capstone→proto/datamesh; gRPC stubs regenerated with buf intogen/datamesh/across all three services (oldgen/capstoneremoved).charts/capstone→charts/datamesh(name, release, labels, image-repo prefix,part-of).datamesh-postgres, db/ownerdatamesh/datamesh_app), Kafka cluster (datamesh-kafka), OTelservice.namespace, Grafana dashboards/PromQL selectors.setup-capstone-profile.sh/bootstrap-capstone.sh→setup-datamesh-profile.sh/bootstrap-datamesh.sh; Avro schema namespace.datamesh) had stalecapstonerefs fixed, incl. a brokenpart-of=capstonelabel selector.Assets — the three
17-capstone-*figure pairs →17-final-project-*; in-figure caption text +capstone.inventory.v1label updated.Site/prose — all chapters, deck sources, README/PRD/onboarding/HTML/
_config/_plans; diagram includes rewired; rootscripts/audit-fedora-prereqs.sh+setup-strimzi.shfixed (one stale renamed-script reference). The two archive decision-log files cited by published chapters renamed tofinal-project-*.md(content + CAP-xxx IDs preserved).Verification
buf lintclean · service imports OK ·helm template charts/datameshcleanjekyll buildclean ·forbidden-syntax/check-cross-references/check-liquid-collisionsall clean_siteLeft verbatim (non-published historical/external audit trail)
README.archive.md(frozen snapshot), external parent-repo paths inexamples/.../README.md, the inertsite.capstonefork-compat branch in_layouts/tutorial.html, and the_plans/archive/build-diaries (real commands as run). TheCAP-xxxdecision IDs were kept (traceability). Say the word if you want the archive scrubbed too — it's a mechanical follow-up.Still needs a manual step
The
data-mesh-openshiftdeck bundles a rasterizedcapstone.inventory.v1figure; its source was updated but the.pptxneeds a rebuild (no localnode_modules). Flagged, not done — decks are the last deliverable anyway.