7 ms·
Enterpriseification
- nathanaldensr 8y agoHoly cow, what a rambling mess this blog article is. Perhaps I'm just tired after a long, arduous day negotiating corporate life. Does anyone know what the author is trying to say?
- lokedhs 8y agoThe last sentence is ironic. Given the amount of effort it took to just barely understand what he's selling, I'd say he has some work to do if he wants people to buy into his idea.
- kemitchell 8y agoThe author does!
- deleted 8y ago[deleted]
- userbinator 8y agoReading the article gives me the same feeling as trying to understand typical highly overabstracted "enterprisey" code, which seems rather fitting given the title.
- jevgeni 8y agoI had a lot of trouble understanding it as well. I also don't find speaking about organizational questions in overly software engineering terms any good. "It's rather coupling than an adapter." No, just say that the sponsor would try to influence your OSS organization according to their interests. Damn.
- Aeolun 8y agoDid anyone elseo reado that as a blogo posto?
- Aeolun 8y agoI guess not then. The arrow icons after every link make it really hard (funky?) to read.
- sciurus 8y agoThis post makes more sense if you know what license zero is. > License Zero is a new way to support open software developers. Contributors can choose from two new licenses, Parity and Prosperity, that make their work free for not-for-profit or open-source users, then sell private licenses to other devs who want to use for profit or in closed source. Everything happens through a simple, dev-friendly interface. https://licensezero.com/ https://licensezero.com/
- nickpsecurity 8y agoI'll add a blog post that describes his thinking and main licenses pretty well: https://blog.licensezero.com/2018/10/26/no-other-terms.html https://blog.licensezero.com/2018/10/26/no-other-terms.html
- vortico 8y agoThe name "license zero" might be a bit too close to the CC0 license. Maybe a rename might be a good idea? It also doesn't describe the license accurately.
- kemitchell 8y agoThe project’s been going for a while now, and I haven’t heard of anyone confusing License Zero, or one of the public licenses it stewards, for CC0. I called the project “License Zero” to reference its impossible goal: reduce the marginal cost of dual licensing, over simply receiving a public license, to zero.
- filesystemdude 8y agoTo be absolutely clear, neither of these "License Zero" licenses are open source or open source compatible in any way whatsoever. Both explicitly violate the first principle of the Open Source Definition (https://opensource.org/osd-annotated https://opensource.org/osd-annotated), free redistribution. We have the open source licenses we do for a reason. They've been vetted. They work. They meet established criteria. It's okay to consider new ones, but the process for that isn't just to make something up and hope it works. Amateurs have no more business playing lawyer and writing general-purpose software licenses than they do playing doctor and handing out surgical advice. It's not thought-provoking, it's dangerous and harmful to people who don't understand why licenses like this could cause them huge unmitigated legal headaches down the road.
- feross 8y ago> Amateurs have no more business playing lawyer and writing general-purpose software licenses than they do playing doctor and handing out surgical advice. It’s worth noting that the creator of License Zero is in fact an actual lawyer. And he has been working on open source license issues (and blogging about it excellently) for many years.
- dragonwriter 8y ago> To be absolutely clear, neither of these "License Zero" licenses are open source or open source compatible in any way whatsoever. Which may be why the author coins the misleading, sound-alike marketing term “open software”. Though I’m not really sure what, if anything, the point of that long, meandering, piece was. It occasionally seemed like it might be circling in on making a clear point, butnthent drifted off in another direction.
- kemitchell 8y agoI neither coined “open software”, nor do I think it misleading. Quite the contrary. Until the recent release of the Blue Oak Model license, with which I was also involved, I don’t think there had been a legally rigorous license as easy for non-lawyers to read and apply than Parity.
- deleted 8y ago[deleted]
- jacques_chester 8y agoI work for an OSS enterprise software vendor which competes with other OSS enterprise software vendors. The characterisation that license indemnity is the bulk of our value added is, putting it mildly, an incomplete one.
- kemitchell 8y agoIf I implied as much, could you mention where in the post? The table under scope specifically addresses differences in licensing expectations, rather than related services like maintenance, support, training, and integration. The string of questions under Scope mention the call for a broader, vendor relationship behind the code. I mention that Tidelift layers on maintenance assurances, aside from the license. This post is inside baseball, and I’m surprised to see it on the front page of HN. But I’d like to make it clearer if I can.
- jacques_chester 8y agoThe string of questions under Scope are themselves scoped to a particular subset of what enterprises require from vendors. Compliance and legal assurance are part of the value. But they are not the whole of what enterprise vendors do. Big companies have needs that no casual OSS contributor would need to scratch.
- Terretta 8y agoCommenting unofficially as an open source fan inside a globally giant enterprise, your post (a) made sense, (b) was circulated to folks much less familiar with these concerns. The table was particularly helpful, and at least this global enterprise is well aware of all the other nonsense it didn’t cover. I would have found adding those to the table to lessen your focused point about license openness and pitfalls vs. need of the ecosystem to be sustainable.
- kemitchell 8y agoI suppose I might have listed "form a company to commercialize" as one of the approaches, and tagged it as the one with greatest flexibility to add more offerings on top of license rights. I think License Zero, Tidelift, and other "sustainability as a service" offerings exist largely because the overhead of company-based commercialization is so high, and it doesn't scale well down to very small open source projects.