Isn't that the same for most open-source software[1]? To a Wikipedia editor going into a programming project to correct documentation, it might seem absurd that we want them to 'pass CI', 'squash the commits and correct the message column width to pass the code style', or 'sign the CLA'.
[1] It's a very prettied-up domain-specific language but it's still copyleft software.
It would be, if the requirements were clearly documented, consistent for all pages, and consistently enforced. They are none of those things.
EDIT: the other big difference is that every time I've attempted to contribute to an open-source project, people have, in general, been helpful and willing to explain what needed improvement. On Wikipedia, it's a much more hostile attitude. People are less willing to explain why your content was reverted or nominated for deletion, and if you protest, there's a decent chance that you'll be sanctioned (either topic-banned or temp-banned from Wikipedia). Imagine if forgetting to run a linter got your SSH key tempbanned from the project and you'll have a closer analogy to the current process.
quanticle|6 years ago
EDIT: the other big difference is that every time I've attempted to contribute to an open-source project, people have, in general, been helpful and willing to explain what needed improvement. On Wikipedia, it's a much more hostile attitude. People are less willing to explain why your content was reverted or nominated for deletion, and if you protest, there's a decent chance that you'll be sanctioned (either topic-banned or temp-banned from Wikipedia). Imagine if forgetting to run a linter got your SSH key tempbanned from the project and you'll have a closer analogy to the current process.