kubernetes
/
community
mirror of https://github.com/kubernetes/community.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
community/wg-lts
History
Tim Pepper 35e16f9ee4 wg-lts: add 
As per October 2018 discussion in SIG Release, k-dev mailing list,
etc., here's our proposal for the working group around evaluating
our support stance and making proposals for improvements.

While not required for a working group, this commit proposes an
initial charter for the WG LTS as this one has a notable potential
to at best bikeshed and at worst get mired in contention.  Documenting
scope, goals, deliverables seems like a reasonable way to aim for
a collaborative analysis of where we are and constructive suggestions
toward improvement.

Signed-off-by: Tim Pepper <tpepper@vmware.com>
 		2019-02-01 09:52:35 -08:00
..
README.md wg-lts: add 2019-02-01 09:52:35 -08:00
charter.md wg-lts: add 2019-02-01 09:52:35 -08:00

README.md

LTS Working Group

Answer the question: Does Kubernetes need a longer support term? If yes, figure out what that looks like for Kubernetes and propose this to the rest of the project. If no, figure out how to help end users cope with this and propose that to the rest of the project. If a proposal is accepted, the working group's mission will change to implement it. The working group is sponsored by SIG Release, but has the potential to span almost all SIGs. For more background see the WG formation proposal.

The charter defines the scope and governance of the LTS Working Group.

Stakeholder SIGs

  • SIG API Machinery
  • SIG CLI
  • SIG Node

Meetings

Organizers

Contact

Goals

  • Evaluate user/operator sentiment and support requirements.
  • Foster cross-vendor, subject matter expert led bug and security fixes for support streams. The project is more sustainable when this work is done once authoritatively in shared support branch(es), versus in parallel at all vendors.
  • Increase developer visibility on cross-release compatibility and stability issues.
  • If appropriate based on analysis, draft LTS KEP for SIG Release to operationalize.

We are an open and active working group, and we always welcome new additions!