Because time is finite. Apparently you're one of the few developers that doesn't have 10x more feature requests than you have resources to work on them. Good for you. However, that's not the norm.
> why not write a few modules for some other people?
See above. It's a mistake to generalize from young and/or small projects to those that have become large and complex over time.
I would understand if there was no one using this project and it was a one-person operation, but if you are getting so many requests that it is literally impossible to comply with the top 5% of them then you should have made friends with enough people in your community who would be suited for doing these tasks.
Don't get me wrong, I am not saying do every single request and I am definitely not saying spend most of your time doing requests. But my the developers admission, "Taskwarrior [...] is easy to programmatically convert to any other data interchange format."
If it would make that many people happy, to the point where you need to have a link handy to tell them "no", then it might be worth it just to write the feature that everyone seems to want, even if it is in an optionally usable format like a 'module'.
If you're not paying us, you need to convince us that your feature is so great, that it's worth giving up our free time to work on.
This is open source. Scratch thine own itch.
I wrote some introductory Python code 10+ years ago, for one of my classes. I put it online. I now get random college students emailing me personally to ask for help doing their homework.
I distribute some of my software for free. I've since had people demand (yes, demand) essentially hours of free support time to debug their hardware configuration for them because they don't know enough to do it themselves.
When do I get to decide what is "better" for me, rather than do things which are "better" for others?
Being lazy, I spent a weekend teaching myself HTML, and did the Web option. It was linked from the course page on the college's site.
Ten years later I was still getting random emails from people who saw it, noted the .edu domain, and assumed I was an academic expert on Hermetic cults. Thankfully, a reorganization of the college's site and course pages seems to have killed it off for good.
The whole document is about answering each of those common questions individually.
Hey, can you rewrite your documentation in Swedish? It would make my life so much better?
Hey, can you implement I/O using size in English units instead of metric? It would make my life much better.
Hey, can you add a GUI for me? It would make my life much better than using the command-line.
If those where the problems in this document, I would agree. However that is not the case.
"Can you switch from Atlassian to the Github issue tracker? That would be so much better for me.
"Can you switch from a custom CI solution to Travis? That would be so much better for me."
Then two years later someone comes along and says:
"Can you rewrite the documentation in reStructuredText instead of Markdown? That would be so much better for me."
"Can you switch from git to mercurial? That would be so much better for me."
And so on.
When does the madness stop?
But in the end, I am not talking about the devops around the application. The only opinion that really matters there is the one coming from the project owner.
Your obvious attempt straw-man is nothing but opaque.
What I am attempting to discuss are features for the application that the owner refuses to implement because "get out".
Had Linus said that to the first person who emailed him about building an init daemon, I don't think many people would have paid much attention to Linux.
Your analogy with Torvalds isn't that relevant. Building an init daemon didn't conflict with the long-term goals, and the advantages are reasonably clear.
Consider the FOQ "Why is Taskwarrior written in C++ and not something hackable".
We can construct a similar question to pose to Torvalds - "Why is git written in C and not a more modern language like C++?"
We know what Torvalds thinks of C++ ("C++ is a horrible language") and of that proposal.
If he ignored or blew off the first email to suggest rewriting git in C++ then we know exactly where git would be.
This demonstrates that your argument concerning "can you implement X, Y, and Z for me, it would make my life much better" has little predictive or even explanatory power.
"But in the end, I am not talking about the devops around the application. The only opinion that really matters there is the one coming from the project owner. Your obvious attempt straw-man is nothing but opaque."
I am simply addressing the section about the feature requests.
You on the other hand are painting my argument as something it is not about.
Edit: By features I mean anything under "Why Didn't You Implement My Favorite Feature?"
My comments are solely on that section.
For a project owner to need to write a page about these common questions, why would you not instead implement these common requests?
I've often done this in some of my projects, which could be considered a microcosm of this.
I've never heard of this application, but if there is a module system, why not write a few modules for some other people? Unless your api is horrible, it shouldn't be too difficult to implement all of the "Why Didn't You Implement My Favorite Feature?" if you are familiar with the code base.