I'm very new to the game, and I probably don't understand all the details and 
politics around this discussion, but:

I'm assuming the concern is over the potential over-restriction of GPL?  
Creative Commons seems to be the best route in terms of disentangling licensing 
complexity, and I feel like CC-BY (by attribution) or CC-BY-SA (sharealike) 
would make the most sense.  It doesn't make sense to restrict commercial use, 
because there are plenty of people who want to be able to use linuxcnc to 
control machines in commercial settings, or perhaps package and sell linuxcnc 
controls as a commercial endeavor.  Restricting commercial use somewhat 
invalidates linuxcnc's purpose, in my mind.  

-BY vs -SA comes down to whether we want to impose our licensing philosophy on 
derivative works.  -BY would allow people to create closed-source derivatives 
so long as it attributes linuxcnc for the original work, whereas -SA would 
require derivatives to share under a similar license.  My gut says sharealike 
is the right choice for ensuring that new technologies make it back to the 
community, but overzealous application of that mentality is what led to people 
wanting/needing to abandon GPL in the first place.

Ian


On Jun 9, 2013, at 2:28 PM, Chris Morley <chrisinnana...@hotmail.com> wrote:

> 
>> If we keep dragging feet, at some point we will have a crossover of returns: 
>> it will be easier to throw away the GPL2 code and baggage like NML and Tcl, 
>> and start with the relicensable core code and postwar supporting components. 
>> 
>> 
>> - Michael
>> 
> 
> Honestly I am tired of this issue popping up and us just talk about it.
> We don't need to talk about it anymore, we need a decision.
> 
> It again really comes done to what we want from this project.
> 
> if you are happy the way it is and don't mind it slowly dieing when
> current developers get busy in life and quit developing it, then leave it
> as it is. It will last a long time but become relatively stalemated.
> If we don't continue to bring in new people then it _WILL_ die eventually.
> 
> If you wish to make it easier to expand and bring in new people, new ideas,
> new technology then we must fix the licence issue.
> If we had started to do it when it first came up, it would be done be now ( I 
> bet )
> 
> So the decision number 1 is: do we fix the licence issue or will our project 
> by forked.
> cause I'm pretty sure that's what will happen.
> 
> decision # 2 is what licence.
> 
> These are the decisions that need to be made. Now. In an open format.
> I prefer maillists for course discussions and announcements.
> We need to set a rough date to make this decision.
> Actions seldom happen if there is no time limit.
> and we need to specify how will we come to this decision.
> the board? by vote? person X?
> 
> I don't really care if you have worked for ten years on this project or 
> started yesterday,
> if you have an informed opinion on those questions lets hear it.
> But we must stay focused and answer them. relatively soon.
> 
> And I don't think having a relatively closed door discussion about these 
> broad questions
> should be done in Wichita. Whichta would be great for figuring out the 
> details of HOW we
> will do what we have decided.
> 
> all IMHO.
> 
> Thanks
> Chris M
>                                         
> ------------------------------------------------------------------------------
> How ServiceNow helps IT people transform IT departments:
> 1. A cloud service to automate IT design, transition and operations
> 2. Dashboards that offer high-level views of enterprise services
> 3. A single system of record for all IT processes
> http://p.sf.net/sfu/servicenow-d2d-j
> _______________________________________________
> Emc-developers mailing list
> Emc-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-developers


------------------------------------------------------------------------------
How ServiceNow helps IT people transform IT departments:
1. A cloud service to automate IT design, transition and operations
2. Dashboards that offer high-level views of enterprise services
3. A single system of record for all IT processes
http://p.sf.net/sfu/servicenow-d2d-j
_______________________________________________
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Reply via email to