[sip-comm-dev] Different license for ui


#1

Just a thought - for those that want to embed the communicator, it would be very useful if the ui package of were under a more liberal license. For instance, an embedder would want to retain the majority of the ui code but maybe change the way various popups occur, etc. I think trying to implement a number of factories to deal with this will never really cover all of the corners.

What do you think?

Cheers
Nick

···

_________________________________________________________________
On the road to retirement? Check out MSN Life Events for advice on how to get there! http://lifeevents.msn.com/category.aspx?cid=Retirement

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#2

Hello Nick,

I don't see why would this be a problem for an embedder. If they are to
only change minor problems in the UI why would it bother them to open
the code? What damage is that going to cause? I can't think of any.

We, on the other hand could benefit from any bug fixes that the embedder
brings public.

Emil

buzz lightyear wrote:

···

Just a thought - for those that want to embed the communicator, it
would be very useful if the ui package of were under a more liberal
license. For instance, an embedder would want to retain the majority
of the ui code but maybe change the way various popups occur, etc. I
think trying to implement a number of factories to deal with this
will never really cover all of the corners.

What do you think?

Cheers Nick

_________________________________________________________________ On
the road to retirement? Check out MSN Life Events for advice on how
to get there! http://lifeevents.msn.com/category.aspx?cid=Retirement

---------------------------------------------------------------------
To unsubscribe, e-mail:
dev-unsubscribe@sip-communicator.dev.java.net For additional
commands, e-mail: dev-help@sip-communicator.dev.java.net


#3

Hi Emil

Actually, I'm not thinking about an embedder hiding any coding he/she has done, or finding bugs etc. I'm thinking about an embedder trying to massage the ui code to suit his/her application. With LGLP the embedder would always have to ensure that the source was also packaged too, which is of little interest to anyone else and simply inflates the library.

Yes, I overlooked the fact that bugs may come to light - guess this is always up to the embedder to report them.

Nick

···

From: Emil Ivov <emil.ivov@gmail.com>
Reply-To: dev@sip-communicator.dev.java.net
To: dev@sip-communicator.dev.java.net
Subject: Re: [sip-comm-dev] Different license for ui
Date: Mon, 08 May 2006 13:12:17 +0200

Hello Nick,

I don't see why would this be a problem for an embedder. If they are to
only change minor problems in the UI why would it bother them to open
the code? What damage is that going to cause? I can't think of any.

We, on the other hand could benefit from any bug fixes that the embedder
brings public.

Emil

buzz lightyear wrote:

Just a thought - for those that want to embed the communicator, it
would be very useful if the ui package of were under a more liberal
license. For instance, an embedder would want to retain the majority
of the ui code but maybe change the way various popups occur, etc. I
think trying to implement a number of factories to deal with this
will never really cover all of the corners.

What do you think?

Cheers Nick

_________________________________________________________________ On
the road to retirement? Check out MSN Life Events for advice on how
to get there! http://lifeevents.msn.com/category.aspx?cid=Retirement

---------------------------------------------------------------------
To unsubscribe, e-mail:
dev-unsubscribe@sip-communicator.dev.java.net For additional
commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

_________________________________________________________________
The new MSN Search Toolbar now includes Desktop search! http://join.msn.com/toolbar/overview

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#4

Nick,

I am no lawyer indeed but I still can't see the problem.

buzz lightyear wrote:

Actually, I'm not thinking about an embedder hiding any coding he/she
has done, or finding bugs etc. I'm thinking about an embedder trying
to massage the ui code to suit his/her application. With LGLP the embedder would always have to ensure that the source was also packaged too, which is of little interest to anyone else and simply inflates the library.

They don't really need to ensure this. They simply need to release their
modified UI bundle under an open source license. This comes down to
zipping it and making it available over the web together with a license
txt. That's why I am saying that I have trouble seeing why this is a
problem. If changes were minor then chances are that there aren't any
trade secrets in the code and therefore nothing to hide from the
competition.

In the case of a complete rewrite of the UI bundle, that didn't have
anything to do with the original code and that might include trade
secrets or privately developed technologies, then there is no obligation
to release the code since the embedder would be simply linking their own
code to the rest of the application which is perfectly ok with
the LGPL.

Emil

···

Yes, I overlooked the fact that bugs may come to light - guess this is always up to the embedder to report them.

Nick

From: Emil Ivov <emil.ivov@gmail.com> Reply-To: dev@sip-communicator.dev.java.net To: dev@sip-communicator.dev.java.net Subject: Re: [sip-comm-dev] Different license for ui Date: Mon, 08 May 2006 13:12:17 +0200

Hello Nick,

I don't see why would this be a problem for an embedder. If they are to only change minor problems in the UI why would it bother them to open the code? What damage is that going to cause? I can't
think of any.

We, on the other hand could benefit from any bug fixes that the embedder brings public.

Emil

buzz lightyear wrote:

Just a thought - for those that want to embed the communicator, it would be very useful if the ui package of were under a more liberal license. For instance, an embedder would want to retain the majority of the ui code but maybe change the way various popups occur, etc. I think trying to implement a number of factories to deal with this will never really cover all of the corners.

What do you think?

Cheers Nick

_________________________________________________________________
On the road to retirement? Check out MSN Life Events for advice
on how to get there! http://lifeevents.msn.com/category.aspx?cid=Retirement

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

_________________________________________________________________ The
new MSN Search Toolbar now includes Desktop search! http://join.msn.com/toolbar/overview

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net For additional commands, e-mail: dev-help@sip-communicator.dev.java.net