License - Modified Apache 2.0 vs Apache 2.0 · maxGraph/maxGraph · Discussion #35
It looks like section 4(e) was added to the license in October 29, 2020, which is a clause on work and derivative works being integrated or used with Atlassian products.
The commit includes:
Note that all versions prior to this commit still fall under the Apache 2.0 license only.
I'm not a lawyer, but I believe the 4(e) clause would prohibit anything using mxgraph from having any kind of Atlassian integration, for example a connector to create Jira tickets.
If all versions prior to that commit still fall under the Apache 2.0 proper license, would we be able to rebase this fork off of the commit prior to this? I'm sure there's been a bit of work that's gone into the source since that commit, which would require a bit of effort to get those individual changes back. I think the benefit of a less restrictive license license would be worth it in the long-term.
I can't stress enough that I'm not a lawyer and this isn't legal advice. 😅
4 replies
Rebase may not be the best option, agreed. I didn't see that issue when I had first looked before opening the discussion, my apologies! I think reverting the commits would definitely be a great way of going about it.
I had an email exchange with @coclav on this and it really is just the name 'mxgraph' that is the problem.
"
So I had the confirmation from the guys at mxGraph that we cannot use the name mxGraph, appart from that we are all good. I posted a message about it there : #23
"
so long as we change the name, then all is good and we can use this code base with a new name. Something to do with :
"//SEIBERT/MEDIA GmbH, Wiesbaden, Germany is the exclusive licensee of
JGraph for software products based on this codebase within the Atlassian
ecosystem of products."
but we have been assured that a simple name change will satisfy everyone
I have to say that it is beyond my understanding ... but a lot of things are
That seems so wrong and feels so weird
so we can rollback to the original apache license v2?
2 replies
Sorry for the late answer
Yes we can rollback to the original apache license v2 it in the development branch.
@lalicw do you want to provide a Pull Request?
I found this discussion too late and I fill like re-doing things already done ! In all cases I created an issue #89 describing a possible process for the transition to the Apache 2.0 license and made #90 and #91 in the same context. I noticed that @tbouffard stated #35 (comment) that the 4 problematic commits could be maybe re-written or re-applied
mostly taken from code proposal in issues
0 replies
Conversation locked, discussions continue in #89
0 replies