Skip to content
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

#BLM and 5.x planned changes #247

Open
1 of 7 tasks
bithavoc opened this issue Jul 22, 2020 · 3 comments
Open
1 of 7 tasks

#BLM and 5.x planned changes #247

bithavoc opened this issue Jul 22, 2020 · 3 comments
Labels

Comments

@bithavoc
Copy link
Owner

bithavoc commented Jul 22, 2020

Based on the great suggestion posted in #241 by @dsafanyuk we're getting rid of terms such as whitelist, blacklist, and master and we're introducing these breaking changes in the 5.x series of this module.

The plan is as follows:

Until January 2021 we will maintain two branches of the project: the 4.x series and the 5.x series which gets rid of all the banned terms.

Plan

  • Added warning in Readme
  • Create 4 branch, all new releases of the 4 series will come from this branch.
  • Rename internals to get rid of banned terms in variables, functions, and non-exposed types.
  • Modify code and test so it merges both the banned configurations and the inclusive configurations as long as we're sure these are backward compatible changes.
  • Create 5 branch, get rid of absolutely all the banned terms.
  • Release minor release of the 4.x series + first release of the 5.x series August 2020.
  • 4.x reaches EOL January 2021
@punund
Copy link

punund commented Mar 12, 2021

If this change gets implemented, my personal blacklist of software will grow by one item.

@evilbuck
Copy link

evilbuck commented Apr 5, 2021

Empty virtue signaling at it's finest. Might want to take a look at real issues before you start making changes to terms that don't have anything to do with race.

@bithavoc
Copy link
Owner Author

bithavoc commented Apr 5, 2021

This is happening, the only reason it hasn't yet is because of lack of time and now I'm considering going typescript and removing the dependency on lodash so we have fewer security issues.

@punund it sounds you have plenty of time to cross out this software from the list. You have my approval :)

@evilbuck this is a free and open-source project, we more than welcome contributions if you really want to make a difference.

Locking this issue until the transition is over.

Repository owner locked and limited conversation to collaborators Apr 5, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants