5

Imagine you decide to spend a few hours to contribute to an open-source project wiki/documentation that hasn't been updated in years, to actually make it useful for new users, and then the maintainers start expecting further modification and corrections from you before pulling the PR, like you work for them, instead of just fucking pulling it in and then editing what they want themselves. It's just another example of how stupid and nonsense the open-source community can be.

Comments
  • 1
    I might be irked.

    But that depends on the request.

    Like better documentation in spot X might actually be technically correct but without jiving with other documentation it is possible that it might not be the best to just improve it at spot X alone ... and it should be part of a larger overhaul. Not everything is something you can iterate in small bites.
  • 1
    I basically updated the whole page to modern practices (it had instructions for Visual Studio 2017).
  • 3
    I've heard people say "don't work on any open source thing that hasn't been worked on by someone else recently because if you're the last one to do anything people will contact you about it". I think that applies here.
Add Comment