News for hackers. Stuff that matters.
Re:RoboVM Is No Longer Open-Source by nickpsecurity on Tuesday November 03, 2015 @01:48PM (#10501615)
"In an ideal world, I'd suggest doing so in a way that doesn't require a CLA, such as a carefully written license exception referencing an updatable list of licensees."

That's worth remembering if possible.

"If you actually meant "commercial use", such that the default version prohibited commercial use"

The idea is it's just like open-source software except you pay for it. People can fix it, modify it, contribute to it, whatever. Might force the mods to be shared with everyone if using free license or let them not be shared if people are paying for it. The money coming in creates active development. The license keeps them from closing things back up or pulling it off the market. Trying to figure out what terms maintain the major benefits of FOSS while preventing the worst parts of proprietary model and keeping money in for development/maintenance.

The philosophy is basically "you get what you pay for or contribute to," with source and benefits that brings. Sort of a middle ground between proprietary and FOSS. Gotta be one that could work but devil is in the details.

Note: Burroughs' 1960's OS, MCP, was delivered as source to paying customers. They could modify it as they saw fit and optionally submit modifications back. Burroughs would try to integrate good submissions into later releases. It was the first or one of the earliest proprietary and OSS combinations.

Re:RoboVM Is No Longer Open-Source by JoshTriplett on Wednesday November 04, 2015 @04:54PM (#10510070)
The problem is that FOSS already exists, and anything incompatible with FOSS isn't likely to gain traction among existing FOSS developers. It isn't a question of "which terms would maintain the major benefits of FOSS"; to get any traction, you need to actually be compatible with the Open Source Initiative's Open Source Definition (https://opensource.org/osd) and the Free Software Foundation's Free Software Definition (https://www.gnu.org/philosophy/free-sw.html). And neither of those allow a prohibition on commercial use.

Now, on the other hand, you could build a community around a GPLed project, or an AGPLed project, funded by selling licenses to use that project in proprietary software. In practice, that will have a very similar effect, while remaining FOSS. And your comments and ideas about using that licensing revenue to directly support the community rather than just a company sound quite appealing.