Hacker News new | ask | show | jobs
by thaneross 1449 days ago
Up to version 1.3 the covenant didn't have a section limiting scope. 1.4 introduced it along with a loophole:

> Representation of a project may be further defined and clarified by project maintainers.

Eg, if you say something the maintainers don't like on your personal Twitter, all they need to say is "you're representing the project in a bad light" and it's fair game to ban you.

Then in version 2.0 the text you quote appears, but changes

> This Code of Conduct applies within all project spaces

to

> This Code of Conduct applies within all community spaces

but never defines what community spaces are. Is your personal Twitter account a community space? Well, once again that's up to the maintainers to decide. It's the same loophole as 1.4 but more cleverly disguised.

1 comments

Have you raised your concern with anyone who can do anything about it?

In any case, I fail to see how this is any worse than any other project. Do you expect some sort of due process before you're banned from any random OSS project? I wouldn't. If you don't like it, you can fork the project. That's how it works.