Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Workers of Open Source, Unite!" blog post #1

Open
ahdinosaur opened this issue Oct 17, 2014 · 4 comments
Open

"Workers of Open Source, Unite!" blog post #1

ahdinosaur opened this issue Oct 17, 2014 · 4 comments

Comments

@ahdinosaur
Copy link
Owner

@ahdinosaur ahdinosaur commented Oct 17, 2014

use this issue to discuss the blog post "Workers of Open Source, Unite" :)

@bhaugen
Copy link

@bhaugen bhaugen commented Oct 21, 2014

Beyond awesome!

@marylychee
Copy link

@marylychee marylychee commented Aug 28, 2019

Unite!

@patcon
Copy link

@patcon patcon commented Aug 28, 2019

Yaaaaay! Loving this.

Tweeted: https://twitter.com/patconnolly/status/1166786419458809856

Also, any hypothetical license should be conscious to carve out generous space for government usage imho. Though realistically, they could be served by any carve-outs for worker co-ops, by simply contracting or favouring working with them. (But some old legislation [cough Ontario cough] actually makes it harder for gov to procure from co-operative company structures as a vendor of record, for the reason. But that's a digression ;) )

But it would be a shame if ambiguous language scared them away from using software under such a future license :)

@patcon
Copy link

@patcon patcon commented Aug 29, 2019

haha just realized how old this post was ;)

But still thinking on it. Realizing that if a clause on for-profit commercial use was even token amount ($1/month flat rate), it would force for-profit companies to start building the processes to deal with this, which seems it may be a significant portion of the battle. Once the paths to payment are present, a dev can be like "either we pay $12/year for this. Even if we use it for a decade, it's still cheaper than if we put an in-house developer on this task for only an hour"

But once there are mechanisms, the employees at that company can perhaps start advocating for discussions of true cost and value, and not have to trailblaze through creation of the base process for purely altruistic reasons

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants
You can’t perform that action at this time.