Re: an interesting read, about "Cloud Native"
I agree that the mission section contains mechanics. It does contain a mission statement. Perhaps, mechanics are best separated. A separate “Cloud Native Qualities” section could include not only these mechanics, but softer properties of values held dear by the foundation (e.g. immutable infra, automatic discovery, self-healing, etc.).toggle quoted messageShow quoted text
While I don’t disagree with Brian’s point that VMs are currently not explicitly included, they are not implicitly excluded either. With the vast amount of work, energy, effort it takes the foundation to track and steward the container ecosystem, I question whether this group (the foundation) will be successful if it tries to explicitly include consideration for VMs within the scope charter as well. Albeit not focused on microservices architectures, other foundations (even within the Linux Foundation like the OVA) are saddled with VM-specific charters. Understanding many organizations will run CNCF container projects within or pointed at VMs, is the lack of explicit inclusion ok or do people feel like there needs to be a specific statement here?
With respect to the list of developer responsibilities, I’ll tack-on security as another responsibility.