Skip to content

Linux + iPhone Continuity / iMessage / SMS

4.8 KB
Raw Blame

Tether Code of Conduct

Tether is a project for making Linux and iPhone play nicely together.

Apparently, that means we also need a document explaining how humans should play nicely together.

So here we are.

This Code of Conduct exists because open-source projects work better when people are treated with basic respect. It is intentionally shorter than a Kubernetes manifest and considerably less complicated than Bluetooth.

The Rules

1. Don't be a jerk.

That's the big one.

Tether welcomes contributors and users regardless of race, ethnicity, gender, sexual orientation, disability, religion, nationality, age, experience level, or any other characteristic that has nothing to do with whether their contribution is useful.

Intolerance is not tolerated.

Harassment, discrimination, threats, personal attacks, hate speech, or other hostile behavior aren't welcome here.

You are allowed to disagree with someone's design, implementation, opinion, or choice of text editor.

You are not allowed to turn that disagreement into an attack on the person.

Yes, this really does need to be written down.

2. AI is a tool, not a contributor.

Tether is perfectly happy for you to use AI.

Use it to explain some horrifying C++ template error. Ask it why BlueZ is doing whatever BlueZ is doing. Have it suggest an implementation. Have it review your code. Make it write boilerplate. Whatever.

However:

Do not submit things you do not understand.

That applies to code, issues, pull requests, comments, documentation, commit messages, and anything else you're presenting as your own contribution.

In particular, completely AI-generated Issues, PRs, and comments are not welcome. We don't need a bot having a conversation with another bot about whether std::optional should be used.

If you submit code, you are responsible for understanding the code. You should be able to explain what it does, why it works, and ideally why it doesn't immediately summon demons when connected to an iPhone.

AI assistance is fine.

Outsourcing your understanding is not.

3. Disagreement is allowed.

In fact, disagreement is useful.

Tether involves Bluetooth, Apple protocols, Linux, networking, C++, reverse engineering, and several technologies that appear to have been designed specifically to generate arguments.

You are encouraged to challenge ideas and point out problems.

Please attack the problem, not the person.

"That implementation will deadlock" is useful.

"Are you stupid?" is not.

4. Keep discussions technical when they can be technical.

Not every discussion needs to become a referendum on someone's character, intelligence, politics, operating system, or preferred editor.

If the question is whether a mutex is necessary, let's discuss the mutex.

If the question is whether Vim is objectively the correct editor (it is), there is unfortunately no Code of Conduct strong enough to settle that matter.

5. Assume good faith, until there is a reason not to.

People make mistakes.

People misunderstand things.

People submit bugs that turn out to be configuration problems.

People write code at 2 AM.

Start from the assumption that someone is trying to help. If something is genuinely problematic, explain why and give them a reasonable opportunity to correct it.

6. Swearing is allowed.

This is an open-source project. Sometimes Bluetooth does something fucking inexplicable.

Swearing at a computer, a compiler, a protocol specification, an API, an error message, or the general state of technology is fine.

Swearing at another person is a different matter.

There is a meaningful difference between:

"What the fuck is this compiler doing?"

and:

"What the fuck is wrong with you?"

The first is encouraged.

The second is not.

In short: Cuss freely. Don't use profanity as a weapon against other people.

Enforcement

If someone violates these rules, maintainers may take whatever reasonable action is necessary, including removing comments, closing issues or pull requests, restricting participation, or banning someone from the project.

We will generally prefer explanation and de-escalation over punishment.

However, nobody is entitled to an infinite number of chances to be awful.

Maintainers are also human beings. Please don't make them read 47 paragraphs of an argument about whether a comment was technically harassment.

One Last Thing

This document is not intended to be a comprehensive legal framework for human interaction.

It is a reminder that there are actual people on the other side of the GitHub username.

Be curious. Be helpful. Be respectful. Assume good faith. Learn things. Ask questions.

And if you disagree with something, that's fine.

Just don't be a dick about it.

That's the entire Code of Conduct.

We have Bluetooth to make unnecessarily complicated.