Comments (8)
@jeremyjh @blabaere: As you've already contributed, I'd like to ask for your opinion.
from mioco.pre-0.9.
Actually, I might try to put this project under: http://fosslawyers.org/the-fair-commons-generic-license-v0/ sooner than later. I guess $100/year, paid to Bitcoin address should be an adequate licensing terms for for-profits.
from mioco.pre-0.9.
Given the ridiculously small efforts I have put in mioco, I think you can choose whatever licensing model you like. Regarding potential future contributions, that one is not a problem for me.
So : I agree.
from mioco.pre-0.9.
Honestly, I don't think this is a good idea at all. It's your project, so you can obviously do as you like, but here are my thoughts:
- Ostensibly, the reason for a CopyFair license is to provide a steady income stream to the developers from commercial entities who do not contribute back. $100 is a pittance and vastly under values the work, assuming the goal is to make money from it directly. And it doesn't discriminate between large companies and small (e.g. IBM may be using it for millions of machines, but only pay $100).
- Realistically, few companies will ever pay anything with bitcoin.
- The legal language seems distressingly vague and I doubt most companies will want to touch it.
- If money is paid to the project, does it go to the founder? Committers? Anyone who "contributes" (documentation, community support, conferences, etc)? Seems like a great way to cause drama, especially if the procedure is not enshrined in legal language
I work on OSS full-time at my dayjob, so I'm sympathetic to the idea. But this doesn't seem like a good way to go about it in my opinion.
from mioco.pre-0.9.
My contributions are small and I do not think you should weight my opinion very heavily but I think these sorts of licenses are more suitable for products than for libraries. mioco could be a core part of an import ecosystem of libraries, but a license like this may hold it back, if others do not want to build on top of it. In any case I am fine with whatever you do decide to do with the license.
from mioco.pre-0.9.
Thanks for feedback!
from mioco.pre-0.9.
@jeremyjh : I agree that a strange license etc. might hold back some people.
@polyfractal: I agreed on discriminating small companies. The pricing should be related to company size, true.
I don't understand why companies would have troubles with paying Bitcoin. I actually think that Bitcoin is great: it's worldwide, publicly available, and what's best: fully transparent. Project leaders could use multi-sig wallets to fully transparently hold and distribute funds. Some alternative form of payment (like PayPal) could be provided but IMO, it's a PITA to deal with, and Bitcoin is great for this purpose. If the only problem is "Bitcoin stigma", I don't really care.
I agree about poor state of the-fair-commons-generic-license-v0 . Right now it's unsuitable for anything serious. The idea is right, but legal matters are hairy by nature, and require a lot of detail.
After I posted this comment I actually chewed on this idea, some of the problems you've raised. I think at least for now it's unrealistic to switch mioco to it, so I'll pass and just keep it MPL2. But I've did some sketch on how this could work in practice: https://github.com/CopyFairCorp/copyfair and contacted people behind CopyFair licenses.
from mioco.pre-0.9.
I don't understand why companies would have troubles with paying Bitcoin. I actually think that Bitcoin is great: it's worldwide, publicly available, and what's best: fully transparent. [...] If the only problem is "Bitcoin stigma", I don't really care.
I can think of several, not just the "stigma" (although that really shouldn't be discounted either):
- Not all companies want their activity to be open and transparent, because their tech stack gives them a competitive edge. I work on OSS, and many commercial entities use our software, but some do not wish to be widely known for using it because they feel it is an "edge" over their competition.
- While it might change in the future, the majority of companies do not have a bitcoin account at present. So any request to wire money would be declined simply because they cannot do it. If I were to ask my boss today to wire some BTC, the request would be denied for purely practical reasons.
- Bitcoin vendors have a bad track record with security and unprofessional behavior, and many companies will not want to open themselves up to potential problems. A company will trust Chase bank more than Coinbase for example (even though banks have their own share of problems)
- Bitcoin is illegal in several countries, a list which might grow in the future
- Bitcoin stigma is a real thing, like it or not
Anyhow, those are just my opinions, I'm sure plenty of people would disagree :)
from mioco.pre-0.9.
Related Issues (20)
- Optimising repeated select!s HOT 1
- Is `mioco::get_userdata` sound? HOT 17
- Error handling for TcpStream::connect to non-listening port HOT 3
- `Receiver` should not be always `Send` HOT 5
- Channel panics when mixing `recv()` and `select!` HOT 5
- `UnixListener` is not usable. HOT 2
- Implement `sync_channel`
- `select!` takes at least one tick, which is super slow.
- No way to cancel notifications - select! on a lot of channels in loop can accumulate tons of notifications. HOT 1
- Change the documentation to remove the need for Rust Nightly HOT 2
- Missing openwrt/mipsel support HOT 3
- Prevent using mioco types from multiple thread(coroutines) at the same time. HOT 3
- clear documentation on handling panics HOT 17
- Travis panic
- Test fail in 0.8.0 with rustc stable and beta HOT 1
- Mioco is blocked polling for IO while there are runnable tasks HOT 1
- Mioco compilation with channels and streams fails. HOT 6
- reader.try_read() blocks forever after reading a few bytes
- Colerr mioco-related crash on short program.
- program crashed when run long time HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from mioco.pre-0.9.