Skip to content

Latest commit

 

History

History
82 lines (53 loc) · 3.96 KB

File metadata and controls

82 lines (53 loc) · 3.96 KB

Contributing

We welcome outside contributions to Kernel Design Agents through GitHub issues and pull requests.

For substantial changes to KDA itself, open an issue first so the proposed scope and approach can be discussed. Kernel wishlist submissions can go directly to a pull request as described below. Keep changes focused, use English for repository-facing content, and include any validation or supporting evidence relevant to the change.

Kernel Wishlist Submissions

Submit kernel optimization requests directly as pull requests (PRs) targeting wishlist; no issue is required. Follow the submission guide, copy the example into requests/<github-username>-<kernel-name>/, and keep the request details in that directory's README.md. The PR description can be brief and may link an existing discussion. The wishlist currently supports NVIDIA B200 and B300 GPUs only.

If you have an idea or need help preparing the files, discuss a kernel idea. Complete files and benchmark results are optional for that discussion. Merging a wishlist PR records the request; optimization progress and result links are tracked on the original PR.

Changes to the active issue form belong on main, and website changes belong on pages.

Licensing

By submitting a contribution, you agree that it may be distributed under the applicable terms in LICENSE:

  • Documentation, prompts, skills-style content, and assets are licensed under CC-BY-4.0.
  • Source code is licensed under Apache-2.0.

Third-party material must retain its original license and attribution information and must be documented in THIRD_PARTY_NOTICES.md when it is distributed with this project.

This project uses the Developer Certificate of Origin (DCO), not a Contributor License Agreement (CLA).

Signing Off Your Work

All contributors must sign off each commit. The sign-off certifies that the contribution is your original work, that you have the right to submit it under the applicable open-source license, or that another person who made the same certification provided it to you.

Use the --signoff or -s option when creating commits:

git commit -s -m "Add cool feature."

This appends a line like the following to the commit message:

Signed-off-by: Your Name <your@email.com>

Contributions containing commits without a valid sign-off will not be accepted.

Developer Certificate of Origin 1.1

Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

The canonical DCO text is available at developercertificate.org.