Comments (6)
After reading the licenses proposed by GitHub and lots of consideration, I believe that Apache License 2 seems the right choice.
I hope that the change from the license material being documented will enable us to keep a good state for this library even if a company create a personal version of this module (still counting on good will though).
From my understanding, the MIT license is a bit too permissive as the users will not know what comes from the original module and what is coming from their developed branche.
It brought me lots of "existential" questions about the project itself and what I wanted to achieve with it. Thanks for it @xSAVIKx.
The goal here is to try to avoid that the project stops being a "community-enhanced" project but still allow private entities to have their own (private) version when needed, stating clearly what has been developed where/by whom.
I do not wish to be a blocker to use what has been developed by the community but I have been a bit too much disappointed by corporate behavior to offer a MIT license (yet).
On this day, I will push the change today for aanalytics2 and probably aepp library so we can start 2021 fresh and clean.
Taking the opportunity to wish a happy new year.
from adobe-analytics-api-2.0.
I understand that it may be a bit too much as you need to publish the source-code.
That is what I found the closest to actually getting anything back from people/companies working on it.
I will consider it over the next days (and most probably change it) just need to find the one being the best suited between the 2 choices.
I'll run some research with wikipedia ;)
Have a nice holidays season if you are off.
from adobe-analytics-api-2.0.
Perhaps GitHub's Choose A License might help you:
from adobe-analytics-api-2.0.
Thanks for the proposal. I need to look more into this.
My main motivation is that people should provide feedback / PR to the main source code so everyone can gain from other experiences.
I don't mind that people re-sell it or productionize it but I don't want people fixing all issues (main) on their own and never give back these fixes to the community.
We are providing lots of value for companies for free and if they decide to invest further in this module (by using it to production), it should be at least provide value for us (analytics community).
If one of your 2 proposed license is providing flexibility and also ensure participation in the code improvement.
I'll definitely consider it.
from adobe-analytics-api-2.0.
Unfortunately, no licensing will defend the open-source here. There'd always be companies who'd use the software and never give anything back. But this particular license can (I'd say will) lead to people not even trying to work with the module.
E.g. the company I help with some backends has a strict licensing policy and no GNU-licensed library can be ever used. It's OK to use the tooling, but not a library.
from adobe-analytics-api-2.0.
Published live via commit 2f6a4b3
from adobe-analytics-api-2.0.
Related Issues (20)
- Issue with findComponentsUsage function after last update HOT 3
- findComponentsUsage function fails HOT 9
- findComponentsUsage KeyError: 'reportlet' HOT 8
- UnboundLocalError: local variable 'myProjectDetails' referenced before assignment HOT 5
- Issue with getUsagelogs method HOT 10
- Data warehouse method HOT 1
- getReport does not work with RequestCreator HOT 2
- [Bug] Statistics needed in getReport2() HOT 5
- createConfigFile() Improved argument parsing HOT 3
- getUsagelogs returning KeyError 'Content' HOT 7
- getReport2 fails if dimensional value filters are used as segments HOT 5
- Limit HOT 2
- Feature Request: Ability to pass through a logging.formatter class to the logger. HOT 2
- Bug: DataFrame obtained from getReport method not matching table seen in Adobe Analytics portal. HOT 3
- Updating segment error HOT 1
- Feature Request: getRequests() Method HOT 1
- getReport methods do not accept requests without a dimension HOT 6
- Pandas error from getReport2 (for a request with no dimensions and no STATIC_ROW_COMPONENT. HOT 3
- getReport2 returns incorrect numbers for metrics/pageviews. HOT 7
- getReport2 should not rewrite the request HOT 12
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from adobe-analytics-api-2.0.