Contribution and issue guidelines, code of conduct #26

New Issue

blek · 2023-12-09T13:39:12+01:00

blek commented

2023-12-09 13:39:12 +01:00

The overall guide to contributing is in the CONTRIBUTING.md file in the root of the repo.
This issue is about creating issues and talking to each other.

Code of Conduct

By participating in a discussion, you agree to a certain number of rules on about how we talk to each other.

Be professional. Even though you are doing volunteer work, professionalism is how you make a nice product, even if you don't get anything out of it.
When in an argument, you are required to base your position only on hard, imperical facts. Anything else will not be tolerated.
Don't be an asshole. This includes causing any kind of problems to anyone.
Put your personal relations aside. Seriously, this is not the time nor the place. You have DM's and emails for that, and this is a public forum. Besides, you would make yourself look like a dick which wouldn't be good for your reputation.

If an argument gets very controversial, the BDFL would have the final say in it as to cause as less trouble as possible.

Issues

Ah, the good old issues.

Please, do your research before posting. If you have a general question, code contributing question (as "how do i understand the codebase", a bug report, anything - it is all welcome as long as it is not absurd or stupid.

Bug reports

Include the full steps on how to reproduce the bug. Its fine if the bug is not easily reproducible, but your report will be dismissed if it does not contain the full steps for reproducing it.

The overall guide to contributing is in the `CONTRIBUTING.md` file in the root of the repo. This issue is about creating issues and talking to each other. # Code of Conduct By participating in a discussion, you agree to a certain number of rules on about how we talk to each other. 1. Be professional. Even though you are doing volunteer work, professionalism is how you make a nice product, even if you don't get anything out of it. 2. When in an argument, you are required to base your position only on **hard, imperical facts.** Anything else will not be tolerated. 3. Don't be an asshole. This includes causing any kind of problems to anyone. 4. Put your personal relations aside. Seriously, this is not the time nor the place. You have DM's and emails for that, and this is a public forum. Besides, you would make yourself look like a dick which wouldn't be good for your reputation. If an argument gets very controversial, the BDFL would have the final say in it as to cause as less trouble as possible. # Issues Ah, the good old issues. Please, **do your research before posting.** If you have a general question, code contributing question (as "how do i understand the codebase", a bug report, anything - it is all welcome as long as it is not absurd or stupid. ## Bug reports Include the full steps on how to reproduce the bug. Its fine if the bug is not easily reproducible, but your report will be dismissed if it does not contain the full steps for reproducing it.

blek pinned this 2023-12-09 13:41:33 +01:00

Sign in to join this conversation.

No Milestone

No project

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blek/bfile#26