3,485 karma · joined January 19, 2011
Edit: Pluto uses Julia's package manager; moreover, Manifest.toml can be used to pin all of your project's dependencies so the notebook is repeatable, from a code perspective.
In my opinion, there is room for many political perspectives in the workplace, moreover, they can all be correct at the same time. In particular, once people stop talking in abstract generalities, but in concrete actions regarding concrete challenges, many of these perceived differences melt away to reveal far more consensus than political posturing might indicate.
In my experience, the best way to handle political speech in the workplace is to ask the speaker to contextualize their perspective into a concrete action that they'd like to be taken, taking into account all of the moving parts and stakeholders. At this point, the ones who have a serious point to make have an opportunity to present a process improvement, or be educated about considerations they are not thinking about.
Edit: This is related to the above comment -- a colleague may be summarizing an uncomfortable experience not in terms of behavior (a rude vendor that talked over them) but in terms of identity (white male).
We had significant IRB work to do for a grant that involved usability testing of an application, to determine if it was more effective than existing tools. The IRB committee wanted to know what kinds of observations about software usability would be recorded and what kind of analysis we would be doing. They wanted assurance testers would be anonymous. They wanted assurance all testers would know about the evaluation, and how the analysis would be used. They wanted assurance that evaluation of the software's usability would not morph into an evaluation of the testers themselves.
Regardless of UMN's decision, perhaps the IEEE should consider withdraw of this paper from their journal regardless, their acceptance criteria reads:
> Discuss steps taken to ensure that participants and others who might have been affected by an experiment were treated ethically and with respect.
> If a paper raises significant ethical and/or legal concerns, it might be rejected based on these concerns.
https://www.ieee-security.org/TC/SP2021/cfpapers.html#Ethica...
In their apology letter, the researchers seem to acknowledge they ran afoul of this requirement:
> As many observers have pointed out to us, we made a mistake by not finding a way to consult with the community and obtain permission before running this study; we did that because we knew we could not ask the maintainers of Linux for permission...
https://www.reddit.com/r/explainlikeimfive/comments/210to8/e...
Unfortunately, the control arm for this study is a placabo instead of a single dose, which I would expect to be the standard of care.
There's no pulling the rug under people here: it's not like the previous releases, under the Apache license, are rescinded. Someone can still fork the project and keep it under the Apache license.
If they are using a proprietary license for their commercial offering, they will probably require future community contributions to be donated under the Apache 2.0 license.
So, this problem can be addressed by cooperatives, it's just a different kind of structure that distributes power locally -- with centralized power deriving from the bottom up, by the membership of localized cooperatives. The organizational challenge for expansion is how to avoid administrative capture: how to keep centralized infrastructure controlled by localized entities.
I don't think this "franchise" challenge has been worked out with platform cooperatives. However, if this NY based cooperative becomes profitable, it could expand to other cities not by getting bigger, but by forking off the operational aspects into a cooperative-of-cooperatives, then, a Chicago driver's cooperative could be a member of this shared operational entity.
I disagree with your characterization: it's the potential sharing of capital expenditures (for storage, processing, distribution and advertising) that drives cooperation. In many cases these costs are far more than software-based services. Cooperatives of this nature often have significant capital contributions required for membership.
> True but bonds don't exist in a vacuum and must compete with other alternative investments including other bonds by other businesses/governments.
Agreed. I would note our current legal environment makes it challenging for cooperatives to raise capital since most of their potential contributors, who see the community "main street" value, are effectively prevented from becoming investors, even if they are willing to do so. Retail investors have their arms twisted (401k) to put their savings into the stock market... rather than into main street. Moreover, since they are not often SEC qualified investors, they are prevented from investing even if they wish to do so. There are some limited exceptions for local organizations, but these rules are hard to navigate. These barriers to capital should be addressed.
Farming cooperatives can be very capital intensive.
In contrast, technology platforms are relatively inexpensive to build these days. The value of a platform is proportional to the number of users (drivers) it has: hence, this is a particularly good application of a cooperative structure.
> It takes a lot of capital to pay programmer salaries for desirable features that customers want and since co-ops are capital-constrained (by definition because they can't take millions in investors money), the app will always have less features compared to Uber/Lyft.
There's nothing saying the cooperative cannot have revenue bonds, notes payable as a percentage of revenue. Savvy.coop received funds from https://indie.vc under these terms. Moreover, technologists could contribute well below their market rates in exchange for revenue bonds. https://start.coop is working on these sorts of legal details.
I've not seen this to be the common case. It depends upon the organizational structure. At one extreme, a cooperative can be seen as a limited partnership; but at the other, membership is open to those who meet reasonable criteria.
In cooperatives, there is often a difference between investor shares (if any) and voting shares. Early owners might have some investor shares (notes to cover capital investment) but, their voting shares are often on-par with new members.
In some states, cooperatives are kinds of non-profits; others, such as Colorado, have their own statutory basis that permit investor shares (rather than only allowing notes at a fixed, say, 5% interest rate). The new Illinois worker-cooperative statute permits up-to 50% investor shares, for example -- just short of controlling interest.
Also, it's a bit of semantics here: I'd call this a platform cooperative rather than a worker cooperative.
https://duckduckgo.com/?q=Motel+of+the+Mysteries+by+David+Ma...
This is not necessarily true. If you are the sole copyright owner, you can have your main product be AGPL and sell proprietary extensions; there's no reason why you need to enforce your copyright against yourself. Alternatively, your combined product could be under a proprietary license that is not the AGPL.