Code of Conduct

This Code of Conduct describes the expectations for behaviour and collaboration within the Tripinger project.

Document Purpose

This Code of Conduct describes the expectations for behaviour and collaboration within the Tripinger project. It applies to everyone interacting with the project: maintainers, contributors, partners, and community members, whether in GitHub issues, pull requests, documentation, design discussions, or internal communication channels.

Tripinger is building a travel platform that serves diverse travelers and local partners across Sri Lanka. The team and contributor community must reflect that diversity with respectful, inclusive, and professional behaviour to keep the project healthy and sustainable.

Our Values

Tripinger’s work is guided by the following principles:

Respect: Treat every person with dignity, regardless of background, role, or opinion.
Inclusivity: Create space for contributors with different experience levels, languages, and perspectives.
Safety and trust: Prioritize user safety, partner trust, and data protection in both product decisions and team behaviour.
Constructive collaboration: Focus feedback on ideas and code, not individuals.
Ownership and accountability: Take responsibility for your contributions and their impact on travelers, partners, and operations.

These values are as important as technical quality and should inform every interaction.

Expected Behaviour

All project participants are expected to:

Be respectful and professional
Use clear, non-insulting language in issues, PRs, comments, and chats.
Assume good intent while still being honest about problems and risks.
Support an inclusive environment
Welcome newcomers; explain context when reviewing or giving feedback.
Avoid jokes or remarks that stereotype, belittle, or exclude groups.
Communicate constructively
Critique ideas, implementation, and designs—not people.
Offer actionable suggestions, alternatives, or examples when raising concerns.
Protect user and partner trust
Treat production incidents, security issues, and data problems seriously.
Avoid public shaming of specific users, partners, or colleagues; focus on fixing systems.
Respect boundaries and roles
Follow the contribution guidelines in CONTRIBUTING.md.
Respect maintainer decisions, even when you disagree, and use appropriate channels for escalation.
Keep documentation and communication honest
Represent project status and limitations accurately in docs and discussions.
Avoid overstating capabilities in ways that could mislead users or partners.

Unacceptable Behaviour

The following behaviours are not tolerated in the Tripinger project:

Harassment and abuse
Threatening or insulting language.
Personal attacks, slurs, or derogatory comments.
Repeated, unwanted contact or attention.
Discrimination
Negative or exclusionary remarks based on nationality, ethnicity, religion, gender, sexual orientation, disability, age, or similar characteristics.
Decisions about collaboration or support that unfairly disadvantage individuals based on these traits.
Sexual or violent content
Sexualized language or imagery in issues, PRs, chats, or documentation.
Jokes or comments that reference violence or harm against individuals or groups.
Disrespecting privacy and confidentiality
Sharing sensitive user or partner data in public channels.
Posting internal operational details (for example, secrets, incident logs) outside approved reporting paths.
Deliberate misrepresentation or bad faith
Knowingly submitting malicious or misleading code, migrations, or configuration.
Misrepresenting identities or affiliations to gain inappropriate access or influence.
Coercion and abuse of power
Using project roles or access to pressure others into actions they are uncomfortable with.
Blocking legitimate contributions without clear technical or safety reasons.

Scope

This Code of Conduct applies to:

All project repositories in the Tripinger monorepo.
All GitHub issues, discussions, pull requests, and code reviews.
Documentation, design notes, and technical planning threads.
Project-related communication channels (chat, email, calls) when representing Tripinger.
Community interactions such as partner onboarding support or early user feedback sessions when driven through project channels.

It does not govern private personal interactions outside the project context, but behaviours there may still affect trust and collaboration if they directly impact project work.

Reporting and Enforcement

Reporting concerns

If you experience or witness behaviour that violates this Code of Conduct:

Prefer private reporting rather than public confrontation, especially for sensitive issues.
Use the channels defined in SECURITY.md for security-related incidents (data exposure, vulnerabilities).
For non-security behavioural issues:
Contact the core maintainers or project leads via the email or contact channel listed in the repository’s main README.md once finalized.
Provide as much context as you can (time, place, participants, links, screenshots), avoiding public disclosure of sensitive data.

You do not need to be directly affected to report a concern; bystanders are encouraged to report too.

How reports are handled

Maintainers will aim to:

Acknowledge receipt of the report promptly.
Review the information and, if necessary, collect additional context (privately).
Decide on appropriate actions, which may include:
A private warning and guidance.
Restriction or removal of repository access.
Rejection or reversion of malicious or harmful contributions.
Coordination with legal or operational channels if serious harm is involved.

Maintainers will strive to respect confidentiality and avoid retaliatory behaviour against reporters.

Consequences

Failure to adhere to this Code of Conduct may result in:

Request to correct behaviour or language.
Temporary or permanent suspension of contribution privileges.
Removal from project roles or administration.
Public documentation of major incidents when necessary for transparency, without exposing sensitive personal details.

For especially severe or repeated violations, maintainers may decide to ban individuals from all Tripinger project spaces.

Relationship to Other Policies

This Code of Conduct works alongside:

CONTRIBUTING.md – defines contribution workflows, technical expectations, and security-sensitive contribution rules.
SECURITY.md – defines vulnerability reporting, incident handling, and data-protection practices.
Architecture and database docs – highlight operational responsibilities and sensitive data categories (user identity, partner compliance, payment references, audit logs).

If any of these documents conflict, safety, security, and respect for individuals always take precedence.

Attribution and Evolution

This Code of Conduct is inspired by common open-source and team collaboration standards, adapted to Tripinger’s specific context as a travel marketplace handling identity, partner compliance, and financial-adjacent data.

As the project grows, this document may be updated to reflect new collaboration norms, regional legal requirements, or community feedback. All participants are responsible for staying aware of the latest version and upholding its expectations.

Code of Conduct

On this page