On 5/18/21 1:46 PM, Gabriel Beims Bräscher wrote:
Thanks for the update, Rich. I agree 100% with you. We can work towards recommending some options, but in the end, each project has its own context. As an example, Kevin showed a nice case where it was adopted *a 'welcome list*' and *'block list*' in order to kept backward compatibility in their context. As opposed to the *'welcome/block*', CloudStack was already adopting *'allow/block'* for a while at some points and now we are normalizing it all to use only 'alow/block'. From what I have seen there is also a need for some sort of pattern; I have seen people arguing that such changes would not make sense as there is no pattern or guideline to be followed, as if we need to have a consensus in the IT industry (or some entity such as ASF) before moving on with such changes.
This is one of the main things that https://inclusivenaming.org/ is working on, and we should go participate in that, rather than doing that work independently here. That will avoid having YAS (Yet Another Standard), and it will also benefit both us, and them, by lending another voice to the effort.
-- Rich Bowen - rbo...@rcbowen.com @rbowen --------------------------------------------------------------------- To unsubscribe, e-mail: diversity-unsubscr...@apache.org For additional commands, e-mail: diversity-h...@apache.org
