19 ms·
Licenses alone do not govern behavior in open source
- breck 5y agoLicenses are for losers. Any half brain can figure out from first principles there can be no such thing as stealing ideas, and ideas are not property. Time to amend the U.S Constitution and liberate ideas and people. http://www.breckyunits.com/the-intellectual-freedom-amendment.html http://www.breckyunits.com/the-intellectual-freedom-amendmen...
- vmception 5y agoI like the direction you’re thinking
- busterarm 5y agoWhile we're at it, coordinated vulnerability disclosure/responsible disclosure is also for losers. If you're white hat, just publish ASAP. Full disclosure is the only way. Bug bounty programs are a trap.
- grayhatter 5y agowow, that response was needlessly cruel... I assume you're just having a bad day, so I hope you feel better soon mate. Good luck!
- breck 5y agoLicenses are for losers. Remember that kids. If you want to do big things in this world, run with the SciHubs and the PirateBays and the PublicDomainers. Flip the bird at the academics publishing junk behind paywalls crowing about licenses. The ones who matter set their ideas free. Been that way for thousands of years. (GPL was an amazing hack, but the next step is to finish the job, abolish IS laws, and bury for good the idea of needing a license to use your mind)
- nine_k 5y agoIf all licenses are for losers, do you suppose GPL to be also for losers?
- jchw 5y agoMy reading of their PoV is more one against IP itself as a concept, and by proxy, licensing software as a concept. In that case, GPL is interesting since the stated goal of copyleft is to basically use the copyright and IP law system against itself. While I don’t personally subscribe to IP anarchy, and I think that it is not being conveyed with an ideal level of tact, I do think it makes mostly logical sense. Deep down, from a purely ideological standpoint, most computer science minded people can probably understand IP anarchy. It’s sort of the other side of the “what color are your bits?” post. I still think the world is better off with some forms of IP, even if we’re all well-aware that the copyright and patent laws have been perverted in most places.
- breck 5y agoYes, IF thought of as a long term solution, and not a stop gap.
- smokey_circles 5y agoI suspect we've forgotten what the original reason for intellectual property laws were and that was rampant theft. "But you can't steal an idea" The world was built by good ideas and bad implementation, so I guess we are gonna disagree here.
- lifeisstillgood 5y agoI try (tried?) to push for greater FOSS adoption by governments (www.oss4gov.org) and it's still a long way off good. One of the biggest hurdles was always "support". Purchasers liked OSS but no one felt they would get commercial levels of support (a single wringable neck if you like). I think that the best solution to this is to commercialise FOsS support - I think that dev shops can select decent FOSS projects and provide various guaranteed support - in a common manner. Perhaps some kind of licenced or insurance payment. I can imagine some kind of back payment to the original project - it won't be as profitable as software use license but it might be enough?
- nine_k 5y agoWas / is it not the core business of Red Hat? You can run Linux for free, but if you want continued support, you can pay for it. I wonder if something like that is available for front-office software, like Libre Office, Odoo, Redmine, etc. I suppose much of the FOSS support business model has been eaten by cloud,providers who offer a lot of such software as a service. I still suspect that many government agencies would prefer or require on-premises installations.
- pabs3 5y agoVarious companies do LibreOffice support: https://www.libreoffice.org/get-help/professional-support/ https://www.libreoffice.org/get-help/professional-support/ Probably there are companies for the other projects you name, or contracting random developers would work.
- lifeisstillgood 5y agoI should have been clearer - in my head I meant software that is specific to government - so I want to see FOSS versions of building licensing applications, or road maintenance gazetteers, or databases of voters, or fleet management applications for refuse collectionnlorries or ... There is a world of software (usually 50% of GDP) that only gets spent by government - it should be free (libre) and it needs creating, distributing and supporting
- pabs3 5y ago
- LIV2 5y agoThis seems to be a common thing in some OSHW stuff I've seen. Some people will take your work and sell it for massive markup but the support is expected to be provided by the creator (and a lot of the issues stem from the fact that these sellers might substitute parts for cheaper ones that don't meet some critical specs like timing or TTL compatibility for example) When those creators say they aren't happy with that arrangement all they get is abuse - sure everything is legal but it doesn't make the behaviour any less immoral or scummy.
- pabs3 5y agoProbably the right social norms for OSHW (and FLOSS TBH) would start with providing their own support and extend to profit sharing.
- quanticle 5y agoI think this is a dangerous mode of thinking. The purpose of a license is to outline what rights I have with regards to copying the software (and redistributing it). If I have the right to do something, then I ought to be able to do it, even if you request otherwise. Imagine if some corporation licensed their software with the GPL, but then "requested" that you not repackage that software for Windows. Would that be a "healthy response" on the part of the company? I don't think so. The GPL clearly states that I have the right to redistribute modified copies of the software, so long as I make my changes available to others. In this case, the software is licensed under the MIT license. MIT is an even looser license than GPL; a redistributor can take the software, make changes to it, and redistribute the modified version as a closed source binary, so long as they acknowledge the original creator. Repackaging the software is clearly within the rights of the NixOS maintainers, and they've chosen to exercise their rights as defined by the law. To argue that they have some unwritten obligation to respect the wishes of the package author subverts the intent of free software, which is that the software that runs on my computer is mine, to run and/or modify as I wish. If the package author wishes to restrict his users from modifying their software, there is a very simple remedy: release the software under a non-free license that restricts redistribution. The way they're behaving now is an attempt to eat their cake (restrict the way software can be modified and distributed) and have it too (get credit for releasing software under a free software license). EDIT: Swapped out BSD in favor of Windows in my first example, because it seems that people were getting confused between BSD (the operating system) and BSD (the license)
- wumpus 5y ago[Because of the edit above, my comment is no longer relevant.]
- bramblerose 5y ago"BSD" can refer to the BSD license, but I think the poster is referring to the operating system here.
- MattGaiser 5y agoI think that is what he meant. What happens when someone created GPL software and then does what this developer does, which is pressure others not to freely use it?
- MattGaiser 5y agoI would rather that norms not be injected where they do not need to be. The problem is that norms are often unclear, applied unequally, deter otherwise worthwhile things from being done, often exist for little reason other than "everyone else does it", and often could be eliminated with by explicitly writing more accurate rules. How many companies would be deterred from adopting open source if they saw it as a reputational risk in case the original developers decided that their particular use case was "not what was wanted"? I used to work for the government, where they require long support times. Someone randomly deciding to change a licence as they didn't really mean what the licence said in the first place would be a huge problem.
- dalbasal 5y agoIMO, this is impossible. Even really formal rules systems like law need a lot of interpretation (eg courts/judges) to bridge the gap between abstract and particular, and to adapt to culture. Even so, explicit laws and contracts can never really cover everything, for example, in employer/employee relationships, business/consumer relationships, etc. A more subjective cultural layer does most of the work. It's not as enforceable as the explicit, contractual layer. This example is, IMO, pretty normal and OK. There is the explicit license, which governs the legal side. There's the unenforceable request, which can still be made. There's recourse, relicensing. There is a subjective layer, which is what this article is doing. Should X have honoured the request? Was it ok for Y to make the request? Was reliscencing against the spirit of open source? We need the whole package. Society can't be written down, because we don't really have the full spec. Explicit, legible rules are important, but they're a cornerstone and a fall back.
- soneil 5y agoI’m not sure “norms” are avoidable. How many posts do we see to various github issues where people haven’t been “delighted” with the maintainer’s response? We are highly defensive of the rights that floss/copyleft licences grant us, but highly dismissive of the “no implied warranty” verbiage that goes with them. That appears to be this maintainer’s issue. And it does come at a cost. There’s a very strong chance his next project won’t be floss/copyleft.
- solidasparagus 5y agoThis article passes over the tone of the communication, which was really the driver for most of the discussion in that thread. Many people had sympathy for the situation, but many also had problems with the way the creator approached the discussions. The comment that is specifically quoted about "not understanding the spirit of FOSS" wasn't even about asking to have a package excluded, it was about the refusal of the dev to engage in any sort of discussion and just the overall unhelpful attitude he took (which the dev improved upon in later communications).
- zargon 5y agoI get the feeling that the demand to have such a conversation, at the whim of downstream, is a significant part of the burden the author wished to avoid. At least it would be for me in his position. I may express a preference and desire not to be forced to expend the (considerable) effort to find words to defend it to the satisfaction of some third party (who may never be satisfied).
- deleted 5y ago[deleted]
- solidasparagus 5y agoBut downstream didn't demand anything. AFAIK there was no communication until the dev asked for it to be removed, they asked why, and he said the equivalent of "just do what I say", which obviously didn't get him anywhere. And the public opinion was really only against the dev because he was being intentionally difficult while the NixOS people were bending over backwards to look for a mutually-satisfying solution. It would have been a non-story if the dev hadn't been a bit of an ass in public forums.
- zargon 5y ago> But downstream didn't demand anything. As you described above, they damanded a conversation about why he was making the request he did. They couldn't just acknowledge that he had a request and choose to respect it or not when it was clear he didn't want to talk about it. Instead they dragged him into a huge spectacle. Even after they closed the issue on their side, (other?) NixOS people went to endlessly harass him on the home assistant forums.
- jchw 5y agoI don’t agree that social pressures to conform to unwritten rules are in the spirit of open source, nor is asking maintainers to treat your project different from 60,000+ other packages. In fact, not all of the packages in Nixpkgs are even open source. Even more in fact, Nixpkgs doesn’t even redistribute packages directly - there are caches, but the core thing that is provided is a manifest. What we have here is not an open source problem. What we have here is a social problem that happens to regard a project that is open source. Outside open source, people who are concerned about distribution for one reason or another certainly exist - in the past, asking people to not repost their downloads and instead link to their pages, pleas that often went unanswered due to the ruthless desire to share information freely online, licitly or illicitly. Tying this into support is totally moot. First of all, that impacts any free as in beer software equally; on NixOS especially. Secondly, the connection to FOSS being unsustainable is not warranted here in my opinion. Home Assistant is a highly visible project that appears to have a couple different approaches to monetization. It isn’t exactly the unsung hero of the open source ecosystem as a whole. Thirdly, there is no obvious specific event that spurred this all on, so it’s not clear this was the motivation. Finally, the NixOS maintainers seemed willing to go different lengths to try to satisfy this support angle and were swiftly shut down with the author acting increasingly more impatient, seeming to not understand why they are trying. And that caused pressure to the NixOS maintainers. Who are volunteers on an open source project who are trying to not break their own users by removing or stalling a popular package they already had[1]. The whole conversation looked very stressful and one-sided. I can’t say exactly what happened here, but I hate the framing that suggests this is a healthy direction for the open source community. It feels like we’re setting up for a world where, counterintuitively, a ton of expectations are hoisted on you if you release open source software. Like do I have to check with all of my upstreams that vendoring my dependencies doesn’t upset them? The second and third order effects here do not sound tenable to a healthy community. Licenses are meant to encode expectations in a tangible way; that this is imperfect is obviously clear when you consider peoples abject reactions to things like the SaaS loophole - it reflects a place where a mismatch occurred. This really isn’t that. This is more like something that could actually just be encoded into the license but isn’t. That’s a problem. Because if they are successful, this sets a bad precedent. It smells an awful lot like distributing software under one license but stipulating additional things on top. Taken to its extreme, it could start to smell an awful lot like shared source but with the legal benefit of being able to rely on software whose licensing wouldn’t permit such a combination. And that’s just it. Open source is an asset and a strong brand. I think when bootstrapping, a lot of people see the benefits as hard to ignore, and maybe make the choice despite that it may not truly align with their personal views and attachments to projects. It’s really the same thing when it comes to a lot of the open source debates lately; it feels like an increasingly large amount of people want the control that you have with closed source, while maintaining the branding benefits and assets opened up by being “open source.” I can’t pretend to know what the motivations for this whole debacle were, but the author actually did suggest they would simply move the dependency to a shared source license and add an exemption for home assistant. In actuality, there is nothing wrong with this, so as long as it doesn’t trample on any license obligations elsewhere. I and many others are not suggesting you are morally obligated to use open source licenses or anything like that. But I think if you do use open source licenses, while you aren’t particularly obligated to do anything, you are also not particularly owed anything. I really, really, really think it needs to be kept that way. [1]: https://github.com/NixOS/nixpkgs/commit/bacbc48c https://github.com/NixOS/nixpkgs/commit/bacbc48c
- hbbio 5y agoI have the impressions that, in some ways, we are reaching the limits of the open source model. I am not saying this light heartedly, I built a fair share of open source software myself. The situation is complex since many different types of contributions exist ranging from two extreme positions: 1. A company or startup following the "open source business model" publishes a complex piece of open source software, trying to get adoption while the company lives off VC money - planning later to sell services (hosted SaaS, support, etc.) and/or extra features for the product. 2. An individual writes a small library or tool in his/her free time, publishes it on GitHub and then forgets about it. But it may still get traction because it is useful. It is a gradient of several variables: type of entity, intended purpose of publishing and expected return, short/long-term commitment, etc. that lead to different situations. For some, especially if we account a growing social factor in, there may be better solutions that open source (as OSI defined). For instance, an independent developer writing an important library should get a share of the business use/revenue, especially if a set of companies that were not involved in writing it end up seizing most of the enterprise business around it. Something like "public source", i.e. source available but not free to use under any condition may be an answer in some cases.
- enriquto 5y agoi'm sure we had a name for that, "coopie-lept" , "copiiiehlift", "cuuu..." please help me
- badsectoracula 5y agoCopyleft certainly is not "source available but not free to use under any condition".
- ozim 5y agoI think there should be something like "Private copying levy" but for open source developers that create useful libraries. My example would be cURL. Car makers have it incorporated in their software and well I don't think any of those car makers was going to Daniel to buy that piece of software or contributed back to the project. For "private copying levy" I don't really agree all poets should take cut because there is no demonstrable evidence that someone is using their work, so they would receive money for nothing. While open source developers can demonstrate that their software is used by those companies to build products and people use their work while using products. https://en.wikipedia.org/wiki/Private_copying_levy https://en.wikipedia.org/wiki/Private_copying_levy https://daniel.haxx.se/blog/2018/08/12/a-hundred-million-cars-run-curl/ https://daniel.haxx.se/blog/2018/08/12/a-hundred-million-car...
- jankotek 5y agoOS author also distributes, maintains and supports project. Just compiling some opensource projects (Firefox, Chromium) is very complicated. I am not sure what happened here. But if large project would use outdated or broken version, author may get bombarded with support requests for problem, that was solved years ago.
- mpfundstein 5y agocompletely off topic but why in gods name is he using they as a pronoun for Frenck who is clearly identifiable as a male...? i dont get it. is there some holy quest out there to just ungenderfy everything just for thr sake of it?
- redis_mlc 5y agoCorrect, "they" is now often used when an author hasn't confirmed the preferred pronoun of the author. See also: - birthing persons = moms - founding fathers = founders - amen = awomen - history = herstory
- sascha_sl 5y agoMaybe you should be a little less presumptuous, technically nobody is "clearly identifiable" as anything. What you're applying here is a shorthand.
- mpfundstein 5y agolook at Frencks github. if he identifies as female, ill eat my socks
- sascha_sl 5y agoI don't doubt it, but not making unnecessary assumptions is still nice. You know, as a general rule. Also, there are people who are neither. (Just preempting: I'm not interested in discussing the validity of non-binary people, please don't write an essay about evil gender ideology under my comment)
- mpfundstein 5y agoi dont care about gender stuff. i use they also if unknown. but using they if subject is clearly male just strikes me as wrong
- randy408 5y agoNot a lawyer, but I _highly_ doubt the MIT license makes any difference when it comes to the author's demands in this situation, he has moral rights (legal term) to the software. You can't just make a mess of packaging someone's work and assume there's no legal avenue for the author, that's just naive.
- wvenable 5y agoThis is the text of the license (emphasis mine): "Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so." The license clearly and explicitly grants the ability to make a mess of packaging the work. One could translate it into BASIC and use it to launch rockets at whales in the pacific ocean and that would be granted by this license.
- randy408 5y agoMoral rights are unalienable in Europe, I'm not gonna quote a full paragraph from Wikipedia[1] here. https://en.wikipedia.org/wiki/Moral_rights https://en.wikipedia.org/wiki/Moral_rights
- aethertron 5y agoThen they're incompatible with FOSS. If someone - releases code under MIT/GPL/whatever, declaring that their work may be changed and redistributed - then later asserts their moral right to NOT have their code changed and redistributed then they have done a nasty bait-and-switch move. The have shown themselves dishonest, and using their software should be considered a legally dangerous idea. If their courts support their claims then FOSS, as we know it, is unviable in that realm. But this hasn't ever happened, has it? Europe's FOSS development activity seems robust enough. But perhaps they are legally on a sand foundation...
- busterarm 5y agoIt's starting to look more and more as the decades pass from when these licenses were written that many authors don't understand the terms nor the purpose of the licenses they're choosing.
- smokey_circles 5y agoThere is no such thing as the spirit of open source. This is a stand-in for an actual argument that bridges the gap between your own philosophy and the reality of maintaining a project. However, if you were so inclined to believe otherwise, please explain to me how that spirit of open source would not have simply dictated that either the project get rebuilt from scratch or simply cloned before inclusion? It's not hard to recognise the human problem and try to work with that. Instead: We find braindead allegiance and arrogance throwing shit on either side of the fence. The open source community is in trouble if this is the direction we're moving in
- philprx 5y agoOk, maybe I'm super wrong here, if so just indicate it (kindly ;-) it seems to be hot in these threads ;-) ). Here it is: It seems to me the root cause has nothing to do with openness and FLOSS and licensing: It seems to me it has to do with NixOS has a technology architectural choice of "fixing" dependencies in a way that's more costly (fox NixOS package maintainers) to maintain to the latest version of each package, that the dependency package author doesn't like that because NixOS therefore keeps older packages, and therefore will create problem down the line. Am I wrong? PS: I usually take the analogy with noisy neighbours and the architect. Some neighbours end up in fight because of noises in another neighbour's flat. In the end, nobody goes to the architect and building company complaining that the walls are too thin. Yet they fight on the downstream problems. Good thing: In software we can fix things more easily than in hardware ;-) Here it seems it's a fight on a downstream fight on a tech architecture choice.
- kosinus 5y agoYes, Nix is a little more strict in this regard, when seen as a package manager. But regardless, the author also mentioned he took issue with Fedora packaging, so is more interested in limiting distribution channels in general.
- soraminazuki 5y agoFrom the looks of it, the upstream author was against downstream packaging of any sort. It's not any particular problem that caused him to attempt to prevent NixOS users from using his software. But anyways, existing packages tend to be easier to maintain on NixOS because of rich tooling around the Nix ecosystem. Most importantly, they have automated workflows for checking and updating upstream sources[1], and it can be merged without problems most of the time. There's also lots of effort around preventing regressions too, and packages are tested as part of the automated workflow. It's also easy to check out the changes yourself, because you can just "git pull" and test the changes locally without interfering with your existing installation, a feature unique to Nix. The upstream author's claim that NixOS was not bothering to update his packages are simply not true. That was just him being incendiary and disrespectful[2]. NixOS was using the exact version required by the latest version of Home Assistant. And he very well should've known that because he happens to be a major Home Assistant contributor. If anything, data shows[3] that NixOS is one of the most up-to-date distros out there. [1]: https://github.com/r-ryantm https://github.com/r-ryantm [2]: https://github.com/NixOS/nixpkgs/pull/126326 https://github.com/NixOS/nixpkgs/pull/126326 [3]: https://repology.org/repositories/graphs https://repology.org/repositories/graphs
- cbsmith 5y agoThis is not a complicated issue. Open source affords one twins one might think as undeniable, but that doesn't mean authors have no voice. It just means that voice isn't backed by people weapons and military training with the express authority & purpose to use all of the above. The idea that the author's voice deserves to be heard and considered is essential to a vibrant community. Authors living and dying by their communities' perception and response to hear ideas/opinions is the point.
- cbsmith 5y agoThis is embarrassing. Autocorrect changed "rights" to "twins", "their" to "hear", and somehow dropped "with" entirely from "people with weapons". :-(
- busterarm 5y agoI would like to argue the direct opposite conclusion of the title. License, alone, governs behavior in open source. The terms and the guidelines of the OSD matter. If you are trying to enforce behavior that is counter to the guidelines of the OSD then we are no longer talking about open source software. Your software should then be publicly derided for abusing an open source license.
- eliah-lakhin 5y agoWhy not just simply write a new type of License that would explicitly ban organizations and entities from using the work in any forms, but, in contrast, would grant large possibilities to use the project for individuals for free? Such approach is no doubt contradicts FOSS principals, but I don't see how else we can defend ourselves from the business exploitation these days. In addition, I would also explicitly state in such License, that the author preserving exclusive rights of the work. To keep an IP in hands of it's creator. When one keeps exclusive ownership rights, it could be clearer how to defend them in the legal field, rather than something developed by uncertain set of contributors. GPL and other FOSS licenses were initial designed for crowd development. But let's face the truth, a lot of nice software projects are practically developing by individuals exclusively. Their authors don't really require crowd contribution even for maintenance. Yet, society(by "society" I mean independent programmers and individual users, not corporations) can still benefit from using of their work. It's a common practice in many other fields of creativity. We rarely see books, visual art creations, scientific articles, etc made by crowd. And there are many examples of outstanding works made this way. And all that works are quit well defended by just normal Copyright laws. So, why shouldn't we, the programmers, avoid such obvious and well defined practice? Of course, FOSS could still be applied for large infrastructure things. Such as Linux maybe, or Wikimedia. Crowd development is beneficial in many aspects, but individual creativity is not crowd development. So, my point is that individual authors just shouldn't adopt FOSS licenses by default.
- andybak 5y agoI develop for myself, for a loose collective, for clients and for my own company. I rarely know where the boundaries are myself. CC-NC is ambiguous enough that I avoid it. I have no idea how an “individual use only” license would work but I suspect I would give it a wide berth.
- quanticle 5y agoThe specific example at hand is that the author of python-ambee requested that NixOS maintainers not package their library, because they disagreed with the approach that NixOS was taking. The NixOS maintainers responded that they have the rights to do so under the MIT license, and the original author agreed that they did so. The original author then continued to request that NixOS not repackage their software, even though they themselves had given the NixOS packagers the right to do so (by selecting the MIT license for their software). I'm not sure how your solution addresses this scenario. Of course the author could have written a license that restricts redistribution to channels that meet their criteria. But they didn't do so. They chose to use a standard free software license instead. I fail to see how the creation of yet another non-free license would solve the scenario of the author understanding that they've given away certain rights via their license agreement, and then expecting people redistributing their software to voluntarily give those rights back with nothing in compensation.
- Applejinx 5y agoI'm an MIT license software author. I frequently get people asking 'I mean to do X thing with your codebase, which is allowed under the license: is this okay with you?' and my answer's typically, 'Of course, that's why I chose that license in the first place'. I'm also a white guy. Let's imagine what would happen if another white guy decided, "I want to make a DAW project that is only white guys' code, based on Chris's work as he seems white enough to me, and I will promote it through pointing to Chris and extolling his racial purity!" That's substantially more unpleasant (at least to my mind) than having an increased support burden, but it wouldn't change my use of the MIT license. Instead, what it would mean is this: if anybody asked, I'd tell 'em that the project was in compliance with the license but the people were absolute bozos and I didn't like them or the way they were behaving. Open source, especially as it leans more permissive, DOES NOT imply a support burden or endorsement deal. This is of course the BSD non-endorsement clause which is not present in the MIT license… It's a bit like this: my surname is Johnson. That's a pretty common name. I can imagine a person who learns this, and then goes, "Oh! I know a guy named Johnson. He is your brother! In fact I know five guys with the name Johnson. What a great family you have! I'll help you by gathering them all together for a reunion in your back yard." That would be dumb, but it would also be not my problem: I have a reasonable expectation that, in the context of normal society, I could say 'that's a very silly thing and not my doing' and people would acknowledge that it's the silly person's problem, NOT mine. By the same token, I feel confident that society would not tie me to a 'Only White Men DAW' using my MIT-licensed code, and lastly that the original package author is free to NOT take personal responsibility for handholding all possible users of their software, even if it's packaged in a large distribution that propagates their work farther than they expected. One possible workaround is what I effectively do with my codebase: if it's unwieldy or difficult in some way, and you're Free software, lean into that! Let it be known that you're too busy doing your part of the work to provide truly great support services, and suggest that third parties might step in and do their best to take up the slack. Odds are, they won't: but the suggestion is truly in the spirit of Free software, in that you are providing everything that YOU reasonably can, to anybody who would like to extend your work into a more fully developed software ecosystem. If there's a profound need for the type of support services you as the author don't feel able to extend to a giant audience, somebody WILL provide that support because it'll be much sought after and bring appreciation and popularity to the supporter. If that sort of popularization is truly important, the support-burden provider might end up seeing more in the way of donations/recompense than you as the original developer, because they'll be the ones directly dealing with the large audience and being 'the face' of the software. Think about what your expectations as a Free software developer are, and communicate those. That's all that's needed. Don't project onto the license, taking on things that aren't being asked of you, and the end result will evolve in a way that is strangely personalized to your needs. Right now I'm watching the evolution of three audio software projects: me with the Airwindows DSP codebase, Surge Synthesizer, and VCV Rack. Each one has developed a 'style' of interaction with society at large around use of the code, but in each case the 'style' is quite different. The expectations and 'style' WILL be communicated, regardless, and this is why I think it's a mistake to do things like request non-inclusion in a distro: that developer underestimates the ecosystem's ability to 'read' their wishes for how they interact with that system. I don't believe they'd get buried under support requests, unless they functionally behaved as if they were actually responsible for doing that. The ecosystem will 'read' what you do, not just what you say you'd like to do. Working in Free software requires that you're honest about what you are and are not offering. I could make my life incredibly harder, by putting forth the appearance that I am about coordinating and overseeing a whole world of pull requests and coordinated derivative projects… diving into stuff that's way beyond my ability to keep track of… but since I don't put across that appearance, my burden to maintain that is effectively zero. Because I'm rigorous about avoiding stuff that I'm ill-suited for, I'm not muddying the waters through pretending to be competent at it…
- eptcyka 5y agoI don't believe Frenck's claim that there ever was a burden by nixOS users laid upon the HA community. Regardless, pulling out the rug from under a lot of users who will then just repackage HA anyway is not something a distribution would do. Once a package is in a repo and people rely on it, it's not easy to remove it. Adding to that, having a conversation and just making the same blunt demand without responding to honest proposals about how to mitigate the undisclosed issues that packaging the plugin for NixOS are two completely different things.
- WesolyKubeczek 5y agoSadly, it’s another case of some software author having a prima donna complex. NixOS is quite a niche distribution. Of the comparatively small overall number of users, the number of those that are going to use his library, is an even smaller subset. A small subset of them will have a bug to report, and a smaller number of them yet will take it to the upstream. So the author makes a fuss about getting drowned in maybe 1.5 people creating three requests in 5 years. Doesn’t compute. Complaining about burnout long before you burn out?
- klyrs 5y ago> Complaining about burnout long before you burn out? One issue that many of us face in OSS is that it's a side project. If a developer is burnt out by their day job, or some other aspect of life, then their tolerance for pushy maintaners drops to zero even if they still occasionally unwind by working on the project.
- WesolyKubeczek 5y agoAs far as I can see, it's his job and not a side project anymore. His LinkedIn lists him as full time developer on HomeAssistant, and elsewhere I've heard Nabu Casa is sponsoring him. His day job must suck, yeah.
- Fuzzeh 5y ago"The creator expressed these concerns by way of a social request instead of a legal threat because part of living in society is being able to resolve disputes without going to court." Is simply not true. The creator made a social request because there was no way a legal challenge could succeed, not because they wanted to avoid court.
- AgentME 5y agoI think one of the most significant things about open source is that you're allowed to port it to new platforms. Imagine if you were porting some MIT or GPL open source application from Windows to Linux, and then the original author of an open source library used by the software you were porting told you that they hate Linux and don't want you to port their library to Linux. Are you obligated to do so and therefore give up on making a direct port of the application to Linux? A lot of people seem to argue that while you're not obligated to follow the developer's request, that it's still proper for them to make an optional request like that. I still think it's improper for the developer to make a request like that without a good reason. Imagine instead that you were the author of that Windows application, you released it as open source in order to guarantee that your code could be used as much as possible, and you specifically chose open source dependencies so that this could happen and that your entire application would be open source. And then you hear years later that your application wasn't ported to a new platform because the developer of one of the dependencies, that you specifically picked because it said it was open source, made a vague request exactly against one of the core benefits of open source. You'd feel like that dependency author misled you by labeling their work as open source. Packaging the project in the NixOS repository seems to be equivalent to porting it to work in NixOS in the most standard way, and as far as I can tell, there's interest in packaging the project because it's a dependency of Home Assistant, an open source project that people want on NixOS. I think it's proper for a dependency developer in this situation to make requests to change the presentation of the code (like that NixOS fork and rename the project so users don't ask the original developer for support), but to make a request that potentially blocks an open source dependent program from being ported to another platform is bad. EDIT: Even weirder, apparently the developer themself added their library as a dependency to the open source Home Assistant project, and now after this they're getting in the way of Home Assistant being ported to other platforms! https://news.ycombinator.com/item?id=27506141 https://news.ycombinator.com/item?id=27506141 >But now that frenk added his code as a dependency, he has the right to transitively make Home Assistant un-packagable on NixOS?
- needle0 5y agoOne advantage of commonly known licenses and their legalese is that it allows people who don't speak the same language to still collaborate without talking to each other in their non-native tongues, through understanding and adhering to the legal code. (For commonly used licenses, high quality translations are already available). Bringing natural-language "requests" into the issue nullifies that advantage and denies casual collaboration/use to those who cannot speak the language. (Machine translation, even DeepL, is still not good enough for language pairs with distant syntax structures.)
- neilv 5y agoI said something slightly similar once. A little weirdness was going on, in a niche platform community, so a while ago added a statement on a Web page that listed my packages for it: > If you'd like to put modified copies of my packages in public Git repos, or otherwise distribute them, I'd appreciate you reaching out to me. The license very intentionally gives you the right to modify and distribute, but [niche project] is a small and cooperative world right now, and it's better for everyone if we coordinate. One of incidents that prompted this wasn't compliant with the licenses, but I thought I'd leave it at the above. Back to TFA, I'm somewhat sympathetic to the developer there, not wanting to get support requests, etc., for problems caused by a packager, and this is a problem that, say, distros normally have to address. (And I've seen it addressed badly, such as a third-party setting up a bug-reporting system for my upstream packages, which gave the appearance of being the official way to report bugs, but... I didn't know about it, I didn't get notified when people made bug reports there, no one was handling those reports, and, when I eventually stumbled upon the reports, the mechanism didn't have a way to contact the submitter for more info. The bad mechanism was just sitting out there, wasting submitters' time, and sabotaging success of the project. Then, when I explained to the party running it that it was hurting the project and contributors, they refused to make it opt-in or let me opt-out. I think this is just one example of the kinds of time-suck that you see after contributing to open source for a while, and which might not be obvious to people until they've seen it or heard about it.) That said, while I think the developer in TFA is fine in saying that they'd prefer a package they develop not be included in some other thing, or perhaps explains why and asks for changes in how that's done to not hurt the developer's work... they have to be aware that, at least in US culture, their request (like mine, in a different situation) is orthogonal to the license, and is a cooperation "ask". There's some value in having terms clearly communicated (such as with licenses). And when you give a license, if you're going to ask for a restriction on what you already gave in the license, you're taking away some of the value of licenses. Considering this an "ask" is even more appropriate -- but not limited to -- cultures/subcultures that might consider "whatever is legal" (or "whatever you can get away with") the sole consideration.
- pessimizer 5y agoIt might be more precise to say that "licenses do not govern all behavior in open source." But the flip side of that acknowledgment should be to notice that while obedience to licenses is governed by force of law, all other behavior common open source is essentially ungoverned, or governed in an arbitrary, self-appointed fashion. There's this tendency in permissive open source to reify "social norms" into their own sort of law, and then indict people based on the violations of them (as they are defined by the speaker.) Social norms are a survey of behavior, not an enforcer of behavior. I may not feel good going against the wishes of the author of a piece of software that is under a permissive license. If enough people feel like me, honoring that sort of request from an author may become a "social norm," especially if people who agree with me start to punish people who don't agree with me, and that creates a pressure for people who don't agree or are neutral to conform to avoid being shunned. This is where actual government is introduced, in the people who refuse to hire, work with, or do business with other people. That's fine, but if you're going to use your authority and autonomy to enforce your arbitrary moral rules, you shouldn't be surprised when massive and massively powerful corporations use their authority and autonomy in the way they see fit. You don't shun Amazon, Amazon shuns you. That's why there's an advantage in encoding whatever moral stance you want to take into your license, and in confederating with others who share your beliefs (as explicitly stated in the license) in order to form a more powerful unit. Then the courts can defend you against Amazon, and a side effect will be that there will be even more power as a community to promulgate your extra-license norms. Also, well-governed GPL within a community isn't incompatible with secret sauce. Dual-licensing schemes give the power to create good businesses, through exchange of permissive relicenses, subsidy and mergers. We just have to be creative about it. If a walled-garden, curated experience can be an advantage in the market, there's no reason you can't create one with GPL'd software, cross-licensed permissively, where the authors, developers, marketers and salespeople get paid. Just uphold the philosophy that you're not going to restrict people's access to and ability to modify their own devices, or use incompatibility to create a moat between yourself and competitors. If possible, encode it in the permissive license. That doesn't mean that you have to recommend that people modify their own devices, or that you have to distribute code, or even make it at all easy to do. If people do modify their own devices or software, it doesn't mean that you can't void their warranty or cut them off from your cloud services. If you notice a player out there doing a good job of modifying your devices or software, bring them inside to do it, giving your users less reason to stray. Apple and Google built their businesses on a mix of permissive open source, proprietary bits, and exclusive services. The same can be done with a mix of GPL, relicensed GPL to permissive licenses with proprietary bits included, and exclusive services. The difference is that the GPL software commons will be built up during the process, and the use of that GPL software will be an advantage the small confederating players will have over the massive multinationals.
- jasonlotito 5y agoThis is another case of an open source developer choosing a license for personal gain instead of the good of the community. People blindly choose MIT/BSD licenses for personal benefit need to understand what they are allowing. They reap the rewards with recognition, jobs (companies seeing you as an open source developer), praise, or in the case of companies, developer mindshare. But then someone does something the license allows but the author doesn't like, and suddenly the person obeying the license is at wrong. Point is, understand what you are allowing with your license choice and accept that you are okay with everything it allows. If you don't want to allow something, include it in the license.
- grawprog 5y agoI read through the whole discussion on github. I understand the author's concerns and point of view, but his response to the NixOS maintainers and way of dealing with the situation was completely unreasonable. The NixOS people seemed willing to work and do what it took to make it work, up to and including rewriting the functionality using an identical API. The author refused to compromise, discuss anything and got fairly hostile and was pretty rude. It might be slightly more understandable if the author had been getting a barrage of complaints from users, but this hadn't even happened, he was preemptively assuming(you know what happens when you assume things...) it would and refusing to listen to the assurances of the NixOS people about taking responsibility for this. All the author really has to do is make it clear somewhere that they won't support any users using a non-official packaged version of the software.
- fsckboy 5y agoall the company needed to do was fork it, he's happy, they're happy, done.
- detaro 5y agoThere is no company involved here, and your "solution" was offered and rejected, so clearly he's not "happy" with that.
- fsckboy 5y agoI read most of the article, and you are relying on information that wasn't in the article. The article doesn't even contain the word "fork". my answer is a good one, he released open source with a license, their fork would not generate work for him which was his main concern.
- zzo38computer 5y ago> If users experiencing issues with [the package], they will knock on my door. And I’m not willing to support that or accept that burden. It is one reason (not the only reason) why I prefer licensing that does not require attribution. Unfortunately, all licensing (other than public domain equivalents) seems to require attribution. The warranty disclaimer is also important for this reason too. You can still accept bug reports and questions and that stuff, although doing so should not be required. You should not necessarily expect the author of any computer program (open source or not) to accept such questions and reports; it is up to them to do so (and may charge money to do so, or it may be free of charge).