Did you add something that I missed? Or just accidently hit send?

 

--

Chad Z. Hower aka Kudzu

"Programming is an art form that fights back"

http://www.KudzuWorld.com/

http://www.Woo-Hoo.net/

http://www.DelphiToDotNet.com/

 

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bruce
Sent: Friday, August 31, 2007 1:31 PM
To: sharpos-developers@lists.sourceforge.net
Subject: Re: [SharpOS Developers] License again

 

 

On 8/30/07, Chad Z. Hower aka Kudzu <[EMAIL PROTECTED]> wrote:

> X11 is close to BSD, I think you are right about themaindifference
> being the credit elsewhere. I think BSD dropped the requirment of
> credit in advertising, but still requires credit on program startup. 
> I am not an expert on liceses, so I don't keep track of the details.

Actually BSD doesn't say where... it just says "must credit". When people
asked us on Indy, we told them we would trust them to make the best judgment

where to credit, but that we suggested the about box and/or credits section
in the docs.

I *really* love BSD as I think it gives proper credit yet is unrestrictive
and *promotes* adoption of the software. For me - that's one of the primary 
goals of the software is to "change the world" or at least change the
developers world. :)

So I guess I'd prefer BSD over X11, but I'd be perfectly fine with X11 as
well. i.e. no objections from me. 

MPL is another one that I've found useful. We didn't so much chose it for
Indy. When Borland decided to ship Indy, they had some legal issues
regarding requirements of their customers. So we added MPL to meet that 
after analyzing many license. Sine Indy was originally BSD - we basically
had a "right" to easily relicense it of sorts. Maybe there was a
technicality - but we credited it via BSD in the MPL... Plus the admin team 
approved it. Maybe there was still a small technicality.. dunno but everyone
seemed happy and most users contributed their code with no strings attached,
basically allowing the admin team to license it.



-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser. 
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
SharpOS-Developers mailing list
SharpOS-Developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sharpos-developers


Since the provisional decision-making board of SharpOS is still being
formed, the decision for this issue should be delayed by two weeks. This
will allow for potential developers to apply to be on the provisional
decision-making board, and then have time to discuss the issue before a
final vote is called. 

I'm not trying to kill the conversation. In fact, I'm suggesting that we
have a set time-frame to decide on this, in a way that satisfies most
contributors. Feel free to continue the discussion, because even if you
don't want to apply to have a vote, at least your opinions can be considered
by the decision-making body when the time comes. 

This issue alone should encourage people to have themselves listed as a
decision-making body member.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
SharpOS-Developers mailing list
SharpOS-Developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sharpos-developers

Reply via email to