[tarsinge]

I think this a consequence of the open-source marketing strategy of big tech companies and commercialization the parent talked about. When developers use open-source, most of the time maintainers are paid and it’s part of their job, and of the parent company’s strategy.

In this landscape it’s unfortunate but I think one way to avoid this especially if published on GitHub is to be upfront in the README that this is a hobby project with no support, only to be used professionally at your own risks (buried in the license is not enough). Otherwise if projects are presented too similarly to professional ones it’s fair to expect developers to be confused, it’s just unfortunate to what GitHub has turned and that the burden is on hobbyist maintainers to differentiate now but that’s where we are.

And also unfortunate is the practice of resume building by publishing professional looking projects on GitHub that adds to the confusion.

[asoneth]

I like the idea of a standardized way of conveying where the project exists on a spectrum of personal hobby to foundation. I'd personally imagine four levels:

Level 0: This code meets (met?) my personal needs. I'm pleased if you find it useful but do not expect a response to suggestions or bug reports.

Level 1: This tool has a solo maintainer. I'll do my best to incorporate suggestions that fit my vision and address bug reports with reproduction steps when I have free time.

Level 2: This project is maintained by a handful of like-minded contributors. Besides suggestions and bug reports, if you're interested in contributing, please join our discord/element/forum/listserv.

Level 3: This project is maintained by an organization. Before submitting a bug report, please read our wiki.

[x0x0]

This is a late update but the site and docs make it extremely clear it's a level 0. ala here's a thing that may help you; I no longer use it either personally or professionally so adjust your expectations accordingly.

This has not dissuaded people from complaining.