This code of conduct outlines acceptable, encouraged, and unacceptable behavior for organizers, participants, and repository maintainers participating in Iran Open Source Hackathon events. Within this document:
- Organizers denotes maintainers of this project and other people involved in decision making for these events.
- Participants denotes people who contribute to repositories specified for each event.
- Repository Maintainers denotes maintainers of repositories specific for each event to which participants should contribute.
The aim of these events is to (in order of priority):
- Encourage Iranian developers to further participate in open-source, mainly through contribution to other projects.
- Provide a spotlight for Iranian open-source projects and help them build a community.
We strive to make these events inclusive and welcoming to everyone, and provide a harassment-free and positive environment for all, regardless of gender, sexual identity, age, ethnicity, disability, experience, etc.
Note that these events are focused on Iranian open source community. If you are not Iranian, you are still more than welcome to participate and/or enter repositories in the hackathon. While we greatly appreciate either (or any other form of contribution), we might be unable to provide a spotlight for your contributions.
Generally speaking, any action or interaction that strives towards aforementioned goals and values is appreciated and encouraged.
- Use welcoming and inclusive language.
- Remember the human. Criticise ideas and opinions, not people.
- Understand and work with different perspectives and viewpoints.
- View criticism as a positive, not a negative.
- Be empathetic towards other community members.
- First and foremost, focus on improving the projects you contribute to.
- Read provided documents for each repository you want to contribute to. Specifically, follow their code of conduct.
- Check the issues and pull requests before submitting.
- When in-doubt, create issues beforehand to discuss your solution with repository maintainers.
- Understand the project goals, structure, conventions, code styles, testing, etc. Follow contribution guidelines if provided.
- Actively seek advice from repository maintainers, and respect their opinion, experience and time.
- Be friendly, welcoming and empathetic to new contributors. Properly explain to them why they are wrong when they are.
- Try to respond to issues and pull requests within 48 hours, if possible.
- Try to prepare good first issues for new contributors to work on. Generally listing issues that people can help with would be much encouraged.
- Provide documentation for project goals, structure, conventions, code styles, dev setup, etc. Having a contributing guideline is encouraged.
- Provide community guidelines. Having a code of conduct is much encouraged. Ensure that your code of conduct or community guidelines follow the same values of inclusivity and welcomingness.
- Be transparent with your processes, what are project priorities, why decisions are made, etc.
Similarly, any action or interaction detrimental to aforementioned goals and values is unacceptable, and appropriate and fair corrective action will be taken in response.
- Avoid use of sexualized language or imagery, unwelcome sexual attention or advances.
- Avoid trolling/insulting/derogatory language. Avoid remarks that can constitute as personal attacks.
- Avoid behavior that can constitute as public or private harassment (whether in the forums related to these events or in other spaces).
- Avoid publishing others' personal information (name, email, address, phone number, etc.) without their explicit permission.
- Avoid any conduct that is unacceptable in a professional setting.
- Avoid spamming repositories. You should be helping improve open-source projects, not use them to gain scores.
- Avoid disruptive contributions, i.e. taking someone else's pull request / branch / work and submiting it.
- Avoid automated pull requests (automated typo fixes, whitespace removal, image optimization).
- Avoid focusing on issues that are not a priority for the project. Be helpful, not a hindrance.
- Avoid being elitist, harsh, discouraging, or any other attitude that goes against inclusivity, towards participants.
- Avoid marking contributions to your own repositories for participation in the hackathon.
- Avoid information disparity, favoritsm towards certain individuals / groups, stalling, or any action that is clearly with the intent of providing unfair competitive advantage.
Organizers are responsible for clarifying the standards of acceptable, encouraged and unacceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
Organizers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
Organizers have the right and responsibility to blacklist pull requests, participants, and repositories not aligned with this code of conduct, either temporarily, for a certain number of events, from all upcoming events, or retroactively from previous events.
This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. It similarly applies to all project and public spaces for all participating repositories, when individuals are representing any of the participating projects, at least for the duration of their participation. In severe cases of violation, the scope might be extended to activity of previously participating repositories as well.
Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
Any violation of this code of conduct or otherwise unacceptable behavior may be reported by contacting organizers at iran-opensource-hackathon@protonmail.com. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The organizers are obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
Organizers, participants and maintainers that do not follow this code of conduct in good faith, may face temporary or permanent reprecussions determined by organization team. The effects might be for a limited time, the event that the incident happened within, all upcoming events, or even retroactively to past events if need be.
Actions we may take in such instances include (but are not limited to) the following:
- Locking conversations
- Not counting certain pull requests
- Removing users
- Removing repositories
- Banning users form further participation
- Banning certain repositories
- Banning repository owners / maintainers
- Blocking users
- Reporting users to GitHub
This Code of Conduct is adapted from Contributor Covenant, version 1.4, available at http://contributor-covenant.org/version/1/4.