I'm a freelance software developer and I don't have the IP rights for the most software that I write (my clients do).
Regarding the open source licenses, the only one that I completely avoid is the GPL. I'll even avoid the LGPL when I can. I hate infectious licenses.
A couple of months ago I wrote a community bot for the Steemit Betting Community ( @sbcbot ).
I had the idea to make it more general and user-friendly so that the other communities on steemit can use it so I created a github repo and published the stripped down version of the bot to see if there's interest and to see in what direction to take it (features to implement,...)
The only response I got has been a guy taking a dump on it and talking to me as if I'm a half-witted child. That kinda killed my taste for contributing to the opensource.
Yeah, it's hard to gauge when engagement is low like that. On the one hand, does a single response represent 10 other people who felt the same way? Or does it actually represent the one person who spoke up who had a differing opinion?
Either way, I can see why that would be discouraging.
I guess I had high expectations 😃
The bot is built to run on Heroku free dyno and if you're familiar with it you know the limitations that platform has (no permanent disk storage, db can take ~5 minutes to spin up,...)
It's much easier to write a bot that will run on normal hosting, but the free Heroku dyno has been the requirement. Free + convenient deployment = a lot of headaches 😃
I've managed to work around the limitations and I thought it would be interesting to someone, but it appears that nobody wants it. I'm still working on the bot but I don't intend to put it on github again.
Anyhow, I've found your github profile and I see that you wrote the Ruby API client (radiator). Somehow it didn't occur to me to look for the Ruby clients and I went with the official Python lib.
Ruby is my old love, but unfortunately, I'm doing more JS these days. Although JS is not as bad as the popular opinion says, it isn't Ruby either.
I get that free + convenient deployment is a big selling point. But for API access when you want to do things that the API fights against (i.e. getting data you want that takes more than 200ms), I feel like $5/month for a droplet isn't such a bad dea.
It's a great idea actually if it weren't for the one thing.
Currently, I'm running the tech side of the community, but in a case that I need to step down, I can with one click transfer the bot from my account to some member's Heroku account.
That is the main reason that keeps me there. A non-technical user can take over the bot and run with it. No sshing into servers,...
Yeah, I've looked at that. It's a neat feature.