Forget the library .. time to open-source the code? (Announce)
> There is no easy answer. I don't see any harm in posting sources, esp. if
> you don't intend to continue development. (For instance, ADOM doesn't want
> secrets spoiled or too many forks a la Angband, hence why it's still
> closed.)
I fully expect to continue development, so having the code forked is a concern for me. But I realize that giving people only binaries to work with might not be satisfying, and certainly doesn't allow anybody to help improve the quality of the code.
> > I would like to open source it but retain my personal copyright. I
> think
> > that the GPL version three allows for this.
>
> Not sure what you mean by this. You are always retaining copyright, but
> with GPL you are letting people use your code in any fashion as long as
> they don't publicly distribute it without (all total) sources. (GPLv3
> combines GPLv2 and LGPL 2.1 into one license, or so I'm told.)
My intent here is to ensure that I can always do what I want with my code, and the original version is recognized as something that came from my brain. 
> > I realize that some people
> > might use the code in a way that might be irritating to me, but there
> is
> > probably more benefit in making it open than not.
>
> In what way? What are you afraid of happening? Both GPLv2 and v3 actually
> allow others to commercially sell your code. What do you want to happen to
> it?
GPL2 and GPL3 allow for commercial use, but you still have to distribute the source code. I would prefer that the code was marked "for hobbyist use only" because I really am not thrilled about people making money off of my hobby time, but I doubt there is much I can do about that. (Then again, a new DOS TCP/IP stack is not going to have a lot of commercial value.)
> > What licenses have people here used for their software? Have their
> been
> > any 'gotchas'? (I am very familiar with open source software, but have
> > never tried to maintain my own project.)
>
> FYI, the GPLv3 is heavily shunned by *BSD and its fans (although I don't
> know why). They stick to GCC 4.2.1 or less (and want Clang or PCC to
> succeed) due to that. But most main GNU projects themselves are GPLv3 now.
> Even FreeDOS proper has a heavy GPL bias, esp. for "BASE".
>
> Personally, I think worrying about licenses is a waste of time. But it's
> your call.
I think the license matters quite a bit. BSD style licenses bother me because the commercial users do not have to release their code. That goes against the nature of what I'm trying to do here, which is release the code for hobbyist use.
My employer is going to make me jump through hoops to release this code, which is another concern. (They want to ensure that anybody who is contributing to open source is not exposing their intellectual property. I'm quite sure my code is safe, but I will have to have it reviewed.)
Mike
---
mTCP - TCP/IP apps for vintage DOS machines!
http://www.brutman.com/mTCP
Complete thread:
- mTCP DOS TCP/IP apps for small machines - mbbrutman, 21.01.2010, 18:06
![Open in board view [Board]](img/board_d.gif)
![Open in mix view [Mix]](img/mix_d.gif)
- mTCP DOS TCP/IP apps for small machines - Japheth, 22.01.2010, 09:47
- mTCP DOS TCP/IP apps for small machines - mbbrutman, 22.01.2010, 16:56
- mTCP DOS TCP/IP apps for small machines - mbbrutman, 07.02.2010, 16:35
- Forget the library .. time to open-source the code? - mbbrutman, 14.03.2010, 03:22
- Forget the library .. time to open-source the code? - Rugxulo, 14.03.2010, 03:56
- Forget the library .. time to open-source the code? - mbbrutman, 14.03.2010, 15:01
- mTCP new release 27/June/2010 - now ported to Open Watcom - Arjay, 27.06.2010, 22:27
- mTCP new release 27/June/2010 - now ported to Open Watcom - Rugxulo, 28.06.2010, 06:30
- mTCP new release 27/June/2010 - now ported to Open Watcom - DOS386, 28.06.2010, 12:05
- mTCP new release 27/June/2010 - now ported to Open Watcom - Arjay, 28.06.2010, 14:22
- mTCP new release 27/June/2010 - now ported to Open Watcom - mbbrutman, 01.07.2010, 07:08
- mTCP new release 27/June/2010 - now ported to Open Watcom - Laaca, 01.07.2010, 13:14
- mTCP new release 27/June/2010 - now ported to Open Watcom - mbbrutman, 01.07.2010, 16:06
- mTCP new release 27/June/2010 - now ported to Open Watcom - DOS386, 01.07.2010, 13:20
- mTCP new release 27/June/2010 - now ported to Open Watcom - mbbrutman, 01.07.2010, 16:03
- mTCP new release 27/June/2010 - now ported to Open Watcom - Laaca, 01.07.2010, 19:16
- mTCP new release 27/June/2010 - now ported to Open Watcom - mbbrutman, 03.07.2010, 16:04
- mTCP new release 27/June/2010 - now ported to Open Watcom - DOS386, 14.07.2010, 03:51
- mTCP new release 27/June/2010 - now ported to Open Watcom - Laaca, 01.07.2010, 19:16
- mTCP new release 27/June/2010 - now ported to Open Watcom - mbbrutman, 01.07.2010, 16:03
- mTCP new release 27/June/2010 - now ported to Open Watcom - Laaca, 01.07.2010, 13:14
- mTCP new release 27/June/2010 - now ported to Open Watcom - mbbrutman, 01.07.2010, 07:08
- mTCP new release 27/June/2010 - now ported to Open Watcom - Arjay, 28.06.2010, 14:22
- mTCP new release 27/June/2010 - now ported to Open Watcom - DOS386, 28.06.2010, 12:05
- mTCP new release 27/June/2010 - now ported to Open Watcom - Rugxulo, 28.06.2010, 06:30
- mTCP new release 27/June/2010 - now ported to Open Watcom - Arjay, 27.06.2010, 22:27
- Forget the library .. time to open-source the code? - mbbrutman, 14.03.2010, 15:01
- Forget the library .. time to open-source the code? - Rugxulo, 14.03.2010, 03:56
- mTCP DOS TCP/IP apps for small machines - mbbrutman, 22.01.2010, 16:56
- mTCP interfacing with TINY remote control for DOS? - Arjay, 20.07.2010, 12:41
- mTCP interfacing with TINY remote control for DOS? - mbbrutman, 20.07.2010, 16:09
- mTCP interfacing with TINY remote control for DOS? - Arjay, 20.07.2010, 17:49
- mTCP interfacing with TINY remote control for DOS? - mbbrutman, 20.07.2010, 16:09
- mTCP DOS - NC documentation issue (design bug)? - Arjay, 20.07.2010, 14:07
- mTCP DOS - NC documentation issue (design bug)? - mbbrutman, 20.07.2010, 15:22
- mTCP DOS - NC documentation issue (design bug)? - Arjay, 20.07.2010, 17:30
- mTCP DOS - NC documentation issue (design bug)? - mbbrutman, 20.07.2010, 19:32
- mTCP DOS - NC documentation issue (design bug)? - Arjay, 20.07.2010, 21:56
- FTP ASCII vs binary "image" - DOS386, 23.07.2010, 07:27
- FTP ASCII vs binary "image" - mbbrutman, 24.07.2010, 01:04
- FTP ASCII vs binary "image" - DOS386, 24.07.2010, 12:12
- FTP ASCII vs binary "image" - Japheth, 24.07.2010, 15:31
- FTP ASCII vs binary "image" - DOS386, 24.07.2010, 15:36
- FTP ASCII vs binary "image" - mbbrutman, 24.07.2010, 16:23
- FTP ASCII vs binary "image" - Japheth, 24.07.2010, 16:57
- FTP ASCII vs binary "image" - mbbrutman, 25.07.2010, 01:35
- FTP ASCII vs binary "image" - Rugxulo, 25.07.2010, 05:34
- FTP ASCII vs binary "image" - DOS386, 25.07.2010, 06:16
- FTP ASCII vs binary "image" - mbbrutman, 25.07.2010, 17:17
- FTP ASCII vs binary "image" | NTLFN issues - DOS386, 26.07.2010, 02:03
- FTP ASCII vs binary "image" | NTLFN issues - mbbrutman, 26.07.2010, 03:11
- FTP ASCII vs binary "image" | NTLFN issues - DOS386, 27.07.2010, 02:53
- FTP ASCII vs binary "image" | NTLFN issues - mbbrutman, 27.07.2010, 03:31
- FTP ASCII vs binary "image" | NTLFN issues - DOS386, 27.07.2010, 03:40
- FTP ASCII vs binary "image" | NTLFN issues - mbbrutman, 27.07.2010, 03:31
- FTP ASCII vs binary "image" | NTLFN issues - DOS386, 27.07.2010, 02:53
- FTP ASCII vs binary "image" | NTLFN issues - mbbrutman, 26.07.2010, 03:11
- FTP ASCII vs binary "image" | NTLFN issues - DOS386, 26.07.2010, 02:03
- FTP ASCII vs binary "image" - mbbrutman, 25.07.2010, 17:17
- FTP ASCII vs binary "image" - DOS386, 25.07.2010, 06:16
- FTP ASCII vs binary "image" - Rugxulo, 25.07.2010, 05:34
- FTP ASCII vs binary "image" - mbbrutman, 25.07.2010, 01:35
- FTP ASCII vs binary "image" - Japheth, 24.07.2010, 16:57
- FTP ASCII vs binary "image" - Japheth, 24.07.2010, 15:31
- FTP ASCII vs binary "image" - DOS386, 24.07.2010, 12:12
- FTP ASCII vs binary "image" - mbbrutman, 24.07.2010, 01:04
- mTCP DOS - NC documentation issue (design bug)? - mbbrutman, 20.07.2010, 19:32
- mTCP DOS - NC documentation issue (design bug)? - Arjay, 20.07.2010, 17:30
- mTCP DOS - NC documentation issue (design bug)? - mbbrutman, 20.07.2010, 15:22
- mTCP DOS TCP/IP apps for small machines - Japheth, 22.01.2010, 09:47
Mix view