You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Leon Rosenberg <ro...@googlemail.com> on 2006/03/08 12:11:15 UTC
[OT] Question about licensing
I'm sorry for OT, but I am pretty stupid with legal stuff, and after
carefully reading gnu und apache license packages I am as unknowing as
I was before. Here my problem:
I am trying to convince one of my customers to make some of the libs I
wrote for him public available. For process reasons the source code of
the libs will not be available, only the jars would be available and
redistributeable. I thought publishing the jar under the LGPL would
make it, but after reading http://www.gnu.org/licenses/lgpl.html I'm
starting to doubt it.
Since we must have many experts in licensing here, I think there is no
better place to ask :-)
The jars would be free for copy, modification, usage, all the gpl
stuff, but not available in sourcecode. This is because the company,
which owns the code, has to make additional reporting to the
headquarters in case they would publish the source code and ensure,
that there are no comments in the source code, that contain
non-disclosure information. Publishing the jars only would be lot of
easier for them, and the probability, that they would do it, is
higher. So under which license do they need to publish the jars?
Or is it something which can be achieved by a trick? Creating a dummy
application which contains the jars and put the application under
lgpl, therefore providing source code for the application, but no
source code for the libs?
any help is highly appreciated
regards
leon
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: [OT] Question about licensing
Posted by Leon Rosenberg <ro...@googlemail.com>.
On 3/8/06, Michael Jouravlev <jm...@gmail.com> wrote:
> The following post contains no value :-)
>
> On 3/8/06, Leon Rosenberg <ro...@googlemail.com> wrote:
> > For process reasons the source code of
> > the libs will not be available
>
> > The jars would be free for copy, modification, usage,
> ^^^^^^^^^^^^^
> How can you allow modification without source code?
the scenario is that someone familar with the code (like me) creates a
open source application and the jars are allowed for distribution.
>
> > This is because the company,
> > which owns the code, has to make additional reporting to the
> > headquarters in case they would publish the source code and ensure,
> > that there are no comments in the source code, that contain
> > non-disclosure information.
>
> This is a really stupid reason ;-) I am curious is there a tool that
> strips out comments from the source code? The code itself can be
> easily reverse-engineered.
well, yes you are right, but:
we are part of one of largest german companies and the politics are
partly more important than common sense. In case someone someday
questions the decision it would be easier to find a legatimation this
way. Don't aks me why :-)
After all I find it most important to have the jars this way as not to
have them at all :-)
>
> Michael.
>
leon
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: [OT] Question about licensing
Posted by Michael Jouravlev <jm...@gmail.com>.
The following post contains no value :-)
On 3/8/06, Leon Rosenberg <ro...@googlemail.com> wrote:
> For process reasons the source code of
> the libs will not be available
> The jars would be free for copy, modification, usage,
^^^^^^^^^^^^^
How can you allow modification without source code?
> This is because the company,
> which owns the code, has to make additional reporting to the
> headquarters in case they would publish the source code and ensure,
> that there are no comments in the source code, that contain
> non-disclosure information.
This is a really stupid reason ;-) I am curious is there a tool that
strips out comments from the source code? The code itself can be
easily reverse-engineered.
Michael.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: [OT] Question about licensing
Posted by Emmanouil Batsis <Em...@eurodyn.com>.
Hello Leon,
IMO the libraries have very little value without the source code being
available under an OS license. In my experience this view now also
applies in the corporate environment; managers want to stay away from
free binary packages since they cannot know how the code actually works
and what exactly it does. Another thing is that if you are using a free
binary package and stumble on a bug, there is no way to fix it.
Anyway, you cannot apply an open source lisense in a binary package with
no source ;-)
just my 0.25.
Manos
Leon Rosenberg wrote:
>I'm sorry for OT, but I am pretty stupid with legal stuff, and after
>carefully reading gnu und apache license packages I am as unknowing as
>I was before. Here my problem:
>
>I am trying to convince one of my customers to make some of the libs I
>wrote for him public available. For process reasons the source code of
>the libs will not be available, only the jars would be available and
>redistributeable. I thought publishing the jar under the LGPL would
>make it, but after reading http://www.gnu.org/licenses/lgpl.html I'm
>starting to doubt it.
>
>Since we must have many experts in licensing here, I think there is no
>better place to ask :-)
>
>The jars would be free for copy, modification, usage, all the gpl
>stuff, but not available in sourcecode. This is because the company,
>which owns the code, has to make additional reporting to the
>headquarters in case they would publish the source code and ensure,
>that there are no comments in the source code, that contain
>non-disclosure information. Publishing the jars only would be lot of
>easier for them, and the probability, that they would do it, is
>higher. So under which license do they need to publish the jars?
>
>Or is it something which can be achieved by a trick? Creating a dummy
>application which contains the jars and put the application under
>lgpl, therefore providing source code for the application, but no
>source code for the libs?
>
>any help is highly appreciated
>
>regards
>leon
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
>For additional commands, e-mail: user-help@struts.apache.org
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org
Re: [OT] Question about licensing
Posted by Leon Rosenberg <ro...@googlemail.com>.
Thanx Ted and Peter,
MIT will do, I will suggest it to the customer, and it is really VERY
brief and understandable :-)
Emmanouil:
>IMO the libraries have very little value without the source code being
>available under an OS license
Normally I would agree, but in this case the MIT license will give me
the opprotunity to create a product on top which would be then
opensource. The jar in question is a interval-stat-value framework,
the application above would be an interval-based
struts/servlet/whatever stats. We actually have one in usage right
now, and the results are magnificent. That's why I want to make an OS
project out of it, to use it in my other projects and to give the
community something back.
regards
Leon
On 3/8/06, Ted Husted <te...@gmail.com> wrote:
> If it were me, I'd probably suggest putting the binaries under the MIT license.
>
> * http://www.opensource.org/licenses/mit-license.php
>
> It talks about "software" but doesn't distinguish between source and
> object form.
>
> The MIT license also has the virtue of being brief and easy to understand :)
>
> Then, later, when there has been time to review and "sanitize" the
> source code, you would be able to include the source in the
> distribution under the same license.
>
> -Ted.
>
> On 3/8/06, Leon Rosenberg <ro...@googlemail.com> wrote:
> > I'm sorry for OT, but I am pretty stupid with legal stuff, and after
> > carefully reading gnu und apache license packages I am as unknowing as
> > I was before. Here my problem:
> >
> > I am trying to convince one of my customers to make some of the libs I
> > wrote for him public available. For process reasons the source code of
> > the libs will not be available, only the jars would be available and
> > redistributeable. I thought publishing the jar under the LGPL would
> > make it, but after reading http://www.gnu.org/licenses/lgpl.html I'm
> > starting to doubt it.
> >
> > Since we must have many experts in licensing here, I think there is no
> > better place to ask :-)
> >
> > The jars would be free for copy, modification, usage, all the gpl
> > stuff, but not available in sourcecode. This is because the company,
> > which owns the code, has to make additional reporting to the
> > headquarters in case they would publish the source code and ensure,
> > that there are no comments in the source code, that contain
> > non-disclosure information. Publishing the jars only would be lot of
> > easier for them, and the probability, that they would do it, is
> > higher. So under which license do they need to publish the jars?
> >
> > Or is it something which can be achieved by a trick? Creating a dummy
> > application which contains the jars and put the application under
> > lgpl, therefore providing source code for the application, but no
> > source code for the libs?
> >
> > any help is highly appreciated
> >
> > regards
> > leon
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
> > For additional commands, e-mail: user-help@struts.apache.org
> >
> >
>
>
> --
> HTH, Ted.
> ** http://www.husted.com/ted/blog/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
> For additional commands, e-mail: user-help@struts.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org
Re: [OT] Question about licensing
Posted by Leon Rosenberg <ro...@googlemail.com>.
Thanx Ted and Peter,
MIT will do, I will suggest it to the customer, and it is really VERY
brief and understandable :-)
Emmanouil:
>IMO the libraries have very little value without the source code being
>available under an OS license
Normally I would agree, but in this case the MIT license will give me
the opprotunity to create a product on top which would be then
opensource. The jar in question is a interval-stat-value framework,
the application above would be an interval-based
struts/servlet/whatever stats. We actually have one in usage right
now, and the results are magnificent. That's why I want to make an OS
project out of it, to use it in my other projects and to give the
community something back.
regards
Leon
On 3/8/06, Ted Husted <te...@gmail.com> wrote:
> If it were me, I'd probably suggest putting the binaries under the MIT license.
>
> * http://www.opensource.org/licenses/mit-license.php
>
> It talks about "software" but doesn't distinguish between source and
> object form.
>
> The MIT license also has the virtue of being brief and easy to understand :)
>
> Then, later, when there has been time to review and "sanitize" the
> source code, you would be able to include the source in the
> distribution under the same license.
>
> -Ted.
>
> On 3/8/06, Leon Rosenberg <ro...@googlemail.com> wrote:
> > I'm sorry for OT, but I am pretty stupid with legal stuff, and after
> > carefully reading gnu und apache license packages I am as unknowing as
> > I was before. Here my problem:
> >
> > I am trying to convince one of my customers to make some of the libs I
> > wrote for him public available. For process reasons the source code of
> > the libs will not be available, only the jars would be available and
> > redistributeable. I thought publishing the jar under the LGPL would
> > make it, but after reading http://www.gnu.org/licenses/lgpl.html I'm
> > starting to doubt it.
> >
> > Since we must have many experts in licensing here, I think there is no
> > better place to ask :-)
> >
> > The jars would be free for copy, modification, usage, all the gpl
> > stuff, but not available in sourcecode. This is because the company,
> > which owns the code, has to make additional reporting to the
> > headquarters in case they would publish the source code and ensure,
> > that there are no comments in the source code, that contain
> > non-disclosure information. Publishing the jars only would be lot of
> > easier for them, and the probability, that they would do it, is
> > higher. So under which license do they need to publish the jars?
> >
> > Or is it something which can be achieved by a trick? Creating a dummy
> > application which contains the jars and put the application under
> > lgpl, therefore providing source code for the application, but no
> > source code for the libs?
> >
> > any help is highly appreciated
> >
> > regards
> > leon
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
> > For additional commands, e-mail: user-help@struts.apache.org
> >
> >
>
>
> --
> HTH, Ted.
> ** http://www.husted.com/ted/blog/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
> For additional commands, e-mail: user-help@struts.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: [OT] Question about licensing
Posted by Ted Husted <te...@gmail.com>.
If it were me, I'd probably suggest putting the binaries under the MIT license.
* http://www.opensource.org/licenses/mit-license.php
It talks about "software" but doesn't distinguish between source and
object form.
The MIT license also has the virtue of being brief and easy to understand :)
Then, later, when there has been time to review and "sanitize" the
source code, you would be able to include the source in the
distribution under the same license.
-Ted.
On 3/8/06, Leon Rosenberg <ro...@googlemail.com> wrote:
> I'm sorry for OT, but I am pretty stupid with legal stuff, and after
> carefully reading gnu und apache license packages I am as unknowing as
> I was before. Here my problem:
>
> I am trying to convince one of my customers to make some of the libs I
> wrote for him public available. For process reasons the source code of
> the libs will not be available, only the jars would be available and
> redistributeable. I thought publishing the jar under the LGPL would
> make it, but after reading http://www.gnu.org/licenses/lgpl.html I'm
> starting to doubt it.
>
> Since we must have many experts in licensing here, I think there is no
> better place to ask :-)
>
> The jars would be free for copy, modification, usage, all the gpl
> stuff, but not available in sourcecode. This is because the company,
> which owns the code, has to make additional reporting to the
> headquarters in case they would publish the source code and ensure,
> that there are no comments in the source code, that contain
> non-disclosure information. Publishing the jars only would be lot of
> easier for them, and the probability, that they would do it, is
> higher. So under which license do they need to publish the jars?
>
> Or is it something which can be achieved by a trick? Creating a dummy
> application which contains the jars and put the application under
> lgpl, therefore providing source code for the application, but no
> source code for the libs?
>
> any help is highly appreciated
>
> regards
> leon
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
> For additional commands, e-mail: user-help@struts.apache.org
>
>
--
HTH, Ted.
** http://www.husted.com/ted/blog/
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org