Update examples.md #167
Update examples.md #167
Conversation
docs/examples.md
Outdated
| @@ -1,6 +1,6 @@ | |||
| # Examples | |||
|
|
|||
| For consistency and clarity of the following examples, we're going to use a simplified dbt project. In practice, the model governance features describe are _most_ beneficial for large dbt projects that are struggling to scale. | |||
| For consistency and clarity of the following examples, we're going to use a simplified dbt project. In practice, the dbt mesh features describe are _most_ beneficial for large dbt projects that are struggling to scale. | |||
There was a problem hiding this comment.
I'd really like to avoid using the term "dbt mesh". I have two reasons:
-
Right now, it doesn't mean anything to someone outside dbt Labs. Most of the industry is familiar with the idea of data mesh and the idea of data governance, so it would behoove us to use these widely-adopted terms. My vote is currently for "data mesh".
In practice, the data mesh features described are most beneficial for large dbt projects ...
-
This is more personal, but I have a hunch that "dbt mesh" is a good candidate to be trademarked by dbt Labs to represent the proprietary multi-project collaboration product within dbt Cloud. If this were to occur, I wouldn't want this open-source project to tied to dbt Labs' proprietary offering as the primary use-case -- particularly when it provides so much value for dbt-core users.
There was a problem hiding this comment.
I'm ok with updating this to be something else, but I think "data mesh" may be confusing / a bit too vague.
What if we went for something more verbose like "model governance and cross-project lineage"?
There was a problem hiding this comment.
Also just a note to self that if we update this: will need to make it consistent in all the docs for this package
There was a problem hiding this comment.
model governance and cross-project lineage
This makes sense to me! 👍🏻
There was a problem hiding this comment.
@graciegoheen I appreciate the consistency that this PR creates in our docs. Thank you for making this ✅
No description provided.