Draft guidelines on how substantial an operator has to be to become an independant project

cncf / toc

⚖️ The CNCF Technical Oversight Committee (TOC) is the technical governing body of the CNCF Foundation.

https://cncf.io

1.67k stars 632 forks source link

Draft guidelines on how substantial an operator has to be to become an independant project #1223

Open jberkus opened 9 months ago

jberkus commented 9 months ago

CNCF is starting to get a lot of Operators submitted as projects in the Sandbox queue. We do have some operators as projects, most notably Strimzi and Rook. However, it is also clear that some operators should instead be subprojects of the software they are operators for, rather than their own projects.

Drafting guidelines for how to make this decision would save time for evaluating the Sandbox queue.

@TheFoxAtWork

TheFoxAtWork commented 9 months ago

Thank you @jberkus for filing this issue.

I think one of the core items the TOC discussed on the most recent sandbox call and in previous discussions breaks this problem into a few different components:

When should a operator be a core integration/offering a project?
Should an operator, to exist as a standalone project, include other capabilities, such as exporters, controllers, plugins, hooks that provide adopters a "solution" to a problem set?

raravena80 commented 9 months ago

TheFoxAtWork commented 5 months ago

Assigning this to myself to draft language on this later.