Criteria for adding additional functions?

[Maushundb]

@char0n Do we have a policy or set of guidelines for what functions will and will not be added to the library? I imagine we want to avoid bloat if the function is too niche or similar to something existing, but also want to make it easy for folks to know if their contribution will likely be accepted.

[char0n]

@Maushundb everybody has a possibility to create an issue with his new feature proposal and elaborate on it there. Usually there is a discussion about it and if consensus is made we push it forward by properly labeling it.

This repo is governed in BNLF mode, which means that even when there is a consensus by contributors or community I can still stop it getting in the codebase if I don't consider it suitable addition to the library. Example of this can be ramda-log which lot of users requested, but I did not allow it to become part of the codebase (obvious impurity + side effects).

Objective parameters of new features:

1.) new features needs to be pure (one exception is various promise transformers and utils)
2.) cannot be toooo specific (this means having feature specific to one person's usecase)
3.) must solve a real problem

[Maushundb]

Got it, that makes sense. Thanks!