Future of Jarvis

[pnhofmann]

I've pushed some experiments to the dev-branch:
https://github.com/sukeesh/Jarvis/tree/dev3

The plan is to bring this project forwards. Biggest changes I worked on:

• New .yaml format to describe plugin metadata
• Allow Enable / Disable plugin; only download pip-packages of enabled plugins (that are actually required!)
• Plugin-architecture for language parser and Frontend (will in future allow Jarvis to run e.g. as GUI or flask service)

Maybe in times of ChatGPT the description "Personal Assistant" is misleading.
As for now, I would describe this project as a highly-hackable framework to share + run useful python-scripts. Both to learn + improve programming skills and because these scripts can be useful.

Additional, I plan to motivate contributors to rather improve existing features than adding new ones, since the number of plugins grew quite a lot over the last years. Probably I'll introduce a new attribute "quality". Every plugin will be set to "legacy". And after any improvement, this level may be raised?

I'll hope to give this project some more love this year ;).