How to handle additional task sources

[kurucu]

I'm happy for Automatic Taskfinder to continue to grow and adopt new task sources (two in discussion now are VSCode task.json files and bob.build buildfiles).

However, this poses a few challenges:

1. Ensuring the extension grows usefully, and the UI/UX remains quick and intuitive
2. Ensuring that the extension is maintainable
3. Ensuring others can contribute meaningfully
4. Ensuring that the performance remains fast; a low concern as the sources aren't processes unless enabled on a per-project bases

My personal thoughts on these are as follows, but I'm keen to hear the opinion of others. Thoughts aligned to the numbers above:

1. It could be worth reviewing the settings flow, so that the extension can be quickly customised for each project. But broadly speaking, it's fire and forget. How does onboarding with the extension feel to you?
2. I'm not an expert in all (or many!) task sources - so this is one bottleneck. If others are happy to use Automatic Taskfinder, then I'm happy to receive and review PRs, but I can't build additional features for all imaginable sources - it really depends on the source.
3. Same again really. Three options here in my mind:
   i. This extension remains "the extension" (I don't see any other task extensions in the Nova store). I'm most excited by this idea, but it necessitates this conversation thread.
   ii. I lock the scope of this extension, such that other features should be formed in other extensions. This is my least preferable idea.
   iii. I make a template extension that makes it easy for others to make their own task provider extensions (like a boilerplate, with a detailed readme, comments and maybe even a customisation script).
4. I think performance is probably a non-issue, but worth keeping on the table.