@b9ace @dreezj Nobody owns a trust. The money of a trust is managed according to the trust's statutes, to fulfill the goals of the trust. No dividends. The statutes can say that a certain entity appoints management, but the government monitors that management works to fulfill the goals of the statutes.
@b9ace @dreezj Some of the difference I'm describing may be more clear culturally than legally. And of course I don't know less about US law and customs.
@dreezj @b9ace Oh yes, but also, words have meaning. Although, meanings change. The big cooperatives in Sweden have very complicated corporate structures and "cooperative" is not a protected legal term.
@b9ace @dreezj The Swedish mega-coop KF is a corporate business group with subsidiaries in retail, banking, investment etc, but the mother company is owned by regional customer cooperatives.
@dreezj @b9ace So, to go back to your original question, I'm not sure what a coop is going to solve in the federation case. An association accepting donations, or simply volunteers donating time and code to the software and to the services is what has been working well so far. The federation is still growing. Not to the billions, but with postActiv, Pleroma and Qvitter, I would say GNU Social is more lively than it has been for years.
If you try to pull in big investments, there is a big risk of ruining it. The origin of GNU Social was StatusNet, a venture capital-funded corporation. Evan tried to earn money through enterprise deployments, but sadly was pushed out by Yammer and others. We are lucky (or Evan was skillful enough) that the company "failed" by quietly winding down, rather than VCs requiring desperate measures like putting up ads or selling user information.
There is no big GNU Social boom, but there is also no crisis. Let's keep working calmly on extending and repairing the codebase and the network.
@b9ace @dreezj If shares are created when you buy them, at a fixed price, and the coop buys them back at the same price, and destroys them, it's not really possible for a market of shares to emerge.
@b9ace @dreezj I would like to once more emphasize that I don't think #statusnet "failed". It gave us GNU Social. And it provided Evan with the experience that allowed him to create pump.io, which has been the structural starting point for the work on the new #ActivityPub W3C federated social network standard, one that may yet be added to GNU Social.
The Linux people mainly rejected GPLv3 and that's it. There's also the additional possible of possible estoppel giving Linux basically a weak copyleft. But we'll see how the next round of Welte's court case goes.
What's the "GPL 2/3 problem" and what's to "take care" about?
Is the problem that Linux is not GPLv3? What about the Firefox "MPLv2 problem"?
If Harald Welte held an interesting talk on Linux, licensing and enforcement, I would be interested to see it. Do you mean https://chemnitzer.linux-tage.de/2017/de/programm/beitrag/311 ? They don't seem to provide videos. Do you know if videos will be up elsewhere?
I don't see any direct connection to permissive licenses.
@clacke @fsfe @b9ace @dreezj who are the "linux people" to disclaim GPL3? i am a fellow of fsfe. And if i give a takl about - the people a very interest in it. The Kernel is GPL2 e.g.: you or i buy a 'embedded linux device' - we can donload the source from manufactor, we can 'change' or patch the source, but we can't bring the code on our?! device #internetofshittythinks :-) - this is imho the GPL2/3 problem. - CLT yes yo right. i will write the orga team for records (IMHO only audio) especilay harald's talk! - permisive 'licence' is ( ok, i am a 'radical' ) a part of "artifical shortage" to make money with "public code/interesting" ps: thx for a very interessting discussion #ilovefs
Linux the kernel. Kernel developers. Linus & Co rejected the v3.
Ok, so by the "GPL 2/3 problem" you mean the limitations of the GPLv2. I would call that the "GPLv2 problem", as the only problem with the GPLv3 is that they're not using it. :-)