CF for K8s should have a clear contributor strategy that encourages community contribution and engagement.

[Birdrock]

Is your feature request related to a problem? Please describe. Currently, cf-for-k8s does not have a contributor strategy or cohesive governance strategy.

Describe the solution you'd like cf-for-k8s should have a contribution strategy - this is the CNCF contributor strategy boilerplate, which we can use as a base.

Additional context The first steps are to reach Sandbox status.

• [ ] Requirements:
  • [ ] CNCF Code of Conduct
    • [ ] Template
    • [ ] Decide if COC enforcement will be handled by the project or by the CNCF
      • [ ] CNCF is a good option for young/small projects. They will provide contact.
    • [ ] If handling it yourself: decide who are the contacts and how to deal with a maintainer being reported, or a contact being reported. Need more than one contact.
      • [ ] CNCF can provide training in COC report handing, on request by a project
      • [ ] If the COC enforcement body is your maintainers, then you need to have a policy to escalate to CNCF if the report is against a maintainer.
  • [ ] Adhere to CNCF IP Policy
  • [ ] CONTRIBUTING.md containing basic “how to contribute” (Harbor example)
    • [ ] Template
  • [ ] Light project roadmap, at least an easily findable list of TODO items or issues
  • [ ] LICENSE
    • [ ] Template
      • [ ] You need to edit "Copyright [yyyy] [name of copyright owner]".
      • [ ] Replace [yyyy] with the current year.
      • [ ] Replace [name of copyright owner] with "The PROJECT Authors", e.g. "The Kubernetes Authors" or "The Helm Authors".
    • [ ] CNCF strongly recommends Apache 2.0
• [ ] Good to Have:
  • [ ] Governance.md with details about leadership (CoreDNS example)
  • [ ] OWNERS.md file (Helm example)
    • [ ] Explain what is it, how it's used, what needs to be in it and if you can reference another source of truth

[cf-gitbot]

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/176082042

The labels on this github issue will be updated when the story is started.

[bkrannich]

@Birdrock: I'm wondering how this is related to the major rework of CF community over at https://github.com/cloudfoundry/community

[Birdrock]

@bkrannich This is an independent effort from the cf-for-k8s team. We have been in contact with people working on the CF community rework, and intend to be compliant with those efforts. It will be an ongoing reconciliation to best serve the open source community at large and the CFF.

[bkrannich]

@Birdrock: Thank you very much for clarifying! I'm all in for more inclusive community engagement beyond CFF. When you write that the intend is to be compliant with the updated CFF governance, it sounds like you want to go beyond what will be manifested there for cf-for-k8s, right? If so, I'd be interested in the "delta" and would ask the question if this delta should be "fed into" the CFF governance update process.

[voelzmo]

Hey @Birdrock, could you please help me understand a bit more about the "why" behind this issue? I might have missed a few discussions about this, sorry.

[Birdrock]

Hi @voelzmo. We decided to establish and codify our practices; this is independent of the CF community rework, but should align nicely.

The motivation for this is to establish more transparency to foster communication with the community. We would like the contribution model and engagement to be clear to encourage participation. As we move forward from our 1.0.0 release, it seems to be the right time to establish governance to set expectations for current and potential contributors.

There haven't been discussions at large, yet - modeling after the CNCF sig-contributor-strategy is a good starting point, where we can gather input from interested parties and iterate from there.

[Birdrock]

@bkrannich At present I'm unsure of what the delta will be. We learned about the community work after embarking on this; as such, there are some unknowns. I think it would serve us well to align closely with the community work being done and pilot it as an alpha consumer.This will allow the cf-for-k8s community to drive out details that are important to us but not presently covered by cloudfoundry/community.

I'll make an edit to the issue to the effect that we are using CNCF sandbox as boilerplate to nucleate the process, with longer term alignment along CFF. I would invite input from interested parties to ensure things are transparent and appropriate.

[loewenstein]

cc @chipchilders

[chipchilders]

This is outstanding to see! The use of the CNCF outline for best practices is super useful, and we should try to use a version of that moving forward across CFF projects. @Birdrock showed up at the CFF tech governance call today and walked us through his goal with this issue, and it is completely in line with the broader changes we are hoping to make across all CFF projects. Namely, driving more inclusion, transparency and clarity into how all CFF projects operate (and how cross-project coordination happens).