Community Code of Conduct

1. Where this applies

This Code of Conduct covers every space the Oprex community uses:

• the city communities, posts, and comments on community.oprex.id;
• community events — meetups, workshops, campus sessions, online or in person;
• public repositories and issue discussions on git.oprex.id;
• official Oprex channels: support tickets, community chat groups, and social accounts we operate.

It applies to everyone equally: members, event organisers, moderators, campus partners, sponsors, and the Oprex team itself. It also applies when someone represents the community elsewhere — speaking at an event as an Oprex organiser, for instance.

2. The standard we hold each other to

3. What is not acceptable

• Harassment — insults, threats, stalking, unwanted contact after being asked to stop, or persistent disruption of a discussion or event.
• Discrimination — treating someone as lesser because of religion, ethnicity, nationality, gender, sexual orientation, disability, age, appearance, education, or economic background.
• Sexual attention that is unwelcome, including sexual imagery, comments about someone's body, or advances in a professional space.
• Doxxing — publishing someone's private information (home address, personal phone number, employer, identity documents, private messages) without their explicit consent.
• Deception — impersonating another person, a company, or a member of the Oprex team; faking credentials or endorsements.
• Abuse of the platform — spam, unsolicited bulk promotion, scraping members' contact details, malware, or using a community space mainly to sell.
• Sabotage — deliberately breaking a shared project, deleting other people's work, or leaking a security issue before its maintainers have had a fair chance to fix it.
• Encouraging any of the above, or retaliating against someone who reported it.

Heated technical argument is not on this list. Passion about a design decision is normal and welcome; contempt for the person holding it is not.

4. Reporting a problem

If you experience or witness behaviour that breaks this Code, report it to hello@oprex.id with "Code of Conduct" in the subject, or open a private ticket at support.oprex.id. If the person you need to report is on the Oprex team, say so in the report — it is routed to the company's management, not to the person involved.

Useful to include, but none of it is required: where it happened, roughly when, what was said or done, links or screenshots, and whether anyone else saw it. A report with only "this person made the meetup unbearable for me" is still a valid report.

What we promise. We acknowledge every report within 2 working days. We keep the reporter's identity confidential within the review, and we never share it with the person being reported without the reporter's permission. Nobody is penalised for making a report in good faith — retaliation is itself a violation. A report that is knowingly false is treated as a violation too.

5. How a report is handled

1. Acknowledgement — within 2 working days, so you know it reached a person.
2. Review — we read the material, and where it is fair to do so we ask the other person for their account. Two people review anything that could lead to a suspension, so no single person decides alone.
3. Decision — normally within 10 working days. Complex cases take longer; if so, we say so rather than going quiet.
4. Outcome — the reporter is told what action was taken. The person concerned is told which part of this Code applied and what happens next.

Urgent safety matters — threats, or anything happening live at an event — are handled immediately by the organisers present, with the review following afterwards.

6. Consequences

What follows a violation depends on its seriousness, on whether it is repeated, and on the harm done. Usually in this order:

1. A private word. A moderator explains what was wrong and what to do instead. No public record.
2. A formal warning. Written, recorded, with a clear condition — commonly no further contact with the person affected for a set period.
3. Temporary suspension. Removal from community spaces and events for a defined period. Content that violates this Code is taken down.
4. Permanent removal. For serious harm, deliberate repetition, or retaliation against a reporter.

Serious cases can start at step 3 or 4 — there is no obligation to work through the ladder before protecting people.

7. Appeals

If you believe a decision about you was wrong, reply to the decision within 14 days and explain why. The appeal is read by someone who was not part of the original decision. The outcome of an appeal is final, and we will tell you plainly either way.

8. If you organise or moderate

Organisers and moderators carry this Code on behalf of everyone else. That means: state at the start of an event that the Code applies and how to reach you; act on what you see rather than waiting for a formal report; write down what happened while it is fresh; and hand anything involving safety, a sponsor, or a member of the Oprex team to hello@oprex.id instead of settling it alone.

9. About this document

This Code is maintained by PT Kinetikum Indo Solusi, which operates Oprex. Its structure follows what has become common practice for developer communities; the wording is our own. We will update it as the community grows, and material changes are announced on community.oprex.id before they take effect.

Questions about how this applies to your city community, campus, or event are welcome at hello@oprex.id — asking in advance is always better than guessing.