Skip to content

Commit fbcbcbe

Browse files
Update contributors guide (#789)
* initial version * update index with link to contributor guide * Add contribution guide link to README * Update new contributors suggestion * remove reporting * previous commit * Add newcomer note * fix ref link * wasted->unproductive * Typo * Update developer.contributing.rst * Apply suggestion from @edwardchalstrey1 Co-authored-by: Ed Chalstrey <edwardchalstrey@gmail.com> * Apply suggestions from code review Co-authored-by: Ed Chalstrey <edwardchalstrey@gmail.com> --------- Co-authored-by: Ted Turocy <ted.turocy@gmail.com>
1 parent d4732be commit fbcbcbe

3 files changed

Lines changed: 59 additions & 5 deletions

File tree

README.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,8 +10,9 @@
1010

1111
**Gambit** is the package for doing computation in (non-cooperative) game theory.
1212

13-
- See our [documentation](https://gambitproject.readthedocs.io/)
14-
- Check our [project website](https://www.gambit-project.org/)
13+
- **Documentation:** for the package is hosted at [gambitproject.readthedocs.io](https://gambitproject.readthedocs.io/).
14+
- **The Gambit project:** Find out more about the project at [gambit-project.org](https://www.gambit-project.org/)
15+
- **Contributors:** Please read the [code of conduct and contribution guidelines](https://gambitproject.readthedocs.io/en/latest/developer.contributing.html) before posting on GitHub.
1516

1617
Gambit provides:
1718

doc/developer.contributing.rst

Lines changed: 52 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,11 +6,25 @@ Contributing to Gambit
66
This section provides guidelines for contributing to Gambit, including how to report bugs, suggest features, and contribute code.
77
It includes information relevant to both core developers and external contributors.
88

9+
.. _code-of-conduct:
10+
11+
Code of Conduct
12+
---------------
13+
14+
All participants in the Gambit community are expected to show respect and courtesy to others.
15+
We are committed to fostering a welcoming and harassment-free environment for everyone, regardless of background or identity.
16+
Please be kind and considerate in your interactions. We are all here to build a better tool for game theory research and education.
17+
Disagreements may happen, but they should be handled with respect and a focus on constructive resolution.
18+
19+
To raise any concerns, please contact `Ted Turocy <mailto:ted.turocy@gmail.com>` or `Rahul Savani <mailto:rahul.savani@gmail.com>`.
20+
921
.. _github-issues:
1022

1123
GitHub issues
1224
-------------
1325

26+
Newcomer to the project? Please read the :ref:`code of conduct <code-of-conduct>` and :ref:`new contributors section <new-contributors>` sections before posting on GitHub.
27+
1428
In the first instance, bug reports, feature requests and improvements to the Gambit documentation should be
1529
posted to the Gambit issue tracker, located at
1630
`<http://github.com/gambitproject/gambit/issues>`_.
@@ -39,6 +53,44 @@ latest development version. New development should in general always
3953
be based off this branch. Branches labeled ``maintX_Y``, where ``X`` is the major version number and ``Y`` is the minor version number, point to the latest commit on a stable
4054
version.
4155

56+
.. _new-contributors:
57+
58+
A Note for New Contributors
59+
^^^^^^^^^^^^^^^^^^^^^^^^^^^
60+
61+
We warmly welcome new contributors to the Gambit project! Your help is valuable to us.
62+
63+
Before you start working on a contribution, we encourage you to familiarize yourself with the project.
64+
Gambit is a mature and complex codebase. Even issues marked as "good first issue" may require some understanding of the context and how different parts of the project interact.
65+
66+
We have always valued thoughtful contributions. A common issue for open-source projects is receiving pull requests that are not well-aligned with the project's needs or coding standards. To avoid unproductive effort on your part and on ours, we strongly encourage you to engage with us before you spend a lot of time on implementation.
67+
68+
A great way to start is by:
69+
70+
1. Looking through the code to understand the relevant parts for your intended change.
71+
2. Contacting the maintainers via commenting with a question on an open issue, or opening a Discussion on GitHub.
72+
3. After your discussion with the maintainers, open a draft pull request early in your process. This allows for discussion and feedback before you've invested too much time.
73+
74+
We are happy to answer questions and provide guidance. Engaging with the maintainers early ensures that your contribution is likely to be accepted and integrated smoothly.
75+
76+
.. _ai-policy:
77+
78+
Policy on AI-Assisted Contributions
79+
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
80+
81+
We recognize that generative AI tools can be a useful aid in software development. We also expect authentic and thoughtful engagement from our contributors.
82+
83+
- **You are responsible for your contributions.** If you use generative AI to help you write code or documentation, you must fully understand the output. You should be able to explain the changes and why they are the correct approach for the project.
84+
- **Add value.** Simply taking a prompt, feeding it to an AI, and posting the result as a contribution is not helpful. We expect you to use your own expertise to verify, test, and refine any AI-generated content. Out of respect for everyone's time, we reserve the right to rigorously reject low-value contributions, whether AI-generated or not.
85+
- **No AI-generated comments.** Please do not post output from Large Language Models (LLMs) or similar tools as comments on GitHub issues or pull requests. Such comments are often generic and do not add to the discussion.
86+
- **Humans over bots.** We discourage the use of automated tools, such as bots or agents, to post AI-generated content to issues or pull requests, without the advance approval of the core development team.
87+
88+
89+
How to submit a contribution
90+
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
91+
92+
To contribute code, please follow these steps:
93+
4294
1. To get started contributing code in the `Gambit GitHub repo <https://github.com/gambitproject/gambit>`__, do one of the following:
4395

4496
- Core developers: request contributor access from one of the `team <https://www.gambit-project.org/team/>`__

doc/index.rst

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,11 @@
1-
##########################
21
Gambit: User documentation
3-
##########################
2+
^^^^^^^^^^^^^^^^^^^^^^^^^^
43

54
**Gambit** is a library of game theory software and tools for the
65
construction and analysis of finite extensive and strategic games.
7-
We recommended most new users install the PyGambit Python package and read the associated documentation, which includes tutorials and a complete API reference.
6+
7+
- **Users:** We recommend most newcomers install the PyGambit Python package and read the associated documentation, which includes tutorials and a complete API reference.
8+
- **Contributors:** Please read the :ref:`code of conduct and contribution guidelines <contributing>` before posting on GitHub.
89

910
.. grid::
1011

0 commit comments

Comments
 (0)