> an extensive month long discussion that leaks implementation details of a private repo and ultimately leads to adding 1 readme comment that merely _suggests_ something
https://github.com/artsy/README/issues/459What implementation details? Most of the stuff linked in there seems to be in public repos that have interfaces to this private repo, so I can't see that the discussion itself is leaking more implementation details than reading the code in the public repos that interacts with the private repo.
Secondly, the conversation in there is long, but hardly unusually so. At most each comment apart from the initial one took up ~10 minutes of time for each of the authors. Are we at the point where 8 well-formatted comments on a GitHub issue are going to make us go "ooh, long discussion, must be something wrong with it"? I would rather have long, well-formatted comments than "lol ok" style garbage.
Finally, I wish more people would conclude a month-long discussion with a simple action rather than carrying out an unnecessary and complicated one because "Well, something has to be done, and it has to be large because we have discussed a lot". This can be counterproductive with dealing with complex libraries that you don't understand yet.
> adding politically motivated language and starting a policy to open issues in dependencies that do not conform. Look at the time and energy putting into changing master -> main and white/blacklist -> allow/deny. Also https://github.com/artsy/README/issues/427
I would prefer to stop talking about this stuff, but it's hard when I often see lazy drive-by denouncements like "Politically motivated" in comments near the top.
Language seems to be important to the people working on the project. It would probably not be the first thing I pick up, but I don't understand why it's considered a "doozy". Good documentation does think about the people using it as well as clarity; and "denylist" is more informational than "blacklist" in addition to being more sensitive. Real language idioms change just like programming language idioms, and railing against them is about as useful as claiming you hate Python 3 because they took out the print statement.