Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.c > #103874
| From | David Brown <david.brown@hesbynett.no> |
|---|---|
| Newsgroups | comp.lang.c |
| Subject | Re: project together? |
| Date | 2017-02-14 13:36 +0100 |
| Organization | A noiseless patient Spider |
| Message-ID | <o7utge$ase$1@dont-email.me> (permalink) |
| References | (7 earlier) <20170213115845.07a60e5a42f78287396f4261@gmail.com> <9967c88c-be8e-4fde-be97-6b9a93bd51c3@googlegroups.com> <20170214121133.9d99097b0f984ede42c6007e@gmail.com> <70185684-b1f2-40ca-96ec-412c996b28a3@googlegroups.com> <o7urg7$473$1@dont-email.me> |
On 14/02/17 13:01, BartC wrote: > On 14/02/2017 11:58, Malcolm McLean wrote: >> On Tuesday, February 14, 2017 at 11:13:33 AM UTC, GOTHIER Nathan wrote: > >>> Once more, there is no copyright or license notice in your files, >>> this can >>> prevent users to modify, copy or distribute your source files to >>> build their >>> program possibly open source. >>> >> I'm not lawyer. It's an open source project and will always be open >> source and >> free for the programming community to use. Oddly enough received a >> similar >> request about the tiff loader. It might be that I've got to put in >> some legalese >> from somewhere, but I'd prefer to avoid it - it comes over as immature. > > That's never worried me either. But it's possible that someone can copy > your code and put /their/ copyright notice on it. > Without any notice, you automatically own copyright on the code you write. But it can be far more difficult to enforce if someone does illegally add their own copyright claims to it. And people that care about open source, or care where they get their code, will not touch your code when there is no copyright and licensing information. So your code is /not/ free for the programming community to use - you need a bit of legalese to say so. It's not hard to copy-and-paste a BSD-style notice, or perhaps the Mozilla Public License would be best suited for such code (basically that says that the programmer can mix the code freely with other code under any license, but any changes they make to /your/ code need to be made available as source. Use the code as you want, but share any improvements or bug-fixes).
Back to comp.lang.c | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
project together? fir <profesor.fir@gmail.com> - 2017-02-09 10:16 -0800
Re: project together? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2017-02-09 18:28 +0000
Re: project together? fir <profesor.fir@gmail.com> - 2017-02-09 10:45 -0800
Re: project together? gazelle@shell.xmission.com (Kenny McCormack) - 2017-02-09 20:04 +0000
Re: project together? David Brown <david.brown@hesbynett.no> - 2017-02-09 21:30 +0100
Re: project together? fir <profesor.fir@gmail.com> - 2017-02-09 12:43 -0800
Re: project together? mark.bluemel@gmail.com - 2017-02-10 00:47 -0800
Re: project together? fir <profesor.fir@gmail.com> - 2017-02-10 00:57 -0800
Re: project together? fir <profesor.fir@gmail.com> - 2017-02-10 07:17 -0800
Re: project together? fir <profesor.fir@gmail.com> - 2017-02-11 04:24 -0800
Re: project together? David Brown <david.brown@hesbynett.no> - 2017-02-13 10:31 +0100
Re: project together? Ian Collins <ian-news@hotmail.com> - 2017-02-11 19:08 +1300
Re: project together? "James R. Kuyper" <jameskuyper@verizon.net> - 2017-02-11 10:02 -0500
Re: project together? David Brown <david.brown@hesbynett.no> - 2017-02-13 10:34 +0100
Re: project together? "James R. Kuyper" <jameskuyper@verizon.net> - 2017-02-13 10:24 -0500
Re: project together? "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2017-02-09 10:46 -0800
Re: project together? fir <profesor.fir@gmail.com> - 2017-02-09 11:06 -0800
Re: project together? fir <profesor.fir@gmail.com> - 2017-02-09 12:06 -0800
Re: project together? fir <profesor.fir@gmail.com> - 2017-02-09 12:18 -0800
Re: project together? Malcolm McLean <malcolm.mclean5@btinternet.com> - 2017-02-09 21:57 -0800
Re: project together? fir <profesor.fir@gmail.com> - 2017-02-10 00:48 -0800
Re: project together? Malcolm McLean <malcolm.mclean5@btinternet.com> - 2017-02-10 02:52 -0800
Re: project together? fir <profesor.fir@gmail.com> - 2017-02-10 06:47 -0800
Re: project together? fir <profesor.fir@gmail.com> - 2017-02-10 07:12 -0800
Re: project together? David Brown <david.brown@hesbynett.no> - 2017-02-13 10:39 +0100
Re: project together? Malcolm McLean <malcolm.mclean5@btinternet.com> - 2017-02-13 02:32 -0800
Re: project together? GOTHIER Nathan <nathan.gothier@gmail.com> - 2017-02-13 11:58 +0100
Re: project together? Malcolm McLean <malcolm.mclean5@btinternet.com> - 2017-02-13 05:39 -0800
Re: project together? GOTHIER Nathan <nathan.gothier@gmail.com> - 2017-02-14 12:11 +0100
Re: project together? Malcolm McLean <malcolm.mclean5@btinternet.com> - 2017-02-14 03:58 -0800
Re: project together? BartC <bc@freeuk.com> - 2017-02-14 12:01 +0000
Re: project together? David Brown <david.brown@hesbynett.no> - 2017-02-14 13:36 +0100
Making things open source requires copyright notices; it's the world we live in (Was: project together?) gazelle@shell.xmission.com (Kenny McCormack) - 2017-02-14 12:46 +0000
Re: project together? GOTHIER Nathan <nathan.gothier@gmail.com> - 2017-02-14 14:24 +0100
Re: project together? raltbos@xs4all.nl (Richard Bos) - 2017-02-15 21:07 +0000
Re: project together? "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2017-02-09 12:48 -0800
Re: project together? fir <profesor.fir@gmail.com> - 2017-02-09 13:04 -0800
Re: project together? void <nathan.gothier@gmail.com> - 2017-02-10 20:00 -0800
Re: project together? fir <profesor.fir@gmail.com> - 2017-02-11 01:18 -0800
Re: project together? fir <profesor.fir@gmail.com> - 2017-02-11 02:20 -0800
Re: project together? fir <profesor.fir@gmail.com> - 2017-02-11 03:31 -0800
Re: project together? void <nathan.gothier@gmail.com> - 2017-02-11 02:48 -0800
Re: project together? fir <profesor.fir@gmail.com> - 2017-02-11 03:16 -0800
Re: project together? fir <profesor.fir@gmail.com> - 2017-02-11 03:40 -0800
csiph-web