Memi contributors are expected to make technical and design collaboration safe, specific, and constructive.
- Critique the work and evidence, not the person.
- Respect accessibility needs, identity, experience level, and cultural context.
- Give and accept feedback with clarity, patience, and good faith.
- Preserve attribution and respect upstream maintainers.
- Take responsibility, apologize, and repair harm when mistakes happen.
- Harassment, threats, stalking, sexualized attention, or discriminatory speech.
- Doxing or publishing another person's private information.
- Trolling, sustained disruption, or personal attacks.
- Spam, deceptive promotion, impersonation, or manufactured engagement.
- Retaliation against someone who reports a concern in good faith.
This policy applies in organization repositories, issues, Discussions, pull requests, release channels, and public events where someone represents Memi.
For conduct on GitHub, use GitHub's private
report-abuse path. To request
maintainer follow-up, mention the release owner
@sarveshsea without posting sensitive details;
a private channel will be established before evidence is shared. Include links,
dates, context, and any immediate safety concern only through that private
channel. Do not open a public issue containing sensitive personal details.
Maintainers will acknowledge reports, limit access to those who need to respond, and avoid conflicts of interest. Depending on severity and history, responses may include a private correction, content removal, a warning, temporary restriction, or permanent removal from community spaces. Reports made in bad faith may themselves violate this policy.
If a report concerns a maintainer, that maintainer will not participate in the decision. Retaliation is prohibited.