What is the feature request? What problem does it solve?
The viewer or repo visitor, may be a single engineer or a large company.
Suggested solution
Create two separate Journey tracks, and link to the project README.md. Add two buttons at the end of the Data Journey and Versatile Data Kit section.
Data Engineer or Data Analyst or Data Practitioner Journey
In case of a single engineer, that person is the direct data practitioner, who needs to understand the minimalistic (bare min) of a functional VDK installation suggested (without or with control-service), to have the ETL up and running. The focus is on the VDK Data Framework.
DevOps or DataOps Journey
In case of a large company, the solution evaluators who decide for tools and adoption, may not necessarily be the end data practitioners. They may put themselves in the shoes of the data practitioners to evaluate, using the other Data Practitioners Journey. So the focus with DataOps Journey is rather continuous data management, clear role-based responsibilities for easier processes, and workloads or big data governance, including troubleshooting and monitoring. Explain how to install to production and upgrade.
Additional context
This task may be additionally split to two smaller tasks per Journey track, and those could be scoped with multiple tasks each, for example create the text then create the video explaining the text.
What is the feature request? What problem does it solve?
The viewer or repo visitor, may be a single engineer or a large company.
Suggested solution
Create two separate Journey tracks, and link to the project README.md. Add two buttons at the end of the Data Journey and Versatile Data Kit section.
Data Engineer or Data Analyst or Data Practitioner Journey
In case of a single engineer, that person is the direct data practitioner, who needs to understand the minimalistic (bare min) of a functional VDK installation suggested (without or with control-service), to have the ETL up and running. The focus is on the VDK Data Framework.
DevOps or DataOps Journey
In case of a large company, the solution evaluators who decide for tools and adoption, may not necessarily be the end data practitioners. They may put themselves in the shoes of the data practitioners to evaluate, using the other Data Practitioners Journey. So the focus with DataOps Journey is rather continuous data management, clear role-based responsibilities for easier processes, and workloads or big data governance, including troubleshooting and monitoring. Explain how to install to production and upgrade.
Additional context
This task may be additionally split to two smaller tasks per Journey track, and those could be scoped with multiple tasks each, for example create the text then create the video explaining the text.