@nihilazo I am not really sure if I concur with that.

For example, there are *good* reasons why the BSD license has the following clause:

"THIS SOFTWARE IS PROVIDED `'AS IS″ AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE."

Writing software, isn't the same as supporting it.

There may be karmic considerations, regardless which I think is closer to your take?

However: developers are users too. SysAdmins are users too (we're just "super" users).

The burden of expecting all users to be supported by developers, is kind of unrealistic; the code itself more often than not: is the primary focus of a developer's contribution and typically facilitates something its users would have to do on their own.

I don't write this to alienate users, most open source developers typically want to co-create and welcome worthwhile contributions (be they bug reports, PRs, typo corrections, etc.) from their community at large.

However, it's also observable on occasion that there can be n00b fatigue in some projects. People asking questions otherwise answered in an FAQ or man page which deplete the patience of those monitoring mailing lists and source code contributions when diluted with questions already sufficiently answered elsewhere.

It's wonderful (ideal, but rarer and certainly not a given) when others within the community at large who are not necessarily the core developers, also put in some effort to help educate and expand the knowledge among the user base as well. That is more of a cultural thing though, and not all projects have it.

@calcifer