News for hackers. Stuff that matters.
Re:The Next Chapter in Swift Build Technologies by caspper69 on Saturday February 01, 2025 @04:57PM (#42902792)
Rotor was BSD licensed, so I suppose if that’s your definition of a not very open license…
Re:The Next Chapter in Swift Build Technologies by dcrazy on Saturday February 01, 2025 @05:25PM (#42903070)
Was it originally BSD-licensed, or did it start out as the MS Public Source License or whatever it was called?

We could go back and check on Codeplex… oh wait.

Re:The Next Chapter in Swift Build Technologies by caspper69 on Sunday February 02, 2025 @02:36PM (#42911096)
As a sibling poster updated it was some bastardized shared source license that never caught on.

Thank goodness MS got over their allergy to open source licenses, as they seem to prefer MIT nowadays for their releases.

My apologies for misremembering the details and being snarky. Humble pie eaten and enjoyed. :)

Re:The Next Chapter in Swift Build Technologies by tamlin on Tuesday February 04, 2025 @11:49AM (#42934945)
No worries, and no humble pie required. Peace, good happiness.
Re:The Next Chapter in Swift Build Technologies by tamlin on Sunday February 02, 2025 @04:11AM (#42907371)
Rotor had it's own license:

https://en.wikipedia.org/wiki/Shared_Source_Common_Language_...

I have various snapshots of the Rotor 1 and 2 sources around and they have the SSCLI license. There is a file that contains BSD licensed code (pal\rotor_pal.h).

Re:The Next Chapter in Swift Build Technologies by caspper69 on Sunday February 02, 2025 @02:34PM (#42911075)
Thank you for the follow up. You know after I posted that my thought was am I mistaking their BSD release for a BSD license, and of course I was. The memory isn’t what it used to be.