Re:Give away your code, but never your time
by rodorgas on Monday September 11, 2017 @09:07PM
(#15223965)
Whether you want give support and maintain the project or just throw the code, it's important to make it clear so people can have reasonable expectations. Also if you want provide paid support, make it clear too.
I've recently saw a license that make the author intentions of not giving support clear: DILLIGASPL (Do I Look Like I Give A Shit Public License)[1]. Sounds like a joke, but it's a way to show what are you up for.
Re:Give away your code, but never your time
by LeoNatan25 on Monday September 11, 2017 @07:10AM
(#15217580)
That statement is made by how I view my open source projects, and thus what I expect from other open source projects. Could be that my expectations are too high, but I don’t believe so. This is not entitlement, it’s expecting a level of seriousness similar to that I am willing to give.
Re:Give away your code, but never your time
by remline on Monday September 11, 2017 @07:13AM
(#15217591)
A community that hasn't established a semaphore for updating the code isn't a community. It is hard to build that with consensus instead of input from its creator.
The nature of what succeeds in opensource has everything to do with whether the creator puts community work in themselves, nominates someone, or just publishes read-only code.
Naturally, anyone is free to do whatever they like.. but most people seem to expect a result from their actions and publishing pure code is rarely going to have any result.
I disagree. Creating an open source project is a gift to the community.
Expecting further time and attention from somebody who gave you a gift, out of a sense of entitlement from having received the gift, is just being rude.
Pay for my time and I'll help you with your issues. Demand my time because you're somehow my "community" and I'll just re-explain the above.