Home » Newcomers » Newcomers » Am I allowed to show Eclipse as an example in our proprietary software's API Documentation?(Licensing, Legal)
| Am I allowed to show Eclipse as an example in our proprietary software's API Documentation? [message #1690516] |
Fri, 27 March 2015 19:13  |
 Chris Ku
Messages: 2
Registered: March 2015 |
Junior Member |
|
|
Hello. I'm a software engineer at a startup.
We're releasing our API for our proprietary product, and thought it'd be great to show how to use the API (It is a packaged .jar!) in Eclipse. It would show, step by step, on how to add the jar to the build path in Eclipse along with screenshots of Eclipse (such as right click -> build path -> add to build path context menu).
Now, of course, the question becomes if I'm allowed to do that. Microsoft allows screenshots of their products if a few conditions are followed (such as not defaming them, having any other third party software installed/shown along with it, etc). I looked through the EPL 1.0, but it seems to mostly just talk about code.
If anyone can point me in the right direction, I'd appreciate it very much!
|
|
|
| Re: Am I allowed to show Eclipse as an example in our proprietary software's API Documentation? [message #1690524 is a reply to message #1690516] |
Fri, 27 March 2015 23:48  |
|
On 03/27/2015 03:01 PM, Chris Ku wrote:
> Hello. I'm a software engineer at a startup.
>
> We're releasing our API for our proprietary product, and thought it'd be
> great to show how to use the API (It is a packaged .jar!) in Eclipse. It
> would show, step by step, on how to add the jar to the build path in
> Eclipse along with screenshots of Eclipse (such as right click -> build
> path -> add to build path context menu).
> Now, of course, the question becomes if I'm allowed to do that.
> Microsoft allows screenshots of their products if a few conditions are
> followed (such as not defaming them, having any other third party
> software installed/shown along with it, etc). I looked through the EPL
> 1.0, but it seems to mostly just talk about code.
>
> If anyone can point me in the right direction, I'd appreciate it very much!
Eclipse is completely free and open. If you've got third-party stuff to
show, that's up to them. It doesn't sound to me as if you've anything to
worry about.
|
|
| |
| Re: Am I allowed to show Eclipse as an example in our proprietary software's API Documentation? [message #1690739 is a reply to message #1690697] |
Mon, 30 March 2015 23:25 |
|
On 03/30/2015 10:28 AM, Chris Ku wrote:
> Thank you so much for your helpful response!
>
> Is there a preferred location to include the Eclipse Public License
> anywhere in our documentation / program / api? I'm assuming this is a
> requirement.
I would not consider it a requirement, but I'm no authority whatsoever.
You crawl through this page, https://eclipse.org/legal/, but remember
that there is a distinction between Eclipse source code, source code
contributors make, source code plug-in author create, and the source
code you create as you implement your own application.
The latter in that list is completely yours and you can make it public
or private as you wish. The rest has increasingly stringent guidelines
as you move up to the beginning of my second paragraph, i.e.: plug-in
authors aren't required to open their plug-in code, but contributors to
Eclipse are more or less abandoning the right to keep their
contributions private since, in theory and in practice, you're able to
build the Eclipse IDE itself.
I've gone way out past my expertise here, but I hope this helps.
|
|
|
Goto Forum:
Current Time: Wed Apr 24 21:07:06 GMT 2024
Powered by FUDForum. Page generated in 0.08036 seconds |
] 
Search
Help
Register
Login
Home
