|Re: [epl-discuss] Inquiry about EPL 1.0|
I am one of the developers of EPL 1.0 software project. This letter is in regard to my inquiry about the usage rule of EPL 1.0.
- Thus, may I write "copyright (c) 2021 XXX project contributors" for a project which will firstly open source a few weeks later under EPL 1.0 as its contributors really want to remain anonymous?
Honestly, I don't know the answer to this question. If no one else on this list can answer it, then I would suggest trying license-discuss@xxxxxxxxxxxxxxxxxxxx.
Historically, the Eclipse Foundation does not allow anonymous
contributions, but I believe that is because we want to ensure
complete transparency on the provenance of all our project's code.
- I learned in the 27th clause of FAQ of EPL 1.0 saying that "if you've written your own Eclipse Platform Plug-in with 100% your own code to implement functionality not currently in Eclipse, then it is not a derivative work" and "For clarity, merely interfacing or interoperating with Eclipse Platform Plug-in APIs (without modification) does not make an Eclipse Platform Plug-in a derivative work. " I wrote myself a J2V8 derivative work and "A Software". "A Software" (licensed under Apache 2.0) can call the J2V8 derivative work by APIs, but the former is not the plug-in of the latter. In this case, can "A software" still prevent from being contaminated by EPL 1.0?
I am sorry, but I am not sure I completely understand the
scenario you're describing. Could you try to restate the scenario?
In what way is your software a J2V8 derivative work?
You can use the EPL 2.0.
I really appreciate your time and patience! Looking forward for your reply!
I hope this was helpful!
Executive Director | Eclipse Foundation AISBL
Back to the top