3 ms·
I like it personally. Free to use, pay for support. The distribution of something already made is free. Supporting, understanding your issue, developing a fix
by brightball 4y ago
I like it personally. Free to use, pay for support.
The distribution of something already made is free. Supporting, understanding your issue, developing a fix and releasing it…all of that takes a real person’s time.
As a contractor, you learn very quickly that people will ask for anything if it doesn’t cost them anything. There are a lot of people happy to take advantage of you if you let them.
I like seeing a good model to get OSS devs paid.
- jcparkyn 4y agoI totally agree for things that would normally be described as support (e.g. feature requests or low quality bug reports), but a lot of things aren't that. Personally, if I submit a bug report or PR to an OSS project (which admittedly doesn't happen very often), it's almost always because I think the time I've spent investigating the bug/feature could benefit other users of the project. For my use cases, it's generally much faster and easier (at least in the short term) to just fork a project and make whatever change I need locally, than to wait for it to go through review/merge/release in the original project. Another commenter has pointed out that they make exceptions for certain types of contributions though, which I guess would help with this.