> I understand that. My argument is that that mentality is doing the project a disservice.
In the world where we accept unfinished software all around us, from government and banking services, to our daily general computing devices like computers and phones, to appliances like TVs, washing machines or elevators, the project seems to be doing great for many a user: we've heard accounts here from people putting the software on their device once years ago and forgetting about it — it just works.
Their focus seems to be exactly that: ensure this project works for them, and allow a select few trusted partners to make it work for their own equipment too. But work it must.
I might have a different perspective on making software and evolving it, but that does not make this perspective any less valuable — it's actually great to have it out there in the world.
> For every person the author might find difficult to collaborate with, there will be many others who will contribute positive input and changes to the project. By not being open to collaboration, someone else will step in and build that community instead, given that the software is actually good. And that's fine, it's their prerogative, but chances are that their closed-but-technically-open project will languish in comparison to the project that's actually open and invites collaboration.
The project has been there for years now, and this hasn't happened. Either there aren't "many" who'd "contribute positive input and changes", or the issues with the project management aren't as big as some are making it seem here.
> So, really, I don't see what they gain from releasing it as open source in the first place.
They don't have to gain anything: they publish it because they don't mind it, not looking for any gain.
> This is not encoded in any legal frameworks or licenses...
Many companies have nothing to lose if they released their IoT device firmware as open source, but they have nothing to gain either, so they don't do it. I'd much prefer it if they released it, even if for the most part, I wouldn't touch it.
But I'd feel the sense of trust that this device is never dying on me, even if a company does.
So I disagree: a free software license is enough to "encode" all that you seek! Just by having access to the source code, and rights to modify and distribute it, anyone can decide to build a different community, evolve a product in a different direction, or change it to have a new technical foundation.
When this need becomes strong enough, it will simply happen: for better or for worse. See eg. LibreOffice vs OpenOffice case. Or the cdrtools maintainer frustration with Debian/Ubuntu forks (https://cdrtools.sourceforge.net/private/linux-dist.html).
In the world where we accept unfinished software all around us, from government and banking services, to our daily general computing devices like computers and phones, to appliances like TVs, washing machines or elevators, the project seems to be doing great for many a user: we've heard accounts here from people putting the software on their device once years ago and forgetting about it — it just works.
Their focus seems to be exactly that: ensure this project works for them, and allow a select few trusted partners to make it work for their own equipment too. But work it must.
I might have a different perspective on making software and evolving it, but that does not make this perspective any less valuable — it's actually great to have it out there in the world.
> For every person the author might find difficult to collaborate with, there will be many others who will contribute positive input and changes to the project. By not being open to collaboration, someone else will step in and build that community instead, given that the software is actually good. And that's fine, it's their prerogative, but chances are that their closed-but-technically-open project will languish in comparison to the project that's actually open and invites collaboration.
The project has been there for years now, and this hasn't happened. Either there aren't "many" who'd "contribute positive input and changes", or the issues with the project management aren't as big as some are making it seem here.
> So, really, I don't see what they gain from releasing it as open source in the first place.
They don't have to gain anything: they publish it because they don't mind it, not looking for any gain.
> This is not encoded in any legal frameworks or licenses...
Many companies have nothing to lose if they released their IoT device firmware as open source, but they have nothing to gain either, so they don't do it. I'd much prefer it if they released it, even if for the most part, I wouldn't touch it.
But I'd feel the sense of trust that this device is never dying on me, even if a company does.
So I disagree: a free software license is enough to "encode" all that you seek! Just by having access to the source code, and rights to modify and distribute it, anyone can decide to build a different community, evolve a product in a different direction, or change it to have a new technical foundation.
When this need becomes strong enough, it will simply happen: for better or for worse. See eg. LibreOffice vs OpenOffice case. Or the cdrtools maintainer frustration with Debian/Ubuntu forks (https://cdrtools.sourceforge.net/private/linux-dist.html).