Difference between revisions of "PKC DevOps/Goal"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
The foremost goal of the PKC DevOps practice is to ensure [[composability]] | The foremost goal of the PKC DevOps practice is to ensure [[composability]] in all three levels, [[Data Content]], in [[Collaborative Workflow]], and in [[Deployment Infrastructure]]s. | ||
#Lower the entry-barrier for digitized [[value production]] and [[value exchange|exchange]] workflow. | #Lower the entry-barrier for digitized [[value production]] and [[value exchange|exchange]] workflow. | ||
#Allow for a secure and user-friendly [[Pull Request]] for all kinds of [[DevOps workflows]]. | #Allow for a secure and user-friendly [[Pull Request]] for all kinds of [[DevOps workflows]]. | ||
Revision as of 14:51, 7 August 2021
The foremost goal of the PKC DevOps practice is to ensure composability in all three levels, Data Content, in Collaborative Workflow, and in Deployment Infrastructures.
- Lower the entry-barrier for digitized value production and exchange workflow.
- Allow for a secure and user-friendly Pull Request for all kinds of DevOps workflows.
- Create a PKC namespace that is sound, precise, and terminable by each development cycle.