.. index:: code of conduct, contribution guidelines, pull requests, issue tracker

Code of Conduct
===============

This project welcomes focused contributions that improve the accuracy,
clarity, examples, accessibility, and maintainability of the book.

Professional Conduct
--------------------

Participation in this project should follow professional and community
standards reflected in:

- the `ACM Code of Ethics and Professional Conduct <https://www.acm.org/code-of-ethics>`_;
- the `IEEE Code of Conduct <https://events.ieee.org/wp-content/uploads/ieee_code_of_conduct.pdf>`_;
- the `IEEE Code of Ethics <https://www.ieee.org/about/corporate/governance/p7-8.html>`_.

Issues, pull requests, reviews, and discussions should be respectful,
specific, and relevant to the work. Abusive, discriminatory, harassing,
hostile, or unprofessional communication will not be accepted.

Contributing
------------

For most contributors, the best starting point is an issue. Please
describe the problem or suggestion clearly, point to the relevant chapter
or section when possible, and keep the issue focused on one topic.

Pull requests should be small and focused. They should use the existing
Sphinx/reStructuredText style of the book, avoid committing generated
build output, include attribution when adapting material from elsewhere,
and preserve the book's concise teaching style.

Contributor Identity
--------------------

Contributor names and public credits should be handled with care. Use the
name a contributor asks to use in the public book. Do not add additional
identity information unless the contributor has approved it for this
project.

Use of AI Assistance
--------------------

Contributors may use AI systems as part of writing, editing, coding, or
review, but AI-assisted contributions should be checked by a human
contributor before submission. The human contributor is responsible for
accuracy, attribution, licensing compatibility, and suitability for this
book.

Editorial Review
----------------

All contributions are subject to editorial review. Submission of an issue,
suggestion, or pull request does not guarantee acceptance. Accepted
contributions may be edited or reorganized so they fit the book's voice,
structure, and goals.
