-
Notifications
You must be signed in to change notification settings - Fork 285
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Linux team approves new terminology, bans terms like 'blacklist' and 'slave' #1880
Comments
How is this a woof-ce issue? We will follow what is appropriate for stable puppy. |
IMHO, I see benefit to what is suggested. And, should be a target for nomenclature used in PUPs going forward.
We should desire any/every approach to attract community membership in PUPPY use. If this is mentioned going forward, it has the potential to attracting consideration to the PUPPY fold for newbies sensitive to this. Thus, could be a benefit without penalty.
Just a thought for consideration.
|
Ok, I understand the sensitivity of the issue, don't get me wrong. But until things filter through from upstream (Ubuntu, Debian, Slackware etc) then there isn't a lot we can do. I'll re-open so it can be discussed I suppose. |
I see this as a development understanding vs a discussion. Our desire should be (and is) focused to be as friendly to attracting Puppy Linux interest, just as it has demonstrated in past product development. Thus, many will see a commitment in our stride to present that; as well as, all the compelling innovations that this group has done. As such leaving this open becomes a development target, where appropriate, vs a discussion. As such it become a supporting part of the mission of WoofCE. Friendly, attentive, progressive along with all the things it has always done. |
https://www.zdnet.com/google-amp/article/linux-team-approves-new-terminology-bans-terms-like-blacklist-and-slave/
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=49decddd39e5f6132ccd7d9fdc3d7c470b0061bb
The text was updated successfully, but these errors were encountered: