cba
cba copied to clipboard
Consider using permissive license instead of GPL-3.0
Background
GPL-3.0
license choice was only based on my experience developing Adblock Plus and Privacy Manager, which also was GPL-3.0
. Lately I was suggested to use more permissive license in order to generate more contributors. As it's an early stage of open source and it seem to be save to switch to using permissive license, that is the right time to decide on the final License before we have more contributors and ask them consent under current issue, before contributing.
What to change
Find a permissive license which will not interfere with the future plans of CBA.
Future plans
CBA was and will be always be free, but I would love to find some monetization options to keep developing the product in future. Here is what I'm planing in the long run:
- Donations.
- Premium features, for example ready
presets
that require maintenance effort, similar to deprecated Facebook Like functionality. - Premium support - currently I have capacity of providing private support(i.e. through emails), but in future that might become unfeasible, so we will have public knowledge sharing platform accessible for everyone for free and premium support for people who prefer 1 on 1.
- New project builds based on CBA, which will provide automation for specific platforms and targeted audience.
Those will allow me keep developing CBA and help the automation industry grow, by finding solutions to automation bottlenecks and make CBA better.
CC: @artemharutyunyan
Note: Puppeteer and Selenium, are using Apache License 2.0.