I write open-source when I see a gap that needs to be bridged. Like a need in software that is not well tended to or that has been tended to, but in my own personal opinion, I don't like how.
I would write the software in the way I'd like it to be and as long as it is useful for me, I will still have to write it anyway, and why not make it available for others interested.
Open source also helps gain traction and affords us a worldwide recognition. One way or the other, this creates opportunities for the developer.
It becomes a heavy load of work to maintain an open-source project when it has gained traction and the community has grown large enough; bug reports, pull requests, etc. This is when more time needs to be dedicated and companies that make use of such project should help sponsor the project. Moreover they won't need to pay as much as hiring a developer to do the work for them, since many other companies that make use of it would also be a part of the donations.
It's painful when you see commercial products make use of open-source without them giving back to the community that helped create it.
In summary: We write open source when we want to personally write a code we need, and want to open opportunities that can help us financially also. No one invest their time in code that doesn't help them, but other companies/developers.
But when bugs you don't see starts getting reported, that probably means someone else has placed more value on your project than you and to satisfy their need they should help you with a token. It's just help me help you!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Great write up.
I write open-source when I see a gap that needs to be bridged. Like a need in software that is not well tended to or that has been tended to, but in my own personal opinion, I don't like how.
I would write the software in the way I'd like it to be and as long as it is useful for me, I will still have to write it anyway, and why not make it available for others interested.
Open source also helps gain traction and affords us a worldwide recognition. One way or the other, this creates opportunities for the developer.
It becomes a heavy load of work to maintain an open-source project when it has gained traction and the community has grown large enough; bug reports, pull requests, etc. This is when more time needs to be dedicated and companies that make use of such project should help sponsor the project. Moreover they won't need to pay as much as hiring a developer to do the work for them, since many other companies that make use of it would also be a part of the donations.
It's painful when you see commercial products make use of open-source without them giving back to the community that helped create it.
In summary: We write open source when we want to personally write a code we need, and want to open opportunities that can help us financially also. No one invest their time in code that doesn't help them, but other companies/developers.
But when bugs you don't see starts getting reported, that probably means someone else has placed more value on your project than you and to satisfy their need they should help you with a token. It's just help me help you!