I’m not too familiar with this situation, but I think one thing that would help Open Source in general is a way to signal what level of user the thing is intended to target.
For instance, is this just something that’s being dumped out on the internet in case someone else finds it useful?
Is it part of your portfolio and intended to showcase your technical skill, but not necessarily be polished from a UX perspective?
Or is it intended to be useful for end users?
Maybe it would be good to have a visually distinct and consistent badge or checklist available for open source projects to communicate the high-level goals so that people’s expectations are set correctly and they know what kind of feedback is inappropriate.
Every project is going to nominally be as-is for obvious liability reasons.
- UX Tier 10 for completely tech-illiterate users
- UX Tier 9 for infrequent mainstream users (do not need to watch a tutorial)
- UX Tier 8 for frequent mainstream users (have watched tutorials)
- UX Tier 7 for power users (need to read the manual)
- UX Tier 6 for sysadmin users (responsible for keeping it running for above users)
- UX Tier 5 for domain specialist users (know the theory behind it)
- UX Tier 4 for developers (read the API reference)
- UX Tier 3 for domain specialist developers (API reference and know the theory)
- UX Tier 2 for project ecosystem developers (know conventions and idiomatic patterns)
- UX Tier 1 for the project team itself (know where the skeletons are buried)
- UX Tier 0 for no further development anticipated