Comment by crote
Shouldn't the "no discrimination" part also apply to the community?
How would you feel about a project with an official policy that pull requests from people with a certain skin color will not be accepted - is that still in the spirit of F/LOSS? If a specific maintainer in an otherwise friendly community refuses to merge pull requests from developers with a certain skin color, how should the community handle that?
If the other maintainers fork the project and continue without that one toxic maintainer, are they following the spirit of F/LOSS, or are they suddenly "needlessly introducing politics" and "distracting from development"? If the latter, why would the actions of that one toxic maintainer not fall under the same?
If you notice that your community is rapidly losing core members because they keep getting insulted by that one toxic maintainer, what do you propose one should do? Do you take action, or do you let the project die?
> How would you feel about a project with an official policy that pull requests from people with a certain skin color will not be accepted - is that still in the spirit of F/LOSS?
No, but this is irrelevant to any of the currently discussed situations.
> If the other maintainers fork the project and continue without that one toxic maintainer, are they following the spirit of F/LOSS
To have this argument requires accepting your framing around "toxic maintainers" which is probably not very productive. But of course forking projects to do your own thing is entirely in the spirit.
Regardless, though, that is not what people are objecting to. For example, an XLibre project wiki was defaced with disparaging comments, including by Jordan Petridis (deeply involved with both GNOME and Xorg) (https://github.com/X11Libre/xserver/issues/346#issuecomment-...). This was highly unprofessional and XLibre should not have to deal with it regardless of what you think about the politics of anyone involved.