View unanswered posts | View active topics It is currently Fri Jun 23, 2017 7:52 am



Reply to topic  [ 4 posts ] 
GPL vs MIT and copyright ownership requirement 
Author Message
1N4001 - Signed up
User avatar

Joined: Tue Jun 10, 2008 5:17 pm
Posts: 1607
HotCat wrote:
Does that means GPL is more restricted than MIT?
This depends on who you ask, and what your goals are. GPL people like to poo poo MIT by claiming it has weak copyleft, while MIT people like to poo poo GPL by claiming it's viral.

In my opinion, MIT is less restricting and therefore more open. However, GPL's viral effect, means that newly contributed code has to also be open, so it's more force full of the open theory, and therefor more open, even though you have a pinch less freedom with the code. Shrug, it really don't matter that much for me.

My primary concerns with an Open license is very clearly noted in MIT. It specifies that you can use my code with out worrying about me claiming you stole my code or taking actions to pursue you. It also specifies that I offer it with no warranty, or liability, so you can't pursue me if something goes wrong and costs you hardship. Those are the critical components in almost any Open license.

GPL intends to protect IP rights from the developer. So they require a history of the developers. I have a mild objection about this tracking mechanism. I don't have any expectations that the open code or files I release will benefit me by putting food in my mouth, or anything of any real tangible consequence. So I see no personal benefit to me of having that tracking mechanism. However there is a mild chance that it opens me to liability issues. For example, if you use my files to build something then you do something mean/bad with it, there have been times when our legal systems come after an enabler. When that happens, they don't care that I specified that I'm not liable. I don't think it's very likely with an EMS, but perhaps it could be an issue, if one of the big MFG's felt this type of project was a threat to their business model.

Most of this also only applies to software, as hardware is covered by a completely different set of laws and regulations. The strongest protections for hardware/mfg controls are patents. The KICAD files I've released are software so this licensing applies, however the hardware they make is covered by a completely different set of rules.

Any how, enough of this garbage, especially if your in china where your culture doesn't toss you in jail for these reasons. Keep up the dev work, that's much more valuable time.


Sun Oct 09, 2011 12:56 pm
Profile
Moderator
User avatar

Joined: Tue Jan 15, 2008 2:31 pm
Posts: 14621
Location: Home sweet home!
Actually, Jared, in order for you to license work out to others, you MUST be the copyright holder, thus MIT doesn't free you from that. The only thing that does is putting it in the "public domain". Another way is copyright assignment to someone else who then distributes it for you on your behalf. This has a lot of advantages and some disadvantages too.

_________________
DIYEFI.org - where Open Source means Open Source, and Free means Freedom
FreeEMS.org - the open source engine management system
FreeEMS dev diary and its comments thread and my turbo truck!
n00bs, do NOT PM or email tech questions! Use the forum!
The ever growing list of FreeEMS success stories!


Sun Oct 09, 2011 5:22 pm
Profile WWW
1N4001 - Signed up
User avatar

Joined: Tue Jun 10, 2008 5:17 pm
Posts: 1607
HotCat wrote:
So I think GPL license is fit, is that right?
It sounds like any open licence will work for you, as you appear to be looking for the basics that allow people to participate and contribute to your project. GPL can work, but you already have the hardware version of GPL in the licence folder, so I'd recommend just keep it TAPR and you're golden. The key constraint with that licence, is that you can't remove references to a contributors work. In your case it appears you started from scratch, as you removed the original source components, so you don't have to worry about maintaining references to original contributors. Also Marco's and I, didn't put in those references, so you don't have to worry about removing those references, even if you used work sourced by either of us.

If you want to keep some rights, you'll need to add some notes, typically at the top of a source file. That's a bit harder to do with files like the KICAD files, but I don't think you're concerned with keeping rights, so don't worry about it. Leaving the TAPR licence in the folder will tell people your intent, such that they can contribute if they would like.


Mon Oct 10, 2011 11:25 am
Profile
Moderator
User avatar

Joined: Tue Jan 15, 2008 2:31 pm
Posts: 14621
Location: Home sweet home!
Jared, I said no more license talk in that thread, don't be disrespectful. Furthermore, HotCat's requirement was:

Quote:
I don't expect to earn money by claiming FreeEMS as proprietary project and won't let otherone to do it.

Which implies that BSD, Apache, MIT, and others are out of the question for him. So your statement "It sounds like any open licence will work for you" is quite simply false.

_________________
DIYEFI.org - where Open Source means Open Source, and Free means Freedom
FreeEMS.org - the open source engine management system
FreeEMS dev diary and its comments thread and my turbo truck!
n00bs, do NOT PM or email tech questions! Use the forum!
The ever growing list of FreeEMS success stories!


Mon Oct 10, 2011 11:37 am
Profile WWW
Display posts from previous:  Sort by  
Reply to topic   [ 4 posts ] 

Who is online

Users browsing this forum: No registered users and 1 guest


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Group
Designed by ST Software for PTF. ColorizeIt.