Re: [bme-develop] Development issues

[Simon T. <sim...@ga...>]

> Hi,
> 
> >For me the GPL is too restrictive. The LPGL is less-so, but still
> >fairly complicated.
> >
> GPL means that the software should be distribute freely, and that all 
> software that uses code from this program should also be distributed 
> under 
> gpl right=3F what's LGPL=3F

GPL stops people from taking the code for whatever purpose - and forces 
them to release whatever they write also under the GPL. That makes it 
harder for people like the IM Kit to take our code - as they'd be 
forced to use GPL too in that case. Designed to ensure the code stays 
free, but it doing that it restricts some of the freedoms IMHO.

LGPL is less restrictive (not quite sure why) - I think it allows 
LGPL'ed libraries to be used in non-LGPL software.

> >My choice would be MIT/BSD (I think that's how I registered the 
> > project
> >on sf, although it's no problem to change it). The license basically
> >says - "Here's the code, do anything you want with it, but don't sue 
> > us
> >if it doesn't work". The problem is it doesn't stop anyone taking 
> > all
> >of our code and selling it commercially. I really don't think that's
> >likely to happen with BeOS software though, so I'd go with the
> >simplicity of the MIT license.
> 
> But, I believe that MIT also says something about acknowledging the 
> makers 
> of the program!

Maybe, not sure.

The OBOS license says that it must be reproduced with any complete 
copies or substantial portions of the software, I guess that means 
credit must be given.

//---------------------------------------------------------------------
---------
//	Copyright (c) 2001-2003, OpenBeOS
//
//	Permission is hereby granted, free of charge, to any person 
obtaining a
//	copy of this software and associated documentation files (the 
"Software"),
//	to deal in the Software without restriction, including without 
limitation
//	the rights to use, copy, modify, merge, publish, distribute, 
sublicense,
//	and/or sell copies of the Software, and to permit persons to whom 
the
//	Software is furnished to do so, subject to the following 
conditions:
//
//	The above copyright notice and this permission notice shall be 
included in
//	all copies or substantial portions of the Software.
//
//	THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, 
EXPRESS OR
//	IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF 
MERCHANTABILITY,
//	FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT 
SHALL THE
//	AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR 
OTHER
//	LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, 
ARISING
//	FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
//	DEALINGS IN THE SOFTWARE.
//---------------------------------------------------------------------
---------

 
> >
> >I think we just need to add a comment at the top of each file. This 
> > is
> >from one of the OBOS files:
> >/*
> >** Copyright 2002-2003, Axel D=F6rfler, ax...@pi.... All
> >rights reserved.
> >** Distributed under the terms of the OpenBeOS License.
> >*/
> >
> 
> Ok hope that is everything....we have to be sure though

Is it really that crucial=3F

I don't see millions of people waiting to steal our code in case we 
choose the wrong license!

> >
> > > I will say for now to post their feedback in the forums. Let's 
> > > wait
> > > until we are a little more organized on the source, the cvs 
> > > server,
> > > license, and everything else. How about you, what do you think=3F
> >
> >I agree. Wait until we're a bit more organised.
> >
> Oke...told one tester already. Daniel one little remark....we have to 
> change 
> that....if you send a IM message you use "message" in the BMessage, 
> and if 
> you receive one you use "body"!
> 
> regards,
> 
> Tim

Simon