• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 252
  • Last Modified:

some code disclaimer for opensource use

Hi,

I wrote some code that I'd like to publish on my website. I'd like to allow people to use the code freely in whatever way they choose, but I'd want them to leave a header at the top of each source file intact - just basically so I get credit for writing it. Something like:

// MyFile.h
/*
Author: John Doe
Contact: johndoe@who.com
This software may be used for any purpose, so long as this original header is left intact.
Oh and you can't sue me if any of the code does something bad.
*/

I guess something like that. Is there any guideline on how to write that?

Thanks
0
DJ_AM_Juicebox
Asked:
DJ_AM_Juicebox
  • 3
  • 2
1 Solution
 
jkrCommented:
That's  a dificult issue - you might want to to take a look at http://en.wikipedia.org/wiki/Open_Source_Licenses prior to choosing a certain approach. In general, you still have to rely on the honesty of the people who use that code in the end.
0
 
peprCommented:
Have a look at the source code of doxygen (http://www.doxygen.org). Franky, I do not know the history and details of how the text was constructed (I am only one of the human-language maintainers). Anyway, you can try to ask the author for details. The initial comment in the sources looks like this:

/******************************************************************************
 *
 *
 *
 * Copyright (C) 1997-2007 by Dimitri van Heesch.
 *
 * Permission to use, copy, modify, and distribute this software and its
 * documentation under the terms of the GNU General Public License is hereby
 * granted. No representations are made about the suitability of this software
 * for any purpose. It is provided "as is" without express or implied warranty.
 * See the GNU General Public License for more details.
 *
 * Documents produced by Doxygen are derivative works derived from the
 * input used in their production; they are not affected by this license.
 *
 */
0
 
DJ_AM_JuiceboxAuthor Commented:
Yeah I just figure if someone wants to take it and use it and remove the credit disclaimer they're going to do it, but at least I can argue I had put it in there as some way to protect myself (instead of doing nothing). Let me check out those license types,

Thanks
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
DJ_AM_JuiceboxAuthor Commented:
ok I read through some of the licenses, the two I'm most familiar with are BSD and GPL. The big difference is that with BSD, people can freely use the code however they want, even in proprietary software.

If they use my code and I put a GPL license on it, then they pretty much cannot use it in proprietary software, unless they also attach the GPL license to it, which is probably pretty unlikely.

Is that accurate?

Thanks
0
 
jkrCommented:
Yes, that's on point. Me for myself have decided to abadon GPL > v2 - for the very reason that it has become to political for me to pursue that path any further. I don't like hardliners, in neither context.
0
 
DJ_AM_JuiceboxAuthor Commented:
yeah I understand,

Thanks
0

Featured Post

[Webinar] Cloud and Mobile-First Strategy

Maybe you’ve fully adopted the cloud since the beginning. Or maybe you started with on-prem resources but are pursuing a “cloud and mobile first” strategy. Getting to that end state has its challenges. Discover how to build out a 100% cloud and mobile IT strategy in this webinar.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now