Skip to content
This repository has been archived by the owner on Feb 27, 2023. It is now read-only.

Inconsistent terminology might be confusing #160

Open
alexbrand opened this issue Jun 20, 2018 · 0 comments
Open

Inconsistent terminology might be confusing #160

alexbrand opened this issue Jun 20, 2018 · 0 comments
Labels
area/documentation Issues or PRs related to documentation. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.

Comments

@alexbrand
Copy link
Contributor

We seem to have terms that we use interchangeably throughout the docs/code/metrics…
For example: replicate, synchronize, discover (services/endpoints), or backend vs upstream.. there might be more.

We should try to converge to a consistent set of terms and clean up user-facing documentation, metrics, and code (probably not high priority).
@alexbrand alexbrand added priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. documentation labels Jun 20, 2018
@projectcontour-bot projectcontour-bot added area/documentation Issues or PRs related to documentation. and removed kind/documentation labels May 9, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
area/documentation Issues or PRs related to documentation. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@alexbrand @projectcontour-bot