No one has answered my question. What about the the word "Apache"? Are
their 'redlist[s]' out there who'll be offended by this name?
For all the talk about giving SA more appropriate and descriptive names
the motivation for changing them (whitelist, blacklist) was ultimately
to be politically correct. Am I wrong?
Admit it, the SA community was never racist to begin with. It was some
white guys trying to improve life for everyone. That's noble and
commendable. This has been my goal in IT as well. Now is not the time to
grovel to whiners, it's time to man up and continue to improve your product.
I'd like to see SA have as good a probability filter as DSPAM but with
the ability to whitelist, which DSPAM does not have.
On 7/10/2020 3:25 PM, John Hardin wrote:
On Fri, 10 Jul 2020, sha...@shanew.net wrote:
On Fri, 10 Jul 2020, Axb wrote:
On 7/10/20 8:31 PM, Bill Cole wrote:
The SpamAssassin Project has a particular self-interest in attracting
contributors from a diversity of cultures, because we are always
at risk
of mislabelling a pattern of letters or words as 'spammy' when in
fact it
is entirely normal in a cultural context other than those of the
existing
contributors to the project. C
From what I see, until now, only two ppl of the SpamAssasin project
have supported this motion and intend to impose this quatsch to the
rest of the world.
Voices against these changes have been politely ignored.
The danger of judging the world only by what is within your sight is
that your field of vision is limited, and there are any number of
explanations for why what you see is not representative of the whole.
Maybe those who agree feel no need to comment.
Maybe a lot of people
on either side of the issue want to avoid adding more noise to a list
that's about SpamAssassin.
For me, this. But I do now feel I should contribute my 5¢ to the noise.
As a PMC member I did vote on the proposal when it came up a week or
so back. I voted +1 with the strong condition that it include full
backwards compatibility for a long time (ideally permanently), but
that vote was reluctant.
I share the opinion that such terminology changes are "political
correctness through newspeak" because the current terms are
widely-known terms having a long standing without racist denotations
or even connotations, and that those who are offended by them on that
basis are the type of people who look for excuses to be offended. But
my thought was if we can avoid that nonsense *without* greatly
disturbing the project, we should probably do it.
But there is no technical reason whatsoever to make this change, and
there are good technical reasons not to. I agree with Joanna 100%:
Political correctness has no place in engineering. Clarity of
communications is a basis of the craft. When you disrupt it
things break.
and
Fixing what works is as fine a way to introduce new faults in
the code as I can think of.
I am rethinking my +1 vote for this change.
