Skip to content

docs: update repository guidelines for new tools policy#445

Merged
mkmeral merged 3 commits intostrands-agents:mainfrom
agent-of-mkmeral:community-guidelines-update
Apr 10, 2026
Merged

docs: update repository guidelines for new tools policy#445
mkmeral merged 3 commits intostrands-agents:mainfrom
agent-of-mkmeral:community-guidelines-update

Conversation

@agent-of-mkmeral
Copy link
Copy Markdown
Contributor

@agent-of-mkmeral agent-of-mkmeral commented Apr 7, 2026

Description

Updates repository guidelines to clearly communicate that we are not accepting new tools, and instead recommend contributors publish standalone community packages using the extension template.

Related Issues

Closes #374

Changes

README.md

  • Added prominent [!IMPORTANT] notice near the top directing contributors to publish community packages
  • Updated the Contributing section to list what we accept (bug fixes, docs, perf improvements, tests) and link to the extension template and community catalog

CONTRIBUTING.md

  • Added New Tools Policy section explaining:
    • What we accept (bug fixes, docs, perf, tests)
    • What we don't accept (new tool PRs/issues)
    • Links to extension template, get-featured page, and contribution guide

.github/PULL_REQUEST_TEMPLATE.md

  • Added note about not accepting new tools with links to extension template and community catalog
  • Removed "New Tool" from the type of change options

.github/ISSUE_TEMPLATE/feature_request.yml

  • Added note in the template header about new tools policy
  • Clarified that we welcome feature requests for improvements to existing tools

Type of Change

Documentation update

Testing

  • Verified all links are correct and working
  • Verified markdown renders correctly

Checklist

  • I have read the CONTRIBUTING document
  • I have updated the documentation accordingly
  • My changes generate no new warnings

Updated README.md, CONTRIBUTING.md, PR template, and feature request
template to clearly communicate that we are not accepting new tools
due to maintenance and scalability concerns. Contributors are directed
to publish standalone community packages using the extension template.

Closes strands-agents#374
Replace 'Due to maintenance and scalability concerns' language with
a simpler, more positive framing: we don't accept new tools, instead
we recommend publishing as standalone community packages.

The message is the same but without over-highlighting internal concerns.
Comment thread README.md Outdated
Comment thread README.md Outdated
Reverts README.md to main per @mkmeral's feedback. The new tools
policy info lives in CONTRIBUTING.md only, keeping the README clean.
@mkmeral mkmeral merged commit 34146fe into strands-agents:main Apr 10, 2026
16 of 17 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Community] Update repository guidelines in README

3 participants