Stories
Slash Boxes
Comments

SoylentNews is people

posted by martyb on Thursday September 05 2019, @07:27AM   Printer-friendly
from the blacklisting-"blacklist" dept.

Arthur T Knackerbracket has found the following story:

Microsoft's adoption of the Google-developed Chromium browser engine for Edge has resulted in a proposal to cleanse the open-source code of "potentially offensive terms."

Issue 981129 in the Chromium bug log lists a suggestion by Microsoft to “cleanup of potentially offensive terms in codebase” aims to rid the software blueprints of language such as whitelist (change to allowlist), blacklist (change to blocklist), “offensive terms using ‘wtf’ as protocol messages,” and other infelicities.

This bug report was raised by a Microsoft contributor, who stated: “We are just sharing a subset of what PoliCheck scanned for us,” Policheck being “a machine-learned model that another team manages that does context based scanning on hundreds of file formats.”

Googler Rick Byers, a Chromium engineer, gave the issue a cautious welcome, saying: "This sounds like a good strategy to me, thanks for doing this! We certainly have never intended for anything in the codebase to be potentially offensive, but I'm also not aware of anyone making an effort to find them all." He added:

I don't expect Chrome teams to necessarily make these bugs a priority (we haven't seen this pose a problem for us in practice as far as I know), but if cleaning this up is valuable for Microsoft (or any another Chromium contributor) then we should have no trouble getting the necessary code reviews (at least in the platform code). And yeah there are folks who look for GoodFirstBug and may want to pick up some easy commits.

Although changing comments or variable names in the source code is generally invisible to the user, this kind of revision can be problematic if it wrecks things like names in preferences and policies.


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 4, Insightful) by maxwell demon on Thursday September 05 2019, @02:30PM (1 child)

    by maxwell demon (1608) on Thursday September 05 2019, @02:30PM (#890037) Journal

    But a more logical counterpart to allowlist would have been denylist.

    --
    The Tao of math: The numbers you can count are not the real numbers.
    Starting Score:    1  point
    Moderation   +2  
       Insightful=1, Touché=1, Total=2
    Extra 'Insightful' Modifier   0  
    Karma-Bonus Modifier   +1  

    Total Score:   4  
  • (Score: 2) by Booga1 on Thursday September 05 2019, @02:51PM

    by Booga1 (6333) on Thursday September 05 2019, @02:51PM (#890045)

    Fair point, I do agree with that.
    Approvedlist/deniedlist or any other context appropriate combination might also work depending on what you're trying to achieve.