Code of Conduct - Amsterdam Web Communities System Project

For purposes of this document, the sole maintainer of the Amsterdam project is Amy G. Bowersox, amy@erbosoft.com.

Any violations of this Code of Conduct may be reported to the maintainers, as listed above.

Purpose

Amsterdam is a collaborative software project. Its primary purpose is to build, maintain, and improve a system for hosting human-scale online communities.

This Code of Conduct exists to support productive collaboration, respectful technical discussion, and a healthy working environment for everyone involved.

This Code of Conduct shall apply to all project spaces including repositories, issue trackers, discussion forums, and official communications channels.

As a general principle, anyone who adheres to this Code of Conduct and provides quality contributions to the project is welcome to participate. ("Contributions" may include but are not limited to code, documentation, testing, or fundraising.)

Expected Behavior

Participants in the Amsterdam project are expected to:

Treat others with respect and professionalism.
Assume good faith in technical and design discussions.
Critique ideas, code, and proposals—not people.
Keep discussions relevant to the project and its goals.
Accept that disagreement is normal and can be constructive when handled respectfully.
Follow the guidance and decisions of the project maintainers.

Contributions

Contributions must be the own work of the contributor. Plagiarism in any form is unacceptable.

All project contributions must be submitted by identifiable human participants who accept full responsibility for their content. Automated agents, bots, or autonomous AI systems may not independently submit issues, pull requests, or other contributions.

Contributors may use software tools, including AI-assisted tools, but the submitting contributor must:

Fully understand the contribution.
Be able to explain design and implementation decisions without the use of AI.
Accept responsibility for maintenance and correctness.

Contributors should indicate AI-generated content in issue and pull request descriptions and comments, specifying which model was used.

Do not use AI to reply to questions about your issue or pull request. The questions are for you, the human, not an AI model.

Project maintainers retain full discretion to accept or reject contributions for any reason consistent with the project's goals, quality standards, and maintainability requirements. Submission of a contribution shall not guarantee review, acceptance, or ongoing support.

Public pressure campaigns, harassment, or attempts to coerce project decisions through social media or other external channels shall be considered violations of this Code of Conduct.

All contributions shall be made available under the Mozilla Public License, Version 2.0. Contributors shall ensure that they have the authority to make their contribution under the terms of this license.

Unacceptable Behavior

The following behaviors shall not be acceptable in project spaces (including code repositories, issue trackers, discussions, and related communication channels):

Harassment, intimidation, or threats of any kind.
Personal attacks, insults, or repeated hostile behavior.
Persistent disruption of discussions or development work.
Bad-faith participation, including deliberate misrepresentation or refusal to engage constructively.
Using the project as a platform for unrelated political, ideological, or personal agendas.
Any behavior that makes collaboration significantly more difficult or less safe for others.

Enforcement

Project maintainers shall be responsible for interpreting and enforcing this Code of Conduct.

If unacceptable behavior occurs, maintainers may take actions including, but not limited to:

Issuing a warning.
Removing content or contributions.
Temporarily or permanently restricting participation.

Maintainer decisions shall be final. Enforcement actions shall not be subject to public debate.

Project Values

Amsterdam prioritizes the quality of contributions and the health of collaboration over ideology, factionalism, or performative conflict.

Participation in the project implies agreement with these principles.

Amsterdam values tools that assist developers, but tools are no substitute for human judgment, accountability, and stewardship. As a human-collaborative software project, all participation must remain human-directed and accountable.

4.5 KiB Raw Blame History