Skip to content

About

Template repo for preparing CNCF Sandbox applications with checklist-driven GitHub issues

Resources

Contributing

Stars

2 stars

Watchers

0 watching

Forks

Latest commit

 

History

16 Commits

Folders and files

Repository files navigation

CNCF Sandbox Application

Project name: Replace with your project name

Official CNCF application issue: Filled in automatically when you run ./scripts/generate-submission.sh --create-issue

Checklist issues: Run ./scripts/bootstrap-issues.sh after creating your repo from this template.

This repository helps you prepare a CNCF Sandbox application.

Edit APPLICATION.md only for checklist answers and form content. This README shows progress and mirrors checklist issue/PR links (updated by automation).

Quick start

  1. Click Use this template to create your own copy of this repository.

  2. Clone and bootstrap checklist issues:

    git clone git@github.com:YOUR_ORG/YOUR_REPO.git
    cd YOUR_REPO
    ./scripts/bootstrap-issues.sh
  3. Commit bootstrap changes and push.

  4. Work in APPLICATION.md only:

    1. complete Your answer section
    2. Open a PR with Closes #N (issue link is on the checklist line)
    3. make sure you add the proper field_id to Application fields updated section: e.g. project_summary, maintainers_file.
  5. When every item is complete:

    ./scripts/generate-submission.sh --validate
    ./scripts/generate-submission.sh --create-issue

    You do not need to sync the CNCF form while working. At submit time, generate-submission.sh checks the live CNCF application template and maps your APPLICATION.md answers onto it.

See CONTRIBUTING.md for the full workflow.

How tracking works

Stage Checklist line shows
After bootstrap - [ ] … (Issue: [#N](…))
After you open a PR with Closes #N - [x] … (PR: [#M](…)) in APPLICATION.md and this README
After the PR merges Issue closes; progress on main matches

Application progress

Application progress: 0 / 29 items complete (0%)
░░░░░░░░░░░░░░░░░░░░ 0%

Application checklist

Each row links to the matching section in APPLICATION.md. A PR with Closes #N checks the box and switches (Issue: …) to (PR: …) automatically — do not edit these lines by hand.

  • Reviewed all prerequisite documentation (Issue: #ISSUE_READ_PREREQUISITES)
  • Project summary and description drafted (Issue: #ISSUE_PROJECT_SUMMARY)
  • This is a reusable open source project designed for broad adoption, not a reference architecture, reference implementation, or demonstration of patterns (Issue: #ISSUE_REUSABLE_PROJECT)
  • Org and repository URLs documented (Issue: #ISSUE_ORG_AND_REPO_URLS)
  • Website URL documented (Issue: #ISSUE_WEBSITE_URL)
  • Roadmap and context documented (Issue: #ISSUE_ROADMAP)
  • Contributing guide linked (Issue: #ISSUE_CONTRIBUTING_GUIDE)
  • Code of Conduct linked (Issue: #ISSUE_CODE_OF_CONDUCT)
  • Adopters list linked or rationale documented (Issue: #ISSUE_ADOPTERS)
  • MAINTAINERS file created with required columns (Issue: #ISSUE_MAINTAINERS_FILE)
  • Security policy linked (Issue: #ISSUE_SECURITY_POLICY)
  • Standard/specification details documented (Issue: #ISSUE_STANDARD_OR_SPEC)
  • Business product/service separation documented (Issue: #ISSUE_PRODUCT_SEPARATION)
  • Why CNCF drafted (Issue: #ISSUE_WHY_CNCF)
  • Landscape benefit drafted (Issue: #ISSUE_LANDSCAPE_BENEFIT)
  • Cloud native fit drafted (Issue: #ISSUE_CLOUD_NATIVE_FIT)
  • Cloud native integration drafted (Issue: #ISSUE_CLOUD_NATIVE_INTEGRATION)
  • Cloud native overlap drafted (Issue: #ISSUE_CLOUD_NATIVE_OVERLAP)
  • Similar projects documented (Issue: #ISSUE_SIMILAR_PROJECTS)
  • Landscape listing status documented (Issue: #ISSUE_LANDSCAPE_LISTING)
  • LFX Insights status documented (Issue: #ISSUE_LFX_INSIGHTS)
  • If the project is accepted, I agree to donate all project trademarks and accounts to the CNCF (Issue: #ISSUE_TRADEMARK_AGREEMENT)
  • If the project is accepted, I agree the project will follow the CNCF IP Policy (Issue: #ISSUE_IP_POLICY_AGREEMENT)
  • License exception review completed (Issue: #ISSUE_LICENSE_EXCEPTION)
  • Dependency license compliance verified (Issue: #ISSUE_DEPENDENCY_LICENSES)
  • Domain Technical Review linked (if applicable) (Issue: #ISSUE_DOMAIN_TECHNICAL_REVIEW)
  • Application contact emails and signatory information completed (Issue: #ISSUE_CONTACT_INFORMATION)
  • CNCF contacts and additional information completed (Issue: #ISSUE_ADDITIONAL_INFORMATION)
  • Final review complete and application submitted to CNCF (Issue: #ISSUE_FINAL_REVIEW)

References

License

Apache License 2.0 — see LICENSE.

About

Template repo for preparing CNCF Sandbox applications with checklist-driven GitHub issues

Resources

Contributing

Stars

2 stars

Watchers

0 watching

Forks

Releases

Packages

Used by

Contributors

Languages