4 ms·
> My day-to-day job that actually pays me a salary wouldn't ever provide a bulleted list of the reasons I suck, let alone a project I develop in my spare time.
by matheusmoreira 3y ago
> My day-to-day job that actually pays me a salary wouldn't ever provide a bulleted list of the reasons I suck, let alone a project I develop in my spare time.
The questions you received were:
> Can we expect development from the maintainer?
> How can the community support?
> Are you open to PRs and reviewing them?
> What's your time commitment?
> Should someone just fork the repo and develop it from there?
This is far from a "bulleted list of the reasons I suck". Whoever asked this cared about your project and its future. They just wanted to know what was going on. They might have been intending to contribute patches to you: they specically asked if you were accepting pull requests for review. It's extremely frustrating when you send a patch in and don't get a response.
This was my approach when I received similar questions:
https://github.com/matheusmoreira/liblinux/issues/16 https://github.com/matheusmoreira/liblinux/issues/16
I think it's better to just be sincere and provide the necessary context.