Let's create 'pipe-cd/community-plugins' repo

[t-kikuc]

What we want

• Create a 'community-plugins' repo under the pipe-cd org
• Store and develop plugins contributed from the community

Why we want

• To create an aggregated location for maintenance and usage to make it easier for developers and users
• To provide a more sustainable and reliable location compared to individual repos
• To make the pace of developing plugins faster
  • Avoid adding plugins to pipe-cd/pipecd, as review and maintenance become more challenging as the number of plugins increases

What has been roughly decided

Directory Structure

pipecd-community-plugins/
├── plugins/
│    └── <plugin-name>/
│        ├── README.md
│        ├── go.mod
│        └── (and other plugin code)
├── CODEOWNERS
├── CONTRIBUTING.md
├── LICENSE
├── README.md
etc.

License

Apache License 2.0
(the same as pipe-cd/pipecd)

Points to be decided

• Flow and requirements for adding a new plugin to the repo
• Who will lead the maintenance of each plugin?
  • I want at least one person besides the PipeCD core maintainers
• Review/merge rules
  • Who (Based on CODEOWNERS seems good)
  • How many reviews
• Release flow
  • when, who
  • Versioning (semver)
    • Independent versioning for each plugin?
    • How to manage version dependencies with PipeCD core/SDK
• CI
  • lint, test, security scanning...
  • Should test level depend on the plugin?
• How to handle documentation for each plugin?
  • Where to write
  • What format to use?
    • Want to standardize how to document configuration fields and supported features
• Should we have Stability Levels? (Alpha/Beta/Stable)
  • Then, what should be the criteria?

Reference Repos

• OpenTelemetry Collector Contrib
• Backstage Community Plugins
• Falco plugins

[t-kikuc]

Now I'm preparing this repo.
Wait until publication!

[t-kikuc]

It's already opened!
https://github.com/pipe-cd/community-plugins