From b144623a7ba2f3317e8bb0b537dd8dca62749bd7 Mon Sep 17 00:00:00 2001 From: Leigh <351529+leighmcculloch@users.noreply.github.com> Date: Mon, 7 Sep 2026 16:04:05 +1000 Subject: [PATCH 01/15] Revise contribution guidelines Updated guidelines for contributing to the Stellar project, including clearer instructions on discussions, proposals, and pull requests. --- CONTRIBUTING.md | 102 ++++++++++++++++++++++-------------------------- 1 file changed, 46 insertions(+), 56 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index c23b25b..e2c248a 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -1,67 +1,57 @@ # How to contribute to a Stellar project Your contributions to the [Stellar network](https://www.stellar.org/) will help improve the world’s -financial infrastructure, faster. +financial infrastructure. -We want to make it as easy as possible to contribute changes that help the Stellar network grow and -thrive. There are a few guidelines that we ask contributors to follow so that we can merge your -changes quickly. +We want to make it as easy as possible to contribute to Stellar in ways that make the network grow +and thrive. There are a few guidelines that we ask contributors to follow so that we all work +effectively together. -## Getting Started - -* Make sure you have a [GitHub account](https://github.com/signup/free). -* Create a GitHub issue for your contribution, assuming one does not already exist. - * Clearly describe the issue including steps to reproduce if it is a bug. -* Fork the repository on GitHub. - -### Minor Changes - -#### Documentation - -For small changes to comments and documentation, it is not -always necessary to create a new GitHub issue. In this case, it is -appropriate to start the first line of a commit with 'doc' instead of -an issue number. - -## Finding things to work on - -The first place to start is always looking over the current GitHub issues for the project you are -interested in contributing to. Issues marked with [help wanted][help-wanted] or are usually pretty -self-contained and a good place to get started. - -The Stellar Development Foundation also uses these same GitHub issues to keep track of what we are -working on. +> [!TIP] +> The Stellar network is open, decentralised, and programmable. For many ideas you may have, they can +> be built without changes to the projects hosted here. Want to contribute to Stellar? Build on Stellar! +> And share your feedback in the forums listed below. -Before starting work on an issue it can be a good idea to communicate on the issue, discussing -what the solution might look like, and if it would make sense to contribute to it. +To contribute to the work of maintaining the projects hosted here the biggest impact contributions +are in discussions, sharing new ideas, reporting bugs, and sharing experience reports. -Of course, feel free to create a new issue if you think something needs to be added or fixed. - - -## Making Changes - -* Create a feature branch from where you want to base your work. - * This is usually the main (or master) branch. - * Please avoid working directly on the `main` (or `master`) branch. -* Make sure you have added the necessary tests for your changes and make sure all tests pass. - -## Submitting Changes - -* All content, comments, pull requests and other contributions must comply with the - [Stellar Code of Conduct][coc]. -* Push your changes to a topic branch in your fork of the repository. -* Submit a pull request to the repository in the Stellar - organization. - * Include a descriptive [commit message][commit-msg]. - * Changes contributed via pull request should focus on a single issue at a time. - * Rebase your local changes against the `main` branch. Resolve any conflicts that arise. - - -At this point you're waiting on us. We like to at least comment on pull requests within three -business days (typically, one business day). We may suggest some changes, improvements or -alternatives. +## Getting Started -# Additional Resources +* Make sure you have a [GitHub account](https://github.com/signup/free) +* Create discussions at https://github.com/orgs/stellar/discussions with problems and new ideas, + or participate in existing discussions +* Create proposals at https://github.com/stellar/stellar-protocol after sharing ideas in a + discussion first +* Create GitHub issues for bugs and feature requests that target specific projects + +## Reporting Bugs and Requesting Features + +First search for an existing issue and join a relevant discussion if an existing issue is present. + +After confirming an issue does not already exist, create a GitHub issue with: + * The concrete problem that needs solving. + * For bugs, include a minimal reproducer with the expected and actual behavior. + * Relevant alternatives, if any, and their tradeoffs. + * Verify everything reported before submitting. Do not submit speculative findings or generated + lists of possible issues. + +## Pull Requests + +Projects hosted here only accept pull requests for issues with the `help wanted` label. Unsolicited +pull requests will be closed without an explanation and reported as spam. Making changes requires +deep architectural knowledge, a good understanding of system constraints, and an idea about the +project roadmap. Many Stellar projects facilitate financial transactions or are dependencies to many +other projects. Correctness is critical and thoughtful evolution of behaviour and APIs is paramount. +However, maintainer and reviewer time is limited. External contributors often do not have the context +required and reviewing takes the maintainers' focus away from high-priority work that's been +discussed in the discussion forums and issues. + +Key things to keep in mind when creating a pull request: +* Confirm, does the pull request narrowly address an open issue and have you been assigned? +* Fork the project's repository and submit the pull request from a branch in your fork. +* Link the approved issue and keep the pull request narrowly within the scope of that issue. + +## Additional Resources * [Explore our APIs](https://developers.stellar.org/docs) * [Stellar Developer Discord](https://discord.com/invite/stellardev) From 5e74c29a97fc80145fc8395624cfa056937b5959 Mon Sep 17 00:00:00 2001 From: Leigh <351529+leighmcculloch@users.noreply.github.com> Date: Wed, 9 Sep 2026 07:53:49 +1000 Subject: [PATCH 02/15] Update CONTRIBUTING.md --- CONTRIBUTING.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index e2c248a..4cb356c 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -18,6 +18,8 @@ are in discussions, sharing new ideas, reporting bugs, and sharing experience re ## Getting Started * Make sure you have a [GitHub account](https://github.com/signup/free) +* Read the [Stellar Code of Conduct][coc], as all content, comments, pull requests and other + contributions must comply with it * Create discussions at https://github.com/orgs/stellar/discussions with problems and new ideas, or participate in existing discussions * Create proposals at https://github.com/stellar/stellar-protocol after sharing ideas in a From 5e2e253543426c1a0a2330352fd4804996d0dab6 Mon Sep 17 00:00:00 2001 From: Leigh <351529+leighmcculloch@users.noreply.github.com> Date: Wed, 9 Sep 2026 10:07:51 +1000 Subject: [PATCH 03/15] Update CONTRIBUTING.md --- CONTRIBUTING.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 4cb356c..19dee0b 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -53,6 +53,21 @@ Key things to keep in mind when creating a pull request: * Fork the project's repository and submit the pull request from a branch in your fork. * Link the approved issue and keep the pull request narrowly within the scope of that issue. +## AI-Assisted Contributions + +The use of AI tools to improve productivity and the quality of contributions is encouraged. AI assistance does not, however, change the responsibilities or standards that apply to the human contributor. + +Before exposing other community members to AI-assisted content, the human submitter is responsible for: + +- Reviewing and verifying all generated content, including code, tests, code comments, documentation, issues, pull-request descriptions, review feedback, chat messages, forum posts, and other project or community communications. Appropriate tests and checks must be performed where applicable. +- Ensuring the contribution is correct, relevant, and appropriate for the project, including its security, reliability, maintainability, and adherence to project standards. +- Ensuring they have the right to submit the contribution, including compliance with applicable copyright, licensing, attribution, and other third-party requirements. +- Fully understanding the contribution. The submitter must be able to explain it in their own words, including its context, assumptions, design choices, tradeoffs, and implications, and be able to answer questions and validate changes arising during review. +- Taking full responsibility for the contribution. AI assistance does not transfer responsibility for errors, omissions, security issues, licensing problems, or other consequences to the AI tool or its provider. +- Respecting the time and attention of other community members. AI must not be used to generate high volumes of low-quality or speculative contributions, or to shift the burden of understanding, verification, debugging, or cleanup onto reviewers and maintainers. + +AI tools must not autonomously publish contributions or communications including code changes, issues, reviews, chat messages, or forum posts to community channels without human review. AI-assisted contributions are held to the same standards as contributions produced without AI assistance. + ## Additional Resources * [Explore our APIs](https://developers.stellar.org/docs) From 3e1206db538c8d17bce97d05efb6a65e81c5f809 Mon Sep 17 00:00:00 2001 From: Leigh <351529+leighmcculloch@users.noreply.github.com> Date: Wed, 9 Sep 2026 10:09:30 +1000 Subject: [PATCH 04/15] Apply batched suggestions from code review Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> --- CONTRIBUTING.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 19dee0b..50d0b1e 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -8,12 +8,12 @@ and thrive. There are a few guidelines that we ask contributors to follow so tha effectively together. > [!TIP] -> The Stellar network is open, decentralised, and programmable. For many ideas you may have, they can +> The Stellar network is open, decentralized, and programmable. For many ideas you may have, they can > be built without changes to the projects hosted here. Want to contribute to Stellar? Build on Stellar! > And share your feedback in the forums listed below. -To contribute to the work of maintaining the projects hosted here the biggest impact contributions -are in discussions, sharing new ideas, reporting bugs, and sharing experience reports. +To contribute to the work of maintaining the projects hosted here, the biggest-impact contributions +are participating in discussions, sharing new ideas, reporting bugs, and sharing experience reports. ## Getting Started From 6b12cf4eabf672546d06f8552bcfc494a614736d Mon Sep 17 00:00:00 2001 From: Leigh <351529+leighmcculloch@users.noreply.github.com> Date: Tue, 22 Sep 2026 06:28:26 +1000 Subject: [PATCH 05/15] fmt --- CONTRIBUTING.md | 136 ++++++++++++++++++++++++++++++------------------ 1 file changed, 84 insertions(+), 52 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 50d0b1e..686d15a 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -1,83 +1,115 @@ # How to contribute to a Stellar project -Your contributions to the [Stellar network](https://www.stellar.org/) will help improve the world’s -financial infrastructure. +Your contributions to the [Stellar network](https://www.stellar.org/) will help +improve the world’s financial infrastructure. -We want to make it as easy as possible to contribute to Stellar in ways that make the network grow -and thrive. There are a few guidelines that we ask contributors to follow so that we all work -effectively together. +We want to make it as easy as possible to contribute to Stellar in ways that +make the network grow and thrive. There are a few guidelines that we ask +contributors to follow so that we all work effectively together. > [!TIP] -> The Stellar network is open, decentralized, and programmable. For many ideas you may have, they can -> be built without changes to the projects hosted here. Want to contribute to Stellar? Build on Stellar! -> And share your feedback in the forums listed below. +> The Stellar network is open, decentralized, and programmable. For many ideas +> you may have, they can be built without changes to the projects hosted here. +> Want to contribute to Stellar? Build on Stellar! And share your feedback in +> the forums listed below. -To contribute to the work of maintaining the projects hosted here, the biggest-impact contributions -are participating in discussions, sharing new ideas, reporting bugs, and sharing experience reports. +To contribute to the work of maintaining the projects hosted here, the +biggest-impact contributions are participating in discussions, sharing new +ideas, reporting bugs, and sharing experience reports. ## Getting Started -* Make sure you have a [GitHub account](https://github.com/signup/free) -* Read the [Stellar Code of Conduct][coc], as all content, comments, pull requests and other - contributions must comply with it -* Create discussions at https://github.com/orgs/stellar/discussions with problems and new ideas, - or participate in existing discussions -* Create proposals at https://github.com/stellar/stellar-protocol after sharing ideas in a - discussion first -* Create GitHub issues for bugs and feature requests that target specific projects +- Make sure you have a [GitHub account](https://github.com/signup/free) +- Read the [Stellar Code of Conduct][coc], as all content, comments, pull + requests and other contributions must comply with it +- Create discussions at https://github.com/orgs/stellar/discussions with + problems and new ideas, or participate in existing discussions +- Create proposals at https://github.com/stellar/stellar-protocol after sharing + ideas in a discussion first +- Create GitHub issues for bugs and feature requests that target specific + projects ## Reporting Bugs and Requesting Features -First search for an existing issue and join a relevant discussion if an existing issue is present. +First search for an existing issue and join a relevant discussion if an existing +issue is present. After confirming an issue does not already exist, create a GitHub issue with: - * The concrete problem that needs solving. - * For bugs, include a minimal reproducer with the expected and actual behavior. - * Relevant alternatives, if any, and their tradeoffs. - * Verify everything reported before submitting. Do not submit speculative findings or generated - lists of possible issues. + +- The concrete problem that needs solving. +- For bugs, include a minimal reproducer with the expected and actual behavior. +- Relevant alternatives, if any, and their tradeoffs. +- Verify everything reported before submitting. Do not submit speculative + findings or generated lists of possible issues. ## Pull Requests -Projects hosted here only accept pull requests for issues with the `help wanted` label. Unsolicited -pull requests will be closed without an explanation and reported as spam. Making changes requires -deep architectural knowledge, a good understanding of system constraints, and an idea about the -project roadmap. Many Stellar projects facilitate financial transactions or are dependencies to many -other projects. Correctness is critical and thoughtful evolution of behaviour and APIs is paramount. -However, maintainer and reviewer time is limited. External contributors often do not have the context -required and reviewing takes the maintainers' focus away from high-priority work that's been -discussed in the discussion forums and issues. +Projects hosted here only accept pull requests for issues with the `help wanted` +label. Unsolicited pull requests will be closed without an explanation and +reported as spam. Making changes requires deep architectural knowledge, a good +understanding of system constraints, and an idea about the project roadmap. Many +Stellar projects facilitate financial transactions or are dependencies to many +other projects. Correctness is critical and thoughtful evolution of behaviour +and APIs is paramount. However, maintainer and reviewer time is limited. +External contributors often do not have the context required and reviewing takes +the maintainers' focus away from high-priority work that's been discussed in the +discussion forums and issues. Key things to keep in mind when creating a pull request: -* Confirm, does the pull request narrowly address an open issue and have you been assigned? -* Fork the project's repository and submit the pull request from a branch in your fork. -* Link the approved issue and keep the pull request narrowly within the scope of that issue. - -## AI-Assisted Contributions -The use of AI tools to improve productivity and the quality of contributions is encouraged. AI assistance does not, however, change the responsibilities or standards that apply to the human contributor. +- Confirm, does the pull request narrowly address an open issue and have you + been assigned? +- Fork the project's repository and submit the pull request from a branch in + your fork. +- Link the approved issue and keep the pull request narrowly within the scope of + that issue. -Before exposing other community members to AI-assisted content, the human submitter is responsible for: - -- Reviewing and verifying all generated content, including code, tests, code comments, documentation, issues, pull-request descriptions, review feedback, chat messages, forum posts, and other project or community communications. Appropriate tests and checks must be performed where applicable. -- Ensuring the contribution is correct, relevant, and appropriate for the project, including its security, reliability, maintainability, and adherence to project standards. -- Ensuring they have the right to submit the contribution, including compliance with applicable copyright, licensing, attribution, and other third-party requirements. -- Fully understanding the contribution. The submitter must be able to explain it in their own words, including its context, assumptions, design choices, tradeoffs, and implications, and be able to answer questions and validate changes arising during review. -- Taking full responsibility for the contribution. AI assistance does not transfer responsibility for errors, omissions, security issues, licensing problems, or other consequences to the AI tool or its provider. -- Respecting the time and attention of other community members. AI must not be used to generate high volumes of low-quality or speculative contributions, or to shift the burden of understanding, verification, debugging, or cleanup onto reviewers and maintainers. +## AI-Assisted Contributions -AI tools must not autonomously publish contributions or communications including code changes, issues, reviews, chat messages, or forum posts to community channels without human review. AI-assisted contributions are held to the same standards as contributions produced without AI assistance. +The use of AI tools to improve productivity and the quality of contributions is +encouraged. AI assistance does not, however, change the responsibilities or +standards that apply to the human contributor. + +Before exposing other community members to AI-assisted content, the human +submitter is responsible for: + +- Reviewing and verifying all generated content, including code, tests, code + comments, documentation, issues, pull-request descriptions, review feedback, + chat messages, forum posts, and other project or community communications. + Appropriate tests and checks must be performed where applicable. +- Ensuring the contribution is correct, relevant, and appropriate for the + project, including its security, reliability, maintainability, and adherence + to project standards. +- Ensuring they have the right to submit the contribution, including compliance + with applicable copyright, licensing, attribution, and other third-party + requirements. +- Fully understanding the contribution. The submitter must be able to explain it + in their own words, including its context, assumptions, design choices, + tradeoffs, and implications, and be able to answer questions and validate + changes arising during review. +- Taking full responsibility for the contribution. AI assistance does not + transfer responsibility for errors, omissions, security issues, licensing + problems, or other consequences to the AI tool or its provider. +- Respecting the time and attention of other community members. AI must not be + used to generate high volumes of low-quality or speculative contributions, or + to shift the burden of understanding, verification, debugging, or cleanup onto + reviewers and maintainers. + +AI tools must not autonomously publish contributions or communications including +code changes, issues, reviews, chat messages, or forum posts to community +channels without human review. AI-assisted contributions are held to the same +standards as contributions produced without AI assistance. ## Additional Resources -* [Explore our APIs](https://developers.stellar.org/docs) -* [Stellar Developer Discord](https://discord.com/invite/stellardev) +- [Explore our APIs](https://developers.stellar.org/docs) +- [Stellar Developer Discord](https://discord.com/invite/stellardev) This document is inspired by: -* https://github.com/puppetlabs/puppet/blob/master/CONTRIBUTING.md -* https://github.com/thoughtbot/factory_girl_rails/blob/master/CONTRIBUTING.md -* https://github.com/rust-lang/rust/blob/master/CONTRIBUTING.md +- https://github.com/puppetlabs/puppet/blob/master/CONTRIBUTING.md +- https://github.com/thoughtbot/factory_girl_rails/blob/master/CONTRIBUTING.md +- https://github.com/rust-lang/rust/blob/master/CONTRIBUTING.md [help-wanted]: https://github.com/issues?q=is%3Aopen+is%3Aissue+user%3Astellar+label%3A%22help+wanted%22 [commit-msg]: https://github.com/erlang/otp/wiki/Writing-good-commit-messages From c43db52ea0917641c49cee7a6c3b2f794ca6487a Mon Sep 17 00:00:00 2001 From: Leigh <351529+leighmcculloch@users.noreply.github.com> Date: Tue, 22 Sep 2026 06:30:33 +1000 Subject: [PATCH 06/15] ref to proj contributing guidelines --- CONTRIBUTING.md | 17 +++++++++-------- 1 file changed, 9 insertions(+), 8 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 686d15a..3991688 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -45,14 +45,15 @@ After confirming an issue does not already exist, create a GitHub issue with: ## Pull Requests Projects hosted here only accept pull requests for issues with the `help wanted` -label. Unsolicited pull requests will be closed without an explanation and -reported as spam. Making changes requires deep architectural knowledge, a good -understanding of system constraints, and an idea about the project roadmap. Many -Stellar projects facilitate financial transactions or are dependencies to many -other projects. Correctness is critical and thoughtful evolution of behaviour -and APIs is paramount. However, maintainer and reviewer time is limited. -External contributors often do not have the context required and reviewing takes -the maintainers' focus away from high-priority work that's been discussed in the +label or if they indicate otherwise in their own contributing guidelines. +Unsolicited pull requests will be closed without an explanation and reported as +spam. Making changes requires deep architectural knowledge, a good understanding +of system constraints, and an idea about the project roadmap. Many Stellar +projects facilitate financial transactions or are dependencies to many other +projects. Correctness is critical and thoughtful evolution of behaviour and APIs +is paramount. However, maintainer and reviewer time is limited. External +contributors often do not have the context required and reviewing takes the +maintainers' focus away from high-priority work that's been discussed in the discussion forums and issues. Key things to keep in mind when creating a pull request: From f2154a7d1de76d3e19861ed8b54f51afab018c8f Mon Sep 17 00:00:00 2001 From: Leigh <351529+leighmcculloch@users.noreply.github.com> Date: Tue, 22 Sep 2026 06:31:21 +1000 Subject: [PATCH 07/15] remove fork statement since it is implied on github --- CONTRIBUTING.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 3991688..a043682 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -60,8 +60,6 @@ Key things to keep in mind when creating a pull request: - Confirm, does the pull request narrowly address an open issue and have you been assigned? -- Fork the project's repository and submit the pull request from a branch in - your fork. - Link the approved issue and keep the pull request narrowly within the scope of that issue. From 34f85b205a7bf36fd17346d88fc2c22324c20074 Mon Sep 17 00:00:00 2001 From: Leigh <351529+leighmcculloch@users.noreply.github.com> Date: Tue, 22 Sep 2026 06:40:01 +1000 Subject: [PATCH 08/15] more tweaks --- CONTRIBUTING.md | 22 ++++++++++++---------- 1 file changed, 12 insertions(+), 10 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index a043682..96951d5 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -47,19 +47,21 @@ After confirming an issue does not already exist, create a GitHub issue with: Projects hosted here only accept pull requests for issues with the `help wanted` label or if they indicate otherwise in their own contributing guidelines. Unsolicited pull requests will be closed without an explanation and reported as -spam. Making changes requires deep architectural knowledge, a good understanding -of system constraints, and an idea about the project roadmap. Many Stellar -projects facilitate financial transactions or are dependencies to many other -projects. Correctness is critical and thoughtful evolution of behaviour and APIs -is paramount. However, maintainer and reviewer time is limited. External -contributors often do not have the context required and reviewing takes the -maintainers' focus away from high-priority work that's been discussed in the -discussion forums and issues. +spam. + +Making changes requires deep architectural knowledge, a good understanding of +system constraints, and an idea about the project roadmap. Many Stellar projects +facilitate financial transactions or are dependencies to many other projects. +Correctness is critical and thoughtful evolution of behaviour and APIs is +paramount. Maintainer and reviewer time is limited. External contributors often +do not have the context required and reviewing takes the maintainers' focus away +from high-priority work that has already been discussed in discussion forums and +that the ecosystem is waiting on. Key things to keep in mind when creating a pull request: -- Confirm, does the pull request narrowly address an open issue and have you - been assigned? +- Does the pull request narrowly address an open issue and have you been + assigned? - Link the approved issue and keep the pull request narrowly within the scope of that issue. From e20b9ae36012a95d720384122b817b566ab38215 Mon Sep 17 00:00:00 2001 From: Leigh <351529+leighmcculloch@users.noreply.github.com> Date: Tue, 22 Sep 2026 06:42:17 +1000 Subject: [PATCH 09/15] more tweaks --- CONTRIBUTING.md | 5 ----- 1 file changed, 5 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 96951d5..dec8c15 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -96,11 +96,6 @@ submitter is responsible for: to shift the burden of understanding, verification, debugging, or cleanup onto reviewers and maintainers. -AI tools must not autonomously publish contributions or communications including -code changes, issues, reviews, chat messages, or forum posts to community -channels without human review. AI-assisted contributions are held to the same -standards as contributions produced without AI assistance. - ## Additional Resources - [Explore our APIs](https://developers.stellar.org/docs) From 7d3b843b20f3e5e0552662b1c790cd4fb47c2400 Mon Sep 17 00:00:00 2001 From: Leigh <351529+leighmcculloch@users.noreply.github.com> Date: Tue, 22 Sep 2026 06:44:13 +1000 Subject: [PATCH 10/15] more tweaks --- CONTRIBUTING.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index dec8c15..1489015 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -60,10 +60,9 @@ that the ecosystem is waiting on. Key things to keep in mind when creating a pull request: -- Does the pull request narrowly address an open issue and have you been - assigned? -- Link the approved issue and keep the pull request narrowly within the scope of - that issue. +- Does the change narrowly address an open issue and have you been assigned? +- Does the change comply with the [Stellar Code of Conduct][coc]. +- Link the approved issue. ## AI-Assisted Contributions From 6fe7fa6d5f16f21482aafcd8fc8b8fd5fa928c60 Mon Sep 17 00:00:00 2001 From: Leigh <351529+leighmcculloch@users.noreply.github.com> Date: Tue, 22 Sep 2026 06:44:36 +1000 Subject: [PATCH 11/15] more tweaks --- CONTRIBUTING.md | 6 ------ 1 file changed, 6 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 1489015..ba8aa1e 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -100,12 +100,6 @@ submitter is responsible for: - [Explore our APIs](https://developers.stellar.org/docs) - [Stellar Developer Discord](https://discord.com/invite/stellardev) -This document is inspired by: - -- https://github.com/puppetlabs/puppet/blob/master/CONTRIBUTING.md -- https://github.com/thoughtbot/factory_girl_rails/blob/master/CONTRIBUTING.md -- https://github.com/rust-lang/rust/blob/master/CONTRIBUTING.md - [help-wanted]: https://github.com/issues?q=is%3Aopen+is%3Aissue+user%3Astellar+label%3A%22help+wanted%22 [commit-msg]: https://github.com/erlang/otp/wiki/Writing-good-commit-messages [coc]: https://github.com/stellar/.github/blob/master/CODE_OF_CONDUCT.md From d81854871e80f9a859790d234609457f39b5e424 Mon Sep 17 00:00:00 2001 From: Leigh <351529+leighmcculloch@users.noreply.github.com> Date: Tue, 22 Sep 2026 06:57:06 +1000 Subject: [PATCH 12/15] improve ease of reading Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> --- CONTRIBUTING.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index ba8aa1e..778dd61 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -8,8 +8,8 @@ make the network grow and thrive. There are a few guidelines that we ask contributors to follow so that we all work effectively together. > [!TIP] -> The Stellar network is open, decentralized, and programmable. For many ideas -> you may have, they can be built without changes to the projects hosted here. +> The Stellar network is open, decentralized, and programmable. Many ideas you +> may have can be built without changes to the projects hosted here. > Want to contribute to Stellar? Build on Stellar! And share your feedback in > the forums listed below. From 1c1b54b3135f0bb05c874db222033926dd594f7c Mon Sep 17 00:00:00 2001 From: Leigh <351529+leighmcculloch@users.noreply.github.com> Date: Tue, 22 Sep 2026 06:57:24 +1000 Subject: [PATCH 13/15] fmt --- CONTRIBUTING.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 778dd61..b6e43e1 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -9,9 +9,9 @@ contributors to follow so that we all work effectively together. > [!TIP] > The Stellar network is open, decentralized, and programmable. Many ideas you -> may have can be built without changes to the projects hosted here. -> Want to contribute to Stellar? Build on Stellar! And share your feedback in -> the forums listed below. +> may have can be built without changes to the projects hosted here. Want to +> contribute to Stellar? Build on Stellar! And share your feedback in the forums +> listed below. To contribute to the work of maintaining the projects hosted here, the biggest-impact contributions are participating in discussions, sharing new From ebd0a0b6523121ec8fa214ef43d65221da12ebe9 Mon Sep 17 00:00:00 2001 From: MonsieurNicolas Date: Mon, 21 Sep 2026 14:31:37 -0700 Subject: [PATCH 14/15] Update AI contribution guidelines in CONTRIBUTING.md Clarify responsibilities of contributors using AI tools in the project. --- CONTRIBUTING.md | 26 +++++++++++++++++++------- 1 file changed, 19 insertions(+), 7 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index b6e43e1..e62d7e0 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -70,31 +70,43 @@ The use of AI tools to improve productivity and the quality of contributions is encouraged. AI assistance does not, however, change the responsibilities or standards that apply to the human contributor. +Maintainers are not obligated to review contributions that do not appear to meet +these standards and may close or reject them without performing the verification +that is the submitter's responsibility. + Before exposing other community members to AI-assisted content, the human submitter is responsible for: -- Reviewing and verifying all generated content, including code, tests, code +- **Reviewing and verifying all generated content**, including code, tests, code comments, documentation, issues, pull-request descriptions, review feedback, chat messages, forum posts, and other project or community communications. Appropriate tests and checks must be performed where applicable. -- Ensuring the contribution is correct, relevant, and appropriate for the - project, including its security, reliability, maintainability, and adherence +- **Ensuring the contribution is correct, relevant, and appropriate for the + project**, including its security, reliability, maintainability, and adherence to project standards. -- Ensuring they have the right to submit the contribution, including compliance +- **Ensuring they have the right to submit the contribution**, including compliance with applicable copyright, licensing, attribution, and other third-party requirements. -- Fully understanding the contribution. The submitter must be able to explain it +- **Fully understanding the contribution**. The submitter must be able to explain it in their own words, including its context, assumptions, design choices, tradeoffs, and implications, and be able to answer questions and validate changes arising during review. -- Taking full responsibility for the contribution. AI assistance does not +- **Participating directly in review and community interactions**. AI may assist with + communication, but must not substitute for the submitter's own understanding, + judgment, or engagement. Contributors must not act merely as an intermediary + relaying content between other community members and an AI system. +- **Taking full responsibility for the contribution**. AI assistance does not transfer responsibility for errors, omissions, security issues, licensing problems, or other consequences to the AI tool or its provider. -- Respecting the time and attention of other community members. AI must not be +- **Respecting the time and attention of other community members**. AI must not be used to generate high volumes of low-quality or speculative contributions, or to shift the burden of understanding, verification, debugging, or cleanup onto reviewers and maintainers. +A corollary is that **AI tools must not autonomously publish contributions or communications +to community channels without human review**; this includes code changes, issues, reviews, +chat messages, and forum posts. + ## Additional Resources - [Explore our APIs](https://developers.stellar.org/docs) From 668dea76d73029039deec58725c5dceeeca5fa7b Mon Sep 17 00:00:00 2001 From: MonsieurNicolas Date: Mon, 21 Sep 2026 16:20:49 -0700 Subject: [PATCH 15/15] Update CONTRIBUTING.md Co-authored-by: Leigh <351529+leighmcculloch@users.noreply.github.com> --- CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index e62d7e0..3bba2a5 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -103,7 +103,7 @@ submitter is responsible for: to shift the burden of understanding, verification, debugging, or cleanup onto reviewers and maintainers. -A corollary is that **AI tools must not autonomously publish contributions or communications +**AI tools must not autonomously publish contributions or communications to community channels without human review**; this includes code changes, issues, reviews, chat messages, and forum posts.