EBo wrote: > On Jun 8 2013 11:45 AM, Jon Elson wrote: > >> GROAN! What a way to wreck a nice Saturday afternoon! >> > > I liked Matt's suggestion to set up a clean slate and slowly migrate > over. I'm not sure such a drastic method is required, but I'm pretty far from this problem, so it may in fact be the best way to handle it. > The brass tax of the matter is that there are some people you > will never be able to find, and others who are vehemently opposed to > relicensing their code. You are simply going to have to replace it. Yes, I can see that, but it may be real hard to do a black box conversion of the disputed code with our organization. Since all the code is open now, it would be hard to recreate it without some taint of the original code. I know big organizations do stuff like this. > So > while you have to do a little of that anyway, this would be good time > to start the LinuxCNC-3.0 design and work through what worked and did > not for v2. There is also the issue that people are spending so much > time and energy thrashing over this that you could probably have > replaced the worst of the offenders already. Anyway, that's my 2c. > I'll probably catch hell for speaking up, but .... > > Oh, just to be clear, if you did something like this the first thing to > do would be to choose a license. I've already heard (L)GPL2+ mentioned. > I would suggest that being the very first discussion at the meeting. > I think that is the MAIN problem here, as the disputed code is (I think) quite small. Several contributors have specific (and incompatible) GPL's they want to be used, and so a consensus may be hard to come to. I hope it really isn't that bad, but this mess has been bouncing around for a couple years, I think, with no real light showing up. I know NOTHING about the details and differences between all these GPLs, I just get bogged down in all that verbiage.
Jon ------------------------------------------------------------------------------ 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
